From e729dcedc6755dba6bb1dac395fb5121d80e61fd Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Wed, 9 Feb 2022 18:19:58 +0000 Subject: [PATCH] Update content of files --- data/core.telegram.org.html | 253 - data/core.telegram.org/api.html | 253 - .../api/account-deletion.html | 129 - .../api/animated-emojis.html | 187 - data/core.telegram.org/api/auth.html | 202 - data/core.telegram.org/api/bots.html | 142 - data/core.telegram.org/api/bots/buttons.html | 242 - data/core.telegram.org/api/bots/commands.html | 140 - data/core.telegram.org/api/bots/games.html | 171 - data/core.telegram.org/api/bots/inline.html | 215 - data/core.telegram.org/api/channel.html | 154 - data/core.telegram.org/api/config.html | 422 - data/core.telegram.org/api/datacenter.html | 152 - data/core.telegram.org/api/dice.html | 149 - data/core.telegram.org/api/discussion.html | 151 - data/core.telegram.org/api/drafts.html | 131 - .../core.telegram.org/api/end-to-end/pfs.html | 176 - .../api/end-to-end/seq_no.html | 173 - .../api/end-to-end/video-calls.html | 215 - .../api/end-to-end/voice-calls.html | 178 - data/core.telegram.org/api/end-to-end_v1.html | 225 - data/core.telegram.org/api/entities.html | 137 - data/core.telegram.org/api/errors.html | 189 - .../core.telegram.org/api/file_reference.html | 125 - data/core.telegram.org/api/files.html | 568 - data/core.telegram.org/api/folders.html | 179 - data/core.telegram.org/api/geochats.html | 115 - data/core.telegram.org/api/import.html | 173 - data/core.telegram.org/api/invoking.html | 154 - data/core.telegram.org/api/live-location.html | 178 - data/core.telegram.org/api/mentions.html | 152 - data/core.telegram.org/api/min.html | 142 - .../api/obtaining_api_id.html | 140 - data/core.telegram.org/api/offsets.html | 170 - data/core.telegram.org/api/optimisation.html | 150 - data/core.telegram.org/api/passport.html | 674 -- data/core.telegram.org/api/pattern.html | 122 - data/core.telegram.org/api/payments.html | 366 - data/core.telegram.org/api/pfs.html | 138 - data/core.telegram.org/api/pin.html | 149 - data/core.telegram.org/api/poll.html | 199 - data/core.telegram.org/api/push-updates.html | 1009 -- data/core.telegram.org/api/qr-login.html | 154 - .../core.telegram.org/api/recent-actions.html | 154 - data/core.telegram.org/api/rights.html | 133 - .../api/scheduled-messages.html | 156 - data/core.telegram.org/api/search.html | 179 - .../api/sponsored-messages.html | 146 - data/core.telegram.org/api/srp.html | 307 - data/core.telegram.org/api/stats.html | 297 - data/core.telegram.org/api/terms.html | 133 - data/core.telegram.org/api/threads.html | 182 - data/core.telegram.org/api/top-rating.html | 145 - data/core.telegram.org/api/updates.html | 226 - .../api/url-authorization.html | 160 - data/core.telegram.org/api/web-events.html | 177 - data/core.telegram.org/apple_privacy.html | 118 - ...hemes-interactive-emoji-read-receipts.html | 115 - data/core.telegram.org/bots.html | 437 - data/core.telegram.org/bots/2-0-intro.html | 230 - .../core.telegram.org/bots/api-changelog.html | 670 -- data/core.telegram.org/bots/api.html | 9488 ----------------- data/core.telegram.org/bots/faq.html | 243 - data/core.telegram.org/bots/games.html | 185 - data/core.telegram.org/bots/inline.html | 182 - data/core.telegram.org/bots/samples.html | 249 - .../bots/samples/hellobot.html | 287 - data/core.telegram.org/bots/self-signed.html | 161 - data/core.telegram.org/bots/webhooks.html | 827 -- data/core.telegram.org/cdn.html | 210 - data/core.telegram.org/cdn/faq_ir.html | 142 - data/core.telegram.org/cdn/faq_ir/durov.html | 133 - .../constructor/account.authorizationForm | 174 - .../constructor/account.authorizations | 147 - .../constructor/account.autoDownloadSettings | 157 - .../constructor/account.chatThemes | 155 - .../constructor/account.chatThemesNotModified | 132 - .../constructor/account.contentSettings | 157 - .../constructor/account.password | 213 - .../constructor/account.passwordInputSettings | 176 - .../constructor/account.passwordSettings | 161 - .../constructor/account.privacyRules | 157 - .../account.resetPasswordFailedWait | 147 - .../constructor/account.resetPasswordOk | 132 - .../account.resetPasswordRequestedWait | 147 - .../constructor/account.sentChangePhoneCode | 161 - .../constructor/account.takeout | 147 - .../constructor/account.themes | 155 - .../constructor/account.themesNotModified | 132 - .../constructor/account.tmpPassword | 152 - .../constructor/account.wallPapers | 155 - .../constructor/account.wallPapersNotModified | 132 - .../constructor/account.webAuthorizations | 152 - .../constructor/accountDaysTTL.html | 147 - .../auth.authorizationSignUpRequired | 155 - .../constructor/auth.codeTypeCall | 132 - .../constructor/auth.codeTypeFlashCall | 132 - .../constructor/auth.codeTypeSms | 132 - .../constructor/auth.exportedAuthorization | 152 - .../constructor/auth.loginToken | 155 - .../constructor/auth.loginTokenMigrateTo | 152 - .../constructor/auth.passwordRecovery | 152 - .../constructor/auth.sentAppCode | 163 - .../constructor/auth.sentCode | 172 - .../constructor/auth.sentCodeTypeApp | 147 - .../constructor/auth.sentCodeTypeFlashCall | 150 - .../constructor/auth.sentCodeTypeSms | 147 - .../constructor/authorization.html | 225 - .../constructor/autoDownloadSettings.html | 187 - .../constructor/bankCardOpenUrl.html | 152 - .../constructor/baseThemeArctic.html | 132 - .../constructor/baseThemeClassic.html | 132 - .../constructor/baseThemeDay.html | 132 - .../constructor/baseThemeNight.html | 132 - .../constructor/baseThemeTinted.html | 132 - .../constructor/boolFalse.html | 132 - .../constructor/boolTrue.html | 132 - .../constructor/botCommand.html | 152 - .../botCommandScopeChatAdmins.html | 135 - .../constructor/botCommandScopeChats.html | 135 - .../constructor/botCommandScopeDefault.html | 132 - .../constructor/botCommandScopePeer.html | 147 - .../botCommandScopePeerAdmins.html | 150 - .../constructor/botCommandScopePeerUser.html | 155 - .../constructor/botCommandScopeUsers.html | 132 - .../constructor/botInfo.html | 157 - .../constructor/botInlineMediaResult.html | 186 - .../botInlineMessageMediaAuto.html | 167 - .../botInlineMessageMediaContact.html | 172 - .../constructor/botInlineMessageMediaGeo.html | 175 - .../botInlineMessageMediaInvoice.html | 189 - .../botInlineMessageMediaVenue.html | 182 - .../constructor/botInlineMessageText.html | 170 - .../constructor/botInlineResult.html | 189 - .../constructor/cdnConfig.html | 149 - .../constructor/cdnPublicKey.html | 154 - .../constructor/channel.html | 289 - .../constructor/channelAdminLogEvent.html | 162 - ...channelAdminLogEventActionChangeAbout.html | 152 - ...elAdminLogEventActionChangeHistoryTTL.html | 152 - ...elAdminLogEventActionChangeLinkedChat.html | 152 - ...nnelAdminLogEventActionChangeLocation.html | 152 - ...channelAdminLogEventActionChangePhoto.html | 152 - ...elAdminLogEventActionChangeStickerSet.html | 152 - ...channelAdminLogEventActionChangeTitle.html | 152 - ...nnelAdminLogEventActionChangeUsername.html | 152 - ...dminLogEventActionDefaultBannedRights.html | 155 - ...annelAdminLogEventActionDeleteMessage.html | 147 - ...elAdminLogEventActionDiscardGroupCall.html | 147 - ...channelAdminLogEventActionEditMessage.html | 152 - ...minLogEventActionExportedInviteDelete.html | 147 - ...AdminLogEventActionExportedInviteEdit.html | 152 - ...minLogEventActionExportedInviteRevoke.html | 147 - ...lAdminLogEventActionParticipantInvite.html | 147 - ...nelAdminLogEventActionParticipantJoin.html | 132 - ...LogEventActionParticipantJoinByInvite.html | 150 - ...elAdminLogEventActionParticipantLeave.html | 132 - ...nelAdminLogEventActionParticipantMute.html | 147 - ...nLogEventActionParticipantToggleAdmin.html | 155 - ...minLogEventActionParticipantToggleBan.html | 155 - ...lAdminLogEventActionParticipantUnmute.html | 147 - ...nnelAdminLogEventActionStartGroupCall.html | 147 - .../channelAdminLogEventActionStopPoll.html | 147 - ...nLogEventActionToggleGroupCallSetting.html | 147 - ...annelAdminLogEventActionToggleInvites.html | 147 - ...nLogEventActionTogglePreHistoryHidden.html | 150 - ...elAdminLogEventActionToggleSignatures.html | 147 - ...nnelAdminLogEventActionToggleSlowMode.html | 155 - ...hannelAdminLogEventActionUpdatePinned.html | 147 - .../channelAdminLogEventsFilter.html | 266 - .../constructor/channelForbidden.html | 177 - .../constructor/channelFull.html | 363 - .../constructor/channelLocation.html | 152 - .../constructor/channelLocationEmpty.html | 132 - .../constructor/channelMessagesFilter.html | 157 - .../channelMessagesFilterEmpty.html | 132 - .../constructor/channelParticipant.html | 152 - .../constructor/channelParticipantAdmin.html | 190 - .../constructor/channelParticipantBanned.html | 175 - .../channelParticipantCreator.html | 162 - .../constructor/channelParticipantLeft.html | 147 - .../constructor/channelParticipantSelf.html | 157 - .../channelParticipantsAdmins.html | 132 - .../channelParticipantsBanned.html | 147 - .../constructor/channelParticipantsBots.html | 132 - .../channelParticipantsContacts.html | 147 - .../channelParticipantsKicked.html | 147 - .../channelParticipantsMentions.html | 161 - .../channelParticipantsRecent.html | 132 - .../channelParticipantsSearch.html | 147 - .../constructor/channels.adminLogResults | 157 - .../constructor/channels.channelParticipants | 162 - .../channels.channelParticipantsNotModified | 132 - data/core.telegram.org/constructor/chat.html | 227 - .../constructor/chatAdminRights.html | 205 - .../constructor/chatAdminWithInvites.html | 157 - .../constructor/chatBannedRights.html | 216 - .../constructor/chatEmpty.html | 147 - .../constructor/chatForbidden.html | 152 - .../constructor/chatFull.html | 231 - .../constructor/chatInvite.html | 190 - .../constructor/chatInviteAlready.html | 147 - .../constructor/chatInviteExported.html | 192 - .../constructor/chatInviteImporter.html | 152 - .../constructor/chatInvitePeek.html | 152 - .../constructor/chatOnlines.html | 147 - .../constructor/chatParticipantAdmin.html | 157 - .../constructor/chatParticipantCreator.html | 147 - .../constructor/chatParticipants.html | 157 - .../chatParticipantsForbidden.html | 157 - .../constructor/chatPhoto.html | 170 - .../constructor/chatPhotoEmpty.html | 132 - .../constructor/chatTheme.html | 157 - .../constructor/codeSettings.html | 166 - .../core.telegram.org/constructor/config.html | 420 - .../constructor/contact.html | 152 - .../constructor/contactStatus.html | 152 - .../constructor/contacts.blocked | 157 - .../constructor/contacts.blockedSlice | 162 - .../constructor/contacts.contacts | 157 - .../constructor/contacts.contactsNotModified | 132 - .../constructor/contacts.found | 162 - .../constructor/contacts.resolvedPeer | 157 - .../constructor/contacts.topPeers | 157 - .../constructor/contacts.topPeersDisabled | 132 - .../constructor/contacts.topPeersNotModified | 132 - .../constructor/dataJSON.html | 147 - .../constructor/dcOption.html | 197 - .../constructor/decryptedMessage.html | 217 - .../decryptedMessageActionAbortKey.html | 148 - .../decryptedMessageActionAcceptKey.html | 160 - .../decryptedMessageActionCommitKey.html | 155 - .../decryptedMessageActionDeleteMessages.html | 148 - .../decryptedMessageActionFlushHistory.html | 133 - .../decryptedMessageActionNoop.html | 133 - .../decryptedMessageActionNotifyLayer.html | 151 - .../decryptedMessageActionReadMessages.html | 148 - .../decryptedMessageActionRequestKey.html | 155 - .../decryptedMessageActionResend.html | 155 - ...ryptedMessageActionScreenshotMessages.html | 148 - .../decryptedMessageActionSetMessageTTL.html | 149 - .../decryptedMessageActionTyping.html | 148 - .../constructor/decryptedMessageLayer.html | 173 - .../decryptedMessageMediaAudio.html | 174 - .../decryptedMessageMediaContact.html | 163 - .../decryptedMessageMediaDocument.html | 191 - .../decryptedMessageMediaEmpty.html | 133 - ...decryptedMessageMediaExternalDocument.html | 183 - .../decryptedMessageMediaGeoPoint.html | 153 - .../decryptedMessageMediaPhoto.html | 191 - .../decryptedMessageMediaVenue.html | 173 - .../decryptedMessageMediaVideo.html | 207 - .../decryptedMessageMediaWebPage.html | 148 - .../constructor/decryptedMessageService.html | 156 - .../core.telegram.org/constructor/dialog.html | 214 - .../constructor/dialogFilter.html | 220 - .../constructor/dialogFilterSuggested.html | 155 - .../constructor/dialogFolder.html | 187 - .../constructor/dialogPeer.html | 147 - .../constructor/dialogPeerFolder.html | 150 - .../constructor/disabledFeature.html | 163 - .../constructor/document.html | 200 - .../documentAttributeAnimated.html | 132 - .../constructor/documentAttributeAudio.html | 172 - .../documentAttributeFilename.html | 147 - .../documentAttributeHasStickers.html | 132 - .../documentAttributeImageSize.html | 152 - .../constructor/documentAttributeSticker.html | 167 - .../constructor/documentAttributeVideo.html | 172 - .../constructor/documentEmpty.html | 147 - .../constructor/draftMessage.html | 177 - .../constructor/draftMessageEmpty.html | 152 - .../constructor/emojiKeyword.html | 152 - .../constructor/emojiKeywordDeleted.html | 152 - .../constructor/emojiKeywordsDifference.html | 162 - .../constructor/emojiLanguage.html | 147 - .../constructor/emojiURL.html | 147 - .../constructor/encryptedChat.html | 177 - .../constructor/encryptedChatDiscarded.html | 157 - .../constructor/encryptedChatEmpty.html | 147 - .../constructor/encryptedChatRequested.html | 185 - .../constructor/encryptedMessage.html | 170 - .../constructor/encryptedMessageService.html | 165 - data/core.telegram.org/constructor/error.html | 152 - .../constructor/exportedMessageLink.html | 152 - .../constructor/fileHash.html | 171 - .../constructor/fileLocation.html | 182 - .../constructor/fileLocationUnavailable.html | 179 - .../core.telegram.org/constructor/folder.html | 177 - .../constructor/folderPeer.html | 155 - data/core.telegram.org/constructor/game.html | 182 - .../constructor/geoPoint.html | 167 - .../constructor/geoPointEmpty.html | 132 - .../constructor/globalPrivacySettings.html | 152 - .../constructor/groupCall.html | 230 - .../constructor/groupCallDiscarded.html | 157 - .../constructor/groupCallParticipant.html | 247 - .../groupCallParticipantVideo.html | 167 - .../groupCallParticipantVideoSourceGroup.html | 152 - .../constructor/help.appUpdate | 190 - .../constructor/help.countriesList | 155 - .../constructor/help.countriesListNotModified | 132 - .../constructor/help.country | 172 - .../constructor/help.countryCode | 162 - .../constructor/help.deepLinkInfo | 165 - .../constructor/help.deepLinkInfoEmpty | 132 - .../constructor/help.inviteText | 147 - .../constructor/help.noAppUpdate | 132 - .../constructor/help.passportConfig | 156 - .../help.passportConfigNotModified | 132 - .../constructor/help.promoData | 182 - .../constructor/help.promoDataEmpty | 147 - .../constructor/help.recentMeUrls | 157 - .../constructor/help.support | 152 - .../constructor/help.supportName | 147 - .../constructor/help.termsOfService | 175 - .../constructor/help.termsOfServiceUpdate | 157 - .../help.termsOfServiceUpdateEmpty | 150 - .../constructor/help.userInfo | 165 - .../constructor/help.userInfoEmpty | 132 - .../constructor/highScore.html | 157 - .../constructor/importedContact.html | 155 - .../constructor/inlineBotSwitchPM.html | 152 - .../inlineQueryPeerTypeBroadcast.html | 135 - .../constructor/inlineQueryPeerTypeChat.html | 135 - .../inlineQueryPeerTypeMegagroup.html | 135 - .../inlineQueryPeerTypeSameBotPM.html | 132 - .../constructor/inputAppEvent.html | 162 - .../inputBotInlineMessageGame.html | 152 - .../constructor/inputBotInlineMessageID.html | 157 - .../inputBotInlineMessageID64.html | 162 - .../inputBotInlineMessageMediaAuto.html | 165 - .../inputBotInlineMessageMediaContact.html | 172 - .../inputBotInlineMessageMediaGeo.html | 175 - .../inputBotInlineMessageMediaInvoice.html | 187 - .../inputBotInlineMessageMediaVenue.html | 182 - .../inputBotInlineMessageText.html | 170 - .../constructor/inputBotInlineResult.html | 189 - .../inputBotInlineResultDocument.html | 179 - .../constructor/inputBotInlineResultGame.html | 157 - .../inputBotInlineResultPhoto.html | 164 - .../constructor/inputChannel.html | 155 - .../constructor/inputChannelEmpty.html | 132 - .../constructor/inputChannelFromMessage.html | 160 - .../constructor/inputChatPhotoEmpty.html | 132 - .../constructor/inputChatUploadedPhoto.html | 165 - .../constructor/inputCheckPasswordEmpty.html | 132 - .../constructor/inputCheckPasswordSRP.html | 160 - .../constructor/inputClientProxy.html | 154 - .../constructor/inputDialogPeer.html | 147 - .../constructor/inputDialogPeerFolder.html | 150 - .../constructor/inputDocument.html | 162 - .../constructor/inputDocumentEmpty.html | 132 - .../inputDocumentFileLocation.html | 167 - .../constructor/inputEncryptedChat.html | 159 - .../constructor/inputEncryptedFile.html | 155 - .../inputEncryptedFileBigUploaded.html | 160 - .../constructor/inputEncryptedFileEmpty.html | 132 - .../inputEncryptedFileLocation.html | 155 - .../inputEncryptedFileUploaded.html | 162 - .../constructor/inputFile.html | 165 - .../constructor/inputFileBig.html | 160 - .../constructor/inputFileLocation.html | 165 - .../constructor/inputFolderPeer.html | 155 - .../constructor/inputGameID.html | 155 - .../constructor/inputGameShortName.html | 152 - .../constructor/inputGeoPoint.html | 162 - .../constructor/inputGeoPointEmpty.html | 132 - .../constructor/inputGroupCall.html | 152 - .../constructor/inputGroupCallStream.html | 172 - .../inputKeyboardButtonUrlAuth.html | 176 - .../constructor/inputMediaContact.html | 162 - .../constructor/inputMediaDice.html | 150 - .../constructor/inputMediaDocument.html | 162 - .../inputMediaDocumentExternal.html | 157 - .../constructor/inputMediaEmpty.html | 132 - .../constructor/inputMediaGame.html | 147 - .../constructor/inputMediaGeoLive.html | 175 - .../constructor/inputMediaGeoPoint.html | 147 - .../constructor/inputMediaInvoice.html | 189 - .../constructor/inputMediaPhoto.html | 157 - .../constructor/inputMediaPoll.html | 170 - .../inputMediaUploadedDocument.html | 190 - .../constructor/inputMediaUploadedPhoto.html | 165 - .../inputMediaUploadedThumbDocument.html | 176 - .../constructor/inputMediaVenue.html | 172 - .../inputMessageCallbackQuery.html | 152 - .../inputMessageEntityMentionName.html | 162 - .../constructor/inputMessageID.html | 147 - .../constructor/inputMessagePinned.html | 132 - .../constructor/inputMessageReplyTo.html | 147 - .../inputMessagesFilterChatPhotos.html | 132 - .../inputMessagesFilterContacts.html | 132 - .../inputMessagesFilterDocument.html | 132 - .../constructor/inputMessagesFilterEmpty.html | 132 - .../constructor/inputMessagesFilterGeo.html | 132 - .../constructor/inputMessagesFilterGif.html | 132 - .../constructor/inputMessagesFilterMusic.html | 132 - .../inputMessagesFilterMyMentions.html | 135 - .../inputMessagesFilterPhoneCalls.html | 152 - .../inputMessagesFilterPhotoVideo.html | 132 - .../inputMessagesFilterPhotos.html | 132 - .../inputMessagesFilterRoundVideo.html | 132 - .../inputMessagesFilterRoundVoice.html | 132 - .../constructor/inputMessagesFilterUrl.html | 132 - .../constructor/inputMessagesFilterVideo.html | 132 - .../constructor/inputNotifyBroadcasts.html | 135 - .../constructor/inputNotifyChats.html | 132 - .../constructor/inputNotifyPeer.html | 147 - .../constructor/inputNotifyUsers.html | 132 - .../constructor/inputPaymentCredentials.html | 157 - .../inputPaymentCredentialsApplePay.html | 147 - .../inputPaymentCredentialsGooglePay.html | 147 - .../inputPaymentCredentialsSaved.html | 152 - .../inputPeerChannelFromMessage.html | 160 - .../constructor/inputPeerChat.html | 147 - .../constructor/inputPeerEmpty.html | 132 - .../constructor/inputPeerNotifySettings.html | 167 - .../inputPeerPhotoFileLocation.html | 162 - .../constructor/inputPeerSelf.html | 132 - .../constructor/inputPeerUser.html | 155 - .../constructor/inputPeerUserFromMessage.html | 160 - .../constructor/inputPhoneCall.html | 152 - .../constructor/inputPhoneContact.html | 166 - .../constructor/inputPhoto.html | 162 - .../constructor/inputPhotoEmpty.html | 132 - .../constructor/inputPhotoFileLocation.html | 171 - .../inputPhotoLegacyFileLocation.html | 172 - .../inputPrivacyKeyAddedByPhone.html | 132 - .../inputPrivacyKeyChatInvite.html | 132 - .../constructor/inputPrivacyKeyForwards.html | 132 - .../constructor/inputPrivacyKeyPhoneCall.html | 132 - .../inputPrivacyKeyPhoneNumber.html | 132 - .../constructor/inputPrivacyKeyPhoneP2P.html | 132 - .../inputPrivacyKeyProfilePhoto.html | 132 - .../inputPrivacyKeyStatusTimestamp.html | 132 - .../inputPrivacyValueAllowAll.html | 132 - ...nputPrivacyValueAllowChatParticipants.html | 147 - .../inputPrivacyValueAllowContacts.html | 132 - .../inputPrivacyValueAllowUsers.html | 147 - .../inputPrivacyValueDisallowAll.html | 132 - ...tPrivacyValueDisallowChatParticipants.html | 147 - .../inputPrivacyValueDisallowUsers.html | 147 - .../inputReportReasonChildAbuse.html | 132 - .../inputReportReasonCopyright.html | 132 - .../constructor/inputReportReasonFake.html | 132 - .../inputReportReasonGeoIrrelevant.html | 132 - .../constructor/inputReportReasonOther.html | 132 - .../inputReportReasonPornography.html | 132 - .../constructor/inputReportReasonSpam.html | 132 - .../inputReportReasonViolence.html | 132 - .../constructor/inputSecureFileLocation.html | 156 - .../constructor/inputSecureFileUploaded.html | 169 - .../constructor/inputSecureValue.html | 190 - .../constructor/inputSingleMedia.html | 174 - ...nputStickerSetAnimatedEmojiAnimations.html | 132 - .../constructor/inputStickerSetEmpty.html | 132 - .../constructor/inputStickerSetItem.html | 162 - .../constructor/inputStickerSetShortName.html | 147 - .../constructor/inputStickerSetThumb.html | 155 - .../inputStickeredMediaDocument.html | 147 - .../constructor/inputStickeredMediaPhoto.html | 147 - .../constructor/inputTakeoutFileLocation.html | 132 - .../constructor/inputTheme.html | 152 - .../constructor/inputThemeSettings.html | 182 - .../constructor/inputThemeSlug.html | 147 - .../constructor/inputUser.html | 155 - .../constructor/inputUserEmpty.html | 132 - .../constructor/inputUserFromMessage.html | 160 - .../constructor/inputUserSelf.html | 132 - .../constructor/inputWallPaper.html | 152 - .../constructor/inputWallPaperNoFile.html | 150 - .../constructor/inputWallPaperSlug.html | 147 - .../constructor/inputWebDocument.html | 165 - .../inputWebFileGeoPointLocation.html | 172 - .../constructor/inputWebFileLocation.html | 152 - .../constructor/invoice.html | 209 - .../constructor/jsonArray.html | 147 - .../constructor/jsonBool.html | 147 - .../constructor/jsonNull.html | 132 - .../constructor/jsonNumber.html | 147 - .../constructor/jsonObject.html | 147 - .../constructor/jsonObjectValue.html | 152 - .../constructor/jsonString.html | 147 - .../constructor/keyboardButton.html | 147 - .../constructor/keyboardButtonBuy.html | 147 - .../constructor/keyboardButtonCallback.html | 167 - .../constructor/keyboardButtonGame.html | 147 - .../keyboardButtonRequestGeoLocation.html | 147 - .../keyboardButtonRequestPhone.html | 147 - .../keyboardButtonRequestPoll.html | 157 - .../constructor/keyboardButtonRow.html | 147 - .../keyboardButtonSwitchInline.html | 162 - .../constructor/keyboardButtonUrl.html | 152 - .../constructor/keyboardButtonUrlAuth.html | 179 - .../constructor/labeledPrice.html | 154 - .../constructor/langPackDifference.html | 162 - .../constructor/langPackLanguage.html | 202 - .../constructor/langPackString.html | 152 - .../constructor/langPackStringDeleted.html | 147 - .../constructor/langPackStringPluralized.html | 182 - .../constructor/maskCoords.html | 169 - .../constructor/message.html | 302 - .../constructor/messageActionBotAllowed.html | 149 - .../messageActionChannelMigrateFrom.html | 155 - .../constructor/messageActionChatAddUser.html | 147 - .../constructor/messageActionChatCreate.html | 152 - .../messageActionChatDeleteUser.html | 147 - .../messageActionChatEditPhoto.html | 147 - .../messageActionChatEditTitle.html | 147 - .../messageActionChatJoinedByLink.html | 147 - .../messageActionChatMigrateTo.html | 150 - .../messageActionContactSignUp.html | 132 - .../messageActionCustomAction.html | 147 - .../constructor/messageActionEmpty.html | 132 - .../constructor/messageActionGameScore.html | 152 - .../constructor/messageActionGroupCall.html | 157 - .../messageActionGroupCallScheduled.html | 152 - .../messageActionHistoryClear.html | 132 - .../constructor/messageActionPaymentSent.html | 154 - .../messageActionPaymentSentMe.html | 179 - .../constructor/messageActionPhoneCall.html | 167 - .../constructor/messageActionPinMessage.html | 132 - .../messageActionSecureValuesSent.html | 149 - .../messageActionSecureValuesSentMe.html | 154 - .../messageActionSetChatTheme.html | 147 - .../messageActionSetMessagesTTL.html | 147 - .../constructor/messageEmpty.html | 157 - .../constructor/messageEntityBankCard.html | 152 - .../constructor/messageEntityBlockquote.html | 152 - .../constructor/messageEntityBold.html | 152 - .../constructor/messageEntityBotCommand.html | 152 - .../constructor/messageEntityCashtag.html | 152 - .../constructor/messageEntityCode.html | 152 - .../constructor/messageEntityEmail.html | 152 - .../constructor/messageEntityHashtag.html | 152 - .../constructor/messageEntityItalic.html | 152 - .../constructor/messageEntityMention.html | 155 - .../constructor/messageEntityMentionName.html | 162 - .../constructor/messageEntityPhone.html | 152 - .../constructor/messageEntityPre.html | 157 - .../constructor/messageEntityStrike.html | 152 - .../constructor/messageEntityTextUrl.html | 160 - .../constructor/messageEntityUnderline.html | 152 - .../constructor/messageEntityUnknown.html | 152 - .../constructor/messageEntityUrl.html | 155 - .../constructor/messageFwdHeader.html | 195 - .../messageInteractionCounters.html | 157 - .../constructor/messageMediaAudio.html | 147 - .../constructor/messageMediaDice.html | 155 - .../constructor/messageMediaDocument.html | 157 - .../constructor/messageMediaEmpty.html | 132 - .../constructor/messageMediaGame.html | 147 - .../constructor/messageMediaGeo.html | 147 - .../constructor/messageMediaGeoLive.html | 170 - .../constructor/messageMediaInvoice.html | 198 - .../constructor/messageMediaPhoto.html | 157 - .../constructor/messageMediaPoll.html | 152 - .../constructor/messageMediaUnsupported.html | 132 - .../constructor/messageMediaVenue.html | 172 - .../constructor/messageMediaVideo.html | 147 - .../constructor/messageMediaWebPage.html | 147 - .../constructor/messageRange.html | 152 - .../constructor/messageReplies.html | 189 - .../constructor/messageReplyHeader.html | 165 - .../constructor/messageService.html | 212 - .../constructor/messageUserVote.html | 157 - .../messageUserVoteInputOption.html | 155 - .../constructor/messageUserVoteMultiple.html | 157 - .../constructor/messageViews.html | 165 - .../messages.affectedFoundMessages | 165 - .../constructor/messages.affectedHistory | 157 - .../constructor/messages.affectedMessages | 155 - .../constructor/messages.allStickers | 155 - .../messages.allStickersNotModified | 132 - .../constructor/messages.archivedStickers | 152 - .../constructor/messages.botResults | 182 - .../messages.chatAdminsWithInvites | 152 - .../constructor/messages.chatFull | 157 - .../constructor/messages.chatInviteImporters | 157 - .../constructor/messages.chats | 147 - .../constructor/messages.chatsSlice | 155 - .../messages.checkedHistoryImportPeer | 150 - .../constructor/messages.dhConfig | 162 - .../constructor/messages.dhConfigNotModified | 147 - .../constructor/messages.dialogsNotModified | 147 - .../constructor/messages.dialogsSlice | 167 - .../constructor/messages.discussionMessage | 185 - .../constructor/messages.exportedChatInvite | 152 - .../constructor/messages.exportedChatInvites | 157 - .../constructor/messages.favedStickers | 160 - .../messages.favedStickersNotModified | 132 - .../constructor/messages.featuredStickers | 165 - .../messages.featuredStickersNotModified | 147 - .../constructor/messages.foundStickerSets | 155 - .../messages.foundStickerSetsNotModified | 132 - .../constructor/messages.highScores | 152 - .../constructor/messages.historyImport | 150 - .../constructor/messages.historyImportParsed | 166 - .../constructor/messages.inactiveChats | 157 - .../constructor/messages.messageEditData | 152 - .../constructor/messages.messageViews | 157 - .../constructor/messages.messagesNotModified | 147 - .../constructor/messages.messagesSlice | 185 - .../constructor/messages.peerDialogs | 170 - .../constructor/messages.recentStickers | 165 - .../messages.recentStickersNotModified | 132 - .../constructor/messages.savedGifs | 155 - .../constructor/messages.savedGifsNotModified | 132 - .../constructor/messages.searchCounter | 165 - .../constructor/messages.sentEncryptedMessage | 147 - .../constructor/messages.sentMessageLink | 167 - .../constructor/messages.sponsoredMessages | 157 - .../constructor/messages.statedMessageLink | 172 - .../constructor/messages.statedMessagesLinks | 172 - .../constructor/messages.stickerSet | 157 - .../messages.stickerSetInstallResultArchive | 147 - .../messages.stickerSetInstallResultSuccess | 132 - .../constructor/messages.stickers | 155 - .../constructor/messages.stickersNotModified | 132 - .../constructor/messages.votesList | 170 - .../constructor/nearestDc.html | 157 - .../constructor/notifyBroadcasts.html | 132 - .../constructor/notifyChats.html | 132 - .../constructor/notifyUsers.html | 132 - data/core.telegram.org/constructor/null.html | 132 - data/core.telegram.org/constructor/page.html | 190 - .../constructor/pageBlockAnchor.html | 147 - .../constructor/pageBlockAudio.html | 155 - .../constructor/pageBlockAuthorDate.html | 152 - .../constructor/pageBlockBlockquote.html | 152 - .../constructor/pageBlockChannel.html | 147 - .../constructor/pageBlockCollage.html | 152 - .../constructor/pageBlockCover.html | 147 - .../constructor/pageBlockDetails.html | 162 - .../constructor/pageBlockDivider.html | 132 - .../constructor/pageBlockEmbed.html | 187 - .../constructor/pageBlockEmbedPost.html | 177 - .../constructor/pageBlockFooter.html | 147 - .../constructor/pageBlockHeader.html | 147 - .../constructor/pageBlockKicker.html | 147 - .../constructor/pageBlockList.html | 147 - .../constructor/pageBlockMap.html | 167 - .../constructor/pageBlockOrderedList.html | 147 - .../constructor/pageBlockParagraph.html | 147 - .../constructor/pageBlockPhoto.html | 167 - .../constructor/pageBlockPreformatted.html | 152 - .../constructor/pageBlockPullquote.html | 152 - .../constructor/pageBlockRelatedArticles.html | 152 - .../constructor/pageBlockSlideshow.html | 152 - .../constructor/pageBlockSubheader.html | 147 - .../constructor/pageBlockSubtitle.html | 147 - .../constructor/pageBlockTitle.html | 147 - .../constructor/pageBlockUnsupported.html | 132 - .../constructor/pageBlockVideo.html | 167 - .../constructor/pageCaption.html | 152 - .../constructor/pageListItemBlocks.html | 147 - .../constructor/pageListItemText.html | 147 - .../constructor/pageListOrderedItemText.html | 152 - .../constructor/pageRelatedArticle.html | 182 - .../constructor/pageTableCell.html | 187 - .../constructor/pageTableRow.html | 147 - ...BKDF2HMACSHA512iter100000SHA256ModPow.html | 165 - .../constructor/passwordKdfAlgoUnknown.html | 132 - .../constructor/paymentCharge.html | 152 - .../constructor/paymentRequestedInfo.html | 167 - .../paymentSavedCredentialsCard.html | 152 - .../payments.ValidatedRequestedInfo | 145 - .../constructor/payments.bankCardData | 152 - .../constructor/payments.paymentForm | 210 - .../constructor/payments.paymentReceipt | 219 - .../constructor/payments.paymentResult | 147 - .../payments.paymentVerificationNeeded | 147 - .../constructor/payments.savedInfo | 157 - .../constructor/peerBlocked.html | 152 - .../constructor/peerChat.html | 147 - .../constructor/peerLocated.html | 157 - .../constructor/peerNotifySettings.html | 182 - .../constructor/peerSelfLocated.html | 147 - .../constructor/peerSettings.html | 197 - .../constructor/peerUser.html | 147 - .../constructor/phone.exportedGroupCallInvite | 147 - .../constructor/phone.groupCall | 170 - .../constructor/phone.groupParticipants | 175 - .../constructor/phone.joinAsPeers | 157 - .../constructor/phone.phoneCall | 152 - .../constructor/phoneCall.html | 209 - .../constructor/phoneCallAccepted.html | 189 - .../phoneCallDiscardReasonBusy.html | 132 - .../phoneCallDiscardReasonDisconnect.html | 132 - .../phoneCallDiscardReasonHangup.html | 132 - .../phoneCallDiscardReasonMissed.html | 132 - .../constructor/phoneCallDiscarded.html | 182 - .../constructor/phoneCallProtocol.html | 179 - .../constructor/phoneCallRequested.html | 189 - .../constructor/phoneCallWaiting.html | 187 - .../constructor/phoneConnection.html | 167 - .../constructor/phoneConnectionWebrtc.html | 187 - data/core.telegram.org/constructor/photo.html | 192 - .../constructor/photoCachedSize.html | 167 - .../constructor/photoEmpty.html | 147 - .../constructor/photoPathSize.html | 155 - .../constructor/photoSize.html | 167 - .../constructor/photoSizeEmpty.html | 150 - .../constructor/photoSizeProgressive.html | 167 - .../constructor/photoStrippedSize.html | 159 - .../constructor/photos.photo | 152 - .../constructor/photos.photos | 152 - .../constructor/photos.photosSlice | 157 - data/core.telegram.org/constructor/poll.html | 195 - .../constructor/pollAnswer.html | 155 - .../constructor/pollAnswerVoters.html | 170 - .../constructor/pollResults.html | 184 - .../constructor/postAddress.html | 172 - .../constructor/privacyKeyAddedByPhone.html | 132 - .../constructor/privacyKeyChatInvite.html | 132 - .../constructor/privacyKeyForwards.html | 132 - .../constructor/privacyKeyPhoneCall.html | 132 - .../constructor/privacyKeyPhoneNumber.html | 132 - .../constructor/privacyKeyPhoneP2P.html | 132 - .../constructor/privacyKeyProfilePhoto.html | 132 - .../privacyKeyStatusTimestamp.html | 132 - .../constructor/privacyValueAllowAll.html | 132 - .../privacyValueAllowChatParticipants.html | 147 - .../privacyValueAllowContacts.html | 132 - .../constructor/privacyValueAllowUsers.html | 147 - .../constructor/privacyValueDisallowAll.html | 132 - .../privacyValueDisallowContacts.html | 132 - .../privacyValueDisallowUsers.html | 147 - .../constructor/receivedNotifyMessage.html | 152 - .../constructor/recentMeUrlChat.html | 152 - .../constructor/recentMeUrlChatInvite.html | 152 - .../constructor/recentMeUrlStickerSet.html | 152 - .../constructor/recentMeUrlUnknown.html | 147 - .../constructor/recentMeUrlUser.html | 152 - .../constructor/replyInlineMarkup.html | 147 - .../constructor/replyKeyboardForceReply.html | 162 - .../constructor/replyKeyboardHide.html | 152 - .../constructor/replyKeyboardMarkup.html | 172 - .../constructor/restrictionReason.html | 158 - .../constructor/savedPhoneContact.html | 162 - .../secureCredentialsEncrypted.html | 159 - .../constructor/secureData.html | 160 - .../constructor/secureFile.html | 180 - .../constructor/secureFileEmpty.html | 132 - ...wordKdfAlgoPBKDF2HMACSHA512iter100000.html | 147 - .../securePasswordKdfAlgoSHA512.html | 147 - .../securePasswordKdfAlgoUnknown.html | 132 - .../constructor/securePlainEmail.html | 150 - .../constructor/securePlainPhone.html | 150 - .../constructor/secureRequiredType.html | 167 - .../constructor/secureSecretSettings.html | 157 - .../constructor/secureValue.html | 194 - .../constructor/secureValueError.html | 157 - .../constructor/secureValueErrorData.html | 175 - .../constructor/secureValueErrorFile.html | 168 - .../constructor/secureValueErrorFiles.html | 168 - .../secureValueErrorFrontSide.html | 166 - .../secureValueErrorReverseSide.html | 162 - .../constructor/secureValueErrorSelfie.html | 166 - .../secureValueErrorTranslationFile.html | 178 - .../secureValueErrorTranslationFiles.html | 178 - .../constructor/secureValueTypeAddress.html | 132 - .../secureValueTypeBankStatement.html | 132 - .../secureValueTypeDriverLicense.html | 132 - .../constructor/secureValueTypeEmail.html | 132 - .../secureValueTypeIdentityCard.html | 132 - .../secureValueTypeInternalPassport.html | 134 - .../constructor/secureValueTypePassport.html | 132 - .../secureValueTypePassportRegistration.html | 134 - .../secureValueTypePersonalDetails.html | 132 - .../constructor/secureValueTypePhone.html | 132 - .../secureValueTypeRentalAgreement.html | 132 - .../secureValueTypeTemporaryRegistration.html | 132 - .../secureValueTypeUtilityBill.html | 132 - .../constructor/sendMessageCancelAction.html | 132 - .../sendMessageChooseContactAction.html | 132 - .../sendMessageChooseStickerAction.html | 132 - .../sendMessageEmojiInteractionSeen.html | 150 - .../sendMessageGamePlayAction.html | 132 - .../sendMessageGeoLocationAction.html | 132 - .../sendMessageHistoryImportAction.html | 147 - .../sendMessageRecordAudioAction.html | 132 - .../sendMessageRecordRoundAction.html | 132 - .../sendMessageRecordVideoAction.html | 132 - .../constructor/sendMessageTypingAction.html | 132 - .../sendMessageUploadAudioAction.html | 147 - .../sendMessageUploadDocumentAction.html | 147 - .../sendMessageUploadRoundAction.html | 147 - .../sendMessageUploadVideoAction.html | 147 - .../constructor/shippingOption.html | 157 - .../speakingInGroupCallAction.html | 132 - .../constructor/sponsoredMessage.html | 178 - .../constructor/stats.broadcastStats | 220 - .../constructor/stats.megagroupStats | 230 - .../constructor/stats.messageStats | 147 - .../constructor/statsAbsValueAndPrev.html | 152 - .../constructor/statsDateRangeDays.html | 155 - .../constructor/statsGraph.html | 160 - .../constructor/statsGraphAsync.html | 152 - .../constructor/statsGraphError.html | 150 - .../constructor/statsGroupTopAdmin.html | 165 - .../constructor/statsGroupTopInviter.html | 155 - .../constructor/statsPercentValue.html | 156 - .../constructor/statsURL.html | 147 - .../constructor/stickerPack.html | 156 - .../constructor/stickerSet.html | 217 - .../constructor/stickerSetCovered.html | 152 - .../constructor/stickerSetMultiCovered.html | 152 - .../constructor/stickers.suggestedShortName | 147 - .../constructor/storage.fileGif | 132 - .../constructor/storage.fileJpeg | 132 - .../constructor/storage.fileMov | 132 - .../constructor/storage.fileMp3 | 132 - .../constructor/storage.fileMp4 | 132 - .../constructor/storage.filePartial | 132 - .../constructor/storage.filePdf | 132 - .../constructor/storage.filePng | 132 - .../constructor/storage.fileUnknown | 132 - .../constructor/storage.fileWebp | 132 - .../constructor/textAnchor.html | 152 - .../constructor/textBold.html | 147 - .../constructor/textConcat.html | 147 - .../constructor/textEmail.html | 152 - .../constructor/textEmpty.html | 132 - .../constructor/textFixed.html | 147 - .../constructor/textImage.html | 157 - .../constructor/textItalic.html | 147 - .../constructor/textMarked.html | 147 - .../constructor/textStrike.html | 147 - .../constructor/textSubscript.html | 147 - .../constructor/textSuperscript.html | 147 - .../constructor/textUnderline.html | 147 - .../constructor/textUrl.html | 157 - data/core.telegram.org/constructor/theme.html | 197 - .../constructor/themeSettings.html | 177 - .../constructor/topPeer.html | 155 - .../topPeerCategoryBotsInline.html | 132 - .../constructor/topPeerCategoryBotsPM.html | 132 - .../constructor/topPeerCategoryChannels.html | 132 - .../topPeerCategoryCorrespondents.html | 132 - .../topPeerCategoryForwardChats.html | 132 - .../topPeerCategoryForwardUsers.html | 132 - .../constructor/topPeerCategoryGroups.html | 132 - .../topPeerCategoryPhoneCalls.html | 132 - data/core.telegram.org/constructor/true.html | 134 - .../constructor/updateBotCallbackQuery.html | 182 - .../constructor/updateBotCommands.html | 159 - .../constructor/updateBotInlineQuery.html | 177 - .../constructor/updateBotShippingQuery.html | 162 - .../constructor/updateBotStopped.html | 165 - .../constructor/updateBotWebhookJSON.html | 147 - .../updateBotWebhookJSONQuery.html | 157 - .../constructor/updateChannel.html | 147 - .../updateChannelMessageForwards.html | 157 - .../updateChannelMessageViews.html | 157 - .../constructor/updateChannelParticipant.html | 192 - .../updateChannelReadMessagesContents.html | 155 - .../constructor/updateChannelTooLong.html | 161 - .../constructor/updateChannelUserTyping.html | 172 - .../constructor/updateChannelWebPage.html | 167 - .../constructor/updateChat.html | 147 - .../updateChatDefaultBannedRights.html | 160 - .../constructor/updateChatParticipantAdd.html | 167 - .../updateChatParticipantAdmin.html | 165 - .../updateChatParticipantDelete.html | 157 - .../constructor/updateChatParticipants.html | 147 - .../constructor/updateChatUserTyping.html | 160 - .../constructor/updateConfig.html | 135 - .../constructor/updateDcOptions.html | 147 - .../updateDeleteChannelMessages.html | 167 - .../constructor/updateDeleteMessages.html | 160 - .../updateDeleteScheduledMessages.html | 155 - .../constructor/updateDialogFilterOrder.html | 150 - .../constructor/updateDialogFilters.html | 135 - .../constructor/updateDialogPinned.html | 165 - .../constructor/updateDialogUnreadMark.html | 157 - .../constructor/updateDraftMessage.html | 155 - .../constructor/updateEditChannelMessage.html | 162 - .../constructor/updateEditMessage.html | 160 - .../updateEncryptedChatTyping.html | 147 - .../updateEncryptedMessagesRead.html | 157 - .../constructor/updateEncryption.html | 152 - .../constructor/updateFavedStickers.html | 135 - .../constructor/updateFolderPeers.html | 162 - .../constructor/updateGeoLiveViewed.html | 152 - .../constructor/updateGroupCall.html | 155 - .../updateGroupCallConnection.html | 157 - .../updateGroupCallParticipants.html | 157 - .../constructor/updateLangPack.html | 147 - .../constructor/updateLangPackTooLong.html | 150 - .../constructor/updateLoginToken.html | 132 - .../constructor/updateMessageID.html | 155 - .../constructor/updateMessagePoll.html | 162 - .../constructor/updateMessagePollVote.html | 165 - .../constructor/updateNewChannelMessage.html | 162 - .../updateNewEncryptedMessage.html | 155 - .../constructor/updateNewMessage.html | 157 - .../updateNewScheduledMessage.html | 150 - .../constructor/updateNewStickerSet.html | 147 - .../constructor/updateNotifySettings.html | 152 - .../constructor/updatePeerBlocked.html | 152 - .../constructor/updatePeerLocated.html | 147 - .../constructor/updatePeerSettings.html | 152 - .../constructor/updatePhoneCall.html | 147 - .../updatePhoneCallSignalingData.html | 152 - .../updatePinnedChannelMessages.html | 177 - .../constructor/updatePinnedDialogs.html | 160 - .../constructor/updatePinnedMessages.html | 175 - .../constructor/updatePrivacy.html | 152 - .../constructor/updatePtsChanged.html | 135 - .../updateReadChannelDiscussionInbox.html | 177 - .../updateReadChannelDiscussionOutbox.html | 162 - .../constructor/updateReadChannelInbox.html | 179 - .../constructor/updateReadChannelOutbox.html | 155 - .../updateReadFeaturedStickers.html | 132 - .../constructor/updateReadHistoryInbox.html | 182 - .../constructor/updateReadHistoryOutbox.html | 165 - .../updateReadMessagesContents.html | 160 - .../constructor/updateRecentStickers.html | 132 - .../constructor/updateSavedGifs.html | 132 - .../updateServiceNotification.html | 183 - .../constructor/updateShort.html | 152 - .../constructor/updateShortMessage.html | 229 - .../constructor/updateShortSentMessage.html | 192 - .../constructor/updateStickerSets.html | 132 - .../constructor/updateStickerSetsOrder.html | 157 - .../constructor/updateTheme.html | 147 - .../constructor/updateUserBlocked.html | 159 - .../constructor/updateUserName.html | 167 - .../constructor/updateUserPhone.html | 152 - .../constructor/updateUserPhoto.html | 165 - .../constructor/updateUserStatus.html | 152 - .../constructor/updateUserTyping.html | 155 - .../constructor/updateWebPage.html | 160 - .../constructor/updates.channelDifference | 185 - .../updates.channelDifferenceEmpty | 165 - .../updates.channelDifferenceTooLong | 190 - .../constructor/updates.difference | 172 - .../constructor/updates.differenceEmpty | 152 - .../constructor/updates.differenceSlice | 175 - .../constructor/updates.differenceTooLong | 150 - .../constructor/updates.html | 167 - .../constructor/updates.state | 172 - .../constructor/updatesCombined.html | 172 - .../constructor/updatesTooLong.html | 135 - .../constructor/upload.cdnFile | 149 - .../constructor/upload.cdnFileReuploadNeeded | 149 - .../core.telegram.org/constructor/upload.file | 157 - .../constructor/upload.fileCdnRedirect | 169 - .../constructor/upload.webFile | 170 - .../constructor/urlAuthResultAccepted.html | 150 - .../constructor/urlAuthResultDefault.html | 135 - .../constructor/urlAuthResultRequest.html | 165 - data/core.telegram.org/constructor/user.html | 287 - .../constructor/userFull.html | 239 - .../constructor/userProfilePhoto.html | 172 - .../constructor/userProfilePhotoEmpty.html | 132 - .../constructor/userStatusEmpty.html | 132 - .../constructor/userStatusLastMonth.html | 132 - .../constructor/userStatusLastWeek.html | 132 - .../constructor/userStatusOffline.html | 147 - .../constructor/userStatusOnline.html | 147 - .../constructor/userStatusRecently.html | 132 - .../core.telegram.org/constructor/vector.html | 134 - .../constructor/videoSize.html | 175 - .../constructor/wallPaper.html | 192 - .../constructor/wallPaperNoFile.html | 171 - .../constructor/wallPaperSettings.html | 187 - .../constructor/wallPaperSolid.html | 162 - .../constructor/webAuthorization.html | 189 - .../constructor/webDocument.html | 167 - .../constructor/webPage.html | 240 - .../constructor/webPageAttributeTheme.html | 157 - .../constructor/webPageEmpty.html | 147 - .../constructor/webPageNotModified.html | 152 - .../constructor/webPagePending.html | 152 - data/core.telegram.org/contest300K.html | 237 - .../core.telegram.org/css/bootstrap-extra.css | 3274 ------ data/core.telegram.org/css/core-widgets.css | 105 - data/core.telegram.org/css/telegram-extra.css | 246 - data/core.telegram.org/getProxyConfig.html | 24 - data/core.telegram.org/import-stickers.html | 159 - data/core.telegram.org/js/core-widgets.js | 279 - data/core.telegram.org/js/jquery-ui.min.js | 9 - .../js/telegram-passport2.js | 413 - .../method/account.acceptAuthorization | 170 - .../method/account.cancelPasswordEmail | 138 - .../method/account.changePhone | 190 - .../method/account.checkUsername | 167 - .../method/account.confirmPasswordEmail | 175 - .../method/account.confirmPhone | 180 - .../method/account.createTheme | 186 - .../method/account.declinePasswordReset | 155 - .../method/account.deleteAccount | 170 - .../method/account.deleteSecureValue | 153 - .../method/account.finishTakeoutSession | 172 - .../method/account.getAccountTTL | 134 - .../method/account.getAllSecureValues | 136 - .../method/account.getAuthorizationForm | 176 - .../method/account.getAuthorizations | 134 - .../method/account.getAutoDownloadSettings | 134 - .../method/account.getChatThemes | 153 - .../account.getContactSignUpNotification | 135 - .../method/account.getContentSettings | 134 - .../method/account.getGlobalPrivacySettings | 134 - .../method/account.getMultiWallPapers | 148 - .../method/account.getNotifyExceptions | 165 - .../method/account.getPassword | 134 - .../method/account.getPasswordSettings | 170 - .../method/account.getPrivacy | 166 - .../method/account.getSecureValue | 151 - .../core.telegram.org/method/account.getTheme | 181 - .../method/account.getThemes | 158 - .../method/account.getTmpPassword | 176 - .../method/account.getWallPaper | 167 - .../method/account.getWallPapers | 153 - .../method/account.getWebAuthorizations | 136 - .../method/account.initTakeoutSession | 204 - .../method/account.installTheme | 165 - .../method/account.installWallPaper | 172 - .../method/account.registerDevice | 217 - .../method/account.reportPeer | 182 - .../method/account.reportProfilePhoto | 165 - .../method/account.resendPasswordEmail | 138 - .../method/account.resetAuthorization | 175 - .../method/account.resetNotifySettings | 135 - .../method/account.resetPassword | 139 - .../method/account.resetWebAuthorization | 171 - .../method/account.resetWebAuthorizations | 137 - .../method/account.saveSecureValue | 174 - .../method/account.saveTheme | 155 - .../method/account.saveWallPaper | 177 - .../method/account.sendChangePhoneCode | 186 - .../method/account.sendConfirmPhoneCode | 174 - .../method/account.sendVerifyEmailCode | 168 - .../method/account.sendVerifyPhoneCode | 173 - .../method/account.setAccountTTL | 167 - .../account.setContactSignUpNotification | 150 - .../method/account.setContentSettings | 172 - .../method/account.setGlobalPrivacySettings | 166 - .../method/account.setPrivacy | 181 - .../method/account.unregisterDevice | 180 - .../method/account.updateDeviceLocked | 153 - .../method/account.updateNotifySettings | 192 - .../method/account.updatePasswordSettings | 207 - .../method/account.updateProfile | 187 - .../method/account.updateStatus | 155 - .../method/account.updateTheme | 196 - .../method/account.updateUsername | 182 - .../method/account.uploadTheme | 190 - .../method/account.uploadWallPaper | 182 - .../method/account.verifyEmail | 179 - .../method/account.verifyPhone | 191 - .../method/auth.acceptLoginToken | 171 - data/core.telegram.org/method/auth.cancelCode | 180 - .../method/auth.checkPassword | 180 - data/core.telegram.org/method/auth.checkPhone | 176 - .../method/auth.checkRecoveryPassword | 174 - .../method/auth.dropTempAuthKeys | 151 - .../method/auth.exportAuthorization | 167 - .../method/auth.exportLoginToken | 183 - .../method/auth.importAuthorization | 178 - .../method/auth.importBotAuthorization | 205 - .../method/auth.importLoginToken | 187 - .../method/auth.recoverPassword | 187 - .../method/auth.requestPasswordRecovery | 159 - data/core.telegram.org/method/auth.resendCode | 191 - .../method/auth.resetAuthorizations | 156 - data/core.telegram.org/method/auth.sendCall | 175 - data/core.telegram.org/method/auth.sendCode | 236 - .../core.telegram.org/method/auth.sendInvites | 157 - data/core.telegram.org/method/auth.sendSms | 167 - data/core.telegram.org/method/auth.signIn | 219 - data/core.telegram.org/method/auth.signUp | 236 - .../method/bots.answerWebhookJSONQuery | 178 - .../method/bots.getBotCommands | 154 - .../method/bots.resetBotCommands | 156 - .../method/bots.sendCustomRequest | 177 - .../method/bots.setBotCommands | 188 - .../method/channels.checkUsername | 190 - .../method/channels.convertToGigagroup | 177 - .../method/channels.createChannel | 232 - .../method/channels.deleteChannel | 200 - .../method/channels.deleteHistory | 180 - .../method/channels.editAdmin | 301 - .../method/channels.editBanned | 241 - .../method/channels.editLocation | 180 - .../method/channels.editPhoto | 221 - .../method/channels.editTitle | 206 - .../method/channels.exportMessageLink | 204 - .../method/channels.getAdminLog | 226 - .../method/channels.getAdminedPublicChannels | 191 - .../method/channels.getChannels | 181 - .../method/channels.getGroupsForDiscussion | 144 - .../method/channels.getInactiveChannels | 134 - .../method/channels.getLeftChannels | 172 - .../method/channels.getMessages | 193 - .../method/channels.getParticipant | 205 - .../method/channels.getParticipants | 203 - .../method/channels.getSponsoredMessages | 154 - .../method/channels.inviteToChannel | 262 - .../method/channels.joinChannel | 227 - .../method/channels.leaveChannel | 201 - .../method/channels.readMessageContents | 185 - .../method/channels.reportSpam | 192 - .../method/channels.setDiscussionGroup | 200 - .../method/channels.setStickers | 183 - .../method/channels.togglePreHistoryHidden | 202 - .../method/channels.toggleSignatures | 187 - .../method/channels.toggleSlowMode | 190 - .../method/channels.updateUsername | 212 - .../method/contacts.acceptContact | 190 - data/core.telegram.org/method/contacts.block | 182 - .../method/contacts.blockFromReplies | 178 - .../method/contacts.deleteByPhones | 150 - .../method/contacts.deleteContacts | 155 - .../method/contacts.getBlocked | 155 - .../method/contacts.getContactIDs | 151 - .../method/contacts.getContacts | 155 - .../method/contacts.getLocated | 197 - .../method/contacts.getSaved | 150 - .../method/contacts.getStatuses | 133 - .../method/contacts.getTopPeers | 226 - .../method/contacts.importContacts | 154 - .../method/contacts.resetSaved | 135 - .../method/contacts.resetTopPeerRating | 175 - .../method/contacts.resolveUsername | 182 - data/core.telegram.org/method/contacts.search | 178 - .../method/contacts.toggleTopPeers | 153 - .../core.telegram.org/method/contacts.unblock | 182 - .../method/folders.deleteFolder | 175 - .../method/folders.editPeerFolders | 175 - .../method/help.acceptTermsOfService | 150 - .../method/help.dismissSuggestion | 160 - .../method/help.editUserInfo | 180 - .../method/help.getAppChangelog | 162 - .../method/help.getAppConfig | 142 - .../method/help.getAppUpdate | 150 - .../method/help.getCdnConfig | 154 - data/core.telegram.org/method/help.getConfig | 192 - .../method/help.getCountriesList | 158 - .../method/help.getDeepLinkInfo | 150 - .../method/help.getInviteText | 134 - .../method/help.getPassportConfig | 154 - .../method/help.getPromoData | 135 - .../method/help.getProxyData | 132 - .../method/help.getRecentMeUrls | 149 - data/core.telegram.org/method/help.getSupport | 134 - .../method/help.getSupportName | 151 - .../method/help.getTermsOfServiceUpdate | 135 - .../core.telegram.org/method/help.getUserInfo | 167 - .../method/help.hidePromoData | 150 - data/core.telegram.org/method/help.saveAppLog | 150 - .../method/help.setBotUpdatesStatus | 156 - .../method/initConnection.html | 216 - .../method/invokeAfterMsg.html | 154 - .../method/invokeAfterMsgs.html | 154 - .../method/invokeWithLayer.html | 204 - .../method/invokeWithTakeout.html | 154 - .../method/invokeWithoutUpdates.html | 154 - .../method/langpack.getDifference | 176 - .../method/langpack.getLangPack | 171 - .../method/langpack.getLanguage | 154 - .../method/langpack.getLanguages | 165 - .../method/messages.acceptEncryption | 190 - .../method/messages.addChatUser | 237 - .../method/messages.checkHistoryImport | 152 - .../method/messages.checkHistoryImportPeer | 172 - .../method/messages.clearAllDrafts | 138 - .../method/messages.clearRecentStickers | 155 - .../method/messages.createChat | 197 - .../method/messages.deleteChat | 170 - .../method/messages.deleteChatUser | 208 - .../method/messages.deleteExportedChatInvite | 155 - .../method/messages.deleteHistory | 206 - .../method/messages.deletePhoneCallHistory | 154 - .../messages.deleteRevokedExportedChatInvites | 155 - .../method/messages.deleteScheduledMessages | 160 - .../method/messages.discardEncryption | 187 - .../method/messages.editChatAbout | 216 - .../method/messages.editChatAdmin | 195 - .../messages.editChatDefaultBannedRights | 206 - .../method/messages.editChatPhoto | 203 - .../method/messages.editChatTitle | 193 - .../method/messages.editExportedChatInvite | 193 - .../method/messages.editInlineBotMessage | 206 - .../method/messages.editMessage | 338 - .../method/messages.exportChatInvite | 217 - .../method/messages.faveSticker | 172 - .../method/messages.forwardMessage | 177 - .../method/messages.forwardMessages | 363 - .../method/messages.getAdminsWithInvites | 149 - .../method/messages.getAllChats | 150 - .../method/messages.getAllDrafts | 143 - .../method/messages.getAllStickers | 153 - .../method/messages.getArchivedStickers | 167 - .../method/messages.getAttachedStickers | 148 - .../method/messages.getBotCallbackAnswer | 226 - .../method/messages.getChatInviteImporters | 172 - .../method/messages.getChats | 173 - .../method/messages.getCommonChats | 185 - .../method/messages.getDhConfig | 175 - .../method/messages.getDialogFilters | 136 - .../method/messages.getDialogUnreadMarks | 133 - .../method/messages.getDialogs | 213 - .../method/messages.getDiscussionMessage | 183 - .../method/messages.getDocumentByHash | 178 - .../method/messages.getEmojiKeywords | 149 - .../messages.getEmojiKeywordsDifference | 154 - .../method/messages.getEmojiKeywordsLanguages | 148 - .../method/messages.getEmojiURL | 149 - .../method/messages.getExportedChatInvite | 155 - .../method/messages.getExportedChatInvites | 182 - .../method/messages.getFeaturedStickers | 153 - .../method/messages.getGameHighScores | 187 - .../method/messages.getInlineBotResults | 226 - .../method/messages.getInlineGameHighScores | 177 - .../method/messages.getMaskStickers | 153 - .../method/messages.getMessageEditData | 186 - .../method/messages.getMessageReactionsList | 178 - .../messages.getMessageReadParticipants | 173 - .../method/messages.getMessages | 153 - .../method/messages.getMessagesReactions | 153 - .../method/messages.getMessagesViews | 199 - .../method/messages.getOldFeaturedStickers | 163 - .../method/messages.getOnlines | 171 - .../method/messages.getPeerDialogs | 181 - .../method/messages.getPeerSettings | 171 - .../method/messages.getPinnedDialogs | 169 - .../method/messages.getPollResults | 177 - .../method/messages.getPollVotes | 204 - .../method/messages.getRecentLocations | 165 - .../method/messages.getReplies | 217 - .../method/messages.getSavedGifs | 153 - .../method/messages.getScheduledHistory | 182 - .../method/messages.getScheduledMessages | 179 - .../method/messages.getSearchCounters | 173 - .../method/messages.getSplitRanges | 133 - .../method/messages.getStickerSet | 172 - .../method/messages.getStickers | 175 - .../method/messages.getSuggestedDialogFilters | 136 - .../method/messages.getUnreadMentions | 212 - .../method/messages.getWebPage | 177 - .../method/messages.getWebPagePreview | 191 - .../method/messages.hidePeerSettingsBar | 153 - .../method/messages.importChatInvite | 227 - .../method/messages.initHistoryImport | 191 - .../method/messages.installStickerSet | 172 - .../method/messages.markDialogUnread | 160 - .../method/messages.migrateChat | 190 - .../method/messages.readDiscussion | 180 - .../method/messages.readEncryptedHistory | 172 - .../method/messages.readFeaturedStickers | 150 - .../method/messages.readMentions | 181 - .../method/messages.readMessageContents | 149 - .../method/messages.receivedMessages | 148 - .../method/messages.receivedQueue | 170 - .../method/messages.reorderPinnedDialogs | 185 - .../method/messages.reorderStickerSets | 160 - data/core.telegram.org/method/messages.report | 187 - .../method/messages.reportEncryptedSpam | 167 - .../method/messages.reportSpam | 180 - .../method/messages.requestEncryption | 185 - .../method/messages.requestUrlAuth | 174 - .../method/messages.saveDraft | 202 - .../core.telegram.org/method/messages.saveGif | 172 - .../method/messages.saveRecentSticker | 182 - data/core.telegram.org/method/messages.search | 291 - .../method/messages.searchGifs | 177 - .../method/messages.searchGlobal | 226 - .../method/messages.searchStickerSets | 168 - .../method/messages.sendBroadcast | 145 - .../method/messages.sendEncrypted | 210 - .../method/messages.sendEncryptedFile | 215 - .../method/messages.sendEncryptedService | 205 - .../method/messages.sendInlineBotResult | 344 - .../method/messages.sendMedia | 518 - .../method/messages.sendMessage | 398 - .../method/messages.sendMultiMedia | 263 - .../method/messages.sendReaction | 185 - .../method/messages.sendScheduledMessages | 182 - .../messages.sendScreenshotNotification | 187 - .../method/messages.sendVote | 220 - .../method/messages.setBotCallbackAnswer | 203 - .../method/messages.setBotPrecheckoutResults | 188 - .../method/messages.setBotShippingResults | 186 - .../method/messages.setChatTheme | 185 - .../method/messages.setEncryptedTyping | 177 - .../method/messages.setGameScore | 218 - .../method/messages.setHistoryTTL | 182 - .../method/messages.setInlineBotResults | 358 - .../method/messages.setInlineGameScore | 198 - .../method/messages.setTyping | 240 - .../method/messages.startBot | 224 - .../method/messages.startHistoryImport | 180 - .../method/messages.toggleDialogPin | 187 - .../method/messages.toggleStickerSets | 170 - .../method/messages.uninstallStickerSet | 167 - .../method/messages.updateDialogFilter | 190 - .../method/messages.updateDialogFiltersOrder | 153 - .../method/messages.updatePinnedMessage | 233 - .../method/messages.uploadEncryptedFile | 155 - .../method/messages.uploadMedia | 264 - .../method/payments.clearSavedInfo | 160 - .../method/payments.getBankCardData | 166 - .../method/payments.getPaymentForm | 181 - .../method/payments.getPaymentReceipt | 171 - .../method/payments.getSavedInfo | 134 - .../method/payments.sendPaymentForm | 206 - .../method/payments.validateRequestedInfo | 186 - .../method/phone.checkGroupCall | 154 - .../method/phone.confirmCall | 188 - .../method/phone.createGroupCall | 200 - .../method/phone.discardCall | 202 - .../method/phone.editGroupCallMember | 167 - .../method/phone.editGroupCallParticipant | 225 - .../method/phone.editGroupCallTitle | 160 - .../method/phone.exportGroupCallInvite | 159 - .../method/phone.getCallConfig | 134 - .../method/phone.getGroupCall | 157 - .../method/phone.getGroupCallJoinAs | 149 - .../method/phone.getGroupParticipants | 174 - .../method/phone.inviteToGroupCall | 177 - .../method/phone.joinGroupCall | 202 - .../method/phone.joinGroupCallPresentation | 180 - .../method/phone.leaveGroupCall | 160 - .../method/phone.leaveGroupCallPresentation | 155 - .../method/phone.receivedCall | 172 - .../method/phone.requestCall | 213 - .../method/phone.saveCallDebug | 177 - .../method/phone.saveDefaultGroupCallJoinAs | 155 - .../method/phone.sendSignalingData | 155 - .../method/phone.setCallRating | 192 - .../method/phone.startScheduledGroupCall | 155 - .../method/phone.toggleGroupCallRecord | 180 - .../method/phone.toggleGroupCallSettings | 187 - .../phone.toggleGroupCallStartSubscription | 160 - .../method/photos.deletePhotos | 148 - .../method/photos.getUserPhotos | 193 - .../method/photos.updateProfilePhoto | 196 - .../method/stats.getBroadcastStats | 194 - .../method/stats.getMegagroupStats | 191 - .../method/stats.getMessagePublicForwards | 212 - .../method/stats.getMessageStats | 189 - .../method/stats.loadAsyncGraph | 193 - .../method/stickers.addStickerToSet | 187 - .../method/stickers.changeStickerPosition | 177 - .../method/stickers.checkShortName | 172 - .../method/stickers.removeStickerFromSet | 172 - .../method/stickers.setStickerSetThumb | 182 - .../method/stickers.suggestShortName | 166 - .../method/updates.getChannelDifference | 247 - .../method/updates.getDifference | 225 - .../core.telegram.org/method/updates.getState | 135 - .../method/upload.getCdnFile | 162 - .../method/upload.getCdnFileHashes | 178 - data/core.telegram.org/method/upload.getFile | 252 - .../method/upload.getFileHashes | 171 - .../method/upload.getWebFile | 176 - .../method/upload.reuploadCdnFile | 173 - .../method/upload.saveBigFilePart | 208 - .../method/upload.saveFilePart | 183 - .../method/users.getFullUser | 177 - data/core.telegram.org/method/users.getUsers | 191 - .../method/users.setSecureValueErrors | 176 - data/core.telegram.org/methods.html | 2306 ---- data/core.telegram.org/mtproto.html | 260 - .../mtproto/TL-abstract-types.html | 202 - .../mtproto/TL-combinators.html | 251 - .../mtproto/TL-dependent.html | 236 - data/core.telegram.org/mtproto/TL-formal.html | 319 - .../core.telegram.org/mtproto/TL-optargs.html | 151 - .../mtproto/TL-patterns.html | 129 - .../mtproto/TL-polymorph.html | 170 - data/core.telegram.org/mtproto/TL-tl.html | 308 - data/core.telegram.org/mtproto/TL-types.html | 124 - data/core.telegram.org/mtproto/TL.html | 210 - data/core.telegram.org/mtproto/auth_key.html | 262 - .../mtproto/description.html | 238 - .../mtproto/description_v1.html | 205 - .../mtproto/mtproto-transports.html | 280 - .../mtproto/samples-auth_key.html | 748 -- .../mtproto/security_guidelines.html | 177 - .../mtproto/security_guidelines_v1.html | 175 - data/core.telegram.org/mtproto/serialize.html | 240 - .../mtproto/service_messages.html | 195 - .../service_messages_about_messages.html | 185 - data/core.telegram.org/mtproto_v1.html | 229 - data/core.telegram.org/passport.html | 690 -- .../passport/encryption.html | 606 -- data/core.telegram.org/passport/example.html | 585 - .../passport/sdk-android.html | 180 - .../passport/sdk-ios-mac.html | 246 - .../passport/sdk-javascript.html | 258 - .../reproducible-builds.html | 488 - data/core.telegram.org/schema.html | 1800 ---- .../schema/end-to-end-json.html | 1 - data/core.telegram.org/schema/end-to-end.html | 225 - data/core.telegram.org/schema/json.html | 1 - .../schema/mtproto-json.html | 1 - data/core.telegram.org/schema/mtproto.html | 204 - data/core.telegram.org/stickers.html | 249 - .../stickers/webm-vp9-encoding.html | 159 - data/core.telegram.org/tdlib.html | 147 - .../tdlib/getting-started.html | 198 - .../tdlib/notification-api.html | 210 - data/core.telegram.org/tdlib/options.html | 501 - data/core.telegram.org/themes.html | 143 - .../type/AccountDaysTTL.html | 162 - data/core.telegram.org/type/Audio.html | 128 - .../core.telegram.org/type/Authorization.html | 162 - .../type/AutoDownloadSettings.html | 143 - .../type/BankCardOpenUrl.html | 143 - data/core.telegram.org/type/BaseTheme.html | 163 - data/core.telegram.org/type/Bool.html | 718 -- data/core.telegram.org/type/BotCommand.html | 143 - .../type/BotCommandScope.html | 176 - .../type/BotInlineMessage.html | 168 - .../type/BotInlineResult.html | 148 - data/core.telegram.org/type/CdnConfig.html | 164 - data/core.telegram.org/type/CdnPublicKey.html | 145 - .../type/ChannelAdminLogEvent.html | 143 - .../type/ChannelAdminLogEventAction.html | 298 - .../type/ChannelAdminLogEventsFilter.html | 143 - .../type/ChannelLocation.html | 148 - .../type/ChannelMessagesFilter.html | 148 - .../type/ChannelParticipant.html | 168 - .../type/ChannelParticipantsFilter.html | 178 - data/core.telegram.org/type/Chat.html | 163 - .../type/ChatAdminRights.html | 146 - .../type/ChatAdminWithInvites.html | 143 - .../type/ChatBannedRights.html | 146 - data/core.telegram.org/type/ChatFull.html | 148 - data/core.telegram.org/type/ChatInvite.html | 172 - .../type/ChatInviteImporter.html | 143 - data/core.telegram.org/type/ChatOnlines.html | 162 - .../type/ChatParticipant.html | 153 - .../type/ChatParticipants.html | 148 - data/core.telegram.org/type/ChatPhoto.html | 148 - data/core.telegram.org/type/ChatTheme.html | 143 - data/core.telegram.org/type/CodeSettings.html | 143 - data/core.telegram.org/type/Config.html | 162 - data/core.telegram.org/type/Contact.html | 143 - .../core.telegram.org/type/ContactStatus.html | 143 - data/core.telegram.org/type/DataJSON.html | 168 - data/core.telegram.org/type/DcOption.html | 143 - .../type/DecryptedDataBlock.html | 128 - .../type/DecryptedMessage.html | 140 - .../type/DecryptedMessageAction.html | 145 - .../type/DecryptedMessageLayer.html | 129 - .../type/DecryptedMessageMedia.html | 149 - data/core.telegram.org/type/Dialog.html | 148 - data/core.telegram.org/type/DialogFilter.html | 143 - .../type/DialogFilterSuggested.html | 143 - data/core.telegram.org/type/DialogPeer.html | 148 - .../type/DisabledFeature.html | 128 - data/core.telegram.org/type/Document.html | 173 - .../type/DocumentAttribute.html | 173 - data/core.telegram.org/type/EmojiKeyword.html | 148 - .../core.telegram.org/type/EmojiLanguage.html | 143 - data/core.telegram.org/type/EmojiURL.html | 162 - .../core.telegram.org/type/EncryptedChat.html | 187 - .../core.telegram.org/type/EncryptedFile.html | 167 - .../type/EncryptedMessage.html | 148 - data/core.telegram.org/type/Error.html | 143 - .../type/ExportedChatInvite.html | 162 - .../type/ExportedMessageLink.html | 162 - data/core.telegram.org/type/FileHash.html | 143 - data/core.telegram.org/type/FileLocation.html | 128 - data/core.telegram.org/type/Folder.html | 143 - data/core.telegram.org/type/FolderPeer.html | 143 - data/core.telegram.org/type/Game.html | 143 - data/core.telegram.org/type/GeoPoint.html | 148 - .../type/GlobalPrivacySettings.html | 167 - data/core.telegram.org/type/GroupCall.html | 148 - .../type/GroupCallParticipant.html | 143 - .../type/GroupCallParticipantVideo.html | 143 - .../GroupCallParticipantVideoSourceGroup.html | 143 - data/core.telegram.org/type/HighScore.html | 143 - .../type/InlineBotSwitchPM.html | 143 - .../type/InlineQueryPeerType.html | 163 - .../core.telegram.org/type/InputAppEvent.html | 143 - .../type/InputBotInlineMessage.html | 173 - .../type/InputBotInlineMessageID.html | 148 - .../type/InputBotInlineResult.html | 158 - data/core.telegram.org/type/InputChannel.html | 153 - .../type/InputChatPhoto.html | 153 - .../type/InputCheckPasswordSRP.html | 151 - data/core.telegram.org/type/InputContact.html | 143 - .../type/InputDialogPeer.html | 148 - .../core.telegram.org/type/InputDocument.html | 148 - .../type/InputEncryptedChat.html | 143 - .../type/InputEncryptedFile.html | 158 - data/core.telegram.org/type/InputFile.html | 148 - .../type/InputFileLocation.html | 188 - data/core.telegram.org/type/InputGame.html | 148 - .../core.telegram.org/type/InputGeoPoint.html | 148 - .../type/InputGroupCall.html | 143 - data/core.telegram.org/type/InputMedia.html | 213 - data/core.telegram.org/type/InputMessage.html | 158 - .../type/InputNotifyPeer.html | 158 - .../type/InputPaymentCredentials.html | 158 - data/core.telegram.org/type/InputPeer.html | 173 - .../type/InputPeerNotifySettings.html | 143 - .../type/InputPhoneCall.html | 143 - data/core.telegram.org/type/InputPhoto.html | 148 - .../type/InputPrivacyKey.html | 178 - .../type/InputPrivacyRule.html | 178 - .../type/InputSecureFile.html | 151 - .../type/InputSecureValue.html | 145 - .../type/InputStickerSet.html | 168 - .../type/InputStickerSetItem.html | 143 - .../type/InputStickeredMedia.html | 148 - data/core.telegram.org/type/InputTheme.html | 148 - .../type/InputThemeSettings.html | 143 - data/core.telegram.org/type/InputUser.html | 158 - .../type/InputWallPaper.html | 153 - .../type/InputWebFileLocation.html | 148 - data/core.telegram.org/type/Invoice.html | 143 - .../type/JSONObjectValue.html | 143 - data/core.telegram.org/type/JSONValue.html | 187 - .../type/KeyboardButton.html | 193 - .../type/KeyboardButtonRow.html | 143 - data/core.telegram.org/type/LabeledPrice.html | 143 - .../type/LangPackDifference.html | 167 - .../type/LangPackLanguage.html | 162 - .../type/LangPackString.html | 153 - data/core.telegram.org/type/MaskCoords.html | 143 - data/core.telegram.org/type/Message.html | 153 - .../core.telegram.org/type/MessageAction.html | 283 - .../core.telegram.org/type/MessageEntity.html | 233 - .../type/MessageFwdHeader.html | 143 - .../type/MessageInteractionCounters.html | 143 - data/core.telegram.org/type/MessageMedia.html | 232 - data/core.telegram.org/type/MessageRange.html | 143 - .../type/MessageReactionsList.html | 128 - .../type/MessageReplies.html | 146 - .../type/MessageReplyHeader.html | 143 - .../type/MessageUserVote.html | 153 - data/core.telegram.org/type/MessageViews.html | 143 - .../type/MessagesFilter.html | 223 - data/core.telegram.org/type/NotifyPeer.html | 158 - data/core.telegram.org/type/Null.html | 143 - data/core.telegram.org/type/Page.html | 143 - data/core.telegram.org/type/PageBlock.html | 283 - data/core.telegram.org/type/PageCaption.html | 143 - data/core.telegram.org/type/PageListItem.html | 148 - .../type/PageListOrderedItem.html | 148 - .../type/PageRelatedArticle.html | 143 - .../core.telegram.org/type/PageTableCell.html | 143 - data/core.telegram.org/type/PageTableRow.html | 143 - .../type/PasswordKdfAlgo.html | 151 - .../core.telegram.org/type/PaymentCharge.html | 143 - .../type/PaymentRequestedInfo.html | 143 - .../type/PaymentSavedCredentials.html | 143 - data/core.telegram.org/type/Peer.html | 153 - data/core.telegram.org/type/PeerBlocked.html | 143 - data/core.telegram.org/type/PeerLocated.html | 148 - .../type/PeerNotifySettings.html | 162 - data/core.telegram.org/type/PeerSettings.html | 162 - data/core.telegram.org/type/PhoneCall.html | 168 - .../type/PhoneCallDiscardReason.html | 158 - .../type/PhoneCallProtocol.html | 143 - data/core.telegram.org/type/Photo.html | 148 - data/core.telegram.org/type/PhotoSize.html | 168 - data/core.telegram.org/type/Poll.html | 143 - data/core.telegram.org/type/PollAnswer.html | 146 - .../type/PollAnswerVoters.html | 143 - data/core.telegram.org/type/PollResults.html | 143 - .../type/PopularContact.html | 143 - data/core.telegram.org/type/PostAddress.html | 143 - data/core.telegram.org/type/PrivacyKey.html | 178 - data/core.telegram.org/type/PrivacyRule.html | 178 - .../type/ReceivedNotifyMessage.html | 143 - data/core.telegram.org/type/ReplyMarkup.html | 158 - data/core.telegram.org/type/ReportReason.html | 178 - .../type/RestrictionReason.html | 143 - data/core.telegram.org/type/RichText.html | 218 - data/core.telegram.org/type/SavedContact.html | 143 - .../type/SecureCredentialsEncrypted.html | 143 - data/core.telegram.org/type/SecureData.html | 146 - data/core.telegram.org/type/SecureFile.html | 151 - .../type/SecurePasswordKdfAlgo.html | 155 - .../type/SecurePlainData.html | 150 - .../type/SecureRequiredType.html | 148 - .../type/SecureSecretSettings.html | 145 - data/core.telegram.org/type/SecureValue.html | 162 - .../type/SecureValueError.html | 183 - .../type/SecureValueHash.html | 143 - .../type/SecureValueType.html | 203 - .../type/SendMessageAction.html | 228 - .../type/ShippingOption.html | 143 - .../type/SponsoredMessage.html | 143 - .../type/StatsAbsValueAndPrev.html | 143 - data/core.telegram.org/type/StatsGraph.html | 172 - .../type/StatsGroupTopAdmin.html | 146 - .../type/StatsGroupTopInviter.html | 146 - .../type/StatsGroupTopPoster.html | 146 - .../type/StatsPercentValue.html | 143 - data/core.telegram.org/type/StatsURL.html | 143 - data/core.telegram.org/type/StickerPack.html | 143 - data/core.telegram.org/type/StickerSet.html | 143 - .../type/StickerSetCovered.html | 148 - data/core.telegram.org/type/Theme.html | 172 - .../core.telegram.org/type/ThemeSettings.html | 143 - data/core.telegram.org/type/TopPeer.html | 143 - .../type/TopPeerCategory.html | 178 - .../type/TopPeerCategoryPeers.html | 143 - data/core.telegram.org/type/True.html | 145 - data/core.telegram.org/type/Update.html | 603 -- data/core.telegram.org/type/Updates.html | 508 - .../core.telegram.org/type/UrlAuthResult.html | 177 - data/core.telegram.org/type/User.html | 177 - data/core.telegram.org/type/UserFull.html | 162 - .../type/UserProfilePhoto.html | 148 - data/core.telegram.org/type/UserStatus.html | 168 - data/core.telegram.org/type/Vector t.html | 143 - data/core.telegram.org/type/Video.html | 128 - data/core.telegram.org/type/VideoSize.html | 143 - data/core.telegram.org/type/WallPaper.html | 172 - .../type/WallPaperSettings.html | 143 - .../type/WebAuthorization.html | 143 - data/core.telegram.org/type/WebDocument.html | 148 - data/core.telegram.org/type/WebPage.html | 177 - .../type/WebPageAttribute.html | 143 - .../type/account.AuthorizationForm | 162 - .../type/account.Authorizations | 162 - .../type/account.AutoDownloadSettings | 162 - .../core.telegram.org/type/account.ChatThemes | 167 - .../type/account.ContentSettings | 162 - data/core.telegram.org/type/account.Password | 162 - .../type/account.PasswordInputSettings | 146 - .../type/account.PasswordSettings | 164 - .../type/account.PrivacyRules | 167 - .../type/account.ResetPasswordResult | 175 - .../type/account.SentChangePhoneCode | 128 - .../type/account.SentEmailCode | 162 - data/core.telegram.org/type/account.Takeout | 162 - data/core.telegram.org/type/account.Themes | 167 - .../type/account.TmpPassword | 162 - .../core.telegram.org/type/account.WallPapers | 167 - .../type/account.WebAuthorizations | 162 - .../core.telegram.org/type/auth.Authorization | 192 - data/core.telegram.org/type/auth.CheckedPhone | 128 - data/core.telegram.org/type/auth.CodeType | 153 - .../type/auth.ExportedAuthorization | 162 - data/core.telegram.org/type/auth.LoginToken | 177 - .../type/auth.PasswordRecovery | 165 - data/core.telegram.org/type/auth.SentCode | 183 - data/core.telegram.org/type/auth.SentCodeType | 158 - data/core.telegram.org/type/bytes.html | 125 - .../type/channels.AdminLogResults | 162 - .../type/channels.ChannelParticipant | 162 - .../type/channels.ChannelParticipants | 167 - data/core.telegram.org/type/contacts.Blocked | 167 - data/core.telegram.org/type/contacts.Contacts | 167 - data/core.telegram.org/type/contacts.Found | 162 - .../type/contacts.ImportedContacts | 162 - data/core.telegram.org/type/contacts.Link | 128 - .../type/contacts.ResolvedPeer | 162 - data/core.telegram.org/type/contacts.TopPeers | 172 - data/core.telegram.org/type/double.html | 118 - data/core.telegram.org/type/help.AppUpdate | 167 - .../core.telegram.org/type/help.CountriesList | 167 - data/core.telegram.org/type/help.CountryCode | 143 - .../type/help.PassportConfig | 169 - data/core.telegram.org/type/help.PromoData | 167 - data/core.telegram.org/type/help.ProxyData | 130 - data/core.telegram.org/type/help.Support | 162 - data/core.telegram.org/type/help.SupportName | 162 - .../type/help.TermsOfService | 143 - .../type/help.TermsOfServiceUpdate | 167 - data/core.telegram.org/type/help.UserInfo | 172 - data/core.telegram.org/type/int.html | 118 - .../type/messages.AffectedFoundMessages | 162 - .../type/messages.AffectedHistory | 178 - .../type/messages.AffectedMessages | 178 - .../type/messages.AllStickers | 172 - .../type/messages.ArchivedStickers | 162 - .../type/messages.BotCallbackAnswer | 162 - .../type/messages.BotResults | 162 - data/core.telegram.org/type/messages.ChatFull | 168 - .../type/messages.ChatInviteImporters | 162 - data/core.telegram.org/type/messages.Chats | 198 - .../type/messages.CheckedHistoryImportPeer | 165 - data/core.telegram.org/type/messages.DhConfig | 167 - data/core.telegram.org/type/messages.Dialogs | 172 - .../type/messages.DiscussionMessage | 162 - .../type/messages.ExportedChatInvite | 172 - .../type/messages.ExportedChatInvites | 162 - .../type/messages.FavedStickers | 167 - .../type/messages.FeaturedStickers | 172 - .../core.telegram.org/type/messages.FoundGifs | 128 - .../type/messages.FoundStickerSets | 167 - .../type/messages.HighScores | 167 - .../type/messages.HistoryImport | 165 - .../type/messages.HistoryImportParsed | 162 - .../type/messages.MessageEditData | 162 - .../type/messages.MessageViews | 162 - .../type/messages.PeerDialogs | 167 - .../type/messages.RecentStickers | 167 - .../core.telegram.org/type/messages.SavedGifs | 167 - .../type/messages.SearchCounter | 143 - .../type/messages.SentEncryptedMessage | 177 - .../type/messages.SentMessage | 128 - .../type/messages.SponsoredMessages | 166 - .../type/messages.StatedMessage | 128 - .../type/messages.StatedMessages | 128 - .../type/messages.StickerSet | 188 - .../type/messages.StickerSetInstallResult | 167 - data/core.telegram.org/type/messages.Stickers | 167 - .../core.telegram.org/type/messages.VotesList | 162 - .../type/payments.BankCardData | 162 - .../type/payments.PaymentForm | 162 - .../type/payments.PaymentReceipt | 162 - .../type/payments.PaymentResult | 167 - .../core.telegram.org/type/payments.SavedInfo | 162 - .../type/payments.ValidatedRequestedInfo | 162 - .../type/phone.ExportedGroupCallInvite | 162 - data/core.telegram.org/type/phone.GroupCall | 162 - .../type/phone.GroupParticipants | 162 - data/core.telegram.org/type/phone.JoinAsPeers | 162 - data/core.telegram.org/type/photos.Photo | 167 - data/core.telegram.org/type/photos.Photos | 167 - .../type/stats.BroadcastStats | 162 - .../type/stats.MegagroupStats | 162 - .../core.telegram.org/type/stats.MessageStats | 162 - .../type/stickers.SuggestedShortName | 162 - data/core.telegram.org/type/storage.FileType | 188 - data/core.telegram.org/type/string.html | 126 - .../type/updates.ChannelDifference | 172 - .../core.telegram.org/type/updates.Difference | 177 - data/core.telegram.org/type/updates.State | 162 - data/core.telegram.org/type/upload.CdnFile | 167 - data/core.telegram.org/type/upload.File | 167 - data/core.telegram.org/type/upload.WebFile | 162 - data/core.telegram.org/video_stickers.html | 115 - data/core.telegram.org/widgets.html | 141 - .../core.telegram.org/widgets/discussion.html | 226 - data/core.telegram.org/widgets/login.html | 404 - data/core.telegram.org/widgets/post.html | 240 - data/core.telegram.org/widgets/share.html | 250 - data/corefork.telegram.org/api.html | 253 - .../api/account-deletion.html | 129 - .../api/animated-emojis.html | 187 - data/corefork.telegram.org/api/auth.html | 202 - data/corefork.telegram.org/api/bots.html | 142 - .../api/bots/buttons.html | 242 - .../api/bots/commands.html | 140 - .../corefork.telegram.org/api/bots/games.html | 171 - .../api/bots/inline.html | 215 - data/corefork.telegram.org/api/channel.html | 154 - data/corefork.telegram.org/api/config.html | 422 - .../corefork.telegram.org/api/datacenter.html | 148 - data/corefork.telegram.org/api/dice.html | 149 - .../corefork.telegram.org/api/discussion.html | 151 - data/corefork.telegram.org/api/drafts.html | 131 - .../corefork.telegram.org/api/end-to-end.html | 244 - .../api/end-to-end/pfs.html | 176 - .../api/end-to-end/seq_no.html | 173 - .../api/end-to-end/video-calls.html | 215 - .../api/end-to-end/voice-calls.html | 178 - .../api/end-to-end_v1.html | 225 - data/corefork.telegram.org/api/errors.html | 189 - data/corefork.telegram.org/api/files.html | 568 - data/corefork.telegram.org/api/folders.html | 179 - data/corefork.telegram.org/api/geochats.html | 115 - data/corefork.telegram.org/api/import.html | 173 - data/corefork.telegram.org/api/invoking.html | 154 - .../api/live-location.html | 178 - data/corefork.telegram.org/api/mentions.html | 152 - data/corefork.telegram.org/api/min.html | 142 - .../api/obtaining_api_id.html | 140 - data/corefork.telegram.org/api/offsets.html | 170 - .../api/optimisation.html | 150 - data/corefork.telegram.org/api/passport.html | 674 -- data/corefork.telegram.org/api/pattern.html | 122 - data/corefork.telegram.org/api/payments.html | 366 - data/corefork.telegram.org/api/pfs.html | 138 - data/corefork.telegram.org/api/pin.html | 149 - data/corefork.telegram.org/api/poll.html | 199 - .../api/push-updates.html | 1009 -- data/corefork.telegram.org/api/qr-login.html | 154 - .../api/recent-actions.html | 154 - data/corefork.telegram.org/api/rights.html | 133 - .../api/scheduled-messages.html | 156 - data/corefork.telegram.org/api/search.html | 179 - .../api/sponsored-messages.html | 146 - data/corefork.telegram.org/api/srp.html | 307 - data/corefork.telegram.org/api/stats.html | 297 - data/corefork.telegram.org/api/terms.html | 133 - .../corefork.telegram.org/api/top-rating.html | 145 - data/corefork.telegram.org/api/updates.html | 226 - .../api/url-authorization.html | 160 - .../corefork.telegram.org/api/web-events.html | 175 - ...hemes-interactive-emoji-read-receipts.html | 115 - data/corefork.telegram.org/bots.html | 420 - .../corefork.telegram.org/bots/2-0-intro.html | 230 - .../bots/api-changelog.html | 670 -- data/corefork.telegram.org/bots/api.html | 9288 ---------------- data/corefork.telegram.org/bots/faq.html | 243 - data/corefork.telegram.org/bots/inline.html | 181 - data/corefork.telegram.org/bots/samples.html | 249 - .../bots/samples/hellobot.html | 287 - .../bots/self-signed.html | 161 - data/corefork.telegram.org/bots/webhooks.html | 827 -- data/corefork.telegram.org/cdn.html | 210 - .../constructor/account.authorizationForm | 174 - .../constructor/account.authorizations | 147 - .../constructor/account.autoDownloadSettings | 157 - .../constructor/account.chatThemes | 155 - .../constructor/account.chatThemesNotModified | 132 - .../constructor/account.contentSettings | 157 - .../constructor/account.password | 213 - .../constructor/account.passwordInputSettings | 176 - .../constructor/account.passwordSettings | 161 - .../constructor/account.privacyRules | 157 - .../account.resetPasswordRequestedWait | 147 - .../constructor/account.sentChangePhoneCode | 161 - .../constructor/account.sentEmailCode | 155 - .../constructor/account.takeout | 147 - .../constructor/account.themes | 155 - .../constructor/account.themesNotModified | 132 - .../constructor/account.tmpPassword | 152 - .../constructor/account.wallPapers | 155 - .../constructor/account.wallPapersNotModified | 132 - .../constructor/account.webAuthorizations | 152 - .../constructor/auth.authorization | 159 - .../auth.authorizationSignUpRequired | 155 - .../constructor/auth.codeTypeCall | 132 - .../constructor/auth.codeTypeFlashCall | 132 - .../constructor/auth.codeTypeSms | 132 - .../constructor/auth.exportedAuthorization | 152 - .../constructor/auth.loginToken | 155 - .../constructor/auth.loginTokenMigrateTo | 152 - .../constructor/auth.loginTokenSuccess | 147 - .../constructor/auth.passwordRecovery | 152 - .../constructor/auth.sentCode | 172 - .../constructor/auth.sentCodeTypeApp | 147 - .../constructor/auth.sentCodeTypeCall | 147 - .../constructor/auth.sentCodeTypeFlashCall | 150 - .../constructor/auth.sentCodeTypeSms | 147 - .../constructor/authorization.html | 225 - .../constructor/bankCardOpenUrl.html | 152 - .../constructor/baseThemeArctic.html | 132 - .../constructor/baseThemeClassic.html | 132 - .../constructor/baseThemeDay.html | 132 - .../constructor/baseThemeNight.html | 132 - .../constructor/baseThemeTinted.html | 132 - .../constructor/boolFalse.html | 132 - .../constructor/boolTrue.html | 132 - .../constructor/botCommand.html | 152 - .../constructor/botCommandScopeChats.html | 135 - .../constructor/botCommandScopeDefault.html | 132 - .../constructor/botCommandScopePeer.html | 147 - .../botCommandScopePeerAdmins.html | 150 - .../constructor/botCommandScopePeerUser.html | 155 - .../constructor/botCommandScopeUsers.html | 132 - .../constructor/botInfo.html | 157 - .../constructor/botInlineMediaResult.html | 186 - .../botInlineMessageMediaAuto.html | 167 - .../botInlineMessageMediaContact.html | 172 - .../botInlineMessageMediaInvoice.html | 189 - .../botInlineMessageMediaVenue.html | 182 - .../constructor/botInlineMessageText.html | 170 - .../constructor/botInlineResult.html | 189 - .../constructor/cdnConfig.html | 149 - .../constructor/cdnPublicKey.html | 154 - .../constructor/channel.html | 289 - .../constructor/channelAdminLogEvent.html | 162 - ...channelAdminLogEventActionChangeAbout.html | 152 - ...elAdminLogEventActionChangeHistoryTTL.html | 152 - ...elAdminLogEventActionChangeLinkedChat.html | 152 - ...nnelAdminLogEventActionChangeLocation.html | 152 - ...channelAdminLogEventActionChangePhoto.html | 152 - ...elAdminLogEventActionChangeStickerSet.html | 152 - ...channelAdminLogEventActionChangeTitle.html | 152 - ...nnelAdminLogEventActionChangeUsername.html | 152 - ...dminLogEventActionDefaultBannedRights.html | 155 - ...annelAdminLogEventActionDeleteMessage.html | 147 - ...elAdminLogEventActionDiscardGroupCall.html | 147 - ...channelAdminLogEventActionEditMessage.html | 152 - ...minLogEventActionExportedInviteDelete.html | 147 - ...AdminLogEventActionExportedInviteEdit.html | 152 - ...minLogEventActionExportedInviteRevoke.html | 147 - ...lAdminLogEventActionParticipantInvite.html | 147 - ...nelAdminLogEventActionParticipantJoin.html | 132 - ...LogEventActionParticipantJoinByInvite.html | 150 - ...elAdminLogEventActionParticipantLeave.html | 132 - ...nelAdminLogEventActionParticipantMute.html | 147 - ...nLogEventActionParticipantToggleAdmin.html | 155 - ...minLogEventActionParticipantToggleBan.html | 155 - ...lAdminLogEventActionParticipantUnmute.html | 147 - ...lAdminLogEventActionParticipantVolume.html | 147 - ...nnelAdminLogEventActionStartGroupCall.html | 147 - .../channelAdminLogEventActionStopPoll.html | 147 - ...nLogEventActionToggleGroupCallSetting.html | 147 - ...annelAdminLogEventActionToggleInvites.html | 147 - ...nLogEventActionTogglePreHistoryHidden.html | 150 - ...elAdminLogEventActionToggleSignatures.html | 147 - ...nnelAdminLogEventActionToggleSlowMode.html | 155 - ...hannelAdminLogEventActionUpdatePinned.html | 147 - .../channelAdminLogEventsFilter.html | 266 - .../constructor/channelForbidden.html | 177 - .../constructor/channelFull.html | 363 - .../constructor/channelLocation.html | 152 - .../constructor/channelLocationEmpty.html | 132 - .../constructor/channelMessagesFilter.html | 157 - .../channelMessagesFilterEmpty.html | 132 - .../constructor/channelParticipant.html | 152 - .../constructor/channelParticipantAdmin.html | 190 - .../constructor/channelParticipantBanned.html | 175 - .../channelParticipantCreator.html | 162 - .../constructor/channelParticipantLeft.html | 147 - .../constructor/channelParticipantSelf.html | 157 - .../channelParticipantsAdmins.html | 132 - .../channelParticipantsBanned.html | 147 - .../constructor/channelParticipantsBots.html | 132 - .../channelParticipantsContacts.html | 147 - .../channelParticipantsKicked.html | 147 - .../channelParticipantsMentions.html | 161 - .../channelParticipantsRecent.html | 132 - .../channelParticipantsSearch.html | 147 - .../constructor/channels.adminLogResults | 157 - .../constructor/channels.channelParticipants | 162 - .../channels.channelParticipantsNotModified | 132 - .../constructor/chat.html | 227 - .../constructor/chatAdminRights.html | 205 - .../constructor/chatAdminWithInvites.html | 157 - .../constructor/chatBannedRights.html | 216 - .../constructor/chatEmpty.html | 147 - .../constructor/chatForbidden.html | 152 - .../constructor/chatFull.html | 231 - .../constructor/chatInvite.html | 190 - .../constructor/chatInviteAlready.html | 147 - .../constructor/chatInviteExported.html | 192 - .../constructor/chatInvitePeek.html | 152 - .../constructor/chatOnlines.html | 147 - .../constructor/chatParticipant.html | 157 - .../constructor/chatParticipantAdmin.html | 157 - .../constructor/chatParticipantCreator.html | 147 - .../constructor/chatParticipants.html | 157 - .../chatParticipantsForbidden.html | 157 - .../constructor/chatPhoto.html | 170 - .../constructor/chatPhotoEmpty.html | 132 - .../constructor/chatTheme.html | 157 - .../constructor/codeSettings.html | 166 - .../constructor/config.html | 420 - .../constructor/contact.html | 152 - .../constructor/contactStatus.html | 152 - .../constructor/contacts.blocked | 157 - .../constructor/contacts.blockedSlice | 162 - .../constructor/contacts.contacts | 157 - .../constructor/contacts.contactsNotModified | 132 - .../constructor/contacts.found | 162 - .../constructor/contacts.importedContacts | 165 - .../constructor/contacts.resolvedPeer | 157 - .../constructor/contacts.topPeers | 157 - .../constructor/contacts.topPeersDisabled | 132 - .../constructor/contacts.topPeersNotModified | 132 - .../constructor/dataJSON.html | 147 - .../constructor/dcOption.html | 197 - .../constructor/decryptedMessage.html | 217 - .../decryptedMessageActionCommitKey.html | 155 - .../decryptedMessageActionDeleteMessages.html | 148 - .../decryptedMessageActionFlushHistory.html | 133 - .../decryptedMessageActionNotifyLayer.html | 151 - .../decryptedMessageActionReadMessages.html | 148 - .../decryptedMessageActionRequestKey.html | 155 - .../decryptedMessageActionResend.html | 155 - ...ryptedMessageActionScreenshotMessages.html | 148 - .../decryptedMessageActionSetMessageTTL.html | 149 - .../decryptedMessageActionTyping.html | 148 - .../constructor/decryptedMessageLayer.html | 173 - .../decryptedMessageMediaAudio.html | 174 - .../decryptedMessageMediaContact.html | 163 - .../decryptedMessageMediaDocument.html | 191 - .../decryptedMessageMediaEmpty.html | 133 - ...decryptedMessageMediaExternalDocument.html | 183 - .../decryptedMessageMediaGeoPoint.html | 153 - .../decryptedMessageMediaPhoto.html | 191 - .../decryptedMessageMediaVenue.html | 173 - .../decryptedMessageMediaVideo.html | 207 - .../decryptedMessageMediaWebPage.html | 148 - .../constructor/decryptedMessageService.html | 156 - .../constructor/dialogFilter.html | 220 - .../constructor/dialogFilterSuggested.html | 155 - .../constructor/dialogFolder.html | 187 - .../constructor/dialogPeer.html | 147 - .../constructor/dialogPeerFolder.html | 150 - .../constructor/document.html | 200 - .../documentAttributeAnimated.html | 132 - .../constructor/documentAttributeAudio.html | 172 - .../documentAttributeFilename.html | 147 - .../documentAttributeHasStickers.html | 132 - .../documentAttributeImageSize.html | 152 - .../constructor/documentAttributeSticker.html | 167 - .../constructor/documentAttributeVideo.html | 172 - .../constructor/documentEmpty.html | 147 - .../constructor/draftMessage.html | 177 - .../constructor/draftMessageEmpty.html | 152 - .../constructor/emojiKeyword.html | 152 - .../constructor/emojiKeywordDeleted.html | 152 - .../constructor/emojiKeywordsDifference.html | 162 - .../constructor/emojiLanguage.html | 147 - .../constructor/emojiURL.html | 147 - .../constructor/encryptedChat.html | 177 - .../constructor/encryptedChatDiscarded.html | 157 - .../constructor/encryptedChatEmpty.html | 147 - .../constructor/encryptedChatRequested.html | 185 - .../constructor/encryptedChatWaiting.html | 167 - .../constructor/encryptedFile.html | 167 - .../constructor/encryptedFileEmpty.html | 132 - .../constructor/encryptedMessage.html | 170 - .../constructor/encryptedMessageService.html | 165 - .../constructor/error.html | 152 - .../constructor/exportedMessageLink.html | 152 - .../constructor/fileHash.html | 171 - .../constructor/fileLocationUnavailable.html | 179 - .../constructor/folder.html | 177 - .../constructor/folderPeer.html | 155 - .../constructor/game.html | 182 - .../constructor/geoPoint.html | 167 - .../constructor/geoPointEmpty.html | 132 - .../constructor/globalPrivacySettings.html | 152 - .../constructor/groupCall.html | 230 - .../constructor/groupCallDiscarded.html | 157 - .../constructor/groupCallParticipant.html | 247 - .../groupCallParticipantVideo.html | 167 - .../groupCallParticipantVideoSourceGroup.html | 152 - .../constructor/help.appUpdate | 190 - .../constructor/help.countriesList | 155 - .../constructor/help.countriesListNotModified | 132 - .../constructor/help.country | 172 - .../constructor/help.countryCode | 162 - .../constructor/help.deepLinkInfo | 165 - .../constructor/help.deepLinkInfoEmpty | 132 - .../constructor/help.inviteText | 147 - .../constructor/help.noAppUpdate | 132 - .../constructor/help.passportConfig | 156 - .../help.passportConfigNotModified | 132 - .../constructor/help.promoData | 182 - .../constructor/help.promoDataEmpty | 147 - .../constructor/help.recentMeUrls | 157 - .../constructor/help.support | 152 - .../constructor/help.supportName | 147 - .../constructor/help.termsOfService | 175 - .../constructor/help.termsOfServiceUpdate | 157 - .../help.termsOfServiceUpdateEmpty | 150 - .../constructor/help.userInfo | 165 - .../constructor/help.userInfoEmpty | 132 - .../constructor/highScore.html | 157 - .../constructor/importedContact.html | 155 - .../constructor/inlineBotSwitchPM.html | 152 - .../inlineQueryPeerTypeBroadcast.html | 135 - .../inlineQueryPeerTypeMegagroup.html | 135 - .../constructor/inlineQueryPeerTypePM.html | 132 - .../inlineQueryPeerTypeSameBotPM.html | 132 - .../constructor/inputAppEvent.html | 162 - .../inputBotInlineMessageGame.html | 152 - .../constructor/inputBotInlineMessageID.html | 157 - .../inputBotInlineMessageID64.html | 162 - .../inputBotInlineMessageMediaAuto.html | 165 - .../inputBotInlineMessageMediaContact.html | 172 - .../inputBotInlineMessageMediaGeo.html | 175 - .../inputBotInlineMessageMediaInvoice.html | 187 - .../inputBotInlineMessageMediaVenue.html | 182 - .../inputBotInlineMessageText.html | 170 - .../constructor/inputBotInlineResult.html | 189 - .../inputBotInlineResultDocument.html | 179 - .../constructor/inputBotInlineResultGame.html | 157 - .../inputBotInlineResultPhoto.html | 164 - .../constructor/inputChannel.html | 155 - .../constructor/inputChannelEmpty.html | 132 - .../constructor/inputChannelFromMessage.html | 160 - .../constructor/inputChatPhotoEmpty.html | 132 - .../constructor/inputChatUploadedPhoto.html | 165 - .../constructor/inputCheckPasswordEmpty.html | 132 - .../constructor/inputCheckPasswordSRP.html | 160 - .../constructor/inputClientProxy.html | 154 - .../constructor/inputDialogPeer.html | 147 - .../constructor/inputDialogPeerFolder.html | 150 - .../constructor/inputDocument.html | 162 - .../constructor/inputDocumentEmpty.html | 132 - .../inputDocumentFileLocation.html | 167 - .../constructor/inputEncryptedChat.html | 159 - .../inputEncryptedFileBigUploaded.html | 160 - .../constructor/inputEncryptedFileEmpty.html | 132 - .../inputEncryptedFileLocation.html | 155 - .../inputEncryptedFileUploaded.html | 162 - .../constructor/inputFileBig.html | 160 - .../constructor/inputFileLocation.html | 165 - .../constructor/inputFolderPeer.html | 155 - .../constructor/inputGameID.html | 155 - .../constructor/inputGameShortName.html | 152 - .../constructor/inputGeoPointEmpty.html | 132 - .../constructor/inputGroupCallStream.html | 172 - .../inputKeyboardButtonUrlAuth.html | 176 - .../constructor/inputMediaContact.html | 162 - .../constructor/inputMediaDice.html | 150 - .../constructor/inputMediaDocument.html | 162 - .../inputMediaDocumentExternal.html | 157 - .../constructor/inputMediaEmpty.html | 132 - .../constructor/inputMediaGame.html | 147 - .../constructor/inputMediaGeoLive.html | 175 - .../constructor/inputMediaGeoPoint.html | 147 - .../constructor/inputMediaInvoice.html | 189 - .../constructor/inputMediaPhoto.html | 157 - .../constructor/inputMediaPhotoExternal.html | 157 - .../constructor/inputMediaPoll.html | 170 - .../constructor/inputMediaUploadedPhoto.html | 165 - .../constructor/inputMediaVenue.html | 172 - .../inputMessageCallbackQuery.html | 152 - .../inputMessageEntityMentionName.html | 162 - .../constructor/inputMessageID.html | 147 - .../constructor/inputMessagePinned.html | 132 - .../constructor/inputMessageReplyTo.html | 147 - .../inputMessagesFilterChatPhotos.html | 132 - .../inputMessagesFilterContacts.html | 132 - .../inputMessagesFilterDocument.html | 132 - .../constructor/inputMessagesFilterEmpty.html | 132 - .../constructor/inputMessagesFilterGeo.html | 132 - .../constructor/inputMessagesFilterGif.html | 132 - .../constructor/inputMessagesFilterMusic.html | 132 - .../inputMessagesFilterPhoneCalls.html | 152 - .../inputMessagesFilterPhotoVideo.html | 132 - .../inputMessagesFilterPhotos.html | 132 - .../inputMessagesFilterPinned.html | 132 - .../inputMessagesFilterRoundVideo.html | 132 - .../inputMessagesFilterRoundVoice.html | 132 - .../constructor/inputMessagesFilterUrl.html | 132 - .../constructor/inputMessagesFilterVideo.html | 132 - .../constructor/inputMessagesFilterVoice.html | 132 - .../constructor/inputNotifyBroadcasts.html | 135 - .../constructor/inputNotifyChats.html | 132 - .../constructor/inputNotifyPeer.html | 147 - .../constructor/inputNotifyUsers.html | 132 - .../constructor/inputPaymentCredentials.html | 157 - .../inputPaymentCredentialsApplePay.html | 147 - .../inputPaymentCredentialsGooglePay.html | 147 - .../inputPaymentCredentialsSaved.html | 152 - .../constructor/inputPeerChannel.html | 155 - .../inputPeerChannelFromMessage.html | 160 - .../constructor/inputPeerChat.html | 147 - .../constructor/inputPeerNotifySettings.html | 167 - .../inputPeerPhotoFileLocation.html | 162 - .../constructor/inputPeerSelf.html | 132 - .../constructor/inputPeerUser.html | 155 - .../constructor/inputPeerUserFromMessage.html | 160 - .../constructor/inputPhoneCall.html | 152 - .../constructor/inputPhoneContact.html | 166 - .../constructor/inputPhoto.html | 162 - .../constructor/inputPhotoEmpty.html | 132 - .../constructor/inputPhotoFileLocation.html | 171 - .../inputPrivacyKeyAddedByPhone.html | 132 - .../inputPrivacyKeyChatInvite.html | 132 - .../constructor/inputPrivacyKeyForwards.html | 132 - .../constructor/inputPrivacyKeyPhoneCall.html | 132 - .../inputPrivacyKeyPhoneNumber.html | 132 - .../constructor/inputPrivacyKeyPhoneP2P.html | 132 - .../inputPrivacyKeyProfilePhoto.html | 132 - ...nputPrivacyValueAllowChatParticipants.html | 147 - .../inputPrivacyValueAllowContacts.html | 132 - .../inputPrivacyValueAllowUsers.html | 147 - .../inputPrivacyValueDisallowAll.html | 132 - ...tPrivacyValueDisallowChatParticipants.html | 147 - .../inputPrivacyValueDisallowUsers.html | 147 - .../inputReportReasonChildAbuse.html | 132 - .../inputReportReasonCopyright.html | 132 - .../constructor/inputReportReasonFake.html | 132 - .../inputReportReasonGeoIrrelevant.html | 132 - .../constructor/inputReportReasonOther.html | 132 - .../inputReportReasonPornography.html | 132 - .../constructor/inputReportReasonSpam.html | 132 - .../inputReportReasonViolence.html | 132 - .../constructor/inputSecureFile.html | 155 - .../constructor/inputSecureFileLocation.html | 156 - .../constructor/inputSecureFileUploaded.html | 169 - .../constructor/inputSecureValue.html | 190 - .../constructor/inputSingleMedia.html | 174 - .../inputStickerSetAnimatedEmoji.html | 132 - ...nputStickerSetAnimatedEmojiAnimations.html | 132 - .../constructor/inputStickerSetDice.html | 150 - .../constructor/inputStickerSetEmpty.html | 132 - .../constructor/inputStickerSetID.html | 152 - .../constructor/inputStickerSetItem.html | 162 - .../constructor/inputStickerSetShortName.html | 147 - .../inputStickeredMediaDocument.html | 147 - .../constructor/inputStickeredMediaPhoto.html | 147 - .../constructor/inputTakeoutFileLocation.html | 132 - .../constructor/inputTheme.html | 152 - .../constructor/inputThemeSettings.html | 182 - .../constructor/inputThemeSlug.html | 147 - .../constructor/inputUser.html | 155 - .../constructor/inputUserEmpty.html | 132 - .../constructor/inputUserFromMessage.html | 160 - .../constructor/inputUserSelf.html | 132 - .../constructor/inputWallPaper.html | 152 - .../constructor/inputWallPaperNoFile.html | 150 - .../constructor/inputWallPaperSlug.html | 147 - .../constructor/inputWebDocument.html | 165 - .../inputWebFileGeoPointLocation.html | 172 - .../constructor/inputWebFileLocation.html | 152 - .../constructor/invoice.html | 209 - .../constructor/jsonArray.html | 147 - .../constructor/jsonBool.html | 147 - .../constructor/jsonNull.html | 132 - .../constructor/jsonNumber.html | 147 - .../constructor/jsonObject.html | 147 - .../constructor/jsonObjectValue.html | 152 - .../constructor/jsonString.html | 147 - .../constructor/keyboardButton.html | 147 - .../constructor/keyboardButtonBuy.html | 147 - .../constructor/keyboardButtonCallback.html | 167 - .../constructor/keyboardButtonGame.html | 147 - .../keyboardButtonRequestGeoLocation.html | 147 - .../keyboardButtonRequestPhone.html | 147 - .../keyboardButtonRequestPoll.html | 157 - .../constructor/keyboardButtonRow.html | 147 - .../keyboardButtonSwitchInline.html | 162 - .../constructor/keyboardButtonUrl.html | 152 - .../constructor/keyboardButtonUrlAuth.html | 179 - .../constructor/labeledPrice.html | 154 - .../constructor/langPackDifference.html | 162 - .../constructor/langPackLanguage.html | 202 - .../constructor/langPackString.html | 152 - .../constructor/langPackStringDeleted.html | 147 - .../constructor/langPackStringPluralized.html | 182 - .../constructor/maskCoords.html | 169 - .../constructor/message.html | 302 - .../constructor/messageActionBotAllowed.html | 149 - .../messageActionChannelCreate.html | 147 - .../messageActionChannelMigrateFrom.html | 155 - .../constructor/messageActionChatAddUser.html | 147 - .../constructor/messageActionChatCreate.html | 152 - .../messageActionChatDeletePhoto.html | 132 - .../messageActionChatDeleteUser.html | 147 - .../messageActionChatEditPhoto.html | 147 - .../messageActionChatEditTitle.html | 147 - .../messageActionChatJoinedByLink.html | 147 - .../messageActionChatMigrateTo.html | 150 - .../messageActionContactSignUp.html | 132 - .../messageActionCustomAction.html | 147 - .../constructor/messageActionEmpty.html | 132 - .../messageActionGeoProximityReached.html | 160 - .../constructor/messageActionGroupCall.html | 157 - .../messageActionGroupCallScheduled.html | 152 - .../messageActionHistoryClear.html | 132 - .../messageActionInviteToGroupCall.html | 152 - .../messageActionPaymentSentMe.html | 179 - .../constructor/messageActionPhoneCall.html | 167 - .../constructor/messageActionPinMessage.html | 132 - .../messageActionScreenshotTaken.html | 132 - .../messageActionSecureValuesSent.html | 149 - .../messageActionSecureValuesSentMe.html | 154 - .../messageActionSetChatTheme.html | 147 - .../messageActionSetMessagesTTL.html | 147 - .../constructor/messageEmpty.html | 157 - .../constructor/messageEntityBankCard.html | 152 - .../constructor/messageEntityBlockquote.html | 152 - .../constructor/messageEntityBold.html | 152 - .../constructor/messageEntityBotCommand.html | 152 - .../constructor/messageEntityCashtag.html | 152 - .../constructor/messageEntityCode.html | 152 - .../constructor/messageEntityEmail.html | 152 - .../constructor/messageEntityHashtag.html | 152 - .../constructor/messageEntityItalic.html | 152 - .../constructor/messageEntityMention.html | 155 - .../constructor/messageEntityMentionName.html | 162 - .../constructor/messageEntityPhone.html | 152 - .../constructor/messageEntityPre.html | 157 - .../constructor/messageEntityStrike.html | 152 - .../constructor/messageEntityTextUrl.html | 160 - .../constructor/messageEntityUnderline.html | 152 - .../constructor/messageEntityUnknown.html | 152 - .../constructor/messageEntityUrl.html | 155 - .../constructor/messageFwdHeader.html | 195 - .../messageInteractionCounters.html | 157 - .../constructor/messageMediaAudio.html | 147 - .../constructor/messageMediaContact.html | 167 - .../constructor/messageMediaDice.html | 155 - .../constructor/messageMediaDocument.html | 157 - .../constructor/messageMediaEmpty.html | 132 - .../constructor/messageMediaGame.html | 147 - .../constructor/messageMediaGeo.html | 147 - .../constructor/messageMediaGeoLive.html | 170 - .../constructor/messageMediaPhoto.html | 157 - .../constructor/messageMediaPoll.html | 152 - .../constructor/messageMediaUnsupported.html | 132 - .../constructor/messageMediaVenue.html | 172 - .../constructor/messageMediaWebPage.html | 147 - .../constructor/messageRange.html | 152 - .../constructor/messageReplies.html | 189 - .../constructor/messageReplyHeader.html | 165 - .../constructor/messageService.html | 212 - .../constructor/messageUserVote.html | 157 - .../messageUserVoteInputOption.html | 155 - .../constructor/messageUserVoteMultiple.html | 157 - .../constructor/messageViews.html | 165 - .../messages.affectedFoundMessages | 165 - .../constructor/messages.affectedHistory | 157 - .../constructor/messages.affectedMessages | 155 - .../constructor/messages.allStickers | 155 - .../messages.allStickersNotModified | 132 - .../constructor/messages.archivedStickers | 152 - .../constructor/messages.botCallbackAnswer | 177 - .../constructor/messages.botResults | 182 - .../constructor/messages.channelMessages | 185 - .../messages.chatAdminsWithInvites | 152 - .../constructor/messages.chatFull | 157 - .../constructor/messages.chatInviteImporters | 157 - .../constructor/messages.chats | 147 - .../constructor/messages.chatsSlice | 155 - .../messages.checkedHistoryImportPeer | 150 - .../constructor/messages.dhConfig | 162 - .../constructor/messages.dhConfigNotModified | 147 - .../constructor/messages.dialogs | 162 - .../constructor/messages.dialogsNotModified | 147 - .../constructor/messages.dialogsSlice | 167 - .../constructor/messages.discussionMessage | 185 - .../constructor/messages.exportedChatInvite | 152 - .../messages.exportedChatInviteReplaced | 157 - .../constructor/messages.favedStickers | 160 - .../messages.favedStickersNotModified | 132 - .../constructor/messages.featuredStickers | 165 - .../messages.featuredStickersNotModified | 147 - .../constructor/messages.foundStickerSets | 155 - .../messages.foundStickerSetsNotModified | 132 - .../constructor/messages.highScores | 152 - .../constructor/messages.historyImport | 150 - .../constructor/messages.historyImportParsed | 166 - .../constructor/messages.messageEditData | 152 - .../constructor/messages.messageViews | 157 - .../constructor/messages.messages | 157 - .../constructor/messages.messagesNotModified | 147 - .../constructor/messages.messagesSlice | 185 - .../constructor/messages.peerDialogs | 170 - .../constructor/messages.recentStickers | 165 - .../messages.recentStickersNotModified | 132 - .../constructor/messages.savedGifs | 155 - .../constructor/messages.savedGifsNotModified | 132 - .../constructor/messages.searchCounter | 165 - .../constructor/messages.sentEncryptedFile | 152 - .../constructor/messages.sentEncryptedMessage | 147 - .../constructor/messages.sentMessageLink | 167 - .../constructor/messages.sponsoredMessages | 157 - .../constructor/messages.statedMessagesLinks | 172 - .../constructor/messages.stickerSet | 157 - .../messages.stickerSetInstallResultArchive | 147 - .../messages.stickerSetInstallResultSuccess | 132 - .../constructor/messages.stickers | 155 - .../constructor/messages.stickersNotModified | 132 - .../constructor/messages.votesList | 170 - .../constructor/nearestDc.html | 157 - .../constructor/notifyBroadcasts.html | 132 - .../constructor/notifyChats.html | 132 - .../constructor/notifyPeer.html | 147 - .../constructor/notifyUsers.html | 132 - .../constructor/null.html | 132 - .../constructor/page.html | 190 - .../constructor/pageBlockAnchor.html | 147 - .../constructor/pageBlockAudio.html | 155 - .../constructor/pageBlockAuthorDate.html | 152 - .../constructor/pageBlockBlockquote.html | 152 - .../constructor/pageBlockChannel.html | 147 - .../constructor/pageBlockCollage.html | 152 - .../constructor/pageBlockCover.html | 147 - .../constructor/pageBlockDetails.html | 162 - .../constructor/pageBlockDivider.html | 132 - .../constructor/pageBlockEmbed.html | 187 - .../constructor/pageBlockEmbedPost.html | 177 - .../constructor/pageBlockFooter.html | 147 - .../constructor/pageBlockHeader.html | 147 - .../constructor/pageBlockKicker.html | 147 - .../constructor/pageBlockList.html | 147 - .../constructor/pageBlockMap.html | 167 - .../constructor/pageBlockOrderedList.html | 147 - .../constructor/pageBlockParagraph.html | 147 - .../constructor/pageBlockPhoto.html | 167 - .../constructor/pageBlockPreformatted.html | 152 - .../constructor/pageBlockPullquote.html | 152 - .../constructor/pageBlockRelatedArticles.html | 152 - .../constructor/pageBlockSlideshow.html | 152 - .../constructor/pageBlockSubheader.html | 147 - .../constructor/pageBlockSubtitle.html | 147 - .../constructor/pageBlockTable.html | 167 - .../constructor/pageBlockTitle.html | 147 - .../constructor/pageBlockUnsupported.html | 132 - .../constructor/pageBlockVideo.html | 167 - .../constructor/pageCaption.html | 152 - .../constructor/pageListItemBlocks.html | 147 - .../constructor/pageListItemText.html | 147 - .../pageListOrderedItemBlocks.html | 152 - .../constructor/pageListOrderedItemText.html | 152 - .../constructor/pageRelatedArticle.html | 182 - .../constructor/pageTableCell.html | 187 - .../constructor/pageTableRow.html | 147 - ...BKDF2HMACSHA512iter100000SHA256ModPow.html | 165 - .../constructor/passwordKdfAlgoUnknown.html | 132 - .../constructor/paymentCharge.html | 152 - .../constructor/paymentRequestedInfo.html | 167 - .../payments.ValidatedRequestedInfo | 145 - .../constructor/payments.bankCardData | 152 - .../constructor/payments.paymentReceipt | 219 - .../constructor/payments.paymentResult | 147 - .../payments.paymentVerificationNeeded | 147 - .../constructor/payments.savedInfo | 157 - .../constructor/peerBlocked.html | 152 - .../constructor/peerChannel.html | 147 - .../constructor/peerChat.html | 147 - .../constructor/peerLocated.html | 157 - .../constructor/peerNotifySettings.html | 182 - .../constructor/peerSelfLocated.html | 147 - .../constructor/peerSettings.html | 197 - .../constructor/peerUser.html | 147 - .../constructor/phone.joinAsPeers | 157 - .../constructor/phone.phoneCall | 152 - .../constructor/phoneCall.html | 209 - .../phoneCallDiscardReasonBusy.html | 132 - .../phoneCallDiscardReasonDisconnect.html | 132 - .../phoneCallDiscardReasonHangup.html | 132 - .../phoneCallDiscardReasonMissed.html | 132 - .../constructor/phoneCallDiscarded.html | 182 - .../constructor/phoneCallEmpty.html | 147 - .../constructor/phoneCallProtocol.html | 179 - .../constructor/phoneCallRequested.html | 189 - .../constructor/phoneCallWaiting.html | 187 - .../constructor/phoneConnection.html | 167 - .../constructor/phoneConnectionWebrtc.html | 187 - .../constructor/photo.html | 192 - .../constructor/photoCachedSize.html | 167 - .../constructor/photoEmpty.html | 147 - .../constructor/photoPathSize.html | 155 - .../constructor/photoSize.html | 167 - .../constructor/photoSizeEmpty.html | 150 - .../constructor/photoStrippedSize.html | 159 - .../constructor/photos.photo | 152 - .../constructor/photos.photos | 152 - .../constructor/photos.photosSlice | 157 - .../constructor/poll.html | 195 - .../constructor/pollAnswer.html | 155 - .../constructor/pollAnswerVoters.html | 170 - .../constructor/pollResults.html | 184 - .../constructor/popularContact.html | 152 - .../constructor/postAddress.html | 172 - .../constructor/privacyKeyAddedByPhone.html | 132 - .../constructor/privacyKeyChatInvite.html | 132 - .../constructor/privacyKeyForwards.html | 132 - .../constructor/privacyKeyPhoneCall.html | 132 - .../constructor/privacyKeyPhoneNumber.html | 132 - .../constructor/privacyKeyPhoneP2P.html | 132 - .../constructor/privacyKeyProfilePhoto.html | 132 - .../privacyKeyStatusTimestamp.html | 132 - .../constructor/privacyValueAllowAll.html | 132 - .../privacyValueAllowChatParticipants.html | 147 - .../privacyValueAllowContacts.html | 132 - .../constructor/privacyValueAllowUsers.html | 147 - .../constructor/privacyValueDisallowAll.html | 132 - .../privacyValueDisallowChatParticipants.html | 147 - .../privacyValueDisallowContacts.html | 132 - .../privacyValueDisallowUsers.html | 147 - .../constructor/receivedNotifyMessage.html | 152 - .../constructor/recentMeUrlChat.html | 152 - .../constructor/recentMeUrlChatInvite.html | 152 - .../constructor/recentMeUrlStickerSet.html | 152 - .../constructor/recentMeUrlUnknown.html | 147 - .../constructor/recentMeUrlUser.html | 152 - .../constructor/replyInlineMarkup.html | 147 - .../constructor/replyKeyboardForceReply.html | 162 - .../constructor/replyKeyboardHide.html | 152 - .../constructor/restrictionReason.html | 158 - .../constructor/savedPhoneContact.html | 162 - .../secureCredentialsEncrypted.html | 159 - .../constructor/secureData.html | 160 - .../constructor/secureFile.html | 180 - .../constructor/secureFileEmpty.html | 132 - ...wordKdfAlgoPBKDF2HMACSHA512iter100000.html | 147 - .../securePasswordKdfAlgoSHA512.html | 147 - .../securePasswordKdfAlgoUnknown.html | 132 - .../constructor/securePlainEmail.html | 150 - .../constructor/securePlainPhone.html | 150 - .../constructor/secureRequiredType.html | 167 - .../constructor/secureRequiredTypeOneOf.html | 147 - .../constructor/secureSecretSettings.html | 157 - .../constructor/secureValue.html | 194 - .../constructor/secureValueError.html | 157 - .../constructor/secureValueErrorData.html | 175 - .../constructor/secureValueErrorFile.html | 168 - .../constructor/secureValueErrorFiles.html | 168 - .../secureValueErrorFrontSide.html | 166 - .../secureValueErrorReverseSide.html | 162 - .../constructor/secureValueErrorSelfie.html | 166 - .../secureValueErrorTranslationFile.html | 178 - .../secureValueErrorTranslationFiles.html | 178 - .../constructor/secureValueHash.html | 152 - .../constructor/secureValueTypeAddress.html | 132 - .../secureValueTypeBankStatement.html | 132 - .../secureValueTypeDriverLicense.html | 132 - .../constructor/secureValueTypeEmail.html | 132 - .../secureValueTypeIdentityCard.html | 132 - .../secureValueTypeInternalPassport.html | 134 - .../constructor/secureValueTypePassport.html | 132 - .../secureValueTypePassportRegistration.html | 134 - .../secureValueTypePersonalDetails.html | 132 - .../constructor/secureValueTypePhone.html | 132 - .../secureValueTypeRentalAgreement.html | 132 - .../secureValueTypeTemporaryRegistration.html | 132 - .../secureValueTypeUtilityBill.html | 132 - .../constructor/sendMessageCancelAction.html | 132 - .../sendMessageChooseContactAction.html | 132 - .../sendMessageChooseStickerAction.html | 132 - .../sendMessageEmojiInteraction.html | 160 - .../sendMessageGamePlayAction.html | 132 - .../sendMessageGeoLocationAction.html | 132 - .../sendMessageHistoryImportAction.html | 147 - .../sendMessageRecordAudioAction.html | 132 - .../sendMessageRecordRoundAction.html | 132 - .../sendMessageRecordVideoAction.html | 132 - .../constructor/sendMessageTypingAction.html | 132 - .../sendMessageUploadAudioAction.html | 147 - .../sendMessageUploadDocumentAction.html | 147 - .../sendMessageUploadPhotoAction.html | 147 - .../sendMessageUploadRoundAction.html | 147 - .../sendMessageUploadVideoAction.html | 147 - .../constructor/shippingOption.html | 157 - .../speakingInGroupCallAction.html | 132 - .../constructor/sponsoredMessage.html | 178 - .../constructor/stats.broadcastStats | 220 - .../constructor/stats.megagroupStats | 230 - .../constructor/statsAbsValueAndPrev.html | 152 - .../constructor/statsDateRangeDays.html | 155 - .../constructor/statsGraph.html | 160 - .../constructor/statsGraphAsync.html | 152 - .../constructor/statsGroupTopAdmin.html | 165 - .../constructor/statsGroupTopInviter.html | 155 - .../constructor/statsGroupTopPoster.html | 160 - .../constructor/statsURL.html | 147 - .../constructor/stickerPack.html | 156 - .../constructor/stickerSet.html | 217 - .../constructor/stickerSetCovered.html | 152 - .../constructor/stickerSetMultiCovered.html | 152 - .../constructor/stickers.suggestedShortName | 147 - .../constructor/storage.fileGif | 132 - .../constructor/storage.fileJpeg | 132 - .../constructor/storage.fileMov | 132 - .../constructor/storage.fileMp3 | 132 - .../constructor/storage.fileMp4 | 132 - .../constructor/storage.filePartial | 132 - .../constructor/storage.filePdf | 132 - .../constructor/storage.filePng | 132 - .../constructor/storage.fileUnknown | 132 - .../constructor/storage.fileWebp | 132 - .../constructor/textAnchor.html | 152 - .../constructor/textBold.html | 147 - .../constructor/textConcat.html | 147 - .../constructor/textEmail.html | 152 - .../constructor/textEmpty.html | 132 - .../constructor/textFixed.html | 147 - .../constructor/textImage.html | 157 - .../constructor/textItalic.html | 147 - .../constructor/textMarked.html | 147 - .../constructor/textPhone.html | 152 - .../constructor/textPlain.html | 147 - .../constructor/textStrike.html | 147 - .../constructor/textSubscript.html | 147 - .../constructor/textSuperscript.html | 147 - .../constructor/textUnderline.html | 147 - .../constructor/textUrl.html | 157 - .../constructor/theme.html | 197 - .../constructor/topPeer.html | 155 - .../topPeerCategoryBotsInline.html | 132 - .../constructor/topPeerCategoryBotsPM.html | 132 - .../constructor/topPeerCategoryChannels.html | 132 - .../topPeerCategoryCorrespondents.html | 132 - .../topPeerCategoryForwardChats.html | 132 - .../topPeerCategoryForwardUsers.html | 132 - .../constructor/topPeerCategoryGroups.html | 132 - .../constructor/topPeerCategoryPeers.html | 157 - .../topPeerCategoryPhoneCalls.html | 132 - .../constructor/true.html | 134 - .../constructor/updateBotCallbackQuery.html | 182 - .../constructor/updateBotCommands.html | 159 - .../constructor/updateBotInlineQuery.html | 177 - .../constructor/updateBotInlineSend.html | 172 - .../updateBotPrecheckoutQuery.html | 184 - .../constructor/updateBotStopped.html | 165 - .../constructor/updateBotWebhookJSON.html | 147 - .../updateBotWebhookJSONQuery.html | 157 - .../constructor/updateChannel.html | 147 - .../updateChannelAvailableMessages.html | 155 - .../updateChannelMessageForwards.html | 157 - .../updateChannelMessageViews.html | 157 - .../constructor/updateChannelParticipant.html | 192 - .../updateChannelReadMessagesContents.html | 155 - .../constructor/updateChannelTooLong.html | 161 - .../constructor/updateChannelUserTyping.html | 172 - .../constructor/updateChannelWebPage.html | 167 - .../constructor/updateChat.html | 147 - .../updateChatDefaultBannedRights.html | 160 - .../constructor/updateChatParticipant.html | 192 - .../constructor/updateChatParticipantAdd.html | 167 - .../updateChatParticipantAdmin.html | 165 - .../constructor/updateChatParticipants.html | 147 - .../constructor/updateChatUserTyping.html | 160 - .../constructor/updateConfig.html | 135 - .../constructor/updateContactsReset.html | 132 - .../constructor/updateDcOptions.html | 147 - .../updateDeleteChannelMessages.html | 167 - .../constructor/updateDeleteMessages.html | 160 - .../constructor/updateDialogFilter.html | 160 - .../constructor/updateDialogFilterOrder.html | 150 - .../constructor/updateDialogFilters.html | 135 - .../constructor/updateDialogPinned.html | 165 - .../constructor/updateDialogUnreadMark.html | 157 - .../constructor/updateDraftMessage.html | 155 - .../constructor/updateEditChannelMessage.html | 162 - .../constructor/updateEditMessage.html | 160 - .../updateEncryptedChatTyping.html | 147 - .../updateEncryptedMessagesRead.html | 157 - .../constructor/updateEncryption.html | 152 - .../constructor/updateFavedStickers.html | 135 - .../constructor/updateFolderPeers.html | 162 - .../constructor/updateGeoLiveViewed.html | 152 - .../constructor/updateGroupCall.html | 155 - .../updateGroupCallConnection.html | 157 - .../updateGroupCallParticipants.html | 157 - .../updateInlineBotCallbackQuery.html | 177 - .../constructor/updateLangPack.html | 147 - .../constructor/updateLangPackTooLong.html | 150 - .../constructor/updateLoginToken.html | 132 - .../constructor/updateMessageID.html | 155 - .../constructor/updateMessagePoll.html | 162 - .../constructor/updateMessagePollVote.html | 165 - .../constructor/updateNewChannelMessage.html | 162 - .../updateNewEncryptedMessage.html | 155 - .../constructor/updateNewMessage.html | 157 - .../updateNewScheduledMessage.html | 150 - .../constructor/updateNewStickerSet.html | 147 - .../constructor/updateNotifySettings.html | 152 - .../constructor/updatePeerBlocked.html | 152 - .../constructor/updatePeerHistoryTTL.html | 157 - .../constructor/updatePeerLocated.html | 147 - .../constructor/updatePeerSettings.html | 152 - .../constructor/updatePhoneCall.html | 147 - .../updatePhoneCallSignalingData.html | 152 - .../constructor/updatePinnedDialogs.html | 160 - .../constructor/updatePinnedMessages.html | 175 - .../constructor/updatePrivacy.html | 152 - .../constructor/updatePtsChanged.html | 135 - .../updateReadChannelDiscussionInbox.html | 177 - .../updateReadChannelDiscussionOutbox.html | 162 - .../constructor/updateReadChannelInbox.html | 179 - .../constructor/updateReadChannelOutbox.html | 155 - .../updateReadFeaturedStickers.html | 132 - .../constructor/updateReadHistoryInbox.html | 182 - .../constructor/updateReadHistoryOutbox.html | 165 - .../updateReadMessagesContents.html | 160 - .../constructor/updateRecentStickers.html | 132 - .../constructor/updateSavedGifs.html | 132 - .../updateServiceNotification.html | 183 - .../constructor/updateShort.html | 152 - .../constructor/updateShortChatMessage.html | 232 - .../constructor/updateShortMessage.html | 229 - .../constructor/updateStickerSets.html | 132 - .../constructor/updateStickerSetsOrder.html | 157 - .../constructor/updateTheme.html | 147 - .../constructor/updateUserBlocked.html | 159 - .../constructor/updateUserName.html | 167 - .../constructor/updateUserPhone.html | 152 - .../constructor/updateUserPhoto.html | 165 - .../constructor/updateUserStatus.html | 152 - .../constructor/updateUserTyping.html | 155 - .../constructor/updateWebPage.html | 160 - .../constructor/updates.channelDifference | 185 - .../updates.channelDifferenceEmpty | 165 - .../updates.channelDifferenceTooLong | 190 - .../constructor/updates.difference | 172 - .../constructor/updates.differenceEmpty | 152 - .../constructor/updates.differenceSlice | 175 - .../constructor/updates.differenceTooLong | 150 - .../constructor/updates.html | 167 - .../constructor/updatesCombined.html | 172 - .../constructor/updatesTooLong.html | 135 - .../constructor/upload.cdnFile | 149 - .../constructor/upload.cdnFileReuploadNeeded | 149 - .../constructor/upload.file | 157 - .../constructor/upload.fileCdnRedirect | 169 - .../constructor/upload.webFile | 170 - .../constructor/urlAuthResultAccepted.html | 150 - .../constructor/urlAuthResultDefault.html | 135 - .../constructor/urlAuthResultRequest.html | 165 - .../constructor/user.html | 287 - .../constructor/userEmpty.html | 147 - .../constructor/userFull.html | 239 - .../constructor/userProfilePhoto.html | 172 - .../constructor/userProfilePhotoEmpty.html | 132 - .../constructor/userStatusEmpty.html | 132 - .../constructor/userStatusLastMonth.html | 132 - .../constructor/userStatusLastWeek.html | 132 - .../constructor/userStatusOffline.html | 147 - .../constructor/userStatusOnline.html | 147 - .../constructor/userStatusRecently.html | 132 - .../constructor/vector.html | 134 - .../constructor/videoSize.html | 175 - .../constructor/wallPaper.html | 192 - .../constructor/wallPaperNoFile.html | 171 - .../constructor/wallPaperSettings.html | 187 - .../constructor/wallPaperSolid.html | 162 - .../constructor/webAuthorization.html | 189 - .../constructor/webDocument.html | 167 - .../constructor/webDocumentNoProxy.html | 165 - .../constructor/webPage.html | 240 - .../constructor/webPageEmpty.html | 147 - .../constructor/webPageNotModified.html | 152 - .../constructor/webPagePending.html | 152 - .../css/core-widgets.css | 105 - .../corefork.telegram.org/getProxyConfig.html | 24 - .../import-stickers.html | 159 - data/corefork.telegram.org/js/core-widgets.js | 279 - .../method/account.acceptAuthorization | 170 - .../method/account.cancelPasswordEmail | 138 - .../method/account.changePhone | 190 - .../method/account.checkUsername | 167 - .../method/account.confirmPasswordEmail | 175 - .../method/account.confirmPhone | 180 - .../method/account.createTheme | 186 - .../method/account.declinePasswordReset | 155 - .../method/account.deleteAccount | 170 - .../method/account.deleteSecureValue | 153 - .../method/account.finishTakeoutSession | 172 - .../method/account.getAccountTTL | 134 - .../method/account.getAllSecureValues | 136 - .../method/account.getAuthorizationForm | 176 - .../method/account.getAuthorizations | 134 - .../method/account.getAutoDownloadSettings | 134 - .../account.getContactSignUpNotification | 135 - .../method/account.getGlobalPrivacySettings | 134 - .../method/account.getMultiWallPapers | 148 - .../method/account.getNotifyExceptions | 165 - .../method/account.getNotifySettings | 166 - .../method/account.getPassword | 134 - .../method/account.getPasswordSettings | 170 - .../method/account.getPrivacy | 166 - .../method/account.getSecureValue | 151 - .../method/account.getTheme | 181 - .../method/account.getThemes | 158 - .../method/account.getTmpPassword | 176 - .../method/account.getWallPaper | 167 - .../method/account.getWallPapers | 153 - .../method/account.getWebAuthorizations | 136 - .../method/account.initTakeoutSession | 204 - .../method/account.installTheme | 165 - .../method/account.installWallPaper | 172 - .../method/account.registerDevice | 217 - .../method/account.reportPeer | 182 - .../method/account.reportProfilePhoto | 165 - .../method/account.resetAuthorization | 175 - .../method/account.resetNotifySettings | 135 - .../method/account.resetPassword | 139 - .../method/account.resetWallPapers | 135 - .../method/account.resetWebAuthorization | 171 - .../method/account.resetWebAuthorizations | 137 - .../method/account.saveAutoDownloadSettings | 165 - .../method/account.saveSecureValue | 174 - .../method/account.saveTheme | 155 - .../method/account.saveWallPaper | 177 - .../method/account.sendChangePhoneCode | 186 - .../method/account.sendConfirmPhoneCode | 174 - .../method/account.sendVerifyEmailCode | 168 - .../method/account.sendVerifyPhoneCode | 173 - .../method/account.setAccountTTL | 167 - .../account.setContactSignUpNotification | 150 - .../method/account.setContentSettings | 172 - .../method/account.setGlobalPrivacySettings | 166 - .../method/account.setPrivacy | 181 - .../method/account.unregisterDevice | 180 - .../method/account.updateDeviceLocked | 153 - .../method/account.updateNotifySettings | 192 - .../method/account.updatePasswordSettings | 207 - .../method/account.updateProfile | 187 - .../method/account.updateTheme | 196 - .../method/account.updateUsername | 182 - .../method/account.uploadTheme | 190 - .../method/account.uploadWallPaper | 182 - .../method/account.verifyEmail | 179 - .../method/account.verifyPhone | 191 - .../method/auth.acceptLoginToken | 171 - .../method/auth.bindTempAuthKey | 252 - .../method/auth.cancelCode | 180 - .../method/auth.checkPassword | 180 - .../method/auth.checkRecoveryPassword | 174 - .../method/auth.dropTempAuthKeys | 151 - .../method/auth.exportAuthorization | 167 - .../method/auth.exportLoginToken | 183 - .../method/auth.importAuthorization | 178 - .../method/auth.importBotAuthorization | 205 - .../method/auth.importLoginToken | 187 - data/corefork.telegram.org/method/auth.logOut | 140 - .../method/auth.recoverPassword | 187 - .../method/auth.requestPasswordRecovery | 159 - .../method/auth.resendCode | 191 - .../method/auth.resetAuthorizations | 156 - .../method/auth.sendCall | 175 - .../method/auth.sendInvites | 157 - .../corefork.telegram.org/method/auth.sendSms | 167 - data/corefork.telegram.org/method/auth.signIn | 219 - data/corefork.telegram.org/method/auth.signUp | 236 - .../method/bots.answerWebhookJSONQuery | 178 - .../method/bots.getBotCommands | 154 - .../method/bots.resetBotCommands | 156 - .../method/bots.sendCustomRequest | 177 - .../method/bots.setBotCommands | 188 - .../method/channels.checkUsername | 190 - .../method/channels.convertToGigagroup | 177 - .../method/channels.createChannel | 232 - .../method/channels.deleteChannel | 200 - .../method/channels.deleteHistory | 180 - .../method/channels.deleteMessages | 190 - .../method/channels.deleteUserHistory | 199 - .../method/channels.editAdmin | 301 - .../method/channels.editBanned | 241 - .../method/channels.editCreator | 225 - .../method/channels.editLocation | 180 - .../method/channels.editPhoto | 221 - .../method/channels.editTitle | 206 - .../method/channels.exportMessageLink | 204 - .../method/channels.getAdminLog | 226 - .../method/channels.getAdminedPublicChannels | 191 - .../method/channels.getChannels | 181 - .../method/channels.getFullChannel | 187 - .../method/channels.getGroupsForDiscussion | 144 - .../method/channels.getInactiveChannels | 134 - .../method/channels.getLeftChannels | 172 - .../method/channels.getMessages | 193 - .../method/channels.getParticipant | 205 - .../method/channels.getParticipants | 203 - .../method/channels.getSponsoredMessages | 154 - .../method/channels.inviteToChannel | 262 - .../method/channels.joinChannel | 227 - .../method/channels.leaveChannel | 201 - .../method/channels.readHistory | 185 - .../method/channels.readMessageContents | 185 - .../method/channels.reportSpam | 192 - .../method/channels.setDiscussionGroup | 200 - .../method/channels.setStickers | 183 - .../method/channels.toggleSignatures | 187 - .../method/channels.toggleSlowMode | 190 - .../method/channels.updateUsername | 212 - .../method/contacts.acceptContact | 190 - .../method/contacts.addContact | 217 - .../method/contacts.block | 182 - .../method/contacts.blockFromReplies | 178 - .../method/contacts.deleteByPhones | 150 - .../method/contacts.deleteContacts | 155 - .../method/contacts.getBlocked | 155 - .../method/contacts.getContactIDs | 151 - .../method/contacts.getContacts | 155 - .../method/contacts.getLocated | 197 - .../method/contacts.getSaved | 150 - .../method/contacts.getStatuses | 133 - .../method/contacts.getTopPeers | 226 - .../method/contacts.importContacts | 154 - .../method/contacts.resetSaved | 135 - .../method/contacts.resetTopPeerRating | 175 - .../method/contacts.search | 178 - .../method/contacts.toggleTopPeers | 153 - .../method/contacts.unblock | 182 - .../method/folders.deleteFolder | 175 - .../method/folders.editPeerFolders | 175 - .../method/help.acceptTermsOfService | 150 - .../method/help.dismissSuggestion | 160 - .../method/help.editUserInfo | 180 - .../method/help.getAppChangelog | 162 - .../method/help.getAppConfig | 142 - .../method/help.getAppUpdate | 150 - .../method/help.getCdnConfig | 154 - .../method/help.getConfig | 192 - .../method/help.getCountriesList | 158 - .../method/help.getDeepLinkInfo | 150 - .../method/help.getInviteText | 134 - .../method/help.getNearestDc | 134 - .../method/help.getPassportConfig | 154 - .../method/help.getPromoData | 135 - .../method/help.getProxyData | 132 - .../method/help.getRecentMeUrls | 149 - .../method/help.getSupport | 134 - .../method/help.getSupportName | 151 - .../method/help.getTermsOfServiceUpdate | 135 - .../method/help.getUserInfo | 167 - .../method/help.hidePromoData | 150 - .../method/help.saveAppLog | 150 - .../method/help.setBotUpdatesStatus | 156 - .../method/initConnection.html | 216 - .../method/invokeAfterMsg.html | 154 - .../method/invokeAfterMsgs.html | 154 - .../method/invokeWithLayer.html | 204 - .../method/invokeWithMessagesRange.html | 154 - .../method/invokeWithTakeout.html | 154 - .../method/invokeWithoutUpdates.html | 154 - .../method/langpack.getDifference | 176 - .../method/langpack.getLanguage | 154 - .../method/langpack.getLanguages | 165 - .../method/messages.acceptEncryption | 190 - .../method/messages.addChatUser | 237 - .../method/messages.checkChatInvite | 178 - .../method/messages.checkHistoryImportPeer | 172 - .../method/messages.clearAllDrafts | 138 - .../method/messages.clearRecentStickers | 155 - .../method/messages.createChat | 197 - .../method/messages.deleteChat | 170 - .../method/messages.deleteExportedChatInvite | 155 - .../method/messages.deleteHistory | 206 - .../method/messages.deleteMessages | 177 - .../method/messages.deletePhoneCallHistory | 154 - .../method/messages.deleteScheduledMessages | 160 - .../method/messages.discardEncryption | 187 - .../method/messages.editChatAbout | 216 - .../method/messages.editChatAdmin | 195 - .../messages.editChatDefaultBannedRights | 206 - .../method/messages.editChatPhoto | 203 - .../method/messages.editChatTitle | 193 - .../method/messages.editExportedChatInvite | 193 - .../method/messages.editInlineBotMessage | 206 - .../method/messages.exportChatInvite | 217 - .../method/messages.faveSticker | 172 - .../method/messages.forwardMessage | 177 - .../method/messages.forwardMessages | 363 - .../method/messages.getAdminsWithInvites | 149 - .../method/messages.getAllChats | 150 - .../method/messages.getAllDrafts | 143 - .../method/messages.getAllStickers | 153 - .../method/messages.getArchivedStickers | 167 - .../method/messages.getBotCallbackAnswer | 226 - .../method/messages.getChatInviteImporters | 172 - .../method/messages.getChats | 173 - .../method/messages.getCommonChats | 185 - .../method/messages.getDhConfig | 175 - .../method/messages.getDialogFilters | 136 - .../method/messages.getDialogUnreadMarks | 133 - .../method/messages.getDialogs | 213 - .../method/messages.getDocumentByHash | 178 - .../method/messages.getEmojiKeywords | 149 - .../messages.getEmojiKeywordsDifference | 154 - .../method/messages.getEmojiKeywordsLanguages | 148 - .../method/messages.getEmojiURL | 149 - .../method/messages.getExportedChatInvite | 155 - .../method/messages.getExportedChatInvites | 182 - .../method/messages.getFavedStickers | 153 - .../method/messages.getFeaturedStickers | 153 - .../method/messages.getFullChat | 172 - .../method/messages.getGameHighScores | 187 - .../method/messages.getInlineBotResults | 226 - .../method/messages.getInlineGameHighScores | 177 - .../method/messages.getMaskStickers | 153 - .../method/messages.getMessageEditData | 186 - .../method/messages.getMessageReactionsList | 178 - .../messages.getMessageReadParticipants | 173 - .../method/messages.getMessages | 153 - .../method/messages.getMessagesReactions | 153 - .../method/messages.getMessagesViews | 199 - .../method/messages.getOldFeaturedStickers | 163 - .../method/messages.getOnlines | 171 - .../method/messages.getPeerDialogs | 181 - .../method/messages.getPeerSettings | 171 - .../method/messages.getPinnedDialogs | 169 - .../method/messages.getPollResults | 177 - .../method/messages.getRecentLocations | 165 - .../method/messages.getRecentStickers | 163 - .../method/messages.getReplies | 217 - .../method/messages.getSavedGifs | 153 - .../method/messages.getScheduledHistory | 182 - .../method/messages.getScheduledMessages | 179 - .../method/messages.getSearchCounters | 173 - .../method/messages.getSplitRanges | 133 - .../method/messages.getStickerSet | 172 - .../method/messages.getStickers | 175 - .../method/messages.getSuggestedDialogFilters | 136 - .../method/messages.getUnreadMentions | 212 - .../method/messages.getWebPage | 177 - .../method/messages.getWebPagePreview | 191 - .../method/messages.hidePeerSettingsBar | 153 - .../method/messages.importChatInvite | 227 - .../method/messages.installStickerSet | 172 - .../method/messages.markDialogUnread | 160 - .../method/messages.migrateChat | 190 - .../method/messages.readDiscussion | 180 - .../method/messages.readEncryptedHistory | 172 - .../method/messages.readFeaturedStickers | 150 - .../method/messages.readHistory | 186 - .../method/messages.readMentions | 181 - .../method/messages.readMessageContents | 149 - .../method/messages.receivedMessages | 148 - .../method/messages.receivedQueue | 170 - .../method/messages.reorderPinnedDialogs | 185 - .../method/messages.reorderStickerSets | 160 - .../method/messages.report | 187 - .../method/messages.reportSpam | 180 - .../method/messages.requestUrlAuth | 174 - .../method/messages.saveDraft | 202 - .../method/messages.saveGif | 172 - .../method/messages.saveRecentSticker | 182 - .../method/messages.search | 291 - .../method/messages.searchGifs | 177 - .../method/messages.searchGlobal | 226 - .../method/messages.searchStickerSets | 168 - .../method/messages.sendBroadcast | 145 - .../method/messages.sendEncrypted | 210 - .../method/messages.sendEncryptedFile | 215 - .../method/messages.sendEncryptedService | 205 - .../method/messages.sendInlineBotResult | 344 - .../method/messages.sendMedia | 518 - .../method/messages.sendMessage | 398 - .../method/messages.sendMultiMedia | 263 - .../method/messages.sendReaction | 185 - .../method/messages.sendScheduledMessages | 182 - .../messages.sendScreenshotNotification | 187 - .../method/messages.sendVote | 220 - .../method/messages.setBotPrecheckoutResults | 188 - .../method/messages.setBotShippingResults | 186 - .../method/messages.setChatTheme | 185 - .../method/messages.setEncryptedTyping | 177 - .../method/messages.setGameScore | 218 - .../method/messages.setHistoryTTL | 182 - .../method/messages.setInlineBotResults | 358 - .../method/messages.setInlineGameScore | 198 - .../method/messages.setTyping | 240 - .../method/messages.startBot | 224 - .../method/messages.startHistoryImport | 180 - .../method/messages.toggleDialogPin | 187 - .../method/messages.toggleStickerSets | 170 - .../method/messages.uninstallStickerSet | 167 - .../method/messages.unpinAllMessages | 153 - .../method/messages.updateDialogFilter | 190 - .../method/messages.updateDialogFiltersOrder | 153 - .../method/messages.updatePinnedMessage | 238 - .../method/messages.uploadEncryptedFile | 155 - .../method/messages.uploadImportedMedia | 181 - .../method/messages.uploadMedia | 264 - .../method/payments.getBankCardData | 166 - .../method/payments.getPaymentForm | 181 - .../method/payments.getSavedInfo | 134 - .../method/payments.sendPaymentForm | 206 - .../method/payments.validateRequestedInfo | 186 - .../method/phone.acceptCall | 193 - .../method/phone.checkGroupCall | 154 - .../method/phone.confirmCall | 188 - .../method/phone.createGroupCall | 200 - .../method/phone.discardCall | 202 - .../method/phone.discardGroupCall | 155 - .../method/phone.editGroupCallMember | 167 - .../method/phone.editGroupCallTitle | 160 - .../method/phone.exportGroupCallInvite | 159 - .../method/phone.getCallConfig | 134 - .../method/phone.getGroupCall | 157 - .../method/phone.getGroupCallJoinAs | 149 - .../method/phone.getGroupParticipants | 174 - .../method/phone.inviteToGroupCall | 177 - .../method/phone.joinGroupCall | 202 - .../method/phone.joinGroupCallPresentation | 180 - .../method/phone.leaveGroupCall | 160 - .../method/phone.leaveGroupCallPresentation | 155 - .../method/phone.receivedCall | 172 - .../method/phone.requestCall | 213 - .../method/phone.saveCallDebug | 177 - .../method/phone.sendSignalingData | 155 - .../method/phone.setCallRating | 192 - .../method/phone.startScheduledGroupCall | 155 - .../method/phone.toggleGroupCallRecord | 180 - .../method/phone.toggleGroupCallSettings | 187 - .../phone.toggleGroupCallStartSubscription | 160 - .../method/photos.deletePhotos | 148 - .../method/photos.getUserPhotos | 193 - .../method/photos.updateProfilePhoto | 196 - .../method/stats.getBroadcastStats | 194 - .../method/stats.getMegagroupStats | 191 - .../method/stats.loadAsyncGraph | 193 - .../method/stickers.changeStickerPosition | 177 - .../method/stickers.checkShortName | 172 - .../method/stickers.createStickerSet | 282 - .../method/stickers.removeStickerFromSet | 172 - .../method/stickers.setStickerSetThumb | 182 - .../method/stickers.suggestShortName | 166 - .../method/updates.getChannelDifference | 247 - .../method/updates.getDifference | 225 - .../method/updates.getState | 135 - .../method/upload.getCdnFile | 162 - .../method/upload.getCdnFileHashes | 178 - .../method/upload.getFile | 252 - .../method/upload.getFileHashes | 171 - .../method/upload.getWebFile | 176 - .../method/upload.reuploadCdnFile | 173 - .../method/upload.saveBigFilePart | 208 - .../method/users.getUsers | 191 - .../method/users.setSecureValueErrors | 176 - data/corefork.telegram.org/mtproto.html | 260 - .../mtproto/TL-abstract-types.html | 202 - .../mtproto/TL-combinators.html | 251 - .../mtproto/TL-dependent.html | 236 - .../mtproto/TL-formal.html | 319 - .../mtproto/TL-optargs.html | 151 - .../mtproto/TL-patterns.html | 129 - .../mtproto/TL-polymorph.html | 170 - data/corefork.telegram.org/mtproto/TL-tl.html | 308 - .../mtproto/TL-types.html | 124 - data/corefork.telegram.org/mtproto/TL.html | 210 - .../mtproto/description.html | 238 - .../mtproto/description_v1.html | 205 - .../mtproto/mtproto-transports.html | 281 - .../mtproto/samples-auth_key.html | 748 -- .../mtproto/security_guidelines.html | 177 - .../mtproto/security_guidelines_v1.html | 175 - .../mtproto/serialize.html | 240 - .../mtproto/service_messages.html | 195 - .../service_messages_about_messages.html | 185 - data/corefork.telegram.org/mtproto_v1.html | 229 - data/corefork.telegram.org/passport.html | 690 -- .../passport/encryption.html | 606 -- .../passport/example.html | 585 - .../passport/sdk-android.html | 180 - .../passport/sdk-ios-mac.html | 246 - .../passport/sdk-javascript.html | 258 - .../schema/end-to-end-json.html | 1 - .../schema/end-to-end.html | 225 - data/corefork.telegram.org/schema/json.html | 1 - .../schema/mtproto-json.html | 1 - .../corefork.telegram.org/schema/mtproto.html | 204 - .../type/AccountDaysTTL.html | 162 - data/corefork.telegram.org/type/Audio.html | 128 - .../type/Authorization.html | 162 - .../type/AutoDownloadSettings.html | 143 - .../type/BankCardOpenUrl.html | 143 - .../corefork.telegram.org/type/BaseTheme.html | 163 - data/corefork.telegram.org/type/Bool.html | 718 -- .../type/BotCommand.html | 143 - .../type/BotCommandScope.html | 176 - data/corefork.telegram.org/type/BotInfo.html | 143 - .../type/BotInlineMessage.html | 168 - .../type/BotInlineResult.html | 148 - .../corefork.telegram.org/type/CdnConfig.html | 164 - .../type/CdnPublicKey.html | 145 - .../type/ChannelAdminLogEvent.html | 143 - .../type/ChannelAdminLogEventAction.html | 298 - .../type/ChannelAdminLogEventsFilter.html | 143 - .../type/ChannelLocation.html | 148 - .../type/ChannelMessagesFilter.html | 148 - .../type/ChannelParticipantsFilter.html | 178 - data/corefork.telegram.org/type/Chat.html | 163 - .../type/ChatAdminWithInvites.html | 143 - .../type/ChatBannedRights.html | 146 - data/corefork.telegram.org/type/ChatFull.html | 148 - .../type/ChatInvite.html | 172 - .../type/ChatInviteImporter.html | 143 - .../type/ChatOnlines.html | 162 - .../type/ChatParticipant.html | 153 - .../type/ChatParticipants.html | 148 - .../corefork.telegram.org/type/ChatPhoto.html | 148 - .../corefork.telegram.org/type/ChatTheme.html | 143 - .../type/CodeSettings.html | 143 - data/corefork.telegram.org/type/Config.html | 162 - data/corefork.telegram.org/type/Contact.html | 143 - data/corefork.telegram.org/type/DataJSON.html | 168 - data/corefork.telegram.org/type/DcOption.html | 143 - .../type/DecryptedDataBlock.html | 128 - .../type/DecryptedMessage.html | 140 - .../type/DecryptedMessageAction.html | 145 - .../type/DecryptedMessageLayer.html | 129 - .../type/DecryptedMessageMedia.html | 149 - data/corefork.telegram.org/type/Dialog.html | 148 - .../type/DialogFilter.html | 143 - .../type/DialogFilterSuggested.html | 143 - .../type/DialogPeer.html | 148 - .../type/DisabledFeature.html | 128 - data/corefork.telegram.org/type/Document.html | 173 - .../type/DocumentAttribute.html | 173 - .../type/DraftMessage.html | 151 - .../type/EmojiKeyword.html | 148 - .../type/EmojiKeywordsDifference.html | 167 - .../type/EmojiLanguage.html | 143 - data/corefork.telegram.org/type/EmojiURL.html | 162 - .../type/EncryptedChat.html | 187 - .../type/EncryptedFile.html | 167 - .../type/EncryptedMessage.html | 148 - data/corefork.telegram.org/type/Error.html | 143 - .../type/ExportedChatInvite.html | 162 - .../type/ExportedMessageLink.html | 162 - .../type/FileLocation.html | 128 - data/corefork.telegram.org/type/Folder.html | 143 - .../type/FolderPeer.html | 143 - data/corefork.telegram.org/type/Game.html | 143 - data/corefork.telegram.org/type/GeoPoint.html | 148 - .../type/GlobalPrivacySettings.html | 167 - .../corefork.telegram.org/type/GroupCall.html | 148 - .../type/GroupCallParticipant.html | 143 - .../type/GroupCallParticipantVideo.html | 143 - .../GroupCallParticipantVideoSourceGroup.html | 143 - .../corefork.telegram.org/type/HighScore.html | 143 - .../type/ImportedContact.html | 143 - .../type/InlineBotSwitchPM.html | 143 - .../type/InlineQueryPeerType.html | 163 - .../type/InputAppEvent.html | 143 - .../type/InputBotInlineMessage.html | 173 - .../type/InputBotInlineMessageID.html | 148 - .../type/InputBotInlineResult.html | 158 - .../type/InputChannel.html | 153 - .../type/InputChatPhoto.html | 153 - .../type/InputCheckPasswordSRP.html | 151 - .../type/InputClientProxy.html | 145 - .../type/InputContact.html | 143 - .../type/InputDialogPeer.html | 148 - .../type/InputDocument.html | 148 - .../type/InputEncryptedChat.html | 143 - .../type/InputEncryptedFile.html | 158 - .../corefork.telegram.org/type/InputFile.html | 148 - .../type/InputFileLocation.html | 188 - .../type/InputFolderPeer.html | 143 - .../corefork.telegram.org/type/InputGame.html | 148 - .../type/InputGroupCall.html | 143 - .../type/InputMedia.html | 213 - .../type/InputMessage.html | 158 - .../type/InputNotifyPeer.html | 158 - .../type/InputPaymentCredentials.html | 158 - .../corefork.telegram.org/type/InputPeer.html | 173 - .../type/InputPeerNotifySettings.html | 143 - .../type/InputPhoneCall.html | 143 - .../type/InputPhoto.html | 148 - .../type/InputPrivacyKey.html | 178 - .../type/InputPrivacyRule.html | 178 - .../type/InputSecureFile.html | 151 - .../type/InputSecureValue.html | 145 - .../type/InputSingleMedia.html | 148 - .../type/InputStickerSet.html | 168 - .../type/InputStickerSetItem.html | 143 - .../type/InputStickeredMedia.html | 148 - .../type/InputTheme.html | 148 - .../type/InputThemeSettings.html | 143 - .../corefork.telegram.org/type/InputUser.html | 158 - .../type/InputWallPaper.html | 153 - .../type/InputWebDocument.html | 143 - .../type/InputWebFileLocation.html | 148 - data/corefork.telegram.org/type/Invoice.html | 143 - .../type/JSONObjectValue.html | 143 - .../corefork.telegram.org/type/JSONValue.html | 187 - .../type/KeyboardButton.html | 193 - .../type/KeyboardButtonRow.html | 143 - .../type/LabeledPrice.html | 143 - .../type/LangPackDifference.html | 167 - .../type/LangPackLanguage.html | 162 - .../type/LangPackString.html | 153 - .../type/MaskCoords.html | 143 - data/corefork.telegram.org/type/Message.html | 153 - .../type/MessageAction.html | 283 - .../type/MessageEntity.html | 233 - .../type/MessageFwdHeader.html | 143 - .../type/MessageInteractionCounters.html | 143 - .../type/MessageRange.html | 143 - .../type/MessageReactionsList.html | 128 - .../type/MessageReplies.html | 146 - .../type/MessageReplyHeader.html | 143 - .../type/MessageUserVote.html | 153 - .../type/MessageViews.html | 143 - .../type/MessagesFilter.html | 223 - .../corefork.telegram.org/type/NearestDc.html | 162 - .../type/NotifyPeer.html | 158 - data/corefork.telegram.org/type/Null.html | 143 - data/corefork.telegram.org/type/Page.html | 143 - .../corefork.telegram.org/type/PageBlock.html | 283 - .../type/PageCaption.html | 143 - .../type/PageListItem.html | 148 - .../type/PageListOrderedItem.html | 148 - .../type/PageRelatedArticle.html | 143 - .../type/PageTableCell.html | 143 - .../type/PageTableRow.html | 143 - .../type/PasswordKdfAlgo.html | 151 - .../type/PaymentCharge.html | 143 - .../type/PaymentRequestedInfo.html | 143 - .../type/PaymentSavedCredentials.html | 143 - data/corefork.telegram.org/type/Peer.html | 153 - .../type/PeerBlocked.html | 143 - .../type/PeerLocated.html | 148 - .../type/PeerNotifySettings.html | 162 - .../type/PeerSettings.html | 162 - .../corefork.telegram.org/type/PhoneCall.html | 168 - .../type/PhoneCallDiscardReason.html | 158 - .../type/PhoneCallProtocol.html | 143 - .../corefork.telegram.org/type/PhotoSize.html | 168 - data/corefork.telegram.org/type/Poll.html | 143 - .../type/PollAnswer.html | 146 - .../type/PollAnswerVoters.html | 143 - .../type/PollResults.html | 143 - .../type/PopularContact.html | 143 - .../type/PostAddress.html | 143 - .../type/PrivacyKey.html | 178 - .../type/PrivacyRule.html | 178 - .../type/ReceivedNotifyMessage.html | 143 - .../type/RecentMeUrl.html | 163 - .../type/ReplyMarkup.html | 158 - .../type/ReportReason.html | 178 - .../type/RestrictionReason.html | 143 - data/corefork.telegram.org/type/RichText.html | 218 - .../type/SavedContact.html | 143 - .../type/SecureCredentialsEncrypted.html | 143 - .../type/SecureData.html | 146 - .../type/SecureFile.html | 151 - .../type/SecurePasswordKdfAlgo.html | 155 - .../type/SecurePlainData.html | 150 - .../type/SecureRequiredType.html | 148 - .../type/SecureSecretSettings.html | 145 - .../type/SecureValue.html | 162 - .../type/SecureValueError.html | 183 - .../type/SecureValueHash.html | 143 - .../type/SecureValueType.html | 203 - .../type/SendMessageAction.html | 228 - .../type/ShippingOption.html | 143 - .../type/SponsoredMessage.html | 143 - .../type/StatsAbsValueAndPrev.html | 143 - .../type/StatsDateRangeDays.html | 143 - .../type/StatsGroupTopAdmin.html | 146 - .../type/StatsGroupTopInviter.html | 146 - .../type/StatsGroupTopPoster.html | 146 - .../type/StatsPercentValue.html | 143 - data/corefork.telegram.org/type/StatsURL.html | 143 - .../type/StickerPack.html | 143 - .../type/StickerSet.html | 143 - .../type/StickerSetCovered.html | 148 - data/corefork.telegram.org/type/Theme.html | 172 - .../type/ThemeSettings.html | 143 - data/corefork.telegram.org/type/TopPeer.html | 143 - .../type/TopPeerCategory.html | 178 - .../type/TopPeerCategoryPeers.html | 143 - data/corefork.telegram.org/type/True.html | 145 - data/corefork.telegram.org/type/Update.html | 603 -- data/corefork.telegram.org/type/Updates.html | 508 - .../type/UrlAuthResult.html | 177 - data/corefork.telegram.org/type/User.html | 177 - data/corefork.telegram.org/type/UserFull.html | 162 - .../type/UserProfilePhoto.html | 148 - .../type/UserStatus.html | 168 - data/corefork.telegram.org/type/Vector t.html | 143 - data/corefork.telegram.org/type/Video.html | 128 - .../corefork.telegram.org/type/VideoSize.html | 143 - .../corefork.telegram.org/type/WallPaper.html | 172 - .../type/WebAuthorization.html | 143 - .../type/WebDocument.html | 148 - .../type/account.AuthorizationForm | 162 - .../type/account.Authorizations | 162 - .../type/account.AutoDownloadSettings | 162 - .../type/account.ChatThemes | 167 - .../type/account.ContentSettings | 162 - .../type/account.Password | 162 - .../type/account.PasswordInputSettings | 146 - .../type/account.PasswordSettings | 164 - .../type/account.PrivacyRules | 167 - .../type/account.ResetPasswordResult | 175 - .../type/account.SentChangePhoneCode | 128 - .../type/account.SentEmailCode | 162 - .../type/account.Takeout | 162 - .../corefork.telegram.org/type/account.Themes | 167 - .../type/account.TmpPassword | 162 - .../type/account.WallPapers | 167 - .../type/account.WebAuthorizations | 162 - .../type/auth.Authorization | 192 - .../type/auth.CheckedPhone | 128 - .../type/auth.ExportedAuthorization | 162 - .../type/auth.LoginToken | 177 - .../type/auth.PasswordRecovery | 165 - data/corefork.telegram.org/type/auth.SentCode | 183 - data/corefork.telegram.org/type/bytes.html | 125 - .../type/channels.AdminLogResults | 162 - .../type/channels.ChannelParticipant | 162 - .../type/channels.ChannelParticipants | 167 - .../type/contacts.Blocked | 167 - .../type/contacts.Contacts | 167 - .../corefork.telegram.org/type/contacts.Found | 162 - .../type/contacts.ImportedContacts | 162 - data/corefork.telegram.org/type/contacts.Link | 128 - .../type/contacts.ResolvedPeer | 162 - .../type/contacts.TopPeers | 172 - data/corefork.telegram.org/type/double.html | 118 - .../corefork.telegram.org/type/help.AppUpdate | 167 - .../type/help.CountriesList | 167 - data/corefork.telegram.org/type/help.Country | 143 - .../type/help.CountryCode | 143 - .../type/help.DeepLinkInfo | 167 - .../type/help.InviteText | 162 - .../type/help.PassportConfig | 169 - .../corefork.telegram.org/type/help.PromoData | 167 - .../corefork.telegram.org/type/help.ProxyData | 130 - .../type/help.RecentMeUrls | 162 - data/corefork.telegram.org/type/help.Support | 162 - .../type/help.SupportName | 162 - .../type/help.TermsOfService | 143 - .../type/help.TermsOfServiceUpdate | 167 - data/corefork.telegram.org/type/help.UserInfo | 172 - data/corefork.telegram.org/type/int.html | 118 - data/corefork.telegram.org/type/long.html | 118 - .../type/messages.AffectedFoundMessages | 162 - .../type/messages.AffectedHistory | 178 - .../type/messages.AffectedMessages | 178 - .../type/messages.AllStickers | 172 - .../type/messages.ArchivedStickers | 162 - .../type/messages.BotCallbackAnswer | 162 - .../type/messages.BotResults | 162 - .../type/messages.ChatAdminsWithInvites | 162 - .../type/messages.ChatFull | 168 - .../type/messages.ChatInviteImporters | 162 - .../corefork.telegram.org/type/messages.Chats | 198 - .../type/messages.CheckedHistoryImportPeer | 165 - .../type/messages.DhConfig | 167 - .../type/messages.Dialogs | 172 - .../type/messages.DiscussionMessage | 162 - .../type/messages.ExportedChatInvite | 172 - .../type/messages.ExportedChatInvites | 162 - .../type/messages.FavedStickers | 167 - .../type/messages.FeaturedStickers | 172 - .../type/messages.FoundGifs | 128 - .../type/messages.FoundStickerSets | 167 - .../type/messages.HighScores | 167 - .../type/messages.HistoryImport | 165 - .../type/messages.HistoryImportParsed | 162 - .../type/messages.InactiveChats | 162 - .../type/messages.MessageEditData | 162 - .../type/messages.MessageViews | 162 - .../type/messages.Messages | 229 - .../type/messages.PeerDialogs | 167 - .../type/messages.RecentStickers | 167 - .../type/messages.SavedGifs | 167 - .../type/messages.SearchCounter | 143 - .../type/messages.SentEncryptedMessage | 177 - .../type/messages.SentMessage | 128 - .../type/messages.SponsoredMessages | 166 - .../type/messages.StatedMessage | 128 - .../type/messages.StatedMessages | 128 - .../type/messages.StickerSet | 188 - .../type/messages.StickerSetInstallResult | 167 - .../type/messages.Stickers | 167 - .../type/messages.VotesList | 162 - .../type/payments.PaymentForm | 162 - .../type/payments.PaymentResult | 167 - .../type/payments.SavedInfo | 162 - .../type/payments.ValidatedRequestedInfo | 162 - .../type/phone.ExportedGroupCallInvite | 162 - .../type/phone.GroupCall | 162 - .../type/phone.GroupParticipants | 162 - .../type/phone.JoinAsPeers | 162 - .../type/phone.PhoneCall | 172 - data/corefork.telegram.org/type/photos.Photos | 167 - .../type/stats.BroadcastStats | 162 - .../type/stats.MegagroupStats | 162 - .../type/stats.MessageStats | 162 - .../type/stickers.SuggestedShortName | 162 - .../type/storage.FileType | 188 - data/corefork.telegram.org/type/string.html | 126 - .../type/updates.ChannelDifference | 172 - .../type/updates.Difference | 177 - data/corefork.telegram.org/type/updates.State | 162 - .../corefork.telegram.org/type/upload.CdnFile | 167 - data/corefork.telegram.org/type/upload.File | 167 - .../corefork.telegram.org/type/upload.WebFile | 162 - data/corefork.telegram.org/widgets.html | 141 - .../widgets/discussion.html | 226 - data/corefork.telegram.org/widgets/login.html | 404 - data/corefork.telegram.org/widgets/post.html | 240 - data/corefork.telegram.org/widgets/share.html | 250 - data/telegram.org.html | 283 - data/telegram.org/android.html | 79 - data/telegram.org/blog.html | 268 - data/telegram.org/blog/400-million.html | 272 - data/telegram.org/blog/admin-revolution.html | 261 - .../blog/albums-saved-messages.html | 268 - data/telegram.org/blog/android-2-0.html | 257 - data/telegram.org/blog/android-themes.html | 246 - .../blog/archive-and-new-design.html | 318 - data/telegram.org/blog/autodelete-inv2.html | 299 - data/telegram.org/blog/bots-2-0.html | 260 - .../telegram.org/blog/cache-and-stickers.html | 231 - data/telegram.org/blog/captions-places.html | 244 - data/telegram.org/blog/channels-2-0.html | 246 - data/telegram.org/blog/channels.html | 224 - ...hemes-interactive-emoji-read-receipts.html | 297 - .../blog/contacts-local-groups.html | 272 - data/telegram.org/blog/coronavirus.html | 254 - data/telegram.org/blog/cryptocontest.html | 224 - data/telegram.org/blog/desktop-1-0.html | 250 - data/telegram.org/blog/desktop-compact.html | 213 - .../blog/discover-stickers-and-more.html | 246 - data/telegram.org/blog/edit.html | 245 - data/telegram.org/blog/export-and-more.html | 238 - .../filters-anonymous-admins-comments.html | 261 - data/telegram.org/blog/group-video-calls.html | 264 - data/telegram.org/blog/inline-bots.html | 234 - data/telegram.org/blog/instant-camera.html | 229 - data/telegram.org/blog/invite-links.html | 217 - .../live-streams-forwarding-next-channel.html | 285 - data/telegram.org/blog/masks.html | 248 - data/telegram.org/blog/moar-stickers.html | 343 - data/telegram.org/blog/move-history.html | 284 - .../blog/new-profiles-people-nearby.html | 263 - data/telegram.org/blog/passport.html | 233 - .../payments-2-0-scheduled-voice-chats.html | 319 - data/telegram.org/blog/payments.html | 253 - .../blog/photo-editor-and-passcodes.html | 252 - data/telegram.org/blog/polls-2-0-vmq.html | 271 - data/telegram.org/blog/polls.html | 230 - .../blog/privacy-discussions-web-bots.html | 284 - .../telegram.org/blog/privacy-revolution.html | 226 - .../blog/reactions-spoilers-translations.html | 300 - .../blog/replies-mentions-stickers.html | 257 - .../blog/scheduled-reminders-themes.html | 264 - data/telegram.org/blog/shared-links.html | 221 - .../blog/silent-messages-slow-mode.html | 296 - .../blog/stickers-meet-art-and-history.html | 338 - .../blog/stickers-revolution.html | 231 - data/telegram.org/blog/supergroups.html | 251 - .../telegram-me-change-number-and-pfs.html | 228 - data/telegram.org/blog/translations-iv2.html | 276 - data/telegram.org/blog/video-1000.html | 354 - data/telegram.org/blog/video-calls.html | 234 - data/telegram.org/blog/video-editor-gifs.html | 252 - .../blog/video-messages-and-telescope.html | 247 - .../blog/video-stickers-better-reactions.html | 273 - .../blog/voice-chats-on-steroids.html | 275 - data/telegram.org/blog/voice-chats.html | 311 - .../blog/winter-contest-ends.html | 224 - data/telegram.org/faq_channels.html | 165 - data/telegram.org/faq_spam.html | 163 - data/telegram.org/privacy.html | 299 - data/telegram.org/support.html | 141 - data/telegram.org/teststore.html | 283 - data/telegram.org/tour/channels.html | 294 - data/telegram.org/tour/groups.html | 266 - data/telegram.org/tour/quizbot.html | 215 - data/telegram.org/tour/screenshots.html | 217 - data/telegram.org/verify.html | 151 - 3534 files changed, 623022 deletions(-) delete mode 100644 data/core.telegram.org.html delete mode 100644 data/core.telegram.org/api.html delete mode 100644 data/core.telegram.org/api/account-deletion.html delete mode 100644 data/core.telegram.org/api/animated-emojis.html delete mode 100644 data/core.telegram.org/api/auth.html delete mode 100644 data/core.telegram.org/api/bots.html delete mode 100644 data/core.telegram.org/api/bots/buttons.html delete mode 100644 data/core.telegram.org/api/bots/commands.html delete mode 100644 data/core.telegram.org/api/bots/games.html delete mode 100644 data/core.telegram.org/api/bots/inline.html delete mode 100644 data/core.telegram.org/api/channel.html delete mode 100644 data/core.telegram.org/api/config.html delete mode 100644 data/core.telegram.org/api/datacenter.html delete mode 100644 data/core.telegram.org/api/dice.html delete mode 100644 data/core.telegram.org/api/discussion.html delete mode 100644 data/core.telegram.org/api/drafts.html delete mode 100644 data/core.telegram.org/api/end-to-end/pfs.html delete mode 100644 data/core.telegram.org/api/end-to-end/seq_no.html delete mode 100644 data/core.telegram.org/api/end-to-end/video-calls.html delete mode 100644 data/core.telegram.org/api/end-to-end/voice-calls.html delete mode 100644 data/core.telegram.org/api/end-to-end_v1.html delete mode 100644 data/core.telegram.org/api/entities.html delete mode 100644 data/core.telegram.org/api/errors.html delete mode 100644 data/core.telegram.org/api/file_reference.html delete mode 100644 data/core.telegram.org/api/files.html delete mode 100644 data/core.telegram.org/api/folders.html delete mode 100644 data/core.telegram.org/api/geochats.html delete mode 100644 data/core.telegram.org/api/import.html delete mode 100644 data/core.telegram.org/api/invoking.html delete mode 100644 data/core.telegram.org/api/live-location.html delete mode 100644 data/core.telegram.org/api/mentions.html delete mode 100644 data/core.telegram.org/api/min.html delete mode 100644 data/core.telegram.org/api/obtaining_api_id.html delete mode 100644 data/core.telegram.org/api/offsets.html delete mode 100644 data/core.telegram.org/api/optimisation.html delete mode 100644 data/core.telegram.org/api/passport.html delete mode 100644 data/core.telegram.org/api/pattern.html delete mode 100644 data/core.telegram.org/api/payments.html delete mode 100644 data/core.telegram.org/api/pfs.html delete mode 100644 data/core.telegram.org/api/pin.html delete mode 100644 data/core.telegram.org/api/poll.html delete mode 100644 data/core.telegram.org/api/push-updates.html delete mode 100644 data/core.telegram.org/api/qr-login.html delete mode 100644 data/core.telegram.org/api/recent-actions.html delete mode 100644 data/core.telegram.org/api/rights.html delete mode 100644 data/core.telegram.org/api/scheduled-messages.html delete mode 100644 data/core.telegram.org/api/search.html delete mode 100644 data/core.telegram.org/api/sponsored-messages.html delete mode 100644 data/core.telegram.org/api/srp.html delete mode 100644 data/core.telegram.org/api/stats.html delete mode 100644 data/core.telegram.org/api/terms.html delete mode 100644 data/core.telegram.org/api/threads.html delete mode 100644 data/core.telegram.org/api/top-rating.html delete mode 100644 data/core.telegram.org/api/updates.html delete mode 100644 data/core.telegram.org/api/url-authorization.html delete mode 100644 data/core.telegram.org/api/web-events.html delete mode 100644 data/core.telegram.org/apple_privacy.html delete mode 100644 data/core.telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html delete mode 100644 data/core.telegram.org/bots.html delete mode 100644 data/core.telegram.org/bots/2-0-intro.html delete mode 100644 data/core.telegram.org/bots/api-changelog.html delete mode 100644 data/core.telegram.org/bots/api.html delete mode 100644 data/core.telegram.org/bots/faq.html delete mode 100644 data/core.telegram.org/bots/games.html delete mode 100644 data/core.telegram.org/bots/inline.html delete mode 100644 data/core.telegram.org/bots/samples.html delete mode 100644 data/core.telegram.org/bots/samples/hellobot.html delete mode 100644 data/core.telegram.org/bots/self-signed.html delete mode 100644 data/core.telegram.org/bots/webhooks.html delete mode 100644 data/core.telegram.org/cdn.html delete mode 100644 data/core.telegram.org/cdn/faq_ir.html delete mode 100644 data/core.telegram.org/cdn/faq_ir/durov.html delete mode 100644 data/core.telegram.org/constructor/account.authorizationForm delete mode 100644 data/core.telegram.org/constructor/account.authorizations delete mode 100644 data/core.telegram.org/constructor/account.autoDownloadSettings delete mode 100644 data/core.telegram.org/constructor/account.chatThemes delete mode 100644 data/core.telegram.org/constructor/account.chatThemesNotModified delete mode 100644 data/core.telegram.org/constructor/account.contentSettings delete mode 100644 data/core.telegram.org/constructor/account.password delete mode 100644 data/core.telegram.org/constructor/account.passwordInputSettings delete mode 100644 data/core.telegram.org/constructor/account.passwordSettings delete mode 100644 data/core.telegram.org/constructor/account.privacyRules delete mode 100644 data/core.telegram.org/constructor/account.resetPasswordFailedWait delete mode 100644 data/core.telegram.org/constructor/account.resetPasswordOk delete mode 100644 data/core.telegram.org/constructor/account.resetPasswordRequestedWait delete mode 100644 data/core.telegram.org/constructor/account.sentChangePhoneCode delete mode 100644 data/core.telegram.org/constructor/account.takeout delete mode 100644 data/core.telegram.org/constructor/account.themes delete mode 100644 data/core.telegram.org/constructor/account.themesNotModified delete mode 100644 data/core.telegram.org/constructor/account.tmpPassword delete mode 100644 data/core.telegram.org/constructor/account.wallPapers delete mode 100644 data/core.telegram.org/constructor/account.wallPapersNotModified delete mode 100644 data/core.telegram.org/constructor/account.webAuthorizations delete mode 100644 data/core.telegram.org/constructor/accountDaysTTL.html delete mode 100644 data/core.telegram.org/constructor/auth.authorizationSignUpRequired delete mode 100644 data/core.telegram.org/constructor/auth.codeTypeCall delete mode 100644 data/core.telegram.org/constructor/auth.codeTypeFlashCall delete mode 100644 data/core.telegram.org/constructor/auth.codeTypeSms delete mode 100644 data/core.telegram.org/constructor/auth.exportedAuthorization delete mode 100644 data/core.telegram.org/constructor/auth.loginToken delete mode 100644 data/core.telegram.org/constructor/auth.loginTokenMigrateTo delete mode 100644 data/core.telegram.org/constructor/auth.passwordRecovery delete mode 100644 data/core.telegram.org/constructor/auth.sentAppCode delete mode 100644 data/core.telegram.org/constructor/auth.sentCode delete mode 100644 data/core.telegram.org/constructor/auth.sentCodeTypeApp delete mode 100644 data/core.telegram.org/constructor/auth.sentCodeTypeFlashCall delete mode 100644 data/core.telegram.org/constructor/auth.sentCodeTypeSms delete mode 100644 data/core.telegram.org/constructor/authorization.html delete mode 100644 data/core.telegram.org/constructor/autoDownloadSettings.html delete mode 100644 data/core.telegram.org/constructor/bankCardOpenUrl.html delete mode 100644 data/core.telegram.org/constructor/baseThemeArctic.html delete mode 100644 data/core.telegram.org/constructor/baseThemeClassic.html delete mode 100644 data/core.telegram.org/constructor/baseThemeDay.html delete mode 100644 data/core.telegram.org/constructor/baseThemeNight.html delete mode 100644 data/core.telegram.org/constructor/baseThemeTinted.html delete mode 100644 data/core.telegram.org/constructor/boolFalse.html delete mode 100644 data/core.telegram.org/constructor/boolTrue.html delete mode 100644 data/core.telegram.org/constructor/botCommand.html delete mode 100644 data/core.telegram.org/constructor/botCommandScopeChatAdmins.html delete mode 100644 data/core.telegram.org/constructor/botCommandScopeChats.html delete mode 100644 data/core.telegram.org/constructor/botCommandScopeDefault.html delete mode 100644 data/core.telegram.org/constructor/botCommandScopePeer.html delete mode 100644 data/core.telegram.org/constructor/botCommandScopePeerAdmins.html delete mode 100644 data/core.telegram.org/constructor/botCommandScopePeerUser.html delete mode 100644 data/core.telegram.org/constructor/botCommandScopeUsers.html delete mode 100644 data/core.telegram.org/constructor/botInfo.html delete mode 100644 data/core.telegram.org/constructor/botInlineMediaResult.html delete mode 100644 data/core.telegram.org/constructor/botInlineMessageMediaAuto.html delete mode 100644 data/core.telegram.org/constructor/botInlineMessageMediaContact.html delete mode 100644 data/core.telegram.org/constructor/botInlineMessageMediaGeo.html delete mode 100644 data/core.telegram.org/constructor/botInlineMessageMediaInvoice.html delete mode 100644 data/core.telegram.org/constructor/botInlineMessageMediaVenue.html delete mode 100644 data/core.telegram.org/constructor/botInlineMessageText.html delete mode 100644 data/core.telegram.org/constructor/botInlineResult.html delete mode 100644 data/core.telegram.org/constructor/cdnConfig.html delete mode 100644 data/core.telegram.org/constructor/cdnPublicKey.html delete mode 100644 data/core.telegram.org/constructor/channel.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEvent.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeAbout.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeHistoryTTL.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangePhoto.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeTitle.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionDefaultBannedRights.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionDeleteMessage.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionDiscardGroupCall.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionEditMessage.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteDelete.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteEdit.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteRevoke.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantInvite.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantLeave.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantMute.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantToggleAdmin.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantToggleBan.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantUnmute.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionStartGroupCall.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionStopPoll.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionToggleInvites.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionTogglePreHistoryHidden.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionToggleSignatures.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionToggleSlowMode.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionUpdatePinned.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventsFilter.html delete mode 100644 data/core.telegram.org/constructor/channelForbidden.html delete mode 100644 data/core.telegram.org/constructor/channelFull.html delete mode 100644 data/core.telegram.org/constructor/channelLocation.html delete mode 100644 data/core.telegram.org/constructor/channelLocationEmpty.html delete mode 100644 data/core.telegram.org/constructor/channelMessagesFilter.html delete mode 100644 data/core.telegram.org/constructor/channelMessagesFilterEmpty.html delete mode 100644 data/core.telegram.org/constructor/channelParticipant.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantAdmin.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantBanned.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantCreator.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantLeft.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantSelf.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantsAdmins.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantsBanned.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantsBots.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantsContacts.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantsKicked.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantsMentions.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantsRecent.html delete mode 100644 data/core.telegram.org/constructor/channelParticipantsSearch.html delete mode 100644 data/core.telegram.org/constructor/channels.adminLogResults delete mode 100644 data/core.telegram.org/constructor/channels.channelParticipants delete mode 100644 data/core.telegram.org/constructor/channels.channelParticipantsNotModified delete mode 100644 data/core.telegram.org/constructor/chat.html delete mode 100644 data/core.telegram.org/constructor/chatAdminRights.html delete mode 100644 data/core.telegram.org/constructor/chatAdminWithInvites.html delete mode 100644 data/core.telegram.org/constructor/chatBannedRights.html delete mode 100644 data/core.telegram.org/constructor/chatEmpty.html delete mode 100644 data/core.telegram.org/constructor/chatForbidden.html delete mode 100644 data/core.telegram.org/constructor/chatFull.html delete mode 100644 data/core.telegram.org/constructor/chatInvite.html delete mode 100644 data/core.telegram.org/constructor/chatInviteAlready.html delete mode 100644 data/core.telegram.org/constructor/chatInviteExported.html delete mode 100644 data/core.telegram.org/constructor/chatInviteImporter.html delete mode 100644 data/core.telegram.org/constructor/chatInvitePeek.html delete mode 100644 data/core.telegram.org/constructor/chatOnlines.html delete mode 100644 data/core.telegram.org/constructor/chatParticipantAdmin.html delete mode 100644 data/core.telegram.org/constructor/chatParticipantCreator.html delete mode 100644 data/core.telegram.org/constructor/chatParticipants.html delete mode 100644 data/core.telegram.org/constructor/chatParticipantsForbidden.html delete mode 100644 data/core.telegram.org/constructor/chatPhoto.html delete mode 100644 data/core.telegram.org/constructor/chatPhotoEmpty.html delete mode 100644 data/core.telegram.org/constructor/chatTheme.html delete mode 100644 data/core.telegram.org/constructor/codeSettings.html delete mode 100644 data/core.telegram.org/constructor/config.html delete mode 100644 data/core.telegram.org/constructor/contact.html delete mode 100644 data/core.telegram.org/constructor/contactStatus.html delete mode 100644 data/core.telegram.org/constructor/contacts.blocked delete mode 100644 data/core.telegram.org/constructor/contacts.blockedSlice delete mode 100644 data/core.telegram.org/constructor/contacts.contacts delete mode 100644 data/core.telegram.org/constructor/contacts.contactsNotModified delete mode 100644 data/core.telegram.org/constructor/contacts.found delete mode 100644 data/core.telegram.org/constructor/contacts.resolvedPeer delete mode 100644 data/core.telegram.org/constructor/contacts.topPeers delete mode 100644 data/core.telegram.org/constructor/contacts.topPeersDisabled delete mode 100644 data/core.telegram.org/constructor/contacts.topPeersNotModified delete mode 100644 data/core.telegram.org/constructor/dataJSON.html delete mode 100644 data/core.telegram.org/constructor/dcOption.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessage.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionAbortKey.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionAcceptKey.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionCommitKey.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionDeleteMessages.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionFlushHistory.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionNoop.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionNotifyLayer.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionReadMessages.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionRequestKey.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionResend.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionScreenshotMessages.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionSetMessageTTL.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageActionTyping.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageLayer.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaAudio.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaContact.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaDocument.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaEmpty.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaExternalDocument.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaGeoPoint.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaPhoto.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaVenue.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaVideo.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageMediaWebPage.html delete mode 100644 data/core.telegram.org/constructor/decryptedMessageService.html delete mode 100644 data/core.telegram.org/constructor/dialog.html delete mode 100644 data/core.telegram.org/constructor/dialogFilter.html delete mode 100644 data/core.telegram.org/constructor/dialogFilterSuggested.html delete mode 100644 data/core.telegram.org/constructor/dialogFolder.html delete mode 100644 data/core.telegram.org/constructor/dialogPeer.html delete mode 100644 data/core.telegram.org/constructor/dialogPeerFolder.html delete mode 100644 data/core.telegram.org/constructor/disabledFeature.html delete mode 100644 data/core.telegram.org/constructor/document.html delete mode 100644 data/core.telegram.org/constructor/documentAttributeAnimated.html delete mode 100644 data/core.telegram.org/constructor/documentAttributeAudio.html delete mode 100644 data/core.telegram.org/constructor/documentAttributeFilename.html delete mode 100644 data/core.telegram.org/constructor/documentAttributeHasStickers.html delete mode 100644 data/core.telegram.org/constructor/documentAttributeImageSize.html delete mode 100644 data/core.telegram.org/constructor/documentAttributeSticker.html delete mode 100644 data/core.telegram.org/constructor/documentAttributeVideo.html delete mode 100644 data/core.telegram.org/constructor/documentEmpty.html delete mode 100644 data/core.telegram.org/constructor/draftMessage.html delete mode 100644 data/core.telegram.org/constructor/draftMessageEmpty.html delete mode 100644 data/core.telegram.org/constructor/emojiKeyword.html delete mode 100644 data/core.telegram.org/constructor/emojiKeywordDeleted.html delete mode 100644 data/core.telegram.org/constructor/emojiKeywordsDifference.html delete mode 100644 data/core.telegram.org/constructor/emojiLanguage.html delete mode 100644 data/core.telegram.org/constructor/emojiURL.html delete mode 100644 data/core.telegram.org/constructor/encryptedChat.html delete mode 100644 data/core.telegram.org/constructor/encryptedChatDiscarded.html delete mode 100644 data/core.telegram.org/constructor/encryptedChatEmpty.html delete mode 100644 data/core.telegram.org/constructor/encryptedChatRequested.html delete mode 100644 data/core.telegram.org/constructor/encryptedMessage.html delete mode 100644 data/core.telegram.org/constructor/encryptedMessageService.html delete mode 100644 data/core.telegram.org/constructor/error.html delete mode 100644 data/core.telegram.org/constructor/exportedMessageLink.html delete mode 100644 data/core.telegram.org/constructor/fileHash.html delete mode 100644 data/core.telegram.org/constructor/fileLocation.html delete mode 100644 data/core.telegram.org/constructor/fileLocationUnavailable.html delete mode 100644 data/core.telegram.org/constructor/folder.html delete mode 100644 data/core.telegram.org/constructor/folderPeer.html delete mode 100644 data/core.telegram.org/constructor/game.html delete mode 100644 data/core.telegram.org/constructor/geoPoint.html delete mode 100644 data/core.telegram.org/constructor/geoPointEmpty.html delete mode 100644 data/core.telegram.org/constructor/globalPrivacySettings.html delete mode 100644 data/core.telegram.org/constructor/groupCall.html delete mode 100644 data/core.telegram.org/constructor/groupCallDiscarded.html delete mode 100644 data/core.telegram.org/constructor/groupCallParticipant.html delete mode 100644 data/core.telegram.org/constructor/groupCallParticipantVideo.html delete mode 100644 data/core.telegram.org/constructor/groupCallParticipantVideoSourceGroup.html delete mode 100644 data/core.telegram.org/constructor/help.appUpdate delete mode 100644 data/core.telegram.org/constructor/help.countriesList delete mode 100644 data/core.telegram.org/constructor/help.countriesListNotModified delete mode 100644 data/core.telegram.org/constructor/help.country delete mode 100644 data/core.telegram.org/constructor/help.countryCode delete mode 100644 data/core.telegram.org/constructor/help.deepLinkInfo delete mode 100644 data/core.telegram.org/constructor/help.deepLinkInfoEmpty delete mode 100644 data/core.telegram.org/constructor/help.inviteText delete mode 100644 data/core.telegram.org/constructor/help.noAppUpdate delete mode 100644 data/core.telegram.org/constructor/help.passportConfig delete mode 100644 data/core.telegram.org/constructor/help.passportConfigNotModified delete mode 100644 data/core.telegram.org/constructor/help.promoData delete mode 100644 data/core.telegram.org/constructor/help.promoDataEmpty delete mode 100644 data/core.telegram.org/constructor/help.recentMeUrls delete mode 100644 data/core.telegram.org/constructor/help.support delete mode 100644 data/core.telegram.org/constructor/help.supportName delete mode 100644 data/core.telegram.org/constructor/help.termsOfService delete mode 100644 data/core.telegram.org/constructor/help.termsOfServiceUpdate delete mode 100644 data/core.telegram.org/constructor/help.termsOfServiceUpdateEmpty delete mode 100644 data/core.telegram.org/constructor/help.userInfo delete mode 100644 data/core.telegram.org/constructor/help.userInfoEmpty delete mode 100644 data/core.telegram.org/constructor/highScore.html delete mode 100644 data/core.telegram.org/constructor/importedContact.html delete mode 100644 data/core.telegram.org/constructor/inlineBotSwitchPM.html delete mode 100644 data/core.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html delete mode 100644 data/core.telegram.org/constructor/inlineQueryPeerTypeChat.html delete mode 100644 data/core.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html delete mode 100644 data/core.telegram.org/constructor/inlineQueryPeerTypeSameBotPM.html delete mode 100644 data/core.telegram.org/constructor/inputAppEvent.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageGame.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageID.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageID64.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageMediaAuto.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageMediaContact.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageMediaGeo.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageMediaInvoice.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageMediaVenue.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageText.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineResult.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineResultDocument.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineResultGame.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineResultPhoto.html delete mode 100644 data/core.telegram.org/constructor/inputChannel.html delete mode 100644 data/core.telegram.org/constructor/inputChannelEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputChannelFromMessage.html delete mode 100644 data/core.telegram.org/constructor/inputChatPhotoEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputChatUploadedPhoto.html delete mode 100644 data/core.telegram.org/constructor/inputCheckPasswordEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputCheckPasswordSRP.html delete mode 100644 data/core.telegram.org/constructor/inputClientProxy.html delete mode 100644 data/core.telegram.org/constructor/inputDialogPeer.html delete mode 100644 data/core.telegram.org/constructor/inputDialogPeerFolder.html delete mode 100644 data/core.telegram.org/constructor/inputDocument.html delete mode 100644 data/core.telegram.org/constructor/inputDocumentEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputDocumentFileLocation.html delete mode 100644 data/core.telegram.org/constructor/inputEncryptedChat.html delete mode 100644 data/core.telegram.org/constructor/inputEncryptedFile.html delete mode 100644 data/core.telegram.org/constructor/inputEncryptedFileBigUploaded.html delete mode 100644 data/core.telegram.org/constructor/inputEncryptedFileEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputEncryptedFileLocation.html delete mode 100644 data/core.telegram.org/constructor/inputEncryptedFileUploaded.html delete mode 100644 data/core.telegram.org/constructor/inputFile.html delete mode 100644 data/core.telegram.org/constructor/inputFileBig.html delete mode 100644 data/core.telegram.org/constructor/inputFileLocation.html delete mode 100644 data/core.telegram.org/constructor/inputFolderPeer.html delete mode 100644 data/core.telegram.org/constructor/inputGameID.html delete mode 100644 data/core.telegram.org/constructor/inputGameShortName.html delete mode 100644 data/core.telegram.org/constructor/inputGeoPoint.html delete mode 100644 data/core.telegram.org/constructor/inputGeoPointEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputGroupCall.html delete mode 100644 data/core.telegram.org/constructor/inputGroupCallStream.html delete mode 100644 data/core.telegram.org/constructor/inputKeyboardButtonUrlAuth.html delete mode 100644 data/core.telegram.org/constructor/inputMediaContact.html delete mode 100644 data/core.telegram.org/constructor/inputMediaDice.html delete mode 100644 data/core.telegram.org/constructor/inputMediaDocument.html delete mode 100644 data/core.telegram.org/constructor/inputMediaDocumentExternal.html delete mode 100644 data/core.telegram.org/constructor/inputMediaEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputMediaGame.html delete mode 100644 data/core.telegram.org/constructor/inputMediaGeoLive.html delete mode 100644 data/core.telegram.org/constructor/inputMediaGeoPoint.html delete mode 100644 data/core.telegram.org/constructor/inputMediaInvoice.html delete mode 100644 data/core.telegram.org/constructor/inputMediaPhoto.html delete mode 100644 data/core.telegram.org/constructor/inputMediaPoll.html delete mode 100644 data/core.telegram.org/constructor/inputMediaUploadedDocument.html delete mode 100644 data/core.telegram.org/constructor/inputMediaUploadedPhoto.html delete mode 100644 data/core.telegram.org/constructor/inputMediaUploadedThumbDocument.html delete mode 100644 data/core.telegram.org/constructor/inputMediaVenue.html delete mode 100644 data/core.telegram.org/constructor/inputMessageCallbackQuery.html delete mode 100644 data/core.telegram.org/constructor/inputMessageEntityMentionName.html delete mode 100644 data/core.telegram.org/constructor/inputMessageID.html delete mode 100644 data/core.telegram.org/constructor/inputMessagePinned.html delete mode 100644 data/core.telegram.org/constructor/inputMessageReplyTo.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterChatPhotos.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterContacts.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterDocument.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterGeo.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterGif.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterMusic.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterMyMentions.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterPhoneCalls.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterPhotoVideo.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterPhotos.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterRoundVideo.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterRoundVoice.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterUrl.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterVideo.html delete mode 100644 data/core.telegram.org/constructor/inputNotifyBroadcasts.html delete mode 100644 data/core.telegram.org/constructor/inputNotifyChats.html delete mode 100644 data/core.telegram.org/constructor/inputNotifyPeer.html delete mode 100644 data/core.telegram.org/constructor/inputNotifyUsers.html delete mode 100644 data/core.telegram.org/constructor/inputPaymentCredentials.html delete mode 100644 data/core.telegram.org/constructor/inputPaymentCredentialsApplePay.html delete mode 100644 data/core.telegram.org/constructor/inputPaymentCredentialsGooglePay.html delete mode 100644 data/core.telegram.org/constructor/inputPaymentCredentialsSaved.html delete mode 100644 data/core.telegram.org/constructor/inputPeerChannelFromMessage.html delete mode 100644 data/core.telegram.org/constructor/inputPeerChat.html delete mode 100644 data/core.telegram.org/constructor/inputPeerEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputPeerNotifySettings.html delete mode 100644 data/core.telegram.org/constructor/inputPeerPhotoFileLocation.html delete mode 100644 data/core.telegram.org/constructor/inputPeerSelf.html delete mode 100644 data/core.telegram.org/constructor/inputPeerUser.html delete mode 100644 data/core.telegram.org/constructor/inputPeerUserFromMessage.html delete mode 100644 data/core.telegram.org/constructor/inputPhoneCall.html delete mode 100644 data/core.telegram.org/constructor/inputPhoneContact.html delete mode 100644 data/core.telegram.org/constructor/inputPhoto.html delete mode 100644 data/core.telegram.org/constructor/inputPhotoEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputPhotoFileLocation.html delete mode 100644 data/core.telegram.org/constructor/inputPhotoLegacyFileLocation.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyAddedByPhone.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyChatInvite.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyForwards.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyPhoneCall.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyPhoneNumber.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyPhoneP2P.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyProfilePhoto.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyValueAllowAll.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyValueAllowChatParticipants.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyValueAllowContacts.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyValueAllowUsers.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyValueDisallowAll.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyValueDisallowChatParticipants.html delete mode 100644 data/core.telegram.org/constructor/inputPrivacyValueDisallowUsers.html delete mode 100644 data/core.telegram.org/constructor/inputReportReasonChildAbuse.html delete mode 100644 data/core.telegram.org/constructor/inputReportReasonCopyright.html delete mode 100644 data/core.telegram.org/constructor/inputReportReasonFake.html delete mode 100644 data/core.telegram.org/constructor/inputReportReasonGeoIrrelevant.html delete mode 100644 data/core.telegram.org/constructor/inputReportReasonOther.html delete mode 100644 data/core.telegram.org/constructor/inputReportReasonPornography.html delete mode 100644 data/core.telegram.org/constructor/inputReportReasonSpam.html delete mode 100644 data/core.telegram.org/constructor/inputReportReasonViolence.html delete mode 100644 data/core.telegram.org/constructor/inputSecureFileLocation.html delete mode 100644 data/core.telegram.org/constructor/inputSecureFileUploaded.html delete mode 100644 data/core.telegram.org/constructor/inputSecureValue.html delete mode 100644 data/core.telegram.org/constructor/inputSingleMedia.html delete mode 100644 data/core.telegram.org/constructor/inputStickerSetAnimatedEmojiAnimations.html delete mode 100644 data/core.telegram.org/constructor/inputStickerSetEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputStickerSetItem.html delete mode 100644 data/core.telegram.org/constructor/inputStickerSetShortName.html delete mode 100644 data/core.telegram.org/constructor/inputStickerSetThumb.html delete mode 100644 data/core.telegram.org/constructor/inputStickeredMediaDocument.html delete mode 100644 data/core.telegram.org/constructor/inputStickeredMediaPhoto.html delete mode 100644 data/core.telegram.org/constructor/inputTakeoutFileLocation.html delete mode 100644 data/core.telegram.org/constructor/inputTheme.html delete mode 100644 data/core.telegram.org/constructor/inputThemeSettings.html delete mode 100644 data/core.telegram.org/constructor/inputThemeSlug.html delete mode 100644 data/core.telegram.org/constructor/inputUser.html delete mode 100644 data/core.telegram.org/constructor/inputUserEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputUserFromMessage.html delete mode 100644 data/core.telegram.org/constructor/inputUserSelf.html delete mode 100644 data/core.telegram.org/constructor/inputWallPaper.html delete mode 100644 data/core.telegram.org/constructor/inputWallPaperNoFile.html delete mode 100644 data/core.telegram.org/constructor/inputWallPaperSlug.html delete mode 100644 data/core.telegram.org/constructor/inputWebDocument.html delete mode 100644 data/core.telegram.org/constructor/inputWebFileGeoPointLocation.html delete mode 100644 data/core.telegram.org/constructor/inputWebFileLocation.html delete mode 100644 data/core.telegram.org/constructor/invoice.html delete mode 100644 data/core.telegram.org/constructor/jsonArray.html delete mode 100644 data/core.telegram.org/constructor/jsonBool.html delete mode 100644 data/core.telegram.org/constructor/jsonNull.html delete mode 100644 data/core.telegram.org/constructor/jsonNumber.html delete mode 100644 data/core.telegram.org/constructor/jsonObject.html delete mode 100644 data/core.telegram.org/constructor/jsonObjectValue.html delete mode 100644 data/core.telegram.org/constructor/jsonString.html delete mode 100644 data/core.telegram.org/constructor/keyboardButton.html delete mode 100644 data/core.telegram.org/constructor/keyboardButtonBuy.html delete mode 100644 data/core.telegram.org/constructor/keyboardButtonCallback.html delete mode 100644 data/core.telegram.org/constructor/keyboardButtonGame.html delete mode 100644 data/core.telegram.org/constructor/keyboardButtonRequestGeoLocation.html delete mode 100644 data/core.telegram.org/constructor/keyboardButtonRequestPhone.html delete mode 100644 data/core.telegram.org/constructor/keyboardButtonRequestPoll.html delete mode 100644 data/core.telegram.org/constructor/keyboardButtonRow.html delete mode 100644 data/core.telegram.org/constructor/keyboardButtonSwitchInline.html delete mode 100644 data/core.telegram.org/constructor/keyboardButtonUrl.html delete mode 100644 data/core.telegram.org/constructor/keyboardButtonUrlAuth.html delete mode 100644 data/core.telegram.org/constructor/labeledPrice.html delete mode 100644 data/core.telegram.org/constructor/langPackDifference.html delete mode 100644 data/core.telegram.org/constructor/langPackLanguage.html delete mode 100644 data/core.telegram.org/constructor/langPackString.html delete mode 100644 data/core.telegram.org/constructor/langPackStringDeleted.html delete mode 100644 data/core.telegram.org/constructor/langPackStringPluralized.html delete mode 100644 data/core.telegram.org/constructor/maskCoords.html delete mode 100644 data/core.telegram.org/constructor/message.html delete mode 100644 data/core.telegram.org/constructor/messageActionBotAllowed.html delete mode 100644 data/core.telegram.org/constructor/messageActionChannelMigrateFrom.html delete mode 100644 data/core.telegram.org/constructor/messageActionChatAddUser.html delete mode 100644 data/core.telegram.org/constructor/messageActionChatCreate.html delete mode 100644 data/core.telegram.org/constructor/messageActionChatDeleteUser.html delete mode 100644 data/core.telegram.org/constructor/messageActionChatEditPhoto.html delete mode 100644 data/core.telegram.org/constructor/messageActionChatEditTitle.html delete mode 100644 data/core.telegram.org/constructor/messageActionChatJoinedByLink.html delete mode 100644 data/core.telegram.org/constructor/messageActionChatMigrateTo.html delete mode 100644 data/core.telegram.org/constructor/messageActionContactSignUp.html delete mode 100644 data/core.telegram.org/constructor/messageActionCustomAction.html delete mode 100644 data/core.telegram.org/constructor/messageActionEmpty.html delete mode 100644 data/core.telegram.org/constructor/messageActionGameScore.html delete mode 100644 data/core.telegram.org/constructor/messageActionGroupCall.html delete mode 100644 data/core.telegram.org/constructor/messageActionGroupCallScheduled.html delete mode 100644 data/core.telegram.org/constructor/messageActionHistoryClear.html delete mode 100644 data/core.telegram.org/constructor/messageActionPaymentSent.html delete mode 100644 data/core.telegram.org/constructor/messageActionPaymentSentMe.html delete mode 100644 data/core.telegram.org/constructor/messageActionPhoneCall.html delete mode 100644 data/core.telegram.org/constructor/messageActionPinMessage.html delete mode 100644 data/core.telegram.org/constructor/messageActionSecureValuesSent.html delete mode 100644 data/core.telegram.org/constructor/messageActionSecureValuesSentMe.html delete mode 100644 data/core.telegram.org/constructor/messageActionSetChatTheme.html delete mode 100644 data/core.telegram.org/constructor/messageActionSetMessagesTTL.html delete mode 100644 data/core.telegram.org/constructor/messageEmpty.html delete mode 100644 data/core.telegram.org/constructor/messageEntityBankCard.html delete mode 100644 data/core.telegram.org/constructor/messageEntityBlockquote.html delete mode 100644 data/core.telegram.org/constructor/messageEntityBold.html delete mode 100644 data/core.telegram.org/constructor/messageEntityBotCommand.html delete mode 100644 data/core.telegram.org/constructor/messageEntityCashtag.html delete mode 100644 data/core.telegram.org/constructor/messageEntityCode.html delete mode 100644 data/core.telegram.org/constructor/messageEntityEmail.html delete mode 100644 data/core.telegram.org/constructor/messageEntityHashtag.html delete mode 100644 data/core.telegram.org/constructor/messageEntityItalic.html delete mode 100644 data/core.telegram.org/constructor/messageEntityMention.html delete mode 100644 data/core.telegram.org/constructor/messageEntityMentionName.html delete mode 100644 data/core.telegram.org/constructor/messageEntityPhone.html delete mode 100644 data/core.telegram.org/constructor/messageEntityPre.html delete mode 100644 data/core.telegram.org/constructor/messageEntityStrike.html delete mode 100644 data/core.telegram.org/constructor/messageEntityTextUrl.html delete mode 100644 data/core.telegram.org/constructor/messageEntityUnderline.html delete mode 100644 data/core.telegram.org/constructor/messageEntityUnknown.html delete mode 100644 data/core.telegram.org/constructor/messageEntityUrl.html delete mode 100644 data/core.telegram.org/constructor/messageFwdHeader.html delete mode 100644 data/core.telegram.org/constructor/messageInteractionCounters.html delete mode 100644 data/core.telegram.org/constructor/messageMediaAudio.html delete mode 100644 data/core.telegram.org/constructor/messageMediaDice.html delete mode 100644 data/core.telegram.org/constructor/messageMediaDocument.html delete mode 100644 data/core.telegram.org/constructor/messageMediaEmpty.html delete mode 100644 data/core.telegram.org/constructor/messageMediaGame.html delete mode 100644 data/core.telegram.org/constructor/messageMediaGeo.html delete mode 100644 data/core.telegram.org/constructor/messageMediaGeoLive.html delete mode 100644 data/core.telegram.org/constructor/messageMediaInvoice.html delete mode 100644 data/core.telegram.org/constructor/messageMediaPhoto.html delete mode 100644 data/core.telegram.org/constructor/messageMediaPoll.html delete mode 100644 data/core.telegram.org/constructor/messageMediaUnsupported.html delete mode 100644 data/core.telegram.org/constructor/messageMediaVenue.html delete mode 100644 data/core.telegram.org/constructor/messageMediaVideo.html delete mode 100644 data/core.telegram.org/constructor/messageMediaWebPage.html delete mode 100644 data/core.telegram.org/constructor/messageRange.html delete mode 100644 data/core.telegram.org/constructor/messageReplies.html delete mode 100644 data/core.telegram.org/constructor/messageReplyHeader.html delete mode 100644 data/core.telegram.org/constructor/messageService.html delete mode 100644 data/core.telegram.org/constructor/messageUserVote.html delete mode 100644 data/core.telegram.org/constructor/messageUserVoteInputOption.html delete mode 100644 data/core.telegram.org/constructor/messageUserVoteMultiple.html delete mode 100644 data/core.telegram.org/constructor/messageViews.html delete mode 100644 data/core.telegram.org/constructor/messages.affectedFoundMessages delete mode 100644 data/core.telegram.org/constructor/messages.affectedHistory delete mode 100644 data/core.telegram.org/constructor/messages.affectedMessages delete mode 100644 data/core.telegram.org/constructor/messages.allStickers delete mode 100644 data/core.telegram.org/constructor/messages.allStickersNotModified delete mode 100644 data/core.telegram.org/constructor/messages.archivedStickers delete mode 100644 data/core.telegram.org/constructor/messages.botResults delete mode 100644 data/core.telegram.org/constructor/messages.chatAdminsWithInvites delete mode 100644 data/core.telegram.org/constructor/messages.chatFull delete mode 100644 data/core.telegram.org/constructor/messages.chatInviteImporters delete mode 100644 data/core.telegram.org/constructor/messages.chats delete mode 100644 data/core.telegram.org/constructor/messages.chatsSlice delete mode 100644 data/core.telegram.org/constructor/messages.checkedHistoryImportPeer delete mode 100644 data/core.telegram.org/constructor/messages.dhConfig delete mode 100644 data/core.telegram.org/constructor/messages.dhConfigNotModified delete mode 100644 data/core.telegram.org/constructor/messages.dialogsNotModified delete mode 100644 data/core.telegram.org/constructor/messages.dialogsSlice delete mode 100644 data/core.telegram.org/constructor/messages.discussionMessage delete mode 100644 data/core.telegram.org/constructor/messages.exportedChatInvite delete mode 100644 data/core.telegram.org/constructor/messages.exportedChatInvites delete mode 100644 data/core.telegram.org/constructor/messages.favedStickers delete mode 100644 data/core.telegram.org/constructor/messages.favedStickersNotModified delete mode 100644 data/core.telegram.org/constructor/messages.featuredStickers delete mode 100644 data/core.telegram.org/constructor/messages.featuredStickersNotModified delete mode 100644 data/core.telegram.org/constructor/messages.foundStickerSets delete mode 100644 data/core.telegram.org/constructor/messages.foundStickerSetsNotModified delete mode 100644 data/core.telegram.org/constructor/messages.highScores delete mode 100644 data/core.telegram.org/constructor/messages.historyImport delete mode 100644 data/core.telegram.org/constructor/messages.historyImportParsed delete mode 100644 data/core.telegram.org/constructor/messages.inactiveChats delete mode 100644 data/core.telegram.org/constructor/messages.messageEditData delete mode 100644 data/core.telegram.org/constructor/messages.messageViews delete mode 100644 data/core.telegram.org/constructor/messages.messagesNotModified delete mode 100644 data/core.telegram.org/constructor/messages.messagesSlice delete mode 100644 data/core.telegram.org/constructor/messages.peerDialogs delete mode 100644 data/core.telegram.org/constructor/messages.recentStickers delete mode 100644 data/core.telegram.org/constructor/messages.recentStickersNotModified delete mode 100644 data/core.telegram.org/constructor/messages.savedGifs delete mode 100644 data/core.telegram.org/constructor/messages.savedGifsNotModified delete mode 100644 data/core.telegram.org/constructor/messages.searchCounter delete mode 100644 data/core.telegram.org/constructor/messages.sentEncryptedMessage delete mode 100644 data/core.telegram.org/constructor/messages.sentMessageLink delete mode 100644 data/core.telegram.org/constructor/messages.sponsoredMessages delete mode 100644 data/core.telegram.org/constructor/messages.statedMessageLink delete mode 100644 data/core.telegram.org/constructor/messages.statedMessagesLinks delete mode 100644 data/core.telegram.org/constructor/messages.stickerSet delete mode 100644 data/core.telegram.org/constructor/messages.stickerSetInstallResultArchive delete mode 100644 data/core.telegram.org/constructor/messages.stickerSetInstallResultSuccess delete mode 100644 data/core.telegram.org/constructor/messages.stickers delete mode 100644 data/core.telegram.org/constructor/messages.stickersNotModified delete mode 100644 data/core.telegram.org/constructor/messages.votesList delete mode 100644 data/core.telegram.org/constructor/nearestDc.html delete mode 100644 data/core.telegram.org/constructor/notifyBroadcasts.html delete mode 100644 data/core.telegram.org/constructor/notifyChats.html delete mode 100644 data/core.telegram.org/constructor/notifyUsers.html delete mode 100644 data/core.telegram.org/constructor/null.html delete mode 100644 data/core.telegram.org/constructor/page.html delete mode 100644 data/core.telegram.org/constructor/pageBlockAnchor.html delete mode 100644 data/core.telegram.org/constructor/pageBlockAudio.html delete mode 100644 data/core.telegram.org/constructor/pageBlockAuthorDate.html delete mode 100644 data/core.telegram.org/constructor/pageBlockBlockquote.html delete mode 100644 data/core.telegram.org/constructor/pageBlockChannel.html delete mode 100644 data/core.telegram.org/constructor/pageBlockCollage.html delete mode 100644 data/core.telegram.org/constructor/pageBlockCover.html delete mode 100644 data/core.telegram.org/constructor/pageBlockDetails.html delete mode 100644 data/core.telegram.org/constructor/pageBlockDivider.html delete mode 100644 data/core.telegram.org/constructor/pageBlockEmbed.html delete mode 100644 data/core.telegram.org/constructor/pageBlockEmbedPost.html delete mode 100644 data/core.telegram.org/constructor/pageBlockFooter.html delete mode 100644 data/core.telegram.org/constructor/pageBlockHeader.html delete mode 100644 data/core.telegram.org/constructor/pageBlockKicker.html delete mode 100644 data/core.telegram.org/constructor/pageBlockList.html delete mode 100644 data/core.telegram.org/constructor/pageBlockMap.html delete mode 100644 data/core.telegram.org/constructor/pageBlockOrderedList.html delete mode 100644 data/core.telegram.org/constructor/pageBlockParagraph.html delete mode 100644 data/core.telegram.org/constructor/pageBlockPhoto.html delete mode 100644 data/core.telegram.org/constructor/pageBlockPreformatted.html delete mode 100644 data/core.telegram.org/constructor/pageBlockPullquote.html delete mode 100644 data/core.telegram.org/constructor/pageBlockRelatedArticles.html delete mode 100644 data/core.telegram.org/constructor/pageBlockSlideshow.html delete mode 100644 data/core.telegram.org/constructor/pageBlockSubheader.html delete mode 100644 data/core.telegram.org/constructor/pageBlockSubtitle.html delete mode 100644 data/core.telegram.org/constructor/pageBlockTitle.html delete mode 100644 data/core.telegram.org/constructor/pageBlockUnsupported.html delete mode 100644 data/core.telegram.org/constructor/pageBlockVideo.html delete mode 100644 data/core.telegram.org/constructor/pageCaption.html delete mode 100644 data/core.telegram.org/constructor/pageListItemBlocks.html delete mode 100644 data/core.telegram.org/constructor/pageListItemText.html delete mode 100644 data/core.telegram.org/constructor/pageListOrderedItemText.html delete mode 100644 data/core.telegram.org/constructor/pageRelatedArticle.html delete mode 100644 data/core.telegram.org/constructor/pageTableCell.html delete mode 100644 data/core.telegram.org/constructor/pageTableRow.html delete mode 100644 data/core.telegram.org/constructor/passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow.html delete mode 100644 data/core.telegram.org/constructor/passwordKdfAlgoUnknown.html delete mode 100644 data/core.telegram.org/constructor/paymentCharge.html delete mode 100644 data/core.telegram.org/constructor/paymentRequestedInfo.html delete mode 100644 data/core.telegram.org/constructor/paymentSavedCredentialsCard.html delete mode 100644 data/core.telegram.org/constructor/payments.ValidatedRequestedInfo delete mode 100644 data/core.telegram.org/constructor/payments.bankCardData delete mode 100644 data/core.telegram.org/constructor/payments.paymentForm delete mode 100644 data/core.telegram.org/constructor/payments.paymentReceipt delete mode 100644 data/core.telegram.org/constructor/payments.paymentResult delete mode 100644 data/core.telegram.org/constructor/payments.paymentVerificationNeeded delete mode 100644 data/core.telegram.org/constructor/payments.savedInfo delete mode 100644 data/core.telegram.org/constructor/peerBlocked.html delete mode 100644 data/core.telegram.org/constructor/peerChat.html delete mode 100644 data/core.telegram.org/constructor/peerLocated.html delete mode 100644 data/core.telegram.org/constructor/peerNotifySettings.html delete mode 100644 data/core.telegram.org/constructor/peerSelfLocated.html delete mode 100644 data/core.telegram.org/constructor/peerSettings.html delete mode 100644 data/core.telegram.org/constructor/peerUser.html delete mode 100644 data/core.telegram.org/constructor/phone.exportedGroupCallInvite delete mode 100644 data/core.telegram.org/constructor/phone.groupCall delete mode 100644 data/core.telegram.org/constructor/phone.groupParticipants delete mode 100644 data/core.telegram.org/constructor/phone.joinAsPeers delete mode 100644 data/core.telegram.org/constructor/phone.phoneCall delete mode 100644 data/core.telegram.org/constructor/phoneCall.html delete mode 100644 data/core.telegram.org/constructor/phoneCallAccepted.html delete mode 100644 data/core.telegram.org/constructor/phoneCallDiscardReasonBusy.html delete mode 100644 data/core.telegram.org/constructor/phoneCallDiscardReasonDisconnect.html delete mode 100644 data/core.telegram.org/constructor/phoneCallDiscardReasonHangup.html delete mode 100644 data/core.telegram.org/constructor/phoneCallDiscardReasonMissed.html delete mode 100644 data/core.telegram.org/constructor/phoneCallDiscarded.html delete mode 100644 data/core.telegram.org/constructor/phoneCallProtocol.html delete mode 100644 data/core.telegram.org/constructor/phoneCallRequested.html delete mode 100644 data/core.telegram.org/constructor/phoneCallWaiting.html delete mode 100644 data/core.telegram.org/constructor/phoneConnection.html delete mode 100644 data/core.telegram.org/constructor/phoneConnectionWebrtc.html delete mode 100644 data/core.telegram.org/constructor/photo.html delete mode 100644 data/core.telegram.org/constructor/photoCachedSize.html delete mode 100644 data/core.telegram.org/constructor/photoEmpty.html delete mode 100644 data/core.telegram.org/constructor/photoPathSize.html delete mode 100644 data/core.telegram.org/constructor/photoSize.html delete mode 100644 data/core.telegram.org/constructor/photoSizeEmpty.html delete mode 100644 data/core.telegram.org/constructor/photoSizeProgressive.html delete mode 100644 data/core.telegram.org/constructor/photoStrippedSize.html delete mode 100644 data/core.telegram.org/constructor/photos.photo delete mode 100644 data/core.telegram.org/constructor/photos.photos delete mode 100644 data/core.telegram.org/constructor/photos.photosSlice delete mode 100644 data/core.telegram.org/constructor/poll.html delete mode 100644 data/core.telegram.org/constructor/pollAnswer.html delete mode 100644 data/core.telegram.org/constructor/pollAnswerVoters.html delete mode 100644 data/core.telegram.org/constructor/pollResults.html delete mode 100644 data/core.telegram.org/constructor/postAddress.html delete mode 100644 data/core.telegram.org/constructor/privacyKeyAddedByPhone.html delete mode 100644 data/core.telegram.org/constructor/privacyKeyChatInvite.html delete mode 100644 data/core.telegram.org/constructor/privacyKeyForwards.html delete mode 100644 data/core.telegram.org/constructor/privacyKeyPhoneCall.html delete mode 100644 data/core.telegram.org/constructor/privacyKeyPhoneNumber.html delete mode 100644 data/core.telegram.org/constructor/privacyKeyPhoneP2P.html delete mode 100644 data/core.telegram.org/constructor/privacyKeyProfilePhoto.html delete mode 100644 data/core.telegram.org/constructor/privacyKeyStatusTimestamp.html delete mode 100644 data/core.telegram.org/constructor/privacyValueAllowAll.html delete mode 100644 data/core.telegram.org/constructor/privacyValueAllowChatParticipants.html delete mode 100644 data/core.telegram.org/constructor/privacyValueAllowContacts.html delete mode 100644 data/core.telegram.org/constructor/privacyValueAllowUsers.html delete mode 100644 data/core.telegram.org/constructor/privacyValueDisallowAll.html delete mode 100644 data/core.telegram.org/constructor/privacyValueDisallowContacts.html delete mode 100644 data/core.telegram.org/constructor/privacyValueDisallowUsers.html delete mode 100644 data/core.telegram.org/constructor/receivedNotifyMessage.html delete mode 100644 data/core.telegram.org/constructor/recentMeUrlChat.html delete mode 100644 data/core.telegram.org/constructor/recentMeUrlChatInvite.html delete mode 100644 data/core.telegram.org/constructor/recentMeUrlStickerSet.html delete mode 100644 data/core.telegram.org/constructor/recentMeUrlUnknown.html delete mode 100644 data/core.telegram.org/constructor/recentMeUrlUser.html delete mode 100644 data/core.telegram.org/constructor/replyInlineMarkup.html delete mode 100644 data/core.telegram.org/constructor/replyKeyboardForceReply.html delete mode 100644 data/core.telegram.org/constructor/replyKeyboardHide.html delete mode 100644 data/core.telegram.org/constructor/replyKeyboardMarkup.html delete mode 100644 data/core.telegram.org/constructor/restrictionReason.html delete mode 100644 data/core.telegram.org/constructor/savedPhoneContact.html delete mode 100644 data/core.telegram.org/constructor/secureCredentialsEncrypted.html delete mode 100644 data/core.telegram.org/constructor/secureData.html delete mode 100644 data/core.telegram.org/constructor/secureFile.html delete mode 100644 data/core.telegram.org/constructor/secureFileEmpty.html delete mode 100644 data/core.telegram.org/constructor/securePasswordKdfAlgoPBKDF2HMACSHA512iter100000.html delete mode 100644 data/core.telegram.org/constructor/securePasswordKdfAlgoSHA512.html delete mode 100644 data/core.telegram.org/constructor/securePasswordKdfAlgoUnknown.html delete mode 100644 data/core.telegram.org/constructor/securePlainEmail.html delete mode 100644 data/core.telegram.org/constructor/securePlainPhone.html delete mode 100644 data/core.telegram.org/constructor/secureRequiredType.html delete mode 100644 data/core.telegram.org/constructor/secureSecretSettings.html delete mode 100644 data/core.telegram.org/constructor/secureValue.html delete mode 100644 data/core.telegram.org/constructor/secureValueError.html delete mode 100644 data/core.telegram.org/constructor/secureValueErrorData.html delete mode 100644 data/core.telegram.org/constructor/secureValueErrorFile.html delete mode 100644 data/core.telegram.org/constructor/secureValueErrorFiles.html delete mode 100644 data/core.telegram.org/constructor/secureValueErrorFrontSide.html delete mode 100644 data/core.telegram.org/constructor/secureValueErrorReverseSide.html delete mode 100644 data/core.telegram.org/constructor/secureValueErrorSelfie.html delete mode 100644 data/core.telegram.org/constructor/secureValueErrorTranslationFile.html delete mode 100644 data/core.telegram.org/constructor/secureValueErrorTranslationFiles.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypeAddress.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypeBankStatement.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypeDriverLicense.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypeEmail.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypeIdentityCard.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypeInternalPassport.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypePassport.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypePassportRegistration.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypePersonalDetails.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypePhone.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypeRentalAgreement.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypeTemporaryRegistration.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypeUtilityBill.html delete mode 100644 data/core.telegram.org/constructor/sendMessageCancelAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageChooseContactAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageChooseStickerAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageEmojiInteractionSeen.html delete mode 100644 data/core.telegram.org/constructor/sendMessageGamePlayAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageGeoLocationAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageHistoryImportAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageRecordAudioAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageRecordRoundAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageRecordVideoAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageTypingAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageUploadAudioAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageUploadDocumentAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageUploadRoundAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageUploadVideoAction.html delete mode 100644 data/core.telegram.org/constructor/shippingOption.html delete mode 100644 data/core.telegram.org/constructor/speakingInGroupCallAction.html delete mode 100644 data/core.telegram.org/constructor/sponsoredMessage.html delete mode 100644 data/core.telegram.org/constructor/stats.broadcastStats delete mode 100644 data/core.telegram.org/constructor/stats.megagroupStats delete mode 100644 data/core.telegram.org/constructor/stats.messageStats delete mode 100644 data/core.telegram.org/constructor/statsAbsValueAndPrev.html delete mode 100644 data/core.telegram.org/constructor/statsDateRangeDays.html delete mode 100644 data/core.telegram.org/constructor/statsGraph.html delete mode 100644 data/core.telegram.org/constructor/statsGraphAsync.html delete mode 100644 data/core.telegram.org/constructor/statsGraphError.html delete mode 100644 data/core.telegram.org/constructor/statsGroupTopAdmin.html delete mode 100644 data/core.telegram.org/constructor/statsGroupTopInviter.html delete mode 100644 data/core.telegram.org/constructor/statsPercentValue.html delete mode 100644 data/core.telegram.org/constructor/statsURL.html delete mode 100644 data/core.telegram.org/constructor/stickerPack.html delete mode 100644 data/core.telegram.org/constructor/stickerSet.html delete mode 100644 data/core.telegram.org/constructor/stickerSetCovered.html delete mode 100644 data/core.telegram.org/constructor/stickerSetMultiCovered.html delete mode 100644 data/core.telegram.org/constructor/stickers.suggestedShortName delete mode 100644 data/core.telegram.org/constructor/storage.fileGif delete mode 100644 data/core.telegram.org/constructor/storage.fileJpeg delete mode 100644 data/core.telegram.org/constructor/storage.fileMov delete mode 100644 data/core.telegram.org/constructor/storage.fileMp3 delete mode 100644 data/core.telegram.org/constructor/storage.fileMp4 delete mode 100644 data/core.telegram.org/constructor/storage.filePartial delete mode 100644 data/core.telegram.org/constructor/storage.filePdf delete mode 100644 data/core.telegram.org/constructor/storage.filePng delete mode 100644 data/core.telegram.org/constructor/storage.fileUnknown delete mode 100644 data/core.telegram.org/constructor/storage.fileWebp delete mode 100644 data/core.telegram.org/constructor/textAnchor.html delete mode 100644 data/core.telegram.org/constructor/textBold.html delete mode 100644 data/core.telegram.org/constructor/textConcat.html delete mode 100644 data/core.telegram.org/constructor/textEmail.html delete mode 100644 data/core.telegram.org/constructor/textEmpty.html delete mode 100644 data/core.telegram.org/constructor/textFixed.html delete mode 100644 data/core.telegram.org/constructor/textImage.html delete mode 100644 data/core.telegram.org/constructor/textItalic.html delete mode 100644 data/core.telegram.org/constructor/textMarked.html delete mode 100644 data/core.telegram.org/constructor/textStrike.html delete mode 100644 data/core.telegram.org/constructor/textSubscript.html delete mode 100644 data/core.telegram.org/constructor/textSuperscript.html delete mode 100644 data/core.telegram.org/constructor/textUnderline.html delete mode 100644 data/core.telegram.org/constructor/textUrl.html delete mode 100644 data/core.telegram.org/constructor/theme.html delete mode 100644 data/core.telegram.org/constructor/themeSettings.html delete mode 100644 data/core.telegram.org/constructor/topPeer.html delete mode 100644 data/core.telegram.org/constructor/topPeerCategoryBotsInline.html delete mode 100644 data/core.telegram.org/constructor/topPeerCategoryBotsPM.html delete mode 100644 data/core.telegram.org/constructor/topPeerCategoryChannels.html delete mode 100644 data/core.telegram.org/constructor/topPeerCategoryCorrespondents.html delete mode 100644 data/core.telegram.org/constructor/topPeerCategoryForwardChats.html delete mode 100644 data/core.telegram.org/constructor/topPeerCategoryForwardUsers.html delete mode 100644 data/core.telegram.org/constructor/topPeerCategoryGroups.html delete mode 100644 data/core.telegram.org/constructor/topPeerCategoryPhoneCalls.html delete mode 100644 data/core.telegram.org/constructor/true.html delete mode 100644 data/core.telegram.org/constructor/updateBotCallbackQuery.html delete mode 100644 data/core.telegram.org/constructor/updateBotCommands.html delete mode 100644 data/core.telegram.org/constructor/updateBotInlineQuery.html delete mode 100644 data/core.telegram.org/constructor/updateBotShippingQuery.html delete mode 100644 data/core.telegram.org/constructor/updateBotStopped.html delete mode 100644 data/core.telegram.org/constructor/updateBotWebhookJSON.html delete mode 100644 data/core.telegram.org/constructor/updateBotWebhookJSONQuery.html delete mode 100644 data/core.telegram.org/constructor/updateChannel.html delete mode 100644 data/core.telegram.org/constructor/updateChannelMessageForwards.html delete mode 100644 data/core.telegram.org/constructor/updateChannelMessageViews.html delete mode 100644 data/core.telegram.org/constructor/updateChannelParticipant.html delete mode 100644 data/core.telegram.org/constructor/updateChannelReadMessagesContents.html delete mode 100644 data/core.telegram.org/constructor/updateChannelTooLong.html delete mode 100644 data/core.telegram.org/constructor/updateChannelUserTyping.html delete mode 100644 data/core.telegram.org/constructor/updateChannelWebPage.html delete mode 100644 data/core.telegram.org/constructor/updateChat.html delete mode 100644 data/core.telegram.org/constructor/updateChatDefaultBannedRights.html delete mode 100644 data/core.telegram.org/constructor/updateChatParticipantAdd.html delete mode 100644 data/core.telegram.org/constructor/updateChatParticipantAdmin.html delete mode 100644 data/core.telegram.org/constructor/updateChatParticipantDelete.html delete mode 100644 data/core.telegram.org/constructor/updateChatParticipants.html delete mode 100644 data/core.telegram.org/constructor/updateChatUserTyping.html delete mode 100644 data/core.telegram.org/constructor/updateConfig.html delete mode 100644 data/core.telegram.org/constructor/updateDcOptions.html delete mode 100644 data/core.telegram.org/constructor/updateDeleteChannelMessages.html delete mode 100644 data/core.telegram.org/constructor/updateDeleteMessages.html delete mode 100644 data/core.telegram.org/constructor/updateDeleteScheduledMessages.html delete mode 100644 data/core.telegram.org/constructor/updateDialogFilterOrder.html delete mode 100644 data/core.telegram.org/constructor/updateDialogFilters.html delete mode 100644 data/core.telegram.org/constructor/updateDialogPinned.html delete mode 100644 data/core.telegram.org/constructor/updateDialogUnreadMark.html delete mode 100644 data/core.telegram.org/constructor/updateDraftMessage.html delete mode 100644 data/core.telegram.org/constructor/updateEditChannelMessage.html delete mode 100644 data/core.telegram.org/constructor/updateEditMessage.html delete mode 100644 data/core.telegram.org/constructor/updateEncryptedChatTyping.html delete mode 100644 data/core.telegram.org/constructor/updateEncryptedMessagesRead.html delete mode 100644 data/core.telegram.org/constructor/updateEncryption.html delete mode 100644 data/core.telegram.org/constructor/updateFavedStickers.html delete mode 100644 data/core.telegram.org/constructor/updateFolderPeers.html delete mode 100644 data/core.telegram.org/constructor/updateGeoLiveViewed.html delete mode 100644 data/core.telegram.org/constructor/updateGroupCall.html delete mode 100644 data/core.telegram.org/constructor/updateGroupCallConnection.html delete mode 100644 data/core.telegram.org/constructor/updateGroupCallParticipants.html delete mode 100644 data/core.telegram.org/constructor/updateLangPack.html delete mode 100644 data/core.telegram.org/constructor/updateLangPackTooLong.html delete mode 100644 data/core.telegram.org/constructor/updateLoginToken.html delete mode 100644 data/core.telegram.org/constructor/updateMessageID.html delete mode 100644 data/core.telegram.org/constructor/updateMessagePoll.html delete mode 100644 data/core.telegram.org/constructor/updateMessagePollVote.html delete mode 100644 data/core.telegram.org/constructor/updateNewChannelMessage.html delete mode 100644 data/core.telegram.org/constructor/updateNewEncryptedMessage.html delete mode 100644 data/core.telegram.org/constructor/updateNewMessage.html delete mode 100644 data/core.telegram.org/constructor/updateNewScheduledMessage.html delete mode 100644 data/core.telegram.org/constructor/updateNewStickerSet.html delete mode 100644 data/core.telegram.org/constructor/updateNotifySettings.html delete mode 100644 data/core.telegram.org/constructor/updatePeerBlocked.html delete mode 100644 data/core.telegram.org/constructor/updatePeerLocated.html delete mode 100644 data/core.telegram.org/constructor/updatePeerSettings.html delete mode 100644 data/core.telegram.org/constructor/updatePhoneCall.html delete mode 100644 data/core.telegram.org/constructor/updatePhoneCallSignalingData.html delete mode 100644 data/core.telegram.org/constructor/updatePinnedChannelMessages.html delete mode 100644 data/core.telegram.org/constructor/updatePinnedDialogs.html delete mode 100644 data/core.telegram.org/constructor/updatePinnedMessages.html delete mode 100644 data/core.telegram.org/constructor/updatePrivacy.html delete mode 100644 data/core.telegram.org/constructor/updatePtsChanged.html delete mode 100644 data/core.telegram.org/constructor/updateReadChannelDiscussionInbox.html delete mode 100644 data/core.telegram.org/constructor/updateReadChannelDiscussionOutbox.html delete mode 100644 data/core.telegram.org/constructor/updateReadChannelInbox.html delete mode 100644 data/core.telegram.org/constructor/updateReadChannelOutbox.html delete mode 100644 data/core.telegram.org/constructor/updateReadFeaturedStickers.html delete mode 100644 data/core.telegram.org/constructor/updateReadHistoryInbox.html delete mode 100644 data/core.telegram.org/constructor/updateReadHistoryOutbox.html delete mode 100644 data/core.telegram.org/constructor/updateReadMessagesContents.html delete mode 100644 data/core.telegram.org/constructor/updateRecentStickers.html delete mode 100644 data/core.telegram.org/constructor/updateSavedGifs.html delete mode 100644 data/core.telegram.org/constructor/updateServiceNotification.html delete mode 100644 data/core.telegram.org/constructor/updateShort.html delete mode 100644 data/core.telegram.org/constructor/updateShortMessage.html delete mode 100644 data/core.telegram.org/constructor/updateShortSentMessage.html delete mode 100644 data/core.telegram.org/constructor/updateStickerSets.html delete mode 100644 data/core.telegram.org/constructor/updateStickerSetsOrder.html delete mode 100644 data/core.telegram.org/constructor/updateTheme.html delete mode 100644 data/core.telegram.org/constructor/updateUserBlocked.html delete mode 100644 data/core.telegram.org/constructor/updateUserName.html delete mode 100644 data/core.telegram.org/constructor/updateUserPhone.html delete mode 100644 data/core.telegram.org/constructor/updateUserPhoto.html delete mode 100644 data/core.telegram.org/constructor/updateUserStatus.html delete mode 100644 data/core.telegram.org/constructor/updateUserTyping.html delete mode 100644 data/core.telegram.org/constructor/updateWebPage.html delete mode 100644 data/core.telegram.org/constructor/updates.channelDifference delete mode 100644 data/core.telegram.org/constructor/updates.channelDifferenceEmpty delete mode 100644 data/core.telegram.org/constructor/updates.channelDifferenceTooLong delete mode 100644 data/core.telegram.org/constructor/updates.difference delete mode 100644 data/core.telegram.org/constructor/updates.differenceEmpty delete mode 100644 data/core.telegram.org/constructor/updates.differenceSlice delete mode 100644 data/core.telegram.org/constructor/updates.differenceTooLong delete mode 100644 data/core.telegram.org/constructor/updates.html delete mode 100644 data/core.telegram.org/constructor/updates.state delete mode 100644 data/core.telegram.org/constructor/updatesCombined.html delete mode 100644 data/core.telegram.org/constructor/updatesTooLong.html delete mode 100644 data/core.telegram.org/constructor/upload.cdnFile delete mode 100644 data/core.telegram.org/constructor/upload.cdnFileReuploadNeeded delete mode 100644 data/core.telegram.org/constructor/upload.file delete mode 100644 data/core.telegram.org/constructor/upload.fileCdnRedirect delete mode 100644 data/core.telegram.org/constructor/upload.webFile delete mode 100644 data/core.telegram.org/constructor/urlAuthResultAccepted.html delete mode 100644 data/core.telegram.org/constructor/urlAuthResultDefault.html delete mode 100644 data/core.telegram.org/constructor/urlAuthResultRequest.html delete mode 100644 data/core.telegram.org/constructor/user.html delete mode 100644 data/core.telegram.org/constructor/userFull.html delete mode 100644 data/core.telegram.org/constructor/userProfilePhoto.html delete mode 100644 data/core.telegram.org/constructor/userProfilePhotoEmpty.html delete mode 100644 data/core.telegram.org/constructor/userStatusEmpty.html delete mode 100644 data/core.telegram.org/constructor/userStatusLastMonth.html delete mode 100644 data/core.telegram.org/constructor/userStatusLastWeek.html delete mode 100644 data/core.telegram.org/constructor/userStatusOffline.html delete mode 100644 data/core.telegram.org/constructor/userStatusOnline.html delete mode 100644 data/core.telegram.org/constructor/userStatusRecently.html delete mode 100644 data/core.telegram.org/constructor/vector.html delete mode 100644 data/core.telegram.org/constructor/videoSize.html delete mode 100644 data/core.telegram.org/constructor/wallPaper.html delete mode 100644 data/core.telegram.org/constructor/wallPaperNoFile.html delete mode 100644 data/core.telegram.org/constructor/wallPaperSettings.html delete mode 100644 data/core.telegram.org/constructor/wallPaperSolid.html delete mode 100644 data/core.telegram.org/constructor/webAuthorization.html delete mode 100644 data/core.telegram.org/constructor/webDocument.html delete mode 100644 data/core.telegram.org/constructor/webPage.html delete mode 100644 data/core.telegram.org/constructor/webPageAttributeTheme.html delete mode 100644 data/core.telegram.org/constructor/webPageEmpty.html delete mode 100644 data/core.telegram.org/constructor/webPageNotModified.html delete mode 100644 data/core.telegram.org/constructor/webPagePending.html delete mode 100644 data/core.telegram.org/contest300K.html delete mode 100644 data/core.telegram.org/css/bootstrap-extra.css delete mode 100644 data/core.telegram.org/css/core-widgets.css delete mode 100644 data/core.telegram.org/css/telegram-extra.css delete mode 100644 data/core.telegram.org/getProxyConfig.html delete mode 100644 data/core.telegram.org/import-stickers.html delete mode 100644 data/core.telegram.org/js/core-widgets.js delete mode 100644 data/core.telegram.org/js/jquery-ui.min.js delete mode 100644 data/core.telegram.org/js/telegram-passport2.js delete mode 100644 data/core.telegram.org/method/account.acceptAuthorization delete mode 100644 data/core.telegram.org/method/account.cancelPasswordEmail delete mode 100644 data/core.telegram.org/method/account.changePhone delete mode 100644 data/core.telegram.org/method/account.checkUsername delete mode 100644 data/core.telegram.org/method/account.confirmPasswordEmail delete mode 100644 data/core.telegram.org/method/account.confirmPhone delete mode 100644 data/core.telegram.org/method/account.createTheme delete mode 100644 data/core.telegram.org/method/account.declinePasswordReset delete mode 100644 data/core.telegram.org/method/account.deleteAccount delete mode 100644 data/core.telegram.org/method/account.deleteSecureValue delete mode 100644 data/core.telegram.org/method/account.finishTakeoutSession delete mode 100644 data/core.telegram.org/method/account.getAccountTTL delete mode 100644 data/core.telegram.org/method/account.getAllSecureValues delete mode 100644 data/core.telegram.org/method/account.getAuthorizationForm delete mode 100644 data/core.telegram.org/method/account.getAuthorizations delete mode 100644 data/core.telegram.org/method/account.getAutoDownloadSettings delete mode 100644 data/core.telegram.org/method/account.getChatThemes delete mode 100644 data/core.telegram.org/method/account.getContactSignUpNotification delete mode 100644 data/core.telegram.org/method/account.getContentSettings delete mode 100644 data/core.telegram.org/method/account.getGlobalPrivacySettings delete mode 100644 data/core.telegram.org/method/account.getMultiWallPapers delete mode 100644 data/core.telegram.org/method/account.getNotifyExceptions delete mode 100644 data/core.telegram.org/method/account.getPassword delete mode 100644 data/core.telegram.org/method/account.getPasswordSettings delete mode 100644 data/core.telegram.org/method/account.getPrivacy delete mode 100644 data/core.telegram.org/method/account.getSecureValue delete mode 100644 data/core.telegram.org/method/account.getTheme delete mode 100644 data/core.telegram.org/method/account.getThemes delete mode 100644 data/core.telegram.org/method/account.getTmpPassword delete mode 100644 data/core.telegram.org/method/account.getWallPaper delete mode 100644 data/core.telegram.org/method/account.getWallPapers delete mode 100644 data/core.telegram.org/method/account.getWebAuthorizations delete mode 100644 data/core.telegram.org/method/account.initTakeoutSession delete mode 100644 data/core.telegram.org/method/account.installTheme delete mode 100644 data/core.telegram.org/method/account.installWallPaper delete mode 100644 data/core.telegram.org/method/account.registerDevice delete mode 100644 data/core.telegram.org/method/account.reportPeer delete mode 100644 data/core.telegram.org/method/account.reportProfilePhoto delete mode 100644 data/core.telegram.org/method/account.resendPasswordEmail delete mode 100644 data/core.telegram.org/method/account.resetAuthorization delete mode 100644 data/core.telegram.org/method/account.resetNotifySettings delete mode 100644 data/core.telegram.org/method/account.resetPassword delete mode 100644 data/core.telegram.org/method/account.resetWebAuthorization delete mode 100644 data/core.telegram.org/method/account.resetWebAuthorizations delete mode 100644 data/core.telegram.org/method/account.saveSecureValue delete mode 100644 data/core.telegram.org/method/account.saveTheme delete mode 100644 data/core.telegram.org/method/account.saveWallPaper delete mode 100644 data/core.telegram.org/method/account.sendChangePhoneCode delete mode 100644 data/core.telegram.org/method/account.sendConfirmPhoneCode delete mode 100644 data/core.telegram.org/method/account.sendVerifyEmailCode delete mode 100644 data/core.telegram.org/method/account.sendVerifyPhoneCode delete mode 100644 data/core.telegram.org/method/account.setAccountTTL delete mode 100644 data/core.telegram.org/method/account.setContactSignUpNotification delete mode 100644 data/core.telegram.org/method/account.setContentSettings delete mode 100644 data/core.telegram.org/method/account.setGlobalPrivacySettings delete mode 100644 data/core.telegram.org/method/account.setPrivacy delete mode 100644 data/core.telegram.org/method/account.unregisterDevice delete mode 100644 data/core.telegram.org/method/account.updateDeviceLocked delete mode 100644 data/core.telegram.org/method/account.updateNotifySettings delete mode 100644 data/core.telegram.org/method/account.updatePasswordSettings delete mode 100644 data/core.telegram.org/method/account.updateProfile delete mode 100644 data/core.telegram.org/method/account.updateStatus delete mode 100644 data/core.telegram.org/method/account.updateTheme delete mode 100644 data/core.telegram.org/method/account.updateUsername delete mode 100644 data/core.telegram.org/method/account.uploadTheme delete mode 100644 data/core.telegram.org/method/account.uploadWallPaper delete mode 100644 data/core.telegram.org/method/account.verifyEmail delete mode 100644 data/core.telegram.org/method/account.verifyPhone delete mode 100644 data/core.telegram.org/method/auth.acceptLoginToken delete mode 100644 data/core.telegram.org/method/auth.cancelCode delete mode 100644 data/core.telegram.org/method/auth.checkPassword delete mode 100644 data/core.telegram.org/method/auth.checkPhone delete mode 100644 data/core.telegram.org/method/auth.checkRecoveryPassword delete mode 100644 data/core.telegram.org/method/auth.dropTempAuthKeys delete mode 100644 data/core.telegram.org/method/auth.exportAuthorization delete mode 100644 data/core.telegram.org/method/auth.exportLoginToken delete mode 100644 data/core.telegram.org/method/auth.importAuthorization delete mode 100644 data/core.telegram.org/method/auth.importBotAuthorization delete mode 100644 data/core.telegram.org/method/auth.importLoginToken delete mode 100644 data/core.telegram.org/method/auth.recoverPassword delete mode 100644 data/core.telegram.org/method/auth.requestPasswordRecovery delete mode 100644 data/core.telegram.org/method/auth.resendCode delete mode 100644 data/core.telegram.org/method/auth.resetAuthorizations delete mode 100644 data/core.telegram.org/method/auth.sendCall delete mode 100644 data/core.telegram.org/method/auth.sendCode delete mode 100644 data/core.telegram.org/method/auth.sendInvites delete mode 100644 data/core.telegram.org/method/auth.sendSms delete mode 100644 data/core.telegram.org/method/auth.signIn delete mode 100644 data/core.telegram.org/method/auth.signUp delete mode 100644 data/core.telegram.org/method/bots.answerWebhookJSONQuery delete mode 100644 data/core.telegram.org/method/bots.getBotCommands delete mode 100644 data/core.telegram.org/method/bots.resetBotCommands delete mode 100644 data/core.telegram.org/method/bots.sendCustomRequest delete mode 100644 data/core.telegram.org/method/bots.setBotCommands delete mode 100644 data/core.telegram.org/method/channels.checkUsername delete mode 100644 data/core.telegram.org/method/channels.convertToGigagroup delete mode 100644 data/core.telegram.org/method/channels.createChannel delete mode 100644 data/core.telegram.org/method/channels.deleteChannel delete mode 100644 data/core.telegram.org/method/channels.deleteHistory delete mode 100644 data/core.telegram.org/method/channels.editAdmin delete mode 100644 data/core.telegram.org/method/channels.editBanned delete mode 100644 data/core.telegram.org/method/channels.editLocation delete mode 100644 data/core.telegram.org/method/channels.editPhoto delete mode 100644 data/core.telegram.org/method/channels.editTitle delete mode 100644 data/core.telegram.org/method/channels.exportMessageLink delete mode 100644 data/core.telegram.org/method/channels.getAdminLog delete mode 100644 data/core.telegram.org/method/channels.getAdminedPublicChannels delete mode 100644 data/core.telegram.org/method/channels.getChannels delete mode 100644 data/core.telegram.org/method/channels.getGroupsForDiscussion delete mode 100644 data/core.telegram.org/method/channels.getInactiveChannels delete mode 100644 data/core.telegram.org/method/channels.getLeftChannels delete mode 100644 data/core.telegram.org/method/channels.getMessages delete mode 100644 data/core.telegram.org/method/channels.getParticipant delete mode 100644 data/core.telegram.org/method/channels.getParticipants delete mode 100644 data/core.telegram.org/method/channels.getSponsoredMessages delete mode 100644 data/core.telegram.org/method/channels.inviteToChannel delete mode 100644 data/core.telegram.org/method/channels.joinChannel delete mode 100644 data/core.telegram.org/method/channels.leaveChannel delete mode 100644 data/core.telegram.org/method/channels.readMessageContents delete mode 100644 data/core.telegram.org/method/channels.reportSpam delete mode 100644 data/core.telegram.org/method/channels.setDiscussionGroup delete mode 100644 data/core.telegram.org/method/channels.setStickers delete mode 100644 data/core.telegram.org/method/channels.togglePreHistoryHidden delete mode 100644 data/core.telegram.org/method/channels.toggleSignatures delete mode 100644 data/core.telegram.org/method/channels.toggleSlowMode delete mode 100644 data/core.telegram.org/method/channels.updateUsername delete mode 100644 data/core.telegram.org/method/contacts.acceptContact delete mode 100644 data/core.telegram.org/method/contacts.block delete mode 100644 data/core.telegram.org/method/contacts.blockFromReplies delete mode 100644 data/core.telegram.org/method/contacts.deleteByPhones delete mode 100644 data/core.telegram.org/method/contacts.deleteContacts delete mode 100644 data/core.telegram.org/method/contacts.getBlocked delete mode 100644 data/core.telegram.org/method/contacts.getContactIDs delete mode 100644 data/core.telegram.org/method/contacts.getContacts delete mode 100644 data/core.telegram.org/method/contacts.getLocated delete mode 100644 data/core.telegram.org/method/contacts.getSaved delete mode 100644 data/core.telegram.org/method/contacts.getStatuses delete mode 100644 data/core.telegram.org/method/contacts.getTopPeers delete mode 100644 data/core.telegram.org/method/contacts.importContacts delete mode 100644 data/core.telegram.org/method/contacts.resetSaved delete mode 100644 data/core.telegram.org/method/contacts.resetTopPeerRating delete mode 100644 data/core.telegram.org/method/contacts.resolveUsername delete mode 100644 data/core.telegram.org/method/contacts.search delete mode 100644 data/core.telegram.org/method/contacts.toggleTopPeers delete mode 100644 data/core.telegram.org/method/contacts.unblock delete mode 100644 data/core.telegram.org/method/folders.deleteFolder delete mode 100644 data/core.telegram.org/method/folders.editPeerFolders delete mode 100644 data/core.telegram.org/method/help.acceptTermsOfService delete mode 100644 data/core.telegram.org/method/help.dismissSuggestion delete mode 100644 data/core.telegram.org/method/help.editUserInfo delete mode 100644 data/core.telegram.org/method/help.getAppChangelog delete mode 100644 data/core.telegram.org/method/help.getAppConfig delete mode 100644 data/core.telegram.org/method/help.getAppUpdate delete mode 100644 data/core.telegram.org/method/help.getCdnConfig delete mode 100644 data/core.telegram.org/method/help.getConfig delete mode 100644 data/core.telegram.org/method/help.getCountriesList delete mode 100644 data/core.telegram.org/method/help.getDeepLinkInfo delete mode 100644 data/core.telegram.org/method/help.getInviteText delete mode 100644 data/core.telegram.org/method/help.getPassportConfig delete mode 100644 data/core.telegram.org/method/help.getPromoData delete mode 100644 data/core.telegram.org/method/help.getProxyData delete mode 100644 data/core.telegram.org/method/help.getRecentMeUrls delete mode 100644 data/core.telegram.org/method/help.getSupport delete mode 100644 data/core.telegram.org/method/help.getSupportName delete mode 100644 data/core.telegram.org/method/help.getTermsOfServiceUpdate delete mode 100644 data/core.telegram.org/method/help.getUserInfo delete mode 100644 data/core.telegram.org/method/help.hidePromoData delete mode 100644 data/core.telegram.org/method/help.saveAppLog delete mode 100644 data/core.telegram.org/method/help.setBotUpdatesStatus delete mode 100644 data/core.telegram.org/method/initConnection.html delete mode 100644 data/core.telegram.org/method/invokeAfterMsg.html delete mode 100644 data/core.telegram.org/method/invokeAfterMsgs.html delete mode 100644 data/core.telegram.org/method/invokeWithLayer.html delete mode 100644 data/core.telegram.org/method/invokeWithTakeout.html delete mode 100644 data/core.telegram.org/method/invokeWithoutUpdates.html delete mode 100644 data/core.telegram.org/method/langpack.getDifference delete mode 100644 data/core.telegram.org/method/langpack.getLangPack delete mode 100644 data/core.telegram.org/method/langpack.getLanguage delete mode 100644 data/core.telegram.org/method/langpack.getLanguages delete mode 100644 data/core.telegram.org/method/messages.acceptEncryption delete mode 100644 data/core.telegram.org/method/messages.addChatUser delete mode 100644 data/core.telegram.org/method/messages.checkHistoryImport delete mode 100644 data/core.telegram.org/method/messages.checkHistoryImportPeer delete mode 100644 data/core.telegram.org/method/messages.clearAllDrafts delete mode 100644 data/core.telegram.org/method/messages.clearRecentStickers delete mode 100644 data/core.telegram.org/method/messages.createChat delete mode 100644 data/core.telegram.org/method/messages.deleteChat delete mode 100644 data/core.telegram.org/method/messages.deleteChatUser delete mode 100644 data/core.telegram.org/method/messages.deleteExportedChatInvite delete mode 100644 data/core.telegram.org/method/messages.deleteHistory delete mode 100644 data/core.telegram.org/method/messages.deletePhoneCallHistory delete mode 100644 data/core.telegram.org/method/messages.deleteRevokedExportedChatInvites delete mode 100644 data/core.telegram.org/method/messages.deleteScheduledMessages delete mode 100644 data/core.telegram.org/method/messages.discardEncryption delete mode 100644 data/core.telegram.org/method/messages.editChatAbout delete mode 100644 data/core.telegram.org/method/messages.editChatAdmin delete mode 100644 data/core.telegram.org/method/messages.editChatDefaultBannedRights delete mode 100644 data/core.telegram.org/method/messages.editChatPhoto delete mode 100644 data/core.telegram.org/method/messages.editChatTitle delete mode 100644 data/core.telegram.org/method/messages.editExportedChatInvite delete mode 100644 data/core.telegram.org/method/messages.editInlineBotMessage delete mode 100644 data/core.telegram.org/method/messages.editMessage delete mode 100644 data/core.telegram.org/method/messages.exportChatInvite delete mode 100644 data/core.telegram.org/method/messages.faveSticker delete mode 100644 data/core.telegram.org/method/messages.forwardMessage delete mode 100644 data/core.telegram.org/method/messages.forwardMessages delete mode 100644 data/core.telegram.org/method/messages.getAdminsWithInvites delete mode 100644 data/core.telegram.org/method/messages.getAllChats delete mode 100644 data/core.telegram.org/method/messages.getAllDrafts delete mode 100644 data/core.telegram.org/method/messages.getAllStickers delete mode 100644 data/core.telegram.org/method/messages.getArchivedStickers delete mode 100644 data/core.telegram.org/method/messages.getAttachedStickers delete mode 100644 data/core.telegram.org/method/messages.getBotCallbackAnswer delete mode 100644 data/core.telegram.org/method/messages.getChatInviteImporters delete mode 100644 data/core.telegram.org/method/messages.getChats delete mode 100644 data/core.telegram.org/method/messages.getCommonChats delete mode 100644 data/core.telegram.org/method/messages.getDhConfig delete mode 100644 data/core.telegram.org/method/messages.getDialogFilters delete mode 100644 data/core.telegram.org/method/messages.getDialogUnreadMarks delete mode 100644 data/core.telegram.org/method/messages.getDialogs delete mode 100644 data/core.telegram.org/method/messages.getDiscussionMessage delete mode 100644 data/core.telegram.org/method/messages.getDocumentByHash delete mode 100644 data/core.telegram.org/method/messages.getEmojiKeywords delete mode 100644 data/core.telegram.org/method/messages.getEmojiKeywordsDifference delete mode 100644 data/core.telegram.org/method/messages.getEmojiKeywordsLanguages delete mode 100644 data/core.telegram.org/method/messages.getEmojiURL delete mode 100644 data/core.telegram.org/method/messages.getExportedChatInvite delete mode 100644 data/core.telegram.org/method/messages.getExportedChatInvites delete mode 100644 data/core.telegram.org/method/messages.getFeaturedStickers delete mode 100644 data/core.telegram.org/method/messages.getGameHighScores delete mode 100644 data/core.telegram.org/method/messages.getInlineBotResults delete mode 100644 data/core.telegram.org/method/messages.getInlineGameHighScores delete mode 100644 data/core.telegram.org/method/messages.getMaskStickers delete mode 100644 data/core.telegram.org/method/messages.getMessageEditData delete mode 100644 data/core.telegram.org/method/messages.getMessageReactionsList delete mode 100644 data/core.telegram.org/method/messages.getMessageReadParticipants delete mode 100644 data/core.telegram.org/method/messages.getMessages delete mode 100644 data/core.telegram.org/method/messages.getMessagesReactions delete mode 100644 data/core.telegram.org/method/messages.getMessagesViews delete mode 100644 data/core.telegram.org/method/messages.getOldFeaturedStickers delete mode 100644 data/core.telegram.org/method/messages.getOnlines delete mode 100644 data/core.telegram.org/method/messages.getPeerDialogs delete mode 100644 data/core.telegram.org/method/messages.getPeerSettings delete mode 100644 data/core.telegram.org/method/messages.getPinnedDialogs delete mode 100644 data/core.telegram.org/method/messages.getPollResults delete mode 100644 data/core.telegram.org/method/messages.getPollVotes delete mode 100644 data/core.telegram.org/method/messages.getRecentLocations delete mode 100644 data/core.telegram.org/method/messages.getReplies delete mode 100644 data/core.telegram.org/method/messages.getSavedGifs delete mode 100644 data/core.telegram.org/method/messages.getScheduledHistory delete mode 100644 data/core.telegram.org/method/messages.getScheduledMessages delete mode 100644 data/core.telegram.org/method/messages.getSearchCounters delete mode 100644 data/core.telegram.org/method/messages.getSplitRanges delete mode 100644 data/core.telegram.org/method/messages.getStickerSet delete mode 100644 data/core.telegram.org/method/messages.getStickers delete mode 100644 data/core.telegram.org/method/messages.getSuggestedDialogFilters delete mode 100644 data/core.telegram.org/method/messages.getUnreadMentions delete mode 100644 data/core.telegram.org/method/messages.getWebPage delete mode 100644 data/core.telegram.org/method/messages.getWebPagePreview delete mode 100644 data/core.telegram.org/method/messages.hidePeerSettingsBar delete mode 100644 data/core.telegram.org/method/messages.importChatInvite delete mode 100644 data/core.telegram.org/method/messages.initHistoryImport delete mode 100644 data/core.telegram.org/method/messages.installStickerSet delete mode 100644 data/core.telegram.org/method/messages.markDialogUnread delete mode 100644 data/core.telegram.org/method/messages.migrateChat delete mode 100644 data/core.telegram.org/method/messages.readDiscussion delete mode 100644 data/core.telegram.org/method/messages.readEncryptedHistory delete mode 100644 data/core.telegram.org/method/messages.readFeaturedStickers delete mode 100644 data/core.telegram.org/method/messages.readMentions delete mode 100644 data/core.telegram.org/method/messages.readMessageContents delete mode 100644 data/core.telegram.org/method/messages.receivedMessages delete mode 100644 data/core.telegram.org/method/messages.receivedQueue delete mode 100644 data/core.telegram.org/method/messages.reorderPinnedDialogs delete mode 100644 data/core.telegram.org/method/messages.reorderStickerSets delete mode 100644 data/core.telegram.org/method/messages.report delete mode 100644 data/core.telegram.org/method/messages.reportEncryptedSpam delete mode 100644 data/core.telegram.org/method/messages.reportSpam delete mode 100644 data/core.telegram.org/method/messages.requestEncryption delete mode 100644 data/core.telegram.org/method/messages.requestUrlAuth delete mode 100644 data/core.telegram.org/method/messages.saveDraft delete mode 100644 data/core.telegram.org/method/messages.saveGif delete mode 100644 data/core.telegram.org/method/messages.saveRecentSticker delete mode 100644 data/core.telegram.org/method/messages.search delete mode 100644 data/core.telegram.org/method/messages.searchGifs delete mode 100644 data/core.telegram.org/method/messages.searchGlobal delete mode 100644 data/core.telegram.org/method/messages.searchStickerSets delete mode 100644 data/core.telegram.org/method/messages.sendBroadcast delete mode 100644 data/core.telegram.org/method/messages.sendEncrypted delete mode 100644 data/core.telegram.org/method/messages.sendEncryptedFile delete mode 100644 data/core.telegram.org/method/messages.sendEncryptedService delete mode 100644 data/core.telegram.org/method/messages.sendInlineBotResult delete mode 100644 data/core.telegram.org/method/messages.sendMedia delete mode 100644 data/core.telegram.org/method/messages.sendMessage delete mode 100644 data/core.telegram.org/method/messages.sendMultiMedia delete mode 100644 data/core.telegram.org/method/messages.sendReaction delete mode 100644 data/core.telegram.org/method/messages.sendScheduledMessages delete mode 100644 data/core.telegram.org/method/messages.sendScreenshotNotification delete mode 100644 data/core.telegram.org/method/messages.sendVote delete mode 100644 data/core.telegram.org/method/messages.setBotCallbackAnswer delete mode 100644 data/core.telegram.org/method/messages.setBotPrecheckoutResults delete mode 100644 data/core.telegram.org/method/messages.setBotShippingResults delete mode 100644 data/core.telegram.org/method/messages.setChatTheme delete mode 100644 data/core.telegram.org/method/messages.setEncryptedTyping delete mode 100644 data/core.telegram.org/method/messages.setGameScore delete mode 100644 data/core.telegram.org/method/messages.setHistoryTTL delete mode 100644 data/core.telegram.org/method/messages.setInlineBotResults delete mode 100644 data/core.telegram.org/method/messages.setInlineGameScore delete mode 100644 data/core.telegram.org/method/messages.setTyping delete mode 100644 data/core.telegram.org/method/messages.startBot delete mode 100644 data/core.telegram.org/method/messages.startHistoryImport delete mode 100644 data/core.telegram.org/method/messages.toggleDialogPin delete mode 100644 data/core.telegram.org/method/messages.toggleStickerSets delete mode 100644 data/core.telegram.org/method/messages.uninstallStickerSet delete mode 100644 data/core.telegram.org/method/messages.updateDialogFilter delete mode 100644 data/core.telegram.org/method/messages.updateDialogFiltersOrder delete mode 100644 data/core.telegram.org/method/messages.updatePinnedMessage delete mode 100644 data/core.telegram.org/method/messages.uploadEncryptedFile delete mode 100644 data/core.telegram.org/method/messages.uploadMedia delete mode 100644 data/core.telegram.org/method/payments.clearSavedInfo delete mode 100644 data/core.telegram.org/method/payments.getBankCardData delete mode 100644 data/core.telegram.org/method/payments.getPaymentForm delete mode 100644 data/core.telegram.org/method/payments.getPaymentReceipt delete mode 100644 data/core.telegram.org/method/payments.getSavedInfo delete mode 100644 data/core.telegram.org/method/payments.sendPaymentForm delete mode 100644 data/core.telegram.org/method/payments.validateRequestedInfo delete mode 100644 data/core.telegram.org/method/phone.checkGroupCall delete mode 100644 data/core.telegram.org/method/phone.confirmCall delete mode 100644 data/core.telegram.org/method/phone.createGroupCall delete mode 100644 data/core.telegram.org/method/phone.discardCall delete mode 100644 data/core.telegram.org/method/phone.editGroupCallMember delete mode 100644 data/core.telegram.org/method/phone.editGroupCallParticipant delete mode 100644 data/core.telegram.org/method/phone.editGroupCallTitle delete mode 100644 data/core.telegram.org/method/phone.exportGroupCallInvite delete mode 100644 data/core.telegram.org/method/phone.getCallConfig delete mode 100644 data/core.telegram.org/method/phone.getGroupCall delete mode 100644 data/core.telegram.org/method/phone.getGroupCallJoinAs delete mode 100644 data/core.telegram.org/method/phone.getGroupParticipants delete mode 100644 data/core.telegram.org/method/phone.inviteToGroupCall delete mode 100644 data/core.telegram.org/method/phone.joinGroupCall delete mode 100644 data/core.telegram.org/method/phone.joinGroupCallPresentation delete mode 100644 data/core.telegram.org/method/phone.leaveGroupCall delete mode 100644 data/core.telegram.org/method/phone.leaveGroupCallPresentation delete mode 100644 data/core.telegram.org/method/phone.receivedCall delete mode 100644 data/core.telegram.org/method/phone.requestCall delete mode 100644 data/core.telegram.org/method/phone.saveCallDebug delete mode 100644 data/core.telegram.org/method/phone.saveDefaultGroupCallJoinAs delete mode 100644 data/core.telegram.org/method/phone.sendSignalingData delete mode 100644 data/core.telegram.org/method/phone.setCallRating delete mode 100644 data/core.telegram.org/method/phone.startScheduledGroupCall delete mode 100644 data/core.telegram.org/method/phone.toggleGroupCallRecord delete mode 100644 data/core.telegram.org/method/phone.toggleGroupCallSettings delete mode 100644 data/core.telegram.org/method/phone.toggleGroupCallStartSubscription delete mode 100644 data/core.telegram.org/method/photos.deletePhotos delete mode 100644 data/core.telegram.org/method/photos.getUserPhotos delete mode 100644 data/core.telegram.org/method/photos.updateProfilePhoto delete mode 100644 data/core.telegram.org/method/stats.getBroadcastStats delete mode 100644 data/core.telegram.org/method/stats.getMegagroupStats delete mode 100644 data/core.telegram.org/method/stats.getMessagePublicForwards delete mode 100644 data/core.telegram.org/method/stats.getMessageStats delete mode 100644 data/core.telegram.org/method/stats.loadAsyncGraph delete mode 100644 data/core.telegram.org/method/stickers.addStickerToSet delete mode 100644 data/core.telegram.org/method/stickers.changeStickerPosition delete mode 100644 data/core.telegram.org/method/stickers.checkShortName delete mode 100644 data/core.telegram.org/method/stickers.removeStickerFromSet delete mode 100644 data/core.telegram.org/method/stickers.setStickerSetThumb delete mode 100644 data/core.telegram.org/method/stickers.suggestShortName delete mode 100644 data/core.telegram.org/method/updates.getChannelDifference delete mode 100644 data/core.telegram.org/method/updates.getDifference delete mode 100644 data/core.telegram.org/method/updates.getState delete mode 100644 data/core.telegram.org/method/upload.getCdnFile delete mode 100644 data/core.telegram.org/method/upload.getCdnFileHashes delete mode 100644 data/core.telegram.org/method/upload.getFile delete mode 100644 data/core.telegram.org/method/upload.getFileHashes delete mode 100644 data/core.telegram.org/method/upload.getWebFile delete mode 100644 data/core.telegram.org/method/upload.reuploadCdnFile delete mode 100644 data/core.telegram.org/method/upload.saveBigFilePart delete mode 100644 data/core.telegram.org/method/upload.saveFilePart delete mode 100644 data/core.telegram.org/method/users.getFullUser delete mode 100644 data/core.telegram.org/method/users.getUsers delete mode 100644 data/core.telegram.org/method/users.setSecureValueErrors delete mode 100644 data/core.telegram.org/methods.html delete mode 100644 data/core.telegram.org/mtproto.html delete mode 100644 data/core.telegram.org/mtproto/TL-abstract-types.html delete mode 100644 data/core.telegram.org/mtproto/TL-combinators.html delete mode 100644 data/core.telegram.org/mtproto/TL-dependent.html delete mode 100644 data/core.telegram.org/mtproto/TL-formal.html delete mode 100644 data/core.telegram.org/mtproto/TL-optargs.html delete mode 100644 data/core.telegram.org/mtproto/TL-patterns.html delete mode 100644 data/core.telegram.org/mtproto/TL-polymorph.html delete mode 100644 data/core.telegram.org/mtproto/TL-tl.html delete mode 100644 data/core.telegram.org/mtproto/TL-types.html delete mode 100644 data/core.telegram.org/mtproto/TL.html delete mode 100644 data/core.telegram.org/mtproto/auth_key.html delete mode 100644 data/core.telegram.org/mtproto/description.html delete mode 100644 data/core.telegram.org/mtproto/description_v1.html delete mode 100644 data/core.telegram.org/mtproto/mtproto-transports.html delete mode 100644 data/core.telegram.org/mtproto/samples-auth_key.html delete mode 100644 data/core.telegram.org/mtproto/security_guidelines.html delete mode 100644 data/core.telegram.org/mtproto/security_guidelines_v1.html delete mode 100644 data/core.telegram.org/mtproto/serialize.html delete mode 100644 data/core.telegram.org/mtproto/service_messages.html delete mode 100644 data/core.telegram.org/mtproto/service_messages_about_messages.html delete mode 100644 data/core.telegram.org/mtproto_v1.html delete mode 100644 data/core.telegram.org/passport.html delete mode 100644 data/core.telegram.org/passport/encryption.html delete mode 100644 data/core.telegram.org/passport/example.html delete mode 100644 data/core.telegram.org/passport/sdk-android.html delete mode 100644 data/core.telegram.org/passport/sdk-ios-mac.html delete mode 100644 data/core.telegram.org/passport/sdk-javascript.html delete mode 100644 data/core.telegram.org/reproducible-builds.html delete mode 100644 data/core.telegram.org/schema.html delete mode 100644 data/core.telegram.org/schema/end-to-end-json.html delete mode 100644 data/core.telegram.org/schema/end-to-end.html delete mode 100644 data/core.telegram.org/schema/json.html delete mode 100644 data/core.telegram.org/schema/mtproto-json.html delete mode 100644 data/core.telegram.org/schema/mtproto.html delete mode 100644 data/core.telegram.org/stickers.html delete mode 100644 data/core.telegram.org/stickers/webm-vp9-encoding.html delete mode 100644 data/core.telegram.org/tdlib.html delete mode 100644 data/core.telegram.org/tdlib/getting-started.html delete mode 100644 data/core.telegram.org/tdlib/notification-api.html delete mode 100644 data/core.telegram.org/tdlib/options.html delete mode 100644 data/core.telegram.org/themes.html delete mode 100644 data/core.telegram.org/type/AccountDaysTTL.html delete mode 100644 data/core.telegram.org/type/Audio.html delete mode 100644 data/core.telegram.org/type/Authorization.html delete mode 100644 data/core.telegram.org/type/AutoDownloadSettings.html delete mode 100644 data/core.telegram.org/type/BankCardOpenUrl.html delete mode 100644 data/core.telegram.org/type/BaseTheme.html delete mode 100644 data/core.telegram.org/type/Bool.html delete mode 100644 data/core.telegram.org/type/BotCommand.html delete mode 100644 data/core.telegram.org/type/BotCommandScope.html delete mode 100644 data/core.telegram.org/type/BotInlineMessage.html delete mode 100644 data/core.telegram.org/type/BotInlineResult.html delete mode 100644 data/core.telegram.org/type/CdnConfig.html delete mode 100644 data/core.telegram.org/type/CdnPublicKey.html delete mode 100644 data/core.telegram.org/type/ChannelAdminLogEvent.html delete mode 100644 data/core.telegram.org/type/ChannelAdminLogEventAction.html delete mode 100644 data/core.telegram.org/type/ChannelAdminLogEventsFilter.html delete mode 100644 data/core.telegram.org/type/ChannelLocation.html delete mode 100644 data/core.telegram.org/type/ChannelMessagesFilter.html delete mode 100644 data/core.telegram.org/type/ChannelParticipant.html delete mode 100644 data/core.telegram.org/type/ChannelParticipantsFilter.html delete mode 100644 data/core.telegram.org/type/Chat.html delete mode 100644 data/core.telegram.org/type/ChatAdminRights.html delete mode 100644 data/core.telegram.org/type/ChatAdminWithInvites.html delete mode 100644 data/core.telegram.org/type/ChatBannedRights.html delete mode 100644 data/core.telegram.org/type/ChatFull.html delete mode 100644 data/core.telegram.org/type/ChatInvite.html delete mode 100644 data/core.telegram.org/type/ChatInviteImporter.html delete mode 100644 data/core.telegram.org/type/ChatOnlines.html delete mode 100644 data/core.telegram.org/type/ChatParticipant.html delete mode 100644 data/core.telegram.org/type/ChatParticipants.html delete mode 100644 data/core.telegram.org/type/ChatPhoto.html delete mode 100644 data/core.telegram.org/type/ChatTheme.html delete mode 100644 data/core.telegram.org/type/CodeSettings.html delete mode 100644 data/core.telegram.org/type/Config.html delete mode 100644 data/core.telegram.org/type/Contact.html delete mode 100644 data/core.telegram.org/type/ContactStatus.html delete mode 100644 data/core.telegram.org/type/DataJSON.html delete mode 100644 data/core.telegram.org/type/DcOption.html delete mode 100644 data/core.telegram.org/type/DecryptedDataBlock.html delete mode 100644 data/core.telegram.org/type/DecryptedMessage.html delete mode 100644 data/core.telegram.org/type/DecryptedMessageAction.html delete mode 100644 data/core.telegram.org/type/DecryptedMessageLayer.html delete mode 100644 data/core.telegram.org/type/DecryptedMessageMedia.html delete mode 100644 data/core.telegram.org/type/Dialog.html delete mode 100644 data/core.telegram.org/type/DialogFilter.html delete mode 100644 data/core.telegram.org/type/DialogFilterSuggested.html delete mode 100644 data/core.telegram.org/type/DialogPeer.html delete mode 100644 data/core.telegram.org/type/DisabledFeature.html delete mode 100644 data/core.telegram.org/type/Document.html delete mode 100644 data/core.telegram.org/type/DocumentAttribute.html delete mode 100644 data/core.telegram.org/type/EmojiKeyword.html delete mode 100644 data/core.telegram.org/type/EmojiLanguage.html delete mode 100644 data/core.telegram.org/type/EmojiURL.html delete mode 100644 data/core.telegram.org/type/EncryptedChat.html delete mode 100644 data/core.telegram.org/type/EncryptedFile.html delete mode 100644 data/core.telegram.org/type/EncryptedMessage.html delete mode 100644 data/core.telegram.org/type/Error.html delete mode 100644 data/core.telegram.org/type/ExportedChatInvite.html delete mode 100644 data/core.telegram.org/type/ExportedMessageLink.html delete mode 100644 data/core.telegram.org/type/FileHash.html delete mode 100644 data/core.telegram.org/type/FileLocation.html delete mode 100644 data/core.telegram.org/type/Folder.html delete mode 100644 data/core.telegram.org/type/FolderPeer.html delete mode 100644 data/core.telegram.org/type/Game.html delete mode 100644 data/core.telegram.org/type/GeoPoint.html delete mode 100644 data/core.telegram.org/type/GlobalPrivacySettings.html delete mode 100644 data/core.telegram.org/type/GroupCall.html delete mode 100644 data/core.telegram.org/type/GroupCallParticipant.html delete mode 100644 data/core.telegram.org/type/GroupCallParticipantVideo.html delete mode 100644 data/core.telegram.org/type/GroupCallParticipantVideoSourceGroup.html delete mode 100644 data/core.telegram.org/type/HighScore.html delete mode 100644 data/core.telegram.org/type/InlineBotSwitchPM.html delete mode 100644 data/core.telegram.org/type/InlineQueryPeerType.html delete mode 100644 data/core.telegram.org/type/InputAppEvent.html delete mode 100644 data/core.telegram.org/type/InputBotInlineMessage.html delete mode 100644 data/core.telegram.org/type/InputBotInlineMessageID.html delete mode 100644 data/core.telegram.org/type/InputBotInlineResult.html delete mode 100644 data/core.telegram.org/type/InputChannel.html delete mode 100644 data/core.telegram.org/type/InputChatPhoto.html delete mode 100644 data/core.telegram.org/type/InputCheckPasswordSRP.html delete mode 100644 data/core.telegram.org/type/InputContact.html delete mode 100644 data/core.telegram.org/type/InputDialogPeer.html delete mode 100644 data/core.telegram.org/type/InputDocument.html delete mode 100644 data/core.telegram.org/type/InputEncryptedChat.html delete mode 100644 data/core.telegram.org/type/InputEncryptedFile.html delete mode 100644 data/core.telegram.org/type/InputFile.html delete mode 100644 data/core.telegram.org/type/InputFileLocation.html delete mode 100644 data/core.telegram.org/type/InputGame.html delete mode 100644 data/core.telegram.org/type/InputGeoPoint.html delete mode 100644 data/core.telegram.org/type/InputGroupCall.html delete mode 100644 data/core.telegram.org/type/InputMedia.html delete mode 100644 data/core.telegram.org/type/InputMessage.html delete mode 100644 data/core.telegram.org/type/InputNotifyPeer.html delete mode 100644 data/core.telegram.org/type/InputPaymentCredentials.html delete mode 100644 data/core.telegram.org/type/InputPeer.html delete mode 100644 data/core.telegram.org/type/InputPeerNotifySettings.html delete mode 100644 data/core.telegram.org/type/InputPhoneCall.html delete mode 100644 data/core.telegram.org/type/InputPhoto.html delete mode 100644 data/core.telegram.org/type/InputPrivacyKey.html delete mode 100644 data/core.telegram.org/type/InputPrivacyRule.html delete mode 100644 data/core.telegram.org/type/InputSecureFile.html delete mode 100644 data/core.telegram.org/type/InputSecureValue.html delete mode 100644 data/core.telegram.org/type/InputStickerSet.html delete mode 100644 data/core.telegram.org/type/InputStickerSetItem.html delete mode 100644 data/core.telegram.org/type/InputStickeredMedia.html delete mode 100644 data/core.telegram.org/type/InputTheme.html delete mode 100644 data/core.telegram.org/type/InputThemeSettings.html delete mode 100644 data/core.telegram.org/type/InputUser.html delete mode 100644 data/core.telegram.org/type/InputWallPaper.html delete mode 100644 data/core.telegram.org/type/InputWebFileLocation.html delete mode 100644 data/core.telegram.org/type/Invoice.html delete mode 100644 data/core.telegram.org/type/JSONObjectValue.html delete mode 100644 data/core.telegram.org/type/JSONValue.html delete mode 100644 data/core.telegram.org/type/KeyboardButton.html delete mode 100644 data/core.telegram.org/type/KeyboardButtonRow.html delete mode 100644 data/core.telegram.org/type/LabeledPrice.html delete mode 100644 data/core.telegram.org/type/LangPackDifference.html delete mode 100644 data/core.telegram.org/type/LangPackLanguage.html delete mode 100644 data/core.telegram.org/type/LangPackString.html delete mode 100644 data/core.telegram.org/type/MaskCoords.html delete mode 100644 data/core.telegram.org/type/Message.html delete mode 100644 data/core.telegram.org/type/MessageAction.html delete mode 100644 data/core.telegram.org/type/MessageEntity.html delete mode 100644 data/core.telegram.org/type/MessageFwdHeader.html delete mode 100644 data/core.telegram.org/type/MessageInteractionCounters.html delete mode 100644 data/core.telegram.org/type/MessageMedia.html delete mode 100644 data/core.telegram.org/type/MessageRange.html delete mode 100644 data/core.telegram.org/type/MessageReactionsList.html delete mode 100644 data/core.telegram.org/type/MessageReplies.html delete mode 100644 data/core.telegram.org/type/MessageReplyHeader.html delete mode 100644 data/core.telegram.org/type/MessageUserVote.html delete mode 100644 data/core.telegram.org/type/MessageViews.html delete mode 100644 data/core.telegram.org/type/MessagesFilter.html delete mode 100644 data/core.telegram.org/type/NotifyPeer.html delete mode 100644 data/core.telegram.org/type/Null.html delete mode 100644 data/core.telegram.org/type/Page.html delete mode 100644 data/core.telegram.org/type/PageBlock.html delete mode 100644 data/core.telegram.org/type/PageCaption.html delete mode 100644 data/core.telegram.org/type/PageListItem.html delete mode 100644 data/core.telegram.org/type/PageListOrderedItem.html delete mode 100644 data/core.telegram.org/type/PageRelatedArticle.html delete mode 100644 data/core.telegram.org/type/PageTableCell.html delete mode 100644 data/core.telegram.org/type/PageTableRow.html delete mode 100644 data/core.telegram.org/type/PasswordKdfAlgo.html delete mode 100644 data/core.telegram.org/type/PaymentCharge.html delete mode 100644 data/core.telegram.org/type/PaymentRequestedInfo.html delete mode 100644 data/core.telegram.org/type/PaymentSavedCredentials.html delete mode 100644 data/core.telegram.org/type/Peer.html delete mode 100644 data/core.telegram.org/type/PeerBlocked.html delete mode 100644 data/core.telegram.org/type/PeerLocated.html delete mode 100644 data/core.telegram.org/type/PeerNotifySettings.html delete mode 100644 data/core.telegram.org/type/PeerSettings.html delete mode 100644 data/core.telegram.org/type/PhoneCall.html delete mode 100644 data/core.telegram.org/type/PhoneCallDiscardReason.html delete mode 100644 data/core.telegram.org/type/PhoneCallProtocol.html delete mode 100644 data/core.telegram.org/type/Photo.html delete mode 100644 data/core.telegram.org/type/PhotoSize.html delete mode 100644 data/core.telegram.org/type/Poll.html delete mode 100644 data/core.telegram.org/type/PollAnswer.html delete mode 100644 data/core.telegram.org/type/PollAnswerVoters.html delete mode 100644 data/core.telegram.org/type/PollResults.html delete mode 100644 data/core.telegram.org/type/PopularContact.html delete mode 100644 data/core.telegram.org/type/PostAddress.html delete mode 100644 data/core.telegram.org/type/PrivacyKey.html delete mode 100644 data/core.telegram.org/type/PrivacyRule.html delete mode 100644 data/core.telegram.org/type/ReceivedNotifyMessage.html delete mode 100644 data/core.telegram.org/type/ReplyMarkup.html delete mode 100644 data/core.telegram.org/type/ReportReason.html delete mode 100644 data/core.telegram.org/type/RestrictionReason.html delete mode 100644 data/core.telegram.org/type/RichText.html delete mode 100644 data/core.telegram.org/type/SavedContact.html delete mode 100644 data/core.telegram.org/type/SecureCredentialsEncrypted.html delete mode 100644 data/core.telegram.org/type/SecureData.html delete mode 100644 data/core.telegram.org/type/SecureFile.html delete mode 100644 data/core.telegram.org/type/SecurePasswordKdfAlgo.html delete mode 100644 data/core.telegram.org/type/SecurePlainData.html delete mode 100644 data/core.telegram.org/type/SecureRequiredType.html delete mode 100644 data/core.telegram.org/type/SecureSecretSettings.html delete mode 100644 data/core.telegram.org/type/SecureValue.html delete mode 100644 data/core.telegram.org/type/SecureValueError.html delete mode 100644 data/core.telegram.org/type/SecureValueHash.html delete mode 100644 data/core.telegram.org/type/SecureValueType.html delete mode 100644 data/core.telegram.org/type/SendMessageAction.html delete mode 100644 data/core.telegram.org/type/ShippingOption.html delete mode 100644 data/core.telegram.org/type/SponsoredMessage.html delete mode 100644 data/core.telegram.org/type/StatsAbsValueAndPrev.html delete mode 100644 data/core.telegram.org/type/StatsGraph.html delete mode 100644 data/core.telegram.org/type/StatsGroupTopAdmin.html delete mode 100644 data/core.telegram.org/type/StatsGroupTopInviter.html delete mode 100644 data/core.telegram.org/type/StatsGroupTopPoster.html delete mode 100644 data/core.telegram.org/type/StatsPercentValue.html delete mode 100644 data/core.telegram.org/type/StatsURL.html delete mode 100644 data/core.telegram.org/type/StickerPack.html delete mode 100644 data/core.telegram.org/type/StickerSet.html delete mode 100644 data/core.telegram.org/type/StickerSetCovered.html delete mode 100644 data/core.telegram.org/type/Theme.html delete mode 100644 data/core.telegram.org/type/ThemeSettings.html delete mode 100644 data/core.telegram.org/type/TopPeer.html delete mode 100644 data/core.telegram.org/type/TopPeerCategory.html delete mode 100644 data/core.telegram.org/type/TopPeerCategoryPeers.html delete mode 100644 data/core.telegram.org/type/True.html delete mode 100644 data/core.telegram.org/type/Update.html delete mode 100644 data/core.telegram.org/type/Updates.html delete mode 100644 data/core.telegram.org/type/UrlAuthResult.html delete mode 100644 data/core.telegram.org/type/User.html delete mode 100644 data/core.telegram.org/type/UserFull.html delete mode 100644 data/core.telegram.org/type/UserProfilePhoto.html delete mode 100644 data/core.telegram.org/type/UserStatus.html delete mode 100644 data/core.telegram.org/type/Vector t.html delete mode 100644 data/core.telegram.org/type/Video.html delete mode 100644 data/core.telegram.org/type/VideoSize.html delete mode 100644 data/core.telegram.org/type/WallPaper.html delete mode 100644 data/core.telegram.org/type/WallPaperSettings.html delete mode 100644 data/core.telegram.org/type/WebAuthorization.html delete mode 100644 data/core.telegram.org/type/WebDocument.html delete mode 100644 data/core.telegram.org/type/WebPage.html delete mode 100644 data/core.telegram.org/type/WebPageAttribute.html delete mode 100644 data/core.telegram.org/type/account.AuthorizationForm delete mode 100644 data/core.telegram.org/type/account.Authorizations delete mode 100644 data/core.telegram.org/type/account.AutoDownloadSettings delete mode 100644 data/core.telegram.org/type/account.ChatThemes delete mode 100644 data/core.telegram.org/type/account.ContentSettings delete mode 100644 data/core.telegram.org/type/account.Password delete mode 100644 data/core.telegram.org/type/account.PasswordInputSettings delete mode 100644 data/core.telegram.org/type/account.PasswordSettings delete mode 100644 data/core.telegram.org/type/account.PrivacyRules delete mode 100644 data/core.telegram.org/type/account.ResetPasswordResult delete mode 100644 data/core.telegram.org/type/account.SentChangePhoneCode delete mode 100644 data/core.telegram.org/type/account.SentEmailCode delete mode 100644 data/core.telegram.org/type/account.Takeout delete mode 100644 data/core.telegram.org/type/account.Themes delete mode 100644 data/core.telegram.org/type/account.TmpPassword delete mode 100644 data/core.telegram.org/type/account.WallPapers delete mode 100644 data/core.telegram.org/type/account.WebAuthorizations delete mode 100644 data/core.telegram.org/type/auth.Authorization delete mode 100644 data/core.telegram.org/type/auth.CheckedPhone delete mode 100644 data/core.telegram.org/type/auth.CodeType delete mode 100644 data/core.telegram.org/type/auth.ExportedAuthorization delete mode 100644 data/core.telegram.org/type/auth.LoginToken delete mode 100644 data/core.telegram.org/type/auth.PasswordRecovery delete mode 100644 data/core.telegram.org/type/auth.SentCode delete mode 100644 data/core.telegram.org/type/auth.SentCodeType delete mode 100644 data/core.telegram.org/type/bytes.html delete mode 100644 data/core.telegram.org/type/channels.AdminLogResults delete mode 100644 data/core.telegram.org/type/channels.ChannelParticipant delete mode 100644 data/core.telegram.org/type/channels.ChannelParticipants delete mode 100644 data/core.telegram.org/type/contacts.Blocked delete mode 100644 data/core.telegram.org/type/contacts.Contacts delete mode 100644 data/core.telegram.org/type/contacts.Found delete mode 100644 data/core.telegram.org/type/contacts.ImportedContacts delete mode 100644 data/core.telegram.org/type/contacts.Link delete mode 100644 data/core.telegram.org/type/contacts.ResolvedPeer delete mode 100644 data/core.telegram.org/type/contacts.TopPeers delete mode 100644 data/core.telegram.org/type/double.html delete mode 100644 data/core.telegram.org/type/help.AppUpdate delete mode 100644 data/core.telegram.org/type/help.CountriesList delete mode 100644 data/core.telegram.org/type/help.CountryCode delete mode 100644 data/core.telegram.org/type/help.PassportConfig delete mode 100644 data/core.telegram.org/type/help.PromoData delete mode 100644 data/core.telegram.org/type/help.ProxyData delete mode 100644 data/core.telegram.org/type/help.Support delete mode 100644 data/core.telegram.org/type/help.SupportName delete mode 100644 data/core.telegram.org/type/help.TermsOfService delete mode 100644 data/core.telegram.org/type/help.TermsOfServiceUpdate delete mode 100644 data/core.telegram.org/type/help.UserInfo delete mode 100644 data/core.telegram.org/type/int.html delete mode 100644 data/core.telegram.org/type/messages.AffectedFoundMessages delete mode 100644 data/core.telegram.org/type/messages.AffectedHistory delete mode 100644 data/core.telegram.org/type/messages.AffectedMessages delete mode 100644 data/core.telegram.org/type/messages.AllStickers delete mode 100644 data/core.telegram.org/type/messages.ArchivedStickers delete mode 100644 data/core.telegram.org/type/messages.BotCallbackAnswer delete mode 100644 data/core.telegram.org/type/messages.BotResults delete mode 100644 data/core.telegram.org/type/messages.ChatFull delete mode 100644 data/core.telegram.org/type/messages.ChatInviteImporters delete mode 100644 data/core.telegram.org/type/messages.Chats delete mode 100644 data/core.telegram.org/type/messages.CheckedHistoryImportPeer delete mode 100644 data/core.telegram.org/type/messages.DhConfig delete mode 100644 data/core.telegram.org/type/messages.Dialogs delete mode 100644 data/core.telegram.org/type/messages.DiscussionMessage delete mode 100644 data/core.telegram.org/type/messages.ExportedChatInvite delete mode 100644 data/core.telegram.org/type/messages.ExportedChatInvites delete mode 100644 data/core.telegram.org/type/messages.FavedStickers delete mode 100644 data/core.telegram.org/type/messages.FeaturedStickers delete mode 100644 data/core.telegram.org/type/messages.FoundGifs delete mode 100644 data/core.telegram.org/type/messages.FoundStickerSets delete mode 100644 data/core.telegram.org/type/messages.HighScores delete mode 100644 data/core.telegram.org/type/messages.HistoryImport delete mode 100644 data/core.telegram.org/type/messages.HistoryImportParsed delete mode 100644 data/core.telegram.org/type/messages.MessageEditData delete mode 100644 data/core.telegram.org/type/messages.MessageViews delete mode 100644 data/core.telegram.org/type/messages.PeerDialogs delete mode 100644 data/core.telegram.org/type/messages.RecentStickers delete mode 100644 data/core.telegram.org/type/messages.SavedGifs delete mode 100644 data/core.telegram.org/type/messages.SearchCounter delete mode 100644 data/core.telegram.org/type/messages.SentEncryptedMessage delete mode 100644 data/core.telegram.org/type/messages.SentMessage delete mode 100644 data/core.telegram.org/type/messages.SponsoredMessages delete mode 100644 data/core.telegram.org/type/messages.StatedMessage delete mode 100644 data/core.telegram.org/type/messages.StatedMessages delete mode 100644 data/core.telegram.org/type/messages.StickerSet delete mode 100644 data/core.telegram.org/type/messages.StickerSetInstallResult delete mode 100644 data/core.telegram.org/type/messages.Stickers delete mode 100644 data/core.telegram.org/type/messages.VotesList delete mode 100644 data/core.telegram.org/type/payments.BankCardData delete mode 100644 data/core.telegram.org/type/payments.PaymentForm delete mode 100644 data/core.telegram.org/type/payments.PaymentReceipt delete mode 100644 data/core.telegram.org/type/payments.PaymentResult delete mode 100644 data/core.telegram.org/type/payments.SavedInfo delete mode 100644 data/core.telegram.org/type/payments.ValidatedRequestedInfo delete mode 100644 data/core.telegram.org/type/phone.ExportedGroupCallInvite delete mode 100644 data/core.telegram.org/type/phone.GroupCall delete mode 100644 data/core.telegram.org/type/phone.GroupParticipants delete mode 100644 data/core.telegram.org/type/phone.JoinAsPeers delete mode 100644 data/core.telegram.org/type/photos.Photo delete mode 100644 data/core.telegram.org/type/photos.Photos delete mode 100644 data/core.telegram.org/type/stats.BroadcastStats delete mode 100644 data/core.telegram.org/type/stats.MegagroupStats delete mode 100644 data/core.telegram.org/type/stats.MessageStats delete mode 100644 data/core.telegram.org/type/stickers.SuggestedShortName delete mode 100644 data/core.telegram.org/type/storage.FileType delete mode 100644 data/core.telegram.org/type/string.html delete mode 100644 data/core.telegram.org/type/updates.ChannelDifference delete mode 100644 data/core.telegram.org/type/updates.Difference delete mode 100644 data/core.telegram.org/type/updates.State delete mode 100644 data/core.telegram.org/type/upload.CdnFile delete mode 100644 data/core.telegram.org/type/upload.File delete mode 100644 data/core.telegram.org/type/upload.WebFile delete mode 100644 data/core.telegram.org/video_stickers.html delete mode 100644 data/core.telegram.org/widgets.html delete mode 100644 data/core.telegram.org/widgets/discussion.html delete mode 100644 data/core.telegram.org/widgets/login.html delete mode 100644 data/core.telegram.org/widgets/post.html delete mode 100644 data/core.telegram.org/widgets/share.html delete mode 100644 data/corefork.telegram.org/api.html delete mode 100644 data/corefork.telegram.org/api/account-deletion.html delete mode 100644 data/corefork.telegram.org/api/animated-emojis.html delete mode 100644 data/corefork.telegram.org/api/auth.html delete mode 100644 data/corefork.telegram.org/api/bots.html delete mode 100644 data/corefork.telegram.org/api/bots/buttons.html delete mode 100644 data/corefork.telegram.org/api/bots/commands.html delete mode 100644 data/corefork.telegram.org/api/bots/games.html delete mode 100644 data/corefork.telegram.org/api/bots/inline.html delete mode 100644 data/corefork.telegram.org/api/channel.html delete mode 100644 data/corefork.telegram.org/api/config.html delete mode 100644 data/corefork.telegram.org/api/datacenter.html delete mode 100644 data/corefork.telegram.org/api/dice.html delete mode 100644 data/corefork.telegram.org/api/discussion.html delete mode 100644 data/corefork.telegram.org/api/drafts.html delete mode 100644 data/corefork.telegram.org/api/end-to-end.html delete mode 100644 data/corefork.telegram.org/api/end-to-end/pfs.html delete mode 100644 data/corefork.telegram.org/api/end-to-end/seq_no.html delete mode 100644 data/corefork.telegram.org/api/end-to-end/video-calls.html delete mode 100644 data/corefork.telegram.org/api/end-to-end/voice-calls.html delete mode 100644 data/corefork.telegram.org/api/end-to-end_v1.html delete mode 100644 data/corefork.telegram.org/api/errors.html delete mode 100644 data/corefork.telegram.org/api/files.html delete mode 100644 data/corefork.telegram.org/api/folders.html delete mode 100644 data/corefork.telegram.org/api/geochats.html delete mode 100644 data/corefork.telegram.org/api/import.html delete mode 100644 data/corefork.telegram.org/api/invoking.html delete mode 100644 data/corefork.telegram.org/api/live-location.html delete mode 100644 data/corefork.telegram.org/api/mentions.html delete mode 100644 data/corefork.telegram.org/api/min.html delete mode 100644 data/corefork.telegram.org/api/obtaining_api_id.html delete mode 100644 data/corefork.telegram.org/api/offsets.html delete mode 100644 data/corefork.telegram.org/api/optimisation.html delete mode 100644 data/corefork.telegram.org/api/passport.html delete mode 100644 data/corefork.telegram.org/api/pattern.html delete mode 100644 data/corefork.telegram.org/api/payments.html delete mode 100644 data/corefork.telegram.org/api/pfs.html delete mode 100644 data/corefork.telegram.org/api/pin.html delete mode 100644 data/corefork.telegram.org/api/poll.html delete mode 100644 data/corefork.telegram.org/api/push-updates.html delete mode 100644 data/corefork.telegram.org/api/qr-login.html delete mode 100644 data/corefork.telegram.org/api/recent-actions.html delete mode 100644 data/corefork.telegram.org/api/rights.html delete mode 100644 data/corefork.telegram.org/api/scheduled-messages.html delete mode 100644 data/corefork.telegram.org/api/search.html delete mode 100644 data/corefork.telegram.org/api/sponsored-messages.html delete mode 100644 data/corefork.telegram.org/api/srp.html delete mode 100644 data/corefork.telegram.org/api/stats.html delete mode 100644 data/corefork.telegram.org/api/terms.html delete mode 100644 data/corefork.telegram.org/api/top-rating.html delete mode 100644 data/corefork.telegram.org/api/updates.html delete mode 100644 data/corefork.telegram.org/api/url-authorization.html delete mode 100644 data/corefork.telegram.org/api/web-events.html delete mode 100644 data/corefork.telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html delete mode 100644 data/corefork.telegram.org/bots.html delete mode 100644 data/corefork.telegram.org/bots/2-0-intro.html delete mode 100644 data/corefork.telegram.org/bots/api-changelog.html delete mode 100644 data/corefork.telegram.org/bots/api.html delete mode 100644 data/corefork.telegram.org/bots/faq.html delete mode 100644 data/corefork.telegram.org/bots/inline.html delete mode 100644 data/corefork.telegram.org/bots/samples.html delete mode 100644 data/corefork.telegram.org/bots/samples/hellobot.html delete mode 100644 data/corefork.telegram.org/bots/self-signed.html delete mode 100644 data/corefork.telegram.org/bots/webhooks.html delete mode 100644 data/corefork.telegram.org/cdn.html delete mode 100644 data/corefork.telegram.org/constructor/account.authorizationForm delete mode 100644 data/corefork.telegram.org/constructor/account.authorizations delete mode 100644 data/corefork.telegram.org/constructor/account.autoDownloadSettings delete mode 100644 data/corefork.telegram.org/constructor/account.chatThemes delete mode 100644 data/corefork.telegram.org/constructor/account.chatThemesNotModified delete mode 100644 data/corefork.telegram.org/constructor/account.contentSettings delete mode 100644 data/corefork.telegram.org/constructor/account.password delete mode 100644 data/corefork.telegram.org/constructor/account.passwordInputSettings delete mode 100644 data/corefork.telegram.org/constructor/account.passwordSettings delete mode 100644 data/corefork.telegram.org/constructor/account.privacyRules delete mode 100644 data/corefork.telegram.org/constructor/account.resetPasswordRequestedWait delete mode 100644 data/corefork.telegram.org/constructor/account.sentChangePhoneCode delete mode 100644 data/corefork.telegram.org/constructor/account.sentEmailCode delete mode 100644 data/corefork.telegram.org/constructor/account.takeout delete mode 100644 data/corefork.telegram.org/constructor/account.themes delete mode 100644 data/corefork.telegram.org/constructor/account.themesNotModified delete mode 100644 data/corefork.telegram.org/constructor/account.tmpPassword delete mode 100644 data/corefork.telegram.org/constructor/account.wallPapers delete mode 100644 data/corefork.telegram.org/constructor/account.wallPapersNotModified delete mode 100644 data/corefork.telegram.org/constructor/account.webAuthorizations delete mode 100644 data/corefork.telegram.org/constructor/auth.authorization delete mode 100644 data/corefork.telegram.org/constructor/auth.authorizationSignUpRequired delete mode 100644 data/corefork.telegram.org/constructor/auth.codeTypeCall delete mode 100644 data/corefork.telegram.org/constructor/auth.codeTypeFlashCall delete mode 100644 data/corefork.telegram.org/constructor/auth.codeTypeSms delete mode 100644 data/corefork.telegram.org/constructor/auth.exportedAuthorization delete mode 100644 data/corefork.telegram.org/constructor/auth.loginToken delete mode 100644 data/corefork.telegram.org/constructor/auth.loginTokenMigrateTo delete mode 100644 data/corefork.telegram.org/constructor/auth.loginTokenSuccess delete mode 100644 data/corefork.telegram.org/constructor/auth.passwordRecovery delete mode 100644 data/corefork.telegram.org/constructor/auth.sentCode delete mode 100644 data/corefork.telegram.org/constructor/auth.sentCodeTypeApp delete mode 100644 data/corefork.telegram.org/constructor/auth.sentCodeTypeCall delete mode 100644 data/corefork.telegram.org/constructor/auth.sentCodeTypeFlashCall delete mode 100644 data/corefork.telegram.org/constructor/auth.sentCodeTypeSms delete mode 100644 data/corefork.telegram.org/constructor/authorization.html delete mode 100644 data/corefork.telegram.org/constructor/bankCardOpenUrl.html delete mode 100644 data/corefork.telegram.org/constructor/baseThemeArctic.html delete mode 100644 data/corefork.telegram.org/constructor/baseThemeClassic.html delete mode 100644 data/corefork.telegram.org/constructor/baseThemeDay.html delete mode 100644 data/corefork.telegram.org/constructor/baseThemeNight.html delete mode 100644 data/corefork.telegram.org/constructor/baseThemeTinted.html delete mode 100644 data/corefork.telegram.org/constructor/boolFalse.html delete mode 100644 data/corefork.telegram.org/constructor/boolTrue.html delete mode 100644 data/corefork.telegram.org/constructor/botCommand.html delete mode 100644 data/corefork.telegram.org/constructor/botCommandScopeChats.html delete mode 100644 data/corefork.telegram.org/constructor/botCommandScopeDefault.html delete mode 100644 data/corefork.telegram.org/constructor/botCommandScopePeer.html delete mode 100644 data/corefork.telegram.org/constructor/botCommandScopePeerAdmins.html delete mode 100644 data/corefork.telegram.org/constructor/botCommandScopePeerUser.html delete mode 100644 data/corefork.telegram.org/constructor/botCommandScopeUsers.html delete mode 100644 data/corefork.telegram.org/constructor/botInfo.html delete mode 100644 data/corefork.telegram.org/constructor/botInlineMediaResult.html delete mode 100644 data/corefork.telegram.org/constructor/botInlineMessageMediaAuto.html delete mode 100644 data/corefork.telegram.org/constructor/botInlineMessageMediaContact.html delete mode 100644 data/corefork.telegram.org/constructor/botInlineMessageMediaInvoice.html delete mode 100644 data/corefork.telegram.org/constructor/botInlineMessageMediaVenue.html delete mode 100644 data/corefork.telegram.org/constructor/botInlineMessageText.html delete mode 100644 data/corefork.telegram.org/constructor/botInlineResult.html delete mode 100644 data/corefork.telegram.org/constructor/cdnConfig.html delete mode 100644 data/corefork.telegram.org/constructor/cdnPublicKey.html delete mode 100644 data/corefork.telegram.org/constructor/channel.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEvent.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeAbout.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeHistoryTTL.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionChangePhoto.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeTitle.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionDefaultBannedRights.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionDeleteMessage.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionDiscardGroupCall.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionEditMessage.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteDelete.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteEdit.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteRevoke.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantInvite.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantLeave.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantMute.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantToggleAdmin.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantToggleBan.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantUnmute.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantVolume.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionStartGroupCall.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionStopPoll.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleInvites.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionTogglePreHistoryHidden.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleSignatures.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleSlowMode.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionUpdatePinned.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventsFilter.html delete mode 100644 data/corefork.telegram.org/constructor/channelForbidden.html delete mode 100644 data/corefork.telegram.org/constructor/channelFull.html delete mode 100644 data/corefork.telegram.org/constructor/channelLocation.html delete mode 100644 data/corefork.telegram.org/constructor/channelLocationEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/channelMessagesFilter.html delete mode 100644 data/corefork.telegram.org/constructor/channelMessagesFilterEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/channelParticipant.html delete mode 100644 data/corefork.telegram.org/constructor/channelParticipantAdmin.html delete mode 100644 data/corefork.telegram.org/constructor/channelParticipantBanned.html delete mode 100644 data/corefork.telegram.org/constructor/channelParticipantCreator.html delete mode 100644 data/corefork.telegram.org/constructor/channelParticipantLeft.html delete mode 100644 data/corefork.telegram.org/constructor/channelParticipantSelf.html delete mode 100644 data/corefork.telegram.org/constructor/channelParticipantsAdmins.html delete mode 100644 data/corefork.telegram.org/constructor/channelParticipantsBanned.html delete mode 100644 data/corefork.telegram.org/constructor/channelParticipantsBots.html delete mode 100644 data/corefork.telegram.org/constructor/channelParticipantsContacts.html delete mode 100644 data/corefork.telegram.org/constructor/channelParticipantsKicked.html delete mode 100644 data/corefork.telegram.org/constructor/channelParticipantsMentions.html delete mode 100644 data/corefork.telegram.org/constructor/channelParticipantsRecent.html delete mode 100644 data/corefork.telegram.org/constructor/channelParticipantsSearch.html delete mode 100644 data/corefork.telegram.org/constructor/channels.adminLogResults delete mode 100644 data/corefork.telegram.org/constructor/channels.channelParticipants delete mode 100644 data/corefork.telegram.org/constructor/channels.channelParticipantsNotModified delete mode 100644 data/corefork.telegram.org/constructor/chat.html delete mode 100644 data/corefork.telegram.org/constructor/chatAdminRights.html delete mode 100644 data/corefork.telegram.org/constructor/chatAdminWithInvites.html delete mode 100644 data/corefork.telegram.org/constructor/chatBannedRights.html delete mode 100644 data/corefork.telegram.org/constructor/chatEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/chatForbidden.html delete mode 100644 data/corefork.telegram.org/constructor/chatFull.html delete mode 100644 data/corefork.telegram.org/constructor/chatInvite.html delete mode 100644 data/corefork.telegram.org/constructor/chatInviteAlready.html delete mode 100644 data/corefork.telegram.org/constructor/chatInviteExported.html delete mode 100644 data/corefork.telegram.org/constructor/chatInvitePeek.html delete mode 100644 data/corefork.telegram.org/constructor/chatOnlines.html delete mode 100644 data/corefork.telegram.org/constructor/chatParticipant.html delete mode 100644 data/corefork.telegram.org/constructor/chatParticipantAdmin.html delete mode 100644 data/corefork.telegram.org/constructor/chatParticipantCreator.html delete mode 100644 data/corefork.telegram.org/constructor/chatParticipants.html delete mode 100644 data/corefork.telegram.org/constructor/chatParticipantsForbidden.html delete mode 100644 data/corefork.telegram.org/constructor/chatPhoto.html delete mode 100644 data/corefork.telegram.org/constructor/chatPhotoEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/chatTheme.html delete mode 100644 data/corefork.telegram.org/constructor/codeSettings.html delete mode 100644 data/corefork.telegram.org/constructor/config.html delete mode 100644 data/corefork.telegram.org/constructor/contact.html delete mode 100644 data/corefork.telegram.org/constructor/contactStatus.html delete mode 100644 data/corefork.telegram.org/constructor/contacts.blocked delete mode 100644 data/corefork.telegram.org/constructor/contacts.blockedSlice delete mode 100644 data/corefork.telegram.org/constructor/contacts.contacts delete mode 100644 data/corefork.telegram.org/constructor/contacts.contactsNotModified delete mode 100644 data/corefork.telegram.org/constructor/contacts.found delete mode 100644 data/corefork.telegram.org/constructor/contacts.importedContacts delete mode 100644 data/corefork.telegram.org/constructor/contacts.resolvedPeer delete mode 100644 data/corefork.telegram.org/constructor/contacts.topPeers delete mode 100644 data/corefork.telegram.org/constructor/contacts.topPeersDisabled delete mode 100644 data/corefork.telegram.org/constructor/contacts.topPeersNotModified delete mode 100644 data/corefork.telegram.org/constructor/dataJSON.html delete mode 100644 data/corefork.telegram.org/constructor/dcOption.html delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessage.html delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionCommitKey.html delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionDeleteMessages.html delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionFlushHistory.html delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionNotifyLayer.html delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionReadMessages.html delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionRequestKey.html delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionResend.html delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionScreenshotMessages.html delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionSetMessageTTL.html delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessageActionTyping.html delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessageLayer.html delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaAudio.html delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaContact.html delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaDocument.html delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaExternalDocument.html delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaGeoPoint.html delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaPhoto.html delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaVenue.html delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaVideo.html delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessageMediaWebPage.html delete mode 100644 data/corefork.telegram.org/constructor/decryptedMessageService.html delete mode 100644 data/corefork.telegram.org/constructor/dialogFilter.html delete mode 100644 data/corefork.telegram.org/constructor/dialogFilterSuggested.html delete mode 100644 data/corefork.telegram.org/constructor/dialogFolder.html delete mode 100644 data/corefork.telegram.org/constructor/dialogPeer.html delete mode 100644 data/corefork.telegram.org/constructor/dialogPeerFolder.html delete mode 100644 data/corefork.telegram.org/constructor/document.html delete mode 100644 data/corefork.telegram.org/constructor/documentAttributeAnimated.html delete mode 100644 data/corefork.telegram.org/constructor/documentAttributeAudio.html delete mode 100644 data/corefork.telegram.org/constructor/documentAttributeFilename.html delete mode 100644 data/corefork.telegram.org/constructor/documentAttributeHasStickers.html delete mode 100644 data/corefork.telegram.org/constructor/documentAttributeImageSize.html delete mode 100644 data/corefork.telegram.org/constructor/documentAttributeSticker.html delete mode 100644 data/corefork.telegram.org/constructor/documentAttributeVideo.html delete mode 100644 data/corefork.telegram.org/constructor/documentEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/draftMessage.html delete mode 100644 data/corefork.telegram.org/constructor/draftMessageEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/emojiKeyword.html delete mode 100644 data/corefork.telegram.org/constructor/emojiKeywordDeleted.html delete mode 100644 data/corefork.telegram.org/constructor/emojiKeywordsDifference.html delete mode 100644 data/corefork.telegram.org/constructor/emojiLanguage.html delete mode 100644 data/corefork.telegram.org/constructor/emojiURL.html delete mode 100644 data/corefork.telegram.org/constructor/encryptedChat.html delete mode 100644 data/corefork.telegram.org/constructor/encryptedChatDiscarded.html delete mode 100644 data/corefork.telegram.org/constructor/encryptedChatEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/encryptedChatRequested.html delete mode 100644 data/corefork.telegram.org/constructor/encryptedChatWaiting.html delete mode 100644 data/corefork.telegram.org/constructor/encryptedFile.html delete mode 100644 data/corefork.telegram.org/constructor/encryptedFileEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/encryptedMessage.html delete mode 100644 data/corefork.telegram.org/constructor/encryptedMessageService.html delete mode 100644 data/corefork.telegram.org/constructor/error.html delete mode 100644 data/corefork.telegram.org/constructor/exportedMessageLink.html delete mode 100644 data/corefork.telegram.org/constructor/fileHash.html delete mode 100644 data/corefork.telegram.org/constructor/fileLocationUnavailable.html delete mode 100644 data/corefork.telegram.org/constructor/folder.html delete mode 100644 data/corefork.telegram.org/constructor/folderPeer.html delete mode 100644 data/corefork.telegram.org/constructor/game.html delete mode 100644 data/corefork.telegram.org/constructor/geoPoint.html delete mode 100644 data/corefork.telegram.org/constructor/geoPointEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/globalPrivacySettings.html delete mode 100644 data/corefork.telegram.org/constructor/groupCall.html delete mode 100644 data/corefork.telegram.org/constructor/groupCallDiscarded.html delete mode 100644 data/corefork.telegram.org/constructor/groupCallParticipant.html delete mode 100644 data/corefork.telegram.org/constructor/groupCallParticipantVideo.html delete mode 100644 data/corefork.telegram.org/constructor/groupCallParticipantVideoSourceGroup.html delete mode 100644 data/corefork.telegram.org/constructor/help.appUpdate delete mode 100644 data/corefork.telegram.org/constructor/help.countriesList delete mode 100644 data/corefork.telegram.org/constructor/help.countriesListNotModified delete mode 100644 data/corefork.telegram.org/constructor/help.country delete mode 100644 data/corefork.telegram.org/constructor/help.countryCode delete mode 100644 data/corefork.telegram.org/constructor/help.deepLinkInfo delete mode 100644 data/corefork.telegram.org/constructor/help.deepLinkInfoEmpty delete mode 100644 data/corefork.telegram.org/constructor/help.inviteText delete mode 100644 data/corefork.telegram.org/constructor/help.noAppUpdate delete mode 100644 data/corefork.telegram.org/constructor/help.passportConfig delete mode 100644 data/corefork.telegram.org/constructor/help.passportConfigNotModified delete mode 100644 data/corefork.telegram.org/constructor/help.promoData delete mode 100644 data/corefork.telegram.org/constructor/help.promoDataEmpty delete mode 100644 data/corefork.telegram.org/constructor/help.recentMeUrls delete mode 100644 data/corefork.telegram.org/constructor/help.support delete mode 100644 data/corefork.telegram.org/constructor/help.supportName delete mode 100644 data/corefork.telegram.org/constructor/help.termsOfService delete mode 100644 data/corefork.telegram.org/constructor/help.termsOfServiceUpdate delete mode 100644 data/corefork.telegram.org/constructor/help.termsOfServiceUpdateEmpty delete mode 100644 data/corefork.telegram.org/constructor/help.userInfo delete mode 100644 data/corefork.telegram.org/constructor/help.userInfoEmpty delete mode 100644 data/corefork.telegram.org/constructor/highScore.html delete mode 100644 data/corefork.telegram.org/constructor/importedContact.html delete mode 100644 data/corefork.telegram.org/constructor/inlineBotSwitchPM.html delete mode 100644 data/corefork.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html delete mode 100644 data/corefork.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html delete mode 100644 data/corefork.telegram.org/constructor/inlineQueryPeerTypePM.html delete mode 100644 data/corefork.telegram.org/constructor/inlineQueryPeerTypeSameBotPM.html delete mode 100644 data/corefork.telegram.org/constructor/inputAppEvent.html delete mode 100644 data/corefork.telegram.org/constructor/inputBotInlineMessageGame.html delete mode 100644 data/corefork.telegram.org/constructor/inputBotInlineMessageID.html delete mode 100644 data/corefork.telegram.org/constructor/inputBotInlineMessageID64.html delete mode 100644 data/corefork.telegram.org/constructor/inputBotInlineMessageMediaAuto.html delete mode 100644 data/corefork.telegram.org/constructor/inputBotInlineMessageMediaContact.html delete mode 100644 data/corefork.telegram.org/constructor/inputBotInlineMessageMediaGeo.html delete mode 100644 data/corefork.telegram.org/constructor/inputBotInlineMessageMediaInvoice.html delete mode 100644 data/corefork.telegram.org/constructor/inputBotInlineMessageMediaVenue.html delete mode 100644 data/corefork.telegram.org/constructor/inputBotInlineMessageText.html delete mode 100644 data/corefork.telegram.org/constructor/inputBotInlineResult.html delete mode 100644 data/corefork.telegram.org/constructor/inputBotInlineResultDocument.html delete mode 100644 data/corefork.telegram.org/constructor/inputBotInlineResultGame.html delete mode 100644 data/corefork.telegram.org/constructor/inputBotInlineResultPhoto.html delete mode 100644 data/corefork.telegram.org/constructor/inputChannel.html delete mode 100644 data/corefork.telegram.org/constructor/inputChannelEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/inputChannelFromMessage.html delete mode 100644 data/corefork.telegram.org/constructor/inputChatPhotoEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/inputChatUploadedPhoto.html delete mode 100644 data/corefork.telegram.org/constructor/inputCheckPasswordEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/inputCheckPasswordSRP.html delete mode 100644 data/corefork.telegram.org/constructor/inputClientProxy.html delete mode 100644 data/corefork.telegram.org/constructor/inputDialogPeer.html delete mode 100644 data/corefork.telegram.org/constructor/inputDialogPeerFolder.html delete mode 100644 data/corefork.telegram.org/constructor/inputDocument.html delete mode 100644 data/corefork.telegram.org/constructor/inputDocumentEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/inputDocumentFileLocation.html delete mode 100644 data/corefork.telegram.org/constructor/inputEncryptedChat.html delete mode 100644 data/corefork.telegram.org/constructor/inputEncryptedFileBigUploaded.html delete mode 100644 data/corefork.telegram.org/constructor/inputEncryptedFileEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/inputEncryptedFileLocation.html delete mode 100644 data/corefork.telegram.org/constructor/inputEncryptedFileUploaded.html delete mode 100644 data/corefork.telegram.org/constructor/inputFileBig.html delete mode 100644 data/corefork.telegram.org/constructor/inputFileLocation.html delete mode 100644 data/corefork.telegram.org/constructor/inputFolderPeer.html delete mode 100644 data/corefork.telegram.org/constructor/inputGameID.html delete mode 100644 data/corefork.telegram.org/constructor/inputGameShortName.html delete mode 100644 data/corefork.telegram.org/constructor/inputGeoPointEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/inputGroupCallStream.html delete mode 100644 data/corefork.telegram.org/constructor/inputKeyboardButtonUrlAuth.html delete mode 100644 data/corefork.telegram.org/constructor/inputMediaContact.html delete mode 100644 data/corefork.telegram.org/constructor/inputMediaDice.html delete mode 100644 data/corefork.telegram.org/constructor/inputMediaDocument.html delete mode 100644 data/corefork.telegram.org/constructor/inputMediaDocumentExternal.html delete mode 100644 data/corefork.telegram.org/constructor/inputMediaEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/inputMediaGame.html delete mode 100644 data/corefork.telegram.org/constructor/inputMediaGeoLive.html delete mode 100644 data/corefork.telegram.org/constructor/inputMediaGeoPoint.html delete mode 100644 data/corefork.telegram.org/constructor/inputMediaInvoice.html delete mode 100644 data/corefork.telegram.org/constructor/inputMediaPhoto.html delete mode 100644 data/corefork.telegram.org/constructor/inputMediaPhotoExternal.html delete mode 100644 data/corefork.telegram.org/constructor/inputMediaPoll.html delete mode 100644 data/corefork.telegram.org/constructor/inputMediaUploadedPhoto.html delete mode 100644 data/corefork.telegram.org/constructor/inputMediaVenue.html delete mode 100644 data/corefork.telegram.org/constructor/inputMessageCallbackQuery.html delete mode 100644 data/corefork.telegram.org/constructor/inputMessageEntityMentionName.html delete mode 100644 data/corefork.telegram.org/constructor/inputMessageID.html delete mode 100644 data/corefork.telegram.org/constructor/inputMessagePinned.html delete mode 100644 data/corefork.telegram.org/constructor/inputMessageReplyTo.html delete mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterChatPhotos.html delete mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterContacts.html delete mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterDocument.html delete mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterGeo.html delete mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterGif.html delete mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterMusic.html delete mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterPhoneCalls.html delete mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterPhotoVideo.html delete mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterPhotos.html delete mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterPinned.html delete mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterRoundVideo.html delete mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterRoundVoice.html delete mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterUrl.html delete mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterVideo.html delete mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterVoice.html delete mode 100644 data/corefork.telegram.org/constructor/inputNotifyBroadcasts.html delete mode 100644 data/corefork.telegram.org/constructor/inputNotifyChats.html delete mode 100644 data/corefork.telegram.org/constructor/inputNotifyPeer.html delete mode 100644 data/corefork.telegram.org/constructor/inputNotifyUsers.html delete mode 100644 data/corefork.telegram.org/constructor/inputPaymentCredentials.html delete mode 100644 data/corefork.telegram.org/constructor/inputPaymentCredentialsApplePay.html delete mode 100644 data/corefork.telegram.org/constructor/inputPaymentCredentialsGooglePay.html delete mode 100644 data/corefork.telegram.org/constructor/inputPaymentCredentialsSaved.html delete mode 100644 data/corefork.telegram.org/constructor/inputPeerChannel.html delete mode 100644 data/corefork.telegram.org/constructor/inputPeerChannelFromMessage.html delete mode 100644 data/corefork.telegram.org/constructor/inputPeerChat.html delete mode 100644 data/corefork.telegram.org/constructor/inputPeerNotifySettings.html delete mode 100644 data/corefork.telegram.org/constructor/inputPeerPhotoFileLocation.html delete mode 100644 data/corefork.telegram.org/constructor/inputPeerSelf.html delete mode 100644 data/corefork.telegram.org/constructor/inputPeerUser.html delete mode 100644 data/corefork.telegram.org/constructor/inputPeerUserFromMessage.html delete mode 100644 data/corefork.telegram.org/constructor/inputPhoneCall.html delete mode 100644 data/corefork.telegram.org/constructor/inputPhoneContact.html delete mode 100644 data/corefork.telegram.org/constructor/inputPhoto.html delete mode 100644 data/corefork.telegram.org/constructor/inputPhotoEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/inputPhotoFileLocation.html delete mode 100644 data/corefork.telegram.org/constructor/inputPrivacyKeyAddedByPhone.html delete mode 100644 data/corefork.telegram.org/constructor/inputPrivacyKeyChatInvite.html delete mode 100644 data/corefork.telegram.org/constructor/inputPrivacyKeyForwards.html delete mode 100644 data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneCall.html delete mode 100644 data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneNumber.html delete mode 100644 data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneP2P.html delete mode 100644 data/corefork.telegram.org/constructor/inputPrivacyKeyProfilePhoto.html delete mode 100644 data/corefork.telegram.org/constructor/inputPrivacyValueAllowChatParticipants.html delete mode 100644 data/corefork.telegram.org/constructor/inputPrivacyValueAllowContacts.html delete mode 100644 data/corefork.telegram.org/constructor/inputPrivacyValueAllowUsers.html delete mode 100644 data/corefork.telegram.org/constructor/inputPrivacyValueDisallowAll.html delete mode 100644 data/corefork.telegram.org/constructor/inputPrivacyValueDisallowChatParticipants.html delete mode 100644 data/corefork.telegram.org/constructor/inputPrivacyValueDisallowUsers.html delete mode 100644 data/corefork.telegram.org/constructor/inputReportReasonChildAbuse.html delete mode 100644 data/corefork.telegram.org/constructor/inputReportReasonCopyright.html delete mode 100644 data/corefork.telegram.org/constructor/inputReportReasonFake.html delete mode 100644 data/corefork.telegram.org/constructor/inputReportReasonGeoIrrelevant.html delete mode 100644 data/corefork.telegram.org/constructor/inputReportReasonOther.html delete mode 100644 data/corefork.telegram.org/constructor/inputReportReasonPornography.html delete mode 100644 data/corefork.telegram.org/constructor/inputReportReasonSpam.html delete mode 100644 data/corefork.telegram.org/constructor/inputReportReasonViolence.html delete mode 100644 data/corefork.telegram.org/constructor/inputSecureFile.html delete mode 100644 data/corefork.telegram.org/constructor/inputSecureFileLocation.html delete mode 100644 data/corefork.telegram.org/constructor/inputSecureFileUploaded.html delete mode 100644 data/corefork.telegram.org/constructor/inputSecureValue.html delete mode 100644 data/corefork.telegram.org/constructor/inputSingleMedia.html delete mode 100644 data/corefork.telegram.org/constructor/inputStickerSetAnimatedEmoji.html delete mode 100644 data/corefork.telegram.org/constructor/inputStickerSetAnimatedEmojiAnimations.html delete mode 100644 data/corefork.telegram.org/constructor/inputStickerSetDice.html delete mode 100644 data/corefork.telegram.org/constructor/inputStickerSetEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/inputStickerSetID.html delete mode 100644 data/corefork.telegram.org/constructor/inputStickerSetItem.html delete mode 100644 data/corefork.telegram.org/constructor/inputStickerSetShortName.html delete mode 100644 data/corefork.telegram.org/constructor/inputStickeredMediaDocument.html delete mode 100644 data/corefork.telegram.org/constructor/inputStickeredMediaPhoto.html delete mode 100644 data/corefork.telegram.org/constructor/inputTakeoutFileLocation.html delete mode 100644 data/corefork.telegram.org/constructor/inputTheme.html delete mode 100644 data/corefork.telegram.org/constructor/inputThemeSettings.html delete mode 100644 data/corefork.telegram.org/constructor/inputThemeSlug.html delete mode 100644 data/corefork.telegram.org/constructor/inputUser.html delete mode 100644 data/corefork.telegram.org/constructor/inputUserEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/inputUserFromMessage.html delete mode 100644 data/corefork.telegram.org/constructor/inputUserSelf.html delete mode 100644 data/corefork.telegram.org/constructor/inputWallPaper.html delete mode 100644 data/corefork.telegram.org/constructor/inputWallPaperNoFile.html delete mode 100644 data/corefork.telegram.org/constructor/inputWallPaperSlug.html delete mode 100644 data/corefork.telegram.org/constructor/inputWebDocument.html delete mode 100644 data/corefork.telegram.org/constructor/inputWebFileGeoPointLocation.html delete mode 100644 data/corefork.telegram.org/constructor/inputWebFileLocation.html delete mode 100644 data/corefork.telegram.org/constructor/invoice.html delete mode 100644 data/corefork.telegram.org/constructor/jsonArray.html delete mode 100644 data/corefork.telegram.org/constructor/jsonBool.html delete mode 100644 data/corefork.telegram.org/constructor/jsonNull.html delete mode 100644 data/corefork.telegram.org/constructor/jsonNumber.html delete mode 100644 data/corefork.telegram.org/constructor/jsonObject.html delete mode 100644 data/corefork.telegram.org/constructor/jsonObjectValue.html delete mode 100644 data/corefork.telegram.org/constructor/jsonString.html delete mode 100644 data/corefork.telegram.org/constructor/keyboardButton.html delete mode 100644 data/corefork.telegram.org/constructor/keyboardButtonBuy.html delete mode 100644 data/corefork.telegram.org/constructor/keyboardButtonCallback.html delete mode 100644 data/corefork.telegram.org/constructor/keyboardButtonGame.html delete mode 100644 data/corefork.telegram.org/constructor/keyboardButtonRequestGeoLocation.html delete mode 100644 data/corefork.telegram.org/constructor/keyboardButtonRequestPhone.html delete mode 100644 data/corefork.telegram.org/constructor/keyboardButtonRequestPoll.html delete mode 100644 data/corefork.telegram.org/constructor/keyboardButtonRow.html delete mode 100644 data/corefork.telegram.org/constructor/keyboardButtonSwitchInline.html delete mode 100644 data/corefork.telegram.org/constructor/keyboardButtonUrl.html delete mode 100644 data/corefork.telegram.org/constructor/keyboardButtonUrlAuth.html delete mode 100644 data/corefork.telegram.org/constructor/labeledPrice.html delete mode 100644 data/corefork.telegram.org/constructor/langPackDifference.html delete mode 100644 data/corefork.telegram.org/constructor/langPackLanguage.html delete mode 100644 data/corefork.telegram.org/constructor/langPackString.html delete mode 100644 data/corefork.telegram.org/constructor/langPackStringDeleted.html delete mode 100644 data/corefork.telegram.org/constructor/langPackStringPluralized.html delete mode 100644 data/corefork.telegram.org/constructor/maskCoords.html delete mode 100644 data/corefork.telegram.org/constructor/message.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionBotAllowed.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionChannelCreate.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionChannelMigrateFrom.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionChatAddUser.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionChatCreate.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionChatDeletePhoto.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionChatDeleteUser.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionChatEditPhoto.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionChatEditTitle.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionChatJoinedByLink.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionChatMigrateTo.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionContactSignUp.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionCustomAction.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionGeoProximityReached.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionGroupCall.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionGroupCallScheduled.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionHistoryClear.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionInviteToGroupCall.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionPaymentSentMe.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionPhoneCall.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionPinMessage.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionScreenshotTaken.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionSecureValuesSent.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionSecureValuesSentMe.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionSetChatTheme.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionSetMessagesTTL.html delete mode 100644 data/corefork.telegram.org/constructor/messageEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/messageEntityBankCard.html delete mode 100644 data/corefork.telegram.org/constructor/messageEntityBlockquote.html delete mode 100644 data/corefork.telegram.org/constructor/messageEntityBold.html delete mode 100644 data/corefork.telegram.org/constructor/messageEntityBotCommand.html delete mode 100644 data/corefork.telegram.org/constructor/messageEntityCashtag.html delete mode 100644 data/corefork.telegram.org/constructor/messageEntityCode.html delete mode 100644 data/corefork.telegram.org/constructor/messageEntityEmail.html delete mode 100644 data/corefork.telegram.org/constructor/messageEntityHashtag.html delete mode 100644 data/corefork.telegram.org/constructor/messageEntityItalic.html delete mode 100644 data/corefork.telegram.org/constructor/messageEntityMention.html delete mode 100644 data/corefork.telegram.org/constructor/messageEntityMentionName.html delete mode 100644 data/corefork.telegram.org/constructor/messageEntityPhone.html delete mode 100644 data/corefork.telegram.org/constructor/messageEntityPre.html delete mode 100644 data/corefork.telegram.org/constructor/messageEntityStrike.html delete mode 100644 data/corefork.telegram.org/constructor/messageEntityTextUrl.html delete mode 100644 data/corefork.telegram.org/constructor/messageEntityUnderline.html delete mode 100644 data/corefork.telegram.org/constructor/messageEntityUnknown.html delete mode 100644 data/corefork.telegram.org/constructor/messageEntityUrl.html delete mode 100644 data/corefork.telegram.org/constructor/messageFwdHeader.html delete mode 100644 data/corefork.telegram.org/constructor/messageInteractionCounters.html delete mode 100644 data/corefork.telegram.org/constructor/messageMediaAudio.html delete mode 100644 data/corefork.telegram.org/constructor/messageMediaContact.html delete mode 100644 data/corefork.telegram.org/constructor/messageMediaDice.html delete mode 100644 data/corefork.telegram.org/constructor/messageMediaDocument.html delete mode 100644 data/corefork.telegram.org/constructor/messageMediaEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/messageMediaGame.html delete mode 100644 data/corefork.telegram.org/constructor/messageMediaGeo.html delete mode 100644 data/corefork.telegram.org/constructor/messageMediaGeoLive.html delete mode 100644 data/corefork.telegram.org/constructor/messageMediaPhoto.html delete mode 100644 data/corefork.telegram.org/constructor/messageMediaPoll.html delete mode 100644 data/corefork.telegram.org/constructor/messageMediaUnsupported.html delete mode 100644 data/corefork.telegram.org/constructor/messageMediaVenue.html delete mode 100644 data/corefork.telegram.org/constructor/messageMediaWebPage.html delete mode 100644 data/corefork.telegram.org/constructor/messageRange.html delete mode 100644 data/corefork.telegram.org/constructor/messageReplies.html delete mode 100644 data/corefork.telegram.org/constructor/messageReplyHeader.html delete mode 100644 data/corefork.telegram.org/constructor/messageService.html delete mode 100644 data/corefork.telegram.org/constructor/messageUserVote.html delete mode 100644 data/corefork.telegram.org/constructor/messageUserVoteInputOption.html delete mode 100644 data/corefork.telegram.org/constructor/messageUserVoteMultiple.html delete mode 100644 data/corefork.telegram.org/constructor/messageViews.html delete mode 100644 data/corefork.telegram.org/constructor/messages.affectedFoundMessages delete mode 100644 data/corefork.telegram.org/constructor/messages.affectedHistory delete mode 100644 data/corefork.telegram.org/constructor/messages.affectedMessages delete mode 100644 data/corefork.telegram.org/constructor/messages.allStickers delete mode 100644 data/corefork.telegram.org/constructor/messages.allStickersNotModified delete mode 100644 data/corefork.telegram.org/constructor/messages.archivedStickers delete mode 100644 data/corefork.telegram.org/constructor/messages.botCallbackAnswer delete mode 100644 data/corefork.telegram.org/constructor/messages.botResults delete mode 100644 data/corefork.telegram.org/constructor/messages.channelMessages delete mode 100644 data/corefork.telegram.org/constructor/messages.chatAdminsWithInvites delete mode 100644 data/corefork.telegram.org/constructor/messages.chatFull delete mode 100644 data/corefork.telegram.org/constructor/messages.chatInviteImporters delete mode 100644 data/corefork.telegram.org/constructor/messages.chats delete mode 100644 data/corefork.telegram.org/constructor/messages.chatsSlice delete mode 100644 data/corefork.telegram.org/constructor/messages.checkedHistoryImportPeer delete mode 100644 data/corefork.telegram.org/constructor/messages.dhConfig delete mode 100644 data/corefork.telegram.org/constructor/messages.dhConfigNotModified delete mode 100644 data/corefork.telegram.org/constructor/messages.dialogs delete mode 100644 data/corefork.telegram.org/constructor/messages.dialogsNotModified delete mode 100644 data/corefork.telegram.org/constructor/messages.dialogsSlice delete mode 100644 data/corefork.telegram.org/constructor/messages.discussionMessage delete mode 100644 data/corefork.telegram.org/constructor/messages.exportedChatInvite delete mode 100644 data/corefork.telegram.org/constructor/messages.exportedChatInviteReplaced delete mode 100644 data/corefork.telegram.org/constructor/messages.favedStickers delete mode 100644 data/corefork.telegram.org/constructor/messages.favedStickersNotModified delete mode 100644 data/corefork.telegram.org/constructor/messages.featuredStickers delete mode 100644 data/corefork.telegram.org/constructor/messages.featuredStickersNotModified delete mode 100644 data/corefork.telegram.org/constructor/messages.foundStickerSets delete mode 100644 data/corefork.telegram.org/constructor/messages.foundStickerSetsNotModified delete mode 100644 data/corefork.telegram.org/constructor/messages.highScores delete mode 100644 data/corefork.telegram.org/constructor/messages.historyImport delete mode 100644 data/corefork.telegram.org/constructor/messages.historyImportParsed delete mode 100644 data/corefork.telegram.org/constructor/messages.messageEditData delete mode 100644 data/corefork.telegram.org/constructor/messages.messageViews delete mode 100644 data/corefork.telegram.org/constructor/messages.messages delete mode 100644 data/corefork.telegram.org/constructor/messages.messagesNotModified delete mode 100644 data/corefork.telegram.org/constructor/messages.messagesSlice delete mode 100644 data/corefork.telegram.org/constructor/messages.peerDialogs delete mode 100644 data/corefork.telegram.org/constructor/messages.recentStickers delete mode 100644 data/corefork.telegram.org/constructor/messages.recentStickersNotModified delete mode 100644 data/corefork.telegram.org/constructor/messages.savedGifs delete mode 100644 data/corefork.telegram.org/constructor/messages.savedGifsNotModified delete mode 100644 data/corefork.telegram.org/constructor/messages.searchCounter delete mode 100644 data/corefork.telegram.org/constructor/messages.sentEncryptedFile delete mode 100644 data/corefork.telegram.org/constructor/messages.sentEncryptedMessage delete mode 100644 data/corefork.telegram.org/constructor/messages.sentMessageLink delete mode 100644 data/corefork.telegram.org/constructor/messages.sponsoredMessages delete mode 100644 data/corefork.telegram.org/constructor/messages.statedMessagesLinks delete mode 100644 data/corefork.telegram.org/constructor/messages.stickerSet delete mode 100644 data/corefork.telegram.org/constructor/messages.stickerSetInstallResultArchive delete mode 100644 data/corefork.telegram.org/constructor/messages.stickerSetInstallResultSuccess delete mode 100644 data/corefork.telegram.org/constructor/messages.stickers delete mode 100644 data/corefork.telegram.org/constructor/messages.stickersNotModified delete mode 100644 data/corefork.telegram.org/constructor/messages.votesList delete mode 100644 data/corefork.telegram.org/constructor/nearestDc.html delete mode 100644 data/corefork.telegram.org/constructor/notifyBroadcasts.html delete mode 100644 data/corefork.telegram.org/constructor/notifyChats.html delete mode 100644 data/corefork.telegram.org/constructor/notifyPeer.html delete mode 100644 data/corefork.telegram.org/constructor/notifyUsers.html delete mode 100644 data/corefork.telegram.org/constructor/null.html delete mode 100644 data/corefork.telegram.org/constructor/page.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockAnchor.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockAudio.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockAuthorDate.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockBlockquote.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockChannel.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockCollage.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockCover.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockDetails.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockDivider.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockEmbed.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockEmbedPost.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockFooter.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockHeader.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockKicker.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockList.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockMap.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockOrderedList.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockParagraph.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockPhoto.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockPreformatted.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockPullquote.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockRelatedArticles.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockSlideshow.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockSubheader.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockSubtitle.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockTable.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockTitle.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockUnsupported.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockVideo.html delete mode 100644 data/corefork.telegram.org/constructor/pageCaption.html delete mode 100644 data/corefork.telegram.org/constructor/pageListItemBlocks.html delete mode 100644 data/corefork.telegram.org/constructor/pageListItemText.html delete mode 100644 data/corefork.telegram.org/constructor/pageListOrderedItemBlocks.html delete mode 100644 data/corefork.telegram.org/constructor/pageListOrderedItemText.html delete mode 100644 data/corefork.telegram.org/constructor/pageRelatedArticle.html delete mode 100644 data/corefork.telegram.org/constructor/pageTableCell.html delete mode 100644 data/corefork.telegram.org/constructor/pageTableRow.html delete mode 100644 data/corefork.telegram.org/constructor/passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow.html delete mode 100644 data/corefork.telegram.org/constructor/passwordKdfAlgoUnknown.html delete mode 100644 data/corefork.telegram.org/constructor/paymentCharge.html delete mode 100644 data/corefork.telegram.org/constructor/paymentRequestedInfo.html delete mode 100644 data/corefork.telegram.org/constructor/payments.ValidatedRequestedInfo delete mode 100644 data/corefork.telegram.org/constructor/payments.bankCardData delete mode 100644 data/corefork.telegram.org/constructor/payments.paymentReceipt delete mode 100644 data/corefork.telegram.org/constructor/payments.paymentResult delete mode 100644 data/corefork.telegram.org/constructor/payments.paymentVerificationNeeded delete mode 100644 data/corefork.telegram.org/constructor/payments.savedInfo delete mode 100644 data/corefork.telegram.org/constructor/peerBlocked.html delete mode 100644 data/corefork.telegram.org/constructor/peerChannel.html delete mode 100644 data/corefork.telegram.org/constructor/peerChat.html delete mode 100644 data/corefork.telegram.org/constructor/peerLocated.html delete mode 100644 data/corefork.telegram.org/constructor/peerNotifySettings.html delete mode 100644 data/corefork.telegram.org/constructor/peerSelfLocated.html delete mode 100644 data/corefork.telegram.org/constructor/peerSettings.html delete mode 100644 data/corefork.telegram.org/constructor/peerUser.html delete mode 100644 data/corefork.telegram.org/constructor/phone.joinAsPeers delete mode 100644 data/corefork.telegram.org/constructor/phone.phoneCall delete mode 100644 data/corefork.telegram.org/constructor/phoneCall.html delete mode 100644 data/corefork.telegram.org/constructor/phoneCallDiscardReasonBusy.html delete mode 100644 data/corefork.telegram.org/constructor/phoneCallDiscardReasonDisconnect.html delete mode 100644 data/corefork.telegram.org/constructor/phoneCallDiscardReasonHangup.html delete mode 100644 data/corefork.telegram.org/constructor/phoneCallDiscardReasonMissed.html delete mode 100644 data/corefork.telegram.org/constructor/phoneCallDiscarded.html delete mode 100644 data/corefork.telegram.org/constructor/phoneCallEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/phoneCallProtocol.html delete mode 100644 data/corefork.telegram.org/constructor/phoneCallRequested.html delete mode 100644 data/corefork.telegram.org/constructor/phoneCallWaiting.html delete mode 100644 data/corefork.telegram.org/constructor/phoneConnection.html delete mode 100644 data/corefork.telegram.org/constructor/phoneConnectionWebrtc.html delete mode 100644 data/corefork.telegram.org/constructor/photo.html delete mode 100644 data/corefork.telegram.org/constructor/photoCachedSize.html delete mode 100644 data/corefork.telegram.org/constructor/photoEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/photoPathSize.html delete mode 100644 data/corefork.telegram.org/constructor/photoSize.html delete mode 100644 data/corefork.telegram.org/constructor/photoSizeEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/photoStrippedSize.html delete mode 100644 data/corefork.telegram.org/constructor/photos.photo delete mode 100644 data/corefork.telegram.org/constructor/photos.photos delete mode 100644 data/corefork.telegram.org/constructor/photos.photosSlice delete mode 100644 data/corefork.telegram.org/constructor/poll.html delete mode 100644 data/corefork.telegram.org/constructor/pollAnswer.html delete mode 100644 data/corefork.telegram.org/constructor/pollAnswerVoters.html delete mode 100644 data/corefork.telegram.org/constructor/pollResults.html delete mode 100644 data/corefork.telegram.org/constructor/popularContact.html delete mode 100644 data/corefork.telegram.org/constructor/postAddress.html delete mode 100644 data/corefork.telegram.org/constructor/privacyKeyAddedByPhone.html delete mode 100644 data/corefork.telegram.org/constructor/privacyKeyChatInvite.html delete mode 100644 data/corefork.telegram.org/constructor/privacyKeyForwards.html delete mode 100644 data/corefork.telegram.org/constructor/privacyKeyPhoneCall.html delete mode 100644 data/corefork.telegram.org/constructor/privacyKeyPhoneNumber.html delete mode 100644 data/corefork.telegram.org/constructor/privacyKeyPhoneP2P.html delete mode 100644 data/corefork.telegram.org/constructor/privacyKeyProfilePhoto.html delete mode 100644 data/corefork.telegram.org/constructor/privacyKeyStatusTimestamp.html delete mode 100644 data/corefork.telegram.org/constructor/privacyValueAllowAll.html delete mode 100644 data/corefork.telegram.org/constructor/privacyValueAllowChatParticipants.html delete mode 100644 data/corefork.telegram.org/constructor/privacyValueAllowContacts.html delete mode 100644 data/corefork.telegram.org/constructor/privacyValueAllowUsers.html delete mode 100644 data/corefork.telegram.org/constructor/privacyValueDisallowAll.html delete mode 100644 data/corefork.telegram.org/constructor/privacyValueDisallowChatParticipants.html delete mode 100644 data/corefork.telegram.org/constructor/privacyValueDisallowContacts.html delete mode 100644 data/corefork.telegram.org/constructor/privacyValueDisallowUsers.html delete mode 100644 data/corefork.telegram.org/constructor/receivedNotifyMessage.html delete mode 100644 data/corefork.telegram.org/constructor/recentMeUrlChat.html delete mode 100644 data/corefork.telegram.org/constructor/recentMeUrlChatInvite.html delete mode 100644 data/corefork.telegram.org/constructor/recentMeUrlStickerSet.html delete mode 100644 data/corefork.telegram.org/constructor/recentMeUrlUnknown.html delete mode 100644 data/corefork.telegram.org/constructor/recentMeUrlUser.html delete mode 100644 data/corefork.telegram.org/constructor/replyInlineMarkup.html delete mode 100644 data/corefork.telegram.org/constructor/replyKeyboardForceReply.html delete mode 100644 data/corefork.telegram.org/constructor/replyKeyboardHide.html delete mode 100644 data/corefork.telegram.org/constructor/restrictionReason.html delete mode 100644 data/corefork.telegram.org/constructor/savedPhoneContact.html delete mode 100644 data/corefork.telegram.org/constructor/secureCredentialsEncrypted.html delete mode 100644 data/corefork.telegram.org/constructor/secureData.html delete mode 100644 data/corefork.telegram.org/constructor/secureFile.html delete mode 100644 data/corefork.telegram.org/constructor/secureFileEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/securePasswordKdfAlgoPBKDF2HMACSHA512iter100000.html delete mode 100644 data/corefork.telegram.org/constructor/securePasswordKdfAlgoSHA512.html delete mode 100644 data/corefork.telegram.org/constructor/securePasswordKdfAlgoUnknown.html delete mode 100644 data/corefork.telegram.org/constructor/securePlainEmail.html delete mode 100644 data/corefork.telegram.org/constructor/securePlainPhone.html delete mode 100644 data/corefork.telegram.org/constructor/secureRequiredType.html delete mode 100644 data/corefork.telegram.org/constructor/secureRequiredTypeOneOf.html delete mode 100644 data/corefork.telegram.org/constructor/secureSecretSettings.html delete mode 100644 data/corefork.telegram.org/constructor/secureValue.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueError.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueErrorData.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueErrorFile.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueErrorFiles.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueErrorFrontSide.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueErrorReverseSide.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueErrorSelfie.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueErrorTranslationFile.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueErrorTranslationFiles.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueHash.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueTypeAddress.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueTypeBankStatement.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueTypeDriverLicense.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueTypeEmail.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueTypeIdentityCard.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueTypeInternalPassport.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueTypePassport.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueTypePassportRegistration.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueTypePersonalDetails.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueTypePhone.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueTypeRentalAgreement.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueTypeTemporaryRegistration.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueTypeUtilityBill.html delete mode 100644 data/corefork.telegram.org/constructor/sendMessageCancelAction.html delete mode 100644 data/corefork.telegram.org/constructor/sendMessageChooseContactAction.html delete mode 100644 data/corefork.telegram.org/constructor/sendMessageChooseStickerAction.html delete mode 100644 data/corefork.telegram.org/constructor/sendMessageEmojiInteraction.html delete mode 100644 data/corefork.telegram.org/constructor/sendMessageGamePlayAction.html delete mode 100644 data/corefork.telegram.org/constructor/sendMessageGeoLocationAction.html delete mode 100644 data/corefork.telegram.org/constructor/sendMessageHistoryImportAction.html delete mode 100644 data/corefork.telegram.org/constructor/sendMessageRecordAudioAction.html delete mode 100644 data/corefork.telegram.org/constructor/sendMessageRecordRoundAction.html delete mode 100644 data/corefork.telegram.org/constructor/sendMessageRecordVideoAction.html delete mode 100644 data/corefork.telegram.org/constructor/sendMessageTypingAction.html delete mode 100644 data/corefork.telegram.org/constructor/sendMessageUploadAudioAction.html delete mode 100644 data/corefork.telegram.org/constructor/sendMessageUploadDocumentAction.html delete mode 100644 data/corefork.telegram.org/constructor/sendMessageUploadPhotoAction.html delete mode 100644 data/corefork.telegram.org/constructor/sendMessageUploadRoundAction.html delete mode 100644 data/corefork.telegram.org/constructor/sendMessageUploadVideoAction.html delete mode 100644 data/corefork.telegram.org/constructor/shippingOption.html delete mode 100644 data/corefork.telegram.org/constructor/speakingInGroupCallAction.html delete mode 100644 data/corefork.telegram.org/constructor/sponsoredMessage.html delete mode 100644 data/corefork.telegram.org/constructor/stats.broadcastStats delete mode 100644 data/corefork.telegram.org/constructor/stats.megagroupStats delete mode 100644 data/corefork.telegram.org/constructor/statsAbsValueAndPrev.html delete mode 100644 data/corefork.telegram.org/constructor/statsDateRangeDays.html delete mode 100644 data/corefork.telegram.org/constructor/statsGraph.html delete mode 100644 data/corefork.telegram.org/constructor/statsGraphAsync.html delete mode 100644 data/corefork.telegram.org/constructor/statsGroupTopAdmin.html delete mode 100644 data/corefork.telegram.org/constructor/statsGroupTopInviter.html delete mode 100644 data/corefork.telegram.org/constructor/statsGroupTopPoster.html delete mode 100644 data/corefork.telegram.org/constructor/statsURL.html delete mode 100644 data/corefork.telegram.org/constructor/stickerPack.html delete mode 100644 data/corefork.telegram.org/constructor/stickerSet.html delete mode 100644 data/corefork.telegram.org/constructor/stickerSetCovered.html delete mode 100644 data/corefork.telegram.org/constructor/stickerSetMultiCovered.html delete mode 100644 data/corefork.telegram.org/constructor/stickers.suggestedShortName delete mode 100644 data/corefork.telegram.org/constructor/storage.fileGif delete mode 100644 data/corefork.telegram.org/constructor/storage.fileJpeg delete mode 100644 data/corefork.telegram.org/constructor/storage.fileMov delete mode 100644 data/corefork.telegram.org/constructor/storage.fileMp3 delete mode 100644 data/corefork.telegram.org/constructor/storage.fileMp4 delete mode 100644 data/corefork.telegram.org/constructor/storage.filePartial delete mode 100644 data/corefork.telegram.org/constructor/storage.filePdf delete mode 100644 data/corefork.telegram.org/constructor/storage.filePng delete mode 100644 data/corefork.telegram.org/constructor/storage.fileUnknown delete mode 100644 data/corefork.telegram.org/constructor/storage.fileWebp delete mode 100644 data/corefork.telegram.org/constructor/textAnchor.html delete mode 100644 data/corefork.telegram.org/constructor/textBold.html delete mode 100644 data/corefork.telegram.org/constructor/textConcat.html delete mode 100644 data/corefork.telegram.org/constructor/textEmail.html delete mode 100644 data/corefork.telegram.org/constructor/textEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/textFixed.html delete mode 100644 data/corefork.telegram.org/constructor/textImage.html delete mode 100644 data/corefork.telegram.org/constructor/textItalic.html delete mode 100644 data/corefork.telegram.org/constructor/textMarked.html delete mode 100644 data/corefork.telegram.org/constructor/textPhone.html delete mode 100644 data/corefork.telegram.org/constructor/textPlain.html delete mode 100644 data/corefork.telegram.org/constructor/textStrike.html delete mode 100644 data/corefork.telegram.org/constructor/textSubscript.html delete mode 100644 data/corefork.telegram.org/constructor/textSuperscript.html delete mode 100644 data/corefork.telegram.org/constructor/textUnderline.html delete mode 100644 data/corefork.telegram.org/constructor/textUrl.html delete mode 100644 data/corefork.telegram.org/constructor/theme.html delete mode 100644 data/corefork.telegram.org/constructor/topPeer.html delete mode 100644 data/corefork.telegram.org/constructor/topPeerCategoryBotsInline.html delete mode 100644 data/corefork.telegram.org/constructor/topPeerCategoryBotsPM.html delete mode 100644 data/corefork.telegram.org/constructor/topPeerCategoryChannels.html delete mode 100644 data/corefork.telegram.org/constructor/topPeerCategoryCorrespondents.html delete mode 100644 data/corefork.telegram.org/constructor/topPeerCategoryForwardChats.html delete mode 100644 data/corefork.telegram.org/constructor/topPeerCategoryForwardUsers.html delete mode 100644 data/corefork.telegram.org/constructor/topPeerCategoryGroups.html delete mode 100644 data/corefork.telegram.org/constructor/topPeerCategoryPeers.html delete mode 100644 data/corefork.telegram.org/constructor/topPeerCategoryPhoneCalls.html delete mode 100644 data/corefork.telegram.org/constructor/true.html delete mode 100644 data/corefork.telegram.org/constructor/updateBotCallbackQuery.html delete mode 100644 data/corefork.telegram.org/constructor/updateBotCommands.html delete mode 100644 data/corefork.telegram.org/constructor/updateBotInlineQuery.html delete mode 100644 data/corefork.telegram.org/constructor/updateBotInlineSend.html delete mode 100644 data/corefork.telegram.org/constructor/updateBotPrecheckoutQuery.html delete mode 100644 data/corefork.telegram.org/constructor/updateBotStopped.html delete mode 100644 data/corefork.telegram.org/constructor/updateBotWebhookJSON.html delete mode 100644 data/corefork.telegram.org/constructor/updateBotWebhookJSONQuery.html delete mode 100644 data/corefork.telegram.org/constructor/updateChannel.html delete mode 100644 data/corefork.telegram.org/constructor/updateChannelAvailableMessages.html delete mode 100644 data/corefork.telegram.org/constructor/updateChannelMessageForwards.html delete mode 100644 data/corefork.telegram.org/constructor/updateChannelMessageViews.html delete mode 100644 data/corefork.telegram.org/constructor/updateChannelParticipant.html delete mode 100644 data/corefork.telegram.org/constructor/updateChannelReadMessagesContents.html delete mode 100644 data/corefork.telegram.org/constructor/updateChannelTooLong.html delete mode 100644 data/corefork.telegram.org/constructor/updateChannelUserTyping.html delete mode 100644 data/corefork.telegram.org/constructor/updateChannelWebPage.html delete mode 100644 data/corefork.telegram.org/constructor/updateChat.html delete mode 100644 data/corefork.telegram.org/constructor/updateChatDefaultBannedRights.html delete mode 100644 data/corefork.telegram.org/constructor/updateChatParticipant.html delete mode 100644 data/corefork.telegram.org/constructor/updateChatParticipantAdd.html delete mode 100644 data/corefork.telegram.org/constructor/updateChatParticipantAdmin.html delete mode 100644 data/corefork.telegram.org/constructor/updateChatParticipants.html delete mode 100644 data/corefork.telegram.org/constructor/updateChatUserTyping.html delete mode 100644 data/corefork.telegram.org/constructor/updateConfig.html delete mode 100644 data/corefork.telegram.org/constructor/updateContactsReset.html delete mode 100644 data/corefork.telegram.org/constructor/updateDcOptions.html delete mode 100644 data/corefork.telegram.org/constructor/updateDeleteChannelMessages.html delete mode 100644 data/corefork.telegram.org/constructor/updateDeleteMessages.html delete mode 100644 data/corefork.telegram.org/constructor/updateDialogFilter.html delete mode 100644 data/corefork.telegram.org/constructor/updateDialogFilterOrder.html delete mode 100644 data/corefork.telegram.org/constructor/updateDialogFilters.html delete mode 100644 data/corefork.telegram.org/constructor/updateDialogPinned.html delete mode 100644 data/corefork.telegram.org/constructor/updateDialogUnreadMark.html delete mode 100644 data/corefork.telegram.org/constructor/updateDraftMessage.html delete mode 100644 data/corefork.telegram.org/constructor/updateEditChannelMessage.html delete mode 100644 data/corefork.telegram.org/constructor/updateEditMessage.html delete mode 100644 data/corefork.telegram.org/constructor/updateEncryptedChatTyping.html delete mode 100644 data/corefork.telegram.org/constructor/updateEncryptedMessagesRead.html delete mode 100644 data/corefork.telegram.org/constructor/updateEncryption.html delete mode 100644 data/corefork.telegram.org/constructor/updateFavedStickers.html delete mode 100644 data/corefork.telegram.org/constructor/updateFolderPeers.html delete mode 100644 data/corefork.telegram.org/constructor/updateGeoLiveViewed.html delete mode 100644 data/corefork.telegram.org/constructor/updateGroupCall.html delete mode 100644 data/corefork.telegram.org/constructor/updateGroupCallConnection.html delete mode 100644 data/corefork.telegram.org/constructor/updateGroupCallParticipants.html delete mode 100644 data/corefork.telegram.org/constructor/updateInlineBotCallbackQuery.html delete mode 100644 data/corefork.telegram.org/constructor/updateLangPack.html delete mode 100644 data/corefork.telegram.org/constructor/updateLangPackTooLong.html delete mode 100644 data/corefork.telegram.org/constructor/updateLoginToken.html delete mode 100644 data/corefork.telegram.org/constructor/updateMessageID.html delete mode 100644 data/corefork.telegram.org/constructor/updateMessagePoll.html delete mode 100644 data/corefork.telegram.org/constructor/updateMessagePollVote.html delete mode 100644 data/corefork.telegram.org/constructor/updateNewChannelMessage.html delete mode 100644 data/corefork.telegram.org/constructor/updateNewEncryptedMessage.html delete mode 100644 data/corefork.telegram.org/constructor/updateNewMessage.html delete mode 100644 data/corefork.telegram.org/constructor/updateNewScheduledMessage.html delete mode 100644 data/corefork.telegram.org/constructor/updateNewStickerSet.html delete mode 100644 data/corefork.telegram.org/constructor/updateNotifySettings.html delete mode 100644 data/corefork.telegram.org/constructor/updatePeerBlocked.html delete mode 100644 data/corefork.telegram.org/constructor/updatePeerHistoryTTL.html delete mode 100644 data/corefork.telegram.org/constructor/updatePeerLocated.html delete mode 100644 data/corefork.telegram.org/constructor/updatePeerSettings.html delete mode 100644 data/corefork.telegram.org/constructor/updatePhoneCall.html delete mode 100644 data/corefork.telegram.org/constructor/updatePhoneCallSignalingData.html delete mode 100644 data/corefork.telegram.org/constructor/updatePinnedDialogs.html delete mode 100644 data/corefork.telegram.org/constructor/updatePinnedMessages.html delete mode 100644 data/corefork.telegram.org/constructor/updatePrivacy.html delete mode 100644 data/corefork.telegram.org/constructor/updatePtsChanged.html delete mode 100644 data/corefork.telegram.org/constructor/updateReadChannelDiscussionInbox.html delete mode 100644 data/corefork.telegram.org/constructor/updateReadChannelDiscussionOutbox.html delete mode 100644 data/corefork.telegram.org/constructor/updateReadChannelInbox.html delete mode 100644 data/corefork.telegram.org/constructor/updateReadChannelOutbox.html delete mode 100644 data/corefork.telegram.org/constructor/updateReadFeaturedStickers.html delete mode 100644 data/corefork.telegram.org/constructor/updateReadHistoryInbox.html delete mode 100644 data/corefork.telegram.org/constructor/updateReadHistoryOutbox.html delete mode 100644 data/corefork.telegram.org/constructor/updateReadMessagesContents.html delete mode 100644 data/corefork.telegram.org/constructor/updateRecentStickers.html delete mode 100644 data/corefork.telegram.org/constructor/updateSavedGifs.html delete mode 100644 data/corefork.telegram.org/constructor/updateServiceNotification.html delete mode 100644 data/corefork.telegram.org/constructor/updateShort.html delete mode 100644 data/corefork.telegram.org/constructor/updateShortChatMessage.html delete mode 100644 data/corefork.telegram.org/constructor/updateShortMessage.html delete mode 100644 data/corefork.telegram.org/constructor/updateStickerSets.html delete mode 100644 data/corefork.telegram.org/constructor/updateStickerSetsOrder.html delete mode 100644 data/corefork.telegram.org/constructor/updateTheme.html delete mode 100644 data/corefork.telegram.org/constructor/updateUserBlocked.html delete mode 100644 data/corefork.telegram.org/constructor/updateUserName.html delete mode 100644 data/corefork.telegram.org/constructor/updateUserPhone.html delete mode 100644 data/corefork.telegram.org/constructor/updateUserPhoto.html delete mode 100644 data/corefork.telegram.org/constructor/updateUserStatus.html delete mode 100644 data/corefork.telegram.org/constructor/updateUserTyping.html delete mode 100644 data/corefork.telegram.org/constructor/updateWebPage.html delete mode 100644 data/corefork.telegram.org/constructor/updates.channelDifference delete mode 100644 data/corefork.telegram.org/constructor/updates.channelDifferenceEmpty delete mode 100644 data/corefork.telegram.org/constructor/updates.channelDifferenceTooLong delete mode 100644 data/corefork.telegram.org/constructor/updates.difference delete mode 100644 data/corefork.telegram.org/constructor/updates.differenceEmpty delete mode 100644 data/corefork.telegram.org/constructor/updates.differenceSlice delete mode 100644 data/corefork.telegram.org/constructor/updates.differenceTooLong delete mode 100644 data/corefork.telegram.org/constructor/updates.html delete mode 100644 data/corefork.telegram.org/constructor/updatesCombined.html delete mode 100644 data/corefork.telegram.org/constructor/updatesTooLong.html delete mode 100644 data/corefork.telegram.org/constructor/upload.cdnFile delete mode 100644 data/corefork.telegram.org/constructor/upload.cdnFileReuploadNeeded delete mode 100644 data/corefork.telegram.org/constructor/upload.file delete mode 100644 data/corefork.telegram.org/constructor/upload.fileCdnRedirect delete mode 100644 data/corefork.telegram.org/constructor/upload.webFile delete mode 100644 data/corefork.telegram.org/constructor/urlAuthResultAccepted.html delete mode 100644 data/corefork.telegram.org/constructor/urlAuthResultDefault.html delete mode 100644 data/corefork.telegram.org/constructor/urlAuthResultRequest.html delete mode 100644 data/corefork.telegram.org/constructor/user.html delete mode 100644 data/corefork.telegram.org/constructor/userEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/userFull.html delete mode 100644 data/corefork.telegram.org/constructor/userProfilePhoto.html delete mode 100644 data/corefork.telegram.org/constructor/userProfilePhotoEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/userStatusEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/userStatusLastMonth.html delete mode 100644 data/corefork.telegram.org/constructor/userStatusLastWeek.html delete mode 100644 data/corefork.telegram.org/constructor/userStatusOffline.html delete mode 100644 data/corefork.telegram.org/constructor/userStatusOnline.html delete mode 100644 data/corefork.telegram.org/constructor/userStatusRecently.html delete mode 100644 data/corefork.telegram.org/constructor/vector.html delete mode 100644 data/corefork.telegram.org/constructor/videoSize.html delete mode 100644 data/corefork.telegram.org/constructor/wallPaper.html delete mode 100644 data/corefork.telegram.org/constructor/wallPaperNoFile.html delete mode 100644 data/corefork.telegram.org/constructor/wallPaperSettings.html delete mode 100644 data/corefork.telegram.org/constructor/wallPaperSolid.html delete mode 100644 data/corefork.telegram.org/constructor/webAuthorization.html delete mode 100644 data/corefork.telegram.org/constructor/webDocument.html delete mode 100644 data/corefork.telegram.org/constructor/webDocumentNoProxy.html delete mode 100644 data/corefork.telegram.org/constructor/webPage.html delete mode 100644 data/corefork.telegram.org/constructor/webPageEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/webPageNotModified.html delete mode 100644 data/corefork.telegram.org/constructor/webPagePending.html delete mode 100644 data/corefork.telegram.org/css/core-widgets.css delete mode 100644 data/corefork.telegram.org/getProxyConfig.html delete mode 100644 data/corefork.telegram.org/import-stickers.html delete mode 100644 data/corefork.telegram.org/js/core-widgets.js delete mode 100644 data/corefork.telegram.org/method/account.acceptAuthorization delete mode 100644 data/corefork.telegram.org/method/account.cancelPasswordEmail delete mode 100644 data/corefork.telegram.org/method/account.changePhone delete mode 100644 data/corefork.telegram.org/method/account.checkUsername delete mode 100644 data/corefork.telegram.org/method/account.confirmPasswordEmail delete mode 100644 data/corefork.telegram.org/method/account.confirmPhone delete mode 100644 data/corefork.telegram.org/method/account.createTheme delete mode 100644 data/corefork.telegram.org/method/account.declinePasswordReset delete mode 100644 data/corefork.telegram.org/method/account.deleteAccount delete mode 100644 data/corefork.telegram.org/method/account.deleteSecureValue delete mode 100644 data/corefork.telegram.org/method/account.finishTakeoutSession delete mode 100644 data/corefork.telegram.org/method/account.getAccountTTL delete mode 100644 data/corefork.telegram.org/method/account.getAllSecureValues delete mode 100644 data/corefork.telegram.org/method/account.getAuthorizationForm delete mode 100644 data/corefork.telegram.org/method/account.getAuthorizations delete mode 100644 data/corefork.telegram.org/method/account.getAutoDownloadSettings delete mode 100644 data/corefork.telegram.org/method/account.getContactSignUpNotification delete mode 100644 data/corefork.telegram.org/method/account.getGlobalPrivacySettings delete mode 100644 data/corefork.telegram.org/method/account.getMultiWallPapers delete mode 100644 data/corefork.telegram.org/method/account.getNotifyExceptions delete mode 100644 data/corefork.telegram.org/method/account.getNotifySettings delete mode 100644 data/corefork.telegram.org/method/account.getPassword delete mode 100644 data/corefork.telegram.org/method/account.getPasswordSettings delete mode 100644 data/corefork.telegram.org/method/account.getPrivacy delete mode 100644 data/corefork.telegram.org/method/account.getSecureValue delete mode 100644 data/corefork.telegram.org/method/account.getTheme delete mode 100644 data/corefork.telegram.org/method/account.getThemes delete mode 100644 data/corefork.telegram.org/method/account.getTmpPassword delete mode 100644 data/corefork.telegram.org/method/account.getWallPaper delete mode 100644 data/corefork.telegram.org/method/account.getWallPapers delete mode 100644 data/corefork.telegram.org/method/account.getWebAuthorizations delete mode 100644 data/corefork.telegram.org/method/account.initTakeoutSession delete mode 100644 data/corefork.telegram.org/method/account.installTheme delete mode 100644 data/corefork.telegram.org/method/account.installWallPaper delete mode 100644 data/corefork.telegram.org/method/account.registerDevice delete mode 100644 data/corefork.telegram.org/method/account.reportPeer delete mode 100644 data/corefork.telegram.org/method/account.reportProfilePhoto delete mode 100644 data/corefork.telegram.org/method/account.resetAuthorization delete mode 100644 data/corefork.telegram.org/method/account.resetNotifySettings delete mode 100644 data/corefork.telegram.org/method/account.resetPassword delete mode 100644 data/corefork.telegram.org/method/account.resetWallPapers delete mode 100644 data/corefork.telegram.org/method/account.resetWebAuthorization delete mode 100644 data/corefork.telegram.org/method/account.resetWebAuthorizations delete mode 100644 data/corefork.telegram.org/method/account.saveAutoDownloadSettings delete mode 100644 data/corefork.telegram.org/method/account.saveSecureValue delete mode 100644 data/corefork.telegram.org/method/account.saveTheme delete mode 100644 data/corefork.telegram.org/method/account.saveWallPaper delete mode 100644 data/corefork.telegram.org/method/account.sendChangePhoneCode delete mode 100644 data/corefork.telegram.org/method/account.sendConfirmPhoneCode delete mode 100644 data/corefork.telegram.org/method/account.sendVerifyEmailCode delete mode 100644 data/corefork.telegram.org/method/account.sendVerifyPhoneCode delete mode 100644 data/corefork.telegram.org/method/account.setAccountTTL delete mode 100644 data/corefork.telegram.org/method/account.setContactSignUpNotification delete mode 100644 data/corefork.telegram.org/method/account.setContentSettings delete mode 100644 data/corefork.telegram.org/method/account.setGlobalPrivacySettings delete mode 100644 data/corefork.telegram.org/method/account.setPrivacy delete mode 100644 data/corefork.telegram.org/method/account.unregisterDevice delete mode 100644 data/corefork.telegram.org/method/account.updateDeviceLocked delete mode 100644 data/corefork.telegram.org/method/account.updateNotifySettings delete mode 100644 data/corefork.telegram.org/method/account.updatePasswordSettings delete mode 100644 data/corefork.telegram.org/method/account.updateProfile delete mode 100644 data/corefork.telegram.org/method/account.updateTheme delete mode 100644 data/corefork.telegram.org/method/account.updateUsername delete mode 100644 data/corefork.telegram.org/method/account.uploadTheme delete mode 100644 data/corefork.telegram.org/method/account.uploadWallPaper delete mode 100644 data/corefork.telegram.org/method/account.verifyEmail delete mode 100644 data/corefork.telegram.org/method/account.verifyPhone delete mode 100644 data/corefork.telegram.org/method/auth.acceptLoginToken delete mode 100644 data/corefork.telegram.org/method/auth.bindTempAuthKey delete mode 100644 data/corefork.telegram.org/method/auth.cancelCode delete mode 100644 data/corefork.telegram.org/method/auth.checkPassword delete mode 100644 data/corefork.telegram.org/method/auth.checkRecoveryPassword delete mode 100644 data/corefork.telegram.org/method/auth.dropTempAuthKeys delete mode 100644 data/corefork.telegram.org/method/auth.exportAuthorization delete mode 100644 data/corefork.telegram.org/method/auth.exportLoginToken delete mode 100644 data/corefork.telegram.org/method/auth.importAuthorization delete mode 100644 data/corefork.telegram.org/method/auth.importBotAuthorization delete mode 100644 data/corefork.telegram.org/method/auth.importLoginToken delete mode 100644 data/corefork.telegram.org/method/auth.logOut delete mode 100644 data/corefork.telegram.org/method/auth.recoverPassword delete mode 100644 data/corefork.telegram.org/method/auth.requestPasswordRecovery delete mode 100644 data/corefork.telegram.org/method/auth.resendCode delete mode 100644 data/corefork.telegram.org/method/auth.resetAuthorizations delete mode 100644 data/corefork.telegram.org/method/auth.sendCall delete mode 100644 data/corefork.telegram.org/method/auth.sendInvites delete mode 100644 data/corefork.telegram.org/method/auth.sendSms delete mode 100644 data/corefork.telegram.org/method/auth.signIn delete mode 100644 data/corefork.telegram.org/method/auth.signUp delete mode 100644 data/corefork.telegram.org/method/bots.answerWebhookJSONQuery delete mode 100644 data/corefork.telegram.org/method/bots.getBotCommands delete mode 100644 data/corefork.telegram.org/method/bots.resetBotCommands delete mode 100644 data/corefork.telegram.org/method/bots.sendCustomRequest delete mode 100644 data/corefork.telegram.org/method/bots.setBotCommands delete mode 100644 data/corefork.telegram.org/method/channels.checkUsername delete mode 100644 data/corefork.telegram.org/method/channels.convertToGigagroup delete mode 100644 data/corefork.telegram.org/method/channels.createChannel delete mode 100644 data/corefork.telegram.org/method/channels.deleteChannel delete mode 100644 data/corefork.telegram.org/method/channels.deleteHistory delete mode 100644 data/corefork.telegram.org/method/channels.deleteMessages delete mode 100644 data/corefork.telegram.org/method/channels.deleteUserHistory delete mode 100644 data/corefork.telegram.org/method/channels.editAdmin delete mode 100644 data/corefork.telegram.org/method/channels.editBanned delete mode 100644 data/corefork.telegram.org/method/channels.editCreator delete mode 100644 data/corefork.telegram.org/method/channels.editLocation delete mode 100644 data/corefork.telegram.org/method/channels.editPhoto delete mode 100644 data/corefork.telegram.org/method/channels.editTitle delete mode 100644 data/corefork.telegram.org/method/channels.exportMessageLink delete mode 100644 data/corefork.telegram.org/method/channels.getAdminLog delete mode 100644 data/corefork.telegram.org/method/channels.getAdminedPublicChannels delete mode 100644 data/corefork.telegram.org/method/channels.getChannels delete mode 100644 data/corefork.telegram.org/method/channels.getFullChannel delete mode 100644 data/corefork.telegram.org/method/channels.getGroupsForDiscussion delete mode 100644 data/corefork.telegram.org/method/channels.getInactiveChannels delete mode 100644 data/corefork.telegram.org/method/channels.getLeftChannels delete mode 100644 data/corefork.telegram.org/method/channels.getMessages delete mode 100644 data/corefork.telegram.org/method/channels.getParticipant delete mode 100644 data/corefork.telegram.org/method/channels.getParticipants delete mode 100644 data/corefork.telegram.org/method/channels.getSponsoredMessages delete mode 100644 data/corefork.telegram.org/method/channels.inviteToChannel delete mode 100644 data/corefork.telegram.org/method/channels.joinChannel delete mode 100644 data/corefork.telegram.org/method/channels.leaveChannel delete mode 100644 data/corefork.telegram.org/method/channels.readHistory delete mode 100644 data/corefork.telegram.org/method/channels.readMessageContents delete mode 100644 data/corefork.telegram.org/method/channels.reportSpam delete mode 100644 data/corefork.telegram.org/method/channels.setDiscussionGroup delete mode 100644 data/corefork.telegram.org/method/channels.setStickers delete mode 100644 data/corefork.telegram.org/method/channels.toggleSignatures delete mode 100644 data/corefork.telegram.org/method/channels.toggleSlowMode delete mode 100644 data/corefork.telegram.org/method/channels.updateUsername delete mode 100644 data/corefork.telegram.org/method/contacts.acceptContact delete mode 100644 data/corefork.telegram.org/method/contacts.addContact delete mode 100644 data/corefork.telegram.org/method/contacts.block delete mode 100644 data/corefork.telegram.org/method/contacts.blockFromReplies delete mode 100644 data/corefork.telegram.org/method/contacts.deleteByPhones delete mode 100644 data/corefork.telegram.org/method/contacts.deleteContacts delete mode 100644 data/corefork.telegram.org/method/contacts.getBlocked delete mode 100644 data/corefork.telegram.org/method/contacts.getContactIDs delete mode 100644 data/corefork.telegram.org/method/contacts.getContacts delete mode 100644 data/corefork.telegram.org/method/contacts.getLocated delete mode 100644 data/corefork.telegram.org/method/contacts.getSaved delete mode 100644 data/corefork.telegram.org/method/contacts.getStatuses delete mode 100644 data/corefork.telegram.org/method/contacts.getTopPeers delete mode 100644 data/corefork.telegram.org/method/contacts.importContacts delete mode 100644 data/corefork.telegram.org/method/contacts.resetSaved delete mode 100644 data/corefork.telegram.org/method/contacts.resetTopPeerRating delete mode 100644 data/corefork.telegram.org/method/contacts.search delete mode 100644 data/corefork.telegram.org/method/contacts.toggleTopPeers delete mode 100644 data/corefork.telegram.org/method/contacts.unblock delete mode 100644 data/corefork.telegram.org/method/folders.deleteFolder delete mode 100644 data/corefork.telegram.org/method/folders.editPeerFolders delete mode 100644 data/corefork.telegram.org/method/help.acceptTermsOfService delete mode 100644 data/corefork.telegram.org/method/help.dismissSuggestion delete mode 100644 data/corefork.telegram.org/method/help.editUserInfo delete mode 100644 data/corefork.telegram.org/method/help.getAppChangelog delete mode 100644 data/corefork.telegram.org/method/help.getAppConfig delete mode 100644 data/corefork.telegram.org/method/help.getAppUpdate delete mode 100644 data/corefork.telegram.org/method/help.getCdnConfig delete mode 100644 data/corefork.telegram.org/method/help.getConfig delete mode 100644 data/corefork.telegram.org/method/help.getCountriesList delete mode 100644 data/corefork.telegram.org/method/help.getDeepLinkInfo delete mode 100644 data/corefork.telegram.org/method/help.getInviteText delete mode 100644 data/corefork.telegram.org/method/help.getNearestDc delete mode 100644 data/corefork.telegram.org/method/help.getPassportConfig delete mode 100644 data/corefork.telegram.org/method/help.getPromoData delete mode 100644 data/corefork.telegram.org/method/help.getProxyData delete mode 100644 data/corefork.telegram.org/method/help.getRecentMeUrls delete mode 100644 data/corefork.telegram.org/method/help.getSupport delete mode 100644 data/corefork.telegram.org/method/help.getSupportName delete mode 100644 data/corefork.telegram.org/method/help.getTermsOfServiceUpdate delete mode 100644 data/corefork.telegram.org/method/help.getUserInfo delete mode 100644 data/corefork.telegram.org/method/help.hidePromoData delete mode 100644 data/corefork.telegram.org/method/help.saveAppLog delete mode 100644 data/corefork.telegram.org/method/help.setBotUpdatesStatus delete mode 100644 data/corefork.telegram.org/method/initConnection.html delete mode 100644 data/corefork.telegram.org/method/invokeAfterMsg.html delete mode 100644 data/corefork.telegram.org/method/invokeAfterMsgs.html delete mode 100644 data/corefork.telegram.org/method/invokeWithLayer.html delete mode 100644 data/corefork.telegram.org/method/invokeWithMessagesRange.html delete mode 100644 data/corefork.telegram.org/method/invokeWithTakeout.html delete mode 100644 data/corefork.telegram.org/method/invokeWithoutUpdates.html delete mode 100644 data/corefork.telegram.org/method/langpack.getDifference delete mode 100644 data/corefork.telegram.org/method/langpack.getLanguage delete mode 100644 data/corefork.telegram.org/method/langpack.getLanguages delete mode 100644 data/corefork.telegram.org/method/messages.acceptEncryption delete mode 100644 data/corefork.telegram.org/method/messages.addChatUser delete mode 100644 data/corefork.telegram.org/method/messages.checkChatInvite delete mode 100644 data/corefork.telegram.org/method/messages.checkHistoryImportPeer delete mode 100644 data/corefork.telegram.org/method/messages.clearAllDrafts delete mode 100644 data/corefork.telegram.org/method/messages.clearRecentStickers delete mode 100644 data/corefork.telegram.org/method/messages.createChat delete mode 100644 data/corefork.telegram.org/method/messages.deleteChat delete mode 100644 data/corefork.telegram.org/method/messages.deleteExportedChatInvite delete mode 100644 data/corefork.telegram.org/method/messages.deleteHistory delete mode 100644 data/corefork.telegram.org/method/messages.deleteMessages delete mode 100644 data/corefork.telegram.org/method/messages.deletePhoneCallHistory delete mode 100644 data/corefork.telegram.org/method/messages.deleteScheduledMessages delete mode 100644 data/corefork.telegram.org/method/messages.discardEncryption delete mode 100644 data/corefork.telegram.org/method/messages.editChatAbout delete mode 100644 data/corefork.telegram.org/method/messages.editChatAdmin delete mode 100644 data/corefork.telegram.org/method/messages.editChatDefaultBannedRights delete mode 100644 data/corefork.telegram.org/method/messages.editChatPhoto delete mode 100644 data/corefork.telegram.org/method/messages.editChatTitle delete mode 100644 data/corefork.telegram.org/method/messages.editExportedChatInvite delete mode 100644 data/corefork.telegram.org/method/messages.editInlineBotMessage delete mode 100644 data/corefork.telegram.org/method/messages.exportChatInvite delete mode 100644 data/corefork.telegram.org/method/messages.faveSticker delete mode 100644 data/corefork.telegram.org/method/messages.forwardMessage delete mode 100644 data/corefork.telegram.org/method/messages.forwardMessages delete mode 100644 data/corefork.telegram.org/method/messages.getAdminsWithInvites delete mode 100644 data/corefork.telegram.org/method/messages.getAllChats delete mode 100644 data/corefork.telegram.org/method/messages.getAllDrafts delete mode 100644 data/corefork.telegram.org/method/messages.getAllStickers delete mode 100644 data/corefork.telegram.org/method/messages.getArchivedStickers delete mode 100644 data/corefork.telegram.org/method/messages.getBotCallbackAnswer delete mode 100644 data/corefork.telegram.org/method/messages.getChatInviteImporters delete mode 100644 data/corefork.telegram.org/method/messages.getChats delete mode 100644 data/corefork.telegram.org/method/messages.getCommonChats delete mode 100644 data/corefork.telegram.org/method/messages.getDhConfig delete mode 100644 data/corefork.telegram.org/method/messages.getDialogFilters delete mode 100644 data/corefork.telegram.org/method/messages.getDialogUnreadMarks delete mode 100644 data/corefork.telegram.org/method/messages.getDialogs delete mode 100644 data/corefork.telegram.org/method/messages.getDocumentByHash delete mode 100644 data/corefork.telegram.org/method/messages.getEmojiKeywords delete mode 100644 data/corefork.telegram.org/method/messages.getEmojiKeywordsDifference delete mode 100644 data/corefork.telegram.org/method/messages.getEmojiKeywordsLanguages delete mode 100644 data/corefork.telegram.org/method/messages.getEmojiURL delete mode 100644 data/corefork.telegram.org/method/messages.getExportedChatInvite delete mode 100644 data/corefork.telegram.org/method/messages.getExportedChatInvites delete mode 100644 data/corefork.telegram.org/method/messages.getFavedStickers delete mode 100644 data/corefork.telegram.org/method/messages.getFeaturedStickers delete mode 100644 data/corefork.telegram.org/method/messages.getFullChat delete mode 100644 data/corefork.telegram.org/method/messages.getGameHighScores delete mode 100644 data/corefork.telegram.org/method/messages.getInlineBotResults delete mode 100644 data/corefork.telegram.org/method/messages.getInlineGameHighScores delete mode 100644 data/corefork.telegram.org/method/messages.getMaskStickers delete mode 100644 data/corefork.telegram.org/method/messages.getMessageEditData delete mode 100644 data/corefork.telegram.org/method/messages.getMessageReactionsList delete mode 100644 data/corefork.telegram.org/method/messages.getMessageReadParticipants delete mode 100644 data/corefork.telegram.org/method/messages.getMessages delete mode 100644 data/corefork.telegram.org/method/messages.getMessagesReactions delete mode 100644 data/corefork.telegram.org/method/messages.getMessagesViews delete mode 100644 data/corefork.telegram.org/method/messages.getOldFeaturedStickers delete mode 100644 data/corefork.telegram.org/method/messages.getOnlines delete mode 100644 data/corefork.telegram.org/method/messages.getPeerDialogs delete mode 100644 data/corefork.telegram.org/method/messages.getPeerSettings delete mode 100644 data/corefork.telegram.org/method/messages.getPinnedDialogs delete mode 100644 data/corefork.telegram.org/method/messages.getPollResults delete mode 100644 data/corefork.telegram.org/method/messages.getRecentLocations delete mode 100644 data/corefork.telegram.org/method/messages.getRecentStickers delete mode 100644 data/corefork.telegram.org/method/messages.getReplies delete mode 100644 data/corefork.telegram.org/method/messages.getSavedGifs delete mode 100644 data/corefork.telegram.org/method/messages.getScheduledHistory delete mode 100644 data/corefork.telegram.org/method/messages.getScheduledMessages delete mode 100644 data/corefork.telegram.org/method/messages.getSearchCounters delete mode 100644 data/corefork.telegram.org/method/messages.getSplitRanges delete mode 100644 data/corefork.telegram.org/method/messages.getStickerSet delete mode 100644 data/corefork.telegram.org/method/messages.getStickers delete mode 100644 data/corefork.telegram.org/method/messages.getSuggestedDialogFilters delete mode 100644 data/corefork.telegram.org/method/messages.getUnreadMentions delete mode 100644 data/corefork.telegram.org/method/messages.getWebPage delete mode 100644 data/corefork.telegram.org/method/messages.getWebPagePreview delete mode 100644 data/corefork.telegram.org/method/messages.hidePeerSettingsBar delete mode 100644 data/corefork.telegram.org/method/messages.importChatInvite delete mode 100644 data/corefork.telegram.org/method/messages.installStickerSet delete mode 100644 data/corefork.telegram.org/method/messages.markDialogUnread delete mode 100644 data/corefork.telegram.org/method/messages.migrateChat delete mode 100644 data/corefork.telegram.org/method/messages.readDiscussion delete mode 100644 data/corefork.telegram.org/method/messages.readEncryptedHistory delete mode 100644 data/corefork.telegram.org/method/messages.readFeaturedStickers delete mode 100644 data/corefork.telegram.org/method/messages.readHistory delete mode 100644 data/corefork.telegram.org/method/messages.readMentions delete mode 100644 data/corefork.telegram.org/method/messages.readMessageContents delete mode 100644 data/corefork.telegram.org/method/messages.receivedMessages delete mode 100644 data/corefork.telegram.org/method/messages.receivedQueue delete mode 100644 data/corefork.telegram.org/method/messages.reorderPinnedDialogs delete mode 100644 data/corefork.telegram.org/method/messages.reorderStickerSets delete mode 100644 data/corefork.telegram.org/method/messages.report delete mode 100644 data/corefork.telegram.org/method/messages.reportSpam delete mode 100644 data/corefork.telegram.org/method/messages.requestUrlAuth delete mode 100644 data/corefork.telegram.org/method/messages.saveDraft delete mode 100644 data/corefork.telegram.org/method/messages.saveGif delete mode 100644 data/corefork.telegram.org/method/messages.saveRecentSticker delete mode 100644 data/corefork.telegram.org/method/messages.search delete mode 100644 data/corefork.telegram.org/method/messages.searchGifs delete mode 100644 data/corefork.telegram.org/method/messages.searchGlobal delete mode 100644 data/corefork.telegram.org/method/messages.searchStickerSets delete mode 100644 data/corefork.telegram.org/method/messages.sendBroadcast delete mode 100644 data/corefork.telegram.org/method/messages.sendEncrypted delete mode 100644 data/corefork.telegram.org/method/messages.sendEncryptedFile delete mode 100644 data/corefork.telegram.org/method/messages.sendEncryptedService delete mode 100644 data/corefork.telegram.org/method/messages.sendInlineBotResult delete mode 100644 data/corefork.telegram.org/method/messages.sendMedia delete mode 100644 data/corefork.telegram.org/method/messages.sendMessage delete mode 100644 data/corefork.telegram.org/method/messages.sendMultiMedia delete mode 100644 data/corefork.telegram.org/method/messages.sendReaction delete mode 100644 data/corefork.telegram.org/method/messages.sendScheduledMessages delete mode 100644 data/corefork.telegram.org/method/messages.sendScreenshotNotification delete mode 100644 data/corefork.telegram.org/method/messages.sendVote delete mode 100644 data/corefork.telegram.org/method/messages.setBotPrecheckoutResults delete mode 100644 data/corefork.telegram.org/method/messages.setBotShippingResults delete mode 100644 data/corefork.telegram.org/method/messages.setChatTheme delete mode 100644 data/corefork.telegram.org/method/messages.setEncryptedTyping delete mode 100644 data/corefork.telegram.org/method/messages.setGameScore delete mode 100644 data/corefork.telegram.org/method/messages.setHistoryTTL delete mode 100644 data/corefork.telegram.org/method/messages.setInlineBotResults delete mode 100644 data/corefork.telegram.org/method/messages.setInlineGameScore delete mode 100644 data/corefork.telegram.org/method/messages.setTyping delete mode 100644 data/corefork.telegram.org/method/messages.startBot delete mode 100644 data/corefork.telegram.org/method/messages.startHistoryImport delete mode 100644 data/corefork.telegram.org/method/messages.toggleDialogPin delete mode 100644 data/corefork.telegram.org/method/messages.toggleStickerSets delete mode 100644 data/corefork.telegram.org/method/messages.uninstallStickerSet delete mode 100644 data/corefork.telegram.org/method/messages.unpinAllMessages delete mode 100644 data/corefork.telegram.org/method/messages.updateDialogFilter delete mode 100644 data/corefork.telegram.org/method/messages.updateDialogFiltersOrder delete mode 100644 data/corefork.telegram.org/method/messages.updatePinnedMessage delete mode 100644 data/corefork.telegram.org/method/messages.uploadEncryptedFile delete mode 100644 data/corefork.telegram.org/method/messages.uploadImportedMedia delete mode 100644 data/corefork.telegram.org/method/messages.uploadMedia delete mode 100644 data/corefork.telegram.org/method/payments.getBankCardData delete mode 100644 data/corefork.telegram.org/method/payments.getPaymentForm delete mode 100644 data/corefork.telegram.org/method/payments.getSavedInfo delete mode 100644 data/corefork.telegram.org/method/payments.sendPaymentForm delete mode 100644 data/corefork.telegram.org/method/payments.validateRequestedInfo delete mode 100644 data/corefork.telegram.org/method/phone.acceptCall delete mode 100644 data/corefork.telegram.org/method/phone.checkGroupCall delete mode 100644 data/corefork.telegram.org/method/phone.confirmCall delete mode 100644 data/corefork.telegram.org/method/phone.createGroupCall delete mode 100644 data/corefork.telegram.org/method/phone.discardCall delete mode 100644 data/corefork.telegram.org/method/phone.discardGroupCall delete mode 100644 data/corefork.telegram.org/method/phone.editGroupCallMember delete mode 100644 data/corefork.telegram.org/method/phone.editGroupCallTitle delete mode 100644 data/corefork.telegram.org/method/phone.exportGroupCallInvite delete mode 100644 data/corefork.telegram.org/method/phone.getCallConfig delete mode 100644 data/corefork.telegram.org/method/phone.getGroupCall delete mode 100644 data/corefork.telegram.org/method/phone.getGroupCallJoinAs delete mode 100644 data/corefork.telegram.org/method/phone.getGroupParticipants delete mode 100644 data/corefork.telegram.org/method/phone.inviteToGroupCall delete mode 100644 data/corefork.telegram.org/method/phone.joinGroupCall delete mode 100644 data/corefork.telegram.org/method/phone.joinGroupCallPresentation delete mode 100644 data/corefork.telegram.org/method/phone.leaveGroupCall delete mode 100644 data/corefork.telegram.org/method/phone.leaveGroupCallPresentation delete mode 100644 data/corefork.telegram.org/method/phone.receivedCall delete mode 100644 data/corefork.telegram.org/method/phone.requestCall delete mode 100644 data/corefork.telegram.org/method/phone.saveCallDebug delete mode 100644 data/corefork.telegram.org/method/phone.sendSignalingData delete mode 100644 data/corefork.telegram.org/method/phone.setCallRating delete mode 100644 data/corefork.telegram.org/method/phone.startScheduledGroupCall delete mode 100644 data/corefork.telegram.org/method/phone.toggleGroupCallRecord delete mode 100644 data/corefork.telegram.org/method/phone.toggleGroupCallSettings delete mode 100644 data/corefork.telegram.org/method/phone.toggleGroupCallStartSubscription delete mode 100644 data/corefork.telegram.org/method/photos.deletePhotos delete mode 100644 data/corefork.telegram.org/method/photos.getUserPhotos delete mode 100644 data/corefork.telegram.org/method/photos.updateProfilePhoto delete mode 100644 data/corefork.telegram.org/method/stats.getBroadcastStats delete mode 100644 data/corefork.telegram.org/method/stats.getMegagroupStats delete mode 100644 data/corefork.telegram.org/method/stats.loadAsyncGraph delete mode 100644 data/corefork.telegram.org/method/stickers.changeStickerPosition delete mode 100644 data/corefork.telegram.org/method/stickers.checkShortName delete mode 100644 data/corefork.telegram.org/method/stickers.createStickerSet delete mode 100644 data/corefork.telegram.org/method/stickers.removeStickerFromSet delete mode 100644 data/corefork.telegram.org/method/stickers.setStickerSetThumb delete mode 100644 data/corefork.telegram.org/method/stickers.suggestShortName delete mode 100644 data/corefork.telegram.org/method/updates.getChannelDifference delete mode 100644 data/corefork.telegram.org/method/updates.getDifference delete mode 100644 data/corefork.telegram.org/method/updates.getState delete mode 100644 data/corefork.telegram.org/method/upload.getCdnFile delete mode 100644 data/corefork.telegram.org/method/upload.getCdnFileHashes delete mode 100644 data/corefork.telegram.org/method/upload.getFile delete mode 100644 data/corefork.telegram.org/method/upload.getFileHashes delete mode 100644 data/corefork.telegram.org/method/upload.getWebFile delete mode 100644 data/corefork.telegram.org/method/upload.reuploadCdnFile delete mode 100644 data/corefork.telegram.org/method/upload.saveBigFilePart delete mode 100644 data/corefork.telegram.org/method/users.getUsers delete mode 100644 data/corefork.telegram.org/method/users.setSecureValueErrors delete mode 100644 data/corefork.telegram.org/mtproto.html delete mode 100644 data/corefork.telegram.org/mtproto/TL-abstract-types.html delete mode 100644 data/corefork.telegram.org/mtproto/TL-combinators.html delete mode 100644 data/corefork.telegram.org/mtproto/TL-dependent.html delete mode 100644 data/corefork.telegram.org/mtproto/TL-formal.html delete mode 100644 data/corefork.telegram.org/mtproto/TL-optargs.html delete mode 100644 data/corefork.telegram.org/mtproto/TL-patterns.html delete mode 100644 data/corefork.telegram.org/mtproto/TL-polymorph.html delete mode 100644 data/corefork.telegram.org/mtproto/TL-tl.html delete mode 100644 data/corefork.telegram.org/mtproto/TL-types.html delete mode 100644 data/corefork.telegram.org/mtproto/TL.html delete mode 100644 data/corefork.telegram.org/mtproto/description.html delete mode 100644 data/corefork.telegram.org/mtproto/description_v1.html delete mode 100644 data/corefork.telegram.org/mtproto/mtproto-transports.html delete mode 100644 data/corefork.telegram.org/mtproto/samples-auth_key.html delete mode 100644 data/corefork.telegram.org/mtproto/security_guidelines.html delete mode 100644 data/corefork.telegram.org/mtproto/security_guidelines_v1.html delete mode 100644 data/corefork.telegram.org/mtproto/serialize.html delete mode 100644 data/corefork.telegram.org/mtproto/service_messages.html delete mode 100644 data/corefork.telegram.org/mtproto/service_messages_about_messages.html delete mode 100644 data/corefork.telegram.org/mtproto_v1.html delete mode 100644 data/corefork.telegram.org/passport.html delete mode 100644 data/corefork.telegram.org/passport/encryption.html delete mode 100644 data/corefork.telegram.org/passport/example.html delete mode 100644 data/corefork.telegram.org/passport/sdk-android.html delete mode 100644 data/corefork.telegram.org/passport/sdk-ios-mac.html delete mode 100644 data/corefork.telegram.org/passport/sdk-javascript.html delete mode 100644 data/corefork.telegram.org/schema/end-to-end-json.html delete mode 100644 data/corefork.telegram.org/schema/end-to-end.html delete mode 100644 data/corefork.telegram.org/schema/json.html delete mode 100644 data/corefork.telegram.org/schema/mtproto-json.html delete mode 100644 data/corefork.telegram.org/schema/mtproto.html delete mode 100644 data/corefork.telegram.org/type/AccountDaysTTL.html delete mode 100644 data/corefork.telegram.org/type/Audio.html delete mode 100644 data/corefork.telegram.org/type/Authorization.html delete mode 100644 data/corefork.telegram.org/type/AutoDownloadSettings.html delete mode 100644 data/corefork.telegram.org/type/BankCardOpenUrl.html delete mode 100644 data/corefork.telegram.org/type/BaseTheme.html delete mode 100644 data/corefork.telegram.org/type/Bool.html delete mode 100644 data/corefork.telegram.org/type/BotCommand.html delete mode 100644 data/corefork.telegram.org/type/BotCommandScope.html delete mode 100644 data/corefork.telegram.org/type/BotInfo.html delete mode 100644 data/corefork.telegram.org/type/BotInlineMessage.html delete mode 100644 data/corefork.telegram.org/type/BotInlineResult.html delete mode 100644 data/corefork.telegram.org/type/CdnConfig.html delete mode 100644 data/corefork.telegram.org/type/CdnPublicKey.html delete mode 100644 data/corefork.telegram.org/type/ChannelAdminLogEvent.html delete mode 100644 data/corefork.telegram.org/type/ChannelAdminLogEventAction.html delete mode 100644 data/corefork.telegram.org/type/ChannelAdminLogEventsFilter.html delete mode 100644 data/corefork.telegram.org/type/ChannelLocation.html delete mode 100644 data/corefork.telegram.org/type/ChannelMessagesFilter.html delete mode 100644 data/corefork.telegram.org/type/ChannelParticipantsFilter.html delete mode 100644 data/corefork.telegram.org/type/Chat.html delete mode 100644 data/corefork.telegram.org/type/ChatAdminWithInvites.html delete mode 100644 data/corefork.telegram.org/type/ChatBannedRights.html delete mode 100644 data/corefork.telegram.org/type/ChatFull.html delete mode 100644 data/corefork.telegram.org/type/ChatInvite.html delete mode 100644 data/corefork.telegram.org/type/ChatInviteImporter.html delete mode 100644 data/corefork.telegram.org/type/ChatOnlines.html delete mode 100644 data/corefork.telegram.org/type/ChatParticipant.html delete mode 100644 data/corefork.telegram.org/type/ChatParticipants.html delete mode 100644 data/corefork.telegram.org/type/ChatPhoto.html delete mode 100644 data/corefork.telegram.org/type/ChatTheme.html delete mode 100644 data/corefork.telegram.org/type/CodeSettings.html delete mode 100644 data/corefork.telegram.org/type/Config.html delete mode 100644 data/corefork.telegram.org/type/Contact.html delete mode 100644 data/corefork.telegram.org/type/DataJSON.html delete mode 100644 data/corefork.telegram.org/type/DcOption.html delete mode 100644 data/corefork.telegram.org/type/DecryptedDataBlock.html delete mode 100644 data/corefork.telegram.org/type/DecryptedMessage.html delete mode 100644 data/corefork.telegram.org/type/DecryptedMessageAction.html delete mode 100644 data/corefork.telegram.org/type/DecryptedMessageLayer.html delete mode 100644 data/corefork.telegram.org/type/DecryptedMessageMedia.html delete mode 100644 data/corefork.telegram.org/type/Dialog.html delete mode 100644 data/corefork.telegram.org/type/DialogFilter.html delete mode 100644 data/corefork.telegram.org/type/DialogFilterSuggested.html delete mode 100644 data/corefork.telegram.org/type/DialogPeer.html delete mode 100644 data/corefork.telegram.org/type/DisabledFeature.html delete mode 100644 data/corefork.telegram.org/type/Document.html delete mode 100644 data/corefork.telegram.org/type/DocumentAttribute.html delete mode 100644 data/corefork.telegram.org/type/DraftMessage.html delete mode 100644 data/corefork.telegram.org/type/EmojiKeyword.html delete mode 100644 data/corefork.telegram.org/type/EmojiKeywordsDifference.html delete mode 100644 data/corefork.telegram.org/type/EmojiLanguage.html delete mode 100644 data/corefork.telegram.org/type/EmojiURL.html delete mode 100644 data/corefork.telegram.org/type/EncryptedChat.html delete mode 100644 data/corefork.telegram.org/type/EncryptedFile.html delete mode 100644 data/corefork.telegram.org/type/EncryptedMessage.html delete mode 100644 data/corefork.telegram.org/type/Error.html delete mode 100644 data/corefork.telegram.org/type/ExportedChatInvite.html delete mode 100644 data/corefork.telegram.org/type/ExportedMessageLink.html delete mode 100644 data/corefork.telegram.org/type/FileLocation.html delete mode 100644 data/corefork.telegram.org/type/Folder.html delete mode 100644 data/corefork.telegram.org/type/FolderPeer.html delete mode 100644 data/corefork.telegram.org/type/Game.html delete mode 100644 data/corefork.telegram.org/type/GeoPoint.html delete mode 100644 data/corefork.telegram.org/type/GlobalPrivacySettings.html delete mode 100644 data/corefork.telegram.org/type/GroupCall.html delete mode 100644 data/corefork.telegram.org/type/GroupCallParticipant.html delete mode 100644 data/corefork.telegram.org/type/GroupCallParticipantVideo.html delete mode 100644 data/corefork.telegram.org/type/GroupCallParticipantVideoSourceGroup.html delete mode 100644 data/corefork.telegram.org/type/HighScore.html delete mode 100644 data/corefork.telegram.org/type/ImportedContact.html delete mode 100644 data/corefork.telegram.org/type/InlineBotSwitchPM.html delete mode 100644 data/corefork.telegram.org/type/InlineQueryPeerType.html delete mode 100644 data/corefork.telegram.org/type/InputAppEvent.html delete mode 100644 data/corefork.telegram.org/type/InputBotInlineMessage.html delete mode 100644 data/corefork.telegram.org/type/InputBotInlineMessageID.html delete mode 100644 data/corefork.telegram.org/type/InputBotInlineResult.html delete mode 100644 data/corefork.telegram.org/type/InputChannel.html delete mode 100644 data/corefork.telegram.org/type/InputChatPhoto.html delete mode 100644 data/corefork.telegram.org/type/InputCheckPasswordSRP.html delete mode 100644 data/corefork.telegram.org/type/InputClientProxy.html delete mode 100644 data/corefork.telegram.org/type/InputContact.html delete mode 100644 data/corefork.telegram.org/type/InputDialogPeer.html delete mode 100644 data/corefork.telegram.org/type/InputDocument.html delete mode 100644 data/corefork.telegram.org/type/InputEncryptedChat.html delete mode 100644 data/corefork.telegram.org/type/InputEncryptedFile.html delete mode 100644 data/corefork.telegram.org/type/InputFile.html delete mode 100644 data/corefork.telegram.org/type/InputFileLocation.html delete mode 100644 data/corefork.telegram.org/type/InputFolderPeer.html delete mode 100644 data/corefork.telegram.org/type/InputGame.html delete mode 100644 data/corefork.telegram.org/type/InputGroupCall.html delete mode 100644 data/corefork.telegram.org/type/InputMedia.html delete mode 100644 data/corefork.telegram.org/type/InputMessage.html delete mode 100644 data/corefork.telegram.org/type/InputNotifyPeer.html delete mode 100644 data/corefork.telegram.org/type/InputPaymentCredentials.html delete mode 100644 data/corefork.telegram.org/type/InputPeer.html delete mode 100644 data/corefork.telegram.org/type/InputPeerNotifySettings.html delete mode 100644 data/corefork.telegram.org/type/InputPhoneCall.html delete mode 100644 data/corefork.telegram.org/type/InputPhoto.html delete mode 100644 data/corefork.telegram.org/type/InputPrivacyKey.html delete mode 100644 data/corefork.telegram.org/type/InputPrivacyRule.html delete mode 100644 data/corefork.telegram.org/type/InputSecureFile.html delete mode 100644 data/corefork.telegram.org/type/InputSecureValue.html delete mode 100644 data/corefork.telegram.org/type/InputSingleMedia.html delete mode 100644 data/corefork.telegram.org/type/InputStickerSet.html delete mode 100644 data/corefork.telegram.org/type/InputStickerSetItem.html delete mode 100644 data/corefork.telegram.org/type/InputStickeredMedia.html delete mode 100644 data/corefork.telegram.org/type/InputTheme.html delete mode 100644 data/corefork.telegram.org/type/InputThemeSettings.html delete mode 100644 data/corefork.telegram.org/type/InputUser.html delete mode 100644 data/corefork.telegram.org/type/InputWallPaper.html delete mode 100644 data/corefork.telegram.org/type/InputWebDocument.html delete mode 100644 data/corefork.telegram.org/type/InputWebFileLocation.html delete mode 100644 data/corefork.telegram.org/type/Invoice.html delete mode 100644 data/corefork.telegram.org/type/JSONObjectValue.html delete mode 100644 data/corefork.telegram.org/type/JSONValue.html delete mode 100644 data/corefork.telegram.org/type/KeyboardButton.html delete mode 100644 data/corefork.telegram.org/type/KeyboardButtonRow.html delete mode 100644 data/corefork.telegram.org/type/LabeledPrice.html delete mode 100644 data/corefork.telegram.org/type/LangPackDifference.html delete mode 100644 data/corefork.telegram.org/type/LangPackLanguage.html delete mode 100644 data/corefork.telegram.org/type/LangPackString.html delete mode 100644 data/corefork.telegram.org/type/MaskCoords.html delete mode 100644 data/corefork.telegram.org/type/Message.html delete mode 100644 data/corefork.telegram.org/type/MessageAction.html delete mode 100644 data/corefork.telegram.org/type/MessageEntity.html delete mode 100644 data/corefork.telegram.org/type/MessageFwdHeader.html delete mode 100644 data/corefork.telegram.org/type/MessageInteractionCounters.html delete mode 100644 data/corefork.telegram.org/type/MessageRange.html delete mode 100644 data/corefork.telegram.org/type/MessageReactionsList.html delete mode 100644 data/corefork.telegram.org/type/MessageReplies.html delete mode 100644 data/corefork.telegram.org/type/MessageReplyHeader.html delete mode 100644 data/corefork.telegram.org/type/MessageUserVote.html delete mode 100644 data/corefork.telegram.org/type/MessageViews.html delete mode 100644 data/corefork.telegram.org/type/MessagesFilter.html delete mode 100644 data/corefork.telegram.org/type/NearestDc.html delete mode 100644 data/corefork.telegram.org/type/NotifyPeer.html delete mode 100644 data/corefork.telegram.org/type/Null.html delete mode 100644 data/corefork.telegram.org/type/Page.html delete mode 100644 data/corefork.telegram.org/type/PageBlock.html delete mode 100644 data/corefork.telegram.org/type/PageCaption.html delete mode 100644 data/corefork.telegram.org/type/PageListItem.html delete mode 100644 data/corefork.telegram.org/type/PageListOrderedItem.html delete mode 100644 data/corefork.telegram.org/type/PageRelatedArticle.html delete mode 100644 data/corefork.telegram.org/type/PageTableCell.html delete mode 100644 data/corefork.telegram.org/type/PageTableRow.html delete mode 100644 data/corefork.telegram.org/type/PasswordKdfAlgo.html delete mode 100644 data/corefork.telegram.org/type/PaymentCharge.html delete mode 100644 data/corefork.telegram.org/type/PaymentRequestedInfo.html delete mode 100644 data/corefork.telegram.org/type/PaymentSavedCredentials.html delete mode 100644 data/corefork.telegram.org/type/Peer.html delete mode 100644 data/corefork.telegram.org/type/PeerBlocked.html delete mode 100644 data/corefork.telegram.org/type/PeerLocated.html delete mode 100644 data/corefork.telegram.org/type/PeerNotifySettings.html delete mode 100644 data/corefork.telegram.org/type/PeerSettings.html delete mode 100644 data/corefork.telegram.org/type/PhoneCall.html delete mode 100644 data/corefork.telegram.org/type/PhoneCallDiscardReason.html delete mode 100644 data/corefork.telegram.org/type/PhoneCallProtocol.html delete mode 100644 data/corefork.telegram.org/type/PhotoSize.html delete mode 100644 data/corefork.telegram.org/type/Poll.html delete mode 100644 data/corefork.telegram.org/type/PollAnswer.html delete mode 100644 data/corefork.telegram.org/type/PollAnswerVoters.html delete mode 100644 data/corefork.telegram.org/type/PollResults.html delete mode 100644 data/corefork.telegram.org/type/PopularContact.html delete mode 100644 data/corefork.telegram.org/type/PostAddress.html delete mode 100644 data/corefork.telegram.org/type/PrivacyKey.html delete mode 100644 data/corefork.telegram.org/type/PrivacyRule.html delete mode 100644 data/corefork.telegram.org/type/ReceivedNotifyMessage.html delete mode 100644 data/corefork.telegram.org/type/RecentMeUrl.html delete mode 100644 data/corefork.telegram.org/type/ReplyMarkup.html delete mode 100644 data/corefork.telegram.org/type/ReportReason.html delete mode 100644 data/corefork.telegram.org/type/RestrictionReason.html delete mode 100644 data/corefork.telegram.org/type/RichText.html delete mode 100644 data/corefork.telegram.org/type/SavedContact.html delete mode 100644 data/corefork.telegram.org/type/SecureCredentialsEncrypted.html delete mode 100644 data/corefork.telegram.org/type/SecureData.html delete mode 100644 data/corefork.telegram.org/type/SecureFile.html delete mode 100644 data/corefork.telegram.org/type/SecurePasswordKdfAlgo.html delete mode 100644 data/corefork.telegram.org/type/SecurePlainData.html delete mode 100644 data/corefork.telegram.org/type/SecureRequiredType.html delete mode 100644 data/corefork.telegram.org/type/SecureSecretSettings.html delete mode 100644 data/corefork.telegram.org/type/SecureValue.html delete mode 100644 data/corefork.telegram.org/type/SecureValueError.html delete mode 100644 data/corefork.telegram.org/type/SecureValueHash.html delete mode 100644 data/corefork.telegram.org/type/SecureValueType.html delete mode 100644 data/corefork.telegram.org/type/SendMessageAction.html delete mode 100644 data/corefork.telegram.org/type/ShippingOption.html delete mode 100644 data/corefork.telegram.org/type/SponsoredMessage.html delete mode 100644 data/corefork.telegram.org/type/StatsAbsValueAndPrev.html delete mode 100644 data/corefork.telegram.org/type/StatsDateRangeDays.html delete mode 100644 data/corefork.telegram.org/type/StatsGroupTopAdmin.html delete mode 100644 data/corefork.telegram.org/type/StatsGroupTopInviter.html delete mode 100644 data/corefork.telegram.org/type/StatsGroupTopPoster.html delete mode 100644 data/corefork.telegram.org/type/StatsPercentValue.html delete mode 100644 data/corefork.telegram.org/type/StatsURL.html delete mode 100644 data/corefork.telegram.org/type/StickerPack.html delete mode 100644 data/corefork.telegram.org/type/StickerSet.html delete mode 100644 data/corefork.telegram.org/type/StickerSetCovered.html delete mode 100644 data/corefork.telegram.org/type/Theme.html delete mode 100644 data/corefork.telegram.org/type/ThemeSettings.html delete mode 100644 data/corefork.telegram.org/type/TopPeer.html delete mode 100644 data/corefork.telegram.org/type/TopPeerCategory.html delete mode 100644 data/corefork.telegram.org/type/TopPeerCategoryPeers.html delete mode 100644 data/corefork.telegram.org/type/True.html delete mode 100644 data/corefork.telegram.org/type/Update.html delete mode 100644 data/corefork.telegram.org/type/Updates.html delete mode 100644 data/corefork.telegram.org/type/UrlAuthResult.html delete mode 100644 data/corefork.telegram.org/type/User.html delete mode 100644 data/corefork.telegram.org/type/UserFull.html delete mode 100644 data/corefork.telegram.org/type/UserProfilePhoto.html delete mode 100644 data/corefork.telegram.org/type/UserStatus.html delete mode 100644 data/corefork.telegram.org/type/Vector t.html delete mode 100644 data/corefork.telegram.org/type/Video.html delete mode 100644 data/corefork.telegram.org/type/VideoSize.html delete mode 100644 data/corefork.telegram.org/type/WallPaper.html delete mode 100644 data/corefork.telegram.org/type/WebAuthorization.html delete mode 100644 data/corefork.telegram.org/type/WebDocument.html delete mode 100644 data/corefork.telegram.org/type/account.AuthorizationForm delete mode 100644 data/corefork.telegram.org/type/account.Authorizations delete mode 100644 data/corefork.telegram.org/type/account.AutoDownloadSettings delete mode 100644 data/corefork.telegram.org/type/account.ChatThemes delete mode 100644 data/corefork.telegram.org/type/account.ContentSettings delete mode 100644 data/corefork.telegram.org/type/account.Password delete mode 100644 data/corefork.telegram.org/type/account.PasswordInputSettings delete mode 100644 data/corefork.telegram.org/type/account.PasswordSettings delete mode 100644 data/corefork.telegram.org/type/account.PrivacyRules delete mode 100644 data/corefork.telegram.org/type/account.ResetPasswordResult delete mode 100644 data/corefork.telegram.org/type/account.SentChangePhoneCode delete mode 100644 data/corefork.telegram.org/type/account.SentEmailCode delete mode 100644 data/corefork.telegram.org/type/account.Takeout delete mode 100644 data/corefork.telegram.org/type/account.Themes delete mode 100644 data/corefork.telegram.org/type/account.TmpPassword delete mode 100644 data/corefork.telegram.org/type/account.WallPapers delete mode 100644 data/corefork.telegram.org/type/account.WebAuthorizations delete mode 100644 data/corefork.telegram.org/type/auth.Authorization delete mode 100644 data/corefork.telegram.org/type/auth.CheckedPhone delete mode 100644 data/corefork.telegram.org/type/auth.ExportedAuthorization delete mode 100644 data/corefork.telegram.org/type/auth.LoginToken delete mode 100644 data/corefork.telegram.org/type/auth.PasswordRecovery delete mode 100644 data/corefork.telegram.org/type/auth.SentCode delete mode 100644 data/corefork.telegram.org/type/bytes.html delete mode 100644 data/corefork.telegram.org/type/channels.AdminLogResults delete mode 100644 data/corefork.telegram.org/type/channels.ChannelParticipant delete mode 100644 data/corefork.telegram.org/type/channels.ChannelParticipants delete mode 100644 data/corefork.telegram.org/type/contacts.Blocked delete mode 100644 data/corefork.telegram.org/type/contacts.Contacts delete mode 100644 data/corefork.telegram.org/type/contacts.Found delete mode 100644 data/corefork.telegram.org/type/contacts.ImportedContacts delete mode 100644 data/corefork.telegram.org/type/contacts.Link delete mode 100644 data/corefork.telegram.org/type/contacts.ResolvedPeer delete mode 100644 data/corefork.telegram.org/type/contacts.TopPeers delete mode 100644 data/corefork.telegram.org/type/double.html delete mode 100644 data/corefork.telegram.org/type/help.AppUpdate delete mode 100644 data/corefork.telegram.org/type/help.CountriesList delete mode 100644 data/corefork.telegram.org/type/help.Country delete mode 100644 data/corefork.telegram.org/type/help.CountryCode delete mode 100644 data/corefork.telegram.org/type/help.DeepLinkInfo delete mode 100644 data/corefork.telegram.org/type/help.InviteText delete mode 100644 data/corefork.telegram.org/type/help.PassportConfig delete mode 100644 data/corefork.telegram.org/type/help.PromoData delete mode 100644 data/corefork.telegram.org/type/help.ProxyData delete mode 100644 data/corefork.telegram.org/type/help.RecentMeUrls delete mode 100644 data/corefork.telegram.org/type/help.Support delete mode 100644 data/corefork.telegram.org/type/help.SupportName delete mode 100644 data/corefork.telegram.org/type/help.TermsOfService delete mode 100644 data/corefork.telegram.org/type/help.TermsOfServiceUpdate delete mode 100644 data/corefork.telegram.org/type/help.UserInfo delete mode 100644 data/corefork.telegram.org/type/int.html delete mode 100644 data/corefork.telegram.org/type/long.html delete mode 100644 data/corefork.telegram.org/type/messages.AffectedFoundMessages delete mode 100644 data/corefork.telegram.org/type/messages.AffectedHistory delete mode 100644 data/corefork.telegram.org/type/messages.AffectedMessages delete mode 100644 data/corefork.telegram.org/type/messages.AllStickers delete mode 100644 data/corefork.telegram.org/type/messages.ArchivedStickers delete mode 100644 data/corefork.telegram.org/type/messages.BotCallbackAnswer delete mode 100644 data/corefork.telegram.org/type/messages.BotResults delete mode 100644 data/corefork.telegram.org/type/messages.ChatAdminsWithInvites delete mode 100644 data/corefork.telegram.org/type/messages.ChatFull delete mode 100644 data/corefork.telegram.org/type/messages.ChatInviteImporters delete mode 100644 data/corefork.telegram.org/type/messages.Chats delete mode 100644 data/corefork.telegram.org/type/messages.CheckedHistoryImportPeer delete mode 100644 data/corefork.telegram.org/type/messages.DhConfig delete mode 100644 data/corefork.telegram.org/type/messages.Dialogs delete mode 100644 data/corefork.telegram.org/type/messages.DiscussionMessage delete mode 100644 data/corefork.telegram.org/type/messages.ExportedChatInvite delete mode 100644 data/corefork.telegram.org/type/messages.ExportedChatInvites delete mode 100644 data/corefork.telegram.org/type/messages.FavedStickers delete mode 100644 data/corefork.telegram.org/type/messages.FeaturedStickers delete mode 100644 data/corefork.telegram.org/type/messages.FoundGifs delete mode 100644 data/corefork.telegram.org/type/messages.FoundStickerSets delete mode 100644 data/corefork.telegram.org/type/messages.HighScores delete mode 100644 data/corefork.telegram.org/type/messages.HistoryImport delete mode 100644 data/corefork.telegram.org/type/messages.HistoryImportParsed delete mode 100644 data/corefork.telegram.org/type/messages.InactiveChats delete mode 100644 data/corefork.telegram.org/type/messages.MessageEditData delete mode 100644 data/corefork.telegram.org/type/messages.MessageViews delete mode 100644 data/corefork.telegram.org/type/messages.Messages delete mode 100644 data/corefork.telegram.org/type/messages.PeerDialogs delete mode 100644 data/corefork.telegram.org/type/messages.RecentStickers delete mode 100644 data/corefork.telegram.org/type/messages.SavedGifs delete mode 100644 data/corefork.telegram.org/type/messages.SearchCounter delete mode 100644 data/corefork.telegram.org/type/messages.SentEncryptedMessage delete mode 100644 data/corefork.telegram.org/type/messages.SentMessage delete mode 100644 data/corefork.telegram.org/type/messages.SponsoredMessages delete mode 100644 data/corefork.telegram.org/type/messages.StatedMessage delete mode 100644 data/corefork.telegram.org/type/messages.StatedMessages delete mode 100644 data/corefork.telegram.org/type/messages.StickerSet delete mode 100644 data/corefork.telegram.org/type/messages.StickerSetInstallResult delete mode 100644 data/corefork.telegram.org/type/messages.Stickers delete mode 100644 data/corefork.telegram.org/type/messages.VotesList delete mode 100644 data/corefork.telegram.org/type/payments.PaymentForm delete mode 100644 data/corefork.telegram.org/type/payments.PaymentResult delete mode 100644 data/corefork.telegram.org/type/payments.SavedInfo delete mode 100644 data/corefork.telegram.org/type/payments.ValidatedRequestedInfo delete mode 100644 data/corefork.telegram.org/type/phone.ExportedGroupCallInvite delete mode 100644 data/corefork.telegram.org/type/phone.GroupCall delete mode 100644 data/corefork.telegram.org/type/phone.GroupParticipants delete mode 100644 data/corefork.telegram.org/type/phone.JoinAsPeers delete mode 100644 data/corefork.telegram.org/type/phone.PhoneCall delete mode 100644 data/corefork.telegram.org/type/photos.Photos delete mode 100644 data/corefork.telegram.org/type/stats.BroadcastStats delete mode 100644 data/corefork.telegram.org/type/stats.MegagroupStats delete mode 100644 data/corefork.telegram.org/type/stats.MessageStats delete mode 100644 data/corefork.telegram.org/type/stickers.SuggestedShortName delete mode 100644 data/corefork.telegram.org/type/storage.FileType delete mode 100644 data/corefork.telegram.org/type/string.html delete mode 100644 data/corefork.telegram.org/type/updates.ChannelDifference delete mode 100644 data/corefork.telegram.org/type/updates.Difference delete mode 100644 data/corefork.telegram.org/type/updates.State delete mode 100644 data/corefork.telegram.org/type/upload.CdnFile delete mode 100644 data/corefork.telegram.org/type/upload.File delete mode 100644 data/corefork.telegram.org/type/upload.WebFile delete mode 100644 data/corefork.telegram.org/widgets.html delete mode 100644 data/corefork.telegram.org/widgets/discussion.html delete mode 100644 data/corefork.telegram.org/widgets/login.html delete mode 100644 data/corefork.telegram.org/widgets/post.html delete mode 100644 data/corefork.telegram.org/widgets/share.html delete mode 100644 data/telegram.org.html delete mode 100644 data/telegram.org/android.html delete mode 100644 data/telegram.org/blog.html delete mode 100644 data/telegram.org/blog/400-million.html delete mode 100644 data/telegram.org/blog/admin-revolution.html delete mode 100644 data/telegram.org/blog/albums-saved-messages.html delete mode 100644 data/telegram.org/blog/android-2-0.html delete mode 100644 data/telegram.org/blog/android-themes.html delete mode 100644 data/telegram.org/blog/archive-and-new-design.html delete mode 100644 data/telegram.org/blog/autodelete-inv2.html delete mode 100644 data/telegram.org/blog/bots-2-0.html delete mode 100644 data/telegram.org/blog/cache-and-stickers.html delete mode 100644 data/telegram.org/blog/captions-places.html delete mode 100644 data/telegram.org/blog/channels-2-0.html delete mode 100644 data/telegram.org/blog/channels.html delete mode 100644 data/telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html delete mode 100644 data/telegram.org/blog/contacts-local-groups.html delete mode 100644 data/telegram.org/blog/coronavirus.html delete mode 100644 data/telegram.org/blog/cryptocontest.html delete mode 100644 data/telegram.org/blog/desktop-1-0.html delete mode 100644 data/telegram.org/blog/desktop-compact.html delete mode 100644 data/telegram.org/blog/discover-stickers-and-more.html delete mode 100644 data/telegram.org/blog/edit.html delete mode 100644 data/telegram.org/blog/export-and-more.html delete mode 100644 data/telegram.org/blog/filters-anonymous-admins-comments.html delete mode 100644 data/telegram.org/blog/group-video-calls.html delete mode 100644 data/telegram.org/blog/inline-bots.html delete mode 100644 data/telegram.org/blog/instant-camera.html delete mode 100644 data/telegram.org/blog/invite-links.html delete mode 100644 data/telegram.org/blog/live-streams-forwarding-next-channel.html delete mode 100644 data/telegram.org/blog/masks.html delete mode 100644 data/telegram.org/blog/moar-stickers.html delete mode 100644 data/telegram.org/blog/move-history.html delete mode 100644 data/telegram.org/blog/new-profiles-people-nearby.html delete mode 100644 data/telegram.org/blog/passport.html delete mode 100644 data/telegram.org/blog/payments-2-0-scheduled-voice-chats.html delete mode 100644 data/telegram.org/blog/payments.html delete mode 100644 data/telegram.org/blog/photo-editor-and-passcodes.html delete mode 100644 data/telegram.org/blog/polls-2-0-vmq.html delete mode 100644 data/telegram.org/blog/polls.html delete mode 100644 data/telegram.org/blog/privacy-discussions-web-bots.html delete mode 100644 data/telegram.org/blog/privacy-revolution.html delete mode 100644 data/telegram.org/blog/reactions-spoilers-translations.html delete mode 100644 data/telegram.org/blog/replies-mentions-stickers.html delete mode 100644 data/telegram.org/blog/scheduled-reminders-themes.html delete mode 100644 data/telegram.org/blog/shared-links.html delete mode 100644 data/telegram.org/blog/silent-messages-slow-mode.html delete mode 100644 data/telegram.org/blog/stickers-meet-art-and-history.html delete mode 100644 data/telegram.org/blog/stickers-revolution.html delete mode 100644 data/telegram.org/blog/supergroups.html delete mode 100644 data/telegram.org/blog/telegram-me-change-number-and-pfs.html delete mode 100644 data/telegram.org/blog/translations-iv2.html delete mode 100644 data/telegram.org/blog/video-1000.html delete mode 100644 data/telegram.org/blog/video-calls.html delete mode 100644 data/telegram.org/blog/video-editor-gifs.html delete mode 100644 data/telegram.org/blog/video-messages-and-telescope.html delete mode 100644 data/telegram.org/blog/video-stickers-better-reactions.html delete mode 100644 data/telegram.org/blog/voice-chats-on-steroids.html delete mode 100644 data/telegram.org/blog/voice-chats.html delete mode 100644 data/telegram.org/blog/winter-contest-ends.html delete mode 100644 data/telegram.org/faq_channels.html delete mode 100644 data/telegram.org/faq_spam.html delete mode 100644 data/telegram.org/privacy.html delete mode 100644 data/telegram.org/support.html delete mode 100644 data/telegram.org/teststore.html delete mode 100644 data/telegram.org/tour/channels.html delete mode 100644 data/telegram.org/tour/groups.html delete mode 100644 data/telegram.org/tour/quizbot.html delete mode 100644 data/telegram.org/tour/screenshots.html delete mode 100644 data/telegram.org/verify.html diff --git a/data/core.telegram.org.html b/data/core.telegram.org.html deleted file mode 100644 index f6775268b5..0000000000 --- a/data/core.telegram.org.html +++ /dev/null @@ -1,253 +0,0 @@ - - - - - Telegram APIs - - - - - - - - - - - - - -
- -
-
-
-
-

Telegram APIs

- -

We offer two kinds of APIs for developers. The Bot API allows you to easily create programs that use Telegram messages for an interface. The Telegram API and TDLib allow you to build your own customized Telegram clients. You are welcome to use both APIs free of charge.

-

You can also add Telegram Widgets to your website.

-

Designers are welcome to create Animated Stickers or Custom Themes for Telegram.

-
-

Bot API

-
- -
-

This API allows you to connect bots to our system. Telegram Bots are special accounts that do not require an additional phone number to set up. These accounts serve as an interface for code running somewhere on your server.

-

To use this, you don't need to know anything about how our MTProto encryption protocol works — our intermediary server will handle all encryption and communication with the Telegram API for you. You communicate with this server via a simple HTTPS-interface that offers a simplified version of the Telegram API.

-
-

Learn more about the Bot API here »

-
-

Bot developers can also make use of our Payments API to accept payments from Telegram users around the world.

-
-

TDLib – build your own Telegram

-

Even if you're looking for maximum customization, you don't have to create your app from scratch. Try our Telegram Database Library (or simply TDLib), a tool for third-party developers that makes it easy to build fast, secure and feature-rich Telegram apps.

-

TDLib takes care of all network implementation details, encryption and local data storage, so that you can dedicate more time to design, responsive interfaces and beautiful animations.

-

TDLib supports all Telegram features and makes developing Telegram apps a breeze on any platform. It can be used on Android, iOS, Windows, macOS, Linux and virtually any other system. The library is open source and compatible with virtually any programming language.

-
-

Learn more about TDLib here »

-
-
-

Telegram API

-

This API allows you to build your own customized Telegram clients. It is 100% open for all developers who wish to create Telegram applications on our platform. Feel free to study the open source code of existing Telegram applications for examples of how things work here. Don't forget to register your application in our system.

- -

Getting started

-

Creating an application

-

How to get your application identifier and create a new Telegram app.

-

User authorization

-

How to register a user's phone to start using the API.

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

-

QR code login

-

QR code login flow

-

Error handling

-

How to handle API return errors correctly.

-

Handling different data centers

-

How to connect to the closest DC access point for faster interaction with the API, and things to watch out for when developing a client.

-

Handling updates

-

How to subscribe to updates and handle them properly.

-

Handling PUSH-notifications

-

How to subscribe and handle them properly.

-

Channels, supergroups and groups

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

-

Calling methods

-

Additional options for calling methods.

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

-

Pagination

-

How to fetch results from large lists of objects.

-

Client configuration

-

The MTProto API has multiple client configuration parameters that can be fetched with the appropriate methods.

-

Security

-

Secret chats, end-to-end encryption

-

End-to-end-encrypted messaging.

-

Security guidelines

-

Important checks required in your client application.

-

Perfect Forward Secrecy

-

Binding temporary authorization key to permanent ones.

-

End-to-End Encryption in Voice and Video Calls

-

End-to-end-encrypted calls.

-

Optimization

-

Client optimization

-

Ways to boost API interactions.

-

API methods

-

Available method list

-

A list of available high-level methods.

-

API TL-schema, as JSON

-

Text and JSON-presentation of types and methods used in API.

-

Available layer list

-

A list of available schema versions.

-

Other articles

-

Working with bots, using the MTProto API

-

How to work with bots using the MTProto API.

-

Commands

-

Bots offer a set of commands that can be used by users in private, or in a chat.

-

Buttons

-

Users can interact with your bot via buttons or even inline buttons, straight from inline messages in any chat.

-

Inline queries

-

Users can interact with your bot via inline queries, straight from the text input field in any chat.

-

Games

-

Bots can offer users HTML5 games to play solo or to compete against each other in groups and one-on-one chats; how to work with games in the MTProto API.

-

Search & filters

-

Telegram allows applying detailed message filters while looking for messages in chats. -This allows the server to filter messages based on a text query, and even on their type, and this feature is often used by graphical clients to implement features like the chat gallery, chat profile pictures and more.

-

Polls

-

Telegram allows sending polls and quizes, that can be voted on by thousands, if not milions of users in chats and channels.

-

Admin, banned and default rights for channels, supergroups and groups

-

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

-

Discussion groups

-

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

-

Channel comments and message threads

-

Telegram allows commenting on a channel post or on a generic group message, thanks to message threads.

-

Admin log

-

Both supergroups and channels offer a so-called admin log, a log of recent relevant supergroup and channel actions, like the modification of group/channel settings or information on behalf of an admin, user kicks and bans, and more.

-

Pinned messages

-

Telegram allows pinning multiple messages on top of a specific chat.

-

Mentions

-

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

-

Scheduled messages

-

Telegram allows scheduling messages.

-

Live geolocations

-

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

-

Min constructors

-

Sometimes, user and channel constructors met in group chat updates may not contain full info about the user: how to handle such constructors.

-

Account deletion

-

How to reset an account if the 2FA password was forgotten.

-

Imported messages

-

Telegram allows importing messages and media from foreign chat apps.

-

Telegram Passport

-

How to work with Telegram Passport directly using the MTProto API.

-

Telegram Payments

-

How to work with Telegram Payments directly using the MTProto API.

-

Styled text with message entities

-

How to create styled text with message entities

-

Working with animated emojis

-

Graphical telegram clients should transform emojis into their respective animated version.

-

Working with animated dice

-

Telegram supports sending animated dice emojis.

-

Message drafts

-

How to handle message drafts

-

Folders

-

Working with folders

-

Top peer rating

-

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

-

Handling file references

-

How to handle file references.

-

Seamless Telegram Login

-

Handle Seamless Telegram Login URL authorization requests.

-

Web events

-

When interacting with HTML5 games and the websites of payment gateways, Telegram apps should expose the following JS APIs.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api.html b/data/core.telegram.org/api.html deleted file mode 100644 index f6775268b5..0000000000 --- a/data/core.telegram.org/api.html +++ /dev/null @@ -1,253 +0,0 @@ - - - - - Telegram APIs - - - - - - - - - - - - - -
- -
-
-
-
-

Telegram APIs

- -

We offer two kinds of APIs for developers. The Bot API allows you to easily create programs that use Telegram messages for an interface. The Telegram API and TDLib allow you to build your own customized Telegram clients. You are welcome to use both APIs free of charge.

-

You can also add Telegram Widgets to your website.

-

Designers are welcome to create Animated Stickers or Custom Themes for Telegram.

-
-

Bot API

-
- -
-

This API allows you to connect bots to our system. Telegram Bots are special accounts that do not require an additional phone number to set up. These accounts serve as an interface for code running somewhere on your server.

-

To use this, you don't need to know anything about how our MTProto encryption protocol works — our intermediary server will handle all encryption and communication with the Telegram API for you. You communicate with this server via a simple HTTPS-interface that offers a simplified version of the Telegram API.

-
-

Learn more about the Bot API here »

-
-

Bot developers can also make use of our Payments API to accept payments from Telegram users around the world.

-
-

TDLib – build your own Telegram

-

Even if you're looking for maximum customization, you don't have to create your app from scratch. Try our Telegram Database Library (or simply TDLib), a tool for third-party developers that makes it easy to build fast, secure and feature-rich Telegram apps.

-

TDLib takes care of all network implementation details, encryption and local data storage, so that you can dedicate more time to design, responsive interfaces and beautiful animations.

-

TDLib supports all Telegram features and makes developing Telegram apps a breeze on any platform. It can be used on Android, iOS, Windows, macOS, Linux and virtually any other system. The library is open source and compatible with virtually any programming language.

-
-

Learn more about TDLib here »

-
-
-

Telegram API

-

This API allows you to build your own customized Telegram clients. It is 100% open for all developers who wish to create Telegram applications on our platform. Feel free to study the open source code of existing Telegram applications for examples of how things work here. Don't forget to register your application in our system.

- -

Getting started

-

Creating an application

-

How to get your application identifier and create a new Telegram app.

-

User authorization

-

How to register a user's phone to start using the API.

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

-

QR code login

-

QR code login flow

-

Error handling

-

How to handle API return errors correctly.

-

Handling different data centers

-

How to connect to the closest DC access point for faster interaction with the API, and things to watch out for when developing a client.

-

Handling updates

-

How to subscribe to updates and handle them properly.

-

Handling PUSH-notifications

-

How to subscribe and handle them properly.

-

Channels, supergroups and groups

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

-

Calling methods

-

Additional options for calling methods.

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

-

Pagination

-

How to fetch results from large lists of objects.

-

Client configuration

-

The MTProto API has multiple client configuration parameters that can be fetched with the appropriate methods.

-

Security

-

Secret chats, end-to-end encryption

-

End-to-end-encrypted messaging.

-

Security guidelines

-

Important checks required in your client application.

-

Perfect Forward Secrecy

-

Binding temporary authorization key to permanent ones.

-

End-to-End Encryption in Voice and Video Calls

-

End-to-end-encrypted calls.

-

Optimization

-

Client optimization

-

Ways to boost API interactions.

-

API methods

-

Available method list

-

A list of available high-level methods.

-

API TL-schema, as JSON

-

Text and JSON-presentation of types and methods used in API.

-

Available layer list

-

A list of available schema versions.

-

Other articles

-

Working with bots, using the MTProto API

-

How to work with bots using the MTProto API.

-

Commands

-

Bots offer a set of commands that can be used by users in private, or in a chat.

-

Buttons

-

Users can interact with your bot via buttons or even inline buttons, straight from inline messages in any chat.

-

Inline queries

-

Users can interact with your bot via inline queries, straight from the text input field in any chat.

-

Games

-

Bots can offer users HTML5 games to play solo or to compete against each other in groups and one-on-one chats; how to work with games in the MTProto API.

-

Search & filters

-

Telegram allows applying detailed message filters while looking for messages in chats. -This allows the server to filter messages based on a text query, and even on their type, and this feature is often used by graphical clients to implement features like the chat gallery, chat profile pictures and more.

-

Polls

-

Telegram allows sending polls and quizes, that can be voted on by thousands, if not milions of users in chats and channels.

-

Admin, banned and default rights for channels, supergroups and groups

-

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

-

Discussion groups

-

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

-

Channel comments and message threads

-

Telegram allows commenting on a channel post or on a generic group message, thanks to message threads.

-

Admin log

-

Both supergroups and channels offer a so-called admin log, a log of recent relevant supergroup and channel actions, like the modification of group/channel settings or information on behalf of an admin, user kicks and bans, and more.

-

Pinned messages

-

Telegram allows pinning multiple messages on top of a specific chat.

-

Mentions

-

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

-

Scheduled messages

-

Telegram allows scheduling messages.

-

Live geolocations

-

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

-

Min constructors

-

Sometimes, user and channel constructors met in group chat updates may not contain full info about the user: how to handle such constructors.

-

Account deletion

-

How to reset an account if the 2FA password was forgotten.

-

Imported messages

-

Telegram allows importing messages and media from foreign chat apps.

-

Telegram Passport

-

How to work with Telegram Passport directly using the MTProto API.

-

Telegram Payments

-

How to work with Telegram Payments directly using the MTProto API.

-

Styled text with message entities

-

How to create styled text with message entities

-

Working with animated emojis

-

Graphical telegram clients should transform emojis into their respective animated version.

-

Working with animated dice

-

Telegram supports sending animated dice emojis.

-

Message drafts

-

How to handle message drafts

-

Folders

-

Working with folders

-

Top peer rating

-

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

-

Handling file references

-

How to handle file references.

-

Seamless Telegram Login

-

Handle Seamless Telegram Login URL authorization requests.

-

Web events

-

When interacting with HTML5 games and the websites of payment gateways, Telegram apps should expose the following JS APIs.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/account-deletion.html b/data/core.telegram.org/api/account-deletion.html deleted file mode 100644 index 95a7c53e43..0000000000 --- a/data/core.telegram.org/api/account-deletion.html +++ /dev/null @@ -1,129 +0,0 @@ - - - - - Account deletion - - - - - - - - - - - - - -
- -
-
-
- -

Account deletion

- -

If the user has successfully provided the login code, but they forgot the 2FA password, the account should be reset: this can be done using account.deleteAccount.

-

If the account's 2FA password was modified more than 7 days ago and was active in the last 7 days, account deletion will be delayed for 7 days, and a service message will be sent to the user, containing a link in one of the following formats:

-
    -
  • https://telegram.me/confirmphone?phone=XXX&hash=YYYY
  • -
  • tg://confirmphone?phone=XXX&hash=YYYY
  • -
-

When clicked, account.sendConfirmPhoneCode must be called with the specified hash, using the account with the specified phone number. -This will send a phone number verification code to the phone number associated with the account. -The phone code settings are the same as for the login code, and auth.cancelCode with auth.resendCode can be used as well, to resend or cancel the phone code as for the login code.

-

Once the SMS code is received, the account.confirmPhone method will have to be called with the SMS code and the phone hash received from the account.sendConfirmPhoneCode method.

-

This will cancel deletion of the account and will log out the user that tried to reset it. -Otherwise, if the number isn't confirmed in 7 days, the account will be deleted and the user will be free to recreate it.

-

Related articles

-

User Authorization

-

How to register a user's phone to start using the API.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/animated-emojis.html b/data/core.telegram.org/api/animated-emojis.html deleted file mode 100644 index 9224f97f2f..0000000000 --- a/data/core.telegram.org/api/animated-emojis.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - Animated Emojis - - - - - - - - - - - - - -
- -
-
-
- -

Animated Emojis

- -

Graphical telegram clients should transform emojis into their respective animated version.

-
inputStickerSetAnimatedEmoji#28703c8 = InputStickerSet;
-
-messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
-
----functions---
-
-messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;
-

On startup, clients should fetch the animated emoji stickerset by calling the messages.getStickerSet method, providing inputStickerSetAnimatedEmoji to the stickerset field.
-The returned stickerset will contain a set of animated stickers, one for each of the supported emojis.

-

Clients should substitute messages containing only one instance of one of the allowed emojis with the respective animated sticker.

-

Animated emojis should loop only once when first sent or received, or when clicked.
-For supported emojis, clients on both sides of private chats with users are supposed to show a reaction animation when any of the two users clicks on the animated emoji: click here for more info ».

-

For special dice emojis like 🎲, 🎯, or 🏀, clients are supposed to behave differently both when sending and receiving such emojis: click here for more info ».

-

Emojis with sounds

-

Certained animated emojis should play sound when clicked, as specified by server-side configuration.

-

The returned JSON object will contain the following map, with a list of file IDs to download:

-
    "emojies_sounds": {
-        "\ud83c\udf83": {
-            "id": "4956223179606458539",
-            "access_hash": "-2107001400913062971",
-            "file_reference_base64": "AF-4ApC7ukC0UWEPZN0TeSJURe7T"
-        },
-        "\u26b0": {
-            "id": "4956223179606458540",
-            "access_hash": "-1498869544183595185",
-            "file_reference_base64": "AF-4ApCLKMGt96WCvLm58kbqZHd3"
-        },
-        "\ud83e\udddf\u200d\u2642": {
-            "id": "4960929110848176331",
-            "access_hash": "3986395821757915468",
-            "file_reference_base64": "AF-4ApAedNln3IMEHH-SUQuH8L9g"
-        },
-    }
-

The file reference field should be base64-decoded before downloading the file.

-

Emoji reactions

-
inputStickerSetAnimatedEmojiAnimations#cde3739 = InputStickerSet;
-
-messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
-
-stickerPack#12b299d4 emoticon:string documents:Vector<long> = StickerPack;
-
-sendMessageEmojiInteraction#25972bcb emoticon:string msg_id:int interaction:DataJSON = SendMessageAction;
-sendMessageEmojiInteractionSeen#b665902e emoticon:string = SendMessageAction;
-
-updateUserTyping#c01e857f user_id:long action:SendMessageAction = Update;
-
----functions---
-
-messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;
-
-messages.setTyping#58943ee2 flags:# peer:InputPeer top_msg_id:flags.0?int action:SendMessageAction = Bool;
-

On startup, clients should fetch the animated reaction emoji stickerset by calling the messages.getStickerSet method, providing inputStickerSetAnimatedEmojiAnimations to the stickerset field.
-The returned stickerset will contain a set of animated emoji reactions, one or more for each of the supported emojis.
-If a set of reactions for the ❤ emoji is returned, the same reactions should also be assigned to the 🧡, 💛, 💚, 💙, 💜, 🖤, 🤍 and 🤎 emojis.

-

Clients on both sides of private chats with users should overlay one of the appropriate reaction animations over the animated sticker when any of the two users clicks on a supported animated emoji.
-The reaction animation for each separate tap should be chosen randomly from all the available reactions for a given emoji, and multiple taps should be aggregated and sent to the other user as follows:

-

At each tap, clients should store all occurred taps in a local list.
-After 1 second has elapsed with no more taps, the local list should be cleared and stored taps should be sent using messages.setTyping, passing a sendMessageEmojiInteraction constructor with the following fields:

-
    -
  • emoticon - The emoji we're reacting to
  • -
  • msg_id - Message ID of the animated emoji that was clicked
  • -
  • interaction - A JSON object with interaction info, containing the following keys:
      -
    • v - An integer indicating the object version, currently 1
    • -
    • a - An array of JSON objects, each containing the following keys:
        -
      • t - float, number of seconds that passed since the previous tap in the array, the first tap uses a value of 0.0.
      • -
      • i - integer, 1-based index of the randomly chosen animation for the tap (equivalent to the index of a specific emoji-related animation in stickerPack + 1).
      • -
      -
    • -
    -
  • -
-

1 second after the receiving user has seen the last reaction animation for a specific emoji, an acknowledgement must be sent using messages.setTyping, passing a sendMessageEmojiInteractionSeen with that emoji.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/auth.html b/data/core.telegram.org/api/auth.html deleted file mode 100644 index 43fec5c314..0000000000 --- a/data/core.telegram.org/api/auth.html +++ /dev/null @@ -1,202 +0,0 @@ - - - - - User Authorization - - - - - - - - - - - - - -
- -
-
-
- -

User Authorization

- -
- -

Authorization is associated with a client’s encryption key identifier: auth_key_id. No additional parameters need to be passed into methods following authorization.

-

To log in as a bot, follow these instructions ».

-

Sending a verification code

-

Example implementations: telegram for android, tdlib.

-

To show a nicely formatted and validated phone number field, the help.countriesList constructor can be obtained using the help.getCountriesList method.
The help.countriesList config is then used as described here ».

-

Authorization requires that a text message containing an authorization code first be sent to the user’s phone.
This may be done using the auth.sendCode method.
The system will automatically choose how to send the authorization code; there are four possible ways the code can arrive:

-
    -
  • Telegram code
  • -
  • SMS code
  • -
  • Phone call: a synthesized voice will tell the user which verification code to input
  • -
  • Flash phone call: the code will be sent via a flash phone call, that will be closed immediately.
    In the last case, the phone code will then be the phone number itself, just make sure that the phone number matches the specified pattern (see auth.sentCodeTypeFlashCall).
  • -
-

The auth.sendCode method also has parameters for enabling/disabling use of flash calls, and allows passing an SMS token that will be included in the sent SMS.
For example, the latter is required in newer versions of android, to use the android SMS receiver APIs.

-

The returned auth.SentCode object will contain multiple parameters:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
flags#Flags, see TL conditional fields
typeauth.SentCodeTypePhone code type
phone_code_hashstringPhone code hash, to be stored and later re-used with auth.signIn
next_typeflags.1?auth.CodeTypePhone code type that will be sent next, if the phone code is not received within timeout seconds: to send it use auth.resendCode
timeoutflags.2?intTimeout for reception of the phone code
-

If the message takes too long (timeout seconds) to arrive at the phone, the auth.resendCode method may be invoked to resend a code of type next_type.
If the same happens again, you can use auth.resendCode with the next_type returned by the previous call to auth.resendCode.
To cancel the verification code use auth.cancelCode.

-

Sign in/sign up

-

When user enters verification code, the auth.signIn method must be used to validate it and possibly sign user in.

-

If the code was entered correctly, but the method returns auth.authorizationSignUpRequired, it means that account with this phone number doesn't exist yet: user needs to provide basic information, accept terms of service and then the new user registration method (auth.signUp) must be invoked.

-

2FA

-

When trying to sign in using auth.signIn, an error 400 SESSION_PASSWORD_NEEDED may be returned, if the user has two-factor authentication enabled.
In this case, instructions for SRP 2FA authentication must be followed.

-

To set up two-factor authorization on an already authorized account, follow the SRP 2FA authentication docs.

-

Test Accounts

-

Each phone number is limited to only a certain amount of logins per day (e.g. 5, but this is subject to change) after which the API will return a FLOOD error until the next day. This might not be enough for testing the implementation of User Authorization flows in client applications.

-

There are several reserved phone number prefixes for testing that your application handles redirects between DCs, sign up, sign in and 2FA flows correctly. These numbers are only available on Test DCs (their IP addresses for TCP transport are availble in API development tools panel after api_id was obtained, URI format for HTTPS/Websocket transport).

-

If you wish to emulate an application of a user associated with DC number X, it is sufficient to specify the phone number as 99966XYYYY, where YYYY are random numbers, when registering the user. A user like this would always get XXXXX as the login confirmation code (the DC number, repeated five times). Note that the value of X must be in the range of 1-3 because there are only 3 Test DCs. When the flood limit is reached for any particular test number, just choose another number (changing the YYYY random part).

-

Do not store any important or private information in the messages of such test accounts; anyone can make use of the simplified authorization mechanism – and we periodically wipe all information stored there.

-

Proceed with User Authorization flows in Production DCs only after you make sure everything works correctly on Test DCs first to avoid reaching flood limits.

-
-

To help you with working on production DCs, logins with the same phone number with which the api_id was registered have more generous flood limits.

-
-

We are authorized

-

As a result of authorization, the client key, auth_key_id, becomes associated with the user, and each subsequent API call with this key will be executed with that user’s identity. The authorization method itself returns the relevant user. It is best to immediately store the User ID locally in a binding with the key.

-

Only a small portion of the API methods are available to unauthorized users:

- -

Other methods will result in an error: 401 UNAUTHORIZED.

-
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/bots.html b/data/core.telegram.org/api/bots.html deleted file mode 100644 index b851aac4a2..0000000000 --- a/data/core.telegram.org/api/bots.html +++ /dev/null @@ -1,142 +0,0 @@ - - - - - Bots - - - - - - - - - - - - - -
- -
-
-
- -

Bots

- -
- -

Working with bots, using the MTProto API.

-

See here for more info about bots.

-

Please note that you can also use the simplified HTTP Bot API to use bots, see here for more info ».

-

Login

-
---functions---
-
-auth.importBotAuthorization#67a3ff2c flags:int api_id:int api_hash:string bot_auth_token:string = auth.Authorization;
-

In order to login as a bot, instead of using the standard login code flow, simply provide the bot token generated by @botfather.
-You must still provide your API ID, as per user logins.

-

After successful authorization, you will be able to use most MTProto API methods, just as any normal user.
-Methods that can be called by bots will have a Bots can use this method notice.

-

Commands

-

Bots offer a set of commands that can be used by users in private, or in a chat.

-

Buttons

-

Users can interact with your bot via buttons or even inline buttons, straight from inline messages in any chat.

-

Inline queries

-

Users can interact with your bot via inline queries, straight from the text input field in any chat.

-

Games

-

Bots can offer users HTML5 games to play solo or to compete against each other in groups and one-on-one chats; how to work with games in the MTProto API.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/bots/buttons.html b/data/core.telegram.org/api/bots/buttons.html deleted file mode 100644 index 0fa43cc1aa..0000000000 --- a/data/core.telegram.org/api/bots/buttons.html +++ /dev/null @@ -1,242 +0,0 @@ - - - - - Buttons - - - - - - - - - - - - - -
- -
-
-
- -

Buttons

- -
- -

Users can interact with your bot via buttons or even inline buttons, straight from inline messages in any chat.
-This article describes the full button flow, using the MTProto API.

-

For a simplified description using the HTTP bot API, see here ».

-

Buttons

-
keyboardButton#a2fa4880 text:string = KeyboardButton;
-keyboardButtonUrl#258aff05 text:string url:string = KeyboardButton;
-keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;
-keyboardButtonRequestPhone#b16a6c29 text:string = KeyboardButton;
-keyboardButtonRequestGeoLocation#fc796b3f text:string = KeyboardButton;
-keyboardButtonSwitchInline#568a748 flags:# same_peer:flags.0?true text:string query:string = KeyboardButton;
-keyboardButtonGame#50f41ccf text:string = KeyboardButton;
-keyboardButtonBuy#afd93fbb text:string = KeyboardButton;
-keyboardButtonUrlAuth#10b78d29 flags:# text:string fwd_text:flags.0?string url:string button_id:int = KeyboardButton;
-inputKeyboardButtonUrlAuth#d02e7fd4 flags:# request_write_access:flags.0?true text:string fwd_text:flags.1?string url:string bot:InputUser = KeyboardButton;
-keyboardButtonRequestPoll#bbc7515d flags:# quiz:flags.0?Bool text:string = KeyboardButton;
-
-keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;
-
-replyKeyboardHide#a03e5b85 flags:# selective:flags.2?true = ReplyMarkup;
-replyKeyboardForceReply#86b40b08 flags:# single_use:flags.1?true selective:flags.2?true placeholder:flags.3?string = ReplyMarkup;
-replyKeyboardMarkup#85dd99d1 flags:# resize:flags.0?true single_use:flags.1?true selective:flags.2?true rows:Vector<KeyboardButtonRow> placeholder:flags.3?string = ReplyMarkup;
-replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;
-
-message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
-
----functions---
-
-messages.sendMessage#520c3870 flags:# no_webpage:flags.1?true silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-

Bots can attach a ReplyMarkup constructor to outgoing messages, to attach an inline keyboard or a custom reply keyboard:

- -

Pressing buttons

-
keyboardButton#a2fa4880 text:string = KeyboardButton;
-keyboardButtonUrl#258aff05 text:string url:string = KeyboardButton;
-keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;
-keyboardButtonRequestPhone#b16a6c29 text:string = KeyboardButton;
-keyboardButtonRequestGeoLocation#fc796b3f text:string = KeyboardButton;
-keyboardButtonRequestPoll#bbc7515d flags:# quiz:flags.0?Bool text:string = KeyboardButton;
-keyboardButtonSwitchInline#568a748 flags:# same_peer:flags.0?true text:string query:string = KeyboardButton;
-keyboardButtonGame#50f41ccf text:string = KeyboardButton;
-keyboardButtonBuy#afd93fbb text:string = KeyboardButton;
-keyboardButtonUrlAuth#10b78d29 flags:# text:string fwd_text:flags.0?string url:string button_id:int = KeyboardButton;
-
-// Used by bots to send a keyboardButtonUrlAuth
-inputKeyboardButtonUrlAuth#d02e7fd4 flags:# request_write_access:flags.0?true text:string fwd_text:flags.1?string url:string bot:InputUser = KeyboardButton;
-
-keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;
-

Both reply and inline keyboards are composed of a vector of rows, each row containing a vector of buttons, for each column.
-Each row can have a different number of columns, and user clients should properly handle clicking buttons of every type.

-

Buttons available only in reply keyboards:

- -

Buttons available only in inline keyboards:

- -

Callback queries

-

keyboardButtonCallback buttons can be used to send the specified data payload back to the bot, when they are clicked.
-Additionally, a bot can verify a user's identity by requiring they verify their 2FA password with SRP.

-

Sending a callback query

-
keyboardButtonGame#50f41ccf text:string = KeyboardButton;
-keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;
-
-messages.botCallbackAnswer#36585ea4 flags:# alert:flags.1?true has_url:flags.3?true native_ui:flags.4?true message:flags.0?string url:flags.2?string cache_time:int = messages.BotCallbackAnswer;
-
----functions---
-
-messages.getBotCallbackAnswer#9342ca07 flags:# game:flags.1?true peer:InputPeer msg_id:int data:flags.0?bytes password:flags.2?InputCheckPasswordSRP = messages.BotCallbackAnswer;
-

When the user clicks on a keyboardButtonCallback in a message sent by a bot, or generated by an inline query, messages.getBotCallbackAnswer should be called, passing the peer and ID of the message.
-The same should happen when clicking on keyboardButtonGame buttons, with the difference that the game flag must be set instead of the data parameter.

-

Make sure to properly handle bot timeouts in the form of BOT_RESPONSE_TIMEOUT RPC errors, as the bot may be offline and unable to reply.

-

The returned messages.botCallbackAnswer constructor contains:

-
    -
  • message if specified, a message that should be shown in a non-blocking toast notification
  • -
  • alert indicates whether the message should be shown as a dismissable prompt, instead of a simple toast notification
  • -
  • has_url Whether an URL is present
  • -
  • url if specified, the client should open the URL, without showing a confirmation prompt.
    This is safe and allowed, because here, bots can only return:
      -
    • URLs to themselves with added query parameters (t.me/bot?start=aaa)
    • -
    • URLs to a valid game, if the bot has manually configured games, and the clicked button was a keyboardButtonGame.
    • -
    -
  • -
  • native_ui whether to open game URLs in a WebView or in native UI.
  • -
  • cache_time specifies for how long should this answer be cached, client-side
  • -
-
SRP verification
-

If the requires_password flag is set, the SRP 2FA payload must also be generated and attached to the query, to verify the identity of the user.

-

Note that the bot will NOT be able to access your password or the SRP payload.

-

The SRP payload will be processed exclusively on the Telegram's servers, simply returning an RPC error without passing the query to the bot if the verification fails.
-This is just a way of verifying the identity of the user, mainly used by the official @botfather bot to allow securely transferring the ownership of a bot to another user.

-

Answering a callback query

-
updateBotCallbackQuery#b9cfc48d flags:# query_id:long user_id:long peer:Peer msg_id:int chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
-
-updateInlineBotCallbackQuery#691e9052 flags:# query_id:long user_id:long msg_id:InputBotInlineMessageID chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
-
----functions---
-
-messages.setBotCallbackAnswer#d58f130a flags:# alert:flags.1?true query_id:long message:flags.0?string url:flags.2?string cache_time:int = Bool;
-

After the user invokes messages.getBotCallbackAnswer, an updateBotCallbackQuery or updateInlineBotCallbackQuery is generated and sent to the bot, depending on whether the query originated from a normal message sent by the bot, or from a message sent from an inline query.

-

Either way, bots must reply to the query as quickly as possible using messages.setBotCallbackAnswer:

- -

If a game_short_name is present in the update, the bot should return the URL of the game with the specified name.
-The messages.setBotCallbackAnswer method must be called anyway, even if no message or url is returned, to avoid timeouts on the client.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/bots/commands.html b/data/core.telegram.org/api/bots/commands.html deleted file mode 100644 index 4a2dc42d6c..0000000000 --- a/data/core.telegram.org/api/bots/commands.html +++ /dev/null @@ -1,140 +0,0 @@ - - - - - Commands - - - - - - - - - - - - - -
- -
-
-
- -

Commands

- -
- -

Bots offer a set of commands that can be used by users in private, or in a chat.

-

For a simplified description using the HTTP bot API, see here ».

-

Getting commands

-
botCommand#c27ac8c7 command:string description:string = BotCommand;
-
-botInfo#1b74b335 user_id:long description:string commands:Vector<BotCommand> = BotInfo;
-
-channelFull#e9b27a17 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector<string> groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string = ChatFull;
-userFull#d697ff05 flags:# blocked:flags.0?true phone_calls_available:flags.4?true phone_calls_private:flags.5?true can_pin_message:flags.7?true has_scheduled:flags.12?true video_calls_available:flags.13?true user:User about:flags.1?string settings:PeerSettings profile_photo:flags.2?Photo notify_settings:PeerNotifySettings bot_info:flags.3?BotInfo pinned_msg_id:flags.6?int common_chats_count:int folder_id:flags.11?int ttl_period:flags.14?int theme_emoticon:flags.15?string = UserFull;
-
-user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
-

The botInfo constructors contained in the userFull, chatFull, channelFull contain a list of commands, and for groups, the ID and a description of each bot.

-

In graphical clients, when users begin a message with a /, a list of commands supported by all bots present in the current chat should be shown; the same should be done for one-to-one chats with the bot itself.

-

If the command list of a bot changes, the bot_info_version contained in the user constructor received in updates will change; this indicates that the client should refetch full bot information using users.getFullUser.

-

Setting commands

-
botCommand#c27ac8c7 command:string description:string = BotCommand;
-
----functions---
-
-bots.setBotCommands#517165a scope:BotCommandScope lang_code:string commands:Vector<BotCommand> = Bool;
-

The command list can be changed by the owner of the bot through @botfather, but bots can also change their own command list by invoking bots.setBotCommands.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/bots/games.html b/data/core.telegram.org/api/bots/games.html deleted file mode 100644 index ba75dd90e6..0000000000 --- a/data/core.telegram.org/api/bots/games.html +++ /dev/null @@ -1,171 +0,0 @@ - - - - - Games - - - - - - - - - - - - - -
- -
-
-
- -

Games

- -
- -

Bots can offer users HTML5 games to play solo or to compete against each other in groups and one-on-one chats.

-

Sending a game

-
inputUserSelf#f7c1b13f = InputUser;
-
-inputGameID#32c3e77 id:long access_hash:long = InputGame;
-inputGameShortName#c331e80a bot_id:InputUser short_name:string = InputGame;
-
-inputMediaGame#d33f43f3 id:InputGame = InputMedia;
-
-game#bdf9653b flags:# id:long access_hash:long short_name:string title:string description:string photo:Photo document:flags.0?Document = Game;
-messageMediaGame#fdb19008 game:Game = MessageMedia;
-
----functions---
-
-messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-

Bots can directly send a game using messages.sendMedia, providing:

-
    -
  • The bot's shortname obtained from @BotFather to inputGameShortName.short_name
  • -
  • The current bot's info to inputGameShortName.bot_id
  • -
-

The sent message will contain a messageMediaGame with a game, that can then be used by users to forward the game using sendMedia with inputGameID.

-

Starting a game

-

Games are started clicking on the button, which triggers an callback query that returns the game URL, for more info see here &raquo.
-The game should then be opened in a WebView or in native UI (specified by the native_ui flag), exposing the appropriate HTML5 APIs in order to receive various JS game events directly from the code of the game, as described here ».

-

Setting highscores

-
---functions---
-
-messages.setGameScore#8ef8ecc0 flags:# edit_message:flags.0?true force:flags.1?true peer:InputPeer id:int user_id:InputUser score:int = Updates;
-messages.setInlineGameScore#15ad9f64 flags:# edit_message:flags.0?true force:flags.1?true id:InputBotInlineMessageID user_id:InputUser score:int = Bool;
-

Games are supposed to report back to the MTProto API every time the user looses a game with a new highscore.
-Since games run in the browser, they cannot directly report data to the API using the bot token, which must be kept secret.
-Instead, they should send highscores to an intermediate server, that will then report scores using messages.setGameScore or messages.setInlineGameScore, depending on the source of the game.

-
    -
  • The edit_message flag should be set if the game message should be automatically edited to include the current scoreboard
  • -
  • The force flag should be set if the high score is allowed to decrease. This can be useful when fixing mistakes or banning cheaters.
  • -
-

Getting highscores

-
messageActionGameScore#92a72876 game_id:long score:int = MessageAction;
-
-messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;
-
-highScore#73a379eb pos:int user_id:long score:int = HighScore;
-
-messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;
-
----functions---
-
-messages.getGameHighScores#e822649d peer:InputPeer id:int user_id:InputUser = messages.HighScores;
-messages.getInlineGameHighScores#f635e1b id:InputBotInlineMessageID user_id:InputUser = messages.HighScores;
-

Every time a highscore is reached, and the edit_message flag is set when reporting the score, a messageService with a messageActionGameScore is generated, indicating that the highscore of a certain game has changed, thanks to a certain user_id.
-Our own current position of the scoreboard is also reported as pos.

-

When receiving such an update, graphical clients should refetch the scoreboard using messages.getGameHighScores or messages.getInlineGameHighScores.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/bots/inline.html b/data/core.telegram.org/api/bots/inline.html deleted file mode 100644 index 558cf6c15d..0000000000 --- a/data/core.telegram.org/api/bots/inline.html +++ /dev/null @@ -1,215 +0,0 @@ - - - - - Inline - - - - - - - - - - - - - -
- -
-
-
-
-

Inline

- -
- -

Users can interact with your bot via inline queries, straight from the text input field in any chat.
-This article describes the full inline bot flow, using the MTProto API.

-

For a simplified description using the HTTP bot API, see here ».

-

Making an inline query

-
messages.botResults#947ca848 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;
-
----functions---
-
-messages.getInlineBotResults#514e999d flags:# bot:InputUser peer:InputPeer geo_point:flags.0?InputGeoPoint query:string offset:string = messages.BotResults;
-

When, in a graphical client, the user starts a message with an @, clients should:

-
    -
  • Use the cached top peer rating for inline bots to show a list of frequently used inline bots.
  • -
  • If the user chooses a bot from the recent bot list or:
  • -
  • Finishes typing a full username followed by a whitespace, and if the username resolves to a valid bot
  • -
  • messages.getInlineBotResults is called, with the following parameters:
      -
    • bot - The bot peer
    • -
    • peer - The chat where the user made the query
    • -
    • geo_point - The user's current geolocation, if the bot requires location-based inline results (the bot_inline_geo flag of the bot's user constructor will be set)
    • -
    • query - What the user typed after the bot's username
    • -
    • offset - If the user scrolls past the first len(results) results, and next_offset field is set, the inline query should be repeated with this offset.
    • -
    -
  • -
-

Answering to an inline query

-
inputBotInlineMessageMediaAuto#3380c786 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageText#3dcd7a87 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageMediaGeo#96929a85 flags:# geo_point:InputGeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageMediaVenue#417bbf11 flags:# geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageMediaContact#a6edbffd flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageGame#4b425864 flags:# reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-
-inputBotInlineResult#88bf9319 flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?InputWebDocument content:flags.5?InputWebDocument send_message:InputBotInlineMessage = InputBotInlineResult;
-inputBotInlineResultPhoto#a8d864a7 id:string type:string photo:InputPhoto send_message:InputBotInlineMessage = InputBotInlineResult;
-inputBotInlineResultDocument#fff8fdc4 flags:# id:string type:string title:flags.1?string description:flags.2?string document:InputDocument send_message:InputBotInlineMessage = InputBotInlineResult;
-inputBotInlineResultGame#4fa417f2 id:string short_name:string send_message:InputBotInlineMessage = InputBotInlineResult;
-
-updateBotInlineQuery#496f379c flags:# query_id:long user_id:long query:string geo:flags.0?GeoPoint peer_type:flags.1?InlineQueryPeerType offset:string = Update;
-
----functions---
-
-messages.setInlineBotResults#eb5ea206 flags:# gallery:flags.0?true private:flags.1?true query_id:long results:Vector<InputBotInlineResult> cache_time:int next_offset:flags.2?string switch_pm:flags.3?InlineBotSwitchPM = Bool;
-

Bots can answer to incoming updateBotInlineQuery updates using messages.setInlineBotResults.
-Just like its bot API counterpart, the method can be used to send a set of inline results to the user; see the constructor page for more info on the MTProto method parameters ».

-

In general, the method accepts a vector of InputBotInlineResult constructors, that when chosen, generates a message with optionally attached media, and even inline buttons.

-

Sending the inline query result

-
botInlineMessageMediaAuto#764cf810 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-botInlineMessageText#8c7f65e2 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-botInlineMessageMediaGeo#51846fd flags:# geo:GeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-botInlineMessageMediaVenue#8a86659c flags:# geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-botInlineMessageMediaContact#18d1cdc2 flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-
-botInlineResult#11965f3a flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?WebDocument content:flags.5?WebDocument send_message:BotInlineMessage = BotInlineResult;
-botInlineMediaResult#17db940b flags:# id:string type:string photo:flags.0?Photo document:flags.1?Document title:flags.2?string description:flags.3?string send_message:BotInlineMessage = BotInlineResult;
-
-messages.botResults#947ca848 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;
-
----functions---
-
-messages.sendInlineBotResult#220815b0 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true hide_via:flags.11?true peer:InputPeer reply_to_msg_id:flags.0?int random_id:long query_id:long id:string schedule_date:flags.10?int = Updates;
-

The user client should display the results obtained during querying in a list, making sure to handle eventual bot timeouts in the form of a BOT_RESPONSE_TIMEOUT RPC error, by simply not displaying anything.

-

If the user then chooses a specific BotInlineResult, the messages.sendInlineBotResult method should be invoked, passing:

-
    -
  • The query_id from messages.botResults
  • -
  • The id of the chosen result
  • -
  • The peer where to send the chosen result
  • -
-

The resulting message will have the via_bot_id field set, to indicate that the result was generated by the bot that generated the inline result.
-Graphical clients should display the bot @username in the header of the message, allowing the user to click on it, automatically starting an inline query by inserting @username in the text bar.

-

Inline feedback

-
inputBotInlineMessageID#890c3d89 dc_id:int id:long access_hash:long = InputBotInlineMessageID;
-
-updateBotInlineSend#12f12a07 flags:# user_id:long query:string geo:flags.0?GeoPoint id:string msg_id:flags.1?InputBotInlineMessageID = Update;
-

If feedback collection is enabled, the bot may receive an updateBotInlineSend when the user chooses and sends an inline result.

-

Even if the probability setting is set to 100%, not all inline results may be reported due to caching (see the cache_time parameter in Answering a callback query).
-Feedback collection can also create load issues for popular bots, so adjust the probability setting to a lower value in such cases.

-

Either way, feedback collection should only be used for statistical purposes rather than functional.

-

The updateBotInlineSend will contain:

-
    -
  • id - The ID of the chosen result
  • -
  • msg_id - The ID of the sent inline message
  • -
  • user_id - The ID of the user that chose the result
  • -
  • query - The query string that was used to obtain the result
  • -
  • geo - For bots requiring location-based inline results, the user's location
  • -
-

Editing sent inline messages

-
updateInlineBotCallbackQuery#691e9052 flags:# query_id:long user_id:long msg_id:InputBotInlineMessageID chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
-
-inputBotInlineMessageID#890c3d89 dc_id:int id:long access_hash:long = InputBotInlineMessageID;
-
----functions---
-
-messages.editInlineBotMessage#83557dba flags:# no_webpage:flags.1?true id:InputBotInlineMessageID message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> = Bool;
-

Sent inline messages can be edited by the bot, for example in response to a button press callback query.

-

Simply pass the inputBotInlineMessageID specified in the updateInlineBotCallbackQuery to messages.editInlineBotMessage along with the new message, making sure to send the query to the datacenter specified in inputBotInlineMessageID.dc_id.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/channel.html b/data/core.telegram.org/api/channel.html deleted file mode 100644 index dc13d8d745..0000000000 --- a/data/core.telegram.org/api/channel.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - Channels - - - - - - - - - - - - - -
- -
-
-
- -

Channels

- -
- -

Channels, chats, supergroups & gigagroups

-

Channels are a tool for broadcasting your messages to large audiences. They can have an unlimited number of subscribers, they can be public with a permanent URL and each post in a channel has its own view counter.
-Technically, they are represented by channel constructors.

-

Supergroups are a powerful tool for building communities and can support up to 200,000 members each.
-Technically, supergroups are actually channels: they are represented by channel constructors, with the megagroup flag set to true.

-

Gigagroups are something inbetween a channel and a supergroup.
-An admin, when prompted by the API using suggestions », can convert a megagroup into a gigagroup using channels.convertToGigagroup (one way only).
-After that, only admins will be able to write in the group (like when send_messages rights are disabled for all group participants by default), but the participant limit is removed and the group can become much bigger than a supergroup (e.g. >200,000 currently).
-Also, one can't invite people into gigagroups and participants of voice chats in gigagroups are muted by default.

-

Channels and supergroup can be created using the channels.createChannel method, by setting the appropriate broadcast or megagroup flags.
-Supergroups can also be assigned a geo_point to become geochats.

-

In previous versions of telegram, only normal groups (represented by chat constructors) could be created using messages.createChat: these groups have fewer features, and can only have 200 members at max.

-

Migration

-

To upgrade a legacy group to a supergroup, messages.migrateChat can be used. -The chats field of the result will have two objects:

-
    -
  • A chat constructor with a migrated_to field, indicating the address of the new supergroup
  • -
  • The new channel megagroup constructor
  • -
-

When getting full info about the migrated channel, the channelFull object will have migrated_from_chat_id and migrated_from_max_id fields indicating the original ID of the chat, and the message ID in the original chat at which the group was migrated.

-

All users of the chat will receive an updateNewMessage from the old chat with a messageService containing a messageActionChatMigrateTo constructor.

-

All new messages have to be sent to the new supergroup.

-

When working with migrated groups clients need to handle loading of the message history (as well as search results et cetera) from both the legacy group and the new supergroup. This is done by merging the two messages lists (requested with different Peer values) client side.

-

Rights

-

Channels, legacy groups and supergroups allow setting granular permissions both for admins and specific users; channels, supergroups and legacy groups also allow setting global granular permissions for users.

-

For more info on how to set and modify rights, see here ».

-

Pinned messages

-

Telegram allows pinning multiple messages on top in a chat, group, supergroup or channel.

-

See here » for more info on pinning and unpinning messages.

-

Discussion

-

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

-

For more info on how to set a discussion group in channel, see here »

-

Recent actions

-

Both supergroups and channels offer a so-called admin log, a log of recent relevant supergroup and channel actions, like the modification of group/channel settings or information on behalf of an admin, user kicks and bans, and more.

-

See here » for more info.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/config.html b/data/core.telegram.org/api/config.html deleted file mode 100644 index 5e804b24ce..0000000000 --- a/data/core.telegram.org/api/config.html +++ /dev/null @@ -1,422 +0,0 @@ - - - - - Client configuration - - - - - - - - - - - - - -
- -
-
-
- -

Client configuration

- -
- -

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

-

MTProto configuration

-
config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;
-nearestDc#8e1a1775 country:string this_dc:int nearest_dc:int = NearestDc;
-
----functions---
-
-help.getConfig#c4f9186b = Config;
-help.getNearestDc#1fb33026 = NearestDc;
-

The huge config constructor contains lots of useful information, from chat and message size limitations, to privacy settings, online status refresh interval and timeout, VoIP configuration, default inline bot usernames for GIF, image and venue lookup, and lots of other global and user-specific information, check out the constructor page for more information.

-

Client configuration

-
jsonObjectValue#c0de1bd9 key:string value:JSONValue = JSONObjectValue;
-
-jsonNull#3f6d7b68 = JSONValue;
-jsonBool#c7345e6a value:Bool = JSONValue;
-jsonNumber#2be0dfa4 value:double = JSONValue;
-jsonString#b71e767a value:string = JSONValue;
-jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;
-jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;
-
----functions---
-
-help.getAppConfig#98914110 = JSONValue;
-

The help.getAppConfig method returns a JSON object containing rapidly evolving, client-specific configuration parameters.
-While help.getConfig returns MTProto-specific configuration with information about server-side limitations and other MTProto-related information, help.getAppConfig returns configuration parameters useful for graphical Telegram clients.

-

Typical fields included in the resulting JSON object are:

-
    -
  • emojies_animated_zoom - Animated emojis and animated dice should be scaled by this factor before being shown to the user (float)
  • -
  • keep_alive_service - Whether app clients should start a keepalive service to keep the app running and fetch updates even when the app is closed (boolean)
  • -
  • background_connection - Whether app clients should start a background TCP connection for MTProto update fetching (boolean)
  • -
  • emojies_send_dice - A list of supported animated dice stickers (array of strings).
  • -
  • emojies_send_dice_success - For animated dice emojis other than the basic 🎲, indicates the winning dice value and the final frame of the animated sticker, at which to show the fireworks 🎆 (object with emoji keys and object values, containing value and frame_start float values)
  • -
  • emojies_sounds - A map of soundbites to be played when the user clicks on the specified animated emoji; the file reference field should be base64-decoded before downloading the file (map of file IDs, with emoji string keys)
  • -
  • gif_search_branding - Specifies the name of the service providing GIF search through gif_search_username (string)
  • -
  • gif_search_emojies - Specifies a list of emojies that should be suggested as search term in a bar above the GIF search box (array of string emojis)
  • -
  • stickers_emoji_suggest_only_api - Specifies that the app should not display local sticker suggestions for emojis at all and just use the result of messages.getStickers (bool)
  • -
  • stickers_emoji_cache_time - Specifies the validity period of the local cache of messages.getStickers, also relevant when generating the pagination hash when invoking the method. (int)
  • -
  • qr_login_camera - Whether the Settings->Devices menu should show an option to scan a QR login code (boolean)
  • -
  • qr_login_code - Whether the login screen should show a QR code login option, possibly as default login method (string, "disabled", "primary" or "secondary")
  • -
  • dialog_filters_enabled - Whether clients should show an option for managing dialog filters AKA folders (boolean)
  • -
  • dialog_filters_tooltip - Whether clients should actively show a tooltip, inviting the user to configure dialog filters AKA folders; typically this happens when the chat list is long enough to start getting cluttered. (boolean)
  • -
  • autoarchive_setting_available - Whether clients can invoke account.setGlobalPrivacySettings with globalPrivacySettings.archive_and_mute_new_noncontact_peers = boolTrue, to automatically archive and mute new incoming chats from non-contacts. (boolean)
  • -
  • pending_suggestions - Contains a list of suggestions that should be actively shown as a tooltip to the user. (Array of strings, possible values shown in the suggestions section ».
  • -
  • url_auth_domains - A list of domains that support automatic login with manual user confirmation, click here for more info on URL authorization ». (array of strings)
  • -
  • autologin_domains - A list of Telegram domains that support automatic login with no user confirmation, click here for more info on URL authorization ». (array of strings)
  • -
  • autologin_token - Autologin token, click here for more info on URL authorization ». (string)
  • -
  • round_video_encoding - Contains a set of recommended codec parameters for round videos.
  • -
  • chat_read_mark_size_threshold - Per-user read receipts, fetchable using messages.getMessageReadParticipants will be available in groups with less than chat_read_mark_size_threshold participants. (int)
  • -
  • chat_read_mark_expire_period - To protect user privacy, read receipts are only stored for chat_read_mark_expire_period seconds after the message was sent. (int)
  • -
-

Example value:

-
{
-    "test": 1,
-    "emojies_animated_zoom": 0.625,
-    "emojies_send_dice": [
-        "\ud83c\udfb2",
-        "\ud83c\udfaf",
-        "\ud83c\udfc0",
-        "\u26bd",
-        "\u26bd\ufe0f",
-        "\ud83c\udfb0",
-        "\ud83c\udfb3"
-    ],
-    "emojies_send_dice_success": {
-        "\ud83c\udfaf": {
-            "value": 6,
-            "frame_start": 62
-        },
-        "\ud83c\udfc0": {
-            "value": 5,
-            "frame_start": 110
-        },
-        "\u26bd": {
-            "value": 5,
-            "frame_start": 110
-        },
-        "\u26bd\ufe0f": {
-            "value": 5,
-            "frame_start": 110
-        },
-        "\ud83c\udfb0": {
-            "value": 64,
-            "frame_start": 110
-        },
-        "\ud83c\udfb3": {
-            "value": 6,
-            "frame_start": 110
-        }
-    },
-    "emojies_sounds": {
-        "\ud83c\udf83": {
-            "id": "4956223179606458539",
-            "access_hash": "-2107001400913062971",
-            "file_reference_base64": "AGFhvoKbftK5O9K9RpgN1ZtgSzWy"
-        },
-        "\u26b0": {
-            "id": "4956223179606458540",
-            "access_hash": "-1498869544183595185",
-            "file_reference_base64": "AGFhvoJIm8Uz0qSMIdm3AsKlK7wJ"
-        },
-        "\ud83e\udddf\u200d\u2642": {
-            "id": "4960929110848176331",
-            "access_hash": "3986395821757915468",
-            "file_reference_base64": "AGFhvoLtXSSIclmvfg6ePz3KsHQF"
-        },
-        "\ud83e\udddf": {
-            "id": "4960929110848176332",
-            "access_hash": "-8929417974289765626",
-            "file_reference_base64": "AGFhvoImaz5Umt4GvMUD5nocIu0W"
-        },
-        "\ud83e\udddf\u200d\u2640": {
-            "id": "4960929110848176333",
-            "access_hash": "9161696144162881753",
-            "file_reference_base64": "AGFhvoIm1QZsb48xlpRfh4Mq7EMG"
-        },
-        "\ud83c\udf51": {
-            "id": "4963180910661861548",
-            "access_hash": "-7431729439735063448",
-            "file_reference_base64": "AGFhvoKLrwl_WKr5LR0Jjs7o3RyT"
-        },
-        "\ud83c\udf8a": {
-            "id": "5094064004578410732",
-            "access_hash": "8518192996098758509",
-            "file_reference_base64": "AGFhvoKMNffRV2J3vKED0O6d8e42"
-        },
-        "\ud83c\udf84": {
-            "id": "5094064004578410733",
-            "access_hash": "-4142643820629256996",
-            "file_reference_base64": "AGFhvoJ1ulPBbXEURlTZWwJFx6xZ"
-        },
-        "\ud83e\uddbe": {
-            "id": "5094064004578410734",
-            "access_hash": "-8934384022571962340",
-            "file_reference_base64": "AGFhvoL4zdMRmYv9z3L8KPaX4JQL"
-        }
-    },
-    "gif_search_branding": "tenor",
-    "gif_search_emojies": [
-        "\ud83d\udc4d",
-        "\ud83d\ude18",
-        "\ud83d\ude0d",
-        "\ud83d\ude21",
-        "\ud83e\udd73",
-        "\ud83d\ude02",
-        "\ud83d\ude2e",
-        "\ud83d\ude44",
-        "\ud83d\ude0e",
-        "\ud83d\udc4e"
-    ],
-    "stickers_emoji_suggest_only_api": false,
-    "stickers_emoji_cache_time": 86400,
-    "qr_login_camera": false,
-    "qr_login_code": "disabled",
-    "dialog_filters_enabled": true,
-    "dialog_filters_tooltip": false,
-    "autoarchive_setting_available": false,
-    "pending_suggestions": [
-        "AUTOARCHIVE_POPULAR",
-        "VALIDATE_PASSWORD",
-        "VALIDATE_PHONE_NUMBER",
-        "NEWCOMER_TICKS"
-    ],
-    "autologin_token": "string",
-    "autologin_domains": [
-        "instantview.telegram.org",
-        "translations.telegram.org",
-        "contest.dev",
-        "contest.com",
-        "bugs.telegram.org",
-        "suggestions.telegram.org",
-        "themes.telegram.org"
-    ],
-    "url_auth_domains": [
-        "somedomain.telegram.org"
-    ],
-    "round_video_encoding": {
-        "diameter": 384,
-        "video_bitrate": 1000,
-        "audio_bitrate": 64,
-        "max_size": 12582912
-    },
-    "chat_read_mark_size_threshold": 50,
-    "chat_read_mark_expire_period": 604800
-}
-

Suggestions

-

The API can return a set of useful suggestions for users of graphical clients.

-

Basic suggestions

-
jsonObjectValue#c0de1bd9 key:string value:JSONValue = JSONObjectValue;
-
-jsonNull#3f6d7b68 = JSONValue;
-jsonBool#c7345e6a value:Bool = JSONValue;
-jsonNumber#2be0dfa4 value:double = JSONValue;
-jsonString#b71e767a value:string = JSONValue;
-jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;
-jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;
-
----functions---
-
-help.getAppConfig#98914110 = JSONValue;
-

The help.getAppConfig method returns a JSON object containing rapidly evolving, client-specific configuration parameters.
-A full list of these parameters can be seen in the Client Configuration section », but we're mostly interested in the pending_suggestions and autoarchive_setting_available fields of the returned JSON object:

- -

Channel suggestions

-
messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.ChatFull;
-
-channelFull#e9b27a17 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector<string> groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string = ChatFull;
-
----functions---
-
-channels.getFullChannel#8736a09 channel:InputChannel = messages.ChatFull;
-

Some channel/supergroup-related suggestions can also be contained in the pending_suggestions field of the channelFull constructor, returned by channels.getFullChannel.
-Here's a list of possible suggestions:

- -

Dismissing suggestions

-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
-
----functions---
-
-help.dismissSuggestion#f50dbaa1 peer:InputPeer suggestion:string = Bool;
-

help.dismissSuggestion can be used to dismiss a suggestion.
-Pass inputPeerEmpty to peer for basic suggestions and the channel/supergroup's peer for channel suggestions.

-

App-specific configuration

-
help.appUpdate#ccbbce30 flags:# can_not_skip:flags.0?true id:int version:string text:string entities:Vector<MessageEntity> document:flags.1?Document url:flags.2?string sticker:flags.3?Document = help.AppUpdate;
-help.noAppUpdate#c45a6536 = help.AppUpdate;
-
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateServiceNotification#ebe46819 flags:# popup:flags.0?true inbox_date:flags.1?int type:string message:string media:MessageMedia entities:Vector<MessageEntity> = Update;
-
-help.inviteText#18cb9f78 message:string = help.InviteText;
-
----functions---
-
-help.getAppUpdate#522d5a7d source:string = help.AppUpdate;
-help.getAppChangelog#9010ef6f prev_app_version:string = Updates;
-
-help.getInviteText#4d392343 = help.InviteText;
-
    -
  • help.getAppUpdate - Get info about an application update, can contain the updated application binary in the attached document
  • -
  • help.getAppChangelog - Get a list of service messages with app-specific changelogs
  • -
  • help.getInviteText - Returns a localized invitation message that can be sent via SMS to contacts that haven't signed up to Telegram yet
  • -
-

Terms of service

-
help.termsOfServiceUpdateEmpty#e3309f7f expires:int = help.TermsOfServiceUpdate;
-help.termsOfServiceUpdate#28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate;
-
-help.termsOfService#780a0310 flags:# popup:flags.0?true id:DataJSON text:string entities:Vector<MessageEntity> min_age_confirm:flags.1?int = help.TermsOfService;
-
-auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
-
----functions---
-
-help.getTermsOfServiceUpdate#2ca51fd1 = help.TermsOfServiceUpdate;
-help.acceptTermsOfService#ee72f79a id:DataJSON = Bool;
-
-auth.signIn#bcd51581 phone_number:string phone_code_hash:string phone_code:string = auth.Authorization;
-
-account.deleteAccount#418d4e0b reason:string = Bool;
-

These methods can be used for managing consent to Telegram's Terms Of Service.

-

Typically, before a user signs up by invoking auth.signUp, apps should show a pop-up (if the popup flag of the help.termsOfService method is set), asking the user to accept Telegram's terms of service; in case of denial, the user is to be returned to the initial page of the login flow.

-

When signing up for the first time, the help.termsOfService is to be obtained from the auth.authorizationSignUpRequired constructor returned by the auth.signIn.

-

After signing up, or when logging in as an existing user, apps are supposed to call help.getTermsOfServiceUpdate to check for any updates to the Terms of Service; this call should be repeated after expires seconds have elapsed.
-If an update to the Terms Of Service is available, clients are supposed to show a consent popup; if accepted, clients should call help.acceptTermsOfService, providing the termsOfService id JSON object; in case of denial, clients are to delete the account using account.deleteAccount, providing Decline ToS update as deletion reason.

-

Example implementation: android (signup), android (after login)

-

Telegram support info

-
user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
-
-help.support#17c6b5f6 phone_number:string user:User = help.Support;
-help.supportName#8c05f1c9 name:string = help.SupportName;
-
----functions---
-
-help.getSupport#9cdf08cd = help.Support;
-help.getSupportName#d360e72c = help.SupportName;
-

These methods can be used for fetching info about Telegram's support user, that users can use to get support and ask questions about the app.

- -

Country information and login phone patterns

-
help.countryCode#4203c5ef flags:# country_code:string prefixes:flags.0?Vector<string> patterns:flags.1?Vector<string> = help.CountryCode;
-
-help.country#c3878e23 flags:# hidden:flags.0?true iso2:string default_name:string name:flags.1?string country_codes:Vector<help.CountryCode> = help.Country;
-
-help.countriesListNotModified#93cc1f32 = help.CountriesList;
-help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;
-
----functions---
-help.getCountriesList#735787a8 lang_code:string hash:int = help.CountriesList;
-

help.getCountriesList can be used to fetch a list of localized names for all available countries and phone code patterns for logging in.

-

The phone code pattern should be used when showing the login screen, or when changing phone number: for example, a pattern value of XXX XXX XXX with country_code +39 indicates that the phone field for login should accept a spaced pattern like +39 123 456 789.
-Also, the beginning of the national part of the phone number (123 456 789) should match one of the prefixes, if any were returned.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/datacenter.html b/data/core.telegram.org/api/datacenter.html deleted file mode 100644 index f660f4af74..0000000000 --- a/data/core.telegram.org/api/datacenter.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - Working with Different Data Centers - - - - - - - - - - - - - -
- -
-
-
- -

Working with Different Data Centers

- -

The servers are divided into several data centers (hereinafter “DCs”) in different parts of the world. -A complete list of proxy access points for these DCs may be obtained using help.getConfig:

-
dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;
-config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;
----functions---
-help.getConfig#c4f9186b = Config;
-

In this context, this_dc is the number of the current DC, dc_options is a list of all DCs available at the moment, each of which has an id, ip, and port for establishing a connection. Please note that ip and port may change frequently, based on proxy server load and the user's current location.
-Typically, each DC has at least one IPv4 and one IPv6 endpoint available.

-

To optimize client communication with the API, each client must use the connection to the closest access point for its main queries (sending messages, getting contacts, etc.). Therefore, knowing how to select a DC is required before communicating with the API.

-

Registration/Authorization

-

The auth.sendCode method is the basic entry point when registering a new user or authorizing an existing user. 95% of all redirection cases to a different DC will occure when invoking this method.

-

The client does not yet know which DC it will be associated with; therefore, it establishes an encrypted connection to a random address and sends its query to that address. -Having received a phone_number from a client, we can find out whether or not it is registered in the system. If it is, then, if necessary, instead of sending a text message, we request that it establish a connection with a different DC first (PHONE_MIGRATE_X error). -If we do not yet have a user with this number, we examine its IP-address. We can use it to identify the closest DC. Again, if necessary, we redirect the user to a different DC (NETWORK_MIGRATE_X error).

-

Testing Redirects

-

There are reserved phone number prefixes to test the correctness of the application’s handling of redirects between DCs. Read more in User Authorization article.

-

File Access

-

A file saved by a user with upload.saveFilePart will be available for direct download only from the DC where the query was executed. That is why each file has a dc_id parameter:

-
document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
-photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;
-
-encryptedFile#4a70994c id:long access_hash:long size:int dc_id:int key_fingerprint:int = EncryptedFile;
-
-userProfilePhoto#82d1f706 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = UserProfilePhoto;
-chatPhoto#1c6e1c11 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = ChatPhoto;
-

To download the file, an encrypted connection to DC dc_id must be established and used to execute the upload.getFile query. -If an attempt is made to download the file over a wrong connection, the FILE_MIGRATE_X error will be returned.

-

Please note that encryption keys are not copied between DCs; therefore, the process of establishing an encrypted connection is started from the very beginning for each new DC. An issued auth_key can be associated with the current authorized user by using an authorization transfer.

-

User Migration

-

During the process of working with the API, user information is accumulated in the DC with which the user is associated. This is the reason a user cannot be associated with a different DC by means of the client. However, in the future, during prolonged communication from an unusual location, we may decide that the user’s data must be moved to a different DC. After some time, the data will be copied and the association will be updated. Once this happens, when executing any query transmitted to the old DC, the API will return the USER_MIGRATE_X error. The client will then have to establish a connection with the new DC and repeat the query.

-

Authorization Transfer

-

The following methods can be used to eliminate the need for users to enter the code from a text message every time:

-
auth.exportedAuthorization#b434e2b8 id:long bytes:bytes = auth.ExportedAuthorization;
-auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
----functions---
-auth.importAuthorization#a57a7dad id:long bytes:bytes = auth.Authorization;
-auth.exportAuthorization#e5bfffcd dc_id:int = auth.ExportedAuthorization;
-

auth.exportAuthorization must be executed in the current DC (the DC with which a connection has already been established), passing in dc_id as the value for the new DC. The method should return the user identifier and a long string of random data. An import operation can be performed at the new DC by sending it what was received. Queries requiring authorization can then be successfully executed in the new DC.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/dice.html b/data/core.telegram.org/api/dice.html deleted file mode 100644 index 3fd5d73de0..0000000000 --- a/data/core.telegram.org/api/dice.html +++ /dev/null @@ -1,149 +0,0 @@ - - - - - Dice - - - - - - - - - - - - - -
- -
-
-
- -

Dice

- -

Telegram supports sending animated dice emojis.
-This is implemented by using the dice constructors:

-
inputMediaDice#e66fbf7b emoticon:string = InputMedia;
-messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;
-
-inputStickerSetDice#e67f520e emoticon:string = InputStickerSet;
-
-messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
-
----functions---
-
-messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-
-messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;
-
-help.getAppConfig#98914110 = JSONValue;
-

On startup, clients should fetch app configuration using help.getAppConfig.
-Then, for each dice emoji contained in the emojies_send_dice field, clients should fetch the dice emoji stickerset by calling the messages.getStickerSet method, providing the properly populated inputStickerSetDice to the stickerset field.
-The returned stickerset will contain a set of animated stickers, one for each of the dice outcomes, plus a first looping sticker that should be shown as preview to the user before actually sending the dice.

-

If a user attempts to send a single emoji from the ones specified in emojies_send_dice, the dice should be sent using messages.sendMedia, providing the dice emoji to the emoticon field.

-

Incoming dice stickers will be received as a messageMediaDice constructor, along with a randomly generated server-side value, ranging from 1 to the maximum allowed value for this type of dice.
-Clients should display the correct dice animated sticker for the specified value: since dice values start from 1, and the first animated sticker in dice stickerset is the preview, value can be used to directly index the documents sticker array from the animated stickerset.

-

The emojies_send_dice_success configuration parameter contains more info about dice emojis other than the basic 🎲:

-
    "emojies_send_dice_success": {
-        "\ud83c\udfaf": {
-            "value": 6,
-            "frame_start": 62
-        },
-        "\ud83c\udfc0": {
-            "value": 5,
-            "frame_start": 110
-        }
-    }
-

For each of the dice emojis, a maximum "winning" value is specified, along with the frame number at which to show the fireworks 🎆.
-Please note that dice animated stickers should loop only once, right after being sent/received for the first time; clicking on the dice sticker should bring up a popup, inviting the user to send a new dice of the same type.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/discussion.html b/data/core.telegram.org/api/discussion.html deleted file mode 100644 index d1181b0f5f..0000000000 --- a/data/core.telegram.org/api/discussion.html +++ /dev/null @@ -1,151 +0,0 @@ - - - - - Discussion groups - - - - - - - - - - - - - -
- -
-
-
- -

Discussion groups

- -
- -

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
-
-channelFull#e9b27a17 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector<string> groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string = ChatFull;
-
-messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
-
----functions---
-
-channels.setDiscussionGroup#40582bb2 broadcast:InputChannel group:InputChannel = Bool;
-channels.getGroupsForDiscussion#f5dad378 = messages.Chats;
-

A discussion group can be associated to a channel using channels.setDiscussionGroup.
-The discussion group can be accessed in the client by clicking on the discuss button of the channel, or by accessing the comment section of a specific post; the discussion group ID is also present in the linked_chat_id field of the channelFull constructor.

-

All messages sent to the channel will also be sent to the linked group (with sender peer from_id equal to the peer of the linked channel); those messages will also be automatically pinned in the group.

-

Linking a discussion group

-

To obtain a list of admined supergroups that a channel admin can possibly associate to a channel, use channels.getGroupsForDiscussion.
-Returned legacy group chats must be first upgraded to supergroups before they can be set as a discussion group.
-Before linking a supergroup to a channel, access to the supergroup's old messages must also be enabled using channels.togglePreHistoryHidden.

-

To set a returned supergroup as a discussion group use channels.setDiscussionGroup.

-

Schema:

-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
-
-messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
-
----functions---
-
-channels.setDiscussionGroup#40582bb2 broadcast:InputChannel group:InputChannel = Bool;
-channels.getGroupsForDiscussion#f5dad378 = messages.Chats;
-
-channels.togglePreHistoryHidden#eabbb94c channel:InputChannel enabled:Bool = Updates;
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/drafts.html b/data/core.telegram.org/api/drafts.html deleted file mode 100644 index b6ffd788e0..0000000000 --- a/data/core.telegram.org/api/drafts.html +++ /dev/null @@ -1,131 +0,0 @@ - - - - - Message drafts - - - - - - - - - - - - - -
- -
-
-
- -

Message drafts

- -
- -

Message drafts in Telegram allow syncing the text typed into message fields between devices.

-

Drafts

-

Drafts are represented by the DraftMessage constructors. -The parameters of the peer-specific draft should be used as defaults when composing a message to be sent to a certain peer (in the case of media, the same draft should still be used as base, the message will become the caption). -If the user exits the app before sending the message, the message should be saved as a draft:

-

Saving drafts

-

Drafts can be saved using the messages.saveDraft method.

-

Downloading drafts

-

New drafts are automatically sent to all devices via updateDraftMessage updates.

-

Dialog objects fetched via the API also contain the draft associated with the dialog.

-

Clearing drafts

-

Drafts can be cleared by setting the clear_draft flag when sending messages or media using messages.sendMessage, messages.sendMedia, messages.sendMultiMedia, messages.sendInlineBotResult and similar or manually by passing empty values to messages.saveDraft.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/end-to-end/pfs.html b/data/core.telegram.org/api/end-to-end/pfs.html deleted file mode 100644 index 8da37768e9..0000000000 --- a/data/core.telegram.org/api/end-to-end/pfs.html +++ /dev/null @@ -1,176 +0,0 @@ - - - - - Perfect Forward Secrecy - - - - - - - - - - - - - -
- -
-
-
- -

Perfect Forward Secrecy

- -
-

Telegram supports Perfect Forward Secrecy (PFS) in Secret Chats as of Layer 20. See updating to new layers.

-
-

In order to keep past communications safe, official Telegram clients will initiate re-keying once a key has been used to decrypt and encrypt more than 100 messages, or has been in use for more than one week, provided the key has been used to encrypt at least one message. Old keys are then securely discarded and cannot be reconstructed, even with access to the new keys currently in use.

-

Any client participating in a Secret Chat can initiate re-keying as soon as it perceives that the current key has been used for too long or for encrypting too many messages. Please note that you should never initiate a new instance of the re-keying protocol if an uncompleted instance exists, initiated by either party.

-

Note: third-party developers are required to maintain the same level of security. All clients with secret chat support must be able to initiate re-keying and accept relevant service messages. See Security Guidelines.

-

Re-keying protocol

-

New keys are generated by exchanging special messages, using previously established keys for encryption. The re-keying protocol between parties A and B normally consists of four steps:

-
1. decryptedMessageActionRequestKey
-

A (re-keying initiator) generates a new value of a, subject to the same limitations as for the initial Diffie-Hellman key exchange, and sends the value of pow(g,a) to B, embedded in a decryptedMessageService:

-
decryptedMessageActionRequestKey exchange_id:long g_a:string = DecryptedMessageAction;
-
    -
  • exchange_id is a random number identifying this instance of the Re-Keying Protocol for both parties
  • -
  • g_a is the value of pow(g,a) mod p
  • -
-

Note that the same Diffie--Hellman parameters (p,g) as for the initial Diffie--Hellman key exchange in this secret chat are used. They do not need to be re-transmitted explicitly.

-
2. decryptedMessageActionAcceptKey
-

Upon receipt of the above service message, B checks its content, and generates a response with same exchange_id, for a newly generated value of b:

-
decryptedMessageActionAcceptKey exchange_id:long g_b:string key_fingerprint:long = DecryptedMessageAction;
-
    -
  • exchange_id is the same as in the received decryptedMessageActionRequestKey
  • -
  • g_b is the value of pow(g,b) mod p
  • -
  • key_fingerprint is the 64-bit fingerprint of the newly generated key = pow(g_a, b) mod p, used as a sanity check of the implementation
  • -
-

At this stage, B can already compute the new key key = pow(g_a, b) mod p and its key_fingerprint (last 64 bits of its SHA-1). However, it continues using the previous key until the completion of the exchange.

-

Once side B sends decryptedMessageActionAcceptKey, it cannot abort the key exchange; it must be ready to switch to the new key immediately after a decryptedMessageActionCommitKey is received. Therefore, if side B wishes to delay the usage of new key, for example in order to fill some seq_no gaps first, it must delay the decryptedMessageActionAcceptKey answer accordingly.

-
3. decryptedMessageActionCommitKey
-

Once A receives a valid decryptedMessageActionAcceptKey, it performs all necessary checks, and "commits" the new key by means of the following service message:

-
decryptedMessageActionCommitKey exchange_id:long key_fingerprint:long = DecryptedMessageAction;
-
    -
  • exchange_id is the same as in the two previous messages
  • -
  • key_fingerprint is the value of the hash (last 64 bits of SHA-1) of the new key computed by A, for implementation sanity check
  • -
-

After that, A can (and must) encrypt all following messages with the new key.

-

If side A wishes to delay installation of the new key, for example because there are some seq_no gaps that it wants to fill first, it must delay decryptedMessageActionCommitKey answer accordingly.

-
4. Final step
-

When B receives either a decryptedMessageActionCommitKey or a message encrypted by the new key, recognized by the value of key_fingerprint prepended to the encrypted message (it may happen that the decryptedMessageActionCommitKey has been lost and will be re-requested later), it assumes that A has started using the new key for encryption, and does the same.

-

However, the previous key may be kept until there are no gaps in received messages up to the switch to the new key. Once all the gaps have been filled, the old key must be securely discarded.

-

There is one exception to this rule — the SHA-1 of the original key (generated during the establishment of Secret Chat in question) is always stored, in order to show key visualizations on the clients.

-

Aborting protocol

-

Any of the parties may abort any instance of an uncompleted re-keying protocol, unless decryptedMessageActionCommitKey or decryptedMessageActionAcceptKey has been already sent by the party in question. In order to abort re-keying, send

-
decryptedMessageActionAbortKey exchange_id:long = DecryptedMessageAction;
-

This could be done, for example, if the party is already participating in a different instance of the re-keying protocol, or if the received values of g_a, g_b and other parameters do not pass security checks. In the latter case, it might be advisable to abort the Secret Chat altogether.

-

Discarding Previous Keys

-

Once B receives decryptedMessageActionCommitKey, it can safely discard the previous key provided there are no gaps. However, A may only discard the previous key after a message encrypted with the new key has been received. If no ordinary messages are scheduled to be sent, a special no-op message should sent by B for this purpose:

-
decryptedMessageActionNoop = DecryptedMessageAction;
-

Concurrent Re-Keying

-

It may happen that both parties concurrently initiate re-keying by sending decryptedMessageActionRequestKey without knowing that the other party has already done so. If each side aborts re-keying because it is already participating in another instance of the protocol initiated by itself, the re-keying will never happen.

-

Because of this possibility, we suggest that only the instance with the smaller exchange_id is aborted, with the option to re-use its (a,g_a) for the re-keying protocol instance with the larger exchange_id (when compared as a long, i.e. signed little-endian 64-bit integer).

-

In other words, if a decryptedMessageActionRequestKey is received after A has sent its decryptedMessageActionRequestKey, but has not yet received decryptedMessageActionAcceptKey, the following is to be done:

-
    -
  • if exchange_id in the sent decryptedMessageActionRequestKey was larger than that in the decryptionActionRequestKey just received, abort the newly-suggested re-keying protocol instance without sending explicit decryptedMessageActionAbortKey (the other side will do the same according to the next rule).
  • -
  • if exchange_id in our decryptedMessageActionRequestKey was smaller, respond to the newly-received decryptedMessageActionRequestKey with a decryptedMessageActionAcceptKey, and participate only in the re-keying protocol instance initiated by the other side. It is possible to re-use at this stage the value of g_a (now called g_b) that was generated for the original decryptedMessageActionRequestKey, now abandoned, or totally new (b,g_b) can be generated.
  • -
  • in the unlikely (2^{-64}) case both exchange_id are equal, abort both instances without sending an explicit decryptedMessageActionAbortKey. The other side will do the same.
  • -
-
Key Visualization
-

Since all re-keying instances are carried over the secure channel established when the secret chat is created, it is necessary for the user to confirm that no MITM attack had taken place during the initial exchange. The key visualization on the clients uses the first 128-bits of the SHA-1 of the original key created when the Secret Chat was first established, followed by the first 160 bits of the SHA-256 of the key in use when the secret chat was updated to layer 46 (coincides with the original key if chat was created using layer 46).

-
-

Please note that the key_fingerprint parameter was introduced as a maintenance tool (with a misleading name) and is not related to key visualization on the clients.

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/end-to-end/seq_no.html b/data/core.telegram.org/api/end-to-end/seq_no.html deleted file mode 100644 index cec36e31d6..0000000000 --- a/data/core.telegram.org/api/end-to-end/seq_no.html +++ /dev/null @@ -1,173 +0,0 @@ - - - - - Sequence numbers in Secret Chats - - - - - - - - - - - - - -
- -
-
-
- -

Sequence numbers in Secret Chats

- -

It is necessary to interpret all messages in their original order to protect against reordering, reflection, replay, omission and other manipulations (decryptedMessageActionResend messages are the only exception to this rule, see avoiding concurrent gaps). Secret chats support a special mechanism for handling seq_no counters independently from the server. Note that any service messages in secret chats must also increment the seq_no.

-

All Secret Chats messages in clients using Layer 17 or higher are wrapped in decryptedMessageLayer and have seq_no (sequence number) counters attached to them. The seq_no counters in their raw form are initialized with (out_seq_no, in_seq_no) := (0,0), and incremented strictly by 1 after any message (service or not) is sent/received and processed. They must be protected from mirroring before being sent to the remote client by transformation according to formula 2*raw_seq_no+x, where x is 0 or 1, determined by the following rule:

- - - - - - - - - - - - - - - - - -
in_seq_noout_seq_no
secret chat initiated by sender01
secret chat initiated by recipient10
-

In this way the least significant bit of each seq_no field included in the message is different for incoming and outgoing messages. This is done to prevent a possible attacker from mirroring the messages. If any of the received in_seq_no or out_seq_no are not consistent in terms of parity (see table above), the client is required to immediately abort the secret chat.

-
-

E.g., the first message the local client sends to any secret chat will have out_seq_no of 0+x_out, the second one will have out_seq_no of 2*1+x_out, and so on, where x_out is 0 if the chat was initiated by the remote client, 1 otherwise; similarly for the received messages, but there x_in is used instead of x_out and is equal to 0 if the chat was initiated by the local client, 1 otherwise.

-
-

Raw sequence numbers will be used in the remaining part of this text, unless otherwise specified.

-

Preventing gaps

-

Your client must ensure that all outgoing secret chat messages are queued on the server in the correct order. This is achieved by correctly placing them into the invokeAfterMsgs chain. Failure to do this may result in gaps on the remote client, which may in turn lead to aborted secret chats. The local client must maintain the correct sequence of in_seq_no for the remote client. To achieve this, assign in_seq_no and out_seq_no to each message at the exact moment when the message is created, and never change them in the future.

-

Security checks

-

Checking out_seq_no

-

Your client must check that it has received each message with the sequence number out_seq_no starting from 0 to some current point C. It should then expect the next message to have the sequence number out_seq_no=C+1. If the out_seq_no in the received message does not match this, the following needs to be done:

-
    -
  • If the received out_seq_no<=C, the local client must drop the message (repeated message). The client should not check the contents of the message because the original message could have been deleted (see Deleting unacknowledged messages).
  • -
  • If the received out_seq_no>C+1, it most likely means that the server left out some messages due to a technical failure or due to the messages becoming obsolete. A temporary solution to this is to simply abort the secret chat. But since this may cause some existing older secret chats to be aborted, it is strongly recommended for the client to properly handle such seq_no gaps. Note that in_seq_no is not increased upon receipt of such a message; it is advanced only after all preceding gaps are filled.
  • -
-

Proper handling of gaps

-

In order to correctly handle incoming messages after a hole has been identified (when received out_seq_no>C+1), it is necessary to put received messages with the wrong seq_no into a "waiting queue" on the local client, and to re-request the missing messages using the special constructor decryptedMessageActionResend start_seq_no:int end_seq_no:int = DecryptedMessageAction;. The sequence numbers used in this constructor must be ready for interpretation by the remote client and therefore cannot be in their raw form: you can easily get the necessary start_seq_no by adding 2 to the out_seq_no of the last message before the hole and the end_seq_no by subtracting 2 from the out_seq_no of the received message with the wrong sequence number.

-

Each hole normally requires only one request to resend messages — if the remote client keeps sending out of sync messages, they should be put into the queue without sending a new request. Having received the missing messages, the local client must first interpret these messages in the right order by their seq_no. Once this is done, the client can proceed to interpret messages from the queue (again, in the right seq_no order).

-

Special cases:

-
    -
  • Note that having two gaps simultaneously is very rare (provided that the remote client and server are operating normally) and it is acceptable to abort the secret chat in this situation.
  • -
  • If a local client receives decryptedMessageActionResend but is unable to satisfy the request, it must abort the secret chat.
  • -
-

Avoiding concurrent gaps

-

In order to avoid getting stuck with concurrent gaps on both sides, decryptedMessageActionResend must always be interpreted immediately upon receipt in all cases, even if its out_seq_no>=C+1. Note that each decryptedMessageActionResend must only be handled once, it must not be interpreted again when we interpret messages in the queue.

-

Checking and handling in_seq_no

-

in_seq_no of all received messages must be valid. To ensure this, perform the following checks:

-
    -
  • in_seq_no must form a non-decreasing sequence of non-negative integer numbers.
  • -
  • in_seq_no must be valid at the moment of receiving the message, that is, if D is the out_seq_no of last message we sent, the received in_seq_no should not be greater than D + 1. This also allows us to insert the received message into its correct place in the secret chat. For example, imagine that the local client has sent 5 secret chat messages, and then receives a secret chat message with the text "Yes" and in_seq_no=2. In this situation the local client must place that message after the second message it sent. This makes manipulations with delayed messages impossible.
  • -
-

If in_seq_no contradicts these criteria, the local client is required to immediately abort the secret chat. This could happen only in case of malicious or buggy behaviour on either server or remote client side.

-

Deleting unacknowledged messages

-

In case the user on the local client has deleted a message before the server (or the remote client, if decryptedMessageActionResend is handled correctly) could acknowledge the message, for security reasons, you must:

-
    -
  • securely destroy the contents of the message (as in case of any other deleted Secret Chat message);
  • -
  • change the local copy of the original message to decryptedMessageActionDeleteMessages with random_id equal to its own random_id;
  • -
  • create a new outgoing message deleting the original message.
  • -
-

This must be done because your client doesn't know whether the remote client really received the message or not. In the case the message was already received, it will be deleted by the second message; otherwise it must arrive as a "self-delete" message to maintain the correct sequence of seq_no.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/end-to-end/video-calls.html b/data/core.telegram.org/api/end-to-end/video-calls.html deleted file mode 100644 index f0e546831e..0000000000 --- a/data/core.telegram.org/api/end-to-end/video-calls.html +++ /dev/null @@ -1,215 +0,0 @@ - - - - - End-to-End Encrypted Voice and Video Calls - - - - - - - - - - - - - -
- -
-
-
- -

End-to-End Encrypted Voice and Video Calls

- -

This article describes the end-to-end encryption used for Telegram voice and video calls.

-
Related Articles
-

- -
-

Establishing Calls

-

Before a call is ready, some preliminary actions have to be performed. The calling party needs to contact the party to be called and check whether it is ready to accept the call. Besides that, the parties have to negotiate the protocols to be used, learn the IP addresses of each other or of the Telegram relay servers to be used (so-called reflectors), and generate a one-time encryption key for this voice call with the aid of Diffie--Hellman key exchange. All of this is accomplished in parallel with the aid of several Telegram API methods and related notifications. This document covers details related to key generation, encryption and security.

-

Key Generation

-

The Diffie-Hellman key exchange, as well as the whole protocol used to create a new voice call, is quite similar to the one used for Secret Chats. We recommend studying the linked article before proceeding.

-

However, we have introduced some important changes to facilitate the key verification process. Below is the entire exchange between the two communicating parties, the Caller (A) and the Callee (B), through the Telegram servers (S).

-
    -
  • A executes messages.getDhConfig to find out the 2048-bit Diffie-Hellman prime p and generator g. The client is expected to check whether p is a safe prime and perform all the security checks necessary for secret chats.
  • -
  • A chooses a random value of a, 1 < a < p-1, and computes g_a:=power(g,a) mod p (a 256-byte number) and g_a_hash:=SHA256(g_a) (32 bytes long).
  • -
  • A invokes (sends to server S) phone.requestCall, which has the field g_a_hash:bytes, among others. For this call, this field is to be filled with g_a_hash, not g_a itself.
  • -
  • The Server S performs privacy checks and sends an updatePhoneCall update with a phoneCallRequested constructor to all of B's active devices. This update, apart from the identity of A and other relevant parameters, contains the g_a_hash field, filled with the value obtained from A.
  • -
  • B accepts the call on one of their devices, stores the received value of g_a_hash for this instance of the voice call creation protocol, chooses a random value of b, 1 < b < p-1, computes g_b:=power(g,b) mod p, performs all the required security checks, and invokes the phone.acceptCall method, which has a g_b:bytes field (among others), to be filled with the value of g_b itself (not its hash).
  • -
  • The Server S sends an updatePhoneCall with the phoneCallDiscarded constructor to all other devices B has authorized, to prevent accepting the same call on any of the other devices. From this point on, the server S works only with that of B's devices which has invoked phone.acceptCall first.
  • -
  • The Server S sends to A an updatePhoneCall update with phoneCallAccepted constructor, containing the value of g_b received from B.
  • -
  • A performs all the usual security checks on g_b and a, computes the Diffie--Hellman key key:=power(g_b,a) mod p and its fingerprint key_fingerprint:long, equal to the lower 64 bits of SHA1(key), the same as with secret chats. Then A invokes the phone.confirmCall method, containing g_a:bytes and key_fingerprint:long.
  • -
  • The Server S sends to B an updatePhoneCall update with the phoneCall constructor, containing the value of g_a in g_a_or_b:bytes field, and key_fingerprint:long
  • -
  • At this point B receives the value of g_a. It checks that SHA256(g_a) is indeed equal to the previously received value of g_a_hash, performs all the usual Diffie-Hellman security checks, and computes the key key:=power(g_a,b) mod p and its fingerprint, equal to the lower 64 bits of SHA1(key). Then it checks that this fingerprint equals the value of key_fingerprint:long received from the other side, as an implementation sanity check.
  • -
-

At this point, the Diffie--Hellman key exchange is complete, and both parties have a 256-byte shared secret key key which is used to encrypt all further exchanges between A and B.

-

It is of paramount importance to accept each update only once for each instance of the key generation protocol, discarding any duplicates or alternative versions of already received and processed messages (updates).

-

Encryption

-
-

This document describes encryption in voice and video calls as implemented in Telegram apps with versions 7.0 and above. See this document for details on encryption used in voice calls in app versions released before August 14, 2020.

-
-

The Telegram Voice and Video Call Library uses an optimized version of MTProto 2.0 to send and receive packets, consisting of one or more end-to-end encrypted messages of various types (ice candidates list, video formats, remote video status, audio stream data, video stream data, message ack or empty).

-

This document describes only the encryption process, leaving out encoding and network-dependent parts.

-

The library starts working with:

-
    -
  • An encryption key key shared between the parties, as generated above.
  • -
  • Information whether the call is outgoing or incoming.
  • -
  • Two data transfer channels: signaling, offered by the Telegram API, and transport based on WebRTC.
  • -
-

Both data transfer channels are unreliable (messages may get lost), but signaling is slower and more reliable.

-

Encrypting Call Data

-

The body of a packet (decrypted_body) consists of several messages and their respective seq numbers concatenated together.

-
    -
  • decrypted_body = message_seq1 + message_body1 + message_seq2 + message_body2
  • -
-

Each decrypted_body is unique because no two seq numbers of the first message can be the same. If only old messages need to be re-sent, an empty message with new unique seq is added to the packet first.

-

The encryption key key is used to compute a 128-bit msg_key and then a 256-bit aes_key and a 128-bit aes_iv:

-
    -
  • msg_key_large = SHA256 (substr(key, 88+x, 32) + decrypted_body);
  • -
  • msg_key = substr (msg_key_large, 8, 16);
  • -
  • sha256_a = SHA256 (msg_key + substr (key, x, 36));
  • -
  • sha256_b = SHA256 (substr (key, 40+x, 36) + msg_key);
  • -
  • aes_key = substr (sha256_a, 0, 8) + substr (sha256_b, 8, 16) + substr (sha256_a, 24, 8);
  • -
  • aes_iv = substr (sha256_b, 0, 4) + substr (sha256_a, 8, 8) + substr (sha256_b, 24, 4);
  • -
-

x depends on whether the call is outgoing or incoming and on the connection type:

-
    -
  • x = 0 for outgoing + transport
  • -
  • x = 8 for incoming + transport
  • -
  • x = 128 for outgoing + signaling
  • -
  • x = 136 for incoming + signaling
  • -
-

This allows apps to decide which packet types will be sent to which connections and work in these connections independently (with each having its own seq counter).

-

The resulting aes_key and aes_iv are used to encrypt decrypted_body:

-
    -
  • encrypted_body = AES_CTR (decrypted_body, aes_key, aes_iv)
  • -
-

The packet that gets sent consists of msg_key and encrypted_body:

-
    -
  • packet_bytes = msg_key + encrypted_body
  • -
-

When received, the packet gets decrypted using key and msg_key, after which msg_key is checked against the relevant SHA256 substring. If the check fails, the packet must be discarded.

-

Protecting Against Replay Attacks

-

Each of the peers maintains its own 32-bit monotonically increasing counter for outgoing messages, seq, starting with 1. This seq counter is prepended to each sent message and increased by 1 for each new message. No two seq numbers of the first message in a packet can be the same. If only old messages need to be re-sent, an empty message with a new unique seq is added to the packet first. When the seq counter reaches 2^30, the call must be aborted. Each peer stores seq values of all the messages it has received (and processed) which are larger than max_received_seq - 64, where max_received_seq is the largest seq number received so far.

-

If a packet is received, the first message of which has a seq that is smaller or equal to max_received_seq - 64 or its seq had already been received, the message is discarded. Otherwise, the seq values of all incoming messages are memorized and max_received_seq is adjusted. This guarantees that no two packets will be processed twice.

-

Key Verification

-

To verify the key, and ensure that no MITM attack is taking place, both parties concatenate the secret key key with the value g_a of the Caller ( A ), compute SHA256 and use it to generate a sequence of emoticons. More precisely, the SHA256 hash is split into four 64-bit integers; each of them is divided by the total number of emoticons used (currently 333), and the remainder is used to select specific emoticons. The specifics of the protocol guarantee that comparing four emoticons out of a set of 333 is sufficient to prevent eavesdropping (MiTM attack on DH) with a probability of 0.9999999999.

-

This is because instead of the standard Diffie-Hellman key exchange which requires only two messages between the parties:

-
    -
  • A->B : (generates a and) sends g_a := g^a
  • -
  • B->A : (generates b and true key (g_a)^b, then) sends g_b := g^b
  • -
  • A : computes key (g_b)^a
  • -
-

we use a three-message modification thereof that works well when both parties are online (which also happens to be a requirement for voice calls):

-
    -
  • A->B : (generates a and) sends g_a_hash := hash(g^a)
  • -
  • B->A : (stores g_a_hash, generates b and) sends g_b := g^b
  • -
  • A->B : (computes key (g_b)^a, then) sends g_a := g^a
  • -
  • B : checks hash(g_a) == g_a_hash, then computes key (g_a)^b
  • -
-

The idea here is that A commits to a specific value of a (and of g_a) without disclosing it to B. B has to choose its value of b and g_b without knowing the true value of g_a, so that it cannot try different values of b to force the final key (g_a)^b to have any specific properties (such as fixed lower 32 bits of SHA256(key)). At this point, B commits to a specific value of g_b without knowing g_a. Then A has to send its value g_a; it cannot change it even though it knows g_b now, because the other party B would accept only a value of g_a that has a hash specified in the very first message of the exchange.

-

If some impostor is pretending to be either A or B and tries to perform a Man-in-the-Middle Attack on this Diffie--Hellman key exchange, the above still holds. Party A will generate a shared key with B -- or whoever pretends to be B -- without having a second chance to change its exponent a depending on the value g_b received from the other side; and the impostor will not have a chance to adapt his value of b depending on g_a, because it has to commit to a value of g_b before learning g_a. The same is valid for the key generation between the impostor and the party B.

-

The use of hash commitment in the DH exchange constrains the attacker to only one guess to generate the correct visualization in their attack, which means that using just over 33 bits of entropy represented by four emoji in the visualization is enough to make a successful attack highly improbable.

-
-

For a slightly more user-friendly explanation of the above see: How are calls authenticated?

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/end-to-end/voice-calls.html b/data/core.telegram.org/api/end-to-end/voice-calls.html deleted file mode 100644 index 2719cf8209..0000000000 --- a/data/core.telegram.org/api/end-to-end/voice-calls.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - End-to-End Encrypted Voice Calls - - - - - - - - - - - - - -
- -
-
-
- -

End-to-End Encrypted Voice Calls

- -
-

This document describes encryption in voice calls as implemented in Telegram apps with versions < 7.0. See this document for details on encryption used in voice and video calls in app versions released on August 14, 2020 and later.

-
-
Related articles
-

- -

Establishing voice calls

-

Before a voice call is ready, some preliminary actions have to be performed. The calling party needs to contact the party to be called and check whether it is ready to accept the call. Besides that, the parties have to negotiate the protocols to be used, learn the IP addresses of each other or of the Telegram relay servers to be used (so-called reflectors), and generate a one-time encryption key for this voice call with the aid of Diffie--Hellman key exchange. All of this is accomplished in parallel with the aid of several Telegram API methods and related notifications. This document details the generation of the encryption key. Other negotiations will be eventually documented elsewhere.

-

Key Generation

-

The Diffie-Hellman key exchange, as well as the whole protocol used to create a new voice call, is quite similar to the one used for Secret Chats. We recommend studying the linked article before proceeding.

-

However, we have introduced some important changes to facilitate the key verification process. Below is the entire exchange between the two communicating parties, the Caller (A) and the Callee (B), through the Telegram servers (S).

-
    -
  • A executes messages.getDhConfig to find out the 2048-bit Diffie-Hellman prime p and generator g. The client is expected to check whether p is a safe prime and perform all the security checks necessary for secret chats.
  • -
  • A chooses a random value of a, 1 < a < p-1, and computes g_a:=power(g,a) mod p (a 256-byte number) and g_a_hash:=SHA256(g_a) (32 bytes long).
  • -
  • A invokes (sends to server S) phone.requestCall, which has the field g_a_hash:bytes, among others. For this call, this field is to be filled with g_a_hash, not g_a itself.
  • -
  • The Server S performs privacy checks and sends an updatePhoneCall update with a phoneCallRequested constructor to all of B's active devices. This update, apart from the identity of A and other relevant parameters, contains the g_a_hash field, filled with the value obtained from A.
  • -
  • B accepts the call on one of their devices, stores the received value of g_a_hash for this instance of the voice call creation protocol, chooses a random value of b, 1 < b < p-1, computes g_b:=power(g,b) mod p, performs all the required security checks, and invokes the phone.acceptCall method, which has a g_b:bytes field (among others), to be filled with the value of g_b itself (not its hash).
  • -
  • The Server S sends an updatePhoneCall with the phoneCallDiscarded constructor to all other devices B has authorized, to prevent accepting the same call on any of the other devices. From this point on, the server S works only with that of B's devices which has invoked phone.acceptCall first.
  • -
  • The Server S sends to A an updatePhoneCall update with phoneCallAccepted constructor, containing the value of g_b received from B.
  • -
  • A performs all the usual security checks on g_b and a, computes the Diffie--Hellman key key:=power(g_b,a) mod p and its fingerprint key_fingerprint:long, equal to the lower 64 bits of SHA1(key), the same as with secret chats. Then A invokes the phone.confirmCall method, containing g_a:bytes and key_fingerprint:long.
  • -
  • The Server S sends to B an updatePhoneCall update with the phoneCall constructor, containing the value of g_a in g_a_or_b:bytes field, and key_fingerprint:long
  • -
  • At this point B receives the value of g_a. It checks that SHA256(g_a) is indeed equal to the previously received value of g_a_hash, performs all the usual Diffie-Hellman security checks, and computes the key key:=power(g_a,b) mod p and its fingerprint, equal to the lower 64 bits of SHA1(key). Then it checks that this fingerprint equals the value of key_fingerprint:long received from the other side, as an implementation sanity check.
  • -
-

At this point, the Diffie--Hellman key exchange is complete, and both parties have a 256-byte shared secret key key which is used to encrypt all further exchanges between A and B.

-

It is of paramount importance to accept each update only once for each instance of the key generation protocol, discarding any duplicates or alternative versions of already received and processed messages (updates).

-

Encryption of voice data

-

Both parties A (the Caller) and B (the Callee) transform the voice information into a sequence of small chunks or packets, not more than 1 kilobyte each. This information is to be encrypted using the shared key key generated during the initial exchange, and sent to the other party, either directly (P2P) or through Telegram's relay servers (so-called reflectors). This document describes only the encryption process for each chunk, leaving out voice encoding and the network-dependent parts.

-

Encapsulation of low-level voice data

-

The low-level data chunk raw_data:string, obtained from voice encoder, is first encapsulated into one of the two constructors for the DecryptedDataBlock type, similar to DecryptedMessage used in secret chats:

-
decryptedDataBlock#dbf948c1 random_id:long random_bytes:string flags:# voice_call_id:flags.2?int128 in_seq_no:flags.4?int out_seq_no:flags.4?int recent_received_mask:flags.5?int proto:flags.3?int extra:flags.1?string raw_data:flags.0?string = DecryptedDataBlock;
-simpleDataBlock#cc0d0e76 random_id:long random_bytes:string raw_data:string = DecryptedDataBlock;
-

Here out_seq_no is the chunk's sequence number among all sent by this party (starting from one), in_seq_no -- the highest known out_seq_no from the received packets. The parameter recent_received_mask is a 32-bit mask, used to track delivery of the last 32 packets sent by the other party. The bit i is set if a packet with out_seq_no equal to in_seq_no-i has been received.

-

The higher 8 bits in flags are reserved for use by the lower-level protocol (the one which generates and interprets raw_data), and will never be used for future extensions of decryptedDataBlock.

-

The parameters voice_call_id and proto are mandatory until the other side confirms reception of at least one packet by sending a packet with a non-zero in_seq_no. After that, they become optional, and the simpleDataBlock constructor can be used if the lower level protocol wants to.

-

The parameter voice_call_id is computed from the key key and equals the lower 128 bits of its SHA-256.

-

The random_bytes string should contain at least 7 bytes of random data. The field random_id also contains 8 random bytes, which can be used as a unique packet identifier if necessary.

-

MTProto encryption

-

Once the data is encapsulated in DecryptedDataBlock, it is TL-serialized and encrypted with MTProto, using key instead of auth_key; the parameter x is to be set to 0 for messages from A to B, and to 8 for messages in the opposite direction. Encrypted data are prepended by the 128-bit msg_key (usual for MTProto); before that, either the 128-bit voice_call_id (if P2P is used) or the peer_tag (if reflectors are used) is prepended. The resulting data packet is sent by UDP either directly to the other party (if P2P is possible) or to the Telegram relay servers (reflectors).

-

Key Verification

-

To verify the key, both parties concatenate the secret key key with the value g_a of the Caller ( A ), compute SHA256 and use it to generate a sequence of emoticons. More precisely, the SHA256 hash is split into four 64-bit integers; each of them is divided by the total number of emoticons used (currently 333), and the remainder is used to select specific emoticons. The specifics of the protocol guarantee that comparing four emoticons out of a set of 333 is sufficient to prevent eavesdropping (MiTM attack on DH) with a probability of 0.9999999999.

-

This is because instead of the standard Diffie-Hellman key exchange which requires only two messages between the parties:

-
    -
  • A->B : (generates a and) sends g_a := g^a
  • -
  • B->A : (generates b and true key (g_a)^b, then) sends g_b := g^b
  • -
  • A : computes key (g_b)^a
  • -
-

we use a three-message modification thereof that works well when both parties are online (which also happens to be a requirement for voice calls):

-
    -
  • A->B : (generates a and) sends g_a_hash := hash(g^a)
  • -
  • B->A : (stores g_a_hash, generates b and) sends g_b := g^b
  • -
  • A->B : (computes key (g_b)^a, then) sends g_a := g^a
  • -
  • B : checks hash(g_a) == g_a_hash, then computes key (g_a)^b
  • -
-

The idea here is that A commits to a specific value of a (and of g_a) without disclosing it to B. B has to choose its value of b and g_b without knowing the true value of g_a, so that it cannot try different values of b to force the final key (g_a)^b to have any specific properties (such as fixed lower 32 bits of SHA256(key)). At this point, B commits to a specific value of g_b without knowing g_a. Then A has to send its value g_a; it cannot change it even though it knows g_b now, because the other party B would accept only a value of g_a that has a hash specified in the very first message of the exchange.

-

If some impostor is pretending to be either A or B and tries to perform a Man-in-the-Middle Attack on this Diffie--Hellman key exchange, the above still holds. Party A will generate a shared key with B -- or whoever pretends to be B -- without having a second chance to change its exponent a depending on the value g_b received from the other side; and the impostor will not have a chance to adapt his value of b depending on g_a, because it has to commit to a value of g_b before learning g_a. The same is valid for the key generation between the impostor and the party B.

-

The use of hash commitment in the DH exchange constrains the attacker to only one guess to generate the correct visualization in their attack, which means that using just over 33 bits of entropy represented by four emoji in the visualization is enough to make a successful attack highly improbable.

-
-

For a slightly more user-friendly explanation of the above see: How are calls authenticated?

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/end-to-end_v1.html b/data/core.telegram.org/api/end-to-end_v1.html deleted file mode 100644 index fa693f86cc..0000000000 --- a/data/core.telegram.org/api/end-to-end_v1.html +++ /dev/null @@ -1,225 +0,0 @@ - - - - - Secret chats, end-to-end encryption (v. 1.0, DEPRECATED) - - - - - - - - - - - - - -
- -
-
-
- -

Secret chats, end-to-end encryption (v. 1.0, DEPRECATED)

- -
-

This document describes end-to-end encrypted Secret Chats in MTProto 1.0, its status is DEPRECATED. -For information on end-to-end encryption used in up-to-date Telegram clients, kindly see this document.

-
-
Related articles
-

-
-

Secret Chats are one-on-one chats wherein messages are encrypted with a key held only by the chat’s participants. Please note that the schema for end-to-end encrypted Secret Chats is different from what is used for cloud chats:

-
- -
-

Key Generation

-

The Diffie-Hellman protocol is used for key generation. For more information, see Wikipedia.

-

Let us consider the following scenario: User A would like to initiate encrypted communication with User B.

-

Sending a Request

-

User A executes messages.getDhConfig to obtain the Diffie-Hellman parameters: a prime p, and a high order element g.

-

Executing this method before each new key generation procedure is of vital importance. It makes sense to cache the values of the parameters together with the version in order to avoid having to receive all of the values every time. If the version stored on the client is still up-to-date, the server will return the constructor messages.dhConfigNotModified.

-

Client is expected to check whether p is a safe 2048-bit prime (meaning that both p and (p-1)/2 are prime, and that 2^2047 < p < 2^2048), and that g generates a cyclic subgroup of prime order (p-1)/2, i.e. is a quadratic residue mod p. Since g is always equal to 2, 3, 4, 5, 6 or 7, this is easily done using quadratic reciprocity law, yielding a simple condition on p mod 4g -- namely, p mod 8 = 7 for g = 2; p mod 3 = 2 for g = 3; no extra condition for g = 4; p mod 5 = 1 or 4 for g = 5; p mod 24 = 19 or 23 for g = 6; and p mod 7 = 3, 5 or 6 for g = 7. After g and p have been checked by the client, it makes sense to cache the result, so as to avoid repeating lengthy computations in future. This cache might be shared with one used for Authorization Key generation.

-

If the client has an inadequate random number generator, it makes sense to pass the random_length parameter (random_length> 0) so the server generates its own random sequence random of the appropriate length. -Important: using the server’s random sequence in its raw form may be unsafe. It must be combined with a client sequence, for example, by generating a client random number of the same length (client_random) and using final_random := random XOR client_random.

-

Client A computes a 2048-bit number a (using sufficient entropy or the server’s random; see above) and executes messages.requestEncryption after passing in g_a := pow(g, a) mod dh_prime.

-

User B receives the update updateEncryption for all associated authorization keys (all authorized devices) with the chat constructor encryptedChatRequested. The user must be shown basic information about User A and must be prompted to accept or reject the request.

-

Both clients are to check that g, g_a and g_b are greater than one and smaller than p-1. We recommend checking that g_a and g_b are between 2^{2048-64} and p - 2^{2048-64} as well.

-

Accepting a Request

-

After User B confirms the creation of a secret chat with A in the client interface, Client B also receives up-to-date configuration parameters for the Diffie-Hellman method. Thereafter, it generates a random 2048-bit number, b, using rules similar to those for a.

-

Having received g_a from the update with encryptedChatRequested, it can immediately generate the final shared key: key = (pow(g_a, b) mod dh_prime). If key length < 256 bytes, add several leading zero bytes as padding — so that the key is exactly 256 bytes long. Its fingerprint, key_fingerprint, is equal to the 64 last bits of SHA1 (key).

-

Note: this fingerprint is used as a sanity check for the key exchange procedure to detect bugs while developing client software — it is not connected to the key visualization used on the clients as means of external authentication in secret chats. Key visualizations on the clients are generated using the first 128 bits of SHA1(initial key) followed by the first 160 bits of SHA256(key used when secret chat was updated to layer 46).

-

Client B executes messages.acceptEncryption after passing it g_b := pow(g, b) mod dh_prime and key_fingerprint.

-

For all of Client B’s authorized devices, except the current one, updateEncryption updates are sent with the constructor encryptedChatDiscarded. Thereafter, the only device that will be able to access the secret chat is Device B, which made the call to messages.acceptEncryption.

-

User A will be sent an updateEncryption update with the constructor encryptedChat, for the authorization key that initiated the chat.

-

With g_b from the update, Client A can also receive the shared key key = (pow(g_b, a) mod dh_prime). If key length < 256 bytes, add several leading zero bytes as padding — so that the key is exactly 256 bytes long. If the fingerprint for the received key is identical to the one that was passed to encryptedChat, incoming messages can be sent and processed. Otherwise, messages.discardEncryption must be executed and the user notified.

-

Perfect Forward Secrecy

-

In order to keep past communications safe, official Telegram clients will initiate re-keying once a key has been used to decrypt and encrypt more than 100 messages, or has been in use for more than one week, provided the key has been used to encrypt at least one message. Old keys are then securely discarded and cannot be reconstructed, even with access to the new keys currently in use.

-
-

The re-keying protocol is further described in this article: Perfect Forward Secrecy in Secret Chats.

-
-

Please note that your client must support Forward Secrecy in Secret Chats to be compatible with official Telegram clients.

-

Sending and Receiving Messages in a Secret Chat

-

Serialization and Encryption of Outgoing Messages

-

A TL object of type DecryptedMessage is created and contains the message in plain text. For backward compatibility, the object must be wrapped in the constructor decryptedMessageLayer with an indication of the supported layer (starting with 8). -The TL-Schema for end-to-end encrypted messages contents is represented here ».

-

The resulting construct is serialized as an array of bytes using generic TL rules. The resulting array is padded at the top with 4 bytes of the array length not counting these 4 bytes. -A message key, msg_key, is computed as the 128 low-order bits of the SHA1 of the data obtained in the previous step. -The byte array is padded with random data until its length is divisible by 16 bytes. -An AES key and an initialization vector are computed ( key is the shared key obtained during Key Generation; in MTProto 1.0, x = 0 ):

-
    -
  • msg_key = substr (SHA1 (plaintext), 4, 16);
  • -
  • sha1_a = SHA1 (msg_key + substr (key, x, 32));
  • -
  • sha1_b = SHA1 (substr (key, 32+x, 16) + msg_key + substr (key, 48+x, 16));
  • -
  • sha1_с = SHA1 (substr (key, 64+x, 32) + msg_key);
  • -
  • sha1_d = SHA1 (msg_key + substr (key, 96+x, 32));
  • -
  • aes_key = substr (sha1_a, 0, 8) + substr (sha1_b, 8, 12) + substr (sha1_c, 4, 12);
  • -
  • aes_iv = substr (sha1_a, 8, 12) + substr (sha1_b, 0, 8) + substr (sha1_c, 16, 4) + substr (sha1_d, 0, 8);
  • -
-

Data is encrypted with a 256-bit key, aes_key, and a 256-bit initialization vector, aes-iv, using AES-256 encryption with infinite garble extension (IGE). Encryption key fingerprint key_fingerprint and the message key msg_key are added at the top of the resulting byte array.

-

Encrypted data is embedded into a messages.sendEncrypted API call and passed to Telegram server for delivery to the other party of the Secret Chat.

-

Decrypting an Incoming Message

-

The steps above are performed in reverse order. -When an encrypted message is received, you must check that msg_key is in fact equal to the 128 low-order bits of the SHA1 hash of the decrypted message. -If the message layer is greater than the one supported by the client, the user must be notified that the client version is out of date and prompted to update.

-

Sequence numbers

-

It is necessary to interpret all messages in their original order to protect against possible manipulations. Secret chats support a special mechanism for handling seq_no counters independently from the server.

-
-

Proper handling of these counters is further described in this article: Sequence numbers in Secret Chats.

-
-

Please note that your client must support sequence numbers in Secret Chats to be compatible with official Telegram clients.

-

Sending Encrypted Files

-

All files sent to secret chats are encrypted with one-time keys that are in no way related to the chat’s shared key. Before an encrypted file is sent, it is assumed that the encrypted file’s address will be attached to the outside of an encrypted message using the file parameter of the messages.sendEncryptedFile method and that the key for direct decryption will be sent in the body of the message (the key parameter in the constructors decryptedMessageMediaPhoto, decryptedMessageMediaVideo and decryptedMessageMediaFile.

-

Prior to a file being sent to a secret chat, 2 random 256-bit numbers are computed which will serve as the AES key and initialization vector used to encrypt the file. AES-256 encryption with infinite garble extension (IGE) is used in like manner.

-

The key fingerprint is computed as follows:

-
    -
  • digest = md5(key + iv)
  • -
  • fingerprint = substr(digest, 0, 4) XOR substr(digest, 4, 4)
  • -
-

The encrypted contents of a file are stored on the server in much the same way as those of a file in cloud chats: piece by piece using calls to upload.saveFilePart. -A subsequent call to messages.sendEncryptedFile will assign an identifier to the stored file and send the address together with the message. The recipient will receive an update with encryptedMessage, and the file parameter will contain file information.

-

Incoming and outgoing encrypted files can be forwarded to other secret chats using the constructor inputEncryptedFile to avoid saving the same content on the server twice.

-

Working with an Update Box

-

Secret chats are associated with specific devices (or rather with authorization keys), not users. A conventional message box, which uses pts to describe the client’s status, is not suitable, because it is designed for long-term message storage and message access from different devices.

-

An additional temporary message queue is introduced as a solution to this problem. When an update regarding a message from a secret chat is sent, a new value of qts is sent, which helps reconstruct the difference if there has been a long break in the connection or in case of loss of an update.

-

As the number of events increases, the value of qts increases monotonically (not always by 1). The initial value may not (and will not) be equal to 0.

-

The fact that events from the temporary queue have been received and stored by the client is acknowledged explicitly by a call to the messages.receivedQueue method or implicitly by a call to updates.getDifference (the value of qts passed, not the final state). All messages acknowledged as delivered by the client, as well as any messages older than 7 days, may (and will) be deleted from the server.

-

Upon de-authorization, the event queue of the corresponding device will be forcibly cleared, and the value of qts will become irrelevant.

-

Updating to new layers

-

Your client should always store the maximal layer that is known to be supported by the client on the other side of a secret chat. When the secret chat is first created, this value should be initialized to 8, the first layer where Secret Chats became available. This remote layer value must always be updated immediately after receiving any packet containing information of an upper layer, i.e.:

-
    -
  • any secret chat message containing layer_no in its decryptedMessageLayer with layer>=17, or
  • -
  • a decryptedMessageActionNotifyLayer service message, wrapped as if it were the decryptedMessageService constructor of the obsolete layer 8 (constructor decryptedMessageService#aa48327d).
  • -
-

Notifying the remote client about your local layer

-

In order to notify the remote client of your local layer, your client must send a message of the decryptedMessageActionNotifyLayer type. This notification must be wrapped in a constructor of an appropriate layer. For instance, if the remote layer for the chat in question is deemed to be lower than 17, the notification must be wrapped as if it were the decryptedMessageService constructor of the obsolete layer 8 (constructor decryptedMessageService#aa48327d), despite the fact that the decryptedMessageActionNotifyLayer constructor is actually not present in Layer 8.

-

There are three cases when your client must notify the remote client about its local layer:

-
    -
  1. As soon as a new secret chat has been created, immediately after the secret key has been successfully exchanged.
  2. -
  3. Immediately after the remote layer value is updated to layer 17 or higher. An exception to this case is when the secret chat in question has been created less than 15 seconds ago. In this case the notification was already sent (see 1).
  4. -
  5. Immediately after the local client has been updated to support a new secret chat layer. In this case notifications must be sent to all currently existing secret chats. Note that this is only necessary when updating to new layers that contain changes in the secret chats implementation (e.g. you don’t need to do this when your client is updated from Layer 17 to Layer 18).
  6. -
-
-

Note that all pending obsolete layer messages must be sent prior to the layer update notification (more on this in Handling Sequence numbers).

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/entities.html b/data/core.telegram.org/api/entities.html deleted file mode 100644 index 5229175237..0000000000 --- a/data/core.telegram.org/api/entities.html +++ /dev/null @@ -1,137 +0,0 @@ - - - - - Styled text with message entities - - - - - - - - - - - - - -
- -
-
-
- -

Styled text with message entities

- -

Telegram supports styled text using message entities.

-

A client that wants to send styled messages would simply have to integrate a Markdown/HTML parser, and generate an array of message entities by iterating through the parsed tags.

-

Special care must be taken to consider the UTF-8 length of strings when generating message entities, see example implementations: tdlib, MadelineProto.

-

Nested entities are supported.
-For example the following HTML/Markdown aliases for message entities can be used:

- -
-```c++
-code
-```
-
-

The following entities can also be used to mention users:

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/errors.html b/data/core.telegram.org/api/errors.html deleted file mode 100644 index f195781ddd..0000000000 --- a/data/core.telegram.org/api/errors.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - Error handling - - - - - - - - - - - - - -
- -
-
-
- -

Error handling

- -

There will be errors when working with the API, and they must be correctly handled on the client.

-

An error is characterized by several parameters:

-

Error Code

-

Numerical value similar to HTTP status. Contains information on the type of error that occurred: for example, a data input error, privacy error, or server error. This is a required parameter.

-

Error Type

-

A string literal in the form of /[A-Z_0-9]+/, which summarizes the problem. For example, AUTH_KEY_UNREGISTERED. This is an optional parameter.

-
-

Error Constructors

-

There should be a way to handle errors that are returned in rpc_error constructors.

-

Below is a list of error codes and their meanings:

-

303 SEE_OTHER

-

The request must be repeated, but directed to a different data center.

-

Examples of Errors:

-
    -
  • FILE_MIGRATE_X: the file to be accessed is currently stored in a different data center.
  • -
  • PHONE_MIGRATE_X: the phone number a user is trying to use for authorization is associated with a different data center.
  • -
  • NETWORK_MIGRATE_X: the source IP address is associated with a different data center (for registration)
  • -
  • USER_MIGRATE_X: the user whose identity is being used to execute queries is associated with a different data center (for registration)
  • -
-

In all these cases, the error description’s string literal contains the number of the data center (instead of the X) to which the repeated query must be sent. -More information about redirects between data centers »

-

400 BAD_REQUEST

-

The query contains errors. In the event that a request was created using a form and contains user generated data, the user should be notified that the data must be corrected before the query is repeated.

-

Examples of Errors:

-
    -
  • FIRSTNAME_INVALID: The first name is invalid
  • -
  • LASTNAME_INVALID: The last name is invalid
  • -
  • PHONE_NUMBER_INVALID: The phone number is invalid
  • -
  • PHONE_CODE_HASH_EMPTY: phone_code_hash is missing
  • -
  • PHONE_CODE_EMPTY: phone_code is missing
  • -
  • PHONE_CODE_EXPIRED: The confirmation code has expired
  • -
  • API_ID_INVALID: The api_id/api_hash combination is invalid
  • -
  • PHONE_NUMBER_OCCUPIED: The phone number is already in use
  • -
  • PHONE_NUMBER_UNOCCUPIED: The phone number is not yet being used
  • -
  • USERS_TOO_FEW: Not enough users (to create a chat, for example)
  • -
  • USERS_TOO_MUCH: The maximum number of users has been exceeded (to create a chat, for example)
  • -
  • TYPE_CONSTRUCTOR_INVALID: The type constructor is invalid
  • -
  • FILE_PART_INVALID: The file part number is invalid
  • -
  • FILE_PARTS_INVALID: The number of file parts is invalid
  • -
  • FILE_PART_Х_MISSING: Part X (where X is a number) of the file is missing from storage
  • -
  • MD5_CHECKSUM_INVALID: The MD5 checksums do not match
  • -
  • PHOTO_INVALID_DIMENSIONS: The photo dimensions are invalid
  • -
  • FIELD_NAME_INVALID: The field with the name FIELD_NAME is invalid
  • -
  • FIELD_NAME_EMPTY: The field with the name FIELD_NAME is missing
  • -
  • MSG_WAIT_FAILED: A request that must be completed before processing the current request returned an error
  • -
  • MSG_WAIT_TIMEOUT: A request that must be completed before processing the current request didn't finish processing yet
  • -
-

401 UNAUTHORIZED

-

There was an unauthorized attempt to use functionality available only to authorized users.

-

Examples of Errors:

-
    -
  • AUTH_KEY_UNREGISTERED: The key is not registered in the system
  • -
  • AUTH_KEY_INVALID: The key is invalid
  • -
  • USER_DEACTIVATED: The user has been deleted/deactivated
  • -
  • SESSION_REVOKED: The authorization has been invalidated, because of the user terminating all sessions
  • -
  • SESSION_EXPIRED: The authorization has expired
  • -
  • AUTH_KEY_PERM_EMPTY: The method is unavailble for temporary authorization key, not bound to permanent
  • -
-

403 FORBIDDEN

-

Privacy violation. For example, an attempt to write a message to someone who has blacklisted the current user.

-

404 NOT_FOUND

-

An attempt to invoke a non-existent object, such as a method.

-

406 NOT_ACCEPTABLE

-

Similar to 400 BAD_REQUEST, but the app should not display any error messages to user in UI as a result of this response. The error message will be delivered via updateServiceNotification instead.

-

420 FLOOD

-

The maximum allowed number of attempts to invoke the given method with the given input parameters has been exceeded. For example, in an attempt to request a large number of text messages (SMS) for the same phone number.

-

Error Example:

-
    -
  • FLOOD_WAIT_X: A wait of X seconds is required (where X is a number)
  • -
-

500 INTERNAL

-

An internal server error occurred while a request was being processed; for example, there was a disruption while accessing a database or file storage.

-

If a client receives a 500 error, or you believe this error should not have occurred, please collect as much information as possible about the query and error and send it to the developers.

-

Other Error Codes

-

If a server returns an error with a code other than the ones listed above, it may be considered the same as a 500 error and treated as an internal server error.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/file_reference.html b/data/core.telegram.org/api/file_reference.html deleted file mode 100644 index 96f184d1dc..0000000000 --- a/data/core.telegram.org/api/file_reference.html +++ /dev/null @@ -1,125 +0,0 @@ - - - - - File references - - - - - - - - - - - - - -
- -
-
-
- -

File references

- -

File references are strings of bytes, that can be encountered in the file_reference fields of document and photo objects.

-

They must be cached by the client, along with the origin context where the document/photo object was found, in order to be refetched when the file reference expires.

-

Example implementation of a reference database: MadelineProto, android, telegram desktop, tdlib.

-

Another example:

-

Assume you receive a message from your friend: that message contains a messageMediaPhoto with a photo.

-

Your client has to cache not only the file_reference field of the photo, but also the context in which the file reference was seen (in this case, a message coming from a specific user).

-

The context info is in this case, an origin context of type message, containing the message ID and the peer ID of the chat/channel/user where the message was seen.

-

The context info has to be associated with the file reference: when downloading a file using upload.getFile, a FILE_REFERENCE_EXPIRED error (or another error starting with FILE_REFERENCE_) may be returned.
-If this happens, the context info must be used to refetch the object that contained the file reference: in this example, the peer info and the message ID have to be used with channels.getMessages or messages.getMessages to refetch the message, recache the file reference and use it in a new file download request.

-

More than one origin context can be associated to one file reference, for greater resilience (in the case of a message that was deleted in one chat but was also forwarded in another chat, the file reference can be refetched from the second chat, instead).

-

Origin contexts for objects returned by method calls with certain parameters can be considered, too (for example, in the case of favorited sticker sets returned by messages.getFavedStickers).

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/files.html b/data/core.telegram.org/api/files.html deleted file mode 100644 index 3747d36865..0000000000 --- a/data/core.telegram.org/api/files.html +++ /dev/null @@ -1,568 +0,0 @@ - - - - - Uploading and Downloading Files - - - - - - - - - - - - - -
- -
-
-
- -

Uploading and Downloading Files

- -
- -

When working with the API, it is sometimes necessary to send a relatively large file to the server. For example, when sending a message with a photo/video attachment or when setting the current user’s profile picture.

-

Uploading files

-

There are a number of API methods to save files. The schema of the types and methods used is presented below:

-
inputFile#f52ff27f id:long parts:int name:string md5_checksum:string = InputFile;
-inputFileBig#fa4f0bb5 id:long parts:int name:string = InputFile;
-
-
-inputEncryptedFileUploaded#64bd0306 id:long parts:int md5_checksum:string key_fingerprint:int = InputEncryptedFile;
-inputEncryptedFileBigUploaded#2dc173c8 id:long parts:int key_fingerprint:int = InputEncryptedFile;
-
-inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;
-inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;
-
-inputMediaUploadedPhoto#1e287d04 flags:# file:InputFile stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
-inputMediaUploadedDocument#5b38c6c1 flags:# nosound_video:flags.3?true force_file:flags.4?true file:InputFile thumb:flags.2?InputFile mime_type:string attributes:Vector<DocumentAttribute> stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
-
-inputChatUploadedPhoto#c642724e flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = InputChatPhoto;
-
-
----functions---
-
-messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-messages.uploadMedia#519bc2b1 peer:InputPeer media:InputMedia = MessageMedia;
-messages.sendEncryptedFile#5559481d flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes file:InputEncryptedFile = messages.SentEncryptedMessage;
-
-photos.uploadProfilePhoto#89f30f69 flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = photos.Photo;    
-
-upload.saveFilePart#b304a621 file_id:long file_part:int bytes:bytes = Bool;
-upload.saveBigFilePart#de7b673d file_id:long file_part:int file_total_parts:int bytes:bytes = Bool;
-

Before transmitting the contents of the file itself, the file has to be assigned a unique 64-bit client identifier: file_id.

-

The file’s binary content is then split into parts. All parts must have the same size ( part_size ) and the following conditions must be met:

-
    -
  • part_size % 1024 = 0 (divisible by 1KB)
  • -
  • 524288 % part_size = 0 (512KB must be evenly divisible by part_size)
  • -
-

The last part does not have to satisfy these conditions, provided its size is less than part_size.

-

Each part should have a sequence number, file_part, with a value ranging from 0 to 2,999.

-

After the file has been partitioned you need to choose a method for saving it on the server. Use upload.saveBigFilePart in case the full size of the file is more than 10 MB and upload.saveFilePart for smaller files.

-

Each call saves a portion of the data in a temporary location on the server to be used later. The storage life of each portion of data is between several minutes and several hours (depending on how busy the storage area is). After this time, the file part will become unavailable. To increase the time efficiency of a file save operation, we recommend using a call queue, so X pieces of the file are being saved at any given moment in time. Each successful operation to save a part invokes the method call to save the next part. The value of X can be tuned to achieve maximum performance.

-

When using one of the methods mentioned above to save file parts, one of the following data input errors may be returned:

-
    -
  • FILE_PARTS_INVALID - Invalid number of parts. The value is not between 1..3000
  • -
  • FILE_PART_INVALID: The file part number is invalid. The value is not between 0 and 2,999.
  • -
  • FILE_PART_TOO_BIG: The size limit (512 KB) for the content of the file part has been exceeded
  • -
  • FILE_PART_EMPTY: The file part sent is empty
  • -
  • FILE_PART_SIZE_INVALID - 512KB cannot be evenly divided by part_size
  • -
  • FILE_PART_SIZE_CHANGED - The part size is different from the size of one of the previous parts in the same file
  • -
-

While the parts are being uploaded, an MD5 hash of the file contents can also be computed to be used later as the md5_checksum parameter in the inputFile constructor (since it is checked only by the server, for encrypted secret chat files it must be generated from the encrypted file). -After the entire file is successfully saved, the final method may be called and passed the generated inputFile object. In case the upload.saveBigFilePart method is used, the inputFileBig constructor must be passed, in other cases use inputFile.

- -

The file save operation may return one of the following data input errors:

-
    -
  • FILE_PARTS_INVALID: The number of file parts is invalid The value is not between 1 and 3,000.
  • -
  • FILE_PART_Х_MISSING: Part X (where X is a number) of the file is missing from storage. Try repeating the method call to resave the part.
  • -
  • MD5_CHECKSUM_INVALID: The file’s checksum did not match the md5_checksum parameter
  • -
-

Albums, grouped media

-
inputMediaUploadedPhoto#1e287d04 flags:# file:InputFile stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
-inputMediaUploadedDocument#5b38c6c1 flags:# nosound_video:flags.3?true force_file:flags.4?true file:InputFile thumb:flags.2?InputFile mime_type:string attributes:Vector<DocumentAttribute> stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
-
-inputSingleMedia#1cc6e91f flags:# media:InputMedia random_id:long message:string entities:flags.0?Vector<MessageEntity> = InputSingleMedia;
-
----functions---
-
-messages.sendMultiMedia#cc0110cb flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int multi_media:Vector<InputSingleMedia> schedule_date:flags.10?int = Updates;
-

Telegram allows grouping photos into albums and generic files (audio, docuemnts) into media groups.

-

To do this, messages.sendMultiMedia is used, wrapping each InputMedia constructor (uploaded or pre-existing, maximum 10 per media group) into an inputSingleMedia constructor, optionally providing a custom per-file caption in message.

-

For photo albums, clients should display an album caption only if exactly one photo in the group has a caption, otherwise no album caption should be displayed, and only when viewing in detail a specific photo of the group the caption should be shown.
-Other grouped media can display a caption under each file.

-

Re-using pre-uploaded files

-
document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
-
----functions---
-
-messages.getDocumentByHash#338e2464 sha256:bytes size:int mime_type:string = Document;
-

For some types of documents like GIFs, messages.getDocumentByHash can be used to search for the document on Telegram servers. -The SHA256 hash of the file is computed, and it is passed along with the file's mime type and size to the method: if the file type is correct and the file is found, a document is returned.

-

Uploading profile or chat pictures

-
photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;
-
-photos.photo#20212ca8 photo:Photo users:Vector<User> = photos.Photo;
-
-inputPhoto#3bb3b94a id:long access_hash:long file_reference:bytes = InputPhoto;
-
-inputFile#f52ff27f id:long parts:int name:string md5_checksum:string = InputFile;
-
-inputChatUploadedPhoto#c642724e flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = InputChatPhoto;
-inputChatPhoto#8953ad37 id:InputPhoto = InputChatPhoto;
-
----functions---
-
-photos.updateProfilePhoto#72d4742c id:InputPhoto = photos.Photo;
-photos.uploadProfilePhoto#89f30f69 flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = photos.Photo;
-
-messages.editChatPhoto#35ddd674 chat_id:long photo:InputChatPhoto = Updates;
-
-channels.editPhoto#f12e57c9 channel:InputChannel photo:InputChatPhoto = Updates;
-

User profile pictures can be uploaded using the photos.uploadProfilePhoto method: the actual profile picture has to be uploaded as for normal files.
-photos.uploadProfilePhoto can also be used to reupload previously uploaded profile pictures.

-

Animated profile pictures

-

Animated profile pictures are also supported, by populating the video constructor: square MPEG4 videos up to 1080x1080 are supported, 800x800 is the recommended resolution.
-The video_start_ts is a floating point UNIX timestamp in seconds, indicating the frame of the video that should be used as static preview.

-

Chat, channel and supergroup profile photos and videos can be uploaded using messages.editChatPhoto (legacy groups) or channels.editPhoto (channels, supergroups).
-Use the inputChatPhoto to reuse previously uploaded profile pictures.

-

Downloading files

-

There are methods available to download files which have been successfully uploaded. The schema of the types and methods used is presented below:

-
upload.file#96a18d5 type:storage.FileType mtime:int bytes:bytes = upload.File;
-upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;
-
-storage.fileUnknown#aa963b05 = storage.FileType;
-storage.fileJpeg#7efe0e = storage.FileType;
-storage.fileGif#cae1aadf = storage.FileType;
-storage.filePng#a4f63c0 = storage.FileType;
-storage.fileMp3#528a0677 = storage.FileType;
-storage.fileMov#4b09ebbc = storage.FileType;
-storage.filePartial#40bc6f52 = storage.FileType;
-storage.fileMp4#b3cea0e4 = storage.FileType;
-storage.fileWebp#1081464c = storage.FileType;
-
----functions---
-
-upload.getFile#b15a9afc flags:# precise:flags.0?true cdn_supported:flags.1?true location:InputFileLocation offset:int limit:int = upload.File;
-

Any file can be downloaded by calling upload.getFile. -The data for the input parameter of the InputFileLocation type is generated as follows:

-
inputFileLocation#dfdaabe1 volume_id:long local_id:int secret:long file_reference:bytes = InputFileLocation;
-inputEncryptedFileLocation#f5235d55 id:long access_hash:long = InputFileLocation;
-inputDocumentFileLocation#bad07584 id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;
-inputSecureFileLocation#cbc7ee28 id:long access_hash:long = InputFileLocation;
-inputTakeoutFileLocation#29be5899 = InputFileLocation;
-inputPhotoFileLocation#40181ffe id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;
-inputPhotoLegacyFileLocation#d83466f3 id:long access_hash:long file_reference:bytes volume_id:long local_id:int secret:long = InputFileLocation;
-inputPeerPhotoFileLocation#37257e99 flags:# big:flags.0?true peer:InputPeer photo_id:long = InputFileLocation;
-inputStickerSetThumb#9d84f3db stickerset:InputStickerSet thumb_version:int = InputFileLocation;
-inputGroupCallStream#598a92a flags:# call:InputGroupCall time_ms:long scale:int video_channel:flags.0?int video_quality:flags.0?int = InputFileLocation;
-
-inputStickerSetEmpty#ffb62b95 = InputStickerSet;
-inputStickerSetID#9de7a269 id:long access_hash:long = InputStickerSet;
-inputStickerSetShortName#861cc8a0 short_name:string = InputStickerSet;
-inputStickerSetAnimatedEmoji#28703c8 = InputStickerSet;
-inputStickerSetDice#e67f520e emoticon:string = InputStickerSet;
-inputStickerSetAnimatedEmojiAnimations#cde3739 = InputStickerSet;
-
-inputPeerSelf#7da07ec9 = InputPeer;
-inputPeerChat#35a95cb9 chat_id:long = InputPeer;
-inputPeerUser#dde8a54c user_id:long access_hash:long = InputPeer;
-inputPeerChannel#27bcbbfc channel_id:long access_hash:long = InputPeer;
-
-photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;
-document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
-
-photoSize#75c78e60 type:string w:int h:int size:int = PhotoSize;
-photoCachedSize#21e1ad6 type:string w:int h:int bytes:bytes = PhotoSize;
-
-chatPhoto#1c6e1c11 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = ChatPhoto;
-userProfilePhoto#82d1f706 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = UserProfilePhoto;
-
    -
  • -

    For photos, inputPhotoFileLocation is used:

    -
      -
    • id, file_reference and access_hash taken from the photo constructor
    • -
    • thumb_size taken from the type field of the desired PhotoSize of the photo
    • -
    -
  • -
  • -

    For profile pictures of users, channels, supergroups and groups, inputPeerPhotoFileLocation has to be used:

    -
      -
    • peer is the identifier of the peer whose photo we want to download
    • -
    • big is used to choose whether to download the full-resolution picture, or just the thumbnail
    • -
    • photo_id is extracted from the chatPhoto or userProfilePhoto of the desired profile photo
    • -
    -
  • -
  • -

    For documents, inputDocumentFileLocation is used:

    -
      -
    • id, file_reference and access_hash taken from the document constructor
    • -
    • If downloading the thumbnail of a document, thumb_size should be taken from the type field of the desired PhotoSize of the photo; otherwise, provide an empty string.
    • -
    -
  • -
  • -

    For previews of sticker sets, inputStickerSetThumb is used (note: to download stickers and previews of stickers use the document method described above for documents):

    - -
  • -
  • -

    For encrypted secret chat and telegram passport documents, respectively inputEncryptedFileLocation and inputSecureFileLocation have to be used, with parameters extracted from encryptedFile and secureFile (passport docs).

    -
  • -
  • -

    For livestream chunks, inputGroupCallStream is used:

    -
      -
    • call contains the related group call ID+access hash, taken from the groupCall constructor.
    • -
    • time_ms specifies the timestamp to fetch
    • -
    • scale specifies the duration of the video segment to fetch in milliseconds, by bitshifting 1000 to the right scale times: duration_ms := 1000 >> scale
    • -
    • video_channel specifies the video channel to fetch
    • -
    • video_quality specifies the selected video quality (0 = lowest, 1 = medium, 2 = best)
    • -
    -
  • -
  • -

    For old deprecated photos, if the client has cached some old fileLocations with the deprecated secret identifier, inputFileLocation or inputPhotoLegacyFileLocation is used (this is mainly used for backwards compatiblity with bot API file IDs, all user clients must use the modern inputPhotoFileLocation file IDs):

    -
      -
    • All fields are taken from the previously cached fileLocation except for file_reference, access_hash and id, which are taken from the photo constructor (the last two fields are used only if available, in which case inputPhotoLegacyFileLocation is used instead of inputFileLocation).
    • -
    -
  • -
-

The size of each file in bytes is available, which makes it possible to download the file in parts using the parameters offset and limit, similar to the way files are uploaded.

-

If precise flag is not specified, then

-
    -
  • The parameter offset must be divisible by 4 KB.
  • -
  • The parameter limit must be divisible by 4 KB.
  • -
  • 1048576 (1 MB) must be divisible by limit.
  • -
-

If precise is specified, then

-
    -
  • The parameter offset must be divisible by 1 KB.
  • -
  • The parameter limit must be divisible by 1 KB.
  • -
  • limit must not exceed 1048576 (1 MB).
  • -
-

In any case the requested part should be within one 1 MB chunk from the beginning of the file, i. e.

-
    -
  • offset / (1024 * 1024) == (offset + limit - 1) / (1024 * 1024).
  • -
-

The file download operation may return a FILE_REFERENCE_EXPIRED error (or another error starting with FILE_REFERENCE_): in this case, the file_reference field of the input location must be refreshed. -The file download operation may return an upload.fileCdnRedirect constructor: in this case, these instructions must be followed for downloading CDN files. -The file download operation may also return one of the following data input errors:

-
    -
  • FILE_ID_INVALID: The file address is invalid
  • -
  • OFFSET_INVALID: The offset value is invalid
  • -
  • LIMIT_INVALID: The limit value is invalid
  • -
  • FILE_MIGRATE_X: The file is in the datacenter No. X
  • -
-

Verifying downloaded chunks

-
fileHash#6242c773 offset:int limit:int hash:bytes = FileHash;
-
----functions---
-
-upload.getFileHashes#c7025931 location:InputFileLocation offset:int = Vector<FileHash>;
-

In order to confirm the integrity of the downloaded file, clients are recommended to verify hashes for each downloaded part, as for CDN DCs. -upload.getFileHashes contain FileHash constructors. Each of these constructors contains the SHA-256 hash of a part of the file that starts with offset and takes limit bytes.

-

Before saving each portion of the data received from the DC into the file, the client can confirm that its hash matches the hash that was received from the master DC. If missing a hash for any file part, client developers must use the upload.getFileHashes method to obtain the missing hash.

-

Handling audio, video and vector previews

-

Schema:

-
photoSizeEmpty#e17e23c type:string = PhotoSize;
-photoSize#75c78e60 type:string w:int h:int size:int = PhotoSize;
-photoCachedSize#21e1ad6 type:string w:int h:int bytes:bytes = PhotoSize;
-photoStrippedSize#e0b0bc2e type:string bytes:bytes = PhotoSize;
-photoSizeProgressive#fa3efb95 type:string w:int h:int sizes:Vector<int> = PhotoSize;
-photoPathSize#d8214d41 type:string bytes:bytes = PhotoSize;
-
-videoSize#de33b094 flags:# type:string w:int h:int size:int video_start_ts:flags.0?double = VideoSize;
-
-document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
-photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;
-
-photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;
-

Telegram attaches a vector of thumbnails with reduced resolution to all uploaded media.
-The server also generates a trimmed and scaled down video preview for videos, GIFs and animated profile pictures.

-

Image thumbnail types

-

Each photo preview has a specific type, indicating the resolution and image transform that was applied server-side.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TypeImage filterSize
sbox100x100
mbox320x320
xbox800x800
ybox1280x1280
wbox2560x2560
acrop160x160
bcrop320x320
ccrop640x640
dcrop1280x1280
-

Special types:

- - - - - - - - - - - - - - - - - -
TypeImage filter
istrip
joutline
-

Stripped thumbnails

-
photoStrippedSize#e0b0bc2e type:string bytes:bytes = PhotoSize;
-

A photoStrippedSize (with type i) is an extremely low-res thumbnail, embedded directly inside media location objects.
-It should be shown to the user in chat message previews, or while still downloading the most appropriately sized photoSize through the media DCs as described above.

-

The stripped bytes payload should be inflated to a JPG payload as seen here ».

-

Vector thumbnails

-
photoPathSize#d8214d41 type:string bytes:bytes = PhotoSize;
-

Messages with animated stickers can have a compressed svg (< 300 bytes) to show the outline of the sticker before fetching the actual lottie animation. -Animated sticker outlines will have a j type photoPathSize thumbnail.

-

This specific vector thumbnail consists in an SVG path, specially encoded to save space.
-This path will be the outline of the animated sticker, and should be shown to the user while downloading the actual sticker.

-

As for stripped sizes, the payload should be inflated using the following algorithm:

-
encoded := photoPathSize.bytes
-
-lookup := "AACAAAAHAAALMAAAQASTAVAAAZaacaaaahaaalmaaaqastava.az0123456789-,"
-
-path := "M"
-
-len := strlen(encoded)
-for (i = 0; i < len; i++) {
-  num := ord(encoded[i])
-  if (num >= 128 + 64) {
-    path += lookup[num - 128 - 64]
-  } else {
-    if (num >= 128) {
-      path += ','
-    } else if (num >= 64) {
-      path += '-'
-    }
-    path += itoa(num & 63)
-  }
-}
-path += "z"
-

path will contain the actual SVG path that can be directly inserted in the d attribute of an svg <path> element:

-
<?xml version="1.0" encoding="utf-8"?>
-<svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"
-   viewBox="0 0 512 512" xml:space="preserve">
-<path d="{$path}"/>
-</svg>
-

Video types

-
videoSize#de33b094 flags:# type:string w:int h:int size:int video_start_ts:flags.0?double = VideoSize;
-

A videoSize constructor is typically used for animated profile pictures and video previews.

- - - - - - - - - - - - - - - - - - - - -
TypeDescriptionFormat
uAnimated profile pictureMPEG4
vVideo previewMPEG4
-

Downloading webfiles

-

Remote HTTP files sent by inline bots in response to inline queries and in other places are represented by WebDocument constructors. -When forwarding such remote HTTP files, they should be sent using external InputMedia constructors. -Remote HTTP files can only be downloaded directly by the client if contained in a webDocumentNoProxy constructor: in this case, the file is deemed safe to download (this is the case for HTTPS files from certain trusted domains).

-

However, if the remote file is contained in a webDocument, to avoid leaking sensitive information the file must be downloaded through telegram's servers. -This can be done in a manner similar to normal files, with the difference that upload.getWebFile must be used, instead.

-
upload.webFile#21e753bc size:int mime_type:string file_type:storage.FileType mtime:int bytes:bytes = upload.WebFile;
-
-storage.fileUnknown#aa963b05 = storage.FileType;
-storage.fileJpeg#7efe0e = storage.FileType;
-storage.fileGif#cae1aadf = storage.FileType;
-storage.filePng#a4f63c0 = storage.FileType;
-storage.fileMp3#528a0677 = storage.FileType;
-storage.fileMov#4b09ebbc = storage.FileType;
-storage.filePartial#40bc6f52 = storage.FileType;
-storage.fileMp4#b3cea0e4 = storage.FileType;
-storage.fileWebp#1081464c = storage.FileType;
-
- ---functions---
-
-upload.getWebFile#24e6818d location:InputWebFileLocation offset:int limit:int = upload.WebFile;
-

The InputWebFileLocation constructor is generated as follows.

-
inputWebFileLocation#c239d686 url:string access_hash:long = InputWebFileLocation;
-inputWebFileGeoPointLocation#9f2221c9 geo_point:InputGeoPoint access_hash:long w:int h:int zoom:int scale:int = InputWebFileLocation;
-
-webDocument#1c570ed1 url:string access_hash:long size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;
-
-inputGeoPoint#48222faf flags:# lat:double long:double accuracy_radius:flags.0?int = InputGeoPoint;
-
-geoPoint#b2a2f663 flags:# long:double lat:double access_hash:long accuracy_radius:flags.0?int = GeoPoint;
-
    -
  • inputWebFileLocation is simply generated by taking the url and access_hash fields of the webDocument constructor.
  • -
  • inputWebFileGeoPointLocation is used to download a server-generated image with the map preview from a geoPoint.
      -
    • geo_point is generated from the lat, long accuracy_radius parameters of the geoPoint
    • -
    • access_hash is the access hash of the geoPoint
    • -
    • w - Map width in pixels before applying scale; 16-1024
    • -
    • h - Map height in pixels before applying scale; 16-1024
    • -
    • zoom - Map zoom level; 13-20
    • -
    • scale - Map scale; 1-3
    • -
    -
  • -
-

General Considerations

-

It is recommended that large queries (upload.getFile, upload.saveFilePart, upload.getWebFile) be handled through a separate session and a separate connection, in which no methods other than these should be executed. If this is done, then data transfer will cause less interference with getting updates and other method calls.

-

Related articles

-

Handling file references

-

How to handle file references.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/folders.html b/data/core.telegram.org/api/folders.html deleted file mode 100644 index e53ea25ae5..0000000000 --- a/data/core.telegram.org/api/folders.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - Folders - - - - - - - - - - - - - -
- -
-
-
- -

Folders

- -
- -

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.
-In the API, folders are called "dialog filters"; in the UI, they are typically represented as tabs.

-

Schema:

-
dialogFilter#7438f7e8 flags:# contacts:flags.0?true non_contacts:flags.1?true groups:flags.2?true broadcasts:flags.3?true bots:flags.4?true exclude_muted:flags.11?true exclude_read:flags.12?true exclude_archived:flags.13?true id:int title:string emoticon:flags.25?string pinned_peers:Vector<InputPeer> include_peers:Vector<InputPeer> exclude_peers:Vector<InputPeer> = DialogFilter;
-
-dialogFilterSuggested#77744d4a filter:DialogFilter description:string = DialogFilterSuggested;
-
-updateDialogFilter#26ffde7d flags:# id:int filter:flags.0?DialogFilter = Update;
-updateDialogFilterOrder#a5d72105 order:Vector<int> = Update;
-updateDialogFilters#3504914f = Update;
-
----functions---
-
-messages.getDialogFilters#f19ed96d = Vector<DialogFilter>;
-messages.getSuggestedDialogFilters#a29cd42c = Vector<DialogFilterSuggested>;
-messages.updateDialogFilter#1ad4a04a flags:# id:int filter:flags.0?DialogFilter = Bool;
-messages.updateDialogFiltersOrder#c563c1e4 order:Vector<int> = Bool;
-
-help.getAppConfig#98914110 = JSONValue;
-

Folders

-

On startup, clients call:

- -

The boolean under the dialog_filters_tooltip JSON key in the result of help.getAppConfig can be used to determine whether a folder tooltip should be presented to the user right away.
-The UI should then show a list of suggested folder combinations.

-

Once configuration is finished, apps call messages.updateDialogFilter to create or update existing folders.
-As per the dialogFilter constructor, folders have multiple flags that can be combined to determine which chats should be included in (or excluded from) the folder.
-Folders can also have unlimited pinned chats, as determined by the pinned_peers field.

-

To reorder existing folders, messages.updateDialogFiltersOrder should be used with the IDs of the various dialog filters.

-

To delete folders, use messages.updateDialogFilter without populating the filter flag field.

-

Clients can receive updateDialogFilter, updateDialogFilterOrder updates with new filter information, generated by other clients when modifying folder info.
-Clients can also receive updateDialogFilters, in which case folder info should be refetched manually using messages.getDialogFilters.

-

Peer folders

-

The API also has another method for identifying groups of peers, typically used only by archived chats.

-

Schema:

-
inputDialogPeer#fcaafeb7 peer:InputPeer = InputDialogPeer;
-inputDialogPeerFolder#64600527 folder_id:int = InputDialogPeer;
-
-dialogPeer#e56dbf05 peer:Peer = DialogPeer;
-dialogPeerFolder#514519e2 folder_id:int = DialogPeer;
-
-updateFolderPeers#19360dc0 folder_peers:Vector<FolderPeer> pts:int pts_count:int = Update;
-
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-
----functions---
-
-folders.editPeerFolders#6847d0ab folder_peers:Vector<InputFolderPeer> = Updates;
-folders.deleteFolder#1c295881 folder_id:int = Updates;
-

API peer folders are typically used only by archived chats, and are really handy for distinguishing groups of peers, since most peer-related constructors (updates, chat info) will contain the folder_id assigned the the specified chat.

-

In Telegram apps, API peer folders are used only to implement the chat archive, identified by folder_id 1; all other peers are in folder_id 0 by default; no other folder_id is allowed at the moment.

-
    -
  • folders.editPeerFolders can be used to add and remove peers from peer folders.
  • -
  • folders.deleteFolder can be used to delete peer folders, moving all peers previously present in that folder to the default 0 folder.
  • -
-

Both methods return an updates constructor, containing a single updateFolderPeers with the new folder_id of moved peers.
-Clients can also receive updateFolderPeers as a normal update, generated by other clients when modifying peer folders.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/geochats.html b/data/core.telegram.org/api/geochats.html deleted file mode 100644 index 13d9c08db3..0000000000 --- a/data/core.telegram.org/api/geochats.html +++ /dev/null @@ -1,115 +0,0 @@ - - - - - Nope - - - - - - - - - - - - - -
- -
-
-
- -

Nope

- -

Deprecated old docs. This was definitely not the droid you were looking for.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/import.html b/data/core.telegram.org/api/import.html deleted file mode 100644 index c087e55134..0000000000 --- a/data/core.telegram.org/api/import.html +++ /dev/null @@ -1,173 +0,0 @@ - - - - - Imported messages - - - - - - - - - - - - - -
- -
-
-
- -

Imported messages

- -
- -

Telegram allows importing messages and media from foreign chat apps.

-
-

Note: This article is intended for MTProto API developers. If you're looking for a way to move history from other chat apps into Telegram, check out the related Telegram blog post.

-
-

1. Validate the chat export file

-
messages.historyImportParsed#5e0fb7b9 flags:# pm:flags.0?true group:flags.1?true title:flags.2?string = messages.HistoryImportParsed;
-
----functions---
-
-messages.checkHistoryImport#43fe19f3 import_head:string = messages.HistoryImportParsed;
-

The import process begins by calling messages.checkHistoryImport, passing to import_head up to 100 lines of the chat export file, starting from the beginning of the file.

-

The returned constructor contains information about the exported chat, including its title or type. -If the pm flag is set, the chat export file was generated from a private chat. -If the group flag is set, the chat export file was generated from a group chat. -If neither the pm or group flags are set, the specified chat export was generated from a chat of unknown type.

-

2. Choosing a destination Telegram chat

-
messages.checkedHistoryImportPeer#a24de717 confirm_text:string = messages.CheckedHistoryImportPeer;
-
----functions---
-
-messages.checkHistoryImportPeer#5dc60f03 peer:InputPeer = messages.CheckedHistoryImportPeer;
-

Using messages.checkHistoryImportPeer, check whether chat history exported from another chat app can be imported into a specific Telegram peer, chosen by the user.
-Typically, history imports are allowed for private chats with a mutual contact or supergroups with change_info administrator rights ».

-

If the check succeeds, and no RPC errors are returned, a messages.CheckedHistoryImportPeer constructor will be returned, with a confirmation text to be shown to the user in a confirmation prompt.
-Upon final user confirmation, the import process is initialized.

-

3. Initialize the import

-
messages.historyImport#1662af0b id:long = messages.HistoryImport;
-
----functions---
-
-messages.initHistoryImport#34090c3b peer:InputPeer file:InputFile media_count:int = messages.HistoryImport;
-

Use messages.initHistoryImport to initialize the import process, passing the following parameters:

-
    -
  • peer - The Telegram chat where the history should be imported.
  • -
  • file - The chat export file.
  • -
  • media_count - The number of media files associated with the export, to be uploaded in the next step.
  • -
-

4. Uploading media

-
---functions---
-
-messages.uploadImportedMedia#2a862092 peer:InputPeer import_id:long file_name:string media:InputMedia = MessageMedia;
-

Use messages.uploadImportedMedia to upload media files eventually associated with the chat export.
-import_id is the id contained in the messages.historyImport constructor, returned by messages.initHistoryImport in the previous step.

-

5. Finalize the import

-
message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
-
-messageFwdHeader#5f777dce flags:# imported:flags.7?true from_id:flags.0?Peer from_name:flags.5?string date:int channel_post:flags.2?int post_author:flags.3?string saved_from_peer:flags.4?Peer saved_from_msg_id:flags.4?int psa_type:flags.6?string = MessageFwdHeader;
-
----functions---
-
-messages.startHistoryImport#b43df344 peer:InputPeer import_id:long = Bool;
-

Finally, invoke messages.startHistoryImport to complete the history import process, importing all messages into the chat.
-As usual, import_id is the id contained in the messages.historyImport constructor, returned by messages.initHistoryImport.

-

Imported messages will show in the chat history as messages containing a fwd_from messageFwdHeader constructor with the imported flag, and should be appropriately marked in the UI as messages imported from a foreign chat app.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/invoking.html b/data/core.telegram.org/api/invoking.html deleted file mode 100644 index d49e333bc7..0000000000 --- a/data/core.telegram.org/api/invoking.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - Calling API Methods - - - - - - - - - - - - - -
- -
-
-
- -

Calling API Methods

- -
- -

Layers

-

Versioning in the API is supported by so-called TL layers.

-

The need to add a new object constructor or to add/remove a field in a constructor creates a backwards compatibility problem for previous versions of API clients. After all, simply changing a constructor in a schema also changes its number. To address this problem, each schema update is separated into a layer.

-

A layer is a collection of updated methods or constructors in a TL schema. Each layer is numbered with sequentially increasing numbers starting with 2. The first layer is the base layer -- the TL schema without any changes.

-

There is a helper method to let the API know that a client supports the Layer layer:

-
invokeWithLayer#da9b0d0d {X:Type} layer:int query:!X = X;
-

The helper method invokeWithLayer can be used only together with initConnection: the present layer will be saved with all other parameters of the client and any future requests will be using this saved value. See more below.

-

List of Available Layers

-

Saving Client Info

-

It is possible to save information about the current client on the server in conjunction with an authorization key. This may help eliminate client-side problems with certain releases on certain devices or with certain localizations, as well as eliminate the need for sending layer information in each request.

-

The helper method initConnection accepts client parameters. This method must be called when first calling the API after the application has restarted or in case the value of one of the parameters could have changed.

-

initConnection must also be called after each auth.bindTempAuthKey.

-

When calling this method, the current layer used by the client is also saved (the layer in which initConnection was wrapped is used). After a successful call to initConnection it is no longer necessary to wrap each API call in invokeWithLayerN.

-

Disabling updates

-
invokeWithoutUpdates#bf9459b7 {X:Type} query:!X = X;
-

invokeWithoutUpdates can be used to invoke a request without subscribing the used connection for updates (this is enabled by default for file queries).

-

Sequential Requests

-

By default, the server processes parallel requests in arbitrary order. Two helper methods exist for cases when the client needs certain requests to be processed in a certain order and intends to send a new request before the previous one is completed:

-
-

invokeAfterMsg#cb9f372d {X:Type} msg_id:long query:!X = X;
-invokeAfterMsgs#3dc4b4f0 {X:Type} msg_ids:Vector query:!X = X;

-
-

They may be used, for example, when a client attempts to send messages that accumulated while waiting for the Internet connection to be restored for a long time. In this case, the 32-bit number 0xcb9f372d must be added before the method number in each request, followed by a 64-bit message identifier, msg_id, which contains the previous request in the queue.

-

The second method is similar, except it takes several messages that must be successfully processed before the current one.

-

If the waiting period exceeds 0.5 seconds (this value may change in the future) and no result has appeared, the method will return the 400 MSG_WAIT_TIMEOUT error.

-

Helper Method Sequence

-

Important: if the helper methods invokeAfterMsg / invokeAfterMsgs are used together with invokeWithLayerN or other helper methods, invokeAfterMsg / invokeAfterMsgs must always be the outermost wrapper.

-

Data Compression

-

We recommend using gzip compression when calling methods to reduce the amount of network traffic.

-

The schema and constructor information are given in the protocol documentation.

-

Data Compression when Making a Request

-

Before transmitting a query, the string containing the entire body of the serialized high-level query (starting with the method number) must be compressed using gzip. If the resulting string is smaller than the original, it makes sense to transmit the gzip_packed constructor.

-

There is no point in doing the above when transmitting binary multimedia data (photos, videos) or small messages (up to 255 bytes).

-

Uncompressing Data

-

By default, the server compresses the response to any request as well as updates, in accordance with the rules stated above. If the gzip_packed constructor is received as a response in rpc_result, then the string that follows must be extracted and uncompressed. Processing then continues on the resulting new string.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/live-location.html b/data/core.telegram.org/api/live-location.html deleted file mode 100644 index 088510459a..0000000000 --- a/data/core.telegram.org/api/live-location.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - Live geolocation - - - - - - - - - - - - - -
- -
-
-
- -

Live geolocation

- -
- -

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

-

Sending live locations

-
inputGeoPointEmpty#e4c123d6 = InputGeoPoint;
-
-inputGeoPoint#48222faf flags:# lat:double long:double accuracy_radius:flags.0?int = InputGeoPoint;
-
-inputMediaGeoLive#971fa843 flags:# stopped:flags.0?true geo_point:InputGeoPoint heading:flags.2?int period:flags.1?int proximity_notification_radius:flags.3?int = InputMedia;
-
----functions---
-
-messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-
-messages.editMessage#48f71778 flags:# no_webpage:flags.1?true peer:InputPeer id:int message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.15?int = Updates;
-

To send a live geolocation, use messages.sendMedia with an inputMediaGeoLive media .

-

The inputMediaGeoLive allows sending the geolocation as an inputGeoPoint with floating point latitude and longitude, with an optional accuracy_radius in meters.
-Clients can also provide a heading, a direction in degrees (1-360) that can be used to indicate the direction of the user, a validity period for the current location, and a proximity_notification_radius .

-

The sent geolocation should be updated perioducally using messages.editMessage at most every period seconds, in order to implement the "live" part of live geolocations.

-

To stop sharing the location, pass inputGeoPointEmpty as location and set the stopped flag to true in a last messages.editMessage call.

-

Receiving live locations

-
geoPoint#b2a2f663 flags:# long:double lat:double access_hash:long accuracy_radius:flags.0?int = GeoPoint;
-messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;
-
-updateGeoLiveViewed#871fb939 peer:Peer msg_id:int = Update;
-

Clients will receive a message with a messageMediaGeoLive, containing the information passed by the sender; when the geolocation message is marked as read, an updateGeoLiveViewed is generated.

-

Periodically, the geolocation will be updated with updateEditMessage/updateEditChannelMessage updates.

-

Live location previews

-
inputWebFileGeoPointLocation#9f2221c9 geo_point:InputGeoPoint access_hash:long w:int h:int zoom:int scale:int = InputWebFileLocation;
-
-inputGeoPoint#48222faf flags:# lat:double long:double accuracy_radius:flags.0?int = InputGeoPoint;
-
----functions---
-
-upload.getWebFile#24e6818d location:InputWebFileLocation offset:int limit:int = upload.WebFile;
-

A map preview can be generated by passing the received geoPoint to upload.getWebFile, to download an image preview of the map.

-
    -
  • geo_point is generated from the lat , long accuracy_radius parameters of the geoPoint
  • -
  • access_hash is the access hash of the geoPoint
  • -
  • w - Map width in pixels before applying scale; 16-1024
  • -
  • h - Map height in pixels before applying scale; 16-1024
  • -
  • zoom - Map zoom level; 13-20
  • -
  • scale - Map scale; 1-3
  • -
-

The image is then downloaded as specified here »

-

Proximity alert

-
messageActionGeoProximityReached#98e0d697 from_id:Peer to_id:Peer distance:int = MessageAction;
-
-messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;
-

If:

-
    -
  • A user sets a proximity_notification_radius when sending a location
  • -
  • Multiple users share their location within the same chat
  • -
  • One of the other users comes within proximity_notification_radius meters of the first user, and updates their location accordingly
  • -
-

An updateNewMessage/updateNewChannelMessage is generated for all chat members, containing a messageService with action messageActionGeoProximityReached:

-
    -
  • messageActionGeoProximityReached.to_id is the peer that enabled proximity alerts
  • -
  • messageActionGeoProximityReached.from_id is the peer that is now in proximity of messageActionGeoProximityReached.to_id
  • -
  • messageActionGeoProximityReached.distance is the distance between them, in meters
  • -
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/mentions.html b/data/core.telegram.org/api/mentions.html deleted file mode 100644 index a6db56c9c3..0000000000 --- a/data/core.telegram.org/api/mentions.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - Mentions - - - - - - - - - - - - - -
- -
-
-
- -

Mentions

- -
- -

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

-
messageEntityMention#fa04579d offset:int length:int = MessageEntity;
-messageEntityMentionName#dc7b1140 offset:int length:int user_id:long = MessageEntity;
-inputMessageEntityMentionName#208e68c9 offset:int length:int user_id:InputUser = MessageEntity;
-
-message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
-
-channelParticipantsMentions#e04b5ceb flags:# q:flags.0?string top_msg_id:flags.1?int = ChannelParticipantsFilter;
-
----functions---
-
-messages.sendMessage#520c3870 flags:# no_webpage:flags.1?true silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-
-channels.getParticipants#77ced9d0 channel:InputChannel filter:ChannelParticipantsFilter offset:int limit:int hash:long = channels.ChannelParticipants;
-

Mentions are implemented as message entities, passed to the messages.sendMessage method:

- -

Incoming messages mentioning to the current user will have the mentioned flag set, and will contain one or more messageEntityMention and messageEntityMentionName constructors.

-

Graphical clients can show a list of mentionable users when the user starts entering an @ in the text bar; for this purpose, the channelParticipantsMentions filter can be used in channels.getParticipants.
-This filter can be enhanced by providing an additional query string q (anything the user enters after @); it will also return non-participant users, in case of channel users commenting in post comment sections.

-

Dialog mentions

-
dialog#2c171f72 flags:# pinned:flags.2?true unread_mark:flags.3?true peer:Peer top_message:int read_inbox_max_id:int read_outbox_max_id:int unread_count:int unread_mentions_count:int notify_settings:PeerNotifySettings pts:flags.0?int draft:flags.1?DraftMessage folder_id:flags.4?int = Dialog;
-
----functions---
-
-messages.getUnreadMentions#46578472 peer:InputPeer offset_id:int add_offset:int limit:int max_id:int min_id:int = messages.Messages;
-messages.readMentions#f0189d3 peer:InputPeer = messages.AffectedHistory;
-

Graphical clients are supposed to show a blue mention indicator next to the message counter of chats in the dialog list.
-The dialog constructor contains an unread_mentions_count field to isolate chats with unread mentions; the actual mention counter should be shown inside of the chat itself, above an @ button that can be used, by clicking multiple times, to navigate back (using messages.getUnreadMentions) through the mention history.

-

When the last unread mention is read, or when long-clicking on the @ button, all mentions for a chat should marked as read using messages.readMentions.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/min.html b/data/core.telegram.org/api/min.html deleted file mode 100644 index 47a60c40eb..0000000000 --- a/data/core.telegram.org/api/min.html +++ /dev/null @@ -1,142 +0,0 @@ - - - - - Min constructors - - - - - - - - - - - - - -
- -
-
-
- -

Min constructors

- -

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set. This is done for performance and privacy reasons.

-

When receiving said constructors, the client must first check if user or chat object without min flag is already present in local cache. If it is present, then the client should just ignore constructors with min flag and use local one instead.

-

The rest of article assumes the client receives min-constructor without full object in local cache.

-

The client must store the context (similar to file references) in which the user/channel was seen. Later, when the client needs to pass the user/channel as input argument (e.g. fetch profile, mute, ban etc), the context is used to generate the input*FromMessage constructor, instead of normal inputUser, inputChannel or inputPeer.

- -

The access_hash value, if present, is only suitable to use in inputPeerPhotoFileLocation, to directly download the profile pictures of channels and users without having to generate an inputPeer*FromMessage, simply using inputPeer* with the specified access hash.

-

Usually min constructors are encountered in messages inside of groups or channels. -When a message mentioning (sender, forwarder or forwardee, et cetera) such a user or channel is found, the constuctor must be associated with the message ID of the message and with the chat where the message was seen.

-

Example

-

Assume a message with id 34 is received from supergroup (actually channel) 123456789. -Said message was sent by from_id 102424212. -The updates container that contained the message has a user with ID 102424212 in the users field, but it has the min flag set, and the provided access_hash may be absent, or otherwise can't be used to generate a typical inputPeerUser constructor to send messages or do other actions.

-

What the client does is associate 102424212 with the channel 123456789 and message ID 34. -When and if the client will need to interact with user 102424212, it will generate one of the *FromMessage constructors mentioned above, setting:

-
    -
  • msg_id to 34
  • -
  • peer to the InputPeer associated with channel 123456789
  • -
  • user_id to 102424212
  • -
-

user_id can also be set to the IDs of users met in the fwd_header (messages forwarded from a user can be used to interact with the original sender, if they don't have privacy settings for forwards enabled). -Users mentioned via messageEntityMentionName in a message can also be used.

-

The same can be done with min channels.

-

Example implementations: Telegram for iOS, tdlib.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/obtaining_api_id.html b/data/core.telegram.org/api/obtaining_api_id.html deleted file mode 100644 index e91ef8a48b..0000000000 --- a/data/core.telegram.org/api/obtaining_api_id.html +++ /dev/null @@ -1,140 +0,0 @@ - - - - - Creating your Telegram Application - - - - - - - - - - - - - -
- -
-
-
- -

Creating your Telegram Application

- -

We welcome all developers to use our API and source code to create Telegram-like messaging applications on our platform free of charge.

-
-

In order to ensure consistency and security across the Telegram ecosystem, -all third-party client apps must comply with the API Terms of Service.

-
-

Obtaining api_id

-

In order to obtain an API id and develop your own application using the Telegram API you need to do the following:

-
    -
  • Sign up for Telegram using any application.
  • -
  • Log in to your Telegram core: https://my.telegram.org.
  • -
  • Go to 'API development tools' and fill out the form.
  • -
  • You will get basic addresses as well as the api_id and api_hash parameters required for user authorization.
  • -
  • For the moment each number can only have one api_id connected to it.
  • -
-

We will be sending important developer notifications to the phone number that you use in this process, so please use an up-to-date number connected to your active Telegram account.

-

Using the api_id

-

Before using the MTProto Telegram API, please note that all API client libraries are strictly monitored to prevent abuse.

-

If you use the Telegram API for flooding, spamming, faking subscriber and view counters of channels, you will be banned forever.

-

Due to excessive abuse of the Telegram API, all accounts that sign up or log in using unofficial Telegram API clients are automatically put under observation to avoid violations of the Terms of Service.

-

If you didn't violate the Terms of Service but your account does get banned after using the API, write to recover@telegram.org explaining what you intend to do with the API, asking to unban your account.
-Please note that emails are checked by a human, so automatically generated emails will be detected and banned.

-

Using Telegram's open source code

-

Everyone is welcome to use our open source code. We have included a sample API id with the code. This API id is limited on the server side and is not suitable for apps released to end-users — using it for anything but testing purposes will result in the API_ID_PUBLISHED_FLOOD error for your users. It is necessary that you obtain your own API id before you publish your app.

-
-

Please remember to publish your code as well in order to comply with the GNU GPL licences.

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/offsets.html b/data/core.telegram.org/api/offsets.html deleted file mode 100644 index bf15c7f46c..0000000000 --- a/data/core.telegram.org/api/offsets.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - Pagination in the API - - - - - - - - - - - - - -
- -
-
-
- -

Pagination in the API

- -
- -

Lots of Telegram API methods provide access to potentially large lists of objects, which requires pagination.

-

In order to fetch only relevant subset of results for each request there is a number of available input parameters. Here is a list in order how they are applied in API.

-

Typically, results are returned in antichronological order with descending object ID values.

-

limit parameter

-

A limit on the number of objects to be returned, typically between 1 and 100. When 0 is provided the limit will often default to an intermediate value like ~20.

-

offset-based pagination

-

For a few methods with mostly static data this parameter allows to skip offset elements from the beginning of list; negative values are ignored.

-

offset_id-based pagination

-

For most methods where results are real-time data (e.g. any chat history) offset value is not passed directly. Instead it is calculated from the passed offset_id and add_offset parameter values as offsetFromID(offset_id) + add_offset, where offsetFromID(offset_id) is a number of results from the beginning of list up to the result with ID offset_id, inclusive.

-

Sample use cases:

-
    -
  • -

    Loading 20 messages, older than message with ID MSGID:

    -

    messages.getHistory({offset_id: MSGID, add_offset: 0, limit: 20})

    -
  • -
  • -

    Loading 20 messages, newer than message with ID MSGID:

    -

    messages.getHistory({offset_id: MSGID, add_offset: -20, limit: 20})

    -
  • -
  • -

    Loading 20 messages around message with ID MSGID:

    -

    messages.getHistory({offset_id: MSGID, add_offset: -10, limit: 20})

    -
  • -
-

Additional filtering

-

There is a number of parameters, which are applied to the list after slicing with offset and limit, to reduce the result subset even more:

-
    -
  • max_id: Can be used to only return results with ID strictly smaller than max_id (e.g. message ID)
  • -
  • min_id: Can be used to only return results with ID strictly greater than min_id(e.g. message ID)
  • -
  • max_date: Can be used to only return results that are older than max_date:
  • -
  • min_date: Can be used to only return results with are newer than min_date:
  • -
  • hash: See below.
  • -
-

Hash generation

-

To further reduce the result subset, there is a mechanism to avoid fetching data if the resulting list hasn't changed from the one stored on client, similar to ETag.

-

When the client has cached results for API request, it can calculate the hash value for it by taking the result IDs (message IDs or other fields with name id) and using them to compute a 64-bit hash with the following algorithm:

-
# Here, ^ indicates a bitwise XOR
-
-hash = 0
-for id in ids:
-    hash = hash ^ (id >> 21)
-    hash = hash ^ (id << 35)
-    hash = hash ^ (id >> 4)
-    hash = hash + id
-

In some cases, the result container already has a hash field, that can be used instead.

-

When the client passes a correct value, the API will return one of *NotModified constructors, e.g. messages.messagesNotModified instead of the actual results.

-

Example methods

-
    -
  • messages.getHistory supports all result navigation parameters including message ID hashes and except filters
  • -
  • channels.getParticipants supports simple navigation using limit and offset, along with filtering and hash reducing using the user IDs of returned participants
  • -
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/optimisation.html b/data/core.telegram.org/api/optimisation.html deleted file mode 100644 index 1fc665b082..0000000000 --- a/data/core.telegram.org/api/optimisation.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - Client-Side Optimization - - - - - - - - - - - - - -
- -
-
-
- -

Client-Side Optimization

- -

Simplified Acknowledgment of Message Delivery

-

An outgoing message may be considered sent once the server has assigned it an identifier. Normally, a client would learn of this from the result of the messages.sendMessage method. -The MTProto server provides a mechanism for “quick acknowledgments". Upon receiving such an acknowledgment, the client may be certain that the call to the send message method has at least been fully received by the server and placed in a processing queue, and can inform the user that the delivery was successful. -It is possible that the server’s actual response will never be received by the client (an interrupted connection; or the app restarts at exactly the wrong time). To correctly handle these situations, you can use a special type of notification generated by the server when updates.getDifference is called: updateMessageID. When processing this notification, the client can use the random_id identifier to associate the previously transmitted message with the one delivered to the server. -If such a notification is not issued when updates.getDifference is called for one of the previously sent messages, the message must be marked as undelivered.

-

Server Salt

-

Server salt is a 64-bit number added to every outgoing and incoming message. At present, a single salt’s lifespan is 1 hour, following which it is considered invalid and the server will return an error for all the messages that contain it. The error message will contain the correct salt, which may be immediately used for sending. Given this approach, there will always be a period of waiting before the client receives a new salt if it connects to the server less frequently than once an hour. -For improved performance, there is a special get_future_salts method, which fetches in advance a list of the salts that will be valid during the course of a specified period of time following the call (1 day, for example). A start time and an end time are specified for each salt. The salts overlap one another by half an hour. We recommend always using the record with the longest remaining lifespan.

-

Downloading Files and Uploading Data to the Server

-

We recommend that separate connections and sessions be created for these tasks. Remember that the extra sessions must be deleted when no longer needed. -It makes sense to download files over several connections (optimally to have a pool). When uploading data to a server one connection is enough to achieve the best results.

-

The file handling API is designed to perform data operations in parts. In its simplest implementation, the process of uploading files to a server looks like this: send a query, wait for a response, send the next query, etc. This approach does not optimize the use of network resources and the ping time has a huge effect. -The upload and download process is optimal when two or more queries are continuously being executed through one connection. In this arrangement, uploading to the server would look like this:

-
    -
  1. Send Query 1
  2. -
  3. Send Query 2
  4. -
  5. Wait for a response to Query 1
  6. -
  7. Send Query 3
  8. -
  9. Wait for a response to Query 2
  10. -
  11. Send Query 4
  12. -
  13. etc.
  14. -
-

This will help reduce the effect of ping latency and maximize the channel workload.

-

Sending Messages in Bulk

-

Sometimes a client needs to transmit several send message method calls to the server all at once in a single message or in several consecutive messages. However, the server may execute these requests out of order (queries are handled by different servers to improve performance, which introduces a degree of randomness to the process). -This requires that dependencies be explicitly stated when processing queries by using the function

-
invokeAfterMsg#cb9f372d {X:Type} msg_id:long query:!X = X;
-

Actually, this means padding the beginning of the query with the 32-bit number 0xcb9f372d and the 64-bit message identifier of the query on which the current query is dependent.

-

Grouping Updates

-

Generating updates (notifications about various server events) and delivering them to the client form two different parts of the system (respectively, the messenger API and MTProto). By itself, MTProto cannot modify in any way the data transmitted to the client, and the server API cannot respond to client-MTProto connection events. -Imagine the situation where a client loses its connection (or is intentionally disconnected from the network) for some time. If lots of different events occur before a new connection is established (contacts come online, typing event messages are sent), then when a connection is established the client will receive lots of data containing all of the intervening events, despite the fact that most of the data is obsolete. -The grouping of messages has been introduced to optimize such situations. If new events occur and the client has not managed to “collect” the previously generated updates, then the server API can combine them into a single package.

-

A client is able to control when the MTProto server begins to consider that the connection has been lost and grouping can begin (the earlier this occurs when there is no connection, the better for the client). This functionality is implemented through a special type of Ping message, ping_delay_disconnect, which specifies a time delay following which the server will close the current connection and start grouping messages.

-

It makes sense to combine the transmission of ping_delay_disconnect with that of other recurring tasks, such as updating the user status (account.updateStatus).

-

Setting the Typing Status

-

If a contact is not online, there is no need to invoke messages.setTyping.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/passport.html b/data/core.telegram.org/api/passport.html deleted file mode 100644 index 4527355cfd..0000000000 --- a/data/core.telegram.org/api/passport.html +++ /dev/null @@ -1,674 +0,0 @@ - - - - - Telegram passport - - - - - - - - - - - - - -
- -
-
-
- -

Telegram passport

- -
- -

Telegram Passport is a unified authorization method for services that require personal identification. Users can upload their documents once, then instantly share their data with services that require real-world ID (finance, ICOs, etc.). Telegram doesn‘t have access to the users’ personal information thanks to end-to-end encryption.

-

This page describes the request flow that client apps must used to send the requested data to the service.

-

Overview

-

From the perspective of a service that requires real-world ID, the process looks like this:

-
    -
  • A user presses “Log in with Telegram” on your website or in your app.
  • -
  • You request the data you need.
  • -
  • The user accepts your privacy policy and agrees to share their data.
  • -
  • The user's Telegram app downloads and decrypts the data you requested from the end-to-end encrypted storage on Telegram.
  • -
  • If some of the data you requested is missing, the user can add it to their Telegram Passport at this point.
  • -
  • The user's app encrypts the data with your public key and sends it to you.
  • -
  • You decrypt the data, check it for errors and re-request any missing or invalid information.
  • -
  • You sign the user up for your service. Tada!
  • -
-

See As a bot to see how to request passport data using a bot, through the MTProto API. -Look at the Passport Manual to see how to request passport data using a bot, through the simplified bot API.

-

From the perspective of a user, the process looks something like this:

-
    -
  • Your app receives an event/intent from one of the SDKs, or from a custom source.
  • -
  • The user accepts your privacy policy and agrees to share their data.
  • -
  • The user's Telegram app downloads the data you requested from the end-to-end encrypted storage on Telegram.
  • -
  • If some of the data you requested is missing, the user can add it to their Telegram Passport at this point.
  • -
  • The user's app encrypts the data with your public key and sends it to the service.
  • -
  • You sign the user up for your service. Tada!
  • -
-

See As a user to see how user client apps should send passport data to a service, through the MTProto API.

-

As a bot

-

A simplified version of this process can be used using the bot API, for more info see the Passport Manual.

-

Using the MTProto API, the process is pretty much the same, up until the actual API calls.

-
-

Note that all binary fields are in raw binary format, unlike in the bot API where they are base64-encoded

-
-

Setting Up Telegram Passport

-

As per the bot API.

-

Requesting Information

-

As per the bot API.

-

Receiving information

-

Schema:

-
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;
-
-securePlainPhone#7d6099dd phone:string = SecurePlainData;
-securePlainEmail#21ec5a5f email:string = SecurePlainData;
-
-secureFile#e0277a62 id:long access_hash:long size:int dc_id:int date:int file_hash:bytes secret:bytes = SecureFile;
-
-secureValueTypePersonalDetails#9d2a81e3 = SecureValueType;
-secureValueTypePassport#3dac6a00 = SecureValueType;
-secureValueTypeDriverLicense#6e425c4 = SecureValueType;
-secureValueTypeIdentityCard#a0d0744b = SecureValueType;
-secureValueTypeInternalPassport#99a48f23 = SecureValueType;
-secureValueTypeAddress#cbe31e26 = SecureValueType;
-secureValueTypeUtilityBill#fc36954e = SecureValueType;
-secureValueTypeBankStatement#89137c0d = SecureValueType;
-secureValueTypeRentalAgreement#8b883488 = SecureValueType;
-secureValueTypePassportRegistration#99e3806a = SecureValueType;
-secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;
-secureValueTypePhone#b320aadb = SecureValueType;
-secureValueTypeEmail#8e3ca7ee = SecureValueType;
-
-secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;
-
-secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;
-
-messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction; 
-messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;
-
-updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
-

When the user confirms your request by pressing the 'Authorize' button, the MTProto API sends an updateNewMessage from the user, with a messageService constructor, containing a messageActionSecureValuesSentMe constructor that contains the encrypted Telegram Passport data.

-

Decrypting data

-
secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;
-
-messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction; 
-

To decrypt the received data, first, decrypt the credentials contained in secureCredentialsEncrypted.

-
    -
  1. -

    Decrypt the credentials secret ( secret field in secureCredentialsEncrypted) using your private key (set OAEP padding option, e.g. OPENSSL_PKCS1_OAEP_PADDING in PHP)

    -
  2. -
  3. -

    Use this secret and the credentials hash ( hash field in secureCredentialsEncrypted) to calculate credentials_key and credentials_iv as described below:

    -
     credentials_secret_hash = SHA512( credentials_secret + credentials_hash )
    - credentials_key = slice( credentials_secret_hash, 0, 32 )
    - credentials_iv = slice( credentials_secret_hash, 32, 16 )
    -
  4. -
  5. -

    Decrypt the credentials data ( data field in secureCredentialsEncrypted) by AES256-CBC using these credentials_key and credentials_iv. IMPORTANT: At this step, make sure that the credentials hash is equal to SHA256( credentials_data )

    -
  6. -
  7. -

    Credentials data is padded with 32 to 255 random padding bytes to make its length divisible by 16 bytes. The first byte contains the length of this padding (including this byte). Remove the padding to get the data.

    -
  8. -
-
-

Note that all hashes are raw binary data, not hexits

-
-

Credentials

-

The credentials are a JSON-serialized object, structured exactly as in the bot API ». -Since decryption credentials are E2E encrypted, apps have to store the decryption credentials as JSON and not TL payloads.

-

The credentials are used as described in the Passport Manual to decrypt the files attached to the secureValue. -In this case, the container for the E2E encrypted data is in TL, while the encrypted data itself is in JSON.

-
secureValue
-
secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;
-
-messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction; 
-

The schema for the secureValue constructor defines the constructor that can be found in each field.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeSecure passport value type
dataflags.0?SecureDataEncrypted Telegram Passport element data
front_sideflags.1?SecureFileEncrypted passport file with the front side of the document
reverse_sideflags.2?SecureFileEncrypted passport file with the reverse side of the document
selfieflags.3?SecureFileEncrypted passport file with a selfie of the user holding the document
translationflags.6?Vector<SecureFile>Array of encrypted passport files with translated versions of the provided documents
filesflags.4?Vector<SecureFile>Array of encrypted passport files with photos the of the documents
plain_dataflags.5?SecurePlainDataPlaintext verified passport data
hashbytesData hash
-

Here's a list of possible SecureValueTypes, and the parameters that can be set/requested when using each type.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TypeAllowed fields
secureValueTypeEmailplain_data
secureValueTypePhoneplain_data
secureValueTypePersonalDetailsdata
secureValueTypePassportdata, front_side, selfie, translation
secureValueTypeDriverLicensedata, front_side, reverse_side, selfie, translation
secureValueTypeIdentityCarddata, front_side, reverse_side, selfie, translation
secureValueTypeInternalPassportdata, front_side, selfie, translation
secureValueTypeAddressdata
secureValueTypeUtilityBillfiles, translation
secureValueTypeBankStatementfiles, translation
secureValueTypeRentalAgreementfiles, translation
secureValueTypePassportRegistrationfiles, translation
secureValueTypeTemporaryRegistrationfiles, translation
-
SecureData
-
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;
-

Data is an encrypted and padded JSON-serialized object of one of the specified JSON types, depending on the chosen type.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Chosen typeJSON object
secureValueTypePersonalDetailsPersonalDetails
secureValueTypePassportIdDocumentData
secureValueTypeDriverLicenseIdDocumentData
secureValueTypeIdentityCardIdDocumentData
secureValueTypeInternalPassportIdDocumentData
secureValueTypeAddressResidentialAddress
-

DataCredentials extracted from the credentials can then be used to decrypt encrypted data from the data field in secureData. -For more info on how to decrypt the data field, see the passport manual.

-
SecureFile
-
secureFile#e0277a62 id:long access_hash:long size:int dc_id:int date:int file_hash:bytes secret:bytes = SecureFile; 
-
-inputSecureFileLocation#cbc7ee28 id:long access_hash:long = InputFileLocation;
-
----functions---
-
-upload.getFile#b15a9afc flags:# precise:flags.0?true cdn_supported:flags.1?true location:InputFileLocation offset:int limit:int = upload.File;
-

Files (JPG format when decrypted, max. 10MB) are downloaded chunk by chunk as described in files », except that instead of generating an inputFileLocation, an inputFileLocation should be generated, instead.

-
    -
  • The id field is the id of the secureFile
  • -
  • The access_hash field is the access_hash of the secureFile
  • -
-

FileCredentials extracted from the credentials can then be used to decrypt downloaded encrypted data. -For more info on how to decrypt passport files, see the passport manual.

-
SecurePlainData
-
securePlainPhone#7d6099dd phone:string = SecurePlainData;
-securePlainEmail#21ec5a5f email:string = SecurePlainData;
-

The email/phone is passed in plaintext using the respective SecurePlainData constructor. -Emails and phone numbers sent using telegram passport are already verified as described in the passport manual.

-

Fixing errors

-
secureValueErrorData#e8a40bd9 type:SecureValueType data_hash:bytes field:string text:string = SecureValueError;
-secureValueErrorFrontSide#be3dfa type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorReverseSide#868a2aa5 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorSelfie#e537ced6 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorFile#7a700873 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorFiles#666220e9 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
-secureValueError#869d758f type:SecureValueType hash:bytes text:string = SecureValueError;
-secureValueErrorTranslationFile#a1144770 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorTranslationFiles#34636dd8 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
-
-inputUser#f21158c6 user_id:long access_hash:long = InputUser;
-
-
----functions---
-
-users.setSecureValueErrors#90c894b5 id:InputUser errors:Vector<SecureValueError> = Bool;
-

If the data you received contains errors, the bot can use the users.setSecureValueErrors method to inform the user and request information again. The user will not be able to resend the data, until all errors are fixed.

-

Descriptions of the method parameters can be found in the method's documentation page ».

-

As a user

-

Receiving requests

-

The process starts when your app receives an event from one of the SDKs, or from a custom source.

-

URI format

-

The SDKs trigger a passport authorization request by opening the following Telegram-specific URI:

-
tg://resolve?params
-

With the following query string parameters:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParametersTypeRequired
domainStringYes
bot_idIntegerYes
scopeUriPassportScopeYes
public_keyStringYes
nonceStringYes
callback_urlStringOptional
payloadStringOptional
-

Example URI, generated by the Telegram Passport Example page:

-
tg://resolve?domain=telegrampassport&bot_id=543260180&scope=%7B%22v%22%3A1%2C%22d%22%3A%5B%7B%22_%22%3A%22pd%22%2C%22n%22%3A1%7D%2C%22ad%22%2C%22pn%22%2C%22em%22%2C%7B%22_%22%3A%5B%7B%22_%22%3A%22pp%22%2C%22s%22%3A1%2C%22t%22%3A1%7D%2C%22ip%22%2C%22dl%22%2C%22ic%22%5D%7D%2C%7B%22_%22%3A%5B%22ub%22%2C%22bs%22%2C%22ra%22%2C%22pr%22%2C%22tr%22%5D%7D%5D%7D&public_key=-----BEGIN%20PUBLIC%20KEY-----%0AMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv6m1zBF8lZOCqcxf8hnj%0AkvHwuWdU8s4rBWaxKXH%2FvDDUklcCS5uhSnmjhxWca9suubaG3lW4HxlCilkeJPVf%0Ajimg5Q8ZqWrR3OoOihEpcG9iJZTOEpsEk7VtEiabgacBG3Quv9JslTrDe95Fn801%0At9d21HXwgMrHeHpWDOn31Dr%2BwoEH%2BkwySUWa6L%2FZbnGwSNP7eeDTE7Amz1RMDk3t%0A8EWGq58u0IQatPcEH09aUQlKzk6MIiALkZ9ILBKCBk6d2WCokKnsdBctovNbxwSx%0AhP1qst1r%2BYc8iPBZozsDC0ZsC5jXCkcODI3OC0tkNtYzN2XKalW5R0DjDRUDmGhT%0AzQIDAQAB%0A-----END%20PUBLIC%20KEY-----%0A&nonce=b8e892dc2e0afe63424d101b964f1256_32858210_708614a4585b84872e&callback_url=https%3A%2F%2Fcore.telegram.org%2Fpassport%2Fexample%3Fpassport_ssid%3Db8e892dc2e0afe63424d101b964f1256_32858210_db259b427f200751ce&payload=b8e892dc2e0afe63424d101b964f1256_32858210_708614a4585b84872e
-

UriPassportScope

-

This object represents the data to be requested.

- - - - - - - - - - - - - - - - - - -
FieldTypeDescription
dArray of UriPassportScopeElementList of requested elements, each type may be used only once in the entire array of UriPassportScopeElement objects
vIntegerScope version, must be 1
-
UriPassportScopeElement
-

This object represents a requested element, should be one of:

- -

Passport document type identifiers are aliased with the following reduced type identifiers:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FullAlias
personal_detailspd
passportpp
driver_licensedl
identity_cardic
internal_passportip
id_documentidd
addressad
utility_billub
bank_statementbs
rental_agreementra
passport_registrationpr
temporary_registrationtr
address_documentadd
phone_numberpn
emailem
-

You can use the special type "idd" as an alias for one of "pp", "dl", "ic" and the special type "add" as an alias for one of "ub", "bs", "ra".

-

UriPassportScopeElementOneOfSeveral

-

This object represents several elements one of which must be provided.

- - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
_Array of UriPassportScopeElementOneList of elements one of which must be provided; must contain either several of “pp”, “dl”, “ic”, “ip” or several of “ub”, “bs”, “ra”, “pr”, “tr”
sBooleanOptional. Use this parameter if you want to request a selfie with the document from this list that the user chooses to upload.
tBooleanOptional. Use this parameter if you want to request a translation of the document from this list that the user chooses to upload. Note: We suggest to only request translations after you have received a valid document that requires one.
-

UriPassportScopeElementOne

-

This object represents one particular element that must be provided. If no options are needed, String can be used instead of this object to specify the type of the element.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
_StringElement type. One of "pd", "pp", "dl", "ic", "ip", "ad", "ub", "bs", "ra", "pr", "tr", "pn", "em"
sBooleanOptional. Use this parameter if you want to request a selfie with the document as well. Available for "pp", "dl", "ic" and "ip"
tBooleanOptional. Use this parameter if you want to request a translation of the document as well. Available for "pp", "dl", "ic", "ip", "ub", "bs", "ra", "pr" and "tr". Note: We suggest to only request translations after you have received a valid document that requires one.
nBooleanOptional. Use this parameter to request the first, last and middle name of the user in the language of the user's country of residence. Available for "pd"
-

You can also use the special type "idd" as an alias for one of "pp", "dl", "ic" and the special type "add" as an alias for one of "ub", "bs", "ra".

-

Setting up Telegram Passport

-

The next step for the client app is to request the user's 2FA passport, and configure Telegram Passport/fetch and decrypt remotely saved Telegram Passport parameters as described in the Encryption article ».

-

Fetching the passport form

-
account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;
-
----functions---
-
-account.getAuthorizationForm#a929597a bot_id:long scope:string public_key:string = account.AuthorizationForm;
-

Then, the client app passes the bot ID, scope and public key from the passport authorization request to the Telegram servers using the account.getAuthorizationForm method.

-

The response will be an account.authorizationForm constructor, with info about the required document types, the URL of the service's privacy policy, as well as info about the bot to which the form should be sent. -If the form was already submitted at least once, the constructor will also contain a list of already submitted data, along with eventual errors.

-

The user should accept the privacy policy and proceed to fill in the required data, and the client should encrypt and upload it as described in the Encryption article ».

-

Submitting the passport form

-
secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;
-
-secureValueHash#ed1ecdb0 type:SecureValueType hash:bytes = SecureValueHash;
-
----functions---
-
-account.acceptAuthorization#f3ed4c73 bot_id:long scope:string public_key:string value_hashes:Vector<SecureValueHash> credentials:SecureCredentialsEncrypted = Bool;
-

Once the user finishes uploading the required documents and clicks on the submit button, the client calls account.acceptAuthorization, submitting the documents to the bot associated to the service.

-
    -
  • As before, bot_id, scope and public_key are taken from the authorization request URI.
  • -
  • value_hashes is used by the server to choose which document of which type to send to the bot: the type field should be set to the document type, and the hash field should be set to the data_hash/file_hash generated when uploading encrypting the data ».
  • -
  • credentials contains the encrypted credentials required by the service to decrypt the sent E2E encrypted secure values: it is generated as described in Passport Credentials ».
  • -
-

Finally, the client opens the callback URL (if present).

-

Handling invalid forms

-
secureValueErrorData#e8a40bd9 type:SecureValueType data_hash:bytes field:string text:string = SecureValueError;
-secureValueErrorFrontSide#be3dfa type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorReverseSide#868a2aa5 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorSelfie#e537ced6 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorFile#7a700873 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorFiles#666220e9 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
-secureValueError#869d758f type:SecureValueType hash:bytes text:string = SecureValueError;
-secureValueErrorTranslationFile#a1144770 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorTranslationFiles#34636dd8 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
-
-account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;
-
----functions---
-
-account.getAuthorizationForm#a929597a bot_id:long scope:string public_key:string = account.AuthorizationForm;
-

If any of the values of the submitted form are rejected by the service, the bot calls the appropriate method to set information about errors.

-

The user can find out about these errors directly from the service, or, if they decide to restart the process and resend the corrected data, directly from the authorization form (errors field).

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/pattern.html b/data/core.telegram.org/api/pattern.html deleted file mode 100644 index dfc49b68da..0000000000 --- a/data/core.telegram.org/api/pattern.html +++ /dev/null @@ -1,122 +0,0 @@ - - - - - Pattern matching - - - - - - - - - - - - - -
- -
-
-
- -

Pattern matching

- -

Some methods require the client to verify if the data obtained from an external source matches a certain pattern.

-

For example, when requesting a login code, if the chosen verification method is a flash call, it is required that the phone number (which is the login code) matches the specified pattern.

-

Same with email verification codes.

-

In all cases, the pattern is a string of the same length as the string to verify: and matching is as simple as checking if all chars in the source string are the same as in the pattern string. -Some chars in the pattern string may be censored using an asterisk *, in this case any char in the source string is considered valid.

-

The pattern string can also be a single asterisk, in this case all patterns are considered valid.

-

If the source string is a phone number, it has to be sanitized first to include only the following chars: 0123456789.

-

Example implementation: telegram for android.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/payments.html b/data/core.telegram.org/api/payments.html deleted file mode 100644 index b888371387..0000000000 --- a/data/core.telegram.org/api/payments.html +++ /dev/null @@ -1,366 +0,0 @@ - - - - - Payments API - - - - - - - - - - - - - -
- -
-
-
- -

Payments API

- -
- -

You can accept payments from Telegram users via Telegram Bots.

-
-

Note: This article is intended for MTProto API developers. If you're looking for a general overview of Telegram Payments, check out the Telegram blog and the bot API payment manual.

-
-

Introducing Payments

-

Telegram bots can accept payments for goods and services from users. -For more info on how payments work, check out the Telegram Blog and the bot API payment manual.

-

This page will elaborate on the actions required to work with payments using the MTProto API.

-
-

A simplified version of the process is available only for bots using the bot API.

-
-

The first step for bots is enable payments as described here ».

-

Then, we work with payments as follows.

-

1. Create Invoice

-
inputWebDocument#9bed434d url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = InputWebDocument;
-
-labeledPrice#cb296bf8 label:string amount:long = LabeledPrice;
-
-invoice#cd886e0 flags:# test:flags.0?true name_requested:flags.1?true phone_requested:flags.2?true email_requested:flags.3?true shipping_address_requested:flags.4?true flexible:flags.5?true phone_to_provider:flags.6?true email_to_provider:flags.7?true currency:string prices:Vector<LabeledPrice> max_tip_amount:flags.8?long suggested_tip_amounts:flags.8?Vector<long> = Invoice;
-
-inputMediaInvoice#d9799874 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON start_param:flags.1?string = InputMedia;
-
----functions---
-
-messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-

The user contacts the bot and requests to purchase something. -The bot forms an inputMediaInvoice with an invoice constructor with a description of the goods or service, amount to be paid, as well as requested shipping info. -The provider parameter of the inputMediaInvoice constructor is where you put the token value that you've obtained earlier via Botfather. It is possible for one merchant bot to use several different tokens for different users or different goods and services.

-

Use the messages.sendMedia method to send the invoice. -You can also attach an inline keyboard to the message using the reply_markup field: if provided, the first button must be a keyboardButtonBuy button. Otherwise, an inline keyboard will be generated automatically, with a Pay 'total price' keyboardButtonBuy as only button.

-

An invoice message with a pay button can only be sent to a private chat with the user. Groups and channels are not supported.

-

2. Order information

-

2.1 Invoice message

-
keyboardButtonBuy#afd93fbb text:string = KeyboardButton;
-
-keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;
-replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;
-
-webDocument#1c570ed1 url:string access_hash:long size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;
-webDocumentNoProxy#f9c8bcc6 url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;
-
-messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
-
-message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
-
-updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
-

The user receives an updateNewMessage constructor from the bot, containing a messageMediaInvoice constructor with basic info about the product.

-

The message will also have a replyInlineMarkup keyboard attached to it. -The the first button of the keyboard will always be a keyboardButtonBuy button.

-

2.2 Getting invoice info about the product

-
invoice#cd886e0 flags:# test:flags.0?true name_requested:flags.1?true phone_requested:flags.2?true email_requested:flags.3?true shipping_address_requested:flags.4?true flexible:flags.5?true phone_to_provider:flags.6?true email_to_provider:flags.7?true currency:string prices:Vector<LabeledPrice> max_tip_amount:flags.8?long suggested_tip_amounts:flags.8?Vector<long> = Invoice;
-
-paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;
-
-paymentSavedCredentialsCard#cdc27a1f id:string title:string = PaymentSavedCredentials;
-
-payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
-
----functions---
-
-payments.getPaymentForm#8a333c8d flags:# peer:InputPeer msg_id:int theme_params:flags.0?DataJSON = payments.PaymentForm;
-

If the user clicks on the keyboardButtonBuy button, the client proceeds to call payments.getPaymentForm with the message ID of the invoice preview message to get the payment form.

-

The returned form will contain fields that should be passed to the payment provider along with the full invoice. -The payment form also contains info about previously saved payment credentials and order information (name, phone number, email, shipping address & so on).

-

The full invoice contains info about the information required for the order, the price and the currency, and whether this is a test order.

-

2.3 Verifying information

-
invoice#cd886e0 flags:# test:flags.0?true name_requested:flags.1?true phone_requested:flags.2?true email_requested:flags.3?true shipping_address_requested:flags.4?true flexible:flags.5?true phone_to_provider:flags.6?true email_to_provider:flags.7?true currency:string prices:Vector<LabeledPrice> max_tip_amount:flags.8?long suggested_tip_amounts:flags.8?Vector<long> = Invoice;
-
-postAddress#1e8caaeb street_line1:string street_line2:string city:string state:string country_iso2:string post_code:string = PostAddress;
-
-paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;
-
-payments.validatedRequestedInfo#d1451883 flags:# id:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = payments.ValidatedRequestedInfo;
-
----functions---
-
-payments.validateRequestedInfo#db103170 flags:# save:flags.0?true peer:InputPeer msg_id:int info:PaymentRequestedInfo = payments.ValidatedRequestedInfo;
-

If any data at all is requested by the invoice (name_requested, phone_requested, email_requested, shipping_address_requested), the user must call payments.validateRequestedInfo, providing the required data (as usual, msg_id is the ID of the invoice message). -The user can choose to save order information for future use by setting the save flag. -Data can be autofilled as described in autofill.

-

If no errors are found in the submitted info, the response of the method will contain an id flag, to be used later to complete the payment.

-

If the flexible flag of the invoice is set, calling the payments.validateRequestedInfo method will send a shipping query update to the bot, to which the bot will reply with the available shipping options for the specified address as described here ». -The return value in this case will also contain a shipping_options field with the available shipping options.

-

If any errors are found in the submmitted data, a service notification will be sent to the user, with a description of the error from the bot.

-

2.3.1 Autofill

-
payments.savedInfo#fb8fe43c flags:# has_saved_credentials:flags.1?true saved_info:flags.0?PaymentRequestedInfo = payments.SavedInfo;
-
----functions---
-
-payments.getSavedInfo#227d824b = payments.SavedInfo;
-payments.clearSavedInfo#d83d70c1 flags:# credentials:flags.0?true info:flags.1?true = Bool;
-

The requested fields can be autofilled with the info provided in the saved_info field of the payment form, or with the info fetched manually using payments.getSavedInfo.

-

Saved order information can also be cleared using payments.clearSavedInfo.

-

2.4 Select delivery option

-
labeledPrice#cb296bf8 label:string amount:long = LabeledPrice;
-
-shippingOption#b6213cdf id:string title:string prices:Vector<LabeledPrice> = ShippingOption;
-
-updateBotShippingQuery#b5aefd7d query_id:long user_id:long payload:bytes shipping_address:PostAddress = Update;
-
----functions---
-
-messages.setBotShippingResults#e5f672fa flags:# query_id:long error:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = Bool;
-

If a shipping address was requested and the bot included the parameter flexible, when the user validates order information the Telegram API will send an updateBotShippingQuery to the bot. -The bot must respond using messages.setBotShippingResults either with a list of possible delivery options and the relevant delivery prices, or with an error (for example, if delivery to the specified address is not possible).

-

The returned shipping options or the shipping error will be returned to the user while validating order information.

-

3. Payment

-
inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;
-inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
-inputPaymentCredentialsApplePay#aa1c39f payment_data:DataJSON = InputPaymentCredentials;
-inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;
-
-
-payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
-

3.1 Web payment

-
inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
-
-payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
-

Typically, payment takes place by opening the url in the specified payment form, which leads to a payment form on the website of the payment gateway. -Once the user finishes entering their payment credentials, a payment_form_submit web event is generated by the payment gateway, containing data and title JSON fields.

-

The title is used by the client app to represent the payment credentials (typically a censored version of credit card information). -The data is used to generate an inputPaymentCredentials constructor. -Eventually, you can set the save flag to save the credit card info for future use, only if 2FA is enabled.

-

Telegram does not have access to your card information. Credit card details will be handled only by the payment system.

-

3.2 Native payment

-
inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
-
-payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
-

Most telegram apps support working natively with the native APIs of some payment providers, without opening the website of the payment and receiving a JS event.

-

This is done using the JSON native_params parameters field of the payments.paymentForm constructor, which contains an object, which can contain one or more of the following fields:

-
    -
  • publishable_key: Stripe API publishable key
  • -
  • apple_pay_merchant_id: Apple Pay merchant ID
  • -
  • android_pay_public_key: Android Pay public key
  • -
  • android_pay_bgcolor: Android Pay form background color
  • -
  • android_pay_inverse: Whether to use the dark theme in the Android Pay form
  • -
  • need_country: True, if the user country must be provided,
  • -
  • need_zip: True, if the user ZIP/postal code must be provided,
  • -
  • need_cardholder_name: True, if the cardholder name must be provided
  • -
-

The payment gateway to use is decided based on the value of the native_provider field.

-
3.2.1 Stripe
-
inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
-
-payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
-

If the native_provider field is set and equal to stripe, the client can make use of the native Stripe token APIs with the publishable_key from the native_params to add a payment method to Stripe, and then use the token type and id to generate a JSON object:

-
{"type":"token.type", "id":"token.id"}"
-

The generated JSON object can then be passed to the data field of the inputPaymentCredentials. -Eventually, you can set the save flag to save the credit card info for future use, only if 2FA is enabled.

-

Telegram does not have access to your card information. Credit card details will be handled only by the payment system.

-

Example implementation: Telegram for Android.

-

3.3 Apple pay

-
inputPaymentCredentialsApplePay#aa1c39f payment_data:DataJSON = InputPaymentCredentials;
-

On iOS devices, Apple Pay can be used to generate payment data, which is then sent using the inputPaymentCredentialsApplePay constructor.

-

Example implementation: Telegram for iOS.

-

3.4 Android pay

-
inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;
-

On Android devices, Google Pay can be used to generate payment data, which is then sent using the inputPaymentCredentialsGooglePay constructor.

-

Example implementation: Telegram for Android.

-

3.5 Using saved payment credentials

-
inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;
-
-paymentSavedCredentialsCard#cdc27a1f id:string title:string = PaymentSavedCredentials;
-
-payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
-
-account.tmpPassword#db64fd34 tmp_password:bytes valid_until:int = account.TmpPassword;
-
----functions---
-
-account.getTmpPassword#449e0b51 password:InputCheckPasswordSRP period:int = account.TmpPassword;
-

To reuse saved payment methods, the saved_credentials field of the payment form is used. -The title of the paymentSavedCredentialsCard can be used to preview a censored version of credit card info. -The id field is provided by the payment provider directly to the Telegram servers when saving the payment method, and identifies the payment method. -Full credit card info is not saved on Telegram Servers, and cannot be fetched by the user.

-

In order to use the saved payment method, 2FA must be enabled: the user must verify their identity by entering their 2FA password, which is then used as described in the SRP docs to generate SRP parameters which must be passed to account.getTmpPassword.

-

The generated temporary password can then be used to make payments using the saved credentials using the inputPaymentCredentialsSaved constructor.

- -

Example implementation: Telegram for Android.

-

4. Pre-Checkout

-
inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;
-inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
-inputPaymentCredentialsApplePay#aa1c39f payment_data:DataJSON = InputPaymentCredentials;
-inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;
-
-payments.paymentResult#4e5f810d updates:Updates = payments.PaymentResult;
-payments.paymentVerificationNeeded#d8411139 url:string = payments.PaymentResult;
-
----functions---
-
-payments.sendPaymentForm#30c3bc9d flags:# form_id:long peer:InputPeer msg_id:int requested_info_id:flags.0?string shipping_option_id:flags.1?string credentials:InputPaymentCredentials tip_amount:flags.2?long = payments.PaymentResult;
-

After verifying order information, the final step for the client is to call payments.sendPaymentForm, with the following parameters:

-
    -
  • The msg_id is set to the ID of the invoice message
  • -
  • requested_info_id is set to the id of the verified order information, if it was requested
  • -
  • shipping_option_id is set to the selected delivery option, if shipping was requested.
  • -
  • credentials are the payment credentials generated by the payment provider, required to complete the order.
  • -
-

Payment method info can also be saved to the Telegram Servers and reused, by setting the save flag of inputPaymentCredentials when sending the form. -This is only possible on accounts with 2FA enabled.

-

The bot then replies to the received precheckout query, finally the user proceeds to checkout.

-

Please note that if the result of the method is a payments.paymentVerificationNeeded, before proceeding to checkout the payment provider requires the user to verify his identity by opening the provided url and following instructions. -Once the user finishes working with the webpage, the client can proceed to checkout.

-

Eventual errors are returned in the form of RPC errors, with the description of the error by the bot contained in service updates.

-

4.1 Receiving pre-checkout query

-
paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;
-
-updateBotPrecheckoutQuery#8caa9a96 flags:# query_id:long user_id:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string currency:string total_amount:long = Update;
-
----functions---
-
-messages.setBotPrecheckoutResults#9c2dd95 flags:# success:flags.1?true query_id:long error:flags.0?string = Bool;
-

The user enters their payment information as described above and presses the final pay button. -At this moment the Telegram API sends an updateBotPrecheckoutQuery constructor that contains all the available information about the order to the bot. -The bot must reply using messages.setBotPrecheckoutResults within 10 seconds after receiving this update or the transaction is canceled.

-

The bot may return an error if it can‘t process the order for any reason. We highly recommend specifying a reason for failure to complete the order in human readable form (e.g. "Sorry, we’re all out of rubber ducks! Would you be interested in a steel bear instead?"). Telegram will display this reason to the user.

-

5. Checkout

-
keyboardButtonBuy#afd93fbb text:string = KeyboardButton;
-
-keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;
-replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;
-
-messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
-
-message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
-
-updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
-
-payments.paymentReceipt#70c4fe03 flags:# date:int bot_id:long provider_id:long title:string description:string photo:flags.2?WebDocument invoice:Invoice info:flags.0?PaymentRequestedInfo shipping:flags.1?ShippingOption tip_amount:flags.3?long currency:string total_amount:long credentials_title:string users:Vector<User> = payments.PaymentReceipt;
-
----functions---
-
-payments.getPaymentReceipt#2478d1cc peer:InputPeer msg_id:int = payments.PaymentReceipt;
-

In case the bot confirms the order, Telegram requests the payment provider to complete the transaction. If the payment information was entered correctly and the payment goes through, the Telegram API will modify the invoice message and send a service message as described below. Once your bot receives this message, it should proceed with delivering the goods or services purchased by the user.

-

If all is OK, the user receives a payments.paymentResult in reply to the payments.sendPaymentForm query, containing info about the updated invoice message in the form of an updateEditMessage.

-

The invoice message will be updated as follows: the attached messageMediaInvoice will now have a receipt_msg_id field. -Clients should treat invoice messages with a receipt_msg_id field as receipt messages, locally modifying the label of the keyboardButtonBuy button to a localized version of the word Receipt. -From this point, clicking on the Receipt button should trigger a call to payments.getPaymentReceipt, providing the receipt_msg_id to the msg_id field, which will return info about the transaction.

-

The payment will also generate one service message of type messageActionPaymentSent or messageActionPaymentSentMe, replying to the invoice. -For bots, the service message will be of type messageActionPaymentSentMe, for users it will be a messageActionPaymentSent.

-
messageActionPaymentSentMe#8f31b327 flags:# currency:string total_amount:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string charge:PaymentCharge = MessageAction;
-messageActionPaymentSent#40699cd0 currency:string total_amount:long = MessageAction;
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/pfs.html b/data/core.telegram.org/api/pfs.html deleted file mode 100644 index 7f03a3eeee..0000000000 --- a/data/core.telegram.org/api/pfs.html +++ /dev/null @@ -1,138 +0,0 @@ - - - - - Perfect Forward Secrecy - - - - - - - - - - - - - -
- -
-
-
- -

Perfect Forward Secrecy

- -
Related articles
-

-
-

This article is about Perfect Forward Secrecy in cloud chats, see also PFS in Secret Chats.

-
-
-

Telegram supports Perfect Forward Secrecy (PFS).

-

To make this possible, the client generates a permanent authorization key using p_q_inner_data and a temporary key using p_q_inner_data_temp. (See Creating an Authorization Key for more info.) These 2 operations may be done in parallel and even using the same connection. The client must save an expires_at unix timestamp expires_at = time + expires_in.

-

Important: in order to achieve PFS, the client must never use the permanent auth_key_id directly. Every message that is sent to MTProto, must be encrypted by a temp_auth_key_id, that was bound to the perm_auth_key_id.

-

An unbound temp_auth_key_id may only be used with the following methods:

- -

In order to bind a temporary authorization key to the permanent key the client creates a special binding message and executes the auth.bindTempAuthKey method using temp_auth_key. Once auth.bindTempAuthKey has been executed successfully, the client may signUp / signIn using other auth.* methods and continue using the API as usual; the client must also rewrite client info using initConnection after each binding. Each permanent key may only be bound to one temporary key at a time, binding a new temporary key overwrites the previous one.

-

Once the temporary key expires, the client needs to generate a new temporary key using p_q_inner_data_temp. Then it needs to re-bind that new temporary key to the initial permanent key. A new key can also be generated in advance, so that the client has a new key ready by the time the old one has expired.

-

For additional security, the client can store the temporary authorization key in RAM only and never save it in persistent storage.

-

A temporary authorization key may expire at any moment before expires_at, since such keys are also stored only in the RAM on the server-side. Be prepared to handle resulting MTProto errors correctly (non-existent auth_key_id results in a 404 error).

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/pin.html b/data/core.telegram.org/api/pin.html deleted file mode 100644 index b5528f5a39..0000000000 --- a/data/core.telegram.org/api/pin.html +++ /dev/null @@ -1,149 +0,0 @@ - - - - - Pinned messages - - - - - - - - - - - - - -
- -
-
-
- -

Pinned messages

- -
- -

Telegram allows pinning multiple messages on top of a specific chat.

-
message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
-
-updatePinnedMessages#ed85eab5 flags:# pinned:flags.0?true peer:Peer messages:Vector<int> pts:int pts_count:int = Update;
-updatePinnedChannelMessages#5bb98608 flags:# pinned:flags.0?true channel_id:long messages:Vector<int> pts:int pts_count:int = Update;
-
----functions---
-
-messages.updatePinnedMessage#d2aaf7ec flags:# silent:flags.0?true unpin:flags.1?true pm_oneside:flags.2?true peer:InputPeer id:int = Updates;
-messages.unpinAllMessages#f025bc8b peer:InputPeer = messages.AffectedHistory;
-
-messages.getMessages#63c66506 id:Vector<InputMessage> = messages.Messages;
-channels.getMessages#ad8c9a23 channel:InputChannel id:Vector<InputMessage> = messages.Messages;
-

The messages.updatePinnedMessage method can be used to pin or unpin a specific message in an arbitrary chat.
-The unpin flags specifies whether to unpin or pin the message, and pm_oneside specifies whether the message should only be pinned on the local side of a one-to-one chat.

-

messages.unpinAllMessages can be used to unpin all messages in a chat.

-

When (un)pinning messages, a updatePinnedMessages or updatePinnedChannelMessages update will be emitted, containing IDs of pinned or unpinned messages.

-

Pinned messages will also have the will also have the pinned flag of message set.

-

Getting pinned messages

-
userFull#d697ff05 flags:# blocked:flags.0?true phone_calls_available:flags.4?true phone_calls_private:flags.5?true can_pin_message:flags.7?true has_scheduled:flags.12?true video_calls_available:flags.13?true user:User about:flags.1?string settings:PeerSettings profile_photo:flags.2?Photo notify_settings:PeerNotifySettings bot_info:flags.3?BotInfo pinned_msg_id:flags.6?int common_chats_count:int folder_id:flags.11?int ttl_period:flags.14?int theme_emoticon:flags.15?string = UserFull;
-chatFull#4dbdc099 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:long about:string participants:ChatParticipants chat_photo:flags.2?Photo notify_settings:PeerNotifySettings exported_invite:flags.13?ExportedChatInvite bot_info:flags.3?Vector<BotInfo> pinned_msg_id:flags.6?int folder_id:flags.11?int call:flags.12?InputGroupCall ttl_period:flags.14?int groupcall_default_join_as:flags.15?Peer theme_emoticon:flags.16?string = ChatFull;
-channelFull#e9b27a17 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector<string> groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string = ChatFull;
-
-inputMessagesFilterPinned#1bb00451 = MessagesFilter;
-
----functions---
-
-messages.search#a0fda762 flags:# peer:InputPeer q:string from_id:flags.0?InputPeer top_msg_id:flags.1?int filter:MessagesFilter min_date:int max_date:int offset_id:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
-

The pinned_msg_id of userFull, chatFull, channelFull contains the ID of only the latest pinned message.
-To obtain a full list, use messages.search with inputMessagesFilterPinned filter.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/poll.html b/data/core.telegram.org/api/poll.html deleted file mode 100644 index e12f1e5996..0000000000 --- a/data/core.telegram.org/api/poll.html +++ /dev/null @@ -1,199 +0,0 @@ - - - - - Poll - - - - - - - - - - - - - -
- -
-
-
- -

Poll

- -
- -

Telegram allows sending polls and quizes, that can be voted on by thousands, if not milions of users in chats and channels.

-

Sending a poll

-
pollAnswer#6ca9c2e9 text:string option:bytes = PollAnswer;
-
-poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;
-
-inputMediaPoll#f94e5f1 flags:# poll:Poll correct_answers:flags.0?Vector<bytes> solution:flags.1?string solution_entities:flags.1?Vector<MessageEntity> = InputMedia;
-
----functions---
-
-messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-

To send a poll in a chat, call messages.sendMedia, providing an inputMediaPoll:

-
    -
  • -

    poll is the actual poll constructor, containing:

    -
      -
    • question - The poll title, aka the poll's title
    • -
    • answers - A vector of possible answers (2-10), each with a visible title text , and a unique option identifier (1-100 bytes)
    • -
    • closed - Whether the poll is closed
    • -
    • public_voters - Whether cast votes are publicly visible to all users (non-anonymous poll)
    • -
    • multiple_choice - Whether multiple options can be chosen as answer
    • -
    • quiz - Whether this is a quiz with correct answer IDs specified in inputMediaPoll.correct_answers
    • -
    • close_period - Amount of time in seconds the poll will be active after creation, 5-600. Can't be used together with close_date .
    • -
    • close_date - Point in time (Unix timestamp) when the poll will be automatically closed. Must be at least 5 and no more than 600 seconds in the future; can't be used together with close_period .
      -These last two parameters are exactly the same, except that one uses absolute, the other relative unixtime.
    • -
    -
  • -
  • -

    correct_answers - For quizes, option ID of the only correct answer

    -
  • -
  • -

    solution - Text that is shown when a user chooses an incorrect answer or taps on the lamp icon in a quiz-style poll, 0-200 characters with at most 2 line feeds

    -
  • -
  • -

    solution_entities - Styled text message entities for the solution explanation

    -
  • -
-

In order to prematurely close the poll, preventing further votes, use messages.editMessage, setting the poll.closed flag to true.

-

Voting in polls

-
pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;
-
-pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;
-
-poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;
-
-messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
-
-updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;
-
----functions---
-
-messages.sendVote#10ea6184 peer:InputPeer msg_id:int options:Vector<bytes> = Updates;
-

When receiving a message with a messageMediaPoll, users can vote in it using messages.sendVote, specifying the chosen option identifiers.

-

The method will return an updateMessagePoll, containing an updated pollResults constructor, with the chosen flag set on the options we chose, and the correct flag set on the correct answers.

-

Getting poll votes

-
pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;
-
-pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;
-
-updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;
-
----functions---
-
-messages.getPollResults#73bb643b peer:InputPeer msg_id:int = Updates;
-

Regularly, if new users have voted in polls available to the user, they will receive an updateMessagePoll, with updated pollResults.

-

The same constructor can also be fetched manually using messages.getPollResults.

-

Getting poll voters in non-anonymous polls

-
messageUserVote#34d247b4 user_id:long option:bytes date:int = MessageUserVote;
-messageUserVoteInputOption#3ca5b0ec user_id:long date:int = MessageUserVote;
-messageUserVoteMultiple#8a65e557 user_id:long options:Vector<bytes> date:int = MessageUserVote;
-
-messages.votesList#823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList; 
-
-updateMessagePollVote#106395c9 poll_id:long user_id:long options:Vector<bytes> qts:int = Update;
-
----functions---
-
-messages.getPollVotes#b86e380e flags:# peer:InputPeer id:int option:flags.0?bytes offset:flags.1?string limit:int = messages.VotesList; 
-

messages.getPollVotes can be used to get poll results for non-anonymous polls, to see how each user voted for a poll option.
-Bots will also receive an updateMessagePollVote every time a user their answer in a non-anonymous poll. Bots receive new votes only in polls that were sent by the bot itself.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/push-updates.html b/data/core.telegram.org/api/push-updates.html deleted file mode 100644 index 0deaeb8156..0000000000 --- a/data/core.telegram.org/api/push-updates.html +++ /dev/null @@ -1,1009 +0,0 @@ - - - - - Handling PUSH-notifications - - - - - - - - - - - - - -
- -
-
-
- -

Handling PUSH-notifications

- -
- -

Configuring the application

-

To be able to send APNS notifications to Apple servers or GCM notifications to Google servers, application certificates (APNS) or an application key (GCM) must be specified in the application settings.

-

Subscribing to notifications

-

To subscribe to notifications, the client must invoke the account.registerDevice query, passing in token_type and token as parameters that identify the current device. It is useful to repeat this query at least once every 24 hours or when restarting the application. Use account.unregisterDevice to unsubscribe.

-

The following modes are supported:

-
    -
  • 1 - APNS (device token for apple push)
  • -
  • 2 - FCM (firebase token for google firebase)
  • -
  • 3 - MPNS (channel URI for microsoft push)
  • -
  • 4 - Deprecated: Simple push (endpoint for firefox's simple push API)
  • -
  • 5 - Ubuntu phone (token for ubuntu push)
  • -
  • 6 - Blackberry (token for blackberry push)
  • -
  • 7 - MTProto separate session
  • -
  • 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 with the following keys:

-
    -
  • endpoint: Absolute URL exposed by the push service where the application server can send push messages
  • -
  • keys: P-256 elliptic curve Diffie-Hellman parameters in the following object
      -
    • p256dh: Base64url-encoded P-256 elliptic curve Diffie-Hellman public key
    • -
    • auth: Base64url-encoded authentication secret
    • -
    -
  • -
-

Notification encryption

-

For FCM and APNS VoIP, an optional encryption key used to encrypt push notifications can be passed to account.registerDevice (secret). This key (auth_key) is used to encrypt the payloads using MTProto v2.

-

The FCM payload will be a JSON payload, containing a p field with the base64-encoded encrypted MTProto payload. After decryption, the result will be a JSON object, prefixed by a 32-bit little-endian integer with the length of the JSON payload. As usual, make sure to follow all security checks as described in the MTProto docs.

-

Example implementation.

-

As mentioned above, payloads can also be encrypted using P-256 Elliptic Curve Diffie-Hellman when using web push.

-

Notification structure

-

An (optionally encrypted) notification is provided as a JSON object in the following format:

-
{
-  "data": {
-    "loc_key": "CHAT_MESSAGE_CONTACT",
-    "loc_args": ["John Doe", "My magical group", "Contact Exchange"],
-    "user_id": 14124122,
-    "custom": {
-      "chat_id": 241233,
-      "msg_id": 123
-    },
-    "sound": "sound1.mp3",
-  }
-}
-

Each notification has several parameters that describe it.

-

Notification type

-

data.loc_key - A string literal in the form /[A-Z_0-9]+/, which summarizes the notification. For example, CHAT_MESSAGE_TEXT.

-

Notification text arguments

-

data.loc_args - A list or arguments which, when inserted into a template, produce a readable notification.

-

Custom parameters

-

data.custom - Parameters which are be passed into the application when a notification is opened.

-

Sound

-

data.sound - The name of an audio file to be played.

-

User id

-

data.user_id - ID of the account to which the PUSH notification should be delivered, in case of clients with multiple accounts active and running.

-

Processing notifications

-

In principle, data.loc_key, data.custom, and an Internet connection are sufficient to generate a notification. Obviously, if possible, when generating a visual notification you need not use all of the transmitted data and may rely on the information already stored on the client. But if a user or a chat is not cached locally, the values passed in loc_args may also be used. data.user_id is the ID of the account to which the PUSH notification should be delivered, in case of clients with multiple accounts active and running.

-

Service notifications

-

The following notifications can be used to update app settings.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TypeExtra custom argumentsDescription
DC_UPDATEdc - number of the data-center
addr - server address with port number in the format 111.112.113.114:443
In case the client gets this notification, it is necessary to add the received server address to the list of possible addresses. In case the address of the first DC was passed (dc=1), it is recommended to call it immediately using help.getConfig to update dc-configuration.
MESSAGE_DELETEDchannel_id: For channels and supergroups, Channel/supergroup identifier
chat_id: For chats, Chat identifier
from_id: For PMs, Author identifier
messages: Comma-separated IDs of messages that were deleted
Messages were deleted, remove multiple notifications for this chat
READ_HISTORYchannel_id: For channels and supergroups, Channel/supergroup identifier
chat_id: For chats, Chat identifier
from_id: For PMs, Author identifier
max_id: Maximum ID of read messages
Message history was read, remove multiple notifications for this chat
GEO_LIVE_PENDING Any of the live locations currently being shared should be updated
SESSION_REVOKE Logout and remove DB for specified session by data.user_id, only apply if coming from an MTProto-encrypted payload
MESSAGE_MUTED Sent rarely, every 10th message in chats or once per 15 sec in PM, to update badge or download messages
-

Possible Notifications

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TypeTemplate exampleArgumentsExtra custom arguments
AUTH_REGIONNew login from unrecognized device {1}, location: {2}1. Device name
2. Location
 
AUTH_UNKNOWNNew login from unrecognized device {1}1. Device name 
CHANNEL_MESSAGES{1} posted an album1. Message authorattachb64: Base64-encoded version of the attached media (related to the first message)
channel_id: Channel/supergroup identifier (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHANNEL_MESSAGE_AUDIO{1} posted a voice message1. Message authorattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_CONTACT{1} posted a contact {2}1. Message author
2. Contact name
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_DOC{1} posted a file1. Message authorattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_DOCS{1} posted {2} files1. Channel name
2. Number of documents that were posted
attachb64: Base64-encoded version of the attached media (related to the first message)
channel_id: Channel/supergroup identifier (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHANNEL_MESSAGE_FWDS{1} posted {2} forwarded messages1. Message author
2. Number of forwarded messages
attachb64: Base64-encoded version of the attached media (related to the first message)
channel_id: Channel/supergroup identifier (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHANNEL_MESSAGE_GAME{1} invited you to play {2}1. Message author
2. Game name
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_GAME_SCORE{1} scored {3} in game {2}1. User
2. Game name
3. Score
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_GEO{1} posted a location1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_GEOLIVE{1} posted a live location1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_GIF{1} posted a GIF1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_NOTEXT{1} posted a message1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_PHOTO{1} posted a photo1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_PHOTOS{1} posted {2} photos1. Channel name
2. Number of photos that was sent
attachb64: Base64-encoded version of the attached media (related to the first message)
channel_id: Channel/supergroup identifier (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHANNEL_MESSAGE_PLAYLIST{1} posted {2} music files1. Channel name
2. Number of audio files that were posted
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_POLL{1} posted a poll {2}1. Channel name
2. Poll name
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_QUIZ{1} posted a quiz {2}1. Channel name
2. Quiz name
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_ROUND{1} posted a video message1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_STICKER{1} posted a {2} sticker1. Channel name
2. Sticker emoji
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_TEXT{1}: {2}1. Channel name
2. Message body
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_VIDEO{1} posted a video1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_VIDEOS{1} posted {2} videos1. Channel name
2. Number of videos that were posted
attachb64: Base64-encoded version of the attached media (related to the first message)
channel_id: Channel/supergroup identifier (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHAT_ADD_MEMBER{1} invited {3} to the group {2}1. Message author
2. Chat name
3. New participant name
chat_id: chat identifier
CHAT_ADD_YOU{1} invited you to the group {2}1. User name
2. Group name
chat_id: chat identifier
CHAT_CREATED{1} invited you to the group {2}1. Message author
2. Chat name
chat_id: chat identifier
CHAT_DELETE_MEMBER{1} removed {3} from the group {2}1. Message author
2. Chat name
3. Dropped participant name
chat_id: chat identifier
CHAT_DELETE_YOU{1} removed you from the group {2}1. Message author
2. Chat name
chat_id: chat identifier
CHAT_JOINED{1} joined the group {2}1. User name
2. Group name
chat_id: chat identifier
CHAT_LEFT{1} left the group {2}1. Message author
2. Chat name
chat_id: chat identifier
CHAT_MESSAGES{1} sent an album to the group {2}1. User name
2. Group name
chat_from_id: Message author identifier
chat_id: chat identifier
mention: Whether the user was mentioned in the message
CHAT_MESSAGE_AUDIO{1} sent a voice message to the group {2}1. Message author
2. Chat name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_CONTACT{1} shared a contact {3} in the group {2}1. User name
2. Group name
3. Contact name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_DOC{1} sent a file to the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_DOCS{1} sent {3} files to the group {2}1. User name
2. Group name
3. Number of documents that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
chat_id: Chat identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHAT_MESSAGE_FWDS{1} forwarded {3} messages to the group {2}1. User name
2. Group name
3. Number of messages that were forwarded
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
chat_id: Chat identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHAT_MESSAGE_GAME{1} invited the group {2} to play {3}1. User name
2. Group name
3. Game name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_GAME_SCORE{1} scored {4} in game {3} in the group {2}1. User name
2. Group name
3. Game name
4. Score
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_GEO{1} sent a location to the group {2}1. Message author
2. Chat name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_GEOLIVE{1} shared a live location with the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_GIF{1} sent a GIF to the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_INVOICE{1} sent an invoice to the group {2} for {3}1. User name
2. Group name
3. Product name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_NOTEXT{1} sent a message to the group {2}1. Message author
2. Chat name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_PHOTO{1} sent a photo to the group {2}1. Message author
2. Chat name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_PHOTOS{1} sent {3} photos to the group {2}1. User name
2. Group name
3. Number of photos that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
chat_id: Chat identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHAT_MESSAGE_PLAYLIST{1} sent {3} music files to the group {2}1. User name
2. Group name
3. Number of audio files that were sent
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_POLL{1} sent a poll {3} to the group {2}1. User name
2. Group name
3. Poll name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_QUIZ{1} sent a quiz {3} to the group {2}1. User name
2. Group name
3. Quiz name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_ROUND{1} sent a video message to the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_STICKER{1} sent a {3} sticker to the group {2}1. User name
2. Group name
3. Sticker emoji
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_TEXT{1} @ {2}: {3}1. Message author
2. Chat name
3. Message body
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_VIDEO{1} sent a video to the group {2}1. Message author
2. Chat name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_VIDEOS{1} sent {3} videos to the group {2}1. User name
2. Group name
3. Number of videos that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
chat_id: Chat identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHAT_PHOTO_EDITED{1} changed the group photo for {2}1. Message author
2. Chat name
chat_from_id: Message author identifier
chat_id: chat identifier
msg_id: ID of the message
CHAT_RETURNED{1} returned to the group {2}1. Message author
2. Chat name
chat_id: chat identifier
CHAT_TITLE_EDITED{1} renamed the group {2}1. User name
2. Group name
chat_id: chat identifier
CHAT_VOICECHAT_END{1} ended a voice chat in the group {2}1. User name
2. Chat name
 
CHAT_VOICECHAT_INVITE{1} invited {3} to a voice chat in the group {2}1. User name
2. Chat name
3. Invited users
 
CHAT_VOICECHAT_INVITE_YOU{1} invited you to a voice chat in the group {2}1. User name
2. Chat name
 
CHAT_VOICECHAT_START{1} started a voice chat in the group {2}1. User name
2. Chat name
 
CONTACT_JOINED{1} joined Telegram!1. Contact namecontact_id: contact identifier
ENCRYPTED_MESSAGEYou have a new message encryption_id: secret chat identifier
random_id: message identifier
ENCRYPTION_ACCEPTYou have a new message encryption_id: secret chat identifier
ENCRYPTION_REQUESTYou have a new message encryption_id: secret chat identifier
LOCKED_MESSAGEYou have a new message  
MESSAGES{1} sent you an album1. User namefrom_id: author identifier
MESSAGE_ANNOUNCEMENT{1}1. Announcementannouncement: Announcement: roughly equivalent to a message received from the service notifications (Telegram Notifications, id 777000) user, but must be delivered via push notifications, without contacting the API.
MESSAGE_AUDIO{1} sent you a voice message1. Message authorattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_CONTACT{1} shared a contact {2} with you1. User name
2. Contact name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_DOC{1} sent you a file1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_DOCS{1} sent you {2} files1. User name
2. Number of documents that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
from_id: Author identifier (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
MESSAGE_FWDS{1} forwarded you {2} messages1. User name
2. Number of messages that were forwarded
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
from_id: Author identifier (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
MESSAGE_GAME{1} invited you to play {2}1. User name
2. Game name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_GAME_SCORE{1} scored {3} in game {2}1. User name
2. Game name
3. Score
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_GEO{1} sent you a location1. Message authorattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_GEOLIVE{1} sent you a live location1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_GIF{1} sent you a GIF1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_INVOICE{1} sent you an invoice for {2}1. User name
2. Product
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_NOTEXT{1} sent you a message1. Message authorattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_PHOTO{1} sent you a photo1. Message authorattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_PHOTOS{1} sent you {2} photos1. User name
2. Number of photos that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
from_id: Author identifier (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
MESSAGE_PHOTO_SECRET{1} sent you a self-destructing photo1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_PLAYLIST{1} sent you {2} music files1. User name
2. Number of audio files that were sent
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_POLL{1} sent you a poll {2}1. User name
2. Poll name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_QUIZ{1} sent you a quiz {2}1. User name
2. Quiz name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_ROUND{1} sent you a video message1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_SCREENSHOT{1} took a screenshot1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_STICKER{1} sent you a {2} sticker1. User name
2. Sticker emoji
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_TEXT{1}: {2}1. Message author
2. Message body
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_VIDEO{1} sent you a video1. Message authorattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_VIDEOS{1} sent you {2} videos1. User name
2. Number of videos that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
from_id: Author identifier (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
MESSAGE_VIDEO_SECRET{1} sent you a self-destructing video1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
PHONE_CALL_MISSEDYou missed a call from {1}1. User name 
PHONE_CALL_REQUEST{1} is calling you!1. User namecall_ah: Call access hash
call_id: Call ID
PINNED_AUDIO{1} pinned a voice message1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_AUDIO{1} pinned a voice message in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_CONTACT{1} pinned a contact {2}1. User name
2. Contact name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_CONTACT{1} pinned a contact {3} in the group {2}1. User name
2. Group name
3. Contact name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_DOC{1} pinned a file1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_DOC{1} pinned a file in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GAME{1} pinned a game1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GAME{1} pinned a game in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GAME_SCORE{1} pinned a game score1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GAME_SCORE{1} pinned a game score in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GEO{1} pinned a map1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GEO{1} pinned a map in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GEOLIVE{1} pinned a live location1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GEOLIVE{1} pinned a live location in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GIF{1} pinned a GIF1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GIF{1} pinned a GIF in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_INVOICE{1} pinned an invoice1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_INVOICE{1} pinned an invoice in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_NOTEXT{1} pinned a message1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_NOTEXT{1} pinned a message in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_PHOTO{1} pinned a photo1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_PHOTO{1} pinned a photo in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_POLL{1} pinned a poll {2}1. User name
2. Poll name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_POLL{1} pinned a poll {3} in the group {2}1. User name
2. Group name
3. Poll name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_QUIZ{1} pinned a quiz {2}1. User name
2. Quiz name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_QUIZ{1} pinned a quiz {3} in the group {2}1. User name
2. Group name
3. Quiz name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_ROUND{1} pinned a video message1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_ROUND{1} pinned a video message in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_STICKER{1} pinned a {2} sticker1. User name
2. Sticker emoji
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_STICKER{1} pinned a {3} sticker in the group {2}1. User name
2. Group name
3. Sticker emoji
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_TEXT{1} pinned "{2}"1. User name
2. Message body
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_TEXT{1} pinned "{3}" in the group {2}1. User name
2. Group name
3. Message body
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_VIDEO{1} pinned a video1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_VIDEO{1} pinned a video in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/qr-login.html b/data/core.telegram.org/api/qr-login.html deleted file mode 100644 index 7995ef9f72..0000000000 --- a/data/core.telegram.org/api/qr-login.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - Login via QR code - - - - - - - - - - - - - -
- -
-
-
- -

Login via QR code

- -
- -

QR code login flow.

-

Related TL schema:

-
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
-auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;
-auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;
-
-updateLoginToken#564fe691 = Update;
-
-authorization#ad01d61d flags:# current:flags.0?true official_app:flags.1?true password_pending:flags.2?true hash:long device_model:string platform:string system_version:string api_id:int app_name:string app_version:string date_created:int date_active:int ip:string country:string region:string = Authorization;
-
----functions---
-
-auth.exportLoginToken#b7e085fe api_id:int api_hash:string except_ids:Vector<long> = auth.LoginToken;
-auth.acceptLoginToken#e894ad4d token:bytes = Authorization;
-auth.importLoginToken#95ac5ce4 token:bytes = auth.LoginToken;
-

Exporting a login token

-

First of all, auth.exportLoginToken must be called by the app that wants to log in to an existing Telegram account.
-The method will return an auth.loginToken constructor, containing a binary login token and an expiry date (usually 30 seconds).

-

The login token must be encoded using base64url, embedded in a tg://login?token=base64encodedtoken URL and shown in the form of a QR code to the user.
-After the expiration of the current QR code, the auth.exportLoginToken method must be recalled and a new QR code must be generated automatically.

-

Accepting a login token

-

In order to log in, the QR code must be scanned and accepted by an already logged-in Telegram app using auth.acceptLoginToken.
-The token must be extracted from the tg://login URI and base64url-decoded before using it in the method.

-

Possible errors returned by the method are:

-
    -
  • 400 - AUTH_TOKEN_INVALID, an invalid authorization token was provided
  • -
  • 400 - AUTH_TOKEN_EXPIRED, the provided authorization token has expired and the updated QR-code must be re-scanned
  • -
  • 400 - AUTH_TOKEN_ALREADY_ACCEPTED, the authorization token was already used
  • -
-

The method will return an authorization object, containing info about the app and session that we just authorized.

-

Confirming (importing) the login token

-

After the logged-in app calls auth.acceptLoginToken and accepts the login token, the app that is trying to login will receive an updateLoginToken update, which should trigger a second call to the auth.exportLoginToken method.

-

This second call should then return an auth.loginTokenSuccess constructor, indicating successful login, essentially allowing further authorized interaction with the API.

-

If, however, there is a DC mismatch between the two apps, auth.loginTokenMigrateTo is returned instead, to which the app that is trying to login should respond by calling auth.importLoginToken with the specified token, to the specified DC.

-

This call should then finally return a auth.loginTokenSuccess constructor.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/recent-actions.html b/data/core.telegram.org/api/recent-actions.html deleted file mode 100644 index d36347c2d5..0000000000 --- a/data/core.telegram.org/api/recent-actions.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - Admin log - - - - - - - - - - - - - -
- -
-
-
- -

Admin log

- -
- -

Both supergroups and channels offer a so-called admin log, a log of recent relevant supergroup and channel actions, like the modification of group/channel settings or information on behalf of an admin, user kicks and bans, and more.

-
channelAdminLogEventActionChangeTitle#e6dfb825 prev_value:string new_value:string = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeAbout#55188a2e prev_value:string new_value:string = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeUsername#6a4afc38 prev_value:string new_value:string = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangePhoto#434bd2af prev_photo:Photo new_photo:Photo = ChannelAdminLogEventAction;
-channelAdminLogEventActionToggleInvites#1b7907ae new_value:Bool = ChannelAdminLogEventAction;
-channelAdminLogEventActionToggleSignatures#26ae0971 new_value:Bool = ChannelAdminLogEventAction;
-channelAdminLogEventActionUpdatePinned#e9e82c18 message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionEditMessage#709b2405 prev_message:Message new_message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionDeleteMessage#42e047bb message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantJoin#183040d3 = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantLeave#f89777f2 = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantInvite#e31c34d8 participant:ChannelParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantToggleBan#e6d83d7e prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantToggleAdmin#d5676710 prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeStickerSet#b1c3caa7 prev_stickerset:InputStickerSet new_stickerset:InputStickerSet = ChannelAdminLogEventAction;
-channelAdminLogEventActionTogglePreHistoryHidden#5f5c95f1 new_value:Bool = ChannelAdminLogEventAction;
-channelAdminLogEventActionDefaultBannedRights#2df5fc0a prev_banned_rights:ChatBannedRights new_banned_rights:ChatBannedRights = ChannelAdminLogEventAction;
-channelAdminLogEventActionStopPoll#8f079643 message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeLinkedChat#50c7ac8 prev_value:long new_value:long = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeLocation#e6b76ae prev_value:ChannelLocation new_value:ChannelLocation = ChannelAdminLogEventAction;
-channelAdminLogEventActionToggleSlowMode#53909779 prev_value:int new_value:int = ChannelAdminLogEventAction;
-
-channelAdminLogEvent#1fad68cd id:long date:int user_id:long action:ChannelAdminLogEventAction = ChannelAdminLogEvent;
-
-channels.adminLogResults#ed8af74d events:Vector<ChannelAdminLogEvent> chats:Vector<Chat> users:Vector<User> = channels.AdminLogResults;
-
-channelAdminLogEventsFilter#ea107ae4 flags:# join:flags.0?true leave:flags.1?true invite:flags.2?true ban:flags.3?true unban:flags.4?true kick:flags.5?true unkick:flags.6?true promote:flags.7?true demote:flags.8?true info:flags.9?true settings:flags.10?true pinned:flags.11?true edit:flags.12?true delete:flags.13?true group_call:flags.14?true invites:flags.15?true = ChannelAdminLogEventsFilter;
-
----functions---
-
-channels.getAdminLog#33ddf480 flags:# channel:InputChannel q:string events_filter:flags.0?ChannelAdminLogEventsFilter admins:flags.1?Vector<InputUser> max_id:long min_id:long limit:int = channels.AdminLogResults;
-

channels.getAdminLog can be used to list recent admin activity.
-A channelAdminLogEventsFilter can be used to filter out actions of a certain type, and the admins field can be used to show only actions by certain admins.
-q can also be used to filter only logs matching a query string.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/rights.html b/data/core.telegram.org/api/rights.html deleted file mode 100644 index a581b8cf79..0000000000 --- a/data/core.telegram.org/api/rights.html +++ /dev/null @@ -1,133 +0,0 @@ - - - - - Admin, banned, default rights - - - - - - - - - - - - - -
- -
-
-
- -

Admin, banned, default rights

- -
- -

Channels and supergroups allow setting granular permissions both for admins and specific users. -Channels, supergroups and legacy groups also allow setting global granular permissions for users.

-

They can be modified as follows:

-

Admin rights

-

channels.editAdmin can be used to modify the admin rights of a user in a channel or supergroup. -Legacy groups do not allow setting granular admin permissions, messages.editChatAdmin has to be used, instead.

-

Permissions are defined by the chatAdminRights constructor, some admin rights can only be used for channels, others both for channels and supergroups (see the constructor page).

-

Banned rights

-

channels.editBanned can be used to modify the rights of a user in a channel or supergroup, to ban/kick a user from the group, or restrict the user from doing certain things. -Legacy groups do not allow setting granular user permissions for single users, single users can only be removed from groups using messages.deleteChatUser: however, setting global granular permissions with legacy groups is supported.

-

Permissions are defined by the chatBannedRights constructor, for more info see the constructor page.

-

Default rights

-

messages.editChatDefaultBannedRights can be used to modify the rights of all users in a channel, supergroup or legacy group, to restrict them from doing certain things.

-

Permissions are defined by the chatBannedRights constructor: all flags can be used except for view_messages, for more info see the constructor page.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/scheduled-messages.html b/data/core.telegram.org/api/scheduled-messages.html deleted file mode 100644 index f1e0fdf7c1..0000000000 --- a/data/core.telegram.org/api/scheduled-messages.html +++ /dev/null @@ -1,156 +0,0 @@ - - - - - Scheduled messages - - - - - - - - - - - - - -
- -
-
-
- -

Scheduled messages

- -

Telegram allows scheduling messages.

-
message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
-
-updateNewScheduledMessage#39a51dfb message:Message = Update;
-updateDeleteScheduledMessages#90866cee peer:Peer messages:Vector<int> = Update;
-
----functions---
-
-messages.sendMessage#520c3870 flags:# no_webpage:flags.1?true silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-
-messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-

To schedule a message, simply provide a future unixtime in the schedule_date flag of messages.sendMessage or messages.sendMedia.

-

The specified message or media will be added to a server-side schedule queue for the current chat, and will be automatically sent at the specified time.
-The method call generates the following updates:

-
    -
  • Immediately, an updateNewScheduledMessage, with ID equal to the ID of the message in the schedule queue for the current chat (each PM, chat, supergroup and channel has its own schedule queue and ID sequence).
  • -
  • At schedule_date, an updateNewMessage or updateNewChannelMessage with the from_scheduled flag set, indicating to the sender that the specified scheduled message was sent.
  • -
  • At schedule_date, an updateDeleteScheduledMessages, indicating that the message was flushed from the schedule queue.
  • -
-

If the schedule_date is less than 10 seconds in the future, the message will be sent immediately, generating a normal updateNewMessage/updateNewChannelMessage .

-

Manipulating the schedule queue

-
updateNewScheduledMessage#39a51dfb message:Message = Update;
-updateDeleteScheduledMessages#90866cee peer:Peer messages:Vector<int> = Update;
-
----functions---
-
-messages.getScheduledHistory#f516760b peer:InputPeer hash:long = messages.Messages;
-messages.getScheduledMessages#bdbb0464 peer:InputPeer id:Vector<int> = messages.Messages;
-messages.sendScheduledMessages#bd38850a peer:InputPeer id:Vector<int> = Updates;
-messages.deleteScheduledMessages#59ae2b16 peer:InputPeer id:Vector<int> = Updates;
-
-messages.editMessage#48f71778 flags:# no_webpage:flags.1?true peer:InputPeer id:int message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.15?int = Updates;
-

Clients can manually edit the schedule queue of a certain chat, providing the scheduled message ID obtained from updateNewScheduledMessage.

- -

Modifying scheduled messages will generate an updateNewScheduledMessage with the same ID, and updated information.
-Deleting scheduled messages will generate an updateDeleteScheduledMessages.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/search.html b/data/core.telegram.org/api/search.html deleted file mode 100644 index 7fb69193a6..0000000000 --- a/data/core.telegram.org/api/search.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - Search - - - - - - - - - - - - - -
- -
-
-
- -

Search

- -
- -

Telegram allows applying detailed message filters while looking for messages in chats.

-

Search filters

-
inputMessagesFilterEmpty#57e2f66c = MessagesFilter;
-inputMessagesFilterPhotos#9609a51c = MessagesFilter;
-inputMessagesFilterVideo#9fc00e65 = MessagesFilter;
-inputMessagesFilterPhotoVideo#56e9f0e4 = MessagesFilter;
-inputMessagesFilterDocument#9eddf188 = MessagesFilter;
-inputMessagesFilterUrl#7ef0dd87 = MessagesFilter;
-inputMessagesFilterGif#ffc86587 = MessagesFilter;
-inputMessagesFilterVoice#50f5c392 = MessagesFilter;
-inputMessagesFilterMusic#3751b49e = MessagesFilter;
-inputMessagesFilterChatPhotos#3a20ecb8 = MessagesFilter;
-inputMessagesFilterPhoneCalls#80c99768 flags:# missed:flags.0?true = MessagesFilter;
-inputMessagesFilterRoundVoice#7a7c17a4 = MessagesFilter;
-inputMessagesFilterRoundVideo#b549da53 = MessagesFilter;
-inputMessagesFilterMyMentions#c1f8e69a = MessagesFilter;
-inputMessagesFilterGeo#e7026d0d = MessagesFilter;
-inputMessagesFilterContacts#e062db83 = MessagesFilter;
-inputMessagesFilterPinned#1bb00451 = MessagesFilter;
-
-messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
-
----functions---
-
-messages.search#a0fda762 flags:# peer:InputPeer q:string from_id:flags.0?InputPeer top_msg_id:flags.1?int filter:MessagesFilter min_date:int max_date:int offset_id:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
-
-messages.searchGlobal#4bc6589a flags:# folder_id:flags.0?int q:string filter:MessagesFilter min_date:int max_date:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;
-

When using messages.search or messages.searchGlobal, a certain message filter may be applied.
-This allows the server to filter messages based on a text query, and even on their type, and this feature is often used by graphical clients to implement features like the chat gallery, chat profile pictures and more. -Available filters:

- -

The returned messages.Messages constructors contain parameters for pagination, the messages themselves and two offset_id_offset/count parameters that can be used to display a progress/total counter like photo 134 of 200.
-For example, when displaying the chat photo gallery, we could display a photo ${offset_id_offset} of ${count} indicator on top.

-

Search counters

-
messages.searchCounter#e844ebff flags:# inexact:flags.1?true filter:MessagesFilter count:int = messages.SearchCounter;
-
----functions---
-
-messages.getSearchCounters#732eef00 peer:InputPeer filters:Vector<MessagesFilter> = Vector<messages.SearchCounter>;
-

Chat counters with filters can also be returned without fetching the actual messages, as seen in the schema above.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/sponsored-messages.html b/data/core.telegram.org/api/sponsored-messages.html deleted file mode 100644 index eac5fe507b..0000000000 --- a/data/core.telegram.org/api/sponsored-messages.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - Sponsored messages - - - - - - - - - - - - - -
- -
-
-
- -

Sponsored messages

- -

Related TL schema:

-
sponsoredMessage flags:# random_id:bytes from_id:Peer channel_post:flags.2?int start_param:flags.0?string message:string entities:flags.1?Vector<MessageEntity> = SponsoredMessage;
-messages.sponsoredMessages messages:Vector<SponsoredMessage> chats:Vector<Chat> users:Vector<User> = messages.SponsoredMessages;
-
----functions---
-
-channels.getSponsoredMessages channel:InputChannel = messages.SponsoredMessages;
-channels.viewSponsoredMessage channel:InputChannel random_id:bytes = Bool;
-

Getting sponsored messages

-

Each time the user opens a channel, channels.getSponsoredMessages must be called to receive sponsored messages available for this channel. The result must be cached for 5 minutes.

-
-

More about sponsored messages on Telegram

-
-

Displaying sponsored messages

-

Sponsored messages must be displayed below all other posts in the channel, after the user scrolls futher down, past the last message. The promoted channel or bot specified in the from_id field must be displayed as the author of the message. The message should also contain one of the following buttons at the bottom:

-
    -
  • View Bot — if a bot is being promoted. Tapping the button must open the chat with the bot. If start_param is specified, the app must use the deep linking mechanism to open the bot.
  • -
  • View Channel — if a channel is being promoted. Tapping the button must open the channel.
  • -
  • View Post — if a channel is being promoted and channel_post is specified. Tapping the button must open the particular channel post.
  • -
-

Counting sponsored message views

-

Once the entire text is shown on the screen (excluding the button), channels.viewSponsoredMessage must be called with the random_id of this sponsored message.

-

Testing sponsored messages

-

For the channel https://t.me/SecretAdTestChannel the system will always return a sponsored message: promoting either a channel, a particular message in a channel, or a bot with a start parameter.

-
-

Sponsored messages in third-party apps

-

Telegram continues to grow worldwide, in part thanks to third-party apps using the Telegram API. To cover the increasing costs that come with this growth, Telegram added sponsored messages – a paid privacy-friendly way to promote bots and channels.

-

If their app allows its users to access content from Telegram channels, third-party developers using the Telegam API are required to support and properly display official sponsored messages in their apps by January 1, 2022. Unfortunately, Telegram cannot financially sustain third-party apps that do not display sponsored messages and they will have to be disconnected.

-

Telegram's API usage will continue to be free of charge for all developers. The rules regarding monetization in third-party apps remain the same: developers are allowed to monetize their coding efforts through advertising of their own or other legitimate means, provided that all the methods of monetization used in their apps are prominently mentioned in their app store descriptions.

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/srp.html b/data/core.telegram.org/api/srp.html deleted file mode 100644 index 7ea2c7a89e..0000000000 --- a/data/core.telegram.org/api/srp.html +++ /dev/null @@ -1,307 +0,0 @@ - - - - - Two-factor authentication - - - - - - - - - - - - - -
- -
-
-
- -

Two-factor authentication

- -
- -

Telegram uses the Secure Remote Password protocol version 6a to implement 2FA.

-

Example impementation: tdlib.

-

Checking the password with SRP

-

To login to an account protected by a 2FA password or to perform some other actions (like changing channel owner), you will need to verify the user's knowledge of the current 2FA account password.

-

To do this, first the client needs to obtain SRP parameters and the KDF algorithm to use to check the validity of the password via account.getPassword method. For now, only the passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow algorithm is supported, so we'll only explain that.

-

Then, after the user provides a password, the client should generate an InputCheckPasswordSRP object using SRP and a specific KDF algorithm as shown below and pass it to appropriate method (e.g. auth.checkPassword in case of authorization).

-

This extension of the SRP protocol uses the password-based PBKDF2 with 100000 iterations using sha512 (PBKDF2HMACSHA512iter100000). -PBKDF2 is used to additionally rehash the x parameter, obtained using a method similar to the one described in RFC 2945 (H(s | H ( I | password | I) | s) instead of H(s | H ( I | ":" | password)) (see below).

-

Here, | denotes concatenation and + denotes the arithmetical operator +. -In all cases where concatenation of numbers passed to hashing functions is done, the numbers must be used in big-endian form, padded to 2048 bits; all maths is modulo p. -Instead of I, salt1 will be used (see SRP protocol). -Instead of s, salt2 will be used (see SRP protocol).

-

The main hashing function H is sha256:

-
    -
  • H(data) := sha256(data)
  • -
-

The salting hashing function SH is defined as follows:

-
    -
  • SH(data, salt) := H(salt | data | salt)
  • -
-

The primary password hashing function is defined as follows:

-
    -
  • PH1(password, salt1, salt2) := SH(SH(password, salt1), salt2)
  • -
-

The secondary password hashing function is defined as follows:

-
    -
  • PH2(password, salt1, salt2) := SH(pbkdf2(sha512, PH1(password, salt1, salt2), salt1, 100000), salt2)
  • -
-

Client-side, the following parameters are extracted from the passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow object, contained in the account.password object.

-
    -
  • -

    g := algo.g

    -
  • -
  • -

    p := algo.p -The client is expected to check whether p is a safe 2048-bit prime (meaning that both p and (p-1)/2 are prime, and that 2^2047 < p < 2^2048), and that g generates a cyclic subgroup of prime order (p-1)/2, i.e. is a quadratic residue mod p. Since g is always equal to 2, 3, 4, 5, 6 or 7, this is easily done using quadratic reciprocity law, yielding a simple condition on p mod 4g -- namely, p mod 8 = 7 for g = 2; p mod 3 = 2 for g = 3; no extra condition for g = 4; p mod 5 = 1 or 4 for g = 5; p mod 24 = 19 or 23 for g = 6; and p mod 7 = 3, 5 or 6 for g = 7. After g and p have been checked by the client, it makes sense to cache the result, so as to avoid repeating lengthy computations in future. This cache might be shared with one used for Authorization Key generation.

    -

    If the client has an inadequate random number generator, it makes sense to use the secure_random of account.password as additional seed.

    -
  • -
  • -

    password := (user-provided password)

    -
  • -
  • -

    salt1 := algo.salt1

    -
  • -
  • -

    salt2 := algo.salt2

    -
  • -
  • -

    g_b := srp_B -srp_B and srp_id are extracted from the account.password object.

    -
  • -
-

The k parameter is generated, both on client and server:

-
    -
  • k := H(p | g)
  • -
-

The shared param u is generated: the client does this, and the server does the same with the g_a we will send him later (see below)

-
    -
  • u := H(g_a | g_b)
  • -
-

The final parameters are generated client-side only:

-
    -
  • x := PH2(password, salt1, salt2)
  • -
  • v := pow(g, x) mod p
  • -
-

The server already has v, from when we set the password.

-

A final shared param is generated, for commodity:

-
    -
  • k_v := (k * v) mod p
  • -
-

Finally, the key exchange process starts on both parties.

-

The client computes a 2048-bit number a (using sufficient entropy or the server’s random; see above) and generates:

-
    -
  • g_a := pow(g, a) mod p.
  • -
-

The server computes a 2048-bit number b using sufficient entropy and generates the g_b parameter that was sent to us (see above).

-
    -
  • g_b := (k_v + (pow(g, b) mod p)) mod p
  • -
-

Finally, the SRP session keys are generated:

-

Client side:

-
    -
  • t := (g_b - k_v) mod p (positive modulo, if the result is negative increment by p)
  • -
  • s_a := pow(t, a + u * x) mod p
  • -
  • k_a := H(s_a)
  • -
-

Server side:

-
    -
  • s_b := pow(g_a * (pow(v, u) mod p), b) mod p
  • -
  • k_b := H(s_b)
  • -
-

Since:

-
    -
  • g_b := (k_v + (pow(g, b) mod p)) mod p
  • -
  • t := (g_b - k_v) mod p
  • -
  • t := ((k_v + (pow(g, b) mod p)) - k_v) mod p
  • -
  • t := pow(g, b) mod p
  • -
  • s_a := pow(t, a + u * x) mod p
  • -
  • s_a := pow(pow(g, b) mod p, a + u * x) mod p
  • -
-

And:

-
    -
  • -

    g_a := pow(g, a) mod p

    -
  • -
  • -

    v := pow(g, x) mod p

    -
  • -
  • -

    s_b := pow(g_a * (pow(v, u) mod p), b) mod p

    -
  • -
  • -

    s_b := pow((pow(g, a) mod p) * (pow(pow(g, x) mod p, u) mod p), b) mod p

    -
  • -
  • -

    s_b := pow(pow(g, a + x * u) mod p, b) mod p

    -
  • -
  • -

    s_b := pow(pow(g, b) mod p, a + u * x) mod p

    -
  • -
  • -

    s_a := pow(pow(g, b) mod p, a + u * x) mod p

    -
  • -
-

This means:

-
    -
  • s_b === s_a
  • -
  • k_b === k_a
  • -
-

Finally, as per SRP:

-
    -
  • M1 := H(H(p) xor H(g) | H(salt1) | H(salt2) | g_a | g_b | k_a)
  • -
-

M1 is passed to inputCheckPasswordSRP, along with g_a (as A parameter) and the srp_id, extracted from the account.password object.

-

The server then computes:

-
    -
  • M2 := H(H(p) xor H(g) | H(salt1) | H(salt2) | g_a | g_b | k_b)
  • -
-

Since we said that:

-
    -
  • s_b === s_a
  • -
  • k_b === k_a
  • -
-

This means, if everything was done correctly,

-
    -
  • M1 === M2
  • -
-

If the password isn't correct, 400 PASSWORD_HASH_INVALID will be returned.

-

Setting a new 2FA password

-

To set a new 2FA password use the account.updatePasswordSettings method.
-If a password is already set, generate an InputCheckPasswordSRP object as per checking passwords with SRP, and insert it in the password field of the account.updatePasswordSettings method.
-To remove the current password, pass an empty new_password_hash in the account.PasswordInputSettings object.

-

To set a new password, use the SRP parameters and the KDF algorithm obtained using account.getPassword when generating the password field. -Then generate a new new_password_hash using the KDF algorithm specified in the new_settings, just append 32 sufficiently random bytes to the salt1, first. -Proceed as for checking passwords with SRP, just stop at the generation of the v parameter, and use it as new_password_hash:

-
    -
  • v := pow(g, x) mod p
  • -
-

As usual in big endian form, padded to 2048 bits.

-

Email verification

-

When setting up two-factor authorization, it is recommended to set up a recovery email, to allow recovery of the password through the user's email address, in case they forget it.

-

To set up a recovery email, it must first be verified. -This can be done directly when setting the new password using account.updatePasswordSettings by setting the email parameter and flag in the account.passwordInputSettings constructor. -If the email isn't verified, an EMAIL_UNCONFIRMED_X 400 error will be returned, where X is the length of the verification code that was just sent to the email. -Use account.confirmPasswordEmail to enter the received verification code and enable the recovery email. -Use account.resendPasswordEmail to resend the verification code. -Use account.cancelPasswordEmail to cancel the verification code.

-

To get the current recovery email, use account.getPasswordSettings.

-

Email recovery

-

In order to recover a forgotten 2FA password, an email must be sent to the previously specified address using the auth.requestPasswordRecovery method.
-Use auth.checkRecoveryPassword to make sure that the user provided a valid code.
-Then use auth.recoverPassword with the received code to delete the current 2FA password, to set a new one follow these instructions.

-

Password reset

-
account.resetPasswordFailedWait#e3779861 retry_date:int = account.ResetPasswordResult;
-account.resetPasswordRequestedWait#e9effc7d until_date:int = account.ResetPasswordResult;
-account.resetPasswordOk#e926d63e = account.ResetPasswordResult;
-
----functions---
-
-account.resetPassword#9308ce1b = account.ResetPasswordResult;
-account.declinePasswordReset#4c9409f6 = Bool;
-

If the user is already logged in and has forgotten their 2FA password, account.resetPassword can be used to initiate a password reset.
-On success, the call will initially return a account.resetPasswordRequestedWait constructor and start a 7-day server-side timer, during which the user can abort the reset process using a button sent by the Telegram service account or directly in-UI using account.declinePasswordReset.

-

When the time comes, account.resetPassword is invoked once more, returning a account.resetPasswordOk to indicate that the password was successfully reset.

-

If the user recently requested a password reset that was canceled, account.resetPasswordFailedWait will be returned by the initial account.resetPassword call, and they must wait until the specified date before requesting another reset.

-

Note that if the user already knows their 2FA password and simply wants to disable 2FA, the same process used to enable the password must also be used to disable it ».

-

Related pages

-

SRP design

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/stats.html b/data/core.telegram.org/api/stats.html deleted file mode 100644 index c9372acb5a..0000000000 --- a/data/core.telegram.org/api/stats.html +++ /dev/null @@ -1,297 +0,0 @@ - - - - - Channel statistics - - - - - - - - - - - - - -
- -
-
-
- -

Channel statistics

- -
- -

Telegram offers detailed channel statistics for channels and supergroups.

-

Channel statistics

-

Schema:

-
statsDateRangeDays#b637edaf min_date:int max_date:int = StatsDateRangeDays;
-
-statsAbsValueAndPrev#cb43acde current:double previous:double = StatsAbsValueAndPrev;
-
-statsPercentValue#cbce2fe0 part:double total:double = StatsPercentValue;
-
-statsGraphAsync#4a27eb2d token:string = StatsGraph;
-statsGraphError#bedc9822 error:string = StatsGraph;
-statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
-
-messageInteractionCounters#ad4fc9bd msg_id:int views:int forwards:int = MessageInteractionCounters;
-
-stats.broadcastStats#bdf78394 period:StatsDateRangeDays followers:StatsAbsValueAndPrev views_per_post:StatsAbsValueAndPrev shares_per_post:StatsAbsValueAndPrev enabled_notifications:StatsPercentValue growth_graph:StatsGraph followers_graph:StatsGraph mute_graph:StatsGraph top_hours_graph:StatsGraph interactions_graph:StatsGraph iv_interactions_graph:StatsGraph views_by_source_graph:StatsGraph new_followers_by_source_graph:StatsGraph languages_graph:StatsGraph recent_message_interactions:Vector<MessageInteractionCounters> = stats.BroadcastStats;
-
----functions---
-
-stats.getBroadcastStats#ab42441a flags:# dark:flags.0?true channel:InputChannel = stats.BroadcastStats;
-stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;
-

Administrators of channels of a certain size (the exact limit is a server-side config, returned in the can_view_stats flag of channelFull) can call stats.getBroadcastStats to get detailed channel statistics.
-The returned stats.broadcastStats contains multiple statistics:

-
    -
  • Period-related statistics: a pair of values, one at the beginning and one at the end of the period in consideration (period).
    The period typically depends on channel activity.
      -
    • Absolute follower count (followers)
    • -
    • total_viewcount/postcount, for posts posted during the period in consideration (views_per_post).
      -Note that in this case, current refers to the period in consideration (min_date till max_date), and prev refers to the previous period ((min_date - (max_date - min_date)) till min_date).
    • -
    • total_sharecount/postcount, for posts posted during the period in consideration (shares_per_post).
      -Note that in this case, current refers to the period in consideration (min_date till max_date), and prev refers to the previous period ((min_date - (max_date - min_date)) till min_date).
    • -
    -
  • -
  • Percentage statistics
      -
    • Percentage of subscribers with enabled notifications (enabled_notifications)
    • -
    -
  • -
  • Graphs: graphs are described below ».
  • -
-

Supergroup statistics

-

Schema:

-
statsGroupTopPoster#9d04af9b user_id:long messages:int avg_chars:int = StatsGroupTopPoster;
-statsGroupTopInviter#535f779d user_id:long invitations:int = StatsGroupTopInviter;
-statsGroupTopAdmin#d7584c87 user_id:long deleted:int kicked:int banned:int = StatsGroupTopAdmin;
-
-stats.megagroupStats#ef7ff916 period:StatsDateRangeDays members:StatsAbsValueAndPrev messages:StatsAbsValueAndPrev viewers:StatsAbsValueAndPrev posters:StatsAbsValueAndPrev growth_graph:StatsGraph members_graph:StatsGraph new_members_by_source_graph:StatsGraph languages_graph:StatsGraph messages_graph:StatsGraph actions_graph:StatsGraph top_hours_graph:StatsGraph weekdays_graph:StatsGraph top_posters:Vector<StatsGroupTopPoster> top_admins:Vector<StatsGroupTopAdmin> top_inviters:Vector<StatsGroupTopInviter> users:Vector<User> = stats.MegagroupStats;
-
----functions---
-
-stats.getMegagroupStats#dcdf8607 flags:# dark:flags.0?true channel:InputChannel = stats.MegagroupStats;
-

Administrators of supergroups of a certain size (the exact limit is a server-side config, returned in the can_view_stats flag of channelFull) can call stats.getMegagroupStats to get detailed supergroup statistics.
-The returned stats.broadcastStats contains multiple statistics, see the constructor page for more info ».

-

Message statistics

-
stats.messageStats#8999f295 views_graph:StatsGraph = stats.MessageStats;
-
----functions---
-
-stats.getMessageStats#b6e0a3f5 flags:# dark:flags.0?true channel:InputChannel msg_id:int = stats.MessageStats;
-

Administrators of channels of a certain size (the exact limit is a server-side config, returned in the can_view_stats flag of channelFull) can call stats.getMessageStats to get statistics of a specific message.
-The returned stats.messageStats contains the view graph of the message.

-

Graph visualization

-

There are four available visualizations for graph types:

- -

Graph modifiers (see various graphs for examples):

-
    -
  • y_scaled - Indicates that each of the two (!) lines in a step graph must be visualized on its own scale, with two different tick axes on the left and right parts of the graph
  • -
  • percentage - Indicates whether value percentages should be shown in labels
  • -
  • stacked - Depending on the graph type, indicates stacking of multiple columns in the same graph
  • -
-

Graph syntax

-
statsGraphAsync#4a27eb2d token:string = StatsGraph;
-statsGraphError#bedc9822 error:string = StatsGraph;
-statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
-
-dataJSON#7d748d04 data:string = DataJSON;
-
----functions---
-
-stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;
-

Certain graphs are not directly sent in the stats.broadcastStats constructor to reduce server load: instead, those graphs will be sent as a statsGraphAsync constructor, and should be fetched separately using stats.loadAsyncGraph.

-

After obtaining the full statsGraph constructor, clients should parse the JSON graph object in the json field.

-

Object structure:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
KeyGraph title
columnsArray of all data column arrays in the chart. Each column array has its label at position 0, followed by values.
typesGraphs types for each of the column arrays (object, "label": "type"):
- line - line graph
- area - area graph
- step - step graph
- bar - bar graph
- x - x axis values for each of the charts at the corresponding positions, UNIX timestamps in milliseconds.
colorsColor for each type (object, "label": "colorKey#AAAAAA"; see chart colors).
namesLocalized name for each variable (object, "label": "Name")
subchartObject indicating the default zoom range for the graph, this is object's structure:
- show - Whether to use the specified zoom range (boolean)
- defaultZoom - An array with two x values, indicating the two ends of the default zoom range
y_scaledIndicates that each of the two (!) lines in a step graph must be visualized on its own scale, with two different tick axes on the left and right parts of the graph (boolean, see various graphs for examples)
percentageIndicates whether value percentages should be shown in labels (boolean, see various graphs for examples)
stackedDepending on the graph type, indicates stacking of multiple columns in the same graph (boolean, see various graphs for examples)
- -

The following chart restrictions apply:

-
    -
  • Up to 50 columns on one graph must be supported.
  • -
  • Chart types are always the same for every column in the graph.
  • -
  • The bar chart type and stacked option are always used together.
  • -
  • percentage is always used with the area graph. - -
  • -
-

Chart zooming

-
statsGraphError#bedc9822 error:string = StatsGraph;
-statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
-
-dataJSON#7d748d04 data:string = DataJSON;
-
----functions---
-
-stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;
-

Graphs that support zooming will contain a zoom_token in the statsGraph constructor.
-Said token should be then used as token in a new stats.loadAsyncGraph call triggered when the user clicks on the label, related to a certain x axis in the graph (see graph examples).
-The x coordinate of the label should be provided to the x parameter; the method will then return (if available) a more detailed subgraph.
-If not enough data is available, a localized statsGraphError will be returned.

-

Typical zoom visualization rules:

- -

Chart colors

-

Chart colors can be provided as a color key, followed by the primary color value in hex format:

-
red#e05356
-

The color key can be one of red, lightblue, lightgreen, golden, green, orange, blue, indigo.
-Apps can choose to use a color value specified by the currently loaded theme: for example, the android app uses statisticChartLine_* themekeys for each of the color keys, check out the assets directory for a bunch of default themes with various colors for channel statistics.

-

However, the server may also choose to return just a plain color value in hex format:

-
#e05356
-

In this case, the dark flag of the stats.getBroadcastStats method can be used to choose the palette of returned colors.

-

Graph examples

-

Line graph

-

Simple single line graph

-

Step graph

-

Step graph, always "stacked" (to indicate multiple lines)

-

Bar graph

-

Bar graph with multiple lines, always "stacked" (to indicate actual stacked bars, biggest bars first)

-

Area graph

-

Mixed bar/line graph, always "stacked" (to indicate actual stacked bars, biggest bars first)

-

Piechart

-

Piechart, typically obtained only when zooming into percentage graphs

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/terms.html b/data/core.telegram.org/api/terms.html deleted file mode 100644 index 20985c7cf7..0000000000 --- a/data/core.telegram.org/api/terms.html +++ /dev/null @@ -1,133 +0,0 @@ - - - - - Telegram API Terms of Service - - - - - - - - - - - - - -
- -
-
-
- -

Telegram API Terms of Service

- -
- -

We welcome all developers to use our API and source code to create Telegram-like messaging applications on our platform free of charge. In order to ensure consistency and security across the Telegram ecosystem, all third-party client apps must comply with the following Terms of Service.

-

1. Privacy & Security

-

1.1. Telegram is a privacy-oriented platform. All client apps must, therefore, guard their users' privacy with utmost care and comply with our Security Guidelines.
1.2. Developers are welcome to add new features or improve and extend existing Telegram features provided that these modifications do not violate these Terms of Service.
1.3. As a client developer, you must make sure that all the basic features of the main Telegram apps function correctly and in an expected way both in your app and when users of your app communicate with other Telegram users. It is forbidden to force users of other Telegram clients to download your app in order to view certain messages and content sent using your app.
1.4. It is forbidden to interfere with the basic functionality of Telegram. This includes but is not limited to: making actions on behalf of the user without the user's knowledge and consent, preventing self-destructing content from disappearing, preventing last seen and online statuses from being displayed correctly, tampering with the 'read' statuses of messages (e.g. implementing a 'ghost mode'), preventing typing statuses from being sent/displayed, etc.

-

2. Transparency

-

2.1. You must obtain your own api_id for your application.
2.2. We offer our API free of charge, but your users must be aware of the fact that your app uses the Telegram API and is part of the Telegram ecosystem. This fact must be featured prominently in the app's description in the app stores and in the in-app intro if your app has it.
2.3. To avoid confusion, the title of your app must not include the word “Telegram”. An exception can be made if the word “Telegram” is preceded with the word “Unofficial” in the title.
2.4. You must not use the official Telegram logo for your app. Both the Telegram brand and its logo are registered trademarks protected by law in almost every country.

-

3. Advertising & Monetization

-

3.1. Developers are allowed to monetize their coding efforts through advertising or other legitimate means.
3.2. If you decide to monetize your app, you must clearly mention all the methods of monetization that are used in your app in all its app store descriptions.
3.3. If your app allows accessing content from Telegram channels, you must include support for official sponsored messages in Telegram channels and may not interefere with this functionality.

-

4. Breach of terms

-

4.1. If your app violates these terms, we will notify the Telegram account responsible for the app about the breach of terms.
4.2. If you do not update the app to fix the highlighted issues within 10 days, we will have to discontinue your access to Telegram API and contact the app stores about the removal of your apps that are using the Telegram API in violation of these terms.

-

We reserve the right to expand these terms and guidelines as the need arises. We will inform client developers of such changes via an in-app notification to their accounts connected to the app in question.

-
-

Back to Creating Your Telegram Application »

-
-
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/threads.html b/data/core.telegram.org/api/threads.html deleted file mode 100644 index ff7a9930f8..0000000000 --- a/data/core.telegram.org/api/threads.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - Threads - - - - - - - - - - - - - -
- -
-
-
- -

Threads

- -
- -

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

-

Message threads

-

Schema:

-
messageReplyHeader#a6d57763 flags:# reply_to_msg_id:int reply_to_peer_id:flags.0?Peer reply_to_top_id:flags.1?int = MessageReplyHeader;
-
-messageReplies#83d60fc2 flags:# comments:flags.0?true replies:int replies_pts:int recent_repliers:flags.1?Vector<Peer> channel_id:flags.0?long max_id:flags.2?int read_max_id:flags.3?int = MessageReplies;
-
-message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
-
----functions---
-
-messages.search#a0fda762 flags:# peer:InputPeer q:string from_id:flags.0?InputPeer top_msg_id:flags.1?int filter:MessagesFilter min_date:int max_date:int offset_id:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
-

Threads are usually automatically created when replying to any message in a group.
-For example, all replies to a message with ID 420 are associated to thread with ID 420, unique to this group; this thread ID is contained in the reply_to_top_id field of reply_to messageReplyHeader, along with an eventual reply_to_msg_id, for replies to messages within a thread.
-Replies to messages in a thread are part of the same thread, and do not spawn new threads.

-

When receiving a message from a group that is also the top of a thread (the message with ID 420), the replies optional field will contain a messageReplies constructor, containing the message ID and PTS of the latest reply in the thread, and the message ID of the latest read thread reply, along with the total number of replies in the thread.

-

Replies to a thread can also be manually fetched using messages.search, providing to top_msg_id the thread ID.

-

Channel comments

-
messageReplies#83d60fc2 flags:# comments:flags.0?true replies:int replies_pts:int recent_repliers:flags.1?Vector<Peer> channel_id:flags.0?long max_id:flags.2?int read_max_id:flags.3?int = MessageReplies;
-

The same messageReplies constructor seen above will also be contained in channel posts, this time containing information about the comment section of a specific channel post.
-The comment section of a channel post is simply the message thread of the automatically forwarded channel message in the linked discussion supergroup; the ID of the linked discussion supergroup will be contained in the messageReplies.channel_id field.

-

For channel posts, the recent_repliers field will also contain information about the last few comment posters for a specific thread, to show a small list of commenter profile pictures in client previews.

-

@replies

-
messageFwdHeader#5f777dce flags:# imported:flags.7?true from_id:flags.0?Peer from_name:flags.5?string date:int channel_post:flags.2?int post_author:flags.3?string saved_from_peer:flags.4?Peer saved_from_msg_id:flags.4?int psa_type:flags.6?string = MessageFwdHeader;
-
-messageReplyHeader#a6d57763 flags:# reply_to_msg_id:int reply_to_peer_id:flags.0?Peer reply_to_top_id:flags.1?int = MessageReplyHeader;
-
-message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
-
-updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
-updateNewChannelMessage#62ba04d9 message:Message pts:int pts_count:int = Update;
-
----functions---
-
-contacts.blockFromReplies#29a8962c flags:# delete_message:flags.0?true delete_history:flags.1?true report_spam:flags.2?true msg_id:int = Updates;
-
-contacts.resolveUsername#f93ccba3 username:string = contacts.ResolvedPeer;
-

Since a user can comment in channel posts without joining the actual discussion supergroup, there must be a way for them to receive notifications about replies in comment sections.
-For this reason, a special @replies username is provided. -Its ID for main and testing endpoints can be seen in the tdlib sources.

-

When someone replies to one of our messages in the comment section of a channel post, and the user is not subscribed to the discussion group, the client will receive two updates:

-
    -
  • An updateNewChannelMessage from the discussion group itself, structured just like any other update coming from a subscribed group, with:
      -
    • id set to the ID of the reply
    • -
    • from_id set to the peer that replied to us
    • -
    • peer_id set to the peer of the discussion group
    • -
    • reply_to.reply_to_msg_id set to the ID of our message
    • -
    • reply_to.reply_to_top_id set to the thread ID.
    • -
    -
  • -
  • An updateNewMessage
      -
    • id set to the common ID sequence for users
    • -
    • from_id set to the peer of @replies
    • -
    • peer_id set to our own peer
    • -
    • fwd_from.saved_from_msg_id set to the ID of the reply
    • -
    • fwd_from.from_id set to the the peer that replied to us
    • -
    • reply_to.reply_to_peer_id set to the peer of the discussion group
    • -
    • reply_to.reply_to_msg_id set to the ID of our message
    • -
    • reply_to.reply_to_top_id set to the thread ID
    • -
    -
  • -
-

Clients should display messages coming from @replies as a read-only supergroup, with each reply displayed as a separate message from the author of the reply, with a "View in chat" button like for channel comments.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/top-rating.html b/data/core.telegram.org/api/top-rating.html deleted file mode 100644 index ae7b246332..0000000000 --- a/data/core.telegram.org/api/top-rating.html +++ /dev/null @@ -1,145 +0,0 @@ - - - - - Top peer rating - - - - - - - - - - - - - -
- -
-
-
- -

Top peer rating

- -

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

-

Schema:

-
topPeer#edcdc05b peer:Peer rating:double = TopPeer;
-
-topPeerCategoryBotsPM#ab661b5b = TopPeerCategory;
-topPeerCategoryBotsInline#148677e2 = TopPeerCategory;
-topPeerCategoryCorrespondents#637b7ed = TopPeerCategory;
-topPeerCategoryGroups#bd17a14a = TopPeerCategory;
-topPeerCategoryChannels#161d9628 = TopPeerCategory;
-topPeerCategoryPhoneCalls#1e76a78c = TopPeerCategory;
-topPeerCategoryForwardUsers#a8406ca9 = TopPeerCategory;
-topPeerCategoryForwardChats#fbeec0f0 = TopPeerCategory;
-
-topPeerCategoryPeers#fb834291 category:TopPeerCategory count:int peers:Vector<TopPeer> = TopPeerCategoryPeers;
-
-contacts.topPeersNotModified#de266ef5 = contacts.TopPeers;
-contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;
-contacts.topPeersDisabled#b52c939d = contacts.TopPeers;
-
----functions---
-
-contacts.getTopPeers#973478b6 flags:# correspondents:flags.0?true bots_pm:flags.1?true bots_inline:flags.2?true phone_calls:flags.3?true forward_users:flags.4?true forward_chats:flags.5?true groups:flags.10?true channels:flags.15?true offset:int limit:int hash:long = contacts.TopPeers;
-

The rate delta is computed by taking the time delta between the last time the user used a certain peer and the last time the rating for that peer was received and dividing it by the exponential decay from config.

-

Example: -Client-side, every time a user opens chat 123456789 the following operation must be done on the cached top peer info.

-
    -
  • dateOpened indicates when was the peer used
  • -
  • normalizeRate is an arbitrary time in the recent past. -When ratings are received from the server using contacts.getTopPeers and the schema described above, it is the time when they were received.
  • -
-
topPeer.rating += e^((dateOpened - normalizeRate) / config.rating_e_decay)
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/api/updates.html b/data/core.telegram.org/api/updates.html deleted file mode 100644 index 4a314b97ea..0000000000 --- a/data/core.telegram.org/api/updates.html +++ /dev/null @@ -1,226 +0,0 @@ - - - - - Working with Updates - - - - - - - - - - - - - -
- -
-
-
- -

Working with Updates

- -
- -

When a client is being actively used, events will occur that affect the current user and that they must learn about as soon as possible, e.g. when a new message is received. To eliminate the need for the client itself to periodically download these events, there is an update delivery mechanism in which the server sends the user notifications over one of its available connections with the client.

-

Subscribing to Updates

-

Update events are sent to an authorized user into the last active connection (except for connections needed for downloading / uploading files).

-

So to start receiving updates the client needs to init connection and call API method, e.g. to fetch current state.

-

Event sequences

-

All events are received from the socket as a sequence of TL-serialized Updates objects, which might be optionally gzip-compressed in the same way as responses to queries.

-

Each Updates object may contain single or multiple Update objects, representing different events happening.

-

In order to apply all updates in precise order and to guarantee that no update is missed or applied twice there is seq attribute in Updates constructors, and pts (with pts_count) or qts attributes in Update constructors. The client must use those attributes values in combination with locally stored state to correctly apply incoming updates.

-

When a gap in updates sequence occurs, it must be filled via calling one of the API methods. More below »

-

Updates sequence

-

As said earlier, each payload with updates has a TL-type Updates. It can be seen from the schema below that this type has several constructors.

-
updatesTooLong#e317af7e = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-

updatesTooLong indicates that there are too many events pending to be pushed to the client, so one needs to fetch them manually.

-

Events inside updateShort constructors, normally, have lower priority and are broadcast to a large number of users, i.e. one of the chat participants started entering text in a big conversation (updateChatUserTyping).

-

The updateShortMessage, updateShortSentMessage and updateShortChatMessage constructors are redundant but help significantly reduce the transmitted message size for 90% of the updates. They should be transformed to updateShort upon receiving.

-

Two remaining constructors updates and updatesCombined are part of the Updates sequence. Both of them have seq attribute, which indicates the remote Updates state after the generation of the Updates, and seq_start indicates the remote Updates state after the first of the Updates in the packet is generated. For updates, seq_start attribute is omitted, because it is assumed that it is always equal to seq.

-

Message-related event sequences

-

Each event related to a message box (message created, message edited, message deleted, etc) is identified by a unique autoincremented pts, or qts in case of secret chat updates, certain bot updates, etc.

-

Each message box can be considered as some server-side DB table that stores messages and events associated with them. -All boxes are completely independent, and each pts sequence is tied to just one box (see below).

-

Update object may contain info about multiple events (for example, updateDeleteMessages). -That's why all single updates might have pts_count parameter indicating the number of events contained in the received update (with some exceptions, in this case, the pts_count is considered to be 0).

-

Each channel and supergroup has its message box and its event sequence as a result; private chats and legacy groups of one user have another common event sequence. -Secret chats, certain bot events and other kinds of updates have yet another common secondary event sequence.

-

To recap, the client has to take care of the integrity of the following sequences to properly handle updates:

-
    -
  • Updates sequence (seq)
      -
    • Common message box sequence (pts)
    • -
    • Secondary event sequence (qts)
    • -
    • Channel message box sequence 1 (pts)
    • -
    • Channel message box sequence 2 (pts)
    • -
    • Channel message box sequence 3 (pts)
    • -
    • and so on...
    • -
    -
  • -
-

Fetching state

-

The common update state is represented by the updates.State constructor. -When the user logs in for the first time, call to updates.getState has to be made to store the latest update state (which will not be the absolute initial state, just the latest state at the current time). -The common update state can also be fetched from updates.differenceTooLong.

-

The channel update state is represented simply by the pts of the event sequence: when first logging in, the initial channel state can be obtained from the dialog constructor when fetching dialogs, from the full channel info, or it can be received as an updateChannelTooLong update.

-

The secondary update state is represented by the qts of the secret event sequence, it is contained in the updates.State of the common update state.

-

The Updates sequence state is represented by the date and seq of the Updates sequence, it is contained in the updates.State of the common update state.

-

Update handling

-

Update handling in Telegram clients consists of receiving events, making sure there were no gaps and no events were missed based on the locally stored state of the correspondent event sequence, and then updating the locally stored state based on the parameters received.

-

When the client receives payload with serialized updates, first of all, it needs to walk through all of the nested Update objects and check if they belong to any of message box sequences (have pts or qts parameters). Those updates need to be handled separately according to corresponding local state and new pts/qts values. Details below »

-

After message box updates are handled, if there are any other updates remaining the client needs to handle them with respect to seq. Details below »

-

pts: checking and applying

-

Here, local_pts will be the local state, pts will be the remote state, pts_count will be the number of events in the update.

-

If local_pts + pts_count === pts, the update can be applied. -If local_pts + pts_count > pts, the update was already applied, and must be ignored. -If local_pts + pts_count < pts, there's an update gap that must be filled.

-

For example, let's assume the client has the following local state for the channel 123456789:

-
local_pts = 131
-

Now let's assume an updateNewChannelMessage from channel 123456789 is received with pts = 132 and pts_count=1. -Since local_pts + pts_count === pts, the total number of events since the last stored state is, in fact, equal to pts_count: this means the update can be safely accepted and the remote pts applied:

-
local_pts = 132
-

Since:

-
    -
  • pts indicates the server state after the new channel message events are generated
  • -
  • pts_count indicates the number of events in the new channel update
  • -
  • The server state before the new channel message event was generated has to be: pts_before = pts - pts_count = 131, which is, in fact, equal to our local state.
  • -
-

Now let's assume an updateNewChannelMessage from channel 123456789 is received with pts = 132 and pts_count=1. -Since local_pts + pts_count > pts (133 > 132), the update is skipped because we've already handled this update (in fact, our current local_pts was set by this same update, and it was resent twice due to network issues or other issues).

-

Now let's assume an updateDeleteChannelMessages from channel 123456789 is received with pts = 140 and pts_count=5. -Since local_pts + pts_count < pts (137 < 140), this means that updates were missed, and the gap must be recovered.

-
Secret chats & bots
-

The whole process is very similar for secret chats and certain bot updates, but there is qts instead of pts, and events are never grouped, so it's assumed that qts_count is always equal to 1.

-

seq: checking and applying

-

On top level when handling received updates and updatesCombined there are three possible cases: -If local_seq + 1 === seq_start, the updates can be applied. -If local_seq + 1 > seq_start, the updates were already applied, and must be ignored. -If local_seq + 1 < seq_start, there's an updates gap that must be filled (updates.getDifference must be used as with common and secret event sequences).

-

If the updates were applied, local Updates state must be updated with seq and date from the constructor.

-

For all the other Updates type constructors there is no need to check seq or change a local state.

-

Recovering gaps

-

To do this, updates.getDifference (common/secret state) or updates.getChannelDifference (channel state) with the respective local states must be called. -These methods should also be called on startup, to fetch new updates (preferably with some flags to reduce server load, see the method's docs). -Manually obtaining updates is also required in the following situations:

-
    -
  • Loss of sync: a gap was found in seq / pts / qts (as described above). It may be useful to wait up to 0.5 seconds in this situation and abort the sync in case a new update arrives, that fills the gap.
  • -
  • Session loss on the server: the client receives a new session created notification. This can be caused by garbage collection on the MTProto server or a server reboot.
  • -
  • Incorrect update: the client cannot deserialize the received data.
  • -
  • Incomplete update: the client is missing data about a chat/user from one of the shortened constructors, such as updateShortChatMessage, etc.
  • -
  • Long period without updates: no updates for 15 minutes or longer.
  • -
  • The server requests the client to fetch the difference using updateChannelTooLong or updatesTooLong.
  • -
-

When calling updates.getDifference if the updates.differenceSlice constructor is returned in response, the full difference was too large to be received in one request. The intermediate status, intermediate_state, must be saved on the client and the query must be repeated, using the intermediate status as the current status.

-

To fetch the updates difference of a channel, updates.getChannelDifference is used. -If the difference is too large to be received in one request, the final flag of the result is not set (see docs). -The intermediate status, represented by the pts, must be saved on the client and the query must be repeated, using the intermediate status as the current status.

-

For perfomance reasons and for better user experience, client can set maximum gap size to be filled: pts_total_limit parameter of updates.getDifference and limit parameter for updates.getChannelDifference can be used.

-

If the gap is too large and there are too many updates to fetch, a *TooLong constructor will be returned. In this case, the client must re-fetch the state, re-start fetching updates from that state and follow the instructions that can be found here.

-

It is recommended to use limit 10-100 for channels and 1000-10000 otherwise.

-

Example implementations

-

Implementations also have to take care to postpone updates received via the socket while filling gaps in the event and Update sequences, as well as avoid filling gaps in the same sequence.

-

Example implementations: tdlib, MadelineProto.

-

An interesting and easy way this can be implemented, instead of using various locks, is by running background loops, like in MadelineProto ».

-

PUSH Notifications about Updates

-

If a client does not have an active connection at the time of an event, PUSH Notifications will also be useful.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/url-authorization.html b/data/core.telegram.org/api/url-authorization.html deleted file mode 100644 index 5e711e4cd3..0000000000 --- a/data/core.telegram.org/api/url-authorization.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - Seamless Telegram Login - - - - - - - - - - - - - -
- -
-
-
- -

Seamless Telegram Login

- -
- -

Bots or Telegram websites may ask users to login to a certain website via Telegram when clicking on certain links or URL buttons in inline keyboards.

-

Bot URL authorization

-

When the user clicks on keyboardButtonUrlAuth, messages.requestUrlAuth should be called, providing the button_id of the button and the ID and peer of the container message. -The returned urlAuthResultRequest object will contain more details about the authorization request:

-
    -
  • The domain parameter will contain the domain name of the website on which the user will log in (example: comments.app).
  • -
  • The bot parameter will contain info about the bot which will be used for user authorization (example: DiscussBot).
  • -
  • The request_write_access will be set if the bot would like to send messages to the user.
  • -
-

The info should be shown in a prompt:

-
- TITLE -
-

If the user agrees to login to the URL, messages.acceptUrlAuth should be called (eventually setting the write_allowed if the permission was requested and the user consented). -The result will be a urlAuthResultAccepted with the final URL to open, which will include a query string with the requested info and a hash that must be verified upon receival by the service.

-

urlAuthResultDefault could also be returned, instead, in which case the url of the keyboardButtonUrlAuth must be opened, instead. -The same must be done if the user opens the link while refusing the authorization request.

-

Link URL authorization

-

Telegram supports automatic authorization on certain websites upon opening an HTTP URL in-app, upon clicking a link in a message or clicking on a keyboardButtonUrl.

-

Automatic authorization

-

Clients should automatically authenticate users when opening official Telegram websites, listed in the url_auth_domains key of the client configuration object ».

-

Upon clicking a link, the URL must be modified by appending the autologin_token from the client configuration object » to the query string, like so:

-

Original URL: https://somedomain.telegram.org/path?query=string#fragment=value
-Modified URL: https://somedomain.telegram.org/path?query=string&autologin_token=$autologin_token#fragment=value

-

Make sure that the used autologin_token is no more than 10000 seconds old, if it is older it must be refetched before use as described in the client configuration section ».

-

Manual authorization

-

Clients should show a confirmation prompt similar to the one used for bots, to authenticate users when opening certain Telegram websites, listed in the url_auth_domains key of the client configuration object ».

-

messages.requestUrlAuth should be called, providing only the original url. -The returned urlAuthResultRequest object will contain more details about the authorization request:

-
    -
  • The domain parameter will contain the domain name of the website on which the user will log in (example: comments.app).
  • -
  • The request_write_access will be set if the website would like to send messages to the user.
  • -
-

The info should be shown in a prompt.

-

If the user agrees to login to the URL, messages.acceptUrlAuth should be called (eventually setting the write_allowed if the permission was requested and the user consented). -The result will be a urlAuthResultAccepted with the final URL to open.

-

urlAuthResultDefault could also be returned, instead, in which case the original URL must be opened, instead. -The same must be done if the user opens the link while refusing the authorization request.

-

Related articles

-

Client configuration

-

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/api/web-events.html b/data/core.telegram.org/api/web-events.html deleted file mode 100644 index fd612b4c95..0000000000 --- a/data/core.telegram.org/api/web-events.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - Web events - - - - - - - - - - - - - -
- -
-
-
- -

Web events

- -
- -

When interacting with HTML5 games and the websites of payment gateways, Telegram apps should expose APIs to allow receiving data and events from the websites.

-

Event APIs

-

Games and payment gateways can generate events that are meant to be received by the Telegram apps. -Typically events are generated by using the postEvent method of the GamingCommunication library. -The postEvent function will try sending the event to the Telegram app in a number of different ways.

-

WebviewProxy

-

In mobile apps, the event receiver API should be typically exposed as a window.TelegramWebviewProxy object with a postEvent method.

-
window.TelegramWebviewProxy.postEvent(eventType, eventData)
-

window.external

-

Alternatively, a window.external.notify method can be exposed, accepting a string JSON payload with the event type and payload:

-
window.external.notify(JSON.stringify({eventType: eventType, eventData: eventData}));
-

postMessage API

-

Finally, web MTProto clients that need to open a game or process a payment in an iframe can use the postMessage API to receive events from iframes. -The GamingCommunication library by defaultwill use '*' as targetOrigin, sending messages to parent pages regardless of the origin of the embedder.

-
window.parent.postMessage(JSON.stringify({eventType: eventType, eventData: eventData}), targetOrigin);
-

Event types

-

eventType is a simple string indicating the event type, and eventData is a payload with an object that will be parsed by the Telegram app.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
eventTypeeventDataDescription
payment_form_submitJSON object with data and title fieldstitle is the censored credit card title.
data is a service-specific JSON payload with information about the payment credentials provided by the user to the payment system.
Neither Telegram, nor bots will have access to your credit card information.
Credit card details will be handled only by the payment system.
share_scorenullWill be called by games when the user explicitly clicks on the share score button to share the game, along with his score.
Typically done by using messages.forwardMessages on the game message with the with_my_score flag.
share_gamenullWill be called by games when the user explicitly clicks on the share game button to share the game, without sharing his score.
Typically done by using messages.forwardMessages on the game message without the with_my_score flag, or by sharing the game's short URL.
game_overnullCan be called by games when the user loses a game
game_loadednullCan be called by games once the game fully loads
resize_frameJSON object with height fieldCalled by supported pages inside of IV iframe embeds, indicates the new size of the embed frame.
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/apple_privacy.html b/data/core.telegram.org/apple_privacy.html deleted file mode 100644 index 749930f957..0000000000 --- a/data/core.telegram.org/apple_privacy.html +++ /dev/null @@ -1,118 +0,0 @@ - - - - - Page moved - - - - - - - - - - - - - -
- -
-
-
-
-

Page moved

- -

This is not the droid you're looking for.
The page has been moved.

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html b/data/core.telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html deleted file mode 100644 index abf48687bc..0000000000 --- a/data/core.telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html +++ /dev/null @@ -1,115 +0,0 @@ - - - - - Page not found - - - - - - - - - - - - - -
- -
-
-
-
-

Page not found

- -
The page has not been saved
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/bots.html b/data/core.telegram.org/bots.html deleted file mode 100644 index fa4bec195b..0000000000 --- a/data/core.telegram.org/bots.html +++ /dev/null @@ -1,437 +0,0 @@ - - - - - Bots: An introduction for developers - - - - - - - - - - - - - -
- -
-
-
-
-

Bots: An introduction for developers

- -
- -

Bots are third-party applications that run inside Telegram. Users can interact with bots by sending them messages, commands and inline requests. You control your bots using HTTPS requests to Telegram's Bot API.

-
-

The full API reference for developers is available here.

-
-

1. What can I do with bots?

-
- -
- -

To name just a few things, you could use bots to:

-
    -
  • Get customized notifications and news. A bot can act as a smart newspaper, sending you relevant content as soon as it's published.

    -
  • -
  • Integrate with other services. A bot can enrich Telegram chats with content from external services.
    Gmail Bot, GIF bot, IMDB bot, Wiki bot, Music bot, Youtube bot, GitHubBot

    -
  • -
  • Accept payments from Telegram users. A bot can offer paid services or work as a virtual storefront. Read more »
    Demo Shop Bot, Demo Store

    -
  • -
  • Create custom tools. A bot may provide you with alerts, weather forecasts, translations, formatting or other services.
    Markdown bot, Sticker bot, Vote bot, Like bot

    -
  • -
  • Build single- and multiplayer games. A bot can offer rich HTML5 experiences, from simple arcades and puzzles to 3D-shooters and real-time strategy games.
    GameBot, Gamee

    -
  • -
  • Build social services. A bot could connect people looking for conversation partners based on common interests or proximity.

    -
  • -
  • Do virtually anything else. Except for dishes — bots are terrible at doing the dishes.

    -
  • -
-

2. How do bots work?

-

At the core, Telegram Bots are special accounts that do not require an additional phone number to set up. Users can interact with bots in two ways:

-
    -
  • Send messages and commands to bots by opening a chat with them or by adding them to groups.
  • -
  • Send requests directly from the input field by typing the bot's @username and a query. This allows sending content from inline bots directly into any chat, group or channel.
  • -
-

Messages, commands and requests sent by users are passed to the software running on your servers. Our intermediary server handles all encryption and communication with the Telegram API for you. You communicate with this server via a simple HTTPS-interface that offers a simplified version of the Telegram API. We call that interface our Bot API.

-
-

A detailed description of the Bot API is available on this page »

-
-

3. How do I create a bot?

-
- -
- -

There's a… bot for that. Just talk to BotFather (described below) and follow a few simple steps. Once you've created a bot and received your authentication token, head down to the Bot API manual to see what you can teach your bot to do.

-
-

You may also like to check out some code examples here »

-
-

4. How are bots different from humans?

-
    -
  • Bots have no online status and no last seen timestamps, the interface shows the label 'bot' instead.
  • -
  • Bots have limited cloud storage — older messages may be removed by the server shortly after they have been processed.
  • -
  • Bots can't initiate conversations with users. A user must either add them to a group or send them a message first. People can use t.me/<bot_username> links or username search to find your bot.
  • -
  • Bot usernames always end in 'bot' (e.g. @TriviaBot, @GitHub_bot).
  • -
  • When added to a group, bots do not receive all messages by default (see Privacy mode).
  • -
  • Bots never eat, sleep or complain (unless expressly programmed otherwise).
  • -
-
-

5. Bot perks

-

Telegram bots are unique in many ways — we offer two kinds of keyboards, additional interfaces for default commands and deep linking as well as text formatting, integrated payments and more.

-

Inline mode

- - -

Users can interact with your bot via inline queries straight from the text input field in any chat. All they need to do is start a message with your bot's username and then type a query.

-

Having received the query, your bot can return some results. As soon as the user taps one of them, it is sent to the user's currently opened chat. This way, people can request content from your bot in any of their chats, groups or channels.

-

Check out this blog to see a sample inline bot in action. You can also try the @sticker and @music bots to see for yourself.

-
-
- -
- -

We've also implemented an easy way for your bot to switch between inline and PM modes.

-
-

Read more about the Inline Mode »

-
-

Payment platform

- - -

You can use bots to accept payments from Telegram users around the world.

-
    -
  • Send invoices to any chat, including to groups and channels.
  • -
  • Create invoices that can be forwarded and used by multiple buyers to order things.
  • -
  • Use inline mode to help users show your goods and services to their friends and communities.
  • -
  • Allow tips from users with preset and custom amounts.
  • -
  • Accept payments from users on mobile or desktop apps.
  • -
  • Try @ShopBot to create a test invoice – or start a message with @ShopBot ... in any chat for an inline invoice.
  • -
  • Check out Demo Shop for an example of a Telegram Channel used as virtual storefront.
  • -
-
- -
- -
-

Read more about the Payments Platform »

-
-

Gaming platform

-

Bots can offer their users HTML5 games to play solo or to compete against each other in groups and one-on-one chats. The platform allows your bot to keep track of high scores for every game played in every chat. Whenever there’s a new leader in the game, other playing members in the chat are notified that they need to step it up.

-
- - -
-
- -

Since the underlying technology is HTML5, the games can be anything from simple arcades and puzzles to multiplayer 3D-shooters and real-time strategy games. Our team has created a couple of simple demos for you to try out:

- -

You can also check out the @gamee bot that has more than 20 games.

-
-

Read more about the Gaming Platform »

-
-

Keyboards

-

Traditional chat bots can of course be taught to understand human language. But sometimes you want some more formal input from the user — and this is where custom keyboards can become extremely useful.

-

Whenever your bot sends a message, it can pass along a special keyboard with predefined reply options (see ReplyKeyboardMarkup). Telegram apps that receive the message will display your keyboard to the user. Tapping any of the buttons will immediately send the respective command. This way you can drastically simplify user interaction with your bot.

-

We currently support text and emoji for your buttons. Here are some custom keyboard examples:

-
-
- - - - - - - -
- -
-

For more technical information on custom keyboards, please consult the Bot API manual (see sendMessage).

-
-

Inline keyboards and on-the-fly updating

-

There are times when you'd prefer to do things without sending any messages to the chat. For example, when your user is changing settings or flipping through search results. In such cases you can use Inline Keyboards that are integrated directly into the messages they belong to.

-

Unlike with custom reply keyboards, pressing buttons on inline keyboards doesn't result in messages sent to the chat. Instead, inline keyboards support buttons that work behind the scenes: callback buttons, URL buttons and switch to inline buttons.

-
- - - - -
- -
- -

When callback buttons are used, your bot can update its existing messages (or just their keyboards) so that the chat remains tidy. Check out these sample bots to see inline keyboards in action: @music, @vote, @like.

-
-

Read more about inline keyboards and on-the-fly editing »

-
-

Commands

-

Commands present a more flexible way to communicate with your bot. The following syntax may be used:

-
/command
-

A command must always start with the '/' symbol and may not be longer than 32 characters. Commands can use latin letters, numbers and underscores. Here are a few examples:

-
/get_messages_stats
-/set_timer 10min Alarm!
-/get_timezone London, UK
-

Messages that start with a slash are always passed to the bot (along with replies to its messages and messages that @mention the bot by username). Telegram apps will:

-
    -
  • Suggest a list of supported commands with descriptions when the user enters a '/' (for this to work, you need to have provided a list of commands to the BotFather). Tapping on a command in the list immediately sends the command.
  • -
  • Show an additional (/) button in the input field in all chats with bots. Tapping it types a '/' and shows the list of commands.
  • -
  • Highlight /commands in messages. When the user taps a highlighted command, the command is sent at once.
  • -
-
- - - - - - - -
- - -

If multiple bots are in a group, it is possible to add bot usernames to commands in order to avoid confusion:

-
/start@TriviaBot
-/start@ApocalypseBot
-

This is done automatically when commands are selected via the list of suggestions. Please remember that your bot needs to be able to process commands that are followed by its username.

-
Global commands
-

In order to make it easier for users to navigate the bot multiverse, we ask all developers to support a few basic commands. Telegram apps will have interface shortcuts for these commands.

-
    -
  • /start - begins interaction with the user, e.g., by sending a greeting message. This command can also be used to pass additional parameters to the bot (see Deep linking)
  • -
  • /help - returns a help message. It can be a short text about what your bot can do and a list of commands.
  • -
  • /settings - (if applicable) returns the bot's settings for this user and suggests commands to edit these settings.
  • -
-

Users will see a Start button when they first open a conversation with your bot. Help and Settings links will be available in the menu on the bot's profile page.

-
- - - - -
- -

Formatting: bold, italic, fixed-width text and inline links

-

You can use bold, italic or fixed-width text, as well as inline links in your bots' messages. Telegram clients will render them accordingly.

-
-

Read more in the Bot API manual »

-
-

Privacy mode

-

Bots are frequently added to groups in order to augment communication between human users, e.g. by providing news, notifications from external services or additional search functionality. This is especially true for work-related groups. Now, when you share a group with a bot, you tend to ask yourself “How can I be sure that the little rascal isn't selling my chat history to my competitors?” The answer is — privacy mode.

-

A bot running in privacy mode will not receive all messages that people send to the group. Instead, it will only receive:

-
    -
  • Messages that start with a slash '/' (see Commands above)
  • -
  • Replies to the bot's own messages
  • -
  • Service messages (people added or removed from the group, etc.)
  • -
  • Messages from channels where it's a member
  • -
-

On one hand, this helps some of us sleep better at night (in our tinfoil nightcaps), on the other — it allows the bot developer to save a lot of resources, since they won't need to process tens of thousands irrelevant messages each day.

-

Privacy mode is enabled by default for all bots, except bots that were added to the group as admins (bot admins always receive all messages). It can be disabled, so that the bot receives all messages like an ordinary user (the bot will need to be re-added to the group for this change to take effect). We only recommend doing this in cases where it is absolutely necessary for your bot to work — users can always see a bot's current privacy setting in the group members list. In most cases, using the force reply option for the bot's messages should be more than enough.

-

So what messages exactly will my bot get? »

-

Deep linking

-

Telegram bots have a deep linking mechanism, that allows for passing additional parameters to the bot on startup. It could be a command that launches the bot — or an authentication token to connect the user's Telegram account to their account on some external service.

-

Each bot has a link that opens a conversation with it in Telegram — https://t.me/<bot username>. You can add the parameters start or startgroup to this link, with values up to 64 characters long. For example:

-
https://t.me/triviabot?startgroup=test
-

A-Z, a-z, 0-9, _ and - are allowed. We recommend using base64url to encode parameters with binary and other types of content.

-

Following a link with the start parameter will open a one-on-one conversation with the bot, showing a START button in the place of the input field. If the startgroup parameter is used, the user is prompted to select a group to add the bot to. As soon as a user confirms the action (presses the START button in their app or selects a group to add the bot to), your bot will receive a message from that user in this format:

-
/start PAYLOAD
-

PAYLOAD stands for the value of the start or startgroup parameter that was passed in the link.

-
Deep linking Example
-

Suppose the website example.com would like to send notifications to its users via a Telegram bot. Here's what they could do to enable notifications for a user with the ID 123.

-
    -
  1. Create a bot with a suitable username, e.g. @ExampleComBot
  2. -
  3. Set up a webhook for incoming messages
  4. -
  5. Generate a random string of a sufficient length, e.g. $memcache_key = "vCH1vGWJxfSeofSAs0K5PA"
  6. -
  7. Put the value 123 with the key $memcache_key into Memcache for 3600 seconds (one hour)
  8. -
  9. Show our user the button https://t.me/ExampleComBot?start=vCH1vGWJxfSeofSAs0K5PA
  10. -
  11. Configure the webhook processor to query Memcached with the parameter that is passed in incoming messages beginning with /start. If the key exists, record the chat_id passed to the webhook as telegram_chat_id for the user 123. Remove the key from Memcache.
  12. -
  13. Now when we want to send a notification to the user 123, check if they have the field telegram_chat_id. If yes, use the sendMessage method in the Bot API to send them a message in Telegram.
  14. -
-

Location and Number

-

Some bots need extra data from the user to work properly. For example, knowing the user's location helps provide more relevant geo-specific results. The user's phone number can be very useful for integrations with other services, like banks, etc.

-

Bots can ask a user for their location and phone number using special buttons. Note that both phone number and location request buttons will only work in private chats.

-
-
- -
- -

When these buttons are pressed, Telegram clients will display a confirmation alert that tells the user what's about to happen.

-
-

Manual: Number and location buttons »

-
-
-

6. BotFather

-
-

Jump to top to learn everything about Telegram bots »

-
-

BotFather is the one bot to rule them all. It will help you create new bots and change settings for existing ones.

-

Creating a new bot

-

Use the /newbot command to create a new bot. The BotFather will ask you for a name and username, then generate an authentication token for your new bot.

-

The name of your bot is displayed in contact details and elsewhere.

-

The Username is a short name, to be used in mentions and t.me links. Usernames are 5-32 characters long and are case insensitive, but may only include Latin characters, numbers, and underscores. Your bot's username must end in 'bot', e.g. 'tetris_bot' or 'TetrisBot'.

-

The token is a string along the lines of 110201543:AAHdqTcvCH1vGWJxfSeofSAs0K5PALDsaw that is required to authorize the bot and send requests to the Bot API. Keep your token secure and store it safely, it can be used by anyone to control your bot.

-

Generating an authentication token

-

If your existing token is compromised or you lost it for some reason, use the /token command to generate a new one.

-

Botfather commands

-

The remaining commands are pretty self-explanatory:

-
    -
  • /mybots — returns a list of your bots with handy controls to edit their settings
  • -
  • /mygames — does the same for your games
  • -
-

Edit bots

-
    -
  • /setname – change your bot's name.
  • -
  • /setdescription — change the bot's description, a short text of up to 512 characters, describing your bot. Users will see this text at the beginning of the conversation with the bot, titled 'What can this bot do?'.
  • -
  • /setabouttext — change the bot's about info, an even shorter text of up to 120 characters. Users will see this text on the bot's profile page. When they share your bot with someone, this text is sent together with the link.
  • -
  • /setuserpic — change the bot's profile pictures. It's always nice to put a face to a name.
  • -
  • /setcommands — change the list of commands supported by your bot. Users will see these commands as suggestions when they type / in the chat with your bot. Each command has a name (must start with a slash ‘/’, alphanumeric plus underscores, no more than 32 characters, case-insensitive), parameters, and a text description. Users will see the list of commands whenever they type '/' in a conversation with your bot.
  • -
  • /deletebot — delete your bot and free its username.
  • -
-

Edit settings

-
    -
  • /setinline — toggle inline mode for your bot.
  • -
  • /setinlinegeo - request location data to provide location-based inline results.
  • -
  • /setjoingroups — toggle whether your bot can be added to groups or not. Any bot must be able to process private messages, but if your bot was not designed to work in groups, you can disable this.
  • -
  • /setprivacy — set which messages your bot will receive when added to a group. With privacy mode disabled, the bot will receive all messages. We recommend leaving privacy mode enabled. You will need to re-add the bot to existing groups for this change to take effect.
  • -
-

Manage games

-
    -
  • /newgame — create a new game.
  • -
  • /listgames — get a list of your games.
  • -
  • /editgame — edit a game.
  • -
  • /deletegame — delete an existing game.
  • -
-
-

Please note, that it may take a few minutes for changes to take effect.

-
-

Status alerts

-

Millions choose Telegram for its speed. To stay competitive in this environment, your bot also needs to be responsive. In order to help developers keep their bots in shape, Botfather will send status alerts if it sees something is wrong.

-

We will be checking the number of replies and the request/response conversion rate for popular bots (~300 requests per minute: but don't write this down as the value may change in the future). If we get abnormally low readings, you will receive a notification from Botfather.

-
Responding to alerts
-

By default, you will only get one alert per bot per hour. Each alert has the following buttons:

-
    -
  • Fixed. Use this if you found an issue with your bot and fixed it. If you press the fix button, we will resume sending alerts in the regular way so that you can see if your fix worked within 5-10 minutes instead of having to wait for an hour.
  • -
  • Support. Use this to open a chat with @BotSupport if you don't see any issues with your bot or if you think the problem is on our side.
  • -
  • Mute for 8h/1w. Use this if you can't fix your bot at the moment. This will disable all alerts for the bot in question for the specified period of time. We do not recommend using this option since your users may migrate to a more stable bot. You can unmute alerts in your bot's settings via Botfather.
  • -
-
Monitored issues
-

We will currently notify you about the following issues:

-

1.

-
Too few **private messages** are sent compared to previous weeks: **{value}**
-

Your bot is sending much fewer messages than it did in the previous weeks. This is useful for newsletter-style bots that send out messages without prompts from the users. The larger the value, the more significant the difference.

-

2.

-
Too few replies to incoming **private messages**. Conversion rate: **{value}**
-

Your bot is not replying to all messages that are being sent to it (the request/response conversion rate for your bot was too low for at least two of the last three 5-minute periods). To provide a good user experience, please respond to all messages that are sent to your bot. Respond to message updates by calling send… methods (e.g. sendMessage).

-

3.

-
Too few answers to **inline queries**. Conversion rate: **{value}**
-

Your bot is not replying to all inline queries that are being sent to it, calculated in the same way as above. Respond to inline_query updates by calling answerInlineQuery.

-

4.

-
Too few answers to **callback queries**. Conversion rate: **{value}**
-Too few answers to **callback game queries**. Conversion rate: **{value}**
-

Your bot is not replying to all callback queries that are being sent to it (with or without games), calculated in the same way as above. Respond to callback_query updates by calling answerCallbackQuery.

-
-

Please note that the status alerts feature is still being tested and will be improved in the future.

-
-
-

That's it for the introduction. You are now definitely ready to proceed to the BOT API MANUAL.

-

If you've got any questions, please check out our Bot FAQ »

-
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/bots/2-0-intro.html b/data/core.telegram.org/bots/2-0-intro.html deleted file mode 100644 index 1856d954bd..0000000000 --- a/data/core.telegram.org/bots/2-0-intro.html +++ /dev/null @@ -1,230 +0,0 @@ - - - - - Introducing Bot API 2.0 - - - - - - - - - - - - - -
- -
-
-
-
-

Introducing Bot API 2.0

- -
- -
-

Howdy! This text assumes that you‘re familiar with Telegram’s bot platform.
If this is not the case, kindly check out our Introduction to Bots.

-
-

Today we‘re introducing the biggest change to Telegram’s Bot Platform since June 2015. These new tools will help you create fluid and intuitive interfaces for your bots. And bots are becoming a lot more capable. They can now send any type of content supported on Telegram, provide location-based services and integrate with other services deeply based on users' phone numbers.

-

If you'd like a more concise changelog, you can find one in the Bot API Manual.

-

New Inline Keyboards

-

To begin with, we're adding a new type of keyboard that is integrated directly into the message it belongs to. Inline keyboards are available for messages sent both in chat mode and inline mode.

-
- - - -

- - - -
- -

Unlike with custom reply keyboards, pressing buttons on inline keyboards doesn't result in messages sent to the chat. Instead, inline keyboards support buttons that work behind the scenes: callback buttons, URL buttons and switch to inline buttons.

-
-

Manual: Inline keyboards »

-
-

Callback buttons

-

When a user presses a callback button, no messages are sent to the chat. Instead, your bot simply receives the relevant query. Upon receiving the query, your bot can display some result in a notification at the top of the chat screen or in an alert.

-
-

-
- -

Sample bot
@music – This sample music bot uses inline callback buttons to flip pages and reload random results.

-

Read on to updating messages to find out how callback buttons can get even cooler.

-

URL buttons

-

Buttons of this type have a small arrow icon to help the user understand that tapping on a URL button will open an external link. Naturally, we'll show them a confirmation alert before opening the link in the browser.

-
-
-
- -

Switch to Inline buttons

-

Pressing a switch to inline button prompts the user to select a chat, opens it and inserts the bot's username into the input field. You can also pass a query that will be inserted along with the username – this way your users will immediately get some inline results they can share.

-
-

-
- -

Sample bot
@sticker – This sticker search bot offers a ‘switch to inline’ button to teach users how to use it in inline mode.

-

Updating Messages

-

Since inline keyboards don‘t send additional messages to the chat, it made sense to give bots a way of manipulating their existing messages, so that they don’t have to send a new message each time they need to update something. This helps reduce clutter and build more fluid interfaces.

-
-
- -
-
- -

Sample bot
@music – Watch how the music bot updates its messages with search results when you press the navigation buttons.

-
-

Manual: Updating messages »

-
-

Locations and Numbers

-

Some bots need extra data from the user to work properly. For example, knowing the user‘s location helps provide more relevant geo-specific results. The user’s phone number can be very useful for integrations with other services, like banks, etc.

-

We've added an easy way for bots to ask the user for their location and phone number using special buttons. Note that both phone number and location request buttons will only work in private chats.

-
-

-
- -

When these buttons are pressed, Telegram clients will display a confirmation alert that tells the user what's about to happen.

-
-

Manual: Number and location buttons »

-
-

Inline bots can also request location data from their users. Use the /setinlinegeo command with @BotFather to enable this. Your bot will ask the user for permission to access their location whenever they send an inline request.

-

Sample bot
@foursquare – This bot will ask for permission to access the user's location, then provide geo-targeted results.

-

Inline Bots 2.0

-

Speaking of inline bots, they are also getting a major upgrade today.

-

New types of content

-

Inline bots now support all types of content available in Telegram (19 in all), they are now capable of sending stickers, videos, music, locations, documents and more.

-
-

-
- -

Sample bots
@sticker – This sticker bot will accept one or more emoji and search for relevant stickers.
@music – The music bot allows users to send mp3 tracks from a database of public domain classical music.

-
-

Manual: Types of inline content »

-
-

Switching between inline mode and private chat

-

Some inline bots can benefit from an initial setup process, like connecting them to an account on an external service (e.g., YouTube). We've added an easy way of switching between the private chat with a bot and whatever chat the user wants to share inline results in.

-
-

-
- -

You can now display a special ‘Switch to PM’ button above the inline results (or instead of them). This button will open a private chat with the bot and pass a parameter of your choosing, so that you can prompt the user for the relevant setup actions. Once done, you can use an inline keyboard with a switch_inline_query button to send the user back to the original chat.

-

Sample bots
@youtube – Shows a ‘Sign in to YouTube’ button, then suggests personalized results.

-
-

Manual: Switch to PM

-
-

Better inline UI

-

Since sending content via inline bots works differently from sending ordinary messages, we‘ve changed the interface a little. There’s hardly a more effective way of explaining that there‘s no need to hit ’Send':

-
-

-
- -

Tapping on the cross icon once will clear the query, tapping twice will give the ‘Send’ button back to the user.

-

Group Admins

-

As a dessert, we‘re beginning to roll out tools that will allow you to create bot solutions for group admins. As the first step, we’ve added methods to remove members from groups and supergroups.

-
-

Manual: Group management »

-
-

And that's about it for now. Stay tuned for more updates and subscribe to our official @Botnews channel on Telegram.

-
-

Read the full changelog for this update »

-
-
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/bots/api-changelog.html b/data/core.telegram.org/bots/api-changelog.html deleted file mode 100644 index c515fad459..0000000000 --- a/data/core.telegram.org/bots/api-changelog.html +++ /dev/null @@ -1,670 +0,0 @@ - - - - - Bot API changelog - - - - - - - - - - - - - -
- -
-
-
-
-

Bot API changelog

- -
- -
-

The Bot API is an HTTP-based interface created for developers keen on building bots for Telegram.
To learn how to create and set up a bot, please consult our Introduction to Bots »

-
-

You will find all changes to our Bot API on this page.

-

Recent changes

-
-

Subscribe to @BotNews to be the first to know about the latest updates and join the discussion in @BotTalk

-
-

January 31, 2022

-

Bot API 5.7

- -

December 30, 2021

-

Bot API 5.6

- -

December 7, 2021

-

Bot API 5.5

-
    -
  • Bots are now allowed to contact users who sent a join request to a chat where the bot is an administrator with the can_invite_users administrator right – even if the user never interacted with the bot before.
  • -
  • Added support for mentioning users by their ID in inline keyboards. This will only work in Telegram versions released after December 7, 2021. Older clients will display unsupported message.
  • -
  • Added the methods banChatSenderChat and unbanChatSenderChat for banning and unbanning channel chats in supergroups and channels.
  • -
  • Added the field has_private_forwards to the class Chat for private chats, which can be used to check the possibility of mentioning the user by their ID.
  • -
  • Added the field has_protected_content to the classes Chat and Message.
  • -
  • Added the field is_automatic_forward to the class Message.
  • -
-

Note: After this update it will become impossible to forward messages from some chats. Use the fields has_protected_content in the classes Message and Chat to check this.

-

Note: After this update users are able to send messages on behalf of channels they own. Bots are expected to use the field sender_chat in the class Message to correctly support such messages.

-

Note: As previously announced, user identifiers can now have up to 52 significant bits and require a 64-bit integer or double-precision float type to be stored safely.

-

November 5, 2021

-

Bot API 5.4

- -
-
-

⚠️ WARNING! ⚠️
User identifiers will become bigger than 2^31 - 1 before the end of this year and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

-
-
-

June 25, 2021

-

Bot API 5.3

-

Personalized Commands

-
    -
  • Bots can now show lists of commands tailored to specific situations - including localized commands for users with different languages, as well as different commands based on chat type or for specific chats, and special lists of commands for chat admins.
  • -
  • Added the class BotCommandScope, describing the scope to which bot commands apply.
  • -
  • Added the parameters scope and language_code to the method setMyCommands to allow bots specify different commands for different chats and users.
  • -
  • Added the parameters scope and language_code to the method getMyCommands.
  • -
  • Added the method deleteMyCommands to allow deletion of the bot's commands for the given scope and user language.
  • -
  • Improved visibility of bot commands in Telegram apps with the new 'Menu' button in chats with bots, read more on the blog.
  • -
-

Custom Placeholders

- -

And More

-
    -
  • Improved documentation of the class ChatMember by splitting it into 6 subclasses.
  • -
  • Renamed the method kickChatMember to banChatMember. The old method name can still be used.
  • -
  • Renamed the method getChatMembersCount to getChatMemberCount. The old method name can still be used.
  • -
  • Values of the field file_unique_id in objects of the type PhotoSize and of the fields small_file_unique_id and big_file_unique_id in objects of the type ChatPhoto were changed.
  • -
-
-
-

⚠️ WARNING! ⚠️
After one of the upcoming Bot API updates, user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

-
-
-

April 26, 2021

-

Bot API 5.2

-
    -
  • Support for Payments 2.0, see this manual for more details about the Bot Payments API.
  • -
  • Added the type InputInvoiceMessageContent to support sending invoices as inline query results.
  • -
  • Allowed sending invoices to group, supergroup and channel chats.
  • -
  • Added the fields max_tip_amount and suggested_tip_amounts to the method sendInvoice to allow adding optional tips to the payment.
  • -
  • The parameter start_parameter of the method sendInvoice became optional. If the parameter isn't specified, the invoice can be paid directly from forwarded messages.
  • -
  • Added the field chat_type to the class InlineQuery, containing the type of the chat, from which the inline request was sent.
  • -
  • Added the type VoiceChatScheduled and the field voice_chat_scheduled to the class Message.
  • -
  • Fixed an error in sendChatAction documentation to correctly mention “record_voice” and “upload_voice” instead of “record_audio” and “upload_audio” for related to voice note actions. Old action names will still work for backward compatibility.
  • -
-
-
-

⚠️ WARNING! ⚠️
After the next Bot API update (Bot API 5.3) there will be a one-time change of the value of the field file_unique_id in objects of the type PhotoSize and of the fields small_file_unique_id and big_file_unique_id in objects of the type ChatPhoto.

-
-
-
-

⚠️ WARNING! ⚠️
Service messages about non-bot users joining the chat will be soon removed from large groups. We recommend using the “chat_member” update as a replacement.

-
-
-
-

⚠️ WARNING! ⚠️
After one of the upcoming Bot API updates, user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

-
-
-

March 9, 2021

-

Bot API 5.1

-

Added two new update types

-
    -
  • Added updates about member status changes in chats, represented by the class ChatMemberUpdated and the fields my_chat_member and chat_member in the Update class. The bot must be an administrator in the chat to receive chat_member updates about other chat members. By default, only my_chat_member updates about the bot itself are received.
  • -
-

Improved Invite Links

-
    -
  • Added the class ChatInviteLink, representing an invite link to a chat.
  • -
  • Added the method createChatInviteLink, which can be used to create new invite links in addition to the primary invite link.
  • -
  • Added the method editChatInviteLink, which can be used to edit non-primary invite links created by the bot.
  • -
  • Added the method revokeChatInviteLink, which can be used to revoke invite links created by the bot.
  • -
-

Voice Chat Info

- -

And More

-
    -
  • Added the type MessageAutoDeleteTimerChanged and the field message_auto_delete_timer_changed to the class Message.
  • -
  • Added the parameter revoke_messages to the method kickChatMember, allowing to delete all messages from a group for the user who is being removed.
  • -
  • Added the new administrator privilege can_manage_chat to the class ChatMember and parameter can_manage_chat to the method promoteChatMember. This administrator right is implied by any other administrator privilege.
  • -
  • Supported the new bowling animation for the random dice. Choose between different animations (dice, darts, basketball, football, bowling, slot machine) by specifying the emoji parameter in the method sendDice.
  • -
-
-
-

⚠️ WARNING! ⚠️
After one of the upcoming Bot API updates, some user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

-
-
-

November 4, 2020

-

Introducing Bot API 5.0

-

Run Your Own Bot API Server

-
    -
  • Bot API source code is now available at telegram-bot-api. You can now run your own Bot API server locally, boosting your bots' performance.
  • -
  • Added the method logOut, which can be used to log out from the cloud Bot API server before launching your bot locally. You must log out the bot before running it locally, otherwise there is no guarantee that the bot will receive all updates.
  • -
  • Added the method close, which can be used to close the bot instance before moving it from one local server to another.
  • -
-

Transfer Bot Ownership

-
    -
  • You can now use @BotFather to transfer your existing bots to another Telegram account.
  • -
-

Webhooks

-
    -
  • Added the parameter ip_address to the method setWebhook, allowing to bypass DNS resolving and use the specified fixed IP address to send webhook requests.
  • -
  • Added the field ip_address to the class WebhookInfo, containing the current IP address used for webhook connections creation.
  • -
  • Added the ability to drop all pending updates when changing webhook URL using the parameter drop_pending_updates in the methods setWebhook and deleteWebhook.
  • -
-

Working with Groups

-
    -
  • The getChat request now returns the user's bio for private chats if available.
  • -
  • The getChat request now returns the identifier of the linked chat for supergroups and channels, i.e. the discussion group identifier for a channel and vice versa.
  • -
  • The getChat request now returns the location to which the supergroup is connected (see Local Groups). Added the class ChatLocation to represent the location.
  • -
  • Added the parameter only_if_banned to the method unbanChatMember to allow safe unban.
  • -
-

Working with Files

-
    -
  • Added the field file_name to the classes Audio and Video, containing the name of the original file.
  • -
  • Added the ability to disable server-side file content type detection using the parameter disable_content_type_detection in the method sendDocument and the class inputMediaDocument.
  • -
-

Multiple Pinned Messages

-
    -
  • Added the ability to pin messages in private chats.
  • -
  • Added the parameter message_id to the method unpinChatMessage to allow unpinning of the specific pinned message.
  • -
  • Added the method unpinAllChatMessages, which can be used to unpin all pinned messages in a chat.
  • -
-

File Albums

-
    -
  • Added support for sending and receiving audio and document albums in the method sendMediaGroup.
  • -
-

Live Locations

- -

Anonymous Admins

-
    -
  • Added the field sender_chat to the class Message, containing the sender of a message which is a chat (group or channel). For backward compatibility in non-channel chats, the field from in such messages will contain the user 777000 for messages automatically forwarded to the discussion group and the user 1087968824 (@GroupAnonymousBot) for messages from anonymous group administrators.
  • -
  • Added the field is_anonymous to the class chatMember, which can be used to distinguish anonymous chat administrators.
  • -
  • Added the parameter is_anonymous to the method promoteChatMember, which allows to promote anonymous chat administrators. The bot itself should have the is_anonymous right to do this. Despite the fact that bots can have the is_anonymous right, they will never appear as anonymous in the chat. Bots can use the right only for passing to other administrators.
  • -
  • Added the custom title of an anonymous message sender to the class Message as author_signature.
  • -
-

And More

- -

And Last but not Least

-
    -
  • Supported the new football and slot machine animations for the random dice. Choose between different animations (dice, darts, basketball, football, slot machine) by specifying the emoji parameter in the method sendDice.
  • -
-

June 4, 2020

-

Bot API 4.9

-
    -
  • Added the new field via_bot to the Message object. You can now know which bot was used to send a message.
  • -
  • Supported video thumbnails for inline GIF and MPEG4 animations.
  • -
  • Supported the new basketball animation for the random dice. Choose between different animations (dice, darts, basketball) by specifying the emoji parameter in the method sendDice.
  • -
-

April 24, 2020

-

Bot API 4.8

-
    -
  • Supported explanations for Quizzes 2.0. Add explanations by specifying the parameters explanation and explanation_parse_mode in the method sendPoll.
  • -
  • Added the fields explanation and explanation_entities to the Poll object.
  • -
  • Supported timed polls that automatically close at a certain date and time. Set up by specifying the parameter open_period or close_date in the method sendPoll.
  • -
  • Added the fields open_period and close_date to the Poll object.
  • -
  • Supported the new darts animation for the dice mini-game. Choose between the default dice animation and darts animation by specifying the parameter emoji in the method sendDice.
  • -
  • Added the field emoji to the Dice object.
  • -
-

March 30, 2020

-

Bot API 4.7

-
    -
  • Added the method sendDice for sending a dice message, which will have a random value from 1 to 6. (Yes, we're aware of the “proper” singular of die. But it's awkward, and we decided to help it change. One dice at a time!)
  • -
  • Added the field dice to the Message object.
  • -
  • Added the method getMyCommands for getting the current list of the bot's commands.
  • -
  • Added the method setMyCommands for changing the list of the bot's commands through the Bot API instead of @BotFather.
  • -
  • Added the ability to create animated sticker sets by specifying the parameter tgs_sticker instead of png_sticker in the method createNewStickerSet.
  • -
  • Added the ability to add animated stickers to sets created by the bot by specifying the parameter tgs_sticker instead of png_sticker in the method addStickerToSet.
  • -
  • Added the field thumb to the StickerSet object.
  • -
  • Added the ability to change thumbnails of sticker sets created by the bot using the method setStickerSetThumb.
  • -
-

January 23, 2020

-

Bot API 4.6

-
    -
  • Supported Polls 2.0.
  • -
  • Added the ability to send non-anonymous, multiple answer, and quiz-style polls: added the parameters is_anonymous, type, allows_multiple_answers, correct_option_id, is_closed options to the method sendPoll.
  • -
  • Added the object KeyboardButtonPollType and the field request_poll to the object KeyboardButton.
  • -
  • Added updates about changes of user answers in non-anonymous polls, represented by the object PollAnswer and the field poll_answer in the Update object.
  • -
  • Added the fields total_voter_count, is_anonymous, type, allows_multiple_answers, correct_option_id to the Poll object.
  • -
  • Bots can now send polls to private chats.
  • -
  • Added more information about the bot in response to the getMe request: added the fields can_join_groups, can_read_all_group_messages and supports_inline_queries to the User object.
  • -
  • Added the optional field language to the MessageEntity object.
  • -
-

December 31, 2019

-

Bot API 4.5

-
    -
  • Added support for two new MessageEntity types, underline and strikethrough.
  • -
  • Added support for nested MessageEntity objects. Entities can now contain other entities. If two entities have common characters then one of them is fully contained inside the other.
  • -
  • Added support for nested entities and the new tags <u>/<ins> (for underlined text) and <s>/<strike>/<del> (for strikethrough text) in parse mode HTML.
  • -
  • Added a new parse mode, MarkdownV2, which supports nested entities and two new entities __ (for underlined text) and ~ (for strikethrough text). Parse mode Markdown remains unchanged for backward compatibility.
  • -
  • Added the field file_unique_id to the objects Animation, Audio, Document, PassportFile, PhotoSize, Sticker, Video, VideoNote, Voice, File and the fields small_file_unique_id and big_file_unique_id to the object ChatPhoto. The new fields contain a unique file identifier, which is supposed to be the same over time and for different bots, but can't be used to download or reuse the file.
  • -
  • Added the field custom_title to the ChatMember object.
  • -
  • Added the new method setChatAdministratorCustomTitle to manage the custom titles of administrators promoted by the bot.
  • -
  • Added the field slow_mode_delay to the Chat object.
  • -
-

July 29, 2019

-

Bot API 4.4

-
    -
  • Added support for animated stickers. New field is_animated in Sticker and StickerSet objects, animated stickers can now be used in sendSticker and InlineQueryResultCachedSticker.
  • -
  • Added support for default permissions in groups. New object ChatPermissions, containing actions which a member can take in a chat. New field permissions in the Chat object; new method setChatPermissions.
  • -
  • The field all_members_are_administrators has been removed from the documentation for the Chat object. The field is still returned in the object for backward compatibility, but new bots should use the permissions field instead.
  • -
  • Added support for more permissions for group and supergroup members: added the new field can_send_polls to ChatMember object, added can_change_info, can_invite_users, can_pin_messages in ChatMember object for restricted users (previously available only for administrators).
  • -
  • The method restrictChatMember now takes the new user permissions in a single argument of the type ChatPermissions. The old way of passing parameters will keep working for a while for backward compatibility.
  • -
  • Added description support for basic groups (previously available in supergroups and channel chats). You can pass a group's chat_id to setChatDescription and receive the group's description in the Chat object in the response to getChat method.
  • -
  • Added invite_link support for basic groups (previously available in supergroups and channel chats). You can pass a group's chat_id to exportChatInviteLink and receive the group's invite link in the Chat object in the response to getChat method.
  • -
  • File identifiers from the ChatPhoto object are now invalidated and can no longer be used whenever the photo is changed.
  • -
  • All webhook requests from the Bot API are now coming from the subnets 149.154.160.0/20 and 91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.
  • -
  • As of the next Bot API update (version 4.5), nested MessageEntity objects will be allowed in message texts and captions. Please make sure that your code can correctly handle such entities.
  • -
-

May 31, 2019

-

Bot API 4.3

-
    -
  • Added support for Seamless Telegram Login on external websites.
  • -
  • Added the new object LoginUrl and the new field login_url to the InlineKeyboardButton object which allows to automatically authorize users before they go to a URL specified by the bot. Users will be asked to confirm authorization in their Telegram app (needs version 5.7 or higher) when they press the button:
  • -
-
- TITLE -
- -

Also in this update:

-
    -
  • Added the field reply_markup to the Message object, containing the inline keyboard attached to the message.
  • -
  • If a message with an inline keyboard is forwarded, the forwarded message will now have an inline keyboard if the keyboard contained only url and login_url buttons or if the message was sent via a bot and the keyboard contained only url, login_url, switch_inline_query or switch_inline_query_current_chat buttons. In the latter case, switch_inline_query_current_chat buttons are replaced with switch_inline_query buttons.
  • -
  • Bots now receive the edited_message Update even if only Message.reply_markup has changed.
  • -
  • Bots that have the can_edit_messages right in a channel can now use the method editMessageReplyMarkup for messages written by other administrators forever without the 48 hours limit.
  • -
  • Don't forget that starting in July 2019, webhook requests from Bot API will be coming from the subnets 149.154.160.0/20 and 91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.
  • -
-

April 14, 2019

-

Bot API 4.2

-
    -
  • Added support for native polls: added the object Poll, the methods sendPoll and stopPoll and the field poll in the Message and Update objects.
  • -
  • The method deleteMessage can now be used to delete messages sent by a user to the bot in private chats within 48 hours.
  • -
  • Added support for pinned messages in basic groups in addition to supergroups and channel chats: you can pass group's chat_id to pinChatMessage and unpinChatMessage, and receive the pinned group message in Chat object.
  • -
  • Added the field is_member to the ChatMember object, which can be used to find whether a restricted user is a member of the chat.
  • -
  • Added the field forward_sender_name to the Message object, containing name of the sender who has opted to hide their account.
  • -
  • Starting in July 2019, webhook requests from Bot API will be coming from the subnets 149.154.160.0/20 and 91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.
  • -
  • Document thumbnails now should be inscribed in a 320x320 square instead of 90x90.
  • -
-

August 27, 2018

-

Bot API 4.1

- -

July 26, 2018

-

Bot API 4.0.

-
    -
  • Added support for Telegram Passport. See the official announcement on the blog and the manual for details.
  • -
  • Added support for editing the media content of messages: added the method editMessageMedia and new types InputMediaAnimation, InputMediaAudio, and InputMediaDocument.
  • -
  • Added the field thumb to the Audio object to contain the thumbnail of the album cover to which the music file belongs.
  • -
  • Added support for attaching custom thumbnails to uploaded files. For animations, audios, videos and video notes, which are less than 10 MB in size, thumbnails are generated automatically.
  • -
  • tg:// URLs now can be used in inline keyboard url buttons and text_link message entities.
  • -
  • Added the method sendAnimation, which can be used instead of sendDocument to send animations, specifying their duration, width and height.
  • -
  • Added the field animation to the Message object. For backward compatibility, when this field is set, the document field will be also set.
  • -
  • Added two new MessageEntity types: cashtag and phone_number.
  • -
  • Added support for Foursquare venues: added the new field foursquare_type to the objects Venue, InlineQueryResultVenue and InputVenueMessageContent, and the parameter foursquare_type to the sendVenue method.
  • -
  • You can now create inline mentions of users, who have pressed your bot's callback buttons.
  • -
  • You can now use the Retry-After response header to configure the delay after which the Bot API will retry the request after an unsuccessful response from a webhook.
  • -
  • If a webhook returns the HTTP error 410 Gone for all requests for more than 23 hours successively, it can be automatically removed.
  • -
  • Added vCard support when sharing contacts: added the field vcard to the objects Contact, InlineQueryResultContact, InputContactMessageContent and the method sendContact.
  • -
-

February 13, 2018

-

Bot API 3.6.

-
    -
  • Supported text formatting in media captions. Specify the desired parse_mode (Markdown or HTML) when you provide a caption.
  • -
  • In supergroups, if the bot receives a message that is a reply, it will also receive the message to which that message is replying – even if the original message is inaccessible due to the bot's privacy settings. (In other words, replying to any message in a supergroup with a message that mentions the bot or features a command for it acts as forwarding the original message to the bot).
  • -
  • Added the new field connected_website to Message. The bot will receive a message with this field in a private chat when a user logs in on the bot's connected website using the Login Widget and allows sending messages from your bot.
  • -
  • Added the new parameter supports_streaming to the sendVideo method and a field with the same name to the InputMediaVideo object.
  • -
-

November 17, 2017

-

Bot API 3.5.

- -

October 11, 2017

-

Bot API 3.4.

- -

August 23, 2017

-

Bot API 3.3.

-
    -
  • Bots can now mention users via inline mentions, without using usernames.
  • -
  • getChat now also returns pinned messages in supergroups, if present. Added the new field pinned_message to the Chat object.
  • -
  • Added the new fields author_signature and forward_signature to the Message object.
  • -
  • Added the new field is_bot to the User object.
  • -
-

July 21, 2017

-

Bot API 3.2. Teach your bot to handle stickers and sticker sets.

- -

June 30, 2017

-

Bot API 3.1. Build your own robotic police force for supergoups with these new methods for admin bots:

- -

May 18, 2017

-

Introducing Bot API 3.0.

-

NEW Payment Platform

-

See Introduction to Bot Payments for a brief overview. If you're not a developer, you may like this user-friendly blog post better.

- -

NEW Video Messages

-
    -
  • As of Telegram v.4.0, users can send short rounded video messages, using an interface similar to that of voice notes.
  • -
  • Added the sendVideoNote method, the new field video_note to Message, the fields record_video_note or upload_video_note to sendChatAction.
  • -
-

NEW Multilingual Bots

-
    -
  • The User object now may have a language_code field that contains the IETF language tag of the user's language.
  • -
  • Thanks to this, your bot can now offer localized responses to users that speak different languages.
  • -
-

More power to admin bots

-
    -
  • unbanChatMemeber now also works in channels!
  • -
  • New method deleteMessage that allows the bot to delete its own messages, as well as messages posted by other in groups and channels where the bot is an administrator.
  • -
-

Minor Changes

-
    -
  • Replaced the field new_chat_member in Message with new_chat_members (the old field will still be available for a while for compatibility purposes).
  • -
  • Inline keyboards with switch_inline_query and switch_inline_query_current_chat can no longer be sent to channels because they are useless there.
  • -
  • New fields gif_duration in InlineQueryResultGif and mpeg4_duration in InlineQueryResultMpeg4Gif.
  • -
-

December 4, 2016

-

Introducing Bot API 2.3.1, a nifty little update that will give you more control over how your bot gets its updates.

-
    -
  • Use the new field max_connections in setWebhook to optimize your bot's server load
  • -
  • Use allowed_updates in setWebhook and getUpdates to selectively subscribe to updates of a certain type. Among other things, this allows you to stop getting updates about new posts in channels where your bot is an admin.
  • -
  • deleteWebhook moved out of setWebhook to get a whole separate method for itself.
  • -
-

November 21, 2016

-

Bot API 2.3

-
    -
  • Modified bot privacy mode for the sake of consistency.
  • -
  • Your bot can now get updates about posts in channels. Added new fields channel_post and edited_channel_post to Update.

    -
  • -
  • You can now update high scores to a lower value by using the new force parameter in setGameScore. Handy for punishing cheaters or fixing errors in your game's High Score table.

    -
  • -
  • Starting today, messages with high scores will be updated with new high scores by default. Use disable_edit_message in setGameScore if you don't want this.
  • -
  • The edit_message parameter from setGameScore is no longer in use. For backward compatibility, it will be taken into account for a while, unless disable_edit_message is passed explicitly.
  • -
  • Added the new field forward_from_message_id to Message.
  • -
  • Added the new parameter cache_time to answerCallbackQuery. Will eventually work in Telegram apps — somewhere after version 3.14, maybe 3.15.
  • -
  • Renamed hide_keyboard to remove_keyboard in ReplyKeyboardRemove for clarity. hide_keyboard will still work for a while for backward compatibility.
  • -
-

October 3, 2016

-

Bot API 2.2. Introducing a new Gaming Platform! See this introduction for a brief overview.
If you're not a developer, you may like this user-friendly blog post better.

- -

Other changes

- -
    -
  • New field all_members_are_administrators in the Chat object.
  • -
  • Certain server responses may now contain the new parameters field with expanded info on errors that occurred while processing your requests.
  • -
-

May 25, 2016

- -

May 22, 2016

- -

May 12, 2016

- -

May 6, 2016

-
    -
  • Added the field emoji to the Sticker object. Your bot can now know the emoji a sticker corresponds to.
  • -
  • Added the field forward_from_chat to the Message object for messages forwarded from channels.
  • -
-

April 9, 2016

-

Introducing Bot API 2.0. Check out this page for a review of this major update.

- -

Inline bots

-
    -
  • Added support for all content types available on Telegram. 19 types of InlineQueryResult objects are now supported.
  • -
  • Inline bots can now substitute all kinds of content with text. Added 4 types of InputMessageContent objects.
  • -
  • Your inline bot can also ask users for permission to use their location. Added the new Botfather command /setinlinegeo, added field location to the InlineQuery object, added fields location and inline_message_id to the ChosenInlineResult object.
  • -
  • Added an easy way to switch between inline mode and a private chat with the bot – useful for settings, establishing external connections and teaching users how to use your bot in inline mode. Added parameters switch_pm_text and switch_pm_parameter to the method answerInlineQuery.
  • -
-

Miscellaneous

- -

February 20, 2016

-
    -
  • Added the disable_notification parameter to all methods that send messages or any kind.
  • -
  • Removed backward compatibility from the method sendAudio. Voice messages now must be sent using the method sendVoice. There is no more need to specify a non-empty title or performer while sending the audio by file_id.
  • -
-

January 20, 2016

-
    -
  • By the way, you can use both HTML-style and markdown-style formatting in your bot's messages to send bold, italic or fixed-width text and inline links. All official Telegram clients support this. See Formatting options for details.
  • -
-

January 14, 2016

-
    -
  • You can now collect feedback on which results provided by your inline bot get chosen by the users. Added the setinlinefeedback command for Botfather, new type ChosenInlineResult, new field chosen_inline_result to the Update object.
  • -
-

January 4, 2016

- -

November, 2015

-
    -
  • Added support for supergroups. The Type field in the Chat object can now contain 'supergroup'.
  • -
  • New optional fields added to the Message object: supergroup_chat_created, migrate_to_chat_id, migrate_from_chat_id and channel_chat_created.
  • -
-

October 8, 2015

-
    -
  • Added initial channel support for bots (no Telegram clients support this at the moment, please wait for updates):
  • -
  • The Chat field in the Message is now of the new type Chat.
  • -
  • You can now pass a channel username (in the format @channelusername) in the place of chat_id in all methods (and instead of from_chat_id in forwardMessage). For this to work, the bot must be an administrator in the channel (and that's exactly what Telegram clients don't support yet — adding bots as administrators coming soon).
  • -
-

September 18, 2015

-
    -
  • Bots can now download files and media sent by users.
  • -
  • Added getFile and File.
  • -
-

September 7, 2015

-
    -
  • You can now pass parameters using application/json (please note that this doesn't work for file uploads: use multipart/form-data to upload files).
  • -
  • Added very basic markdown support. New field parse_mode added to sendMessage. For the moment messages with markdown will be displayed correctly only in Telegram for Android. Other official apps will catch up soon.
  • -
-

August 29, 2015

-
    -
  • Added support for self-signed certificates: upload your certificate using the certificate parameter in the setWebhook method.
  • -
  • You can now make new requests when responding to webhook updates.
  • -
-

August 15, 2015

-
    -
  • Added new type Voice and new method sendVoice for sending voice messages.
  • -
  • Earlier Audio and sendAudio should now be used for sending music files. Telegram clients will show such files in the in-app music player. If you were using sendAudio for your bot to send voice messages, please use sendVoice instead.
  • -
  • Added optional fields performer, title to the Audio object and sendAudio method.
  • -
  • Added optional field voice to the Message object.
  • -
-

July 2015

-
    -
  • The thumb field is now optional for Video, Sticker and Document objects
  • -
  • The API now supports both video and photo captions. The caption field has been removed from the Video object and added to the Message object instead.
  • -
  • caption and duration optional fields have been added to the sendVideo method.
  • -
  • Fixed typo: user_id in the Contact object is now correctly labeled as Integer, not String
  • -
-

June 24, 2015

-

The bot platform was officially launched.

-
-

Back to the Bot API Manual »

-
-
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/bots/api.html b/data/core.telegram.org/bots/api.html deleted file mode 100644 index b80cdfcfc8..0000000000 --- a/data/core.telegram.org/bots/api.html +++ /dev/null @@ -1,9488 +0,0 @@ - - - - - Telegram Bot API - - - - - - - - - - - - - -
- -
-
-
- -

Telegram Bot API

- -
- -
-

The Bot API is an HTTP-based interface created for developers keen on building bots for Telegram.
To learn how to create and set up a bot, please consult our Introduction to Bots and Bot FAQ.

-
-

Recent changes

-
-

Subscribe to @BotNews to be the first to know about the latest updates and join the discussion in @BotTalk

-
-

January 31, 2022

-

Bot API 5.7

- -

December 30, 2021

-

Bot API 5.6

- -

December 7, 2021

-

Bot API 5.5

-
    -
  • Bots are now allowed to contact users who sent a join request to a chat where the bot is an administrator with the can_invite_users administrator right – even if the user never interacted with the bot before.
  • -
  • Added support for mentioning users by their ID in inline keyboards. This will only work in Telegram versions released after December 7, 2021. Older clients will display unsupported message.
  • -
  • Added the methods banChatSenderChat and unbanChatSenderChat for banning and unbanning channel chats in supergroups and channels.
  • -
  • Added the field has_private_forwards to the class Chat for private chats, which can be used to check the possibility of mentioning the user by their ID.
  • -
  • Added the field has_protected_content to the classes Chat and Message.
  • -
  • Added the field is_automatic_forward to the class Message.
  • -
-

Note: After this update it will become impossible to forward messages from some chats. Use the fields has_protected_content in the classes Message and Chat to check this.

-

Note: After this update users are able to send messages on behalf of channels they own. Bots are expected to use the field sender_chat in the class Message to correctly support such messages.

-

Note: As previously announced, user identifiers can now have up to 52 significant bits and require a 64-bit integer or double-precision float type to be stored safely.

-

November 5, 2021

-

Bot API 5.4

- -

See earlier changes »

-

Authorizing your bot

-

Each bot is given a unique authentication token when it is created. The token looks something like 123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11, but we'll use simply <token> in this document instead. You can learn about obtaining tokens and generating new ones in this document.

-

Making requests

-

All queries to the Telegram Bot API must be served over HTTPS and need to be presented in this form: https://api.telegram.org/bot<token>/METHOD_NAME. Like this for example:

-
https://api.telegram.org/bot123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11/getMe
-

We support GET and POST HTTP methods. We support four ways of passing parameters in Bot API requests:

-
    -
  • URL query string
  • -
  • application/x-www-form-urlencoded
  • -
  • application/json (except for uploading files)
  • -
  • multipart/form-data (use to upload files)
  • -
-

The response contains a JSON object, which always has a Boolean field 'ok' and may have an optional String field 'description' with a human-readable description of the result. If 'ok' equals True, the request was successful and the result of the query can be found in the 'result' field. In case of an unsuccessful request, 'ok' equals false and the error is explained in the 'description'. An Integer 'error_code' field is also returned, but its contents are subject to change in the future. Some errors may also have an optional field 'parameters' of the type ResponseParameters, which can help to automatically handle the error.

-
    -
  • All methods in the Bot API are case-insensitive.
  • -
  • All queries must be made using UTF-8.
  • -
-

Making requests when getting updates

-

If you're using webhooks, you can perform a request to the Bot API while sending an answer to the webhook. Use either application/json or application/x-www-form-urlencoded or multipart/form-data response content type for passing parameters. Specify the method to be invoked in the method parameter of the request. It's not possible to know that such a request was successful or get its result.

-
-

Please see our FAQ for examples.

-
-

Using a Local Bot API Server

-

The Bot API server source code is available at telegram-bot-api. You can run it locally and send the requests to your own server instead of https://api.telegram.org. If you switch to a local Bot API server, your bot will be able to:

-
    -
  • Download files without a size limit.
  • -
  • Upload files up to 2000 MB.
  • -
  • Upload files using their local path and the file URI scheme.
  • -
  • Use an HTTP URL for the webhook.
  • -
  • Use any local IP address for the webhook.
  • -
  • Use any port for the webhook.
  • -
  • Set max_webhook_connections up to 100000.
  • -
  • Receive the absolute local path as a value of the file_path field without the need to download the file after a getFile request.
  • -
-

Do I need a Local Bot API Server

-

The majority of bots will be OK with the default configuration, running on our servers. But if you feel that you need one of these features, you're welcome to switch to your own at any time.

-

Getting updates

-

There are two mutually exclusive ways of receiving updates for your bot — the getUpdates method on one hand and Webhooks on the other. Incoming updates are stored on the server until the bot receives them either way, but they will not be kept longer than 24 hours.

-

Regardless of which option you choose, you will receive JSON-serialized Update objects as a result.

-

Update

-

This object represents an incoming update.
At most one of the optional parameters can be present in any given update.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
update_idIntegerThe update's unique identifier. Update identifiers start from a certain positive number and increase sequentially. This ID becomes especially handy if you're using Webhooks, since it allows you to ignore repeated updates or to restore the correct update sequence, should they get out of order. If there are no new updates for at least a week, then identifier of the next update will be chosen randomly instead of sequentially.
messageMessageOptional. New incoming message of any kind — text, photo, sticker, etc.
edited_messageMessageOptional. New version of a message that is known to the bot and was edited
channel_postMessageOptional. New incoming channel post of any kind — text, photo, sticker, etc.
edited_channel_postMessageOptional. New version of a channel post that is known to the bot and was edited
inline_queryInlineQueryOptional. New incoming inline query
chosen_inline_resultChosenInlineResultOptional. The result of an inline query that was chosen by a user and sent to their chat partner. Please see our documentation on the feedback collecting for details on how to enable these updates for your bot.
callback_queryCallbackQueryOptional. New incoming callback query
shipping_queryShippingQueryOptional. New incoming shipping query. Only for invoices with flexible price
pre_checkout_queryPreCheckoutQueryOptional. New incoming pre-checkout query. Contains full information about checkout
pollPollOptional. New poll state. Bots receive only updates about stopped polls and polls, which are sent by the bot
poll_answerPollAnswerOptional. A user changed their answer in a non-anonymous poll. Bots receive new votes only in polls that were sent by the bot itself.
my_chat_memberChatMemberUpdatedOptional. The bot's chat member status was updated in a chat. For private chats, this update is received only when the bot is blocked or unblocked by the user.
chat_memberChatMemberUpdatedOptional. A chat member's status was updated in a chat. The bot must be an administrator in the chat and must explicitly specify “chat_member” in the list of allowed_updates to receive these updates.
chat_join_requestChatJoinRequestOptional. A request to join the chat has been sent. The bot must have the can_invite_users administrator right in the chat to receive these updates.
-

getUpdates

-

Use this method to receive incoming updates using long polling (wiki). An Array of Update objects is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
offsetIntegerOptionalIdentifier of the first update to be returned. Must be greater by one than the highest among the identifiers of previously received updates. By default, updates starting with the earliest unconfirmed update are returned. An update is considered confirmed as soon as getUpdates is called with an offset higher than its update_id. The negative offset can be specified to retrieve updates starting from -offset update from the end of the updates queue. All previous updates will forgotten.
limitIntegerOptionalLimits the number of updates to be retrieved. Values between 1-100 are accepted. Defaults to 100.
timeoutIntegerOptionalTimeout in seconds for long polling. Defaults to 0, i.e. usual short polling. Should be positive, short polling should be used for testing purposes only.
allowed_updatesArray of StringOptionalA JSON-serialized list of the update types you want your bot to receive. For example, specify [“message”, “edited_channel_post”, “callback_query”] to only receive updates of these types. See Update for a complete list of available update types. Specify an empty list to receive all update types except chat_member (default). If not specified, the previous setting will be used.

Please note that this parameter doesn't affect updates created before the call to the getUpdates, so unwanted updates may be received for a short period of time.
-
-

Notes
1. This method will not work if an outgoing webhook is set up.
2. In order to avoid getting duplicate updates, recalculate offset after each server response.

-
-

setWebhook

-

Use this method to specify a url and receive incoming updates via an outgoing webhook. Whenever there is an update for the bot, we will send an HTTPS POST request to the specified url, containing a JSON-serialized Update. In case of an unsuccessful request, we will give up after a reasonable amount of attempts. Returns True on success.

-

If you'd like to make sure that the Webhook request comes from Telegram, we recommend using a secret path in the URL, e.g. https://www.example.com/<token>. Since nobody else knows your bot's token, you can be pretty sure it's us.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
urlStringYesHTTPS url to send updates to. Use an empty string to remove webhook integration
certificateInputFileOptionalUpload your public key certificate so that the root certificate in use can be checked. See our self-signed guide for details.
ip_addressStringOptionalThe fixed IP address which will be used to send webhook requests instead of the IP address resolved through DNS
max_connectionsIntegerOptionalMaximum allowed number of simultaneous HTTPS connections to the webhook for update delivery, 1-100. Defaults to 40. Use lower values to limit the load on your bot's server, and higher values to increase your bot's throughput.
allowed_updatesArray of StringOptionalA JSON-serialized list of the update types you want your bot to receive. For example, specify [“message”, “edited_channel_post”, “callback_query”] to only receive updates of these types. See Update for a complete list of available update types. Specify an empty list to receive all update types except chat_member (default). If not specified, the previous setting will be used.
Please note that this parameter doesn't affect updates created before the call to the setWebhook, so unwanted updates may be received for a short period of time.
drop_pending_updatesBooleanOptionalPass True to drop all pending updates
-
-

Notes
1. You will not be able to receive updates using getUpdates for as long as an outgoing webhook is set up.
2. To use a self-signed certificate, you need to upload your public key certificate using certificate parameter. Please upload as InputFile, sending a String will not work.
3. Ports currently supported for Webhooks: 443, 80, 88, 8443.

-

NEW! If you're having any trouble setting up webhooks, please check out this amazing guide to Webhooks.

-
-

deleteWebhook

-

Use this method to remove webhook integration if you decide to switch back to getUpdates. Returns True on success.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
drop_pending_updatesBooleanOptionalPass True to drop all pending updates
-

getWebhookInfo

-

Use this method to get current webhook status. Requires no parameters. On success, returns a WebhookInfo object. If the bot is using getUpdates, will return an object with the url field empty.

-

WebhookInfo

-

Contains information about the current status of a webhook.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
urlStringWebhook URL, may be empty if webhook is not set up
has_custom_certificateBooleanTrue, if a custom certificate was provided for webhook certificate checks
pending_update_countIntegerNumber of updates awaiting delivery
ip_addressStringOptional. Currently used webhook IP address
last_error_dateIntegerOptional. Unix time for the most recent error that happened when trying to deliver an update via webhook
last_error_messageStringOptional. Error message in human-readable format for the most recent error that happened when trying to deliver an update via webhook
max_connectionsIntegerOptional. Maximum allowed number of simultaneous HTTPS connections to the webhook for update delivery
allowed_updatesArray of StringOptional. A list of update types the bot is subscribed to. Defaults to all update types except chat_member
-

Available types

-

All types used in the Bot API responses are represented as JSON-objects.

-

It is safe to use 32-bit signed integers for storing all Integer fields unless otherwise noted.

-
-

Optional fields may be not returned when irrelevant.

-
-

User

-

This object represents a Telegram user or bot.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
idIntegerUnique identifier for this user or bot. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a 64-bit integer or double-precision float type are safe for storing this identifier.
is_botBooleanTrue, if this user is a bot
first_nameStringUser's or bot's first name
last_nameStringOptional. User's or bot's last name
usernameStringOptional. User's or bot's username
language_codeStringOptional. IETF language tag of the user's language
can_join_groupsBooleanOptional. True, if the bot can be invited to groups. Returned only in getMe.
can_read_all_group_messagesBooleanOptional. True, if privacy mode is disabled for the bot. Returned only in getMe.
supports_inline_queriesBooleanOptional. True, if the bot supports inline queries. Returned only in getMe.
-

Chat

-

This object represents a chat.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
idIntegerUnique identifier for this chat. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier.
typeStringType of chat, can be either “private”, “group”, “supergroup” or “channel”
titleStringOptional. Title, for supergroups, channels and group chats
usernameStringOptional. Username, for private chats, supergroups and channels if available
first_nameStringOptional. First name of the other party in a private chat
last_nameStringOptional. Last name of the other party in a private chat
photoChatPhotoOptional. Chat photo. Returned only in getChat.
bioStringOptional. Bio of the other party in a private chat. Returned only in getChat.
has_private_forwardsTrueOptional. True, if privacy settings of the other party in the private chat allows to use tg://user?id=<user_id> links only in chats with the user. Returned only in getChat.
descriptionStringOptional. Description, for groups, supergroups and channel chats. Returned only in getChat.
invite_linkStringOptional. Primary invite link, for groups, supergroups and channel chats. Returned only in getChat.
pinned_messageMessageOptional. The most recent pinned message (by sending date). Returned only in getChat.
permissionsChatPermissionsOptional. Default chat member permissions, for groups and supergroups. Returned only in getChat.
slow_mode_delayIntegerOptional. For supergroups, the minimum allowed delay between consecutive messages sent by each unpriviledged user; in seconds. Returned only in getChat.
message_auto_delete_timeIntegerOptional. The time after which all messages sent to the chat will be automatically deleted; in seconds. Returned only in getChat.
has_protected_contentTrueOptional. True, if messages from the chat can't be forwarded to other chats. Returned only in getChat.
sticker_set_nameStringOptional. For supergroups, name of group sticker set. Returned only in getChat.
can_set_sticker_setTrueOptional. True, if the bot can change the group sticker set. Returned only in getChat.
linked_chat_idIntegerOptional. Unique identifier for the linked chat, i.e. the discussion group identifier for a channel and vice versa; for supergroups and channel chats. This identifier may be greater than 32 bits and some programming languages may have difficulty/silent defects in interpreting it. But it is smaller than 52 bits, so a signed 64 bit integer or double-precision float type are safe for storing this identifier. Returned only in getChat.
locationChatLocationOptional. For supergroups, the location to which the supergroup is connected. Returned only in getChat.
-

Message

-

This object represents a message.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
message_idIntegerUnique message identifier inside this chat
fromUserOptional. Sender of the message; empty for messages sent to channels. For backward compatibility, the field contains a fake sender user in non-channel chats, if the message was sent on behalf of a chat.
sender_chatChatOptional. Sender of the message, sent on behalf of a chat. For example, the channel itself for channel posts, the supergroup itself for messages from anonymous group administrators, the linked channel for messages automatically forwarded to the discussion group. For backward compatibility, the field from contains a fake sender user in non-channel chats, if the message was sent on behalf of a chat.
dateIntegerDate the message was sent in Unix time
chatChatConversation the message belongs to
forward_fromUserOptional. For forwarded messages, sender of the original message
forward_from_chatChatOptional. For messages forwarded from channels or from anonymous administrators, information about the original sender chat
forward_from_message_idIntegerOptional. For messages forwarded from channels, identifier of the original message in the channel
forward_signatureStringOptional. For forwarded messages that were originally sent in channels or by an anonymous chat administrator, signature of the message sender if present
forward_sender_nameStringOptional. Sender's name for messages forwarded from users who disallow adding a link to their account in forwarded messages
forward_dateIntegerOptional. For forwarded messages, date the original message was sent in Unix time
is_automatic_forwardTrueOptional. True, if the message is a channel post that was automatically forwarded to the connected discussion group
reply_to_messageMessageOptional. For replies, the original message. Note that the Message object in this field will not contain further reply_to_message fields even if it itself is a reply.
via_botUserOptional. Bot through which the message was sent
edit_dateIntegerOptional. Date the message was last edited in Unix time
has_protected_contentTrueOptional. True, if the message can't be forwarded
media_group_idStringOptional. The unique identifier of a media message group this message belongs to
author_signatureStringOptional. Signature of the post author for messages in channels, or the custom title of an anonymous group administrator
textStringOptional. For text messages, the actual UTF-8 text of the message, 0-4096 characters
entitiesArray of MessageEntityOptional. For text messages, special entities like usernames, URLs, bot commands, etc. that appear in the text
animationAnimationOptional. Message is an animation, information about the animation. For backward compatibility, when this field is set, the document field will also be set
audioAudioOptional. Message is an audio file, information about the file
documentDocumentOptional. Message is a general file, information about the file
photoArray of PhotoSizeOptional. Message is a photo, available sizes of the photo
stickerStickerOptional. Message is a sticker, information about the sticker
videoVideoOptional. Message is a video, information about the video
video_noteVideoNoteOptional. Message is a video note, information about the video message
voiceVoiceOptional. Message is a voice message, information about the file
captionStringOptional. Caption for the animation, audio, document, photo, video or voice, 0-1024 characters
caption_entitiesArray of MessageEntityOptional. For messages with a caption, special entities like usernames, URLs, bot commands, etc. that appear in the caption
contactContactOptional. Message is a shared contact, information about the contact
diceDiceOptional. Message is a dice with random value
gameGameOptional. Message is a game, information about the game. More about games »
pollPollOptional. Message is a native poll, information about the poll
venueVenueOptional. Message is a venue, information about the venue. For backward compatibility, when this field is set, the location field will also be set
locationLocationOptional. Message is a shared location, information about the location
new_chat_membersArray of UserOptional. New members that were added to the group or supergroup and information about them (the bot itself may be one of these members)
left_chat_memberUserOptional. A member was removed from the group, information about them (this member may be the bot itself)
new_chat_titleStringOptional. A chat title was changed to this value
new_chat_photoArray of PhotoSizeOptional. A chat photo was change to this value
delete_chat_photoTrueOptional. Service message: the chat photo was deleted
group_chat_createdTrueOptional. Service message: the group has been created
supergroup_chat_createdTrueOptional. Service message: the supergroup has been created. This field can't be received in a message coming through updates, because bot can't be a member of a supergroup when it is created. It can only be found in reply_to_message if someone replies to a very first message in a directly created supergroup.
channel_chat_createdTrueOptional. Service message: the channel has been created. This field can't be received in a message coming through updates, because bot can't be a member of a channel when it is created. It can only be found in reply_to_message if someone replies to a very first message in a channel.
message_auto_delete_timer_changedMessageAutoDeleteTimerChangedOptional. Service message: auto-delete timer settings changed in the chat
migrate_to_chat_idIntegerOptional. The group has been migrated to a supergroup with the specified identifier. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier.
migrate_from_chat_idIntegerOptional. The supergroup has been migrated from a group with the specified identifier. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier.
pinned_messageMessageOptional. Specified message was pinned. Note that the Message object in this field will not contain further reply_to_message fields even if it is itself a reply.
invoiceInvoiceOptional. Message is an invoice for a payment, information about the invoice. More about payments »
successful_paymentSuccessfulPaymentOptional. Message is a service message about a successful payment, information about the payment. More about payments »
connected_websiteStringOptional. The domain name of the website on which the user has logged in. More about Telegram Login »
passport_dataPassportDataOptional. Telegram Passport data
proximity_alert_triggeredProximityAlertTriggeredOptional. Service message. A user in the chat triggered another user's proximity alert while sharing Live Location.
voice_chat_scheduledVoiceChatScheduledOptional. Service message: voice chat scheduled
voice_chat_startedVoiceChatStartedOptional. Service message: voice chat started
voice_chat_endedVoiceChatEndedOptional. Service message: voice chat ended
voice_chat_participants_invitedVoiceChatParticipantsInvitedOptional. Service message: new participants invited to a voice chat
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message. login_url buttons are represented as ordinary url buttons.
-

MessageId

-

This object represents a unique message identifier.

- - - - - - - - - - - - - - - -
FieldTypeDescription
message_idIntegerUnique message identifier
-

MessageEntity

-

This object represents one special entity in a text message. For example, hashtags, usernames, URLs, etc.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the entity. Currently, can be “mention” (@username), “hashtag” (#hashtag), “cashtag” ($USD), “bot_command” (/start@jobs_bot), “url” (https://telegram.org), “email” (do-not-reply@telegram.org), “phone_number” (+1-212-555-0123), “bold” (bold text), “italic” (italic text), “underline” (underlined text), “strikethrough” (strikethrough text), “spoiler” (spoiler message), “code” (monowidth string), “pre” (monowidth block), “text_link” (for clickable text URLs), “text_mention” (for users without usernames)
offsetIntegerOffset in UTF-16 code units to the start of the entity
lengthIntegerLength of the entity in UTF-16 code units
urlStringOptional. For “text_link” only, url that will be opened after user taps on the text
userUserOptional. For “text_mention” only, the mentioned user
languageStringOptional. For “pre” only, the programming language of the entity text
-

PhotoSize

-

This object represents one size of a photo or a file / sticker thumbnail.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
widthIntegerPhoto width
heightIntegerPhoto height
file_sizeIntegerOptional. File size in bytes
-

Animation

-

This object represents an animation file (GIF or H.264/MPEG-4 AVC video without sound).

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
widthIntegerVideo width as defined by sender
heightIntegerVideo height as defined by sender
durationIntegerDuration of the video in seconds as defined by sender
thumbPhotoSizeOptional. Animation thumbnail as defined by sender
file_nameStringOptional. Original animation filename as defined by sender
mime_typeStringOptional. MIME type of the file as defined by sender
file_sizeIntegerOptional. File size in bytes
-

Audio

-

This object represents an audio file to be treated as music by the Telegram clients.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
durationIntegerDuration of the audio in seconds as defined by sender
performerStringOptional. Performer of the audio as defined by sender or by audio tags
titleStringOptional. Title of the audio as defined by sender or by audio tags
file_nameStringOptional. Original filename as defined by sender
mime_typeStringOptional. MIME type of the file as defined by sender
file_sizeIntegerOptional. File size in bytes
thumbPhotoSizeOptional. Thumbnail of the album cover to which the music file belongs
-

Document

-

This object represents a general file (as opposed to photos, voice messages and audio files).

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
thumbPhotoSizeOptional. Document thumbnail as defined by sender
file_nameStringOptional. Original filename as defined by sender
mime_typeStringOptional. MIME type of the file as defined by sender
file_sizeIntegerOptional. File size in bytes
-

Video

-

This object represents a video file.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
widthIntegerVideo width as defined by sender
heightIntegerVideo height as defined by sender
durationIntegerDuration of the video in seconds as defined by sender
thumbPhotoSizeOptional. Video thumbnail
file_nameStringOptional. Original filename as defined by sender
mime_typeStringOptional. Mime type of a file as defined by sender
file_sizeIntegerOptional. File size in bytes
-

VideoNote

-

This object represents a video message (available in Telegram apps as of v.4.0).

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
lengthIntegerVideo width and height (diameter of the video message) as defined by sender
durationIntegerDuration of the video in seconds as defined by sender
thumbPhotoSizeOptional. Video thumbnail
file_sizeIntegerOptional. File size in bytes
-

Voice

-

This object represents a voice note.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
durationIntegerDuration of the audio in seconds as defined by sender
mime_typeStringOptional. MIME type of the file as defined by sender
file_sizeIntegerOptional. File size in bytes
-

Contact

-

This object represents a phone contact.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
phone_numberStringContact's phone number
first_nameStringContact's first name
last_nameStringOptional. Contact's last name
user_idIntegerOptional. Contact's user identifier in Telegram. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a 64-bit integer or double-precision float type are safe for storing this identifier.
vcardStringOptional. Additional data about the contact in the form of a vCard
-

Dice

-

This object represents an animated emoji that displays a random value.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
emojiStringEmoji on which the dice throw animation is based
valueIntegerValue of the dice, 1-6 for “🎲”, “🎯” and “🎳” base emoji, 1-5 for “🏀” and “⚽” base emoji, 1-64 for “🎰” base emoji
-

PollOption

-

This object contains information about one answer option in a poll.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
textStringOption text, 1-100 characters
voter_countIntegerNumber of users that voted for this option
-

PollAnswer

-

This object represents an answer of a user in a non-anonymous poll.

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
poll_idStringUnique poll identifier
userUserThe user, who changed the answer to the poll
option_idsArray of Integer0-based identifiers of answer options, chosen by the user. May be empty if the user retracted their vote.
-

Poll

-

This object contains information about a poll.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
idStringUnique poll identifier
questionStringPoll question, 1-300 characters
optionsArray of PollOptionList of poll options
total_voter_countIntegerTotal number of users that voted in the poll
is_closedBooleanTrue, if the poll is closed
is_anonymousBooleanTrue, if the poll is anonymous
typeStringPoll type, currently can be “regular” or “quiz”
allows_multiple_answersBooleanTrue, if the poll allows multiple answers
correct_option_idIntegerOptional. 0-based identifier of the correct answer option. Available only for polls in the quiz mode, which are closed, or was sent (not forwarded) by the bot or to the private chat with the bot.
explanationStringOptional. Text that is shown when a user chooses an incorrect answer or taps on the lamp icon in a quiz-style poll, 0-200 characters
explanation_entitiesArray of MessageEntityOptional. Special entities like usernames, URLs, bot commands, etc. that appear in the explanation
open_periodIntegerOptional. Amount of time in seconds the poll will be active after creation
close_dateIntegerOptional. Point in time (Unix timestamp) when the poll will be automatically closed
-

Location

-

This object represents a point on the map.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
longitudeFloatLongitude as defined by sender
latitudeFloatLatitude as defined by sender
horizontal_accuracyFloat numberOptional. The radius of uncertainty for the location, measured in meters; 0-1500
live_periodIntegerOptional. Time relative to the message sending date, during which the location can be updated; in seconds. For active live locations only.
headingIntegerOptional. The direction in which user is moving, in degrees; 1-360. For active live locations only.
proximity_alert_radiusIntegerOptional. Maximum distance for proximity alerts about approaching another chat member, in meters. For sent live locations only.
-

Venue

-

This object represents a venue.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
locationLocationVenue location. Can't be a live location
titleStringName of the venue
addressStringAddress of the venue
foursquare_idStringOptional. Foursquare identifier of the venue
foursquare_typeStringOptional. Foursquare type of the venue. (For example, “arts_entertainment/default”, “arts_entertainment/aquarium” or “food/icecream”.)
google_place_idStringOptional. Google Places identifier of the venue
google_place_typeStringOptional. Google Places type of the venue. (See supported types.)
-

ProximityAlertTriggered

-

This object represents the content of a service message, sent whenever a user in the chat triggers a proximity alert set by another user.

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
travelerUserUser that triggered the alert
watcherUserUser that set the alert
distanceIntegerThe distance between the users
-

MessageAutoDeleteTimerChanged

-

This object represents a service message about a change in auto-delete timer settings.

- - - - - - - - - - - - - - - -
FieldTypeDescription
message_auto_delete_timeIntegerNew auto-delete time for messages in the chat; in seconds
-

VoiceChatScheduled

-

This object represents a service message about a voice chat scheduled in the chat.

- - - - - - - - - - - - - - - -
FieldTypeDescription
start_dateIntegerPoint in time (Unix timestamp) when the voice chat is supposed to be started by a chat administrator
-

VoiceChatStarted

-

This object represents a service message about a voice chat started in the chat. Currently holds no information.

-

VoiceChatEnded

-

This object represents a service message about a voice chat ended in the chat.

- - - - - - - - - - - - - - - -
FieldTypeDescription
durationIntegerVoice chat duration in seconds
-

VoiceChatParticipantsInvited

-

This object represents a service message about new members invited to a voice chat.

- - - - - - - - - - - - - - - -
FieldTypeDescription
usersArray of UserOptional. New members that were invited to the voice chat
-

UserProfilePhotos

-

This object represent a user's profile pictures.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
total_countIntegerTotal number of profile pictures the target user has
photosArray of Array of PhotoSizeRequested profile pictures (in up to 4 sizes each)
-

File

-

This object represents a file ready to be downloaded. The file can be downloaded via the link https://api.telegram.org/file/bot<token>/<file_path>. It is guaranteed that the link will be valid for at least 1 hour. When the link expires, a new one can be requested by calling getFile.

-
-

Maximum file size to download is 20 MB

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
file_sizeIntegerOptional. File size in bytes, if known
file_pathStringOptional. File path. Use https://api.telegram.org/file/bot<token>/<file_path> to get the file.
-

ReplyKeyboardMarkup

-

This object represents a custom keyboard with reply options (see Introduction to bots for details and examples).

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
keyboardArray of Array of KeyboardButtonArray of button rows, each represented by an Array of KeyboardButton objects
resize_keyboardBooleanOptional. Requests clients to resize the keyboard vertically for optimal fit (e.g., make the keyboard smaller if there are just two rows of buttons). Defaults to false, in which case the custom keyboard is always of the same height as the app's standard keyboard.
one_time_keyboardBooleanOptional. Requests clients to hide the keyboard as soon as it's been used. The keyboard will still be available, but clients will automatically display the usual letter-keyboard in the chat – the user can press a special button in the input field to see the custom keyboard again. Defaults to false.
input_field_placeholderStringOptional. The placeholder to be shown in the input field when the keyboard is active; 1-64 characters
selectiveBooleanOptional. Use this parameter if you want to show the keyboard to specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.

Example: A user requests to change the bot's language, bot replies to the request with a keyboard to select the new language. Other users in the group don't see the keyboard.
-

KeyboardButton

-

This object represents one button of the reply keyboard. For simple text buttons String can be used instead of this object to specify text of the button. Optional fields request_contact, request_location, and request_poll are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
textStringText of the button. If none of the optional fields are used, it will be sent as a message when the button is pressed
request_contactBooleanOptional. If True, the user's phone number will be sent as a contact when the button is pressed. Available in private chats only
request_locationBooleanOptional. If True, the user's current location will be sent when the button is pressed. Available in private chats only
request_pollKeyboardButtonPollTypeOptional. If specified, the user will be asked to create a poll and send it to the bot when the button is pressed. Available in private chats only
-

Note: request_contact and request_location options will only work in Telegram versions released after 9 April, 2016. Older clients will display unsupported message.
Note: request_poll option will only work in Telegram versions released after 23 January, 2020. Older clients will display unsupported message.

-

KeyboardButtonPollType

-

This object represents type of a poll, which is allowed to be created and sent when the corresponding button is pressed.

- - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringOptional. If quiz is passed, the user will be allowed to create only polls in the quiz mode. If regular is passed, only regular polls will be allowed. Otherwise, the user will be allowed to create a poll of any type.
-

ReplyKeyboardRemove

-

Upon receiving a message with this object, Telegram clients will remove the current custom keyboard and display the default letter-keyboard. By default, custom keyboards are displayed until a new keyboard is sent by a bot. An exception is made for one-time keyboards that are hidden immediately after the user presses a button (see ReplyKeyboardMarkup).

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
remove_keyboardTrueRequests clients to remove the custom keyboard (user will not be able to summon this keyboard; if you want to hide the keyboard from sight but keep it accessible, use one_time_keyboard in ReplyKeyboardMarkup)
selectiveBooleanOptional. Use this parameter if you want to remove the keyboard for specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.

Example: A user votes in a poll, bot returns confirmation message in reply to the vote and removes the keyboard for that user, while still showing the keyboard with poll options to users who haven't voted yet.
-

InlineKeyboardMarkup

-

This object represents an inline keyboard that appears right next to the message it belongs to.

- - - - - - - - - - - - - - - -
FieldTypeDescription
inline_keyboardArray of Array of InlineKeyboardButtonArray of button rows, each represented by an Array of InlineKeyboardButton objects
-

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will display unsupported message.

-

InlineKeyboardButton

-

This object represents one button of an inline keyboard. You must use exactly one of the optional fields.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
textStringLabel text on the button
urlStringOptional. HTTP or tg:// url to be opened when the button is pressed. Links tg://user?id=<user_id> can be used to mention a user by their ID without using a username, if this is allowed by their privacy settings.
login_urlLoginUrlOptional. An HTTP URL used to automatically authorize the user. Can be used as a replacement for the Telegram Login Widget.
callback_dataStringOptional. Data to be sent in a callback query to the bot when button is pressed, 1-64 bytes
switch_inline_queryStringOptional. If set, pressing the button will prompt the user to select one of their chats, open that chat and insert the bot's username and the specified inline query in the input field. Can be empty, in which case just the bot's username will be inserted.

Note: This offers an easy way for users to start using your bot in inline mode when they are currently in a private chat with it. Especially useful when combined with switch_pm… actions – in this case the user will be automatically returned to the chat they switched from, skipping the chat selection screen.
switch_inline_query_current_chatStringOptional. If set, pressing the button will insert the bot's username and the specified inline query in the current chat's input field. Can be empty, in which case only the bot's username will be inserted.

This offers a quick way for the user to open your bot in inline mode in the same chat – good for selecting something from multiple options.
callback_gameCallbackGameOptional. Description of the game that will be launched when the user presses the button.

NOTE: This type of button must always be the first button in the first row.
payBooleanOptional. Specify True, to send a Pay button.

NOTE: This type of button must always be the first button in the first row and can only be used in invoice messages.
-

LoginUrl

-

This object represents a parameter of the inline keyboard button used to automatically authorize a user. Serves as a great replacement for the Telegram Login Widget when the user is coming from Telegram. All the user needs to do is tap/click a button and confirm that they want to log in:

-
- TITLE -
- -

Telegram apps support these buttons as of version 5.7.

-
-

Sample bot: @discussbot

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
urlStringAn HTTP URL to be opened with user authorization data added to the query string when the button is pressed. If the user refuses to provide authorization data, the original URL without information about the user will be opened. The data added is the same as described in Receiving authorization data.

NOTE: You must always check the hash of the received data to verify the authentication and the integrity of the data as described in Checking authorization.
forward_textStringOptional. New text of the button in forwarded messages.
bot_usernameStringOptional. Username of a bot, which will be used for user authorization. See Setting up a bot for more details. If not specified, the current bot's username will be assumed. The url's domain must be the same as the domain linked with the bot. See Linking your domain to the bot for more details.
request_write_accessBooleanOptional. Pass True to request the permission for your bot to send messages to the user.
-

CallbackQuery

-

This object represents an incoming callback query from a callback button in an inline keyboard. If the button that originated the query was attached to a message sent by the bot, the field message will be present. If the button was attached to a message sent via the bot (in inline mode), the field inline_message_id will be present. Exactly one of the fields data or game_short_name will be present.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
idStringUnique identifier for this query
fromUserSender
messageMessageOptional. Message with the callback button that originated the query. Note that message content and message date will not be available if the message is too old
inline_message_idStringOptional. Identifier of the message sent via the bot in inline mode, that originated the query.
chat_instanceStringGlobal identifier, uniquely corresponding to the chat to which the message with the callback button was sent. Useful for high scores in games.
dataStringOptional. Data associated with the callback button. Be aware that a bad client can send arbitrary data in this field.
game_short_nameStringOptional. Short name of a Game to be returned, serves as the unique identifier for the game
-
-

NOTE: After the user presses a callback button, Telegram clients will display a progress bar until you call answerCallbackQuery. It is, therefore, necessary to react by calling answerCallbackQuery even if no notification to the user is needed (e.g., without specifying any of the optional parameters).

-
-

ForceReply

-

Upon receiving a message with this object, Telegram clients will display a reply interface to the user (act as if the user has selected the bot's message and tapped 'Reply'). This can be extremely useful if you want to create user-friendly step-by-step interfaces without having to sacrifice privacy mode.

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
force_replyTrueShows reply interface to the user, as if they manually selected the bot's message and tapped 'Reply'
input_field_placeholderStringOptional. The placeholder to be shown in the input field when the reply is active; 1-64 characters
selectiveBooleanOptional. Use this parameter if you want to force reply from specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.
-
-

Example: A poll bot for groups runs in privacy mode (only receives commands, replies to its messages and mentions). There could be two ways to create a new poll:

-
    -
  • Explain the user how to send a command with parameters (e.g. /newpoll question answer1 answer2). May be appealing for hardcore users but lacks modern day polish.
  • -
  • Guide the user through a step-by-step process. 'Please send me your question', 'Cool, now let's add the first answer option', 'Great. Keep adding answer options, then send /done when you're ready'.
  • -
-

The last option is definitely more attractive. And if you use ForceReply in your bot's questions, it will receive the user's answers even if it only receives replies, commands and mentions — without any extra work for the user.

-
-

ChatPhoto

-

This object represents a chat photo.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
small_file_idStringFile identifier of small (160x160) chat photo. This file_id can be used only for photo download and only for as long as the photo is not changed.
small_file_unique_idStringUnique file identifier of small (160x160) chat photo, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
big_file_idStringFile identifier of big (640x640) chat photo. This file_id can be used only for photo download and only for as long as the photo is not changed.
big_file_unique_idStringUnique file identifier of big (640x640) chat photo, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
-

ChatInviteLink

-

Represents an invite link for a chat.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
invite_linkStringThe invite link. If the link was created by another chat administrator, then the second part of the link will be replaced with “…”.
creatorUserCreator of the link
creates_join_requestBooleanTrue, if users joining the chat via the link need to be approved by chat administrators
is_primaryBooleanTrue, if the link is primary
is_revokedBooleanTrue, if the link is revoked
nameStringOptional. Invite link name
expire_dateIntegerOptional. Point in time (Unix timestamp) when the link will expire or has been expired
member_limitIntegerOptional. Maximum number of users that can be members of the chat simultaneously after joining the chat via this invite link; 1-99999
pending_join_request_countIntegerOptional. Number of pending join requests created using this link
-

ChatMember

-

This object contains information about one member of a chat. Currently, the following 6 types of chat members are supported:

- -

ChatMemberOwner

-

Represents a chat member that owns the chat and has all administrator privileges.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
statusStringThe member's status in the chat, always “creator”
userUserInformation about the user
is_anonymousBooleanTrue, if the user's presence in the chat is hidden
custom_titleStringOptional. Custom title for this user
-

ChatMemberAdministrator

-

Represents a chat member that has some additional privileges.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
statusStringThe member's status in the chat, always “administrator”
userUserInformation about the user
can_be_editedBooleanTrue, if the bot is allowed to edit administrator privileges of that user
is_anonymousBooleanTrue, if the user's presence in the chat is hidden
can_manage_chatBooleanTrue, if the administrator can access the chat event log, chat statistics, message statistics in channels, see channel members, see anonymous administrators in supergroups and ignore slow mode. Implied by any other administrator privilege
can_delete_messagesBooleanTrue, if the administrator can delete messages of other users
can_manage_voice_chatsBooleanTrue, if the administrator can manage voice chats
can_restrict_membersBooleanTrue, if the administrator can restrict, ban or unban chat members
can_promote_membersBooleanTrue, if the administrator can add new administrators with a subset of their own privileges or demote administrators that he has promoted, directly or indirectly (promoted by administrators that were appointed by the user)
can_change_infoBooleanTrue, if the user is allowed to change the chat title, photo and other settings
can_invite_usersBooleanTrue, if the user is allowed to invite new users to the chat
can_post_messagesBooleanOptional. True, if the administrator can post in the channel; channels only
can_edit_messagesBooleanOptional. True, if the administrator can edit messages of other users and can pin messages; channels only
can_pin_messagesBooleanOptional. True, if the user is allowed to pin messages; groups and supergroups only
custom_titleStringOptional. Custom title for this user
-

ChatMemberMember

-

Represents a chat member that has no additional privileges or restrictions.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
statusStringThe member's status in the chat, always “member”
userUserInformation about the user
-

ChatMemberRestricted

-

Represents a chat member that is under certain restrictions in the chat. Supergroups only.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
statusStringThe member's status in the chat, always “restricted”
userUserInformation about the user
is_memberBooleanTrue, if the user is a member of the chat at the moment of the request
can_change_infoBooleanTrue, if the user is allowed to change the chat title, photo and other settings
can_invite_usersBooleanTrue, if the user is allowed to invite new users to the chat
can_pin_messagesBooleanTrue, if the user is allowed to pin messages
can_send_messagesBooleanTrue, if the user is allowed to send text messages, contacts, locations and venues
can_send_media_messagesBooleanTrue, if the user is allowed to send audios, documents, photos, videos, video notes and voice notes
can_send_pollsBooleanTrue, if the user is allowed to send polls
can_send_other_messagesBooleanTrue, if the user is allowed to send animations, games, stickers and use inline bots
can_add_web_page_previewsBooleanTrue, if the user is allowed to add web page previews to their messages
until_dateIntegerDate when restrictions will be lifted for this user; unix time. If 0, then the user is restricted forever
-

ChatMemberLeft

-

Represents a chat member that isn't currently a member of the chat, but may join it themselves.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
statusStringThe member's status in the chat, always “left”
userUserInformation about the user
-

ChatMemberBanned

-

Represents a chat member that was banned in the chat and can't return to the chat or view chat messages.

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
statusStringThe member's status in the chat, always “kicked”
userUserInformation about the user
until_dateIntegerDate when restrictions will be lifted for this user; unix time. If 0, then the user is banned forever
-

ChatMemberUpdated

-

This object represents changes in the status of a chat member.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
chatChatChat the user belongs to
fromUserPerformer of the action, which resulted in the change
dateIntegerDate the change was done in Unix time
old_chat_memberChatMemberPrevious information about the chat member
new_chat_memberChatMemberNew information about the chat member
invite_linkChatInviteLinkOptional. Chat invite link, which was used by the user to join the chat; for joining by invite link events only.
-

ChatJoinRequest

-

Represents a join request sent to a chat.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
chatChatChat to which the request was sent
fromUserUser that sent the join request
dateIntegerDate the request was sent in Unix time
bioStringOptional. Bio of the user.
invite_linkChatInviteLinkOptional. Chat invite link that was used by the user to send the join request
-

ChatPermissions

-

Describes actions that a non-administrator user is allowed to take in a chat.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
can_send_messagesBooleanOptional. True, if the user is allowed to send text messages, contacts, locations and venues
can_send_media_messagesBooleanOptional. True, if the user is allowed to send audios, documents, photos, videos, video notes and voice notes, implies can_send_messages
can_send_pollsBooleanOptional. True, if the user is allowed to send polls, implies can_send_messages
can_send_other_messagesBooleanOptional. True, if the user is allowed to send animations, games, stickers and use inline bots, implies can_send_media_messages
can_add_web_page_previewsBooleanOptional. True, if the user is allowed to add web page previews to their messages, implies can_send_media_messages
can_change_infoBooleanOptional. True, if the user is allowed to change the chat title, photo and other settings. Ignored in public supergroups
can_invite_usersBooleanOptional. True, if the user is allowed to invite new users to the chat
can_pin_messagesBooleanOptional. True, if the user is allowed to pin messages. Ignored in public supergroups
-

ChatLocation

-

Represents a location to which a chat is connected.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
locationLocationThe location to which the supergroup is connected. Can't be a live location.
addressStringLocation address; 1-64 characters, as defined by the chat owner
-

BotCommand

-

This object represents a bot command.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
commandStringText of the command; 1-32 characters. Can contain only lowercase English letters, digits and underscores.
descriptionStringDescription of the command; 1-256 characters.
-

BotCommandScope

-

This object represents the scope to which bot commands are applied. Currently, the following 7 scopes are supported:

- -

Determining list of commands

-

The following algorithm is used to determine the list of commands for a particular user viewing the bot menu. The first list of commands which is set is returned:

-

Commands in the chat with the bot

-
    -
  • botCommandScopeChat + language_code
  • -
  • botCommandScopeChat
  • -
  • botCommandScopeAllPrivateChats + language_code
  • -
  • botCommandScopeAllPrivateChats
  • -
  • botCommandScopeDefault + language_code
  • -
  • botCommandScopeDefault
  • -
-

Commands in group and supergroup chats

-
    -
  • botCommandScopeChatMember + language_code
  • -
  • botCommandScopeChatMember
  • -
  • botCommandScopeChatAdministrators + language_code (administrators only)
  • -
  • botCommandScopeChatAdministrators (administrators only)
  • -
  • botCommandScopeChat + language_code
  • -
  • botCommandScopeChat
  • -
  • botCommandScopeAllChatAdministrators + language_code (administrators only)
  • -
  • botCommandScopeAllChatAdministrators (administrators only)
  • -
  • botCommandScopeAllGroupChats + language_code
  • -
  • botCommandScopeAllGroupChats
  • -
  • botCommandScopeDefault + language_code
  • -
  • botCommandScopeDefault
  • -
-

BotCommandScopeDefault

-

Represents the default scope of bot commands. Default commands are used if no commands with a narrower scope are specified for the user.

- - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringScope type, must be default
-

BotCommandScopeAllPrivateChats

-

Represents the scope of bot commands, covering all private chats.

- - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringScope type, must be all_private_chats
-

BotCommandScopeAllGroupChats

-

Represents the scope of bot commands, covering all group and supergroup chats.

- - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringScope type, must be all_group_chats
-

BotCommandScopeAllChatAdministrators

-

Represents the scope of bot commands, covering all group and supergroup chat administrators.

- - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringScope type, must be all_chat_administrators
-

BotCommandScopeChat

-

Represents the scope of bot commands, covering a specific chat.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringScope type, must be chat
chat_idInteger or StringUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
-

BotCommandScopeChatAdministrators

-

Represents the scope of bot commands, covering all administrators of a specific group or supergroup chat.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringScope type, must be chat_administrators
chat_idInteger or StringUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
-

BotCommandScopeChatMember

-

Represents the scope of bot commands, covering a specific member of a group or supergroup chat.

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringScope type, must be chat_member
chat_idInteger or StringUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
user_idIntegerUnique identifier of the target user
-

ResponseParameters

-

Contains information about why a request was unsuccessful.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
migrate_to_chat_idIntegerOptional. The group has been migrated to a supergroup with the specified identifier. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier.
retry_afterIntegerOptional. In case of exceeding flood control, the number of seconds left to wait before the request can be repeated
-

InputMedia

-

This object represents the content of a media message to be sent. It should be one of

- -

InputMediaPhoto

-

Represents a photo to be sent.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be photo
mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
captionStringOptional. Caption of the photo to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the photo caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
-

InputMediaVideo

-

Represents a video to be sent.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be video
mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
thumbInputFile or StringOptional. Thumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptional. Caption of the video to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the video caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
widthIntegerOptional. Video width
heightIntegerOptional. Video height
durationIntegerOptional. Video duration in seconds
supports_streamingBooleanOptional. Pass True, if the uploaded video is suitable for streaming
-

InputMediaAnimation

-

Represents an animation file (GIF or H.264/MPEG-4 AVC video without sound) to be sent.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be animation
mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
thumbInputFile or StringOptional. Thumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptional. Caption of the animation to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the animation caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
widthIntegerOptional. Animation width
heightIntegerOptional. Animation height
durationIntegerOptional. Animation duration in seconds
-

InputMediaAudio

-

Represents an audio file to be treated as music to be sent.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be audio
mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
thumbInputFile or StringOptional. Thumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptional. Caption of the audio to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the audio caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
durationIntegerOptional. Duration of the audio in seconds
performerStringOptional. Performer of the audio
titleStringOptional. Title of the audio
-

InputMediaDocument

-

Represents a general file to be sent.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be document
mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass “attach://<file_attach_name>” to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
thumbInputFile or StringOptional. Thumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptional. Caption of the document to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the document caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
disable_content_type_detectionBooleanOptional. Disables automatic server-side content type detection for files uploaded using multipart/form-data. Always True, if the document is sent as part of an album.
-

InputFile

-

This object represents the contents of a file to be uploaded. Must be posted using multipart/form-data in the usual way that files are uploaded via the browser.

-

Sending files

-

There are three ways to send files (photos, stickers, audio, media, etc.):

-
    -
  1. If the file is already stored somewhere on the Telegram servers, you don't need to reupload it: each file object has a file_id field, simply pass this file_id as a parameter instead of uploading. There are no limits for files sent this way.
  2. -
  3. Provide Telegram with an HTTP URL for the file to be sent. Telegram will download and send the file. 5 MB max size for photos and 20 MB max for other types of content.
  4. -
  5. Post the file using multipart/form-data in the usual way that files are uploaded via the browser. 10 MB max size for photos, 50 MB for other files.
  6. -
-

Sending by file_id

-
    -
  • It is not possible to change the file type when resending by file_id. I.e. a video can't be sent as a photo, a photo can't be sent as a document, etc.
  • -
  • It is not possible to resend thumbnails.
  • -
  • Resending a photo by file_id will send all of its sizes.
  • -
  • file_id is unique for each individual bot and can't be transferred from one bot to another.
  • -
  • file_id uniquely identifies a file, but a file can have different valid file_ids even for the same bot.
  • -
-

Sending by URL

-
    -
  • When sending by URL the target file must have the correct MIME type (e.g., audio/mpeg for sendAudio, etc.).
  • -
  • In sendDocument, sending by URL will currently only work for GIF, PDF and ZIP files.
  • -
  • To use sendVoice, the file must have the type audio/ogg and be no more than 1MB in size. 1-20MB voice notes will be sent as files.
  • -
  • Other configurations may work but we can't guarantee that they will.
  • -
-

Inline mode objects

-

Objects and methods used in the inline mode are described in the Inline mode section.

-

Available methods

-
-

All methods in the Bot API are case-insensitive. We support GET and POST HTTP methods. Use either URL query string or application/json or application/x-www-form-urlencoded or multipart/form-data for passing parameters in Bot API requests.
On successful call, a JSON-object containing the result will be returned.

-
-

getMe

-

A simple method for testing your bot's authentication token. Requires no parameters. Returns basic information about the bot in form of a User object.

-

logOut

-

Use this method to log out from the cloud Bot API server before launching the bot locally. You must log out the bot before running it locally, otherwise there is no guarantee that the bot will receive updates. After a successful call, you can immediately log in on a local server, but will not be able to log in back to the cloud Bot API server for 10 minutes. Returns True on success. Requires no parameters.

-

close

-

Use this method to close the bot instance before moving it from one local server to another. You need to delete the webhook before calling this method to ensure that the bot isn't launched again after server restart. The method will return error 429 in the first 10 minutes after the bot is launched. Returns True on success. Requires no parameters.

-

sendMessage

-

Use this method to send text messages. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
textStringYesText of the message to be sent, 1-4096 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the message text. See formatting options for more details.
entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in message text, which can be specified instead of parse_mode
disable_web_page_previewBooleanOptionalDisables link previews for links in this message
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

Formatting options

-

The Bot API supports basic formatting for messages. You can use bold, italic, underlined, strikethrough, and spoiler text, as well as inline links and pre-formatted code in your bots' messages. Telegram clients will render them accordingly. You can use either markdown-style or HTML-style formatting.

-

Note that Telegram clients will display an alert to the user before opening an inline link ('Open this link?' together with the full URL).

-

Message entities can be nested, providing following restrictions are met:
- If two entities have common characters then one of them is fully contained inside another.
- bold, italic, underline, strikethrough, and spoiler entities can contain and can be part of any other entities, except pre and code.
- All other entities can't contain each other.

-

Links tg://user?id=<user_id> can be used to mention a user by their ID without using a username. Please note:

-
    -
  • These links will work only if they are used inside an inline link or in an inline keyboard button. For example, they will not work, when used in a message text.
  • -
  • These mentions are only guaranteed to work if the user has contacted the bot in the past, has sent a callback query to the bot via an inline button or is a member in the group where he was mentioned.
  • -
-
MarkdownV2 style
-

To use this mode, pass MarkdownV2 in the parse_mode field. Use the following syntax in your message:

-
*bold \*text*
-_italic \*text_
-__underline__
-~strikethrough~
-||spoiler||
-*bold _italic bold ~italic bold strikethrough ||italic bold strikethrough spoiler||~ __underline italic bold___ bold*
-[inline URL](http://www.example.com/)
-[inline mention of a user](tg://user?id=123456789)
-`inline fixed-width code`
-```
-pre-formatted fixed-width code block
-```
-```python
-pre-formatted fixed-width code block written in the Python programming language
-```
-

Please note:

-
    -
  • Any character with code between 1 and 126 inclusively can be escaped anywhere with a preceding '\' character, in which case it is treated as an ordinary character and not a part of the markup. This implies that '\' character usually must be escaped with a preceding '\' character.
  • -
  • Inside pre and code entities, all '`' and '\' characters must be escaped with a preceding '\' character.
  • -
  • Inside (...) part of inline link definition, all ')' and '\' must be escaped with a preceding '\' character.
  • -
  • In all other places characters '_', '*', '[', ']', '(', ')', '~', '`', '>', '#', '+', '-', '=', '|', '{', '}', '.', '!' must be escaped with the preceding character '\'.
  • -
  • In case of ambiguity between italic and underline entities __ is always greadily treated from left to right as beginning or end of underline entity, so instead of ___italic underline___ use ___italic underline_\r__, where \r is a character with code 13, which will be ignored.
  • -
-
HTML style
-

To use this mode, pass HTML in the parse_mode field. The following tags are currently supported:

-
<b>bold</b>, <strong>bold</strong>
-<i>italic</i>, <em>italic</em>
-<u>underline</u>, <ins>underline</ins>
-<s>strikethrough</s>, <strike>strikethrough</strike>, <del>strikethrough</del>
-<span class="tg-spoiler">spoiler</span>, <tg-spoiler>spoiler</tg-spoiler>
-<b>bold <i>italic bold <s>italic bold strikethrough <span class="tg-spoiler">italic bold strikethrough spoiler</span></s> <u>underline italic bold</u></i> bold</b>
-<a href="http://www.example.com/">inline URL</a>
-<a href="tg://user?id=123456789">inline mention of a user</a>
-<code>inline fixed-width code</code>
-<pre>pre-formatted fixed-width code block</pre>
-<pre><code class="language-python">pre-formatted fixed-width code block written in the Python programming language</code></pre>
-

Please note:

-
    -
  • Only the tags mentioned above are currently supported.
  • -
  • All <, > and & symbols that are not a part of a tag or an HTML entity must be replaced with the corresponding HTML entities (< with &lt;, > with &gt; and & with &amp;).
  • -
  • All numerical HTML entities are supported.
  • -
  • The API currently supports only the following named HTML entities: &lt;, &gt;, &amp; and &quot;.
  • -
  • Use nested pre and code tags, to define programming language for pre entity.
  • -
  • Programming language can't be specified for standalone code tags.
  • -
-
Markdown style
-

This is a legacy mode, retained for backward compatibility. To use this mode, pass Markdown in the parse_mode field. Use the following syntax in your message:

-
*bold text*
-_italic text_
-[inline URL](http://www.example.com/)
-[inline mention of a user](tg://user?id=123456789)
-`inline fixed-width code`
-```
-pre-formatted fixed-width code block
-```
-```python
-pre-formatted fixed-width code block written in the Python programming language
-```
-

Please note:

-
    -
  • Entities must not be nested, use parse mode MarkdownV2 instead.
  • -
  • There is no way to specify underline and strikethrough entities, use parse mode MarkdownV2 instead.
  • -
  • To escape characters '_', '*', '`', '[' outside of an entity, prepend the characters '\' before them.
  • -
  • Escaping inside entities is not allowed, so entity must be closed first and reopened again: use _snake_\__case_ for italic snake_case and *2*\**2=4* for bold 2*2=4.
  • -
-

forwardMessage

-

Use this method to forward messages of any kind. Service messages can't be forwarded. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
from_chat_idInteger or StringYesUnique identifier for the chat where the original message was sent (or channel username in the format @channelusername)
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the forwarded message from forwarding and saving
message_idIntegerYesMessage identifier in the chat specified in from_chat_id
-

copyMessage

-

Use this method to copy messages of any kind. Service messages and invoice messages can't be copied. The method is analogous to the method forwardMessage, but the copied message doesn't have a link to the original message. Returns the MessageId of the sent message on success.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
from_chat_idInteger or StringYesUnique identifier for the chat where the original message was sent (or channel username in the format @channelusername)
message_idIntegerYesMessage identifier in the chat specified in from_chat_id
captionStringOptionalNew caption for media, 0-1024 characters after entities parsing. If not specified, the original caption is kept
parse_modeStringOptionalMode for parsing entities in the new caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the new caption, which can be specified instead of parse_mode
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

sendPhoto

-

Use this method to send photos. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
photoInputFile or StringYesPhoto to send. Pass a file_id as String to send a photo that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a photo from the Internet, or upload a new photo using multipart/form-data. The photo must be at most 10 MB in size. The photo's width and height must not exceed 10000 in total. Width and height ratio must be at most 20. More info on Sending Files »
captionStringOptionalPhoto caption (may also be used when resending photos by file_id), 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the photo caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

sendAudio

-

Use this method to send audio files, if you want Telegram clients to display them in the music player. Your audio must be in the .MP3 or .M4A format. On success, the sent Message is returned. Bots can currently send audio files of up to 50 MB in size, this limit may be changed in the future.

-

For sending voice messages, use the sendVoice method instead.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
audioInputFile or StringYesAudio file to send. Pass a file_id as String to send an audio file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get an audio file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
captionStringOptionalAudio caption, 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the audio caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
durationIntegerOptionalDuration of the audio in seconds
performerStringOptionalPerformer
titleStringOptionalTrack name
thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

sendDocument

-

Use this method to send general files. On success, the sent Message is returned. Bots can currently send files of any type of up to 50 MB in size, this limit may be changed in the future.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
documentInputFile or StringYesFile to send. Pass a file_id as String to send a file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptionalDocument caption (may also be used when resending documents by file_id), 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the document caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
disable_content_type_detectionBooleanOptionalDisables automatic server-side content type detection for files uploaded using multipart/form-data
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

sendVideo

-

Use this method to send video files, Telegram clients support mp4 videos (other formats may be sent as Document). On success, the sent Message is returned. Bots can currently send video files of up to 50 MB in size, this limit may be changed in the future.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
videoInputFile or StringYesVideo to send. Pass a file_id as String to send a video that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a video from the Internet, or upload a new video using multipart/form-data. More info on Sending Files »
durationIntegerOptionalDuration of sent video in seconds
widthIntegerOptionalVideo width
heightIntegerOptionalVideo height
thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptionalVideo caption (may also be used when resending videos by file_id), 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the video caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
supports_streamingBooleanOptionalPass True, if the uploaded video is suitable for streaming
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

sendAnimation

-

Use this method to send animation files (GIF or H.264/MPEG-4 AVC video without sound). On success, the sent Message is returned. Bots can currently send animation files of up to 50 MB in size, this limit may be changed in the future.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
animationInputFile or StringYesAnimation to send. Pass a file_id as String to send an animation that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get an animation from the Internet, or upload a new animation using multipart/form-data. More info on Sending Files »
durationIntegerOptionalDuration of sent animation in seconds
widthIntegerOptionalAnimation width
heightIntegerOptionalAnimation height
thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptionalAnimation caption (may also be used when resending animation by file_id), 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the animation caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

sendVoice

-

Use this method to send audio files, if you want Telegram clients to display the file as a playable voice message. For this to work, your audio must be in an .OGG file encoded with OPUS (other formats may be sent as Audio or Document). On success, the sent Message is returned. Bots can currently send voice messages of up to 50 MB in size, this limit may be changed in the future.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
voiceInputFile or StringYesAudio file to send. Pass a file_id as String to send a file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
captionStringOptionalVoice message caption, 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the voice message caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
durationIntegerOptionalDuration of the voice message in seconds
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

sendVideoNote

-

As of v.4.0, Telegram clients support rounded square mp4 videos of up to 1 minute long. Use this method to send video messages. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
video_noteInputFile or StringYesVideo note to send. Pass a file_id as String to send a video note that exists on the Telegram servers (recommended) or upload a new video using multipart/form-data. More info on Sending Files ». Sending video notes by a URL is currently unsupported
durationIntegerOptionalDuration of sent video in seconds
lengthIntegerOptionalVideo width and height, i.e. diameter of the video message
thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass “attach://<file_attach_name>” if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

sendMediaGroup

-

Use this method to send a group of photos, videos, documents or audios as an album. Documents and audio files can be only grouped in an album with messages of the same type. On success, an array of Messages that were sent is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
mediaArray of InputMediaAudio, InputMediaDocument, InputMediaPhoto and InputMediaVideoYesA JSON-serialized array describing messages to be sent, must include 2-10 items
disable_notificationBooleanOptionalSends messages silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent messages from forwarding and saving
reply_to_message_idIntegerOptionalIf the messages are a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
-

sendLocation

-

Use this method to send point on the map. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
latitudeFloat numberYesLatitude of the location
longitudeFloat numberYesLongitude of the location
horizontal_accuracyFloat numberOptionalThe radius of uncertainty for the location, measured in meters; 0-1500
live_periodIntegerOptionalPeriod in seconds for which the location will be updated (see Live Locations, should be between 60 and 86400.
headingIntegerOptionalFor live locations, a direction in which the user is moving, in degrees. Must be between 1 and 360 if specified.
proximity_alert_radiusIntegerOptionalFor live locations, a maximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

editMessageLiveLocation

-

Use this method to edit live location messages. A location can be edited until its live_period expires or editing is explicitly disabled by a call to stopMessageLiveLocation. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
latitudeFloat numberYesLatitude of new location
longitudeFloat numberYesLongitude of new location
horizontal_accuracyFloat numberOptionalThe radius of uncertainty for the location, measured in meters; 0-1500
headingIntegerOptionalDirection in which the user is moving, in degrees. Must be between 1 and 360 if specified.
proximity_alert_radiusIntegerOptionalMaximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for a new inline keyboard.
-

stopMessageLiveLocation

-

Use this method to stop updating a live location message before live_period expires. On success, if the message is not an inline message, the edited Message is returned, otherwise True is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message with live location to stop
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for a new inline keyboard.
-

sendVenue

-

Use this method to send information about a venue. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
latitudeFloat numberYesLatitude of the venue
longitudeFloat numberYesLongitude of the venue
titleStringYesName of the venue
addressStringYesAddress of the venue
foursquare_idStringOptionalFoursquare identifier of the venue
foursquare_typeStringOptionalFoursquare type of the venue, if known. (For example, “arts_entertainment/default”, “arts_entertainment/aquarium” or “food/icecream”.)
google_place_idStringOptionalGoogle Places identifier of the venue
google_place_typeStringOptionalGoogle Places type of the venue. (See supported types.)
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

sendContact

-

Use this method to send phone contacts. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
phone_numberStringYesContact's phone number
first_nameStringYesContact's first name
last_nameStringOptionalContact's last name
vcardStringOptionalAdditional data about the contact in the form of a vCard, 0-2048 bytes
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove keyboard or to force a reply from the user.
-

sendPoll

-

Use this method to send a native poll. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
questionStringYesPoll question, 1-300 characters
optionsArray of StringYesA JSON-serialized list of answer options, 2-10 strings 1-100 characters each
is_anonymousBooleanOptionalTrue, if the poll needs to be anonymous, defaults to True
typeStringOptionalPoll type, “quiz” or “regular”, defaults to “regular”
allows_multiple_answersBooleanOptionalTrue, if the poll allows multiple answers, ignored for polls in quiz mode, defaults to False
correct_option_idIntegerOptional0-based identifier of the correct answer option, required for polls in quiz mode
explanationStringOptionalText that is shown when a user chooses an incorrect answer or taps on the lamp icon in a quiz-style poll, 0-200 characters with at most 2 line feeds after entities parsing
explanation_parse_modeStringOptionalMode for parsing entities in the explanation. See formatting options for more details.
explanation_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the poll explanation, which can be specified instead of parse_mode
open_periodIntegerOptionalAmount of time in seconds the poll will be active after creation, 5-600. Can't be used together with close_date.
close_dateIntegerOptionalPoint in time (Unix timestamp) when the poll will be automatically closed. Must be at least 5 and no more than 600 seconds in the future. Can't be used together with open_period.
is_closedBooleanOptionalPass True, if the poll needs to be immediately closed. This can be useful for poll preview.
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

sendDice

-

Use this method to send an animated emoji that will display a random value. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
emojiStringOptionalEmoji on which the dice throw animation is based. Currently, must be one of “🎲”, “🎯”, “🏀”, “⚽”, “🎳”, or “🎰”. Dice can have values 1-6 for “🎲”, “🎯” and “🎳”, values 1-5 for “🏀” and “⚽”, and values 1-64 for “🎰”. Defaults to “🎲
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

sendChatAction

-

Use this method when you need to tell the user that something is happening on the bot's side. The status is set for 5 seconds or less (when a message arrives from your bot, Telegram clients clear its typing status). Returns True on success.

-
-

Example: The ImageBot needs some time to process a request and upload the image. Instead of sending a text message along the lines of “Retrieving image, please wait…”, the bot may use sendChatAction with action = upload_photo. The user will see a “sending photo” status for the bot.

-
-

We only recommend using this method when a response from the bot will take a noticeable amount of time to arrive.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
actionStringYesType of action to broadcast. Choose one, depending on what the user is about to receive: typing for text messages, upload_photo for photos, record_video or upload_video for videos, record_voice or upload_voice for voice notes, upload_document for general files, choose_sticker for stickers, find_location for location data, record_video_note or upload_video_note for video notes.
-

getUserProfilePhotos

-

Use this method to get a list of profile pictures for a user. Returns a UserProfilePhotos object.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
user_idIntegerYesUnique identifier of the target user
offsetIntegerOptionalSequential number of the first photo to be returned. By default, all photos are returned.
limitIntegerOptionalLimits the number of photos to be retrieved. Values between 1-100 are accepted. Defaults to 100.
-

getFile

-

Use this method to get basic info about a file and prepare it for downloading. For the moment, bots can download files of up to 20MB in size. On success, a File object is returned. The file can then be downloaded via the link https://api.telegram.org/file/bot<token>/<file_path>, where <file_path> is taken from the response. It is guaranteed that the link will be valid for at least 1 hour. When the link expires, a new one can be requested by calling getFile again.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
file_idStringYesFile identifier to get info about
-

Note: This function may not preserve the original file name and MIME type. You should save the file's MIME type and name (if available) when the File object is received.

-

banChatMember

-

Use this method to ban a user in a group, a supergroup or a channel. In the case of supergroups and channels, the user will not be able to return to the chat on their own using invite links, etc., unless unbanned first. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target group or username of the target supergroup or channel (in the format @channelusername)
user_idIntegerYesUnique identifier of the target user
until_dateIntegerOptionalDate when the user will be unbanned, unix time. If user is banned for more than 366 days or less than 30 seconds from the current time they are considered to be banned forever. Applied for supergroups and channels only.
revoke_messagesBooleanOptionalPass True to delete all messages from the chat for the user that is being removed. If False, the user will be able to see messages in the group that were sent before the user was removed. Always True for supergroups and channels.
-

unbanChatMember

-

Use this method to unban a previously banned user in a supergroup or channel. The user will not return to the group or channel automatically, but will be able to join via link, etc. The bot must be an administrator for this to work. By default, this method guarantees that after the call the user is not a member of the chat, but will be able to join it. So if the user is a member of the chat they will also be removed from the chat. If you don't want this, use the parameter only_if_banned. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target group or username of the target supergroup or channel (in the format @channelusername)
user_idIntegerYesUnique identifier of the target user
only_if_bannedBooleanOptionalDo nothing if the user is not banned
-

restrictChatMember

-

Use this method to restrict a user in a supergroup. The bot must be an administrator in the supergroup for this to work and must have the appropriate administrator rights. Pass True for all permissions to lift restrictions from a user. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
user_idIntegerYesUnique identifier of the target user
permissionsChatPermissionsYesA JSON-serialized object for new user permissions
until_dateIntegerOptionalDate when restrictions will be lifted for the user, unix time. If user is restricted for more than 366 days or less than 30 seconds from the current time, they are considered to be restricted forever
-

promoteChatMember

-

Use this method to promote or demote a user in a supergroup or a channel. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Pass False for all boolean parameters to demote a user. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
user_idIntegerYesUnique identifier of the target user
is_anonymousBooleanOptionalPass True, if the administrator's presence in the chat is hidden
can_manage_chatBooleanOptionalPass True, if the administrator can access the chat event log, chat statistics, message statistics in channels, see channel members, see anonymous administrators in supergroups and ignore slow mode. Implied by any other administrator privilege
can_post_messagesBooleanOptionalPass True, if the administrator can create channel posts, channels only
can_edit_messagesBooleanOptionalPass True, if the administrator can edit messages of other users and can pin messages, channels only
can_delete_messagesBooleanOptionalPass True, if the administrator can delete messages of other users
can_manage_voice_chatsBooleanOptionalPass True, if the administrator can manage voice chats
can_restrict_membersBooleanOptionalPass True, if the administrator can restrict, ban or unban chat members
can_promote_membersBooleanOptionalPass True, if the administrator can add new administrators with a subset of their own privileges or demote administrators that he has promoted, directly or indirectly (promoted by administrators that were appointed by him)
can_change_infoBooleanOptionalPass True, if the administrator can change chat title, photo and other settings
can_invite_usersBooleanOptionalPass True, if the administrator can invite new users to the chat
can_pin_messagesBooleanOptionalPass True, if the administrator can pin messages, supergroups only
-

setChatAdministratorCustomTitle

-

Use this method to set a custom title for an administrator in a supergroup promoted by the bot. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
user_idIntegerYesUnique identifier of the target user
custom_titleStringYesNew custom title for the administrator; 0-16 characters, emoji are not allowed
-

banChatSenderChat

-

Use this method to ban a channel chat in a supergroup or a channel. Until the chat is unbanned, the owner of the banned chat won't be able to send messages on behalf of any of their channels. The bot must be an administrator in the supergroup or channel for this to work and must have the appropriate administrator rights. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
sender_chat_idIntegerYesUnique identifier of the target sender chat
-

unbanChatSenderChat

-

Use this method to unban a previously banned channel chat in a supergroup or channel. The bot must be an administrator for this to work and must have the appropriate administrator rights. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
sender_chat_idIntegerYesUnique identifier of the target sender chat
-

setChatPermissions

-

Use this method to set default chat permissions for all members. The bot must be an administrator in the group or a supergroup for this to work and must have the can_restrict_members administrator rights. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
permissionsChatPermissionsYesA JSON-serialized object for new default chat permissions
-

exportChatInviteLink

-

Use this method to generate a new primary invite link for a chat; any previously generated primary link is revoked. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns the new invite link as String on success.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
-
-

Note: Each administrator in a chat generates their own invite links. Bots can't use invite links generated by other administrators. If you want your bot to work with invite links, it will need to generate its own link using exportChatInviteLink or by calling the getChat method. If your bot needs to generate a new primary invite link replacing its previous one, use exportChatInviteLink again.

-
-

createChatInviteLink

-

Use this method to create an additional invite link for a chat. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. The link can be revoked using the method revokeChatInviteLink. Returns the new invite link as ChatInviteLink object.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
nameStringOptionalInvite link name; 0-32 characters
expire_dateIntegerOptionalPoint in time (Unix timestamp) when the link will expire
member_limitIntegerOptionalMaximum number of users that can be members of the chat simultaneously after joining the chat via this invite link; 1-99999
creates_join_requestBooleanOptionalTrue, if users joining the chat via the link need to be approved by chat administrators. If True, member_limit can't be specified
-

editChatInviteLink

-

Use this method to edit a non-primary invite link created by the bot. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns the edited invite link as a ChatInviteLink object.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
invite_linkStringYesThe invite link to edit
nameStringOptionalInvite link name; 0-32 characters
expire_dateIntegerOptionalPoint in time (Unix timestamp) when the link will expire
member_limitIntegerOptionalMaximum number of users that can be members of the chat simultaneously after joining the chat via this invite link; 1-99999
creates_join_requestBooleanOptionalTrue, if users joining the chat via the link need to be approved by chat administrators. If True, member_limit can't be specified
-

revokeChatInviteLink

-

Use this method to revoke an invite link created by the bot. If the primary link is revoked, a new link is automatically generated. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns the revoked invite link as ChatInviteLink object.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier of the target chat or username of the target channel (in the format @channelusername)
invite_linkStringYesThe invite link to revoke
-

approveChatJoinRequest

-

Use this method to approve a chat join request. The bot must be an administrator in the chat for this to work and must have the can_invite_users administrator right. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
user_idIntegerYesUnique identifier of the target user
-

declineChatJoinRequest

-

Use this method to decline a chat join request. The bot must be an administrator in the chat for this to work and must have the can_invite_users administrator right. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
user_idIntegerYesUnique identifier of the target user
-

setChatPhoto

-

Use this method to set a new profile photo for the chat. Photos can't be changed for private chats. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
photoInputFileYesNew chat photo, uploaded using multipart/form-data
-

deleteChatPhoto

-

Use this method to delete a chat photo. Photos can't be changed for private chats. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns True on success.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
-

setChatTitle

-

Use this method to change the title of a chat. Titles can't be changed for private chats. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
titleStringYesNew chat title, 1-255 characters
-

setChatDescription

-

Use this method to change the description of a group, a supergroup or a channel. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
descriptionStringOptionalNew chat description, 0-255 characters
-

pinChatMessage

-

Use this method to add a message to the list of pinned messages in a chat. If the chat is not a private chat, the bot must be an administrator in the chat for this to work and must have the 'can_pin_messages' administrator right in a supergroup or 'can_edit_messages' administrator right in a channel. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerYesIdentifier of a message to pin
disable_notificationBooleanOptionalPass True, if it is not necessary to send a notification to all chat members about the new pinned message. Notifications are always disabled in channels and private chats.
-

unpinChatMessage

-

Use this method to remove a message from the list of pinned messages in a chat. If the chat is not a private chat, the bot must be an administrator in the chat for this to work and must have the 'can_pin_messages' administrator right in a supergroup or 'can_edit_messages' administrator right in a channel. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalIdentifier of a message to unpin. If not specified, the most recent pinned message (by sending date) will be unpinned.
-

unpinAllChatMessages

-

Use this method to clear the list of pinned messages in a chat. If the chat is not a private chat, the bot must be an administrator in the chat for this to work and must have the 'can_pin_messages' administrator right in a supergroup or 'can_edit_messages' administrator right in a channel. Returns True on success.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
-

leaveChat

-

Use this method for your bot to leave a group, supergroup or channel. Returns True on success.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
-

getChat

-

Use this method to get up to date information about the chat (current name of the user for one-on-one conversations, current username of a user, group or channel, etc.). Returns a Chat object on success.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
-

getChatAdministrators

-

Use this method to get a list of administrators in a chat. On success, returns an Array of ChatMember objects that contains information about all chat administrators except other bots. If the chat is a group or a supergroup and no administrators were appointed, only the creator will be returned.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
-

getChatMemberCount

-

Use this method to get the number of members in a chat. Returns Int on success.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
-

getChatMember

-

Use this method to get information about a member of a chat. Returns a ChatMember object on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
user_idIntegerYesUnique identifier of the target user
-

setChatStickerSet

-

Use this method to set a new group sticker set for a supergroup. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Use the field can_set_sticker_set optionally returned in getChat requests to check if the bot can use this method. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
sticker_set_nameStringYesName of the sticker set to be set as the group sticker set
-

deleteChatStickerSet

-

Use this method to delete a group sticker set from a supergroup. The bot must be an administrator in the chat for this to work and must have the appropriate administrator rights. Use the field can_set_sticker_set optionally returned in getChat requests to check if the bot can use this method. Returns True on success.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
-

answerCallbackQuery

-

Use this method to send answers to callback queries sent from inline keyboards. The answer will be displayed to the user as a notification at the top of the chat screen or as an alert. On success, True is returned.

-
-

Alternatively, the user can be redirected to the specified Game URL. For this option to work, you must first create a game for your bot via @Botfather and accept the terms. Otherwise, you may use links like t.me/your_bot?start=XXXX that open your bot with a parameter.

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
callback_query_idStringYesUnique identifier for the query to be answered
textStringOptionalText of the notification. If not specified, nothing will be shown to the user, 0-200 characters
show_alertBooleanOptionalIf True, an alert will be shown by the client instead of a notification at the top of the chat screen. Defaults to false.
urlStringOptionalURL that will be opened by the user's client. If you have created a Game and accepted the conditions via @Botfather, specify the URL that opens your game — note that this will only work if the query comes from a callback_game button.

Otherwise, you may use links like t.me/your_bot?start=XXXX that open your bot with a parameter.
cache_timeIntegerOptionalThe maximum amount of time in seconds that the result of the callback query may be cached client-side. Telegram apps will support caching starting in version 3.14. Defaults to 0.
-

setMyCommands

-

Use this method to change the list of the bot's commands. See https://core.telegram.org/bots#commands for more details about bot commands. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
commandsArray of BotCommandYesA JSON-serialized list of bot commands to be set as the list of the bot's commands. At most 100 commands can be specified.
scopeBotCommandScopeOptionalA JSON-serialized object, describing scope of users for which the commands are relevant. Defaults to BotCommandScopeDefault.
language_codeStringOptionalA two-letter ISO 639-1 language code. If empty, commands will be applied to all users from the given scope, for whose language there are no dedicated commands
-

deleteMyCommands

-

Use this method to delete the list of the bot's commands for the given scope and user language. After deletion, higher level commands will be shown to affected users. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
scopeBotCommandScopeOptionalA JSON-serialized object, describing scope of users for which the commands are relevant. Defaults to BotCommandScopeDefault.
language_codeStringOptionalA two-letter ISO 639-1 language code. If empty, commands will be applied to all users from the given scope, for whose language there are no dedicated commands
-

getMyCommands

-

Use this method to get the current list of the bot's commands for the given scope and user language. Returns Array of BotCommand on success. If commands aren't set, an empty list is returned.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
scopeBotCommandScopeOptionalA JSON-serialized object, describing scope of users. Defaults to BotCommandScopeDefault.
language_codeStringOptionalA two-letter ISO 639-1 language code or an empty string
-

Inline mode methods

-

Methods and objects used in the inline mode are described in the Inline mode section.

-

Updating messages

-

The following methods allow you to change an existing message in the message history instead of sending a new one with a result of an action. This is most useful for messages with inline keyboards using callback queries, but can also help reduce clutter in conversations with regular chat bots.

-

Please note, that it is currently only possible to edit messages without reply_markup or with inline keyboards.

-

editMessageText

-

Use this method to edit text and game messages. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
textStringYesNew text of the message, 1-4096 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the message text. See formatting options for more details.
entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in message text, which can be specified instead of parse_mode
disable_web_page_previewBooleanOptionalDisables link previews for links in this message
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard.
-

editMessageCaption

-

Use this method to edit captions of messages. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
captionStringOptionalNew caption of the message, 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the message caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard.
-

editMessageMedia

-

Use this method to edit animation, audio, document, photo, or video messages. If a message is part of a message album, then it can be edited only to an audio for audio albums, only to a document for document albums and to a photo or a video otherwise. When an inline message is edited, a new file can't be uploaded; use a previously uploaded file via its file_id or specify a URL. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
mediaInputMediaYesA JSON-serialized object for a new media content of the message
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for a new inline keyboard.
-

editMessageReplyMarkup

-

Use this method to edit only the reply markup of messages. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard.
-

stopPoll

-

Use this method to stop a poll which was sent by the bot. On success, the stopped Poll is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerYesIdentifier of the original message with the poll
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for a new message inline keyboard.
-

deleteMessage

-

Use this method to delete a message, including service messages, with the following limitations:
- A message can only be deleted if it was sent less than 48 hours ago.
- A dice message in a private chat can only be deleted if it was sent more than 24 hours ago.
- Bots can delete outgoing messages in private chats, groups, and supergroups.
- Bots can delete incoming messages in private chats.
- Bots granted can_post_messages permissions can delete outgoing messages in channels.
- If the bot is an administrator of a group, it can delete any message there.
- If the bot has can_delete_messages permission in a supergroup or a channel, it can delete any message there.
Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerYesIdentifier of the message to delete
-

Stickers

-

The following methods and objects allow your bot to handle stickers and sticker sets.

-

Sticker

-

This object represents a sticker.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
widthIntegerSticker width
heightIntegerSticker height
is_animatedBooleanTrue, if the sticker is animated
is_videoBooleanTrue, if the sticker is a video sticker
thumbPhotoSizeOptional. Sticker thumbnail in the .WEBP or .JPG format
emojiStringOptional. Emoji associated with the sticker
set_nameStringOptional. Name of the sticker set to which the sticker belongs
mask_positionMaskPositionOptional. For mask stickers, the position where the mask should be placed
file_sizeIntegerOptional. File size in bytes
-

StickerSet

-

This object represents a sticker set.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
nameStringSticker set name
titleStringSticker set title
is_animatedBooleanTrue, if the sticker set contains animated stickers
is_videoBooleanTrue, if the sticker set contains video stickers
contains_masksBooleanTrue, if the sticker set contains masks
stickersArray of StickerList of all set stickers
thumbPhotoSizeOptional. Sticker set thumbnail in the .WEBP, .TGS, or .WEBM format
-

MaskPosition

-

This object describes the position on faces where a mask should be placed by default.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
pointStringThe part of the face relative to which the mask should be placed. One of “forehead”, “eyes”, “mouth”, or “chin”.
x_shiftFloat numberShift by X-axis measured in widths of the mask scaled to the face size, from left to right. For example, choosing -1.0 will place mask just to the left of the default mask position.
y_shiftFloat numberShift by Y-axis measured in heights of the mask scaled to the face size, from top to bottom. For example, 1.0 will place the mask just below the default mask position.
scaleFloat numberMask scaling coefficient. For example, 2.0 means double size.
-

sendSticker

-

Use this method to send static .WEBP, animated .TGS, or video .WEBM stickers. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
stickerInputFile or StringYesSticker to send. Pass a file_id as String to send a file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a .WEBP file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

getStickerSet

-

Use this method to get a sticker set. On success, a StickerSet object is returned.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
nameStringYesName of the sticker set
-

uploadStickerFile

-

Use this method to upload a .PNG file with a sticker for later use in createNewStickerSet and addStickerToSet methods (can be used multiple times). Returns the uploaded File on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
user_idIntegerYesUser identifier of sticker file owner
png_stickerInputFileYesPNG image with the sticker, must be up to 512 kilobytes in size, dimensions must not exceed 512px, and either width or height must be exactly 512px. More info on Sending Files »
-

createNewStickerSet

-

Use this method to create a new sticker set owned by a user. The bot will be able to edit the sticker set thus created. You must use exactly one of the fields png_sticker, tgs_sticker, or webm_sticker. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
user_idIntegerYesUser identifier of created sticker set owner
nameStringYesShort name of sticker set, to be used in t.me/addstickers/ URLs (e.g., animals). Can contain only english letters, digits and underscores. Must begin with a letter, can't contain consecutive underscores and must end in “_by_<bot username>”. <bot_username> is case insensitive. 1-64 characters.
titleStringYesSticker set title, 1-64 characters
png_stickerInputFile or StringOptionalPNG image with the sticker, must be up to 512 kilobytes in size, dimensions must not exceed 512px, and either width or height must be exactly 512px. Pass a file_id as a String to send a file that already exists on the Telegram servers, pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
tgs_stickerInputFileOptionalTGS animation with the sticker, uploaded using multipart/form-data. See https://core.telegram.org/stickers#animated-sticker-requirements for technical requirements
webm_stickerInputFileOptionalWEBM video with the sticker, uploaded using multipart/form-data. See https://core.telegram.org/stickers#video-sticker-requirements for technical requirements
emojisStringYesOne or more emoji corresponding to the sticker
contains_masksBooleanOptionalPass True, if a set of mask stickers should be created
mask_positionMaskPositionOptionalA JSON-serialized object for position where the mask should be placed on faces
-

addStickerToSet

-

Use this method to add a new sticker to a set created by the bot. You must use exactly one of the fields png_sticker, tgs_sticker, or webm_sticker. Animated stickers can be added to animated sticker sets and only to them. Animated sticker sets can have up to 50 stickers. Static sticker sets can have up to 120 stickers. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
user_idIntegerYesUser identifier of sticker set owner
nameStringYesSticker set name
png_stickerInputFile or StringOptionalPNG image with the sticker, must be up to 512 kilobytes in size, dimensions must not exceed 512px, and either width or height must be exactly 512px. Pass a file_id as a String to send a file that already exists on the Telegram servers, pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
tgs_stickerInputFileOptionalTGS animation with the sticker, uploaded using multipart/form-data. See https://core.telegram.org/stickers#animated-sticker-requirements for technical requirements
webm_stickerInputFileOptionalWEBM video with the sticker, uploaded using multipart/form-data. See https://core.telegram.org/stickers#video-sticker-requirements for technical requirements
emojisStringYesOne or more emoji corresponding to the sticker
mask_positionMaskPositionOptionalA JSON-serialized object for position where the mask should be placed on faces
-

setStickerPositionInSet

-

Use this method to move a sticker in a set created by the bot to a specific position. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
stickerStringYesFile identifier of the sticker
positionIntegerYesNew sticker position in the set, zero-based
-

deleteStickerFromSet

-

Use this method to delete a sticker from a set created by the bot. Returns True on success.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
stickerStringYesFile identifier of the sticker
-

setStickerSetThumb

-

Use this method to set the thumbnail of a sticker set. Animated thumbnails can be set for animated sticker sets only. Video thumbnails can be set only for video sticker sets only. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
nameStringYesSticker set name
user_idIntegerYesUser identifier of the sticker set owner
thumbInputFile or StringOptionalA PNG image with the thumbnail, must be up to 128 kilobytes in size and have width and height exactly 100px, or a TGS animation with the thumbnail up to 32 kilobytes in size; see https://core.telegram.org/stickers#animated-sticker-requirements for animated sticker technical requirements, or a WEBM video with the thumbnail up to 32 kilobytes in size; see https://core.telegram.org/stickers#video-sticker-requirements for video sticker technical requirements. Pass a file_id as a String to send a file that already exists on the Telegram servers, pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files ». Animated sticker set thumbnails can't be uploaded via HTTP URL.
-

Inline mode

-

The following methods and objects allow your bot to work in inline mode.
Please see our Introduction to Inline bots for more details.

-

To enable this option, send the /setinline command to @BotFather and provide the placeholder text that the user will see in the input field after typing your bot's name.

-

InlineQuery

-

This object represents an incoming inline query. When the user sends an empty query, your bot could return some default or trending results.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
idStringUnique identifier for this query
fromUserSender
queryStringText of the query (up to 256 characters)
offsetStringOffset of the results to be returned, can be controlled by the bot
chat_typeStringOptional. Type of the chat, from which the inline query was sent. Can be either “sender” for a private chat with the inline query sender, “private”, “group”, “supergroup”, or “channel”. The chat type should be always known for requests sent from official clients and most third-party clients, unless the request was sent from a secret chat
locationLocationOptional. Sender location, only for bots that request user location
-

answerInlineQuery

-

Use this method to send answers to an inline query. On success, True is returned.
No more than 50 results per query are allowed.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
inline_query_idStringYesUnique identifier for the answered query
resultsArray of InlineQueryResultYesA JSON-serialized array of results for the inline query
cache_timeIntegerOptionalThe maximum amount of time in seconds that the result of the inline query may be cached on the server. Defaults to 300.
is_personalBooleanOptionalPass True, if results may be cached on the server side only for the user that sent the query. By default, results may be returned to any user who sends the same query
next_offsetStringOptionalPass the offset that a client should send in the next query with the same text to receive more results. Pass an empty string if there are no more results or if you don't support pagination. Offset length can't exceed 64 bytes.
switch_pm_textStringOptionalIf passed, clients will display a button with specified text that switches the user to a private chat with the bot and sends the bot a start message with the parameter switch_pm_parameter
switch_pm_parameterStringOptionalDeep-linking parameter for the /start message sent to the bot when user presses the switch button. 1-64 characters, only A-Z, a-z, 0-9, _ and - are allowed.

Example: An inline bot that sends YouTube videos can ask the user to connect the bot to their YouTube account to adapt search results accordingly. To do this, it displays a 'Connect your YouTube account' button above the results, or even before showing any. The user presses the button, switches to a private chat with the bot and, in doing so, passes a start parameter that instructs the bot to return an OAuth link. Once done, the bot can offer a switch_inline button so that the user can easily return to the chat where they wanted to use the bot's inline capabilities.
-

InlineQueryResult

-

This object represents one result of an inline query. Telegram clients currently support results of the following 20 types:

- -

Note: All URLs passed in inline query results will be available to end users and therefore must be assumed to be public.

-

InlineQueryResultArticle

-

Represents a link to an article or web page.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be article
idStringUnique identifier for this result, 1-64 Bytes
titleStringTitle of the result
input_message_contentInputMessageContentContent of the message to be sent
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
urlStringOptional. URL of the result
hide_urlBooleanOptional. Pass True, if you don't want the URL to be shown in the message
descriptionStringOptional. Short description of the result
thumb_urlStringOptional. Url of the thumbnail for the result
thumb_widthIntegerOptional. Thumbnail width
thumb_heightIntegerOptional. Thumbnail height
-

InlineQueryResultPhoto

-

Represents a link to a photo. By default, this photo will be sent by the user with optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the photo.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be photo
idStringUnique identifier for this result, 1-64 bytes
photo_urlStringA valid URL of the photo. Photo must be in JPEG format. Photo size must not exceed 5MB
thumb_urlStringURL of the thumbnail for the photo
photo_widthIntegerOptional. Width of the photo
photo_heightIntegerOptional. Height of the photo
titleStringOptional. Title for the result
descriptionStringOptional. Short description of the result
captionStringOptional. Caption of the photo to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the photo caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the photo
-

InlineQueryResultGif

-

Represents a link to an animated GIF file. By default, this animated GIF file will be sent by the user with optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the animation.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be gif
idStringUnique identifier for this result, 1-64 bytes
gif_urlStringA valid URL for the GIF file. File size must not exceed 1MB
gif_widthIntegerOptional. Width of the GIF
gif_heightIntegerOptional. Height of the GIF
gif_durationIntegerOptional. Duration of the GIF in seconds
thumb_urlStringURL of the static (JPEG or GIF) or animated (MPEG4) thumbnail for the result
thumb_mime_typeStringOptional. MIME type of the thumbnail, must be one of “image/jpeg”, “image/gif”, or “video/mp4”. Defaults to “image/jpeg”
titleStringOptional. Title for the result
captionStringOptional. Caption of the GIF file to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the GIF animation
-

InlineQueryResultMpeg4Gif

-

Represents a link to a video animation (H.264/MPEG-4 AVC video without sound). By default, this animated MPEG-4 file will be sent by the user with optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the animation.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be mpeg4_gif
idStringUnique identifier for this result, 1-64 bytes
mpeg4_urlStringA valid URL for the MP4 file. File size must not exceed 1MB
mpeg4_widthIntegerOptional. Video width
mpeg4_heightIntegerOptional. Video height
mpeg4_durationIntegerOptional. Video duration in seconds
thumb_urlStringURL of the static (JPEG or GIF) or animated (MPEG4) thumbnail for the result
thumb_mime_typeStringOptional. MIME type of the thumbnail, must be one of “image/jpeg”, “image/gif”, or “video/mp4”. Defaults to “image/jpeg”
titleStringOptional. Title for the result
captionStringOptional. Caption of the MPEG-4 file to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the video animation
-

InlineQueryResultVideo

-

Represents a link to a page containing an embedded video player or a video file. By default, this video file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the video.

-
-

If an InlineQueryResultVideo message contains an embedded video (e.g., YouTube), you must replace its content using input_message_content.

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be video
idStringUnique identifier for this result, 1-64 bytes
video_urlStringA valid URL for the embedded video player or video file
mime_typeStringMime type of the content of video url, “text/html” or “video/mp4”
thumb_urlStringURL of the thumbnail (JPEG only) for the video
titleStringTitle for the result
captionStringOptional. Caption of the video to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the video caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
video_widthIntegerOptional. Video width
video_heightIntegerOptional. Video height
video_durationIntegerOptional. Video duration in seconds
descriptionStringOptional. Short description of the result
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the video. This field is required if InlineQueryResultVideo is used to send an HTML-page as a result (e.g., a YouTube video).
-

InlineQueryResultAudio

-

Represents a link to an MP3 audio file. By default, this audio file will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the audio.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be audio
idStringUnique identifier for this result, 1-64 bytes
audio_urlStringA valid URL for the audio file
titleStringTitle
captionStringOptional. Caption, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the audio caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
performerStringOptional. Performer
audio_durationIntegerOptional. Audio duration in seconds
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the audio
-

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

-

InlineQueryResultVoice

-

Represents a link to a voice recording in an .OGG container encoded with OPUS. By default, this voice recording will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the the voice message.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be voice
idStringUnique identifier for this result, 1-64 bytes
voice_urlStringA valid URL for the voice recording
titleStringRecording title
captionStringOptional. Caption, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the voice message caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
voice_durationIntegerOptional. Recording duration in seconds
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the voice recording
-

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

-

InlineQueryResultDocument

-

Represents a link to a file. By default, this file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the file. Currently, only .PDF and .ZIP files can be sent using this method.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be document
idStringUnique identifier for this result, 1-64 bytes
titleStringTitle for the result
captionStringOptional. Caption of the document to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the document caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
document_urlStringA valid URL for the file
mime_typeStringMime type of the content of the file, either “application/pdf” or “application/zip”
descriptionStringOptional. Short description of the result
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the file
thumb_urlStringOptional. URL of the thumbnail (JPEG only) for the file
thumb_widthIntegerOptional. Thumbnail width
thumb_heightIntegerOptional. Thumbnail height
-

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

-

InlineQueryResultLocation

-

Represents a location on a map. By default, the location will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the location.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be location
idStringUnique identifier for this result, 1-64 Bytes
latitudeFloat numberLocation latitude in degrees
longitudeFloat numberLocation longitude in degrees
titleStringLocation title
horizontal_accuracyFloat numberOptional. The radius of uncertainty for the location, measured in meters; 0-1500
live_periodIntegerOptional. Period in seconds for which the location can be updated, should be between 60 and 86400.
headingIntegerOptional. For live locations, a direction in which the user is moving, in degrees. Must be between 1 and 360 if specified.
proximity_alert_radiusIntegerOptional. For live locations, a maximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the location
thumb_urlStringOptional. Url of the thumbnail for the result
thumb_widthIntegerOptional. Thumbnail width
thumb_heightIntegerOptional. Thumbnail height
-

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

-

InlineQueryResultVenue

-

Represents a venue. By default, the venue will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the venue.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be venue
idStringUnique identifier for this result, 1-64 Bytes
latitudeFloatLatitude of the venue location in degrees
longitudeFloatLongitude of the venue location in degrees
titleStringTitle of the venue
addressStringAddress of the venue
foursquare_idStringOptional. Foursquare identifier of the venue if known
foursquare_typeStringOptional. Foursquare type of the venue, if known. (For example, “arts_entertainment/default”, “arts_entertainment/aquarium” or “food/icecream”.)
google_place_idStringOptional. Google Places identifier of the venue
google_place_typeStringOptional. Google Places type of the venue. (See supported types.)
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the venue
thumb_urlStringOptional. Url of the thumbnail for the result
thumb_widthIntegerOptional. Thumbnail width
thumb_heightIntegerOptional. Thumbnail height
-

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

-

InlineQueryResultContact

-

Represents a contact with a phone number. By default, this contact will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the contact.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be contact
idStringUnique identifier for this result, 1-64 Bytes
phone_numberStringContact's phone number
first_nameStringContact's first name
last_nameStringOptional. Contact's last name
vcardStringOptional. Additional data about the contact in the form of a vCard, 0-2048 bytes
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the contact
thumb_urlStringOptional. Url of the thumbnail for the result
thumb_widthIntegerOptional. Thumbnail width
thumb_heightIntegerOptional. Thumbnail height
-

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

-

InlineQueryResultGame

-

Represents a Game.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be game
idStringUnique identifier for this result, 1-64 bytes
game_short_nameStringShort name of the game
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
-

Note: This will only work in Telegram versions released after October 1, 2016. Older clients will not display any inline results if a game result is among them.

-

InlineQueryResultCachedPhoto

-

Represents a link to a photo stored on the Telegram servers. By default, this photo will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the photo.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be photo
idStringUnique identifier for this result, 1-64 bytes
photo_file_idStringA valid file identifier of the photo
titleStringOptional. Title for the result
descriptionStringOptional. Short description of the result
captionStringOptional. Caption of the photo to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the photo caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the photo
-

InlineQueryResultCachedGif

-

Represents a link to an animated GIF file stored on the Telegram servers. By default, this animated GIF file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with specified content instead of the animation.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be gif
idStringUnique identifier for this result, 1-64 bytes
gif_file_idStringA valid file identifier for the GIF file
titleStringOptional. Title for the result
captionStringOptional. Caption of the GIF file to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the GIF animation
-

InlineQueryResultCachedMpeg4Gif

-

Represents a link to a video animation (H.264/MPEG-4 AVC video without sound) stored on the Telegram servers. By default, this animated MPEG-4 file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the animation.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be mpeg4_gif
idStringUnique identifier for this result, 1-64 bytes
mpeg4_file_idStringA valid file identifier for the MP4 file
titleStringOptional. Title for the result
captionStringOptional. Caption of the MPEG-4 file to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the video animation
-

InlineQueryResultCachedSticker

-

Represents a link to a sticker stored on the Telegram servers. By default, this sticker will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the sticker.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be sticker
idStringUnique identifier for this result, 1-64 bytes
sticker_file_idStringA valid file identifier of the sticker
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the sticker
-

Note: This will only work in Telegram versions released after 9 April, 2016 for static stickers and after 06 July, 2019 for animated stickers. Older clients will ignore them.

-

InlineQueryResultCachedDocument

-

Represents a link to a file stored on the Telegram servers. By default, this file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the file.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be document
idStringUnique identifier for this result, 1-64 bytes
titleStringTitle for the result
document_file_idStringA valid file identifier for the file
descriptionStringOptional. Short description of the result
captionStringOptional. Caption of the document to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the document caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the file
-

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

-

InlineQueryResultCachedVideo

-

Represents a link to a video file stored on the Telegram servers. By default, this video file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the video.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be video
idStringUnique identifier for this result, 1-64 bytes
video_file_idStringA valid file identifier for the video file
titleStringTitle for the result
descriptionStringOptional. Short description of the result
captionStringOptional. Caption of the video to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the video caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the video
-

InlineQueryResultCachedVoice

-

Represents a link to a voice message stored on the Telegram servers. By default, this voice message will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the voice message.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be voice
idStringUnique identifier for this result, 1-64 bytes
voice_file_idStringA valid file identifier for the voice message
titleStringVoice message title
captionStringOptional. Caption, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the voice message caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the voice message
-

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

-

InlineQueryResultCachedAudio

-

Represents a link to an MP3 audio file stored on the Telegram servers. By default, this audio file will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the audio.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be audio
idStringUnique identifier for this result, 1-64 bytes
audio_file_idStringA valid file identifier for the audio file
captionStringOptional. Caption, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the audio caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the audio
-

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

-

InputMessageContent

-

This object represents the content of a message to be sent as a result of an inline query. Telegram clients currently support the following 5 types:

- -

InputTextMessageContent

-

Represents the content of a text message to be sent as the result of an inline query.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
message_textStringText of the message to be sent, 1-4096 characters
parse_modeStringOptional. Mode for parsing entities in the message text. See formatting options for more details.
entitiesArray of MessageEntityOptional. List of special entities that appear in message text, which can be specified instead of parse_mode
disable_web_page_previewBooleanOptional. Disables link previews for links in the sent message
-

InputLocationMessageContent

-

Represents the content of a location message to be sent as the result of an inline query.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
latitudeFloatLatitude of the location in degrees
longitudeFloatLongitude of the location in degrees
horizontal_accuracyFloat numberOptional. The radius of uncertainty for the location, measured in meters; 0-1500
live_periodIntegerOptional. Period in seconds for which the location can be updated, should be between 60 and 86400.
headingIntegerOptional. For live locations, a direction in which the user is moving, in degrees. Must be between 1 and 360 if specified.
proximity_alert_radiusIntegerOptional. For live locations, a maximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.
-

InputVenueMessageContent

-

Represents the content of a venue message to be sent as the result of an inline query.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
latitudeFloatLatitude of the venue in degrees
longitudeFloatLongitude of the venue in degrees
titleStringName of the venue
addressStringAddress of the venue
foursquare_idStringOptional. Foursquare identifier of the venue, if known
foursquare_typeStringOptional. Foursquare type of the venue, if known. (For example, “arts_entertainment/default”, “arts_entertainment/aquarium” or “food/icecream”.)
google_place_idStringOptional. Google Places identifier of the venue
google_place_typeStringOptional. Google Places type of the venue. (See supported types.)
-

InputContactMessageContent

-

Represents the content of a contact message to be sent as the result of an inline query.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
phone_numberStringContact's phone number
first_nameStringContact's first name
last_nameStringOptional. Contact's last name
vcardStringOptional. Additional data about the contact in the form of a vCard, 0-2048 bytes
-

InputInvoiceMessageContent

-

Represents the content of an invoice message to be sent as the result of an inline query.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
titleStringProduct name, 1-32 characters
descriptionStringProduct description, 1-255 characters
payloadStringBot-defined invoice payload, 1-128 bytes. This will not be displayed to the user, use for your internal processes.
provider_tokenStringPayment provider token, obtained via Botfather
currencyStringThree-letter ISO 4217 currency code, see more on currencies
pricesArray of LabeledPricePrice breakdown, a JSON-serialized list of components (e.g. product price, tax, discount, delivery cost, delivery tax, bonus, etc.)
max_tip_amountIntegerOptional. The maximum accepted amount for tips in the smallest units of the currency (integer, not float/double). For example, for a maximum tip of US$ 1.45 pass max_tip_amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies). Defaults to 0
suggested_tip_amountsArray of IntegerOptional. A JSON-serialized array of suggested amounts of tip in the smallest units of the currency (integer, not float/double). At most 4 suggested tip amounts can be specified. The suggested tip amounts must be positive, passed in a strictly increased order and must not exceed max_tip_amount.
provider_dataStringOptional. A JSON-serialized object for data about the invoice, which will be shared with the payment provider. A detailed description of the required fields should be provided by the payment provider.
photo_urlStringOptional. URL of the product photo for the invoice. Can be a photo of the goods or a marketing image for a service. People like it better when they see what they are paying for.
photo_sizeIntegerOptional. Photo size
photo_widthIntegerOptional. Photo width
photo_heightIntegerOptional. Photo height
need_nameBooleanOptional. Pass True, if you require the user's full name to complete the order
need_phone_numberBooleanOptional. Pass True, if you require the user's phone number to complete the order
need_emailBooleanOptional. Pass True, if you require the user's email address to complete the order
need_shipping_addressBooleanOptional. Pass True, if you require the user's shipping address to complete the order
send_phone_number_to_providerBooleanOptional. Pass True, if user's phone number should be sent to provider
send_email_to_providerBooleanOptional. Pass True, if user's email address should be sent to provider
is_flexibleBooleanOptional. Pass True, if the final price depends on the shipping method
-

ChosenInlineResult

-

Represents a result of an inline query that was chosen by the user and sent to their chat partner.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
result_idStringThe unique identifier for the result that was chosen
fromUserThe user that chose the result
locationLocationOptional. Sender location, only for bots that require user location
inline_message_idStringOptional. Identifier of the sent inline message. Available only if there is an inline keyboard attached to the message. Will be also received in callback queries and can be used to edit the message.
queryStringThe query that was used to obtain the result
-

Note: It is necessary to enable inline feedback via @Botfather in order to receive these objects in updates.

-

Payments

-

Your bot can accept payments from Telegram users. Please see the introduction to payments for more details on the process and how to set up payments for your bot. Please note that users will need Telegram v.4.0 or higher to use payments (released on May 18, 2017).

-

sendInvoice

-

Use this method to send invoices. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
titleStringYesProduct name, 1-32 characters
descriptionStringYesProduct description, 1-255 characters
payloadStringYesBot-defined invoice payload, 1-128 bytes. This will not be displayed to the user, use for your internal processes.
provider_tokenStringYesPayments provider token, obtained via Botfather
currencyStringYesThree-letter ISO 4217 currency code, see more on currencies
pricesArray of LabeledPriceYesPrice breakdown, a JSON-serialized list of components (e.g. product price, tax, discount, delivery cost, delivery tax, bonus, etc.)
max_tip_amountIntegerOptionalThe maximum accepted amount for tips in the smallest units of the currency (integer, not float/double). For example, for a maximum tip of US$ 1.45 pass max_tip_amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies). Defaults to 0
suggested_tip_amountsArray of IntegerOptionalA JSON-serialized array of suggested amounts of tips in the smallest units of the currency (integer, not float/double). At most 4 suggested tip amounts can be specified. The suggested tip amounts must be positive, passed in a strictly increased order and must not exceed max_tip_amount.
start_parameterStringOptionalUnique deep-linking parameter. If left empty, forwarded copies of the sent message will have a Pay button, allowing multiple users to pay directly from the forwarded message, using the same invoice. If non-empty, forwarded copies of the sent message will have a URL button with a deep link to the bot (instead of a Pay button), with the value used as the start parameter
provider_dataStringOptionalA JSON-serialized data about the invoice, which will be shared with the payment provider. A detailed description of required fields should be provided by the payment provider.
photo_urlStringOptionalURL of the product photo for the invoice. Can be a photo of the goods or a marketing image for a service. People like it better when they see what they are paying for.
photo_sizeIntegerOptionalPhoto size
photo_widthIntegerOptionalPhoto width
photo_heightIntegerOptionalPhoto height
need_nameBooleanOptionalPass True, if you require the user's full name to complete the order
need_phone_numberBooleanOptionalPass True, if you require the user's phone number to complete the order
need_emailBooleanOptionalPass True, if you require the user's email address to complete the order
need_shipping_addressBooleanOptionalPass True, if you require the user's shipping address to complete the order
send_phone_number_to_providerBooleanOptionalPass True, if user's phone number should be sent to provider
send_email_to_providerBooleanOptionalPass True, if user's email address should be sent to provider
is_flexibleBooleanOptionalPass True, if the final price depends on the shipping method
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard. If empty, one 'Pay total price' button will be shown. If not empty, the first button must be a Pay button.
-

answerShippingQuery

-

If you sent an invoice requesting a shipping address and the parameter is_flexible was specified, the Bot API will send an Update with a shipping_query field to the bot. Use this method to reply to shipping queries. On success, True is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
shipping_query_idStringYesUnique identifier for the query to be answered
okBooleanYesSpecify True if delivery to the specified address is possible and False if there are any problems (for example, if delivery to the specified address is not possible)
shipping_optionsArray of ShippingOptionOptionalRequired if ok is True. A JSON-serialized array of available shipping options.
error_messageStringOptionalRequired if ok is False. Error message in human readable form that explains why it is impossible to complete the order (e.g. "Sorry, delivery to your desired address is unavailable'). Telegram will display this message to the user.
-

answerPreCheckoutQuery

-

Once the user has confirmed their payment and shipping details, the Bot API sends the final confirmation in the form of an Update with the field pre_checkout_query. Use this method to respond to such pre-checkout queries. On success, True is returned. Note: The Bot API must receive an answer within 10 seconds after the pre-checkout query was sent.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
pre_checkout_query_idStringYesUnique identifier for the query to be answered
okBooleanYesSpecify True if everything is alright (goods are available, etc.) and the bot is ready to proceed with the order. Use False if there are any problems.
error_messageStringOptionalRequired if ok is False. Error message in human readable form that explains the reason for failure to proceed with the checkout (e.g. "Sorry, somebody just bought the last of our amazing black T-shirts while you were busy filling out your payment details. Please choose a different color or garment!"). Telegram will display this message to the user.
-

LabeledPrice

-

This object represents a portion of the price for goods or services.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
labelStringPortion label
amountIntegerPrice of the product in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
-

Invoice

-

This object contains basic information about an invoice.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
titleStringProduct name
descriptionStringProduct description
start_parameterStringUnique bot deep-linking parameter that can be used to generate this invoice
currencyStringThree-letter ISO 4217 currency code
total_amountIntegerTotal price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
-

ShippingAddress

-

This object represents a shipping address.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
country_codeStringISO 3166-1 alpha-2 country code
stateStringState, if applicable
cityStringCity
street_line1StringFirst line for the address
street_line2StringSecond line for the address
post_codeStringAddress post code
-

OrderInfo

-

This object represents information about an order.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
nameStringOptional. User name
phone_numberStringOptional. User's phone number
emailStringOptional. User email
shipping_addressShippingAddressOptional. User shipping address
-

ShippingOption

-

This object represents one shipping option.

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
idStringShipping option identifier
titleStringOption title
pricesArray of LabeledPriceList of price portions
-

SuccessfulPayment

-

This object contains basic information about a successful payment.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
currencyStringThree-letter ISO 4217 currency code
total_amountIntegerTotal price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
invoice_payloadStringBot specified invoice payload
shipping_option_idStringOptional. Identifier of the shipping option chosen by the user
order_infoOrderInfoOptional. Order info provided by the user
telegram_payment_charge_idStringTelegram payment identifier
provider_payment_charge_idStringProvider payment identifier
-

ShippingQuery

-

This object contains information about an incoming shipping query.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
idStringUnique query identifier
fromUserUser who sent the query
invoice_payloadStringBot specified invoice payload
shipping_addressShippingAddressUser specified shipping address
-

PreCheckoutQuery

-

This object contains information about an incoming pre-checkout query.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
idStringUnique query identifier
fromUserUser who sent the query
currencyStringThree-letter ISO 4217 currency code
total_amountIntegerTotal price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
invoice_payloadStringBot specified invoice payload
shipping_option_idStringOptional. Identifier of the shipping option chosen by the user
order_infoOrderInfoOptional. Order info provided by the user
-

Telegram Passport

-

Telegram Passport is a unified authorization method for services that require personal identification. Users can upload their documents once, then instantly share their data with services that require real-world ID (finance, ICOs, etc.). Please see the manual for details.

-

PassportData

-

Contains information about Telegram Passport data shared with the bot by the user.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
dataArray of EncryptedPassportElementArray with information about documents and other Telegram Passport elements that was shared with the bot
credentialsEncryptedCredentialsEncrypted credentials required to decrypt the data
-

PassportFile

-

This object represents a file uploaded to Telegram Passport. Currently all Telegram Passport files are in JPEG format when decrypted and don't exceed 10MB.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
file_sizeIntegerFile size in bytes
file_dateIntegerUnix time when the file was uploaded
-

EncryptedPassportElement

-

Contains information about documents or other Telegram Passport elements shared with the bot by the user.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringElement type. One of “personal_details”, “passport”, “driver_license”, “identity_card”, “internal_passport”, “address”, “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”, “phone_number”, “email”.
dataStringOptional. Base64-encoded encrypted Telegram Passport element data provided by the user, available for “personal_details”, “passport”, “driver_license”, “identity_card”, “internal_passport” and “address” types. Can be decrypted and verified using the accompanying EncryptedCredentials.
phone_numberStringOptional. User's verified phone number, available only for “phone_number” type
emailStringOptional. User's verified email address, available only for “email” type
filesArray of PassportFileOptional. Array of encrypted files with documents provided by the user, available for “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration” and “temporary_registration” types. Files can be decrypted and verified using the accompanying EncryptedCredentials.
front_sidePassportFileOptional. Encrypted file with the front side of the document, provided by the user. Available for “passport”, “driver_license”, “identity_card” and “internal_passport”. The file can be decrypted and verified using the accompanying EncryptedCredentials.
reverse_sidePassportFileOptional. Encrypted file with the reverse side of the document, provided by the user. Available for “driver_license” and “identity_card”. The file can be decrypted and verified using the accompanying EncryptedCredentials.
selfiePassportFileOptional. Encrypted file with the selfie of the user holding a document, provided by the user; available for “passport”, “driver_license”, “identity_card” and “internal_passport”. The file can be decrypted and verified using the accompanying EncryptedCredentials.
translationArray of PassportFileOptional. Array of encrypted files with translated versions of documents provided by the user. Available if requested for “passport”, “driver_license”, “identity_card”, “internal_passport”, “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration” and “temporary_registration” types. Files can be decrypted and verified using the accompanying EncryptedCredentials.
hashStringBase64-encoded element hash for using in PassportElementErrorUnspecified
-

EncryptedCredentials

-

Contains data required for decrypting and authenticating EncryptedPassportElement. See the Telegram Passport Documentation for a complete description of the data decryption and authentication processes.

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
dataStringBase64-encoded encrypted JSON-serialized data with unique user's payload, data hashes and secrets required for EncryptedPassportElement decryption and authentication
hashStringBase64-encoded data hash for data authentication
secretStringBase64-encoded secret, encrypted with the bot's public RSA key, required for data decryption
-

setPassportDataErrors

-

Informs a user that some of the Telegram Passport elements they provided contains errors. The user will not be able to re-submit their Passport to you until the errors are fixed (the contents of the field for which you returned the error must change). Returns True on success.

-

Use this if the data submitted by the user doesn't satisfy the standards your service requires for any reason. For example, if a birthday date seems invalid, a submitted document is blurry, a scan shows evidence of tampering, etc. Supply some details in the error message to make sure the user knows how to correct the issues.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
user_idIntegerYesUser identifier
errorsArray of PassportElementErrorYesA JSON-serialized array describing the errors
-

PassportElementError

-

This object represents an error in the Telegram Passport element which was submitted that should be resolved by the user. It should be one of:

- -

PassportElementErrorDataField

-

Represents an issue in one of the data fields that was provided by the user. The error is considered resolved when the field's value changes.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
sourceStringError source, must be data
typeStringThe section of the user's Telegram Passport which has the error, one of “personal_details”, “passport”, “driver_license”, “identity_card”, “internal_passport”, “address”
field_nameStringName of the data field which has the error
data_hashStringBase64-encoded data hash
messageStringError message
-

PassportElementErrorFrontSide

-

Represents an issue with the front side of a document. The error is considered resolved when the file with the front side of the document changes.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
sourceStringError source, must be front_side
typeStringThe section of the user's Telegram Passport which has the issue, one of “passport”, “driver_license”, “identity_card”, “internal_passport”
file_hashStringBase64-encoded hash of the file with the front side of the document
messageStringError message
-

PassportElementErrorReverseSide

-

Represents an issue with the reverse side of a document. The error is considered resolved when the file with reverse side of the document changes.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
sourceStringError source, must be reverse_side
typeStringThe section of the user's Telegram Passport which has the issue, one of “driver_license”, “identity_card”
file_hashStringBase64-encoded hash of the file with the reverse side of the document
messageStringError message
-

PassportElementErrorSelfie

-

Represents an issue with the selfie with a document. The error is considered resolved when the file with the selfie changes.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
sourceStringError source, must be selfie
typeStringThe section of the user's Telegram Passport which has the issue, one of “passport”, “driver_license”, “identity_card”, “internal_passport”
file_hashStringBase64-encoded hash of the file with the selfie
messageStringError message
-

PassportElementErrorFile

-

Represents an issue with a document scan. The error is considered resolved when the file with the document scan changes.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
sourceStringError source, must be file
typeStringThe section of the user's Telegram Passport which has the issue, one of “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”
file_hashStringBase64-encoded file hash
messageStringError message
-

PassportElementErrorFiles

-

Represents an issue with a list of scans. The error is considered resolved when the list of files containing the scans changes.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
sourceStringError source, must be files
typeStringThe section of the user's Telegram Passport which has the issue, one of “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”
file_hashesArray of StringList of base64-encoded file hashes
messageStringError message
-

PassportElementErrorTranslationFile

-

Represents an issue with one of the files that constitute the translation of a document. The error is considered resolved when the file changes.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
sourceStringError source, must be translation_file
typeStringType of element of the user's Telegram Passport which has the issue, one of “passport”, “driver_license”, “identity_card”, “internal_passport”, “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”
file_hashStringBase64-encoded file hash
messageStringError message
-

PassportElementErrorTranslationFiles

-

Represents an issue with the translated version of a document. The error is considered resolved when a file with the document translation change.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
sourceStringError source, must be translation_files
typeStringType of element of the user's Telegram Passport which has the issue, one of “passport”, “driver_license”, “identity_card”, “internal_passport”, “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”
file_hashesArray of StringList of base64-encoded file hashes
messageStringError message
-

PassportElementErrorUnspecified

-

Represents an issue in an unspecified place. The error is considered resolved when new data is added.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
sourceStringError source, must be unspecified
typeStringType of element of the user's Telegram Passport which has the issue
element_hashStringBase64-encoded element hash
messageStringError message
-

Games

-

Your bot can offer users HTML5 games to play solo or to compete against each other in groups and one-on-one chats. Create games via @BotFather using the /newgame command. Please note that this kind of power requires responsibility: you will need to accept the terms for each game that your bots will be offering.

-
    -
  • Games are a new type of content on Telegram, represented by the Game and InlineQueryResultGame objects.
  • -
  • Once you've created a game via BotFather, you can send games to chats as regular messages using the sendGame method, or use inline mode with InlineQueryResultGame.
  • -
  • If you send the game message without any buttons, it will automatically have a 'Play GameName' button. When this button is pressed, your bot gets a CallbackQuery with the game_short_name of the requested game. You provide the correct URL for this particular user and the app opens the game in the in-app browser.
  • -
  • You can manually add multiple buttons to your game message. Please note that the first button in the first row must always launch the game, using the field callback_game in InlineKeyboardButton. You can add extra buttons according to taste: e.g., for a description of the rules, or to open the game's official community.
  • -
  • To make your game more attractive, you can upload a GIF animation that demostrates the game to the users via BotFather (see Lumberjack for example).
  • -
  • A game message will also display high scores for the current chat. Use setGameScore to post high scores to the chat with the game, add the edit_message parameter to automatically update the message with the current scoreboard.
  • -
  • Use getGameHighScores to get data for in-game high score tables.
  • -
  • You can also add an extra sharing button for users to share their best score to different chats.
  • -
  • For examples of what can be done using this new stuff, check the @gamebot and @gamee bots.
  • -
-

sendGame

-

Use this method to send a game. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idIntegerYesUnique identifier for the target chat
game_short_nameStringYesShort name of the game, serves as the unique identifier for the game. Set up your games via Botfather.
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
protect_contentBooleanOptionalProtects the contents of the sent message from forwarding and saving
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard. If empty, one 'Play game_title' button will be shown. If not empty, the first button must launch the game.
-

Game

-

This object represents a game. Use BotFather to create and edit games, their short names will act as unique identifiers.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
titleStringTitle of the game
descriptionStringDescription of the game
photoArray of PhotoSizePhoto that will be displayed in the game message in chats.
textStringOptional. Brief description of the game or high scores included in the game message. Can be automatically edited to include current high scores for the game when the bot calls setGameScore, or manually edited using editMessageText. 0-4096 characters.
text_entitiesArray of MessageEntityOptional. Special entities that appear in text, such as usernames, URLs, bot commands, etc.
animationAnimationOptional. Animation that will be displayed in the game message in chats. Upload via BotFather
-

CallbackGame

-

A placeholder, currently holds no information. Use BotFather to set up your game.

-

setGameScore

-

Use this method to set the score of the specified user in a game message. On success, if the message is not an inline message, the Message is returned, otherwise True is returned. Returns an error, if the new score is not greater than the user's current score in the chat and force is False.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
user_idIntegerYesUser identifier
scoreIntegerYesNew score, must be non-negative
forceBooleanOptionalPass True, if the high score is allowed to decrease. This can be useful when fixing mistakes or banning cheaters
disable_edit_messageBooleanOptionalPass True, if the game message should not be automatically edited to include the current scoreboard
chat_idIntegerOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the sent message
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
-

getGameHighScores

-

Use this method to get data for high score tables. Will return the score of the specified user and several of their neighbors in a game. On success, returns an Array of GameHighScore objects.

-
-

This method will currently return scores for the target user, plus two of their closest neighbors on each side. Will also return the top three users if the user and his neighbors are not among them. Please note that this behavior is subject to change.

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
user_idIntegerYesTarget user id
chat_idIntegerOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the sent message
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
-

GameHighScore

-

This object represents one row of the high scores table for a game.

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
positionIntegerPosition in high score table for the game
userUserUser
scoreIntegerScore
-
-

And that's about all we've got for now.
If you've got any questions, please check out our Bot FAQ »

-
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/bots/faq.html b/data/core.telegram.org/bots/faq.html deleted file mode 100644 index 223b0a9eea..0000000000 --- a/data/core.telegram.org/bots/faq.html +++ /dev/null @@ -1,243 +0,0 @@ - - - - - Bots FAQ - - - - - - - - - - - - - -
- -
-
-
- -

Bots FAQ

- -
-

If you are new to Telegram bots, we recommend checking out our Introduction to Bots first.
You may also find the Bot API Manual useful.

-
-

- -
-

General Questions

-

How do I create a bot?

-

Creating Telegram bots is super-easy, but you will need at least some skills at computer programming. In order for a bot to work, set up a bot account with @BotFather, then connect it to your backend server via our API.

-

Unfortunately, there are no out-of-the-box ways to create a working bot if you are not a developer. But we're sure you'll soon find plenty of bots created by other people to play with.

-

I'm a developer. Where can I find some examples?

-

Here are two sample bots, both written in PHP:

-
    -
  • Hello Bot demonstrates the basics of the Telegram bot API.
  • -
  • Simple Poll bot is a more complete example, it supports both long-polling and Webhooks for updates.
  • -
-
-

Many members of our community are building bots and publishing sources.
We're collecting them on this page »

-
-

Ping us on @BotSupport if you've built a bot and would like to share it with others.

-

Will you add X to the Bot API?

-

The bot API is still pretty young. There are many potential features to consider and implement. We'll be studying what people do with their bots for a while to see which directions will be most important for the platform.

-

All bot developers are welcome to share ideas for our Bot API with our @BotSupport account.

-

What messages will my bot get?

-

1. All bots, regardless of settings, will receive:

-
    -
  • All service messages.
  • -
  • All messages from private chats with users.
  • -
  • All messages from channels where they are a member.
  • -
-

2. Bot admins and bots with privacy mode disabled will receive all messages except messages sent by other bots.

-

3. Bots with privacy mode enabled will receive:

-
    -
  • Commands explicitly meant for them (e.g., /command@this_bot).
  • -
  • General commands from users (e.g. /start) if the bot was the last bot to send a message to the group.
  • -
  • Messages sent via this bot.
  • -
  • Replies to any messages implicitly or explicitly meant for this bot.
  • -
-

Note that each particular message can only be available to one privacy-enabled bot at a time, i.e., a reply to bot A containing an explicit command for bot B or sent via bot C will only be available to bot A. Replies have the highest priority.

-

Why doesn't my bot see messages from other bots?

-

Bots talking to each other could potentially get stuck in unwelcome loops. To avoid this, we decided that bots will not be able to see messages from other bots regardless of mode.

-

Getting Updates

-

How do I get updates?

-

There are currently two ways of getting updates. You can either use long polling or Webhooks. Please note that it's not possible to get updates via long polling while an outgoing Webhook is set.

-

Long polling gives me the same updates again and again!

-

The getUpdates method returns the earliest 100 unconfirmed updates. To confirm an update, use the offset parameter when calling getUpdates like this:

-
offset = update_id of last processed update + 1
-

All updates with update_id less than or equal to offset will be marked as confirmed on the server and will no longer be returned.

-

I'm having problems with Webhooks.

-

If you've set up your webhook successfully, but are not getting any updates, please remember:

-
    -
  • You need a valid SSL certificate for webhooks to work.
  • -
  • To use a self-signed certificate, you need to upload your public key certificate using the certificate parameter in setWebhook. Please upload as InputFile, sending a String will not work.
  • -
  • Ports currently supported for Webhooks: 443, 80, 88, 8443.
  • -
  • Wildcard certificates may not be supported.
  • -
  • Redirects are not supported.
  • -
  • CN must exactly match your domain.
  • -
-
-

Please check out this new WEBHOOK GUIDE to learn all there is to know about webhooks!

-
-

I'm having trouble with my self-signed certificate!

-

Please take a look at this self-signed certificate guide we made just for you. If you've read it and still have a question, ping us on botsupport.

-

How can I make sure that Webhook requests are coming from Telegram?

-

If you'd like to make sure that the Webhook request comes from Telegram, we recommend using a secret path in the URL you give us, e.g. www.example.com/your_token. Since nobody else knows your bot's token, you can be pretty sure it's us.

-

How can I make requests in response to updates?

-

This is possible if you're using webhooks. The upside is that you need less requests, the downside — that in this case it's not possible to know that such a request was successful or get its result.

-

Whenever you receive a webhook update, you have two options:

-

1. Issue POST to https://api.telegram.org/bot<token>/method

-
- -
- -

2. Reply directly and give method as JSON payload in the reply

-
-
- -
-

You may also want to look at our sample HelloBot, it offers a PHP implementation of this.

-
-

Handling Media

-

How do I download files?

-

Use the getFile method. Please note that this will only work with files of up to 20 MB in size.

-

How do I upload a large file?

-

Bots can currently send files of any type of up to 50 MB in size, so yes, very large files won't work for now. Sorry. This limit may be changed in the future.

-

Can I count on file_ids to be persistent?

-

Yes, file_ids can be treated as persistent.

-

Broadcasting to Users

-

My bot is hitting limits, how do I avoid this?

-

When sending messages inside a particular chat, avoid sending more than one message per second. We may allow short bursts that go over this limit, but eventually you'll begin receiving 429 errors.

-

If you're sending bulk notifications to multiple users, the API will not allow more than 30 messages per second or so. Consider spreading out notifications over large intervals of 8—12 hours for best results.

-

Also note that your bot will not be able to send more than 20 messages per minute to the same group.

-

How can I message all of my bot's subscribers at once?

-

Unfortunately, at this moment we don't have methods for sending bulk messages, e.g. notifications. We may add something along these lines in the future.

-

In order to avoid hitting our limits when sending out mass notifications, consider spreading them over longer intervals, e.g. 8-12 hours. The API will not allow bulk notifications to more than ~30 users per second, if you go over that, you'll start getting 429 errors.

-

See also: How to avoid hitting limits?

-
-
-

If you've got questions that are not answered on this page, ping us at @BotSupport in Telegram.
We welcome any suggestions for the Bot Platform and API.

-
-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/bots/games.html b/data/core.telegram.org/bots/games.html deleted file mode 100644 index 201d45f947..0000000000 --- a/data/core.telegram.org/bots/games.html +++ /dev/null @@ -1,185 +0,0 @@ - - - - - Gaming Platform - - - - - - - - - - - - - -
- -
-
-
- -

Gaming Platform

- -
- -
- -
- -

Bots can offer their users HTML5 games to play solo or to compete against each other in groups and one-on-one chats. Games are a new type of content on Telegram that your bot can send to users.

-
-

-
- -
-

This introduction is meant for bot developers. Click here, in case you'd like something more user-friendly.
Check out the @gamebot and @gamee bots for examples of what you can do using the new Gaming Platform.

-
-

Creating a Game

-

To get started, send the /newgame command to @BotFather.You will be prompted for a description text and a photo. You can also upload an optional GIF animation that demostrates your game to the users to make messages with the game more attractive (check out Lumberjack or Corsairs for examples).

-

Launching the Game

-

Once the game is created, your bot can send it to chats as regular messages, or offer them via inline mode. The game message will always have an inline Play button.

-

When this button is pressed, your bot gets a callback query that indicates the requested game. You provide the correct URL for this particular user and the app automatically opens the game in the in-app browser.

-

Adding Buttons

-

If you send the game message without any buttons, it will automatically have a 'Play GameName' button. You can manually add multiple buttons to your game message. Please note that the first button in the first row must always be the one that launches the game. You can add more buttons: e.g., for a description of the rules, or a button that links to the game's official community.

-

Tracking High Scores

-

The message with your game will also display high scores for the current chat. When a new high score is set, a service message will be sent to the chat and the message with the current scoreboard will be updated. You can also request the necessary data for building in-game high score tables.

-
-
- -

- -

- -

Sharing Your Game to Telegram Chats

-

There are many way for users to spread your game virally if they like it. The interface will always have the standard system button for sharing the game in the top right corner:

-
- - -

- -
- - - -

You can also create an additional Share button inside your HTML page. Pressing this button will send the game to a desired chat along with the user's best score in the game.

-
- - - - - -

- - -

To add the sharing button, include this script at the end of the <body> tag on your page:

-
<script src="https://telegram.org/js/games.js"></script>
-

Then use the method TelegramGameProxy.shareScore() to call the sharing option.

-
-

Warning: Do not call this method without consent and direct action from the user.

-
-

Example:

-
<button onclick="TelegramGameProxy.shareScore()">Share score</button>
-

This library will only work when launched from inside Telegram, so please don't use it on ordinary web pages.

-

Using URL Parameters

-

If your URL is using a fragment identifier, please note that Telegram Apps could add certain service parameters to the fragment id. The names for such parameters will start in tg (you can check the code that adds them here). Use the TelegramGameProxy.initParams object if you need to read your own parameters from the fragment id.

-

Creating a Great HTML5 Experience

-

Please make sure that your HTML5 page is responsive and works well on all Telegram apps and supported platforms. If you find it impossible to support certain conditions or platforms, don't leave your users hanging and at least provide a notification.

-
-

See the Bot API Manual for the relevant methods and objects.

-
-
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/bots/inline.html b/data/core.telegram.org/bots/inline.html deleted file mode 100644 index 3bf2192115..0000000000 --- a/data/core.telegram.org/bots/inline.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - Inline Bots - - - - - - - - - - - - - -
- -
-
-
- -

Inline Bots

- -
- -
- -
- -

Beyond sending commands in private messages or groups, users can interact with your bot via inline queries. If inline queries are enabled, users can call your bot by typing its username and a query in the text input field in any chat. The query is sent to your bot in an update. This way, people can request content from your bot in any of their chats, groups, or channels without sending any messages at all.

-
-
-
- - -

To enable this option, send the /setinline command to @BotFather and provide the placeholder text that the user will see in the input field after typing your bot’s name.

-
-

See the Bot API Manual for the relevant methods and objects.

-
-

Inline results

-

Inline bots support all types of content available in Telegram (20 in all). They are capable of sending stickers, videos, music, locations, documents and more.

-
-

-
- -

Clients can display the results with vertical or horizontal scrolling, depending on the type of content:

-
- - - - - -
-
- -

As soon as the user taps on an item, it's immediately sent to the recipient, and the input field is cleared.

-

Switching inline/PM modes

-

Some inline bots can benefit from an initial setup process, like connecting them to an account on an external service (e.g., YouTube). We've added an easy way of switching between the private chat with a bot and whatever chat the user wants to share inline results in.

-
-

-
- -

You can display a special ‘Switch to PM’ button above the inline results (or instead of them). This button will open a private chat with the bot and pass a parameter of your choosing, so that you can prompt the user for the relevant setup actions. Once done, you can use an inline keyboard with a switch_inline_query button to send the user back to the original chat.

-

Sample bots
@youtube – Shows a ‘Sign in to YouTube’ button, then suggests personalized results.

-
-

Manual: Switch to PM

-
-

Location-based results

-

Inline bots can request location data from their users. Use the /setinlinegeo command with @BotFather to enable this. Your bot will ask the user for permission to access their location whenever they send an inline request.

-

Sample bot
@foursquare – This bot will ask for permission to access the user's location, then provide geo-targeted results.

-

Spreading virally

-

Messages sent with the help of your bot will show its username next to the sender's name.

-
- - - - - -

- -

When a user taps on the bot username in the message header, the mention is automatically inserted into the input field. Entering the @ symbol in the input field brings up a list of suggestions, featuring recently used inline bots.

-

Collecting feedback

-

To know which of the provided results your users are sending to their chat partners, send @Botfather the /setinlinefeedback command. With this enabled, you will receive updates on the results chosen by your users.

-

Please note that this can create load issues for popular bots – you may receive more results than actual requests due to caching (see the cache_time parameter in answerInlineQuery). For these cases, we recommend adjusting the probability setting to receive 1/10, 1/100 or 1/1000 of the results.

-

Inline bot samples

-

Here are some sample inline bots, in case you’re curious to see one in action. Try any of these:
@gif – GIF search
@vid – Video search
@pic – Yandex image search
@bing – Bing image search
@wiki – Wikipedia search
@imdb – IMDB search
@bold – Make bold, italic or fixed sys text

-

NEW
@youtube - Connect your account for personalized results
@music - Search and send classical music
@foursquare – Find and send venue addresses
@sticker – Find and send stickers based on emoji

-
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/bots/samples.html b/data/core.telegram.org/bots/samples.html deleted file mode 100644 index 7cc5729af4..0000000000 --- a/data/core.telegram.org/bots/samples.html +++ /dev/null @@ -1,249 +0,0 @@ - - - - - Bot Code Examples - - - - - - - - - - - - - -
- -
-
-
- -

Bot Code Examples

- -
-

If you want to learn more about Telegram bots, start with our Introduction to Bots »
Check out the FAQ, if you have questions.

-
-

Many members of our community are building bots and libraries and publishing their source code. We collect these examples here. Ping us on BotSupport if you've built a bot and would like to share its code with others.

-

PHP

- -

Node.js

- -

Rust

- -

Python

- -

Ruby

- -

Swift

- -

Kotlin

- -

Java

- -

Go

- -

Other Languages

- -
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/bots/samples/hellobot.html b/data/core.telegram.org/bots/samples/hellobot.html deleted file mode 100644 index 9aaf3fa190..0000000000 --- a/data/core.telegram.org/bots/samples/hellobot.html +++ /dev/null @@ -1,287 +0,0 @@ - - - - - Hellobot - - - - - - - - - - - - - -
- -
-
-
- -

Hellobot

- -
-

This sample PHP bot demonstrates the basics of the Telegram Bot API.
If you have questions, try our FAQ or check out this page for more examples.

-
-

- -
<?php
-
-define('BOT_TOKEN', '12345678:replace-me-with-real-token');
-define('API_URL', 'https://api.telegram.org/bot'.BOT_TOKEN.'/');
-
-function apiRequestWebhook($method, $parameters) {
-  if (!is_string($method)) {
-    error_log("Method name must be a string\n");
-    return false;
-  }
-
-  if (!$parameters) {
-    $parameters = array();
-  } else if (!is_array($parameters)) {
-    error_log("Parameters must be an array\n");
-    return false;
-  }
-
-  $parameters["method"] = $method;
-
-  $payload = json_encode($parameters);
-  header('Content-Type: application/json');
-  header('Content-Length: '.strlen($payload));
-  echo $payload;
-
-  return true;
-}
-
-function exec_curl_request($handle) {
-  $response = curl_exec($handle);
-
-  if ($response === false) {
-    $errno = curl_errno($handle);
-    $error = curl_error($handle);
-    error_log("Curl returned error $errno: $error\n");
-    curl_close($handle);
-    return false;
-  }
-
-  $http_code = intval(curl_getinfo($handle, CURLINFO_HTTP_CODE));
-  curl_close($handle);
-
-  if ($http_code >= 500) {
-    // do not wat to DDOS server if something goes wrong
-    sleep(10);
-    return false;
-  } else if ($http_code != 200) {
-    $response = json_decode($response, true);
-    error_log("Request has failed with error {$response['error_code']}: {$response['description']}\n");
-    if ($http_code == 401) {
-      throw new Exception('Invalid access token provided');
-    }
-    return false;
-  } else {
-    $response = json_decode($response, true);
-    if (isset($response['description'])) {
-      error_log("Request was successful: {$response['description']}\n");
-    }
-    $response = $response['result'];
-  }
-
-  return $response;
-}
-
-function apiRequest($method, $parameters) {
-  if (!is_string($method)) {
-    error_log("Method name must be a string\n");
-    return false;
-  }
-
-  if (!$parameters) {
-    $parameters = array();
-  } else if (!is_array($parameters)) {
-    error_log("Parameters must be an array\n");
-    return false;
-  }
-
-  foreach ($parameters as $key => &$val) {
-    // encoding to JSON array parameters, for example reply_markup
-    if (!is_numeric($val) && !is_string($val)) {
-      $val = json_encode($val);
-    }
-  }
-  $url = API_URL.$method.'?'.http_build_query($parameters);
-
-  $handle = curl_init($url);
-  curl_setopt($handle, CURLOPT_RETURNTRANSFER, true);
-  curl_setopt($handle, CURLOPT_CONNECTTIMEOUT, 5);
-  curl_setopt($handle, CURLOPT_TIMEOUT, 60);
-
-  return exec_curl_request($handle);
-}
-
-function apiRequestJson($method, $parameters) {
-  if (!is_string($method)) {
-    error_log("Method name must be a string\n");
-    return false;
-  }
-
-  if (!$parameters) {
-    $parameters = array();
-  } else if (!is_array($parameters)) {
-    error_log("Parameters must be an array\n");
-    return false;
-  }
-
-  $parameters["method"] = $method;
-
-  $handle = curl_init(API_URL);
-  curl_setopt($handle, CURLOPT_RETURNTRANSFER, true);
-  curl_setopt($handle, CURLOPT_CONNECTTIMEOUT, 5);
-  curl_setopt($handle, CURLOPT_TIMEOUT, 60);
-  curl_setopt($handle, CURLOPT_POST, true);
-  curl_setopt($handle, CURLOPT_POSTFIELDS, json_encode($parameters));
-  curl_setopt($handle, CURLOPT_HTTPHEADER, array("Content-Type: application/json"));
-
-  return exec_curl_request($handle);
-}
-
-function processMessage($message) {
-  // process incoming message
-  $message_id = $message['message_id'];
-  $chat_id = $message['chat']['id'];
-  if (isset($message['text'])) {
-    // incoming text message
-    $text = $message['text'];
-
-    if (strpos($text, "/start") === 0) {
-      apiRequestJson("sendMessage", array('chat_id' => $chat_id, "text" => 'Hello', 'reply_markup' => array(
-        'keyboard' => array(array('Hello', 'Hi')),
-        'one_time_keyboard' => true,
-        'resize_keyboard' => true)));
-    } else if ($text === "Hello" || $text === "Hi") {
-      apiRequest("sendMessage", array('chat_id' => $chat_id, "text" => 'Nice to meet you'));
-    } else if (strpos($text, "/stop") === 0) {
-      // stop now
-    } else {
-      apiRequestWebhook("sendMessage", array('chat_id' => $chat_id, "reply_to_message_id" => $message_id, "text" => 'Cool'));
-    }
-  } else {
-    apiRequest("sendMessage", array('chat_id' => $chat_id, "text" => 'I understand only text messages'));
-  }
-}
-
-
-define('WEBHOOK_URL', 'https://my-site.example.com/secret-path-for-webhooks/');
-
-if (php_sapi_name() == 'cli') {
-  // if run from console, set or delete webhook
-  apiRequest('setWebhook', array('url' => isset($argv[1]) && $argv[1] == 'delete' ? '' : WEBHOOK_URL));
-  exit;
-}
-
-
-$content = file_get_contents("php://input");
-$update = json_decode($content, true);
-
-if (!$update) {
-  // receive wrong update, must not happen
-  exit;
-}
-
-if (isset($update["message"])) {
-  processMessage($update["message"]);
-}
-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/bots/self-signed.html b/data/core.telegram.org/bots/self-signed.html deleted file mode 100644 index ec670a6a4b..0000000000 --- a/data/core.telegram.org/bots/self-signed.html +++ /dev/null @@ -1,161 +0,0 @@ - - - - - Using self-signed certificates - - - - - - - - - - - - - -
- -
-
-
- -

Using self-signed certificates

- -

Upload your certificate using the certificate parameter in the setWebhook method. The certificate supplied should be PEM encoded (ASCII BASE64), the pem file should only contain the public key (including BEGIN and END portions). When converting from a bundle format, please split the file to only include the public key.

-

Generating a self-signed certificate pair (PEM):

-

Openssl

-
-

Windows binaries for Openssl are available online

-
-

openssl req -newkey rsa:2048 -sha256 -nodes -keyout YOURPRIVATE.key -x509 -days 365 -out YOURPUBLIC.pem -subj "/C=US/ST=New York/L=Brooklyn/O=Example Brooklyn Company/CN=YOURDOMAIN.EXAMPLE"

-

YOURPUBLIC.pem has to be used as input for setting the self-signed webhook.

-

You can inspect the generated certificate with:
openssl x509 -text -noout -in YOURPUBLIC.pem

-

Converting from a previously generated DER:
openssl x509 -inform der -in YOURDER.der -out YOURPEM.pem

-

Converting from a previously generated PKCS12:
openssl pkcs12 -in YOURPKCS.p12 -out YOURPEM.pem

-
-

More information: https://www.openssl.org/

-
-

Java keystore

-

Generate self-signed JKS:
keytool -genkey -keyalg RSA -alias YOURDOMAIN.EXAMPLE -keystore YOURJKS.jks -storepass YOURPASSWORD -validity 360 -keysize 2048

-

Converting JKS to pkcs12 (intermediate step for conversion to PEM):
keytool -importkeystore -srckeystore YOURJKS.jks -destkeystore YOURPKCS.p12 -srcstoretype jks -deststoretype pkcs12

-

Convert PKCS12 to PEM (requires openssl):
openssl pkcs12 -in YOURPKCS.p12 -out YOURPEM.pem

-
-

More information: https://docs.oracle.com

-
-

Windows

-

Creating a self-signed certificate using Windows native utilities is also possible, although OpenSSL binaries for Windows are available online.

-

On the commandline:
certreq -new TEMPLATE.txt RequestFileOut

-

TEMPLATE.txt example file:

-
[NewRequest]
-
-; At least one value must be set in this section
-Subject = "CN=DOMAIN.EXAMPLE"
-KeyLength = 2048
-KeyAlgorithm = RSA
-HashAlgorithm = sha256
-;MachineKeySet = true
-RequestType = Cert
-UseExistingKeySet=false ;generates a new private key (for export)
-Exportable = true ;makes the private key exportable with the PFX
-

A self-signed certificate will be generated and installed, to view the certificate:
certutil -store -user my

-

To export in DER format (intermediate step for conversion to PEM)
certutil -user -store -split my SERIALNUMBER YOURDER.crt

-

Converting to PEM (used for setting the webhook)
certutil -encode YOURDER.crt YOURPEM.cer

-

To delete a certificate from your store:
certutil -delstore -user my SERIALNUMBER (from view)

-

To export in PFX(PKCS12) format
certutil -exportpfx -user YOURDOMAIN.EXAMPLE YOURPKCS.pfx NoChain

-
-

More information: https://technet.microsoft.com

-
-

Converting YOURPKCS.pfx to PEM including the private key is best done with OpenSSL:
openssl pkcs12 -in YOURPKCS.pfx -out YOURPEM.cer

-

Remember that only the public key is needed as input for the self-signed webhook certificate parameter. certmgr.msc can also be used as a GUI to export the public part of self-signed certificates to PEM.

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/bots/webhooks.html b/data/core.telegram.org/bots/webhooks.html deleted file mode 100644 index f2a08082c7..0000000000 --- a/data/core.telegram.org/bots/webhooks.html +++ /dev/null @@ -1,827 +0,0 @@ - - - - - Marvin's Marvellous Guide to All Things Webhook - - - - - - - - - - - - - -
- -
-
-
- -

Marvin's Marvellous Guide to All Things Webhook

- -
- -

We currently support two ways of processing bot updates, getUpdates and setWebhook. getUpdates is a pull mechanism, setwebhook is push. Although the concept of a webhook is fairly simple, the setup of the individual components has proven to be tricky for many. This guide provides some extra information for those of you brave enough to venture into the art of the webhook.

-

There are some advantages of using a webhook over getUpdates. As soon as an update arrives, we’ll kindly deliver it to your bot for processing.

-

This:

-
1. Avoids your bot having to ask for updates frequently.
-2. Avoids the need for some kind of polling mechanism in your code.
-

Other advantages may include saving some potential CPU cycles and an increase in response time, these things however depend heavily on the usage pattern of your bot.

-

Setting a webhook means you supplying Telegram with a location in the form of a URL, on which your bot listens for updates. We need to be able to connect and post updates to that URL.

-

To ensure that we can do that, there are some basic requirements:

-

The short version

-

You'll need a server that:

-
    -
  • Supports IPv4, IPv6 is currently not supported for webhooks.
  • -
  • Accepts incoming POSTs from subnets 149.154.160.0/20 and 91.108.4.0/22 on port 443, 80, 88, or 8443.
  • -
  • Is able to handle TLS1.2(+) HTTPS-traffic.
  • -
  • Provides a supported, verified or self-signed certificate.
  • -
  • Uses a CN or SAN that matches the domain you’ve supplied on setup.
  • -
  • Supplies all intermediate certificates to complete a verification chain.
  • -
-

That’s almost all there’s to it.
If you decide to limit traffic to our specific range of addresses, keep an eye on this document whenever you seem to run into trouble. Our IP-range might change in the future.

-

The longer version

-
    -
  • A domain name

    -

    Setting a webhook needs a URL for us to post to. For that you'll need a server with a domain name. If you don't have one, you'll need to obtain one first. Telegram currently doesn't offer hosting or domain name services. There are quite a few VPS/Web hosting providers around the internet, feel free to pick one to your liking.
    If you're using a self-signed certificate, you may use the IP as a CN, instead of the domain name.
    How do I get a server with a domain name?

    -
  • -
  • An open port

    -

    A webhook needs an open port on your server. We currently support the following ports: 443, 80, 88 and 8443. Other ports are not supported and will not work. Make sure your bot is running on one of those supported ports, and that the bot is reachable via its public address.

    -
    If you want to limit access to Telegram only, please allow traffic from 149.154.167.197-233 (starting July 2019 please use: 149.154.160.0/20 and 91.108.4.0/22). 
    -Whenever something stops working in the future, please check this document again as 
    -the range might expand or change.
    -

    How do I check for open ports or limit access to my bot?

    -
  • -
  • Always SSL/TLS

    -

    A webhook requires SSL/TLS encryption, no matter which port is used. It's not possible to use a plain-text HTTP webhook. You shouldn't want to either, for the sake of your bot and users.
    SSL/TLS, why do I have to handle this for a webhook?

    -
  • -
  • Not all SSL/TLS is equal

    -

    We support any SSL/TLS version TLS1.2 and up for your webhook. This means that SSLV2/3/TLS1.0/TSL1.1 are NOT supported, due to security issues associated with those older versions.
    How do I check that I’m handling the right version?

    -
  • -
  • SSL needs a certificate

    -

    The common name (CN) of your certificate (self-signed or verified) has to match the domain name where your bot is hosted. You may also use a subject alternative name (SAN), that matches the domain for your webhook. Server Name Indication (SNI)-routing is supported. If you're using a self-signed certificate, you may use the IP as a CN, instead of the domain name.
    A certificate, where do I get one, and how?

    -
  • -
  • Verified or self-signed

    -

    A certificate can either be verified or self-signed. Setting a webhook with a self-signed certificate differs a little from setting a webhook with a verified certificate. Ensure you're using the correct setup for the type of certificate you've chosen for your webhook.
    How do I set a webhook for either type?

    -
  • -
  • Supported certificates

    -

    Not all verified certificates are supported. Certificates are based on a network of trust and come in a chain. Trusting your verified certificate means we have to trust the provider of that certificate, the Certificate Authority (and hence its root certificate). Before you pick a certificate provider, Check this list to make sure that we actually trust their root certificate.
    What if my root certificate isn’t on that list?

    -
  • -
  • An Untrusted root

    -

    Ok, so you already had a certificate installed and just discovered it’s not on our list.
    Start by ignoring it, and just try to set it. We occasionally add extra root certificates to keep up with popular demand, so the list isn't always exhaustive. Unlucky after all? We'll allow you to supply an unsupported root certificate when setting the webhook. This method is nearly identical to setting a self-signed certificate webhook. Instead of your self-signed certificate you'll be sending us the root certificate as inputFile.
    Setting a verified webhook with an untrusted root

    -
  • -
  • Intermediate certificates

    -

    Some verified certificates require an intermediate certificate. In this construction the provider of your verified certificate has used their root certificate to sign an intermediate certificate. This intermediate certificate is then used to sign your verified certificate. You'll need to provide the intermediate certificate for us to be able to verify the chain of trust. CA's that use this type of chain supply an intermediate certificate.
    Supplying an intermediate certificate

    -
  • -
  • More information

    -

    Since we know webhooks can be a tad overwhelming, we’re working on a little digital assistant that’ll try and help you with the most common problems, it's not nearly perfect, but you may try using @CanOfWormsBot to check if your chain of certificates is installed correctly before contacting support.

    -
  • -
  • Testing your bot

    -

    We took the liberty of adding a set of example updates. They come in handy when testing your bot, no matter which method of getting updates you might be using.

    -
  • -
  • Don't panic.

    -

    If by now you're looking for your fishing gear because we've mentioned ports and hooks or you're about to Google what kind of bait URL and TLS exactly are, this guide might not be completely for you. You’re quite likely still a brilliant bot programmer, don’t worry. Perhaps this whole webhook thing is just new to you, not all is lost. If you currently have a working getUpdates situation, it's a good idea to pick up this guide again on a rainy Sunday afternoon and take your time to read up on some subjects around the internet. This guide can only contain a finite amount of information after all.

    -
  • -
-

The verbose version

-
How do I get a server with a domain name?
-

If you use a webhook, we have to deliver requests to your bot to a server we can reach. So yes, you need a server we can connect to. It can be anywhere in the galaxy, if you ensure we can reach the server by domain name (or at least via IP for a self-signed certificate), it will work just fine.

-

There are quite a few ways to get this done, as a novice however it's likely that you're not directly jumping at the chance of crafting this from scratch. Actually, as a novice, we recommend you don't. It's likely to be a complex and long ride.

-

If you got stuck here, make a choice:

-
    -
  • You use getUpdates at the moment and it works, keep it that way. Especially if you're running your bot from a nice machine that does well. There is nothing wrong with using getUpdates.

    -
  • -
  • Go with a hosted service and let a bunch of professionals worry about things like registering a domain, setting up DNS, a web server, securing it and so on.

    -
  • -
-
If you're going with a hosted service, make sure to look for a hosting provider that 
-not only supports your code’s needs, for example: support for your PHP version,
-but one that also handles SSL and allows you to create/deploy certificates.
-
    -
  • Go crazy, dive on the internet and start reading. Once you’re confident that you’ve got all the basic theories down, find yourself a nice hosted VPS or roll your own machine at home and get back to us here.
  • -
-
How do I check for open ports or limit access to my bot?
-

So you have the hosting thing down and all is good so far, however, when you enter the address of your bot in your browser it seems unreachable.

-

Explaining every firewall or web server solution in detail isn't possible for us, which we hope you understand. If you’re running a hosted solution, you’re more likely to have a nice UI where you configure these settings. Head to your configuration panel and check all of them. If you’re on a Linux based VPS with shell access, we have some tips for you:

-
    -
  • Make sure your bot process is indeed configured to listen on the port you're using.
    netstat –ln | grep portnumber
    Shows you if your bot is actually listening for incoming requests on the port you expect.
    sudo lsof -i | grep process name
    Is a simple way to check if that’s actually being listened on by the process your bot is using.
  • -
-
    -
  • Make sure it’s listening correctly.
    Your bot has to listen on the address you’ve exposed to the outside (your public IP), it can also listen on all addresses (*: or 0.0.0.0).
    The netstat and lsof-commands mentioned above assist in checking this. If nothing shows up, it is time to check your configuration and fix it. Set the correct IP, make sure it’s listening on a supported port and fire away! Just use a Web Browser to check if you’re reachable. The problem can be in the configuration of your bot, your web server virtual host configuration, or the servers binding configuration.
  • -
-
    -
  • If you still can’t reach your address, check your firewall.
    sudo iptables –L
    OR
    sudo ufw status verbose (Ubuntu)
    Gives you some insight in the current firewall settings.

    -
  • -
  • If it looks like you’re blocking incoming traffic, let’s fix that.
    sudo iptables –A INPUT –p tcp –m tcp –dport portnumber -j ACCEPT
    OR
    sudo ufw allow portnumber/tcp
    Allows incoming traffic on all interfaces to the specified tcp port.
    sudo iptables –A INPUT –i interfacename –p tcp –m tcp –dport portnumber -j ACCEPT
    OR
    sudo ufw allow in on interfacename to any port portnumber proto tcp
    Allows incoming traffic to a specific interface and a specific port from everywhere.
    sudo ifconfig
    Helps you find the interface with the public address you’re going to use.

    -
  • -
-
If you use iptables, make sure to actually SAVE after changing the configuration.
-On a Debian based system the iptables-persistent package is be a good option.
-RHEL/CentOS offers a service iptables save -command.
-A quick online search for "YOUROPERATINGSYSTEM save iptables" also helps.
-
    -
  • If you’re just looking for some hints on how to limit incoming traffic:
    sudo iptables –A INPUT –i interfacename –p tcp –m iprange –src-range 149.154.167.197-149.154.167.233 –dport portnumber -j ACCEPT
    OR
    sudo ufw allow in on interfacename to any port portnumber proto tcp from 149.154.167.192/26
    Allows incoming traffic to a specific interface and a specific port from a specific range of addresses. (ufw is using a subnet mask in the example, ranging from 192-255)
  • -
-

That’s all for our examples. More information on best practices for setting up your firewall, on whichever operating system you prefer for your bot, is best found on the internet.

-
SSL/TLS, what is it and why do I have to handle this for a webhook?
-

You’re already familiar with it in some form or another. Whenever you see that (nicely green) lock in your browser bar, you know it’s reasonably safe to assume that you’ve landed on the site you actually wanted to visit. If you see the green lock, that's SSL/TLS in action. If you want to learn more about how SSL/TLS works in general, it's best to search the internet.

-

The main difference between getUpdates and a webhook is the way the connection takes place. getUpdates means you'll connect to our server, a webhook means we'll be connecting to your server instead. Connecting to your server has to be done secure, we have to know for sure it's you we're talking to after all. This means you'll have to handle all that server side encryption stuff, virtually presenting us with a green lock. If you use a web server for us to post to, you need to support SSL/TLS handling on the port/virtual host of your choice. An online search for “YOURWEBSERVER enable HTTPS” will help you.

-

Not using a regular web server? Have a look at our example page, most examples there include code for handling SSL/TLS in a webhook setup.

-
How do I check that I’m handling the right version?
-

You just read up on the whole SSL/TLS stuff, figured out that it’s not all that bad to setup and we add some more requirements. Here are some tips to check if you’re indeed supporting at least TLS1.2.

-
    -
  • Several online services exist that allow you to check your certificate installation,
    They give you an overview of your supported TLS versions/Cipher suites and other details. Search online for Symantec crypto report or Qualys ssl. Both supply tools to verify your setup.

    -
  • -
  • Checking locally can also be done, in several ways, here are three options,

    -
      -
    • Go simple:
      Using Chrome as a browser? Open up the URL to your bot and inspect the certificate details. If you’re supporting TLS Chrome tells you so in the security overview tab. Other browsers are likely able to give you similar basic information.

      -
    • -
    • Using curl:
      curl --tlsv1.2 -v -k https://yourbotdomain:yourbotport/
      You can add --tlsv1.2 to force curl into using TLS1.2 when trying to connect. -k is optional and used to check against a self-signed certificate. yourbotdomain is the public hostname your webhook is running on. For local testing purposes you can also use the IP. yourbotport is the port you’re using.

      -
    • -
    • Using OpenSSL
      openssl s_client -tls1_2 -connect yourbotdomain:yourbotport -servername yourbotdomain
      You can add -tls1_2 to force OpenSSL into using TLS1.2 when trying to connect. yourbotdomain is the public hostname your webhook is running on. For local testing purposes you can also use the IP. yourbotport is the port you’re using. Note that https:// isn’t used for OpenSSL. -servername is optional, and included here for some shared hosters, which use SNI to route traffic to the correct domain. When SNI is used you’ll notice that your server appears to be returning a certificate for a different domain than your own. Adding -servername yourbotdomain ensures that SNI negotiation is done, and the correct certificate is returned.

      -
    • -
    -
  • -
  • Some additional configuration pointers

    -
      -
    • Forcing TLS in your virtual host on Apache:
      SSLProtocol -all +TLSv1.2
    • -
    • Forcing TLS in your virtual host on Nginx:
      ssl_protocols TLSv1.2;
    • -
    • Force TLS for your Java virtual machine through system properties:
      -Dhttps.protocols=TLSv1.2 -Djdk.tls.client.protocols=TLSv1.2
    • -
    • Enabling ssl debug for your JVM:
      -Djavax.net.debug=ssl,handshake,record
    • -
    -
  • -
  • Other tools that may help in debugging issues:

    -
      -
    • Wireshark: excellent packet capturing
    • -
    • Tcpdump: equally excellent and doesn’t need a GUI
    • -
    • Charles: web debugging proxy
    • -
    • Fiddler: web debugging proxy
    • -
    -
  • -
-
A certificate, where do I get one and how?
-

You need a certificate, pick on of these types;

-
    -
  • A verified, supported certificate
  • -
  • A self-signed certificate

    -
  • -
  • A verified, supported certificate
    -

    Using a verified certificate means you already have, or will obtain, a certificate backed by a trusted certificate authority (CA). There are many ways to acquire a verified certificate, paid or free. Two popular examples of free suppliers are StartSSL and Let’s Encrypt. You’re welcome to pick another. Just make sure first the supplier is likely to be supported.
    Check this list before selecting a CA.
    Once you’ve picked a CA and validated your identity with them, you can craft your certificate. This frequently starts by generating a CSR (Certificate Signing Request). Generating a CSR is done either through your host machine, or online via the tools provided by the CA.

    -
  • -
  • Here is an example (PEM format output).

    -
      -
    • Using OpenSSL:
      openssl req -newkey rsa:2048 -keyout yourprivatekey.key -out yoursigningrequest.csr
    • -
    -
  • -
-
----
-Generating a 2048 bit RSA private keywriting new private key to yourprivatekey.key
-Enter PEM pass phrase: enter a password for your key here 
-Verifying - Enter PEM pass phrase: confirm the entered password
------
-You are about to be asked to enter information that will be incorporated
-into your certificate request.
-What you are about to enter is what is called a Distinguished Name or a DN.
-There are quite a few fields but you can leave some blank
-For some fields there will be a default value,If you enter '.',
-the field will be left blank.-----
-Country Name (2 letter code) [AU]:
-State or Province Name (full name) [Some-State]:
-Locality Name (eg, city) []:
-Organization Name (eg, company) [Internet Widgits Pty Ltd]:
-Organizational Unit Name (eg, section) []:
-Common Name (e.g. server FQDN or YOUR name) []: yourbotdomainname
-Email Address []:
-Please enter the following 'extra' attributes
-to be sent with your certificate request
-A challenge password []:
-An optional company name []:
----
-
    -
  • Another example:

    -
      -
    • Using Java keytool:
      keytool -genkey -alias yourbotdomainname -keyalg RSA -keystore yourkeystore.jks -keysize 2048
    • -
    -
  • -
-
---
-Enter keystore password:  
-Re-enter new password: 
-What is your first and last name?  [Unknown]: yourbotdomainname
-What is the name of your organizational unit?  [Unknown]:  
-What is the name of your organization?  [Unknown]:  
-What is the name of your City or Locality?  [Unknown]:  
-What is the name of your State or Province?  [Unknown]:  
-What is the two-letter country code for this unit?  [Unknown]:  
-Is CN=test.telegram.org, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown correct?  
-[no]:  yes
-Enter key password for yourbotdomainname   
-(RETURN if same as keystore password): 
----
-

This generates the initial keystore, from which you can then create a CSR like this:

-

keytool -certreq -alias yourbotdomainname -keystore yourkeystore.jks -file yourbotdomainname.csr

-
---
-Enter keystore password:
----
-

To validate your certificate the Common Name (CN) has to match your webhook domain. Example, if you’re using https://www.example.com/example.php as a webhook address, the certificate CN has to be www.example.com.
So you need an exact match of the FQDN you’re setting for the webhook

-

There is an exception, if you’re using a SAN (Subject Alternative Name) the webhook address can either match the CN of your certificate, OR one of the SANs provided in the certificate. In most cases you’ll be using the CN.

-

Create your CSR and supply the contents of the file to your CA. Most CA’s are kind enough to give you an example command of the input format they expect.

-

cat yoursigningrequest.csr or cat yourbotdomainname.csr
Lets you have a look at the CSR we just generated:

-
- -
- -

That doesn’t seem to informative, but we can deduce that the file is in PEM format (ASCII base64 encoded) and contains a certificate signing request. Luckily it is possible to look at the human readable contents of the CSR. Use the following commands to double check if all fields are set correctly.

-
    -
  • Using OpenSSL
    openssl req -text -noout -verify -in yoursigningrequest.csr

    -
  • -
  • Using Java keytool
    keytool -printcertreq -v -file yourbotdomainname.csr

    -
  • -
-

Verify your CSR and supply it to your CA to get a certificate. We’ll use StartSSL as an example here. StartSSL allows you to set up to 5 names (SAN), Their intermediate certificate is also needed for a webhook to work, which makes for a nice complete example.

-

Go to the certificates wizard, enter the required hostname(s) for your SSL certificate (this is the CN you’ve also set in the CSR and an optional SAN).

-
- -
- -

In the example above we’ve chosen to set a CN (test.telegram.org), but also a SAN (sanexample.telegram.org) The CN given has to match the CN used for generating the CSR.
Set your CN (and optional SAN) and copy the contents of the yoursigningrequest.csr file.

-
- -
- -

Paste the contents, submit and you’re done.

-
- -
- -

Now you can download the created certificate directly. In the example used above you’ll receive a zip file with several PEM certificates. The root, intermediate and yourdomain certificate.
You need the intermediate and yourdomain to set a webhook with a StartSSL certificate.

-

You can inspect the set of certificates you’ve just downloaded.

-
    -
  • Here are some example commands:

    -
      -
    • Using OpenSSL:
      openssl x509 -in yourdomain.crt -text -noout

      -
    • -
    • Using Java keytool:
      keytool -printcert -v -yourdomain.crt

      -
    • -
    • Using Windows:
      StartSSL supplies certificates in PEM format with a .crt extension, on Windows you can view the contents of them with a quick double click. Extract the files or open the “Otherserver.zip” and double click each of the certificates for inspection. The details tab supplies you with extra information.
      Make sure you have a correct CN in the Subject-field of the yourdomain-certificate. If you're using a SAN, make sure that it is listed in the Subject Alternative Name-field.

      -
    • -
    -
  • -
-
- -
- -

With your fresh certificates at hand, you can now continue setting your webhook.

-
    -
  • A self-signed certificate
    -

    Using a self-signed certificate means you’ll forfeit on the chain of trust backed by a CA. Instead you are the CA. For this to work, a slight difference in setup is required. Because Telegram will have no chain of trust to verify your certificate, you have to use the generated public certificate as an input file when setting the webhook. Keep in mind that the certificate file has to be uploaded as multipart/form data in PEM encoded (ASCII BASE64) format.

    -
  • -
  • First let’s generate some certificates:

    -
      -
    • Using OpenSSL:
      openssl req -newkey rsa:2048 -sha256 -nodes -keyout YOURPRIVATE.key -x509 -days 365 -out YOURPUBLIC.pem -subj "/C=US/ST=New York/L=Brooklyn/O=Example Brooklyn Company/CN=YOURDOMAIN.EXAMPLE"
      You’ll end up with 2 files, a private key and the public certificate file. Use YOURPUBLIC.PEM as input file for setting the webhook.

      -
    • -
    • Using Java keytool:
      keytool -genkey -keyalg RSA -alias YOURDOMAIN.EXAMPLE -keystore YOURJKS.jks -storepass YOURPASSWORD -validity 360 -keysize 2048

      -
      What is your first and last name?
      -[test.telegram.org]:
      -What is the name of your organizational unit?
      -[Unknown]:  
      -What is the name of your organization?
      -[Unknown]:  
      -What is the name of your City or Locality?
      -[Unknown]:  
      -What is the name of your State or Province?
      -[Unknown]:  
      -What is the two-letter country code for this unit?
      -[Unknown]:  
      -Is CN=test.telegram.org, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown correct?
      -[no]: yes
      -

      Once done you’ll need 2 more commands to export the public certificate file from the generated store (you’ll be using the store for your JVM and the PEM for setting the webhook)

      -
    • -
    • Convert the JKS to pkcs12 (intermediate step for conversion to PEM):
      keytool -importkeystore -srckeystore YOURJKS.jks -destkeystore YOURPKCS.p12 -srcstoretype jks -deststoretype pkcs12

      -
    • -
    • Convert PKCS12 to PEM (requires OpenSSL)
      openssl pkcs12 -in YOURPKCS.p12 -out YOURPEM.pem -nokeys

      -
    • -
    • Using Windows:
      Creating a self-signed certificate using Windows native utilities is also possible, although OpenSSL binaries for Windows are available online.
      certreq -new TEMPLATE.txt RequestFileOut generates a CSR.

      -
    • -
    • TEMPLATE.txt example file:

      -
      [NewRequest]
      -; At least one value must be set in this section
      -Subject = "CN=DOMAIN.EXAMPLE"
      -KeyLength = 2048
      -KeyAlgorithm = RSA
      -HashAlgorithm = sha256
      -;MachineKeySet = true
      -RequestType = Cert
      -UseExistingKeySet=false ;generates a new private key (for export)
      -Exportable = true ;makes the private key exportable with the PFX
      -
    • -
    -
  • -
-

A self-signed certificate is generated and installed, to use the certificate for a self-signed webhook you'll have to export it in PEM format.

-
    -
  • Windows continued:

    -
      -
    • You can have a look at the certificates in your store with:
      certutil -store -user my

      -
    • -
    • To export the installed certificate in DER format (intermediate step for conversion to PEM):
      certutil -user -store -split my SERIALNUMBER YOURDER.der

      -
    • -
    • Now you can convert the certificate to PEM:
      certutil -encode YOURDER.der YOURPEM.pem
      Remember that only the public certificate is needed as input for the self-signed webhook certificate parameter.
      certmgr.msc can also be used as a GUI to export the public part of self-signed certificate to PEM.

      -
    • -
    -
  • -
-

After following the above you'll end up with a nice self-signed certificate. You’ll still have to set the webhook, and handle SSL correctly.

-
How do I set a webhook for either type?
-

The setWebhook method is needed for both types. For a verified certificate with a trusted root CA, it’s enough to use the setWebhook method with just the URL parameter.

-
    -
  • A curl example for a verified certificate:
    curl -F "url=https://<YOURDOMAIN.EXAMPLE>/<WEBHOOKLOCATION>" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
  • -
-

For a self-signed certificate an extra parameter is needed, certificate, with the public certificate in PEM format as data.

-
    -
  • A curl example for a self-signed certificate:
    curl -F "url=https://<YOURDOMAIN.EXAMPLE>/<WEBHOOKLOCATION>" -F "certificate=@<YOURCERTIFICATE>.pem" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
  • -
-

The -F means we’re using the multipart/form-data-type to supply the certificate, the type of the certificate parameter is inputFile. Make sure that you’re supplying the correct type.

-

Both parameters for the setWebhook method are classed as optional. Calling the method with an empty URL parameter can be used to clear a previously set webhook.

-
    -
  • A curl example to clear a previous webhook :
    curl -F "url=" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
  • -
-

Keep in mind that the URL parameter starts with https:// when setting a webhook. By default that means we’re knocking at your door on port 443. If you want to use another port (80,88 or 8443), you’ll have to specify the port in the URL parameter.

-
    -
  • Example:
    url=https://<YOURDOMAIN.EXAMPLE>:88/<WEBHOOKLOCATION>
  • -
-
Setting a verified webhook with an untrusted root
-

If you already have a verified certificate and our servers don’t trust your root CA, we have an alternative way for you to set a webhook. Instead of using the setWebhook method without the certificate parameter, you can use the self-signed method. Your CA's root certificate has to be used as an inputFile for the certificate parameter.

-
    -
  • A curl example to supply an untrusted root certificate:
    curl -F "url=https://<YOURDOMAIN.EXAMPLE>" -F "certificate=@<YOURCAROOTCERTIFICATE>.pem" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
    Before you can do this, you need the root certificate of your certificate’s CA. Most CA’s supply their root certificates in several different formats (PEM/DER/etc.). Visit your CA’s website, and download the Root certificate indicated for your verified certificate.
  • -
-

You can use these commands to quickly convert a DER formatted root certificate to PEM:

-
    -
  • Using OpenSSL:
    openssl x509 -inform der -in root.cer -out root.pem

    -
  • -
  • Using Java keytool:
    keytool -import -alias Root -keystore YOURKEYSTORE.JKS -trustcacerts -file ROOTCERT.CER
    The root certificate needs to be imported in your keystore first:
    keytool -exportcert -alias Root -file <YOURROOTPEMFILE.PEM> -rfc -keystore YOURKEYSTORE.JKS

    -
  • -
-

Once done, set your webhook with the root-pem-file and you’ll be good to go. If you need more pointers, have a look at the self-signed part of this guide.

-
Supplying an intermediate certificate
-

Once you’ve crafted your certificate, your CA might present you with a nice bundle. Most bundles contain a root certificate, your public certificate and sometimes an intermediate certificate. StartSSL is one of many CA’s that’ll supply such an intermediate beast. This certificate has to be supplied in the chain of certificates you’re presenting to us when we connect to your server. If an intermediate was used to sign your certificate but isn’t supplied to our servers, we won’t be able to verify the chain of trust and your webhook will not work.

-

If your webhook isn’t working and you’re wondering if the chain is complete:

-
    -
  • Check with your certificate provider if you need an intermediate certificate.
  • -
  • Verify your certificate chain.
    Search online for Symantec crypto report or Qualys ssl. 
    -Both supply tools to verify your setup.
    -
  • -
-

Here’s an example of a complete chain, note that in this case 2 intermediate certificates have been supplied.

-
- -
- -

Even though your browser might not complain when visiting your page, an incomplete chain will not work for your webhook. If your chain is incomplete we have some tips to add them to your current setup:

-
    -
  • Apache:
    Add the intermediate certificate to the end of the file configured in the SSLCertificateFile directive of your virtual host configuration. If you’re using an older version than Apache 2.4.8, you may use the SSLCertificateChainFile directive instead.

    -
  • -
  • Nginx:
    Add the intermediate certificate to the end of the file configured in the ssl_certificate_key directive of your virtual host configuration.

    -
  • -
  • A quick command for doing this correctly:
    cat your_domain_name.pem intermediate.pem >> bundle.pem
    Make sure the order is correct, expect failure otherwise.

    -
  • -
  • Java keytool:
    keytool -import -trustcacerts -alias intermediate -file intermediate.pem -keystore YOURKEYSTORE.jks

    -
  • -
-

The end result of all this is a complete certificate chain, backed by either a root certificate we trust or, in the case of an untrusted root, a root certificate you're supplying to us. Make sure to verify your setup again after adding the intermediate, once done, you're good to go!

-
Testing your bot with updates
-
    -
  • Update examples
    A set of example updates, which comes in handy for testing your bot.

    -
      -
    • Message with text using curl:

      -
      curl --tlsv1.2 -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test",
      -     "username":"Test"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test",
      -     "username":"Test"
      -  },
      -  "text":"/start"
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -

      --tlsv1.2 will force using TLS1.2.

      -
    • -
    • Message with text using Postman:

      -
      - -
      -
    • -
    -
  • -
  • More examples in curl:

    -
      -
    • Message with text:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "type": "private",
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "text":"/start"
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Forwarded message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "type": "private",
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "forward_from": {
      -     "last_name":"Forward Lastname",
      -     "id": 222222,
      -     "first_name":"Forward Firstname"
      -  },
      -  "forward_date":1441645550,
      -  "text":"/start"
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Forwarded channel message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "forward_from": {
      -     "id": -10000000000,
      -     "type": "channel",
      -     "title": "Test channel"
      -  },
      -  "forward_date":1441645550,
      -  "text":"/start"
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Message with a reply:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "text":"/start",
      -  "reply_to_message":{
      -      "date":1441645000,
      -      "chat":{
      -          "last_name":"Reply Lastname",
      -          "type": "private",
      -          "id":1111112,
      -          "first_name":"Reply Firstname",
      -          "username":"Testusername"
      -      },
      -      "message_id":1334,
      -      "text":"Original"
      -  }
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Edited message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"edited_message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "text":"Edited text",
      -  "edit_date": 1441646600
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Message with entities:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "text":"Bold and italics",
      -  "entities": [
      -      {
      -          "type": "italic",
      -          "offset": 9,
      -          "length": 7
      -      },
      -      {
      -          "type": "bold",
      -          "offset": 0,
      -          "length": 4
      -      }
      -      ]
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Message with audio:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "audio": {
      -      "file_id": "AwADBAADbXXXXXXXXXXXGBdhD2l6_XX",
      -      "duration": 243,
      -      "mime_type": "audio/mpeg",
      -      "file_size": 3897500,
      -      "title": "Test music file"
      -  }
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Voice message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "voice": {
      -      "file_id": "AwADBAADbXXXXXXXXXXXGBdhD2l6_XX",
      -      "duration": 5,
      -      "mime_type": "audio/ogg",
      -      "file_size": 23000
      -  }
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Message with a document:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "document": {
      -      "file_id": "AwADBAADbXXXXXXXXXXXGBdhD2l6_XX",
      -      "file_name": "Testfile.pdf",
      -      "mime_type": "application/pdf",
      -      "file_size": 536392
      -  }
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Inline query:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"inline_query":{
      -  "id": 134567890097,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "query": "inline query",
      -  "offset": ""
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Chosen inline query:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"chosen_inline_result":{
      -  "result_id": "12",
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "query": "inline query",
      -  "inline_message_id": "1234csdbsk4839"
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Callback query:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"callback_query":{
      -  "id": "4382bfdwdsb323b2d9",
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "data": "Data from button callback",
      -  "inline_message_id": "1234csdbsk4839"
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -That's all we have for now!
    • -
    -
  • -
-
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/cdn.html b/data/core.telegram.org/cdn.html deleted file mode 100644 index 197bb8e0e2..0000000000 --- a/data/core.telegram.org/cdn.html +++ /dev/null @@ -1,210 +0,0 @@ - - - - - Encrypted CDNs for Speed and Security - - - - - - - - - - - - - -
- -
-
-
-
-

Encrypted CDNs for Speed and Security

- -

Following the launch of version 4.2 of the official apps, Telegram client apps may be required to download popular files that were published in public channels with more than 100,000 members from secondary Content Delivery Network data centers. These CDN DCs are located in regions with significant Telegram traffic where we wouldn't want to place Telegram servers for various reasons.

-

The CDN DCs are not a part of the Telegram cloud and should be considered enemy territory. For this reason, each file that is to be sent to these CDN DCs is encrypted with a unique key using AES-256-CTR encryption. The CDN can't access the data it stores because these keys are only accessible to the main MTProto server and to the authorized client.

-
-

See also: More about CDNs and governments in the Advanced FAQ

-
-

How this works

-

When a file from a public channel with ~100,000 members becomes popular in a particular region, the Telegram server may encrypt this file with a unique AES-256-CTR key and send it to a relevant CDN DC for storage.

-

When a file is stored in a CDN DC close to the end user, the download speed will be much higher because the data needs to travel smaller distances and will likely avoid many bottlenecks that exist between regions.

-

This is secure because CDN DCs are treated the same way as internet providers / random third parties:

-
    -
  • CDN DCs don‘t have the keys to decrypt files that are stored there, so they can’t access the data even if a DC becomes compromised.
  • -
  • Encrypted files fragments are protected from tampering by their SHA-256 hash which is checked on the client upon receipt.
  • -
  • No private data is stored in or passed to the CDN DCs.
  • -
  • The server only allows media from public channels with more than 100,000 subscribers to be cached in CDN DCs (this includes media forwarded from those channels and viral media that originated from other large public channels).
  • -
-
- -
- -

CDNs are very limited when it comes to communication: the master data center only uploads encrypted files for storage and will accept no data from the CDN. The client apps only download encrypted files and accept no other updates. The client apps obtain the keys necessary to decrypt the file from the main Telegram server and verify the integrity of the file by its hash, which means that the CDN may only supply the correct file – anything different will be immediately discarded by the client.

-

CDN DCs do not store files on hard disks – only in memory. When a CDN server runs out of memory, a simple LRU algorithm is used to replace the least popular files with new ones.

-

How CDN DCs are different from the master DCs

-
    -
  • CDNs may not be trusted.
  • -
  • Client developers can use help.getCdnConfig to obtain a list of public RSA keys for CDN DCs, which are different from public RSA keys of the master DCs.
  • -
  • CDNs support only the following methods: upload.getCdnFile, initConnection, invokeWithLayer.
  • -
  • When working with CDNs, client developers must remember that auth_key may be deleted at any given moment (resulting in a -404 error, in which case a new key must be generated).
  • -
  • Client apps must not accept updates from CDN DCs (apps should only accept updates from their main connection to the master DC).
  • -
  • Clients must not allow the CDN DCs to substitute replies to queries sent to other DCs.
  • -
  • Clients must not send private user info that is passed in initConnection to the CDNs.
  • -
-

Getting files from a CDN

-

The API may return the upload.fileCdnRedirect constructor after an upload.getFile query. In this case, the client must request the required file from a CDN DC. The dc_id in the response is the id of the new CDN. The IP address for the connection will be available in help.getConfig, same as with the master DCs. The corresponding dcOption will have the flag cdn:flags.3?true.

-

Once a successful connection to the CDN-dc_id is established, the client must generate an auth_key (after confirming that the public RSA MTProto key of the CDN DC matches one from the list returned in help.getCdnConfig). Then the client must perform an upload.getCdnFile for each offset. For files of an unknown size it is necessary to repeat the query until an empty reply is returned.

-

upload.getCdnFile may return the upload.cdnFileReuploadNeeded constructor. In this case, the client needs to send an upload.reuploadCdnFile request to the DC that got the original upload.getFile request. Once upload.reuploadCdnFile is successfull, the app needs to request the file from the CDN DC again.

-

The main DC for a file is the DC where its main copy is stored (not to be confused with the main DC of the user) – either userProfilePhoto.dc_id, chatPhoto.dc_id, photo.dc_id, or document.dc_id.

-

Decrypting files

-

In upload.fileCdnRedirect, the server sends a decryption key and IV for the file (the fields encryption_key:bytes and encryption_iv:bytes respectively).

-

Having received a portion of encrypted data from the CDN DC inside upload.cdnFile, the client must decrypt this data using AES-256-CTR. For IV, it should use the value of encryption_iv, modified in the following manner: for each offset replace the last 4 bytes of the encryption_iv with offset / 16 in big-endian. This allows to effectively decrypt a file and to use random access to a file's content (e.g., for streaming).

-

Verifying files

-

In order to confirm that the CDN DC passed an untampered file, clients must verify hashes for each downloaded part. upload.fileCdnRedirect, upload.reuploadCdnFile and upload.getCdnFileHashes contain FileHash constructors. Each of these constructors contains the SHA-256 hash of a part of the file that starts with offset and takes limit bytes.

-

Before saving each portion of the data received from the CDN DC into the file, the client must confirm that its hash matches the hash that was received from the master DC. If missing a hash for any file part, client developers must use the upload.getCdnFileHashes method to obtain the missing hash.

-

Schema

-
fileHash#6242c773 offset:int limit:int hash:bytes = FileHash;
-
-upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;
-
-upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;
-upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;
-
-
-dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;
-
-cdnPublicKey#c982eaba dc_id:int public_key:string = CdnPublicKey;
-
-
-cdnConfig#5725e40a public_keys:Vector<CdnPublicKey> = CdnConfig;
-
----functions---
-
-// CDN DC
-upload.getCdnFile#2000bcc3 file_token:bytes offset:int limit:int = upload.CdnFile;
-
-// Master DC
-upload.reuploadCdnFile#9b2754a8 file_token:bytes request_token:bytes = Vector<FileHash>;
-upload.getCdnFileHashes#4da54231 file_token:bytes offset:int = Vector<FileHash>;
-
-help.getCdnConfig#52029342 = CdnConfig;
-

Restrictions on upload.getFile and upload.getCdnFile parameters

-
    -
  • offset must be divisible by 4096 bytes
  • -
  • limit must be divisible by 4096 bytes
  • -
  • 1048576 (1MB) must be divisible by limit
  • -
  • offset / (1024 * 1024) == (offset + limit - 1) / (1024 * 1024)
    (file parts that are being downloaded must always be inside the same megabyte-sized fragment)
  • -
-

Possible errors and their meanings

- - - - - - - - - - - - - - - - - - -
upload.getCdnFileFILE_TOKEN_INVALIDThe CDN DC did not accept the file_token (e.g., the token has expired). Continue downloading the file from the master DC using upload.getFile.
upload.reuploadCdnFileFILE_TOKEN_INVALIDThe master DC did not accept the file_token (e.g., the token has expired). Continue downloading the file from the master DC using upload.getFile.
upload.reuploadCdnFileREQUEST_TOKEN_INVALIDThe master DC did not accept the request_token from the CDN DC. Continue downloading the file from the master DC using upload.getFile.
-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/cdn/faq_ir.html b/data/core.telegram.org/cdn/faq_ir.html deleted file mode 100644 index 0ba8a4f1a6..0000000000 --- a/data/core.telegram.org/cdn/faq_ir.html +++ /dev/null @@ -1,142 +0,0 @@ - - - - - شبکه‌های تحویل محتوا (CDN) رمزنگاری شده - - - - - - - - - - - - - -
- -
-
-
-
-

شبکه‌های تحویل محتوا (CDN) رمزنگاری شده

- -
- - -

از نسخهٔ ۴.۲ تلگرام ما از CDN رمزنگاری شده برای ذخیره فایل‌های کانال های عمومی با بیش از ۱۰۰٫۰۰۰ عضو پشتیبانی می‌کنیم. نقاط ذخیره سازی CDN در مناطقی در نظر گرفته شده اند که تلگرام ترافیک زیادی دارد ولی ما به دلایل مختلف تمایلی به قرارگیری سرورهای تلگرام در آن مناطق نداریم.

-
-

برای اطلاعات فنی در خصوص نحوه پیاده سازی، رمزنگاری و تایید اعتبار داده‌ها راهنمای CDN در این لینک را ببینید. همچنین برای توضیحات سیستم از طرف پاول دورُف به این پست مراجعه کنید.

-
-

سوال: چرا تصمیم به استفاده از CDN گرفتید؟

-

ما از سرور‌های توزیع شده خود برای افزایش سرعت دانلود در مناطق بدون سانسور که در آنها آزادی بیان تضمین شده‌است استفاده می‌کنیم. و حتی در آن مناطق نیز به آنها اعتماد نمی‌کنیم. اما وقتی تلگرام در مناطق دیگر به شدت محبوب می‌شود، فقط می‌توانیم روی CDNها تکیه کنیم؛ که با آنها از نقطه نظر فنی مانند سرویس‌دهنده‌‌های اینترنت (ISP) رفتار می‌کنیم و آنها فقط داده‌های رمزنگاری شده‌ای را که قادر به کشف رمز آن نیستند دریافت می‌کنند.
به لطف این فناوری، سرعت دانلود عکس‌ها و فیلم‌هایی که به صورت عمومی منتشر می‌شوند در مناطقی نظیر ترکیه، اندونزی،‌ عربستان سعودی، هند، ایران و عراق به مراتب افزایش می‌یابد، بدون اینکه کمترین خدشه‌ای به امنیت وارد شود.

-

سوال: آیا CDN می‌تواند فایل‌ها را رمزگشایی کند؟

-

خیر. هر فایلی که به مراکز داده CDN ارسال می‌شود، با یک کلید منحصر به فرد با استفاده از تکنولوژی AES-256-CTR رمزگذاری می‌شود. CDN دسترسی به اطلاعاتی که ذخیره می‌کند ندارد، چرا که این کلید‌ها تنها در سرور MTProto (سرور رمزگذاری) اصلی و دستگاه کاربر قابل دسترسی هستند.

-

سوال: آیا CDNها می‌توانند اطلاعات را با اطلاعات دلخواه خودشان جایگزین کنند؟

-

خیر. اطلاعات و داده‌های دانلود شده (دریافتی)‌ از سمت نقاط ذخیره سازی CDN همیشه از طرف Telegram بوسیله رمزنگاری hash تایید و بررسی می‌شود: بدين ترتیب هکرها یا افراد متجاوز نمی‌توانند هیچ فایلی را جایگزین کنند.

-

سوال: آيا CDN مى‌تواند هر نوع فايل را حذف كند؟

-

خير. CDNها فقط كپى‌ فايل هاى رمزنگارى شده را ذخيره مى‌كنند، فايل‌هاى اصلي در سرورهای تلگرام ذخيره مى‌شوند. كاربر تنها اعلان دريافت فايل را از طريق سرور تلگرام مى‌گيرد. اگر كه CDN فايل مورد نظر را به كاربر ارسال نكند، كاربر اين فايل را مستقيماً از سرور تلگرام دريافت خواهد كرد.

-

سوال: آيا CDN ها مى توانند برای سانسور استفاده بشوند؟

-

خير. تمامى فايل‌هاى اصلي در سرورهای تلگرام ذخيره مى‌شوند. CDN ها فقط داده هاى رمزگذاري شده را دريافت مى‌كنند و قادر نيستند آن را رمزگشايى و يا هيچ گونه داده را جايگزين كنند. اگر مشكلى پيش آيد، فايل مورد نظر مستقيما از سرور هاى تلگرام به كاربران ارسال می‌شود. كاربران هميشه داده هایشان را دريافت مى‌كنند و هيچ كس نمى‌تواند مانع آنها بشود.

-

سوال: آیا می‌توانم این موضوع را بررسی کنم؟

-

بله. همه می‌توانند روش ما برای پیاده‌سازی CDN را با بررسی کد‌های Source Code برنامه‌های تلگرام و بررسی ترافیک داده بررسی کنند.

-

سوال: آیا این شامل اطلاعات خصوصی هم می‌شود؟

-

خیر. نقاط ذخیره سازی CDN بخشی از سرور اَبری تلگرام نیستند. CDNها فقط برای ذخیره‌سازی فایل‌های پر طرفدار از کانال‌های پر بازدید استفاده می‌شوند. اطلاعات خصوصی و شخصی هرگز به آنها راه پیدا نمی‌کنند.

-

سوال: آیا این با درخواست‌های دولت‌ها برای انتقال اطلاعات خصوصی به قلمرو آن‌ها مرتبط هست؟

-

خیر. ما وارد هیچ توافق یا تفاهمی با دولت‌ها در این مورد نشده‌ایم و CDNها بخشی از هیچ معامله‌ای نیستند. این به دلیل غیر منطقی بودن قوانین محلی نیست – ما هیچ‌گاه سرورهایمان را به کشوری با سابقه سانسور اینترنتی انتقال نمی‌دهیم.

-

تنها هدف استفاده از CDNها این است که کیفیت اتصال در مناطق با تقاضای بالا، که تلگرام نمی‌تواند سرورهای خود را به آنجا منتقل کند، با روشی ایمن، افزایش یابد.

-

سوال: آیا این موضوع می‌تواند به برخی کشورها، قدرت تسلط بر تلگرام بدهد؟

-

خیر. ما احتیاط ویژه‌ای به خرج داده‌ایم تا مطمئن شویم هیچ کشوری از طریق نقاط ذخیره سازی CDN به قدرت نفوذ روی تلگرام دست نیابد:
- CDNها و نقاط آن به تلگرام تعلق نداشته و همه ریسک آن به گردن شرکت ثالثی که نقاط ذخیره سازی CDN در سراسر دنیا را برای ما تامین می‌کند خواهد بود.
- ما هیچ سرمایه‌گذاری‌ای روی این CDNها انجام نمی‌دهیم و تنها بابت ترافیک مصرفی برای انتقال موارد ذخیره شده از خوشهٔ کامپیوترهای اصلی خودمان به کاربر نهایی، هزینه پرداخت می‌کنیم.

-

در نتیجه، اگر کشوری تصمیم به دستکاری CDN در منطقه خودش بگیرد، به چیزی جز پایین آوردن کیفیت اتصال شهروندان خودشان دست نمی‌یابد – و تلگرام هیچ چیز با ارزشی را از دست نخواهد داد.

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/cdn/faq_ir/durov.html b/data/core.telegram.org/cdn/faq_ir/durov.html deleted file mode 100644 index 606b94f25a..0000000000 --- a/data/core.telegram.org/cdn/faq_ir/durov.html +++ /dev/null @@ -1,133 +0,0 @@ - - - - - توضيحات CDNهاى رمزنگارى شده - - - - - - - - - - - - - -
- -
-
-
-
-

توضيحات CDNهاى رمزنگارى شده

- -
- -
-

ترجمه فارسى اين پست از كانال رسمى پاول دورُف در تلگرام در زير آمده است:

-
-

همانطور که پیشتر قول داده بودم، جزئیات بیشتری درباره اینکه چطور نقاط ذخیره سازی CDN ثالث می‌توانند سرعت دانلود محتوای عمومیِ پربازدید را در مناطقی که تلگرام تمایل به نصب سرورهای خود در آنجا ندارد، به روشی امن بالا ببرد، منتشر می‌کنم.

- -

همانطور که مشاهده می‌کنید، نقاط ذخیره سازی CDN هیچ ارتباطی با مساله انتقال سرورهای تلگرام یا رعایت قوانین غیر منطقی محلی ندارند. CDNها صرفا ابزاری جهت ارتقا کیفیت اتصال میلیون‌ها کاربر، به روشی امن، هستند. ما با این نقاط CDN دقیقا همانطور رفتار می‌کنیم که با مراکز تامین کننده اینترنت (ISP) شما رفتار می‌کنیم. آنها صرفا مشتی دادهٔ رمزنگاری شده دریافت می‌کنند که قادر به کشف رمز آن نخواهند بود.

-

خوبی تلگرام این است که وقتی بحث امنیت مطرح می‌شود، لازم نیست صرفا روی گفته‌های من حساب کنید. هر کسی می‌تواند نحوه اجرای نقاط CDN در نسخه بروز شده تلگرام برای iOS و اندروید را بررسی کند. همچنین اگر تمایل داشته‌باشید می‌توانید نگاهی به اسناد ما در لینک فوق بیندازید، تا مطمئن شوید همه چیز امن است.

-

ما با یک تامین کننده بین‌المللی CDN همکاری می‌کنیم که با نقاط ذخیره سازی خود در سراسر دنیا به ما کمک می‌کند. اگر یک دولت محلی تصمیم به توقیف یک نقطه ذخیره سازی در مرزهای خود بگیرد، تلگرام چیزی از دست نخواهد داد؛ چرا که آن CDN جز اموال ما نیست و حتی در تئوری کوچکترین اطلاعات خصوصی تحت تاثیر این عمل قرار نخواهد گرفت. بنابراین به قوانین و دولت‌های محلی وابستگی پیدا نمی‌کنیم و هیچ ریسک حقوقی یا مالی نخواهیم داشت، اما سرعت دانلود محتوای عمومی را بطور چشمگیری افزایش می‌دهیم.

-

چنانچه، با وجود توضیحات فوق، باز هم برخی رسانه‌ها از تیتر های جنجالی مانند «تلگرام سرورهایش را به کره شمالی انتقال داد» استفاده کردند، لطفا مارا با اطلاع رسانی در مورد حقیقت ماجرا که در لینک‌های این پیام آمده است، یاری کنید. بابت مطالعه این مطلب از شما تشکر می‌کنم و مثل همیشه، در همین کانال، شما را از هر خبر بین المللی در مورد تلگرام مطلع خواهم کرد.

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.authorizationForm b/data/core.telegram.org/constructor/account.authorizationForm deleted file mode 100644 index f12161fe65..0000000000 --- a/data/core.telegram.org/constructor/account.authorizationForm +++ /dev/null @@ -1,174 +0,0 @@ - - - - - account.authorizationForm - - - - - - - - - - - - - -
- -
-
-
- -

account.authorizationForm

- -

Telegram Passport authorization form

-

- -
-
account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
required_typesVector<SecureRequiredType>Required Telegram Passport documents
valuesVector<SecureValue>Already submitted Telegram Passport documents
errorsVector<SecureValueError>Telegram Passport errors
usersVector<User>Info about the bot to which the form will be submitted
privacy_policy_urlflags.0?stringURL of the service's privacy policy
-

Type

-

account.AuthorizationForm

-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.authorizations b/data/core.telegram.org/constructor/account.authorizations deleted file mode 100644 index 6f44355f75..0000000000 --- a/data/core.telegram.org/constructor/account.authorizations +++ /dev/null @@ -1,147 +0,0 @@ - - - - - account.authorizations - - - - - - - - - - - - - -
- -
-
-
- -

account.authorizations

- -

Logged-in sessions

-

- -
-
account.authorizations#1250abde authorizations:Vector<Authorization> = account.Authorizations;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
authorizationsVector<Authorization>Logged-in sessions
-

Type

-

account.Authorizations

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.autoDownloadSettings b/data/core.telegram.org/constructor/account.autoDownloadSettings deleted file mode 100644 index e9d893123b..0000000000 --- a/data/core.telegram.org/constructor/account.autoDownloadSettings +++ /dev/null @@ -1,157 +0,0 @@ - - - - - account.autoDownloadSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.autoDownloadSettings

- -

Media autodownload settings

-

- -
-
account.autoDownloadSettings#63cacf26 low:AutoDownloadSettings medium:AutoDownloadSettings high:AutoDownloadSettings = account.AutoDownloadSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
lowAutoDownloadSettingsLow data usage preset
mediumAutoDownloadSettingsMedium data usage preset
highAutoDownloadSettingsHigh data usage preset
-

Type

-

account.AutoDownloadSettings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.chatThemes b/data/core.telegram.org/constructor/account.chatThemes deleted file mode 100644 index 77eac280a5..0000000000 --- a/data/core.telegram.org/constructor/account.chatThemes +++ /dev/null @@ -1,155 +0,0 @@ - - - - - account.chatThemes - - - - - - - - - - - - - -
- -
-
-
- -

account.chatThemes

- -

Available chat themes

-

- -
-
account.chatThemes#fe4cbebd hash:int themes:Vector<ChatTheme> = account.ChatThemes;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashintHash for pagination, for more info click here
themesVector<ChatTheme>Available chat themes
-

Type

-

account.ChatThemes

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.chatThemesNotModified b/data/core.telegram.org/constructor/account.chatThemesNotModified deleted file mode 100644 index 6c8eb40de5..0000000000 --- a/data/core.telegram.org/constructor/account.chatThemesNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - account.chatThemesNotModified - - - - - - - - - - - - - -
- -
-
-
- -

account.chatThemesNotModified

- -

The available chat themes were not modified

-

- -
-
account.chatThemesNotModified#e011e1c4 = account.ChatThemes;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

account.ChatThemes

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.contentSettings b/data/core.telegram.org/constructor/account.contentSettings deleted file mode 100644 index 898494bafa..0000000000 --- a/data/core.telegram.org/constructor/account.contentSettings +++ /dev/null @@ -1,157 +0,0 @@ - - - - - account.contentSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.contentSettings

- -

Sensitive content settings

-

- -
-
account.contentSettings#57e28221 flags:# sensitive_enabled:flags.0?true sensitive_can_change:flags.1?true = account.ContentSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
sensitive_enabledflags.0?trueWhether viewing of sensitive (NSFW) content is enabled
sensitive_can_changeflags.1?trueWhether the current client can change the sensitive content settings to view NSFW content
-

Type

-

account.ContentSettings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.password b/data/core.telegram.org/constructor/account.password deleted file mode 100644 index a6d3dc0217..0000000000 --- a/data/core.telegram.org/constructor/account.password +++ /dev/null @@ -1,213 +0,0 @@ - - - - - account.password - - - - - - - - - - - - - -
- -
-
-
- -

account.password

- -

Configuration for two-factor authorization

-

- -
-
account.password#185b184f flags:# has_recovery:flags.0?true has_secure_values:flags.1?true has_password:flags.2?true current_algo:flags.2?PasswordKdfAlgo srp_B:flags.2?bytes srp_id:flags.2?long hint:flags.3?string email_unconfirmed_pattern:flags.4?string new_algo:PasswordKdfAlgo new_secure_algo:SecurePasswordKdfAlgo secure_random:bytes pending_reset_date:flags.5?int = account.Password;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
has_recoveryflags.0?trueWhether the user has a recovery method configured
has_secure_valuesflags.1?trueWhether telegram passport is enabled
has_passwordflags.2?trueWhether the user has a password
current_algoflags.2?PasswordKdfAlgoThe KDF algorithm for SRP two-factor authentication of the current password
srp_Bflags.2?bytesSrp B param for SRP authorization
srp_idflags.2?longSrp ID param for SRP authorization
hintflags.3?stringText hint for the password
email_unconfirmed_patternflags.4?stringA password recovery email with the specified pattern is still awaiting verification
new_algoPasswordKdfAlgoThe KDF algorithm for SRP two-factor authentication to use when creating new passwords
new_secure_algoSecurePasswordKdfAlgoThe KDF algorithm for telegram passport
secure_randombytesSecure random string
pending_reset_dateflags.5?intThe 2FA password will be automatically removed at this date, unless the user cancels the operation
-

Type

-

account.Password

-

Related pages

-

Telegram Passport Manual

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

-

Pattern matching

-

Some methods require the client to verify if the data obtained from an external source matches a certain pattern.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.passwordInputSettings b/data/core.telegram.org/constructor/account.passwordInputSettings deleted file mode 100644 index a0f05063c4..0000000000 --- a/data/core.telegram.org/constructor/account.passwordInputSettings +++ /dev/null @@ -1,176 +0,0 @@ - - - - - account.passwordInputSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.passwordInputSettings

- -

Settings for setting up a new password

-

- -
-
account.passwordInputSettings#c23727c9 flags:# new_algo:flags.0?PasswordKdfAlgo new_password_hash:flags.0?bytes hint:flags.0?string email:flags.1?string new_secure_settings:flags.2?SecureSecretSettings = account.PasswordInputSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
new_algoflags.0?PasswordKdfAlgoThe SRP algorithm to use
new_password_hashflags.0?bytesThe computed password hash
hintflags.0?stringText hint for the password
emailflags.1?stringPassword recovery email
new_secure_settingsflags.2?SecureSecretSettingsTelegram passport settings
-

Type

-

account.PasswordInputSettings

-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.passwordSettings b/data/core.telegram.org/constructor/account.passwordSettings deleted file mode 100644 index 195be40875..0000000000 --- a/data/core.telegram.org/constructor/account.passwordSettings +++ /dev/null @@ -1,161 +0,0 @@ - - - - - account.passwordSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.passwordSettings

- -

Private info associated to the password info (recovery email, telegram passport info & so on)

-

- -
-
account.passwordSettings#9a5c33e5 flags:# email:flags.0?string secure_settings:flags.1?SecureSecretSettings = account.PasswordSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
emailflags.0?string2FA Recovery email
secure_settingsflags.1?SecureSecretSettingsTelegram passport settings
-

Type

-

account.PasswordSettings

-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.privacyRules b/data/core.telegram.org/constructor/account.privacyRules deleted file mode 100644 index 46337ebbae..0000000000 --- a/data/core.telegram.org/constructor/account.privacyRules +++ /dev/null @@ -1,157 +0,0 @@ - - - - - account.privacyRules - - - - - - - - - - - - - -
- -
-
-
- -

account.privacyRules

- -

Privacy rules

-

- -
-
account.privacyRules#50a04e45 rules:Vector<PrivacyRule> chats:Vector<Chat> users:Vector<User> = account.PrivacyRules;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
rulesVector<PrivacyRule>Privacy rules
chatsVector<Chat>Chats to which the rules apply
usersVector<User>Users to which the rules apply
-

Type

-

account.PrivacyRules

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.resetPasswordFailedWait b/data/core.telegram.org/constructor/account.resetPasswordFailedWait deleted file mode 100644 index 4a83d90f5d..0000000000 --- a/data/core.telegram.org/constructor/account.resetPasswordFailedWait +++ /dev/null @@ -1,147 +0,0 @@ - - - - - account.resetPasswordFailedWait - - - - - - - - - - - - - -
- -
-
-
- -

account.resetPasswordFailedWait

- -

You recently requested a password reset that was canceled, please wait until the specified date before requesting another reset.

-

- -
-
account.resetPasswordFailedWait#e3779861 retry_date:int = account.ResetPasswordResult;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
retry_dateintWait until this date before requesting another reset.
-

Type

-

account.ResetPasswordResult

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.resetPasswordOk b/data/core.telegram.org/constructor/account.resetPasswordOk deleted file mode 100644 index 017da1a3ab..0000000000 --- a/data/core.telegram.org/constructor/account.resetPasswordOk +++ /dev/null @@ -1,132 +0,0 @@ - - - - - account.resetPasswordOk - - - - - - - - - - - - - -
- -
-
-
- -

account.resetPasswordOk

- -

The 2FA password was reset successfully.

-

- -
-
account.resetPasswordOk#e926d63e = account.ResetPasswordResult;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

account.ResetPasswordResult

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.resetPasswordRequestedWait b/data/core.telegram.org/constructor/account.resetPasswordRequestedWait deleted file mode 100644 index 4eec3d9720..0000000000 --- a/data/core.telegram.org/constructor/account.resetPasswordRequestedWait +++ /dev/null @@ -1,147 +0,0 @@ - - - - - account.resetPasswordRequestedWait - - - - - - - - - - - - - -
- -
-
-
- -

account.resetPasswordRequestedWait

- -

You successfully requested a password reset, please wait until the specified date before finalizing the reset.

-

- -
-
account.resetPasswordRequestedWait#e9effc7d until_date:int = account.ResetPasswordResult;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
until_dateintWait until this date before finalizing the reset.
-

Type

-

account.ResetPasswordResult

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.sentChangePhoneCode b/data/core.telegram.org/constructor/account.sentChangePhoneCode deleted file mode 100644 index ff48a68f29..0000000000 --- a/data/core.telegram.org/constructor/account.sentChangePhoneCode +++ /dev/null @@ -1,161 +0,0 @@ - - - - - account.sentChangePhoneCode - - - - - - - - - - - - - -
- -
-
-
- -

account.sentChangePhoneCode

- -

Sent change phone code

-

- -
-
Constructor schema is available as of layer 50. Switch »

-

Parameters

- - - - - - - - - - - - - -
phone_code_hashstringChange phone code hash
send_call_timeoutintCall timeout
-

Type

-

account.SentChangePhoneCode

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.takeout b/data/core.telegram.org/constructor/account.takeout deleted file mode 100644 index 3f1dea5d51..0000000000 --- a/data/core.telegram.org/constructor/account.takeout +++ /dev/null @@ -1,147 +0,0 @@ - - - - - account.takeout - - - - - - - - - - - - - -
- -
-
-
- -

account.takeout

- -

Takout info

-

- -
-
account.takeout#4dba4501 id:long = account.Takeout;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idlongTakeout ID
-

Type

-

account.Takeout

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.themes b/data/core.telegram.org/constructor/account.themes deleted file mode 100644 index 08714a793a..0000000000 --- a/data/core.telegram.org/constructor/account.themes +++ /dev/null @@ -1,155 +0,0 @@ - - - - - account.themes - - - - - - - - - - - - - -
- -
-
-
- -

account.themes

- -

Installed themes

-

- -
-
account.themes#9a3d8c6d hash:long themes:Vector<Theme> = account.Themes;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
themesVector<Theme>Themes
-

Type

-

account.Themes

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.themesNotModified b/data/core.telegram.org/constructor/account.themesNotModified deleted file mode 100644 index b13593d6a7..0000000000 --- a/data/core.telegram.org/constructor/account.themesNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - account.themesNotModified - - - - - - - - - - - - - -
- -
-
-
- -

account.themesNotModified

- -

No new themes were installed

-

- -
-
account.themesNotModified#f41eb622 = account.Themes;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

account.Themes

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.tmpPassword b/data/core.telegram.org/constructor/account.tmpPassword deleted file mode 100644 index 02fea03f7f..0000000000 --- a/data/core.telegram.org/constructor/account.tmpPassword +++ /dev/null @@ -1,152 +0,0 @@ - - - - - account.tmpPassword - - - - - - - - - - - - - -
- -
-
-
- -

account.tmpPassword

- -

Temporary payment password

-

- -
-
account.tmpPassword#db64fd34 tmp_password:bytes valid_until:int = account.TmpPassword;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
tmp_passwordbytesTemporary password
valid_untilintValidity period
-

Type

-

account.TmpPassword

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.wallPapers b/data/core.telegram.org/constructor/account.wallPapers deleted file mode 100644 index 8eb2dd9d90..0000000000 --- a/data/core.telegram.org/constructor/account.wallPapers +++ /dev/null @@ -1,155 +0,0 @@ - - - - - account.wallPapers - - - - - - - - - - - - - -
- -
-
-
- -

account.wallPapers

- -

Installed wallpapers

-

- -
-
account.wallPapers#cdc3858c hash:long wallpapers:Vector<WallPaper> = account.WallPapers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
wallpapersVector<WallPaper>Wallpapers
-

Type

-

account.WallPapers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.wallPapersNotModified b/data/core.telegram.org/constructor/account.wallPapersNotModified deleted file mode 100644 index 47da3801ad..0000000000 --- a/data/core.telegram.org/constructor/account.wallPapersNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - account.wallPapersNotModified - - - - - - - - - - - - - -
- -
-
-
- -

account.wallPapersNotModified

- -

No new wallpapers were found

-

- -
-
account.wallPapersNotModified#1c199183 = account.WallPapers;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

account.WallPapers

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/account.webAuthorizations b/data/core.telegram.org/constructor/account.webAuthorizations deleted file mode 100644 index cb093d4cd7..0000000000 --- a/data/core.telegram.org/constructor/account.webAuthorizations +++ /dev/null @@ -1,152 +0,0 @@ - - - - - account.webAuthorizations - - - - - - - - - - - - - -
- -
-
-
- -

account.webAuthorizations

- -

Web authorizations

-

- -
-
account.webAuthorizations#ed56c9fc authorizations:Vector<WebAuthorization> users:Vector<User> = account.WebAuthorizations;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
authorizationsVector<WebAuthorization>Web authorization list
usersVector<User>Users
-

Type

-

account.WebAuthorizations

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/accountDaysTTL.html b/data/core.telegram.org/constructor/accountDaysTTL.html deleted file mode 100644 index c0ef3668e3..0000000000 --- a/data/core.telegram.org/constructor/accountDaysTTL.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - accountDaysTTL - - - - - - - - - - - - - -
- -
-
-
- -

accountDaysTTL

- -

Time to live in days of the current account

-

- -
-
accountDaysTTL#b8d0afdf days:int = AccountDaysTTL;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
daysintThis account will self-destruct in the specified number of days
-

Type

-

AccountDaysTTL

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.authorizationSignUpRequired b/data/core.telegram.org/constructor/auth.authorizationSignUpRequired deleted file mode 100644 index d66bde469d..0000000000 --- a/data/core.telegram.org/constructor/auth.authorizationSignUpRequired +++ /dev/null @@ -1,155 +0,0 @@ - - - - - auth.authorizationSignUpRequired - - - - - - - - - - - - - -
- -
-
-
- -

auth.authorizationSignUpRequired

- -

An account with this phone number doesn't exist on telegram: the user has to enter basic information and sign up

-

- -
-
auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
terms_of_serviceflags.0?help.TermsOfServiceTelegram's terms of service: the user must read and accept the terms of service before signing up to telegram
-

Type

-

auth.Authorization

-

Related pages

-

User Authorization

-

How to register a user's phone to start using the API.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.codeTypeCall b/data/core.telegram.org/constructor/auth.codeTypeCall deleted file mode 100644 index bceaa717e7..0000000000 --- a/data/core.telegram.org/constructor/auth.codeTypeCall +++ /dev/null @@ -1,132 +0,0 @@ - - - - - auth.codeTypeCall - - - - - - - - - - - - - -
- -
-
-
- -

auth.codeTypeCall

- -

Type of verification code that will be sent next if you call the resendCode method: SMS code

-

- -
-
auth.codeTypeCall#741cd3e3 = auth.CodeType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

auth.CodeType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.codeTypeFlashCall b/data/core.telegram.org/constructor/auth.codeTypeFlashCall deleted file mode 100644 index 9a3b9150f6..0000000000 --- a/data/core.telegram.org/constructor/auth.codeTypeFlashCall +++ /dev/null @@ -1,132 +0,0 @@ - - - - - auth.codeTypeFlashCall - - - - - - - - - - - - - -
- -
-
-
- -

auth.codeTypeFlashCall

- -

Type of verification code that will be sent next if you call the resendCode method: SMS code

-

- -
-
auth.codeTypeFlashCall#226ccefb = auth.CodeType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

auth.CodeType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.codeTypeSms b/data/core.telegram.org/constructor/auth.codeTypeSms deleted file mode 100644 index 4929e6b1f8..0000000000 --- a/data/core.telegram.org/constructor/auth.codeTypeSms +++ /dev/null @@ -1,132 +0,0 @@ - - - - - auth.codeTypeSms - - - - - - - - - - - - - -
- -
-
-
- -

auth.codeTypeSms

- -

Type of verification code that will be sent next if you call the resendCode method: SMS code

-

- -
-
auth.codeTypeSms#72a3158c = auth.CodeType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

auth.CodeType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.exportedAuthorization b/data/core.telegram.org/constructor/auth.exportedAuthorization deleted file mode 100644 index 9e01321cea..0000000000 --- a/data/core.telegram.org/constructor/auth.exportedAuthorization +++ /dev/null @@ -1,152 +0,0 @@ - - - - - auth.exportedAuthorization - - - - - - - - - - - - - -
- -
-
-
- -

auth.exportedAuthorization

- -

Data for copying of authorization between data centres.

-

- -
-
auth.exportedAuthorization#b434e2b8 id:long bytes:bytes = auth.ExportedAuthorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongcurrent user identifier
bytesbytesauthorizes key
-

Type

-

auth.ExportedAuthorization

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.loginToken b/data/core.telegram.org/constructor/auth.loginToken deleted file mode 100644 index c487be56f4..0000000000 --- a/data/core.telegram.org/constructor/auth.loginToken +++ /dev/null @@ -1,155 +0,0 @@ - - - - - auth.loginToken - - - - - - - - - - - - - -
- -
-
-
- -

auth.loginToken

- -

Login token (for QR code login)

-

- -
-
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
expiresintExpiry date of QR code
tokenbytesToken to render in QR code
-

Type

-

auth.LoginToken

-

Related pages

-

Login via QR code

-

QR code login flow

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.loginTokenMigrateTo b/data/core.telegram.org/constructor/auth.loginTokenMigrateTo deleted file mode 100644 index 64b21065c3..0000000000 --- a/data/core.telegram.org/constructor/auth.loginTokenMigrateTo +++ /dev/null @@ -1,152 +0,0 @@ - - - - - auth.loginTokenMigrateTo - - - - - - - - - - - - - -
- -
-
-
- -

auth.loginTokenMigrateTo

- -

Repeat the query to the specified DC

-

- -
-
auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
dc_idintDC ID
tokenbytesToken to use for login
-

Type

-

auth.LoginToken

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.passwordRecovery b/data/core.telegram.org/constructor/auth.passwordRecovery deleted file mode 100644 index be4437c0a7..0000000000 --- a/data/core.telegram.org/constructor/auth.passwordRecovery +++ /dev/null @@ -1,152 +0,0 @@ - - - - - auth.passwordRecovery - - - - - - - - - - - - - -
- -
-
-
- -

auth.passwordRecovery

- -

Recovery info of a 2FA password, only for accounts with a recovery email configured.

-

- -
-
auth.passwordRecovery#137948a5 email_pattern:string = auth.PasswordRecovery;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
email_patternstringThe email to which the recovery code was sent must match this pattern.
-

Type

-

auth.PasswordRecovery

-

Related pages

-

Pattern matching

-

Some methods require the client to verify if the data obtained from an external source matches a certain pattern.

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.sentAppCode b/data/core.telegram.org/constructor/auth.sentAppCode deleted file mode 100644 index 2c38b96ecc..0000000000 --- a/data/core.telegram.org/constructor/auth.sentAppCode +++ /dev/null @@ -1,163 +0,0 @@ - - - - - auth.sentAppCode - - - - - - - - - - - - - -
- -
-
-
- -

auth.sentAppCode

- -

Contains info on a confirmation code message sent via Telegram.

-

You can force resending the message via SMS by invoking the method auth.sendSms.

-

- -
-
Constructor schema is available as of layer 50. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_registeredBoolThe given number corresponds to a registered Telegram user
phone_code_hashstringMessage identifier
send_call_timeoutintDelay in seconds before calling auth.sendCall
is_passwordBoolThe sent code is a text password
-

Type

-

auth.SentCode

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.sentCode b/data/core.telegram.org/constructor/auth.sentCode deleted file mode 100644 index 53413116fa..0000000000 --- a/data/core.telegram.org/constructor/auth.sentCode +++ /dev/null @@ -1,172 +0,0 @@ - - - - - auth.sentCode - - - - - - - - - - - - - -
- -
-
-
- -

auth.sentCode

- -

Contains info about a sent verification code.

-

- -
-
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
typeauth.SentCodeTypePhone code type
phone_code_hashstringPhone code hash, to be stored and later re-used with auth.signIn
next_typeflags.1?auth.CodeTypePhone code type that will be sent next, if the phone code is not received within timeout seconds: to send it use auth.resendCode
timeoutflags.2?intTimeout for reception of the phone code
-

Type

-

auth.SentCode

-

Related pages

-

auth.signIn

-

Signs in a user with a validated phone number.

-

auth.resendCode

-

Resend the login code via another medium, the phone code type is determined by the return value of the previous auth.sendCode/auth.resendCode: see login for more info.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.sentCodeTypeApp b/data/core.telegram.org/constructor/auth.sentCodeTypeApp deleted file mode 100644 index cacd6caff5..0000000000 --- a/data/core.telegram.org/constructor/auth.sentCodeTypeApp +++ /dev/null @@ -1,147 +0,0 @@ - - - - - auth.sentCodeTypeApp - - - - - - - - - - - - - -
- -
-
-
- -

auth.sentCodeTypeApp

- -

The code was sent through the telegram app

-

- -
-
auth.sentCodeTypeApp#3dbb5986 length:int = auth.SentCodeType;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
lengthintLength of the code in bytes
-

Type

-

auth.SentCodeType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.sentCodeTypeFlashCall b/data/core.telegram.org/constructor/auth.sentCodeTypeFlashCall deleted file mode 100644 index 0ad15e1f94..0000000000 --- a/data/core.telegram.org/constructor/auth.sentCodeTypeFlashCall +++ /dev/null @@ -1,150 +0,0 @@ - - - - - auth.sentCodeTypeFlashCall - - - - - - - - - - - - - -
- -
-
-
- -

auth.sentCodeTypeFlashCall

- -

The code will be sent via a flash phone call, that will be closed immediately. The phone code will then be the phone number itself, just make sure that the phone number matches the specified pattern.

-

- -
-
auth.sentCodeTypeFlashCall#ab03c6d9 pattern:string = auth.SentCodeType;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
patternstringpattern to match
-

Type

-

auth.SentCodeType

-

Related pages

-

Pattern matching

-

Some methods require the client to verify if the data obtained from an external source matches a certain pattern.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/auth.sentCodeTypeSms b/data/core.telegram.org/constructor/auth.sentCodeTypeSms deleted file mode 100644 index e6519bbea3..0000000000 --- a/data/core.telegram.org/constructor/auth.sentCodeTypeSms +++ /dev/null @@ -1,147 +0,0 @@ - - - - - auth.sentCodeTypeSms - - - - - - - - - - - - - -
- -
-
-
- -

auth.sentCodeTypeSms

- -

The code was sent via SMS

-

- -
-
auth.sentCodeTypeSms#c000bba2 length:int = auth.SentCodeType;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
lengthintLength of the code in bytes
-

Type

-

auth.SentCodeType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/authorization.html b/data/core.telegram.org/constructor/authorization.html deleted file mode 100644 index 7b703daa9e..0000000000 --- a/data/core.telegram.org/constructor/authorization.html +++ /dev/null @@ -1,225 +0,0 @@ - - - - - authorization - - - - - - - - - - - - - -
- -
-
-
- -

authorization

- -

Logged-in session

-

- -
-
authorization#ad01d61d flags:# current:flags.0?true official_app:flags.1?true password_pending:flags.2?true encrypted_requests_disabled:flags.3?true call_requests_disabled:flags.4?true hash:long device_model:string platform:string system_version:string api_id:int app_name:string app_version:string date_created:int date_active:int ip:string country:string region:string = Authorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
currentflags.0?trueWhether this is the current session
official_appflags.1?trueWhether the session is from an official app
password_pendingflags.2?trueWhether the session is still waiting for a 2FA password
hashlongIdentifier
device_modelstringDevice model
platformstringPlatform
system_versionstringSystem version
api_idintAPI ID
app_namestringApp name
app_versionstringApp version
date_createdintWhen was the session created
date_activeintWhen was the session last active
ipstringLast known IP
countrystringCountry determined from IP
regionstringRegion determined from IP
-

Type

-

Authorization

-

Related pages

-

Creating your Telegram Application

-

How to get your application identifier and create a new Telegram app.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/autoDownloadSettings.html b/data/core.telegram.org/constructor/autoDownloadSettings.html deleted file mode 100644 index b5e409b811..0000000000 --- a/data/core.telegram.org/constructor/autoDownloadSettings.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - autoDownloadSettings - - - - - - - - - - - - - -
- -
-
-
- -

autoDownloadSettings

- -

Autodownload settings

-

- -
-
autoDownloadSettings#e04232f3 flags:# disabled:flags.0?true video_preload_large:flags.1?true audio_preload_next:flags.2?true phonecalls_less_data:flags.3?true photo_size_max:int video_size_max:int file_size_max:int video_upload_maxbitrate:int = AutoDownloadSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
disabledflags.0?trueDisable automatic media downloads?
video_preload_largeflags.1?trueWhether to preload the first seconds of videos larger than the specified limit
audio_preload_nextflags.2?trueWhether to preload the next audio track when you're listening to music
phonecalls_less_dataflags.3?trueWhether to enable data saving mode in phone calls
photo_size_maxintMaximum size of photos to preload
video_size_maxintMaximum size of videos to preload
file_size_maxintMaximum size of other files to preload
video_upload_maxbitrateintMaximum suggested bitrate for uploading videos
-

Type

-

AutoDownloadSettings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/bankCardOpenUrl.html b/data/core.telegram.org/constructor/bankCardOpenUrl.html deleted file mode 100644 index 131cda896e..0000000000 --- a/data/core.telegram.org/constructor/bankCardOpenUrl.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - bankCardOpenUrl - - - - - - - - - - - - - -
- -
-
-
- -

bankCardOpenUrl

- -

Credit card info URL provided by the bank

-

- -
-
bankCardOpenUrl#f568028a url:string name:string = BankCardOpenUrl;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringInfo URL
namestringBank name
-

Type

-

BankCardOpenUrl

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/baseThemeArctic.html b/data/core.telegram.org/constructor/baseThemeArctic.html deleted file mode 100644 index 4fa0e7d848..0000000000 --- a/data/core.telegram.org/constructor/baseThemeArctic.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - baseThemeArctic - - - - - - - - - - - - - -
- -
-
-
- -

baseThemeArctic

- -

Arctic theme

-

- -
-
baseThemeArctic#5b11125a = BaseTheme;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

BaseTheme

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/baseThemeClassic.html b/data/core.telegram.org/constructor/baseThemeClassic.html deleted file mode 100644 index 2e602c05e4..0000000000 --- a/data/core.telegram.org/constructor/baseThemeClassic.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - baseThemeClassic - - - - - - - - - - - - - -
- -
-
-
- -

baseThemeClassic

- -

Classic theme

-

- -
-
baseThemeClassic#c3a12462 = BaseTheme;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

BaseTheme

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/baseThemeDay.html b/data/core.telegram.org/constructor/baseThemeDay.html deleted file mode 100644 index 7fa0ff7124..0000000000 --- a/data/core.telegram.org/constructor/baseThemeDay.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - baseThemeDay - - - - - - - - - - - - - -
- -
-
-
- -

baseThemeDay

- -

Day theme

-

- -
-
baseThemeDay#fbd81688 = BaseTheme;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

BaseTheme

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/baseThemeNight.html b/data/core.telegram.org/constructor/baseThemeNight.html deleted file mode 100644 index bbf39cc335..0000000000 --- a/data/core.telegram.org/constructor/baseThemeNight.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - baseThemeNight - - - - - - - - - - - - - -
- -
-
-
- -

baseThemeNight

- -

Night theme

-

- -
-
baseThemeNight#b7b31ea8 = BaseTheme;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

BaseTheme

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/baseThemeTinted.html b/data/core.telegram.org/constructor/baseThemeTinted.html deleted file mode 100644 index bc4dea5385..0000000000 --- a/data/core.telegram.org/constructor/baseThemeTinted.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - baseThemeTinted - - - - - - - - - - - - - -
- -
-
-
- -

baseThemeTinted

- -

Tinted theme

-

- -
-
baseThemeTinted#6d5f77ee = BaseTheme;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

BaseTheme

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/boolFalse.html b/data/core.telegram.org/constructor/boolFalse.html deleted file mode 100644 index 316e0e24f5..0000000000 --- a/data/core.telegram.org/constructor/boolFalse.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - boolFalse - - - - - - - - - - - - - -
- -
-
-
- -

boolFalse

- -

Constructor may be interpreted as a booleanfalse value.

-

- -
-
boolFalse#bc799737 = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/boolTrue.html b/data/core.telegram.org/constructor/boolTrue.html deleted file mode 100644 index 76b69b97b1..0000000000 --- a/data/core.telegram.org/constructor/boolTrue.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - boolTrue - - - - - - - - - - - - - -
- -
-
-
- -

boolTrue

- -

The constructor can be interpreted as a booleantrue value.

-

- -
-
boolTrue#997275b5 = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botCommand.html b/data/core.telegram.org/constructor/botCommand.html deleted file mode 100644 index fa16707733..0000000000 --- a/data/core.telegram.org/constructor/botCommand.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - botCommand - - - - - - - - - - - - - -
- -
-
-
- -

botCommand

- -

Describes a bot command that can be used in a chat

-

- -
-
botCommand#c27ac8c7 command:string description:string = BotCommand;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
commandstring/command name
descriptionstringDescription of the command
-

Type

-

BotCommand

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botCommandScopeChatAdmins.html b/data/core.telegram.org/constructor/botCommandScopeChatAdmins.html deleted file mode 100644 index d2304a64f2..0000000000 --- a/data/core.telegram.org/constructor/botCommandScopeChatAdmins.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - botCommandScopeChatAdmins - - - - - - - - - - - - - -
- -
-
-
- -

botCommandScopeChatAdmins

- -

The specified bot commands will be valid only for chat administrators, in all groups and supergroups.

-

- -
-
botCommandScopeChatAdmins#b9aa606a = BotCommandScope;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

BotCommandScope

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botCommandScopeChats.html b/data/core.telegram.org/constructor/botCommandScopeChats.html deleted file mode 100644 index bf42ab91e4..0000000000 --- a/data/core.telegram.org/constructor/botCommandScopeChats.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - botCommandScopeChats - - - - - - - - - - - - - -
- -
-
-
- -

botCommandScopeChats

- -

The specified bot commands will be valid in all groups and supergroups.

-

- -
-
botCommandScopeChats#6fe1a881 = BotCommandScope;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

BotCommandScope

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botCommandScopeDefault.html b/data/core.telegram.org/constructor/botCommandScopeDefault.html deleted file mode 100644 index 4316af87eb..0000000000 --- a/data/core.telegram.org/constructor/botCommandScopeDefault.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - botCommandScopeDefault - - - - - - - - - - - - - -
- -
-
-
- -

botCommandScopeDefault

- -

The commands will be valid in all dialogs

-

- -
-
botCommandScopeDefault#2f6cb2ab = BotCommandScope;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

BotCommandScope

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botCommandScopePeer.html b/data/core.telegram.org/constructor/botCommandScopePeer.html deleted file mode 100644 index 19416fbb6f..0000000000 --- a/data/core.telegram.org/constructor/botCommandScopePeer.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - botCommandScopePeer - - - - - - - - - - - - - -
- -
-
-
- -

botCommandScopePeer

- -

The specified bot commands will be valid only in a specific dialog.

-

- -
-
botCommandScopePeer#db9d897d peer:InputPeer = BotCommandScope;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe dialog
-

Type

-

BotCommandScope

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botCommandScopePeerAdmins.html b/data/core.telegram.org/constructor/botCommandScopePeerAdmins.html deleted file mode 100644 index 09ed3db8d4..0000000000 --- a/data/core.telegram.org/constructor/botCommandScopePeerAdmins.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - botCommandScopePeerAdmins - - - - - - - - - - - - - -
- -
-
-
- -

botCommandScopePeerAdmins

- -

The specified bot commands will be valid for all admins of the specified group or supergroup.

-

- -
-
botCommandScopePeerAdmins#3fd863d1 peer:InputPeer = BotCommandScope;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat
-

Type

-

BotCommandScope

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botCommandScopePeerUser.html b/data/core.telegram.org/constructor/botCommandScopePeerUser.html deleted file mode 100644 index b9e1f1945f..0000000000 --- a/data/core.telegram.org/constructor/botCommandScopePeerUser.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - botCommandScopePeerUser - - - - - - - - - - - - - -
- -
-
-
- -

botCommandScopePeerUser

- -

The specified bot commands will be valid only for a specific user in the specified group or supergroup.

-

- -
-
botCommandScopePeerUser#a1321f3 peer:InputPeer user_id:InputUser = BotCommandScope;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat
user_idInputUserThe user
-

Type

-

BotCommandScope

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botCommandScopeUsers.html b/data/core.telegram.org/constructor/botCommandScopeUsers.html deleted file mode 100644 index ff03cb3e3b..0000000000 --- a/data/core.telegram.org/constructor/botCommandScopeUsers.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - botCommandScopeUsers - - - - - - - - - - - - - -
- -
-
-
- -

botCommandScopeUsers

- -

The specified bot commands will only be valid in all private chats with users.

-

- -
-
botCommandScopeUsers#3c4f04d8 = BotCommandScope;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

BotCommandScope

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botInfo.html b/data/core.telegram.org/constructor/botInfo.html deleted file mode 100644 index 8a8fa43226..0000000000 --- a/data/core.telegram.org/constructor/botInfo.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - botInfo - - - - - - - - - - - - - -
- -
-
-
- -

botInfo

- -

Info about bots (available bot commands, etc)

-

- -
-
botInfo#1b74b335 user_id:long description:string commands:Vector<BotCommand> = BotInfo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongID of the bot
descriptionstringDescription of the bot
commandsVector<BotCommand>Bot commands that can be used in the chat
-

Type

-

BotInfo

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botInlineMediaResult.html b/data/core.telegram.org/constructor/botInlineMediaResult.html deleted file mode 100644 index 5543f348d4..0000000000 --- a/data/core.telegram.org/constructor/botInlineMediaResult.html +++ /dev/null @@ -1,186 +0,0 @@ - - - - - botInlineMediaResult - - - - - - - - - - - - - -
- -
-
-
- -

botInlineMediaResult

- -

Media result

-

- -
-
botInlineMediaResult#17db940b flags:# id:string type:string photo:flags.0?Photo document:flags.1?Document title:flags.2?string description:flags.3?string send_message:BotInlineMessage = BotInlineResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idstringResult ID
typestringResult type (see bot API docs)
photoflags.0?PhotoIf type is photo, the photo to send
documentflags.1?DocumentIf type is document, the document to send
titleflags.2?stringResult title
descriptionflags.3?stringDescription
send_messageBotInlineMessageDepending on the type and on the constructor, contains the caption of the media or the content of the message to be sent instead of the media
-

Type

-

BotInlineResult

-

Related pages

-

Telegram Bot API

-

BotInlineMessage

-

Inline message

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botInlineMessageMediaAuto.html b/data/core.telegram.org/constructor/botInlineMessageMediaAuto.html deleted file mode 100644 index fafae10d6a..0000000000 --- a/data/core.telegram.org/constructor/botInlineMessageMediaAuto.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - botInlineMessageMediaAuto - - - - - - - - - - - - - -
- -
-
-
- -

botInlineMessageMediaAuto

- -

Send whatever media is attached to the botInlineMediaResult

-

- -
-
botInlineMessageMediaAuto#764cf810 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
messagestringCaption
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

BotInlineMessage

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

-

botInlineMediaResult

-

Media result

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botInlineMessageMediaContact.html b/data/core.telegram.org/constructor/botInlineMessageMediaContact.html deleted file mode 100644 index 401a5f6d9f..0000000000 --- a/data/core.telegram.org/constructor/botInlineMessageMediaContact.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - botInlineMessageMediaContact - - - - - - - - - - - - - -
- -
-
-
- -

botInlineMessageMediaContact

- -

Send a contact

-

- -
-
botInlineMessageMediaContact#18d1cdc2 flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
phone_numberstringPhone number
first_namestringFirst name
last_namestringLast name
vcardstringVCard info
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

BotInlineMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botInlineMessageMediaGeo.html b/data/core.telegram.org/constructor/botInlineMessageMediaGeo.html deleted file mode 100644 index d106e79ba5..0000000000 --- a/data/core.telegram.org/constructor/botInlineMessageMediaGeo.html +++ /dev/null @@ -1,175 +0,0 @@ - - - - - botInlineMessageMediaGeo - - - - - - - - - - - - - -
- -
-
-
- -

botInlineMessageMediaGeo

- -

Send a geolocation

-

- -
-
botInlineMessageMediaGeo#51846fd flags:# geo:GeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
geoGeoPointGeolocation
headingflags.0?intFor live locations, a direction in which the location moves, in degrees; 1-360.
periodflags.1?intValidity period
proximity_notification_radiusflags.3?intFor live locations, a maximum distance to another chat member for proximity alerts, in meters (0-100000).
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

BotInlineMessage

-

Related pages

-

Live geolocation

-

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botInlineMessageMediaInvoice.html b/data/core.telegram.org/constructor/botInlineMessageMediaInvoice.html deleted file mode 100644 index 7fdade1179..0000000000 --- a/data/core.telegram.org/constructor/botInlineMessageMediaInvoice.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - botInlineMessageMediaInvoice - - - - - - - - - - - - - -
- -
-
-
- -

botInlineMessageMediaInvoice

- -

Send an invoice

-

- -
-
botInlineMessageMediaInvoice#354a9b09 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument currency:string total_amount:long reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
shipping_address_requestedflags.1?trueSet this flag if you require the user's shipping address to complete the order
testflags.3?trueTest invoice
titlestringProduct name, 1-32 characters
descriptionstringProduct description, 1-255 characters
photoflags.0?WebDocumentProduct photo
currencystringThree-letter ISO 4217 currency code
total_amountlongTotal price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

BotInlineMessage

-

Related pages

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botInlineMessageMediaVenue.html b/data/core.telegram.org/constructor/botInlineMessageMediaVenue.html deleted file mode 100644 index 9f6a86b39f..0000000000 --- a/data/core.telegram.org/constructor/botInlineMessageMediaVenue.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - botInlineMessageMediaVenue - - - - - - - - - - - - - -
- -
-
-
- -

botInlineMessageMediaVenue

- -

Send a venue

-

- -
-
botInlineMessageMediaVenue#8a86659c flags:# geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
geoGeoPointGeolocation of venue
titlestringVenue name
addressstringAddress
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
venue_typestringVenue type in the provider's database
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

BotInlineMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botInlineMessageText.html b/data/core.telegram.org/constructor/botInlineMessageText.html deleted file mode 100644 index 9fb7d1d5aa..0000000000 --- a/data/core.telegram.org/constructor/botInlineMessageText.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - botInlineMessageText - - - - - - - - - - - - - -
- -
-
-
- -

botInlineMessageText

- -

Send a simple text message

-

- -
-
botInlineMessageText#8c7f65e2 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.0?trueDisable webpage preview
messagestringThe message
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

BotInlineMessage

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/botInlineResult.html b/data/core.telegram.org/constructor/botInlineResult.html deleted file mode 100644 index fc0c46a83b..0000000000 --- a/data/core.telegram.org/constructor/botInlineResult.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - botInlineResult - - - - - - - - - - - - - -
- -
-
-
- -

botInlineResult

- -

Generic result

-

- -
-
botInlineResult#11965f3a flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?WebDocument content:flags.5?WebDocument send_message:BotInlineMessage = BotInlineResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idstringResult ID
typestringResult type (see bot API docs)
titleflags.1?stringResult title
descriptionflags.2?stringResult description
urlflags.3?stringURL of article or webpage
thumbflags.4?WebDocumentThumbnail for the result
contentflags.5?WebDocumentContent of the result
send_messageBotInlineMessageMessage to send
-

Type

-

BotInlineResult

-

Related pages

-

Telegram Bot API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/cdnConfig.html b/data/core.telegram.org/constructor/cdnConfig.html deleted file mode 100644 index 1157b7340e..0000000000 --- a/data/core.telegram.org/constructor/cdnConfig.html +++ /dev/null @@ -1,149 +0,0 @@ - - - - - cdnConfig - - - - - - - - - - - - - -
- -
-
-
- -

cdnConfig

- -

Configuration for CDN file downloads.

-

- -
-
cdnConfig#5725e40a public_keys:Vector<CdnPublicKey> = CdnConfig;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
public_keysVector<CdnPublicKey>Vector of public keys to use only during handshakes to CDN DCs.
-

Type

-

CdnConfig

-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/cdnPublicKey.html b/data/core.telegram.org/constructor/cdnPublicKey.html deleted file mode 100644 index d6eaa0e16a..0000000000 --- a/data/core.telegram.org/constructor/cdnPublicKey.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - cdnPublicKey - - - - - - - - - - - - - -
- -
-
-
- -

cdnPublicKey

- -

Public key to use only during handshakes to CDN DCs.

-

- -
-
cdnPublicKey#c982eaba dc_id:int public_key:string = CdnPublicKey;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
dc_idintCDN DC ID
public_keystringRSA public key
-

Type

-

CdnPublicKey

-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channel.html b/data/core.telegram.org/constructor/channel.html deleted file mode 100644 index 73ec97d243..0000000000 --- a/data/core.telegram.org/constructor/channel.html +++ /dev/null @@ -1,289 +0,0 @@ - - - - - channel - - - - - - - - - - - - - -
- -
-
-
- -

channel

- -

Channel/supergroup info

-

- -
-
channel#8261ac61 flags:# creator:flags.0?true left:flags.2?true broadcast:flags.5?true verified:flags.7?true megagroup:flags.8?true restricted:flags.9?true signatures:flags.11?true min:flags.12?true scam:flags.19?true has_link:flags.20?true has_geo:flags.21?true slowmode_enabled:flags.22?true call_active:flags.23?true call_not_empty:flags.24?true fake:flags.25?true gigagroup:flags.26?true noforwards:flags.27?true id:long access_hash:flags.13?long title:string username:flags.6?string photo:ChatPhoto date:int restriction_reason:flags.9?Vector<RestrictionReason> admin_rights:flags.14?ChatAdminRights banned_rights:flags.15?ChatBannedRights default_banned_rights:flags.18?ChatBannedRights participants_count:flags.17?int = Chat;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
creatorflags.0?trueWhether the current user is the creator of this channel
leftflags.2?trueWhether the current user has left this channel
broadcastflags.5?trueIs this a channel?
verifiedflags.7?trueIs this channel verified by telegram?
megagroupflags.8?trueIs this a supergroup?
restrictedflags.9?trueWhether viewing/writing in this channel for a reason (see restriction_reason
signaturesflags.11?trueWhether signatures are enabled (channels)
minflags.12?trueSee min
scamflags.19?trueThis channel/supergroup is probably a scam
has_linkflags.20?trueWhether this channel has a private join link
has_geoflags.21?trueWhether this chanel has a geoposition
slowmode_enabledflags.22?trueWhether slow mode is enabled for groups to prevent flood in chat
call_activeflags.23?trueWhether a group call or livestream is currently active
call_not_emptyflags.24?trueWhether there's anyone in the group call or livestream
fakeflags.25?trueIf set, this supergroup/channel was reported by many users as a fake or scam: be careful when interacting with it.
gigagroupflags.26?trueWhether this supergroup is a gigagroup
idlongID of the channel
access_hashflags.13?longAccess hash
titlestringTitle
usernameflags.6?stringUsername
photoChatPhotoProfile photo
dateintDate when the user joined the supergroup/channel, or if the user isn't a member, its creation date
restriction_reasonflags.9?Vector<RestrictionReason>Contains the reason why access to this channel must be restricted.
admin_rightsflags.14?ChatAdminRightsAdmin rights of the user in this channel (see rights)
banned_rightsflags.15?ChatBannedRightsBanned rights of the user in this channel (see rights)
default_banned_rightsflags.18?ChatBannedRightsDefault chat rights (see rights)
participants_countflags.17?intParticipant count
-

Type

-

Chat

-

Related pages

-

Min constructors

-

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

Admin, banned, default rights

-

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEvent.html b/data/core.telegram.org/constructor/channelAdminLogEvent.html deleted file mode 100644 index 08d01a45ca..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEvent.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - channelAdminLogEvent - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEvent

- -

Admin log event

-

- -
-
channelAdminLogEvent#1fad68cd id:long date:int user_id:long action:ChannelAdminLogEventAction = ChannelAdminLogEvent;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongEvent ID
dateintDate
user_idlongUser ID
actionChannelAdminLogEventActionAction
-

Type

-

ChannelAdminLogEvent

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeAbout.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeAbout.html deleted file mode 100644 index c9fe0ac9d8..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeAbout.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionChangeAbout - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionChangeAbout

- -

The description was changed

-

- -
-
channelAdminLogEventActionChangeAbout#55188a2e prev_value:string new_value:string = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_valuestringPrevious description
new_valuestringNew description
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeHistoryTTL.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeHistoryTTL.html deleted file mode 100644 index 234d968fe8..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeHistoryTTL.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionChangeHistoryTTL - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionChangeHistoryTTL

- -

The Time-To-Live of messages in this chat was changed

-

- -
-
channelAdminLogEventActionChangeHistoryTTL#6e941a38 prev_value:int new_value:int = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_valueintPrevious value
new_valueintNew value
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html deleted file mode 100644 index d8470afca7..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionChangeLinkedChat - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionChangeLinkedChat

- -

The linked chat was changed

-

- -
-
channelAdminLogEventActionChangeLinkedChat#50c7ac8 prev_value:long new_value:long = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_valuelongPrevious linked chat
new_valuelongNew linked chat
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html deleted file mode 100644 index 827058690a..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionChangeLocation - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionChangeLocation

- -

The geogroup location was changed

-

- -
-
channelAdminLogEventActionChangeLocation#e6b76ae prev_value:ChannelLocation new_value:ChannelLocation = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_valueChannelLocationPrevious location
new_valueChannelLocationNew location
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangePhoto.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangePhoto.html deleted file mode 100644 index 305046f1b5..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionChangePhoto.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionChangePhoto - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionChangePhoto

- -

The channel/supergroup's picture was changed

-

- -
-
channelAdminLogEventActionChangePhoto#434bd2af prev_photo:Photo new_photo:Photo = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_photoPhotoPrevious picture
new_photoPhotoNew picture
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html deleted file mode 100644 index d0d6c768cf..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionChangeStickerSet - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionChangeStickerSet

- -

The supergroup's stickerset was changed

-

- -
-
channelAdminLogEventActionChangeStickerSet#b1c3caa7 prev_stickerset:InputStickerSet new_stickerset:InputStickerSet = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_stickersetInputStickerSetPrevious stickerset
new_stickersetInputStickerSetNew stickerset
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeTitle.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeTitle.html deleted file mode 100644 index f2699fa673..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeTitle.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionChangeTitle - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionChangeTitle

- -

Channel/supergroup title was changed

-

- -
-
channelAdminLogEventActionChangeTitle#e6dfb825 prev_value:string new_value:string = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_valuestringPrevious title
new_valuestringNew title
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html deleted file mode 100644 index 6c4edcbca6..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionChangeUsername - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionChangeUsername

- -

Channel/supergroup username was changed

-

- -
-
channelAdminLogEventActionChangeUsername#6a4afc38 prev_value:string new_value:string = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_valuestringOld username
new_valuestringNew username
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionDefaultBannedRights.html b/data/core.telegram.org/constructor/channelAdminLogEventActionDefaultBannedRights.html deleted file mode 100644 index 455200c451..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionDefaultBannedRights.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - channelAdminLogEventActionDefaultBannedRights - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionDefaultBannedRights

- -

The default banned rights were modified

-

- -
-
channelAdminLogEventActionDefaultBannedRights#2df5fc0a prev_banned_rights:ChatBannedRights new_banned_rights:ChatBannedRights = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_banned_rightsChatBannedRightsPrevious global banned rights
new_banned_rightsChatBannedRightsNew glboal banned rights.
-

Type

-

ChannelAdminLogEventAction

-

Related pages

-

Admin, banned, default rights

-

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionDeleteMessage.html b/data/core.telegram.org/constructor/channelAdminLogEventActionDeleteMessage.html deleted file mode 100644 index 374aec1406..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionDeleteMessage.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionDeleteMessage - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionDeleteMessage

- -

A message was deleted

-

- -
-
channelAdminLogEventActionDeleteMessage#42e047bb message:Message = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageThe message that was deleted
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionDiscardGroupCall.html b/data/core.telegram.org/constructor/channelAdminLogEventActionDiscardGroupCall.html deleted file mode 100644 index 6eb96f8f9e..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionDiscardGroupCall.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionDiscardGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionDiscardGroupCall

- -

A group call was terminated

-

- -
-
channelAdminLogEventActionDiscardGroupCall#db9f9140 call:InputGroupCall = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallThe group call that was terminated
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionEditMessage.html b/data/core.telegram.org/constructor/channelAdminLogEventActionEditMessage.html deleted file mode 100644 index e5d68279d7..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionEditMessage.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionEditMessage - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionEditMessage

- -

A message was edited

-

- -
-
channelAdminLogEventActionEditMessage#709b2405 prev_message:Message new_message:Message = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_messageMessageOld message
new_messageMessageNew message
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteDelete.html b/data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteDelete.html deleted file mode 100644 index 2d9c9fab07..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteDelete.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionExportedInviteDelete - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionExportedInviteDelete

- -

A chat invite was deleted

-

- -
-
channelAdminLogEventActionExportedInviteDelete#5a50fca4 invite:ExportedChatInvite = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
inviteExportedChatInviteThe deleted chat invite
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteEdit.html b/data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteEdit.html deleted file mode 100644 index 4f69d5962c..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteEdit.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionExportedInviteEdit - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionExportedInviteEdit

- -

A chat invite was edited

-

- -
-
channelAdminLogEventActionExportedInviteEdit#e90ebb59 prev_invite:ExportedChatInvite new_invite:ExportedChatInvite = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_inviteExportedChatInvitePrevious chat invite information
new_inviteExportedChatInviteNew chat invite information
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteRevoke.html b/data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteRevoke.html deleted file mode 100644 index ce1bc6f620..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionExportedInviteRevoke.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionExportedInviteRevoke - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionExportedInviteRevoke

- -

A specific invite link was revoked

-

- -
-
channelAdminLogEventActionExportedInviteRevoke#410a134e invite:ExportedChatInvite = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
inviteExportedChatInviteThe invite link that was revoked
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantInvite.html b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantInvite.html deleted file mode 100644 index eb0f9a9a7b..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantInvite.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionParticipantInvite - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionParticipantInvite

- -

A user was invited to the group

-

- -
-
channelAdminLogEventActionParticipantInvite#e31c34d8 participant:ChannelParticipant = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
participantChannelParticipantThe user that was invited
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html deleted file mode 100644 index 70fa7b1339..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channelAdminLogEventActionParticipantJoin - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionParticipantJoin

- -

A user has joined the group (in the case of big groups, info of the user that has joined isn't shown)

-

- -
-
channelAdminLogEventActionParticipantJoin#183040d3 = ChannelAdminLogEventAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html deleted file mode 100644 index f37e737a11..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - channelAdminLogEventActionParticipantJoinByInvite - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionParticipantJoinByInvite

- -

A user joined the supergroup/channel using a specific invite link

-

- -
-
channelAdminLogEventActionParticipantJoinByInvite#5cdada77 invite:ExportedChatInvite = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
inviteExportedChatInviteThe invite link used to join the supergroup/channel
-

Type

-

ChannelAdminLogEventAction

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantLeave.html b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantLeave.html deleted file mode 100644 index 85bda0a29b..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantLeave.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channelAdminLogEventActionParticipantLeave - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionParticipantLeave

- -

A user left the channel/supergroup (in the case of big groups, info of the user that has joined isn't shown)

-

- -
-
channelAdminLogEventActionParticipantLeave#f89777f2 = ChannelAdminLogEventAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantMute.html b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantMute.html deleted file mode 100644 index aa90572c70..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantMute.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionParticipantMute - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionParticipantMute

- -

A group call participant was muted

-

- -
-
channelAdminLogEventActionParticipantMute#f92424d2 participant:GroupCallParticipant = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
participantGroupCallParticipantThe participant that was muted
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantToggleAdmin.html b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantToggleAdmin.html deleted file mode 100644 index 7ae8d0b701..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantToggleAdmin.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - channelAdminLogEventActionParticipantToggleAdmin - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionParticipantToggleAdmin

- -

The admin rights of a user were changed

-

- -
-
channelAdminLogEventActionParticipantToggleAdmin#d5676710 prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_participantChannelParticipantPrevious admin rights
new_participantChannelParticipantNew admin rights
-

Type

-

ChannelAdminLogEventAction

-

Related pages

-

Admin, banned, default rights

-

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantToggleBan.html b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantToggleBan.html deleted file mode 100644 index 63b91a8939..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantToggleBan.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - channelAdminLogEventActionParticipantToggleBan - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionParticipantToggleBan

- -

The banned rights of a user were changed

-

- -
-
channelAdminLogEventActionParticipantToggleBan#e6d83d7e prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_participantChannelParticipantOld banned rights of user
new_participantChannelParticipantNew banned rights of user
-

Type

-

ChannelAdminLogEventAction

-

Related pages

-

Admin, banned, default rights

-

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantUnmute.html b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantUnmute.html deleted file mode 100644 index 186a54135e..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantUnmute.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionParticipantUnmute - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionParticipantUnmute

- -

A group call participant was unmuted

-

- -
-
channelAdminLogEventActionParticipantUnmute#e64429c0 participant:GroupCallParticipant = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
participantGroupCallParticipantThe participant that was unmuted
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionStartGroupCall.html b/data/core.telegram.org/constructor/channelAdminLogEventActionStartGroupCall.html deleted file mode 100644 index cbd6939d24..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionStartGroupCall.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionStartGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionStartGroupCall

- -

A group call was started

-

- -
-
channelAdminLogEventActionStartGroupCall#23209745 call:InputGroupCall = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallGroup call
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionStopPoll.html b/data/core.telegram.org/constructor/channelAdminLogEventActionStopPoll.html deleted file mode 100644 index 1be11cb8f5..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionStopPoll.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionStopPoll - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionStopPoll

- -

A poll was stopped

-

- -
-
channelAdminLogEventActionStopPoll#8f079643 message:Message = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageThe poll that was stopped
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html b/data/core.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html deleted file mode 100644 index 998071cb0a..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionToggleGroupCallSetting - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionToggleGroupCallSetting

- -

Group call settings were changed

-

- -
-
channelAdminLogEventActionToggleGroupCallSetting#56d6a247 join_muted:Bool = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
join_mutedBoolWhether all users are muted by default upon joining
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionToggleInvites.html b/data/core.telegram.org/constructor/channelAdminLogEventActionToggleInvites.html deleted file mode 100644 index ae10df6bbd..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionToggleInvites.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionToggleInvites - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionToggleInvites

- -

Invites were enabled/disabled

-

- -
-
channelAdminLogEventActionToggleInvites#1b7907ae new_value:Bool = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
new_valueBoolNew value
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionTogglePreHistoryHidden.html b/data/core.telegram.org/constructor/channelAdminLogEventActionTogglePreHistoryHidden.html deleted file mode 100644 index 7ad1f45bd9..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionTogglePreHistoryHidden.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - channelAdminLogEventActionTogglePreHistoryHidden - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionTogglePreHistoryHidden

- -

The hidden prehistory setting was changed

-

- -
-
channelAdminLogEventActionTogglePreHistoryHidden#5f5c95f1 new_value:Bool = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
new_valueBoolNew value
-

Type

-

ChannelAdminLogEventAction

-

Related pages

-

channels.togglePreHistoryHidden

-

Hide/unhide message history for new channel/supergroup users

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionToggleSignatures.html b/data/core.telegram.org/constructor/channelAdminLogEventActionToggleSignatures.html deleted file mode 100644 index 16da2eb601..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionToggleSignatures.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionToggleSignatures - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionToggleSignatures

- -

Channel signatures were enabled/disabled

-

- -
-
channelAdminLogEventActionToggleSignatures#26ae0971 new_value:Bool = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
new_valueBoolNew value
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionToggleSlowMode.html b/data/core.telegram.org/constructor/channelAdminLogEventActionToggleSlowMode.html deleted file mode 100644 index 41157ff1ab..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionToggleSlowMode.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - channelAdminLogEventActionToggleSlowMode - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionToggleSlowMode

- -

Slow mode setting for supergroups was changed

-

- -
-
channelAdminLogEventActionToggleSlowMode#53909779 prev_value:int new_value:int = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_valueintPrevious slow mode value
new_valueintNew slow mode value
-

Type

-

ChannelAdminLogEventAction

-

Related pages

-

channels.toggleSlowMode

-

Toggle supergroup slow mode: if enabled, users will only be able to send one message every seconds seconds

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventActionUpdatePinned.html b/data/core.telegram.org/constructor/channelAdminLogEventActionUpdatePinned.html deleted file mode 100644 index 00e54c411c..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventActionUpdatePinned.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionUpdatePinned - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionUpdatePinned

- -

A message was pinned

-

- -
-
channelAdminLogEventActionUpdatePinned#e9e82c18 message:Message = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageThe message that was pinned
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelAdminLogEventsFilter.html b/data/core.telegram.org/constructor/channelAdminLogEventsFilter.html deleted file mode 100644 index dd094a41a3..0000000000 --- a/data/core.telegram.org/constructor/channelAdminLogEventsFilter.html +++ /dev/null @@ -1,266 +0,0 @@ - - - - - channelAdminLogEventsFilter - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventsFilter

- -

Filter only certain admin log events

-

- -
-
channelAdminLogEventsFilter#ea107ae4 flags:# join:flags.0?true leave:flags.1?true invite:flags.2?true ban:flags.3?true unban:flags.4?true kick:flags.5?true unkick:flags.6?true promote:flags.7?true demote:flags.8?true info:flags.9?true settings:flags.10?true pinned:flags.11?true edit:flags.12?true delete:flags.13?true group_call:flags.14?true invites:flags.15?true send:flags.16?true = ChannelAdminLogEventsFilter;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
joinflags.0?trueJoin events
leaveflags.1?trueLeave events
inviteflags.2?trueInvite events
banflags.3?trueBan events
unbanflags.4?trueUnban events
kickflags.5?trueKick events
unkickflags.6?trueUnkick events
promoteflags.7?trueAdmin promotion events
demoteflags.8?trueAdmin demotion events
infoflags.9?trueInfo change events (when about, linked chat, location, photo, stickerset, title or username data of a channel gets modified)
settingsflags.10?trueSettings change events (invites, hidden prehistory, signatures, default banned rights)
pinnedflags.11?trueMessage pin events
editflags.12?trueMessage edit events
deleteflags.13?trueMessage deletion events
group_callflags.14?trueGroup call events
invitesflags.15?trueInvite events
-

Type

-

ChannelAdminLogEventsFilter

-

Related pages

-

channelAdminLogEventActionParticipantJoin

-

A user has joined the group (in the case of big groups, info of the user that has joined isn't shown)

-

channelAdminLogEventActionParticipantLeave

-

A user left the channel/supergroup (in the case of big groups, info of the user that has joined isn't shown)

-

channelAdminLogEventActionParticipantInvite

-

A user was invited to the group

-

channelAdminLogEventActionParticipantToggleBan

-

The banned rights of a user were changed

-

channelAdminLogEventActionParticipantToggleAdmin

-

The admin rights of a user were changed

-

channelAdminLogEventActionChangeAbout

-

The description was changed

-

channelAdminLogEventActionChangeLinkedChat

-

The linked chat was changed

-

channelAdminLogEventActionChangeLocation

-

The geogroup location was changed

-

channelAdminLogEventActionChangePhoto

-

The channel/supergroup's picture was changed

-

channelAdminLogEventActionChangeStickerSet

-

The supergroup's stickerset was changed

-

channelAdminLogEventActionChangeTitle

-

Channel/supergroup title was changed

-

channelAdminLogEventActionChangeUsername

-

Channel/supergroup username was changed

-

channelAdminLogEventActionToggleInvites

-

Invites were enabled/disabled

-

channelAdminLogEventActionTogglePreHistoryHidden

-

The hidden prehistory setting was changed

-

channelAdminLogEventActionToggleSignatures

-

Channel signatures were enabled/disabled

-

channelAdminLogEventActionDefaultBannedRights

-

The default banned rights were modified

-

channelAdminLogEventActionUpdatePinned

-

A message was pinned

-

channelAdminLogEventActionEditMessage

-

A message was edited

-

channelAdminLogEventActionDeleteMessage

-

A message was deleted

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelForbidden.html b/data/core.telegram.org/constructor/channelForbidden.html deleted file mode 100644 index e972d470e7..0000000000 --- a/data/core.telegram.org/constructor/channelForbidden.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - channelForbidden - - - - - - - - - - - - - -
- -
-
-
- -

channelForbidden

- -

Indicates a channel/supergroup we can't access because we were banned, or for some other reason.

-

- -
-
channelForbidden#17d493d5 flags:# broadcast:flags.5?true megagroup:flags.8?true id:long access_hash:long title:string until_date:flags.16?int = Chat;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
broadcastflags.5?trueIs this a channel
megagroupflags.8?trueIs this a supergroup
idlongChannel ID
access_hashlongAccess hash
titlestringTitle
until_dateflags.16?intThe ban is valid until the specified date
-

Type

-

Chat

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelFull.html b/data/core.telegram.org/constructor/channelFull.html deleted file mode 100644 index 54ada2ff22..0000000000 --- a/data/core.telegram.org/constructor/channelFull.html +++ /dev/null @@ -1,363 +0,0 @@ - - - - - channelFull - - - - - - - - - - - - - -
- -
-
-
- -

channelFull

- -

Full info about a channel/supergroup

-

- -
-
channelFull#e9b27a17 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector<string> groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string = ChatFull;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
can_view_participantsflags.3?trueCan we vew the participant list?
can_set_usernameflags.6?trueCan we set the channel's username?
can_set_stickersflags.7?trueCan we associate a stickerpack to the supergroup?
hidden_prehistoryflags.10?trueIs the history before we joined hidden to us?
can_set_locationflags.16?trueCan we set the geolocation of this group (for geogroups)
has_scheduledflags.19?trueWhether scheduled messages are available
can_view_statsflags.20?trueCan the user view channel/supergroup statistics
blockedflags.22?trueWhether any anonymous admin of this supergroup was blocked: if set, you won't receive messages from anonymous group admins in discussion replies via @replies
idlongID of the channel
aboutstringInfo about the channel
participants_countflags.0?intNumber of participants of the channel
admins_countflags.1?intNumber of channel admins
kicked_countflags.2?intNumber of users kicked from the channel
banned_countflags.2?intNumber of users banned from the channel
online_countflags.13?intNumber of users currently online
read_inbox_max_idintPosition up to which all incoming messages are read.
read_outbox_max_idintPosition up to which all outgoing messages are read.
unread_countintCount of unread messages
chat_photoPhotoChannel picture
notify_settingsPeerNotifySettingsNotification settings
exported_inviteflags.23?ExportedChatInviteInvite link
bot_infoVector<BotInfo>Info about bots in the channel/supergrup
migrated_from_chat_idflags.4?longThe chat ID from which this group was migrated
migrated_from_max_idflags.4?intThe message ID in the original chat at which this group was migrated
pinned_msg_idflags.5?intMessage ID of the last pinned message
stickersetflags.8?StickerSetAssociated stickerset
available_min_idflags.9?intIdentifier of a maximum unavailable message in a channel due to hidden history.
folder_idflags.11?intPeer folder ID, for more info click here
linked_chat_idflags.14?longID of the linked discussion chat for channels
locationflags.15?ChannelLocationLocation of the geogroup
slowmode_secondsflags.17?intIf specified, users in supergroups will only be able to send one message every slowmode_seconds seconds
slowmode_next_send_dateflags.18?intIndicates when the user will be allowed to send another message in the supergroup (unixdate)
stats_dcflags.12?intIf set, specifies the DC to use for fetching channel statistics
ptsintLatest PTS for this channel
callflags.21?InputGroupCallLivestream or group call information
ttl_periodflags.24?intTime-To-Live of messages in this channel or supergroup
pending_suggestionsflags.25?Vector<string>A list of suggested actions for the supergroup admin, see here for more info ».
groupcall_default_join_asflags.26?PeerWhen using phone.getGroupCallJoinAs to get a list of peers that can be used to join a group call, this field indicates the peer that should be selected by default.
theme_emoticonflags.27?stringEmoji representing a specific chat theme
-

Type

-

ChatFull

-

Related pages

-

channels.setStickers

-

Associate a stickerset to the supergroup

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

-

Discussion groups

-

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

-

Admin, banned, default rights

-

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

Pinned messages

-

Telegram allows pinning multiple messages on top of a specific chat.

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Client configuration

-

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

-

phone.getGroupCallJoinAs

-

Get a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelLocation.html b/data/core.telegram.org/constructor/channelLocation.html deleted file mode 100644 index 90a018d887..0000000000 --- a/data/core.telegram.org/constructor/channelLocation.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelLocation - - - - - - - - - - - - - -
- -
-
-
- -

channelLocation

- -

Geographical location of supergroup (geogroups)

-

- -
-
channelLocation#209b82db geo_point:GeoPoint address:string = ChannelLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
geo_pointGeoPointGeographical location of supergrup
addressstringTextual description of the address
-

Type

-

ChannelLocation

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelLocationEmpty.html b/data/core.telegram.org/constructor/channelLocationEmpty.html deleted file mode 100644 index 2483d6968d..0000000000 --- a/data/core.telegram.org/constructor/channelLocationEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channelLocationEmpty - - - - - - - - - - - - - -
- -
-
-
- -

channelLocationEmpty

- -

No location (normal supergroup)

-

- -
-
channelLocationEmpty#bfb5ad8b = ChannelLocation;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ChannelLocation

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelMessagesFilter.html b/data/core.telegram.org/constructor/channelMessagesFilter.html deleted file mode 100644 index 1e12608d09..0000000000 --- a/data/core.telegram.org/constructor/channelMessagesFilter.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - channelMessagesFilter - - - - - - - - - - - - - -
- -
-
-
- -

channelMessagesFilter

- -

Filter for getting only certain types of channel messages

-

- -
-
channelMessagesFilter#cd77d957 flags:# exclude_new_messages:flags.1?true ranges:Vector<MessageRange> = ChannelMessagesFilter;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
exclude_new_messagesflags.1?trueWhether to exclude new messages from the search
rangesVector<MessageRange>A range of messages to fetch
-

Type

-

ChannelMessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelMessagesFilterEmpty.html b/data/core.telegram.org/constructor/channelMessagesFilterEmpty.html deleted file mode 100644 index be6ba03f36..0000000000 --- a/data/core.telegram.org/constructor/channelMessagesFilterEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channelMessagesFilterEmpty - - - - - - - - - - - - - -
- -
-
-
- -

channelMessagesFilterEmpty

- -

No filter

-

- -
-
channelMessagesFilterEmpty#94d42ee7 = ChannelMessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ChannelMessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipant.html b/data/core.telegram.org/constructor/channelParticipant.html deleted file mode 100644 index 2cb702153b..0000000000 --- a/data/core.telegram.org/constructor/channelParticipant.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelParticipant - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipant

- -

Channel/supergroup participant

-

- -
-
channelParticipant#c00c07c0 user_id:long date:int = ChannelParticipant;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongPariticipant user ID
dateintDate joined
-

Type

-

ChannelParticipant

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantAdmin.html b/data/core.telegram.org/constructor/channelParticipantAdmin.html deleted file mode 100644 index 74db228270..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantAdmin.html +++ /dev/null @@ -1,190 +0,0 @@ - - - - - channelParticipantAdmin - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantAdmin

- -

Admin

-

- -
-
channelParticipantAdmin#34c3bb53 flags:# can_edit:flags.0?true self:flags.1?true user_id:long inviter_id:flags.1?long promoted_by:long date:int admin_rights:ChatAdminRights rank:flags.2?string = ChannelParticipant;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
can_editflags.0?trueCan this admin promote other admins with the same permissions?
selfflags.1?trueIs this the current user
user_idlongAdmin user ID
inviter_idflags.1?longUser that invited the admin to the channel/group
promoted_bylongUser that promoted the user to admin
dateintWhen did the user join
admin_rightsChatAdminRightsAdmin rights
rankflags.2?stringThe role (rank) of the admin in the group: just an arbitrary string, admin by default
-

Type

-

ChannelParticipant

-

Related pages

-

Admin, banned, default rights

-

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantBanned.html b/data/core.telegram.org/constructor/channelParticipantBanned.html deleted file mode 100644 index 6a5e362583..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantBanned.html +++ /dev/null @@ -1,175 +0,0 @@ - - - - - channelParticipantBanned - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantBanned

- -

Banned/kicked user

-

- -
-
channelParticipantBanned#6df8014e flags:# left:flags.0?true peer:Peer kicked_by:long date:int banned_rights:ChatBannedRights = ChannelParticipant;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
leftflags.0?trueWhether the user has left the group
peerPeerThe banned peer
kicked_bylongUser was kicked by the specified admin
dateintWhen did the user join the group
banned_rightsChatBannedRightsBanned rights
-

Type

-

ChannelParticipant

-

Related pages

-

Admin, banned, default rights

-

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantCreator.html b/data/core.telegram.org/constructor/channelParticipantCreator.html deleted file mode 100644 index d644a8b090..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantCreator.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - channelParticipantCreator - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantCreator

- -

Channel/supergroup creator

-

- -
-
channelParticipantCreator#2fe601d3 flags:# user_id:long admin_rights:ChatAdminRights rank:flags.0?string = ChannelParticipant;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
user_idlongUser ID
admin_rightsChatAdminRightsCreator admin rights
rankflags.0?stringThe role (rank) of the group creator in the group: just an arbitrary string, admin by default
-

Type

-

ChannelParticipant

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantLeft.html b/data/core.telegram.org/constructor/channelParticipantLeft.html deleted file mode 100644 index 96911d5117..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantLeft.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelParticipantLeft - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantLeft

- -

A participant that left the channel/supergroup

-

- -
-
channelParticipantLeft#1b03f006 peer:Peer = ChannelParticipant;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerThe peer that left
-

Type

-

ChannelParticipant

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantSelf.html b/data/core.telegram.org/constructor/channelParticipantSelf.html deleted file mode 100644 index 4024f25e89..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantSelf.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - channelParticipantSelf - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantSelf

- -

Myself

-

- -
-
channelParticipantSelf#28a8bc67 user_id:long inviter_id:long date:int = ChannelParticipant;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser ID
inviter_idlongUser that invited me to the channel/supergroup
dateintWhen did I join the channel/supergroup
-

Type

-

ChannelParticipant

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantsAdmins.html b/data/core.telegram.org/constructor/channelParticipantsAdmins.html deleted file mode 100644 index 62aa8fe76b..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantsAdmins.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channelParticipantsAdmins - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsAdmins

- -

Fetch only admin participants

-

- -
-
channelParticipantsAdmins#b4608969 = ChannelParticipantsFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ChannelParticipantsFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantsBanned.html b/data/core.telegram.org/constructor/channelParticipantsBanned.html deleted file mode 100644 index 26e1c21347..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantsBanned.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelParticipantsBanned - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsBanned

- -

Fetch only banned participants

-

- -
-
channelParticipantsBanned#1427a5e1 q:string = ChannelParticipantsFilter;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
qstringOptional filter for searching banned participants by name (otherwise empty)
-

Type

-

ChannelParticipantsFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantsBots.html b/data/core.telegram.org/constructor/channelParticipantsBots.html deleted file mode 100644 index 3792f73fe1..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantsBots.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channelParticipantsBots - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsBots

- -

Fetch only bot participants

-

- -
-
channelParticipantsBots#b0d1865b = ChannelParticipantsFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ChannelParticipantsFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantsContacts.html b/data/core.telegram.org/constructor/channelParticipantsContacts.html deleted file mode 100644 index 2563dfc7ee..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantsContacts.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelParticipantsContacts - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsContacts

- -

Fetch only participants that are also contacts

-

- -
-
channelParticipantsContacts#bb6ae88d q:string = ChannelParticipantsFilter;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
qstringOptional search query for searching contact participants by name
-

Type

-

ChannelParticipantsFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantsKicked.html b/data/core.telegram.org/constructor/channelParticipantsKicked.html deleted file mode 100644 index 4d7d23f656..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantsKicked.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelParticipantsKicked - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsKicked

- -

Fetch only kicked participants

-

- -
-
channelParticipantsKicked#a3b54985 q:string = ChannelParticipantsFilter;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
qstringOptional filter for searching kicked participants by name (otherwise empty)
-

Type

-

ChannelParticipantsFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantsMentions.html b/data/core.telegram.org/constructor/channelParticipantsMentions.html deleted file mode 100644 index 2ed49b9ee6..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantsMentions.html +++ /dev/null @@ -1,161 +0,0 @@ - - - - - channelParticipantsMentions - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsMentions

- -

This filter is used when looking for supergroup members to mention.
-This filter will automatically remove anonymous admins, and return even non-participant users that replied to a specific thread through the comment section of a channel.

-

- -
-
channelParticipantsMentions#e04b5ceb flags:# q:flags.0?string top_msg_id:flags.1?int = ChannelParticipantsFilter;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
qflags.0?stringFilter by user name or username
top_msg_idflags.1?intLook only for users that posted in this thread
-

Type

-

ChannelParticipantsFilter

-

Related pages

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantsRecent.html b/data/core.telegram.org/constructor/channelParticipantsRecent.html deleted file mode 100644 index 9bd1b9de9b..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantsRecent.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channelParticipantsRecent - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsRecent

- -

Fetch only recent participants

-

- -
-
channelParticipantsRecent#de3f3c79 = ChannelParticipantsFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ChannelParticipantsFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channelParticipantsSearch.html b/data/core.telegram.org/constructor/channelParticipantsSearch.html deleted file mode 100644 index 543589d2d9..0000000000 --- a/data/core.telegram.org/constructor/channelParticipantsSearch.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelParticipantsSearch - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsSearch

- -

Query participants by name

-

- -
-
channelParticipantsSearch#656ac4b q:string = ChannelParticipantsFilter;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
qstringSearch query
-

Type

-

ChannelParticipantsFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channels.adminLogResults b/data/core.telegram.org/constructor/channels.adminLogResults deleted file mode 100644 index 4e5cccbfe5..0000000000 --- a/data/core.telegram.org/constructor/channels.adminLogResults +++ /dev/null @@ -1,157 +0,0 @@ - - - - - channels.adminLogResults - - - - - - - - - - - - - -
- -
-
-
- -

channels.adminLogResults

- -

Admin log events

-

- -
-
channels.adminLogResults#ed8af74d events:Vector<ChannelAdminLogEvent> chats:Vector<Chat> users:Vector<User> = channels.AdminLogResults;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
eventsVector<ChannelAdminLogEvent>Admin log events
chatsVector<Chat>Chats mentioned in events
usersVector<User>Users mentioned in events
-

Type

-

channels.AdminLogResults

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channels.channelParticipants b/data/core.telegram.org/constructor/channels.channelParticipants deleted file mode 100644 index 5993ce565d..0000000000 --- a/data/core.telegram.org/constructor/channels.channelParticipants +++ /dev/null @@ -1,162 +0,0 @@ - - - - - channels.channelParticipants - - - - - - - - - - - - - -
- -
-
-
- -

channels.channelParticipants

- -

Represents multiple channel participants

-

- -
-
channels.channelParticipants#9ab0feaf count:int participants:Vector<ChannelParticipant> chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipants;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countintTotal number of participants that correspond to the given query
participantsVector<ChannelParticipant>Participants
chatsVector<Chat>Mentioned chats
usersVector<User>Users mentioned in participant info
-

Type

-

channels.ChannelParticipants

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/channels.channelParticipantsNotModified b/data/core.telegram.org/constructor/channels.channelParticipantsNotModified deleted file mode 100644 index 407af45564..0000000000 --- a/data/core.telegram.org/constructor/channels.channelParticipantsNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channels.channelParticipantsNotModified - - - - - - - - - - - - - -
- -
-
-
- -

channels.channelParticipantsNotModified

- -

No new participant info could be found

-

- -
-
channels.channelParticipantsNotModified#f0173fe9 = channels.ChannelParticipants;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

channels.ChannelParticipants

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chat.html b/data/core.telegram.org/constructor/chat.html deleted file mode 100644 index 124814f17f..0000000000 --- a/data/core.telegram.org/constructor/chat.html +++ /dev/null @@ -1,227 +0,0 @@ - - - - - chat - - - - - - - - - - - - - -
- -
-
-
- -

chat

- -

Info about a group

-

- -
-
chat#41cbf256 flags:# creator:flags.0?true kicked:flags.1?true left:flags.2?true deactivated:flags.5?true call_active:flags.23?true call_not_empty:flags.24?true noforwards:flags.25?true id:long title:string photo:ChatPhoto participants_count:int date:int version:int migrated_to:flags.6?InputChannel admin_rights:flags.14?ChatAdminRights default_banned_rights:flags.18?ChatBannedRights = Chat;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
creatorflags.0?trueWhether the current user is the creator of the group
kickedflags.1?trueWhether the current user was kicked from the group
leftflags.2?trueWhether the current user has left the group
deactivatedflags.5?trueWhether the group was migrated
call_activeflags.23?trueWhether a group call is currently active
call_not_emptyflags.24?trueWhether there's anyone in the group call
idlongID of the group
titlestringTitle
photoChatPhotoChat photo
participants_countintParticipant count
dateintDate of creation of the group
versionintUsed in basic groups to reorder updates and make sure that all of them were received.
migrated_toflags.6?InputChannelMeans this chat was upgraded to a supergroup
admin_rightsflags.14?ChatAdminRightsAdmin rights of the user in the group
default_banned_rightsflags.18?ChatBannedRightsDefault banned rights of all users in the group
-

Type

-

Chat

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

Admin, banned, default rights

-

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatAdminRights.html b/data/core.telegram.org/constructor/chatAdminRights.html deleted file mode 100644 index 531393d8c2..0000000000 --- a/data/core.telegram.org/constructor/chatAdminRights.html +++ /dev/null @@ -1,205 +0,0 @@ - - - - - chatAdminRights - - - - - - - - - - - - - -
- -
-
-
- -

chatAdminRights

- -

Represents the rights of an admin in a channel/supergroup.

-

- -
-
chatAdminRights#5fb224d5 flags:# change_info:flags.0?true post_messages:flags.1?true edit_messages:flags.2?true delete_messages:flags.3?true ban_users:flags.4?true invite_users:flags.5?true pin_messages:flags.7?true add_admins:flags.9?true anonymous:flags.10?true manage_call:flags.11?true other:flags.12?true = ChatAdminRights;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
change_infoflags.0?trueIf set, allows the admin to modify the description of the channel/supergroup
post_messagesflags.1?trueIf set, allows the admin to post messages in the channel
edit_messagesflags.2?trueIf set, allows the admin to also edit messages from other admins in the channel
delete_messagesflags.3?trueIf set, allows the admin to also delete messages from other admins in the channel
ban_usersflags.4?trueIf set, allows the admin to ban users from the channel/supergroup
invite_usersflags.5?trueIf set, allows the admin to invite users in the channel/supergroup
pin_messagesflags.7?trueIf set, allows the admin to pin messages in the channel/supergroup
add_adminsflags.9?trueIf set, allows the admin to add other admins with the same (or more limited) permissions in the channel/supergroup
anonymousflags.10?trueWhether this admin is anonymous
manage_callflags.11?trueIf set, allows the admin to change group call/livestream settings
otherflags.12?trueSet this flag if none of the other flags are set, but you stil want the user to be an admin.
-

Type

-

ChatAdminRights

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatAdminWithInvites.html b/data/core.telegram.org/constructor/chatAdminWithInvites.html deleted file mode 100644 index 5c62dde3f0..0000000000 --- a/data/core.telegram.org/constructor/chatAdminWithInvites.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - chatAdminWithInvites - - - - - - - - - - - - - -
- -
-
-
- -

chatAdminWithInvites

- -

Info about chat invites generated by admins.

-

- -
-
chatAdminWithInvites#f2ecef23 admin_id:long invites_count:int revoked_invites_count:int = ChatAdminWithInvites;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
admin_idlongThe admin
invites_countintNumber of invites generated by the admin
revoked_invites_countintNumber of revoked invites
-

Type

-

ChatAdminWithInvites

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatBannedRights.html b/data/core.telegram.org/constructor/chatBannedRights.html deleted file mode 100644 index c211ebffd1..0000000000 --- a/data/core.telegram.org/constructor/chatBannedRights.html +++ /dev/null @@ -1,216 +0,0 @@ - - - - - chatBannedRights - - - - - - - - - - - - - -
- -
-
-
- -

chatBannedRights

- -

Represents the rights of a normal user in a supergroup/channel/chat. In this case, the flags are inverted: if set, a flag does not allow a user to do X.

-

- -
-
chatBannedRights#9f120418 flags:# view_messages:flags.0?true send_messages:flags.1?true send_media:flags.2?true send_stickers:flags.3?true send_gifs:flags.4?true send_games:flags.5?true send_inline:flags.6?true embed_links:flags.7?true send_polls:flags.8?true change_info:flags.10?true invite_users:flags.15?true pin_messages:flags.17?true until_date:int = ChatBannedRights;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
view_messagesflags.0?trueIf set, does not allow a user to view messages in a supergroup/channel/chat
send_messagesflags.1?trueIf set, does not allow a user to send messages in a supergroup/chat
send_mediaflags.2?trueIf set, does not allow a user to send any media in a supergroup/chat
send_stickersflags.3?trueIf set, does not allow a user to send stickers in a supergroup/chat
send_gifsflags.4?trueIf set, does not allow a user to send gifs in a supergroup/chat
send_gamesflags.5?trueIf set, does not allow a user to send games in a supergroup/chat
send_inlineflags.6?trueIf set, does not allow a user to use inline bots in a supergroup/chat
embed_linksflags.7?trueIf set, does not allow a user to embed links in the messages of a supergroup/chat
send_pollsflags.8?trueIf set, does not allow a user to send polls in a supergroup/chat
change_infoflags.10?trueIf set, does not allow any user to change the description of a supergroup/chat
invite_usersflags.15?trueIf set, does not allow any user to invite users in a supergroup/chat
pin_messagesflags.17?trueIf set, does not allow any user to pin messages in a supergroup/chat
until_dateintValidity of said permissions (it is considered forever any value less then 30 seconds or more then 366 days).
-

Type

-

ChatBannedRights

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatEmpty.html b/data/core.telegram.org/constructor/chatEmpty.html deleted file mode 100644 index 59eb91e223..0000000000 --- a/data/core.telegram.org/constructor/chatEmpty.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - chatEmpty - - - - - - - - - - - - - -
- -
-
-
- -

chatEmpty

- -

Empty constructor, group doesn't exist

-

- -
-
chatEmpty#29562865 id:long = Chat;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idlongGroup identifier
-

Type

-

Chat

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatForbidden.html b/data/core.telegram.org/constructor/chatForbidden.html deleted file mode 100644 index 65ebd13046..0000000000 --- a/data/core.telegram.org/constructor/chatForbidden.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - chatForbidden - - - - - - - - - - - - - -
- -
-
-
- -

chatForbidden

- -

A group to which the user has no access. E.g., because the user was kicked from the group.

-

- -
-
chatForbidden#6592a1a7 id:long title:string = Chat;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongUser identifier
titlestringGroup name
-

Type

-

Chat

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatFull.html b/data/core.telegram.org/constructor/chatFull.html deleted file mode 100644 index 107d414c47..0000000000 --- a/data/core.telegram.org/constructor/chatFull.html +++ /dev/null @@ -1,231 +0,0 @@ - - - - - chatFull - - - - - - - - - - - - - -
- -
-
-
- -

chatFull

- -

Detailed chat info

-

- -
-
chatFull#4dbdc099 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:long about:string participants:ChatParticipants chat_photo:flags.2?Photo notify_settings:PeerNotifySettings exported_invite:flags.13?ExportedChatInvite bot_info:flags.3?Vector<BotInfo> pinned_msg_id:flags.6?int folder_id:flags.11?int call:flags.12?InputGroupCall ttl_period:flags.14?int groupcall_default_join_as:flags.15?Peer theme_emoticon:flags.16?string = ChatFull;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
can_set_usernameflags.7?trueCan we change the username of this chat
has_scheduledflags.8?trueWhether scheduled messages are available
idlongID of the chat
aboutstringAbout string for this chat
participantsChatParticipantsParticipant list
chat_photoflags.2?PhotoChat photo
notify_settingsPeerNotifySettingsNotification settings
exported_inviteflags.13?ExportedChatInviteChat invite
bot_infoflags.3?Vector<BotInfo>Info about bots that are in this chat
pinned_msg_idflags.6?intMessage ID of the last pinned message
folder_idflags.11?intPeer folder ID, for more info click here
callflags.12?InputGroupCallGroup call information
ttl_periodflags.14?intTime-To-Live of messages sent by the current user to this chat
groupcall_default_join_asflags.15?PeerWhen using phone.getGroupCallJoinAs to get a list of peers that can be used to join a group call, this field indicates the peer that should be selected by default.
theme_emoticonflags.16?stringEmoji representing a specific chat theme
-

Type

-

ChatFull

-

Related pages

-

Scheduled messages

-

Telegram allows scheduling messages

-

Pinned messages

-

Telegram allows pinning multiple messages on top of a specific chat.

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

-

phone.getGroupCallJoinAs

-

Get a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatInvite.html b/data/core.telegram.org/constructor/chatInvite.html deleted file mode 100644 index a09dd853cf..0000000000 --- a/data/core.telegram.org/constructor/chatInvite.html +++ /dev/null @@ -1,190 +0,0 @@ - - - - - chatInvite - - - - - - - - - - - - - -
- -
-
-
- -

chatInvite

- -

Chat invite info

-

- -
-
chatInvite#dfc2f58e flags:# channel:flags.0?true broadcast:flags.1?true public:flags.2?true megagroup:flags.3?true title:string photo:Photo participants_count:int participants:flags.4?Vector<User> = ChatInvite;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
channelflags.0?trueWhether this is a channel/supergroup or a normal group
broadcastflags.1?trueWhether this is a channel
publicflags.2?trueWhether this is a public channel/supergroup
megagroupflags.3?trueWhether this is a supergroup
titlestringChat/supergroup/channel title
photoPhotoChat/supergroup/channel photo
participants_countintParticipant count
participantsflags.4?Vector<User>A few of the participants that are in the group
-

Type

-

ChatInvite

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatInviteAlready.html b/data/core.telegram.org/constructor/chatInviteAlready.html deleted file mode 100644 index 02c6e303a8..0000000000 --- a/data/core.telegram.org/constructor/chatInviteAlready.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - chatInviteAlready - - - - - - - - - - - - - -
- -
-
-
- -

chatInviteAlready

- -

The user has already joined this chat

-

- -
-
chatInviteAlready#5a686d7c chat:Chat = ChatInvite;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chatChatThe chat connected to the invite
-

Type

-

ChatInvite

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatInviteExported.html b/data/core.telegram.org/constructor/chatInviteExported.html deleted file mode 100644 index 8d44404a2a..0000000000 --- a/data/core.telegram.org/constructor/chatInviteExported.html +++ /dev/null @@ -1,192 +0,0 @@ - - - - - chatInviteExported - - - - - - - - - - - - - -
- -
-
-
- -

chatInviteExported

- -

Exported chat invite

-

- -
-
chatInviteExported#b18105e8 flags:# revoked:flags.0?true permanent:flags.5?true link:string admin_id:long date:int start_date:flags.4?int expire_date:flags.1?int usage_limit:flags.2?int usage:flags.3?int = ExportedChatInvite;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
revokedflags.0?trueWhether this chat invite was revoked
permanentflags.5?trueWhether this chat invite has no expiration
linkstringChat invitation link
admin_idlongID of the admin that created this chat invite
dateintWhen was this chat invite created
start_dateflags.4?intWhen was this chat invite last modified
expire_dateflags.1?intWhen does this chat invite expire
usage_limitflags.2?intMaximum number of users that can join using this link
usageflags.3?intHow many users joined using this link
-

Type

-

ExportedChatInvite

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatInviteImporter.html b/data/core.telegram.org/constructor/chatInviteImporter.html deleted file mode 100644 index 4d8a380fca..0000000000 --- a/data/core.telegram.org/constructor/chatInviteImporter.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - chatInviteImporter - - - - - - - - - - - - - -
- -
-
-
- -

chatInviteImporter

- -

When and which user joined the chat using a chat invite

-

- -
-
chatInviteImporter#b5cd5f4 user_id:long date:int = ChatInviteImporter;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongThe user
dateintWhen did the user join
-

Type

-

ChatInviteImporter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatInvitePeek.html b/data/core.telegram.org/constructor/chatInvitePeek.html deleted file mode 100644 index bf275ef208..0000000000 --- a/data/core.telegram.org/constructor/chatInvitePeek.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - chatInvitePeek - - - - - - - - - - - - - -
- -
-
-
- -

chatInvitePeek

- -

A chat invitation that also allows peeking into the group to read messages without joining it.

-

- -
-
chatInvitePeek#61695cb0 chat:Chat expires:int = ChatInvite;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chatChatChat information
expiresintRead-only anonymous access to this group will be revoked at this date
-

Type

-

ChatInvite

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatOnlines.html b/data/core.telegram.org/constructor/chatOnlines.html deleted file mode 100644 index f1810aecd3..0000000000 --- a/data/core.telegram.org/constructor/chatOnlines.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - chatOnlines - - - - - - - - - - - - - -
- -
-
-
- -

chatOnlines

- -

Number of online users in a chat

-

- -
-
chatOnlines#f041e250 onlines:int = ChatOnlines;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
onlinesintNumber of online users
-

Type

-

ChatOnlines

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatParticipantAdmin.html b/data/core.telegram.org/constructor/chatParticipantAdmin.html deleted file mode 100644 index 5847d665ae..0000000000 --- a/data/core.telegram.org/constructor/chatParticipantAdmin.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - chatParticipantAdmin - - - - - - - - - - - - - -
- -
-
-
- -

chatParticipantAdmin

- -

Chat admin

-

- -
-
chatParticipantAdmin#a0933f5b user_id:long inviter_id:long date:int = ChatParticipant;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongID of a group member that is admin
inviter_idlongID of the user that added the member to the group
dateintDate when the user was added
-

Type

-

ChatParticipant

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatParticipantCreator.html b/data/core.telegram.org/constructor/chatParticipantCreator.html deleted file mode 100644 index 85d70ec86c..0000000000 --- a/data/core.telegram.org/constructor/chatParticipantCreator.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - chatParticipantCreator - - - - - - - - - - - - - -
- -
-
-
- -

chatParticipantCreator

- -

Represents the creator of the group

-

- -
-
chatParticipantCreator#e46bcee4 user_id:long = ChatParticipant;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongID of the user that created the group
-

Type

-

ChatParticipant

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatParticipants.html b/data/core.telegram.org/constructor/chatParticipants.html deleted file mode 100644 index f85fedd61c..0000000000 --- a/data/core.telegram.org/constructor/chatParticipants.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - chatParticipants - - - - - - - - - - - - - -
- -
-
-
- -

chatParticipants

- -

Group members.

-

- -
-
chatParticipants#3cbc93f8 chat_id:long participants:Vector<ChatParticipant> version:int = ChatParticipants;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongGroup identifier
participantsVector<ChatParticipant>List of group members
versionintGroup version number
-

Type

-

ChatParticipants

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatParticipantsForbidden.html b/data/core.telegram.org/constructor/chatParticipantsForbidden.html deleted file mode 100644 index f0e86df249..0000000000 --- a/data/core.telegram.org/constructor/chatParticipantsForbidden.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - chatParticipantsForbidden - - - - - - - - - - - - - -
- -
-
-
- -

chatParticipantsForbidden

- -

Info on members is unavailable

-

- -
-
chatParticipantsForbidden#8763d3e1 flags:# chat_id:long self_participant:flags.0?ChatParticipant = ChatParticipants;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
chat_idlongGroup ID
self_participantflags.0?ChatParticipantInfo about the group membership of the current user
-

Type

-

ChatParticipants

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatPhoto.html b/data/core.telegram.org/constructor/chatPhoto.html deleted file mode 100644 index 870530a858..0000000000 --- a/data/core.telegram.org/constructor/chatPhoto.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - chatPhoto - - - - - - - - - - - - - -
- -
-
-
- -

chatPhoto

- -

Group profile photo.

-

- -
-
chatPhoto#1c6e1c11 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = ChatPhoto;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
has_videoflags.0?trueWhether the user has an animated profile picture
photo_idlongPhoto ID
stripped_thumbflags.1?bytesStripped thumbnail
dc_idintDC where this photo is stored
-

Type

-

ChatPhoto

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatPhotoEmpty.html b/data/core.telegram.org/constructor/chatPhotoEmpty.html deleted file mode 100644 index 676b2b3f0d..0000000000 --- a/data/core.telegram.org/constructor/chatPhotoEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - chatPhotoEmpty - - - - - - - - - - - - - -
- -
-
-
- -

chatPhotoEmpty

- -

Group photo is not set.

-

- -
-
chatPhotoEmpty#37c1011c = ChatPhoto;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ChatPhoto

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/chatTheme.html b/data/core.telegram.org/constructor/chatTheme.html deleted file mode 100644 index 3d671d7b26..0000000000 --- a/data/core.telegram.org/constructor/chatTheme.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - chatTheme - - - - - - - - - - - - - -
- -
-
-
- -

chatTheme

- -

A chat theme

-

- -
-
chatTheme#ed0b5c33 emoticon:string theme:Theme dark_theme:Theme = ChatTheme;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
emoticonstringEmoji, identifying this specific chat theme
themeThemeTheme
dark_themeThemeDark mode theme
-

Type

-

ChatTheme

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/codeSettings.html b/data/core.telegram.org/constructor/codeSettings.html deleted file mode 100644 index e12acdc731..0000000000 --- a/data/core.telegram.org/constructor/codeSettings.html +++ /dev/null @@ -1,166 +0,0 @@ - - - - - codeSettings - - - - - - - - - - - - - -
- -
-
-
- -

codeSettings

- -

Settings used by telegram servers for sending the confirm code.

-

Example implementations: telegram for android, tdlib.

-

- -
-
codeSettings#debebe83 flags:# allow_flashcall:flags.0?true current_number:flags.1?true allow_app_hash:flags.4?true = CodeSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
allow_flashcallflags.0?trueWhether to allow phone verification via phone calls.
current_numberflags.1?truePass true if the phone number is used on the current device. Ignored if allow_flashcall is not set.
allow_app_hashflags.4?trueIf a token that will be included in eventually sent SMSs is required: required in newer versions of android, to use the android SMS receiver APIs
-

Type

-

CodeSettings

-

Related pages

-

User Authorization

-

How to register a user's phone to start using the API.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/config.html b/data/core.telegram.org/constructor/config.html deleted file mode 100644 index 8ff611def8..0000000000 --- a/data/core.telegram.org/constructor/config.html +++ /dev/null @@ -1,420 +0,0 @@ - - - - - config - - - - - - - - - - - - - -
- -
-
-
- -

config

- -

Current configuration

-

- -
-
config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
phonecalls_enabledflags.1?trueWhether phone calls can be used
default_p2p_contactsflags.3?trueWhether the client should use P2P by default for phone calls with contacts
preload_featured_stickersflags.4?trueWhether the client should preload featured stickers
ignore_phone_entitiesflags.5?trueWhether the client should ignore phone entities
revoke_pm_inboxflags.6?trueWhether incoming private messages can be deleted for both participants
blocked_modeflags.8?trueIndicates that telegram is probably censored by governments/ISPs in the current region
pfs_enabledflags.13?trueWhether pfs was used
dateintCurrent date at the server
expiresintExpiration date of this config: when it expires it'll have to be refetched using help.getConfig
test_modeBoolWhether we're connected to the test DCs
this_dcintID of the DC that returned the reply
dc_optionsVector<DcOption>DC IP list
dc_txt_domain_namestringDomain name for fetching encrypted DC list from DNS TXT record
chat_size_maxintMaximum member count for normal groups
megagroup_size_maxintMaximum member count for supergroups
forwarded_count_maxintMaximum number of messages that can be forwarded at once using messages.forwardMessages.
online_update_period_msintThe client should update its online status every N milliseconds
offline_blur_timeout_msintDelay before offline status needs to be sent to the server
offline_idle_timeout_msintTime without any user activity after which it should be treated offline
online_cloud_timeout_msintIf we are offline, but were online from some other client in last online_cloud_timeout_ms milliseconds after we had gone offline, then delay offline notification for notify_cloud_delay_ms milliseconds.
notify_cloud_delay_msintIf we are offline, but online from some other client then delay sending the offline notification for notify_cloud_delay_ms milliseconds.
notify_default_delay_msintIf some other client is online, then delay notification for notification_default_delay_ms milliseconds
push_chat_period_msintNot for client use
push_chat_limitintNot for client use
saved_gifs_limitintMaximum count of saved gifs
edit_time_limitintOnly messages with age smaller than the one specified can be edited
revoke_time_limitintOnly channel/supergroup messages with age smaller than the specified can be deleted
revoke_pm_time_limitintOnly private messages with age smaller than the specified can be deleted
rating_e_decayintExponential decay rate for computing top peer rating
stickers_recent_limitintMaximum number of recent stickers
stickers_faved_limitintMaximum number of faved stickers
channels_read_media_periodintIndicates that round videos (video notes) and voice messages sent in channels and older than the specified period must be marked as read
tmp_sessionsflags.0?intTemporary passport sessions
pinned_dialogs_count_maxintMaximum count of pinned dialogs
pinned_infolder_count_maxintMaximum count of dialogs per folder
call_receive_timeout_msintMaximum allowed outgoing ring time in VoIP calls: if the user we're calling doesn't reply within the specified time (in milliseconds), we should hang up the call
call_ring_timeout_msintMaximum allowed incoming ring time in VoIP calls: if the current user doesn't reply within the specified time (in milliseconds), the call will be automatically refused
call_connect_timeout_msintVoIP connection timeout: if the instance of libtgvoip on the other side of the call doesn't connect to our instance of libtgvoip within the specified time (in milliseconds), the call must be aborted
call_packet_timeout_msintIf during a VoIP call a packet isn't received for the specified period of time, the call must be aborted
me_url_prefixstringThe domain to use to parse in-app links.
For example t.me indicates that t.me/username links should parsed to @username, t.me/addsticker/name should be parsed to the appropriate stickerset and so on...
autoupdate_url_prefixflags.7?stringURL to use to auto-update the current app
gif_search_usernameflags.9?stringUsername of the bot to use to search for GIFs
venue_search_usernameflags.10?stringUsername of the bot to use to search for venues
img_search_usernameflags.11?stringUsername of the bot to use for image search
static_maps_providerflags.12?stringID of the map provider to use for venues
caption_length_maxintMaximum length of caption (length in utf8 codepoints)
message_length_maxintMaximum length of messages (length in utf8 codepoints)
webfile_dc_idintDC ID to use to download webfiles
suggested_lang_codeflags.2?stringSuggested language code
lang_pack_versionflags.2?intLanguage pack version
base_lang_pack_versionflags.2?intBasic language pack version
-

Type

-

Config

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

-

Perfect Forward Secrecy

-

Binding temporary authorization key to permanent ones.

-

help.getConfig

-

Returns current configuration, including data center configuration.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

messages.forwardMessages

-

Forwards messages by their IDs.

-

account.updateStatus

-

Updates online user status.

-

Top peer rating

-

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

-

Telegram Passport Manual

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/contact.html b/data/core.telegram.org/constructor/contact.html deleted file mode 100644 index f2ebed910e..0000000000 --- a/data/core.telegram.org/constructor/contact.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - contact - - - - - - - - - - - - - -
- -
-
-
- -

contact

- -

A contact of the current user that is registered in the system.

-

- -
-
contact#145ade0b user_id:long mutual:Bool = Contact;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser identifier
mutualBoolCurrent user is in the user's contact list
-

Type

-

Contact

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/contactStatus.html b/data/core.telegram.org/constructor/contactStatus.html deleted file mode 100644 index 92d5afcf34..0000000000 --- a/data/core.telegram.org/constructor/contactStatus.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - contactStatus - - - - - - - - - - - - - -
- -
-
-
- -

contactStatus

- -

Contact status: online / offline.

-

- -
-
contactStatus#16d9703b user_id:long status:UserStatus = ContactStatus;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser identifier
statusUserStatusOnline status
-

Type

-

ContactStatus

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/contacts.blocked b/data/core.telegram.org/constructor/contacts.blocked deleted file mode 100644 index 362c714072..0000000000 --- a/data/core.telegram.org/constructor/contacts.blocked +++ /dev/null @@ -1,157 +0,0 @@ - - - - - contacts.blocked - - - - - - - - - - - - - -
- -
-
-
- -

contacts.blocked

- -

Full list of blocked users.

-

- -
-
contacts.blocked#ade1591 blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
blockedVector<PeerBlocked>List of blocked users
chatsVector<Chat>Blocked chats
usersVector<User>List of users
-

Type

-

contacts.Blocked

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/contacts.blockedSlice b/data/core.telegram.org/constructor/contacts.blockedSlice deleted file mode 100644 index 29af09b856..0000000000 --- a/data/core.telegram.org/constructor/contacts.blockedSlice +++ /dev/null @@ -1,162 +0,0 @@ - - - - - contacts.blockedSlice - - - - - - - - - - - - - -
- -
-
-
- -

contacts.blockedSlice

- -

Incomplete list of blocked users.

-

- -
-
contacts.blockedSlice#e1664194 count:int blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countintTotal number of elements in the list
blockedVector<PeerBlocked>List of blocked users
chatsVector<Chat>Blocked chats
usersVector<User>List of users
-

Type

-

contacts.Blocked

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/contacts.contacts b/data/core.telegram.org/constructor/contacts.contacts deleted file mode 100644 index 0470e98560..0000000000 --- a/data/core.telegram.org/constructor/contacts.contacts +++ /dev/null @@ -1,157 +0,0 @@ - - - - - contacts.contacts - - - - - - - - - - - - - -
- -
-
-
- -

contacts.contacts

- -

The current user's contact list and info on users.

-

- -
-
contacts.contacts#eae87e42 contacts:Vector<Contact> saved_count:int users:Vector<User> = contacts.Contacts;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
contactsVector<Contact>Contact list
saved_countintNumber of contacts that were saved successfully
usersVector<User>User list
-

Type

-

contacts.Contacts

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/contacts.contactsNotModified b/data/core.telegram.org/constructor/contacts.contactsNotModified deleted file mode 100644 index bb513a2e67..0000000000 --- a/data/core.telegram.org/constructor/contacts.contactsNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - contacts.contactsNotModified - - - - - - - - - - - - - -
- -
-
-
- -

contacts.contactsNotModified

- -

Contact list on the server is the same as the list on the client.

-

- -
-
contacts.contactsNotModified#b74ba9d2 = contacts.Contacts;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

contacts.Contacts

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/contacts.found b/data/core.telegram.org/constructor/contacts.found deleted file mode 100644 index 69c2e79636..0000000000 --- a/data/core.telegram.org/constructor/contacts.found +++ /dev/null @@ -1,162 +0,0 @@ - - - - - contacts.found - - - - - - - - - - - - - -
- -
-
-
- -

contacts.found

- -

Users found by name substring and auxiliary data.

-

- -
-
contacts.found#b3134d9d my_results:Vector<Peer> results:Vector<Peer> chats:Vector<Chat> users:Vector<User> = contacts.Found;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
my_resultsVector<Peer>Personalized results
resultsVector<Peer>List of found user identifiers
chatsVector<Chat>Found chats
usersVector<User>List of users
-

Type

-

contacts.Found

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/contacts.resolvedPeer b/data/core.telegram.org/constructor/contacts.resolvedPeer deleted file mode 100644 index a29b89dc96..0000000000 --- a/data/core.telegram.org/constructor/contacts.resolvedPeer +++ /dev/null @@ -1,157 +0,0 @@ - - - - - contacts.resolvedPeer - - - - - - - - - - - - - -
- -
-
-
- -

contacts.resolvedPeer

- -

Resolved peer

-

- -
-
contacts.resolvedPeer#7f077ad9 peer:Peer chats:Vector<Chat> users:Vector<User> = contacts.ResolvedPeer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerThe peer
chatsVector<Chat>Chats
usersVector<User>Users
-

Type

-

contacts.ResolvedPeer

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/contacts.topPeers b/data/core.telegram.org/constructor/contacts.topPeers deleted file mode 100644 index 7a12dc54f6..0000000000 --- a/data/core.telegram.org/constructor/contacts.topPeers +++ /dev/null @@ -1,157 +0,0 @@ - - - - - contacts.topPeers - - - - - - - - - - - - - -
- -
-
-
- -

contacts.topPeers

- -

Top peers

-

- -
-
contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
categoriesVector<TopPeerCategoryPeers>Top peers by top peer category
chatsVector<Chat>Chats
usersVector<User>Users
-

Type

-

contacts.TopPeers

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/contacts.topPeersDisabled b/data/core.telegram.org/constructor/contacts.topPeersDisabled deleted file mode 100644 index 033541c269..0000000000 --- a/data/core.telegram.org/constructor/contacts.topPeersDisabled +++ /dev/null @@ -1,132 +0,0 @@ - - - - - contacts.topPeersDisabled - - - - - - - - - - - - - -
- -
-
-
- -

contacts.topPeersDisabled

- -

Top peers disabled

-

- -
-
contacts.topPeersDisabled#b52c939d = contacts.TopPeers;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

contacts.TopPeers

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/contacts.topPeersNotModified b/data/core.telegram.org/constructor/contacts.topPeersNotModified deleted file mode 100644 index 1e6a36f955..0000000000 --- a/data/core.telegram.org/constructor/contacts.topPeersNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - contacts.topPeersNotModified - - - - - - - - - - - - - -
- -
-
-
- -

contacts.topPeersNotModified

- -

Top peer info hasn't changed

-

- -
-
contacts.topPeersNotModified#de266ef5 = contacts.TopPeers;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

contacts.TopPeers

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/dataJSON.html b/data/core.telegram.org/constructor/dataJSON.html deleted file mode 100644 index a31c1532b9..0000000000 --- a/data/core.telegram.org/constructor/dataJSON.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - dataJSON - - - - - - - - - - - - - -
- -
-
-
- -

dataJSON

- -

Represents a json-encoded object

-

- -
-
dataJSON#7d748d04 data:string = DataJSON;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
datastringJSON-encoded object
-

Type

-

DataJSON

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/dcOption.html b/data/core.telegram.org/constructor/dcOption.html deleted file mode 100644 index e1c99b2723..0000000000 --- a/data/core.telegram.org/constructor/dcOption.html +++ /dev/null @@ -1,197 +0,0 @@ - - - - - dcOption - - - - - - - - - - - - - -
- -
-
-
- -

dcOption

- -

Data centre

-

- -
-
dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
ipv6flags.0?trueWhether the specified IP is an IPv6 address
media_onlyflags.1?trueWhether this DC should only be used to download or upload files
tcpo_onlyflags.2?trueWhether this DC only supports connection with transport obfuscation
cdnflags.3?trueWhether this is a CDN DC.
staticflags.4?trueIf set, this IP should be used when connecting through a proxy
idintDC ID
ip_addressstringIP address of DC
portintPort
secretflags.10?bytesIf the tcpo_only flag is set, specifies the secret to use when connecting using transport obfuscation
-

Type

-

DcOption

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

-

MTProto transports

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessage.html b/data/core.telegram.org/constructor/decryptedMessage.html deleted file mode 100644 index a22553d1cf..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessage.html +++ /dev/null @@ -1,217 +0,0 @@ - - - - - decryptedMessage - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessage

- -

Contents of an encrypted message.

-

- -
-
===8===
-decryptedMessage#1f814f1f random_id:long random_bytes:bytes message:string media:DecryptedMessageMedia = DecryptedMessage;
-
-===17===
-decryptedMessage#204d3878 random_id:long ttl:int message:string media:DecryptedMessageMedia = DecryptedMessage;
-
-===45===
-decryptedMessage#36b091de flags:# random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long = DecryptedMessage;
-
-===73===
-decryptedMessage#91cc4674 flags:# no_webpage:flags.1?true silent:flags.5?true random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long grouped_id:flags.17?long = DecryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields (added in layer 45)
no_webpageflags.1?trueWhether the webpage preview is disabled
silentflags.5?trueWhether this is a silent message (no notification triggered)
random_idlongRandom message ID, assigned by the author of message.
Must be equal to the ID passed to sending method.
ttlintMessage lifetime. Has higher priority than decryptedMessageActionSetMessageTTL.
Parameter added in Layer 17.
messagestringMessage text
mediaflags.9?DecryptedMessageMediaMedia content
entitiesflags.7?Vector<MessageEntity>Message entities for styled text (parameter added in layer 45)
via_bot_nameflags.11?stringSpecifies the ID of the inline bot that generated the message (parameter added in layer 45)
reply_to_random_idflags.3?longRandom message ID of the message this message replies to (parameter added in layer 45)
grouped_idflags.17?longRandom group ID, assigned by the author of message.
Multiple encrypted messages with a photo attached and with the same group ID indicate an album or grouped media (parameter added in layer 45)
-

Type

-

DecryptedMessage

-

Related pages

-

decryptedMessageActionSetMessageTTL

-

Setting of a message lifetime after reading.

-

Upon receiving such message the client shall start deleting of all messages of an encrypted chat ttl_seconds seconds after the messages were read by user.

-

Layers

-

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

-

Styled text with message entities

-

How to create styled text with message entities

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionAbortKey.html b/data/core.telegram.org/constructor/decryptedMessageActionAbortKey.html deleted file mode 100644 index c0e215340b..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionAbortKey.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - decryptedMessageActionAbortKey - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionAbortKey

- -

Abort rekeying

-

- -
-
===20===
-decryptedMessageActionAbortKey#dd05ec6b exchange_id:long = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
exchange_idlongExchange ID
-

Type

-

DecryptedMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionAcceptKey.html b/data/core.telegram.org/constructor/decryptedMessageActionAcceptKey.html deleted file mode 100644 index b6c5fb406f..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionAcceptKey.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - decryptedMessageActionAcceptKey - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionAcceptKey

- -

Accept new key

-

- -
-
===20===
-decryptedMessageActionAcceptKey#6fe1735b exchange_id:long g_b:bytes key_fingerprint:long = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
exchange_idlongExchange ID
g_bbytesB parameter, see rekeying process
key_fingerprintlongKey fingerprint, see rekeying process
-

Type

-

DecryptedMessageAction

-

Related pages

-

Perfect Forward Secrecy

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionCommitKey.html b/data/core.telegram.org/constructor/decryptedMessageActionCommitKey.html deleted file mode 100644 index 51a021301c..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionCommitKey.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - decryptedMessageActionCommitKey - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionCommitKey

- -

Commit new key, see rekeying process

-

- -
-
===20===
-decryptedMessageActionCommitKey#ec2e0b9b exchange_id:long key_fingerprint:long = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
exchange_idlongExchange ID, see rekeying process
key_fingerprintlongKey fingerprint, see rekeying process
-

Type

-

DecryptedMessageAction

-

Related pages

-

Perfect Forward Secrecy

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionDeleteMessages.html b/data/core.telegram.org/constructor/decryptedMessageActionDeleteMessages.html deleted file mode 100644 index 694a95b7da..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionDeleteMessages.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - decryptedMessageActionDeleteMessages - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionDeleteMessages

- -

Deleted messages.

-

- -
-
===8===
-decryptedMessageActionDeleteMessages#65614304 random_ids:Vector<long> = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
random_idsVector<long>List of deleted message IDs
-

Type

-

DecryptedMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionFlushHistory.html b/data/core.telegram.org/constructor/decryptedMessageActionFlushHistory.html deleted file mode 100644 index 429be2b493..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionFlushHistory.html +++ /dev/null @@ -1,133 +0,0 @@ - - - - - decryptedMessageActionFlushHistory - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionFlushHistory

- -

The entire message history has been deleted.

-

- -
-
===8===
-decryptedMessageActionFlushHistory#6719e45c = DecryptedMessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

DecryptedMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionNoop.html b/data/core.telegram.org/constructor/decryptedMessageActionNoop.html deleted file mode 100644 index 9ddff65b0d..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionNoop.html +++ /dev/null @@ -1,133 +0,0 @@ - - - - - decryptedMessageActionNoop - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionNoop

- -

NOOP action

-

- -
-
===20===
-decryptedMessageActionNoop#a82fdd63 = DecryptedMessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

DecryptedMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionNotifyLayer.html b/data/core.telegram.org/constructor/decryptedMessageActionNotifyLayer.html deleted file mode 100644 index 23af64d198..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionNotifyLayer.html +++ /dev/null @@ -1,151 +0,0 @@ - - - - - decryptedMessageActionNotifyLayer - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionNotifyLayer

- -

A notification stating the API layer that is used by the client. You should use your current layer and take notice of the layer used on the other side of a conversation when sending messages.

-

- -
-
===17===
-decryptedMessageActionNotifyLayer#f3048883 layer:int = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
layerintLayer number, must be 17 or higher (this contructor was introduced in Layer 17).
-

Type

-

DecryptedMessageAction

-

Related pages

-

Layers

-

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionReadMessages.html b/data/core.telegram.org/constructor/decryptedMessageActionReadMessages.html deleted file mode 100644 index c02f0bce9d..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionReadMessages.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - decryptedMessageActionReadMessages - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionReadMessages

- -

Messages marked as read.

-

- -
-
===8===
-decryptedMessageActionReadMessages#c4f40be random_ids:Vector<long> = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
random_idsVector<long>List of message IDs
-

Type

-

DecryptedMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionRequestKey.html b/data/core.telegram.org/constructor/decryptedMessageActionRequestKey.html deleted file mode 100644 index c6169d8bad..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionRequestKey.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - decryptedMessageActionRequestKey - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionRequestKey

- -

Request rekeying, see rekeying process

-

- -
-
===20===
-decryptedMessageActionRequestKey#f3c9611b exchange_id:long g_a:bytes = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
exchange_idlongExchange ID
g_abytesg_a, see rekeying process
-

Type

-

DecryptedMessageAction

-

Related pages

-

Perfect Forward Secrecy

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionResend.html b/data/core.telegram.org/constructor/decryptedMessageActionResend.html deleted file mode 100644 index 27ca55189a..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionResend.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - decryptedMessageActionResend - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionResend

- -

Request for the other party in a Secret Chat to automatically resend a contiguous range of previously sent messages, as explained in Sequence number is Secret Chats.

-

- -
-
===17===
-decryptedMessageActionResend#511110b0 start_seq_no:int end_seq_no:int = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
start_seq_nointout_seq_no of the first message to be resent, with correct parity
end_seq_nointout_seq_no of the last message to be resent, with same parity.
-

Type

-

DecryptedMessageAction

-

Related pages

-

Sequence numbers in Secret Chats

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionScreenshotMessages.html b/data/core.telegram.org/constructor/decryptedMessageActionScreenshotMessages.html deleted file mode 100644 index 887a7e164e..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionScreenshotMessages.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - decryptedMessageActionScreenshotMessages - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionScreenshotMessages

- -

A screenshot was taken.

-

- -
-
===8===
-decryptedMessageActionScreenshotMessages#8ac1f475 random_ids:Vector<long> = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
random_idsVector<long>List of affected message ids (that appeared on the screenshot)
-

Type

-

DecryptedMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionSetMessageTTL.html b/data/core.telegram.org/constructor/decryptedMessageActionSetMessageTTL.html deleted file mode 100644 index 2d4194974c..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionSetMessageTTL.html +++ /dev/null @@ -1,149 +0,0 @@ - - - - - decryptedMessageActionSetMessageTTL - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionSetMessageTTL

- -

Setting of a message lifetime after reading.

-

Upon receiving such message the client shall start deleting of all messages of an encrypted chat ttl_seconds seconds after the messages were read by user.

-

- -
-
===8===
-decryptedMessageActionSetMessageTTL#a1733aec ttl_seconds:int = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
ttl_secondsintLifetime in seconds
-

Type

-

DecryptedMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageActionTyping.html b/data/core.telegram.org/constructor/decryptedMessageActionTyping.html deleted file mode 100644 index b6dee6a583..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageActionTyping.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - decryptedMessageActionTyping - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionTyping

- -

User is preparing a message: typing, recording, uploading, etc.

-

- -
-
===17===
-decryptedMessageActionTyping#ccb27641 action:SendMessageAction = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
actionSendMessageActionType of action
-

Type

-

DecryptedMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageLayer.html b/data/core.telegram.org/constructor/decryptedMessageLayer.html deleted file mode 100644 index c73f0aa007..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageLayer.html +++ /dev/null @@ -1,173 +0,0 @@ - - - - - decryptedMessageLayer - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageLayer

- -

Sets the layer number for the contents of an encrypted message.

-

- -
-
===17===
-decryptedMessageLayer#1be31789 random_bytes:bytes layer:int in_seq_no:int out_seq_no:int message:DecryptedMessage = DecryptedMessageLayer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
random_bytesbytesSet of random bytes to prevent content recognition in short encrypted messages.
Clients are required to check that there are at least 15 random bytes included in each message. Messages with less than 15 random bytes must be ignored.
Parameter moved here from decryptedMessage in Layer 17.
layerintLayer number. Mimimal value - 17 (the layer in which the constructor was added).
in_seq_noint2x the number of messages in the sender's inbox (including deleted and service messages), incremented by 1 if current user was not the chat creator
Parameter added in Layer 17.
out_seq_noint2x the number of messages in the recipient's inbox (including deleted and service messages), incremented by 1 if current user was the chat creator
Parameter added in Layer 17.
messageDecryptedMessageThe content of message itself
-

Type

-

DecryptedMessageLayer

-

Related pages

-

decryptedMessage

-

Contents of an encrypted message.

-

Layers

-

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaAudio.html b/data/core.telegram.org/constructor/decryptedMessageMediaAudio.html deleted file mode 100644 index 8bd08c313d..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageMediaAudio.html +++ /dev/null @@ -1,174 +0,0 @@ - - - - - decryptedMessageMediaAudio - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaAudio

- -

Audio file attached to a secret chat message.

-

- -
-
===8===
-decryptedMessageMediaAudio#6080758f duration:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-
-===17===
-decryptedMessageMediaAudio#57e0a9cb duration:int mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
durationintAudio duration in seconds
mime_typestringMIME-type of the audio file
Parameter added in Layer 13.
sizeintFile size
keybytesKey to decrypt the attached media file
ivbytesInitialization vector
-

Type

-

DecryptedMessageMedia

-

Related pages

-

Layers

-

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaContact.html b/data/core.telegram.org/constructor/decryptedMessageMediaContact.html deleted file mode 100644 index b308706c91..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageMediaContact.html +++ /dev/null @@ -1,163 +0,0 @@ - - - - - decryptedMessageMediaContact - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaContact

- -

Contact attached to an encrypted message.

-

- -
-
===8===
-decryptedMessageMediaContact#588a0a97 phone_number:string first_name:string last_name:string user_id:int = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number
first_namestringContact's first name
last_namestringContact's last name
user_idintTelegram User ID of signed-up contact
-

Type

-

DecryptedMessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaDocument.html b/data/core.telegram.org/constructor/decryptedMessageMediaDocument.html deleted file mode 100644 index 7db8d51194..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageMediaDocument.html +++ /dev/null @@ -1,191 +0,0 @@ - - - - - decryptedMessageMediaDocument - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaDocument

- -

Document attached to a message in a secret chat.

-

- -
-
===8===
-decryptedMessageMediaDocument#b095434b thumb:bytes thumb_w:int thumb_h:int file_name:string mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
-
-===45===
-decryptedMessageMediaDocument#7afe8ae2 thumb:bytes thumb_w:int thumb_h:int mime_type:string size:int key:bytes iv:bytes attributes:Vector<DocumentAttribute> caption:string = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
thumbbytesThumbnail-file contents (JPEG-file, quality 55, set in a 90x90 square)
thumb_wintThumbnail width
thumb_hintThumbnail height
mime_typestringFile MIME-type
sizeintDocument size
keybytesKey to decrypt the attached document file
ivbytesInitialization
attributesVector<DocumentAttribute>Document attributes for media types
captionstringCaption
-

Type

-

DecryptedMessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaEmpty.html b/data/core.telegram.org/constructor/decryptedMessageMediaEmpty.html deleted file mode 100644 index 6fafcb2463..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageMediaEmpty.html +++ /dev/null @@ -1,133 +0,0 @@ - - - - - decryptedMessageMediaEmpty - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaEmpty

- -

Empty constructor, no media content.

-

- -
-
===8===
-decryptedMessageMediaEmpty#89f5c4a = DecryptedMessageMedia;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

DecryptedMessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaExternalDocument.html b/data/core.telegram.org/constructor/decryptedMessageMediaExternalDocument.html deleted file mode 100644 index 32baa84ad4..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageMediaExternalDocument.html +++ /dev/null @@ -1,183 +0,0 @@ - - - - - decryptedMessageMediaExternalDocument - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaExternalDocument

- -

Non-e2e documented forwarded from non-secret chat

-

- -
-
===23===
-decryptedMessageMediaExternalDocument#fa95b0dd id:long access_hash:long date:int mime_type:string size:int thumb:PhotoSize dc_id:int attributes:Vector<DocumentAttribute> = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongDocument ID
access_hashlongaccess hash
dateintDate
mime_typestringMime type
sizeintSize
thumbPhotoSizeThumbnail
dc_idintDC ID
attributesVector<DocumentAttribute>Attributes for media types
-

Type

-

DecryptedMessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaGeoPoint.html b/data/core.telegram.org/constructor/decryptedMessageMediaGeoPoint.html deleted file mode 100644 index 6bd97831ff..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageMediaGeoPoint.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - decryptedMessageMediaGeoPoint - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaGeoPoint

- -

GeoPont attached to an encrypted message.

-

- -
-
===8===
-decryptedMessageMediaGeoPoint#35480a59 lat:double long:double = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
latdoubleLatitude of point
longdoubleLongtitude of point
-

Type

-

DecryptedMessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaPhoto.html b/data/core.telegram.org/constructor/decryptedMessageMediaPhoto.html deleted file mode 100644 index e3f1ac7a70..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageMediaPhoto.html +++ /dev/null @@ -1,191 +0,0 @@ - - - - - decryptedMessageMediaPhoto - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaPhoto

- -

Photo attached to an encrypted message.

-

- -
-
===8===
-decryptedMessageMediaPhoto#32798a8c thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-
-===45===
-decryptedMessageMediaPhoto#f1fa8d78 thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
thumbbytesContent of thumbnail file (JPEGfile, quality 55, set in a square 90x90)
thumb_wintThumbnail width
thumb_hintThumbnail height
wintPhoto width
hintPhoto height
sizeintSize of the photo in bytes
keybytesKey to decrypt an attached file with a full version
ivbytesInitialization vector
captionstringCaption
-

Type

-

DecryptedMessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaVenue.html b/data/core.telegram.org/constructor/decryptedMessageMediaVenue.html deleted file mode 100644 index c330e81f7c..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageMediaVenue.html +++ /dev/null @@ -1,173 +0,0 @@ - - - - - decryptedMessageMediaVenue - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaVenue

- -

Venue

-

- -
-
===45===
-decryptedMessageMediaVenue#8a0df56f lat:double long:double title:string address:string provider:string venue_id:string = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
latdoubleLatitude of venue
longdoubleLongitude of venue
titlestringVenue name
addressstringAddress
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
-

Type

-

DecryptedMessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaVideo.html b/data/core.telegram.org/constructor/decryptedMessageMediaVideo.html deleted file mode 100644 index d57b799699..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageMediaVideo.html +++ /dev/null @@ -1,207 +0,0 @@ - - - - - decryptedMessageMediaVideo - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaVideo

- -

Video attached to an encrypted message.

-

- -
-
===8===
-decryptedMessageMediaVideo#4cee6ef3 thumb:bytes thumb_w:int thumb_h:int duration:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-
-===17===
-decryptedMessageMediaVideo#524a415d thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-
-===45===
-decryptedMessageMediaVideo#970c8c0e thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
thumbbytesContent of thumbnail file (JPEG file, quality 55, set in a square 90x90)
thumb_wintThumbnail width
thumb_hintThumbnail height
durationintDuration of video in seconds
mime_typestringMIME-type of the video file
Parameter added in Layer 17.
wintImage width
hintImage height
sizeintFile size
keybytesKey to decrypt the attached video file
ivbytesInitialization vector
captionstringCaption
-

Type

-

DecryptedMessageMedia

-

Related pages

-

Layers

-

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageMediaWebPage.html b/data/core.telegram.org/constructor/decryptedMessageMediaWebPage.html deleted file mode 100644 index ede7a98af5..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageMediaWebPage.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - decryptedMessageMediaWebPage - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaWebPage

- -

Webpage preview

-

- -
-
===45===
-decryptedMessageMediaWebPage#e50511d8 url:string = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
urlstringURL of webpage
-

Type

-

DecryptedMessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/decryptedMessageService.html b/data/core.telegram.org/constructor/decryptedMessageService.html deleted file mode 100644 index de1faa372b..0000000000 --- a/data/core.telegram.org/constructor/decryptedMessageService.html +++ /dev/null @@ -1,156 +0,0 @@ - - - - - decryptedMessageService - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageService

- -

Contents of an encrypted service message.

-

- -
-
===8===
-decryptedMessageService#aa48327d random_id:long random_bytes:bytes action:DecryptedMessageAction = DecryptedMessage;
-
-===17===
-decryptedMessageService#73164160 random_id:long action:DecryptedMessageAction = DecryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
random_idlongRandom message ID, assigned by the message author.
Must be equal to the ID passed to the sending method.
actionDecryptedMessageActionAction relevant to the service message
-

Type

-

DecryptedMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/dialog.html b/data/core.telegram.org/constructor/dialog.html deleted file mode 100644 index 5b957328f0..0000000000 --- a/data/core.telegram.org/constructor/dialog.html +++ /dev/null @@ -1,214 +0,0 @@ - - - - - dialog - - - - - - - - - - - - - -
- -
-
-
- -

dialog

- -

Chat

-

- -
-
dialog#2c171f72 flags:# pinned:flags.2?true unread_mark:flags.3?true peer:Peer top_message:int read_inbox_max_id:int read_outbox_max_id:int unread_count:int unread_mentions_count:int notify_settings:PeerNotifySettings pts:flags.0?int draft:flags.1?DraftMessage folder_id:flags.4?int = Dialog;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.2?trueIs the dialog pinned
unread_markflags.3?trueWhether the chat was manually marked as unread
peerPeerThe chat
top_messageintThe latest message ID
read_inbox_max_idintPosition up to which all incoming messages are read.
read_outbox_max_idintPosition up to which all outgoing messages are read.
unread_countintNumber of unread messages
unread_mentions_countintNumber of unread mentions
notify_settingsPeerNotifySettingsNotification settings
ptsflags.0?intPTS
draftflags.1?DraftMessageMessage draft
folder_idflags.4?intPeer folder ID, for more info click here
-

Type

-

Dialog

-

Related pages

-

Mentions

-

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/dialogFilter.html b/data/core.telegram.org/constructor/dialogFilter.html deleted file mode 100644 index 79d611da43..0000000000 --- a/data/core.telegram.org/constructor/dialogFilter.html +++ /dev/null @@ -1,220 +0,0 @@ - - - - - dialogFilter - - - - - - - - - - - - - -
- -
-
-
- -

dialogFilter

- -

Dialog filter AKA folder

-

- -
-
dialogFilter#7438f7e8 flags:# contacts:flags.0?true non_contacts:flags.1?true groups:flags.2?true broadcasts:flags.3?true bots:flags.4?true exclude_muted:flags.11?true exclude_read:flags.12?true exclude_archived:flags.13?true id:int title:string emoticon:flags.25?string pinned_peers:Vector<InputPeer> include_peers:Vector<InputPeer> exclude_peers:Vector<InputPeer> = DialogFilter;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
contactsflags.0?trueWhether to include all contacts in this folder
non_contactsflags.1?trueWhether to include all non-contacts in this folder
groupsflags.2?trueWhether to include all groups in this folder
broadcastsflags.3?trueWhether to include all channels in this folder
botsflags.4?trueWhether to include all bots in this folder
exclude_mutedflags.11?trueWhether to exclude muted chats from this folder
exclude_readflags.12?trueWhether to exclude read chats from this folder
exclude_archivedflags.13?trueWhether to exclude archived chats from this folder
idintFolder ID
titlestringFolder name
emoticonflags.25?stringFolder emoticon
pinned_peersVector<InputPeer>Pinned chats, folders can have unlimited pinned chats
include_peersVector<InputPeer>Include the following chats in this folder
exclude_peersVector<InputPeer>Exclude the following chats from this folder
-

Type

-

DialogFilter

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/dialogFilterSuggested.html b/data/core.telegram.org/constructor/dialogFilterSuggested.html deleted file mode 100644 index d7e5df87c6..0000000000 --- a/data/core.telegram.org/constructor/dialogFilterSuggested.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - dialogFilterSuggested - - - - - - - - - - - - - -
- -
-
-
- -

dialogFilterSuggested

- -

Suggested folders

-

- -
-
dialogFilterSuggested#77744d4a filter:DialogFilter description:string = DialogFilterSuggested;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
filterDialogFilterFolder info
descriptionstringFolder description
-

Type

-

DialogFilterSuggested

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/dialogFolder.html b/data/core.telegram.org/constructor/dialogFolder.html deleted file mode 100644 index 772045e45a..0000000000 --- a/data/core.telegram.org/constructor/dialogFolder.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - dialogFolder - - - - - - - - - - - - - -
- -
-
-
- -

dialogFolder

- -

Dialog in folder

-

- -
-
dialogFolder#71bd134c flags:# pinned:flags.2?true folder:Folder peer:Peer top_message:int unread_muted_peers_count:int unread_unmuted_peers_count:int unread_muted_messages_count:int unread_unmuted_messages_count:int = Dialog;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.2?trueIs this folder pinned
folderFolderThe folder
peerPeerPeer in folder
top_messageintLatest message ID of dialog
unread_muted_peers_countintNumber of unread muted peers in folder
unread_unmuted_peers_countintNumber of unread unmuted peers in folder
unread_muted_messages_countintNumber of unread messages from muted peers in folder
unread_unmuted_messages_countintNumber of unread messages from unmuted peers in folder
-

Type

-

Dialog

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/dialogPeer.html b/data/core.telegram.org/constructor/dialogPeer.html deleted file mode 100644 index 46835a4ddb..0000000000 --- a/data/core.telegram.org/constructor/dialogPeer.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - dialogPeer - - - - - - - - - - - - - -
- -
-
-
- -

dialogPeer

- -

Peer

-

- -
-
dialogPeer#e56dbf05 peer:Peer = DialogPeer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerPeer
-

Type

-

DialogPeer

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/dialogPeerFolder.html b/data/core.telegram.org/constructor/dialogPeerFolder.html deleted file mode 100644 index 807726ff5f..0000000000 --- a/data/core.telegram.org/constructor/dialogPeerFolder.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - dialogPeerFolder - - - - - - - - - - - - - -
- -
-
-
- -

dialogPeerFolder

- -

Peer folder

-

- -
-
dialogPeerFolder#514519e2 folder_id:int = DialogPeer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
folder_idintPeer folder ID, for more info click here
-

Type

-

DialogPeer

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/disabledFeature.html b/data/core.telegram.org/constructor/disabledFeature.html deleted file mode 100644 index 7f0d00308b..0000000000 --- a/data/core.telegram.org/constructor/disabledFeature.html +++ /dev/null @@ -1,163 +0,0 @@ - - - - - disabledFeature - - - - - - - - - - - - - -
- -
-
-
- -

disabledFeature

- -

A disabled feature

-

- -
-
Constructor schema is available as of layer 76. Switch »

-

Parameters

- - - - - - - - - - - - - -
featurestringThe feature that was disabled
descriptionstringDescription
-

Type

-

DisabledFeature

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/document.html b/data/core.telegram.org/constructor/document.html deleted file mode 100644 index 9b220ccb40..0000000000 --- a/data/core.telegram.org/constructor/document.html +++ /dev/null @@ -1,200 +0,0 @@ - - - - - document - - - - - - - - - - - - - -
- -
-
-
- -

document

- -

Document

-

- -
-
document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idlongDocument ID
access_hashlongCheck sum, dependant on document ID
file_referencebytesFile reference
dateintCreation date
mime_typestringMIME type
sizeintSize
thumbsflags.0?Vector<PhotoSize>Thumbnails
video_thumbsflags.1?Vector<VideoSize>Video thumbnails
dc_idintDC ID
attributesVector<DocumentAttribute>Attributes
-

Type

-

Document

-

Related pages

-

File references

-

How to handle file references.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/documentAttributeAnimated.html b/data/core.telegram.org/constructor/documentAttributeAnimated.html deleted file mode 100644 index bd8055a20d..0000000000 --- a/data/core.telegram.org/constructor/documentAttributeAnimated.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - documentAttributeAnimated - - - - - - - - - - - - - -
- -
-
-
- -

documentAttributeAnimated

- -

Defines an animated GIF

-

- -
-
documentAttributeAnimated#11b58939 = DocumentAttribute;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

DocumentAttribute

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/documentAttributeAudio.html b/data/core.telegram.org/constructor/documentAttributeAudio.html deleted file mode 100644 index 6fc246cc23..0000000000 --- a/data/core.telegram.org/constructor/documentAttributeAudio.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - documentAttributeAudio - - - - - - - - - - - - - -
- -
-
-
- -

documentAttributeAudio

- -

Represents an audio file

-

- -
-
documentAttributeAudio#9852f9c6 flags:# voice:flags.10?true duration:int title:flags.0?string performer:flags.1?string waveform:flags.2?bytes = DocumentAttribute;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
voiceflags.10?trueWhether this is a voice message
durationintDuration in seconds
titleflags.0?stringName of song
performerflags.1?stringPerformer
waveformflags.2?bytesWaveform
-

Type

-

DocumentAttribute

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/documentAttributeFilename.html b/data/core.telegram.org/constructor/documentAttributeFilename.html deleted file mode 100644 index 5adfd817a0..0000000000 --- a/data/core.telegram.org/constructor/documentAttributeFilename.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - documentAttributeFilename - - - - - - - - - - - - - -
- -
-
-
- -

documentAttributeFilename

- -

A simple document with a file name

-

- -
-
documentAttributeFilename#15590068 file_name:string = DocumentAttribute;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
file_namestringThe file name
-

Type

-

DocumentAttribute

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/documentAttributeHasStickers.html b/data/core.telegram.org/constructor/documentAttributeHasStickers.html deleted file mode 100644 index 08ea716327..0000000000 --- a/data/core.telegram.org/constructor/documentAttributeHasStickers.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - documentAttributeHasStickers - - - - - - - - - - - - - -
- -
-
-
- -

documentAttributeHasStickers

- -

Whether the current document has stickers attached

-

- -
-
documentAttributeHasStickers#9801d2f7 = DocumentAttribute;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

DocumentAttribute

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/documentAttributeImageSize.html b/data/core.telegram.org/constructor/documentAttributeImageSize.html deleted file mode 100644 index b172bc339c..0000000000 --- a/data/core.telegram.org/constructor/documentAttributeImageSize.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - documentAttributeImageSize - - - - - - - - - - - - - -
- -
-
-
- -

documentAttributeImageSize

- -

Defines the width and height of an image uploaded as document

-

- -
-
documentAttributeImageSize#6c37c15c w:int h:int = DocumentAttribute;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
wintWidth of image
hintHeight of image
-

Type

-

DocumentAttribute

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/documentAttributeSticker.html b/data/core.telegram.org/constructor/documentAttributeSticker.html deleted file mode 100644 index 681385d0c7..0000000000 --- a/data/core.telegram.org/constructor/documentAttributeSticker.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - documentAttributeSticker - - - - - - - - - - - - - -
- -
-
-
- -

documentAttributeSticker

- -

Defines a sticker

-

- -
-
documentAttributeSticker#6319d612 flags:# mask:flags.1?true alt:string stickerset:InputStickerSet mask_coords:flags.0?MaskCoords = DocumentAttribute;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
maskflags.1?trueWhether this is a mask sticker
altstringAlternative emoji representation of sticker
stickersetInputStickerSetAssociated stickerset
mask_coordsflags.0?MaskCoordsMask coordinates (if this is a mask sticker, attached to a photo)
-

Type

-

DocumentAttribute

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/documentAttributeVideo.html b/data/core.telegram.org/constructor/documentAttributeVideo.html deleted file mode 100644 index 63a0e30596..0000000000 --- a/data/core.telegram.org/constructor/documentAttributeVideo.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - documentAttributeVideo - - - - - - - - - - - - - -
- -
-
-
- -

documentAttributeVideo

- -

Defines a video

-

- -
-
documentAttributeVideo#ef02ce6 flags:# round_message:flags.0?true supports_streaming:flags.1?true duration:int w:int h:int = DocumentAttribute;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
round_messageflags.0?trueWhether this is a round video
supports_streamingflags.1?trueWhether the video supports streaming
durationintDuration in seconds
wintVideo width
hintVideo height
-

Type

-

DocumentAttribute

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/documentEmpty.html b/data/core.telegram.org/constructor/documentEmpty.html deleted file mode 100644 index 873257a1e7..0000000000 --- a/data/core.telegram.org/constructor/documentEmpty.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - documentEmpty - - - - - - - - - - - - - -
- -
-
-
- -

documentEmpty

- -

Empty constructor, document doesn't exist.

-

- -
-
documentEmpty#36f8c871 id:long = Document;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idlongDocument ID or 0
-

Type

-

Document

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/draftMessage.html b/data/core.telegram.org/constructor/draftMessage.html deleted file mode 100644 index 052dfef445..0000000000 --- a/data/core.telegram.org/constructor/draftMessage.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - draftMessage - - - - - - - - - - - - - -
- -
-
-
- -

draftMessage

- -

Represents a message draft.

-

- -
-
draftMessage#fd8e711f flags:# no_webpage:flags.1?true reply_to_msg_id:flags.0?int message:string entities:flags.3?Vector<MessageEntity> date:int = DraftMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.1?trueWhether no webpage preview will be generated
reply_to_msg_idflags.0?intThe message this message will reply to
messagestringThe draft
entitiesflags.3?Vector<MessageEntity>Message entities for styled text.
dateintDate of last update of the draft.
-

Type

-

DraftMessage

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

-

Message drafts

-

How to handle message drafts

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/draftMessageEmpty.html b/data/core.telegram.org/constructor/draftMessageEmpty.html deleted file mode 100644 index 8f6fb7c5e8..0000000000 --- a/data/core.telegram.org/constructor/draftMessageEmpty.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - draftMessageEmpty - - - - - - - - - - - - - -
- -
-
-
- -

draftMessageEmpty

- -

Empty draft

-

- -
-
draftMessageEmpty#1b0c841a flags:# date:flags.0?int = DraftMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
dateflags.0?intWhen was the draft last updated
-

Type

-

DraftMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/emojiKeyword.html b/data/core.telegram.org/constructor/emojiKeyword.html deleted file mode 100644 index 7e34a40c58..0000000000 --- a/data/core.telegram.org/constructor/emojiKeyword.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - emojiKeyword - - - - - - - - - - - - - -
- -
-
-
- -

emojiKeyword

- -

Emoji keyword

-

- -
-
emojiKeyword#d5b3b9f9 keyword:string emoticons:Vector<string> = EmojiKeyword;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
keywordstringKeyword
emoticonsVector<string>Emojis associated to keyword
-

Type

-

EmojiKeyword

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/emojiKeywordDeleted.html b/data/core.telegram.org/constructor/emojiKeywordDeleted.html deleted file mode 100644 index 10c70c0e2b..0000000000 --- a/data/core.telegram.org/constructor/emojiKeywordDeleted.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - emojiKeywordDeleted - - - - - - - - - - - - - -
- -
-
-
- -

emojiKeywordDeleted

- -

Deleted emoji keyword

-

- -
-
emojiKeywordDeleted#236df622 keyword:string emoticons:Vector<string> = EmojiKeyword;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
keywordstringKeyword
emoticonsVector<string>Emojis that were associated to keyword
-

Type

-

EmojiKeyword

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/emojiKeywordsDifference.html b/data/core.telegram.org/constructor/emojiKeywordsDifference.html deleted file mode 100644 index 338760d0aa..0000000000 --- a/data/core.telegram.org/constructor/emojiKeywordsDifference.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - emojiKeywordsDifference - - - - - - - - - - - - - -
- -
-
-
- -

emojiKeywordsDifference

- -

Changes to emoji keywords

-

- -
-
emojiKeywordsDifference#5cc761bd lang_code:string from_version:int version:int keywords:Vector<EmojiKeyword> = EmojiKeywordsDifference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
lang_codestringLanguage code for keywords
from_versionintPrevious emoji keyword list version
versionintCurrent version of emoji keyword list
keywordsVector<EmojiKeyword>Emojis associated to keywords
-

Type

-

EmojiKeywordsDifference

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/emojiLanguage.html b/data/core.telegram.org/constructor/emojiLanguage.html deleted file mode 100644 index 982cc08851..0000000000 --- a/data/core.telegram.org/constructor/emojiLanguage.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - emojiLanguage - - - - - - - - - - - - - -
- -
-
-
- -

emojiLanguage

- -

Emoji language

-

- -
-
emojiLanguage#b3fb5361 lang_code:string = EmojiLanguage;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
lang_codestringLanguage code
-

Type

-

EmojiLanguage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/emojiURL.html b/data/core.telegram.org/constructor/emojiURL.html deleted file mode 100644 index b87df8a416..0000000000 --- a/data/core.telegram.org/constructor/emojiURL.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - emojiURL - - - - - - - - - - - - - -
- -
-
-
- -

emojiURL

- -

An HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation

-

- -
-
emojiURL#a575739d url:string = EmojiURL;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
urlstringAn HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation
-

Type

-

EmojiURL

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/encryptedChat.html b/data/core.telegram.org/constructor/encryptedChat.html deleted file mode 100644 index ce2692a0db..0000000000 --- a/data/core.telegram.org/constructor/encryptedChat.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - encryptedChat - - - - - - - - - - - - - -
- -
-
-
- -

encryptedChat

- -

Encrypted chat

-

- -
-
encryptedChat#61f0d4c7 id:int access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long = EncryptedChat;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idintChat ID
access_hashlongCheck sum dependant on the user ID
dateintDate chat was created
admin_idlongChat creator ID
participant_idlongID of the second chat participant
g_a_or_bbytesB = g ^ b mod p, if the currently authorized user is the chat's creator,
or A = g ^ a mod p otherwise
See Wikipedia for more info
key_fingerprintlong64-bit fingerprint of received key
-

Type

-

EncryptedChat

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/encryptedChatDiscarded.html b/data/core.telegram.org/constructor/encryptedChatDiscarded.html deleted file mode 100644 index dc5d6bee34..0000000000 --- a/data/core.telegram.org/constructor/encryptedChatDiscarded.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - encryptedChatDiscarded - - - - - - - - - - - - - -
- -
-
-
- -

encryptedChatDiscarded

- -

Discarded or deleted chat.

-

- -
-
encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
history_deletedflags.0?trueWhether both users of this secret chat should also remove all of its messages
idintChat ID
-

Type

-

EncryptedChat

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/encryptedChatEmpty.html b/data/core.telegram.org/constructor/encryptedChatEmpty.html deleted file mode 100644 index a00b3384eb..0000000000 --- a/data/core.telegram.org/constructor/encryptedChatEmpty.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - encryptedChatEmpty - - - - - - - - - - - - - -
- -
-
-
- -

encryptedChatEmpty

- -

Empty constructor.

-

- -
-
encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idintChat ID
-

Type

-

EncryptedChat

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/encryptedChatRequested.html b/data/core.telegram.org/constructor/encryptedChatRequested.html deleted file mode 100644 index e744d93430..0000000000 --- a/data/core.telegram.org/constructor/encryptedChatRequested.html +++ /dev/null @@ -1,185 +0,0 @@ - - - - - encryptedChatRequested - - - - - - - - - - - - - -
- -
-
-
- -

encryptedChatRequested

- -

Request to create an encrypted chat.

-

- -
-
encryptedChatRequested#48f1d94c flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:long participant_id:long g_a:bytes = EncryptedChat;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.0?intPeer folder ID, for more info click here
idintChat ID
access_hashlongCheck sum depending on user ID
dateintChat creation date
admin_idlongChat creator ID
participant_idlongID of second chat participant
g_abytesA = g ^ a mod p, see Wikipedia
-

Type

-

EncryptedChat

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/encryptedMessage.html b/data/core.telegram.org/constructor/encryptedMessage.html deleted file mode 100644 index 0cddfd4daf..0000000000 --- a/data/core.telegram.org/constructor/encryptedMessage.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - encryptedMessage - - - - - - - - - - - - - -
- -
-
-
- -

encryptedMessage

- -

Encrypted message.

-

- -
-
encryptedMessage#ed18c118 random_id:long chat_id:int date:int bytes:bytes file:EncryptedFile = EncryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
random_idlongRandom message ID, assigned by the author of message
chat_idintID of encrypted chat
dateintDate of sending
bytesbytesTL-serialising of DecryptedMessage type, encrypted with the key creatied at stage of chat initialization
fileEncryptedFileAttached encrypted file
-

Type

-

EncryptedMessage

-

Related pages

-

DecryptedMessage

-

Object describes the contents of an encrypted message.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/encryptedMessageService.html b/data/core.telegram.org/constructor/encryptedMessageService.html deleted file mode 100644 index d994207a2d..0000000000 --- a/data/core.telegram.org/constructor/encryptedMessageService.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - encryptedMessageService - - - - - - - - - - - - - -
- -
-
-
- -

encryptedMessageService

- -

Encrypted service message

-

- -
-
encryptedMessageService#23734b06 random_id:long chat_id:int date:int bytes:bytes = EncryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
random_idlongRandom message ID, assigned by the author of message
chat_idintID of encrypted chat
dateintDate of sending
bytesbytesTL-serialising of DecryptedMessage type, encrypted with the key creatied at stage of chat initialization
-

Type

-

EncryptedMessage

-

Related pages

-

DecryptedMessage

-

Object describes the contents of an encrypted message.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/error.html b/data/core.telegram.org/constructor/error.html deleted file mode 100644 index 50690654a5..0000000000 --- a/data/core.telegram.org/constructor/error.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - error - - - - - - - - - - - - - -
- -
-
-
- -

error

- -

Error.

-

- -
-
error#c4b9f9bb code:int text:string = Error;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
codeintError code
textstringMessage
-

Type

-

Error

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/exportedMessageLink.html b/data/core.telegram.org/constructor/exportedMessageLink.html deleted file mode 100644 index 7f76b44b8f..0000000000 --- a/data/core.telegram.org/constructor/exportedMessageLink.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - exportedMessageLink - - - - - - - - - - - - - -
- -
-
-
- -

exportedMessageLink

- -

Link to a message in a supergroup/channel

-

- -
-
exportedMessageLink#5dab1af4 link:string html:string = ExportedMessageLink;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
linkstringURL
htmlstringEmbed code
-

Type

-

ExportedMessageLink

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/fileHash.html b/data/core.telegram.org/constructor/fileHash.html deleted file mode 100644 index 4edb3ffc04..0000000000 --- a/data/core.telegram.org/constructor/fileHash.html +++ /dev/null @@ -1,171 +0,0 @@ - - - - - FileHash - - - - - - - - - - - - - -
- -
-
-
- -

FileHash

- -

SHA256 Hash of an uploaded file, to be checked for validity after download

-

- -
-
fileHash#6242c773 offset:int limit:int hash:bytes = FileHash;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset from where to start computing SHA-256 hash
limitintLength
hashbytesSHA-256 Hash of file chunk, to be checked for validity after download
-

Type

-

FileHash

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/fileLocation.html b/data/core.telegram.org/constructor/fileLocation.html deleted file mode 100644 index e59f25ac3c..0000000000 --- a/data/core.telegram.org/constructor/fileLocation.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - fileLocation - - - - - - - - - - - - - -
- -
-
-
- -

fileLocation

- -

File location.

-

- -
-
Constructor schema is available as of layer 86. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
dc_idintNumber of the data center holding the file
volume_idlongServer volume
local_idintFile ID
secretlongChecksum to access the file
-

Type

-

FileLocation

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/fileLocationUnavailable.html b/data/core.telegram.org/constructor/fileLocationUnavailable.html deleted file mode 100644 index 171eb081e5..0000000000 --- a/data/core.telegram.org/constructor/fileLocationUnavailable.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - fileLocationUnavailable - - - - - - - - - - - - - -
- -
-
-
- -

fileLocationUnavailable

- -

File is currently unavailable.

-

- -
-
Constructor schema is available as of layer 98. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
volume_idlongServer volume
local_idintFile ID
secretlongChecksum to access the file
-

Type

-

FileLocation

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/folder.html b/data/core.telegram.org/constructor/folder.html deleted file mode 100644 index 9dae755722..0000000000 --- a/data/core.telegram.org/constructor/folder.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - folder - - - - - - - - - - - - - -
- -
-
-
- -

folder

- -

Folder

-

- -
-
folder#ff544e65 flags:# autofill_new_broadcasts:flags.0?true autofill_public_groups:flags.1?true autofill_new_correspondents:flags.2?true id:int title:string photo:flags.3?ChatPhoto = Folder;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
autofill_new_broadcastsflags.0?trueAutomatically add new channels to this folder
autofill_public_groupsflags.1?trueAutomatically add joined new public supergroups to this folder
autofill_new_correspondentsflags.2?trueAutomatically add new private chats to this folder
idintFolder ID
titlestringFolder title
photoflags.3?ChatPhotoFolder picture
-

Type

-

Folder

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/folderPeer.html b/data/core.telegram.org/constructor/folderPeer.html deleted file mode 100644 index f11703481e..0000000000 --- a/data/core.telegram.org/constructor/folderPeer.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - folderPeer - - - - - - - - - - - - - -
- -
-
-
- -

folderPeer

- -

Peer in a folder

-

- -
-
folderPeer#e9baa668 peer:Peer folder_id:int = FolderPeer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerFolder peer info
folder_idintPeer folder ID, for more info click here
-

Type

-

FolderPeer

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/game.html b/data/core.telegram.org/constructor/game.html deleted file mode 100644 index 7d75f1217a..0000000000 --- a/data/core.telegram.org/constructor/game.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - game - - - - - - - - - - - - - -
- -
-
-
- -

game

- -

Indicates an already sent game

-

- -
-
game#bdf9653b flags:# id:long access_hash:long short_name:string title:string description:string photo:Photo document:flags.0?Document = Game;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idlongID of the game
access_hashlongAccess hash of the game
short_namestringShort name for the game
titlestringTitle of the game
descriptionstringGame description
photoPhotoGame preview
documentflags.0?DocumentOptional attached document
-

Type

-

Game

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/geoPoint.html b/data/core.telegram.org/constructor/geoPoint.html deleted file mode 100644 index 496f5bbdb0..0000000000 --- a/data/core.telegram.org/constructor/geoPoint.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - geoPoint - - - - - - - - - - - - - -
- -
-
-
- -

geoPoint

- -

GeoPoint.

-

- -
-
geoPoint#b2a2f663 flags:# long:double lat:double access_hash:long accuracy_radius:flags.0?int = GeoPoint;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
longdoubleLongtitude
latdoubleLatitude
access_hashlongAccess hash
accuracy_radiusflags.0?intThe estimated horizontal accuracy of the location, in meters; as defined by the sender.
-

Type

-

GeoPoint

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/geoPointEmpty.html b/data/core.telegram.org/constructor/geoPointEmpty.html deleted file mode 100644 index 281c782f30..0000000000 --- a/data/core.telegram.org/constructor/geoPointEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - geoPointEmpty - - - - - - - - - - - - - -
- -
-
-
- -

geoPointEmpty

- -

Empty constructor.

-

- -
-
geoPointEmpty#1117dd5f = GeoPoint;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

GeoPoint

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/globalPrivacySettings.html b/data/core.telegram.org/constructor/globalPrivacySettings.html deleted file mode 100644 index 6017aa062a..0000000000 --- a/data/core.telegram.org/constructor/globalPrivacySettings.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - globalPrivacySettings - - - - - - - - - - - - - -
- -
-
-
- -

globalPrivacySettings

- -

Global privacy settings

-

- -
-
globalPrivacySettings#bea2f424 flags:# archive_and_mute_new_noncontact_peers:flags.0?Bool = GlobalPrivacySettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
archive_and_mute_new_noncontact_peersflags.0?BoolWhether to archive and mute new chats from non-contacts
-

Type

-

GlobalPrivacySettings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/groupCall.html b/data/core.telegram.org/constructor/groupCall.html deleted file mode 100644 index 6468bec12a..0000000000 --- a/data/core.telegram.org/constructor/groupCall.html +++ /dev/null @@ -1,230 +0,0 @@ - - - - - groupCall - - - - - - - - - - - - - -
- -
-
-
- -

groupCall

- -

Info about a group call or livestream

-

- -
-
groupCall#d597650c flags:# join_muted:flags.1?true can_change_join_muted:flags.2?true join_date_asc:flags.6?true schedule_start_subscribed:flags.8?true can_start_video:flags.9?true record_video_active:flags.11?true id:long access_hash:long participants_count:int title:flags.3?string stream_dc_id:flags.4?int record_start_date:flags.5?int schedule_date:flags.7?int unmuted_video_count:flags.10?int unmuted_video_limit:int version:int = GroupCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
join_mutedflags.1?trueWhether the user should be muted upon joining the call
can_change_join_mutedflags.2?trueWhether the current user can change the value of the join_muted flag using phone.toggleGroupCallSettings
join_date_ascflags.6?trueSpecifies the ordering to use when locally sorting by date and displaying in the UI group call participants.
schedule_start_subscribedflags.8?trueWhether we subscribed to the scheduled call
can_start_videoflags.9?trueWhether you can start streaming video into the call
record_video_activeflags.11?trueWhether the group call is currently being recorded
idlongGroup call ID
access_hashlongGroup call access hash
participants_countintParticipant count
titleflags.3?stringGroup call title
stream_dc_idflags.4?intDC ID to be used for livestream chunks
record_start_dateflags.5?intWhen was the recording started
schedule_dateflags.7?intWhen is the call scheduled to start
unmuted_video_countflags.10?intNumber of people currently streaming video into the call
unmuted_video_limitintMaximum number of people allowed to stream video into the call
versionintVersion
-

Type

-

GroupCall

-

Related pages

-

phone.toggleGroupCallSettings

-

Change group call settings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/groupCallDiscarded.html b/data/core.telegram.org/constructor/groupCallDiscarded.html deleted file mode 100644 index 757f4b716e..0000000000 --- a/data/core.telegram.org/constructor/groupCallDiscarded.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - groupCallDiscarded - - - - - - - - - - - - - -
- -
-
-
- -

groupCallDiscarded

- -

An ended group call

-

- -
-
groupCallDiscarded#7780bcb4 id:long access_hash:long duration:int = GroupCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongGroup call ID
access_hashlongGroup call access hash
durationintGroup call duration
-

Type

-

GroupCall

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/groupCallParticipant.html b/data/core.telegram.org/constructor/groupCallParticipant.html deleted file mode 100644 index de9007327d..0000000000 --- a/data/core.telegram.org/constructor/groupCallParticipant.html +++ /dev/null @@ -1,247 +0,0 @@ - - - - - groupCallParticipant - - - - - - - - - - - - - -
- -
-
-
- -

groupCallParticipant

- -

Info about a group call participant

-

- -
-
groupCallParticipant#eba636fe flags:# muted:flags.0?true left:flags.1?true can_self_unmute:flags.2?true just_joined:flags.4?true versioned:flags.5?true min:flags.8?true muted_by_you:flags.9?true volume_by_admin:flags.10?true self:flags.12?true video_joined:flags.15?true peer:Peer date:int active_date:flags.3?int source:int volume:flags.7?int about:flags.11?string raise_hand_rating:flags.13?long video:flags.6?GroupCallParticipantVideo presentation:flags.14?GroupCallParticipantVideo = GroupCallParticipant;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
mutedflags.0?trueWhether the participant is muted
leftflags.1?trueWhether the participant has left
can_self_unmuteflags.2?trueWhether the participant can unmute themselves
just_joinedflags.4?trueWhether the participant has just joined
versionedflags.5?trueIf set, and updateGroupCallParticipants.version < locally stored call.version, info about this participant should be ignored. If (...), and updateGroupCallParticipants.version > call.version+1, the participant list should be refetched using phone.getGroupParticipants.
minflags.8?trueIf not set, the volume and muted_by_you fields can be safely used to overwrite locally cached information; otherwise, volume will contain valid information only if volume_by_admin is set both in the cache and in the received constructor.
muted_by_youflags.9?trueWhether this participant was muted by the current user
volume_by_adminflags.10?trueWhether our volume can only changed by an admin
selfflags.12?trueWhether this participant is the current user
video_joinedflags.15?trueWhether this participant is currently broadcasting video
peerPeerPeer information
dateintWhen did this participant join the group call
active_dateflags.3?intWhen was this participant last active in the group call
sourceintSource ID
volumeflags.7?intVolume, if not set the volume is set to 100%.
aboutflags.11?stringInfo about this participant
raise_hand_ratingflags.13?longSpecifies the UI visualization order of peers with raised hands: peers with a higher rating should be showed first in the list.
videoflags.6?GroupCallParticipantVideoInfo about the video stream the participant is currently broadcasting
presentationflags.14?GroupCallParticipantVideoInfo about the screen sharing stream the participant is currently broadcasting
-

Type

-

GroupCallParticipant

-

Related pages

-

updateGroupCallParticipants

-

The participant list of a certain group call has changed

-

phone.getGroupParticipants

-

Get group call participants

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/groupCallParticipantVideo.html b/data/core.telegram.org/constructor/groupCallParticipantVideo.html deleted file mode 100644 index 7adea98c53..0000000000 --- a/data/core.telegram.org/constructor/groupCallParticipantVideo.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - groupCallParticipantVideo - - - - - - - - - - - - - -
- -
-
-
- -

groupCallParticipantVideo

- -

Info about a video stream

-

- -
-
groupCallParticipantVideo#67753ac8 flags:# paused:flags.0?true endpoint:string source_groups:Vector<GroupCallParticipantVideoSourceGroup> audio_source:flags.1?int = GroupCallParticipantVideo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
pausedflags.0?trueWhether the stream is currently paused
endpointstringEndpoint
source_groupsVector<GroupCallParticipantVideoSourceGroup>Source groups
audio_sourceflags.1?intAudio source ID
-

Type

-

GroupCallParticipantVideo

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/groupCallParticipantVideoSourceGroup.html b/data/core.telegram.org/constructor/groupCallParticipantVideoSourceGroup.html deleted file mode 100644 index 5015af0769..0000000000 --- a/data/core.telegram.org/constructor/groupCallParticipantVideoSourceGroup.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - groupCallParticipantVideoSourceGroup - - - - - - - - - - - - - -
- -
-
-
- -

groupCallParticipantVideoSourceGroup

- -

Describes a group of video synchronization source identifiers

-

- -
-
groupCallParticipantVideoSourceGroup#dcb118b7 semantics:string sources:Vector<int> = GroupCallParticipantVideoSourceGroup;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
semanticsstringSDP semantics
sourcesVector<int>Source IDs
-

Type

-

GroupCallParticipantVideoSourceGroup

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.appUpdate b/data/core.telegram.org/constructor/help.appUpdate deleted file mode 100644 index 0ba49ba0ee..0000000000 --- a/data/core.telegram.org/constructor/help.appUpdate +++ /dev/null @@ -1,190 +0,0 @@ - - - - - help.appUpdate - - - - - - - - - - - - - -
- -
-
-
- -

help.appUpdate

- -

An update is available for the application.

-

- -
-
help.appUpdate#ccbbce30 flags:# can_not_skip:flags.0?true id:int version:string text:string entities:Vector<MessageEntity> document:flags.1?Document url:flags.2?string sticker:flags.3?Document = help.AppUpdate;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
can_not_skipflags.0?trueUnskippable, the new info must be shown to the user (with a popup or something else)
idintUpdate ID
versionstringNew version name
textstringText description of the update
entitiesVector<MessageEntity>Message entities for styled text
documentflags.1?DocumentApplication binary
urlflags.2?stringApplication download URL
stickerflags.3?DocumentAssociated sticker
-

Type

-

help.AppUpdate

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.countriesList b/data/core.telegram.org/constructor/help.countriesList deleted file mode 100644 index 0ea61c46eb..0000000000 --- a/data/core.telegram.org/constructor/help.countriesList +++ /dev/null @@ -1,155 +0,0 @@ - - - - - help.countriesList - - - - - - - - - - - - - -
- -
-
-
- -

help.countriesList

- -

Name, ISO code, localized name and phone codes/patterns of all available countries

-

- -
-
help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countriesVector<help.Country>Name, ISO code, localized name and phone codes/patterns of all available countries
hashintHash for pagination, for more info click here
-

Type

-

help.CountriesList

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.countriesListNotModified b/data/core.telegram.org/constructor/help.countriesListNotModified deleted file mode 100644 index 033eb4c430..0000000000 --- a/data/core.telegram.org/constructor/help.countriesListNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - help.countriesListNotModified - - - - - - - - - - - - - -
- -
-
-
- -

help.countriesListNotModified

- -

The country list has not changed

-

- -
-
help.countriesListNotModified#93cc1f32 = help.CountriesList;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

help.CountriesList

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.country b/data/core.telegram.org/constructor/help.country deleted file mode 100644 index 48f232d08f..0000000000 --- a/data/core.telegram.org/constructor/help.country +++ /dev/null @@ -1,172 +0,0 @@ - - - - - help.country - - - - - - - - - - - - - -
- -
-
-
- -

help.country

- -

Name, ISO code, localized name and phone codes/patterns of a specific country

-

- -
-
help.country#c3878e23 flags:# hidden:flags.0?true iso2:string default_name:string name:flags.1?string country_codes:Vector<help.CountryCode> = help.Country;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
hiddenflags.0?trueWhether this country should not be shown in the list
iso2stringISO code of country
default_namestringName of the country in the country's language
nameflags.1?stringName of the country in the user's language, if different from the original name
country_codesVector<help.CountryCode>Phone codes/patterns
-

Type

-

help.Country

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.countryCode b/data/core.telegram.org/constructor/help.countryCode deleted file mode 100644 index 2626e3dcf4..0000000000 --- a/data/core.telegram.org/constructor/help.countryCode +++ /dev/null @@ -1,162 +0,0 @@ - - - - - help.countryCode - - - - - - - - - - - - - -
- -
-
-
- -

help.countryCode

- -

Country code and phone number pattern of a specific country

-

- -
-
help.countryCode#4203c5ef flags:# country_code:string prefixes:flags.0?Vector<string> patterns:flags.1?Vector<string> = help.CountryCode;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
country_codestringISO country code
prefixesflags.0?Vector<string>Possible phone prefixes
patternsflags.1?Vector<string>Phone patterns: for example, XXX XXX XXX
-

Type

-

help.CountryCode

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.deepLinkInfo b/data/core.telegram.org/constructor/help.deepLinkInfo deleted file mode 100644 index cbdcdf38e0..0000000000 --- a/data/core.telegram.org/constructor/help.deepLinkInfo +++ /dev/null @@ -1,165 +0,0 @@ - - - - - help.deepLinkInfo - - - - - - - - - - - - - -
- -
-
-
- -

help.deepLinkInfo

- -

Deep linking info

-

- -
-
help.deepLinkInfo#6a4ee832 flags:# update_app:flags.0?true message:string entities:flags.1?Vector<MessageEntity> = help.DeepLinkInfo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
update_appflags.0?trueAn update of the app is required to parse this link
messagestringMessage to show to the user
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
-

Type

-

help.DeepLinkInfo

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.deepLinkInfoEmpty b/data/core.telegram.org/constructor/help.deepLinkInfoEmpty deleted file mode 100644 index 36f84eca8d..0000000000 --- a/data/core.telegram.org/constructor/help.deepLinkInfoEmpty +++ /dev/null @@ -1,132 +0,0 @@ - - - - - help.deepLinkInfoEmpty - - - - - - - - - - - - - -
- -
-
-
- -

help.deepLinkInfoEmpty

- -

Deep link info empty

-

- -
-
help.deepLinkInfoEmpty#66afa166 = help.DeepLinkInfo;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

help.DeepLinkInfo

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.inviteText b/data/core.telegram.org/constructor/help.inviteText deleted file mode 100644 index fa8c38459a..0000000000 --- a/data/core.telegram.org/constructor/help.inviteText +++ /dev/null @@ -1,147 +0,0 @@ - - - - - help.inviteText - - - - - - - - - - - - - -
- -
-
-
- -

help.inviteText

- -

Text of a text message with an invitation to install Telegram.

-

- -
-
help.inviteText#18cb9f78 message:string = help.InviteText;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
messagestringText of the message
-

Type

-

help.InviteText

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.noAppUpdate b/data/core.telegram.org/constructor/help.noAppUpdate deleted file mode 100644 index 94ec14d918..0000000000 --- a/data/core.telegram.org/constructor/help.noAppUpdate +++ /dev/null @@ -1,132 +0,0 @@ - - - - - help.noAppUpdate - - - - - - - - - - - - - -
- -
-
-
- -

help.noAppUpdate

- -

No updates are available for the application.

-

- -
-
help.noAppUpdate#c45a6536 = help.AppUpdate;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

help.AppUpdate

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.passportConfig b/data/core.telegram.org/constructor/help.passportConfig deleted file mode 100644 index fd58c3692f..0000000000 --- a/data/core.telegram.org/constructor/help.passportConfig +++ /dev/null @@ -1,156 +0,0 @@ - - - - - help.passportConfig - - - - - - - - - - - - - -
- -
-
-
- -

help.passportConfig

- -

Telegram passport configuration

-

- -
-
help.passportConfig#a098d6af hash:int countries_langs:DataJSON = help.PassportConfig;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashintHash for pagination, for more info click here
countries_langsDataJSONLocalization
-

Type

-

help.PassportConfig

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.passportConfigNotModified b/data/core.telegram.org/constructor/help.passportConfigNotModified deleted file mode 100644 index 30ded66bc7..0000000000 --- a/data/core.telegram.org/constructor/help.passportConfigNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - help.passportConfigNotModified - - - - - - - - - - - - - -
- -
-
-
- -

help.passportConfigNotModified

- -

Password configuration not modified

-

- -
-
help.passportConfigNotModified#bfb9f457 = help.PassportConfig;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

help.PassportConfig

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.promoData b/data/core.telegram.org/constructor/help.promoData deleted file mode 100644 index d78dcd4277..0000000000 --- a/data/core.telegram.org/constructor/help.promoData +++ /dev/null @@ -1,182 +0,0 @@ - - - - - help.promoData - - - - - - - - - - - - - -
- -
-
-
- -

help.promoData

- -

MTProxy/Public Service Announcement information

-

- -
-
help.promoData#8c39793f flags:# proxy:flags.0?true expires:int peer:Peer chats:Vector<Chat> users:Vector<User> psa_type:flags.1?string psa_message:flags.2?string = help.PromoData;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
proxyflags.0?trueMTProxy-related channel
expiresintExpiry of PSA/MTProxy info
peerPeerMTProxy/PSA peer
chatsVector<Chat>Chat info
usersVector<User>User info
psa_typeflags.1?stringPSA type
psa_messageflags.2?stringPSA message
-

Type

-

help.PromoData

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.promoDataEmpty b/data/core.telegram.org/constructor/help.promoDataEmpty deleted file mode 100644 index ccfdddebfd..0000000000 --- a/data/core.telegram.org/constructor/help.promoDataEmpty +++ /dev/null @@ -1,147 +0,0 @@ - - - - - help.promoDataEmpty - - - - - - - - - - - - - -
- -
-
-
- -

help.promoDataEmpty

- -

No PSA/MTProxy info is available

-

- -
-
help.promoDataEmpty#98f6ac75 expires:int = help.PromoData;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
expiresintRe-fetch PSA/MTProxy info after the specified number of seconds
-

Type

-

help.PromoData

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.recentMeUrls b/data/core.telegram.org/constructor/help.recentMeUrls deleted file mode 100644 index d3941a8020..0000000000 --- a/data/core.telegram.org/constructor/help.recentMeUrls +++ /dev/null @@ -1,157 +0,0 @@ - - - - - help.recentMeUrls - - - - - - - - - - - - - -
- -
-
-
- -

help.recentMeUrls

- -

Recent t.me URLs

-

- -
-
help.recentMeUrls#e0310d7 urls:Vector<RecentMeUrl> chats:Vector<Chat> users:Vector<User> = help.RecentMeUrls;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlsVector<RecentMeUrl>URLs
chatsVector<Chat>Chats
usersVector<User>Users
-

Type

-

help.RecentMeUrls

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.support b/data/core.telegram.org/constructor/help.support deleted file mode 100644 index 9fd3a27f7d..0000000000 --- a/data/core.telegram.org/constructor/help.support +++ /dev/null @@ -1,152 +0,0 @@ - - - - - help.support - - - - - - - - - - - - - -
- -
-
-
- -

help.support

- -

Info on support user.

-

- -
-
help.support#17c6b5f6 phone_number:string user:User = help.Support;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number
userUserUser
-

Type

-

help.Support

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.supportName b/data/core.telegram.org/constructor/help.supportName deleted file mode 100644 index 1678b3093b..0000000000 --- a/data/core.telegram.org/constructor/help.supportName +++ /dev/null @@ -1,147 +0,0 @@ - - - - - help.supportName - - - - - - - - - - - - - -
- -
-
-
- -

help.supportName

- -

Localized name for telegram support

-

- -
-
help.supportName#8c05f1c9 name:string = help.SupportName;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
namestringLocalized name
-

Type

-

help.SupportName

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.termsOfService b/data/core.telegram.org/constructor/help.termsOfService deleted file mode 100644 index a541b36b04..0000000000 --- a/data/core.telegram.org/constructor/help.termsOfService +++ /dev/null @@ -1,175 +0,0 @@ - - - - - help.termsOfService - - - - - - - - - - - - - -
- -
-
-
- -

help.termsOfService

- -

Info about the latest telegram Terms Of Service

-

- -
-
help.termsOfService#780a0310 flags:# popup:flags.0?true id:DataJSON text:string entities:Vector<MessageEntity> min_age_confirm:flags.1?int = help.TermsOfService;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
popupflags.0?trueWhether a prompt must be showed to the user, in order to accept the new terms.
idDataJSONID of the new terms
textstringText of the new terms
entitiesVector<MessageEntity>Message entities for styled text
min_age_confirmflags.1?intMinimum age required to sign up to telegram, the user must confirm that they is older than the minimum age.
-

Type

-

help.TermsOfService

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.termsOfServiceUpdate b/data/core.telegram.org/constructor/help.termsOfServiceUpdate deleted file mode 100644 index f8a6a726cf..0000000000 --- a/data/core.telegram.org/constructor/help.termsOfServiceUpdate +++ /dev/null @@ -1,157 +0,0 @@ - - - - - help.termsOfServiceUpdate - - - - - - - - - - - - - -
- -
-
-
- -

help.termsOfServiceUpdate

- -

Info about an update of telegram's terms of service. If the terms of service are declined, then the account.deleteAccount method should be called with the reason "Decline ToS update"

-

- -
-
help.termsOfServiceUpdate#28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
expiresintNew TOS updates will have to be queried using help.getTermsOfServiceUpdate in expires seconds
terms_of_servicehelp.TermsOfServiceNew terms of service
-

Type

-

help.TermsOfServiceUpdate

-

Related pages

-

help.getTermsOfServiceUpdate

-

Look for updates of telegram's terms of service

-

account.deleteAccount

-

Delete the user's account from the telegram servers. Can be used, for example, to delete the account of a user that provided the login code, but forgot the 2FA password and no recovery method is configured.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.termsOfServiceUpdateEmpty b/data/core.telegram.org/constructor/help.termsOfServiceUpdateEmpty deleted file mode 100644 index 9e7c7a5816..0000000000 --- a/data/core.telegram.org/constructor/help.termsOfServiceUpdateEmpty +++ /dev/null @@ -1,150 +0,0 @@ - - - - - help.termsOfServiceUpdateEmpty - - - - - - - - - - - - - -
- -
-
-
- -

help.termsOfServiceUpdateEmpty

- -

No changes were made to telegram's terms of service

-

- -
-
help.termsOfServiceUpdateEmpty#e3309f7f expires:int = help.TermsOfServiceUpdate;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
expiresintNew TOS updates will have to be queried using help.getTermsOfServiceUpdate in expires seconds
-

Type

-

help.TermsOfServiceUpdate

-

Related pages

-

help.getTermsOfServiceUpdate

-

Look for updates of telegram's terms of service

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.userInfo b/data/core.telegram.org/constructor/help.userInfo deleted file mode 100644 index 59adcc9e18..0000000000 --- a/data/core.telegram.org/constructor/help.userInfo +++ /dev/null @@ -1,165 +0,0 @@ - - - - - help.userInfo - - - - - - - - - - - - - -
- -
-
-
- -

help.userInfo

- -

Internal use

-

- -
-
help.userInfo#1eb3758 message:string entities:Vector<MessageEntity> author:string date:int = help.UserInfo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messagestringInfo
entitiesVector<MessageEntity>Message entities for styled text
authorstringAuthor
dateintDate
-

Type

-

help.UserInfo

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/help.userInfoEmpty b/data/core.telegram.org/constructor/help.userInfoEmpty deleted file mode 100644 index 785d3211d1..0000000000 --- a/data/core.telegram.org/constructor/help.userInfoEmpty +++ /dev/null @@ -1,132 +0,0 @@ - - - - - help.userInfoEmpty - - - - - - - - - - - - - -
- -
-
-
- -

help.userInfoEmpty

- -

Internal use

-

- -
-
help.userInfoEmpty#f3ae2eed = help.UserInfo;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

help.UserInfo

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/highScore.html b/data/core.telegram.org/constructor/highScore.html deleted file mode 100644 index f7d137486c..0000000000 --- a/data/core.telegram.org/constructor/highScore.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - highScore - - - - - - - - - - - - - -
- -
-
-
- -

highScore

- -

Game highscore

-

- -
-
highScore#73a379eb pos:int user_id:long score:int = HighScore;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
posintPosition in highscore list
user_idlongUser ID
scoreintScore
-

Type

-

HighScore

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/importedContact.html b/data/core.telegram.org/constructor/importedContact.html deleted file mode 100644 index 5c4edd048d..0000000000 --- a/data/core.telegram.org/constructor/importedContact.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - importedContact - - - - - - - - - - - - - -
- -
-
-
- -

importedContact

- -

Successfully imported contact.

-

- -
-
importedContact#c13e3c50 user_id:long client_id:long = ImportedContact;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser identifier
client_idlongThe contact's client identifier (passed to one of the InputContact constructors)
-

Type

-

ImportedContact

-

Related pages

-

InputContact

-

Object defines a contact from the user's phonebook.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inlineBotSwitchPM.html b/data/core.telegram.org/constructor/inlineBotSwitchPM.html deleted file mode 100644 index 6d3591f322..0000000000 --- a/data/core.telegram.org/constructor/inlineBotSwitchPM.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inlineBotSwitchPM - - - - - - - - - - - - - -
- -
-
-
- -

inlineBotSwitchPM

- -

The bot requested the user to message him in private

-

- -
-
inlineBotSwitchPM#3c20629f text:string start_param:string = InlineBotSwitchPM;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textstringText for the button that switches the user to a private chat with the bot and sends the bot a start message with the parameter start_parameter (can be empty)
start_paramstringThe parameter for the /start parameter
-

Type

-

InlineBotSwitchPM

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html b/data/core.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html deleted file mode 100644 index 5b9493c1d7..0000000000 --- a/data/core.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - inlineQueryPeerTypeBroadcast - - - - - - - - - - - - - -
- -
-
-
- -

inlineQueryPeerTypeBroadcast

- -

The inline query was sent in a channel

-

- -
-
inlineQueryPeerTypeBroadcast#6334ee9a = InlineQueryPeerType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InlineQueryPeerType

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inlineQueryPeerTypeChat.html b/data/core.telegram.org/constructor/inlineQueryPeerTypeChat.html deleted file mode 100644 index a2965a58d3..0000000000 --- a/data/core.telegram.org/constructor/inlineQueryPeerTypeChat.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - inlineQueryPeerTypeChat - - - - - - - - - - - - - -
- -
-
-
- -

inlineQueryPeerTypeChat

- -

The inline query was sent in a chat

-

- -
-
inlineQueryPeerTypeChat#d766c50a = InlineQueryPeerType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InlineQueryPeerType

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html b/data/core.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html deleted file mode 100644 index 34576da4ac..0000000000 --- a/data/core.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - inlineQueryPeerTypeMegagroup - - - - - - - - - - - - - -
- -
-
-
- -

inlineQueryPeerTypeMegagroup

- -

The inline query was sent in a supergroup

-

- -
-
inlineQueryPeerTypeMegagroup#5ec4be43 = InlineQueryPeerType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InlineQueryPeerType

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inlineQueryPeerTypeSameBotPM.html b/data/core.telegram.org/constructor/inlineQueryPeerTypeSameBotPM.html deleted file mode 100644 index 22b1e8a59c..0000000000 --- a/data/core.telegram.org/constructor/inlineQueryPeerTypeSameBotPM.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inlineQueryPeerTypeSameBotPM - - - - - - - - - - - - - -
- -
-
-
- -

inlineQueryPeerTypeSameBotPM

- -

The inline query was sent in a private chat with the bot itself

-

- -
-
inlineQueryPeerTypeSameBotPM#3081ed9d = InlineQueryPeerType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InlineQueryPeerType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputAppEvent.html b/data/core.telegram.org/constructor/inputAppEvent.html deleted file mode 100644 index dbff673a46..0000000000 --- a/data/core.telegram.org/constructor/inputAppEvent.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputAppEvent - - - - - - - - - - - - - -
- -
-
-
- -

inputAppEvent

- -

Event that occured in the application.

-

- -
-
inputAppEvent#1d1b1245 time:double type:string peer:long data:JSONValue = InputAppEvent;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
timedoubleClient's exact timestamp for the event
typestringType of event
peerlongArbitrary numeric value for more convenient selection of certain event types, or events referring to a certain object
dataJSONValueDetails of the event
-

Type

-

InputAppEvent

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineMessageGame.html b/data/core.telegram.org/constructor/inputBotInlineMessageGame.html deleted file mode 100644 index 4d56e62a47..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineMessageGame.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputBotInlineMessageGame - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageGame

- -

A game

-

- -
-
inputBotInlineMessageGame#4b425864 flags:# reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

InputBotInlineMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineMessageID.html b/data/core.telegram.org/constructor/inputBotInlineMessageID.html deleted file mode 100644 index 19b00417b6..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineMessageID.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - inputBotInlineMessageID - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageID

- -

Represents a sent inline message from the perspective of a bot (legacy constructor)

-

- -
-
inputBotInlineMessageID#890c3d89 dc_id:int id:long access_hash:long = InputBotInlineMessageID;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
dc_idintDC ID to use when working with this inline message
idlongID of message, contains both the (32-bit, legacy) owner ID and the message ID, used only for Bot API backwards compatibility with 32-bit user ID.
access_hashlongAccess hash of message
-

Type

-

InputBotInlineMessageID

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineMessageID64.html b/data/core.telegram.org/constructor/inputBotInlineMessageID64.html deleted file mode 100644 index e00f17ecde..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineMessageID64.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputBotInlineMessageID64 - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageID64

- -

Represents a sent inline message from the perspective of a bot

-

- -
-
inputBotInlineMessageID64#b6d915d7 dc_id:int owner_id:long id:int access_hash:long = InputBotInlineMessageID;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
dc_idintDC ID to use when working with this inline message
owner_idlongID of the owner of this message
idintID of message
access_hashlongAccess hash of message
-

Type

-

InputBotInlineMessageID

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineMessageMediaAuto.html b/data/core.telegram.org/constructor/inputBotInlineMessageMediaAuto.html deleted file mode 100644 index e486db81c4..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineMessageMediaAuto.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - inputBotInlineMessageMediaAuto - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageMediaAuto

- -

A media

-

- -
-
inputBotInlineMessageMediaAuto#3380c786 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
messagestringCaption
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

InputBotInlineMessage

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineMessageMediaContact.html b/data/core.telegram.org/constructor/inputBotInlineMessageMediaContact.html deleted file mode 100644 index 97e3df4376..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineMessageMediaContact.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - inputBotInlineMessageMediaContact - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageMediaContact

- -

A contact

-

- -
-
inputBotInlineMessageMediaContact#a6edbffd flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
phone_numberstringPhone number
first_namestringFirst name
last_namestringLast name
vcardstringVCard info
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

InputBotInlineMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineMessageMediaGeo.html b/data/core.telegram.org/constructor/inputBotInlineMessageMediaGeo.html deleted file mode 100644 index b65b63cb30..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineMessageMediaGeo.html +++ /dev/null @@ -1,175 +0,0 @@ - - - - - inputBotInlineMessageMediaGeo - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageMediaGeo

- -

Geolocation

-

- -
-
inputBotInlineMessageMediaGeo#96929a85 flags:# geo_point:InputGeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
geo_pointInputGeoPointGeolocation
headingflags.0?intFor live locations, a direction in which the location moves, in degrees; 1-360
periodflags.1?intValidity period
proximity_notification_radiusflags.3?intFor live locations, a maximum distance to another chat member for proximity alerts, in meters (0-100000)
reply_markupflags.2?ReplyMarkupReply markup for bot/inline keyboards
-

Type

-

InputBotInlineMessage

-

Related pages

-

Live geolocation

-

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineMessageMediaInvoice.html b/data/core.telegram.org/constructor/inputBotInlineMessageMediaInvoice.html deleted file mode 100644 index da702cb351..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineMessageMediaInvoice.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - inputBotInlineMessageMediaInvoice - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageMediaInvoice

- -

An invoice

-

- -
-
inputBotInlineMessageMediaInvoice#d7e78225 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
titlestringProduct name, 1-32 characters
descriptionstringProduct description, 1-255 characters
photoflags.0?InputWebDocumentInvoice photo
invoiceInvoiceThe invoice
payloadbytesBot-defined invoice payload, 1-128 bytes. This will not be displayed to the user, use for your internal processes.
providerstringPayments provider token, obtained via Botfather
provider_dataDataJSONA JSON-serialized object for data about the invoice, which will be shared with the payment provider. A detailed description of the required fields should be provided by the payment provider.
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

InputBotInlineMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineMessageMediaVenue.html b/data/core.telegram.org/constructor/inputBotInlineMessageMediaVenue.html deleted file mode 100644 index a9df186da6..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineMessageMediaVenue.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - inputBotInlineMessageMediaVenue - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageMediaVenue

- -

Venue

-

- -
-
inputBotInlineMessageMediaVenue#417bbf11 flags:# geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
geo_pointInputGeoPointGeolocation
titlestringVenue name
addressstringAddress
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
venue_typestringVenue type in the provider's database
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

InputBotInlineMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineMessageText.html b/data/core.telegram.org/constructor/inputBotInlineMessageText.html deleted file mode 100644 index 7519809734..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineMessageText.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - inputBotInlineMessageText - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageText

- -

Simple text message

-

- -
-
inputBotInlineMessageText#3dcd7a87 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.0?trueDisable webpage preview
messagestringMessage
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

InputBotInlineMessage

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineResult.html b/data/core.telegram.org/constructor/inputBotInlineResult.html deleted file mode 100644 index d054d480a7..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineResult.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - inputBotInlineResult - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineResult

- -

An inline bot result

-

- -
-
inputBotInlineResult#88bf9319 flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?InputWebDocument content:flags.5?InputWebDocument send_message:InputBotInlineMessage = InputBotInlineResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idstringID of result
typestringResult type (see bot API docs)
titleflags.1?stringResult title
descriptionflags.2?stringResult description
urlflags.3?stringURL of result
thumbflags.4?InputWebDocumentThumbnail for result
contentflags.5?InputWebDocumentResult contents
send_messageInputBotInlineMessageMessage to send when the result is selected
-

Type

-

InputBotInlineResult

-

Related pages

-

Telegram Bot API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineResultDocument.html b/data/core.telegram.org/constructor/inputBotInlineResultDocument.html deleted file mode 100644 index 7201913625..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineResultDocument.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - inputBotInlineResultDocument - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineResultDocument

- -

Document (media of any type except for photos)

-

- -
-
inputBotInlineResultDocument#fff8fdc4 flags:# id:string type:string title:flags.1?string description:flags.2?string document:InputDocument send_message:InputBotInlineMessage = InputBotInlineResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idstringResult ID
typestringResult type (see bot API docs)
titleflags.1?stringResult title
descriptionflags.2?stringResult description
documentInputDocumentDocument to send
send_messageInputBotInlineMessageMessage to send when the result is selected
-

Type

-

InputBotInlineResult

-

Related pages

-

Telegram Bot API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineResultGame.html b/data/core.telegram.org/constructor/inputBotInlineResultGame.html deleted file mode 100644 index ce75d7eb22..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineResultGame.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - inputBotInlineResultGame - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineResultGame

- -

Game

-

- -
-
inputBotInlineResultGame#4fa417f2 id:string short_name:string send_message:InputBotInlineMessage = InputBotInlineResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idstringResult ID
short_namestringGame short name
send_messageInputBotInlineMessageMessage to send when the result is selected
-

Type

-

InputBotInlineResult

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputBotInlineResultPhoto.html b/data/core.telegram.org/constructor/inputBotInlineResultPhoto.html deleted file mode 100644 index cb0d8308c0..0000000000 --- a/data/core.telegram.org/constructor/inputBotInlineResultPhoto.html +++ /dev/null @@ -1,164 +0,0 @@ - - - - - inputBotInlineResultPhoto - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineResultPhoto

- -

Photo

-

- -
-
inputBotInlineResultPhoto#a8d864a7 id:string type:string photo:InputPhoto send_message:InputBotInlineMessage = InputBotInlineResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idstringResult ID
typestringResult type (see bot API docs)
photoInputPhotoPhoto to send
send_messageInputBotInlineMessageMessage to send when the result is selected
-

Type

-

InputBotInlineResult

-

Related pages

-

Telegram Bot API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputChannel.html b/data/core.telegram.org/constructor/inputChannel.html deleted file mode 100644 index 446f12351e..0000000000 --- a/data/core.telegram.org/constructor/inputChannel.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputChannel - - - - - - - - - - - - - -
- -
-
-
- -

inputChannel

- -

Represents a channel

-

- -
-
inputChannel#f35aec28 channel_id:long access_hash:long = InputChannel;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idlongChannel ID
access_hashlongAccess hash taken from the channel constructor
-

Type

-

InputChannel

-

Related pages

-

channel

-

Channel/supergroup info

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputChannelEmpty.html b/data/core.telegram.org/constructor/inputChannelEmpty.html deleted file mode 100644 index cbda28bc2a..0000000000 --- a/data/core.telegram.org/constructor/inputChannelEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputChannelEmpty - - - - - - - - - - - - - -
- -
-
-
- -

inputChannelEmpty

- -

Represents the absence of a channel

-

- -
-
inputChannelEmpty#ee8c1e86 = InputChannel;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputChannel

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputChannelFromMessage.html b/data/core.telegram.org/constructor/inputChannelFromMessage.html deleted file mode 100644 index c35d28fc4d..0000000000 --- a/data/core.telegram.org/constructor/inputChannelFromMessage.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - inputChannelFromMessage - - - - - - - - - - - - - -
- -
-
-
- -

inputChannelFromMessage

- -

Defines a min channel that was seen in a certain message of a certain chat.

-

- -
-
inputChannelFromMessage#5b934f9d peer:InputPeer msg_id:int channel_id:long = InputChannel;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat where the channel was seen
msg_idintThe message ID in the chat where the channel was seen
channel_idlongThe channel ID
-

Type

-

InputChannel

-

Related pages

-

Min constructors

-

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputChatPhotoEmpty.html b/data/core.telegram.org/constructor/inputChatPhotoEmpty.html deleted file mode 100644 index 0bbacd38ac..0000000000 --- a/data/core.telegram.org/constructor/inputChatPhotoEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputChatPhotoEmpty - - - - - - - - - - - - - -
- -
-
-
- -

inputChatPhotoEmpty

- -

Empty constructor, remove group photo.

-

- -
-
inputChatPhotoEmpty#1ca48f57 = InputChatPhoto;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputChatPhoto

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputChatUploadedPhoto.html b/data/core.telegram.org/constructor/inputChatUploadedPhoto.html deleted file mode 100644 index 9c2878c525..0000000000 --- a/data/core.telegram.org/constructor/inputChatUploadedPhoto.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - inputChatUploadedPhoto - - - - - - - - - - - - - -
- -
-
-
- -

inputChatUploadedPhoto

- -

New photo to be set as group profile photo.

-

- -
-
inputChatUploadedPhoto#c642724e flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = InputChatPhoto;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
fileflags.0?InputFileFile saved in parts using the method upload.saveFilePart
videoflags.1?InputFileSquare video for animated profile picture
video_start_tsflags.2?doubleTimestamp that should be shown as static preview to the user (seconds)
-

Type

-

InputChatPhoto

-

Related pages

-

upload.saveFilePart

-

Saves a part of file for futher sending to one of the methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputCheckPasswordEmpty.html b/data/core.telegram.org/constructor/inputCheckPasswordEmpty.html deleted file mode 100644 index 6ee3bb2418..0000000000 --- a/data/core.telegram.org/constructor/inputCheckPasswordEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputCheckPasswordEmpty - - - - - - - - - - - - - -
- -
-
-
- -

inputCheckPasswordEmpty

- -

There is no password

-

- -
-
inputCheckPasswordEmpty#9880f658 = InputCheckPasswordSRP;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputCheckPasswordSRP

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputCheckPasswordSRP.html b/data/core.telegram.org/constructor/inputCheckPasswordSRP.html deleted file mode 100644 index c10f94221e..0000000000 --- a/data/core.telegram.org/constructor/inputCheckPasswordSRP.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - inputCheckPasswordSRP - - - - - - - - - - - - - -
- -
-
-
- -

inputCheckPasswordSRP

- -

Constructor for checking the validity of a 2FA SRP password (see SRP)

-

- -
-
inputCheckPasswordSRP#d27ff082 srp_id:long A:bytes M1:bytes = InputCheckPasswordSRP;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
srp_idlongSRP ID
AbytesA parameter (see SRP)
M1bytesM1 parameter (see SRP)
-

Type

-

InputCheckPasswordSRP

-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputClientProxy.html b/data/core.telegram.org/constructor/inputClientProxy.html deleted file mode 100644 index 622a381c94..0000000000 --- a/data/core.telegram.org/constructor/inputClientProxy.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - inputClientProxy - - - - - - - - - - - - - -
- -
-
-
- -

inputClientProxy

- -

Info about an MTProxy used to connect.

-

- -
-
inputClientProxy#75588b3f address:string port:int = InputClientProxy;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
addressstringProxy address
portintProxy port
-

Type

-

InputClientProxy

-

Related pages

-

MTProto transports

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputDialogPeer.html b/data/core.telegram.org/constructor/inputDialogPeer.html deleted file mode 100644 index f2f30e9651..0000000000 --- a/data/core.telegram.org/constructor/inputDialogPeer.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputDialogPeer - - - - - - - - - - - - - -
- -
-
-
- -

inputDialogPeer

- -

A peer

-

- -
-
inputDialogPeer#fcaafeb7 peer:InputPeer = InputDialogPeer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
-

Type

-

InputDialogPeer

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputDialogPeerFolder.html b/data/core.telegram.org/constructor/inputDialogPeerFolder.html deleted file mode 100644 index ac4abe8a2e..0000000000 --- a/data/core.telegram.org/constructor/inputDialogPeerFolder.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - inputDialogPeerFolder - - - - - - - - - - - - - -
- -
-
-
- -

inputDialogPeerFolder

- -

All peers in a peer folder

-

- -
-
inputDialogPeerFolder#64600527 folder_id:int = InputDialogPeer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
folder_idintPeer folder ID, for more info click here
-

Type

-

InputDialogPeer

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputDocument.html b/data/core.telegram.org/constructor/inputDocument.html deleted file mode 100644 index 8e1427d141..0000000000 --- a/data/core.telegram.org/constructor/inputDocument.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputDocument - - - - - - - - - - - - - -
- -
-
-
- -

inputDocument

- -

Defines a video for subsequent interaction.

-

- -
-
inputDocument#1abfb575 id:long access_hash:long file_reference:bytes = InputDocument;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongDocument ID
access_hashlongaccess_hash parameter from the document constructor
file_referencebytesFile reference
-

Type

-

InputDocument

-

Related pages

-

document

-

Document

-

File references

-

How to handle file references.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputDocumentEmpty.html b/data/core.telegram.org/constructor/inputDocumentEmpty.html deleted file mode 100644 index fd5b82388f..0000000000 --- a/data/core.telegram.org/constructor/inputDocumentEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputDocumentEmpty - - - - - - - - - - - - - -
- -
-
-
- -

inputDocumentEmpty

- -

Empty constructor.

-

- -
-
inputDocumentEmpty#72f0eaae = InputDocument;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputDocument

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputDocumentFileLocation.html b/data/core.telegram.org/constructor/inputDocumentFileLocation.html deleted file mode 100644 index 8646345423..0000000000 --- a/data/core.telegram.org/constructor/inputDocumentFileLocation.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - inputDocumentFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputDocumentFileLocation

- -

Document location (video, voice, audio, basically every type except photo)

-

- -
-
inputDocumentFileLocation#bad07584 id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongDocument ID
access_hashlongaccess_hash parameter from the document constructor
file_referencebytesFile reference
thumb_sizestringThumbnail size to download the thumbnail
-

Type

-

InputFileLocation

-

Related pages

-

document

-

Document

-

File references

-

How to handle file references.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputEncryptedChat.html b/data/core.telegram.org/constructor/inputEncryptedChat.html deleted file mode 100644 index 5aa25b5c19..0000000000 --- a/data/core.telegram.org/constructor/inputEncryptedChat.html +++ /dev/null @@ -1,159 +0,0 @@ - - - - - inputEncryptedChat - - - - - - - - - - - - - -
- -
-
-
- -

inputEncryptedChat

- -

Creates an encrypted chat.

-

- -
-
inputEncryptedChat#f141b5e1 chat_id:int access_hash:long = InputEncryptedChat;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idintChat ID
access_hashlongChecking sum from constructor encryptedChat, encryptedChatWaiting or encryptedChatRequested
-

Type

-

InputEncryptedChat

-

Related pages

-

encryptedChat

-

Encrypted chat

-

encryptedChatWaiting

-

Chat waiting for approval of second participant.

-

encryptedChatRequested

-

Request to create an encrypted chat.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputEncryptedFile.html b/data/core.telegram.org/constructor/inputEncryptedFile.html deleted file mode 100644 index da625b6136..0000000000 --- a/data/core.telegram.org/constructor/inputEncryptedFile.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputEncryptedFile - - - - - - - - - - - - - -
- -
-
-
- -

inputEncryptedFile

- -

Sets forwarded encrypted file for attachment.

-

- -
-
inputEncryptedFile#5a17b5e5 id:long access_hash:long = InputEncryptedFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongFile ID, value of id parameter from encryptedFile
access_hashlongChecking sum, value of access_hash parameter from encryptedFile
-

Type

-

InputEncryptedFile

-

Related pages

-

encryptedFile

-

Encrypted file.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputEncryptedFileBigUploaded.html b/data/core.telegram.org/constructor/inputEncryptedFileBigUploaded.html deleted file mode 100644 index 99734c28a4..0000000000 --- a/data/core.telegram.org/constructor/inputEncryptedFileBigUploaded.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - inputEncryptedFileBigUploaded - - - - - - - - - - - - - -
- -
-
-
- -

inputEncryptedFileBigUploaded

- -

Assigns a new big encrypted file (over 10Mb in size), saved in parts using the method upload.saveBigFilePart.

-

- -
-
inputEncryptedFileBigUploaded#2dc173c8 id:long parts:int key_fingerprint:int = InputEncryptedFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongRandom file id, created by the client
partsintNumber of saved parts
key_fingerprintint32-bit imprint of the key used to encrypt the file
-

Type

-

InputEncryptedFile

-

Related pages

-

upload.saveBigFilePart

-

Saves a part of a large file (over 10Mb in size) to be later passed to one of the methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputEncryptedFileEmpty.html b/data/core.telegram.org/constructor/inputEncryptedFileEmpty.html deleted file mode 100644 index d4ff3e220e..0000000000 --- a/data/core.telegram.org/constructor/inputEncryptedFileEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputEncryptedFileEmpty - - - - - - - - - - - - - -
- -
-
-
- -

inputEncryptedFileEmpty

- -

Empty constructor.

-

- -
-
inputEncryptedFileEmpty#1837c364 = InputEncryptedFile;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputEncryptedFile

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputEncryptedFileLocation.html b/data/core.telegram.org/constructor/inputEncryptedFileLocation.html deleted file mode 100644 index 9cbf818169..0000000000 --- a/data/core.telegram.org/constructor/inputEncryptedFileLocation.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputEncryptedFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputEncryptedFileLocation

- -

Location of encrypted secret chat file.

-

- -
-
inputEncryptedFileLocation#f5235d55 id:long access_hash:long = InputFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongFile ID, id parameter value from encryptedFile
access_hashlongChecksum, access_hash parameter value from encryptedFile
-

Type

-

InputFileLocation

-

Related pages

-

encryptedFile

-

Encrypted file.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputEncryptedFileUploaded.html b/data/core.telegram.org/constructor/inputEncryptedFileUploaded.html deleted file mode 100644 index 9b74ed857d..0000000000 --- a/data/core.telegram.org/constructor/inputEncryptedFileUploaded.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputEncryptedFileUploaded - - - - - - - - - - - - - -
- -
-
-
- -

inputEncryptedFileUploaded

- -

Sets new encrypted file saved by parts using upload.saveFilePart method.

-

- -
-
inputEncryptedFileUploaded#64bd0306 id:long parts:int md5_checksum:string key_fingerprint:int = InputEncryptedFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongRandom file ID created by clien
partsintNumber of saved parts
md5_checksumstringIn case md5-HASH of the (already encrypted) file was transmitted, file content will be checked prior to use
key_fingerprintint32-bit fingerprint of the key used to encrypt a file
-

Type

-

InputEncryptedFile

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputFile.html b/data/core.telegram.org/constructor/inputFile.html deleted file mode 100644 index 1e85ee5228..0000000000 --- a/data/core.telegram.org/constructor/inputFile.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - inputFile - - - - - - - - - - - - - -
- -
-
-
- -

inputFile

- -

Defines a file saved in parts using the method upload.saveFilePart.

-

- -
-
inputFile#f52ff27f id:long parts:int name:string md5_checksum:string = InputFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongRandom file identifier created by the client
partsintNumber of parts saved
namestringFull name of the file
md5_checksumstringIn case the file's md5-hash was passed, contents of the file will be checked prior to use
-

Type

-

InputFile

-

Related pages

-

upload.saveFilePart

-

Saves a part of file for futher sending to one of the methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputFileBig.html b/data/core.telegram.org/constructor/inputFileBig.html deleted file mode 100644 index c173b0a37d..0000000000 --- a/data/core.telegram.org/constructor/inputFileBig.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - inputFileBig - - - - - - - - - - - - - -
- -
-
-
- -

inputFileBig

- -

Assigns a big file (over 10Mb in size), saved in part using the method upload.saveBigFilePart.

-

- -
-
inputFileBig#fa4f0bb5 id:long parts:int name:string = InputFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongRandom file id, created by the client
partsintNumber of parts saved
namestringFull file name
-

Type

-

InputFile

-

Related pages

-

upload.saveBigFilePart

-

Saves a part of a large file (over 10Mb in size) to be later passed to one of the methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputFileLocation.html b/data/core.telegram.org/constructor/inputFileLocation.html deleted file mode 100644 index 80d6f2e22e..0000000000 --- a/data/core.telegram.org/constructor/inputFileLocation.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - inputFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputFileLocation

- -

DEPRECATED location of a photo

-

- -
-
inputFileLocation#dfdaabe1 volume_id:long local_id:int secret:long file_reference:bytes = InputFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
volume_idlongServer volume
local_idintFile identifier
secretlongCheck sum to access the file
file_referencebytesFile reference
-

Type

-

InputFileLocation

-

Related pages

-

File references

-

How to handle file references.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputFolderPeer.html b/data/core.telegram.org/constructor/inputFolderPeer.html deleted file mode 100644 index 0e6afeeef7..0000000000 --- a/data/core.telegram.org/constructor/inputFolderPeer.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputFolderPeer - - - - - - - - - - - - - -
- -
-
-
- -

inputFolderPeer

- -

Peer in a folder

-

- -
-
inputFolderPeer#fbd2c296 peer:InputPeer folder_id:int = InputFolderPeer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
folder_idintPeer folder ID, for more info click here
-

Type

-

InputFolderPeer

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputGameID.html b/data/core.telegram.org/constructor/inputGameID.html deleted file mode 100644 index d651626822..0000000000 --- a/data/core.telegram.org/constructor/inputGameID.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputGameID - - - - - - - - - - - - - -
- -
-
-
- -

inputGameID

- -

Indicates an already sent game

-

- -
-
inputGameID#32c3e77 id:long access_hash:long = InputGame;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlonggame ID from Game constructor
access_hashlongaccess hash from Game constructor
-

Type

-

InputGame

-

Related pages

-

Game

-

Indicates an already sent game

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputGameShortName.html b/data/core.telegram.org/constructor/inputGameShortName.html deleted file mode 100644 index 300b20232b..0000000000 --- a/data/core.telegram.org/constructor/inputGameShortName.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputGameShortName - - - - - - - - - - - - - -
- -
-
-
- -

inputGameShortName

- -

Game by short name

-

- -
-
inputGameShortName#c331e80a bot_id:InputUser short_name:string = InputGame;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
bot_idInputUserThe bot that provides the game
short_namestringThe game's short name
-

Type

-

InputGame

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputGeoPoint.html b/data/core.telegram.org/constructor/inputGeoPoint.html deleted file mode 100644 index 5f8ae96eaa..0000000000 --- a/data/core.telegram.org/constructor/inputGeoPoint.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputGeoPoint - - - - - - - - - - - - - -
- -
-
-
- -

inputGeoPoint

- -

Defines a GeoPoint by its coordinates.

-

- -
-
inputGeoPoint#48222faf flags:# lat:double long:double accuracy_radius:flags.0?int = InputGeoPoint;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
latdoubleLatitide
longdoubleLongtitude
accuracy_radiusflags.0?intThe estimated horizontal accuracy of the location, in meters; as defined by the sender.
-

Type

-

InputGeoPoint

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputGeoPointEmpty.html b/data/core.telegram.org/constructor/inputGeoPointEmpty.html deleted file mode 100644 index ecda414917..0000000000 --- a/data/core.telegram.org/constructor/inputGeoPointEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputGeoPointEmpty - - - - - - - - - - - - - -
- -
-
-
- -

inputGeoPointEmpty

- -

Empty GeoPoint constructor.

-

- -
-
inputGeoPointEmpty#e4c123d6 = InputGeoPoint;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputGeoPoint

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputGroupCall.html b/data/core.telegram.org/constructor/inputGroupCall.html deleted file mode 100644 index 30b035aa84..0000000000 --- a/data/core.telegram.org/constructor/inputGroupCall.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

inputGroupCall

- -

Points to a specific group call

-

- -
-
inputGroupCall#d8aa840f id:long access_hash:long = InputGroupCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongGroup call ID
access_hashlongGroup call access hash
-

Type

-

InputGroupCall

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputGroupCallStream.html b/data/core.telegram.org/constructor/inputGroupCallStream.html deleted file mode 100644 index f94ce73d66..0000000000 --- a/data/core.telegram.org/constructor/inputGroupCallStream.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - inputGroupCallStream - - - - - - - - - - - - - -
- -
-
-
- -

inputGroupCallStream

- -

Chunk of a livestream

-

- -
-
inputGroupCallStream#598a92a flags:# call:InputGroupCall time_ms:long scale:int video_channel:flags.0?int video_quality:flags.0?int = InputFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
callInputGroupCallLivestream info
time_mslongTimestamp in milliseconds
scaleintSpecifies the duration of the video segment to fetch in milliseconds, by bitshifting 1000 to the right scale times: duration_ms := 1000 >> scale
video_channelflags.0?intSelected video channel
video_qualityflags.0?intSelected video quality (0 = lowest, 1 = medium, 2 = best)
-

Type

-

InputFileLocation

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputKeyboardButtonUrlAuth.html b/data/core.telegram.org/constructor/inputKeyboardButtonUrlAuth.html deleted file mode 100644 index 2de7853f5c..0000000000 --- a/data/core.telegram.org/constructor/inputKeyboardButtonUrlAuth.html +++ /dev/null @@ -1,176 +0,0 @@ - - - - - inputKeyboardButtonUrlAuth - - - - - - - - - - - - - -
- -
-
-
- -

inputKeyboardButtonUrlAuth

- -

Button to request a user to authorize via URL using Seamless Telegram Login.

-

- -
-
inputKeyboardButtonUrlAuth#d02e7fd4 flags:# request_write_access:flags.0?true text:string fwd_text:flags.1?string url:string bot:InputUser = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
request_write_accessflags.0?trueSet this flag to request the permission for your bot to send messages to the user.
textstringButton text
fwd_textflags.1?stringNew text of the button in forwarded messages.
urlstringAn HTTP URL to be opened with user authorization data added to the query string when the button is pressed. If the user refuses to provide authorization data, the original URL without information about the user will be opened. The data added is the same as described in Receiving authorization data.
NOTE: You must always check the hash of the received data to verify the authentication and the integrity of the data as described in Checking authorization.
botInputUserUsername of a bot, which will be used for user authorization. See Setting up a bot for more details. If not specified, the current bot's username will be assumed. The url's domain must be the same as the domain linked with the bot. See Linking your domain to the bot for more details.
-

Type

-

KeyboardButton

-

Related pages

-

Telegram Login Widget

-

messages.acceptUrlAuth

-

Use this to accept a Seamless Telegram Login authorization request, for more info click here »

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaContact.html b/data/core.telegram.org/constructor/inputMediaContact.html deleted file mode 100644 index 0cfb9daa93..0000000000 --- a/data/core.telegram.org/constructor/inputMediaContact.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputMediaContact - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaContact

- -

Phonebook contact

-

- -
-
inputMediaContact#f8ab7dfb phone_number:string first_name:string last_name:string vcard:string = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number
first_namestringContact's first name
last_namestringContact's last name
vcardstringContact vcard
-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaDice.html b/data/core.telegram.org/constructor/inputMediaDice.html deleted file mode 100644 index d4970073bd..0000000000 --- a/data/core.telegram.org/constructor/inputMediaDice.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - inputMediaDice - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaDice

- -

Send a dice-based animated sticker

-

- -
-
inputMediaDice#e66fbf7b emoticon:string = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
emoticonstringThe emoji, for now 🏀, 🎲 and 🎯 are supported
-

Type

-

InputMedia

-

Related pages

-

Dice

-

Telegram supports sending animated dice emojis.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaDocument.html b/data/core.telegram.org/constructor/inputMediaDocument.html deleted file mode 100644 index 72afc685b3..0000000000 --- a/data/core.telegram.org/constructor/inputMediaDocument.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputMediaDocument - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaDocument

- -

Forwarded document

-

- -
-
inputMediaDocument#33473058 flags:# id:InputDocument ttl_seconds:flags.0?int query:flags.1?string = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idInputDocumentThe document to be forwarded.
ttl_secondsflags.0?intTime to live of self-destructing document
queryflags.1?stringText query or emoji that was used by the user to find this sticker or GIF: used to improve search result relevance.
-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaDocumentExternal.html b/data/core.telegram.org/constructor/inputMediaDocumentExternal.html deleted file mode 100644 index fa2d260996..0000000000 --- a/data/core.telegram.org/constructor/inputMediaDocumentExternal.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - inputMediaDocumentExternal - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaDocumentExternal

- -

Document that will be downloaded by the telegram servers

-

- -
-
inputMediaDocumentExternal#fb52dc99 flags:# url:string ttl_seconds:flags.0?int = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
urlstringURL of the document
ttl_secondsflags.0?intSelf-destruct time to live of document
-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaEmpty.html b/data/core.telegram.org/constructor/inputMediaEmpty.html deleted file mode 100644 index 9134ab2239..0000000000 --- a/data/core.telegram.org/constructor/inputMediaEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMediaEmpty - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaEmpty

- -

Empty media content of a message.

-

- -
-
inputMediaEmpty#9664f57f = InputMedia;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaGame.html b/data/core.telegram.org/constructor/inputMediaGame.html deleted file mode 100644 index f48c578646..0000000000 --- a/data/core.telegram.org/constructor/inputMediaGame.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputMediaGame - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaGame

- -

A game

-

- -
-
inputMediaGame#d33f43f3 id:InputGame = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idInputGameThe game to forward
-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaGeoLive.html b/data/core.telegram.org/constructor/inputMediaGeoLive.html deleted file mode 100644 index 4b7c529d09..0000000000 --- a/data/core.telegram.org/constructor/inputMediaGeoLive.html +++ /dev/null @@ -1,175 +0,0 @@ - - - - - inputMediaGeoLive - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaGeoLive

- -

Live geolocation

-

- -
-
inputMediaGeoLive#971fa843 flags:# stopped:flags.0?true geo_point:InputGeoPoint heading:flags.2?int period:flags.1?int proximity_notification_radius:flags.3?int = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
stoppedflags.0?trueWhether sending of the geolocation was stopped
geo_pointInputGeoPointCurrent geolocation
headingflags.2?intFor live locations, a direction in which the location moves, in degrees; 1-360.
periodflags.1?intValidity period of the current location
proximity_notification_radiusflags.3?intFor live locations, a maximum distance to another chat member for proximity alerts, in meters (0-100000)
-

Type

-

InputMedia

-

Related pages

-

Live geolocation

-

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaGeoPoint.html b/data/core.telegram.org/constructor/inputMediaGeoPoint.html deleted file mode 100644 index 5a5dc83319..0000000000 --- a/data/core.telegram.org/constructor/inputMediaGeoPoint.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputMediaGeoPoint - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaGeoPoint

- -

Map.

-

- -
-
inputMediaGeoPoint#f9c44144 geo_point:InputGeoPoint = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
geo_pointInputGeoPointGeoPoint
-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaInvoice.html b/data/core.telegram.org/constructor/inputMediaInvoice.html deleted file mode 100644 index 453dc2c840..0000000000 --- a/data/core.telegram.org/constructor/inputMediaInvoice.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - inputMediaInvoice - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaInvoice

- -

Generated invoice of a bot payment

-

- -
-
inputMediaInvoice#d9799874 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON start_param:flags.1?string = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
titlestringProduct name, 1-32 characters
descriptionstringProduct description, 1-255 characters
photoflags.0?InputWebDocumentURL of the product photo for the invoice. Can be a photo of the goods or a marketing image for a service. People like it better when they see what they are paying for.
invoiceInvoiceThe actual invoice
payloadbytesBot-defined invoice payload, 1-128 bytes. This will not be displayed to the user, use for your internal processes.
providerstringPayments provider token, obtained via Botfather
provider_dataDataJSONJSON-encoded data about the invoice, which will be shared with the payment provider. A detailed description of required fields should be provided by the payment provider.
start_paramflags.1?stringStart parameter
-

Type

-

InputMedia

-

Related pages

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaPhoto.html b/data/core.telegram.org/constructor/inputMediaPhoto.html deleted file mode 100644 index 112d09c05b..0000000000 --- a/data/core.telegram.org/constructor/inputMediaPhoto.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - inputMediaPhoto - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaPhoto

- -

Forwarded photo

-

- -
-
inputMediaPhoto#b3ba0635 flags:# id:InputPhoto ttl_seconds:flags.0?int = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idInputPhotoPhoto to be forwarded
ttl_secondsflags.0?intTime to live in seconds of self-destructing photo
-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaPoll.html b/data/core.telegram.org/constructor/inputMediaPoll.html deleted file mode 100644 index f974f133c5..0000000000 --- a/data/core.telegram.org/constructor/inputMediaPoll.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - inputMediaPoll - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaPoll

- -

A poll

-

- -
-
inputMediaPoll#f94e5f1 flags:# poll:Poll correct_answers:flags.0?Vector<bytes> solution:flags.1?string solution_entities:flags.1?Vector<MessageEntity> = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
pollPollThe poll to send
correct_answersflags.0?Vector<bytes>Correct answer IDs (for quiz polls)
solutionflags.1?stringExplanation of quiz solution
solution_entitiesflags.1?Vector<MessageEntity>Message entities for styled text
-

Type

-

InputMedia

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaUploadedDocument.html b/data/core.telegram.org/constructor/inputMediaUploadedDocument.html deleted file mode 100644 index 8f8034f307..0000000000 --- a/data/core.telegram.org/constructor/inputMediaUploadedDocument.html +++ /dev/null @@ -1,190 +0,0 @@ - - - - - inputMediaUploadedDocument - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaUploadedDocument

- -

New document

-

- -
-
inputMediaUploadedDocument#5b38c6c1 flags:# nosound_video:flags.3?true force_file:flags.4?true file:InputFile thumb:flags.2?InputFile mime_type:string attributes:Vector<DocumentAttribute> stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
nosound_videoflags.3?trueWhether the specified document is a video file with no audio tracks (a GIF animation (even as MPEG4), for example)
force_fileflags.4?trueForce the media file to be uploaded as document
fileInputFileThe uploaded file
thumbflags.2?InputFileThumbnail of the document, uploaded as for the file
mime_typestringMIME type of document
attributesVector<DocumentAttribute>Attributes that specify the type of the document (video, audio, voice, sticker, etc.)
stickersflags.0?Vector<InputDocument>Attached stickers
ttl_secondsflags.1?intTime to live in seconds of self-destructing document
-

Type

-

InputMedia

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaUploadedPhoto.html b/data/core.telegram.org/constructor/inputMediaUploadedPhoto.html deleted file mode 100644 index 809c3dffe9..0000000000 --- a/data/core.telegram.org/constructor/inputMediaUploadedPhoto.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - inputMediaUploadedPhoto - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaUploadedPhoto

- -

Photo

-

- -
-
inputMediaUploadedPhoto#1e287d04 flags:# file:InputFile stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
fileInputFileThe uploaded file
stickersflags.0?Vector<InputDocument>Attached mask stickers
ttl_secondsflags.1?intTime to live in seconds of self-destructing photo
-

Type

-

InputMedia

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaUploadedThumbDocument.html b/data/core.telegram.org/constructor/inputMediaUploadedThumbDocument.html deleted file mode 100644 index 6f562d9add..0000000000 --- a/data/core.telegram.org/constructor/inputMediaUploadedThumbDocument.html +++ /dev/null @@ -1,176 +0,0 @@ - - - - - inputMediaUploadedThumbDocument - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaUploadedThumbDocument

- -

New document with a thumbnail.

-

- -
-
Constructor schema is available as of layer 22. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
fileInputFileDocument, saved in parts by using the methods upload.saveFilePart or upload.saveBigFilePart
thumbInputFileThumbnail file, saved in parts by using upload.saveFilePart
file_namestringFile name with extension
mime_typestringFile MIME-type
-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMediaVenue.html b/data/core.telegram.org/constructor/inputMediaVenue.html deleted file mode 100644 index b56966fc83..0000000000 --- a/data/core.telegram.org/constructor/inputMediaVenue.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - inputMediaVenue - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaVenue

- -

Can be used to send a venue geolocation.

-

- -
-
inputMediaVenue#c13d1c11 geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
geo_pointInputGeoPointGeolocation
titlestringVenue name
addressstringPhysical address of the venue
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
venue_typestringVenue type in the provider's database
-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessageCallbackQuery.html b/data/core.telegram.org/constructor/inputMessageCallbackQuery.html deleted file mode 100644 index 6afc34fe1e..0000000000 --- a/data/core.telegram.org/constructor/inputMessageCallbackQuery.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputMessageCallbackQuery - - - - - - - - - - - - - -
- -
-
-
- -

inputMessageCallbackQuery

- -

Used by bots for fetching information about the message that originated a callback query

-

- -
-
inputMessageCallbackQuery#acfa1a7e id:int query_id:long = InputMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idintMessage ID
query_idlongCallback query ID
-

Type

-

InputMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessageEntityMentionName.html b/data/core.telegram.org/constructor/inputMessageEntityMentionName.html deleted file mode 100644 index 7b8f9b9fcd..0000000000 --- a/data/core.telegram.org/constructor/inputMessageEntityMentionName.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputMessageEntityMentionName - - - - - - - - - - - - - -
- -
-
-
- -

inputMessageEntityMentionName

- -

Message entity that can be used to create a user user mention: received mentions use the messageEntityMentionName constructor, instead.

-

- -
-
inputMessageEntityMentionName#208e68c9 offset:int length:int user_id:InputUser = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
user_idInputUserIdentifier of the user that was mentioned
-

Type

-

MessageEntity

-

Related pages

-

Mentions

-

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

-

messageEntityMentionName

-

Message entity representing a user mention: for creating a mention use inputMessageEntityMentionName.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessageID.html b/data/core.telegram.org/constructor/inputMessageID.html deleted file mode 100644 index e963113d09..0000000000 --- a/data/core.telegram.org/constructor/inputMessageID.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputMessageID - - - - - - - - - - - - - -
- -
-
-
- -

inputMessageID

- -

Message by ID

-

- -
-
inputMessageID#a676a322 id:int = InputMessage;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idintMessage ID
-

Type

-

InputMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagePinned.html b/data/core.telegram.org/constructor/inputMessagePinned.html deleted file mode 100644 index 8f1e3668e0..0000000000 --- a/data/core.telegram.org/constructor/inputMessagePinned.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagePinned - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagePinned

- -

Pinned message

-

- -
-
inputMessagePinned#86872538 = InputMessage;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessageReplyTo.html b/data/core.telegram.org/constructor/inputMessageReplyTo.html deleted file mode 100644 index e6c8d722f8..0000000000 --- a/data/core.telegram.org/constructor/inputMessageReplyTo.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputMessageReplyTo - - - - - - - - - - - - - -
- -
-
-
- -

inputMessageReplyTo

- -

Message to which the specified message replies to

-

- -
-
inputMessageReplyTo#bad88395 id:int = InputMessage;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idintID of the message that replies to the message we need
-

Type

-

InputMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterChatPhotos.html b/data/core.telegram.org/constructor/inputMessagesFilterChatPhotos.html deleted file mode 100644 index 8d8250b104..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterChatPhotos.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterChatPhotos - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterChatPhotos

- -

Return only chat photo changes

-

- -
-
inputMessagesFilterChatPhotos#3a20ecb8 = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterContacts.html b/data/core.telegram.org/constructor/inputMessagesFilterContacts.html deleted file mode 100644 index 7ad7f7e001..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterContacts.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterContacts - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterContacts

- -

Return only messages containing contacts

-

- -
-
inputMessagesFilterContacts#e062db83 = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterDocument.html b/data/core.telegram.org/constructor/inputMessagesFilterDocument.html deleted file mode 100644 index cce6c52f71..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterDocument.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterDocument - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterDocument

- -

Filter for messages containing documents.

-

- -
-
inputMessagesFilterDocument#9eddf188 = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterEmpty.html b/data/core.telegram.org/constructor/inputMessagesFilterEmpty.html deleted file mode 100644 index 8859a0230e..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterEmpty - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterEmpty

- -

Filter is absent.

-

- -
-
inputMessagesFilterEmpty#57e2f66c = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterGeo.html b/data/core.telegram.org/constructor/inputMessagesFilterGeo.html deleted file mode 100644 index 9996ac6dab..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterGeo.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterGeo - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterGeo

- -

Return only messages containing geolocations

-

- -
-
inputMessagesFilterGeo#e7026d0d = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterGif.html b/data/core.telegram.org/constructor/inputMessagesFilterGif.html deleted file mode 100644 index 8013c90838..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterGif.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterGif - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterGif

- -

Return only messages containing gifs

-

- -
-
inputMessagesFilterGif#ffc86587 = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterMusic.html b/data/core.telegram.org/constructor/inputMessagesFilterMusic.html deleted file mode 100644 index 5ede2afb2b..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterMusic.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterMusic - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterMusic

- -

Return only messages containing audio files

-

- -
-
inputMessagesFilterMusic#3751b49e = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterMyMentions.html b/data/core.telegram.org/constructor/inputMessagesFilterMyMentions.html deleted file mode 100644 index 44315d5366..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterMyMentions.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - inputMessagesFilterMyMentions - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterMyMentions

- -

Return only messages where the current user was mentioned.

-

- -
-
inputMessagesFilterMyMentions#c1f8e69a = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

-

Related pages

-

Mentions

-

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterPhoneCalls.html b/data/core.telegram.org/constructor/inputMessagesFilterPhoneCalls.html deleted file mode 100644 index 7e52897222..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterPhoneCalls.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputMessagesFilterPhoneCalls - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterPhoneCalls

- -

Return only phone calls

-

- -
-
inputMessagesFilterPhoneCalls#80c99768 flags:# missed:flags.0?true = MessagesFilter;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
missedflags.0?trueReturn only missed phone calls
-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterPhotoVideo.html b/data/core.telegram.org/constructor/inputMessagesFilterPhotoVideo.html deleted file mode 100644 index 1f5baef1e7..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterPhotoVideo.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterPhotoVideo - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterPhotoVideo

- -

Filter for messages containing photos or videos.

-

- -
-
inputMessagesFilterPhotoVideo#56e9f0e4 = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterPhotos.html b/data/core.telegram.org/constructor/inputMessagesFilterPhotos.html deleted file mode 100644 index 2ee576bd78..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterPhotos.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterPhotos - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterPhotos

- -

Filter for messages containing photos.

-

- -
-
inputMessagesFilterPhotos#9609a51c = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterRoundVideo.html b/data/core.telegram.org/constructor/inputMessagesFilterRoundVideo.html deleted file mode 100644 index 1f2ea2876a..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterRoundVideo.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterRoundVideo - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterRoundVideo

- -

Return only round videos

-

- -
-
inputMessagesFilterRoundVideo#b549da53 = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterRoundVoice.html b/data/core.telegram.org/constructor/inputMessagesFilterRoundVoice.html deleted file mode 100644 index 26c674d727..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterRoundVoice.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterRoundVoice - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterRoundVoice

- -

Return only round videos and voice notes

-

- -
-
inputMessagesFilterRoundVoice#7a7c17a4 = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterUrl.html b/data/core.telegram.org/constructor/inputMessagesFilterUrl.html deleted file mode 100644 index 7df7ab51c8..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterUrl.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterUrl - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterUrl

- -

Return only messages containing URLs

-

- -
-
inputMessagesFilterUrl#7ef0dd87 = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputMessagesFilterVideo.html b/data/core.telegram.org/constructor/inputMessagesFilterVideo.html deleted file mode 100644 index 2507e24c6d..0000000000 --- a/data/core.telegram.org/constructor/inputMessagesFilterVideo.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterVideo - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterVideo

- -

Filter for messages containing videos.

-

- -
-
inputMessagesFilterVideo#9fc00e65 = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputNotifyBroadcasts.html b/data/core.telegram.org/constructor/inputNotifyBroadcasts.html deleted file mode 100644 index 167efa32ba..0000000000 --- a/data/core.telegram.org/constructor/inputNotifyBroadcasts.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - inputNotifyBroadcasts - - - - - - - - - - - - - -
- -
-
-
- -

inputNotifyBroadcasts

- -

All channels

-

- -
-
inputNotifyBroadcasts#b1db7c7e = InputNotifyPeer;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputNotifyPeer

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputNotifyChats.html b/data/core.telegram.org/constructor/inputNotifyChats.html deleted file mode 100644 index 8cd45038b6..0000000000 --- a/data/core.telegram.org/constructor/inputNotifyChats.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputNotifyChats - - - - - - - - - - - - - -
- -
-
-
- -

inputNotifyChats

- -

Notifications generated by all groups.

-

- -
-
inputNotifyChats#4a95e84e = InputNotifyPeer;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputNotifyPeer

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputNotifyPeer.html b/data/core.telegram.org/constructor/inputNotifyPeer.html deleted file mode 100644 index 9c0f21ab11..0000000000 --- a/data/core.telegram.org/constructor/inputNotifyPeer.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputNotifyPeer - - - - - - - - - - - - - -
- -
-
-
- -

inputNotifyPeer

- -

Notifications generated by a certain user or group.

-

- -
-
inputNotifyPeer#b8bc5b0c peer:InputPeer = InputNotifyPeer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerUser or group
-

Type

-

InputNotifyPeer

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputNotifyUsers.html b/data/core.telegram.org/constructor/inputNotifyUsers.html deleted file mode 100644 index 05ff385b4b..0000000000 --- a/data/core.telegram.org/constructor/inputNotifyUsers.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputNotifyUsers - - - - - - - - - - - - - -
- -
-
-
- -

inputNotifyUsers

- -

Notifications generated by all users.

-

- -
-
inputNotifyUsers#193b4417 = InputNotifyPeer;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputNotifyPeer

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPaymentCredentials.html b/data/core.telegram.org/constructor/inputPaymentCredentials.html deleted file mode 100644 index aaf1b05c15..0000000000 --- a/data/core.telegram.org/constructor/inputPaymentCredentials.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - inputPaymentCredentials - - - - - - - - - - - - - -
- -
-
-
- -

inputPaymentCredentials

- -

Payment credentials

-

- -
-
inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
saveflags.0?trueSave payment credential for future use
dataDataJSONPayment credentials
-

Type

-

InputPaymentCredentials

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPaymentCredentialsApplePay.html b/data/core.telegram.org/constructor/inputPaymentCredentialsApplePay.html deleted file mode 100644 index 6a8dffa157..0000000000 --- a/data/core.telegram.org/constructor/inputPaymentCredentialsApplePay.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputPaymentCredentialsApplePay - - - - - - - - - - - - - -
- -
-
-
- -

inputPaymentCredentialsApplePay

- -

Apple pay payment credentials

-

- -
-
inputPaymentCredentialsApplePay#aa1c39f payment_data:DataJSON = InputPaymentCredentials;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
payment_dataDataJSONPayment data
-

Type

-

InputPaymentCredentials

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPaymentCredentialsGooglePay.html b/data/core.telegram.org/constructor/inputPaymentCredentialsGooglePay.html deleted file mode 100644 index 5092d70baa..0000000000 --- a/data/core.telegram.org/constructor/inputPaymentCredentialsGooglePay.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputPaymentCredentialsGooglePay - - - - - - - - - - - - - -
- -
-
-
- -

inputPaymentCredentialsGooglePay

- -

Google Pay payment credentials

-

- -
-
inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
payment_tokenDataJSONPayment token
-

Type

-

InputPaymentCredentials

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPaymentCredentialsSaved.html b/data/core.telegram.org/constructor/inputPaymentCredentialsSaved.html deleted file mode 100644 index 68fabf3079..0000000000 --- a/data/core.telegram.org/constructor/inputPaymentCredentialsSaved.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputPaymentCredentialsSaved - - - - - - - - - - - - - -
- -
-
-
- -

inputPaymentCredentialsSaved

- -

Saved payment credentials

-

- -
-
inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idstringCredential ID
tmp_passwordbytesTemporary password
-

Type

-

InputPaymentCredentials

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPeerChannelFromMessage.html b/data/core.telegram.org/constructor/inputPeerChannelFromMessage.html deleted file mode 100644 index 1e3520bee6..0000000000 --- a/data/core.telegram.org/constructor/inputPeerChannelFromMessage.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - inputPeerChannelFromMessage - - - - - - - - - - - - - -
- -
-
-
- -

inputPeerChannelFromMessage

- -

Defines a min channel that was seen in a certain message of a certain chat.

-

- -
-
inputPeerChannelFromMessage#bd2a0840 peer:InputPeer msg_id:int channel_id:long = InputPeer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat where the channel's message was seen
msg_idintThe message ID
channel_idlongThe identifier of the channel that was seen
-

Type

-

InputPeer

-

Related pages

-

Min constructors

-

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPeerChat.html b/data/core.telegram.org/constructor/inputPeerChat.html deleted file mode 100644 index 1816841acb..0000000000 --- a/data/core.telegram.org/constructor/inputPeerChat.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputPeerChat - - - - - - - - - - - - - -
- -
-
-
- -

inputPeerChat

- -

Defines a chat for further interaction.

-

- -
-
inputPeerChat#35a95cb9 chat_id:long = InputPeer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongChat idientifier
-

Type

-

InputPeer

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPeerEmpty.html b/data/core.telegram.org/constructor/inputPeerEmpty.html deleted file mode 100644 index befbf1c746..0000000000 --- a/data/core.telegram.org/constructor/inputPeerEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPeerEmpty - - - - - - - - - - - - - -
- -
-
-
- -

inputPeerEmpty

- -

An empty constructor, no user or chat is defined.

-

- -
-
inputPeerEmpty#7f3b18ea = InputPeer;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPeer

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPeerNotifySettings.html b/data/core.telegram.org/constructor/inputPeerNotifySettings.html deleted file mode 100644 index d994de4b68..0000000000 --- a/data/core.telegram.org/constructor/inputPeerNotifySettings.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - inputPeerNotifySettings - - - - - - - - - - - - - -
- -
-
-
- -

inputPeerNotifySettings

- -

Notification settings.

-

- -
-
inputPeerNotifySettings#9c3d198e flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = InputPeerNotifySettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
show_previewsflags.0?BoolIf the text of the message shall be displayed in notification
silentflags.1?BoolPeer was muted?
mute_untilflags.2?intDate until which all notifications shall be switched off
soundflags.3?stringName of an audio file for notification
-

Type

-

InputPeerNotifySettings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPeerPhotoFileLocation.html b/data/core.telegram.org/constructor/inputPeerPhotoFileLocation.html deleted file mode 100644 index 5b30662baa..0000000000 --- a/data/core.telegram.org/constructor/inputPeerPhotoFileLocation.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputPeerPhotoFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputPeerPhotoFileLocation

- -

Location of profile photo of channel/group/supergroup/user

-

- -
-
inputPeerPhotoFileLocation#37257e99 flags:# big:flags.0?true peer:InputPeer photo_id:long = InputFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
bigflags.0?trueWhether to download the high-quality version of the picture
peerInputPeerThe peer whose profile picture should be downloaded
photo_idlongPhoto ID
-

Type

-

InputFileLocation

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPeerSelf.html b/data/core.telegram.org/constructor/inputPeerSelf.html deleted file mode 100644 index 45a02fe522..0000000000 --- a/data/core.telegram.org/constructor/inputPeerSelf.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPeerSelf - - - - - - - - - - - - - -
- -
-
-
- -

inputPeerSelf

- -

Defines the current user.

-

- -
-
inputPeerSelf#7da07ec9 = InputPeer;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPeer

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPeerUser.html b/data/core.telegram.org/constructor/inputPeerUser.html deleted file mode 100644 index acabf3ee89..0000000000 --- a/data/core.telegram.org/constructor/inputPeerUser.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputPeerUser - - - - - - - - - - - - - -
- -
-
-
- -

inputPeerUser

- -

Defines a user for further interaction.

-

- -
-
inputPeerUser#dde8a54c user_id:long access_hash:long = InputPeer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser identifier
access_hashlongaccess_hash value from the user constructor
-

Type

-

InputPeer

-

Related pages

-

user

-

Indicates info about a certain user

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPeerUserFromMessage.html b/data/core.telegram.org/constructor/inputPeerUserFromMessage.html deleted file mode 100644 index e0beebbbc9..0000000000 --- a/data/core.telegram.org/constructor/inputPeerUserFromMessage.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - inputPeerUserFromMessage - - - - - - - - - - - - - -
- -
-
-
- -

inputPeerUserFromMessage

- -

Defines a min user that was seen in a certain message of a certain chat.

-

- -
-
inputPeerUserFromMessage#a87b0a1c peer:InputPeer msg_id:int user_id:long = InputPeer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat where the user was seen
msg_idintThe message ID
user_idlongThe identifier of the user that was seen
-

Type

-

InputPeer

-

Related pages

-

Min constructors

-

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPhoneCall.html b/data/core.telegram.org/constructor/inputPhoneCall.html deleted file mode 100644 index 89bcff0bdb..0000000000 --- a/data/core.telegram.org/constructor/inputPhoneCall.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputPhoneCall - - - - - - - - - - - - - -
- -
-
-
- -

inputPhoneCall

- -

Phone call

-

- -
-
inputPhoneCall#1e36fded id:long access_hash:long = InputPhoneCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongCall ID
access_hashlongAccess hash
-

Type

-

InputPhoneCall

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPhoneContact.html b/data/core.telegram.org/constructor/inputPhoneContact.html deleted file mode 100644 index ba51c8bf7d..0000000000 --- a/data/core.telegram.org/constructor/inputPhoneContact.html +++ /dev/null @@ -1,166 +0,0 @@ - - - - - inputPhoneContact - - - - - - - - - - - - - -
- -
-
-
- -

inputPhoneContact

- -

Phone contact. The client_id is just an arbitrary contact ID: it should be set, for example, to an incremental number when using contacts.importContacts, in order to retry importing only the contacts that weren't imported successfully.

-

- -
-
inputPhoneContact#f392b7f4 client_id:long phone:string first_name:string last_name:string = InputContact;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
client_idlongUser identifier on the client
phonestringPhone number
first_namestringContact's first name
last_namestringContact's last name
-

Type

-

InputContact

-

Related pages

-

contacts.importContacts

-

Imports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.

-

Use contacts.addContact to add Telegram contacts without actually using their phone number.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPhoto.html b/data/core.telegram.org/constructor/inputPhoto.html deleted file mode 100644 index addf5a5bf6..0000000000 --- a/data/core.telegram.org/constructor/inputPhoto.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputPhoto - - - - - - - - - - - - - -
- -
-
-
- -

inputPhoto

- -

Defines a photo for further interaction.

-

- -
-
inputPhoto#3bb3b94a id:long access_hash:long file_reference:bytes = InputPhoto;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongPhoto identifier
access_hashlongaccess_hash value from the photo constructor
file_referencebytesFile reference
-

Type

-

InputPhoto

-

Related pages

-

photo

-

Photo

-

File references

-

How to handle file references.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPhotoEmpty.html b/data/core.telegram.org/constructor/inputPhotoEmpty.html deleted file mode 100644 index 79effed578..0000000000 --- a/data/core.telegram.org/constructor/inputPhotoEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPhotoEmpty - - - - - - - - - - - - - -
- -
-
-
- -

inputPhotoEmpty

- -

Empty constructor.

-

- -
-
inputPhotoEmpty#1cd7bf0d = InputPhoto;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPhoto

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPhotoFileLocation.html b/data/core.telegram.org/constructor/inputPhotoFileLocation.html deleted file mode 100644 index 625e163c82..0000000000 --- a/data/core.telegram.org/constructor/inputPhotoFileLocation.html +++ /dev/null @@ -1,171 +0,0 @@ - - - - - inputPhotoFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputPhotoFileLocation

- -

Use this object to download a photo with upload.getFile method

-

- -
-
inputPhotoFileLocation#40181ffe id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongPhoto ID, obtained from the photo object
access_hashlongPhoto's access hash, obtained from the photo object
file_referencebytesFile reference
thumb_sizestringThe PhotoSize to download: must be set to the type field of the desired PhotoSize object of the photo
-

Type

-

InputFileLocation

-

Related pages

-

photo

-

Photo

-

File references

-

How to handle file references.

-

PhotoSize

-

Location of a certain size of a picture

-

upload.getFile

-

Returns content of a whole file or its part.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPhotoLegacyFileLocation.html b/data/core.telegram.org/constructor/inputPhotoLegacyFileLocation.html deleted file mode 100644 index 461753c0e1..0000000000 --- a/data/core.telegram.org/constructor/inputPhotoLegacyFileLocation.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - inputPhotoLegacyFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputPhotoLegacyFileLocation

- -

DEPRECATED legacy photo file location

-

- -
-
inputPhotoLegacyFileLocation#d83466f3 id:long access_hash:long file_reference:bytes volume_id:long local_id:int secret:long = InputFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongPhoto ID
access_hashlongAccess hash
file_referencebytesFile reference
volume_idlongVolume ID
local_idintLocal ID
secretlongSecret
-

Type

-

InputFileLocation

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyKeyAddedByPhone.html b/data/core.telegram.org/constructor/inputPrivacyKeyAddedByPhone.html deleted file mode 100644 index 4a43c77464..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyKeyAddedByPhone.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyAddedByPhone - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyKeyAddedByPhone

- -

Whether people can add you to their contact list by your phone number

-

- -
-
inputPrivacyKeyAddedByPhone#d1219bdd = InputPrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyKeyChatInvite.html b/data/core.telegram.org/constructor/inputPrivacyKeyChatInvite.html deleted file mode 100644 index bf8280fd43..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyKeyChatInvite.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyKeyChatInvite

- -

Whether the user can be invited to chats

-

- -
-
inputPrivacyKeyChatInvite#bdfb0426 = InputPrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyKeyForwards.html b/data/core.telegram.org/constructor/inputPrivacyKeyForwards.html deleted file mode 100644 index 26ee4c83a1..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyKeyForwards.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyForwards - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyKeyForwards

- -

Whether messages forwarded from this user will be anonymous

-

- -
-
inputPrivacyKeyForwards#a4dd4c08 = InputPrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyKeyPhoneCall.html b/data/core.telegram.org/constructor/inputPrivacyKeyPhoneCall.html deleted file mode 100644 index 27039b54a8..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyKeyPhoneCall.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyPhoneCall - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyKeyPhoneCall

- -

Whether the user will accept phone calls

-

- -
-
inputPrivacyKeyPhoneCall#fabadc5f = InputPrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyKeyPhoneNumber.html b/data/core.telegram.org/constructor/inputPrivacyKeyPhoneNumber.html deleted file mode 100644 index 4c89cb42fb..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyKeyPhoneNumber.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyPhoneNumber - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyKeyPhoneNumber

- -

Whether people will be able to see the user's phone number

-

- -
-
inputPrivacyKeyPhoneNumber#352dafa = InputPrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyKeyPhoneP2P.html b/data/core.telegram.org/constructor/inputPrivacyKeyPhoneP2P.html deleted file mode 100644 index a11b083a1d..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyKeyPhoneP2P.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyPhoneP2P - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyKeyPhoneP2P

- -

Whether the user allows P2P communication during VoIP calls

-

- -
-
inputPrivacyKeyPhoneP2P#db9e70d2 = InputPrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyKeyProfilePhoto.html b/data/core.telegram.org/constructor/inputPrivacyKeyProfilePhoto.html deleted file mode 100644 index 46c17a25ed..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyKeyProfilePhoto.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyProfilePhoto - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyKeyProfilePhoto

- -

Whether people will be able to see the user's profile picture

-

- -
-
inputPrivacyKeyProfilePhoto#5719bacc = InputPrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html b/data/core.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html deleted file mode 100644 index b5cc1c6b2e..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyKeyStatusTimestamp.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyStatusTimestamp - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyKeyStatusTimestamp

- -

Whether we can see the exact last online timestamp of the user

-

- -
-
inputPrivacyKeyStatusTimestamp#4f96cb18 = InputPrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyValueAllowAll.html b/data/core.telegram.org/constructor/inputPrivacyValueAllowAll.html deleted file mode 100644 index 85164c819c..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyValueAllowAll.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyValueAllowAll - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyValueAllowAll

- -

Allow all users

-

- -
-
inputPrivacyValueAllowAll#184b35ce = InputPrivacyRule;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyValueAllowChatParticipants.html b/data/core.telegram.org/constructor/inputPrivacyValueAllowChatParticipants.html deleted file mode 100644 index 9a899eeb73..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyValueAllowChatParticipants.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputPrivacyValueAllowChatParticipants - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyValueAllowChatParticipants

- -

Allow only participants of certain chats

-

- -
-
inputPrivacyValueAllowChatParticipants#840649cf chats:Vector<long> = InputPrivacyRule;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chatsVector<long>Allowed chat IDs
-

Type

-

InputPrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyValueAllowContacts.html b/data/core.telegram.org/constructor/inputPrivacyValueAllowContacts.html deleted file mode 100644 index 7ac1476f9f..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyValueAllowContacts.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyValueAllowContacts - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyValueAllowContacts

- -

Allow only contacts

-

- -
-
inputPrivacyValueAllowContacts#d09e07b = InputPrivacyRule;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyValueAllowUsers.html b/data/core.telegram.org/constructor/inputPrivacyValueAllowUsers.html deleted file mode 100644 index 572c06af8d..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyValueAllowUsers.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputPrivacyValueAllowUsers - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyValueAllowUsers

- -

Allow only certain users

-

- -
-
inputPrivacyValueAllowUsers#131cc67f users:Vector<InputUser> = InputPrivacyRule;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
usersVector<InputUser>Allowed users
-

Type

-

InputPrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyValueDisallowAll.html b/data/core.telegram.org/constructor/inputPrivacyValueDisallowAll.html deleted file mode 100644 index 1bf29d6635..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyValueDisallowAll.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyValueDisallowAll - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyValueDisallowAll

- -

Disallow all

-

- -
-
inputPrivacyValueDisallowAll#d66b66c9 = InputPrivacyRule;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyValueDisallowChatParticipants.html b/data/core.telegram.org/constructor/inputPrivacyValueDisallowChatParticipants.html deleted file mode 100644 index 322a376251..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyValueDisallowChatParticipants.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputPrivacyValueDisallowChatParticipants - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyValueDisallowChatParticipants

- -

Disallow only participants of certain chats

-

- -
-
inputPrivacyValueDisallowChatParticipants#e94f0f86 chats:Vector<long> = InputPrivacyRule;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chatsVector<long>Disallowed chat IDs
-

Type

-

InputPrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputPrivacyValueDisallowUsers.html b/data/core.telegram.org/constructor/inputPrivacyValueDisallowUsers.html deleted file mode 100644 index 57404c0f39..0000000000 --- a/data/core.telegram.org/constructor/inputPrivacyValueDisallowUsers.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputPrivacyValueDisallowUsers - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyValueDisallowUsers

- -

Disallow only certain users

-

- -
-
inputPrivacyValueDisallowUsers#90110467 users:Vector<InputUser> = InputPrivacyRule;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
usersVector<InputUser>Users to disallow
-

Type

-

InputPrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputReportReasonChildAbuse.html b/data/core.telegram.org/constructor/inputReportReasonChildAbuse.html deleted file mode 100644 index 8529533cbc..0000000000 --- a/data/core.telegram.org/constructor/inputReportReasonChildAbuse.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputReportReasonChildAbuse - - - - - - - - - - - - - -
- -
-
-
- -

inputReportReasonChildAbuse

- -

Report for child abuse

-

- -
-
inputReportReasonChildAbuse#adf44ee3 = ReportReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ReportReason

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputReportReasonCopyright.html b/data/core.telegram.org/constructor/inputReportReasonCopyright.html deleted file mode 100644 index 2383e4ed2b..0000000000 --- a/data/core.telegram.org/constructor/inputReportReasonCopyright.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputReportReasonCopyright - - - - - - - - - - - - - -
- -
-
-
- -

inputReportReasonCopyright

- -

Report for copyrighted content

-

- -
-
inputReportReasonCopyright#9b89f93a = ReportReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ReportReason

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputReportReasonFake.html b/data/core.telegram.org/constructor/inputReportReasonFake.html deleted file mode 100644 index 3ddec4d04a..0000000000 --- a/data/core.telegram.org/constructor/inputReportReasonFake.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputReportReasonFake - - - - - - - - - - - - - -
- -
-
-
- -

inputReportReasonFake

- -

Report for impersonation

-

- -
-
inputReportReasonFake#f5ddd6e7 = ReportReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ReportReason

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputReportReasonGeoIrrelevant.html b/data/core.telegram.org/constructor/inputReportReasonGeoIrrelevant.html deleted file mode 100644 index 4395262675..0000000000 --- a/data/core.telegram.org/constructor/inputReportReasonGeoIrrelevant.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputReportReasonGeoIrrelevant - - - - - - - - - - - - - -
- -
-
-
- -

inputReportReasonGeoIrrelevant

- -

Report an irrelevant geogroup

-

- -
-
inputReportReasonGeoIrrelevant#dbd4feed = ReportReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ReportReason

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputReportReasonOther.html b/data/core.telegram.org/constructor/inputReportReasonOther.html deleted file mode 100644 index 208a6ae511..0000000000 --- a/data/core.telegram.org/constructor/inputReportReasonOther.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputReportReasonOther - - - - - - - - - - - - - -
- -
-
-
- -

inputReportReasonOther

- -

Other

-

- -
-
inputReportReasonOther#c1e4a2b1 = ReportReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ReportReason

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputReportReasonPornography.html b/data/core.telegram.org/constructor/inputReportReasonPornography.html deleted file mode 100644 index daa10d7d5c..0000000000 --- a/data/core.telegram.org/constructor/inputReportReasonPornography.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputReportReasonPornography - - - - - - - - - - - - - -
- -
-
-
- -

inputReportReasonPornography

- -

Report for pornography

-

- -
-
inputReportReasonPornography#2e59d922 = ReportReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ReportReason

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputReportReasonSpam.html b/data/core.telegram.org/constructor/inputReportReasonSpam.html deleted file mode 100644 index 73dfed9198..0000000000 --- a/data/core.telegram.org/constructor/inputReportReasonSpam.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputReportReasonSpam - - - - - - - - - - - - - -
- -
-
-
- -

inputReportReasonSpam

- -

Report for spam

-

- -
-
inputReportReasonSpam#58dbcab8 = ReportReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ReportReason

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputReportReasonViolence.html b/data/core.telegram.org/constructor/inputReportReasonViolence.html deleted file mode 100644 index 44a933a223..0000000000 --- a/data/core.telegram.org/constructor/inputReportReasonViolence.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputReportReasonViolence - - - - - - - - - - - - - -
- -
-
-
- -

inputReportReasonViolence

- -

Report for violence

-

- -
-
inputReportReasonViolence#1e22c78d = ReportReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ReportReason

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputSecureFileLocation.html b/data/core.telegram.org/constructor/inputSecureFileLocation.html deleted file mode 100644 index 6c8a7f47e4..0000000000 --- a/data/core.telegram.org/constructor/inputSecureFileLocation.html +++ /dev/null @@ -1,156 +0,0 @@ - - - - - inputSecureFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputSecureFileLocation

- -

Location of encrypted telegram passport file.

-

- -
-
inputSecureFileLocation#cbc7ee28 id:long access_hash:long = InputFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongFile ID, id parameter value from secureFile
access_hashlongChecksum, access_hash parameter value from secureFile
-

Type

-

InputFileLocation

-

Related pages

-

secureFile

-

Secure passport file, for more info see the passport docs »

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputSecureFileUploaded.html b/data/core.telegram.org/constructor/inputSecureFileUploaded.html deleted file mode 100644 index 2ecd0ec67a..0000000000 --- a/data/core.telegram.org/constructor/inputSecureFileUploaded.html +++ /dev/null @@ -1,169 +0,0 @@ - - - - - inputSecureFileUploaded - - - - - - - - - - - - - -
- -
-
-
- -

inputSecureFileUploaded

- -

Uploaded secure file, for more info see the passport docs »

-

- -
-
inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongSecure file ID
partsintSecure file part count
md5_checksumstringMD5 hash of encrypted uploaded file, to be checked server-side
file_hashbytesFile hash
secretbytesSecret
-

Type

-

InputSecureFile

-

Related pages

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputSecureValue.html b/data/core.telegram.org/constructor/inputSecureValue.html deleted file mode 100644 index e2625ec09d..0000000000 --- a/data/core.telegram.org/constructor/inputSecureValue.html +++ /dev/null @@ -1,190 +0,0 @@ - - - - - inputSecureValue - - - - - - - - - - - - - -
- -
-
-
- -

inputSecureValue

- -

Secure value, for more info see the passport docs »

-

- -
-
inputSecureValue#db21d0a7 flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?InputSecureFile reverse_side:flags.2?InputSecureFile selfie:flags.3?InputSecureFile translation:flags.6?Vector<InputSecureFile> files:flags.4?Vector<InputSecureFile> plain_data:flags.5?SecurePlainData = InputSecureValue;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
typeSecureValueTypeSecure passport value type
dataflags.0?SecureDataEncrypted Telegram Passport element data
front_sideflags.1?InputSecureFileEncrypted passport file with the front side of the document
reverse_sideflags.2?InputSecureFileEncrypted passport file with the reverse side of the document
selfieflags.3?InputSecureFileEncrypted passport file with a selfie of the user holding the document
translationflags.6?Vector<InputSecureFile>Array of encrypted passport files with translated versions of the provided documents
filesflags.4?Vector<InputSecureFile>Array of encrypted passport files with photos the of the documents
plain_dataflags.5?SecurePlainDataPlaintext verified passport data
-

Type

-

InputSecureValue

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputSingleMedia.html b/data/core.telegram.org/constructor/inputSingleMedia.html deleted file mode 100644 index 51f91b5804..0000000000 --- a/data/core.telegram.org/constructor/inputSingleMedia.html +++ /dev/null @@ -1,174 +0,0 @@ - - - - - inputSingleMedia - - - - - - - - - - - - - -
- -
-
-
- -

inputSingleMedia

- -

A single media in an album or grouped media sent with messages.sendMultiMedia.

-

- -
-
inputSingleMedia#1cc6e91f flags:# media:InputMedia random_id:long message:string entities:flags.0?Vector<MessageEntity> = InputSingleMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
mediaInputMediaThe media
random_idlongUnique client media ID required to prevent message resending
messagestringA caption for the media
entitiesflags.0?Vector<MessageEntity>Message entities for styled text
-

Type

-

InputSingleMedia

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

-

messages.sendMultiMedia

-

Send an album or grouped media

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputStickerSetAnimatedEmojiAnimations.html b/data/core.telegram.org/constructor/inputStickerSetAnimatedEmojiAnimations.html deleted file mode 100644 index ac97df05f0..0000000000 --- a/data/core.telegram.org/constructor/inputStickerSetAnimatedEmojiAnimations.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputStickerSetAnimatedEmojiAnimations - - - - - - - - - - - - - -
- -
-
-
- -

inputStickerSetAnimatedEmojiAnimations

- -

Animated emoji reaction stickerset (contains animations to play when a user clicks on a given animated emoji)

-

- -
-
inputStickerSetAnimatedEmojiAnimations#cde3739 = InputStickerSet;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputStickerSet

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputStickerSetEmpty.html b/data/core.telegram.org/constructor/inputStickerSetEmpty.html deleted file mode 100644 index dcadb50f38..0000000000 --- a/data/core.telegram.org/constructor/inputStickerSetEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputStickerSetEmpty - - - - - - - - - - - - - -
- -
-
-
- -

inputStickerSetEmpty

- -

Empty constructor

-

- -
-
inputStickerSetEmpty#ffb62b95 = InputStickerSet;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputStickerSet

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputStickerSetItem.html b/data/core.telegram.org/constructor/inputStickerSetItem.html deleted file mode 100644 index 1cc21a714b..0000000000 --- a/data/core.telegram.org/constructor/inputStickerSetItem.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputStickerSetItem - - - - - - - - - - - - - -
- -
-
-
- -

inputStickerSetItem

- -

Sticker in a stickerset

-

- -
-
inputStickerSetItem#ffa0a496 flags:# document:InputDocument emoji:string mask_coords:flags.0?MaskCoords = InputStickerSetItem;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
documentInputDocumentThe sticker
emojistringAssociated emoji
mask_coordsflags.0?MaskCoordsCoordinates for mask sticker
-

Type

-

InputStickerSetItem

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputStickerSetShortName.html b/data/core.telegram.org/constructor/inputStickerSetShortName.html deleted file mode 100644 index f4a7361f55..0000000000 --- a/data/core.telegram.org/constructor/inputStickerSetShortName.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputStickerSetShortName - - - - - - - - - - - - - -
- -
-
-
- -

inputStickerSetShortName

- -

Stickerset by short name, from tg://addstickers?set=short_name

-

- -
-
inputStickerSetShortName#861cc8a0 short_name:string = InputStickerSet;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
short_namestringFrom tg://addstickers?set=short_name
-

Type

-

InputStickerSet

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputStickerSetThumb.html b/data/core.telegram.org/constructor/inputStickerSetThumb.html deleted file mode 100644 index 47c63b6c53..0000000000 --- a/data/core.telegram.org/constructor/inputStickerSetThumb.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputStickerSetThumb - - - - - - - - - - - - - -
- -
-
-
- -

inputStickerSetThumb

- -

Location of stickerset thumbnail (see files)

-

- -
-
inputStickerSetThumb#9d84f3db stickerset:InputStickerSet thumb_version:int = InputFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
stickersetInputStickerSetSticker set
thumb_versionintThumbnail version
-

Type

-

InputFileLocation

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputStickeredMediaDocument.html b/data/core.telegram.org/constructor/inputStickeredMediaDocument.html deleted file mode 100644 index 186dc647b3..0000000000 --- a/data/core.telegram.org/constructor/inputStickeredMediaDocument.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputStickeredMediaDocument - - - - - - - - - - - - - -
- -
-
-
- -

inputStickeredMediaDocument

- -

A document with stickers attached

-

- -
-
inputStickeredMediaDocument#438865b id:InputDocument = InputStickeredMedia;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idInputDocumentThe document
-

Type

-

InputStickeredMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputStickeredMediaPhoto.html b/data/core.telegram.org/constructor/inputStickeredMediaPhoto.html deleted file mode 100644 index 85e684cd61..0000000000 --- a/data/core.telegram.org/constructor/inputStickeredMediaPhoto.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputStickeredMediaPhoto - - - - - - - - - - - - - -
- -
-
-
- -

inputStickeredMediaPhoto

- -

A photo with stickers attached

-

- -
-
inputStickeredMediaPhoto#4a992157 id:InputPhoto = InputStickeredMedia;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idInputPhotoThe photo
-

Type

-

InputStickeredMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputTakeoutFileLocation.html b/data/core.telegram.org/constructor/inputTakeoutFileLocation.html deleted file mode 100644 index d5b309c2e7..0000000000 --- a/data/core.telegram.org/constructor/inputTakeoutFileLocation.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputTakeoutFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputTakeoutFileLocation

- -

Empty constructor for takeout

-

- -
-
inputTakeoutFileLocation#29be5899 = InputFileLocation;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputFileLocation

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputTheme.html b/data/core.telegram.org/constructor/inputTheme.html deleted file mode 100644 index 2b385c80c6..0000000000 --- a/data/core.telegram.org/constructor/inputTheme.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputTheme - - - - - - - - - - - - - -
- -
-
-
- -

inputTheme

- -

Theme

-

- -
-
inputTheme#3c5693e9 id:long access_hash:long = InputTheme;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongID
access_hashlongAccess hash
-

Type

-

InputTheme

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputThemeSettings.html b/data/core.telegram.org/constructor/inputThemeSettings.html deleted file mode 100644 index afd0437507..0000000000 --- a/data/core.telegram.org/constructor/inputThemeSettings.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - inputThemeSettings - - - - - - - - - - - - - -
- -
-
-
- -

inputThemeSettings

- -

Theme settings

-

- -
-
inputThemeSettings#8fde504f flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int outbox_accent_color:flags.3?int message_colors:flags.0?Vector<int> wallpaper:flags.1?InputWallPaper wallpaper_settings:flags.1?WallPaperSettings = InputThemeSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
message_colors_animatedflags.2?trueIf set, the freeform gradient fill needs to be animated on every sent message
base_themeBaseThemeDefault theme on which this theme is based
accent_colorintAccent color, ARGB format
outbox_accent_colorflags.3?intAccent color of outgoing messages in ARGB format
message_colorsflags.0?Vector<int>The fill to be used as a background for outgoing messages, in RGB24 format.
If just one or two equal colors are provided, describes a solid fill of a background.
If two different colors are provided, describes the top and bottom colors of a 0-degree gradient.
If three or four colors are provided, describes a freeform gradient fill of a background.
wallpaperflags.1?InputWallPaperWallpaper
wallpaper_settingsflags.1?WallPaperSettingsWallpaper settings
-

Type

-

InputThemeSettings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputThemeSlug.html b/data/core.telegram.org/constructor/inputThemeSlug.html deleted file mode 100644 index 13acc9f9c7..0000000000 --- a/data/core.telegram.org/constructor/inputThemeSlug.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputThemeSlug - - - - - - - - - - - - - -
- -
-
-
- -

inputThemeSlug

- -

Theme by theme ID

-

- -
-
inputThemeSlug#f5890df1 slug:string = InputTheme;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
slugstringUnique theme ID
-

Type

-

InputTheme

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputUser.html b/data/core.telegram.org/constructor/inputUser.html deleted file mode 100644 index 19c4056092..0000000000 --- a/data/core.telegram.org/constructor/inputUser.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputUser - - - - - - - - - - - - - -
- -
-
-
- -

inputUser

- -

Defines a user for further interaction.

-

- -
-
inputUser#f21158c6 user_id:long access_hash:long = InputUser;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser identifier
access_hashlongaccess_hash value from the user constructor
-

Type

-

InputUser

-

Related pages

-

user

-

Indicates info about a certain user

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputUserEmpty.html b/data/core.telegram.org/constructor/inputUserEmpty.html deleted file mode 100644 index 44b8adcaf6..0000000000 --- a/data/core.telegram.org/constructor/inputUserEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputUserEmpty - - - - - - - - - - - - - -
- -
-
-
- -

inputUserEmpty

- -

Empty constructor, does not define a user.

-

- -
-
inputUserEmpty#b98886cf = InputUser;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputUser

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputUserFromMessage.html b/data/core.telegram.org/constructor/inputUserFromMessage.html deleted file mode 100644 index 4eec2ed10d..0000000000 --- a/data/core.telegram.org/constructor/inputUserFromMessage.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - inputUserFromMessage - - - - - - - - - - - - - -
- -
-
-
- -

inputUserFromMessage

- -

Defines a min user that was seen in a certain message of a certain chat.

-

- -
-
inputUserFromMessage#1da448e2 peer:InputPeer msg_id:int user_id:long = InputUser;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat where the user was seen
msg_idintThe message ID
user_idlongThe identifier of the user that was seen
-

Type

-

InputUser

-

Related pages

-

Min constructors

-

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputUserSelf.html b/data/core.telegram.org/constructor/inputUserSelf.html deleted file mode 100644 index 21d44f392d..0000000000 --- a/data/core.telegram.org/constructor/inputUserSelf.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputUserSelf - - - - - - - - - - - - - -
- -
-
-
- -

inputUserSelf

- -

Defines the current user.

-

- -
-
inputUserSelf#f7c1b13f = InputUser;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputUser

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputWallPaper.html b/data/core.telegram.org/constructor/inputWallPaper.html deleted file mode 100644 index 4432bf6581..0000000000 --- a/data/core.telegram.org/constructor/inputWallPaper.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputWallPaper - - - - - - - - - - - - - -
- -
-
-
- -

inputWallPaper

- -

Wallpaper

-

- -
-
inputWallPaper#e630b979 id:long access_hash:long = InputWallPaper;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongWallpaper ID
access_hashlongAccess hash
-

Type

-

InputWallPaper

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputWallPaperNoFile.html b/data/core.telegram.org/constructor/inputWallPaperNoFile.html deleted file mode 100644 index 8a56c3a709..0000000000 --- a/data/core.telegram.org/constructor/inputWallPaperNoFile.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - inputWallPaperNoFile - - - - - - - - - - - - - -
- -
-
-
- -

inputWallPaperNoFile

- -

Wallpaper with no file access hash, used for example when deleting (unsave=true) wallpapers using account.saveWallPaper, specifying just the wallpaper ID.

-

- -
-
inputWallPaperNoFile#967a462e id:long = InputWallPaper;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idlongWallpaper ID
-

Type

-

InputWallPaper

-

Related pages

-

account.saveWallPaper

-

Install/uninstall wallpaper

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputWallPaperSlug.html b/data/core.telegram.org/constructor/inputWallPaperSlug.html deleted file mode 100644 index 6ca41fab1c..0000000000 --- a/data/core.telegram.org/constructor/inputWallPaperSlug.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputWallPaperSlug - - - - - - - - - - - - - -
- -
-
-
- -

inputWallPaperSlug

- -

Wallpaper by slug (a unique ID)

-

- -
-
inputWallPaperSlug#72091c80 slug:string = InputWallPaper;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
slugstringUnique wallpaper ID
-

Type

-

InputWallPaper

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputWebDocument.html b/data/core.telegram.org/constructor/inputWebDocument.html deleted file mode 100644 index 4cd5d55682..0000000000 --- a/data/core.telegram.org/constructor/inputWebDocument.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - inputWebDocument - - - - - - - - - - - - - -
- -
-
-
- -

inputWebDocument

- -

The document

-

- -
-
inputWebDocument#9bed434d url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = InputWebDocument;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringRemote document URL to be downloaded using the appropriate method
sizeintRemote file size
mime_typestringMime type
attributesVector<DocumentAttribute>Attributes for media types
-

Type

-

InputWebDocument

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputWebFileGeoPointLocation.html b/data/core.telegram.org/constructor/inputWebFileGeoPointLocation.html deleted file mode 100644 index e7f9359db6..0000000000 --- a/data/core.telegram.org/constructor/inputWebFileGeoPointLocation.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - inputWebFileGeoPointLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputWebFileGeoPointLocation

- -

Geolocation

-

- -
-
inputWebFileGeoPointLocation#9f2221c9 geo_point:InputGeoPoint access_hash:long w:int h:int zoom:int scale:int = InputWebFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
geo_pointInputGeoPointGeolocation
access_hashlongAccess hash
wintMap width in pixels before applying scale; 16-1024
hintMap height in pixels before applying scale; 16-1024
zoomintMap zoom level; 13-20
scaleintMap scale; 1-3
-

Type

-

InputWebFileLocation

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/inputWebFileLocation.html b/data/core.telegram.org/constructor/inputWebFileLocation.html deleted file mode 100644 index 6c66568007..0000000000 --- a/data/core.telegram.org/constructor/inputWebFileLocation.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputWebFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputWebFileLocation

- -

Location of a remote HTTP(s) file

-

- -
-
inputWebFileLocation#c239d686 url:string access_hash:long = InputWebFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringHTTP URL of file
access_hashlongAccess hash
-

Type

-

InputWebFileLocation

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/invoice.html b/data/core.telegram.org/constructor/invoice.html deleted file mode 100644 index 8e10e9d9c2..0000000000 --- a/data/core.telegram.org/constructor/invoice.html +++ /dev/null @@ -1,209 +0,0 @@ - - - - - invoice - - - - - - - - - - - - - -
- -
-
-
- -

invoice

- -

Invoice

-

- -
-
invoice#cd886e0 flags:# test:flags.0?true name_requested:flags.1?true phone_requested:flags.2?true email_requested:flags.3?true shipping_address_requested:flags.4?true flexible:flags.5?true phone_to_provider:flags.6?true email_to_provider:flags.7?true currency:string prices:Vector<LabeledPrice> max_tip_amount:flags.8?long suggested_tip_amounts:flags.8?Vector<long> = Invoice;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
testflags.0?trueTest invoice
name_requestedflags.1?trueSet this flag if you require the user's full name to complete the order
phone_requestedflags.2?trueSet this flag if you require the user's phone number to complete the order
email_requestedflags.3?trueSet this flag if you require the user's email address to complete the order
shipping_address_requestedflags.4?trueSet this flag if you require the user's shipping address to complete the order
flexibleflags.5?trueSet this flag if the final price depends on the shipping method
phone_to_providerflags.6?trueSet this flag if user's phone number should be sent to provider
email_to_providerflags.7?trueSet this flag if user's email address should be sent to provider
currencystringThree-letter ISO 4217 currency code
pricesVector<LabeledPrice>Price breakdown, a list of components (e.g. product price, tax, discount, delivery cost, delivery tax, bonus, etc.)
max_tip_amountflags.8?longThe maximum accepted amount for tips in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
suggested_tip_amountsflags.8?Vector<long>A vector of suggested amounts of tips in the smallest units of the currency (integer, not float/double). At most 4 suggested tip amounts can be specified. The suggested tip amounts must be positive, passed in a strictly increased order and must not exceed max_tip_amount.
-

Type

-

Invoice

-

Related pages

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/jsonArray.html b/data/core.telegram.org/constructor/jsonArray.html deleted file mode 100644 index 70f79d96eb..0000000000 --- a/data/core.telegram.org/constructor/jsonArray.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - jsonArray - - - - - - - - - - - - - -
- -
-
-
- -

jsonArray

- -

JSON array

-

- -
-
jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
valueVector<JSONValue>JSON values
-

Type

-

JSONValue

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/jsonBool.html b/data/core.telegram.org/constructor/jsonBool.html deleted file mode 100644 index 7d834c2670..0000000000 --- a/data/core.telegram.org/constructor/jsonBool.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - jsonBool - - - - - - - - - - - - - -
- -
-
-
- -

jsonBool

- -

JSON boolean value

-

- -
-
jsonBool#c7345e6a value:Bool = JSONValue;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
valueBoolValue
-

Type

-

JSONValue

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/jsonNull.html b/data/core.telegram.org/constructor/jsonNull.html deleted file mode 100644 index 89d234ae35..0000000000 --- a/data/core.telegram.org/constructor/jsonNull.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - jsonNull - - - - - - - - - - - - - -
- -
-
-
- -

jsonNull

- -

null JSON value

-

- -
-
jsonNull#3f6d7b68 = JSONValue;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

JSONValue

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/jsonNumber.html b/data/core.telegram.org/constructor/jsonNumber.html deleted file mode 100644 index eb7f4e3815..0000000000 --- a/data/core.telegram.org/constructor/jsonNumber.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - jsonNumber - - - - - - - - - - - - - -
- -
-
-
- -

jsonNumber

- -

JSON numeric value

-

- -
-
jsonNumber#2be0dfa4 value:double = JSONValue;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
valuedoubleValue
-

Type

-

JSONValue

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/jsonObject.html b/data/core.telegram.org/constructor/jsonObject.html deleted file mode 100644 index a8fb071e23..0000000000 --- a/data/core.telegram.org/constructor/jsonObject.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - jsonObject - - - - - - - - - - - - - -
- -
-
-
- -

jsonObject

- -

JSON object value

-

- -
-
jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
valueVector<JSONObjectValue>Values
-

Type

-

JSONValue

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/jsonObjectValue.html b/data/core.telegram.org/constructor/jsonObjectValue.html deleted file mode 100644 index a25a310f02..0000000000 --- a/data/core.telegram.org/constructor/jsonObjectValue.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - jsonObjectValue - - - - - - - - - - - - - -
- -
-
-
- -

jsonObjectValue

- -

JSON key: value pair

-

- -
-
jsonObjectValue#c0de1bd9 key:string value:JSONValue = JSONObjectValue;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
keystringKey
valueJSONValueValue
-

Type

-

JSONObjectValue

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/jsonString.html b/data/core.telegram.org/constructor/jsonString.html deleted file mode 100644 index 7bef87ac42..0000000000 --- a/data/core.telegram.org/constructor/jsonString.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - jsonString - - - - - - - - - - - - - -
- -
-
-
- -

jsonString

- -

JSON string

-

- -
-
jsonString#b71e767a value:string = JSONValue;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
valuestringValue
-

Type

-

JSONValue

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/keyboardButton.html b/data/core.telegram.org/constructor/keyboardButton.html deleted file mode 100644 index f4601525ca..0000000000 --- a/data/core.telegram.org/constructor/keyboardButton.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - keyboardButton - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButton

- -

Bot keyboard button

-

- -
-
keyboardButton#a2fa4880 text:string = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textstringButton text
-

Type

-

KeyboardButton

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/keyboardButtonBuy.html b/data/core.telegram.org/constructor/keyboardButtonBuy.html deleted file mode 100644 index 223cf96d05..0000000000 --- a/data/core.telegram.org/constructor/keyboardButtonBuy.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - keyboardButtonBuy - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonBuy

- -

Button to buy a product

-

- -
-
keyboardButtonBuy#afd93fbb text:string = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textstringButton text
-

Type

-

KeyboardButton

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/keyboardButtonCallback.html b/data/core.telegram.org/constructor/keyboardButtonCallback.html deleted file mode 100644 index 5b5263399f..0000000000 --- a/data/core.telegram.org/constructor/keyboardButtonCallback.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - keyboardButtonCallback - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonCallback

- -

Callback button

-

- -
-
keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
requires_passwordflags.0?trueWhether the user should verify his identity by entering his 2FA SRP parameters to the messages.getBotCallbackAnswer method. NOTE: telegram and the bot WILL NOT have access to the plaintext password, thanks to SRP. This button is mainly used by the official @botfather bot, for verifying the user's identity before transferring ownership of a bot to another user.
textstringButton text
databytesCallback data
-

Type

-

KeyboardButton

-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

-

messages.getBotCallbackAnswer

-

Press an inline callback button and get a callback answer from the bot

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/keyboardButtonGame.html b/data/core.telegram.org/constructor/keyboardButtonGame.html deleted file mode 100644 index f12baa8348..0000000000 --- a/data/core.telegram.org/constructor/keyboardButtonGame.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - keyboardButtonGame - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonGame

- -

Button to start a game

-

- -
-
keyboardButtonGame#50f41ccf text:string = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textstringButton text
-

Type

-

KeyboardButton

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/keyboardButtonRequestGeoLocation.html b/data/core.telegram.org/constructor/keyboardButtonRequestGeoLocation.html deleted file mode 100644 index b9d0c6f693..0000000000 --- a/data/core.telegram.org/constructor/keyboardButtonRequestGeoLocation.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - keyboardButtonRequestGeoLocation - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonRequestGeoLocation

- -

Button to request a user's geolocation

-

- -
-
keyboardButtonRequestGeoLocation#fc796b3f text:string = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textstringButton text
-

Type

-

KeyboardButton

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/keyboardButtonRequestPhone.html b/data/core.telegram.org/constructor/keyboardButtonRequestPhone.html deleted file mode 100644 index 2d93039361..0000000000 --- a/data/core.telegram.org/constructor/keyboardButtonRequestPhone.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - keyboardButtonRequestPhone - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonRequestPhone

- -

Button to request a user's phone number

-

- -
-
keyboardButtonRequestPhone#b16a6c29 text:string = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textstringButton text
-

Type

-

KeyboardButton

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/keyboardButtonRequestPoll.html b/data/core.telegram.org/constructor/keyboardButtonRequestPoll.html deleted file mode 100644 index 98cf901d7b..0000000000 --- a/data/core.telegram.org/constructor/keyboardButtonRequestPoll.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - keyboardButtonRequestPoll - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonRequestPoll

- -

A button that allows the user to create and send a poll when pressed; available only in private

-

- -
-
keyboardButtonRequestPoll#bbc7515d flags:# quiz:flags.0?Bool text:string = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
quizflags.0?BoolIf set, only quiz polls can be sent
textstringButton text
-

Type

-

KeyboardButton

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/keyboardButtonRow.html b/data/core.telegram.org/constructor/keyboardButtonRow.html deleted file mode 100644 index 96aacbfdf3..0000000000 --- a/data/core.telegram.org/constructor/keyboardButtonRow.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - keyboardButtonRow - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonRow

- -

Inline keyboard row

-

- -
-
keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
buttonsVector<KeyboardButton>Bot or inline keyboard buttons
-

Type

-

KeyboardButtonRow

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/keyboardButtonSwitchInline.html b/data/core.telegram.org/constructor/keyboardButtonSwitchInline.html deleted file mode 100644 index 106c395e5a..0000000000 --- a/data/core.telegram.org/constructor/keyboardButtonSwitchInline.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - keyboardButtonSwitchInline - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonSwitchInline

- -

Button to force a user to switch to inline mode Pressing the button will prompt the user to select one of their chats, open that chat and insert the bot‘s username and the specified inline query in the input field.

-

- -
-
keyboardButtonSwitchInline#568a748 flags:# same_peer:flags.0?true text:string query:string = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
same_peerflags.0?trueIf set, pressing the button will insert the bot‘s username and the specified inline query in the current chat's input field.
textstringButton label
querystringThe inline query to use
-

Type

-

KeyboardButton

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/keyboardButtonUrl.html b/data/core.telegram.org/constructor/keyboardButtonUrl.html deleted file mode 100644 index 9defc29723..0000000000 --- a/data/core.telegram.org/constructor/keyboardButtonUrl.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - keyboardButtonUrl - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonUrl

- -

URL button

-

- -
-
keyboardButtonUrl#258aff05 text:string url:string = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textstringButton label
urlstringURL
-

Type

-

KeyboardButton

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/keyboardButtonUrlAuth.html b/data/core.telegram.org/constructor/keyboardButtonUrlAuth.html deleted file mode 100644 index c5f12d448b..0000000000 --- a/data/core.telegram.org/constructor/keyboardButtonUrlAuth.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - keyboardButtonUrlAuth - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonUrlAuth

- -

Button to request a user to authorize via URL using Seamless Telegram Login. When the user clicks on such a button, messages.requestUrlAuth should be called, providing the button_id and the ID of the container message. The returned urlAuthResultRequest object will contain more details about the authorization request (request_write_access if the bot would like to send messages to the user along with the username of the bot which will be used for user authorization). Finally, the user can choose to call messages.acceptUrlAuth to get a urlAuthResultAccepted with the URL to open instead of the url of this constructor, or a urlAuthResultDefault, in which case the url of this constructor must be opened, instead. If the user refuses the authorization request but still wants to open the link, the url of this constructor must be used.

-

- -
-
keyboardButtonUrlAuth#10b78d29 flags:# text:string fwd_text:flags.0?string url:string button_id:int = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
textstringButton label
fwd_textflags.0?stringNew text of the button in forwarded messages.
urlstringAn HTTP URL to be opened with user authorization data added to the query string when the button is pressed. If the user refuses to provide authorization data, the original URL without information about the user will be opened. The data added is the same as described in Receiving authorization data.

NOTE: Services must always check the hash of the received data to verify the authentication and the integrity of the data as described in Checking authorization.
button_idintID of the button to pass to messages.requestUrlAuth
-

Type

-

KeyboardButton

-

Related pages

-

Telegram Login Widget

-

messages.requestUrlAuth

-

Get more info about a Seamless Telegram Login authorization request, for more info click here »

-

urlAuthResultRequest

-

Details about the authorization request, for more info click here »

-

messages.acceptUrlAuth

-

Use this to accept a Seamless Telegram Login authorization request, for more info click here »

-

urlAuthResultAccepted

-

Details about an accepted authorization request, for more info click here »

-

urlAuthResultDefault

-

Details about an accepted authorization request, for more info click here »

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/labeledPrice.html b/data/core.telegram.org/constructor/labeledPrice.html deleted file mode 100644 index 336c0b3c2d..0000000000 --- a/data/core.telegram.org/constructor/labeledPrice.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - labeledPrice - - - - - - - - - - - - - -
- -
-
-
- -

labeledPrice

- -

This object represents a portion of the price for goods or services.

-

- -
-
labeledPrice#cb296bf8 label:string amount:long = LabeledPrice;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
labelstringPortion label
amountlongPrice of the product in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
-

Type

-

LabeledPrice

-

Related pages

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/langPackDifference.html b/data/core.telegram.org/constructor/langPackDifference.html deleted file mode 100644 index 5b6120a163..0000000000 --- a/data/core.telegram.org/constructor/langPackDifference.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - langPackDifference - - - - - - - - - - - - - -
- -
-
-
- -

langPackDifference

- -

Changes to the app's localization pack

-

- -
-
langPackDifference#f385c1f6 lang_code:string from_version:int version:int strings:Vector<LangPackString> = LangPackDifference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
lang_codestringLanguage code
from_versionintPrevious version number
versionintNew version number
stringsVector<LangPackString>Localized strings
-

Type

-

LangPackDifference

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/langPackLanguage.html b/data/core.telegram.org/constructor/langPackLanguage.html deleted file mode 100644 index 9d4795691a..0000000000 --- a/data/core.telegram.org/constructor/langPackLanguage.html +++ /dev/null @@ -1,202 +0,0 @@ - - - - - langPackLanguage - - - - - - - - - - - - - -
- -
-
-
- -

langPackLanguage

- -

Identifies a localization pack

-

- -
-
langPackLanguage#eeca5ce3 flags:# official:flags.0?true rtl:flags.2?true beta:flags.3?true name:string native_name:string lang_code:string base_lang_code:flags.1?string plural_code:string strings_count:int translated_count:int translations_url:string = LangPackLanguage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
officialflags.0?trueWhether the language pack is official
rtlflags.2?trueIs this a localization pack for an RTL language
betaflags.3?trueIs this a beta localization pack?
namestringLanguage name
native_namestringLanguage name in the language itself
lang_codestringLanguage code (pack identifier)
base_lang_codeflags.1?stringIdentifier of a base language pack; may be empty. If a string is missed in the language pack, then it should be fetched from base language pack. Unsupported in custom language packs
plural_codestringA language code to be used to apply plural forms. See https://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html for more info
strings_countintTotal number of non-deleted strings from the language pack
translated_countintTotal number of translated strings from the language pack
translations_urlstringLink to language translation interface; empty for custom local language packs
-

Type

-

LangPackLanguage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/langPackString.html b/data/core.telegram.org/constructor/langPackString.html deleted file mode 100644 index 9093daddde..0000000000 --- a/data/core.telegram.org/constructor/langPackString.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - langPackString - - - - - - - - - - - - - -
- -
-
-
- -

langPackString

- -

Translated localization string

-

- -
-
langPackString#cad181f6 key:string value:string = LangPackString;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
keystringLanguage key
valuestringValue
-

Type

-

LangPackString

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/langPackStringDeleted.html b/data/core.telegram.org/constructor/langPackStringDeleted.html deleted file mode 100644 index 028ad5eae0..0000000000 --- a/data/core.telegram.org/constructor/langPackStringDeleted.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - langPackStringDeleted - - - - - - - - - - - - - -
- -
-
-
- -

langPackStringDeleted

- -

Deleted localization string

-

- -
-
langPackStringDeleted#2979eeb2 key:string = LangPackString;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
keystringLocalization key
-

Type

-

LangPackString

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/langPackStringPluralized.html b/data/core.telegram.org/constructor/langPackStringPluralized.html deleted file mode 100644 index 6012cb2751..0000000000 --- a/data/core.telegram.org/constructor/langPackStringPluralized.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - langPackStringPluralized - - - - - - - - - - - - - -
- -
-
-
- -

langPackStringPluralized

- -

A language pack string which has different forms based on the number of some object it mentions. See https://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html for more info

-

- -
-
langPackStringPluralized#6c47ac9f flags:# key:string zero_value:flags.0?string one_value:flags.1?string two_value:flags.2?string few_value:flags.3?string many_value:flags.4?string other_value:string = LangPackString;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
keystringLocalization key
zero_valueflags.0?stringValue for zero objects
one_valueflags.1?stringValue for one object
two_valueflags.2?stringValue for two objects
few_valueflags.3?stringValue for a few objects
many_valueflags.4?stringValue for many objects
other_valuestringDefault value
-

Type

-

LangPackString

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/maskCoords.html b/data/core.telegram.org/constructor/maskCoords.html deleted file mode 100644 index e81910719a..0000000000 --- a/data/core.telegram.org/constructor/maskCoords.html +++ /dev/null @@ -1,169 +0,0 @@ - - - - - maskCoords - - - - - - - - - - - - - -
- -
-
-
- -

maskCoords

- -

Position on a photo where a mask should be placed

-

The n position indicates where the mask should be placed:

-
    -
  • 0 => Relative to the forehead
  • -
  • 1 => Relative to the eyes
  • -
  • 2 => Relative to the mouth
  • -
  • 3 => Relative to the chin
  • -
-

- -
-
maskCoords#aed6dbb2 n:int x:double y:double zoom:double = MaskCoords;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
nintPart of the face, relative to which the mask should be placed
xdoubleShift by X-axis measured in widths of the mask scaled to the face size, from left to right. (For example, -1.0 will place the mask just to the left of the default mask position)
ydoubleShift by Y-axis measured in widths of the mask scaled to the face size, from left to right. (For example, -1.0 will place the mask just to the left of the default mask position)
zoomdoubleMask scaling coefficient. (For example, 2.0 means a doubled size)
-

Type

-

MaskCoords

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/message.html b/data/core.telegram.org/constructor/message.html deleted file mode 100644 index 16de546363..0000000000 --- a/data/core.telegram.org/constructor/message.html +++ /dev/null @@ -1,302 +0,0 @@ - - - - - message - - - - - - - - - - - - - -
- -
-
-
- -

message

- -

A message

-

- -
-
message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true noforwards:flags.26?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
outflags.1?trueIs this an outgoing message
mentionedflags.4?trueWhether we were mentioned in this message
media_unreadflags.5?trueWhether there are unread media attachments in this message
silentflags.13?trueWhether this is a silent message (no notification triggered)
postflags.14?trueWhether this is a channel post
from_scheduledflags.18?trueWhether this is a scheduled message
legacyflags.19?trueThis is a legacy message: it has to be refetched with the new layer
edit_hideflags.21?trueWhether the message should be shown as not modified to the user, even if an edit date is present
pinnedflags.24?trueWhether this message is pinned
idintID of the message
from_idflags.8?PeerID of the sender of the message
peer_idPeerPeer ID, the chat where this message was sent
fwd_fromflags.2?MessageFwdHeaderInfo about forwarded messages
via_bot_idflags.11?longID of the inline bot that generated the message
reply_toflags.3?MessageReplyHeaderReply information
dateintDate of the message
messagestringThe message
mediaflags.9?MessageMediaMedia attachment
reply_markupflags.6?ReplyMarkupReply markup (bot/inline keyboards)
entitiesflags.7?Vector<MessageEntity>Message entities for styled text
viewsflags.10?intView count for channel posts
forwardsflags.10?intForward counter
repliesflags.23?MessageRepliesInfo about post comments (for channels) or message replies (for groups)
edit_dateflags.15?intLast edit date of this message
post_authorflags.16?stringName of the author of this message for channel posts (with signatures enabled)
grouped_idflags.17?longMultiple media messages sent using messages.sendMultiMedia with the same grouped ID indicate an album or media group
restriction_reasonflags.22?Vector<RestrictionReason>Contains the reason why access to this message must be restricted.
ttl_periodflags.25?intTime To Live of the message, once message.date+message.ttl_period === time(), the message will be deleted on the server, and must be deleted locally as well.
-

Type

-

Message

-

Related pages

-

Mentions

-

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

-

Scheduled messages

-

Telegram allows scheduling messages

-

Pinned messages

-

Telegram allows pinning multiple messages on top of a specific chat.

-

Styled text with message entities

-

How to create styled text with message entities

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

-

messages.sendMultiMedia

-

Send an album or grouped media

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionBotAllowed.html b/data/core.telegram.org/constructor/messageActionBotAllowed.html deleted file mode 100644 index fa06938c18..0000000000 --- a/data/core.telegram.org/constructor/messageActionBotAllowed.html +++ /dev/null @@ -1,149 +0,0 @@ - - - - - messageActionBotAllowed - - - - - - - - - - - - - -
- -
-
-
- -

messageActionBotAllowed

- -

The domain name of the website on which the user has logged in. More about Telegram Login »

-

- -
-
messageActionBotAllowed#abe9affe domain:string = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
domainstringThe domain name of the website on which the user has logged in.
-

Type

-

MessageAction

-

Related pages

-

Telegram Login Widget

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionChannelMigrateFrom.html b/data/core.telegram.org/constructor/messageActionChannelMigrateFrom.html deleted file mode 100644 index d636a24ab6..0000000000 --- a/data/core.telegram.org/constructor/messageActionChannelMigrateFrom.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messageActionChannelMigrateFrom - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChannelMigrateFrom

- -

Indicates the channel was migrated from the specified chat

-

- -
-
messageActionChannelMigrateFrom#ea3948e9 title:string chat_id:long = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
titlestringThe old chat tite
chat_idlongThe old chat ID
-

Type

-

MessageAction

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionChatAddUser.html b/data/core.telegram.org/constructor/messageActionChatAddUser.html deleted file mode 100644 index 659e185341..0000000000 --- a/data/core.telegram.org/constructor/messageActionChatAddUser.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionChatAddUser - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChatAddUser

- -

New member in the group

-

- -
-
messageActionChatAddUser#15cefd00 users:Vector<long> = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
usersVector<long>Users that were invited to the chat
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionChatCreate.html b/data/core.telegram.org/constructor/messageActionChatCreate.html deleted file mode 100644 index c4c19cf60d..0000000000 --- a/data/core.telegram.org/constructor/messageActionChatCreate.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageActionChatCreate - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChatCreate

- -

Group created

-

- -
-
messageActionChatCreate#bd47cbad title:string users:Vector<long> = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
titlestringGroup name
usersVector<long>List of group members
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionChatDeleteUser.html b/data/core.telegram.org/constructor/messageActionChatDeleteUser.html deleted file mode 100644 index 7ea47c2b29..0000000000 --- a/data/core.telegram.org/constructor/messageActionChatDeleteUser.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionChatDeleteUser - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChatDeleteUser

- -

User left the group.

-

- -
-
messageActionChatDeleteUser#a43f30cc user_id:long = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongLeaving user ID
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionChatEditPhoto.html b/data/core.telegram.org/constructor/messageActionChatEditPhoto.html deleted file mode 100644 index 43c505f3d8..0000000000 --- a/data/core.telegram.org/constructor/messageActionChatEditPhoto.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionChatEditPhoto - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChatEditPhoto

- -

Group profile changed

-

- -
-
messageActionChatEditPhoto#7fcb13a8 photo:Photo = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
photoPhotoNew group pofile photo
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionChatEditTitle.html b/data/core.telegram.org/constructor/messageActionChatEditTitle.html deleted file mode 100644 index 5dd19c081d..0000000000 --- a/data/core.telegram.org/constructor/messageActionChatEditTitle.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionChatEditTitle - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChatEditTitle

- -

Group name changed.

-

- -
-
messageActionChatEditTitle#b5a1ce5a title:string = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
titlestringNew group name
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionChatJoinedByLink.html b/data/core.telegram.org/constructor/messageActionChatJoinedByLink.html deleted file mode 100644 index a5365fcde3..0000000000 --- a/data/core.telegram.org/constructor/messageActionChatJoinedByLink.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionChatJoinedByLink - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChatJoinedByLink

- -

A user joined the chat via an invite link

-

- -
-
messageActionChatJoinedByLink#31224c3 inviter_id:long = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
inviter_idlongID of the user that created the invite link
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionChatMigrateTo.html b/data/core.telegram.org/constructor/messageActionChatMigrateTo.html deleted file mode 100644 index 323bec7d1a..0000000000 --- a/data/core.telegram.org/constructor/messageActionChatMigrateTo.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - messageActionChatMigrateTo - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChatMigrateTo

- -

Indicates the chat was migrated to the specified supergroup

-

- -
-
messageActionChatMigrateTo#e1037f92 channel_id:long = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
channel_idlongThe supergroup it was migrated to
-

Type

-

MessageAction

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionContactSignUp.html b/data/core.telegram.org/constructor/messageActionContactSignUp.html deleted file mode 100644 index 0086008c26..0000000000 --- a/data/core.telegram.org/constructor/messageActionContactSignUp.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messageActionContactSignUp - - - - - - - - - - - - - -
- -
-
-
- -

messageActionContactSignUp

- -

A contact just signed up to telegram

-

- -
-
messageActionContactSignUp#f3f25f76 = MessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionCustomAction.html b/data/core.telegram.org/constructor/messageActionCustomAction.html deleted file mode 100644 index 0035330426..0000000000 --- a/data/core.telegram.org/constructor/messageActionCustomAction.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionCustomAction - - - - - - - - - - - - - -
- -
-
-
- -

messageActionCustomAction

- -

Custom action (most likely not supported by the current layer, an upgrade might be needed)

-

- -
-
messageActionCustomAction#fae69f56 message:string = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
messagestringAction message
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionEmpty.html b/data/core.telegram.org/constructor/messageActionEmpty.html deleted file mode 100644 index a886e79552..0000000000 --- a/data/core.telegram.org/constructor/messageActionEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messageActionEmpty - - - - - - - - - - - - - -
- -
-
-
- -

messageActionEmpty

- -

Empty constructor.

-

- -
-
messageActionEmpty#b6aef7b0 = MessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionGameScore.html b/data/core.telegram.org/constructor/messageActionGameScore.html deleted file mode 100644 index 1a4ae26249..0000000000 --- a/data/core.telegram.org/constructor/messageActionGameScore.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageActionGameScore - - - - - - - - - - - - - -
- -
-
-
- -

messageActionGameScore

- -

Someone scored in a game

-

- -
-
messageActionGameScore#92a72876 game_id:long score:int = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
game_idlongGame ID
scoreintScore
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionGroupCall.html b/data/core.telegram.org/constructor/messageActionGroupCall.html deleted file mode 100644 index 793f748714..0000000000 --- a/data/core.telegram.org/constructor/messageActionGroupCall.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messageActionGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

messageActionGroupCall

- -

The group call has ended

-

- -
-
messageActionGroupCall#7a0d7f42 flags:# call:InputGroupCall duration:flags.0?int = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
callInputGroupCallGroup call
durationflags.0?intGroup call duration
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionGroupCallScheduled.html b/data/core.telegram.org/constructor/messageActionGroupCallScheduled.html deleted file mode 100644 index a089ad27f7..0000000000 --- a/data/core.telegram.org/constructor/messageActionGroupCallScheduled.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageActionGroupCallScheduled - - - - - - - - - - - - - -
- -
-
-
- -

messageActionGroupCallScheduled

- -

A group call was scheduled

-

- -
-
messageActionGroupCallScheduled#b3a07661 call:InputGroupCall schedule_date:int = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallThe group call
schedule_dateintWhen is this group call scheduled to start
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionHistoryClear.html b/data/core.telegram.org/constructor/messageActionHistoryClear.html deleted file mode 100644 index 5244cb2c65..0000000000 --- a/data/core.telegram.org/constructor/messageActionHistoryClear.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messageActionHistoryClear - - - - - - - - - - - - - -
- -
-
-
- -

messageActionHistoryClear

- -

Chat history was cleared

-

- -
-
messageActionHistoryClear#9fbab604 = MessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionPaymentSent.html b/data/core.telegram.org/constructor/messageActionPaymentSent.html deleted file mode 100644 index 2fb384462f..0000000000 --- a/data/core.telegram.org/constructor/messageActionPaymentSent.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - messageActionPaymentSent - - - - - - - - - - - - - -
- -
-
-
- -

messageActionPaymentSent

- -

A payment was sent

-

- -
-
messageActionPaymentSent#40699cd0 currency:string total_amount:long = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
currencystringThree-letter ISO 4217 currency code
total_amountlongPrice of the product in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
-

Type

-

MessageAction

-

Related pages

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionPaymentSentMe.html b/data/core.telegram.org/constructor/messageActionPaymentSentMe.html deleted file mode 100644 index ad0a6554e0..0000000000 --- a/data/core.telegram.org/constructor/messageActionPaymentSentMe.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - messageActionPaymentSentMe - - - - - - - - - - - - - -
- -
-
-
- -

messageActionPaymentSentMe

- -

A user just sent a payment to me (a bot)

-

- -
-
messageActionPaymentSentMe#8f31b327 flags:# currency:string total_amount:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string charge:PaymentCharge = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
currencystringThree-letter ISO 4217 currency code
total_amountlongPrice of the product in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
payloadbytesBot specified invoice payload
infoflags.0?PaymentRequestedInfoOrder info provided by the user
shipping_option_idflags.1?stringIdentifier of the shipping option chosen by the user
chargePaymentChargeProvider payment identifier
-

Type

-

MessageAction

-

Related pages

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionPhoneCall.html b/data/core.telegram.org/constructor/messageActionPhoneCall.html deleted file mode 100644 index a810e4e061..0000000000 --- a/data/core.telegram.org/constructor/messageActionPhoneCall.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - messageActionPhoneCall - - - - - - - - - - - - - -
- -
-
-
- -

messageActionPhoneCall

- -

A phone call

-

- -
-
messageActionPhoneCall#80e11a7f flags:# video:flags.2?true call_id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.2?trueIs this a video call?
call_idlongCall ID
reasonflags.0?PhoneCallDiscardReasonIf the call has ended, the reason why it ended
durationflags.1?intDuration of the call in seconds
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionPinMessage.html b/data/core.telegram.org/constructor/messageActionPinMessage.html deleted file mode 100644 index ad5c92c963..0000000000 --- a/data/core.telegram.org/constructor/messageActionPinMessage.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messageActionPinMessage - - - - - - - - - - - - - -
- -
-
-
- -

messageActionPinMessage

- -

A message was pinned

-

- -
-
messageActionPinMessage#94bd38ed = MessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionSecureValuesSent.html b/data/core.telegram.org/constructor/messageActionSecureValuesSent.html deleted file mode 100644 index 8720707f39..0000000000 --- a/data/core.telegram.org/constructor/messageActionSecureValuesSent.html +++ /dev/null @@ -1,149 +0,0 @@ - - - - - messageActionSecureValuesSent - - - - - - - - - - - - - -
- -
-
-
- -

messageActionSecureValuesSent

- -

Request for secure telegram passport values was sent

-

- -
-
messageActionSecureValuesSent#d95c6154 types:Vector<SecureValueType> = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
typesVector<SecureValueType>Secure value types
-

Type

-

MessageAction

-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionSecureValuesSentMe.html b/data/core.telegram.org/constructor/messageActionSecureValuesSentMe.html deleted file mode 100644 index e243bdbd9e..0000000000 --- a/data/core.telegram.org/constructor/messageActionSecureValuesSentMe.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - messageActionSecureValuesSentMe - - - - - - - - - - - - - -
- -
-
-
- -

messageActionSecureValuesSentMe

- -

Secure telegram passport values were received

-

- -
-
messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
valuesVector<SecureValue>Vector with information about documents and other Telegram Passport elements that were shared with the bot
credentialsSecureCredentialsEncryptedEncrypted credentials required to decrypt the data
-

Type

-

MessageAction

-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionSetChatTheme.html b/data/core.telegram.org/constructor/messageActionSetChatTheme.html deleted file mode 100644 index 6dcc4af289..0000000000 --- a/data/core.telegram.org/constructor/messageActionSetChatTheme.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionSetChatTheme - - - - - - - - - - - - - -
- -
-
-
- -

messageActionSetChatTheme

- -

The chat theme was changed

-

- -
-
messageActionSetChatTheme#aa786345 emoticon:string = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
emoticonstringThe emoji that identifies a chat theme
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageActionSetMessagesTTL.html b/data/core.telegram.org/constructor/messageActionSetMessagesTTL.html deleted file mode 100644 index c3331eea07..0000000000 --- a/data/core.telegram.org/constructor/messageActionSetMessagesTTL.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionSetMessagesTTL - - - - - - - - - - - - - -
- -
-
-
- -

messageActionSetMessagesTTL

- -

The Time-To-Live of messages in this chat was changed.

-

- -
-
messageActionSetMessagesTTL#aa1afbfd period:int = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
periodintNew Time-To-Live
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEmpty.html b/data/core.telegram.org/constructor/messageEmpty.html deleted file mode 100644 index 9785a0e652..0000000000 --- a/data/core.telegram.org/constructor/messageEmpty.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messageEmpty - - - - - - - - - - - - - -
- -
-
-
- -

messageEmpty

- -

Empty constructor, non-existent message.

-

- -
-
messageEmpty#90a6ca84 flags:# id:int peer_id:flags.0?Peer = Message;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idintMessage identifier
peer_idflags.0?PeerPeer ID, the chat where this message was sent
-

Type

-

Message

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityBankCard.html b/data/core.telegram.org/constructor/messageEntityBankCard.html deleted file mode 100644 index d1dc75a1f5..0000000000 --- a/data/core.telegram.org/constructor/messageEntityBankCard.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityBankCard - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityBankCard

- -

Indicates a credit card number

-

- -
-
messageEntityBankCard#761e6af4 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityBlockquote.html b/data/core.telegram.org/constructor/messageEntityBlockquote.html deleted file mode 100644 index 818551c8ff..0000000000 --- a/data/core.telegram.org/constructor/messageEntityBlockquote.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityBlockquote - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityBlockquote

- -

Message entity representing a block quote.

-

- -
-
messageEntityBlockquote#20df5d0 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityBold.html b/data/core.telegram.org/constructor/messageEntityBold.html deleted file mode 100644 index e140938aa8..0000000000 --- a/data/core.telegram.org/constructor/messageEntityBold.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityBold - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityBold

- -

Message entity representing bold text.

-

- -
-
messageEntityBold#bd610bc9 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityBotCommand.html b/data/core.telegram.org/constructor/messageEntityBotCommand.html deleted file mode 100644 index 594b2c97b6..0000000000 --- a/data/core.telegram.org/constructor/messageEntityBotCommand.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityBotCommand - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityBotCommand

- -

Message entity representing a bot /command

-

- -
-
messageEntityBotCommand#6cef8ac7 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityCashtag.html b/data/core.telegram.org/constructor/messageEntityCashtag.html deleted file mode 100644 index 723fe1a2a9..0000000000 --- a/data/core.telegram.org/constructor/messageEntityCashtag.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityCashtag - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityCashtag

- -

Message entity representing a $cashtag.

-

- -
-
messageEntityCashtag#4c4e743f offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityCode.html b/data/core.telegram.org/constructor/messageEntityCode.html deleted file mode 100644 index dbb8132c6d..0000000000 --- a/data/core.telegram.org/constructor/messageEntityCode.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityCode - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityCode

- -

Message entity representing a codeblock.

-

- -
-
messageEntityCode#28a20571 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityEmail.html b/data/core.telegram.org/constructor/messageEntityEmail.html deleted file mode 100644 index 99324ce92b..0000000000 --- a/data/core.telegram.org/constructor/messageEntityEmail.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityEmail - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityEmail

- -

Message entity representing an email@example.com.

-

- -
-
messageEntityEmail#64e475c2 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityHashtag.html b/data/core.telegram.org/constructor/messageEntityHashtag.html deleted file mode 100644 index f216b8463a..0000000000 --- a/data/core.telegram.org/constructor/messageEntityHashtag.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityHashtag - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityHashtag

- -

#hashtag message entity

-

- -
-
messageEntityHashtag#6f635b0d offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityItalic.html b/data/core.telegram.org/constructor/messageEntityItalic.html deleted file mode 100644 index 598c5f0a32..0000000000 --- a/data/core.telegram.org/constructor/messageEntityItalic.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityItalic - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityItalic

- -

Message entity representing italic text.

-

- -
-
messageEntityItalic#826f8b60 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityMention.html b/data/core.telegram.org/constructor/messageEntityMention.html deleted file mode 100644 index 4584daf19d..0000000000 --- a/data/core.telegram.org/constructor/messageEntityMention.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messageEntityMention - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityMention

- -

Message entity mentioning the current user

-

- -
-
messageEntityMention#fa04579d offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

-

Related pages

-

Mentions

-

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityMentionName.html b/data/core.telegram.org/constructor/messageEntityMentionName.html deleted file mode 100644 index efcaa4849f..0000000000 --- a/data/core.telegram.org/constructor/messageEntityMentionName.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messageEntityMentionName - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityMentionName

- -

Message entity representing a user mention: for creating a mention use inputMessageEntityMentionName.

-

- -
-
messageEntityMentionName#dc7b1140 offset:int length:int user_id:long = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
user_idlongIdentifier of the user that was mentioned
-

Type

-

MessageEntity

-

Related pages

-

Mentions

-

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

-

inputMessageEntityMentionName

-

Message entity that can be used to create a user user mention: received mentions use the messageEntityMentionName constructor, instead.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityPhone.html b/data/core.telegram.org/constructor/messageEntityPhone.html deleted file mode 100644 index 794f1b0197..0000000000 --- a/data/core.telegram.org/constructor/messageEntityPhone.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityPhone - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityPhone

- -

Message entity representing a phone number.

-

- -
-
messageEntityPhone#9b69e34b offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityPre.html b/data/core.telegram.org/constructor/messageEntityPre.html deleted file mode 100644 index 14e32ff352..0000000000 --- a/data/core.telegram.org/constructor/messageEntityPre.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messageEntityPre - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityPre

- -

Message entity representing a preformatted codeblock, allowing the user to specify a programming language for the codeblock.

-

- -
-
messageEntityPre#73924be0 offset:int length:int language:string = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
languagestringProgramming language of the code
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityStrike.html b/data/core.telegram.org/constructor/messageEntityStrike.html deleted file mode 100644 index 78281e474d..0000000000 --- a/data/core.telegram.org/constructor/messageEntityStrike.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityStrike - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityStrike

- -

Message entity representing strikethrough text.

-

- -
-
messageEntityStrike#bf0693d4 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityTextUrl.html b/data/core.telegram.org/constructor/messageEntityTextUrl.html deleted file mode 100644 index 00a81ee79b..0000000000 --- a/data/core.telegram.org/constructor/messageEntityTextUrl.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - messageEntityTextUrl - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityTextUrl

- -

Message entity representing a text url: for in-text urls like https://google.com use messageEntityUrl.

-

- -
-
messageEntityTextUrl#76a6d327 offset:int length:int url:string = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
urlstringThe actual URL
-

Type

-

MessageEntity

-

Related pages

-

messageEntityUrl

-

Message entity representing an in-text url: https://google.com; for text urls, use messageEntityTextUrl.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityUnderline.html b/data/core.telegram.org/constructor/messageEntityUnderline.html deleted file mode 100644 index a74348e32e..0000000000 --- a/data/core.telegram.org/constructor/messageEntityUnderline.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityUnderline - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityUnderline

- -

Message entity representing underlined text.

-

- -
-
messageEntityUnderline#9c4e7e8b offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityUnknown.html b/data/core.telegram.org/constructor/messageEntityUnknown.html deleted file mode 100644 index bb67ce7f8c..0000000000 --- a/data/core.telegram.org/constructor/messageEntityUnknown.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityUnknown - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityUnknown

- -

Unknown message entity

-

- -
-
messageEntityUnknown#bb92ba95 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageEntityUrl.html b/data/core.telegram.org/constructor/messageEntityUrl.html deleted file mode 100644 index 87ec3fe3e0..0000000000 --- a/data/core.telegram.org/constructor/messageEntityUrl.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messageEntityUrl - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityUrl

- -

Message entity representing an in-text url: https://google.com; for text urls, use messageEntityTextUrl.

-

- -
-
messageEntityUrl#6ed02538 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

-

Related pages

-

messageEntityTextUrl

-

Message entity representing a text url: for in-text urls like https://google.com use messageEntityUrl.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageFwdHeader.html b/data/core.telegram.org/constructor/messageFwdHeader.html deleted file mode 100644 index bbfc984d74..0000000000 --- a/data/core.telegram.org/constructor/messageFwdHeader.html +++ /dev/null @@ -1,195 +0,0 @@ - - - - - messageFwdHeader - - - - - - - - - - - - - -
- -
-
-
- -

messageFwdHeader

- -

Info about a forwarded message

-

- -
-
messageFwdHeader#5f777dce flags:# imported:flags.7?true from_id:flags.0?Peer from_name:flags.5?string date:int channel_post:flags.2?int post_author:flags.3?string saved_from_peer:flags.4?Peer saved_from_msg_id:flags.4?int psa_type:flags.6?string = MessageFwdHeader;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
importedflags.7?trueWhether this message was imported from a foreign chat service, click here for more info »
from_idflags.0?PeerThe ID of the user that originally sent the message
from_nameflags.5?stringThe name of the user that originally sent the message
dateintWhen was the message originally sent
channel_postflags.2?intID of the channel message that was forwarded
post_authorflags.3?stringFor channels and if signatures are enabled, author of the channel message
saved_from_peerflags.4?PeerOnly for messages forwarded to the current user (inputPeerSelf), full info about the user/channel that originally sent the message
saved_from_msg_idflags.4?intOnly for messages forwarded to the current user (inputPeerSelf), ID of the message that was forwarded from the original user/channel
psa_typeflags.6?stringPSA type
-

Type

-

MessageFwdHeader

-

Related pages

-

Imported messages

-

Telegram allows importing messages and media from foreign chat apps.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageInteractionCounters.html b/data/core.telegram.org/constructor/messageInteractionCounters.html deleted file mode 100644 index 4c189ab684..0000000000 --- a/data/core.telegram.org/constructor/messageInteractionCounters.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messageInteractionCounters - - - - - - - - - - - - - -
- -
-
-
- -

messageInteractionCounters

- -

Message interaction counters

-

- -
-
messageInteractionCounters#ad4fc9bd msg_id:int views:int forwards:int = MessageInteractionCounters;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
msg_idintMessage ID
viewsintViews
forwardsintNumber of times this message was forwarded
-

Type

-

MessageInteractionCounters

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaAudio.html b/data/core.telegram.org/constructor/messageMediaAudio.html deleted file mode 100644 index 4b99bc798d..0000000000 --- a/data/core.telegram.org/constructor/messageMediaAudio.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageMediaAudio - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaAudio

- -

Attached audio file.

-

- -
-
Constructor schema is available as of layer 46. Switch »

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
audioAudioAudi file
-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaDice.html b/data/core.telegram.org/constructor/messageMediaDice.html deleted file mode 100644 index 5a50eab126..0000000000 --- a/data/core.telegram.org/constructor/messageMediaDice.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messageMediaDice - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaDice

- -

Dice-based animated sticker

-

- -
-
messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
valueintDice value
emoticonstringThe emoji, for now 🏀, 🎲 and 🎯 are supported
-

Type

-

MessageMedia

-

Related pages

-

Dice

-

Telegram supports sending animated dice emojis.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaDocument.html b/data/core.telegram.org/constructor/messageMediaDocument.html deleted file mode 100644 index bd23851587..0000000000 --- a/data/core.telegram.org/constructor/messageMediaDocument.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messageMediaDocument - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaDocument

- -

Document (video, audio, voice, sticker, any media type except photo)

-

- -
-
messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
documentflags.0?DocumentAttached document
ttl_secondsflags.2?intTime to live of self-destructing document
-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaEmpty.html b/data/core.telegram.org/constructor/messageMediaEmpty.html deleted file mode 100644 index a4d518f5b4..0000000000 --- a/data/core.telegram.org/constructor/messageMediaEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messageMediaEmpty - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaEmpty

- -

Empty constructor.

-

- -
-
messageMediaEmpty#3ded6320 = MessageMedia;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaGame.html b/data/core.telegram.org/constructor/messageMediaGame.html deleted file mode 100644 index e439d34c75..0000000000 --- a/data/core.telegram.org/constructor/messageMediaGame.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageMediaGame - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaGame

- -

Telegram game

-

- -
-
messageMediaGame#fdb19008 game:Game = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
gameGameGame
-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaGeo.html b/data/core.telegram.org/constructor/messageMediaGeo.html deleted file mode 100644 index 3bcf17c634..0000000000 --- a/data/core.telegram.org/constructor/messageMediaGeo.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageMediaGeo - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaGeo

- -

Attached map.

-

- -
-
messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
geoGeoPointGeoPoint
-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaGeoLive.html b/data/core.telegram.org/constructor/messageMediaGeoLive.html deleted file mode 100644 index fa4967169f..0000000000 --- a/data/core.telegram.org/constructor/messageMediaGeoLive.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - messageMediaGeoLive - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaGeoLive

- -

Indicates a live geolocation

-

- -
-
messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
geoGeoPointGeolocation
headingflags.0?intFor live locations, a direction in which the location moves, in degrees; 1-360
periodintValidity period of provided geolocation
proximity_notification_radiusflags.1?intFor live locations, a maximum distance to another chat member for proximity alerts, in meters (0-100000).
-

Type

-

MessageMedia

-

Related pages

-

Live geolocation

-

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaInvoice.html b/data/core.telegram.org/constructor/messageMediaInvoice.html deleted file mode 100644 index e06d694510..0000000000 --- a/data/core.telegram.org/constructor/messageMediaInvoice.html +++ /dev/null @@ -1,198 +0,0 @@ - - - - - messageMediaInvoice - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaInvoice

- -

Invoice

-

- -
-
messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
shipping_address_requestedflags.1?trueWhether the shipping address was requested
testflags.3?trueWhether this is an example invoice
titlestringProduct name, 1-32 characters
descriptionstringProduct description, 1-255 characters
photoflags.0?WebDocumentURL of the product photo for the invoice. Can be a photo of the goods or a marketing image for a service. People like it better when they see what they are paying for.
receipt_msg_idflags.2?intMessage ID of receipt: if set, clients should change the text of the first keyboardButtonBuy button always attached to the message to a localized version of the word Receipt
currencystringThree-letter ISO 4217 currency code
total_amountlongTotal price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
start_paramstringUnique bot deep-linking parameter that can be used to generate this invoice
-

Type

-

MessageMedia

-

Related pages

-

keyboardButtonBuy

-

Button to buy a product

-

message

-

A message

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaPhoto.html b/data/core.telegram.org/constructor/messageMediaPhoto.html deleted file mode 100644 index 71475f35d0..0000000000 --- a/data/core.telegram.org/constructor/messageMediaPhoto.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messageMediaPhoto - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaPhoto

- -

Attached photo.

-

- -
-
messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
photoflags.0?PhotoPhoto
ttl_secondsflags.2?intTime to live in seconds of self-destructing photo
-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaPoll.html b/data/core.telegram.org/constructor/messageMediaPoll.html deleted file mode 100644 index d68156fd1b..0000000000 --- a/data/core.telegram.org/constructor/messageMediaPoll.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageMediaPoll - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaPoll

- -

Poll

-

- -
-
messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
pollPollThe poll
resultsPollResultsThe results of the poll
-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaUnsupported.html b/data/core.telegram.org/constructor/messageMediaUnsupported.html deleted file mode 100644 index 0a7a4728fc..0000000000 --- a/data/core.telegram.org/constructor/messageMediaUnsupported.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messageMediaUnsupported - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaUnsupported

- -

Current version of the client does not support this media type.

-

- -
-
messageMediaUnsupported#9f84f49e = MessageMedia;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaVenue.html b/data/core.telegram.org/constructor/messageMediaVenue.html deleted file mode 100644 index 5bcb778635..0000000000 --- a/data/core.telegram.org/constructor/messageMediaVenue.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messageMediaVenue - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaVenue

- -

Venue

-

- -
-
messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
geoGeoPointGeolocation of venue
titlestringVenue name
addressstringAddress
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
venue_typestringVenue type in the provider's database
-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaVideo.html b/data/core.telegram.org/constructor/messageMediaVideo.html deleted file mode 100644 index c2832334c5..0000000000 --- a/data/core.telegram.org/constructor/messageMediaVideo.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageMediaVideo - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaVideo

- -

Attached video.

-

- -
-
Constructor schema is available as of layer 28. Switch »

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
videoVideoVideo
-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageMediaWebPage.html b/data/core.telegram.org/constructor/messageMediaWebPage.html deleted file mode 100644 index 0de3ffed8f..0000000000 --- a/data/core.telegram.org/constructor/messageMediaWebPage.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageMediaWebPage - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaWebPage

- -

Preview of webpage

-

- -
-
messageMediaWebPage#a32dd600 webpage:WebPage = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
webpageWebPageWebpage preview
-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageRange.html b/data/core.telegram.org/constructor/messageRange.html deleted file mode 100644 index 3b73eaecdb..0000000000 --- a/data/core.telegram.org/constructor/messageRange.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageRange - - - - - - - - - - - - - -
- -
-
-
- -

messageRange

- -

Indicates a range of chat messages

-

- -
-
messageRange#ae30253 min_id:int max_id:int = MessageRange;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
min_idintStart of range (message ID)
max_idintEnd of range (message ID)
-

Type

-

MessageRange

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageReplies.html b/data/core.telegram.org/constructor/messageReplies.html deleted file mode 100644 index e180f705fa..0000000000 --- a/data/core.telegram.org/constructor/messageReplies.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - messageReplies - - - - - - - - - - - - - -
- -
-
-
- -

messageReplies

- -

Info about the comment section of a channel post, or a simple message thread

-

- -
-
messageReplies#83d60fc2 flags:# comments:flags.0?true replies:int replies_pts:int recent_repliers:flags.1?Vector<Peer> channel_id:flags.0?long max_id:flags.2?int read_max_id:flags.3?int = MessageReplies;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
commentsflags.0?trueWhether this constructor contains information about the comment section of a channel post, or a simple message thread
repliesintContains the total number of replies in this thread or comment section.
replies_ptsintPTS of the message that started this thread.
recent_repliersflags.1?Vector<Peer>For channel post comments, contains information about the last few comment posters for a specific thread, to show a small list of commenter profile pictures in client previews.
channel_idflags.0?longFor channel post comments, contains the ID of the associated discussion supergroup
max_idflags.2?intID of the latest message in this thread or comment section.
read_max_idflags.3?intContains the ID of the latest read message in this thread or comment section.
-

Type

-

MessageReplies

-

Related pages

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Discussion groups

-

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageReplyHeader.html b/data/core.telegram.org/constructor/messageReplyHeader.html deleted file mode 100644 index e662887c71..0000000000 --- a/data/core.telegram.org/constructor/messageReplyHeader.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - messageReplyHeader - - - - - - - - - - - - - -
- -
-
-
- -

messageReplyHeader

- -

Message replies and thread information

-

- -
-
messageReplyHeader#a6d57763 flags:# reply_to_msg_id:int reply_to_peer_id:flags.0?Peer reply_to_top_id:flags.1?int = MessageReplyHeader;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
reply_to_msg_idintID of message to which this message is replying
reply_to_peer_idflags.0?PeerFor replies sent in channel discussion threads of which the current user is not a member, the discussion group ID
reply_to_top_idflags.1?intID of the message that started this message thread
-

Type

-

MessageReplyHeader

-

Related pages

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageService.html b/data/core.telegram.org/constructor/messageService.html deleted file mode 100644 index f226f554e6..0000000000 --- a/data/core.telegram.org/constructor/messageService.html +++ /dev/null @@ -1,212 +0,0 @@ - - - - - messageService - - - - - - - - - - - - - -
- -
-
-
- -

messageService

- -

Indicates a service message

-

- -
-
messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
outflags.1?trueWhether the message is outgoing
mentionedflags.4?trueWhether we were mentioned in the message
media_unreadflags.5?trueWhether the message contains unread media
silentflags.13?trueWhether the message is silent
postflags.14?trueWhether it's a channel post
legacyflags.19?trueThis is a legacy message: it has to be refetched with the new layer
idintMessage ID
from_idflags.8?PeerID of the sender of this message
peer_idPeerSender of service message
reply_toflags.3?MessageReplyHeaderReply (thread) information
dateintMessage date
actionMessageActionEvent connected with the service message
ttl_periodflags.25?intTime To Live of the message, once message.date+message.ttl_period === time(), the message will be deleted on the server, and must be deleted locally as well.
-

Type

-

Message

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageUserVote.html b/data/core.telegram.org/constructor/messageUserVote.html deleted file mode 100644 index 03592d4f54..0000000000 --- a/data/core.telegram.org/constructor/messageUserVote.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messageUserVote - - - - - - - - - - - - - -
- -
-
-
- -

messageUserVote

- -

How a user voted in a poll

-

- -
-
messageUserVote#34d247b4 user_id:long option:bytes date:int = MessageUserVote;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser ID
optionbytesThe option chosen by the user
dateintWhen did the user cast the vote
-

Type

-

MessageUserVote

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageUserVoteInputOption.html b/data/core.telegram.org/constructor/messageUserVoteInputOption.html deleted file mode 100644 index c1c8117b11..0000000000 --- a/data/core.telegram.org/constructor/messageUserVoteInputOption.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messageUserVoteInputOption - - - - - - - - - - - - - -
- -
-
-
- -

messageUserVoteInputOption

- -

How a user voted in a poll (reduced constructor, returned if an option was provided to messages.getPollVotes)

-

- -
-
messageUserVoteInputOption#3ca5b0ec user_id:long date:int = MessageUserVote;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongThe user that voted for the queried option
dateintWhen did the user cast the vote
-

Type

-

MessageUserVote

-

Related pages

-

messages.getPollVotes

-

Get poll results for non-anonymous polls

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageUserVoteMultiple.html b/data/core.telegram.org/constructor/messageUserVoteMultiple.html deleted file mode 100644 index c9e22bf08a..0000000000 --- a/data/core.telegram.org/constructor/messageUserVoteMultiple.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messageUserVoteMultiple - - - - - - - - - - - - - -
- -
-
-
- -

messageUserVoteMultiple

- -

How a user voted in a multiple-choice poll

-

- -
-
messageUserVoteMultiple#8a65e557 user_id:long options:Vector<bytes> date:int = MessageUserVote;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser ID
optionsVector<bytes>Options chosen by the user
dateintWhen did the user cast their votes
-

Type

-

MessageUserVote

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messageViews.html b/data/core.telegram.org/constructor/messageViews.html deleted file mode 100644 index 8c03b860d4..0000000000 --- a/data/core.telegram.org/constructor/messageViews.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - messageViews - - - - - - - - - - - - - -
- -
-
-
- -

messageViews

- -

View, forward counter + info about replies of a specific message

-

- -
-
messageViews#455b853d flags:# views:flags.0?int forwards:flags.1?int replies:flags.2?MessageReplies = MessageViews;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
viewsflags.0?intViewcount of message
forwardsflags.1?intForward count of message
repliesflags.2?MessageRepliesReply and thread information of message
-

Type

-

MessageViews

-

Related pages

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.affectedFoundMessages b/data/core.telegram.org/constructor/messages.affectedFoundMessages deleted file mode 100644 index f955fe1dfe..0000000000 --- a/data/core.telegram.org/constructor/messages.affectedFoundMessages +++ /dev/null @@ -1,165 +0,0 @@ - - - - - messages.affectedFoundMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.affectedFoundMessages

- -

Messages found and affected by changes

-

- -
-
messages.affectedFoundMessages#ef8d3e6c pts:int pts_count:int offset:int messages:Vector<int> = messages.AffectedFoundMessages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
ptsintEvent count after generation
pts_countintNumber of events that were generated
offsetintIf bigger than zero, the request must be repeated to remove more messages
messagesVector<int>Affected message IDs
-

Type

-

messages.AffectedFoundMessages

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.affectedHistory b/data/core.telegram.org/constructor/messages.affectedHistory deleted file mode 100644 index d8b960021b..0000000000 --- a/data/core.telegram.org/constructor/messages.affectedHistory +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messages.affectedHistory - - - - - - - - - - - - - -
- -
-
-
- -

messages.affectedHistory

- -

Affected part of communication history with the user or in a chat.

-

- -
-
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
ptsintNumber of events occured in a text box
pts_countintNumber of affected events
offsetintIf a parameter contains positive value, it is necessary to repeat the method call using the given value; during the proceeding of all the history the value itself shall gradually decrease
-

Type

-

messages.AffectedHistory

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.affectedMessages b/data/core.telegram.org/constructor/messages.affectedMessages deleted file mode 100644 index 557b694732..0000000000 --- a/data/core.telegram.org/constructor/messages.affectedMessages +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.affectedMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.affectedMessages

- -

Events affected by operation

-

- -
-
messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

messages.AffectedMessages

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.allStickers b/data/core.telegram.org/constructor/messages.allStickers deleted file mode 100644 index 1d5a2403bc..0000000000 --- a/data/core.telegram.org/constructor/messages.allStickers +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.allStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.allStickers

- -

Info about all installed stickers

-

- -
-
messages.allStickers#cdbbcebb hash:long sets:Vector<StickerSet> = messages.AllStickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
setsVector<StickerSet>All stickersets
-

Type

-

messages.AllStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.allStickersNotModified b/data/core.telegram.org/constructor/messages.allStickersNotModified deleted file mode 100644 index 180d8a43b8..0000000000 --- a/data/core.telegram.org/constructor/messages.allStickersNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messages.allStickersNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.allStickersNotModified

- -

Info about all installed stickers hasn't changed

-

- -
-
messages.allStickersNotModified#e86602c3 = messages.AllStickers;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

messages.AllStickers

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.archivedStickers b/data/core.telegram.org/constructor/messages.archivedStickers deleted file mode 100644 index 8d1f505279..0000000000 --- a/data/core.telegram.org/constructor/messages.archivedStickers +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messages.archivedStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.archivedStickers

- -

Archived stickersets

-

- -
-
messages.archivedStickers#4fcba9c8 count:int sets:Vector<StickerSetCovered> = messages.ArchivedStickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countintNumber of archived stickers
setsVector<StickerSetCovered>Archived stickersets
-

Type

-

messages.ArchivedStickers

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.botResults b/data/core.telegram.org/constructor/messages.botResults deleted file mode 100644 index 14ce77f8c6..0000000000 --- a/data/core.telegram.org/constructor/messages.botResults +++ /dev/null @@ -1,182 +0,0 @@ - - - - - messages.botResults - - - - - - - - - - - - - -
- -
-
-
- -

messages.botResults

- -

Result of a query to an inline bot

-

- -
-
messages.botResults#947ca848 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
galleryflags.0?trueWhether the result is a picture gallery
query_idlongQuery ID
next_offsetflags.1?stringThe next offset to use when navigating through results
switch_pmflags.2?InlineBotSwitchPMWhether the bot requested the user to message him in private
resultsVector<BotInlineResult>The results
cache_timeintCaching validity of the results
usersVector<User>Users mentioned in the results
-

Type

-

messages.BotResults

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.chatAdminsWithInvites b/data/core.telegram.org/constructor/messages.chatAdminsWithInvites deleted file mode 100644 index eb2e6e7853..0000000000 --- a/data/core.telegram.org/constructor/messages.chatAdminsWithInvites +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messages.chatAdminsWithInvites - - - - - - - - - - - - - -
- -
-
-
- -

messages.chatAdminsWithInvites

- -

Info about chat invites generated by admins.

-

- -
-
messages.chatAdminsWithInvites#b69b72d7 admins:Vector<ChatAdminWithInvites> users:Vector<User> = messages.ChatAdminsWithInvites;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
adminsVector<ChatAdminWithInvites>Info about chat invites generated by admins.
usersVector<User>Mentioned users
-

Type

-

messages.ChatAdminsWithInvites

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.chatFull b/data/core.telegram.org/constructor/messages.chatFull deleted file mode 100644 index 7f2160eb7a..0000000000 --- a/data/core.telegram.org/constructor/messages.chatFull +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messages.chatFull - - - - - - - - - - - - - -
- -
-
-
- -

messages.chatFull

- -

Extended info on chat and auxiliary data.

-

- -
-
messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.ChatFull;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
full_chatChatFullExtended info on a chat
chatsVector<Chat>List containing basic info on chat
usersVector<User>List of users mentioned above
-

Type

-

messages.ChatFull

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.chatInviteImporters b/data/core.telegram.org/constructor/messages.chatInviteImporters deleted file mode 100644 index 222ee4d54b..0000000000 --- a/data/core.telegram.org/constructor/messages.chatInviteImporters +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messages.chatInviteImporters - - - - - - - - - - - - - -
- -
-
-
- -

messages.chatInviteImporters

- -

Info about the users that joined the chat using a specific chat invite

-

- -
-
messages.chatInviteImporters#81b6b00a count:int importers:Vector<ChatInviteImporter> users:Vector<User> = messages.ChatInviteImporters;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countintNumber of users that joined
importersVector<ChatInviteImporter>The users that joined
usersVector<User>The users that joined
-

Type

-

messages.ChatInviteImporters

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.chats b/data/core.telegram.org/constructor/messages.chats deleted file mode 100644 index cab0da8262..0000000000 --- a/data/core.telegram.org/constructor/messages.chats +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messages.chats - - - - - - - - - - - - - -
- -
-
-
- -

messages.chats

- -

List of chats with auxiliary data.

-

- -
-
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chatsVector<Chat>List of chats
-

Type

-

messages.Chats

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.chatsSlice b/data/core.telegram.org/constructor/messages.chatsSlice deleted file mode 100644 index 22e0895dec..0000000000 --- a/data/core.telegram.org/constructor/messages.chatsSlice +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.chatsSlice - - - - - - - - - - - - - -
- -
-
-
- -

messages.chatsSlice

- -

Partial list of chats, more would have to be fetched with pagination

-

- -
-
messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countintTotal number of results that were found server-side (not all are included in chats)
chatsVector<Chat>Chats
-

Type

-

messages.Chats

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.checkedHistoryImportPeer b/data/core.telegram.org/constructor/messages.checkedHistoryImportPeer deleted file mode 100644 index 43ef5a8c32..0000000000 --- a/data/core.telegram.org/constructor/messages.checkedHistoryImportPeer +++ /dev/null @@ -1,150 +0,0 @@ - - - - - messages.checkedHistoryImportPeer - - - - - - - - - - - - - -
- -
-
-
- -

messages.checkedHistoryImportPeer

- -

Contains a confirmation text to be shown to the user, upon importing chat history, click here for more info ».

-

- -
-
messages.checkedHistoryImportPeer#a24de717 confirm_text:string = messages.CheckedHistoryImportPeer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
confirm_textstringA confirmation text to be shown to the user, upon importing chat history ».
-

Type

-

messages.CheckedHistoryImportPeer

-

Related pages

-

Imported messages

-

Telegram allows importing messages and media from foreign chat apps.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.dhConfig b/data/core.telegram.org/constructor/messages.dhConfig deleted file mode 100644 index afb3f3c3f0..0000000000 --- a/data/core.telegram.org/constructor/messages.dhConfig +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.dhConfig - - - - - - - - - - - - - -
- -
-
-
- -

messages.dhConfig

- -

New set of configuring parameters.

-

- -
-
messages.dhConfig#2c221edd g:int p:bytes version:int random:bytes = messages.DhConfig;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
gintNew value prime, see Wikipedia
pbytesNew value primitive root, see Wikipedia
versionintVestion of set of parameters
randombytesRandom sequence of bytes of assigned length
-

Type

-

messages.DhConfig

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.dhConfigNotModified b/data/core.telegram.org/constructor/messages.dhConfigNotModified deleted file mode 100644 index b364445f51..0000000000 --- a/data/core.telegram.org/constructor/messages.dhConfigNotModified +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messages.dhConfigNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.dhConfigNotModified

- -

Configuring parameters did not change.

-

- -
-
messages.dhConfigNotModified#c0e24635 random:bytes = messages.DhConfig;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
randombytesRandom sequence of bytes of assigned length
-

Type

-

messages.DhConfig

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.dialogsNotModified b/data/core.telegram.org/constructor/messages.dialogsNotModified deleted file mode 100644 index b48535f510..0000000000 --- a/data/core.telegram.org/constructor/messages.dialogsNotModified +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messages.dialogsNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.dialogsNotModified

- -

Dialogs haven't changed

-

- -
-
messages.dialogsNotModified#f0e3e596 count:int = messages.Dialogs;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
countintNumber of dialogs found server-side by the query
-

Type

-

messages.Dialogs

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.dialogsSlice b/data/core.telegram.org/constructor/messages.dialogsSlice deleted file mode 100644 index d1fd165555..0000000000 --- a/data/core.telegram.org/constructor/messages.dialogsSlice +++ /dev/null @@ -1,167 +0,0 @@ - - - - - messages.dialogsSlice - - - - - - - - - - - - - -
- -
-
-
- -

messages.dialogsSlice

- -

Incomplete list of dialogs with messages and auxiliary data.

-

- -
-
messages.dialogsSlice#71e094f3 count:int dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countintTotal number of dialogs
dialogsVector<Dialog>List of dialogs
messagesVector<Message>List of last messages from dialogs
chatsVector<Chat>List of chats mentioned in dialogs
usersVector<User>List of users mentioned in messages and chats
-

Type

-

messages.Dialogs

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.discussionMessage b/data/core.telegram.org/constructor/messages.discussionMessage deleted file mode 100644 index be23222222..0000000000 --- a/data/core.telegram.org/constructor/messages.discussionMessage +++ /dev/null @@ -1,185 +0,0 @@ - - - - - messages.discussionMessage - - - - - - - - - - - - - -
- -
-
-
- -

messages.discussionMessage

- -

Information about a message thread

-

- -
-
messages.discussionMessage#a6341782 flags:# messages:Vector<Message> max_id:flags.0?int read_inbox_max_id:flags.1?int read_outbox_max_id:flags.2?int unread_count:int chats:Vector<Chat> users:Vector<User> = messages.DiscussionMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
messagesVector<Message>Discussion messages
max_idflags.0?intMessage ID of latest reply in this thread
read_inbox_max_idflags.1?intMessage ID of latest read incoming message in this thread
read_outbox_max_idflags.2?intMessage ID of latest read outgoing message in this thread
unread_countintNumber of unread messages
chatsVector<Chat>Chats mentioned in constructor
usersVector<User>Users mentioned in constructor
-

Type

-

messages.DiscussionMessage

-

Related pages

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.exportedChatInvite b/data/core.telegram.org/constructor/messages.exportedChatInvite deleted file mode 100644 index 8d965aabd0..0000000000 --- a/data/core.telegram.org/constructor/messages.exportedChatInvite +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messages.exportedChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

messages.exportedChatInvite

- -

Info about a chat invite

-

- -
-
messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
inviteExportedChatInviteInfo about the chat invite
usersVector<User>Mentioned users
-

Type

-

messages.ExportedChatInvite

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.exportedChatInvites b/data/core.telegram.org/constructor/messages.exportedChatInvites deleted file mode 100644 index 5fbcb7dc5e..0000000000 --- a/data/core.telegram.org/constructor/messages.exportedChatInvites +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messages.exportedChatInvites - - - - - - - - - - - - - -
- -
-
-
- -

messages.exportedChatInvites

- -

Info about chat invites exported by a certain admin.

-

- -
-
messages.exportedChatInvites#bdc62dcc count:int invites:Vector<ExportedChatInvite> users:Vector<User> = messages.ExportedChatInvites;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countintNumber of invites exported by the admin
invitesVector<ExportedChatInvite>Exported invites
usersVector<User>Info about the admin
-

Type

-

messages.ExportedChatInvites

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.favedStickers b/data/core.telegram.org/constructor/messages.favedStickers deleted file mode 100644 index ec70df2b2f..0000000000 --- a/data/core.telegram.org/constructor/messages.favedStickers +++ /dev/null @@ -1,160 +0,0 @@ - - - - - messages.favedStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.favedStickers

- -

Favorited stickers

-

- -
-
messages.favedStickers#2cb51097 hash:long packs:Vector<StickerPack> stickers:Vector<Document> = messages.FavedStickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
packsVector<StickerPack>Emojis associated to stickers
stickersVector<Document>Favorited stickers
-

Type

-

messages.FavedStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.favedStickersNotModified b/data/core.telegram.org/constructor/messages.favedStickersNotModified deleted file mode 100644 index 58f4bbfd2f..0000000000 --- a/data/core.telegram.org/constructor/messages.favedStickersNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messages.favedStickersNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.favedStickersNotModified

- -

No new favorited stickers were found

-

- -
-
messages.favedStickersNotModified#9e8fa6d3 = messages.FavedStickers;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

messages.FavedStickers

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.featuredStickers b/data/core.telegram.org/constructor/messages.featuredStickers deleted file mode 100644 index 256f1725d7..0000000000 --- a/data/core.telegram.org/constructor/messages.featuredStickers +++ /dev/null @@ -1,165 +0,0 @@ - - - - - messages.featuredStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.featuredStickers

- -

Featured stickersets

-

- -
-
messages.featuredStickers#84c02310 hash:long count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
countintTotal number of featured stickers
setsVector<StickerSetCovered>Featured stickersets
unreadVector<long>IDs of new featured stickersets
-

Type

-

messages.FeaturedStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.featuredStickersNotModified b/data/core.telegram.org/constructor/messages.featuredStickersNotModified deleted file mode 100644 index d56e5b5a76..0000000000 --- a/data/core.telegram.org/constructor/messages.featuredStickersNotModified +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messages.featuredStickersNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.featuredStickersNotModified

- -

Featured stickers haven't changed

-

- -
-
messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
countintTotal number of featured stickers
-

Type

-

messages.FeaturedStickers

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.foundStickerSets b/data/core.telegram.org/constructor/messages.foundStickerSets deleted file mode 100644 index 01d19baa25..0000000000 --- a/data/core.telegram.org/constructor/messages.foundStickerSets +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.foundStickerSets - - - - - - - - - - - - - -
- -
-
-
- -

messages.foundStickerSets

- -

Found stickersets

-

- -
-
messages.foundStickerSets#8af09dd2 hash:long sets:Vector<StickerSetCovered> = messages.FoundStickerSets;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
setsVector<StickerSetCovered>Found stickersets
-

Type

-

messages.FoundStickerSets

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.foundStickerSetsNotModified b/data/core.telegram.org/constructor/messages.foundStickerSetsNotModified deleted file mode 100644 index 168fc83b54..0000000000 --- a/data/core.telegram.org/constructor/messages.foundStickerSetsNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messages.foundStickerSetsNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.foundStickerSetsNotModified

- -

No further results were found

-

- -
-
messages.foundStickerSetsNotModified#d54b65d = messages.FoundStickerSets;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

messages.FoundStickerSets

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.highScores b/data/core.telegram.org/constructor/messages.highScores deleted file mode 100644 index a6da22ce25..0000000000 --- a/data/core.telegram.org/constructor/messages.highScores +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messages.highScores - - - - - - - - - - - - - -
- -
-
-
- -

messages.highScores

- -

Highscores in a game

-

- -
-
messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
scoresVector<HighScore>Highscores
usersVector<User>Users, associated to the highscores
-

Type

-

messages.HighScores

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.historyImport b/data/core.telegram.org/constructor/messages.historyImport deleted file mode 100644 index 10daabdd9d..0000000000 --- a/data/core.telegram.org/constructor/messages.historyImport +++ /dev/null @@ -1,150 +0,0 @@ - - - - - messages.historyImport - - - - - - - - - - - - - -
- -
-
-
- -

messages.historyImport

- -

ID of a specific chat import session, click here for more info ».

-

- -
-
messages.historyImport#1662af0b id:long = messages.HistoryImport;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idlongHistory import ID
-

Type

-

messages.HistoryImport

-

Related pages

-

Imported messages

-

Telegram allows importing messages and media from foreign chat apps.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.historyImportParsed b/data/core.telegram.org/constructor/messages.historyImportParsed deleted file mode 100644 index 2c49dcc24e..0000000000 --- a/data/core.telegram.org/constructor/messages.historyImportParsed +++ /dev/null @@ -1,166 +0,0 @@ - - - - - messages.historyImportParsed - - - - - - - - - - - - - -
- -
-
-
- -

messages.historyImportParsed

- -

Contains information about a chat export file generated by a foreign chat app, click here for more info.
-If neither the pm or group flags are set, the specified chat export was generated from a chat of unknown type.

-

- -
-
messages.historyImportParsed#5e0fb7b9 flags:# pm:flags.0?true group:flags.1?true title:flags.2?string = messages.HistoryImportParsed;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
pmflags.0?trueThe chat export file was generated from a private chat.
groupflags.1?trueThe chat export file was generated from a group chat.
titleflags.2?stringTitle of the chat.
-

Type

-

messages.HistoryImportParsed

-

Related pages

-

Imported messages

-

Telegram allows importing messages and media from foreign chat apps.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.inactiveChats b/data/core.telegram.org/constructor/messages.inactiveChats deleted file mode 100644 index a2d77f9780..0000000000 --- a/data/core.telegram.org/constructor/messages.inactiveChats +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messages.inactiveChats - - - - - - - - - - - - - -
- -
-
-
- -

messages.inactiveChats

- -

Inactive chat list

-

- -
-
messages.inactiveChats#a927fec5 dates:Vector<int> chats:Vector<Chat> users:Vector<User> = messages.InactiveChats;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
datesVector<int>When was the chat last active
chatsVector<Chat>Chat list
usersVector<User>Users mentioned in the chat list
-

Type

-

messages.InactiveChats

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.messageEditData b/data/core.telegram.org/constructor/messages.messageEditData deleted file mode 100644 index b36d5f264c..0000000000 --- a/data/core.telegram.org/constructor/messages.messageEditData +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messages.messageEditData - - - - - - - - - - - - - -
- -
-
-
- -

messages.messageEditData

- -

Message edit data for media

-

- -
-
messages.messageEditData#26b5dde6 flags:# caption:flags.0?true = messages.MessageEditData;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
captionflags.0?trueMedia caption, if the specified media's caption can be edited
-

Type

-

messages.MessageEditData

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.messageViews b/data/core.telegram.org/constructor/messages.messageViews deleted file mode 100644 index 4f44796a53..0000000000 --- a/data/core.telegram.org/constructor/messages.messageViews +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messages.messageViews - - - - - - - - - - - - - -
- -
-
-
- -

messages.messageViews

- -

View, forward counter + info about replies

-

- -
-
messages.messageViews#b6c4f543 views:Vector<MessageViews> chats:Vector<Chat> users:Vector<User> = messages.MessageViews;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
viewsVector<MessageViews>View, forward counter + info about replies
chatsVector<Chat>Chats mentioned in constructor
usersVector<User>Users mentioned in constructor
-

Type

-

messages.MessageViews

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.messagesNotModified b/data/core.telegram.org/constructor/messages.messagesNotModified deleted file mode 100644 index df24944e7f..0000000000 --- a/data/core.telegram.org/constructor/messages.messagesNotModified +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messages.messagesNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.messagesNotModified

- -

No new messages matching the query were found

-

- -
-
messages.messagesNotModified#74535f21 count:int = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
countintNumber of results found server-side by the given query
-

Type

-

messages.Messages

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.messagesSlice b/data/core.telegram.org/constructor/messages.messagesSlice deleted file mode 100644 index 03e3f7b7bd..0000000000 --- a/data/core.telegram.org/constructor/messages.messagesSlice +++ /dev/null @@ -1,185 +0,0 @@ - - - - - messages.messagesSlice - - - - - - - - - - - - - -
- -
-
-
- -

messages.messagesSlice

- -

Incomplete list of messages and auxiliary data.

-

- -
-
messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
inexactflags.1?trueIf set, indicates that the results may be inexact
countintTotal number of messages in the list
next_rateflags.0?intRate to use in the offset_rate parameter in the next call to messages.searchGlobal
offset_id_offsetflags.2?intIndicates the absolute position of messages[0] within the total result set with count count.
This is useful, for example, if the result was fetched using offset_id, and we need to display a progress/total counter (like photo 134 of 200, for all media in a chat, we could simply use photo ${offset_id_offset} of ${count}.
messagesVector<Message>List of messages
chatsVector<Chat>List of chats mentioned in messages
usersVector<User>List of users mentioned in messages and chats
-

Type

-

messages.Messages

-

Related pages

-

messages.searchGlobal

-

Search for messages and peers globally

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.peerDialogs b/data/core.telegram.org/constructor/messages.peerDialogs deleted file mode 100644 index 328434af49..0000000000 --- a/data/core.telegram.org/constructor/messages.peerDialogs +++ /dev/null @@ -1,170 +0,0 @@ - - - - - messages.peerDialogs - - - - - - - - - - - - - -
- -
-
-
- -

messages.peerDialogs

- -

Dialog info of multiple peers

-

- -
-
messages.peerDialogs#3371c354 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> state:updates.State = messages.PeerDialogs;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
dialogsVector<Dialog>Dialog info
messagesVector<Message>Messages mentioned in dialog info
chatsVector<Chat>Chats
usersVector<User>Users
stateupdates.StateCurrent update state of dialog
-

Type

-

messages.PeerDialogs

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.recentStickers b/data/core.telegram.org/constructor/messages.recentStickers deleted file mode 100644 index f1320e84a0..0000000000 --- a/data/core.telegram.org/constructor/messages.recentStickers +++ /dev/null @@ -1,165 +0,0 @@ - - - - - messages.recentStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.recentStickers

- -

Recently used stickers

-

- -
-
messages.recentStickers#88d37c56 hash:long packs:Vector<StickerPack> stickers:Vector<Document> dates:Vector<int> = messages.RecentStickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
packsVector<StickerPack>Emojis associated to stickers
stickersVector<Document>Recent stickers
datesVector<int>When was each sticker last used
-

Type

-

messages.RecentStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.recentStickersNotModified b/data/core.telegram.org/constructor/messages.recentStickersNotModified deleted file mode 100644 index 9b6c0caf08..0000000000 --- a/data/core.telegram.org/constructor/messages.recentStickersNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messages.recentStickersNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.recentStickersNotModified

- -

No new recent sticker was found

-

- -
-
messages.recentStickersNotModified#b17f890 = messages.RecentStickers;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

messages.RecentStickers

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.savedGifs b/data/core.telegram.org/constructor/messages.savedGifs deleted file mode 100644 index 355dc2ba0d..0000000000 --- a/data/core.telegram.org/constructor/messages.savedGifs +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.savedGifs - - - - - - - - - - - - - -
- -
-
-
- -

messages.savedGifs

- -

Saved gifs

-

- -
-
messages.savedGifs#84a02a0d hash:long gifs:Vector<Document> = messages.SavedGifs;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
gifsVector<Document>List of saved gifs
-

Type

-

messages.SavedGifs

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.savedGifsNotModified b/data/core.telegram.org/constructor/messages.savedGifsNotModified deleted file mode 100644 index 24e390a658..0000000000 --- a/data/core.telegram.org/constructor/messages.savedGifsNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messages.savedGifsNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.savedGifsNotModified

- -

No new saved gifs were found

-

- -
-
messages.savedGifsNotModified#e8025ca2 = messages.SavedGifs;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

messages.SavedGifs

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.searchCounter b/data/core.telegram.org/constructor/messages.searchCounter deleted file mode 100644 index 43cd3b55aa..0000000000 --- a/data/core.telegram.org/constructor/messages.searchCounter +++ /dev/null @@ -1,165 +0,0 @@ - - - - - messages.searchCounter - - - - - - - - - - - - - -
- -
-
-
- -

messages.searchCounter

- -

Indicates how many results would be found by a messages.search call with the same parameters

-

- -
-
messages.searchCounter#e844ebff flags:# inexact:flags.1?true filter:MessagesFilter count:int = messages.SearchCounter;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
inexactflags.1?trueIf set, the results may be inexact
filterMessagesFilterProvided message filter
countintNumber of results that were found server-side
-

Type

-

messages.SearchCounter

-

Related pages

-

messages.search

-

Gets back found messages

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.sentEncryptedMessage b/data/core.telegram.org/constructor/messages.sentEncryptedMessage deleted file mode 100644 index f88f8392e0..0000000000 --- a/data/core.telegram.org/constructor/messages.sentEncryptedMessage +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messages.sentEncryptedMessage - - - - - - - - - - - - - -
- -
-
-
- -

messages.sentEncryptedMessage

- -

Message without file attachemts sent to an encrypted file.

-

- -
-
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
dateintDate of sending
-

Type

-

messages.SentEncryptedMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.sentMessageLink b/data/core.telegram.org/constructor/messages.sentMessageLink deleted file mode 100644 index f56f6d1e61..0000000000 --- a/data/core.telegram.org/constructor/messages.sentMessageLink +++ /dev/null @@ -1,167 +0,0 @@ - - - - - messages.sentMessageLink - - - - - - - - - - - - - -
- -
-
-
- -

messages.sentMessageLink

- -

Info on successfully sent message and on changes links.

-

- -
-
Constructor schema is available as of layer 24. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idintMessage ID
dateintDate of sending
ptsintNew value of pts parameter of a current state
seqintNew value of seq parameter of a current state
linksVector<contacts.Link>List of changes links
-

Type

-

messages.SentMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.sponsoredMessages b/data/core.telegram.org/constructor/messages.sponsoredMessages deleted file mode 100644 index 16b95514f2..0000000000 --- a/data/core.telegram.org/constructor/messages.sponsoredMessages +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messages.sponsoredMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.sponsoredMessages

- -

A set of sponsored messages associated to a channel

-

- -
-
messages.sponsoredMessages#65a4c7d5 messages:Vector<SponsoredMessage> chats:Vector<Chat> users:Vector<User> = messages.SponsoredMessages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messagesVector<SponsoredMessage>Sponsored messages
chatsVector<Chat>Chats mentioned in the sponsored messages
usersVector<User>Users mentioned in the sponsored messages
-

Type

-

messages.SponsoredMessages

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.statedMessageLink b/data/core.telegram.org/constructor/messages.statedMessageLink deleted file mode 100644 index 562a59257c..0000000000 --- a/data/core.telegram.org/constructor/messages.statedMessageLink +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.statedMessageLink - - - - - - - - - - - - - -
- -
-
-
- -

messages.statedMessageLink

- -

Message with auxiliary data, state data and the list of changed links.

-

- -
-
Constructor schema is available as of layer 24. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageMessage
chatsVector<Chat>List of chats mentioned in message
usersVector<User>List of users mentioned in message and chats
linksVector<contacts.Link>List of changed links
ptsintNumber of events occurred in text box
seqintNumber of sent updates
-

Type

-

messages.StatedMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.statedMessagesLinks b/data/core.telegram.org/constructor/messages.statedMessagesLinks deleted file mode 100644 index 13eeddd424..0000000000 --- a/data/core.telegram.org/constructor/messages.statedMessagesLinks +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.statedMessagesLinks - - - - - - - - - - - - - -
- -
-
-
- -

messages.statedMessagesLinks

- -

Message with auxiliary data, state data and the list of changed links.

-

- -
-
Constructor schema is available as of layer 24. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messagesVector<Message>List of messages
chatsVector<Chat>List of cats mentioned in messages
usersVector<User>List of users mentioned in messages and cahts
linksVector<contacts.Link>List of changed links
ptsintNumber of event occurred in a text box
seqintNumber of sent updates
-

Type

-

messages.StatedMessages

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.stickerSet b/data/core.telegram.org/constructor/messages.stickerSet deleted file mode 100644 index 46e45cdbee..0000000000 --- a/data/core.telegram.org/constructor/messages.stickerSet +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messages.stickerSet - - - - - - - - - - - - - -
- -
-
-
- -

messages.stickerSet

- -

Stickerset and stickers inside it

-

- -
-
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
setStickerSetThe stickerset
packsVector<StickerPack>Emoji info for stickers
documentsVector<Document>Stickers in stickerset
-

Type

-

messages.StickerSet

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.stickerSetInstallResultArchive b/data/core.telegram.org/constructor/messages.stickerSetInstallResultArchive deleted file mode 100644 index 00859a4765..0000000000 --- a/data/core.telegram.org/constructor/messages.stickerSetInstallResultArchive +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messages.stickerSetInstallResultArchive - - - - - - - - - - - - - -
- -
-
-
- -

messages.stickerSetInstallResultArchive

- -

The stickerset was installed, but since there are too many stickersets some were archived

-

- -
-
messages.stickerSetInstallResultArchive#35e410a8 sets:Vector<StickerSetCovered> = messages.StickerSetInstallResult;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
setsVector<StickerSetCovered>Archived stickersets
-

Type

-

messages.StickerSetInstallResult

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.stickerSetInstallResultSuccess b/data/core.telegram.org/constructor/messages.stickerSetInstallResultSuccess deleted file mode 100644 index 3e5fb096b1..0000000000 --- a/data/core.telegram.org/constructor/messages.stickerSetInstallResultSuccess +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messages.stickerSetInstallResultSuccess - - - - - - - - - - - - - -
- -
-
-
- -

messages.stickerSetInstallResultSuccess

- -

The stickerset was installed successfully

-

- -
-
messages.stickerSetInstallResultSuccess#38641628 = messages.StickerSetInstallResult;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

messages.StickerSetInstallResult

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.stickers b/data/core.telegram.org/constructor/messages.stickers deleted file mode 100644 index 9eb9b02d0b..0000000000 --- a/data/core.telegram.org/constructor/messages.stickers +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.stickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.stickers

- -

Found stickers

-

- -
-
messages.stickers#30a6ec7e hash:long stickers:Vector<Document> = messages.Stickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
stickersVector<Document>Stickers
-

Type

-

messages.Stickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.stickersNotModified b/data/core.telegram.org/constructor/messages.stickersNotModified deleted file mode 100644 index dc640e7b7a..0000000000 --- a/data/core.telegram.org/constructor/messages.stickersNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messages.stickersNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.stickersNotModified

- -

No new stickers were found for the given query

-

- -
-
messages.stickersNotModified#f1749a22 = messages.Stickers;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

messages.Stickers

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/messages.votesList b/data/core.telegram.org/constructor/messages.votesList deleted file mode 100644 index 33c76927cc..0000000000 --- a/data/core.telegram.org/constructor/messages.votesList +++ /dev/null @@ -1,170 +0,0 @@ - - - - - messages.votesList - - - - - - - - - - - - - -
- -
-
-
- -

messages.votesList

- -

How users voted in a poll

-

- -
-
messages.votesList#823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
countintTotal number of votes for all options (or only for the chosen option, if provided to messages.getPollVotes)
votesVector<MessageUserVote>Vote info for each user
usersVector<User>Info about users that voted in the poll
next_offsetflags.0?stringOffset to use with the next messages.getPollVotes request, empty string if no more results are available.
-

Type

-

messages.VotesList

-

Related pages

-

messages.getPollVotes

-

Get poll results for non-anonymous polls

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/nearestDc.html b/data/core.telegram.org/constructor/nearestDc.html deleted file mode 100644 index c1dd455bc7..0000000000 --- a/data/core.telegram.org/constructor/nearestDc.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - nearestDc - - - - - - - - - - - - - -
- -
-
-
- -

nearestDc

- -

Nearest data centre, according to geo-ip.

-

- -
-
nearestDc#8e1a1775 country:string this_dc:int nearest_dc:int = NearestDc;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countrystringCountry code determined by geo-ip
this_dcintNumber of current data centre
nearest_dcintNumber of nearest data centre
-

Type

-

NearestDc

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/notifyBroadcasts.html b/data/core.telegram.org/constructor/notifyBroadcasts.html deleted file mode 100644 index a2e26db1d9..0000000000 --- a/data/core.telegram.org/constructor/notifyBroadcasts.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - notifyBroadcasts - - - - - - - - - - - - - -
- -
-
-
- -

notifyBroadcasts

- -

Channel notification settings

-

- -
-
notifyBroadcasts#d612e8ef = NotifyPeer;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

NotifyPeer

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/notifyChats.html b/data/core.telegram.org/constructor/notifyChats.html deleted file mode 100644 index c2edc13500..0000000000 --- a/data/core.telegram.org/constructor/notifyChats.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - notifyChats - - - - - - - - - - - - - -
- -
-
-
- -

notifyChats

- -

Notifications generated by all groups.

-

- -
-
notifyChats#c007cec3 = NotifyPeer;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

NotifyPeer

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/notifyUsers.html b/data/core.telegram.org/constructor/notifyUsers.html deleted file mode 100644 index a72465c25a..0000000000 --- a/data/core.telegram.org/constructor/notifyUsers.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - notifyUsers - - - - - - - - - - - - - -
- -
-
-
- -

notifyUsers

- -

Notifications generated by all users.

-

- -
-
notifyUsers#b4c83b4c = NotifyPeer;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

NotifyPeer

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/null.html b/data/core.telegram.org/constructor/null.html deleted file mode 100644 index 3c3bb87d9d..0000000000 --- a/data/core.telegram.org/constructor/null.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - null - - - - - - - - - - - - - -
- -
-
-
- -

null

- -

Corresponds to an arbitrary empty object.

-

- -
-
null#56730bcc = Null;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Null

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/page.html b/data/core.telegram.org/constructor/page.html deleted file mode 100644 index 619d560c57..0000000000 --- a/data/core.telegram.org/constructor/page.html +++ /dev/null @@ -1,190 +0,0 @@ - - - - - page - - - - - - - - - - - - - -
- -
-
-
- -

page

- -

Instant view page

-

- -
-
page#98657f0d flags:# part:flags.0?true rtl:flags.1?true v2:flags.2?true url:string blocks:Vector<PageBlock> photos:Vector<Photo> documents:Vector<Document> views:flags.3?int = Page;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
partflags.0?trueIndicates that not full page preview is available to the client and it will need to fetch full Instant View from the server using messages.getWebPagePreview.
rtlflags.1?trueWhether the page contains RTL text
v2flags.2?trueWhether this is an IV v2 page
urlstringOriginal page HTTP URL
blocksVector<PageBlock>Page elements (like with HTML elements, only as TL constructors)
photosVector<Photo>Photos in page
documentsVector<Document>Media in page
viewsflags.3?intViewcount
-

Type

-

Page

-

Related pages

-

messages.getWebPagePreview

-

Get preview of webpage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockAnchor.html b/data/core.telegram.org/constructor/pageBlockAnchor.html deleted file mode 100644 index c48e66b036..0000000000 --- a/data/core.telegram.org/constructor/pageBlockAnchor.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockAnchor - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockAnchor

- -

Link to section within the page itself (like <a href="#target">anchor</a>)

-

- -
-
pageBlockAnchor#ce0d37b0 name:string = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
namestringName of target section
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockAudio.html b/data/core.telegram.org/constructor/pageBlockAudio.html deleted file mode 100644 index e3698915a7..0000000000 --- a/data/core.telegram.org/constructor/pageBlockAudio.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - pageBlockAudio - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockAudio

- -

Audio

-

- -
-
pageBlockAudio#804361ea audio_id:long caption:PageCaption = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
audio_idlongAudio ID (to be fetched from the container page constructor
captionPageCaptionAudio caption
-

Type

-

PageBlock

-

Related pages

-

page

-

Instant view page

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockAuthorDate.html b/data/core.telegram.org/constructor/pageBlockAuthorDate.html deleted file mode 100644 index 0f24d2fbda..0000000000 --- a/data/core.telegram.org/constructor/pageBlockAuthorDate.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageBlockAuthorDate - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockAuthorDate

- -

Author and date of creation of article

-

- -
-
pageBlockAuthorDate#baafe5e0 author:RichText published_date:int = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
authorRichTextAuthor name
published_dateintDate of pubblication
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockBlockquote.html b/data/core.telegram.org/constructor/pageBlockBlockquote.html deleted file mode 100644 index 1d207c8fce..0000000000 --- a/data/core.telegram.org/constructor/pageBlockBlockquote.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageBlockBlockquote - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockBlockquote

- -

Quote (equivalent to the HTML <blockquote>)

-

- -
-
pageBlockBlockquote#263d7c26 text:RichText caption:RichText = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextQuote contents
captionRichTextCaption
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockChannel.html b/data/core.telegram.org/constructor/pageBlockChannel.html deleted file mode 100644 index e8690b2830..0000000000 --- a/data/core.telegram.org/constructor/pageBlockChannel.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockChannel - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockChannel

- -

Reference to a telegram channel

-

- -
-
pageBlockChannel#ef1751b5 channel:Chat = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
channelChatThe channel/supergroup/chat
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockCollage.html b/data/core.telegram.org/constructor/pageBlockCollage.html deleted file mode 100644 index f6a8fd5db7..0000000000 --- a/data/core.telegram.org/constructor/pageBlockCollage.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageBlockCollage - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockCollage

- -

Collage of media

-

- -
-
pageBlockCollage#65a0fa4d items:Vector<PageBlock> caption:PageCaption = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
itemsVector<PageBlock>Media elements
captionPageCaptionCaption
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockCover.html b/data/core.telegram.org/constructor/pageBlockCover.html deleted file mode 100644 index 714bf0551b..0000000000 --- a/data/core.telegram.org/constructor/pageBlockCover.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockCover - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockCover

- -

A page cover

-

- -
-
pageBlockCover#39f23300 cover:PageBlock = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
coverPageBlockCover
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockDetails.html b/data/core.telegram.org/constructor/pageBlockDetails.html deleted file mode 100644 index e9e599be5a..0000000000 --- a/data/core.telegram.org/constructor/pageBlockDetails.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - pageBlockDetails - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockDetails

- -

A collapsible details block

-

- -
-
pageBlockDetails#76768bed flags:# open:flags.0?true blocks:Vector<PageBlock> title:RichText = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
openflags.0?trueWhether the block is open by default
blocksVector<PageBlock>Block contents
titleRichTextAlways visible heading for the block
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockDivider.html b/data/core.telegram.org/constructor/pageBlockDivider.html deleted file mode 100644 index c760735f55..0000000000 --- a/data/core.telegram.org/constructor/pageBlockDivider.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - pageBlockDivider - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockDivider

- -

An empty block separating a page

-

- -
-
pageBlockDivider#db20b188 = PageBlock;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockEmbed.html b/data/core.telegram.org/constructor/pageBlockEmbed.html deleted file mode 100644 index 2cb9358f7c..0000000000 --- a/data/core.telegram.org/constructor/pageBlockEmbed.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - pageBlockEmbed - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockEmbed

- -

An embedded webpage

-

- -
-
pageBlockEmbed#a8718dc5 flags:# full_width:flags.0?true allow_scrolling:flags.3?true url:flags.1?string html:flags.2?string poster_photo_id:flags.4?long w:flags.5?int h:flags.5?int caption:PageCaption = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
full_widthflags.0?trueWhether the block should be full width
allow_scrollingflags.3?trueWhether scrolling should be allowed
urlflags.1?stringWeb page URL, if available
htmlflags.2?stringHTML-markup of the embedded page
poster_photo_idflags.4?longPoster photo, if available
wflags.5?intBlock width, if known
hflags.5?intBlock height, if known
captionPageCaptionCaption
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockEmbedPost.html b/data/core.telegram.org/constructor/pageBlockEmbedPost.html deleted file mode 100644 index 41dfac8c00..0000000000 --- a/data/core.telegram.org/constructor/pageBlockEmbedPost.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - pageBlockEmbedPost - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockEmbedPost

- -

An embedded post

-

- -
-
pageBlockEmbedPost#f259a80b url:string webpage_id:long author_photo_id:long author:string date:int blocks:Vector<PageBlock> caption:PageCaption = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringWeb page URL
webpage_idlongID of generated webpage preview
author_photo_idlongID of the author's photo
authorstringAuthor name
dateintCreation date
blocksVector<PageBlock>Post contents
captionPageCaptionCaption
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockFooter.html b/data/core.telegram.org/constructor/pageBlockFooter.html deleted file mode 100644 index b168e0bb1f..0000000000 --- a/data/core.telegram.org/constructor/pageBlockFooter.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockFooter - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockFooter

- -

Page footer

-

- -
-
pageBlockFooter#48870999 text:RichText = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextContents
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockHeader.html b/data/core.telegram.org/constructor/pageBlockHeader.html deleted file mode 100644 index a16dac3083..0000000000 --- a/data/core.telegram.org/constructor/pageBlockHeader.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockHeader - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockHeader

- -

Page header

-

- -
-
pageBlockHeader#bfd064ec text:RichText = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextContents
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockKicker.html b/data/core.telegram.org/constructor/pageBlockKicker.html deleted file mode 100644 index 4414562bac..0000000000 --- a/data/core.telegram.org/constructor/pageBlockKicker.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockKicker - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockKicker

- -

Kicker

-

- -
-
pageBlockKicker#1e148390 text:RichText = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextContents
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockList.html b/data/core.telegram.org/constructor/pageBlockList.html deleted file mode 100644 index 925921bc8c..0000000000 --- a/data/core.telegram.org/constructor/pageBlockList.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockList - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockList

- -

Unordered list of IV blocks

-

- -
-
pageBlockList#e4e88011 items:Vector<PageListItem> = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
itemsVector<PageListItem>List of blocks in an IV page
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockMap.html b/data/core.telegram.org/constructor/pageBlockMap.html deleted file mode 100644 index e2af18353b..0000000000 --- a/data/core.telegram.org/constructor/pageBlockMap.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - pageBlockMap - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockMap

- -

A map

-

- -
-
pageBlockMap#a44f3ef6 geo:GeoPoint zoom:int w:int h:int caption:PageCaption = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
geoGeoPointLocation of the map center
zoomintMap zoom level; 13-20
wintMap width in pixels before applying scale; 16-102
hintMap height in pixels before applying scale; 16-1024
captionPageCaptionCaption
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockOrderedList.html b/data/core.telegram.org/constructor/pageBlockOrderedList.html deleted file mode 100644 index 5528e7602a..0000000000 --- a/data/core.telegram.org/constructor/pageBlockOrderedList.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockOrderedList - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockOrderedList

- -

Ordered list of IV blocks

-

- -
-
pageBlockOrderedList#9a8ae1e1 items:Vector<PageListOrderedItem> = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
itemsVector<PageListOrderedItem>List items
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockParagraph.html b/data/core.telegram.org/constructor/pageBlockParagraph.html deleted file mode 100644 index f971022717..0000000000 --- a/data/core.telegram.org/constructor/pageBlockParagraph.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockParagraph - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockParagraph

- -

A paragraph

-

- -
-
pageBlockParagraph#467a0766 text:RichText = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockPhoto.html b/data/core.telegram.org/constructor/pageBlockPhoto.html deleted file mode 100644 index f8ed8806e0..0000000000 --- a/data/core.telegram.org/constructor/pageBlockPhoto.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - pageBlockPhoto - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockPhoto

- -

A photo

-

- -
-
pageBlockPhoto#1759c560 flags:# photo_id:long caption:PageCaption url:flags.0?string webpage_id:flags.0?long = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
photo_idlongPhoto ID
captionPageCaptionCaption
urlflags.0?stringHTTP URL of page the photo leads to when clicked
webpage_idflags.0?longID of preview of the page the photo leads to when clicked
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockPreformatted.html b/data/core.telegram.org/constructor/pageBlockPreformatted.html deleted file mode 100644 index 6efc006058..0000000000 --- a/data/core.telegram.org/constructor/pageBlockPreformatted.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageBlockPreformatted - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockPreformatted

- -

Preformatted (<pre> text)

-

- -
-
pageBlockPreformatted#c070d93e text:RichText language:string = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
languagestringProgramming language of preformatted text
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockPullquote.html b/data/core.telegram.org/constructor/pageBlockPullquote.html deleted file mode 100644 index ff8b351133..0000000000 --- a/data/core.telegram.org/constructor/pageBlockPullquote.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageBlockPullquote - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockPullquote

- -

Pullquote

-

- -
-
pageBlockPullquote#4f4456d3 text:RichText caption:RichText = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
captionRichTextCaption
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockRelatedArticles.html b/data/core.telegram.org/constructor/pageBlockRelatedArticles.html deleted file mode 100644 index 64f79422f3..0000000000 --- a/data/core.telegram.org/constructor/pageBlockRelatedArticles.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageBlockRelatedArticles - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockRelatedArticles

- -

Related articles

-

- -
-
pageBlockRelatedArticles#16115a96 title:RichText articles:Vector<PageRelatedArticle> = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
titleRichTextTitle
articlesVector<PageRelatedArticle>Related articles
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockSlideshow.html b/data/core.telegram.org/constructor/pageBlockSlideshow.html deleted file mode 100644 index dbf984b58b..0000000000 --- a/data/core.telegram.org/constructor/pageBlockSlideshow.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageBlockSlideshow - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockSlideshow

- -

Slideshow

-

- -
-
pageBlockSlideshow#31f9590 items:Vector<PageBlock> caption:PageCaption = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
itemsVector<PageBlock>Slideshow items
captionPageCaptionCaption
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockSubheader.html b/data/core.telegram.org/constructor/pageBlockSubheader.html deleted file mode 100644 index 67ffc78d55..0000000000 --- a/data/core.telegram.org/constructor/pageBlockSubheader.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockSubheader - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockSubheader

- -

Subheader

-

- -
-
pageBlockSubheader#f12bb6e1 text:RichText = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextSubheader
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockSubtitle.html b/data/core.telegram.org/constructor/pageBlockSubtitle.html deleted file mode 100644 index 56ecef710c..0000000000 --- a/data/core.telegram.org/constructor/pageBlockSubtitle.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockSubtitle - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockSubtitle

- -

Subtitle

-

- -
-
pageBlockSubtitle#8ffa9a1f text:RichText = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockTitle.html b/data/core.telegram.org/constructor/pageBlockTitle.html deleted file mode 100644 index bf3d2ff4ef..0000000000 --- a/data/core.telegram.org/constructor/pageBlockTitle.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockTitle - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockTitle

- -

Title

-

- -
-
pageBlockTitle#70abc3fd text:RichText = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextTitle
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockUnsupported.html b/data/core.telegram.org/constructor/pageBlockUnsupported.html deleted file mode 100644 index a2fc55c003..0000000000 --- a/data/core.telegram.org/constructor/pageBlockUnsupported.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - pageBlockUnsupported - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockUnsupported

- -

Unsupported IV element

-

- -
-
pageBlockUnsupported#13567e8a = PageBlock;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageBlockVideo.html b/data/core.telegram.org/constructor/pageBlockVideo.html deleted file mode 100644 index 662ddf3ab6..0000000000 --- a/data/core.telegram.org/constructor/pageBlockVideo.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - pageBlockVideo - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockVideo

- -

Video

-

- -
-
pageBlockVideo#7c8fe7b6 flags:# autoplay:flags.0?true loop:flags.1?true video_id:long caption:PageCaption = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
autoplayflags.0?trueWhether the video is set to autoplay
loopflags.1?trueWhether the video is set to loop
video_idlongVideo ID
captionPageCaptionCaption
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageCaption.html b/data/core.telegram.org/constructor/pageCaption.html deleted file mode 100644 index 9604f73951..0000000000 --- a/data/core.telegram.org/constructor/pageCaption.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageCaption - - - - - - - - - - - - - -
- -
-
-
- -

pageCaption

- -

Page caption

-

- -
-
pageCaption#6f747657 text:RichText credit:RichText = PageCaption;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextCaption
creditRichTextCredits
-

Type

-

PageCaption

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageListItemBlocks.html b/data/core.telegram.org/constructor/pageListItemBlocks.html deleted file mode 100644 index 93be908282..0000000000 --- a/data/core.telegram.org/constructor/pageListItemBlocks.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageListItemBlocks - - - - - - - - - - - - - -
- -
-
-
- -

pageListItemBlocks

- -

List item

-

- -
-
pageListItemBlocks#25e073fc blocks:Vector<PageBlock> = PageListItem;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
blocksVector<PageBlock>Blocks
-

Type

-

PageListItem

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageListItemText.html b/data/core.telegram.org/constructor/pageListItemText.html deleted file mode 100644 index b04f4f3b02..0000000000 --- a/data/core.telegram.org/constructor/pageListItemText.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageListItemText - - - - - - - - - - - - - -
- -
-
-
- -

pageListItemText

- -

List item

-

- -
-
pageListItemText#b92fb6cd text:RichText = PageListItem;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
-

Type

-

PageListItem

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageListOrderedItemText.html b/data/core.telegram.org/constructor/pageListOrderedItemText.html deleted file mode 100644 index 12982f75d7..0000000000 --- a/data/core.telegram.org/constructor/pageListOrderedItemText.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageListOrderedItemText - - - - - - - - - - - - - -
- -
-
-
- -

pageListOrderedItemText

- -

Ordered list of text items

-

- -
-
pageListOrderedItemText#5e068047 num:string text:RichText = PageListOrderedItem;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
numstringNumber of element within ordered list
textRichTextText
-

Type

-

PageListOrderedItem

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageRelatedArticle.html b/data/core.telegram.org/constructor/pageRelatedArticle.html deleted file mode 100644 index 2a0691b04c..0000000000 --- a/data/core.telegram.org/constructor/pageRelatedArticle.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - pageRelatedArticle - - - - - - - - - - - - - -
- -
-
-
- -

pageRelatedArticle

- -

Related article

-

- -
-
pageRelatedArticle#b390dc08 flags:# url:string webpage_id:long title:flags.0?string description:flags.1?string photo_id:flags.2?long author:flags.3?string published_date:flags.4?int = PageRelatedArticle;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
urlstringURL of article
webpage_idlongWebpage ID of generated IV preview
titleflags.0?stringTitle
descriptionflags.1?stringDescription
photo_idflags.2?longID of preview photo
authorflags.3?stringAuthor name
published_dateflags.4?intDate of pubblication
-

Type

-

PageRelatedArticle

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageTableCell.html b/data/core.telegram.org/constructor/pageTableCell.html deleted file mode 100644 index dd1952dc1e..0000000000 --- a/data/core.telegram.org/constructor/pageTableCell.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - pageTableCell - - - - - - - - - - - - - -
- -
-
-
- -

pageTableCell

- -

Table cell

-

- -
-
pageTableCell#34566b6a flags:# header:flags.0?true align_center:flags.3?true align_right:flags.4?true valign_middle:flags.5?true valign_bottom:flags.6?true text:flags.7?RichText colspan:flags.1?int rowspan:flags.2?int = PageTableCell;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
headerflags.0?trueIs this element part of the column header
align_centerflags.3?trueHorizontally centered block
align_rightflags.4?trueRight-aligned block
valign_middleflags.5?trueVertically centered block
valign_bottomflags.6?trueBlock vertically-alligned to the bottom
textflags.7?RichTextContent
colspanflags.1?intFor how many columns should this cell extend
rowspanflags.2?intFor how many rows should this cell extend
-

Type

-

PageTableCell

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pageTableRow.html b/data/core.telegram.org/constructor/pageTableRow.html deleted file mode 100644 index 41fe78d3f3..0000000000 --- a/data/core.telegram.org/constructor/pageTableRow.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageTableRow - - - - - - - - - - - - - -
- -
-
-
- -

pageTableRow

- -

Table row

-

- -
-
pageTableRow#e0c0c5e5 cells:Vector<PageTableCell> = PageTableRow;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
cellsVector<PageTableCell>Table cells
-

Type

-

PageTableRow

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow.html b/data/core.telegram.org/constructor/passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow.html deleted file mode 100644 index c0c099b198..0000000000 --- a/data/core.telegram.org/constructor/passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow - - - - - - - - - - - - - -
- -
-
-
- -

passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow

- -

This key derivation algorithm defines that SRP 2FA login must be used

-

- -
-
passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow#3a912d4a salt1:bytes salt2:bytes g:int p:bytes = PasswordKdfAlgo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
salt1bytesOne of two salts used by the derivation function (see SRP 2FA login)
salt2bytesOne of two salts used by the derivation function (see SRP 2FA login)
gintBase (see SRP 2FA login)
pbytes2048-bit modulus (see SRP 2FA login)
-

Type

-

PasswordKdfAlgo

-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/passwordKdfAlgoUnknown.html b/data/core.telegram.org/constructor/passwordKdfAlgoUnknown.html deleted file mode 100644 index 13e8c3ab09..0000000000 --- a/data/core.telegram.org/constructor/passwordKdfAlgoUnknown.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - passwordKdfAlgoUnknown - - - - - - - - - - - - - -
- -
-
-
- -

passwordKdfAlgoUnknown

- -

Unknown KDF (most likely, the client is outdated and does not support the specified KDF algorithm)

-

- -
-
passwordKdfAlgoUnknown#d45ab096 = PasswordKdfAlgo;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PasswordKdfAlgo

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/paymentCharge.html b/data/core.telegram.org/constructor/paymentCharge.html deleted file mode 100644 index 2479c9f5c4..0000000000 --- a/data/core.telegram.org/constructor/paymentCharge.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - paymentCharge - - - - - - - - - - - - - -
- -
-
-
- -

paymentCharge

- -

Payment identifier

-

- -
-
paymentCharge#ea02c27e id:string provider_charge_id:string = PaymentCharge;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idstringTelegram payment identifier
provider_charge_idstringProvider payment identifier
-

Type

-

PaymentCharge

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/paymentRequestedInfo.html b/data/core.telegram.org/constructor/paymentRequestedInfo.html deleted file mode 100644 index 2e8b57c64b..0000000000 --- a/data/core.telegram.org/constructor/paymentRequestedInfo.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - paymentRequestedInfo - - - - - - - - - - - - - -
- -
-
-
- -

paymentRequestedInfo

- -

Order info provided by the user

-

- -
-
paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
nameflags.0?stringUser's full name
phoneflags.1?stringUser's phone number
emailflags.2?stringUser's email address
shipping_addressflags.3?PostAddressUser's shipping address
-

Type

-

PaymentRequestedInfo

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/paymentSavedCredentialsCard.html b/data/core.telegram.org/constructor/paymentSavedCredentialsCard.html deleted file mode 100644 index 2ed138c16c..0000000000 --- a/data/core.telegram.org/constructor/paymentSavedCredentialsCard.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - paymentSavedCredentialsCard - - - - - - - - - - - - - -
- -
-
-
- -

paymentSavedCredentialsCard

- -

Saved credit card

-

- -
-
paymentSavedCredentialsCard#cdc27a1f id:string title:string = PaymentSavedCredentials;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idstringCard ID
titlestringTitle
-

Type

-

PaymentSavedCredentials

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/payments.ValidatedRequestedInfo b/data/core.telegram.org/constructor/payments.ValidatedRequestedInfo deleted file mode 100644 index 4a81460ed0..0000000000 --- a/data/core.telegram.org/constructor/payments.ValidatedRequestedInfo +++ /dev/null @@ -1,145 +0,0 @@ - - - - - payments.ValidatedRequestedInfo - - - - - - - - - - - - - -
- -
-
-
- -

payments.ValidatedRequestedInfo

- -

Validated user-provided info

-

{schema}

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idflags.0?stringID
shipping_optionsflags.1?Vector<ShippingOption>Shipping options
-

Type

-

payments.ValidatedRequestedInfo

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/payments.bankCardData b/data/core.telegram.org/constructor/payments.bankCardData deleted file mode 100644 index eb3fe8753d..0000000000 --- a/data/core.telegram.org/constructor/payments.bankCardData +++ /dev/null @@ -1,152 +0,0 @@ - - - - - payments.bankCardData - - - - - - - - - - - - - -
- -
-
-
- -

payments.bankCardData

- -

Credit card info, provided by the card's bank(s)

-

- -
-
payments.bankCardData#3e24e573 title:string open_urls:Vector<BankCardOpenUrl> = payments.BankCardData;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
titlestringCredit card title
open_urlsVector<BankCardOpenUrl>Info URL(s) provided by the card's bank(s)
-

Type

-

payments.BankCardData

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/payments.paymentForm b/data/core.telegram.org/constructor/payments.paymentForm deleted file mode 100644 index 920813f6f6..0000000000 --- a/data/core.telegram.org/constructor/payments.paymentForm +++ /dev/null @@ -1,210 +0,0 @@ - - - - - payments.paymentForm - - - - - - - - - - - - - -
- -
-
-
- -

payments.paymentForm

- -

Payment form

-

- -
-
payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
can_save_credentialsflags.2?trueWhether the user can choose to save credentials.
password_missingflags.3?trueIndicates that the user can save payment credentials, but only after setting up a 2FA password (currently the account doesn't have a 2FA password)
form_idlongForm ID
bot_idlongBot ID
invoiceInvoiceInvoice
provider_idlongPayment provider ID.
urlstringPayment form URL
native_providerflags.4?stringPayment provider name.
One of the following:
- stripe
native_paramsflags.4?DataJSONContains information about the payment provider, if available, to support it natively without the need for opening the URL.
A JSON object that can contain the following fields:

- apple_pay_merchant_id: Apple Pay merchant ID
- google_pay_public_key: Google Pay public key
- need_country: True, if the user country must be provided,
- need_zip: True, if the user ZIP/postal code must be provided,
- need_cardholder_name: True, if the cardholder name must be provided
saved_infoflags.0?PaymentRequestedInfoSaved server-side order information
saved_credentialsflags.1?PaymentSavedCredentialsContains information about saved card credentials
usersVector<User>Users
-

Type

-

payments.PaymentForm

-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/payments.paymentReceipt b/data/core.telegram.org/constructor/payments.paymentReceipt deleted file mode 100644 index a8a7696e9b..0000000000 --- a/data/core.telegram.org/constructor/payments.paymentReceipt +++ /dev/null @@ -1,219 +0,0 @@ - - - - - payments.paymentReceipt - - - - - - - - - - - - - -
- -
-
-
- -

payments.paymentReceipt

- -

Receipt

-

- -
-
payments.paymentReceipt#70c4fe03 flags:# date:int bot_id:long provider_id:long title:string description:string photo:flags.2?WebDocument invoice:Invoice info:flags.0?PaymentRequestedInfo shipping:flags.1?ShippingOption tip_amount:flags.3?long currency:string total_amount:long credentials_title:string users:Vector<User> = payments.PaymentReceipt;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
dateintDate of generation
bot_idlongBot ID
provider_idlongProvider ID
titlestringTitle
descriptionstringDescription
photoflags.2?WebDocumentPhoto
invoiceInvoiceInvoice
infoflags.0?PaymentRequestedInfoInfo
shippingflags.1?ShippingOptionSelected shipping option
tip_amountflags.3?longTipped amount
currencystringThree-letter ISO 4217 currency code
total_amountlongTotal amount in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
credentials_titlestringPayment credential name
usersVector<User>Users
-

Type

-

payments.PaymentReceipt

-

Related pages

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/payments.paymentResult b/data/core.telegram.org/constructor/payments.paymentResult deleted file mode 100644 index 5306a7d5c5..0000000000 --- a/data/core.telegram.org/constructor/payments.paymentResult +++ /dev/null @@ -1,147 +0,0 @@ - - - - - payments.paymentResult - - - - - - - - - - - - - -
- -
-
-
- -

payments.paymentResult

- -

Payment result

-

- -
-
payments.paymentResult#4e5f810d updates:Updates = payments.PaymentResult;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
updatesUpdatesInfo about the payment
-

Type

-

payments.PaymentResult

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/payments.paymentVerificationNeeded b/data/core.telegram.org/constructor/payments.paymentVerificationNeeded deleted file mode 100644 index 836c7e1c85..0000000000 --- a/data/core.telegram.org/constructor/payments.paymentVerificationNeeded +++ /dev/null @@ -1,147 +0,0 @@ - - - - - payments.paymentVerificationNeeded - - - - - - - - - - - - - -
- -
-
-
- -

payments.paymentVerificationNeeded

- -

Payment was not successful, additional verification is needed

-

- -
-
payments.paymentVerificationNeeded#d8411139 url:string = payments.PaymentResult;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
urlstringURL for additional payment credentials verification
-

Type

-

payments.PaymentResult

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/payments.savedInfo b/data/core.telegram.org/constructor/payments.savedInfo deleted file mode 100644 index 2cedcbe780..0000000000 --- a/data/core.telegram.org/constructor/payments.savedInfo +++ /dev/null @@ -1,157 +0,0 @@ - - - - - payments.savedInfo - - - - - - - - - - - - - -
- -
-
-
- -

payments.savedInfo

- -

Saved server-side order information

-

- -
-
payments.savedInfo#fb8fe43c flags:# has_saved_credentials:flags.1?true saved_info:flags.0?PaymentRequestedInfo = payments.SavedInfo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
has_saved_credentialsflags.1?trueWhether the user has some saved payment credentials
saved_infoflags.0?PaymentRequestedInfoSaved server-side order information
-

Type

-

payments.SavedInfo

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/peerBlocked.html b/data/core.telegram.org/constructor/peerBlocked.html deleted file mode 100644 index 1b3bf106a5..0000000000 --- a/data/core.telegram.org/constructor/peerBlocked.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - peerBlocked - - - - - - - - - - - - - -
- -
-
-
- -

peerBlocked

- -

Information about a blocked peer

-

- -
-
peerBlocked#e8fd8014 peer_id:Peer date:int = PeerBlocked;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peer_idPeerPeer ID
dateintWhen was the peer blocked
-

Type

-

PeerBlocked

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/peerChat.html b/data/core.telegram.org/constructor/peerChat.html deleted file mode 100644 index 2abfcb727a..0000000000 --- a/data/core.telegram.org/constructor/peerChat.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - peerChat - - - - - - - - - - - - - -
- -
-
-
- -

peerChat

- -

Group.

-

- -
-
peerChat#36c6019a chat_id:long = Peer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongGroup identifier
-

Type

-

Peer

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/peerLocated.html b/data/core.telegram.org/constructor/peerLocated.html deleted file mode 100644 index ead8d9e2e3..0000000000 --- a/data/core.telegram.org/constructor/peerLocated.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - peerLocated - - - - - - - - - - - - - -
- -
-
-
- -

peerLocated

- -

Peer geolocated nearby

-

- -
-
peerLocated#ca461b5d peer:Peer expires:int distance:int = PeerLocated;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerPeer
expiresintValidity period of current data
distanceintDistance from the peer in meters
-

Type

-

PeerLocated

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/peerNotifySettings.html b/data/core.telegram.org/constructor/peerNotifySettings.html deleted file mode 100644 index 1a8febde59..0000000000 --- a/data/core.telegram.org/constructor/peerNotifySettings.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - peerNotifySettings - - - - - - - - - - - - - -
- -
-
-
- -

peerNotifySettings

- -

Notification settings.

-

- -
-
peerNotifySettings#af509d20 flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = PeerNotifySettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
show_previewsflags.0?BoolDisplay text in notifications
silentflags.1?BoolMute peer?
mute_untilflags.2?intMute all notifications until this date
soundflags.3?stringAudio file name for notifications
-

Type

-

PeerNotifySettings

-

Event flags (events_mask)

- - - - - - - - - - - - - -
0x00000001Profile photo update notification
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/peerSelfLocated.html b/data/core.telegram.org/constructor/peerSelfLocated.html deleted file mode 100644 index c67b1f8860..0000000000 --- a/data/core.telegram.org/constructor/peerSelfLocated.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - peerSelfLocated - - - - - - - - - - - - - -
- -
-
-
- -

peerSelfLocated

- -

Current peer

-

- -
-
peerSelfLocated#f8ec284b expires:int = PeerLocated;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
expiresintExpiry of geolocation info for current peer
-

Type

-

PeerLocated

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/peerSettings.html b/data/core.telegram.org/constructor/peerSettings.html deleted file mode 100644 index adbec89557..0000000000 --- a/data/core.telegram.org/constructor/peerSettings.html +++ /dev/null @@ -1,197 +0,0 @@ - - - - - peerSettings - - - - - - - - - - - - - -
- -
-
-
- -

peerSettings

- -

Peer settings

-

- -
-
peerSettings#733f2961 flags:# report_spam:flags.0?true add_contact:flags.1?true block_contact:flags.2?true share_contact:flags.3?true need_contacts_exception:flags.4?true report_geo:flags.5?true autoarchived:flags.7?true invite_members:flags.8?true geo_distance:flags.6?int = PeerSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
report_spamflags.0?trueWhether we can still report the user for spam
add_contactflags.1?trueWhether we can add the user as contact
block_contactflags.2?trueWhether we can block the user
share_contactflags.3?trueWhether we can share the user's contact
need_contacts_exceptionflags.4?trueWhether a special exception for contacts is needed
report_geoflags.5?trueWhether we can report a geogroup is irrelevant for this location
autoarchivedflags.7?trueWhether this peer was automatically archived according to privacy settings
invite_membersflags.8?trueWhether we can invite members to a group or channel
geo_distanceflags.6?intDistance in meters between us and this peer
-

Type

-

PeerSettings

-

Related pages

-

globalPrivacySettings

-

Global privacy settings

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/peerUser.html b/data/core.telegram.org/constructor/peerUser.html deleted file mode 100644 index dd682b961d..0000000000 --- a/data/core.telegram.org/constructor/peerUser.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - peerUser - - - - - - - - - - - - - -
- -
-
-
- -

peerUser

- -

Chat partner

-

- -
-
peerUser#59511722 user_id:long = Peer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser identifier
-

Type

-

Peer

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phone.exportedGroupCallInvite b/data/core.telegram.org/constructor/phone.exportedGroupCallInvite deleted file mode 100644 index 34667582aa..0000000000 --- a/data/core.telegram.org/constructor/phone.exportedGroupCallInvite +++ /dev/null @@ -1,147 +0,0 @@ - - - - - phone.exportedGroupCallInvite - - - - - - - - - - - - - -
- -
-
-
- -

phone.exportedGroupCallInvite

- -

An invite to a group call or livestream

-

- -
-
phone.exportedGroupCallInvite#204bd158 link:string = phone.ExportedGroupCallInvite;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
linkstringInvite link
-

Type

-

phone.ExportedGroupCallInvite

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phone.groupCall b/data/core.telegram.org/constructor/phone.groupCall deleted file mode 100644 index 4cfc527411..0000000000 --- a/data/core.telegram.org/constructor/phone.groupCall +++ /dev/null @@ -1,170 +0,0 @@ - - - - - phone.groupCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.groupCall

- -

Contains info about a group call, and partial info about its participants.

-

- -
-
phone.groupCall#9e727aad call:GroupCall participants:Vector<GroupCallParticipant> participants_next_offset:string chats:Vector<Chat> users:Vector<User> = phone.GroupCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
callGroupCallInfo about the group call
participantsVector<GroupCallParticipant>A partial list of participants.
participants_next_offsetstringNext offset to use when fetching the remaining participants using phone.getGroupParticipants
chatsVector<Chat>Chats mentioned in the participants vector
usersVector<User>Users mentioned in the participants vector
-

Type

-

phone.GroupCall

-

Related pages

-

phone.getGroupParticipants

-

Get group call participants

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phone.groupParticipants b/data/core.telegram.org/constructor/phone.groupParticipants deleted file mode 100644 index 639e22c978..0000000000 --- a/data/core.telegram.org/constructor/phone.groupParticipants +++ /dev/null @@ -1,175 +0,0 @@ - - - - - phone.groupParticipants - - - - - - - - - - - - - -
- -
-
-
- -

phone.groupParticipants

- -

Info about the participants of a group call or livestream

-

- -
-
phone.groupParticipants#f47751b6 count:int participants:Vector<GroupCallParticipant> next_offset:string chats:Vector<Chat> users:Vector<User> version:int = phone.GroupParticipants;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countintNumber of participants
participantsVector<GroupCallParticipant>List of participants
next_offsetstringIf not empty, the specified list of participants is partial, and more participants can be fetched specifying this parameter as offset in phone.getGroupParticipants.
chatsVector<Chat>Mentioned chats
usersVector<User>Mentioned users
versionintVersion info
-

Type

-

phone.GroupParticipants

-

Related pages

-

phone.getGroupParticipants

-

Get group call participants

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phone.joinAsPeers b/data/core.telegram.org/constructor/phone.joinAsPeers deleted file mode 100644 index 9da076f9c0..0000000000 --- a/data/core.telegram.org/constructor/phone.joinAsPeers +++ /dev/null @@ -1,157 +0,0 @@ - - - - - phone.joinAsPeers - - - - - - - - - - - - - -
- -
-
-
- -

phone.joinAsPeers

- -

A list of peers that can be used to join a group call, presenting yourself as a specific user/channel.

-

- -
-
phone.joinAsPeers#afe5623f peers:Vector<Peer> chats:Vector<Chat> users:Vector<User> = phone.JoinAsPeers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peersVector<Peer>Peers
chatsVector<Chat>Chats mentioned in the peers vector
usersVector<User>Users mentioned in the peers vector
-

Type

-

phone.JoinAsPeers

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phone.phoneCall b/data/core.telegram.org/constructor/phone.phoneCall deleted file mode 100644 index fc55a16006..0000000000 --- a/data/core.telegram.org/constructor/phone.phoneCall +++ /dev/null @@ -1,152 +0,0 @@ - - - - - phone.phoneCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.phoneCall

- -

A VoIP phone call

-

- -
-
phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_callPhoneCallThe VoIP phone call
usersVector<User>VoIP phone call participants
-

Type

-

phone.PhoneCall

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneCall.html b/data/core.telegram.org/constructor/phoneCall.html deleted file mode 100644 index dcba9dafe1..0000000000 --- a/data/core.telegram.org/constructor/phoneCall.html +++ /dev/null @@ -1,209 +0,0 @@ - - - - - phoneCall - - - - - - - - - - - - - -
- -
-
-
- -

phoneCall

- -

Phone call

-

- -
-
phoneCall#967f7c67 flags:# p2p_allowed:flags.5?true video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long protocol:PhoneCallProtocol connections:Vector<PhoneConnection> start_date:int = PhoneCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
p2p_allowedflags.5?trueWhether P2P connection to the other peer is allowed
videoflags.6?trueWhether this is a video call
idlongCall ID
access_hashlongAccess hash
dateintDate of creation of the call
admin_idlongUser ID of the creator of the call
participant_idlongUser ID of the other participant in the call
g_a_or_bbytesParameter for key exchange
key_fingerprintlongKey fingerprint
protocolPhoneCallProtocolCall protocol info to be passed to libtgvoip
connectionsVector<PhoneConnection>List of endpoints the user can connect to to exchange call data
start_dateintWhen was the call actually started
-

Type

-

PhoneCall

-

Related pages

-

End-to-End Encrypted Voice Calls

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneCallAccepted.html b/data/core.telegram.org/constructor/phoneCallAccepted.html deleted file mode 100644 index 86e8ad2759..0000000000 --- a/data/core.telegram.org/constructor/phoneCallAccepted.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - phoneCallAccepted - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallAccepted

- -

An accepted phone call

-

- -
-
phoneCallAccepted#3660c311 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_b:bytes protocol:PhoneCallProtocol = PhoneCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.6?trueWhether this is a video call
idlongID of accepted phone call
access_hashlongAccess hash of phone call
dateintWhen was the call accepted
admin_idlongID of the call creator
participant_idlongID of the other user in the call
g_bbytesB parameter for secure E2E phone call key exchange
protocolPhoneCallProtocolProtocol to use for phone call
-

Type

-

PhoneCall

-

Related pages

-

End-to-End Encrypted Voice Calls

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneCallDiscardReasonBusy.html b/data/core.telegram.org/constructor/phoneCallDiscardReasonBusy.html deleted file mode 100644 index 123c8f66b9..0000000000 --- a/data/core.telegram.org/constructor/phoneCallDiscardReasonBusy.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - phoneCallDiscardReasonBusy - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallDiscardReasonBusy

- -

The phone call was discared because the user is busy in another call

-

- -
-
phoneCallDiscardReasonBusy#faf7e8c9 = PhoneCallDiscardReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PhoneCallDiscardReason

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneCallDiscardReasonDisconnect.html b/data/core.telegram.org/constructor/phoneCallDiscardReasonDisconnect.html deleted file mode 100644 index d736931a9a..0000000000 --- a/data/core.telegram.org/constructor/phoneCallDiscardReasonDisconnect.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - phoneCallDiscardReasonDisconnect - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallDiscardReasonDisconnect

- -

The phone call was disconnected

-

- -
-
phoneCallDiscardReasonDisconnect#e095c1a0 = PhoneCallDiscardReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PhoneCallDiscardReason

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneCallDiscardReasonHangup.html b/data/core.telegram.org/constructor/phoneCallDiscardReasonHangup.html deleted file mode 100644 index a79d8d0bdd..0000000000 --- a/data/core.telegram.org/constructor/phoneCallDiscardReasonHangup.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - phoneCallDiscardReasonHangup - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallDiscardReasonHangup

- -

The phone call was ended normally

-

- -
-
phoneCallDiscardReasonHangup#57adc690 = PhoneCallDiscardReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PhoneCallDiscardReason

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneCallDiscardReasonMissed.html b/data/core.telegram.org/constructor/phoneCallDiscardReasonMissed.html deleted file mode 100644 index 9283cfeec6..0000000000 --- a/data/core.telegram.org/constructor/phoneCallDiscardReasonMissed.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - phoneCallDiscardReasonMissed - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallDiscardReasonMissed

- -

The phone call was missed

-

- -
-
phoneCallDiscardReasonMissed#85e42301 = PhoneCallDiscardReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PhoneCallDiscardReason

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneCallDiscarded.html b/data/core.telegram.org/constructor/phoneCallDiscarded.html deleted file mode 100644 index b3a32314fc..0000000000 --- a/data/core.telegram.org/constructor/phoneCallDiscarded.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - phoneCallDiscarded - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallDiscarded

- -

Indicates a discarded phone call

-

- -
-
phoneCallDiscarded#50ca4de1 flags:# need_rating:flags.2?true need_debug:flags.3?true video:flags.6?true id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = PhoneCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
need_ratingflags.2?trueWhether the server required the user to rate the call
need_debugflags.3?trueWhether the server required the client to send the libtgvoip call debug data
videoflags.6?trueWhether the call was a video call
idlongCall ID
reasonflags.0?PhoneCallDiscardReasonWhy was the phone call discarded
durationflags.1?intDuration of the phone call in seconds
-

Type

-

PhoneCall

-

Related pages

-

phone.setCallRating

-

Rate a call

-

phone.saveCallDebug

-

Send phone call debug data to server

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneCallProtocol.html b/data/core.telegram.org/constructor/phoneCallProtocol.html deleted file mode 100644 index 65e1a9db31..0000000000 --- a/data/core.telegram.org/constructor/phoneCallProtocol.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - phoneCallProtocol - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallProtocol

- -

Protocol info for libtgvoip

-

- -
-
phoneCallProtocol#fc878fc8 flags:# udp_p2p:flags.0?true udp_reflector:flags.1?true min_layer:int max_layer:int library_versions:Vector<string> = PhoneCallProtocol;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
udp_p2pflags.0?trueWhether to allow P2P connection to the other participant
udp_reflectorflags.1?trueWhether to allow connection to the other participants through the reflector servers
min_layerintMinimum layer for remote libtgvoip
max_layerintMaximum layer for remote libtgvoip
library_versionsVector<string>When using phone.requestCall and phone.acceptCall, specify all library versions supported by the client.
The server will merge and choose the best library version supported by both peers, returning only the best value in the result of the callee's phone.acceptCall and in the phoneCallAccepted update received by the caller.
-

Type

-

PhoneCallProtocol

-

Related pages

-

phone.requestCall

-

Start a telegram phone call

-

phone.acceptCall

-

Accept incoming call

-

phoneCallAccepted

-

An accepted phone call

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneCallRequested.html b/data/core.telegram.org/constructor/phoneCallRequested.html deleted file mode 100644 index 34eb4e4dd2..0000000000 --- a/data/core.telegram.org/constructor/phoneCallRequested.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - phoneCallRequested - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallRequested

- -

Requested phone call

-

- -
-
phoneCallRequested#14b0ed0c flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_hash:bytes protocol:PhoneCallProtocol = PhoneCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.6?trueWhether this is a video call
idlongPhone call ID
access_hashlongAccess hash
dateintWhen was the phone call created
admin_idlongID of the creator of the phone call
participant_idlongID of the other participant of the phone call
g_a_hashbytesParameter for key exchange
protocolPhoneCallProtocolCall protocol info to be passed to libtgvoip
-

Type

-

PhoneCall

-

Related pages

-

End-to-End Encrypted Voice Calls

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneCallWaiting.html b/data/core.telegram.org/constructor/phoneCallWaiting.html deleted file mode 100644 index e0ea1c39ef..0000000000 --- a/data/core.telegram.org/constructor/phoneCallWaiting.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - phoneCallWaiting - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallWaiting

- -

Incoming phone call

-

- -
-
phoneCallWaiting#c5226f17 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long protocol:PhoneCallProtocol receive_date:flags.0?int = PhoneCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.6?trueIs this a video call
idlongCall ID
access_hashlongAccess hash
dateintDate
admin_idlongAdmin ID
participant_idlongParticipant ID
protocolPhoneCallProtocolPhone call protocol info
receive_dateflags.0?intWhen was the phone call received
-

Type

-

PhoneCall

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneConnection.html b/data/core.telegram.org/constructor/phoneConnection.html deleted file mode 100644 index 3d716a6502..0000000000 --- a/data/core.telegram.org/constructor/phoneConnection.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - phoneConnection - - - - - - - - - - - - - -
- -
-
-
- -

phoneConnection

- -

Identifies an endpoint that can be used to connect to the other user in a phone call

-

- -
-
phoneConnection#9d4c17c0 id:long ip:string ipv6:string port:int peer_tag:bytes = PhoneConnection;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongEndpoint ID
ipstringIP address of endpoint
ipv6stringIPv6 address of endpoint
portintPort ID
peer_tagbytesOur peer tag
-

Type

-

PhoneConnection

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/phoneConnectionWebrtc.html b/data/core.telegram.org/constructor/phoneConnectionWebrtc.html deleted file mode 100644 index 4a9891e060..0000000000 --- a/data/core.telegram.org/constructor/phoneConnectionWebrtc.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - phoneConnectionWebrtc - - - - - - - - - - - - - -
- -
-
-
- -

phoneConnectionWebrtc

- -

WebRTC connection parameters

-

- -
-
phoneConnectionWebrtc#635fe375 flags:# turn:flags.0?true stun:flags.1?true id:long ip:string ipv6:string port:int username:string password:string = PhoneConnection;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
turnflags.0?trueWhether this is a TURN endpoint
stunflags.1?trueWhether this is a STUN endpoint
idlongEndpoint ID
ipstringIP address
ipv6stringIPv6 address
portintPort
usernamestringUsername
passwordstringPassword
-

Type

-

PhoneConnection

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/photo.html b/data/core.telegram.org/constructor/photo.html deleted file mode 100644 index 9d1e2ee6fd..0000000000 --- a/data/core.telegram.org/constructor/photo.html +++ /dev/null @@ -1,192 +0,0 @@ - - - - - photo - - - - - - - - - - - - - -
- -
-
-
- -

photo

- -

Photo

-

- -
-
photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
has_stickersflags.0?trueWhether the photo has mask stickers attached to it
idlongID
access_hashlongAccess hash
file_referencebytesfile reference
dateintDate of upload
sizesVector<PhotoSize>Available sizes for download
video_sizesflags.1?Vector<VideoSize>For animated profiles, the MPEG4 videos
dc_idintDC ID to use for download
-

Type

-

Photo

-

Related pages

-

File references

-

How to handle file references.

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/photoCachedSize.html b/data/core.telegram.org/constructor/photoCachedSize.html deleted file mode 100644 index 15adf1e61a..0000000000 --- a/data/core.telegram.org/constructor/photoCachedSize.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - photoCachedSize - - - - - - - - - - - - - -
- -
-
-
- -

photoCachedSize

- -

Description of an image and its content.

-

- -
-
photoCachedSize#21e1ad6 type:string w:int h:int bytes:bytes = PhotoSize;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typestringThumbnail type
wintImage width
hintImage height
bytesbytesBinary data, file content
-

Type

-

PhotoSize

-

Thumbnail type and its sizes

-

See here.

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/photoEmpty.html b/data/core.telegram.org/constructor/photoEmpty.html deleted file mode 100644 index 93b32cc30a..0000000000 --- a/data/core.telegram.org/constructor/photoEmpty.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - photoEmpty - - - - - - - - - - - - - -
- -
-
-
- -

photoEmpty

- -

Empty constructor, non-existent photo

-

- -
-
photoEmpty#2331b22d id:long = Photo;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idlongPhoto identifier
-

Type

-

Photo

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/photoPathSize.html b/data/core.telegram.org/constructor/photoPathSize.html deleted file mode 100644 index 51ffd63c8a..0000000000 --- a/data/core.telegram.org/constructor/photoPathSize.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - photoPathSize - - - - - - - - - - - - - -
- -
-
-
- -

photoPathSize

- -

Messages with animated stickers can have a compressed svg (< 300 bytes) to show the outline of the sticker before fetching the actual lottie animation.

-

- -
-
photoPathSize#d8214d41 type:string bytes:bytes = PhotoSize;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typestringAlways j
bytesbytesCompressed SVG path payload, see here for decompression instructions
-

Type

-

PhotoSize

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/photoSize.html b/data/core.telegram.org/constructor/photoSize.html deleted file mode 100644 index 6b9a13a466..0000000000 --- a/data/core.telegram.org/constructor/photoSize.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - photoSize - - - - - - - - - - - - - -
- -
-
-
- -

photoSize

- -

Image description.

-

- -
-
photoSize#75c78e60 type:string w:int h:int size:int = PhotoSize;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typestringThumbnail type
wintImage width
hintImage height
sizeintFile size
-

Type

-

PhotoSize

-

Thumbnail type and its sizes

-

See here.

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/photoSizeEmpty.html b/data/core.telegram.org/constructor/photoSizeEmpty.html deleted file mode 100644 index f32028a6ae..0000000000 --- a/data/core.telegram.org/constructor/photoSizeEmpty.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - photoSizeEmpty - - - - - - - - - - - - - -
- -
-
-
- -

photoSizeEmpty

- -

Empty constructor. Image with this thumbnail is unavailable.

-

- -
-
photoSizeEmpty#e17e23c type:string = PhotoSize;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
typestringThumbnail type (see. photoSize)
-

Type

-

PhotoSize

-

Related pages

-

photoSize

-

Image description.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/photoSizeProgressive.html b/data/core.telegram.org/constructor/photoSizeProgressive.html deleted file mode 100644 index 04f09890b3..0000000000 --- a/data/core.telegram.org/constructor/photoSizeProgressive.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - photoSizeProgressive - - - - - - - - - - - - - -
- -
-
-
- -

photoSizeProgressive

- -

Progressively encoded photosize

-

- -
-
photoSizeProgressive#fa3efb95 type:string w:int h:int sizes:Vector<int> = PhotoSize;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typestringPhotosize type
wintPhoto width
hintPhoto height
sizesVector<int>Sizes of progressive JPEG file prefixes, which can be used to preliminarily show the image.
-

Type

-

PhotoSize

-

Thumbnail type and its sizes

-

See here.

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/photoStrippedSize.html b/data/core.telegram.org/constructor/photoStrippedSize.html deleted file mode 100644 index 6fb252ccfb..0000000000 --- a/data/core.telegram.org/constructor/photoStrippedSize.html +++ /dev/null @@ -1,159 +0,0 @@ - - - - - photoStrippedSize - - - - - - - - - - - - - -
- -
-
-
- -

photoStrippedSize

- -

A low-resolution compressed JPG payload

-

- -
-
photoStrippedSize#e0b0bc2e type:string bytes:bytes = PhotoSize;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typestringThumbnail type
bytesbytesThumbnail data, see here for more info on decompression »
-

Type

-

PhotoSize

-

Thumbnail type and its sizes

-

See the photoSize constructor.

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

-

photoSize

-

Image description.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/photos.photo b/data/core.telegram.org/constructor/photos.photo deleted file mode 100644 index cdd463d8b2..0000000000 --- a/data/core.telegram.org/constructor/photos.photo +++ /dev/null @@ -1,152 +0,0 @@ - - - - - photos.photo - - - - - - - - - - - - - -
- -
-
-
- -

photos.photo

- -

Photo with auxiliary data.

-

- -
-
photos.photo#20212ca8 photo:Photo users:Vector<User> = photos.Photo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
photoPhotoPhoto
usersVector<User>Users
-

Type

-

photos.Photo

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/photos.photos b/data/core.telegram.org/constructor/photos.photos deleted file mode 100644 index 8e11ec97d4..0000000000 --- a/data/core.telegram.org/constructor/photos.photos +++ /dev/null @@ -1,152 +0,0 @@ - - - - - photos.photos - - - - - - - - - - - - - -
- -
-
-
- -

photos.photos

- -

Full list of photos with auxiliary data.

-

- -
-
photos.photos#8dca6aa5 photos:Vector<Photo> users:Vector<User> = photos.Photos;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
photosVector<Photo>List of photos
usersVector<User>List of mentioned users
-

Type

-

photos.Photos

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/photos.photosSlice b/data/core.telegram.org/constructor/photos.photosSlice deleted file mode 100644 index 5ea78e2a0c..0000000000 --- a/data/core.telegram.org/constructor/photos.photosSlice +++ /dev/null @@ -1,157 +0,0 @@ - - - - - photos.photosSlice - - - - - - - - - - - - - -
- -
-
-
- -

photos.photosSlice

- -

Incomplete list of photos with auxiliary data.

-

- -
-
photos.photosSlice#15051f54 count:int photos:Vector<Photo> users:Vector<User> = photos.Photos;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countintTotal number of photos
photosVector<Photo>List of photos
usersVector<User>List of mentioned users
-

Type

-

photos.Photos

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/poll.html b/data/core.telegram.org/constructor/poll.html deleted file mode 100644 index 55d47dbc5d..0000000000 --- a/data/core.telegram.org/constructor/poll.html +++ /dev/null @@ -1,195 +0,0 @@ - - - - - poll - - - - - - - - - - - - - -
- -
-
-
- -

poll

- -

Poll

-

- -
-
poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongID of the poll
flags#Flags, see TL conditional fields
closedflags.0?trueWhether the poll is closed and doesn't accept any more answers
public_votersflags.1?trueWhether cast votes are publicly visible to all users (non-anonymous poll)
multiple_choiceflags.2?trueWhether multiple options can be chosen as answer
quizflags.3?trueWhether this is a quiz (with wrong and correct answers, results shown in the return type)
questionstringThe question of the poll
answersVector<PollAnswer>The possible answers, vote using messages.sendVote.
close_periodflags.4?intAmount of time in seconds the poll will be active after creation, 5-600. Can't be used together with close_date.
close_dateflags.5?intPoint in time (Unix timestamp) when the poll will be automatically closed. Must be at least 5 and no more than 600 seconds in the future; can't be used together with close_period.
-

Type

-

Poll

-

Related pages

-

messages.sendVote

-

Vote in a poll

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pollAnswer.html b/data/core.telegram.org/constructor/pollAnswer.html deleted file mode 100644 index 92870d7ac6..0000000000 --- a/data/core.telegram.org/constructor/pollAnswer.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - pollAnswer - - - - - - - - - - - - - -
- -
-
-
- -

pollAnswer

- -

A possible answer of a poll

-

- -
-
pollAnswer#6ca9c2e9 text:string option:bytes = PollAnswer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textstringTextual representation of the answer
optionbytesThe param that has to be passed to messages.sendVote.
-

Type

-

PollAnswer

-

Related pages

-

messages.sendVote

-

Vote in a poll

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pollAnswerVoters.html b/data/core.telegram.org/constructor/pollAnswerVoters.html deleted file mode 100644 index 494b0a6316..0000000000 --- a/data/core.telegram.org/constructor/pollAnswerVoters.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - pollAnswerVoters - - - - - - - - - - - - - -
- -
-
-
- -

pollAnswerVoters

- -

A poll answer, and how users voted on it

-

- -
-
pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
chosenflags.0?trueWhether we have chosen this answer
correctflags.1?trueFor quizes, whether the option we have chosen is correct
optionbytesThe param that has to be passed to messages.sendVote.
votersintHow many users voted for this option
-

Type

-

PollAnswerVoters

-

Related pages

-

messages.sendVote

-

Vote in a poll

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/pollResults.html b/data/core.telegram.org/constructor/pollResults.html deleted file mode 100644 index f21c0eb9c6..0000000000 --- a/data/core.telegram.org/constructor/pollResults.html +++ /dev/null @@ -1,184 +0,0 @@ - - - - - pollResults - - - - - - - - - - - - - -
- -
-
-
- -

pollResults

- -

Results of poll

-

- -
-
pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
minflags.0?trueSimilar to min objects, used for poll constructors that are the same for all users so they don't have option chosen by the current user (you can use messages.getPollResults to get the full poll results).
resultsflags.1?Vector<PollAnswerVoters>Poll results
total_votersflags.2?intTotal number of people that voted in the poll
recent_votersflags.3?Vector<long>IDs of the last users that recently voted in the poll
solutionflags.4?stringExplanation of quiz solution
solution_entitiesflags.4?Vector<MessageEntity>Message entities for styled text in quiz solution
-

Type

-

PollResults

-

Related pages

-

Min constructors

-

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

-

messages.getPollResults

-

Get poll results

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/postAddress.html b/data/core.telegram.org/constructor/postAddress.html deleted file mode 100644 index a278e6fd1e..0000000000 --- a/data/core.telegram.org/constructor/postAddress.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - postAddress - - - - - - - - - - - - - -
- -
-
-
- -

postAddress

- -

Shipping address

-

- -
-
postAddress#1e8caaeb street_line1:string street_line2:string city:string state:string country_iso2:string post_code:string = PostAddress;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
street_line1stringFirst line for the address
street_line2stringSecond line for the address
citystringCity
statestringState, if applicable (empty otherwise)
country_iso2stringISO 3166-1 alpha-2 country code
post_codestringAddress post code
-

Type

-

PostAddress

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyKeyAddedByPhone.html b/data/core.telegram.org/constructor/privacyKeyAddedByPhone.html deleted file mode 100644 index 90dde99417..0000000000 --- a/data/core.telegram.org/constructor/privacyKeyAddedByPhone.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyAddedByPhone - - - - - - - - - - - - - -
- -
-
-
- -

privacyKeyAddedByPhone

- -

Whether people can add you to their contact list by your phone number

-

- -
-
privacyKeyAddedByPhone#42ffd42b = PrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyKeyChatInvite.html b/data/core.telegram.org/constructor/privacyKeyChatInvite.html deleted file mode 100644 index acdb7d4a55..0000000000 --- a/data/core.telegram.org/constructor/privacyKeyChatInvite.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

privacyKeyChatInvite

- -

Whether the user can be invited to chats

-

- -
-
privacyKeyChatInvite#500e6dfa = PrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyKeyForwards.html b/data/core.telegram.org/constructor/privacyKeyForwards.html deleted file mode 100644 index 27ac48e238..0000000000 --- a/data/core.telegram.org/constructor/privacyKeyForwards.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyForwards - - - - - - - - - - - - - -
- -
-
-
- -

privacyKeyForwards

- -

Whether messages forwarded from the user will be anonymously forwarded

-

- -
-
privacyKeyForwards#69ec56a3 = PrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyKeyPhoneCall.html b/data/core.telegram.org/constructor/privacyKeyPhoneCall.html deleted file mode 100644 index 0fb27a24e1..0000000000 --- a/data/core.telegram.org/constructor/privacyKeyPhoneCall.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyPhoneCall - - - - - - - - - - - - - -
- -
-
-
- -

privacyKeyPhoneCall

- -

Whether the user accepts phone calls

-

- -
-
privacyKeyPhoneCall#3d662b7b = PrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyKeyPhoneNumber.html b/data/core.telegram.org/constructor/privacyKeyPhoneNumber.html deleted file mode 100644 index c3e42dae75..0000000000 --- a/data/core.telegram.org/constructor/privacyKeyPhoneNumber.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyPhoneNumber - - - - - - - - - - - - - -
- -
-
-
- -

privacyKeyPhoneNumber

- -

Whether the user allows us to see his phone number

-

- -
-
privacyKeyPhoneNumber#d19ae46d = PrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyKeyPhoneP2P.html b/data/core.telegram.org/constructor/privacyKeyPhoneP2P.html deleted file mode 100644 index 96dcfcf675..0000000000 --- a/data/core.telegram.org/constructor/privacyKeyPhoneP2P.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyPhoneP2P - - - - - - - - - - - - - -
- -
-
-
- -

privacyKeyPhoneP2P

- -

Whether P2P connections in phone calls are allowed

-

- -
-
privacyKeyPhoneP2P#39491cc8 = PrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyKeyProfilePhoto.html b/data/core.telegram.org/constructor/privacyKeyProfilePhoto.html deleted file mode 100644 index 1e6eeda0db..0000000000 --- a/data/core.telegram.org/constructor/privacyKeyProfilePhoto.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyProfilePhoto - - - - - - - - - - - - - -
- -
-
-
- -

privacyKeyProfilePhoto

- -

Whether the profile picture of the user is visible

-

- -
-
privacyKeyProfilePhoto#96151fed = PrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyKeyStatusTimestamp.html b/data/core.telegram.org/constructor/privacyKeyStatusTimestamp.html deleted file mode 100644 index 44ae3b03f2..0000000000 --- a/data/core.telegram.org/constructor/privacyKeyStatusTimestamp.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyStatusTimestamp - - - - - - - - - - - - - -
- -
-
-
- -

privacyKeyStatusTimestamp

- -

Whether we can see the last online timestamp

-

- -
-
privacyKeyStatusTimestamp#bc2eab30 = PrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyValueAllowAll.html b/data/core.telegram.org/constructor/privacyValueAllowAll.html deleted file mode 100644 index 334775c79a..0000000000 --- a/data/core.telegram.org/constructor/privacyValueAllowAll.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyValueAllowAll - - - - - - - - - - - - - -
- -
-
-
- -

privacyValueAllowAll

- -

Allow all users

-

- -
-
privacyValueAllowAll#65427b82 = PrivacyRule;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyValueAllowChatParticipants.html b/data/core.telegram.org/constructor/privacyValueAllowChatParticipants.html deleted file mode 100644 index 9e1fb6d291..0000000000 --- a/data/core.telegram.org/constructor/privacyValueAllowChatParticipants.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - privacyValueAllowChatParticipants - - - - - - - - - - - - - -
- -
-
-
- -

privacyValueAllowChatParticipants

- -

Allow all participants of certain chats

-

- -
-
privacyValueAllowChatParticipants#6b134e8e chats:Vector<long> = PrivacyRule;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chatsVector<long>Allowed chats
-

Type

-

PrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyValueAllowContacts.html b/data/core.telegram.org/constructor/privacyValueAllowContacts.html deleted file mode 100644 index b93c047dfc..0000000000 --- a/data/core.telegram.org/constructor/privacyValueAllowContacts.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyValueAllowContacts - - - - - - - - - - - - - -
- -
-
-
- -

privacyValueAllowContacts

- -

Allow all contacts

-

- -
-
privacyValueAllowContacts#fffe1bac = PrivacyRule;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyValueAllowUsers.html b/data/core.telegram.org/constructor/privacyValueAllowUsers.html deleted file mode 100644 index 74c2d8375e..0000000000 --- a/data/core.telegram.org/constructor/privacyValueAllowUsers.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - privacyValueAllowUsers - - - - - - - - - - - - - -
- -
-
-
- -

privacyValueAllowUsers

- -

Allow only certain users

-

- -
-
privacyValueAllowUsers#b8905fb2 users:Vector<long> = PrivacyRule;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
usersVector<long>Allowed users
-

Type

-

PrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyValueDisallowAll.html b/data/core.telegram.org/constructor/privacyValueDisallowAll.html deleted file mode 100644 index 726ea2978a..0000000000 --- a/data/core.telegram.org/constructor/privacyValueDisallowAll.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyValueDisallowAll - - - - - - - - - - - - - -
- -
-
-
- -

privacyValueDisallowAll

- -

Disallow all users

-

- -
-
privacyValueDisallowAll#8b73e763 = PrivacyRule;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyValueDisallowContacts.html b/data/core.telegram.org/constructor/privacyValueDisallowContacts.html deleted file mode 100644 index 40cb335dcd..0000000000 --- a/data/core.telegram.org/constructor/privacyValueDisallowContacts.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyValueDisallowContacts - - - - - - - - - - - - - -
- -
-
-
- -

privacyValueDisallowContacts

- -

Disallow only contacts

-

- -
-
privacyValueDisallowContacts#f888fa1a = PrivacyRule;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/privacyValueDisallowUsers.html b/data/core.telegram.org/constructor/privacyValueDisallowUsers.html deleted file mode 100644 index e0f2dc77a6..0000000000 --- a/data/core.telegram.org/constructor/privacyValueDisallowUsers.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - privacyValueDisallowUsers - - - - - - - - - - - - - -
- -
-
-
- -

privacyValueDisallowUsers

- -

Disallow only certain users

-

- -
-
privacyValueDisallowUsers#e4621141 users:Vector<long> = PrivacyRule;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
usersVector<long>Disallowed users
-

Type

-

PrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/receivedNotifyMessage.html b/data/core.telegram.org/constructor/receivedNotifyMessage.html deleted file mode 100644 index 369fba0239..0000000000 --- a/data/core.telegram.org/constructor/receivedNotifyMessage.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - receivedNotifyMessage - - - - - - - - - - - - - -
- -
-
-
- -

receivedNotifyMessage

- -

Message ID, for which PUSH-notifications were cancelled.

-

- -
-
receivedNotifyMessage#a384b779 id:int flags:int = ReceivedNotifyMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idintMessage ID, for which PUSH-notifications were canceled
flagsintReserved for future use
-

Type

-

ReceivedNotifyMessage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/recentMeUrlChat.html b/data/core.telegram.org/constructor/recentMeUrlChat.html deleted file mode 100644 index 366ba650bc..0000000000 --- a/data/core.telegram.org/constructor/recentMeUrlChat.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - recentMeUrlChat - - - - - - - - - - - - - -
- -
-
-
- -

recentMeUrlChat

- -

Recent t.me link to a chat

-

- -
-
recentMeUrlChat#b2da71d2 url:string chat_id:long = RecentMeUrl;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringt.me URL
chat_idlongChat ID
-

Type

-

RecentMeUrl

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/recentMeUrlChatInvite.html b/data/core.telegram.org/constructor/recentMeUrlChatInvite.html deleted file mode 100644 index f01570470f..0000000000 --- a/data/core.telegram.org/constructor/recentMeUrlChatInvite.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - recentMeUrlChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

recentMeUrlChatInvite

- -

Recent t.me invite link to a chat

-

- -
-
recentMeUrlChatInvite#eb49081d url:string chat_invite:ChatInvite = RecentMeUrl;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringt.me URL
chat_inviteChatInviteChat invitation
-

Type

-

RecentMeUrl

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/recentMeUrlStickerSet.html b/data/core.telegram.org/constructor/recentMeUrlStickerSet.html deleted file mode 100644 index 11c7deb858..0000000000 --- a/data/core.telegram.org/constructor/recentMeUrlStickerSet.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - recentMeUrlStickerSet - - - - - - - - - - - - - -
- -
-
-
- -

recentMeUrlStickerSet

- -

Recent t.me stickerset installation URL

-

- -
-
recentMeUrlStickerSet#bc0a57dc url:string set:StickerSetCovered = RecentMeUrl;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringt.me URL
setStickerSetCoveredStickerset
-

Type

-

RecentMeUrl

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/recentMeUrlUnknown.html b/data/core.telegram.org/constructor/recentMeUrlUnknown.html deleted file mode 100644 index 48665c4550..0000000000 --- a/data/core.telegram.org/constructor/recentMeUrlUnknown.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - recentMeUrlUnknown - - - - - - - - - - - - - -
- -
-
-
- -

recentMeUrlUnknown

- -

Unknown t.me url

-

- -
-
recentMeUrlUnknown#46e1d13d url:string = RecentMeUrl;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
urlstringURL
-

Type

-

RecentMeUrl

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/recentMeUrlUser.html b/data/core.telegram.org/constructor/recentMeUrlUser.html deleted file mode 100644 index b035f11485..0000000000 --- a/data/core.telegram.org/constructor/recentMeUrlUser.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - recentMeUrlUser - - - - - - - - - - - - - -
- -
-
-
- -

recentMeUrlUser

- -

Recent t.me link to a user

-

- -
-
recentMeUrlUser#b92c09e2 url:string user_id:long = RecentMeUrl;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringURL
user_idlongUser ID
-

Type

-

RecentMeUrl

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/replyInlineMarkup.html b/data/core.telegram.org/constructor/replyInlineMarkup.html deleted file mode 100644 index 358df9d4e8..0000000000 --- a/data/core.telegram.org/constructor/replyInlineMarkup.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - replyInlineMarkup - - - - - - - - - - - - - -
- -
-
-
- -

replyInlineMarkup

- -

Bot or inline keyboard

-

- -
-
replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
rowsVector<KeyboardButtonRow>Bot or inline keyboard rows
-

Type

-

ReplyMarkup

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/replyKeyboardForceReply.html b/data/core.telegram.org/constructor/replyKeyboardForceReply.html deleted file mode 100644 index 39a8734fae..0000000000 --- a/data/core.telegram.org/constructor/replyKeyboardForceReply.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - replyKeyboardForceReply - - - - - - - - - - - - - -
- -
-
-
- -

replyKeyboardForceReply

- -

Force the user to send a reply

-

- -
-
replyKeyboardForceReply#86b40b08 flags:# single_use:flags.1?true selective:flags.2?true placeholder:flags.3?string = ReplyMarkup;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
single_useflags.1?trueRequests clients to hide the keyboard as soon as it's been used. The keyboard will still be available, but clients will automatically display the usual letter-keyboard in the chat – the user can press a special button in the input field to see the custom keyboard again.
selectiveflags.2?trueUse this parameter if you want to show the keyboard to specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.
Example: A user requests to change the bot‘s language, bot replies to the request with a keyboard to select the new language. Other users in the group don’t see the keyboard.
placeholderflags.3?stringThe placeholder to be shown in the input field when the keyboard is active; 1-64 characters.
-

Type

-

ReplyMarkup

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/replyKeyboardHide.html b/data/core.telegram.org/constructor/replyKeyboardHide.html deleted file mode 100644 index 1e81784d4a..0000000000 --- a/data/core.telegram.org/constructor/replyKeyboardHide.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - replyKeyboardHide - - - - - - - - - - - - - -
- -
-
-
- -

replyKeyboardHide

- -

Hide sent bot keyboard

-

- -
-
replyKeyboardHide#a03e5b85 flags:# selective:flags.2?true = ReplyMarkup;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
selectiveflags.2?trueUse this flag if you want to remove the keyboard for specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.

Example: A user votes in a poll, bot returns confirmation message in reply to the vote and removes the keyboard for that user, while still showing the keyboard with poll options to users who haven't voted yet
-

Type

-

ReplyMarkup

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/replyKeyboardMarkup.html b/data/core.telegram.org/constructor/replyKeyboardMarkup.html deleted file mode 100644 index 7f2009e348..0000000000 --- a/data/core.telegram.org/constructor/replyKeyboardMarkup.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - replyKeyboardMarkup - - - - - - - - - - - - - -
- -
-
-
- -

replyKeyboardMarkup

- -

Bot keyboard

-

- -
-
replyKeyboardMarkup#85dd99d1 flags:# resize:flags.0?true single_use:flags.1?true selective:flags.2?true rows:Vector<KeyboardButtonRow> placeholder:flags.3?string = ReplyMarkup;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
resizeflags.0?trueRequests clients to resize the keyboard vertically for optimal fit (e.g., make the keyboard smaller if there are just two rows of buttons). If not set, the custom keyboard is always of the same height as the app's standard keyboard.
single_useflags.1?trueRequests clients to hide the keyboard as soon as it's been used. The keyboard will still be available, but clients will automatically display the usual letter-keyboard in the chat – the user can press a special button in the input field to see the custom keyboard again.
selectiveflags.2?trueUse this parameter if you want to show the keyboard to specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.

Example: A user requests to change the bot‘s language, bot replies to the request with a keyboard to select the new language. Other users in the group don’t see the keyboard.
rowsVector<KeyboardButtonRow>Button row
placeholderflags.3?stringThe placeholder to be shown in the input field when the keyboard is active; 1-64 characters.
-

Type

-

ReplyMarkup

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/restrictionReason.html b/data/core.telegram.org/constructor/restrictionReason.html deleted file mode 100644 index 101fe987d6..0000000000 --- a/data/core.telegram.org/constructor/restrictionReason.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - - restrictionReason - - - - - - - - - - - - - -
- -
-
-
- -

restrictionReason

- -

Restriction reason.

-

Contains the reason why access to a certain object must be restricted. Clients are supposed to deny access to the channel if the platform field is equal to all or to the current platform (ios, android, wp, etc.). Platforms can be concatenated (ios-android, ios-wp), unknown platforms are to be ignored. The text is the error message that should be shown to the user.

-

- -
-
restrictionReason#d072acb4 platform:string reason:string text:string = RestrictionReason;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
platformstringPlatform identifier (ios, android, wp, all, etc.), can be concatenated with a dash as separator (android-ios, ios-wp, etc)
reasonstringRestriction reason (porno, terms, etc.)
textstringError message to be shown to the user
-

Type

-

RestrictionReason

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/savedPhoneContact.html b/data/core.telegram.org/constructor/savedPhoneContact.html deleted file mode 100644 index e450c1f02b..0000000000 --- a/data/core.telegram.org/constructor/savedPhoneContact.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - savedPhoneContact - - - - - - - - - - - - - -
- -
-
-
- -

savedPhoneContact

- -

Saved contact

-

- -
-
savedPhoneContact#1142bd56 phone:string first_name:string last_name:string date:int = SavedContact;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phonestringPhone number
first_namestringFirst name
last_namestringLast name
dateintDate added
-

Type

-

SavedContact

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureCredentialsEncrypted.html b/data/core.telegram.org/constructor/secureCredentialsEncrypted.html deleted file mode 100644 index 8aac7afa96..0000000000 --- a/data/core.telegram.org/constructor/secureCredentialsEncrypted.html +++ /dev/null @@ -1,159 +0,0 @@ - - - - - secureCredentialsEncrypted - - - - - - - - - - - - - -
- -
-
-
- -

secureCredentialsEncrypted

- -

Encrypted credentials required to decrypt telegram passport data.

-

- -
-
secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
databytesEncrypted JSON-serialized data with unique user's payload, data hashes and secrets required for EncryptedPassportElement decryption and authentication, as described in decrypting data »
hashbytesData hash for data authentication as described in decrypting data »
secretbytesSecret, encrypted with the bot's public RSA key, required for data decryption as described in decrypting data »
-

Type

-

SecureCredentialsEncrypted

-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureData.html b/data/core.telegram.org/constructor/secureData.html deleted file mode 100644 index 5f46624a3e..0000000000 --- a/data/core.telegram.org/constructor/secureData.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - secureData - - - - - - - - - - - - - -
- -
-
-
- -

secureData

- -

Secure passport data, for more info see the passport docs »

-

- -
-
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
databytesData
data_hashbytesData hash
secretbytesSecret
-

Type

-

SecureData

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureFile.html b/data/core.telegram.org/constructor/secureFile.html deleted file mode 100644 index e8f04136c0..0000000000 --- a/data/core.telegram.org/constructor/secureFile.html +++ /dev/null @@ -1,180 +0,0 @@ - - - - - secureFile - - - - - - - - - - - - - -
- -
-
-
- -

secureFile

- -

Secure passport file, for more info see the passport docs »

-

- -
-
secureFile#e0277a62 id:long access_hash:long size:int dc_id:int date:int file_hash:bytes secret:bytes = SecureFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongID
access_hashlongAccess hash
sizeintFile size
dc_idintDC ID
dateintDate of upload
file_hashbytesFile hash
secretbytesSecret
-

Type

-

SecureFile

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureFileEmpty.html b/data/core.telegram.org/constructor/secureFileEmpty.html deleted file mode 100644 index e038aa90f8..0000000000 --- a/data/core.telegram.org/constructor/secureFileEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureFileEmpty - - - - - - - - - - - - - -
- -
-
-
- -

secureFileEmpty

- -

Empty constructor

-

- -
-
secureFileEmpty#64199744 = SecureFile;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureFile

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/securePasswordKdfAlgoPBKDF2HMACSHA512iter100000.html b/data/core.telegram.org/constructor/securePasswordKdfAlgoPBKDF2HMACSHA512iter100000.html deleted file mode 100644 index e261f3b770..0000000000 --- a/data/core.telegram.org/constructor/securePasswordKdfAlgoPBKDF2HMACSHA512iter100000.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - securePasswordKdfAlgoPBKDF2HMACSHA512iter100000 - - - - - - - - - - - - - -
- -
-
-
- -

securePasswordKdfAlgoPBKDF2HMACSHA512iter100000

- -

PBKDF2 with SHA512 and 100000 iterations KDF algo

-

- -
-
securePasswordKdfAlgoPBKDF2HMACSHA512iter100000#bbf2dda0 salt:bytes = SecurePasswordKdfAlgo;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
saltbytesSalt
-

Type

-

SecurePasswordKdfAlgo

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/securePasswordKdfAlgoSHA512.html b/data/core.telegram.org/constructor/securePasswordKdfAlgoSHA512.html deleted file mode 100644 index cc27b9b16d..0000000000 --- a/data/core.telegram.org/constructor/securePasswordKdfAlgoSHA512.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - securePasswordKdfAlgoSHA512 - - - - - - - - - - - - - -
- -
-
-
- -

securePasswordKdfAlgoSHA512

- -

SHA512 KDF algo

-

- -
-
securePasswordKdfAlgoSHA512#86471d92 salt:bytes = SecurePasswordKdfAlgo;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
saltbytesSalt
-

Type

-

SecurePasswordKdfAlgo

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/securePasswordKdfAlgoUnknown.html b/data/core.telegram.org/constructor/securePasswordKdfAlgoUnknown.html deleted file mode 100644 index efedcb8096..0000000000 --- a/data/core.telegram.org/constructor/securePasswordKdfAlgoUnknown.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - securePasswordKdfAlgoUnknown - - - - - - - - - - - - - -
- -
-
-
- -

securePasswordKdfAlgoUnknown

- -

Unknown KDF algo (most likely the client has to be updated)

-

- -
-
securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecurePasswordKdfAlgo

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/securePlainEmail.html b/data/core.telegram.org/constructor/securePlainEmail.html deleted file mode 100644 index 3ffdc4669c..0000000000 --- a/data/core.telegram.org/constructor/securePlainEmail.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - securePlainEmail - - - - - - - - - - - - - -
- -
-
-
- -

securePlainEmail

- -

Email address to use in telegram passport: it must be verified, first ».

-

- -
-
securePlainEmail#21ec5a5f email:string = SecurePlainData;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
emailstringEmail address
-

Type

-

SecurePlainData

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/securePlainPhone.html b/data/core.telegram.org/constructor/securePlainPhone.html deleted file mode 100644 index 68faa5d2ad..0000000000 --- a/data/core.telegram.org/constructor/securePlainPhone.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - securePlainPhone - - - - - - - - - - - - - -
- -
-
-
- -

securePlainPhone

- -

Phone number to use in telegram passport: it must be verified, first ».

-

- -
-
securePlainPhone#7d6099dd phone:string = SecurePlainData;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
phonestringPhone number
-

Type

-

SecurePlainData

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureRequiredType.html b/data/core.telegram.org/constructor/secureRequiredType.html deleted file mode 100644 index 0ec1da6d0e..0000000000 --- a/data/core.telegram.org/constructor/secureRequiredType.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - secureRequiredType - - - - - - - - - - - - - -
- -
-
-
- -

secureRequiredType

- -

Required type

-

- -
-
secureRequiredType#829d99da flags:# native_names:flags.0?true selfie_required:flags.1?true translation_required:flags.2?true type:SecureValueType = SecureRequiredType;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
native_namesflags.0?trueNative names
selfie_requiredflags.1?trueIs a selfie required
translation_requiredflags.2?trueIs a translation required
typeSecureValueTypeSecure value type
-

Type

-

SecureRequiredType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureSecretSettings.html b/data/core.telegram.org/constructor/secureSecretSettings.html deleted file mode 100644 index 256ecbbcd3..0000000000 --- a/data/core.telegram.org/constructor/secureSecretSettings.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - secureSecretSettings - - - - - - - - - - - - - -
- -
-
-
- -

secureSecretSettings

- -

Secure settings

-

- -
-
secureSecretSettings#1527bcac secure_algo:SecurePasswordKdfAlgo secure_secret:bytes secure_secret_id:long = SecureSecretSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
secure_algoSecurePasswordKdfAlgoSecure KDF algo
secure_secretbytesSecure secret
secure_secret_idlongSecret ID
-

Type

-

SecureSecretSettings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValue.html b/data/core.telegram.org/constructor/secureValue.html deleted file mode 100644 index 9f4304ca11..0000000000 --- a/data/core.telegram.org/constructor/secureValue.html +++ /dev/null @@ -1,194 +0,0 @@ - - - - - secureValue - - - - - - - - - - - - - -
- -
-
-
- -

secureValue

- -

Secure value

-

- -
-
secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
typeSecureValueTypeSecure passport value type
dataflags.0?SecureDataEncrypted Telegram Passport element data
front_sideflags.1?SecureFileEncrypted passport file with the front side of the document
reverse_sideflags.2?SecureFileEncrypted passport file with the reverse side of the document
selfieflags.3?SecureFileEncrypted passport file with a selfie of the user holding the document
translationflags.6?Vector<SecureFile>Array of encrypted passport files with translated versions of the provided documents
filesflags.4?Vector<SecureFile>Array of encrypted passport files with photos the of the documents
plain_dataflags.5?SecurePlainDataPlaintext verified passport data
hashbytesData hash
-

Type

-

SecureValue

-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueError.html b/data/core.telegram.org/constructor/secureValueError.html deleted file mode 100644 index 98db7a6786..0000000000 --- a/data/core.telegram.org/constructor/secureValueError.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - secureValueError - - - - - - - - - - - - - -
- -
-
-
- -

secureValueError

- -

Secure value error

-

- -
-
secureValueError#869d758f type:SecureValueType hash:bytes text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeType of element which has the issue
hashbytesHash
textstringError message
-

Type

-

SecureValueError

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueErrorData.html b/data/core.telegram.org/constructor/secureValueErrorData.html deleted file mode 100644 index 841de58f46..0000000000 --- a/data/core.telegram.org/constructor/secureValueErrorData.html +++ /dev/null @@ -1,175 +0,0 @@ - - - - - secureValueErrorData - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorData

- -

Represents an issue in one of the data fields that was provided by the user. The error is considered resolved when the field's value changes.

-

- -
-
secureValueErrorData#e8a40bd9 type:SecureValueType data_hash:bytes field:string text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeThe section of the user's Telegram Passport which has the error, one of secureValueTypePersonalDetails, secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport, secureValueTypeAddress
data_hashbytesData hash
fieldstringName of the data field which has the error
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypePersonalDetails

-

Personal details

-

secureValueTypePassport

-

Passport

-

secureValueTypeDriverLicense

-

Driver's license

-

secureValueTypeIdentityCard

-

Identity card

-

secureValueTypeInternalPassport

-

Internal passport

-

secureValueTypeAddress

-

Address

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueErrorFile.html b/data/core.telegram.org/constructor/secureValueErrorFile.html deleted file mode 100644 index d50de5bf36..0000000000 --- a/data/core.telegram.org/constructor/secureValueErrorFile.html +++ /dev/null @@ -1,168 +0,0 @@ - - - - - secureValueErrorFile - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorFile

- -

Represents an issue with a document scan. The error is considered resolved when the file with the document scan changes.

-

- -
-
secureValueErrorFile#7a700873 type:SecureValueType file_hash:bytes text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeOne of secureValueTypeUtilityBill, secureValueTypeBankStatement, secureValueTypeRentalAgreement, secureValueTypePassportRegistration, secureValueTypeTemporaryRegistration
file_hashbytesFile hash
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypeUtilityBill

-

Utility bill

-

secureValueTypeBankStatement

-

Bank statement

-

secureValueTypeRentalAgreement

-

Rental agreement

-

secureValueTypePassportRegistration

-

Internal registration passport

-

secureValueTypeTemporaryRegistration

-

Temporary registration

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueErrorFiles.html b/data/core.telegram.org/constructor/secureValueErrorFiles.html deleted file mode 100644 index 4b44f96a63..0000000000 --- a/data/core.telegram.org/constructor/secureValueErrorFiles.html +++ /dev/null @@ -1,168 +0,0 @@ - - - - - secureValueErrorFiles - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorFiles

- -

Represents an issue with a list of scans. The error is considered resolved when the list of files containing the scans changes.

-

- -
-
secureValueErrorFiles#666220e9 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeOne of secureValueTypeUtilityBill, secureValueTypeBankStatement, secureValueTypeRentalAgreement, secureValueTypePassportRegistration, secureValueTypeTemporaryRegistration
file_hashVector<bytes>File hash
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypeUtilityBill

-

Utility bill

-

secureValueTypeBankStatement

-

Bank statement

-

secureValueTypeRentalAgreement

-

Rental agreement

-

secureValueTypePassportRegistration

-

Internal registration passport

-

secureValueTypeTemporaryRegistration

-

Temporary registration

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueErrorFrontSide.html b/data/core.telegram.org/constructor/secureValueErrorFrontSide.html deleted file mode 100644 index 9fc313585b..0000000000 --- a/data/core.telegram.org/constructor/secureValueErrorFrontSide.html +++ /dev/null @@ -1,166 +0,0 @@ - - - - - secureValueErrorFrontSide - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorFrontSide

- -

Represents an issue with the front side of a document. The error is considered resolved when the file with the front side of the document changes.

-

- -
-
secureValueErrorFrontSide#be3dfa type:SecureValueType file_hash:bytes text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeOne of secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport
file_hashbytesFile hash
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypePassport

-

Passport

-

secureValueTypeDriverLicense

-

Driver's license

-

secureValueTypeIdentityCard

-

Identity card

-

secureValueTypeInternalPassport

-

Internal passport

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueErrorReverseSide.html b/data/core.telegram.org/constructor/secureValueErrorReverseSide.html deleted file mode 100644 index 91bb222d72..0000000000 --- a/data/core.telegram.org/constructor/secureValueErrorReverseSide.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - secureValueErrorReverseSide - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorReverseSide

- -

Represents an issue with the reverse side of a document. The error is considered resolved when the file with reverse side of the document changes.

-

- -
-
secureValueErrorReverseSide#868a2aa5 type:SecureValueType file_hash:bytes text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeOne of secureValueTypeDriverLicense, secureValueTypeIdentityCard
file_hashbytesFile hash
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypeDriverLicense

-

Driver's license

-

secureValueTypeIdentityCard

-

Identity card

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueErrorSelfie.html b/data/core.telegram.org/constructor/secureValueErrorSelfie.html deleted file mode 100644 index 0a05a21b7f..0000000000 --- a/data/core.telegram.org/constructor/secureValueErrorSelfie.html +++ /dev/null @@ -1,166 +0,0 @@ - - - - - secureValueErrorSelfie - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorSelfie

- -

Represents an issue with the selfie with a document. The error is considered resolved when the file with the selfie changes.

-

- -
-
secureValueErrorSelfie#e537ced6 type:SecureValueType file_hash:bytes text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeOne of secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport
file_hashbytesFile hash
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypePassport

-

Passport

-

secureValueTypeDriverLicense

-

Driver's license

-

secureValueTypeIdentityCard

-

Identity card

-

secureValueTypeInternalPassport

-

Internal passport

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueErrorTranslationFile.html b/data/core.telegram.org/constructor/secureValueErrorTranslationFile.html deleted file mode 100644 index 19f9424f76..0000000000 --- a/data/core.telegram.org/constructor/secureValueErrorTranslationFile.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - secureValueErrorTranslationFile - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorTranslationFile

- -

Represents an issue with one of the files that constitute the translation of a document. The error is considered resolved when the file changes.

-

- -
-
secureValueErrorTranslationFile#a1144770 type:SecureValueType file_hash:bytes text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeOne of secureValueTypePersonalDetails, secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport, secureValueTypeUtilityBill, secureValueTypeBankStatement, secureValueTypeRentalAgreement, secureValueTypePassportRegistration, secureValueTypeTemporaryRegistration
file_hashbytesFile hash
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypePersonalDetails

-

Personal details

-

secureValueTypePassport

-

Passport

-

secureValueTypeDriverLicense

-

Driver's license

-

secureValueTypeIdentityCard

-

Identity card

-

secureValueTypeInternalPassport

-

Internal passport

-

secureValueTypeUtilityBill

-

Utility bill

-

secureValueTypeBankStatement

-

Bank statement

-

secureValueTypeRentalAgreement

-

Rental agreement

-

secureValueTypePassportRegistration

-

Internal registration passport

-

secureValueTypeTemporaryRegistration

-

Temporary registration

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueErrorTranslationFiles.html b/data/core.telegram.org/constructor/secureValueErrorTranslationFiles.html deleted file mode 100644 index 505f9f2db6..0000000000 --- a/data/core.telegram.org/constructor/secureValueErrorTranslationFiles.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - secureValueErrorTranslationFiles - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorTranslationFiles

- -

Represents an issue with the translated version of a document. The error is considered resolved when a file with the document translation changes.

-

- -
-
secureValueErrorTranslationFiles#34636dd8 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeOne of secureValueTypePersonalDetails, secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport, secureValueTypeUtilityBill, secureValueTypeBankStatement, secureValueTypeRentalAgreement, secureValueTypePassportRegistration, secureValueTypeTemporaryRegistration
file_hashVector<bytes>Hash
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypePersonalDetails

-

Personal details

-

secureValueTypePassport

-

Passport

-

secureValueTypeDriverLicense

-

Driver's license

-

secureValueTypeIdentityCard

-

Identity card

-

secureValueTypeInternalPassport

-

Internal passport

-

secureValueTypeUtilityBill

-

Utility bill

-

secureValueTypeBankStatement

-

Bank statement

-

secureValueTypeRentalAgreement

-

Rental agreement

-

secureValueTypePassportRegistration

-

Internal registration passport

-

secureValueTypeTemporaryRegistration

-

Temporary registration

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypeAddress.html b/data/core.telegram.org/constructor/secureValueTypeAddress.html deleted file mode 100644 index d83a0b1593..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypeAddress.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeAddress - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypeAddress

- -

Address

-

- -
-
secureValueTypeAddress#cbe31e26 = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypeBankStatement.html b/data/core.telegram.org/constructor/secureValueTypeBankStatement.html deleted file mode 100644 index e0f1d7f738..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypeBankStatement.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeBankStatement - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypeBankStatement

- -

Bank statement

-

- -
-
secureValueTypeBankStatement#89137c0d = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypeDriverLicense.html b/data/core.telegram.org/constructor/secureValueTypeDriverLicense.html deleted file mode 100644 index 247d4461ec..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypeDriverLicense.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeDriverLicense - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypeDriverLicense

- -

Driver's license

-

- -
-
secureValueTypeDriverLicense#6e425c4 = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypeEmail.html b/data/core.telegram.org/constructor/secureValueTypeEmail.html deleted file mode 100644 index fa245300e0..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypeEmail.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeEmail - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypeEmail

- -

Email

-

- -
-
secureValueTypeEmail#8e3ca7ee = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypeIdentityCard.html b/data/core.telegram.org/constructor/secureValueTypeIdentityCard.html deleted file mode 100644 index 7e03c3b718..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypeIdentityCard.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeIdentityCard - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypeIdentityCard

- -

Identity card

-

- -
-
secureValueTypeIdentityCard#a0d0744b = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypeInternalPassport.html b/data/core.telegram.org/constructor/secureValueTypeInternalPassport.html deleted file mode 100644 index 36058bd81f..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypeInternalPassport.html +++ /dev/null @@ -1,134 +0,0 @@ - - - - - secureValueTypeInternalPassport - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypeInternalPassport

- -

Internal passport

-

- -
-
secureValueTypeInternalPassport#99a48f23 = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypePassport.html b/data/core.telegram.org/constructor/secureValueTypePassport.html deleted file mode 100644 index 17fa521cab..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypePassport.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypePassport - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypePassport

- -

Passport

-

- -
-
secureValueTypePassport#3dac6a00 = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypePassportRegistration.html b/data/core.telegram.org/constructor/secureValueTypePassportRegistration.html deleted file mode 100644 index 32b8dada30..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypePassportRegistration.html +++ /dev/null @@ -1,134 +0,0 @@ - - - - - secureValueTypePassportRegistration - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypePassportRegistration

- -

Internal registration passport

-

- -
-
secureValueTypePassportRegistration#99e3806a = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypePersonalDetails.html b/data/core.telegram.org/constructor/secureValueTypePersonalDetails.html deleted file mode 100644 index 6d091d2b8c..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypePersonalDetails.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypePersonalDetails - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypePersonalDetails

- -

Personal details

-

- -
-
secureValueTypePersonalDetails#9d2a81e3 = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypePhone.html b/data/core.telegram.org/constructor/secureValueTypePhone.html deleted file mode 100644 index 4c31fad60b..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypePhone.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypePhone - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypePhone

- -

Phone

-

- -
-
secureValueTypePhone#b320aadb = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypeRentalAgreement.html b/data/core.telegram.org/constructor/secureValueTypeRentalAgreement.html deleted file mode 100644 index 2e375b1061..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypeRentalAgreement.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeRentalAgreement - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypeRentalAgreement

- -

Rental agreement

-

- -
-
secureValueTypeRentalAgreement#8b883488 = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypeTemporaryRegistration.html b/data/core.telegram.org/constructor/secureValueTypeTemporaryRegistration.html deleted file mode 100644 index 7312f9e65f..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypeTemporaryRegistration.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeTemporaryRegistration - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypeTemporaryRegistration

- -

Temporary registration

-

- -
-
secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/secureValueTypeUtilityBill.html b/data/core.telegram.org/constructor/secureValueTypeUtilityBill.html deleted file mode 100644 index bbbb3ea296..0000000000 --- a/data/core.telegram.org/constructor/secureValueTypeUtilityBill.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeUtilityBill - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypeUtilityBill

- -

Utility bill

-

- -
-
secureValueTypeUtilityBill#fc36954e = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageCancelAction.html b/data/core.telegram.org/constructor/sendMessageCancelAction.html deleted file mode 100644 index 0a02c7e36b..0000000000 --- a/data/core.telegram.org/constructor/sendMessageCancelAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageCancelAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageCancelAction

- -

Invalidate all previous action updates. E.g. when user deletes entered text or aborts a video upload.

-

- -
-
sendMessageCancelAction#fd5ec8f5 = SendMessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageChooseContactAction.html b/data/core.telegram.org/constructor/sendMessageChooseContactAction.html deleted file mode 100644 index 43986989ce..0000000000 --- a/data/core.telegram.org/constructor/sendMessageChooseContactAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageChooseContactAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageChooseContactAction

- -

User is selecting a contact to share.

-

- -
-
sendMessageChooseContactAction#628cbc6f = SendMessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageChooseStickerAction.html b/data/core.telegram.org/constructor/sendMessageChooseStickerAction.html deleted file mode 100644 index 097f269723..0000000000 --- a/data/core.telegram.org/constructor/sendMessageChooseStickerAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageChooseStickerAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageChooseStickerAction

- -

User is choosing a sticker

-

- -
-
sendMessageChooseStickerAction#b05ac6b1 = SendMessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageEmojiInteractionSeen.html b/data/core.telegram.org/constructor/sendMessageEmojiInteractionSeen.html deleted file mode 100644 index 75c5141b80..0000000000 --- a/data/core.telegram.org/constructor/sendMessageEmojiInteractionSeen.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - sendMessageEmojiInteractionSeen - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageEmojiInteractionSeen

- -

User is watching an animated emoji reaction triggered by another user, click here for more info ».

-

- -
-
sendMessageEmojiInteractionSeen#b665902e emoticon:string = SendMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
emoticonstringEmoji
-

Type

-

SendMessageAction

-

Related pages

-

Animated Emojis

-

Graphical telegram clients should transform emojis into their respective animated version.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageGamePlayAction.html b/data/core.telegram.org/constructor/sendMessageGamePlayAction.html deleted file mode 100644 index 1528d72a25..0000000000 --- a/data/core.telegram.org/constructor/sendMessageGamePlayAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageGamePlayAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageGamePlayAction

- -

User is playing a game

-

- -
-
sendMessageGamePlayAction#dd6a8f48 = SendMessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageGeoLocationAction.html b/data/core.telegram.org/constructor/sendMessageGeoLocationAction.html deleted file mode 100644 index 452f169866..0000000000 --- a/data/core.telegram.org/constructor/sendMessageGeoLocationAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageGeoLocationAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageGeoLocationAction

- -

User is selecting a location to share.

-

- -
-
sendMessageGeoLocationAction#176f8ba1 = SendMessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageHistoryImportAction.html b/data/core.telegram.org/constructor/sendMessageHistoryImportAction.html deleted file mode 100644 index 8dbec2bee6..0000000000 --- a/data/core.telegram.org/constructor/sendMessageHistoryImportAction.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - sendMessageHistoryImportAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageHistoryImportAction

- -

Chat history is being imported

-

- -
-
sendMessageHistoryImportAction#dbda9246 progress:int = SendMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
progressintProgress percentage
-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageRecordAudioAction.html b/data/core.telegram.org/constructor/sendMessageRecordAudioAction.html deleted file mode 100644 index 7203f42405..0000000000 --- a/data/core.telegram.org/constructor/sendMessageRecordAudioAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageRecordAudioAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageRecordAudioAction

- -

User is recording a voice message.

-

- -
-
sendMessageRecordAudioAction#d52f73f7 = SendMessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageRecordRoundAction.html b/data/core.telegram.org/constructor/sendMessageRecordRoundAction.html deleted file mode 100644 index 68b47b4573..0000000000 --- a/data/core.telegram.org/constructor/sendMessageRecordRoundAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageRecordRoundAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageRecordRoundAction

- -

User is recording a round video to share

-

- -
-
sendMessageRecordRoundAction#88f27fbc = SendMessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageRecordVideoAction.html b/data/core.telegram.org/constructor/sendMessageRecordVideoAction.html deleted file mode 100644 index 8b3dcd0cdc..0000000000 --- a/data/core.telegram.org/constructor/sendMessageRecordVideoAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageRecordVideoAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageRecordVideoAction

- -

User is recording a video.

-

- -
-
sendMessageRecordVideoAction#a187d66f = SendMessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageTypingAction.html b/data/core.telegram.org/constructor/sendMessageTypingAction.html deleted file mode 100644 index c6aa231f99..0000000000 --- a/data/core.telegram.org/constructor/sendMessageTypingAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageTypingAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageTypingAction

- -

User is typing.

-

- -
-
sendMessageTypingAction#16bf744e = SendMessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageUploadAudioAction.html b/data/core.telegram.org/constructor/sendMessageUploadAudioAction.html deleted file mode 100644 index 2c16728bae..0000000000 --- a/data/core.telegram.org/constructor/sendMessageUploadAudioAction.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - sendMessageUploadAudioAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageUploadAudioAction

- -

User is uploading a voice message.

-

- -
-
sendMessageUploadAudioAction#f351d7ab progress:int = SendMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
progressintProgress percentage
-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageUploadDocumentAction.html b/data/core.telegram.org/constructor/sendMessageUploadDocumentAction.html deleted file mode 100644 index e94884cbeb..0000000000 --- a/data/core.telegram.org/constructor/sendMessageUploadDocumentAction.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - sendMessageUploadDocumentAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageUploadDocumentAction

- -

User is uploading a file.

-

- -
-
sendMessageUploadDocumentAction#aa0cd9e4 progress:int = SendMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
progressintProgress percentage
-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageUploadRoundAction.html b/data/core.telegram.org/constructor/sendMessageUploadRoundAction.html deleted file mode 100644 index 646a82f427..0000000000 --- a/data/core.telegram.org/constructor/sendMessageUploadRoundAction.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - sendMessageUploadRoundAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageUploadRoundAction

- -

User is uploading a round video

-

- -
-
sendMessageUploadRoundAction#243e1c66 progress:int = SendMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
progressintProgress percentage
-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sendMessageUploadVideoAction.html b/data/core.telegram.org/constructor/sendMessageUploadVideoAction.html deleted file mode 100644 index a27269a0f4..0000000000 --- a/data/core.telegram.org/constructor/sendMessageUploadVideoAction.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - sendMessageUploadVideoAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageUploadVideoAction

- -

User is uploading a video.

-

- -
-
sendMessageUploadVideoAction#e9763aec progress:int = SendMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
progressintProgress percentage
-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/shippingOption.html b/data/core.telegram.org/constructor/shippingOption.html deleted file mode 100644 index 1883b6a596..0000000000 --- a/data/core.telegram.org/constructor/shippingOption.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - shippingOption - - - - - - - - - - - - - -
- -
-
-
- -

shippingOption

- -

Shipping option

-

- -
-
shippingOption#b6213cdf id:string title:string prices:Vector<LabeledPrice> = ShippingOption;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idstringOption ID
titlestringTitle
pricesVector<LabeledPrice>List of price portions
-

Type

-

ShippingOption

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/speakingInGroupCallAction.html b/data/core.telegram.org/constructor/speakingInGroupCallAction.html deleted file mode 100644 index a9bb9ca4c0..0000000000 --- a/data/core.telegram.org/constructor/speakingInGroupCallAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - speakingInGroupCallAction - - - - - - - - - - - - - -
- -
-
-
- -

speakingInGroupCallAction

- -

User is currently speaking in the group call

-

- -
-
speakingInGroupCallAction#d92c2285 = SendMessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/sponsoredMessage.html b/data/core.telegram.org/constructor/sponsoredMessage.html deleted file mode 100644 index ec0c80c006..0000000000 --- a/data/core.telegram.org/constructor/sponsoredMessage.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - sponsoredMessage - - - - - - - - - - - - - -
- -
-
-
- -

sponsoredMessage

- -

A sponsored message.

-

- -
-
sponsoredMessage#2a3c381f flags:# random_id:bytes from_id:Peer start_param:flags.0?string message:string entities:flags.1?Vector<MessageEntity> = SponsoredMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
random_idbytesMessage ID
from_idPeerID of the sender of the message
start_paramflags.0?stringParameter for the bot start message if the sponsored chat is a chat with a bot.
messagestringSponsored message
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
-

Type

-

SponsoredMessage

-

Related pages

-

Sponsored messages

-

How to implement sponsored messages

-

Styled text with message entities

-

How to create styled text with message entities

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/stats.broadcastStats b/data/core.telegram.org/constructor/stats.broadcastStats deleted file mode 100644 index 39abf285e6..0000000000 --- a/data/core.telegram.org/constructor/stats.broadcastStats +++ /dev/null @@ -1,220 +0,0 @@ - - - - - stats.broadcastStats - - - - - - - - - - - - - -
- -
-
-
- -

stats.broadcastStats

- -

Channel statistics.

-

- -
-
stats.broadcastStats#bdf78394 period:StatsDateRangeDays followers:StatsAbsValueAndPrev views_per_post:StatsAbsValueAndPrev shares_per_post:StatsAbsValueAndPrev enabled_notifications:StatsPercentValue growth_graph:StatsGraph followers_graph:StatsGraph mute_graph:StatsGraph top_hours_graph:StatsGraph interactions_graph:StatsGraph iv_interactions_graph:StatsGraph views_by_source_graph:StatsGraph new_followers_by_source_graph:StatsGraph languages_graph:StatsGraph recent_message_interactions:Vector<MessageInteractionCounters> = stats.BroadcastStats;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
periodStatsDateRangeDaysPeriod in consideration
followersStatsAbsValueAndPrevFollower count change for period in consideration
views_per_postStatsAbsValueAndPrevtotal_viewcount/postcount, for posts posted during the period in consideration (views_per_post).
Note that in this case, current refers to the period in consideration (min_date till max_date), and prev refers to the previous period ((min_date - (max_date - min_date)) till min_date).
shares_per_postStatsAbsValueAndPrevtotal_viewcount/postcount, for posts posted during the period in consideration (views_per_post).
Note that in this case, current refers to the period in consideration (min_date till max_date), and prev refers to the previous period ((min_date - (max_date - min_date)) till min_date)
enabled_notificationsStatsPercentValuePercentage of subscribers with enabled notifications
growth_graphStatsGraphChannel growth graph (absolute subscriber count)
followers_graphStatsGraphFollowers growth graph (relative subscriber count)
mute_graphStatsGraphMuted users graph (relative)
top_hours_graphStatsGraphViews per hour graph (absolute)
interactions_graphStatsGraphInteractions graph (absolute)
iv_interactions_graphStatsGraphIV interactions graph (absolute)
views_by_source_graphStatsGraphViews by source graph (absolute)
new_followers_by_source_graphStatsGraphNew followers by source graph (absolute)
languages_graphStatsGraphSubscriber language graph (piechart)
recent_message_interactionsVector<MessageInteractionCounters>Recent message interactions
-

Type

-

stats.BroadcastStats

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/stats.megagroupStats b/data/core.telegram.org/constructor/stats.megagroupStats deleted file mode 100644 index dcc826e2cc..0000000000 --- a/data/core.telegram.org/constructor/stats.megagroupStats +++ /dev/null @@ -1,230 +0,0 @@ - - - - - stats.megagroupStats - - - - - - - - - - - - - -
- -
-
-
- -

stats.megagroupStats

- -

Supergroup statistics

-

- -
-
stats.megagroupStats#ef7ff916 period:StatsDateRangeDays members:StatsAbsValueAndPrev messages:StatsAbsValueAndPrev viewers:StatsAbsValueAndPrev posters:StatsAbsValueAndPrev growth_graph:StatsGraph members_graph:StatsGraph new_members_by_source_graph:StatsGraph languages_graph:StatsGraph messages_graph:StatsGraph actions_graph:StatsGraph top_hours_graph:StatsGraph weekdays_graph:StatsGraph top_posters:Vector<StatsGroupTopPoster> top_admins:Vector<StatsGroupTopAdmin> top_inviters:Vector<StatsGroupTopInviter> users:Vector<User> = stats.MegagroupStats;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
periodStatsDateRangeDaysPeriod in consideration
membersStatsAbsValueAndPrevMember count change for period in consideration
messagesStatsAbsValueAndPrevMessage number change for period in consideration
viewersStatsAbsValueAndPrevNumber of users that viewed messages, for range in consideration
postersStatsAbsValueAndPrevNumber of users that posted messages, for range in consideration
growth_graphStatsGraphSupergroup growth graph (absolute subscriber count)
members_graphStatsGraphMembers growth (relative subscriber count)
new_members_by_source_graphStatsGraphNew members by source graph
languages_graphStatsGraphSubscriber language graph (piechart)
messages_graphStatsGraphMessage activity graph (stacked bar graph, message type)
actions_graphStatsGraphGroup activity graph (deleted, modified messages, blocked users)
top_hours_graphStatsGraphActivity per hour graph (absolute)
weekdays_graphStatsGraphActivity per day of week graph (absolute)
top_postersVector<StatsGroupTopPoster>Info about most active group members
top_adminsVector<StatsGroupTopAdmin>Info about most active group admins
top_invitersVector<StatsGroupTopInviter>Info about most active group inviters
usersVector<User>Info about users mentioned in statistics
-

Type

-

stats.MegagroupStats

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/stats.messageStats b/data/core.telegram.org/constructor/stats.messageStats deleted file mode 100644 index 045190b0ff..0000000000 --- a/data/core.telegram.org/constructor/stats.messageStats +++ /dev/null @@ -1,147 +0,0 @@ - - - - - stats.messageStats - - - - - - - - - - - - - -
- -
-
-
- -

stats.messageStats

- -

Message statistics

-

- -
-
stats.messageStats#8999f295 views_graph:StatsGraph = stats.MessageStats;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
views_graphStatsGraphMessage view graph
-

Type

-

stats.MessageStats

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/statsAbsValueAndPrev.html b/data/core.telegram.org/constructor/statsAbsValueAndPrev.html deleted file mode 100644 index f0dfb13108..0000000000 --- a/data/core.telegram.org/constructor/statsAbsValueAndPrev.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - statsAbsValueAndPrev - - - - - - - - - - - - - -
- -
-
-
- -

statsAbsValueAndPrev

- -

Statistics value couple; initial and final value for period of time currently in consideration

-

- -
-
statsAbsValueAndPrev#cb43acde current:double previous:double = StatsAbsValueAndPrev;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
currentdoubleCurrent value
previousdoublePrevious value
-

Type

-

StatsAbsValueAndPrev

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/statsDateRangeDays.html b/data/core.telegram.org/constructor/statsDateRangeDays.html deleted file mode 100644 index b5a605ab1c..0000000000 --- a/data/core.telegram.org/constructor/statsDateRangeDays.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - statsDateRangeDays - - - - - - - - - - - - - -
- -
-
-
- -

statsDateRangeDays

- -

Channel statistics date range

-

- -
-
statsDateRangeDays#b637edaf min_date:int max_date:int = StatsDateRangeDays;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
min_dateintInitial date
max_dateintFinal date
-

Type

-

StatsDateRangeDays

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/statsGraph.html b/data/core.telegram.org/constructor/statsGraph.html deleted file mode 100644 index 59cd41cf93..0000000000 --- a/data/core.telegram.org/constructor/statsGraph.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - statsGraph - - - - - - - - - - - - - -
- -
-
-
- -

statsGraph

- -

Channel statistics graph

-

- -
-
statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
jsonDataJSONStatistics data
zoom_tokenflags.0?stringZoom token
-

Type

-

StatsGraph

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/statsGraphAsync.html b/data/core.telegram.org/constructor/statsGraphAsync.html deleted file mode 100644 index af13962104..0000000000 --- a/data/core.telegram.org/constructor/statsGraphAsync.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - statsGraphAsync - - - - - - - - - - - - - -
- -
-
-
- -

statsGraphAsync

- -

This channel statistics graph must be generated asynchronously using stats.loadAsyncGraph to reduce server load

-

- -
-
statsGraphAsync#4a27eb2d token:string = StatsGraph;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
tokenstringToken to use for fetching the async graph
-

Type

-

StatsGraph

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

-

stats.loadAsyncGraph

-

Load channel statistics graph asynchronously

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/statsGraphError.html b/data/core.telegram.org/constructor/statsGraphError.html deleted file mode 100644 index 1dc902e539..0000000000 --- a/data/core.telegram.org/constructor/statsGraphError.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - statsGraphError - - - - - - - - - - - - - -
- -
-
-
- -

statsGraphError

- -

An error occurred while generating the statistics graph

-

- -
-
statsGraphError#bedc9822 error:string = StatsGraph;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
errorstringThe error
-

Type

-

StatsGraph

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/statsGroupTopAdmin.html b/data/core.telegram.org/constructor/statsGroupTopAdmin.html deleted file mode 100644 index 479ff8cd4c..0000000000 --- a/data/core.telegram.org/constructor/statsGroupTopAdmin.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - statsGroupTopAdmin - - - - - - - - - - - - - -
- -
-
-
- -

statsGroupTopAdmin

- -

Information about an active admin in a supergroup

-

- -
-
statsGroupTopAdmin#d7584c87 user_id:long deleted:int kicked:int banned:int = StatsGroupTopAdmin;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser ID
deletedintNumber of deleted messages for statistics period in consideration
kickedintNumber of kicked users for statistics period in consideration
bannedintNumber of banned users for statistics period in consideration
-

Type

-

StatsGroupTopAdmin

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/statsGroupTopInviter.html b/data/core.telegram.org/constructor/statsGroupTopInviter.html deleted file mode 100644 index f007061d0e..0000000000 --- a/data/core.telegram.org/constructor/statsGroupTopInviter.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - statsGroupTopInviter - - - - - - - - - - - - - -
- -
-
-
- -

statsGroupTopInviter

- -

Information about an active supergroup inviter

-

- -
-
statsGroupTopInviter#535f779d user_id:long invitations:int = StatsGroupTopInviter;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser ID
invitationsintNumber of invitations for statistics period in consideration
-

Type

-

StatsGroupTopInviter

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/statsPercentValue.html b/data/core.telegram.org/constructor/statsPercentValue.html deleted file mode 100644 index 2cb40ffd2b..0000000000 --- a/data/core.telegram.org/constructor/statsPercentValue.html +++ /dev/null @@ -1,156 +0,0 @@ - - - - - statsPercentValue - - - - - - - - - - - - - -
- -
-
-
- -

statsPercentValue

- -

Channel statistics percentage.
-Compute the percentage simply by doing part * total / 100

-

- -
-
statsPercentValue#cbce2fe0 part:double total:double = StatsPercentValue;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
partdoublePartial value
totaldoubleTotal value
-

Type

-

StatsPercentValue

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/statsURL.html b/data/core.telegram.org/constructor/statsURL.html deleted file mode 100644 index 896601ca9f..0000000000 --- a/data/core.telegram.org/constructor/statsURL.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - statsURL - - - - - - - - - - - - - -
- -
-
-
- -

statsURL

- -

URL with chat statistics

-

- -
-
statsURL#47a971e0 url:string = StatsURL;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
urlstringChat statistics
-

Type

-

StatsURL

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/stickerPack.html b/data/core.telegram.org/constructor/stickerPack.html deleted file mode 100644 index 9b6858a67d..0000000000 --- a/data/core.telegram.org/constructor/stickerPack.html +++ /dev/null @@ -1,156 +0,0 @@ - - - - - stickerPack - - - - - - - - - - - - - -
- -
-
-
- -

stickerPack

- -

A stickerpack is a group of stickers associated to the same emoji.
-It is not a sticker pack the way it is usually intended, you may be looking for a StickerSet.

-

- -
-
stickerPack#12b299d4 emoticon:string documents:Vector<long> = StickerPack;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
emoticonstringEmoji
documentsVector<long>Stickers
-

Type

-

StickerPack

-

Related pages

-

StickerSet

-

Represents a stickerset (stickerpack)

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/stickerSet.html b/data/core.telegram.org/constructor/stickerSet.html deleted file mode 100644 index df7e9e3c08..0000000000 --- a/data/core.telegram.org/constructor/stickerSet.html +++ /dev/null @@ -1,217 +0,0 @@ - - - - - stickerSet - - - - - - - - - - - - - -
- -
-
-
- -

stickerSet

- -

Represents a stickerset (stickerpack)

-

- -
-
stickerSet#d7df217a flags:# archived:flags.1?true official:flags.2?true masks:flags.3?true animated:flags.5?true videos:flags.6?true installed_date:flags.0?int id:long access_hash:long title:string short_name:string thumbs:flags.4?Vector<PhotoSize> thumb_dc_id:flags.4?int thumb_version:flags.4?int count:int hash:int = StickerSet;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
archivedflags.1?trueWhether this stickerset was archived (due to too many saved stickers in the current account)
officialflags.2?trueIs this stickerset official
masksflags.3?trueIs this a mask stickerset
animatedflags.5?trueIs this an animated stickerpack
installed_dateflags.0?intWhen was this stickerset installed
idlongID of the stickerset
access_hashlongAccess hash of stickerset
titlestringTitle of stickerset
short_namestringShort name of stickerset to use in tg://addstickers?set=short_name
thumbsflags.4?Vector<PhotoSize>Stickerset thumbnail
thumb_dc_idflags.4?intDC ID of thumbnail
thumb_versionflags.4?intThumbnail version
countintNumber of stickers in pack
hashintHash
-

Type

-

StickerSet

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/stickerSetCovered.html b/data/core.telegram.org/constructor/stickerSetCovered.html deleted file mode 100644 index c89e76f518..0000000000 --- a/data/core.telegram.org/constructor/stickerSetCovered.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - stickerSetCovered - - - - - - - - - - - - - -
- -
-
-
- -

stickerSetCovered

- -

Stickerset, with a specific sticker as preview

-

- -
-
stickerSetCovered#6410a5d2 set:StickerSet cover:Document = StickerSetCovered;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
setStickerSetStickerset
coverDocumentPreview
-

Type

-

StickerSetCovered

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/stickerSetMultiCovered.html b/data/core.telegram.org/constructor/stickerSetMultiCovered.html deleted file mode 100644 index a422f91723..0000000000 --- a/data/core.telegram.org/constructor/stickerSetMultiCovered.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - stickerSetMultiCovered - - - - - - - - - - - - - -
- -
-
-
- -

stickerSetMultiCovered

- -

Stickerset, with a specific stickers as preview

-

- -
-
stickerSetMultiCovered#3407e51b set:StickerSet covers:Vector<Document> = StickerSetCovered;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
setStickerSetStickerset
coversVector<Document>Preview stickers
-

Type

-

StickerSetCovered

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/stickers.suggestedShortName b/data/core.telegram.org/constructor/stickers.suggestedShortName deleted file mode 100644 index 536386d55e..0000000000 --- a/data/core.telegram.org/constructor/stickers.suggestedShortName +++ /dev/null @@ -1,147 +0,0 @@ - - - - - stickers.suggestedShortName - - - - - - - - - - - - - -
- -
-
-
- -

stickers.suggestedShortName

- -

A suggested short name for a stickerpack

-

- -
-
stickers.suggestedShortName#85fea03f short_name:string = stickers.SuggestedShortName;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
short_namestringSuggested short name
-

Type

-

stickers.SuggestedShortName

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/storage.fileGif b/data/core.telegram.org/constructor/storage.fileGif deleted file mode 100644 index 276e955acf..0000000000 --- a/data/core.telegram.org/constructor/storage.fileGif +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.fileGif - - - - - - - - - - - - - -
- -
-
-
- -

storage.fileGif

- -

GIF image. MIME type: image/gif.

-

- -
-
storage.fileGif#cae1aadf = storage.FileType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

storage.FileType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/storage.fileJpeg b/data/core.telegram.org/constructor/storage.fileJpeg deleted file mode 100644 index fa1545b29c..0000000000 --- a/data/core.telegram.org/constructor/storage.fileJpeg +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.fileJpeg - - - - - - - - - - - - - -
- -
-
-
- -

storage.fileJpeg

- -

JPEG image. MIME type: image/jpeg.

-

- -
-
storage.fileJpeg#7efe0e = storage.FileType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

storage.FileType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/storage.fileMov b/data/core.telegram.org/constructor/storage.fileMov deleted file mode 100644 index b6c2a8a2c9..0000000000 --- a/data/core.telegram.org/constructor/storage.fileMov +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.fileMov - - - - - - - - - - - - - -
- -
-
-
- -

storage.fileMov

- -

Quicktime video. MIME type: video/quicktime.

-

- -
-
storage.fileMov#4b09ebbc = storage.FileType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

storage.FileType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/storage.fileMp3 b/data/core.telegram.org/constructor/storage.fileMp3 deleted file mode 100644 index e3b2e9ab90..0000000000 --- a/data/core.telegram.org/constructor/storage.fileMp3 +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.fileMp3 - - - - - - - - - - - - - -
- -
-
-
- -

storage.fileMp3

- -

Mp3 audio. MIME type: audio/mpeg.

-

- -
-
storage.fileMp3#528a0677 = storage.FileType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

storage.FileType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/storage.fileMp4 b/data/core.telegram.org/constructor/storage.fileMp4 deleted file mode 100644 index f318e4e8dc..0000000000 --- a/data/core.telegram.org/constructor/storage.fileMp4 +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.fileMp4 - - - - - - - - - - - - - -
- -
-
-
- -

storage.fileMp4

- -

MPEG-4 video. MIME type: video/mp4.

-

- -
-
storage.fileMp4#b3cea0e4 = storage.FileType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

storage.FileType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/storage.filePartial b/data/core.telegram.org/constructor/storage.filePartial deleted file mode 100644 index 871ba727db..0000000000 --- a/data/core.telegram.org/constructor/storage.filePartial +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.filePartial - - - - - - - - - - - - - -
- -
-
-
- -

storage.filePartial

- -

Part of a bigger file.

-

- -
-
storage.filePartial#40bc6f52 = storage.FileType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

storage.FileType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/storage.filePdf b/data/core.telegram.org/constructor/storage.filePdf deleted file mode 100644 index 4683010343..0000000000 --- a/data/core.telegram.org/constructor/storage.filePdf +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.filePdf - - - - - - - - - - - - - -
- -
-
-
- -

storage.filePdf

- -

PDF document image. MIME type: application/pdf.

-

- -
-
storage.filePdf#ae1e508d = storage.FileType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

storage.FileType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/storage.filePng b/data/core.telegram.org/constructor/storage.filePng deleted file mode 100644 index 0dc8cecafb..0000000000 --- a/data/core.telegram.org/constructor/storage.filePng +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.filePng - - - - - - - - - - - - - -
- -
-
-
- -

storage.filePng

- -

PNG image. MIME type: image/png.

-

- -
-
storage.filePng#a4f63c0 = storage.FileType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

storage.FileType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/storage.fileUnknown b/data/core.telegram.org/constructor/storage.fileUnknown deleted file mode 100644 index 64ec949ae3..0000000000 --- a/data/core.telegram.org/constructor/storage.fileUnknown +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.fileUnknown - - - - - - - - - - - - - -
- -
-
-
- -

storage.fileUnknown

- -

Unknown type.

-

- -
-
storage.fileUnknown#aa963b05 = storage.FileType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

storage.FileType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/storage.fileWebp b/data/core.telegram.org/constructor/storage.fileWebp deleted file mode 100644 index faca63bb5c..0000000000 --- a/data/core.telegram.org/constructor/storage.fileWebp +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.fileWebp - - - - - - - - - - - - - -
- -
-
-
- -

storage.fileWebp

- -

WEBP image. MIME type: image/webp.

-

- -
-
storage.fileWebp#1081464c = storage.FileType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

storage.FileType

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/textAnchor.html b/data/core.telegram.org/constructor/textAnchor.html deleted file mode 100644 index 08b2472a50..0000000000 --- a/data/core.telegram.org/constructor/textAnchor.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - textAnchor - - - - - - - - - - - - - -
- -
-
-
- -

textAnchor

- -

Text linking to another section of the page

-

- -
-
textAnchor#35553762 text:RichText name:string = RichText;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
namestringSection name
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/textBold.html b/data/core.telegram.org/constructor/textBold.html deleted file mode 100644 index 1295f8fe80..0000000000 --- a/data/core.telegram.org/constructor/textBold.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textBold - - - - - - - - - - - - - -
- -
-
-
- -

textBold

- -

Bold text

-

- -
-
textBold#6724abc4 text:RichText = RichText;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/textConcat.html b/data/core.telegram.org/constructor/textConcat.html deleted file mode 100644 index 3f8c30fd65..0000000000 --- a/data/core.telegram.org/constructor/textConcat.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textConcat - - - - - - - - - - - - - -
- -
-
-
- -

textConcat

- -

Concatenation of rich texts

-

- -
-
textConcat#7e6260d7 texts:Vector<RichText> = RichText;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textsVector<RichText>Concatenated rich texts
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/textEmail.html b/data/core.telegram.org/constructor/textEmail.html deleted file mode 100644 index a93efc09fa..0000000000 --- a/data/core.telegram.org/constructor/textEmail.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - textEmail - - - - - - - - - - - - - -
- -
-
-
- -

textEmail

- -

Rich text email link

-

- -
-
textEmail#de5a0dd6 text:RichText email:string = RichText;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextLink text
emailstringEmail address
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/textEmpty.html b/data/core.telegram.org/constructor/textEmpty.html deleted file mode 100644 index 3969e47115..0000000000 --- a/data/core.telegram.org/constructor/textEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - textEmpty - - - - - - - - - - - - - -
- -
-
-
- -

textEmpty

- -

Empty rich text element

-

- -
-
textEmpty#dc3d824f = RichText;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/textFixed.html b/data/core.telegram.org/constructor/textFixed.html deleted file mode 100644 index 10ad7c895b..0000000000 --- a/data/core.telegram.org/constructor/textFixed.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textFixed - - - - - - - - - - - - - -
- -
-
-
- -

textFixed

- -

fixed-width rich text

-

- -
-
textFixed#6c3f19b9 text:RichText = RichText;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/textImage.html b/data/core.telegram.org/constructor/textImage.html deleted file mode 100644 index d9745acea3..0000000000 --- a/data/core.telegram.org/constructor/textImage.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - textImage - - - - - - - - - - - - - -
- -
-
-
- -

textImage

- -

Inline image

-

- -
-
textImage#81ccf4f document_id:long w:int h:int = RichText;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
document_idlongDocument ID
wintWidth
hintHeight
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/textItalic.html b/data/core.telegram.org/constructor/textItalic.html deleted file mode 100644 index 3ca45eaf6a..0000000000 --- a/data/core.telegram.org/constructor/textItalic.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textItalic - - - - - - - - - - - - - -
- -
-
-
- -

textItalic

- -

Italic text

-

- -
-
textItalic#d912a59c text:RichText = RichText;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/textMarked.html b/data/core.telegram.org/constructor/textMarked.html deleted file mode 100644 index ffd36bf700..0000000000 --- a/data/core.telegram.org/constructor/textMarked.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textMarked - - - - - - - - - - - - - -
- -
-
-
- -

textMarked

- -

Highlighted text

-

- -
-
textMarked#34b8621 text:RichText = RichText;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/textStrike.html b/data/core.telegram.org/constructor/textStrike.html deleted file mode 100644 index e866d3cf63..0000000000 --- a/data/core.telegram.org/constructor/textStrike.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textStrike - - - - - - - - - - - - - -
- -
-
-
- -

textStrike

- -

Strikethrough text

-

- -
-
textStrike#9bf8bb95 text:RichText = RichText;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/textSubscript.html b/data/core.telegram.org/constructor/textSubscript.html deleted file mode 100644 index 9b2deb6e77..0000000000 --- a/data/core.telegram.org/constructor/textSubscript.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textSubscript - - - - - - - - - - - - - -
- -
-
-
- -

textSubscript

- -

Subscript text

-

- -
-
textSubscript#ed6a8504 text:RichText = RichText;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/textSuperscript.html b/data/core.telegram.org/constructor/textSuperscript.html deleted file mode 100644 index 2efa9771a5..0000000000 --- a/data/core.telegram.org/constructor/textSuperscript.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textSuperscript - - - - - - - - - - - - - -
- -
-
-
- -

textSuperscript

- -

Superscript text

-

- -
-
textSuperscript#c7fb5e01 text:RichText = RichText;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/textUnderline.html b/data/core.telegram.org/constructor/textUnderline.html deleted file mode 100644 index 3ad40497c0..0000000000 --- a/data/core.telegram.org/constructor/textUnderline.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textUnderline - - - - - - - - - - - - - -
- -
-
-
- -

textUnderline

- -

Underlined text

-

- -
-
textUnderline#c12622c4 text:RichText = RichText;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/textUrl.html b/data/core.telegram.org/constructor/textUrl.html deleted file mode 100644 index 8531b73455..0000000000 --- a/data/core.telegram.org/constructor/textUrl.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - textUrl - - - - - - - - - - - - - -
- -
-
-
- -

textUrl

- -

Link

-

- -
-
textUrl#3c2884c1 text:RichText url:string webpage_id:long = RichText;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText of link
urlstringWebpage HTTP URL
webpage_idlongIf a preview was already generated for the page, the page ID
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/theme.html b/data/core.telegram.org/constructor/theme.html deleted file mode 100644 index bde25e1c3d..0000000000 --- a/data/core.telegram.org/constructor/theme.html +++ /dev/null @@ -1,197 +0,0 @@ - - - - - theme - - - - - - - - - - - - - -
- -
-
-
- -

theme

- -

Theme

-

- -
-
theme#e802b8dc flags:# creator:flags.0?true default:flags.1?true for_chat:flags.5?true id:long access_hash:long slug:string title:string document:flags.2?Document settings:flags.3?ThemeSettings installs_count:flags.4?int = Theme;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
creatorflags.0?trueWhether the current user is the creator of this theme
defaultflags.1?trueWhether this is the default theme
for_chatflags.5?trueWhether this theme is meant to be used as a chat theme
idlongTheme ID
access_hashlongTheme access hash
slugstringUnique theme ID
titlestringTheme name
documentflags.2?DocumentTheme
settingsflags.3?ThemeSettingsTheme settings
installs_countflags.4?intInstallation count
-

Type

-

Theme

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/themeSettings.html b/data/core.telegram.org/constructor/themeSettings.html deleted file mode 100644 index c19f416a6b..0000000000 --- a/data/core.telegram.org/constructor/themeSettings.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - themeSettings - - - - - - - - - - - - - -
- -
-
-
- -

themeSettings

- -

Theme settings

-

- -
-
themeSettings#fa58b6d4 flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int outbox_accent_color:flags.3?int message_colors:flags.0?Vector<int> wallpaper:flags.1?WallPaper = ThemeSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
message_colors_animatedflags.2?trueIf set, the freeform gradient fill needs to be animated on every sent message.
base_themeBaseThemeBase theme
accent_colorintAccent color, ARGB format
outbox_accent_colorflags.3?intAccent color of outgoing messages in ARGB format
message_colorsflags.0?Vector<int>The fill to be used as a background for outgoing messages, in RGB24 format.
If just one or two equal colors are provided, describes a solid fill of a background.
If two different colors are provided, describes the top and bottom colors of a 0-degree gradient.
If three or four colors are provided, describes a freeform gradient fill of a background.
wallpaperflags.1?WallPaperWallpaper
-

Type

-

ThemeSettings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/topPeer.html b/data/core.telegram.org/constructor/topPeer.html deleted file mode 100644 index b43cdb82b5..0000000000 --- a/data/core.telegram.org/constructor/topPeer.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - topPeer - - - - - - - - - - - - - -
- -
-
-
- -

topPeer

- -

Top peer

-

- -
-
topPeer#edcdc05b peer:Peer rating:double = TopPeer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerPeer
ratingdoubleRating as computed in top peer rating »
-

Type

-

TopPeer

-

Related pages

-

Top peer rating

-

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/topPeerCategoryBotsInline.html b/data/core.telegram.org/constructor/topPeerCategoryBotsInline.html deleted file mode 100644 index a80f92f18d..0000000000 --- a/data/core.telegram.org/constructor/topPeerCategoryBotsInline.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryBotsInline - - - - - - - - - - - - - -
- -
-
-
- -

topPeerCategoryBotsInline

- -

Most used inline bots

-

- -
-
topPeerCategoryBotsInline#148677e2 = TopPeerCategory;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

TopPeerCategory

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/topPeerCategoryBotsPM.html b/data/core.telegram.org/constructor/topPeerCategoryBotsPM.html deleted file mode 100644 index 70cf994243..0000000000 --- a/data/core.telegram.org/constructor/topPeerCategoryBotsPM.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryBotsPM - - - - - - - - - - - - - -
- -
-
-
- -

topPeerCategoryBotsPM

- -

Most used bots

-

- -
-
topPeerCategoryBotsPM#ab661b5b = TopPeerCategory;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

TopPeerCategory

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/topPeerCategoryChannels.html b/data/core.telegram.org/constructor/topPeerCategoryChannels.html deleted file mode 100644 index 697e9e4ced..0000000000 --- a/data/core.telegram.org/constructor/topPeerCategoryChannels.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryChannels - - - - - - - - - - - - - -
- -
-
-
- -

topPeerCategoryChannels

- -

Most frequently visited channels

-

- -
-
topPeerCategoryChannels#161d9628 = TopPeerCategory;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

TopPeerCategory

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/topPeerCategoryCorrespondents.html b/data/core.telegram.org/constructor/topPeerCategoryCorrespondents.html deleted file mode 100644 index 426095f2a6..0000000000 --- a/data/core.telegram.org/constructor/topPeerCategoryCorrespondents.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryCorrespondents - - - - - - - - - - - - - -
- -
-
-
- -

topPeerCategoryCorrespondents

- -

Users we've chatted most frequently with

-

- -
-
topPeerCategoryCorrespondents#637b7ed = TopPeerCategory;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

TopPeerCategory

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/topPeerCategoryForwardChats.html b/data/core.telegram.org/constructor/topPeerCategoryForwardChats.html deleted file mode 100644 index c678f8aa12..0000000000 --- a/data/core.telegram.org/constructor/topPeerCategoryForwardChats.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryForwardChats - - - - - - - - - - - - - -
- -
-
-
- -

topPeerCategoryForwardChats

- -

Chats to which the users often forwards messages to

-

- -
-
topPeerCategoryForwardChats#fbeec0f0 = TopPeerCategory;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

TopPeerCategory

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/topPeerCategoryForwardUsers.html b/data/core.telegram.org/constructor/topPeerCategoryForwardUsers.html deleted file mode 100644 index fcb286ba72..0000000000 --- a/data/core.telegram.org/constructor/topPeerCategoryForwardUsers.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryForwardUsers - - - - - - - - - - - - - -
- -
-
-
- -

topPeerCategoryForwardUsers

- -

Users to which the users often forwards messages to

-

- -
-
topPeerCategoryForwardUsers#a8406ca9 = TopPeerCategory;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

TopPeerCategory

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/topPeerCategoryGroups.html b/data/core.telegram.org/constructor/topPeerCategoryGroups.html deleted file mode 100644 index 537448ece5..0000000000 --- a/data/core.telegram.org/constructor/topPeerCategoryGroups.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryGroups - - - - - - - - - - - - - -
- -
-
-
- -

topPeerCategoryGroups

- -

Often-opened groups and supergroups

-

- -
-
topPeerCategoryGroups#bd17a14a = TopPeerCategory;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

TopPeerCategory

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/topPeerCategoryPhoneCalls.html b/data/core.telegram.org/constructor/topPeerCategoryPhoneCalls.html deleted file mode 100644 index 81ef90445d..0000000000 --- a/data/core.telegram.org/constructor/topPeerCategoryPhoneCalls.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryPhoneCalls - - - - - - - - - - - - - -
- -
-
-
- -

topPeerCategoryPhoneCalls

- -

Most frequently called users

-

- -
-
topPeerCategoryPhoneCalls#1e76a78c = TopPeerCategory;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

TopPeerCategory

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/true.html b/data/core.telegram.org/constructor/true.html deleted file mode 100644 index a609bce6e3..0000000000 --- a/data/core.telegram.org/constructor/true.html +++ /dev/null @@ -1,134 +0,0 @@ - - - - - true - - - - - - - - - - - - - -
- -
-
-
- -

true

- -

See predefined identifiers.

-

- -
-
true#3fedd339 = True;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

True

-

Related pages

-

TL-formal

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateBotCallbackQuery.html b/data/core.telegram.org/constructor/updateBotCallbackQuery.html deleted file mode 100644 index 5be1adf264..0000000000 --- a/data/core.telegram.org/constructor/updateBotCallbackQuery.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - updateBotCallbackQuery - - - - - - - - - - - - - -
- -
-
-
- -

updateBotCallbackQuery

- -

A callback button was pressed, and the button data was sent to the bot that created the button

-

- -
-
updateBotCallbackQuery#b9cfc48d flags:# query_id:long user_id:long peer:Peer msg_id:int chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
query_idlongQuery ID
user_idlongID of the user that pressed the button
peerPeerChat where the inline keyboard was sent
msg_idintMessage ID
chat_instancelongGlobal identifier, uniquely corresponding to the chat to which the message with the callback button was sent. Useful for high scores in games.
dataflags.0?bytesCallback data
game_short_nameflags.1?stringShort name of a Game to be returned, serves as the unique identifier for the game
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateBotCommands.html b/data/core.telegram.org/constructor/updateBotCommands.html deleted file mode 100644 index 30148f73f1..0000000000 --- a/data/core.telegram.org/constructor/updateBotCommands.html +++ /dev/null @@ -1,159 +0,0 @@ - - - - - updateBotCommands - - - - - - - - - - - - - -
- -
-
-
- -

updateBotCommands

- -

The command set of a certain bot in a certain chat has changed.

-

- -
-
updateBotCommands#4d712f2e peer:Peer bot_id:long commands:Vector<BotCommand> = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerThe affected chat
bot_idlongID of the bot that changed its command set
commandsVector<BotCommand>New bot commands
-

Type

-

Update

-

Related pages

-

Telegram Bot API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateBotInlineQuery.html b/data/core.telegram.org/constructor/updateBotInlineQuery.html deleted file mode 100644 index f71006b5a3..0000000000 --- a/data/core.telegram.org/constructor/updateBotInlineQuery.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - updateBotInlineQuery - - - - - - - - - - - - - -
- -
-
-
- -

updateBotInlineQuery

- -

An incoming inline query

-

- -
-
updateBotInlineQuery#496f379c flags:# query_id:long user_id:long query:string geo:flags.0?GeoPoint peer_type:flags.1?InlineQueryPeerType offset:string = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
query_idlongQuery ID
user_idlongUser that sent the query
querystringText of query
geoflags.0?GeoPointAttached geolocation
peer_typeflags.1?InlineQueryPeerTypeType of the chat from which the inline query was sent.
offsetstringOffset to navigate through results
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateBotShippingQuery.html b/data/core.telegram.org/constructor/updateBotShippingQuery.html deleted file mode 100644 index 7e0efdf187..0000000000 --- a/data/core.telegram.org/constructor/updateBotShippingQuery.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - updateBotShippingQuery - - - - - - - - - - - - - -
- -
-
-
- -

updateBotShippingQuery

- -

This object contains information about an incoming shipping query.

-

- -
-
updateBotShippingQuery#b5aefd7d query_id:long user_id:long payload:bytes shipping_address:PostAddress = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
query_idlongUnique query identifier
user_idlongUser who sent the query
payloadbytesBot specified invoice payload
shipping_addressPostAddressUser specified shipping address
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateBotStopped.html b/data/core.telegram.org/constructor/updateBotStopped.html deleted file mode 100644 index a54e6754ec..0000000000 --- a/data/core.telegram.org/constructor/updateBotStopped.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - updateBotStopped - - - - - - - - - - - - - -
- -
-
-
- -

updateBotStopped

- -

A bot was stopped or re-started.

-

- -
-
updateBotStopped#c4870a49 user_id:long date:int stopped:Bool qts:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongThe bot ID
dateintWhen did this action occur
stoppedBoolWhether the bot was stopped or started
qtsintNew qts value, see updates » for more info.
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateBotWebhookJSON.html b/data/core.telegram.org/constructor/updateBotWebhookJSON.html deleted file mode 100644 index ea38f033de..0000000000 --- a/data/core.telegram.org/constructor/updateBotWebhookJSON.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateBotWebhookJSON - - - - - - - - - - - - - -
- -
-
-
- -

updateBotWebhookJSON

- -

A new incoming event; for bots only

-

- -
-
updateBotWebhookJSON#8317c0c3 data:DataJSON = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
dataDataJSONThe event
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateBotWebhookJSONQuery.html b/data/core.telegram.org/constructor/updateBotWebhookJSONQuery.html deleted file mode 100644 index eaeed8e555..0000000000 --- a/data/core.telegram.org/constructor/updateBotWebhookJSONQuery.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateBotWebhookJSONQuery - - - - - - - - - - - - - -
- -
-
-
- -

updateBotWebhookJSONQuery

- -

A new incoming query; for bots only

-

- -
-
updateBotWebhookJSONQuery#9b9240a6 query_id:long data:DataJSON timeout:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
query_idlongQuery identifier
dataDataJSONQuery data
timeoutintQuery timeout
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChannel.html b/data/core.telegram.org/constructor/updateChannel.html deleted file mode 100644 index f322d0d6ce..0000000000 --- a/data/core.telegram.org/constructor/updateChannel.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateChannel - - - - - - - - - - - - - -
- -
-
-
- -

updateChannel

- -

A new channel is available

-

- -
-
updateChannel#635b4c09 channel_id:long = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
channel_idlongChannel ID
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChannelMessageForwards.html b/data/core.telegram.org/constructor/updateChannelMessageForwards.html deleted file mode 100644 index b48ed507df..0000000000 --- a/data/core.telegram.org/constructor/updateChannelMessageForwards.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateChannelMessageForwards - - - - - - - - - - - - - -
- -
-
-
- -

updateChannelMessageForwards

- -

The forward counter of a message in a channel has changed

-

- -
-
updateChannelMessageForwards#d29a27f4 channel_id:long id:int forwards:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idlongChannel ID
idintID of the message
forwardsintNew forward counter
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChannelMessageViews.html b/data/core.telegram.org/constructor/updateChannelMessageViews.html deleted file mode 100644 index bd31194007..0000000000 --- a/data/core.telegram.org/constructor/updateChannelMessageViews.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateChannelMessageViews - - - - - - - - - - - - - -
- -
-
-
- -

updateChannelMessageViews

- -

The view counter of a message in a channel has changed

-

- -
-
updateChannelMessageViews#f226ac08 channel_id:long id:int views:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idlongChannel ID
idintID of the message
viewsintNew view counter
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChannelParticipant.html b/data/core.telegram.org/constructor/updateChannelParticipant.html deleted file mode 100644 index 7e0a5630df..0000000000 --- a/data/core.telegram.org/constructor/updateChannelParticipant.html +++ /dev/null @@ -1,192 +0,0 @@ - - - - - updateChannelParticipant - - - - - - - - - - - - - -
- -
-
-
- -

updateChannelParticipant

- -

A participant has left, joined, was banned or admined in a channel or supergroup.

-

- -
-
updateChannelParticipant#985d3abb flags:# channel_id:long date:int actor_id:long user_id:long prev_participant:flags.0?ChannelParticipant new_participant:flags.1?ChannelParticipant invite:flags.2?ExportedChatInvite qts:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
channel_idlongChannel ID
dateintDate of the event
actor_idlongUser that triggered the change (inviter, admin that kicked the user, or the even the user_id itself)
user_idlongUser that was affected by the change
prev_participantflags.0?ChannelParticipantPrevious participant status
new_participantflags.1?ChannelParticipantNew participant status
inviteflags.2?ExportedChatInviteChat invite used to join the channel/supergroup
qtsintNew qts value, see updates » for more info.
-

Type

-

Update

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChannelReadMessagesContents.html b/data/core.telegram.org/constructor/updateChannelReadMessagesContents.html deleted file mode 100644 index c1640cd6df..0000000000 --- a/data/core.telegram.org/constructor/updateChannelReadMessagesContents.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - updateChannelReadMessagesContents - - - - - - - - - - - - - -
- -
-
-
- -

updateChannelReadMessagesContents

- -

The specified channel/supergroup messages were read

-

- -
-
updateChannelReadMessagesContents#44bdd535 channel_id:long messages:Vector<int> = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idlongChannel/supergroup ID
messagesVector<int>IDs of messages that were read
-

Type

-

Update

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChannelTooLong.html b/data/core.telegram.org/constructor/updateChannelTooLong.html deleted file mode 100644 index 7e001417d8..0000000000 --- a/data/core.telegram.org/constructor/updateChannelTooLong.html +++ /dev/null @@ -1,161 +0,0 @@ - - - - - updateChannelTooLong - - - - - - - - - - - - - -
- -
-
-
- -

updateChannelTooLong

- -

There are new updates in the specified channel, the client must fetch them.
-If the difference is too long or if the channel isn't currently in the states, start fetching from the specified pts.

-

- -
-
updateChannelTooLong#108d941f flags:# channel_id:long pts:flags.0?int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
channel_idlongThe channel
ptsflags.0?intThe PTS.
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChannelUserTyping.html b/data/core.telegram.org/constructor/updateChannelUserTyping.html deleted file mode 100644 index 822be5c625..0000000000 --- a/data/core.telegram.org/constructor/updateChannelUserTyping.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - updateChannelUserTyping - - - - - - - - - - - - - -
- -
-
-
- -

updateChannelUserTyping

- -

A user is typing in a supergroup, channel or message thread

-

- -
-
updateChannelUserTyping#8c88c923 flags:# channel_id:long top_msg_id:flags.0?int from_id:Peer action:SendMessageAction = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
channel_idlongChannel ID
top_msg_idflags.0?intThread ID
from_idPeerThe peer that is typing
actionSendMessageActionWhether the user is typing, sending a media or doing something else
-

Type

-

Update

-

Related pages

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChannelWebPage.html b/data/core.telegram.org/constructor/updateChannelWebPage.html deleted file mode 100644 index ac21f0f9da..0000000000 --- a/data/core.telegram.org/constructor/updateChannelWebPage.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - updateChannelWebPage - - - - - - - - - - - - - -
- -
-
-
- -

updateChannelWebPage

- -

A webpage preview of a link in a channel/supergroup message was generated

-

- -
-
updateChannelWebPage#2f2ba99f channel_id:long webpage:WebPage pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idlongChannel/supergroup ID
webpageWebPageGenerated webpage preview
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChat.html b/data/core.telegram.org/constructor/updateChat.html deleted file mode 100644 index 6157de529f..0000000000 --- a/data/core.telegram.org/constructor/updateChat.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateChat - - - - - - - - - - - - - -
- -
-
-
- -

updateChat

- -

A new chat is available

-

- -
-
updateChat#f89a6a4e chat_id:long = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongChat ID
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChatDefaultBannedRights.html b/data/core.telegram.org/constructor/updateChatDefaultBannedRights.html deleted file mode 100644 index fb84016788..0000000000 --- a/data/core.telegram.org/constructor/updateChatDefaultBannedRights.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - updateChatDefaultBannedRights - - - - - - - - - - - - - -
- -
-
-
- -

updateChatDefaultBannedRights

- -

Default banned rights in a normal chat were updated

-

- -
-
updateChatDefaultBannedRights#54c01850 peer:Peer default_banned_rights:ChatBannedRights version:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerThe chat
default_banned_rightsChatBannedRightsNew default banned rights
versionintVersion
-

Type

-

Update

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChatParticipantAdd.html b/data/core.telegram.org/constructor/updateChatParticipantAdd.html deleted file mode 100644 index 4da2034a61..0000000000 --- a/data/core.telegram.org/constructor/updateChatParticipantAdd.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - updateChatParticipantAdd - - - - - - - - - - - - - -
- -
-
-
- -

updateChatParticipantAdd

- -

New group member.

-

- -
-
updateChatParticipantAdd#3dda5451 chat_id:long user_id:long inviter_id:long date:int version:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongGroup ID
user_idlongID of the new member
inviter_idlongID of the user, who added member to the group
dateintWhen was the participant added
versionintChat version number
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChatParticipantAdmin.html b/data/core.telegram.org/constructor/updateChatParticipantAdmin.html deleted file mode 100644 index 62c10ebbc4..0000000000 --- a/data/core.telegram.org/constructor/updateChatParticipantAdmin.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - updateChatParticipantAdmin - - - - - - - - - - - - - -
- -
-
-
- -

updateChatParticipantAdmin

- -

Admin permissions of a user in a legacy group were changed

-

- -
-
updateChatParticipantAdmin#d7ca61a2 chat_id:long user_id:long is_admin:Bool version:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongChat ID
user_idlongID of the (de)admined user
is_adminBoolWhether the user was rendered admin
versionintUsed in basic groups to reorder updates and make sure that all of them was received.
-

Type

-

Update

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChatParticipantDelete.html b/data/core.telegram.org/constructor/updateChatParticipantDelete.html deleted file mode 100644 index 0fd95c5d0c..0000000000 --- a/data/core.telegram.org/constructor/updateChatParticipantDelete.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateChatParticipantDelete - - - - - - - - - - - - - -
- -
-
-
- -

updateChatParticipantDelete

- -

A member has left the group.

-

- -
-
updateChatParticipantDelete#e32f3d77 chat_id:long user_id:long version:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongGroup ID
user_idlongID of the user
versionintUsed in basic groups to reorder updates and make sure that all of them was received.
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChatParticipants.html b/data/core.telegram.org/constructor/updateChatParticipants.html deleted file mode 100644 index 834f29d27d..0000000000 --- a/data/core.telegram.org/constructor/updateChatParticipants.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateChatParticipants - - - - - - - - - - - - - -
- -
-
-
- -

updateChatParticipants

- -

Composition of chat participants changed.

-

- -
-
updateChatParticipants#7761198 participants:ChatParticipants = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
participantsChatParticipantsUpdated chat participants
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateChatUserTyping.html b/data/core.telegram.org/constructor/updateChatUserTyping.html deleted file mode 100644 index 8d6aa09372..0000000000 --- a/data/core.telegram.org/constructor/updateChatUserTyping.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - updateChatUserTyping - - - - - - - - - - - - - -
- -
-
-
- -

updateChatUserTyping

- -

The user is preparing a message in a group; typing, recording, uploading, etc. This update is valid for 6 seconds. If no repeated update received after 6 seconds, it should be considered that the user stopped doing whatever he's been doing.

-

- -
-
updateChatUserTyping#83487af0 chat_id:long from_id:Peer action:SendMessageAction = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongGroup id
from_idPeerPeer that started typing (can be the chat itself, in case of anonymous admins).
actionSendMessageActionType of action
Parameter added in Layer 17.
-

Type

-

Update

-

Related pages

-

Layers

-

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateConfig.html b/data/core.telegram.org/constructor/updateConfig.html deleted file mode 100644 index 421388b500..0000000000 --- a/data/core.telegram.org/constructor/updateConfig.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - updateConfig - - - - - - - - - - - - - -
- -
-
-
- -

updateConfig

- -

The server-side configuration has changed; the client should re-fetch the config using help.getConfig

-

- -
-
updateConfig#a229dd06 = Update;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Update

-

Related pages

-

help.getConfig

-

Returns current configuration, including data center configuration.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateDcOptions.html b/data/core.telegram.org/constructor/updateDcOptions.html deleted file mode 100644 index f8c04ce363..0000000000 --- a/data/core.telegram.org/constructor/updateDcOptions.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateDcOptions - - - - - - - - - - - - - -
- -
-
-
- -

updateDcOptions

- -

Changes in the data center configuration options.

-

- -
-
updateDcOptions#8e5e9873 dc_options:Vector<DcOption> = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
dc_optionsVector<DcOption>New connection options
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateDeleteChannelMessages.html b/data/core.telegram.org/constructor/updateDeleteChannelMessages.html deleted file mode 100644 index ba1ca84fb3..0000000000 --- a/data/core.telegram.org/constructor/updateDeleteChannelMessages.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - updateDeleteChannelMessages - - - - - - - - - - - - - -
- -
-
-
- -

updateDeleteChannelMessages

- -

Some messages in a supergroup/channel were deleted

-

- -
-
updateDeleteChannelMessages#c32d5b12 channel_id:long messages:Vector<int> pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idlongChannel ID
messagesVector<int>IDs of messages that were deleted
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateDeleteMessages.html b/data/core.telegram.org/constructor/updateDeleteMessages.html deleted file mode 100644 index 778c70d0b2..0000000000 --- a/data/core.telegram.org/constructor/updateDeleteMessages.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - updateDeleteMessages - - - - - - - - - - - - - -
- -
-
-
- -

updateDeleteMessages

- -

Messages were deleted.

-

- -
-
updateDeleteMessages#a20db0e5 messages:Vector<int> pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messagesVector<int>List of identifiers of deleted messages
ptsintNew quality of actions in a message box
pts_countintNumber of generated events
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateDeleteScheduledMessages.html b/data/core.telegram.org/constructor/updateDeleteScheduledMessages.html deleted file mode 100644 index f44b5cb077..0000000000 --- a/data/core.telegram.org/constructor/updateDeleteScheduledMessages.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - updateDeleteScheduledMessages - - - - - - - - - - - - - -
- -
-
-
- -

updateDeleteScheduledMessages

- -

Some scheduled messages were deleted from the schedule queue of a chat

-

- -
-
updateDeleteScheduledMessages#90866cee peer:Peer messages:Vector<int> = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerPeer
messagesVector<int>Deleted scheduled messages
-

Type

-

Update

-

Related pages

-

Scheduled messages

-

Telegram allows scheduling messages

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateDialogFilterOrder.html b/data/core.telegram.org/constructor/updateDialogFilterOrder.html deleted file mode 100644 index 0cec4f5e97..0000000000 --- a/data/core.telegram.org/constructor/updateDialogFilterOrder.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - updateDialogFilterOrder - - - - - - - - - - - - - -
- -
-
-
- -

updateDialogFilterOrder

- -

New folder order

-

- -
-
updateDialogFilterOrder#a5d72105 order:Vector<int> = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
orderVector<int>Ordered folder IDs
-

Type

-

Update

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateDialogFilters.html b/data/core.telegram.org/constructor/updateDialogFilters.html deleted file mode 100644 index 73f9eaa1cd..0000000000 --- a/data/core.telegram.org/constructor/updateDialogFilters.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - updateDialogFilters - - - - - - - - - - - - - -
- -
-
-
- -

updateDialogFilters

- -

Clients should update folder info

-

- -
-
updateDialogFilters#3504914f = Update;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Update

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateDialogPinned.html b/data/core.telegram.org/constructor/updateDialogPinned.html deleted file mode 100644 index 9953aab326..0000000000 --- a/data/core.telegram.org/constructor/updateDialogPinned.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - updateDialogPinned - - - - - - - - - - - - - -
- -
-
-
- -

updateDialogPinned

- -

A dialog was pinned/unpinned

-

- -
-
updateDialogPinned#6e6fe51c flags:# pinned:flags.0?true folder_id:flags.1?int peer:DialogPeer = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.0?trueWhether the dialog was pinned
folder_idflags.1?intPeer folder ID, for more info click here
peerDialogPeerThe dialog
-

Type

-

Update

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateDialogUnreadMark.html b/data/core.telegram.org/constructor/updateDialogUnreadMark.html deleted file mode 100644 index b535f9f65b..0000000000 --- a/data/core.telegram.org/constructor/updateDialogUnreadMark.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateDialogUnreadMark - - - - - - - - - - - - - -
- -
-
-
- -

updateDialogUnreadMark

- -

The manual unread mark of a chat was changed

-

- -
-
updateDialogUnreadMark#e16459c3 flags:# unread:flags.0?true peer:DialogPeer = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
unreadflags.0?trueWas the chat marked or unmarked as read
peerDialogPeerThe dialog
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateDraftMessage.html b/data/core.telegram.org/constructor/updateDraftMessage.html deleted file mode 100644 index 29d14ce52b..0000000000 --- a/data/core.telegram.org/constructor/updateDraftMessage.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - updateDraftMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateDraftMessage

- -

Notifies a change of a message draft.

-

- -
-
updateDraftMessage#ee2bb969 peer:Peer draft:DraftMessage = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerThe peer to which the draft is associated
draftDraftMessageThe draft
-

Type

-

Update

-

Related pages

-

Message drafts

-

How to handle message drafts

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateEditChannelMessage.html b/data/core.telegram.org/constructor/updateEditChannelMessage.html deleted file mode 100644 index ee2dbbcb70..0000000000 --- a/data/core.telegram.org/constructor/updateEditChannelMessage.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - updateEditChannelMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateEditChannelMessage

- -

A message was edited in a channel/supergroup

-

- -
-
updateEditChannelMessage#1b3f4df7 message:Message pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageThe new message
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateEditMessage.html b/data/core.telegram.org/constructor/updateEditMessage.html deleted file mode 100644 index c768e06310..0000000000 --- a/data/core.telegram.org/constructor/updateEditMessage.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - updateEditMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateEditMessage

- -

A message was edited

-

- -
-
updateEditMessage#e40370a3 message:Message pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageThe new edited message
ptsintPTS
pts_countintPTS count
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateEncryptedChatTyping.html b/data/core.telegram.org/constructor/updateEncryptedChatTyping.html deleted file mode 100644 index e40625d470..0000000000 --- a/data/core.telegram.org/constructor/updateEncryptedChatTyping.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateEncryptedChatTyping - - - - - - - - - - - - - -
- -
-
-
- -

updateEncryptedChatTyping

- -

Interlocutor is typing a message in an encrypted chat. Update period is 6 second. If upon this time there is no repeated update, it shall be considered that the interlocutor stopped typing.

-

- -
-
updateEncryptedChatTyping#1710f156 chat_id:int = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chat_idintChat ID
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateEncryptedMessagesRead.html b/data/core.telegram.org/constructor/updateEncryptedMessagesRead.html deleted file mode 100644 index d5cdc87540..0000000000 --- a/data/core.telegram.org/constructor/updateEncryptedMessagesRead.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateEncryptedMessagesRead - - - - - - - - - - - - - -
- -
-
-
- -

updateEncryptedMessagesRead

- -

Communication history in an encrypted chat was marked as read.

-

- -
-
updateEncryptedMessagesRead#38fe25b7 chat_id:int max_date:int date:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idintChat ID
max_dateintMaximum value of data for read messages
dateintTime when messages were read
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateEncryption.html b/data/core.telegram.org/constructor/updateEncryption.html deleted file mode 100644 index 87fd5efd86..0000000000 --- a/data/core.telegram.org/constructor/updateEncryption.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updateEncryption - - - - - - - - - - - - - -
- -
-
-
- -

updateEncryption

- -

Change of state in an encrypted chat.

-

- -
-
updateEncryption#b4a2e88d chat:EncryptedChat date:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chatEncryptedChatEncrypted chat
dateintDate of change
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateFavedStickers.html b/data/core.telegram.org/constructor/updateFavedStickers.html deleted file mode 100644 index da0a4ad57c..0000000000 --- a/data/core.telegram.org/constructor/updateFavedStickers.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - updateFavedStickers - - - - - - - - - - - - - -
- -
-
-
- -

updateFavedStickers

- -

The list of favorited stickers was changed, the client should call messages.getFavedStickers to refetch the new list

-

- -
-
updateFavedStickers#e511996d = Update;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Update

-

Related pages

-

messages.getFavedStickers

-

Get faved stickers

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateFolderPeers.html b/data/core.telegram.org/constructor/updateFolderPeers.html deleted file mode 100644 index 8e2734d4f9..0000000000 --- a/data/core.telegram.org/constructor/updateFolderPeers.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - updateFolderPeers - - - - - - - - - - - - - -
- -
-
-
- -

updateFolderPeers

- -

The peer list of a peer folder was updated

-

- -
-
updateFolderPeers#19360dc0 folder_peers:Vector<FolderPeer> pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
folder_peersVector<FolderPeer>New peer list
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateGeoLiveViewed.html b/data/core.telegram.org/constructor/updateGeoLiveViewed.html deleted file mode 100644 index 4019a83f92..0000000000 --- a/data/core.telegram.org/constructor/updateGeoLiveViewed.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updateGeoLiveViewed - - - - - - - - - - - - - -
- -
-
-
- -

updateGeoLiveViewed

- -

Live geoposition message was viewed

-

- -
-
updateGeoLiveViewed#871fb939 peer:Peer msg_id:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerThe user that viewed the live geoposition
msg_idintMessage ID of geoposition message
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateGroupCall.html b/data/core.telegram.org/constructor/updateGroupCall.html deleted file mode 100644 index 490a4d0037..0000000000 --- a/data/core.telegram.org/constructor/updateGroupCall.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - updateGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

updateGroupCall

- -

A new groupcall was started

-

- -
-
updateGroupCall#14b24500 chat_id:long call:GroupCall = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongThe channel/supergroup where this group call or livestream takes place
callGroupCallInfo about the group call or livestream
-

Type

-

Update

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateGroupCallConnection.html b/data/core.telegram.org/constructor/updateGroupCallConnection.html deleted file mode 100644 index 7682a21b61..0000000000 --- a/data/core.telegram.org/constructor/updateGroupCallConnection.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateGroupCallConnection - - - - - - - - - - - - - -
- -
-
-
- -

updateGroupCallConnection

- -

New WebRTC parameters

-

- -
-
updateGroupCallConnection#b783982 flags:# presentation:flags.0?true params:DataJSON = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
presentationflags.0?trueAre these parameters related to the screen capture session currently in progress?
paramsDataJSONWebRTC parameters
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateGroupCallParticipants.html b/data/core.telegram.org/constructor/updateGroupCallParticipants.html deleted file mode 100644 index 16b868f25c..0000000000 --- a/data/core.telegram.org/constructor/updateGroupCallParticipants.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateGroupCallParticipants - - - - - - - - - - - - - -
- -
-
-
- -

updateGroupCallParticipants

- -

The participant list of a certain group call has changed

-

- -
-
updateGroupCallParticipants#f2ebdb4e call:InputGroupCall participants:Vector<GroupCallParticipant> version:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallGroup call
participantsVector<GroupCallParticipant>New participant list
versionintVersion
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateLangPack.html b/data/core.telegram.org/constructor/updateLangPack.html deleted file mode 100644 index cd5b069397..0000000000 --- a/data/core.telegram.org/constructor/updateLangPack.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateLangPack - - - - - - - - - - - - - -
- -
-
-
- -

updateLangPack

- -

Language pack updated

-

- -
-
updateLangPack#56022f4d difference:LangPackDifference = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
differenceLangPackDifferenceChanged strings
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateLangPackTooLong.html b/data/core.telegram.org/constructor/updateLangPackTooLong.html deleted file mode 100644 index 72fbf1b373..0000000000 --- a/data/core.telegram.org/constructor/updateLangPackTooLong.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - updateLangPackTooLong - - - - - - - - - - - - - -
- -
-
-
- -

updateLangPackTooLong

- -

A language pack has changed, the client should manually fetch the changed strings using langpack.getDifference

-

- -
-
updateLangPackTooLong#46560264 lang_code:string = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
lang_codestringLanguage code
-

Type

-

Update

-

Related pages

-

langpack.getDifference

-

Get new strings in languagepack

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateLoginToken.html b/data/core.telegram.org/constructor/updateLoginToken.html deleted file mode 100644 index 88cfe05c8f..0000000000 --- a/data/core.telegram.org/constructor/updateLoginToken.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - updateLoginToken - - - - - - - - - - - - - -
- -
-
-
- -

updateLoginToken

- -

A login token (for login via QR code) was accepted.

-

- -
-
updateLoginToken#564fe691 = Update;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateMessageID.html b/data/core.telegram.org/constructor/updateMessageID.html deleted file mode 100644 index b087c5f3e9..0000000000 --- a/data/core.telegram.org/constructor/updateMessageID.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - updateMessageID - - - - - - - - - - - - - -
- -
-
-
- -

updateMessageID

- -

Sent message with random_id client identifier was assigned an identifier.

-

- -
-
updateMessageID#4e90bfd6 id:int random_id:long = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idintid identifier of a respective Message
random_idlongPreviuosly transferred client random_id identifier
-

Type

-

Update

-

Related pages

-

Message

-

Object describing a message.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateMessagePoll.html b/data/core.telegram.org/constructor/updateMessagePoll.html deleted file mode 100644 index 3fe5ffacbd..0000000000 --- a/data/core.telegram.org/constructor/updateMessagePoll.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - updateMessagePoll - - - - - - - - - - - - - -
- -
-
-
- -

updateMessagePoll

- -

The results of a poll have changed

-

- -
-
updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
poll_idlongPoll ID
pollflags.0?PollIf the server knows the client hasn't cached this poll yet, the poll itself
resultsPollResultsNew poll results
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateMessagePollVote.html b/data/core.telegram.org/constructor/updateMessagePollVote.html deleted file mode 100644 index 80cc68ae52..0000000000 --- a/data/core.telegram.org/constructor/updateMessagePollVote.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - updateMessagePollVote - - - - - - - - - - - - - -
- -
-
-
- -

updateMessagePollVote

- -

A specific user has voted in a poll

-

- -
-
updateMessagePollVote#106395c9 poll_id:long user_id:long options:Vector<bytes> qts:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
poll_idlongPoll ID
user_idlongUser ID
optionsVector<bytes>Chosen option(s)
qtsintNew qts value, see updates » for more info.
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateNewChannelMessage.html b/data/core.telegram.org/constructor/updateNewChannelMessage.html deleted file mode 100644 index 7cd11f83d0..0000000000 --- a/data/core.telegram.org/constructor/updateNewChannelMessage.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - updateNewChannelMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateNewChannelMessage

- -

A new message was sent in a channel/supergroup

-

- -
-
updateNewChannelMessage#62ba04d9 message:Message pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageNew message
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateNewEncryptedMessage.html b/data/core.telegram.org/constructor/updateNewEncryptedMessage.html deleted file mode 100644 index ba19543609..0000000000 --- a/data/core.telegram.org/constructor/updateNewEncryptedMessage.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - updateNewEncryptedMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateNewEncryptedMessage

- -

New encrypted message.

-

- -
-
updateNewEncryptedMessage#12bcbd9a message:EncryptedMessage qts:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messageEncryptedMessageMessage
qtsintNew qts value, see updates » for more info.
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateNewMessage.html b/data/core.telegram.org/constructor/updateNewMessage.html deleted file mode 100644 index 7521944f26..0000000000 --- a/data/core.telegram.org/constructor/updateNewMessage.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateNewMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateNewMessage

- -

New message in a private chat or in a legacy group.

-

- -
-
updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageMessage
ptsintNew quantity of actions in a message box
pts_countintNumber of generated events
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateNewScheduledMessage.html b/data/core.telegram.org/constructor/updateNewScheduledMessage.html deleted file mode 100644 index 2930466baf..0000000000 --- a/data/core.telegram.org/constructor/updateNewScheduledMessage.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - updateNewScheduledMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateNewScheduledMessage

- -

A message was added to the schedule queue of a chat

-

- -
-
updateNewScheduledMessage#39a51dfb message:Message = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageMessage
-

Type

-

Update

-

Related pages

-

Scheduled messages

-

Telegram allows scheduling messages

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateNewStickerSet.html b/data/core.telegram.org/constructor/updateNewStickerSet.html deleted file mode 100644 index d43e415fcb..0000000000 --- a/data/core.telegram.org/constructor/updateNewStickerSet.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateNewStickerSet - - - - - - - - - - - - - -
- -
-
-
- -

updateNewStickerSet

- -

A new stickerset was installed

-

- -
-
updateNewStickerSet#688a30aa stickerset:messages.StickerSet = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
stickersetmessages.StickerSetThe installed stickerset
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateNotifySettings.html b/data/core.telegram.org/constructor/updateNotifySettings.html deleted file mode 100644 index ed81c06c47..0000000000 --- a/data/core.telegram.org/constructor/updateNotifySettings.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updateNotifySettings - - - - - - - - - - - - - -
- -
-
-
- -

updateNotifySettings

- -

Changes in notification settings.

-

- -
-
updateNotifySettings#bec268ef peer:NotifyPeer notify_settings:PeerNotifySettings = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerNotifyPeerNofication source
notify_settingsPeerNotifySettingsNew notification settings
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatePeerBlocked.html b/data/core.telegram.org/constructor/updatePeerBlocked.html deleted file mode 100644 index 386902435c..0000000000 --- a/data/core.telegram.org/constructor/updatePeerBlocked.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updatePeerBlocked - - - - - - - - - - - - - -
- -
-
-
- -

updatePeerBlocked

- -

A peer was blocked

-

- -
-
updatePeerBlocked#246a4b22 peer_id:Peer blocked:Bool = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peer_idPeerThe blocked peer
blockedBoolWhether the peer was blocked or unblocked
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatePeerLocated.html b/data/core.telegram.org/constructor/updatePeerLocated.html deleted file mode 100644 index 29defe6111..0000000000 --- a/data/core.telegram.org/constructor/updatePeerLocated.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updatePeerLocated - - - - - - - - - - - - - -
- -
-
-
- -

updatePeerLocated

- -

List of peers near you was updated

-

- -
-
updatePeerLocated#b4afcfb0 peers:Vector<PeerLocated> = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peersVector<PeerLocated>Geolocated peer list update
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatePeerSettings.html b/data/core.telegram.org/constructor/updatePeerSettings.html deleted file mode 100644 index 2cb8beb1be..0000000000 --- a/data/core.telegram.org/constructor/updatePeerSettings.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updatePeerSettings - - - - - - - - - - - - - -
- -
-
-
- -

updatePeerSettings

- -

Settings of a certain peer have changed

-

- -
-
updatePeerSettings#6a7e7366 peer:Peer settings:PeerSettings = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerThe peer
settingsPeerSettingsAssociated peer settings
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatePhoneCall.html b/data/core.telegram.org/constructor/updatePhoneCall.html deleted file mode 100644 index 46fc1ca7b1..0000000000 --- a/data/core.telegram.org/constructor/updatePhoneCall.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updatePhoneCall - - - - - - - - - - - - - -
- -
-
-
- -

updatePhoneCall

- -

An incoming phone call

-

- -
-
updatePhoneCall#ab0f6b1e phone_call:PhoneCall = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
phone_callPhoneCallPhone call
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatePhoneCallSignalingData.html b/data/core.telegram.org/constructor/updatePhoneCallSignalingData.html deleted file mode 100644 index 55ce7cf3ad..0000000000 --- a/data/core.telegram.org/constructor/updatePhoneCallSignalingData.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updatePhoneCallSignalingData - - - - - - - - - - - - - -
- -
-
-
- -

updatePhoneCallSignalingData

- -

Incoming phone call signaling payload

-

- -
-
updatePhoneCallSignalingData#2661bf09 phone_call_id:long data:bytes = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_call_idlongPhone call ID
databytesSignaling payload
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatePinnedChannelMessages.html b/data/core.telegram.org/constructor/updatePinnedChannelMessages.html deleted file mode 100644 index 16773d610c..0000000000 --- a/data/core.telegram.org/constructor/updatePinnedChannelMessages.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - updatePinnedChannelMessages - - - - - - - - - - - - - -
- -
-
-
- -

updatePinnedChannelMessages

- -

Messages were pinned/unpinned in a channel/supergroup

-

- -
-
updatePinnedChannelMessages#5bb98608 flags:# pinned:flags.0?true channel_id:long messages:Vector<int> pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.0?trueWhether the messages were pinned or unpinned
channel_idlongChannel ID
messagesVector<int>Messages
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatePinnedDialogs.html b/data/core.telegram.org/constructor/updatePinnedDialogs.html deleted file mode 100644 index db5888e8fa..0000000000 --- a/data/core.telegram.org/constructor/updatePinnedDialogs.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - updatePinnedDialogs - - - - - - - - - - - - - -
- -
-
-
- -

updatePinnedDialogs

- -

Pinned dialogs were updated

-

- -
-
updatePinnedDialogs#fa0f3ca2 flags:# folder_id:flags.1?int order:flags.0?Vector<DialogPeer> = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.1?intPeer folder ID, for more info click here
orderflags.0?Vector<DialogPeer>New order of pinned dialogs
-

Type

-

Update

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatePinnedMessages.html b/data/core.telegram.org/constructor/updatePinnedMessages.html deleted file mode 100644 index 199fbaff94..0000000000 --- a/data/core.telegram.org/constructor/updatePinnedMessages.html +++ /dev/null @@ -1,175 +0,0 @@ - - - - - updatePinnedMessages - - - - - - - - - - - - - -
- -
-
-
- -

updatePinnedMessages

- -

Some messages were pinned in a chat

-

- -
-
updatePinnedMessages#ed85eab5 flags:# pinned:flags.0?true peer:Peer messages:Vector<int> pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.0?trueWhether the messages were pinned or unpinned
peerPeerPeer
messagesVector<int>Message IDs
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatePrivacy.html b/data/core.telegram.org/constructor/updatePrivacy.html deleted file mode 100644 index 4631dd9a46..0000000000 --- a/data/core.telegram.org/constructor/updatePrivacy.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updatePrivacy - - - - - - - - - - - - - -
- -
-
-
- -

updatePrivacy

- -

Privacy rules were changed

-

- -
-
updatePrivacy#ee3b272a key:PrivacyKey rules:Vector<PrivacyRule> = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
keyPrivacyKeyPeers to which the privacy rules apply
rulesVector<PrivacyRule>New privacy rules
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatePtsChanged.html b/data/core.telegram.org/constructor/updatePtsChanged.html deleted file mode 100644 index 41d7f504f1..0000000000 --- a/data/core.telegram.org/constructor/updatePtsChanged.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - updatePtsChanged - - - - - - - - - - - - - -
- -
-
-
- -

updatePtsChanged

- -

Common message box sequence PTS has changed, state has to be refetched using updates.getState

-

- -
-
updatePtsChanged#3354678f = Update;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateReadChannelDiscussionInbox.html b/data/core.telegram.org/constructor/updateReadChannelDiscussionInbox.html deleted file mode 100644 index 88b1b1ec15..0000000000 --- a/data/core.telegram.org/constructor/updateReadChannelDiscussionInbox.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - updateReadChannelDiscussionInbox - - - - - - - - - - - - - -
- -
-
-
- -

updateReadChannelDiscussionInbox

- -

Incoming comments in a discussion thread were marked as read

-

- -
-
updateReadChannelDiscussionInbox#d6b19546 flags:# channel_id:long top_msg_id:int read_max_id:int broadcast_id:flags.0?long broadcast_post:flags.0?int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
channel_idlongDiscussion group ID
top_msg_idintID of the group message that started the thread (message in linked discussion group)
read_max_idintMessage ID of latest read incoming message for this thread
broadcast_idflags.0?longIf set, contains the ID of the channel that contains the post that started the comment thread in the discussion group (channel_id)
broadcast_postflags.0?intIf set, contains the ID of the channel post that started the the comment thread
-

Type

-

Update

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateReadChannelDiscussionOutbox.html b/data/core.telegram.org/constructor/updateReadChannelDiscussionOutbox.html deleted file mode 100644 index c0c57517cb..0000000000 --- a/data/core.telegram.org/constructor/updateReadChannelDiscussionOutbox.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - updateReadChannelDiscussionOutbox - - - - - - - - - - - - - -
- -
-
-
- -

updateReadChannelDiscussionOutbox

- -

Outgoing comments in a discussion thread were marked as read

-

- -
-
updateReadChannelDiscussionOutbox#695c9e7c channel_id:long top_msg_id:int read_max_id:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idlongSupergroup ID
top_msg_idintID of the group message that started the thread
read_max_idintMessage ID of latest read outgoing message for this thread
-

Type

-

Update

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateReadChannelInbox.html b/data/core.telegram.org/constructor/updateReadChannelInbox.html deleted file mode 100644 index 7d80dff5a1..0000000000 --- a/data/core.telegram.org/constructor/updateReadChannelInbox.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - updateReadChannelInbox - - - - - - - - - - - - - -
- -
-
-
- -

updateReadChannelInbox

- -

Incoming messages in a channel/supergroup were read

-

- -
-
updateReadChannelInbox#922e6e10 flags:# folder_id:flags.0?int channel_id:long max_id:int still_unread_count:int pts:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.0?intPeer folder ID, for more info click here
channel_idlongChannel/supergroup ID
max_idintPosition up to which all incoming messages are read.
still_unread_countintCount of messages weren't read yet
ptsintEvent count after generation
-

Type

-

Update

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateReadChannelOutbox.html b/data/core.telegram.org/constructor/updateReadChannelOutbox.html deleted file mode 100644 index 82976bfc8b..0000000000 --- a/data/core.telegram.org/constructor/updateReadChannelOutbox.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - updateReadChannelOutbox - - - - - - - - - - - - - -
- -
-
-
- -

updateReadChannelOutbox

- -

Outgoing messages in a channel/supergroup were read

-

- -
-
updateReadChannelOutbox#b75f99a9 channel_id:long max_id:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idlongChannel/supergroup ID
max_idintPosition up to which all outgoing messages are read.
-

Type

-

Update

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateReadFeaturedStickers.html b/data/core.telegram.org/constructor/updateReadFeaturedStickers.html deleted file mode 100644 index aeb162deee..0000000000 --- a/data/core.telegram.org/constructor/updateReadFeaturedStickers.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - updateReadFeaturedStickers - - - - - - - - - - - - - -
- -
-
-
- -

updateReadFeaturedStickers

- -

Some featured stickers were marked as read

-

- -
-
updateReadFeaturedStickers#571d2742 = Update;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateReadHistoryInbox.html b/data/core.telegram.org/constructor/updateReadHistoryInbox.html deleted file mode 100644 index bdfa1383f5..0000000000 --- a/data/core.telegram.org/constructor/updateReadHistoryInbox.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - updateReadHistoryInbox - - - - - - - - - - - - - -
- -
-
-
- -

updateReadHistoryInbox

- -

Incoming messages were read

-

- -
-
updateReadHistoryInbox#9c974fdf flags:# folder_id:flags.0?int peer:Peer max_id:int still_unread_count:int pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.0?intPeer folder ID, for more info click here
peerPeerPeer
max_idintMaximum ID of messages read
still_unread_countintNumber of messages that are still unread
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateReadHistoryOutbox.html b/data/core.telegram.org/constructor/updateReadHistoryOutbox.html deleted file mode 100644 index b67c225240..0000000000 --- a/data/core.telegram.org/constructor/updateReadHistoryOutbox.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - updateReadHistoryOutbox - - - - - - - - - - - - - -
- -
-
-
- -

updateReadHistoryOutbox

- -

Outgoing messages were read

-

- -
-
updateReadHistoryOutbox#2f2f21bf peer:Peer max_id:int pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerPeer
max_idintMaximum ID of read outgoing messages
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateReadMessagesContents.html b/data/core.telegram.org/constructor/updateReadMessagesContents.html deleted file mode 100644 index 7db4c08653..0000000000 --- a/data/core.telegram.org/constructor/updateReadMessagesContents.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - updateReadMessagesContents - - - - - - - - - - - - - -
- -
-
-
- -

updateReadMessagesContents

- -

Contents of messages in the common message box were read

-

- -
-
updateReadMessagesContents#68c13933 messages:Vector<int> pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messagesVector<int>IDs of read messages
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateRecentStickers.html b/data/core.telegram.org/constructor/updateRecentStickers.html deleted file mode 100644 index 10d375b9b5..0000000000 --- a/data/core.telegram.org/constructor/updateRecentStickers.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - updateRecentStickers - - - - - - - - - - - - - -
- -
-
-
- -

updateRecentStickers

- -

The recent sticker list was updated

-

- -
-
updateRecentStickers#9a422c20 = Update;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateSavedGifs.html b/data/core.telegram.org/constructor/updateSavedGifs.html deleted file mode 100644 index d1ab17d29c..0000000000 --- a/data/core.telegram.org/constructor/updateSavedGifs.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - updateSavedGifs - - - - - - - - - - - - - -
- -
-
-
- -

updateSavedGifs

- -

The saved gif list has changed, the client should refetch it using messages.getSavedGifs

-

- -
-
updateSavedGifs#9375341e = Update;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateServiceNotification.html b/data/core.telegram.org/constructor/updateServiceNotification.html deleted file mode 100644 index e724518904..0000000000 --- a/data/core.telegram.org/constructor/updateServiceNotification.html +++ /dev/null @@ -1,183 +0,0 @@ - - - - - updateServiceNotification - - - - - - - - - - - - - -
- -
-
-
- -

updateServiceNotification

- -

A service message for the user.

-

The app must show the message to the user upon receiving this update. In case the popup parameter was passed, the text message must be displayed in a popup alert immediately upon receipt. It is recommended to handle the text as you would an ordinary message in terms of highlighting links, etc. The message must also be stored locally as part of the message history with the user id 777000 (Telegram Notifications).

-

- -
-
updateServiceNotification#ebe46819 flags:# popup:flags.0?true inbox_date:flags.1?int type:string message:string media:MessageMedia entities:Vector<MessageEntity> = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
popupflags.0?true(boolTrue) if the message must be displayed in a popup.
inbox_dateflags.1?intWhen was the notification received
The message must also be stored locally as part of the message history with the user id 777000 (Telegram Notifications).
typestringString, identical in format and contents to the type field in API errors. Describes type of service message. It is acceptable to ignore repeated messages of the same type within a short period of time (15 minutes).
messagestringMessage text
mediaMessageMediaMedia content (optional)
entitiesVector<MessageEntity>Message entities for styled text
-

Type

-

Update

-

Related pages

-

Error handling

-

How to handle API return errors correctly.

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateShort.html b/data/core.telegram.org/constructor/updateShort.html deleted file mode 100644 index a12ae23837..0000000000 --- a/data/core.telegram.org/constructor/updateShort.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updateShort - - - - - - - - - - - - - -
- -
-
-
- -

updateShort

- -

Shortened constructor containing info on one update not requiring auxiliary data

-

- -
-
updateShort#78d4dec1 update:Update date:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
updateUpdateUpdate
dateintDate of event
-

Type

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateShortMessage.html b/data/core.telegram.org/constructor/updateShortMessage.html deleted file mode 100644 index 8221fbc669..0000000000 --- a/data/core.telegram.org/constructor/updateShortMessage.html +++ /dev/null @@ -1,229 +0,0 @@ - - - - - updateShortMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateShortMessage

- -

Info about a message sent to (received from) another user

-

- -
-
updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
outflags.1?trueWhether the message is outgoing
mentionedflags.4?trueWhether we were mentioned in the message
media_unreadflags.5?trueWhether there are some unread mentions in this message
silentflags.13?trueIf true, the message is a silent message, no notifications should be triggered
idintThe message ID
user_idlongThe ID of the sender (if outgoing will be the ID of the destination) of the message
messagestringThe message
ptsintPTS
pts_countintPTS count
dateintdate
fwd_fromflags.2?MessageFwdHeaderInfo about a forwarded message
via_bot_idflags.11?longInfo about the inline bot used to generate this message
reply_toflags.3?MessageReplyHeaderReply and thread information
entitiesflags.7?Vector<MessageEntity>Entities for styled text
ttl_periodflags.25?intTime To Live of the message, once message.date+message.ttl_period === time(), the message will be deleted on the server, and must be deleted locally as well.
-

Type

-

Updates

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateShortSentMessage.html b/data/core.telegram.org/constructor/updateShortSentMessage.html deleted file mode 100644 index a3a338533f..0000000000 --- a/data/core.telegram.org/constructor/updateShortSentMessage.html +++ /dev/null @@ -1,192 +0,0 @@ - - - - - updateShortSentMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateShortSentMessage

- -

Shortened constructor containing info on one outgoing message to a contact (the destination chat has to be extracted from the method call that returned this object).

-

- -
-
updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
outflags.1?trueWhether the message is outgoing
idintID of the sent message
ptsintPTS
pts_countintPTS count
dateintdate
mediaflags.9?MessageMediaAttached media
entitiesflags.7?Vector<MessageEntity>Entities for styled text
ttl_periodflags.25?intTime To Live of the message, once message.date+message.ttl_period === time(), the message will be deleted on the server, and must be deleted locally as well.
-

Type

-

Updates

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateStickerSets.html b/data/core.telegram.org/constructor/updateStickerSets.html deleted file mode 100644 index 3e7e2547b4..0000000000 --- a/data/core.telegram.org/constructor/updateStickerSets.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - updateStickerSets - - - - - - - - - - - - - -
- -
-
-
- -

updateStickerSets

- -

Installed stickersets have changed, the client should refetch them using messages.getAllStickers

-

- -
-
updateStickerSets#43ae3dec = Update;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateStickerSetsOrder.html b/data/core.telegram.org/constructor/updateStickerSetsOrder.html deleted file mode 100644 index 776a9c9fe7..0000000000 --- a/data/core.telegram.org/constructor/updateStickerSetsOrder.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateStickerSetsOrder - - - - - - - - - - - - - -
- -
-
-
- -

updateStickerSetsOrder

- -

The order of stickersets was changed

-

- -
-
updateStickerSetsOrder#bb2d201 flags:# masks:flags.0?true order:Vector<long> = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
masksflags.0?trueWhether the updated stickers are mask stickers
orderVector<long>New sticker order by sticker ID
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateTheme.html b/data/core.telegram.org/constructor/updateTheme.html deleted file mode 100644 index c987d45e7d..0000000000 --- a/data/core.telegram.org/constructor/updateTheme.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateTheme - - - - - - - - - - - - - -
- -
-
-
- -

updateTheme

- -

A cloud theme was updated

-

- -
-
updateTheme#8216fba3 theme:Theme = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
themeThemeTheme
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateUserBlocked.html b/data/core.telegram.org/constructor/updateUserBlocked.html deleted file mode 100644 index 0890b946fd..0000000000 --- a/data/core.telegram.org/constructor/updateUserBlocked.html +++ /dev/null @@ -1,159 +0,0 @@ - - - - - updateUserBlocked - - - - - - - - - - - - - -
- -
-
-
- -

updateUserBlocked

- -

User was added to the blacklist (method contacts.block) or removed from the blacklist (method contacts.unblock).

-

- -
-
Constructor schema is available as of layer 119. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idintUser id
blockedBool(boolTrue) if the the user is blocked
-

Type

-

Update

-

Related pages

-

boolTrue

-

The constructor can be interpreted as a booleantrue value.

-

contacts.block

-

Adds the user to the blacklist.

-

contacts.unblock

-

Deletes the user from the blacklist.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateUserName.html b/data/core.telegram.org/constructor/updateUserName.html deleted file mode 100644 index 067c54060a..0000000000 --- a/data/core.telegram.org/constructor/updateUserName.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - updateUserName - - - - - - - - - - - - - -
- -
-
-
- -

updateUserName

- -

Changes the user's first name, last name and username.

-

- -
-
updateUserName#c3f202e0 user_id:long first_name:string last_name:string username:string = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser identifier
first_namestringNew first name. Corresponds to the new value of real_first_name field of the userFull constructor.
last_namestringNew last name. Corresponds to the new value of real_last_name field of the userFull constructor.
usernamestringNew username.
Parameter added in Layer 18.
-

Type

-

Update

-

Related pages

-

userFull

-

Extended user info

-

Layers

-

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateUserPhone.html b/data/core.telegram.org/constructor/updateUserPhone.html deleted file mode 100644 index 77c322cd7d..0000000000 --- a/data/core.telegram.org/constructor/updateUserPhone.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updateUserPhone - - - - - - - - - - - - - -
- -
-
-
- -

updateUserPhone

- -

A user's phone number was changed

-

- -
-
updateUserPhone#5492a13 user_id:long phone:string = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser ID
phonestringNew phone number
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateUserPhoto.html b/data/core.telegram.org/constructor/updateUserPhoto.html deleted file mode 100644 index 7780786a47..0000000000 --- a/data/core.telegram.org/constructor/updateUserPhoto.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - updateUserPhoto - - - - - - - - - - - - - -
- -
-
-
- -

updateUserPhoto

- -

Change of contact's profile photo.

-

- -
-
updateUserPhoto#f227868c user_id:long date:int photo:UserProfilePhoto previous:Bool = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser identifier
dateintDate of photo update.
photoUserProfilePhotoNew profile photo
previousBool(boolTrue), if one of the previously used photos is set a profile photo.
-

Type

-

Update

-

Related pages

-

boolTrue

-

The constructor can be interpreted as a booleantrue value.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateUserStatus.html b/data/core.telegram.org/constructor/updateUserStatus.html deleted file mode 100644 index 0cc8b39514..0000000000 --- a/data/core.telegram.org/constructor/updateUserStatus.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updateUserStatus - - - - - - - - - - - - - -
- -
-
-
- -

updateUserStatus

- -

Contact status update.

-

- -
-
updateUserStatus#e5bdf8de user_id:long status:UserStatus = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser identifier
statusUserStatusNew status
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateUserTyping.html b/data/core.telegram.org/constructor/updateUserTyping.html deleted file mode 100644 index 4abd9a1760..0000000000 --- a/data/core.telegram.org/constructor/updateUserTyping.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - updateUserTyping - - - - - - - - - - - - - -
- -
-
-
- -

updateUserTyping

- -

The user is preparing a message; typing, recording, uploading, etc. This update is valid for 6 seconds. If no repeated update received after 6 seconds, it should be considered that the user stopped doing whatever he's been doing.

-

- -
-
updateUserTyping#c01e857f user_id:long action:SendMessageAction = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser id
actionSendMessageActionAction type
Param added in Layer 17.
-

Type

-

Update

-

Related pages

-

Layers

-

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updateWebPage.html b/data/core.telegram.org/constructor/updateWebPage.html deleted file mode 100644 index 516f3dfcf9..0000000000 --- a/data/core.telegram.org/constructor/updateWebPage.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - updateWebPage - - - - - - - - - - - - - -
- -
-
-
- -

updateWebPage

- -

An instant view webpage preview was generated

-

- -
-
updateWebPage#7f891213 webpage:WebPage pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
webpageWebPageWebpage preview
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updates.channelDifference b/data/core.telegram.org/constructor/updates.channelDifference deleted file mode 100644 index 5cfe96f6c3..0000000000 --- a/data/core.telegram.org/constructor/updates.channelDifference +++ /dev/null @@ -1,185 +0,0 @@ - - - - - updates.channelDifference - - - - - - - - - - - - - -
- -
-
-
- -

updates.channelDifference

- -

The new updates

-

- -
-
updates.channelDifference#2064674e flags:# final:flags.0?true pts:int timeout:flags.1?int new_messages:Vector<Message> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
finalflags.0?trueWhether there are more updates to be fetched using getDifference, starting from the provided pts
ptsintThe PTS from which to start getting updates the next time
timeoutflags.1?intClients are supposed to refetch the channel difference after timeout seconds have elapsed
new_messagesVector<Message>New messages
other_updatesVector<Update>Other updates
chatsVector<Chat>Chats
usersVector<User>Users
-

Type

-

updates.ChannelDifference

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updates.channelDifferenceEmpty b/data/core.telegram.org/constructor/updates.channelDifferenceEmpty deleted file mode 100644 index 4d921e9a5c..0000000000 --- a/data/core.telegram.org/constructor/updates.channelDifferenceEmpty +++ /dev/null @@ -1,165 +0,0 @@ - - - - - updates.channelDifferenceEmpty - - - - - - - - - - - - - -
- -
-
-
- -

updates.channelDifferenceEmpty

- -

There are no new updates

-

- -
-
updates.channelDifferenceEmpty#3e11affb flags:# final:flags.0?true pts:int timeout:flags.1?int = updates.ChannelDifference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
finalflags.0?trueWhether there are more updates that must be fetched (always false)
ptsintThe latest PTS
timeoutflags.1?intClients are supposed to refetch the channel difference after timeout seconds have elapsed
-

Type

-

updates.ChannelDifference

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updates.channelDifferenceTooLong b/data/core.telegram.org/constructor/updates.channelDifferenceTooLong deleted file mode 100644 index 82b6ea7081..0000000000 --- a/data/core.telegram.org/constructor/updates.channelDifferenceTooLong +++ /dev/null @@ -1,190 +0,0 @@ - - - - - updates.channelDifferenceTooLong - - - - - - - - - - - - - -
- -
-
-
- -

updates.channelDifferenceTooLong

- -

The provided pts + limit < remote pts. Simply, there are too many updates to be fetched (more than limit), the client has to resolve the update gap in one of the following ways:

-
    -
  1. Delete all known messages in the chat, begin from scratch by refetching all messages manually with getHistory. It is easy to implement, but suddenly disappearing messages looks awful for the user.
  2. -
  3. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to getHistory. It looks much smoothly for the user, they will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of getHistory and getMessages must be used to update state of deleted and edited messages left in the memory.
  4. -
  5. Save all messages loaded in the memory and stored in the database without saving that some messages form continuous ranges. Messages in the database will be excluded from results of getChatHistory and searchChatMessages after application restart and will be available only through getMessage. Every message should still be checked using getHistory. It has more disadvantages over 2) than advantages.
  6. -
  7. Save all messages with saving all data about continuous message ranges. Messages from the database may be used as results of getChatHistory and (if implemented continuous ranges support for searching shared media) searchChatMessages. The messages should still be lazily checked using getHistory, but they are still available offline. It is the best way for gaps support, but it is pretty hard to implement correctly. It should be also noted that some messages like live location messages shouldn't be deleted.
  8. -
-

- -
-
updates.channelDifferenceTooLong#a4bcc6fe flags:# final:flags.0?true timeout:flags.1?int dialog:Dialog messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
finalflags.0?trueWhether there are more updates that must be fetched (always false)
timeoutflags.1?intClients are supposed to refetch the channel difference after timeout seconds have elapsed
dialogDialogDialog containing the latest PTS that can be used to reset the channel state
messagesVector<Message>The latest messages
chatsVector<Chat>Chats from messages
usersVector<User>Users from messages
-

Type

-

updates.ChannelDifference

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

messages.getHistory

-

Gets back the conversation history with one interlocutor / within a chat

-

messages.getMessages

-

Returns the list of messages by their IDs.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updates.difference b/data/core.telegram.org/constructor/updates.difference deleted file mode 100644 index fe42f002ed..0000000000 --- a/data/core.telegram.org/constructor/updates.difference +++ /dev/null @@ -1,172 +0,0 @@ - - - - - updates.difference - - - - - - - - - - - - - -
- -
-
-
- -

updates.difference

- -

Full list of occurred events.

-

- -
-
updates.difference#f49ca0 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> state:updates.State = updates.Difference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
new_messagesVector<Message>List of new messages
new_encrypted_messagesVector<EncryptedMessage>List of new encrypted secret chat messages
other_updatesVector<Update>List of updates
chatsVector<Chat>List of chats mentioned in events
usersVector<User>List of users mentioned in events
stateupdates.StateCurrent state
-

Type

-

updates.Difference

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updates.differenceEmpty b/data/core.telegram.org/constructor/updates.differenceEmpty deleted file mode 100644 index 9035d2548b..0000000000 --- a/data/core.telegram.org/constructor/updates.differenceEmpty +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updates.differenceEmpty - - - - - - - - - - - - - -
- -
-
-
- -

updates.differenceEmpty

- -

No events.

-

- -
-
updates.differenceEmpty#5d75a138 date:int seq:int = updates.Difference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
dateintCurrent date
seqintNumber of sent updates
-

Type

-

updates.Difference

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updates.differenceSlice b/data/core.telegram.org/constructor/updates.differenceSlice deleted file mode 100644 index 836ba3aa41..0000000000 --- a/data/core.telegram.org/constructor/updates.differenceSlice +++ /dev/null @@ -1,175 +0,0 @@ - - - - - updates.differenceSlice - - - - - - - - - - - - - -
- -
-
-
- -

updates.differenceSlice

- -

Incomplete list of occurred events.

-

- -
-
updates.differenceSlice#a8fb1981 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> intermediate_state:updates.State = updates.Difference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
new_messagesVector<Message>List of new messgaes
new_encrypted_messagesVector<EncryptedMessage>New messages from the encrypted event sequence
other_updatesVector<Update>List of updates
chatsVector<Chat>List of chats mentioned in events
usersVector<User>List of users mentioned in events
intermediate_stateupdates.StateIntermediary state
-

Type

-

updates.Difference

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updates.differenceTooLong b/data/core.telegram.org/constructor/updates.differenceTooLong deleted file mode 100644 index 3217397acc..0000000000 --- a/data/core.telegram.org/constructor/updates.differenceTooLong +++ /dev/null @@ -1,150 +0,0 @@ - - - - - updates.differenceTooLong - - - - - - - - - - - - - -
- -
-
-
- -

updates.differenceTooLong

- -

The difference is too long, and the specified state must be used to refetch updates.

-

- -
-
updates.differenceTooLong#4afe8f6d pts:int = updates.Difference;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
ptsintThe new state to use.
-

Type

-

updates.Difference

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updates.html b/data/core.telegram.org/constructor/updates.html deleted file mode 100644 index 19eaddce47..0000000000 --- a/data/core.telegram.org/constructor/updates.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Updates - - - - - - - - - - - - - -
- -
-
-
- -

Updates

- -

Full constructor of updates

-

- -
-
updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
updatesVector<Update>List of updates
usersVector<User>List of users mentioned in updates
chatsVector<Chat>List of chats mentioned in updates
dateintCurrent date
seqintTotal number of sent updates
-

Type

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updates.state b/data/core.telegram.org/constructor/updates.state deleted file mode 100644 index 0cb5396b9d..0000000000 --- a/data/core.telegram.org/constructor/updates.state +++ /dev/null @@ -1,172 +0,0 @@ - - - - - updates.state - - - - - - - - - - - - - -
- -
-
-
- -

updates.state

- -

Updates state.

-

- -
-
updates.state#a56c2a3e pts:int qts:int date:int seq:int unread_count:int = updates.State;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
ptsintNumber of events occured in a text box
qtsintPosition in a sequence of updates in secret chats. For further detailes refer to article secret chats
Parameter was added in eigth layer.
dateintDate of condition
seqintNumber of sent updates
unread_countintNumber of unread messages
-

Type

-

updates.State

-

Related pages

-

End-to-End Encryption, Secret Chats

-

New feature for end-to-end-encrypted messaging.

-

Layers

-

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatesCombined.html b/data/core.telegram.org/constructor/updatesCombined.html deleted file mode 100644 index 5492a443a0..0000000000 --- a/data/core.telegram.org/constructor/updatesCombined.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - updatesCombined - - - - - - - - - - - - - -
- -
-
-
- -

updatesCombined

- -

Constructor for a group of updates.

-

- -
-
updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
updatesVector<Update>List of updates
usersVector<User>List of users mentioned in updates
chatsVector<Chat>List of chats mentioned in updates
dateintCurrent date
seq_startintValue seq for the earliest update in a group
seqintValue seq for the latest update in a group
-

Type

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/updatesTooLong.html b/data/core.telegram.org/constructor/updatesTooLong.html deleted file mode 100644 index 1c23cb9265..0000000000 --- a/data/core.telegram.org/constructor/updatesTooLong.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - updatesTooLong - - - - - - - - - - - - - -
- -
-
-
- -

updatesTooLong

- -

Too many updates, it is necessary to execute updates.getDifference.

-

- -
-
updatesTooLong#e317af7e = Updates;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Updates

-

Related pages

-

updates.getDifference

-

Get new updates.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/upload.cdnFile b/data/core.telegram.org/constructor/upload.cdnFile deleted file mode 100644 index b50c25186c..0000000000 --- a/data/core.telegram.org/constructor/upload.cdnFile +++ /dev/null @@ -1,149 +0,0 @@ - - - - - upload.cdnFile - - - - - - - - - - - - - -
- -
-
-
- -

upload.cdnFile

- -

Represent a chunk of a CDN file.

-

- -
-
upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
bytesbytesThe data
-

Type

-

upload.CdnFile

-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/upload.cdnFileReuploadNeeded b/data/core.telegram.org/constructor/upload.cdnFileReuploadNeeded deleted file mode 100644 index 369787176d..0000000000 --- a/data/core.telegram.org/constructor/upload.cdnFileReuploadNeeded +++ /dev/null @@ -1,149 +0,0 @@ - - - - - upload.cdnFileReuploadNeeded - - - - - - - - - - - - - -
- -
-
-
- -

upload.cdnFileReuploadNeeded

- -

The file was cleared from the temporary RAM cache of the CDN and has to be reuploaded.

-

- -
-
upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
request_tokenbytesRequest token (see CDN)
-

Type

-

upload.CdnFile

-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/upload.file b/data/core.telegram.org/constructor/upload.file deleted file mode 100644 index aff8630cd4..0000000000 --- a/data/core.telegram.org/constructor/upload.file +++ /dev/null @@ -1,157 +0,0 @@ - - - - - upload.file - - - - - - - - - - - - - -
- -
-
-
- -

upload.file

- -

File content.

-

- -
-
upload.file#96a18d5 type:storage.FileType mtime:int bytes:bytes = upload.File;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typestorage.FileTypeFile type
mtimeintModification type
bytesbytesBinary data, file content
-

Type

-

upload.File

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/upload.fileCdnRedirect b/data/core.telegram.org/constructor/upload.fileCdnRedirect deleted file mode 100644 index cf7db284bd..0000000000 --- a/data/core.telegram.org/constructor/upload.fileCdnRedirect +++ /dev/null @@ -1,169 +0,0 @@ - - - - - upload.fileCdnRedirect - - - - - - - - - - - - - -
- -
-
-
- -

upload.fileCdnRedirect

- -

The file must be downloaded from a CDN DC.

-

- -
-
upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
dc_idintCDN DC ID
file_tokenbytesFile token (see CDN files)
encryption_keybytesEncryption key (see CDN files)
encryption_ivbytesEncryption IV (see CDN files)
file_hashesVector<FileHash>File hashes (see CDN files)
-

Type

-

upload.File

-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/upload.webFile b/data/core.telegram.org/constructor/upload.webFile deleted file mode 100644 index 0e2ae5132c..0000000000 --- a/data/core.telegram.org/constructor/upload.webFile +++ /dev/null @@ -1,170 +0,0 @@ - - - - - upload.webFile - - - - - - - - - - - - - -
- -
-
-
- -

upload.webFile

- -

Represents a chunk of an HTTP webfile downloaded through telegram's secure MTProto servers

-

- -
-
upload.webFile#21e753bc size:int mime_type:string file_type:storage.FileType mtime:int bytes:bytes = upload.WebFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
sizeintFile size
mime_typestringMime type
file_typestorage.FileTypeFile type
mtimeintModified time
bytesbytesData
-

Type

-

upload.WebFile

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/urlAuthResultAccepted.html b/data/core.telegram.org/constructor/urlAuthResultAccepted.html deleted file mode 100644 index 3f41ade644..0000000000 --- a/data/core.telegram.org/constructor/urlAuthResultAccepted.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - urlAuthResultAccepted - - - - - - - - - - - - - -
- -
-
-
- -

urlAuthResultAccepted

- -

Details about an accepted authorization request, for more info click here »

-

- -
-
urlAuthResultAccepted#8f8c0e4e url:string = UrlAuthResult;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
urlstringThe URL name of the website on which the user has logged in.
-

Type

-

UrlAuthResult

-

Related pages

-

Seamless Telegram Login

-

Handle Seamless Telegram Login URL authorization requests.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/urlAuthResultDefault.html b/data/core.telegram.org/constructor/urlAuthResultDefault.html deleted file mode 100644 index ec78328aee..0000000000 --- a/data/core.telegram.org/constructor/urlAuthResultDefault.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - urlAuthResultDefault - - - - - - - - - - - - - -
- -
-
-
- -

urlAuthResultDefault

- -

Details about an accepted authorization request, for more info click here »

-

- -
-
urlAuthResultDefault#a9d6db1f = UrlAuthResult;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

UrlAuthResult

-

Related pages

-

Seamless Telegram Login

-

Handle Seamless Telegram Login URL authorization requests.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/urlAuthResultRequest.html b/data/core.telegram.org/constructor/urlAuthResultRequest.html deleted file mode 100644 index a2bf6d57bd..0000000000 --- a/data/core.telegram.org/constructor/urlAuthResultRequest.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - urlAuthResultRequest - - - - - - - - - - - - - -
- -
-
-
- -

urlAuthResultRequest

- -

Details about the authorization request, for more info click here »

-

- -
-
urlAuthResultRequest#92d33a0e flags:# request_write_access:flags.0?true bot:User domain:string = UrlAuthResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
request_write_accessflags.0?trueWhether the bot would like to send messages to the user
botUserUsername of a bot, which will be used for user authorization. If not specified, the current bot's username will be assumed. The url's domain must be the same as the domain linked with the bot. See Linking your domain to the bot for more details.
domainstringThe domain name of the website on which the user will log in.
-

Type

-

UrlAuthResult

-

Related pages

-

Seamless Telegram Login

-

Handle Seamless Telegram Login URL authorization requests.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/user.html b/data/core.telegram.org/constructor/user.html deleted file mode 100644 index b6d8f4eddb..0000000000 --- a/data/core.telegram.org/constructor/user.html +++ /dev/null @@ -1,287 +0,0 @@ - - - - - user - - - - - - - - - - - - - -
- -
-
-
- -

user

- -

Indicates info about a certain user

-

- -
-
user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
selfflags.10?trueWhether this user indicates the currently logged in user
contactflags.11?trueWhether this user is a contact
mutual_contactflags.12?trueWhether this user is a mutual contact
deletedflags.13?trueWhether the account of this user was deleted
botflags.14?trueIs this user a bot?
bot_chat_historyflags.15?trueCan the bot see all messages in groups?
bot_nochatsflags.16?trueCan the bot be added to groups?
verifiedflags.17?trueWhether this user is verified
restrictedflags.18?trueAccess to this user must be restricted for the reason specified in restriction_reason
minflags.20?trueSee min
bot_inline_geoflags.21?trueWhether the bot can request our geolocation in inline mode
supportflags.23?trueWhether this is an official support user
scamflags.24?trueThis may be a scam user
apply_min_photoflags.25?trueIf set, the profile picture for this user should be refetched
fakeflags.26?trueIf set, this user was reported by many users as a fake or scam user: be careful when interacting with them.
idlongID of the user
access_hashflags.0?longAccess hash of the user
first_nameflags.1?stringFirst name
last_nameflags.2?stringLast name
usernameflags.3?stringUsername
phoneflags.4?stringPhone number
photoflags.5?UserProfilePhotoProfile picture of user
statusflags.6?UserStatusOnline status of user
bot_info_versionflags.14?intVersion of the bot_info field in userFull, incremented every time it changes
restriction_reasonflags.18?Vector<RestrictionReason>Contains the reason why access to this user must be restricted.
bot_inline_placeholderflags.19?stringInline placeholder for this inline bot
lang_codeflags.22?stringLanguage code of the user
-

Type

-

User

-

Related pages

-

Min constructors

-

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

-

userFull

-

Extended user info

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/userFull.html b/data/core.telegram.org/constructor/userFull.html deleted file mode 100644 index 2ea79bc0e1..0000000000 --- a/data/core.telegram.org/constructor/userFull.html +++ /dev/null @@ -1,239 +0,0 @@ - - - - - userFull - - - - - - - - - - - - - -
- -
-
-
- -

userFull

- -

Extended user info

-

- -
-
userFull#d697ff05 flags:# blocked:flags.0?true phone_calls_available:flags.4?true phone_calls_private:flags.5?true can_pin_message:flags.7?true has_scheduled:flags.12?true video_calls_available:flags.13?true user:User about:flags.1?string settings:PeerSettings profile_photo:flags.2?Photo notify_settings:PeerNotifySettings bot_info:flags.3?BotInfo pinned_msg_id:flags.6?int common_chats_count:int folder_id:flags.11?int ttl_period:flags.14?int theme_emoticon:flags.15?string = UserFull;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
blockedflags.0?trueWhether you have blocked this user
phone_calls_availableflags.4?trueWhether this user can make VoIP calls
phone_calls_privateflags.5?trueWhether this user's privacy settings allow you to call him
can_pin_messageflags.7?trueWhether you can pin messages in the chat with this user, you can do this only for a chat with yourself
has_scheduledflags.12?trueWhether scheduled messages are available
video_calls_availableflags.13?trueWhether the user can receive video calls
userUserRemaining user info
aboutflags.1?stringBio of the user
settingsPeerSettingsPeer settings
profile_photoflags.2?PhotoProfile photo
notify_settingsPeerNotifySettingsNotification settings
bot_infoflags.3?BotInfoFor bots, info about the bot (bot commands, etc)
pinned_msg_idflags.6?intMessage ID of the last pinned message
common_chats_countintChats in common with this user
folder_idflags.11?intPeer folder ID, for more info click here
ttl_periodflags.14?intTime To Live of all messages in this chat; once a message is this many seconds old, it must be deleted.
theme_emoticonflags.15?stringEmoji associated with chat theme
-

Type

-

UserFull

-

Related pages

-

Scheduled messages

-

Telegram allows scheduling messages

-

Pinned messages

-

Telegram allows pinning multiple messages on top of a specific chat.

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/userProfilePhoto.html b/data/core.telegram.org/constructor/userProfilePhoto.html deleted file mode 100644 index d74ed77ce8..0000000000 --- a/data/core.telegram.org/constructor/userProfilePhoto.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - userProfilePhoto - - - - - - - - - - - - - -
- -
-
-
- -

userProfilePhoto

- -

User profile photo.

-

- -
-
userProfilePhoto#82d1f706 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = UserProfilePhoto;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
has_videoflags.0?trueWhether an animated profile picture is available for this user
photo_idlongIdentifier of the respective photo
Parameter added in Layer 2
stripped_thumbflags.1?bytesStripped thumbnail
dc_idintDC ID where the photo is stored
-

Type

-

UserProfilePhoto

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

-

Layers

-

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/userProfilePhotoEmpty.html b/data/core.telegram.org/constructor/userProfilePhotoEmpty.html deleted file mode 100644 index cf1ead2630..0000000000 --- a/data/core.telegram.org/constructor/userProfilePhotoEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - userProfilePhotoEmpty - - - - - - - - - - - - - -
- -
-
-
- -

userProfilePhotoEmpty

- -

Profile photo has not been set, or was hidden.

-

- -
-
userProfilePhotoEmpty#4f11bae1 = UserProfilePhoto;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

UserProfilePhoto

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/userStatusEmpty.html b/data/core.telegram.org/constructor/userStatusEmpty.html deleted file mode 100644 index b83f28c2c0..0000000000 --- a/data/core.telegram.org/constructor/userStatusEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - userStatusEmpty - - - - - - - - - - - - - -
- -
-
-
- -

userStatusEmpty

- -

User status has not been set yet.

-

- -
-
userStatusEmpty#9d05049 = UserStatus;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

UserStatus

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/userStatusLastMonth.html b/data/core.telegram.org/constructor/userStatusLastMonth.html deleted file mode 100644 index 04c6f0d8d8..0000000000 --- a/data/core.telegram.org/constructor/userStatusLastMonth.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - userStatusLastMonth - - - - - - - - - - - - - -
- -
-
-
- -

userStatusLastMonth

- -

Online status: last seen last month

-

- -
-
userStatusLastMonth#77ebc742 = UserStatus;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

UserStatus

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/userStatusLastWeek.html b/data/core.telegram.org/constructor/userStatusLastWeek.html deleted file mode 100644 index 69d55d347c..0000000000 --- a/data/core.telegram.org/constructor/userStatusLastWeek.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - userStatusLastWeek - - - - - - - - - - - - - -
- -
-
-
- -

userStatusLastWeek

- -

Online status: last seen last week

-

- -
-
userStatusLastWeek#7bf09fc = UserStatus;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

UserStatus

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/userStatusOffline.html b/data/core.telegram.org/constructor/userStatusOffline.html deleted file mode 100644 index ad3d0401f7..0000000000 --- a/data/core.telegram.org/constructor/userStatusOffline.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - userStatusOffline - - - - - - - - - - - - - -
- -
-
-
- -

userStatusOffline

- -

The user's offline status.

-

- -
-
userStatusOffline#8c703f was_online:int = UserStatus;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
was_onlineintTime the user was last seen online
-

Type

-

UserStatus

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/userStatusOnline.html b/data/core.telegram.org/constructor/userStatusOnline.html deleted file mode 100644 index 4b7f165d9c..0000000000 --- a/data/core.telegram.org/constructor/userStatusOnline.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - userStatusOnline - - - - - - - - - - - - - -
- -
-
-
- -

userStatusOnline

- -

Online status of the user.

-

- -
-
userStatusOnline#edb93949 expires:int = UserStatus;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
expiresintTime to expiration of the current online status
-

Type

-

UserStatus

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/userStatusRecently.html b/data/core.telegram.org/constructor/userStatusRecently.html deleted file mode 100644 index 9910e5a4f7..0000000000 --- a/data/core.telegram.org/constructor/userStatusRecently.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - userStatusRecently - - - - - - - - - - - - - -
- -
-
-
- -

userStatusRecently

- -

Online status: last seen recently

-

- -
-
userStatusRecently#e26f42f1 = UserStatus;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

UserStatus

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/vector.html b/data/core.telegram.org/constructor/vector.html deleted file mode 100644 index 4b7754b27b..0000000000 --- a/data/core.telegram.org/constructor/vector.html +++ /dev/null @@ -1,134 +0,0 @@ - - - - - vector - - - - - - - - - - - - - -
- -
-
-
- -

vector

- -

A universal vector constructor.

-

- -
-
vector#1cb5c415 {t:Type} # [ t ] = Vector t;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Vector t

-

Params additional

-

For serialization write the constructor id 0x1cb5c415:int, then the number of vector elements - #:int, then, one after another, the # of the elements of the type t, that was implicitly passed to the constructor.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/videoSize.html b/data/core.telegram.org/constructor/videoSize.html deleted file mode 100644 index 03edb72674..0000000000 --- a/data/core.telegram.org/constructor/videoSize.html +++ /dev/null @@ -1,175 +0,0 @@ - - - - - videoSize - - - - - - - - - - - - - -
- -
-
-
- -

videoSize

- -

Animated profile picture in MPEG4 format

-

- -
-
videoSize#de33b094 flags:# type:string w:int h:int size:int video_start_ts:flags.0?double = VideoSize;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
typestringu for animated profile pictures, and v for trimmed and downscaled video previews
wintVideo width
hintVideo height
sizeintFile size
video_start_tsflags.0?doubleTimestamp that should be shown as static preview to the user (seconds)
-

Type

-

VideoSize

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/wallPaper.html b/data/core.telegram.org/constructor/wallPaper.html deleted file mode 100644 index 309380f275..0000000000 --- a/data/core.telegram.org/constructor/wallPaper.html +++ /dev/null @@ -1,192 +0,0 @@ - - - - - wallPaper - - - - - - - - - - - - - -
- -
-
-
- -

wallPaper

- -

Wallpaper settings.

-

- -
-
wallPaper#a437c3ed id:long flags:# creator:flags.0?true default:flags.1?true pattern:flags.3?true dark:flags.4?true access_hash:long slug:string document:Document settings:flags.2?WallPaperSettings = WallPaper;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongIdentifier
flags#Flags, see TL conditional fields
creatorflags.0?trueCreator of the wallpaper
defaultflags.1?trueWhether this is the default wallpaper
patternflags.3?truePattern
darkflags.4?trueDark mode
access_hashlongAccess hash
slugstringUnique wallpaper ID
documentDocumentThe actual wallpaper
settingsflags.2?WallPaperSettingsWallpaper settings
-

Type

-

WallPaper

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/wallPaperNoFile.html b/data/core.telegram.org/constructor/wallPaperNoFile.html deleted file mode 100644 index dd043811ee..0000000000 --- a/data/core.telegram.org/constructor/wallPaperNoFile.html +++ /dev/null @@ -1,171 +0,0 @@ - - - - - wallPaperNoFile - - - - - - - - - - - - - -
- -
-
-
- -

wallPaperNoFile

- -

Wallpaper with no file access hash, used for example when deleting (unsave=true) wallpapers using account.saveWallPaper, specifying just the wallpaper ID.
-Also used for some default wallpapers which contain only colours.

-

- -
-
wallPaperNoFile#e0804116 id:long flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongWallpaper ID
flags#Flags, see TL conditional fields
defaultflags.1?trueWhether this is the default wallpaper
darkflags.4?trueDark mode
settingsflags.2?WallPaperSettingsWallpaper settings
-

Type

-

WallPaper

-

Related pages

-

account.saveWallPaper

-

Install/uninstall wallpaper

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/wallPaperSettings.html b/data/core.telegram.org/constructor/wallPaperSettings.html deleted file mode 100644 index 175e5095ba..0000000000 --- a/data/core.telegram.org/constructor/wallPaperSettings.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - wallPaperSettings - - - - - - - - - - - - - -
- -
-
-
- -

wallPaperSettings

- -

Wallpaper settings

-

- -
-
wallPaperSettings#1dc1bca4 flags:# blur:flags.1?true motion:flags.2?true background_color:flags.0?int second_background_color:flags.4?int third_background_color:flags.5?int fourth_background_color:flags.6?int intensity:flags.3?int rotation:flags.4?int = WallPaperSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
blurflags.1?trueIf set, the wallpaper must be downscaled to fit in 450x450 square and then box-blurred with radius 12
motionflags.2?trueIf set, the background needs to be slightly moved when device is rotated
background_colorflags.0?intIf set, a PNG pattern is to be combined with the color chosen by the user: the main color of the background in RGB24 format
second_background_colorflags.4?intIf set, a PNG pattern is to be combined with the first and second background colors (RGB24 format) in a top-bottom gradient
third_background_colorflags.5?intIf set, a PNG pattern is to be combined with the first, second and third background colors (RGB24 format) in a freeform gradient
fourth_background_colorflags.6?intIf set, a PNG pattern is to be combined with the first, second, third and fourth background colors (RGB24 format) in a freeform gradient
intensityflags.3?intIntensity of the pattern when it is shown above the main background color, 0-100
rotationflags.4?intClockwise rotation angle of the gradient, in degrees; 0-359. Should be always divisible by 45
-

Type

-

WallPaperSettings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/wallPaperSolid.html b/data/core.telegram.org/constructor/wallPaperSolid.html deleted file mode 100644 index 435ebb5bc5..0000000000 --- a/data/core.telegram.org/constructor/wallPaperSolid.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - wallPaperSolid - - - - - - - - - - - - - -
- -
-
-
- -

wallPaperSolid

- -

One-color background wallpaper (no image).

-

- -
-
Constructor schema is available as of layer 93. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idintIdentifier
titlestringName
bg_colorintBackground color (RGB)
colorintBasic background color (RGB)
-

Type

-

WallPaper

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/webAuthorization.html b/data/core.telegram.org/constructor/webAuthorization.html deleted file mode 100644 index f90b8e5141..0000000000 --- a/data/core.telegram.org/constructor/webAuthorization.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - webAuthorization - - - - - - - - - - - - - -
- -
-
-
- -

webAuthorization

- -

Represents a bot logged in using the Telegram login widget

-

- -
-
webAuthorization#a6f8f452 hash:long bot_id:long domain:string browser:string platform:string date_created:int date_active:int ip:string region:string = WebAuthorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashlongAuthorization hash
bot_idlongBot ID
domainstringThe domain name of the website on which the user has logged in.
browserstringBrowser user-agent
platformstringPlatform
date_createdintWhen was the web session created
date_activeintWhen was the web session last active
ipstringIP address
regionstringRegion, determined from IP address
-

Type

-

WebAuthorization

-

Related pages

-

Telegram Login Widget

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/webDocument.html b/data/core.telegram.org/constructor/webDocument.html deleted file mode 100644 index 6f07616c6b..0000000000 --- a/data/core.telegram.org/constructor/webDocument.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - webDocument - - - - - - - - - - - - - -
- -
-
-
- -

webDocument

- -

Remote document

-

- -
-
webDocument#1c570ed1 url:string access_hash:long size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringDocument URL
access_hashlongAccess hash
sizeintFile size
mime_typestringMIME type
attributesVector<DocumentAttribute>Attributes for media types
-

Type

-

WebDocument

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/webPage.html b/data/core.telegram.org/constructor/webPage.html deleted file mode 100644 index 2278dac240..0000000000 --- a/data/core.telegram.org/constructor/webPage.html +++ /dev/null @@ -1,240 +0,0 @@ - - - - - webPage - - - - - - - - - - - - - -
- -
-
-
- -

webPage

- -

Webpage preview

-

- -
-
webPage#e89c45b2 flags:# id:long url:string display_url:string hash:int type:flags.0?string site_name:flags.1?string title:flags.2?string description:flags.3?string photo:flags.4?Photo embed_url:flags.5?string embed_type:flags.5?string embed_width:flags.6?int embed_height:flags.6?int duration:flags.7?int author:flags.8?string document:flags.9?Document cached_page:flags.10?Page attributes:flags.12?Vector<WebPageAttribute> = WebPage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idlongPreview ID
urlstringURL of previewed webpage
display_urlstringWebpage URL to be displayed to the user
hashintHash for pagination, for more info click here
typeflags.0?stringType of the web page. Can be: article, photo, audio, video, document, profile, app, or something else
site_nameflags.1?stringShort name of the site (e.g., Google Docs, App Store)
titleflags.2?stringTitle of the content
descriptionflags.3?stringContent description
photoflags.4?PhotoImage representing the content
embed_urlflags.5?stringURL to show in the embedded preview
embed_typeflags.5?stringMIME type of the embedded preview, (e.g., text/html or video/mp4)
embed_widthflags.6?intWidth of the embedded preview
embed_heightflags.6?intHeight of the embedded preview
durationflags.7?intDuration of the content, in seconds
authorflags.8?stringAuthor of the content
documentflags.9?DocumentPreview of the content as a media file
cached_pageflags.10?PagePage contents in instant view format
attributesflags.12?Vector<WebPageAttribute>Webpage attributes
-

Type

-

WebPage

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/webPageAttributeTheme.html b/data/core.telegram.org/constructor/webPageAttributeTheme.html deleted file mode 100644 index 7d464abca6..0000000000 --- a/data/core.telegram.org/constructor/webPageAttributeTheme.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - webPageAttributeTheme - - - - - - - - - - - - - -
- -
-
-
- -

webPageAttributeTheme

- -

Page theme

-

- -
-
webPageAttributeTheme#54b56617 flags:# documents:flags.0?Vector<Document> settings:flags.1?ThemeSettings = WebPageAttribute;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
documentsflags.0?Vector<Document>Theme files
settingsflags.1?ThemeSettingsTheme settings
-

Type

-

WebPageAttribute

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/webPageEmpty.html b/data/core.telegram.org/constructor/webPageEmpty.html deleted file mode 100644 index 0f77f8fbb5..0000000000 --- a/data/core.telegram.org/constructor/webPageEmpty.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - webPageEmpty - - - - - - - - - - - - - -
- -
-
-
- -

webPageEmpty

- -

No preview is available for the webpage

-

- -
-
webPageEmpty#eb1477e8 id:long = WebPage;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idlongPreview ID
-

Type

-

WebPage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/webPageNotModified.html b/data/core.telegram.org/constructor/webPageNotModified.html deleted file mode 100644 index 1ea6beaf22..0000000000 --- a/data/core.telegram.org/constructor/webPageNotModified.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - webPageNotModified - - - - - - - - - - - - - -
- -
-
-
- -

webPageNotModified

- -

The preview of the webpage hasn't changed

-

- -
-
webPageNotModified#7311ca11 flags:# cached_page_views:flags.0?int = WebPage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
cached_page_viewsflags.0?intPage view count
-

Type

-

WebPage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/constructor/webPagePending.html b/data/core.telegram.org/constructor/webPagePending.html deleted file mode 100644 index f116f7ff33..0000000000 --- a/data/core.telegram.org/constructor/webPagePending.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - webPagePending - - - - - - - - - - - - - -
- -
-
-
- -

webPagePending

- -

A preview of the webpage is currently being generated

-

- -
-
webPagePending#c586da1c id:long date:int = WebPage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongID of preview
dateintWhen was the processing started
-

Type

-

WebPage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/contest300K.html b/data/core.telegram.org/contest300K.html deleted file mode 100644 index 86ddea9c34..0000000000 --- a/data/core.telegram.org/contest300K.html +++ /dev/null @@ -1,237 +0,0 @@ - - - - - Telegram Cracking Contest Description - - - - - - - - - - - - - -
- -
-
-
-
-

Telegram Cracking Contest Description

- -

« Back to Contest Announcement

-
-

The current round of the contest is over. Go to results »

-
-

In this contest you assume the role of a malicious entity in control of Telegram's servers. Your goal is to extract sensitive data (a secret email and password) from a conversation between two peers — Paul and Nick. They are represented by two virtual users that communicate via Secret Chats in Telegram.

-

Paul and Nick are both using clients that perform all the checks from Telegram Security Guidelines and compare their key visualizations over an independent channel as soon as a new Secret Chat is established. If any of these checks fails, they stop accepting messages in that Secret Chat. You control the entire process by sending commands to the Telegram user @CryptoContest, used as an interface for this contest. This enables contestants to try CPA, KPA, MITM and other kinds of active attacks and data tampering.

-

Protocol

-

The protocol used by Paul and Nick to establish Secret Сhats and exchange messages is identical to the one used for Secret Chats in Telegram. Since we assume that the attacker is already in full control of the Telegram servers, basic MTProto encryption is bypassed altogether. In order to further simplify the task for contestants, we have removed irrelevant parameters, such as user_id and random_id.

-

The following TL scheme is used to establish Secret Chats in this contest:

-
contest.dhConfig#01e00a51 g:int p:64*[int] random:64*[int] = contest.DhConfig;
-contest.requestEncryption#3a73a74c g_a:64*[int] = contest.Message;
-contest.acceptEncryption#068e4342 g_b:64*[int] fingerprint:int = contest.Message;
-contest.encryptedMessage#11a6d4b1 id:long message:string = contest.Message;
----functions---
-contest.getDhConfig#369ee1a6 = contest.DhConfig;
-

For exchange of encrypted messages (see documentation), the up-to-date layer 17 scheme with sequence numbers is used, but with plain text message support only.

-

Each plaintext message is first created as a layer 17 decryptedMessage, then embedded in a decryptedMessageLayer and encrypted as explained in the Secret Chat documentation. For the purpose of this contest, it is the result of this encryption (ciphertext) that is exchanged between the parties.

-

Notice that sending messages in an actual Telegram Secret Chat involves further embedding of that ciphertext into an API call and an additional layer of MTProto encryption for client-server interaction. This step is omitted here, since we assume the attacker to be in control of the Telegram servers, not just of the communication lines between the clients and Telegram servers.

-

Interface

-

To access the interface, find the Telegram user @CryptoContest using the Global Search by username in any of the Telegram apps. This is a special bot we created for this contest. You can control communication between Paul and Nick by sending particularly formed text messages to this bot and processing automatically generated answers to these messages (you may find the unofficial Linux CLI convenient for mass automated queries).

-

You can create as many parallel Secret Chats between Paul and Nick as you like using the bot — each of them will have a separate session_id. All data is represented in hexadecimal format, with the exception of the session_id.

-

Commands

-

Below, A stands for the creator of the Secret Chat, B stands for the second party, S — the Telegram Server.

-

Each Secret Chat session in this contest is divided in two phases:

- -
1. Creating a Secret Chat
-

In order to create a new Secret Chat, six messages need to be exchanged:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
SourceDestinationMessage
AScontest.getDhConfig
SAcontest.DhConfig
ABcontest.requestEncryption
BScontest.getDhConfig
SBcontest.DhConfig
BAcontest.acceptEncryption
-

To create a Secret Chat in this contest:

-
    -
  • Send the START command to the user @CryptoContest in Telegram. You'll get the getDhConfig query, sent by A to the Server, and the answer that the server would normally send to A. You shall also receive the new session_id as the first 32-bit integer. All further messages related to this particular session (Secret Chat instance) must be prefixed with this session_id in decimal form.
  • -
  • After that, use the PASS command to pass the server's answer to A or ANSWER bytes to send a different answer instead. Bytes is represented by a string of an even number of hexadecimal digits. You'll receive the requestEncryption query as the result.
  • -
  • After that, use the PASS command to pass this query to B or ANSWER bytes to arbitrarily change it. You‘ll receive B’s getDhConfig to the server as the result.
  • -
  • As before, you can use either PASS or ANSWER bytes. You'll receive acceptEncryption as the result.
  • -
  • As before, you can use either PASS or ANSWER bytes. You'll receive “Ok” as the result.
  • -
-

You will receive an error text as the result after any of these steps in case the participating clients perceive that something went wrong. This can happen if a security check is failed, or in the case that the first 128 bits of the SHA-1 of the newly created encryption key don‘t match on both parties’ clients when this stage is completed (this corresponds to Paul and Nick comparing the key visualizations for the Secret Chat in their Telegram apps).

-

If you obtain such an error, the session is failed and can no longer be used. You'll have to start new session. Note that the time to complete this phase is limited. Each step should not take longer than one hour, otherwise the Secret Chat will get cancelled.

-

Example:

-
START
-15 a6e19e36 510ae00103000000c71caeb9c6b1c9048e6c522f70f13f73980d40238e3e21c14934d037563d930f48198a0aa7c14058229493d22530f4dbfa336f6e0ac925139543aed44cce7c3720fd51f69458705ac68cd4fe6b6b13abdc9746512969328454f18faf8c595f642477fe96bb2a941d5bcd1d4ac8cc49880708fa9b378e3c4f3a9060bee67cf9a4a4a695811051907e162753b56b0f6b410dba74d8a84b2a14b3144e0ef1284754fd17ed950d5965b4b9dd46582db1178d169c6bc465b0d6ff9ca3928fef5b9ae4e418fc15e83ebea0f87fa9ff5eed70050ded2849f47bf959d956850ce929851f0d8115f635b105ee2e4e15d04b2454bf6f4fadf034b10403119cd8e3b92fcc5b202d33053c2340fd84dd024e8012277e9c6442ad7cd09fe85955c13196e2d32861ad0d8f8139ce5870f1c3563fbff77428632897352abd91cd0a6497a0f64a33d87cd8b53470cf1bc6a052bba7d0121623e9611c0de83ffeb63b7d15831a70187093373cb20df5613bdfab12a54bbc6fff94598d95a8dcdb1374631b021e77c350261bca9ffc16c59b19d3041bee011a20b06fc9806d633b6b9cdd79cbb8b02fe8ef9dde29b6d31d80b030c69d67d6fc4a7edb33ffab532d085796cf3e7635fd42ee72ea24840082186fd40c3c45cf0acef886533d4de7468f88942a662d302928470aa8704529180a6aec2f877398efb91893cc9b549e5123d7269adfe7b6ee
-15 PASS
-15 4ca7733a1a7823b420111d8e86e3fe9a7cff9fc611ce339d6999fc3053973ef6c8276af841b53547fdebdcb057cbad16aff6178be3fb8747889937dec082c984227c974a19232b85ad85ef457521fcf17d5f697a17b7e62952306f0ed086deb1ebcff0c8a32787789fe7afaa4035c2d0e07c10db46c0df6930a1729d3607fb035154e90c02036318862c5a9537e87a55bc656e3fc53db08f41a07f834e4917ebaaace1214409ffb44c5a806a9cb4def209bfb8ab2e59f1cb6257e422f37dfab288170bdc5666e6a63d1b0447a7b935ad3bdac8d53f64278d433b45925c84dc60214473363d57a30e31324d9b3cc42fb56d375aac2d9d1af16331ad3a92b43a9d64e47813
-15 PASS
-15 a6e19e36 510ae00103000000c71caeb9c6b1c9048e6c522f70f13f73980d40238e3e21c14934d037563d930f48198a0aa7c14058229493d22530f4dbfa336f6e0ac925139543aed44cce7c3720fd51f69458705ac68cd4fe6b6b13abdc9746512969328454f18faf8c595f642477fe96bb2a941d5bcd1d4ac8cc49880708fa9b378e3c4f3a9060bee67cf9a4a4a695811051907e162753b56b0f6b410dba74d8a84b2a14b3144e0ef1284754fd17ed950d5965b4b9dd46582db1178d169c6bc465b0d6ff9ca3928fef5b9ae4e418fc15e83ebea0f87fa9ff5eed70050ded2849f47bf959d956850ce929851f0d8115f635b105ee2e4e15d04b2454bf6f4fadf034b10403119cd8e3b92fcc5b1ccd9c752428f0bca9ac9060bb85b8f90acb9374cd8d5a03110635f591a18f131cb7cc204407efec0687a8b77ba6c4e6732c35174e79e36aaa7fa6ab685257710e074065961ce1b16d21fed8a83cd95efcc4be7111cd33b5704fe759dfab21fc3e8aaa86d44609dc0b073354f8160c653f4fbde3ae7c28c87c3667e0797fac24b32e5c1a870cd898b2a9c517709bb0b8e4ee875ff857868eb56548e6dc993f198fd78c8a77cf997ed42a15f99a9b6265c7cf9bedc7580a11514047b881f717b233f3570ec21856bd2b9791e4c43b125e9260ac3fd48b9a10de5f9d5080e53d92d194adb796766684d905cca35e691fab0c76d6b5f49242f81eb92fcc8adc5a64
-15 ANSWER 510ae00103000000c71caeb9c6b1c9048e6c522f70f13f73980d40238e3e21c14934d037563d930f48198a0aa7c14058229493d22530f4dbfa336f6e0ac925139543aed44cce7c3720fd51f69458705ac68cd4fe6b6b13abdc9746512969328454f18faf8c595f642477fe96bb2a941d5bcd1d4ac8cc49880708fa9b378e3c4f3a9060bee67cf9a4a4a695811051907e162753b56b0f6b410dba74d8a84b2a14b3144e0ef1284754fd17ed950d5965b4b9dd46582db1178d169c6bc465b0d6ff9ca3928fef5b9ae4e418fc15e83ebea0f87fa9ff5eed70050ded2849f47bf959d956850ce929851f0d8115f635b105ee2e4e15d04b2454bf6f4fadf034b10403119cd8e3b92fcc5b1ccd9c752428f0bca9ac9060bb85b8f90acb9374cd8d5a03110635f591a18f131cb7cc204407efec0687a8b77ba6c4e6732c35174e79e36aaa7fa6ab685257710e074065961ce1b16d21fed8a83cd95efcc4be7111cd33b5704fe759dfab21fc3e8aaa86d44609dc0b073354f8160c653f4fbde3ae7c28c87c3667e0797fac24b32e5c1a870cd898b2a9c517709bb0b8e4ee875ff857868eb56548e6dc993f198fd78c8a77cf997ed42a15f99a9b6265c7cf9bedc7580a11514047b881f717b233f3570ec21856bd2b9791e4c43b125e9260ac3fd48b9a10de5f9d5080e53d92d194adb796766684d905cca35e691fab0c76d6b5f49242f81eb92fcc8ad00000
-15 42438e06bbb424bba5fd95122ec2f206c9b502f1f6d4e4fdbf74ed2c946ad60abaefd6fbd6a08e3ef418709d15bc557ef5e486a51d1e304f6c1e943faad948fde4e6273c0cad0df07068ad028fb01dc0fd7221aeed6ed5dc510dbe4824939036b0f3a45e740b40cef86a32f0b73b20234efc41d573f3e14efc08b3f65e9f7be52d5b930de52d41c7aadc4e0e85dfcf3bb1dd2e9cdf94fc236082879aea27207415cb846a5d5969e619040416a7f0f708f56a5b340a8fd0be1a26bfdc3de365a950532d363b427d6d905af7534af574ae8afd3f47658de5da3fa02dd818a31523122ff53dd31ffd7aa22e53cbf2da7772a1589e9a242f28f9cb1130f54553fcb355b3398fc877b80b3ef2cc3d
-15 PASS
-15 Ok
-
2. Sending Text Messages
-

Once the Secret Chat has been established, you can use the following queries to make Paul and Nick exchange text messages inside the Secret Chat:

-
    -
  • ASK [A|B] — asks A or B to send a random plaintext message to the other party. It is guaranteed that at least one of the first ten generated messages will contain the secret email and password that are the goal of this contest. It is also guaranteed that apart from that, all messages will contain only dictionary English words, spaces, line breaks and punctuation marks. The result to this query is the ciphertext corresponding to the randomly generated plaintext.
  • -
  • TXT [A|B] bytes — asks A or B to encrypt bytes as the (plaintext) contents of a text message and send it to the other party. Note that bytes can be any byte sequence, not necessarily a valid UTF-8 sequence. The result to this query is the ciphertext corresponding to the given plaintext.
  • -
  • MSG [A|B] bytes — send a specified (ciphertext) message (for example, obtained as an answer to an ASK or TXT query) to A or B. You will receive ‘Ok’ if this message was decrypted successfully and accepted by the client, or ‘Fail’ otherwise.
  • -
-

Example:

-
15 ASK A
-15 b1d4a6119278722b0309a8c1fee80000c877b80b3ef2cc3dc92104de4322d8ae374fbf38758091fe4c86bafffa792f7eb37d8431cf8f868319c3af005791b7c55f788e260b8fa6a96b6808d0d448abfdb49913160c5355ef2d4e439a676055e42de6b26dd7d0e06e3fb48981208449658aff63fd8262ef0669f8bb242ade401e1190d2f54f3896ac17c1b796cbe185d5b0166649d5bac25e4626c08c78527458fc7877ee2add14a8e7b1f9b56651b8264284aa2fd28de55f96bcec8075dd43bbc69f6c05c2428795e51a081e3995e4ede72d190d55d0b30d8215bf4ed13fde7c8f578993050280ec4a940e910eb182bd335e52e2a699d9b5
-15 MSG B b1d4a6119278722b0309a8c1fee80000c877b80b3ef2cc3dc92104de4322d8ae374fbf38758091fe4c86bafffa792f7eb37d8431cf8f868319c3af005791b7c55f788e260b8fa6a96b6808d0d448abfdb49913160c5355ef2d4e439a676055e42de6b26dd7d0e06e3fb48981208449658aff63fd8262ef0669f8bb242ade401e1190d2f54f3896ac17c1b796cbe185d5b0166649d5bac25e4626c08c78527458fc7877ee2add14a8e7b1f9b56651b8264284aa2fd28de55f96bcec8075dd43bbc69f6c05c2428795e51a081e3995e4ede72d190d55d0b30d8215bf4ed13fde7c8f578993050280ec4a940e910eb182bd335e52e2a699d9b0
-15 Fail
-15 MSG B b1d4a6119278722b0309a8c1fee80000c877b80b3ef2cc3dc92104de4322d8ae374fbf38758091fe4c86bafffa792f7eb37d8431cf8f868319c3af005791b7c55f788e260b8fa6a96b6808d0d448abfdb49913160c5355ef2d4e439a676055e42de6b26dd7d0e06e3fb48981208449658aff63fd8262ef0669f8bb242ade401e1190d2f54f3896ac17c1b796cbe185d5b0166649d5bac25e4626c08c78527458fc7877ee2add14a8e7b1f9b56651b8264284aa2fd28de55f96bcec8075dd43bbc69f6c05c2428795e51a081e3995e4ede72d190d55d0b30d8215bf4ed13fde7c8f578993050280ec4a940e910eb182bd335e52e2a699d9b5
-15 Ok
-15 TXT B abac
-15 b1d4a61101771d42f62323e6fe680000c877b80b3ef2cc3df751e68b935b083a6f5c15ba8d95b94388fc34453a1e7b9b20222402b7698be5dd8a6ff69a5141b01ca2488b0dada8f2b0e47980218f48912168ddd2cebd3b61b1edf2f557c7ec44768595ce1cb42a01f7c14dd4e6e6e7601cb17ab0b6d5a274
-
-

Objectives

-

We are offering a $300,000 reward to the first person to break Telegram's encryption protocol in this contest.

-

Your goal is to extract a secret email address from one of the random messages that are exchanged between Nick and Paul when you use the ASK command. It is guaranteed that at least one of the first ten generated messages within a session will contain the secret address. It is also guaranteed that apart from that, all messages will contain only dictionary English words, spaces, line breaks and punctuation marks.

-

Once you have the address, you will need to send an email to it. That email must contain:
- The entire text of the message that contained the secret email.
- Session logs for the successful attempt with your user_id.
- A detailed explanation of the attack on the protocol.
- Your bank account details to receive the $300,000 prize.

-

Decrypting messages

-

To prove that the competition was fair, we will add a command that returns the keys used for a particular session by its session_id at the end of the contest. This will be done as soon as a winner is announced, or on February 4, 2015 in case no winner is announced to that date.

-

Bonus objective

-

We are also offering an independent $100,000 reward to the first person to make the bot accept a ciphertext message (i.e. the first person to send a message using MSG [A|B] bytes and receive the result ‘OK’), provided that that ciphertext deciphers to a plaintext that was never encrypted by the bot itself within this session.

-

Should you succeed at this, kindly send an email to security@telegram.org and include the following:
- Session logs for the successful attempt with your user_id.
- A detailed explanation of the attack on the protocol.
- Your bank account details to receive the $100,000 prize.

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/css/bootstrap-extra.css b/data/core.telegram.org/css/bootstrap-extra.css deleted file mode 100644 index 8a35b6069b..0000000000 --- a/data/core.telegram.org/css/bootstrap-extra.css +++ /dev/null @@ -1,3274 +0,0 @@ -/* glyph */ -@font-face { - font-family: 'Glyphicons Halflings'; - src: url('../fonts/glyphicons-halflings-regular.eot'); - src: url('../fonts/glyphicons-halflings-regular.eot?#iefix') format('embedded-opentype'), url('../fonts/glyphicons-halflings-regular.woff') format('woff'), url('../fonts/glyphicons-halflings-regular.ttf') format('truetype'), url('../fonts/glyphicons-halflings-regular.svg#glyphicons_halflingsregular') format('svg'); -} -.glyphicon { - position: relative; - top: 1px; - display: inline-block; - font-family: 'Glyphicons Halflings'; - font-style: normal; - font-weight: normal; - line-height: 1; - -webkit-font-smoothing: antialiased; - -moz-osx-font-smoothing: grayscale; -} -.glyphicon-asterisk:before { - content: "\2a"; -} -.glyphicon-plus:before { - content: "\2b"; -} -.glyphicon-euro:before { - content: "\20ac"; -} -.glyphicon-minus:before { - content: "\2212"; -} -.glyphicon-cloud:before { - content: "\2601"; -} -.glyphicon-envelope:before { - content: "\2709"; -} -.glyphicon-pencil:before { - content: "\270f"; -} -.glyphicon-glass:before { - content: "\e001"; -} -.glyphicon-music:before { - content: "\e002"; -} -.glyphicon-search:before { - content: "\e003"; -} -.glyphicon-heart:before { - content: "\e005"; -} -.glyphicon-star:before { - content: "\e006"; -} -.glyphicon-star-empty:before { - content: "\e007"; -} -.glyphicon-user:before { - content: "\e008"; -} -.glyphicon-film:before { - content: "\e009"; -} -.glyphicon-th-large:before { - content: "\e010"; -} -.glyphicon-th:before { - content: "\e011"; -} -.glyphicon-th-list:before { - content: "\e012"; -} -.glyphicon-ok:before { - content: "\e013"; -} -.glyphicon-remove:before { - content: "\e014"; -} -.glyphicon-zoom-in:before { - content: "\e015"; -} -.glyphicon-zoom-out:before { - content: "\e016"; -} -.glyphicon-off:before { - content: "\e017"; -} -.glyphicon-signal:before { - content: "\e018"; -} -.glyphicon-cog:before { - content: "\e019"; -} -.glyphicon-trash:before { - content: "\e020"; -} -.glyphicon-home:before { - content: "\e021"; -} -.glyphicon-file:before { - content: "\e022"; -} -.glyphicon-time:before { - content: "\e023"; -} -.glyphicon-road:before { - content: "\e024"; -} -.glyphicon-download-alt:before { - content: "\e025"; -} -.glyphicon-download:before { - content: "\e026"; -} -.glyphicon-upload:before { - content: "\e027"; -} -.glyphicon-inbox:before { - content: "\e028"; -} -.glyphicon-play-circle:before { - content: "\e029"; -} -.glyphicon-repeat:before { - content: "\e030"; -} -.glyphicon-refresh:before { - content: "\e031"; -} -.glyphicon-list-alt:before { - content: "\e032"; -} -.glyphicon-lock:before { - content: "\e033"; -} -.glyphicon-flag:before { - content: "\e034"; -} -.glyphicon-headphones:before { - content: "\e035"; -} -.glyphicon-volume-off:before { - content: "\e036"; -} -.glyphicon-volume-down:before { - content: "\e037"; -} -.glyphicon-volume-up:before { - content: "\e038"; -} -.glyphicon-qrcode:before { - content: "\e039"; -} -.glyphicon-barcode:before { - content: "\e040"; -} -.glyphicon-tag:before { - content: "\e041"; -} -.glyphicon-tags:before { - content: "\e042"; -} -.glyphicon-book:before { - content: "\e043"; -} -.glyphicon-bookmark:before { - content: "\e044"; -} -.glyphicon-print:before { - content: "\e045"; -} -.glyphicon-camera:before { - content: "\e046"; -} -.glyphicon-font:before { - content: "\e047"; -} -.glyphicon-bold:before { - content: "\e048"; -} -.glyphicon-italic:before { - content: "\e049"; -} -.glyphicon-text-height:before { - content: "\e050"; -} -.glyphicon-text-width:before { - content: "\e051"; -} -.glyphicon-align-left:before { - content: "\e052"; -} -.glyphicon-align-center:before { - content: "\e053"; -} -.glyphicon-align-right:before { - content: "\e054"; -} -.glyphicon-align-justify:before { - content: "\e055"; -} -.glyphicon-list:before { - content: "\e056"; -} -.glyphicon-indent-left:before { - content: "\e057"; -} -.glyphicon-indent-right:before { - content: "\e058"; -} -.glyphicon-facetime-video:before { - content: "\e059"; -} -.glyphicon-picture:before { - content: "\e060"; -} -.glyphicon-map-marker:before { - content: "\e062"; -} -.glyphicon-adjust:before { - content: "\e063"; -} -.glyphicon-tint:before { - content: "\e064"; -} -.glyphicon-edit:before { - content: "\e065"; -} -.glyphicon-share:before { - content: "\e066"; -} -.glyphicon-check:before { - content: "\e067"; -} -.glyphicon-move:before { - content: "\e068"; -} -.glyphicon-step-backward:before { - content: "\e069"; -} -.glyphicon-fast-backward:before { - content: "\e070"; -} -.glyphicon-backward:before { - content: "\e071"; -} -.glyphicon-play:before { - content: "\e072"; -} -.glyphicon-pause:before { - content: "\e073"; -} -.glyphicon-stop:before { - content: "\e074"; -} -.glyphicon-forward:before { - content: "\e075"; -} -.glyphicon-fast-forward:before { - content: "\e076"; -} -.glyphicon-step-forward:before { - content: "\e077"; -} -.glyphicon-eject:before { - content: "\e078"; -} -.glyphicon-chevron-left:before { - content: "\e079"; -} -.glyphicon-chevron-right:before { - content: "\e080"; -} -.glyphicon-plus-sign:before { - content: "\e081"; -} -.glyphicon-minus-sign:before { - content: "\e082"; -} -.glyphicon-remove-sign:before { - content: "\e083"; -} -.glyphicon-ok-sign:before { - content: "\e084"; -} -.glyphicon-question-sign:before { - content: "\e085"; -} -.glyphicon-info-sign:before { - content: "\e086"; -} -.glyphicon-screenshot:before { - content: "\e087"; -} -.glyphicon-remove-circle:before { - content: "\e088"; -} -.glyphicon-ok-circle:before { - content: "\e089"; -} -.glyphicon-ban-circle:before { - content: "\e090"; -} -.glyphicon-arrow-left:before { - content: "\e091"; -} -.glyphicon-arrow-right:before { - content: "\e092"; -} -.glyphicon-arrow-up:before { - content: "\e093"; -} -.glyphicon-arrow-down:before { - content: "\e094"; -} -.glyphicon-share-alt:before { - content: "\e095"; -} -.glyphicon-resize-full:before { - content: "\e096"; -} -.glyphicon-resize-small:before { - content: "\e097"; -} -.glyphicon-exclamation-sign:before { - content: "\e101"; -} -.glyphicon-gift:before { - content: "\e102"; -} -.glyphicon-leaf:before { - content: "\e103"; -} -.glyphicon-fire:before { - content: "\e104"; -} -.glyphicon-eye-open:before { - content: "\e105"; -} -.glyphicon-eye-close:before { - content: "\e106"; -} -.glyphicon-warning-sign:before { - content: "\e107"; -} -.glyphicon-plane:before { - content: "\e108"; -} -.glyphicon-calendar:before { - content: "\e109"; -} -.glyphicon-random:before { - content: "\e110"; -} -.glyphicon-comment:before { - content: "\e111"; -} -.glyphicon-magnet:before { - content: "\e112"; -} -.glyphicon-chevron-up:before { - content: "\e113"; -} -.glyphicon-chevron-down:before { - content: "\e114"; -} -.glyphicon-retweet:before { - content: "\e115"; -} -.glyphicon-shopping-cart:before { - content: "\e116"; -} -.glyphicon-folder-close:before { - content: "\e117"; -} -.glyphicon-folder-open:before { - content: "\e118"; -} -.glyphicon-resize-vertical:before { - content: "\e119"; -} -.glyphicon-resize-horizontal:before { - content: "\e120"; -} -.glyphicon-hdd:before { - content: "\e121"; -} -.glyphicon-bullhorn:before { - content: "\e122"; -} -.glyphicon-bell:before { - content: "\e123"; -} -.glyphicon-certificate:before { - content: "\e124"; -} -.glyphicon-thumbs-up:before { - content: "\e125"; -} -.glyphicon-thumbs-down:before { - content: "\e126"; -} -.glyphicon-hand-right:before { - content: "\e127"; -} -.glyphicon-hand-left:before { - content: "\e128"; -} -.glyphicon-hand-up:before { - content: "\e129"; -} -.glyphicon-hand-down:before { - content: "\e130"; -} -.glyphicon-circle-arrow-right:before { - content: "\e131"; -} -.glyphicon-circle-arrow-left:before { - content: "\e132"; -} -.glyphicon-circle-arrow-up:before { - content: "\e133"; -} -.glyphicon-circle-arrow-down:before { - content: "\e134"; -} -.glyphicon-globe:before { - content: "\e135"; -} -.glyphicon-wrench:before { - content: "\e136"; -} -.glyphicon-tasks:before { - content: "\e137"; -} -.glyphicon-filter:before { - content: "\e138"; -} -.glyphicon-briefcase:before { - content: "\e139"; -} -.glyphicon-fullscreen:before { - content: "\e140"; -} -.glyphicon-dashboard:before { - content: "\e141"; -} -.glyphicon-paperclip:before { - content: "\e142"; -} -.glyphicon-heart-empty:before { - content: "\e143"; -} -.glyphicon-link:before { - content: "\e144"; -} -.glyphicon-phone:before { - content: "\e145"; -} -.glyphicon-pushpin:before { - content: "\e146"; -} -.glyphicon-usd:before { - content: "\e148"; -} -.glyphicon-gbp:before { - content: "\e149"; -} -.glyphicon-sort:before { - content: "\e150"; -} -.glyphicon-sort-by-alphabet:before { - content: "\e151"; -} -.glyphicon-sort-by-alphabet-alt:before { - content: "\e152"; -} -.glyphicon-sort-by-order:before { - content: "\e153"; -} -.glyphicon-sort-by-order-alt:before { - content: "\e154"; -} -.glyphicon-sort-by-attributes:before { - content: "\e155"; -} -.glyphicon-sort-by-attributes-alt:before { - content: "\e156"; -} -.glyphicon-unchecked:before { - content: "\e157"; -} -.glyphicon-expand:before { - content: "\e158"; -} -.glyphicon-collapse-down:before { - content: "\e159"; -} -.glyphicon-collapse-up:before { - content: "\e160"; -} -.glyphicon-log-in:before { - content: "\e161"; -} -.glyphicon-flash:before { - content: "\e162"; -} -.glyphicon-log-out:before { - content: "\e163"; -} -.glyphicon-new-window:before { - content: "\e164"; -} -.glyphicon-record:before { - content: "\e165"; -} -.glyphicon-save:before { - content: "\e166"; -} -.glyphicon-open:before { - content: "\e167"; -} -.glyphicon-saved:before { - content: "\e168"; -} -.glyphicon-import:before { - content: "\e169"; -} -.glyphicon-export:before { - content: "\e170"; -} -.glyphicon-send:before { - content: "\e171"; -} -.glyphicon-floppy-disk:before { - content: "\e172"; -} -.glyphicon-floppy-saved:before { - content: "\e173"; -} -.glyphicon-floppy-remove:before { - content: "\e174"; -} -.glyphicon-floppy-save:before { - content: "\e175"; -} -.glyphicon-floppy-open:before { - content: "\e176"; -} -.glyphicon-credit-card:before { - content: "\e177"; -} -.glyphicon-transfer:before { - content: "\e178"; -} -.glyphicon-cutlery:before { - content: "\e179"; -} -.glyphicon-header:before { - content: "\e180"; -} -.glyphicon-compressed:before { - content: "\e181"; -} -.glyphicon-earphone:before { - content: "\e182"; -} -.glyphicon-phone-alt:before { - content: "\e183"; -} -.glyphicon-tower:before { - content: "\e184"; -} -.glyphicon-stats:before { - content: "\e185"; -} -.glyphicon-sd-video:before { - content: "\e186"; -} -.glyphicon-hd-video:before { - content: "\e187"; -} -.glyphicon-subtitles:before { - content: "\e188"; -} -.glyphicon-sound-stereo:before { - content: "\e189"; -} -.glyphicon-sound-dolby:before { - content: "\e190"; -} -.glyphicon-sound-5-1:before { - content: "\e191"; -} -.glyphicon-sound-6-1:before { - content: "\e192"; -} -.glyphicon-sound-7-1:before { - content: "\e193"; -} -.glyphicon-copyright-mark:before { - content: "\e194"; -} -.glyphicon-registration-mark:before { - content: "\e195"; -} -.glyphicon-cloud-download:before { - content: "\e197"; -} -.glyphicon-cloud-upload:before { - content: "\e198"; -} -.glyphicon-tree-conifer:before { - content: "\e199"; -} -.glyphicon-tree-deciduous:before { - content: "\e200"; -} - - -/*btn*/ -.btn { - display: inline-block; - margin-bottom: 0; - font-weight: normal; - text-align: center; - vertical-align: middle; - cursor: pointer; - background-image: none; - border: 1px solid transparent; - white-space: nowrap; - padding: 6px 12px; - font-size: 12px; - line-height: 1.42857143; - border-radius: 4px; - -webkit-user-select: none; - -moz-user-select: none; - -ms-user-select: none; - user-select: none; -} -.btn:focus, -.btn:active:focus, -.btn.active:focus { - outline: thin dotted; - outline: 5px auto -webkit-focus-ring-color; - outline-offset: -2px; -} -.btn:hover, -.btn:focus { - color: #333333; - text-decoration: none; -} -.btn:active, -.btn.active { - outline: 0; - background-image: none; - -webkit-box-shadow: inset 0 3px 5px rgba(0, 0, 0, 0.125); - box-shadow: inset 0 3px 5px rgba(0, 0, 0, 0.125); -} -.btn.disabled, -.btn[disabled], -fieldset[disabled] .btn { - cursor: not-allowed; - pointer-events: none; - opacity: 0.65; - filter: alpha(opacity=65); - -webkit-box-shadow: none; - box-shadow: none; -} -.btn-default { - color: #333333; - background-color: #ffffff; - border-color: #cccccc; -} -.btn-default:hover, -.btn-default:focus, -.btn-default:active, -.btn-default.active, -.open > .dropdown-toggle.btn-default { - color: #333333; - background-color: #e6e6e6; - border-color: #adadad; -} -.btn-default:active, -.btn-default.active, -.open > .dropdown-toggle.btn-default { - background-image: none; -} -.btn-default.disabled, -.btn-default[disabled], -fieldset[disabled] .btn-default, -.btn-default.disabled:hover, -.btn-default[disabled]:hover, -fieldset[disabled] .btn-default:hover, -.btn-default.disabled:focus, -.btn-default[disabled]:focus, -fieldset[disabled] .btn-default:focus, -.btn-default.disabled:active, -.btn-default[disabled]:active, -fieldset[disabled] .btn-default:active, -.btn-default.disabled.active, -.btn-default[disabled].active, -fieldset[disabled] .btn-default.active { - background-color: #ffffff; - border-color: #cccccc; -} -.btn-default .badge { - color: #ffffff; - background-color: #333333; -} -.btn-primary { - color: #ffffff; - background-color: #428bca; - border-color: #357ebd; -} -.btn-primary:hover, -.btn-primary:focus, -.btn-primary:active, -.btn-primary.active, -.open > .dropdown-toggle.btn-primary { - color: #ffffff; - background-color: #3071a9; - border-color: #285e8e; -} -.btn-primary:active, -.btn-primary.active, -.open > .dropdown-toggle.btn-primary { - background-image: none; -} -.btn-primary.disabled, -.btn-primary[disabled], -fieldset[disabled] .btn-primary, -.btn-primary.disabled:hover, -.btn-primary[disabled]:hover, -fieldset[disabled] .btn-primary:hover, -.btn-primary.disabled:focus, -.btn-primary[disabled]:focus, -fieldset[disabled] .btn-primary:focus, -.btn-primary.disabled:active, -.btn-primary[disabled]:active, -fieldset[disabled] .btn-primary:active, -.btn-primary.disabled.active, -.btn-primary[disabled].active, -fieldset[disabled] .btn-primary.active { - background-color: #428bca; - border-color: #357ebd; -} -.btn-primary .badge { - color: #428bca; - background-color: #ffffff; -} -.btn-success { - color: #ffffff; - background-color: #5cb85c; - border-color: #4cae4c; -} -.btn-success:hover, -.btn-success:focus, -.btn-success:active, -.btn-success.active, -.open > .dropdown-toggle.btn-success { - color: #ffffff; - background-color: #449d44; - border-color: #398439; -} -.btn-success:active, -.btn-success.active, -.open > .dropdown-toggle.btn-success { - background-image: none; -} -.btn-success.disabled, -.btn-success[disabled], -fieldset[disabled] .btn-success, -.btn-success.disabled:hover, -.btn-success[disabled]:hover, -fieldset[disabled] .btn-success:hover, -.btn-success.disabled:focus, -.btn-success[disabled]:focus, -fieldset[disabled] .btn-success:focus, -.btn-success.disabled:active, -.btn-success[disabled]:active, -fieldset[disabled] .btn-success:active, -.btn-success.disabled.active, -.btn-success[disabled].active, -fieldset[disabled] .btn-success.active { - background-color: #5cb85c; - border-color: #4cae4c; -} -.btn-success .badge { - color: #5cb85c; - background-color: #ffffff; -} -.btn-info { - color: #ffffff; - background-color: #5bc0de; - border-color: #46b8da; -} -.btn-info:hover, -.btn-info:focus, -.btn-info:active, -.btn-info.active, -.open > .dropdown-toggle.btn-info { - color: #ffffff; - background-color: #31b0d5; - border-color: #269abc; -} -.btn-info:active, -.btn-info.active, -.open > .dropdown-toggle.btn-info { - background-image: none; -} -.btn-info.disabled, -.btn-info[disabled], -fieldset[disabled] .btn-info, -.btn-info.disabled:hover, -.btn-info[disabled]:hover, -fieldset[disabled] .btn-info:hover, -.btn-info.disabled:focus, -.btn-info[disabled]:focus, -fieldset[disabled] .btn-info:focus, -.btn-info.disabled:active, -.btn-info[disabled]:active, -fieldset[disabled] .btn-info:active, -.btn-info.disabled.active, -.btn-info[disabled].active, -fieldset[disabled] .btn-info.active { - background-color: #5bc0de; - border-color: #46b8da; -} -.btn-info .badge { - color: #5bc0de; - background-color: #ffffff; -} -.btn-warning { - color: #ffffff; - background-color: #f0ad4e; - border-color: #eea236; -} -.btn-warning:hover, -.btn-warning:focus, -.btn-warning:active, -.btn-warning.active, -.open > .dropdown-toggle.btn-warning { - color: #ffffff; - background-color: #ec971f; - border-color: #d58512; -} -.btn-warning:active, -.btn-warning.active, -.open > .dropdown-toggle.btn-warning { - background-image: none; -} -.btn-warning.disabled, -.btn-warning[disabled], -fieldset[disabled] .btn-warning, -.btn-warning.disabled:hover, -.btn-warning[disabled]:hover, -fieldset[disabled] .btn-warning:hover, -.btn-warning.disabled:focus, -.btn-warning[disabled]:focus, -fieldset[disabled] .btn-warning:focus, -.btn-warning.disabled:active, -.btn-warning[disabled]:active, -fieldset[disabled] .btn-warning:active, -.btn-warning.disabled.active, -.btn-warning[disabled].active, -fieldset[disabled] .btn-warning.active { - background-color: #f0ad4e; - border-color: #eea236; -} -.btn-warning .badge { - color: #f0ad4e; - background-color: #ffffff; -} -.btn-danger { - color: #ffffff; - background-color: #d9534f; - border-color: #d43f3a; -} -.btn-danger:hover, -.btn-danger:focus, -.btn-danger:active, -.btn-danger.active, -.open > .dropdown-toggle.btn-danger { - color: #ffffff; - background-color: #c9302c; - border-color: #ac2925; -} -.btn-danger:active, -.btn-danger.active, -.open > .dropdown-toggle.btn-danger { - background-image: none; -} -.btn-danger.disabled, -.btn-danger[disabled], -fieldset[disabled] .btn-danger, -.btn-danger.disabled:hover, -.btn-danger[disabled]:hover, -fieldset[disabled] .btn-danger:hover, -.btn-danger.disabled:focus, -.btn-danger[disabled]:focus, -fieldset[disabled] .btn-danger:focus, -.btn-danger.disabled:active, -.btn-danger[disabled]:active, -fieldset[disabled] .btn-danger:active, -.btn-danger.disabled.active, -.btn-danger[disabled].active, -fieldset[disabled] .btn-danger.active { - background-color: #d9534f; - border-color: #d43f3a; -} -.btn-danger .badge { - color: #d9534f; - background-color: #ffffff; -} -.btn-link { - color: #0088cc; - font-weight: normal; - cursor: pointer; - border-radius: 0; -} -.btn-link, -.btn-link:active, -.btn-link[disabled], -fieldset[disabled] .btn-link { - background-color: transparent; - -webkit-box-shadow: none; - box-shadow: none; -} -.btn-link, -.btn-link:hover, -.btn-link:focus, -.btn-link:active { - border-color: transparent; -} -.btn-link:hover, -.btn-link:focus { - color: #0088cc; - text-decoration: underline; - background-color: transparent; -} -.btn-link[disabled]:hover, -fieldset[disabled] .btn-link:hover, -.btn-link[disabled]:focus, -fieldset[disabled] .btn-link:focus { - color: #777777; - text-decoration: none; -} -.btn-lg { - padding: 10px 16px; - font-size: 15px; - line-height: 1.33; - border-radius: 6px; -} -.btn-sm { - padding: 5px 10px; - font-size: 11px; - line-height: 1.5; - border-radius: 3px; -} -.btn-xs { - padding: 1px 5px; - font-size: 11px; - line-height: 1.5; - border-radius: 3px; -} -.btn-block { - display: block; - width: 100%; -} -.btn-block + .btn-block { - margin-top: 5px; -} -input[type="submit"].btn-block, -input[type="reset"].btn-block, -input[type="button"].btn-block { - width: 100%; -} - -.img-responsive { - display: block; - width: 100% \9; - max-width: 100%; - height: auto; -} -.img-rounded { - border-radius: 6px; -} -.img-thumbnail { - padding: 4px; - line-height: 1.42857143; - background-color: #ffffff; - border: 1px solid #dddddd; - border-radius: 0; - -webkit-transition: all 0.2s ease-in-out; - -o-transition: all 0.2s ease-in-out; - transition: all 0.2s ease-in-out; - display: inline-block; - width: 100% \9; - max-width: 100%; - height: auto; -} -.img-circle { - border-radius: 50%; -} - - - -.row { - margin-left: -15px; - margin-right: -15px; -} -.col-xs-1, .col-sm-1, .col-md-1, .col-lg-1, .col-xs-2, .col-sm-2, .col-md-2, .col-lg-2, .col-xs-3, .col-sm-3, .col-md-3, .col-lg-3, .col-xs-4, .col-sm-4, .col-md-4, .col-lg-4, .col-xs-5, .col-sm-5, .col-md-5, .col-lg-5, .col-xs-6, .col-sm-6, .col-md-6, .col-lg-6, .col-xs-7, .col-sm-7, .col-md-7, .col-lg-7, .col-xs-8, .col-sm-8, .col-md-8, .col-lg-8, .col-xs-9, .col-sm-9, .col-md-9, .col-lg-9, .col-xs-10, .col-sm-10, .col-md-10, .col-lg-10, .col-xs-11, .col-sm-11, .col-md-11, .col-lg-11, .col-xs-12, .col-sm-12, .col-md-12, .col-lg-12 { - position: relative; - min-height: 1px; - padding-left: 15px; - padding-right: 15px; -} -.col-xs-1, .col-xs-2, .col-xs-3, .col-xs-4, .col-xs-5, .col-xs-6, .col-xs-7, .col-xs-8, .col-xs-9, .col-xs-10, .col-xs-11, .col-xs-12 { - float: left; -} -.col-xs-12 { - width: 100%; -} -.col-xs-11 { - width: 91.66666667%; -} -.col-xs-10 { - width: 83.33333333%; -} -.col-xs-9 { - width: 75%; -} -.col-xs-8 { - width: 66.66666667%; -} -.col-xs-7 { - width: 58.33333333%; -} -.col-xs-6 { - width: 50%; -} -.col-xs-5 { - width: 41.66666667%; -} -.col-xs-4 { - width: 33.33333333%; -} -.col-xs-3 { - width: 25%; -} -.col-xs-2 { - width: 16.66666667%; -} -.col-xs-1 { - width: 8.33333333%; -} -.col-xs-pull-12 { - right: 100%; -} -.col-xs-pull-11 { - right: 91.66666667%; -} -.col-xs-pull-10 { - right: 83.33333333%; -} -.col-xs-pull-9 { - right: 75%; -} -.col-xs-pull-8 { - right: 66.66666667%; -} -.col-xs-pull-7 { - right: 58.33333333%; -} -.col-xs-pull-6 { - right: 50%; -} -.col-xs-pull-5 { - right: 41.66666667%; -} -.col-xs-pull-4 { - right: 33.33333333%; -} -.col-xs-pull-3 { - right: 25%; -} -.col-xs-pull-2 { - right: 16.66666667%; -} -.col-xs-pull-1 { - right: 8.33333333%; -} -.col-xs-pull-0 { - right: auto; -} -.col-xs-push-12 { - left: 100%; -} -.col-xs-push-11 { - left: 91.66666667%; -} -.col-xs-push-10 { - left: 83.33333333%; -} -.col-xs-push-9 { - left: 75%; -} -.col-xs-push-8 { - left: 66.66666667%; -} -.col-xs-push-7 { - left: 58.33333333%; -} -.col-xs-push-6 { - left: 50%; -} -.col-xs-push-5 { - left: 41.66666667%; -} -.col-xs-push-4 { - left: 33.33333333%; -} -.col-xs-push-3 { - left: 25%; -} -.col-xs-push-2 { - left: 16.66666667%; -} -.col-xs-push-1 { - left: 8.33333333%; -} -.col-xs-push-0 { - left: auto; -} -.col-xs-offset-12 { - margin-left: 100%; -} -.col-xs-offset-11 { - margin-left: 91.66666667%; -} -.col-xs-offset-10 { - margin-left: 83.33333333%; -} -.col-xs-offset-9 { - margin-left: 75%; -} -.col-xs-offset-8 { - margin-left: 66.66666667%; -} -.col-xs-offset-7 { - margin-left: 58.33333333%; -} -.col-xs-offset-6 { - margin-left: 50%; -} -.col-xs-offset-5 { - margin-left: 41.66666667%; -} -.col-xs-offset-4 { - margin-left: 33.33333333%; -} -.col-xs-offset-3 { - margin-left: 25%; -} -.col-xs-offset-2 { - margin-left: 16.66666667%; -} -.col-xs-offset-1 { - margin-left: 8.33333333%; -} -.col-xs-offset-0 { - margin-left: 0%; -} -@media (min-width: 768px) { - .col-sm-1, .col-sm-2, .col-sm-3, .col-sm-4, .col-sm-5, .col-sm-6, .col-sm-7, .col-sm-8, .col-sm-9, .col-sm-10, .col-sm-11, .col-sm-12 { - float: left; - } - .col-sm-12 { - width: 100%; - } - .col-sm-11 { - width: 91.66666667%; - } - .col-sm-10 { - width: 83.33333333%; - } - .col-sm-9 { - width: 75%; - } - .col-sm-8 { - width: 66.66666667%; - } - .col-sm-7 { - width: 58.33333333%; - } - .col-sm-6 { - width: 50%; - } - .col-sm-5 { - width: 41.66666667%; - } - .col-sm-4 { - width: 33.33333333%; - } - .col-sm-3 { - width: 25%; - } - .col-sm-2 { - width: 16.66666667%; - } - .col-sm-1 { - width: 8.33333333%; - } - .col-sm-pull-12 { - right: 100%; - } - .col-sm-pull-11 { - right: 91.66666667%; - } - .col-sm-pull-10 { - right: 83.33333333%; - } - .col-sm-pull-9 { - right: 75%; - } - .col-sm-pull-8 { - right: 66.66666667%; - } - .col-sm-pull-7 { - right: 58.33333333%; - } - .col-sm-pull-6 { - right: 50%; - } - .col-sm-pull-5 { - right: 41.66666667%; - } - .col-sm-pull-4 { - right: 33.33333333%; - } - .col-sm-pull-3 { - right: 25%; - } - .col-sm-pull-2 { - right: 16.66666667%; - } - .col-sm-pull-1 { - right: 8.33333333%; - } - .col-sm-pull-0 { - right: auto; - } - .col-sm-push-12 { - left: 100%; - } - .col-sm-push-11 { - left: 91.66666667%; - } - .col-sm-push-10 { - left: 83.33333333%; - } - .col-sm-push-9 { - left: 75%; - } - .col-sm-push-8 { - left: 66.66666667%; - } - .col-sm-push-7 { - left: 58.33333333%; - } - .col-sm-push-6 { - left: 50%; - } - .col-sm-push-5 { - left: 41.66666667%; - } - .col-sm-push-4 { - left: 33.33333333%; - } - .col-sm-push-3 { - left: 25%; - } - .col-sm-push-2 { - left: 16.66666667%; - } - .col-sm-push-1 { - left: 8.33333333%; - } - .col-sm-push-0 { - left: auto; - } - .col-sm-offset-12 { - margin-left: 100%; - } - .col-sm-offset-11 { - margin-left: 91.66666667%; - } - .col-sm-offset-10 { - margin-left: 83.33333333%; - } - .col-sm-offset-9 { - margin-left: 75%; - } - .col-sm-offset-8 { - margin-left: 66.66666667%; - } - .col-sm-offset-7 { - margin-left: 58.33333333%; - } - .col-sm-offset-6 { - margin-left: 50%; - } - .col-sm-offset-5 { - margin-left: 41.66666667%; - } - .col-sm-offset-4 { - margin-left: 33.33333333%; - } - .col-sm-offset-3 { - margin-left: 25%; - } - .col-sm-offset-2 { - margin-left: 16.66666667%; - } - .col-sm-offset-1 { - margin-left: 8.33333333%; - } - .col-sm-offset-0 { - margin-left: 0%; - } -} -@media (min-width: 992px) { - .col-md-1, .col-md-2, .col-md-3, .col-md-4, .col-md-5, .col-md-6, .col-md-7, .col-md-8, .col-md-9, .col-md-10, .col-md-11, .col-md-12 { - float: left; - } - .col-md-12 { - width: 100%; - } - .col-md-11 { - width: 91.66666667%; - } - .col-md-10 { - width: 83.33333333%; - } - .col-md-9 { - width: 75%; - } - .col-md-8 { - width: 66.66666667%; - } - .col-md-7 { - width: 58.33333333%; - } - .col-md-6 { - width: 50%; - } - .col-md-5 { - width: 41.66666667%; - } - .col-md-4 { - width: 33.33333333%; - } - .col-md-3 { - width: 25%; - } - .col-md-2 { - width: 16.66666667%; - } - .col-md-1 { - width: 8.33333333%; - } - .col-md-pull-12 { - right: 100%; - } - .col-md-pull-11 { - right: 91.66666667%; - } - .col-md-pull-10 { - right: 83.33333333%; - } - .col-md-pull-9 { - right: 75%; - } - .col-md-pull-8 { - right: 66.66666667%; - } - .col-md-pull-7 { - right: 58.33333333%; - } - .col-md-pull-6 { - right: 50%; - } - .col-md-pull-5 { - right: 41.66666667%; - } - .col-md-pull-4 { - right: 33.33333333%; - } - .col-md-pull-3 { - right: 25%; - } - .col-md-pull-2 { - right: 16.66666667%; - } - .col-md-pull-1 { - right: 8.33333333%; - } - .col-md-pull-0 { - right: auto; - } - .col-md-push-12 { - left: 100%; - } - .col-md-push-11 { - left: 91.66666667%; - } - .col-md-push-10 { - left: 83.33333333%; - } - .col-md-push-9 { - left: 75%; - } - .col-md-push-8 { - left: 66.66666667%; - } - .col-md-push-7 { - left: 58.33333333%; - } - .col-md-push-6 { - left: 50%; - } - .col-md-push-5 { - left: 41.66666667%; - } - .col-md-push-4 { - left: 33.33333333%; - } - .col-md-push-3 { - left: 25%; - } - .col-md-push-2 { - left: 16.66666667%; - } - .col-md-push-1 { - left: 8.33333333%; - } - .col-md-push-0 { - left: auto; - } - .col-md-offset-12 { - margin-left: 100%; - } - .col-md-offset-11 { - margin-left: 91.66666667%; - } - .col-md-offset-10 { - margin-left: 83.33333333%; - } - .col-md-offset-9 { - margin-left: 75%; - } - .col-md-offset-8 { - margin-left: 66.66666667%; - } - .col-md-offset-7 { - margin-left: 58.33333333%; - } - .col-md-offset-6 { - margin-left: 50%; - } - .col-md-offset-5 { - margin-left: 41.66666667%; - } - .col-md-offset-4 { - margin-left: 33.33333333%; - } - .col-md-offset-3 { - margin-left: 25%; - } - .col-md-offset-2 { - margin-left: 16.66666667%; - } - .col-md-offset-1 { - margin-left: 8.33333333%; - } - .col-md-offset-0 { - margin-left: 0%; - } -} -@media (min-width: 1200px) { - .col-lg-1, .col-lg-2, .col-lg-3, .col-lg-4, .col-lg-5, .col-lg-6, .col-lg-7, .col-lg-8, .col-lg-9, .col-lg-10, .col-lg-11, .col-lg-12 { - float: left; - } - .col-lg-12 { - width: 100%; - } - .col-lg-11 { - width: 91.66666667%; - } - .col-lg-10 { - width: 83.33333333%; - } - .col-lg-9 { - width: 75%; - } - .col-lg-8 { - width: 66.66666667%; - } - .col-lg-7 { - width: 58.33333333%; - } - .col-lg-6 { - width: 50%; - } - .col-lg-5 { - width: 41.66666667%; - } - .col-lg-4 { - width: 33.33333333%; - } - .col-lg-3 { - width: 25%; - } - .col-lg-2 { - width: 16.66666667%; - } - .col-lg-1 { - width: 8.33333333%; - } - .col-lg-pull-12 { - right: 100%; - } - .col-lg-pull-11 { - right: 91.66666667%; - } - .col-lg-pull-10 { - right: 83.33333333%; - } - .col-lg-pull-9 { - right: 75%; - } - .col-lg-pull-8 { - right: 66.66666667%; - } - .col-lg-pull-7 { - right: 58.33333333%; - } - .col-lg-pull-6 { - right: 50%; - } - .col-lg-pull-5 { - right: 41.66666667%; - } - .col-lg-pull-4 { - right: 33.33333333%; - } - .col-lg-pull-3 { - right: 25%; - } - .col-lg-pull-2 { - right: 16.66666667%; - } - .col-lg-pull-1 { - right: 8.33333333%; - } - .col-lg-pull-0 { - right: auto; - } - .col-lg-push-12 { - left: 100%; - } - .col-lg-push-11 { - left: 91.66666667%; - } - .col-lg-push-10 { - left: 83.33333333%; - } - .col-lg-push-9 { - left: 75%; - } - .col-lg-push-8 { - left: 66.66666667%; - } - .col-lg-push-7 { - left: 58.33333333%; - } - .col-lg-push-6 { - left: 50%; - } - .col-lg-push-5 { - left: 41.66666667%; - } - .col-lg-push-4 { - left: 33.33333333%; - } - .col-lg-push-3 { - left: 25%; - } - .col-lg-push-2 { - left: 16.66666667%; - } - .col-lg-push-1 { - left: 8.33333333%; - } - .col-lg-push-0 { - left: auto; - } - .col-lg-offset-12 { - margin-left: 100%; - } - .col-lg-offset-11 { - margin-left: 91.66666667%; - } - .col-lg-offset-10 { - margin-left: 83.33333333%; - } - .col-lg-offset-9 { - margin-left: 75%; - } - .col-lg-offset-8 { - margin-left: 66.66666667%; - } - .col-lg-offset-7 { - margin-left: 58.33333333%; - } - .col-lg-offset-6 { - margin-left: 50%; - } - .col-lg-offset-5 { - margin-left: 41.66666667%; - } - .col-lg-offset-4 { - margin-left: 33.33333333%; - } - .col-lg-offset-3 { - margin-left: 25%; - } - .col-lg-offset-2 { - margin-left: 16.66666667%; - } - .col-lg-offset-1 { - margin-left: 8.33333333%; - } - .col-lg-offset-0 { - margin-left: 0%; - } -} - - - - -.form-control { - display: block; - width: 100%; - height: 31px; - padding: 6px 12px; - font-size: 12px; - line-height: 1.42857143; - color: #555555; - background-color: #ffffff; - background-image: none; - border: 1px solid #cccccc; - border-radius: 0; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); - -webkit-transition: border-color ease-in-out .15s, box-shadow ease-in-out .15s; - -o-transition: border-color ease-in-out .15s, box-shadow ease-in-out .15s; - transition: border-color ease-in-out .15s, box-shadow ease-in-out .15s; -} -.form-control:focus { - border-color: #66afe9; - outline: 0; - -webkit-box-shadow: inset 0 1px 1px rgba(0,0,0,.075), 0 0 8px rgba(102, 175, 233, 0.6); - box-shadow: inset 0 1px 1px rgba(0,0,0,.075), 0 0 8px rgba(102, 175, 233, 0.6); -} -.form-control::-moz-placeholder { - color: #777777; - opacity: 1; -} -.form-control:-ms-input-placeholder { - color: #777777; -} -.form-control::-webkit-input-placeholder { - color: #777777; -} -.form-control[disabled], -.form-control[readonly], -fieldset[disabled] .form-control { - cursor: not-allowed; - background-color: #eeeeee; - opacity: 1; -} -textarea.form-control { - height: auto; -} -input[type="search"] { - -webkit-appearance: none; -} -input[type="date"], -input[type="time"], -input[type="datetime-local"], -input[type="month"] { - line-height: 31px; - line-height: 1.42857143 \0; -} -input[type="date"].input-sm, -input[type="time"].input-sm, -input[type="datetime-local"].input-sm, -input[type="month"].input-sm { - line-height: 28px; -} -input[type="date"].input-lg, -input[type="time"].input-lg, -input[type="datetime-local"].input-lg, -input[type="month"].input-lg { - line-height: 42px; -} -.form-group { - margin-bottom: 15px; -} -.radio, -.checkbox { - position: relative; - display: block; - min-height: 17px; - margin-top: 10px; - margin-bottom: 10px; -} -.radio label, -.checkbox label { - padding-left: 20px; - margin-bottom: 0; - font-weight: normal; - cursor: pointer; -} -.radio input[type="radio"], -.radio-inline input[type="radio"], -.checkbox input[type="checkbox"], -.checkbox-inline input[type="checkbox"] { - position: absolute; - margin-left: -20px; - margin-top: 4px \9; -} -.radio + .radio, -.checkbox + .checkbox { - margin-top: -5px; -} -.radio-inline, -.checkbox-inline { - display: inline-block; - padding-left: 20px; - margin-bottom: 0; - vertical-align: middle; - font-weight: normal; - cursor: pointer; -} -.radio-inline + .radio-inline, -.checkbox-inline + .checkbox-inline { - margin-top: 0; - margin-left: 10px; -} -input[type="radio"][disabled], -input[type="checkbox"][disabled], -input[type="radio"].disabled, -input[type="checkbox"].disabled, -fieldset[disabled] input[type="radio"], -fieldset[disabled] input[type="checkbox"] { - cursor: not-allowed; -} -.radio-inline.disabled, -.checkbox-inline.disabled, -fieldset[disabled] .radio-inline, -fieldset[disabled] .checkbox-inline { - cursor: not-allowed; -} -.radio.disabled label, -.checkbox.disabled label, -fieldset[disabled] .radio label, -fieldset[disabled] .checkbox label { - cursor: not-allowed; -} -.form-control-static { - padding-top: 7px; - padding-bottom: 7px; - margin-bottom: 0; -} -.form-control-static.input-lg, -.form-control-static.input-sm { - padding-left: 0; - padding-right: 0; -} -.input-sm, -.form-horizontal .form-group-sm .form-control { - height: 28px; - padding: 5px 10px; - font-size: 11px; - line-height: 1.5; - border-radius: 3px; -} -select.input-sm { - height: 28px; - line-height: 28px; -} -textarea.input-sm, -select[multiple].input-sm { - height: auto; -} -.input-lg, -.form-horizontal .form-group-lg .form-control { - height: 42px; - padding: 10px 16px; - font-size: 15px; - line-height: 1.33; - border-radius: 6px; -} -select.input-lg { - height: 42px; - line-height: 42px; -} -textarea.input-lg, -select[multiple].input-lg { - height: auto; -} -.has-feedback { - position: relative; -} -.has-feedback .form-control { - padding-right: 38.75px; -} -.form-control-feedback { - position: absolute; - top: 22px; - right: 0; - z-index: 2; - display: block; - width: 31px; - height: 31px; - line-height: 31px; - text-align: center; -} -.input-lg + .form-control-feedback { - width: 42px; - height: 42px; - line-height: 42px; -} -.input-sm + .form-control-feedback { - width: 28px; - height: 28px; - line-height: 28px; -} -.has-success .help-block, -.has-success .control-label, -.has-success .radio, -.has-success .checkbox, -.has-success .radio-inline, -.has-success .checkbox-inline { - color: #3c763d; -} -.has-success .form-control { - border-color: #3c763d; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); -} -.has-success .form-control:focus { - border-color: #2b542c; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075), 0 0 6px #67b168; - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075), 0 0 6px #67b168; -} -.has-success .input-group-addon { - color: #3c763d; - border-color: #3c763d; - background-color: #dff0d8; -} -.has-success .form-control-feedback { - color: #3c763d; -} -.has-warning .help-block, -.has-warning .control-label, -.has-warning .radio, -.has-warning .checkbox, -.has-warning .radio-inline, -.has-warning .checkbox-inline { - color: #8a6d3b; -} -.has-warning .form-control { - border-color: #8a6d3b; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); -} -.has-warning .form-control:focus { - border-color: #66512c; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075), 0 0 6px #c0a16b; - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075), 0 0 6px #c0a16b; -} -.has-warning .input-group-addon { - color: #8a6d3b; - border-color: #8a6d3b; - background-color: #fcf8e3; -} -.has-warning .form-control-feedback { - color: #8a6d3b; -} -.has-error .help-block, -.has-error .control-label, -.has-error .radio, -.has-error .checkbox, -.has-error .radio-inline, -.has-error .checkbox-inline { - color: #a94442; -} -.has-error .form-control { - border-color: #a94442; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075); -} -.has-error .form-control:focus { - border-color: #843534; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075), 0 0 6px #ce8483; - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.075), 0 0 6px #ce8483; -} -.has-error .input-group-addon { - color: #a94442; - border-color: #a94442; - background-color: #f2dede; -} -.has-error .form-control-feedback { - color: #a94442; -} -.has-feedback label.sr-only ~ .form-control-feedback { - top: 0; -} -.help-block { - display: block; - margin-top: 5px; - margin-bottom: 10px; - color: #737373; -} -@media (min-width: 768px) { - .form-inline .form-group { - display: inline-block; - margin-bottom: 0; - vertical-align: middle; - } - .form-inline .form-control { - display: inline-block; - width: auto; - vertical-align: middle; - } - .form-inline .input-group { - display: inline-table; - vertical-align: middle; - } - .form-inline .input-group .input-group-addon, - .form-inline .input-group .input-group-btn, - .form-inline .input-group .form-control { - width: auto; - } - .form-inline .input-group > .form-control { - width: 100%; - } - .form-inline .control-label { - margin-bottom: 0; - vertical-align: middle; - } - .form-inline .radio, - .form-inline .checkbox { - display: inline-block; - margin-top: 0; - margin-bottom: 0; - vertical-align: middle; - } - .form-inline .radio label, - .form-inline .checkbox label { - padding-left: 0; - } - .form-inline .radio input[type="radio"], - .form-inline .checkbox input[type="checkbox"] { - position: relative; - margin-left: 0; - } - .form-inline .has-feedback .form-control-feedback { - top: 0; - } -} -.form-horizontal .radio, -.form-horizontal .checkbox, -.form-horizontal .radio-inline, -.form-horizontal .checkbox-inline { - margin-top: 0; - margin-bottom: 0; - padding-top: 7px; -} -.form-horizontal .radio, -.form-horizontal .checkbox { - min-height: 24px; -} -.form-horizontal .form-group { - margin-left: -15px; - margin-right: -15px; -} -@media (min-width: 768px) { - .form-horizontal .control-label { - text-align: right; - margin-bottom: 0; - padding-top: 7px; - } -} -.form-horizontal .has-feedback .form-control-feedback { - top: 0; - right: 15px; -} -@media (min-width: 768px) { - .form-horizontal .form-group-lg .control-label { - padding-top: 14.3px; - } -} -@media (min-width: 768px) { - .form-horizontal .form-group-sm .control-label { - padding-top: 6px; - } -} - -.tooltip { - position: absolute; - z-index: 1070; - display: block; - visibility: visible; - font-size: 11px; - line-height: 1.4; - opacity: 0; - filter: alpha(opacity=0); -} -.tooltip.in { - opacity: 0.9; - filter: alpha(opacity=90); -} -.tooltip.top { - margin-top: -3px; - padding: 5px 0; -} -.tooltip.right { - margin-left: 3px; - padding: 0 5px; -} -.tooltip.bottom { - margin-top: 3px; - padding: 5px 0; -} -.tooltip.left { - margin-left: -3px; - padding: 0 5px; -} -.tooltip-inner { - max-width: 200px; - padding: 3px 8px; - color: #ffffff; - text-align: center; - text-decoration: none; - background-color: #000000; - border-radius: 4px; -} -.tooltip-arrow { - position: absolute; - width: 0; - height: 0; - border-color: transparent; - border-style: solid; -} -.tooltip.top .tooltip-arrow { - bottom: 0; - left: 50%; - margin-left: -5px; - border-width: 5px 5px 0; - border-top-color: #000000; -} -.tooltip.top-left .tooltip-arrow { - bottom: 0; - left: 5px; - border-width: 5px 5px 0; - border-top-color: #000000; -} -.tooltip.top-right .tooltip-arrow { - bottom: 0; - right: 5px; - border-width: 5px 5px 0; - border-top-color: #000000; -} -.tooltip.right .tooltip-arrow { - top: 50%; - left: 0; - margin-top: -5px; - border-width: 5px 5px 5px 0; - border-right-color: #000000; -} -.tooltip.left .tooltip-arrow { - top: 50%; - right: 0; - margin-top: -5px; - border-width: 5px 0 5px 5px; - border-left-color: #000000; -} -.tooltip.bottom .tooltip-arrow { - top: 0; - left: 50%; - margin-left: -5px; - border-width: 0 5px 5px; - border-bottom-color: #000000; -} -.tooltip.bottom-left .tooltip-arrow { - top: 0; - left: 5px; - border-width: 0 5px 5px; - border-bottom-color: #000000; -} -.tooltip.bottom-right .tooltip-arrow { - top: 0; - right: 5px; - border-width: 0 5px 5px; - border-bottom-color: #000000; -} - -.modal-open { - overflow: hidden; -} -.modal { - display: none; - overflow: hidden; - position: fixed; - top: 0; - right: 0; - bottom: 0; - left: 0; - z-index: 1050; - -webkit-overflow-scrolling: touch; - outline: 0; -} -.modal.fade .modal-dialog { - -webkit-transform: translate3d(0, -25%, 0); - transform: translate3d(0, -25%, 0); - -webkit-transition: -webkit-transform 0.3s ease-out; - -moz-transition: -moz-transform 0.3s ease-out; - -o-transition: -o-transform 0.3s ease-out; - transition: transform 0.3s ease-out; -} -.modal.in .modal-dialog { - -webkit-transform: translate3d(0, 0, 0); - transform: translate3d(0, 0, 0); -} -.modal-open .modal { - overflow-x: hidden; - overflow-y: auto; -} -.modal-dialog { - position: relative; - width: auto; - margin: 10px; -} -.modal-content { - position: relative; - background-color: #ffffff; - border: 1px solid #999999; - border: 1px solid rgba(0, 0, 0, 0.2); - border-radius: 6px; - -webkit-box-shadow: 0 3px 9px rgba(0, 0, 0, 0.5); - box-shadow: 0 3px 9px rgba(0, 0, 0, 0.5); - background-clip: padding-box; - outline: 0; -} -.modal-backdrop { - position: fixed; - top: 0; - right: 0; - bottom: 0; - left: 0; - z-index: 1040; - background-color: #000000; -} -.modal-backdrop.fade { - opacity: 0; - filter: alpha(opacity=0); -} -.modal-backdrop.in { - opacity: 0.5; - filter: alpha(opacity=50); -} -.modal-header { - padding: 15px; - border-bottom: 1px solid #e5e5e5; - min-height: 16.42857143px; -} -.modal-header .close { - margin-top: -2px; -} -.modal-title { - margin: 0; - line-height: 1.42857143; -} -.modal-body { - position: relative; - padding: 15px; -} -.modal-footer { - padding: 15px; - text-align: right; - border-top: 1px solid #e5e5e5; -} -.modal-footer .btn + .btn { - margin-left: 5px; - margin-bottom: 0; -} -.modal-footer .btn-group .btn + .btn { - margin-left: -1px; -} -.modal-footer .btn-block + .btn-block { - margin-left: 0; -} -.modal-scrollbar-measure { - position: absolute; - top: -9999px; - width: 50px; - height: 50px; - overflow: scroll; -} -@media (min-width: 768px) { - .modal-dialog { - width: 600px; - margin: 30px auto; - } - .modal-content { - -webkit-box-shadow: 0 5px 15px rgba(0, 0, 0, 0.5); - box-shadow: 0 5px 15px rgba(0, 0, 0, 0.5); - } - .modal-sm { - width: 300px; - } -} -@media (min-width: 992px) { - .modal-lg { - width: 900px; - } -} - -.modal-footer:before, -.modal-footer:after { - content: " "; - display: table; -} -.navbar-collapse:after, -.modal-footer:after { - clear: both; -} - - -.alert { - padding: 15px; - margin-bottom: 17px; - border: 1px solid transparent; - border-radius: 0; -} -.alert h4 { - margin-top: 0; - color: inherit; -} -.alert .alert-link { - font-weight: bold; -} -.alert > p, -.alert > ul { - margin-bottom: 0; -} -.alert > p + p { - margin-top: 5px; -} -.alert-dismissable, -.alert-dismissible { - padding-right: 35px; -} -.alert-dismissable .close, -.alert-dismissible .close { - position: relative; - top: -2px; - right: -21px; - color: inherit; -} -.alert-success { - background-color: #dff0d8; - border-color: #d6e9c6; - color: #3c763d; -} -.alert-success hr { - border-top-color: #c9e2b3; -} -.alert-success .alert-link { - color: #2b542c; -} -.alert-info { - background-color: #d9edf7; - border-color: #bce8f1; - color: #31708f; -} -.alert-info hr { - border-top-color: #a6e1ec; -} -.alert-info .alert-link { - color: #245269; -} -.alert-warning { - background-color: #fcf8e3; - border-color: #faebcc; - color: #8a6d3b; -} -.alert-warning hr { - border-top-color: #f7e1b5; -} -.alert-warning .alert-link { - color: #66512c; -} -.alert-danger { - background-color: #f2dede; - border-color: #ebccd1; - color: #a94442; -} -.alert-danger hr { - border-top-color: #e4b9c0; -} - -.well { - min-height: 20px; - padding: 19px; - margin-bottom: 20px; - background-color: #f5f5f5; - border: 1px solid #e3e3e3; - border-radius: 4px; - -webkit-box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.05); - box-shadow: inset 0 1px 1px rgba(0, 0, 0, 0.05); -} -.well blockquote { - border-color: #ddd; - border-color: rgba(0, 0, 0, 0.15); -} -.well-lg { - padding: 24px; - border-radius: 6px; -} -.well-sm { - padding: 9px; - border-radius: 3px; -} -.close { - float: right; - font-size: 18px; - font-weight: bold; - line-height: 1; - color: #000000; - text-shadow: 0 1px 0 #ffffff; - opacity: 0.2; - filter: alpha(opacity=20); -} -.close:hover, -.close:focus { - color: #000000; - text-decoration: none; - cursor: pointer; - opacity: 0.5; - filter: alpha(opacity=50); -} -button.close { - padding: 0; - cursor: pointer; - background: transparent; - border: 0; - -webkit-appearance: none; -} - - -/* Manually added pager */ -.pagination { - display: inline-block; - padding-left: 0; - margin: 20px 0; - border-radius: 4px; -} -.pagination > li { - display: inline; -} -.pagination > li > a, -.pagination > li > span { - position: relative; - float: left; - padding: 6px 12px; - line-height: 1.42857143; - text-decoration: none; - color: #337ab7; - background-color: #ffffff; - border: 1px solid #dddddd; - margin-left: -1px; -} -.pagination > li:first-child > a, -.pagination > li:first-child > span { - margin-left: 0; - border-bottom-left-radius: 4px; - border-top-left-radius: 4px; -} -.pagination > li:last-child > a, -.pagination > li:last-child > span { - border-bottom-right-radius: 4px; - border-top-right-radius: 4px; -} -.pagination > li > a:hover, -.pagination > li > span:hover, -.pagination > li > a:focus, -.pagination > li > span:focus { - z-index: 2; - color: #23527c; - background-color: #eeeeee; - border-color: #dddddd; -} -.pagination > .active > a, -.pagination > .active > span, -.pagination > .active > a:hover, -.pagination > .active > span:hover, -.pagination > .active > a:focus, -.pagination > .active > span:focus { - z-index: 3; - color: #ffffff; - background-color: #337ab7; - border-color: #337ab7; - cursor: default; -} -.pagination > .disabled > span, -.pagination > .disabled > span:hover, -.pagination > .disabled > span:focus, -.pagination > .disabled > a, -.pagination > .disabled > a:hover, -.pagination > .disabled > a:focus { - color: #777777; - background-color: #ffffff; - border-color: #dddddd; - cursor: not-allowed; -} -.pagination-lg > li > a, -.pagination-lg > li > span { - padding: 10px 16px; - font-size: 18px; - line-height: 1.3333333; -} -.pagination-lg > li:first-child > a, -.pagination-lg > li:first-child > span { - border-bottom-left-radius: 6px; - border-top-left-radius: 6px; -} -.pagination-lg > li:last-child > a, -.pagination-lg > li:last-child > span { - border-bottom-right-radius: 6px; - border-top-right-radius: 6px; -} -.pagination-sm > li > a, -.pagination-sm > li > span { - padding: 5px 10px; - font-size: 12px; - line-height: 1.5; -} -.pagination-sm > li:first-child > a, -.pagination-sm > li:first-child > span { - border-bottom-left-radius: 3px; - border-top-left-radius: 3px; -} -.pagination-sm > li:last-child > a, -.pagination-sm > li:last-child > span { - border-bottom-right-radius: 3px; - border-top-right-radius: 3px; -} -.pager { - padding-left: 0; - margin: 20px 0; - list-style: none; - text-align: center; -} -.pager li { - display: inline; -} -.pager li > a, -.pager li > span { - display: inline-block; - padding: 5px 14px; - background-color: #ffffff; - border: 1px solid #dddddd; - border-radius: 15px; -} -.pager li > a:hover, -.pager li > a:focus { - text-decoration: none; - background-color: #eeeeee; -} -.pager .next > a, -.pager .next > span { - float: right; -} -.pager .previous > a, -.pager .previous > span { - float: left; -} -.pager .disabled > a, -.pager .disabled > a:hover, -.pager .disabled > a:focus, -.pager .disabled > span { - color: #777777; - background-color: #ffffff; - cursor: not-allowed; -} -.pager:before, -.pager:after { - content: " "; - display: table; -} -.pager:after { - clear: both; -} - -/* List and panel */ -.list-group { - margin-bottom: 20px; - padding-left: 0; -} -.list-group-item { - position: relative; - display: block; - padding: 10px 15px; - margin-bottom: -1px; - background-color: #ffffff; - border: 1px solid #dddddd; -} -.list-group-item:first-child { - border-top-right-radius: 4px; - border-top-left-radius: 4px; -} -.list-group-item:last-child { - margin-bottom: 0; - border-bottom-right-radius: 4px; - border-bottom-left-radius: 4px; -} -a.list-group-item, -button.list-group-item { - color: #555555; -} -a.list-group-item .list-group-item-heading, -button.list-group-item .list-group-item-heading { - color: #333333; -} -a.list-group-item:hover, -button.list-group-item:hover, -a.list-group-item:focus, -button.list-group-item:focus { - text-decoration: none; - color: #555555; - background-color: #f5f5f5; -} -button.list-group-item { - width: 100%; - text-align: left; -} -.list-group-item.disabled, -.list-group-item.disabled:hover, -.list-group-item.disabled:focus { - background-color: #eeeeee; - color: #777777; - cursor: not-allowed; -} -.list-group-item.disabled .list-group-item-heading, -.list-group-item.disabled:hover .list-group-item-heading, -.list-group-item.disabled:focus .list-group-item-heading { - color: inherit; -} -.list-group-item.disabled .list-group-item-text, -.list-group-item.disabled:hover .list-group-item-text, -.list-group-item.disabled:focus .list-group-item-text { - color: #777777; -} -.list-group-item.active, -.list-group-item.active:hover, -.list-group-item.active:focus { - z-index: 2; - color: #ffffff; - background-color: #337ab7; - border-color: #337ab7; -} -.list-group-item.active .list-group-item-heading, -.list-group-item.active:hover .list-group-item-heading, -.list-group-item.active:focus .list-group-item-heading, -.list-group-item.active .list-group-item-heading > small, -.list-group-item.active:hover .list-group-item-heading > small, -.list-group-item.active:focus .list-group-item-heading > small, -.list-group-item.active .list-group-item-heading > .small, -.list-group-item.active:hover .list-group-item-heading > .small, -.list-group-item.active:focus .list-group-item-heading > .small { - color: inherit; -} -.list-group-item.active .list-group-item-text, -.list-group-item.active:hover .list-group-item-text, -.list-group-item.active:focus .list-group-item-text { - color: #c7ddef; -} -.list-group-item-success { - color: #3c763d; - background-color: #dff0d8; -} -a.list-group-item-success, -button.list-group-item-success { - color: #3c763d; -} -a.list-group-item-success .list-group-item-heading, -button.list-group-item-success .list-group-item-heading { - color: inherit; -} -a.list-group-item-success:hover, -button.list-group-item-success:hover, -a.list-group-item-success:focus, -button.list-group-item-success:focus { - color: #3c763d; - background-color: #d0e9c6; -} -a.list-group-item-success.active, -button.list-group-item-success.active, -a.list-group-item-success.active:hover, -button.list-group-item-success.active:hover, -a.list-group-item-success.active:focus, -button.list-group-item-success.active:focus { - color: #fff; - background-color: #3c763d; - border-color: #3c763d; -} -.list-group-item-info { - color: #31708f; - background-color: #d9edf7; -} -a.list-group-item-info, -button.list-group-item-info { - color: #31708f; -} -a.list-group-item-info .list-group-item-heading, -button.list-group-item-info .list-group-item-heading { - color: inherit; -} -a.list-group-item-info:hover, -button.list-group-item-info:hover, -a.list-group-item-info:focus, -button.list-group-item-info:focus { - color: #31708f; - background-color: #c4e3f3; -} -a.list-group-item-info.active, -button.list-group-item-info.active, -a.list-group-item-info.active:hover, -button.list-group-item-info.active:hover, -a.list-group-item-info.active:focus, -button.list-group-item-info.active:focus { - color: #fff; - background-color: #31708f; - border-color: #31708f; -} -.list-group-item-warning { - color: #8a6d3b; - background-color: #fcf8e3; -} -a.list-group-item-warning, -button.list-group-item-warning { - color: #8a6d3b; -} -a.list-group-item-warning .list-group-item-heading, -button.list-group-item-warning .list-group-item-heading { - color: inherit; -} -a.list-group-item-warning:hover, -button.list-group-item-warning:hover, -a.list-group-item-warning:focus, -button.list-group-item-warning:focus { - color: #8a6d3b; - background-color: #faf2cc; -} -a.list-group-item-warning.active, -button.list-group-item-warning.active, -a.list-group-item-warning.active:hover, -button.list-group-item-warning.active:hover, -a.list-group-item-warning.active:focus, -button.list-group-item-warning.active:focus { - color: #fff; - background-color: #8a6d3b; - border-color: #8a6d3b; -} -.list-group-item-danger { - color: #a94442; - background-color: #f2dede; -} -a.list-group-item-danger, -button.list-group-item-danger { - color: #a94442; -} -a.list-group-item-danger .list-group-item-heading, -button.list-group-item-danger .list-group-item-heading { - color: inherit; -} -a.list-group-item-danger:hover, -button.list-group-item-danger:hover, -a.list-group-item-danger:focus, -button.list-group-item-danger:focus { - color: #a94442; - background-color: #ebcccc; -} -a.list-group-item-danger.active, -button.list-group-item-danger.active, -a.list-group-item-danger.active:hover, -button.list-group-item-danger.active:hover, -a.list-group-item-danger.active:focus, -button.list-group-item-danger.active:focus { - color: #fff; - background-color: #a94442; - border-color: #a94442; -} -.list-group-item-muted { - color: #777777; - background-color: #f7f7f7; -} -a.list-group-item-muted, -button.list-group-item-muted { - color: #777777; -} -a.list-group-item-muted .list-group-item-heading, -button.list-group-item-muted .list-group-item-heading { - color: inherit; -} -a.list-group-item-muted:hover, -button.list-group-item-muted:hover, -a.list-group-item-muted:focus, -button.list-group-item-muted:focus { - color: #777777; - background-color: #f1f1f1; -} -a.list-group-item-muted.active, -button.list-group-item-muted.active, -a.list-group-item-muted.active:hover, -button.list-group-item-muted.active:hover, -a.list-group-item-muted.active:focus, -button.list-group-item-muted.active:focus { - color: #fff; - background-color: #777777; - border-color: #777777; -} -.list-group-item-heading { - margin-top: 0; - margin-bottom: 0; -} -.list-group-item-text { - margin-top: 5px; - margin-bottom: 0; - line-height: 1.3; -} -.list-group-item-text:empty { - margin-top: 0; -} -.panel { - margin-bottom: 20px; - background-color: #ffffff; - border: 1px solid transparent; - border-radius: 4px; - -webkit-box-shadow: 0 1px 1px rgba(0, 0, 0, 0.05); - box-shadow: 0 1px 1px rgba(0, 0, 0, 0.05); -} -.panel-body { - padding: 15px; -} -.panel-heading { - padding: 10px 15px; - border-bottom: 1px solid transparent; - border-top-right-radius: 3px; - border-top-left-radius: 3px; -} -.panel-heading > .dropdown .dropdown-toggle { - color: inherit; -} -.panel-title { - margin-top: 0; - margin-bottom: 0; - font-size: 16px; - color: inherit; -} -.panel-title > a, -.panel-title > small, -.panel-title > .small, -.panel-title > small > a, -.panel-title > .small > a { - color: inherit; -} -.panel-footer { - padding: 10px 15px; - background-color: #f5f5f5; - border-top: 1px solid #dddddd; - border-bottom-right-radius: 3px; - border-bottom-left-radius: 3px; -} -.panel > .list-group, -.panel > .panel-collapse > .list-group { - margin-bottom: 0; -} -.panel > .list-group .list-group-item, -.panel > .panel-collapse > .list-group .list-group-item { - border-width: 1px 0; - border-radius: 0; -} -.panel > .list-group:first-child .list-group-item:first-child, -.panel > .panel-collapse > .list-group:first-child .list-group-item:first-child { - border-top: 0; - border-top-right-radius: 3px; - border-top-left-radius: 3px; -} -.panel > .list-group:last-child .list-group-item:last-child, -.panel > .panel-collapse > .list-group:last-child .list-group-item:last-child { - border-bottom: 0; - border-bottom-right-radius: 3px; - border-bottom-left-radius: 3px; -} -.panel > .panel-heading + .panel-collapse > .list-group .list-group-item:first-child { - border-top-right-radius: 0; - border-top-left-radius: 0; -} -.panel-heading + .list-group .list-group-item:first-child { - border-top-width: 0; -} -.list-group + .panel-footer { - border-top-width: 0; -} -.panel > .table, -.panel > .table-responsive > .table, -.panel > .panel-collapse > .table { - margin-bottom: 0; -} -.panel > .table caption, -.panel > .table-responsive > .table caption, -.panel > .panel-collapse > .table caption { - padding-left: 15px; - padding-right: 15px; -} -.panel > .table:first-child, -.panel > .table-responsive:first-child > .table:first-child { - border-top-right-radius: 3px; - border-top-left-radius: 3px; -} -.panel > .table:first-child > thead:first-child > tr:first-child, -.panel > .table-responsive:first-child > .table:first-child > thead:first-child > tr:first-child, -.panel > .table:first-child > tbody:first-child > tr:first-child, -.panel > .table-responsive:first-child > .table:first-child > tbody:first-child > tr:first-child { - border-top-left-radius: 3px; - border-top-right-radius: 3px; -} -.panel > .table:first-child > thead:first-child > tr:first-child td:first-child, -.panel > .table-responsive:first-child > .table:first-child > thead:first-child > tr:first-child td:first-child, -.panel > .table:first-child > tbody:first-child > tr:first-child td:first-child, -.panel > .table-responsive:first-child > .table:first-child > tbody:first-child > tr:first-child td:first-child, -.panel > .table:first-child > thead:first-child > tr:first-child th:first-child, -.panel > .table-responsive:first-child > .table:first-child > thead:first-child > tr:first-child th:first-child, -.panel > .table:first-child > tbody:first-child > tr:first-child th:first-child, -.panel > .table-responsive:first-child > .table:first-child > tbody:first-child > tr:first-child th:first-child { - border-top-left-radius: 3px; -} -.panel > .table:first-child > thead:first-child > tr:first-child td:last-child, -.panel > .table-responsive:first-child > .table:first-child > thead:first-child > tr:first-child td:last-child, -.panel > .table:first-child > tbody:first-child > tr:first-child td:last-child, -.panel > .table-responsive:first-child > .table:first-child > tbody:first-child > tr:first-child td:last-child, -.panel > .table:first-child > thead:first-child > tr:first-child th:last-child, -.panel > .table-responsive:first-child > .table:first-child > thead:first-child > tr:first-child th:last-child, -.panel > .table:first-child > tbody:first-child > tr:first-child th:last-child, -.panel > .table-responsive:first-child > .table:first-child > tbody:first-child > tr:first-child th:last-child { - border-top-right-radius: 3px; -} -.panel > .table:last-child, -.panel > .table-responsive:last-child > .table:last-child { - border-bottom-right-radius: 3px; - border-bottom-left-radius: 3px; -} -.panel > .table:last-child > tbody:last-child > tr:last-child, -.panel > .table-responsive:last-child > .table:last-child > tbody:last-child > tr:last-child, -.panel > .table:last-child > tfoot:last-child > tr:last-child, -.panel > .table-responsive:last-child > .table:last-child > tfoot:last-child > tr:last-child { - border-bottom-left-radius: 3px; - border-bottom-right-radius: 3px; -} -.panel > .table:last-child > tbody:last-child > tr:last-child td:first-child, -.panel > .table-responsive:last-child > .table:last-child > tbody:last-child > tr:last-child td:first-child, -.panel > .table:last-child > tfoot:last-child > tr:last-child td:first-child, -.panel > .table-responsive:last-child > .table:last-child > tfoot:last-child > tr:last-child td:first-child, -.panel > .table:last-child > tbody:last-child > tr:last-child th:first-child, -.panel > .table-responsive:last-child > .table:last-child > tbody:last-child > tr:last-child th:first-child, -.panel > .table:last-child > tfoot:last-child > tr:last-child th:first-child, -.panel > .table-responsive:last-child > .table:last-child > tfoot:last-child > tr:last-child th:first-child { - border-bottom-left-radius: 3px; -} -.panel > .table:last-child > tbody:last-child > tr:last-child td:last-child, -.panel > .table-responsive:last-child > .table:last-child > tbody:last-child > tr:last-child td:last-child, -.panel > .table:last-child > tfoot:last-child > tr:last-child td:last-child, -.panel > .table-responsive:last-child > .table:last-child > tfoot:last-child > tr:last-child td:last-child, -.panel > .table:last-child > tbody:last-child > tr:last-child th:last-child, -.panel > .table-responsive:last-child > .table:last-child > tbody:last-child > tr:last-child th:last-child, -.panel > .table:last-child > tfoot:last-child > tr:last-child th:last-child, -.panel > .table-responsive:last-child > .table:last-child > tfoot:last-child > tr:last-child th:last-child { - border-bottom-right-radius: 3px; -} -.panel > .panel-body + .table, -.panel > .panel-body + .table-responsive, -.panel > .table + .panel-body, -.panel > .table-responsive + .panel-body { - border-top: 1px solid #dddddd; -} -.panel > .table > tbody:first-child > tr:first-child th, -.panel > .table > tbody:first-child > tr:first-child td { - border-top: 0; -} -.panel > .table-bordered, -.panel > .table-responsive > .table-bordered { - border: 0; -} -.panel > .table-bordered > thead > tr > th:first-child, -.panel > .table-responsive > .table-bordered > thead > tr > th:first-child, -.panel > .table-bordered > tbody > tr > th:first-child, -.panel > .table-responsive > .table-bordered > tbody > tr > th:first-child, -.panel > .table-bordered > tfoot > tr > th:first-child, -.panel > .table-responsive > .table-bordered > tfoot > tr > th:first-child, -.panel > .table-bordered > thead > tr > td:first-child, -.panel > .table-responsive > .table-bordered > thead > tr > td:first-child, -.panel > .table-bordered > tbody > tr > td:first-child, -.panel > .table-responsive > .table-bordered > tbody > tr > td:first-child, -.panel > .table-bordered > tfoot > tr > td:first-child, -.panel > .table-responsive > .table-bordered > tfoot > tr > td:first-child { - border-left: 0; -} -.panel > .table-bordered > thead > tr > th:last-child, -.panel > .table-responsive > .table-bordered > thead > tr > th:last-child, -.panel > .table-bordered > tbody > tr > th:last-child, -.panel > .table-responsive > .table-bordered > tbody > tr > th:last-child, -.panel > .table-bordered > tfoot > tr > th:last-child, -.panel > .table-responsive > .table-bordered > tfoot > tr > th:last-child, -.panel > .table-bordered > thead > tr > td:last-child, -.panel > .table-responsive > .table-bordered > thead > tr > td:last-child, -.panel > .table-bordered > tbody > tr > td:last-child, -.panel > .table-responsive > .table-bordered > tbody > tr > td:last-child, -.panel > .table-bordered > tfoot > tr > td:last-child, -.panel > .table-responsive > .table-bordered > tfoot > tr > td:last-child { - border-right: 0; -} -.panel > .table-bordered > thead > tr:first-child > td, -.panel > .table-responsive > .table-bordered > thead > tr:first-child > td, -.panel > .table-bordered > tbody > tr:first-child > td, -.panel > .table-responsive > .table-bordered > tbody > tr:first-child > td, -.panel > .table-bordered > thead > tr:first-child > th, -.panel > .table-responsive > .table-bordered > thead > tr:first-child > th, -.panel > .table-bordered > tbody > tr:first-child > th, -.panel > .table-responsive > .table-bordered > tbody > tr:first-child > th { - border-bottom: 0; -} -.panel > .table-bordered > tbody > tr:last-child > td, -.panel > .table-responsive > .table-bordered > tbody > tr:last-child > td, -.panel > .table-bordered > tfoot > tr:last-child > td, -.panel > .table-responsive > .table-bordered > tfoot > tr:last-child > td, -.panel > .table-bordered > tbody > tr:last-child > th, -.panel > .table-responsive > .table-bordered > tbody > tr:last-child > th, -.panel > .table-bordered > tfoot > tr:last-child > th, -.panel > .table-responsive > .table-bordered > tfoot > tr:last-child > th { - border-bottom: 0; -} -.panel > .table-responsive { - border: 0; - margin-bottom: 0; -} -.panel-group { - margin-bottom: 20px; -} -.panel-group .panel { - margin-bottom: 0; - border-radius: 4px; -} -.panel-group .panel + .panel { - margin-top: 5px; -} -.panel-group .panel-heading { - border-bottom: 0; -} -.panel-group .panel-heading + .panel-collapse > .panel-body, -.panel-group .panel-heading + .panel-collapse > .list-group { - border-top: 1px solid #dddddd; -} -.panel-group .panel-footer { - border-top: 0; -} -.panel-group .panel-footer + .panel-collapse .panel-body { - border-bottom: 1px solid #dddddd; -} -.panel-default { - border-color: #dddddd; -} -.panel-default > .panel-heading { - color: #333333; - background-color: #f5f5f5; - border-color: #dddddd; -} -.panel-default > .panel-heading + .panel-collapse > .panel-body { - border-top-color: #dddddd; -} -.panel-default > .panel-heading .badge { - color: #f5f5f5; - background-color: #333333; -} -.panel-default > .panel-footer + .panel-collapse > .panel-body { - border-bottom-color: #dddddd; -} -.panel-primary { - border-color: #337ab7; -} -.panel-primary > .panel-heading { - color: #ffffff; - background-color: #337ab7; - border-color: #337ab7; -} -.panel-primary > .panel-heading + .panel-collapse > .panel-body { - border-top-color: #337ab7; -} -.panel-primary > .panel-heading .badge { - color: #337ab7; - background-color: #ffffff; -} -.panel-primary > .panel-footer + .panel-collapse > .panel-body { - border-bottom-color: #337ab7; -} -.panel-success { - border-color: #d6e9c6; -} -.panel-success > .panel-heading { - color: #3c763d; - background-color: #dff0d8; - border-color: #d6e9c6; -} -.panel-success > .panel-heading + .panel-collapse > .panel-body { - border-top-color: #d6e9c6; -} -.panel-success > .panel-heading .badge { - color: #dff0d8; - background-color: #3c763d; -} -.panel-success > .panel-footer + .panel-collapse > .panel-body { - border-bottom-color: #d6e9c6; -} -.panel-info { - border-color: #bce8f1; -} -.panel-info > .panel-heading { - color: #31708f; - background-color: #d9edf7; - border-color: #bce8f1; -} -.panel-info > .panel-heading + .panel-collapse > .panel-body { - border-top-color: #bce8f1; -} -.panel-info > .panel-heading .badge { - color: #d9edf7; - background-color: #31708f; -} -.panel-info > .panel-footer + .panel-collapse > .panel-body { - border-bottom-color: #bce8f1; -} -.panel-warning { - border-color: #faebcc; -} -.panel-warning > .panel-heading { - color: #8a6d3b; - background-color: #fcf8e3; - border-color: #faebcc; -} -.panel-warning > .panel-heading + .panel-collapse > .panel-body { - border-top-color: #faebcc; -} -.panel-warning > .panel-heading .badge { - color: #fcf8e3; - background-color: #8a6d3b; -} -.panel-warning > .panel-footer + .panel-collapse > .panel-body { - border-bottom-color: #faebcc; -} -.panel-danger { - border-color: #ebccd1; -} -.panel-danger > .panel-heading { - color: #a94442; - background-color: #f2dede; - border-color: #ebccd1; -} -.panel-danger > .panel-heading + .panel-collapse > .panel-body { - border-top-color: #ebccd1; -} -.panel-danger > .panel-heading .badge { - color: #f2dede; - background-color: #a94442; -} -.panel-danger > .panel-footer + .panel-collapse > .panel-body { - border-bottom-color: #ebccd1; -} - -/* Inline Group */ - -.input-group { - position: relative; - display: table; - border-collapse: separate; -} -.input-group[class*="col-"] { - float: none; - padding-left: 0; - padding-right: 0; -} -.input-group .form-control { - position: relative; - z-index: 2; - float: left; - width: 100%; - margin-bottom: 0; -} -.input-group .form-control:focus { - z-index: 3; -} -.input-group-lg > .form-control, -.input-group-lg > .input-group-addon, -.input-group-lg > .input-group-btn > .btn { - height: 41px; - padding: 10px 16px; - font-size: 15px; - line-height: 1.3333333; - border-radius: 6px; -} -select.input-group-lg > .form-control, -select.input-group-lg > .input-group-addon, -select.input-group-lg > .input-group-btn > .btn { - height: 41px; - line-height: 41px; -} -textarea.input-group-lg > .form-control, -textarea.input-group-lg > .input-group-addon, -textarea.input-group-lg > .input-group-btn > .btn, -select[multiple].input-group-lg > .form-control, -select[multiple].input-group-lg > .input-group-addon, -select[multiple].input-group-lg > .input-group-btn > .btn { - height: auto; -} -.input-group-sm > .form-control, -.input-group-sm > .input-group-addon, -.input-group-sm > .input-group-btn > .btn { - height: 30px; - padding: 5px 10px; - font-size: 12px; - line-height: 1.5; - border-radius: 3px; -} -select.input-group-sm > .form-control, -select.input-group-sm > .input-group-addon, -select.input-group-sm > .input-group-btn > .btn { - height: 30px; - line-height: 30px; -} -textarea.input-group-sm > .form-control, -textarea.input-group-sm > .input-group-addon, -textarea.input-group-sm > .input-group-btn > .btn, -select[multiple].input-group-sm > .form-control, -select[multiple].input-group-sm > .input-group-addon, -select[multiple].input-group-sm > .input-group-btn > .btn { - height: auto; -} -.input-group-addon, -.input-group-btn, -.input-group .form-control { - display: table-cell; -} -.input-group-addon:not(:first-child):not(:last-child), -.input-group-btn:not(:first-child):not(:last-child), -.input-group .form-control:not(:first-child):not(:last-child) { - border-radius: 0; -} -.input-group-addon, -.input-group-btn { - width: 1%; - white-space: nowrap; - vertical-align: middle; -} -.input-group-addon { - padding: 6px 12px; - font-size: 14px; - font-weight: normal; - line-height: 1; - color: #555555; - text-align: center; - background-color: #eeeeee; - border: 1px solid #cccccc; - border-radius: 4px; -} -.input-group-addon.input-sm { - padding: 5px 10px; - font-size: 12px; - border-radius: 3px; -} -.input-group-addon.input-lg { - padding: 10px 16px; - font-size: 15px; - border-radius: 6px; -} -.input-group-addon input[type="radio"], -.input-group-addon input[type="checkbox"] { - margin-top: 0; -} -.input-group .form-control:first-child, -.input-group-addon:first-child, -.input-group-btn:first-child > .btn, -.input-group-btn:first-child > .btn-group > .btn, -.input-group-btn:first-child > .dropdown-toggle, -.input-group-btn:last-child > .btn:not(:last-child):not(.dropdown-toggle), -.input-group-btn:last-child > .btn-group:not(:last-child) > .btn { - border-bottom-right-radius: 0; - border-top-right-radius: 0; -} -.input-group-addon:first-child { - border-right: 0; -} -.input-group .form-control:last-child, -.input-group-addon:last-child, -.input-group-btn:last-child > .btn, -.input-group-btn:last-child > .btn-group > .btn, -.input-group-btn:last-child > .dropdown-toggle, -.input-group-btn:first-child > .btn:not(:first-child), -.input-group-btn:first-child > .btn-group:not(:first-child) > .btn { - border-bottom-left-radius: 0; - border-top-left-radius: 0; -} -.input-group-addon:last-child { - border-left: 0; -} -.input-group-btn { - position: relative; - font-size: 0; - white-space: nowrap; -} -.input-group-btn > .btn { - position: relative; -} -.input-group-btn > .btn + .btn { - margin-left: -1px; -} -.input-group-btn > .btn:hover, -.input-group-btn > .btn:focus, -.input-group-btn > .btn:active { - z-index: 2; -} -.input-group-btn:first-child > .btn, -.input-group-btn:first-child > .btn-group { - margin-right: -1px; -} -.input-group-btn:last-child > .btn, -.input-group-btn:last-child > .btn-group { - z-index: 2; - margin-left: -1px; -} -.clearfix:before, -.clearfix:after, -.form-horizontal .form-group:before, -.form-horizontal .form-group:after { - content: " "; - display: table; -} -.clearfix:after, -.form-horizontal .form-group:after { - clear: both; -} diff --git a/data/core.telegram.org/css/core-widgets.css b/data/core.telegram.org/css/core-widgets.css deleted file mode 100644 index 6b86cfbf74..0000000000 --- a/data/core.telegram.org/css/core-widgets.css +++ /dev/null @@ -1,105 +0,0 @@ -.widget-accent-colors { - display: flex; - flex-wrap: nowrap; - justify-content: space-between; - max-width: 480px; - margin: 3px 0 0; -} -.widget-accent-colors .widget-accent-color-item { - position: relative; - flex-basis: 42px; - font-weight: normal; - text-align: center; - cursor: pointer; -} -.widget-accent-color-item input.radio { - position: absolute; - left: -5000px; -} -.widget-accent-color-item input.radio + .widget-color-circle:after { - position: absolute; - left: 0; - display: inline-block; - content: ''; - width: 100%; - height: 100%; - border-radius: 50%; - vertical-align: top; - background: url('data:image/svg+xml,%3Csvg height="15" viewBox="0 0 18 15" width="18" xmlns="http://www.w3.org/2000/svg"%3E%3Cg fill="%23fff" fill-rule="evenodd"%3E%3Crect height="8" rx="1.472727" transform="matrix(.70710678 -.70710678 .70710678 .70710678 -5.753048 6.110913)" width="3" x="3" y="6"/%3E%3Crect height="3" rx="1.472727" transform="matrix(.70710678 -.70710678 .70710678 .70710678 -2.081475 9.974874)" width="16" x="3" y="6"/%3E%3C/g%3E%3C/svg%3E') no-repeat center 11px; - transition: transform 0.12s linear; - transform: scale3d(0, 0, 1); -} -.widget-accent-color-item input.radio + .widget-color-circle.bordered, -.widget-accent-color-item input.radio:checked + .widget-color-circle-custom.bordered { - box-shadow: inset 0 0 0 1px #eaeaea; -} -.widget-accent-color-item input.radio + .widget-color-circle-custom.bordered { - border: none; -} -.widget-accent-color-item input.radio + .widget-color-circle.light:after { - background-image: url('data:image/svg+xml,%3Csvg height="15" viewBox="0 0 18 15" width="18" xmlns="http://www.w3.org/2000/svg"%3E%3Cg fill="%2315202b" fill-rule="evenodd"%3E%3Crect height="8" rx="1.472727" transform="matrix(.70710678 -.70710678 .70710678 .70710678 -5.753048 6.110913)" width="3" x="3" y="6"/%3E%3Crect height="3" rx="1.472727" transform="matrix(.70710678 -.70710678 .70710678 .70710678 -2.081475 9.974874)" width="16" x="3" y="6"/%3E%3C/g%3E%3C/svg%3E'); -} -.widget-accent-color-item input.radio:checked + .widget-color-circle:after { - transform: scale3d(1, 1, 1); -} -.widget-color-circle { - position: relative; - display: inline-block; - vertical-align: top; - width: 36px; - height: 36px; - border-radius: 50%; - background-color: #319BE6; - transition: background-color 0.12s ease, box-shadow 0.12s ease; -} -.widget-color-circle-custom { - background-color: #F5F5F5; - color: #F5F5F5; -} -.widget-accent-color-item input.radio + .widget-color-circle-custom:before { - position: absolute; - left: 0; - display: inline-block; - content: ''; - width: 100%; - height: 100%; - vertical-align: top; - background: url('data:image/svg+xml,%3Csvg height="14" viewBox="0 0 15 14" width="15" xmlns="http://www.w3.org/2000/svg"%3E%3Cpath d="m3.9468491 8.55631162c-1.3103539 0-2.36810946 1.04207749-2.36810946 2.33300928 0 1.0187474-.91566899 1.5553396-1.57873964 1.5553396.72622023.9487571 1.96553085 1.5553395 3.15747928 1.5553395 1.7445073 0 3.15747928-1.3920289 3.15747928-3.1106791 0-1.29093179-1.05775556-2.33300928-2.36810946-2.33300928zm10.8222602-7.28676572-1.0577555-1.04207749c-.3078543-.30329121-.8051572-.30329121-1.1130115 0l-7.07275356 6.96792112 2.170767 2.13859186 7.07275356-6.96792112c.3078543-.30329121.3078543-.79322316 0-1.09651437z" fill="%23bdbdbd"/%3E%3C/svg%3E') no-repeat center; - transition: opacity 0.12s ease; -} -.widget-color-label { - font-size: 12px; - line-height: 14px; - margin-top: 8px; - color: #333; -} -.widget-color-label-custom { - transition: opacity 0.12s ease; - position: absolute; - width: 100%; -} -.widget-accent-color-field-item { - transition: all .2s ease; - opacity: 0; -} -.widget-accent-color-field-item input.widget-accent-color-field { - font-size: 12px !important; - line-height: 14px !important; - text-transform: uppercase; - position: relative; - text-align: center; - margin-top: 3px !important; - padding: 5px 0 !important; - color: #222 !important; - width: 52px !important; -} -.widget-accent-color-item input.radio:checked ~ .widget-accent-color-field-item { - opacity: 1; -} -.widget-accent-color-item input.radio:checked ~ .widget-color-circle-custom { - background-color: currentColor !important; -} -.widget-accent-color-item input.radio:checked + .widget-color-circle-custom:before, -.widget-accent-color-item input.radio:checked ~ .widget-color-label-custom { - opacity: 0; -} diff --git a/data/core.telegram.org/css/telegram-extra.css b/data/core.telegram.org/css/telegram-extra.css deleted file mode 100644 index 6b408d1ae4..0000000000 --- a/data/core.telegram.org/css/telegram-extra.css +++ /dev/null @@ -1,246 +0,0 @@ -.telegram-passport-wrap { - overflow: hidden; -} -.telegram-passport-form { - position: relative; -} -.telegram-passport-form .control-label { - line-height: 20px; - padding-top: 11px; -} -.telegram-passport-header { - font-size: 18px; - line-height: 27px; -} -.telegram-passport-greeting { - margin-right: 10px; -} -.telegram-passport-greeting a, -.telegram-passport-greeting a:hover { - color: inherit; -} -.telegram-passport-logout { - font-size: 16px; - font-weight: normal; -} -.telegram-passport-login-wrap { - margin: 10px 0 50px; - text-align: center; -} -.telegram-passport-relogin-wrap { - margin: 10px 0 50px; - text-align: center; -} -.telegram-passport-pending { - padding: 20px 0 40px; - text-align: center; -} -.telegram-passport-block-header, -.telegram-passport-item { - border-bottom: 1px solid #e7e7e7; -} -.telegram-passport-block-header, -.telegram-passport-item-name, -.telegram-passport-item-value { - padding: 15px 0; - line-height: 20px; -} -.telegram-passport-block-header { - margin: 25px 0 0; -} -.telegram-passport-item-name { - margin-right: 15px; - margin-bottom: -5px; - padding-bottom: 0; - float: left; -} -.telegram-passport-item-files, -.telegram-passport-item-value { - clear: left; - font-weight: bold; -} -.telegram-passport-item-value { - transition: color .12s linear; -} -.telegram-passport-item-files { - padding: 6px 0; -} -.telegram-passport-item-file { - padding: 6px 0; - min-height: 60px; -} -.telegram-passport-item .telegram-passport-checkbox-right .checkbox-input { - margin: 0; -} -.telegram-passport-item .telegram-passport-checkbox-right { - float: right; - margin: 40px -5px 10px; - padding: 5px; -} -.telegram-passport-item-files .checkbox-item-block { - margin: 6px 0; -} -.telegram-passport-item-file .telegram-passport-checkbox-right { - margin: 9px -5px; -} -.telegram-passport-scan-thumb { - display: inline-block; - width: 64px; - height: 48px; - background: #f7f7f7 no-repeat center; - background-size: cover; - float: left; - border-radius: 3px; - margin-right: 15px; -} -.telegram-passport-scan-name { - display: inline-block; - font-size: 14px; - padding: 3px 0 0; - transition: color .12s linear; - color: #2e87ca; -} -.telegram-passport-scan-size { - font-size: 13px; - padding: 1px 0 0; - font-weight: normal; - transition: color .12s linear; - color: #999; -} -.telegram-passport-item-value, -.telegram-passport-scan-info { - margin-right: 42px; -} -.telegram-passport-item .checkbox-item-block .checkbox-label { - transition: color .12s linear; -} -.telegram-passport-item.item-rejected .telegram-passport-item-value, -.telegram-passport-item-file.item-rejected .telegram-passport-scan-name, -.telegram-passport-item-file.item-rejected .telegram-passport-scan-size, -.telegram-passport-item .checkbox-item-block.item-rejected .checkbox-label { - color: #c93c3c; -} - -.telegram-passport-item .checkbox-item-block .checkbox-input-icon:before { - border-color: #eb5454; - background-color: #eb5454; - background-position: -3px -119px; -} -.telegram-passport-item .checkbox-item-block input.checkbox:checked + .checkbox-input .ripple { - background-color: rgba(235, 84, 84, .2); -} -.telegram-passport-errors-wrap { - text-align: right; - margin: 20px 16px 0; -} -.btn.telegram-passport-errors { - font-size: 15px; - font-weight: 500; - line-height: 20px; - border-radius: 6px; - background-color: transparent; - padding: 8px 16px 10px; - margin: 4px -16px; - border: none; - color: #c93c3c; - position: relative; - z-index: 1; -} -.btn.telegram-passport-errors:hover { - background-color: #f7e3e3; -} -.btn.telegram-passport-errors:focus { - outline: none; -} -.btn.telegram-passport-errors:active { - box-shadow: none; -} -.telegram-passport-errors-icon { - display: inline-block; - vertical-align: top; - width: 18px; - height: 19px; - margin: 1px 12px 0 0; - background: url(/img/passport_bug.png) no-repeat 0 0; -} -@media (-webkit-min-device-pixel-ratio: 2), (min-resolution: 192dpi) { - .telegram-passport-errors-icon { - background-image: url(/img/passport_bug_2x.png); - background-size: 18px 19px; - } -} -.telegram-passport-errors-sent { - font-size: 14px; - line-height: 20px; - padding: 13px 24px 0 0; - color: #999; - transition: opacity .12s linear; - opacity: 0; -} -.telegram-passport-errors-sent.shown { - opacity: 1; -} - -@media (min-width: 768px) { - .telegram-passport-login-wrap { - text-align: left; - } - .telegram-passport-relogin-wrap { - text-align: left; - margin: 50px 0 50px 240px; - } - .telegram-passport-item-files, - .telegram-passport-item-value { - clear: none; - margin-left: 240px; - } - .telegram-passport-item .telegram-passport-checkbox-right { - margin-top: 10px; - } - .telegram-passport-item-file .telegram-passport-checkbox-right { - margin: 9px -5px; - } - .telegram-passport-errors-wrap { - position: absolute; - right: 0; - margin: 50px 0 0; - } -} - -.telegram-passport-form .sub-control-label { - text-align: left; - margin: 11px 0 6px; -} -.telegram-passport-form .sub-control-label .radio-label { - font-weight: bold; -} -.telegram-passport-form .sub-control-label .radio-item + .radio-item, -.telegram-passport-form .sub-control-label .checkbox-item + .checkbox-item { - margin-left: 25px; -} -.telegram-passport-form label.control-label .radio-label { - font-weight: bold; -} -.passport-opt, -.passport-opt-col { - display: inline-block; - margin-left: 31px; - margin-top: -10px; -} -.passport-opt + .passport-opt, -.passport-opt-col + .passport-opt-col { - margin-left: 0; -} -@media (min-width: 992px) { - .passport-opt-col { - margin-left: 0; - margin-top: 0; - text-align: center; - } - .passport-opt-col .checkbox-label { - text-align: left; - } - .passport-opt-col .checkbox-item input.checkbox ~ .checkbox-label { - display: none; - } -} diff --git a/data/core.telegram.org/getProxyConfig.html b/data/core.telegram.org/getProxyConfig.html deleted file mode 100644 index 7238f2dd28..0000000000 --- a/data/core.telegram.org/getProxyConfig.html +++ /dev/null @@ -1,24 +0,0 @@ -# force_probability 10 10 -default 2; -proxy_for 1 149.154.X.X:8888; -proxy_for -1 149.154.X.X:8888; -proxy_for 2 149.154.X.X:8888; -proxy_for -2 149.154.X.X:8888; -proxy_for 3 149.154.X.X:8888; -proxy_for -3 149.154.X.X:8888; -proxy_for 4 91.108.X.X:8888; -proxy_for 4 91.108.X.X:8888; -proxy_for 4 91.108.X.X:8888; -proxy_for 4 91.108.X.X:8888; -proxy_for 4 91.108.X.X:8888; -proxy_for 4 91.108.X.X:8888; -proxy_for 4 91.108.X.X:8888; -proxy_for 4 91.108.X.X:8888; -proxy_for 4 91.108.X.X:8888; -proxy_for 4 91.108.X.X:8888; -proxy_for -4 149.154.X.X:8888; -proxy_for -4 149.154.X.X:8888; -proxy_for 5 91.108.X.X:8888; -proxy_for 5 91.108.X.X:8888; -proxy_for -5 91.108.X.X:8888; -proxy_for -5 91.108.X.X:8888; diff --git a/data/core.telegram.org/import-stickers.html b/data/core.telegram.org/import-stickers.html deleted file mode 100644 index c784348887..0000000000 --- a/data/core.telegram.org/import-stickers.html +++ /dev/null @@ -1,159 +0,0 @@ - - - - - Importing Stickers to Telegram - - - - - - - - - - - - - -
- -
-
-
-
-

Importing Stickers to Telegram

- -

The easiest way to create stickers on Telegram is to simply upload them using the @stickers bot. This bot can help you upload new stickers, create sticker packs and get usage stats for your stickers and packs.

-

Telegram also offers a platform for developers of apps that help users make their own stickers. For example, apps that allow people to upload pictures of themselves and turn them into stickers.

-

Who is this for?

-

USE this:

-
    -
  • To help people make their own unique custom stickers.
  • -
  • To help people migrate their unique custom stickers they created from another platform.
  • -
-

DON'T use this:

- -

In short, if a set of stickers is already available on Telegram – there's no need to import it!

-

Sticker Importing Apps

-

As of version 7.8, Telegram apps support a simple API for importing stickers.

-
- -
- -
-

WARNING: Each time a user imports stickers, a new sticker pack is created on Telegram. Do not use the importing feature to share stickers you made with other users. If you want to share your stickers, simply upload them using @stickers and share the link of your pack. For example, here's a link to install some Duck Stickers.

-
-

Importing SDKs

-

We have created libraries and sample apps for iOS and Android which you can use to implement importing stickers to Telegram from your app.

-

Sticker Formats

-

Telegram apps support two sticker types. Regardless of the type, each sticker must be associated with at least one emoji that expresses the emotion corresponding to the sticker.

-

Animated Stickers

-

Must be in TGS format, created using the Bodymovin-TG plugin for Adobe After Effects.

-
-

Note: Animated .WEBP is NOT currently supported, only static .WEBP is supported for static stickers. Animated stickers must be in .TGS format. You can also import .WEBM video stickers.

-
-

Max. size: 64 KB
Dimensions: 512x512 px
FPS: 30-60 FPS
Max. duration: 3 seconds

-
-

For full technical details on Telegram animated stickers, see this page.

-
-

Video Stickers

-

Must be in WEBM format with VP9 and alpha channel encoding (transparency is a temporary requirement).

-

Max. size: 256 KB
Max. dimensions: 512x512 px, at least one side of the image must be 512px.
FPS: 30
Max. duration: 3 seconds

-

Static Stickers

-

Must be in PNG or WEBP format with a transparent layer. All static stickers should use white stroke and shadow, exactly like in this example: StickerExample.psd

-

Max. size: 512 KB
Max. dimensions: 512x512 px, at least one side of the image must be 512px.

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/js/core-widgets.js b/data/core.telegram.org/js/core-widgets.js deleted file mode 100644 index 67bf4c7d05..0000000000 --- a/data/core.telegram.org/js/core-widgets.js +++ /dev/null @@ -1,279 +0,0 @@ -function fixColor(color) { - color = color.toUpperCase(); - if (color.length == 1 || color.length == 2) { - color = color + color + color; - } else if (color.length > 3 && color.length < 6) { - color = color.substr(0, 3); - } else if (color.length > 6) { - color = color.substr(0, 6); - } - return color; -} - -function isColorLight(color, k) { - var hsl = rgb2hsl(color); - if (typeof k === 'undefined') k = 0.8; - if (k > 0) return (hsl.l > k); - return (hsl.l < (1 + k)); -} - -function rgb2hsl(rgb) { - rgb = fixColor(rgb); - if (rgb.length == 3) { - rgb = rgb[0] + rgb[0] + rgb[1] + rgb[1] + rgb[2] + rgb[2]; - } - var r = parseInt(rgb.substr(0, 2), 16); - var g = parseInt(rgb.substr(2, 2), 16); - var b = parseInt(rgb.substr(4, 2), 16); - r /= 255; g /= 255; b /= 255; - var max = Math.max(r, g, b), - min = Math.min(r, g, b); - var h, s, l = (max + min) / 2; - if (max == min) { - h = s = 0; // achromatic - } else { - var d = max - min; - s = l > 0.5 ? d / (2 - max - min) : d / (max + min); - switch (max) { - case r: h = (g - b) / d + (g < b ? 6 : 0); break; - case g: h = (b - r) / d + 2; break; - case b: h = (r - g) / d + 4; break; - } - h /= 6; - } - return {h: h, s: s, l: l}; -} - -var PostWidget = { - options: {}, - init: function(options) { - var form = $('#post_widget_config').get(0); - if (!form) return; - PostWidget.options = options || {}; - $('.form-telegram input.form-control[type="text"]').on('change blur', function() { - PostWidget.update(); - }); - $('.form-telegram input.radio, .form-telegram input.checkbox').on('change', function() { - var is_dark = (this.getAttribute('name') == 'dark'); - PostWidget.update(is_dark); - }); - $('.widget-accent-color-item input.radio').on('change', function() { - if (this.value == 'custom') { - $('.widget-accent-color-field').select(); - } - PostWidget.update(); - }); - $('.widget-accent-color-field').on('input', function() { - var val = this.value; - this.value = val.toUpperCase().replace(/[^0-9A-F]+/g, ''); - var color = fixColor(this.value); - $('.widget-color-circle-custom').css('color', color ? '#' + color : '').toggleClass('light', isColorLight(color)).toggleClass('bordered', isColorLight(color, 0.95)); - }); - $('.widget-accent-color-field').on('focus', function() { - $('.widget-accent-color-item .radio[value="custom"]').prop('checked', true); - PostWidget.update(); - }); - PostWidget.update(); - initRipple(); - }, - update: function(toggle_dark) { - var options = PostWidget.options || {}; - var form = $('#post_widget_config').get(0); - if (!form) return; - var tfi = $('#post_link').parents('.textfield-item'); - var post_link = $('#post_link').val() || options.default_link, - match; - if (match = post_link.match(/^(?:(?:https?):\/\/)?(?:t\.me|telegram\.me|telegram\.dog)\/([a-zA-Z0-9_]+\/\d+)(?:\?(.*))?$/i)) { - var post_id = match[1], suffix = match[2] || ''; - var querystring = suffix.split('#')[0]; - var str_values = querystring.split('&'); - var query = {}; - for (var i = 0; i < str_values.length; i++) { - var key_value = str_values[i].split('='); - var key = decodeURIComponent(key_value[0]); - var value = key_value.length > 1 ? decodeURIComponent(key_value[1]) : null; - query[key] = value; - } - var single = typeof query.single !== 'undefined'; - var comment_id = parseInt(query.comment); - } else { - tfi.addClass('is-invalid'); - $('#post_link_error').html(options.link_error); - $('#post_link').one('input', function() { - tfi.removeClass('is-invalid'); - }); - return; - } - tfi.removeClass('is-invalid'); - var width = form.width.value; - if (!width) width = '100%'; - var author_photo = form.author_photo.value; - var dark = form.dark.checked; - var dark_colors = {}; - $('.widget-accent-color-item[data-color]').each(function() { - var color = $(this).attr('data-color'); - var dark_color = $(this).attr('data-dark-color'); - var bg_color = $(this).attr(dark ? 'data-dark-color' : 'data-bg-color'); - var text = $(this).attr(dark ? 'data-dark-text' : 'data-text'); - var cur_color = dark && dark_color ? dark_color : color; - dark_colors[color] = dark_color; - $('.widget-color-circle', this).css('backgroundColor', '#' + bg_color).toggleClass('light', isColorLight(cur_color)).toggleClass('bordered', isColorLight(cur_color, 0.95)); - if (text) { - $('.widget-color-label', this).text(text); - } - }); - var color = form.color.value; - var dark_color = ''; - var customcolor = form.customcolor.value; - if (color == 'default') { - color = ''; - dark_color = ''; - } else if (color == 'custom') { - color = fixColor(customcolor); - if (color != customcolor) { - form.customcolor.value = color; - $('.widget-color-circle-custom').css('color', color ? '#' + color : '').toggleClass('light', isColorLight(color)).toggleClass('bordered', isColorLight(color, 0.95)); - } - dark_color = color; - } else { - dark_color = dark_colors[color] || color; - } - if (!color) { - color = ''; - dark_color = ''; - $('.widget-accent-color-item .radio[value="default"]').prop('checked', true); - var custom_default = form.customcolor.defaultValue; - form.customcolor.value = custom_default; - $('.widget-color-circle-custom').css('color', custom_default ? '#' + custom_default : '').toggleClass('light', isColorLight(custom_default)).toggleClass('bordered', isColorLight(custom_default, 0.95)); - } - var code = ''; - $('#embed_code').val(code); - $('#embed_code').height(0); - $('#embed_code').height($('#embed_code').get(0).scrollHeight); - if (PostWidget.lastCode != code) { - PostWidget.lastCode = code; - $('#widget_container').toggleClass('dark', !!dark); - if (toggle_dark) { - var frame = $('#widget_container iframe').get(0); - Telegram.setWidgetOptions({dark: dark}, frame); - } else { - $('#widget_container').html(code); - } - } - } -}; - -var DiscussionWidget = { - options: {}, - init: function(options) { - var form = $('#discussion_widget_config').get(0); - if (!form) return; - DiscussionWidget.options = options || {}; - $('.form-telegram input.form-control[type="text"]').on('change blur', function() { - DiscussionWidget.update(); - }); - $('.form-telegram input.checkbox').on('change', function() { - var is_dark = (this.getAttribute('name') == 'dark'); - DiscussionWidget.update(is_dark); - }); - $('.widget-accent-color-item input.radio').on('change', function() { - if (this.value == 'custom') { - $('.widget-accent-color-field').select(); - } - DiscussionWidget.update(); - }); - $('.widget-accent-color-field').on('input', function() { - var val = this.value; - this.value = val.toUpperCase().replace(/[^0-9A-F]+/g, ''); - var color = fixColor(this.value); - $('.widget-color-circle-custom').css('color', color ? '#' + color : '').toggleClass('light', isColorLight(color)).toggleClass('bordered', isColorLight(color, 0.95)); - }); - $('.widget-accent-color-field').on('focus', function() { - $('.widget-accent-color-item .radio[value="custom"]').prop('checked', true); - DiscussionWidget.update(); - }); - DiscussionWidget.update(); - initRipple(); - }, - update: function(toggle_dark) { - var options = DiscussionWidget.options || {}; - var form = $('#discussion_widget_config').get(0); - if (!form) return; - var tfi = $('#post_link').parents('.textfield-item'); - var post_link = $('#post_link').val() || options.default_link, - match; - var post_full_id = '', post_id = 0; - if (match = post_link.match(/^(?:(?:https?):\/\/)?(?:t\.me|telegram\.me|telegram\.dog)\/([a-zA-Z0-9_]+(\/\d+)?)/i)) { - post_full_id = match[1]; - post_id = match[2] || 0; - } else { - tfi.addClass('is-invalid'); - $('#post_link_error').html(options.link_error); - $('#post_link').one('input', function() { - tfi.removeClass('is-invalid'); - }); - return; - } - $('.canonical-helper', form).toggleClass('hide', !!post_id); - tfi.removeClass('is-invalid'); - var limit = parseInt(form.comments_limit.value) || 5; - var real_limit = Math.max(3, Math.min(50, limit)); - form.comments_limit.value = real_limit; - var height = parseInt(form.height.value) || 0; - var real_height = height > 0 ? Math.max(300, height) : 0; - form.height.value = real_height || ''; - var dark = form.dark.checked; - var dark_colors = {}; - $('.widget-accent-color-item[data-color]').each(function() { - var color = $(this).attr('data-color'); - var dark_color = $(this).attr('data-dark-color'); - var bg_color = $(this).attr(dark ? 'data-dark-color' : 'data-bg-color'); - var text = $(this).attr(dark ? 'data-dark-text' : 'data-text'); - var cur_color = dark && dark_color ? dark_color : color; - dark_colors[color] = dark_color; - $('.widget-color-circle', this).css('backgroundColor', '#' + bg_color).toggleClass('light', isColorLight(cur_color)).toggleClass('bordered', isColorLight(cur_color, 0.95)); - if (text) { - $('.widget-color-label', this).text(text); - } - }); - var color = form.color.value; - var dark_color = ''; - var customcolor = form.customcolor.value; - if (color == 'default') { - color = ''; - dark_color = ''; - } else if (color == 'custom') { - color = fixColor(customcolor); - if (color != customcolor) { - form.customcolor.value = color; - $('.widget-color-circle-custom').css('color', color ? '#' + color : '').toggleClass('light', isColorLight(color)).toggleClass('bordered', isColorLight(color, 0.95)); - } - dark_color = color; - } else { - dark_color = dark_colors[color] || color; - } - if (!color) { - color = ''; - dark_color = ''; - $('.widget-accent-color-item .radio[value="default"]').prop('checked', true); - var custom_default = form.customcolor.defaultValue; - form.customcolor.value = custom_default; - $('.widget-color-circle-custom').css('color', custom_default ? '#' + custom_default : '').toggleClass('light', isColorLight(custom_default)).toggleClass('bordered', isColorLight(custom_default, 0.95)); - } - var colorful = form.colorful.checked; - var code = ''; - $('#embed_code').val(code); - $('#embed_code').height(0); - $('#embed_code').height($('#embed_code').get(0).scrollHeight); - if (DiscussionWidget.lastCode != code) { - DiscussionWidget.lastCode = code; - $('#widget_container').toggleClass('dark', !!dark); - if (toggle_dark) { - var frame = $('#widget_container iframe').get(0); - Telegram.setWidgetOptions({dark: dark}, frame); - } else { - $('#widget_container').html(code); - } - } - } -}; diff --git a/data/core.telegram.org/js/jquery-ui.min.js b/data/core.telegram.org/js/jquery-ui.min.js deleted file mode 100644 index a47c061a05..0000000000 --- a/data/core.telegram.org/js/jquery-ui.min.js +++ /dev/null @@ -1,9 +0,0 @@ -/*! jQuery UI - v1.11.4 - 2017-08-30 -* http://jqueryui.com -* Includes: core.js, widget.js, mouse.js, draggable.js, resizable.js, sortable.js, slider.js, effect.js, effect-slide.js -* Copyright jQuery Foundation and other contributors; Licensed MIT */ - -(function(t){"function"==typeof define&&define.amd?define(["jquery"],t):t(jQuery)})(function(t){function e(e,s){var n,o,a,r=e.nodeName.toLowerCase();return"area"===r?(n=e.parentNode,o=n.name,e.href&&o&&"map"===n.nodeName.toLowerCase()?(a=t("img[usemap='#"+o+"']")[0],!!a&&i(a)):!1):(/^(input|select|textarea|button|object)$/.test(r)?!e.disabled:"a"===r?e.href||s:s)&&i(e)}function i(e){return t.expr.filters.visible(e)&&!t(e).parents().addBack().filter(function(){return"hidden"===t.css(this,"visibility")}).length}t.ui=t.ui||{},t.extend(t.ui,{version:"1.11.4",keyCode:{BACKSPACE:8,COMMA:188,DELETE:46,DOWN:40,END:35,ENTER:13,ESCAPE:27,HOME:36,LEFT:37,PAGE_DOWN:34,PAGE_UP:33,PERIOD:190,RIGHT:39,SPACE:32,TAB:9,UP:38}}),t.fn.extend({scrollParent:function(e){var i=this.css("position"),s="absolute"===i,n=e?/(auto|scroll|hidden)/:/(auto|scroll)/,o=this.parents().filter(function(){var e=t(this);return s&&"static"===e.css("position")?!1:n.test(e.css("overflow")+e.css("overflow-y")+e.css("overflow-x"))}).eq(0);return"fixed"!==i&&o.length?o:t(this[0].ownerDocument||document)},uniqueId:function(){var t=0;return function(){return this.each(function(){this.id||(this.id="ui-id-"+ ++t)})}}(),removeUniqueId:function(){return this.each(function(){/^ui-id-\d+$/.test(this.id)&&t(this).removeAttr("id")})}}),t.extend(t.expr[":"],{data:t.expr.createPseudo?t.expr.createPseudo(function(e){return function(i){return!!t.data(i,e)}}):function(e,i,s){return!!t.data(e,s[3])},focusable:function(i){return e(i,!isNaN(t.attr(i,"tabindex")))},tabbable:function(i){var s=t.attr(i,"tabindex"),n=isNaN(s);return(n||s>=0)&&e(i,!n)}}),t("").outerWidth(1).jquery||t.each(["Width","Height"],function(e,i){function s(e,i,s,o){return t.each(n,function(){i-=parseFloat(t.css(e,"padding"+this))||0,s&&(i-=parseFloat(t.css(e,"border"+this+"Width"))||0),o&&(i-=parseFloat(t.css(e,"margin"+this))||0)}),i}var n="Width"===i?["Left","Right"]:["Top","Bottom"],o=i.toLowerCase(),a={innerWidth:t.fn.innerWidth,innerHeight:t.fn.innerHeight,outerWidth:t.fn.outerWidth,outerHeight:t.fn.outerHeight};t.fn["inner"+i]=function(e){return void 0===e?a["inner"+i].call(this):this.each(function(){t(this).css(o,s(this,e)+"px")})},t.fn["outer"+i]=function(e,n){return"number"!=typeof e?a["outer"+i].call(this,e):this.each(function(){t(this).css(o,s(this,e,!0,n)+"px")})}}),t.fn.addBack||(t.fn.addBack=function(t){return this.add(null==t?this.prevObject:this.prevObject.filter(t))}),t("").data("a-b","a").removeData("a-b").data("a-b")&&(t.fn.removeData=function(e){return function(i){return arguments.length?e.call(this,t.camelCase(i)):e.call(this)}}(t.fn.removeData)),t.ui.ie=!!/msie [\w.]+/.exec(navigator.userAgent.toLowerCase()),t.fn.extend({focus:function(e){return function(i,s){return"number"==typeof i?this.each(function(){var e=this;setTimeout(function(){t(e).focus(),s&&s.call(e)},i)}):e.apply(this,arguments)}}(t.fn.focus),disableSelection:function(){var t="onselectstart"in document.createElement("div")?"selectstart":"mousedown";return function(){return this.bind(t+".ui-disableSelection",function(t){t.preventDefault()})}}(),enableSelection:function(){return this.unbind(".ui-disableSelection")},zIndex:function(e){if(void 0!==e)return this.css("zIndex",e);if(this.length)for(var i,s,n=t(this[0]);n.length&&n[0]!==document;){if(i=n.css("position"),("absolute"===i||"relative"===i||"fixed"===i)&&(s=parseInt(n.css("zIndex"),10),!isNaN(s)&&0!==s))return s;n=n.parent()}return 0}}),t.ui.plugin={add:function(e,i,s){var n,o=t.ui[e].prototype;for(n in s)o.plugins[n]=o.plugins[n]||[],o.plugins[n].push([i,s[n]])},call:function(t,e,i,s){var n,o=t.plugins[e];if(o&&(s||t.element[0].parentNode&&11!==t.element[0].parentNode.nodeType))for(n=0;o.length>n;n++)t.options[o[n][0]]&&o[n][1].apply(t.element,i)}};var s=0,n=Array.prototype.slice;t.cleanData=function(e){return function(i){var s,n,o;for(o=0;null!=(n=i[o]);o++)try{s=t._data(n,"events"),s&&s.remove&&t(n).triggerHandler("remove")}catch(a){}e(i)}}(t.cleanData),t.widget=function(e,i,s){var n,o,a,r,l={},h=e.split(".")[0];return e=e.split(".")[1],n=h+"-"+e,s||(s=i,i=t.Widget),t.expr[":"][n.toLowerCase()]=function(e){return!!t.data(e,n)},t[h]=t[h]||{},o=t[h][e],a=t[h][e]=function(t,e){return this._createWidget?(arguments.length&&this._createWidget(t,e),void 0):new a(t,e)},t.extend(a,o,{version:s.version,_proto:t.extend({},s),_childConstructors:[]}),r=new i,r.options=t.widget.extend({},r.options),t.each(s,function(e,s){return t.isFunction(s)?(l[e]=function(){var t=function(){return i.prototype[e].apply(this,arguments)},n=function(t){return i.prototype[e].apply(this,t)};return function(){var e,i=this._super,o=this._superApply;return this._super=t,this._superApply=n,e=s.apply(this,arguments),this._super=i,this._superApply=o,e}}(),void 0):(l[e]=s,void 0)}),a.prototype=t.widget.extend(r,{widgetEventPrefix:o?r.widgetEventPrefix||e:e},l,{constructor:a,namespace:h,widgetName:e,widgetFullName:n}),o?(t.each(o._childConstructors,function(e,i){var s=i.prototype;t.widget(s.namespace+"."+s.widgetName,a,i._proto)}),delete o._childConstructors):i._childConstructors.push(a),t.widget.bridge(e,a),a},t.widget.extend=function(e){for(var i,s,o=n.call(arguments,1),a=0,r=o.length;r>a;a++)for(i in o[a])s=o[a][i],o[a].hasOwnProperty(i)&&void 0!==s&&(e[i]=t.isPlainObject(s)?t.isPlainObject(e[i])?t.widget.extend({},e[i],s):t.widget.extend({},s):s);return e},t.widget.bridge=function(e,i){var s=i.prototype.widgetFullName||e;t.fn[e]=function(o){var a="string"==typeof o,r=n.call(arguments,1),l=this;return a?this.each(function(){var i,n=t.data(this,s);return"instance"===o?(l=n,!1):n?t.isFunction(n[o])&&"_"!==o.charAt(0)?(i=n[o].apply(n,r),i!==n&&void 0!==i?(l=i&&i.jquery?l.pushStack(i.get()):i,!1):void 0):t.error("no such method '"+o+"' for "+e+" widget instance"):t.error("cannot call methods on "+e+" prior to initialization; "+"attempted to call method '"+o+"'")}):(r.length&&(o=t.widget.extend.apply(null,[o].concat(r))),this.each(function(){var e=t.data(this,s);e?(e.option(o||{}),e._init&&e._init()):t.data(this,s,new i(o,this))})),l}},t.Widget=function(){},t.Widget._childConstructors=[],t.Widget.prototype={widgetName:"widget",widgetEventPrefix:"",defaultElement:"
",options:{disabled:!1,create:null},_createWidget:function(e,i){i=t(i||this.defaultElement||this)[0],this.element=t(i),this.uuid=s++,this.eventNamespace="."+this.widgetName+this.uuid,this.bindings=t(),this.hoverable=t(),this.focusable=t(),i!==this&&(t.data(i,this.widgetFullName,this),this._on(!0,this.element,{remove:function(t){t.target===i&&this.destroy()}}),this.document=t(i.style?i.ownerDocument:i.document||i),this.window=t(this.document[0].defaultView||this.document[0].parentWindow)),this.options=t.widget.extend({},this.options,this._getCreateOptions(),e),this._create(),this._trigger("create",null,this._getCreateEventData()),this._init()},_getCreateOptions:t.noop,_getCreateEventData:t.noop,_create:t.noop,_init:t.noop,destroy:function(){this._destroy(),this.element.unbind(this.eventNamespace).removeData(this.widgetFullName).removeData(t.camelCase(this.widgetFullName)),this.widget().unbind(this.eventNamespace).removeAttr("aria-disabled").removeClass(this.widgetFullName+"-disabled "+"ui-state-disabled"),this.bindings.unbind(this.eventNamespace),this.hoverable.removeClass("ui-state-hover"),this.focusable.removeClass("ui-state-focus")},_destroy:t.noop,widget:function(){return this.element},option:function(e,i){var s,n,o,a=e;if(0===arguments.length)return t.widget.extend({},this.options);if("string"==typeof e)if(a={},s=e.split("."),e=s.shift(),s.length){for(n=a[e]=t.widget.extend({},this.options[e]),o=0;s.length-1>o;o++)n[s[o]]=n[s[o]]||{},n=n[s[o]];if(e=s.pop(),1===arguments.length)return void 0===n[e]?null:n[e];n[e]=i}else{if(1===arguments.length)return void 0===this.options[e]?null:this.options[e];a[e]=i}return this._setOptions(a),this},_setOptions:function(t){var e;for(e in t)this._setOption(e,t[e]);return this},_setOption:function(t,e){return this.options[t]=e,"disabled"===t&&(this.widget().toggleClass(this.widgetFullName+"-disabled",!!e),e&&(this.hoverable.removeClass("ui-state-hover"),this.focusable.removeClass("ui-state-focus"))),this},enable:function(){return this._setOptions({disabled:!1})},disable:function(){return this._setOptions({disabled:!0})},_on:function(e,i,s){var n,o=this;"boolean"!=typeof e&&(s=i,i=e,e=!1),s?(i=n=t(i),this.bindings=this.bindings.add(i)):(s=i,i=this.element,n=this.widget()),t.each(s,function(s,a){function r(){return e||o.options.disabled!==!0&&!t(this).hasClass("ui-state-disabled")?("string"==typeof a?o[a]:a).apply(o,arguments):void 0}"string"!=typeof a&&(r.guid=a.guid=a.guid||r.guid||t.guid++);var l=s.match(/^([\w:-]*)\s*(.*)$/),h=l[1]+o.eventNamespace,c=l[2];c?n.delegate(c,h,r):i.bind(h,r)})},_off:function(e,i){i=(i||"").split(" ").join(this.eventNamespace+" ")+this.eventNamespace,e.unbind(i).undelegate(i),this.bindings=t(this.bindings.not(e).get()),this.focusable=t(this.focusable.not(e).get()),this.hoverable=t(this.hoverable.not(e).get())},_delay:function(t,e){function i(){return("string"==typeof t?s[t]:t).apply(s,arguments)}var s=this;return setTimeout(i,e||0)},_hoverable:function(e){this.hoverable=this.hoverable.add(e),this._on(e,{mouseenter:function(e){t(e.currentTarget).addClass("ui-state-hover")},mouseleave:function(e){t(e.currentTarget).removeClass("ui-state-hover")}})},_focusable:function(e){this.focusable=this.focusable.add(e),this._on(e,{focusin:function(e){t(e.currentTarget).addClass("ui-state-focus")},focusout:function(e){t(e.currentTarget).removeClass("ui-state-focus")}})},_trigger:function(e,i,s){var n,o,a=this.options[e];if(s=s||{},i=t.Event(i),i.type=(e===this.widgetEventPrefix?e:this.widgetEventPrefix+e).toLowerCase(),i.target=this.element[0],o=i.originalEvent)for(n in o)n in i||(i[n]=o[n]);return this.element.trigger(i,s),!(t.isFunction(a)&&a.apply(this.element[0],[i].concat(s))===!1||i.isDefaultPrevented())}},t.each({show:"fadeIn",hide:"fadeOut"},function(e,i){t.Widget.prototype["_"+e]=function(s,n,o){"string"==typeof n&&(n={effect:n});var a,r=n?n===!0||"number"==typeof n?i:n.effect||i:e;n=n||{},"number"==typeof n&&(n={duration:n}),a=!t.isEmptyObject(n),n.complete=o,n.delay&&s.delay(n.delay),a&&t.effects&&t.effects.effect[r]?s[e](n):r!==e&&s[r]?s[r](n.duration,n.easing,o):s.queue(function(i){t(this)[e](),o&&o.call(s[0]),i()})}}),t.widget;var o=!1;t(document).mouseup(function(){o=!1}),t.widget("ui.mouse",{version:"1.11.4",options:{cancel:"input,textarea,button,select,option",distance:1,delay:0},_mouseInit:function(){var e=this;this.element.bind("mousedown."+this.widgetName,function(t){return e._mouseDown(t)}).bind("click."+this.widgetName,function(i){return!0===t.data(i.target,e.widgetName+".preventClickEvent")?(t.removeData(i.target,e.widgetName+".preventClickEvent"),i.stopImmediatePropagation(),!1):void 0}),this.started=!1},_mouseDestroy:function(){this.element.unbind("."+this.widgetName),this._mouseMoveDelegate&&this.document.unbind("mousemove."+this.widgetName,this._mouseMoveDelegate).unbind("mouseup."+this.widgetName,this._mouseUpDelegate)},_mouseDown:function(e){if(!o){this._mouseMoved=!1,this._mouseStarted&&this._mouseUp(e),this._mouseDownEvent=e;var i=this,s=1===e.which,n="string"==typeof this.options.cancel&&e.target.nodeName?t(e.target).closest(this.options.cancel).length:!1;return s&&!n&&this._mouseCapture(e)?(this.mouseDelayMet=!this.options.delay,this.mouseDelayMet||(this._mouseDelayTimer=setTimeout(function(){i.mouseDelayMet=!0},this.options.delay)),this._mouseDistanceMet(e)&&this._mouseDelayMet(e)&&(this._mouseStarted=this._mouseStart(e)!==!1,!this._mouseStarted)?(e.preventDefault(),!0):(!0===t.data(e.target,this.widgetName+".preventClickEvent")&&t.removeData(e.target,this.widgetName+".preventClickEvent"),this._mouseMoveDelegate=function(t){return i._mouseMove(t)},this._mouseUpDelegate=function(t){return i._mouseUp(t)},this.document.bind("mousemove."+this.widgetName,this._mouseMoveDelegate).bind("mouseup."+this.widgetName,this._mouseUpDelegate),e.preventDefault(),o=!0,!0)):!0}},_mouseMove:function(e){if(this._mouseMoved){if(t.ui.ie&&(!document.documentMode||9>document.documentMode)&&!e.button)return this._mouseUp(e);if(!e.which)return this._mouseUp(e)}return(e.which||e.button)&&(this._mouseMoved=!0),this._mouseStarted?(this._mouseDrag(e),e.preventDefault()):(this._mouseDistanceMet(e)&&this._mouseDelayMet(e)&&(this._mouseStarted=this._mouseStart(this._mouseDownEvent,e)!==!1,this._mouseStarted?this._mouseDrag(e):this._mouseUp(e)),!this._mouseStarted)},_mouseUp:function(e){return this.document.unbind("mousemove."+this.widgetName,this._mouseMoveDelegate).unbind("mouseup."+this.widgetName,this._mouseUpDelegate),this._mouseStarted&&(this._mouseStarted=!1,e.target===this._mouseDownEvent.target&&t.data(e.target,this.widgetName+".preventClickEvent",!0),this._mouseStop(e)),o=!1,!1},_mouseDistanceMet:function(t){return Math.max(Math.abs(this._mouseDownEvent.pageX-t.pageX),Math.abs(this._mouseDownEvent.pageY-t.pageY))>=this.options.distance},_mouseDelayMet:function(){return this.mouseDelayMet},_mouseStart:function(){},_mouseDrag:function(){},_mouseStop:function(){},_mouseCapture:function(){return!0}}),t.widget("ui.draggable",t.ui.mouse,{version:"1.11.4",widgetEventPrefix:"drag",options:{addClasses:!0,appendTo:"parent",axis:!1,connectToSortable:!1,containment:!1,cursor:"auto",cursorAt:!1,grid:!1,handle:!1,helper:"original",iframeFix:!1,opacity:!1,refreshPositions:!1,revert:!1,revertDuration:500,scope:"default",scroll:!0,scrollSensitivity:20,scrollSpeed:20,snap:!1,snapMode:"both",snapTolerance:20,stack:!1,zIndex:!1,drag:null,start:null,stop:null},_create:function(){"original"===this.options.helper&&this._setPositionRelative(),this.options.addClasses&&this.element.addClass("ui-draggable"),this.options.disabled&&this.element.addClass("ui-draggable-disabled"),this._setHandleClassName(),this._mouseInit()},_setOption:function(t,e){this._super(t,e),"handle"===t&&(this._removeHandleClassName(),this._setHandleClassName())},_destroy:function(){return(this.helper||this.element).is(".ui-draggable-dragging")?(this.destroyOnClear=!0,void 0):(this.element.removeClass("ui-draggable ui-draggable-dragging ui-draggable-disabled"),this._removeHandleClassName(),this._mouseDestroy(),void 0)},_mouseCapture:function(e){var i=this.options;return this._blurActiveElement(e),this.helper||i.disabled||t(e.target).closest(".ui-resizable-handle").length>0?!1:(this.handle=this._getHandle(e),this.handle?(this._blockFrames(i.iframeFix===!0?"iframe":i.iframeFix),!0):!1)},_blockFrames:function(e){this.iframeBlocks=this.document.find(e).map(function(){var e=t(this);return t("
").css("position","absolute").appendTo(e.parent()).outerWidth(e.outerWidth()).outerHeight(e.outerHeight()).offset(e.offset())[0]})},_unblockFrames:function(){this.iframeBlocks&&(this.iframeBlocks.remove(),delete this.iframeBlocks)},_blurActiveElement:function(e){var i=this.document[0];if(this.handleElement.is(e.target))try{i.activeElement&&"body"!==i.activeElement.nodeName.toLowerCase()&&t(i.activeElement).blur()}catch(s){}},_mouseStart:function(e){var i=this.options;return this.helper=this._createHelper(e),this.helper.addClass("ui-draggable-dragging"),this._cacheHelperProportions(),t.ui.ddmanager&&(t.ui.ddmanager.current=this),this._cacheMargins(),this.cssPosition=this.helper.css("position"),this.scrollParent=this.helper.scrollParent(!0),this.offsetParent=this.helper.offsetParent(),this.hasFixedAncestor=this.helper.parents().filter(function(){return"fixed"===t(this).css("position")}).length>0,this.positionAbs=this.element.offset(),this._refreshOffsets(e),this.originalPosition=this.position=this._generatePosition(e,!1),this.originalPageX=e.pageX,this.originalPageY=e.pageY,i.cursorAt&&this._adjustOffsetFromHelper(i.cursorAt),this._setContainment(),this._trigger("start",e)===!1?(this._clear(),!1):(this._cacheHelperProportions(),t.ui.ddmanager&&!i.dropBehaviour&&t.ui.ddmanager.prepareOffsets(this,e),this._normalizeRightBottom(),this._mouseDrag(e,!0),t.ui.ddmanager&&t.ui.ddmanager.dragStart(this,e),!0)},_refreshOffsets:function(t){this.offset={top:this.positionAbs.top-this.margins.top,left:this.positionAbs.left-this.margins.left,scroll:!1,parent:this._getParentOffset(),relative:this._getRelativeOffset()},this.offset.click={left:t.pageX-this.offset.left,top:t.pageY-this.offset.top}},_mouseDrag:function(e,i){if(this.hasFixedAncestor&&(this.offset.parent=this._getParentOffset()),this.position=this._generatePosition(e,!0),this.positionAbs=this._convertPositionTo("absolute"),!i){var s=this._uiHash();if(this._trigger("drag",e,s)===!1)return this._mouseUp({}),!1;this.position=s.position}return this.helper[0].style.left=this.position.left+"px",this.helper[0].style.top=this.position.top+"px",t.ui.ddmanager&&t.ui.ddmanager.drag(this,e),!1},_mouseStop:function(e){var i=this,s=!1;return t.ui.ddmanager&&!this.options.dropBehaviour&&(s=t.ui.ddmanager.drop(this,e)),this.dropped&&(s=this.dropped,this.dropped=!1),"invalid"===this.options.revert&&!s||"valid"===this.options.revert&&s||this.options.revert===!0||t.isFunction(this.options.revert)&&this.options.revert.call(this.element,s)?t(this.helper).animate(this.originalPosition,parseInt(this.options.revertDuration,10),function(){i._trigger("stop",e)!==!1&&i._clear()}):this._trigger("stop",e)!==!1&&this._clear(),!1},_mouseUp:function(e){return this._unblockFrames(),t.ui.ddmanager&&t.ui.ddmanager.dragStop(this,e),this.handleElement.is(e.target)&&this.element.focus(),t.ui.mouse.prototype._mouseUp.call(this,e)},cancel:function(){return this.helper.is(".ui-draggable-dragging")?this._mouseUp({}):this._clear(),this},_getHandle:function(e){return this.options.handle?!!t(e.target).closest(this.element.find(this.options.handle)).length:!0},_setHandleClassName:function(){this.handleElement=this.options.handle?this.element.find(this.options.handle):this.element,this.handleElement.addClass("ui-draggable-handle")},_removeHandleClassName:function(){this.handleElement.removeClass("ui-draggable-handle")},_createHelper:function(e){var i=this.options,s=t.isFunction(i.helper),n=s?t(i.helper.apply(this.element[0],[e])):"clone"===i.helper?this.element.clone().removeAttr("id"):this.element;return n.parents("body").length||n.appendTo("parent"===i.appendTo?this.element[0].parentNode:i.appendTo),s&&n[0]===this.element[0]&&this._setPositionRelative(),n[0]===this.element[0]||/(fixed|absolute)/.test(n.css("position"))||n.css("position","absolute"),n},_setPositionRelative:function(){/^(?:r|a|f)/.test(this.element.css("position"))||(this.element[0].style.position="relative")},_adjustOffsetFromHelper:function(e){"string"==typeof e&&(e=e.split(" ")),t.isArray(e)&&(e={left:+e[0],top:+e[1]||0}),"left"in e&&(this.offset.click.left=e.left+this.margins.left),"right"in e&&(this.offset.click.left=this.helperProportions.width-e.right+this.margins.left),"top"in e&&(this.offset.click.top=e.top+this.margins.top),"bottom"in e&&(this.offset.click.top=this.helperProportions.height-e.bottom+this.margins.top)},_isRootNode:function(t){return/(html|body)/i.test(t.tagName)||t===this.document[0]},_getParentOffset:function(){var e=this.offsetParent.offset(),i=this.document[0];return"absolute"===this.cssPosition&&this.scrollParent[0]!==i&&t.contains(this.scrollParent[0],this.offsetParent[0])&&(e.left+=this.scrollParent.scrollLeft(),e.top+=this.scrollParent.scrollTop()),this._isRootNode(this.offsetParent[0])&&(e={top:0,left:0}),{top:e.top+(parseInt(this.offsetParent.css("borderTopWidth"),10)||0),left:e.left+(parseInt(this.offsetParent.css("borderLeftWidth"),10)||0)}},_getRelativeOffset:function(){if("relative"!==this.cssPosition)return{top:0,left:0};var t=this.element.position(),e=this._isRootNode(this.scrollParent[0]);return{top:t.top-(parseInt(this.helper.css("top"),10)||0)+(e?0:this.scrollParent.scrollTop()),left:t.left-(parseInt(this.helper.css("left"),10)||0)+(e?0:this.scrollParent.scrollLeft())}},_cacheMargins:function(){this.margins={left:parseInt(this.element.css("marginLeft"),10)||0,top:parseInt(this.element.css("marginTop"),10)||0,right:parseInt(this.element.css("marginRight"),10)||0,bottom:parseInt(this.element.css("marginBottom"),10)||0}},_cacheHelperProportions:function(){this.helperProportions={width:this.helper.outerWidth(),height:this.helper.outerHeight()}},_setContainment:function(){var e,i,s,n=this.options,o=this.document[0];return this.relativeContainer=null,n.containment?"window"===n.containment?(this.containment=[t(window).scrollLeft()-this.offset.relative.left-this.offset.parent.left,t(window).scrollTop()-this.offset.relative.top-this.offset.parent.top,t(window).scrollLeft()+t(window).width()-this.helperProportions.width-this.margins.left,t(window).scrollTop()+(t(window).height()||o.body.parentNode.scrollHeight)-this.helperProportions.height-this.margins.top],void 0):"document"===n.containment?(this.containment=[0,0,t(o).width()-this.helperProportions.width-this.margins.left,(t(o).height()||o.body.parentNode.scrollHeight)-this.helperProportions.height-this.margins.top],void 0):n.containment.constructor===Array?(this.containment=n.containment,void 0):("parent"===n.containment&&(n.containment=this.helper[0].parentNode),i=t(n.containment),s=i[0],s&&(e=/(scroll|auto)/.test(i.css("overflow")),this.containment=[(parseInt(i.css("borderLeftWidth"),10)||0)+(parseInt(i.css("paddingLeft"),10)||0),(parseInt(i.css("borderTopWidth"),10)||0)+(parseInt(i.css("paddingTop"),10)||0),(e?Math.max(s.scrollWidth,s.offsetWidth):s.offsetWidth)-(parseInt(i.css("borderRightWidth"),10)||0)-(parseInt(i.css("paddingRight"),10)||0)-this.helperProportions.width-this.margins.left-this.margins.right,(e?Math.max(s.scrollHeight,s.offsetHeight):s.offsetHeight)-(parseInt(i.css("borderBottomWidth"),10)||0)-(parseInt(i.css("paddingBottom"),10)||0)-this.helperProportions.height-this.margins.top-this.margins.bottom],this.relativeContainer=i),void 0):(this.containment=null,void 0)},_convertPositionTo:function(t,e){e||(e=this.position);var i="absolute"===t?1:-1,s=this._isRootNode(this.scrollParent[0]);return{top:e.top+this.offset.relative.top*i+this.offset.parent.top*i-("fixed"===this.cssPosition?-this.offset.scroll.top:s?0:this.offset.scroll.top)*i,left:e.left+this.offset.relative.left*i+this.offset.parent.left*i-("fixed"===this.cssPosition?-this.offset.scroll.left:s?0:this.offset.scroll.left)*i}},_generatePosition:function(t,e){var i,s,n,o,a=this.options,r=this._isRootNode(this.scrollParent[0]),l=t.pageX,h=t.pageY;return r&&this.offset.scroll||(this.offset.scroll={top:this.scrollParent.scrollTop(),left:this.scrollParent.scrollLeft()}),e&&(this.containment&&(this.relativeContainer?(s=this.relativeContainer.offset(),i=[this.containment[0]+s.left,this.containment[1]+s.top,this.containment[2]+s.left,this.containment[3]+s.top]):i=this.containment,t.pageX-this.offset.click.lefti[2]&&(l=i[2]+this.offset.click.left),t.pageY-this.offset.click.top>i[3]&&(h=i[3]+this.offset.click.top)),a.grid&&(n=a.grid[1]?this.originalPageY+Math.round((h-this.originalPageY)/a.grid[1])*a.grid[1]:this.originalPageY,h=i?n-this.offset.click.top>=i[1]||n-this.offset.click.top>i[3]?n:n-this.offset.click.top>=i[1]?n-a.grid[1]:n+a.grid[1]:n,o=a.grid[0]?this.originalPageX+Math.round((l-this.originalPageX)/a.grid[0])*a.grid[0]:this.originalPageX,l=i?o-this.offset.click.left>=i[0]||o-this.offset.click.left>i[2]?o:o-this.offset.click.left>=i[0]?o-a.grid[0]:o+a.grid[0]:o),"y"===a.axis&&(l=this.originalPageX),"x"===a.axis&&(h=this.originalPageY)),{top:h-this.offset.click.top-this.offset.relative.top-this.offset.parent.top+("fixed"===this.cssPosition?-this.offset.scroll.top:r?0:this.offset.scroll.top),left:l-this.offset.click.left-this.offset.relative.left-this.offset.parent.left+("fixed"===this.cssPosition?-this.offset.scroll.left:r?0:this.offset.scroll.left)}},_clear:function(){this.helper.removeClass("ui-draggable-dragging"),this.helper[0]===this.element[0]||this.cancelHelperRemoval||this.helper.remove(),this.helper=null,this.cancelHelperRemoval=!1,this.destroyOnClear&&this.destroy()},_normalizeRightBottom:function(){"y"!==this.options.axis&&"auto"!==this.helper.css("right")&&(this.helper.width(this.helper.width()),this.helper.css("right","auto")),"x"!==this.options.axis&&"auto"!==this.helper.css("bottom")&&(this.helper.height(this.helper.height()),this.helper.css("bottom","auto"))},_trigger:function(e,i,s){return s=s||this._uiHash(),t.ui.plugin.call(this,e,[i,s,this],!0),/^(drag|start|stop)/.test(e)&&(this.positionAbs=this._convertPositionTo("absolute"),s.offset=this.positionAbs),t.Widget.prototype._trigger.call(this,e,i,s)},plugins:{},_uiHash:function(){return{helper:this.helper,position:this.position,originalPosition:this.originalPosition,offset:this.positionAbs}}}),t.ui.plugin.add("draggable","connectToSortable",{start:function(e,i,s){var n=t.extend({},i,{item:s.element});s.sortables=[],t(s.options.connectToSortable).each(function(){var i=t(this).sortable("instance");i&&!i.options.disabled&&(s.sortables.push(i),i.refreshPositions(),i._trigger("activate",e,n))})},stop:function(e,i,s){var n=t.extend({},i,{item:s.element});s.cancelHelperRemoval=!1,t.each(s.sortables,function(){var t=this;t.isOver?(t.isOver=0,s.cancelHelperRemoval=!0,t.cancelHelperRemoval=!1,t._storedCSS={position:t.placeholder.css("position"),top:t.placeholder.css("top"),left:t.placeholder.css("left")},t._mouseStop(e),t.options.helper=t.options._helper):(t.cancelHelperRemoval=!0,t._trigger("deactivate",e,n))})},drag:function(e,i,s){t.each(s.sortables,function(){var n=!1,o=this;o.positionAbs=s.positionAbs,o.helperProportions=s.helperProportions,o.offset.click=s.offset.click,o._intersectsWith(o.containerCache)&&(n=!0,t.each(s.sortables,function(){return this.positionAbs=s.positionAbs,this.helperProportions=s.helperProportions,this.offset.click=s.offset.click,this!==o&&this._intersectsWith(this.containerCache)&&t.contains(o.element[0],this.element[0])&&(n=!1),n})),n?(o.isOver||(o.isOver=1,s._parent=i.helper.parent(),o.currentItem=i.helper.appendTo(o.element).data("ui-sortable-item",!0),o.options._helper=o.options.helper,o.options.helper=function(){return i.helper[0]},e.target=o.currentItem[0],o._mouseCapture(e,!0),o._mouseStart(e,!0,!0),o.offset.click.top=s.offset.click.top,o.offset.click.left=s.offset.click.left,o.offset.parent.left-=s.offset.parent.left-o.offset.parent.left,o.offset.parent.top-=s.offset.parent.top-o.offset.parent.top,s._trigger("toSortable",e),s.dropped=o.element,t.each(s.sortables,function(){this.refreshPositions()}),s.currentItem=s.element,o.fromOutside=s),o.currentItem&&(o._mouseDrag(e),i.position=o.position)):o.isOver&&(o.isOver=0,o.cancelHelperRemoval=!0,o.options._revert=o.options.revert,o.options.revert=!1,o._trigger("out",e,o._uiHash(o)),o._mouseStop(e,!0),o.options.revert=o.options._revert,o.options.helper=o.options._helper,o.placeholder&&o.placeholder.remove(),i.helper.appendTo(s._parent),s._refreshOffsets(e),i.position=s._generatePosition(e,!0),s._trigger("fromSortable",e),s.dropped=!1,t.each(s.sortables,function(){this.refreshPositions()}))})}}),t.ui.plugin.add("draggable","cursor",{start:function(e,i,s){var n=t("body"),o=s.options;n.css("cursor")&&(o._cursor=n.css("cursor")),n.css("cursor",o.cursor)},stop:function(e,i,s){var n=s.options;n._cursor&&t("body").css("cursor",n._cursor)}}),t.ui.plugin.add("draggable","opacity",{start:function(e,i,s){var n=t(i.helper),o=s.options;n.css("opacity")&&(o._opacity=n.css("opacity")),n.css("opacity",o.opacity)},stop:function(e,i,s){var n=s.options;n._opacity&&t(i.helper).css("opacity",n._opacity)}}),t.ui.plugin.add("draggable","scroll",{start:function(t,e,i){i.scrollParentNotHidden||(i.scrollParentNotHidden=i.helper.scrollParent(!1)),i.scrollParentNotHidden[0]!==i.document[0]&&"HTML"!==i.scrollParentNotHidden[0].tagName&&(i.overflowOffset=i.scrollParentNotHidden.offset())},drag:function(e,i,s){var n=s.options,o=!1,a=s.scrollParentNotHidden[0],r=s.document[0];a!==r&&"HTML"!==a.tagName?(n.axis&&"x"===n.axis||(s.overflowOffset.top+a.offsetHeight-e.pageY=0;d--)l=s.snapElements[d].left-s.margins.left,h=l+s.snapElements[d].width,c=s.snapElements[d].top-s.margins.top,u=c+s.snapElements[d].height,l-g>_||m>h+g||c-g>b||v>u+g||!t.contains(s.snapElements[d].item.ownerDocument,s.snapElements[d].item)?(s.snapElements[d].snapping&&s.options.snap.release&&s.options.snap.release.call(s.element,e,t.extend(s._uiHash(),{snapItem:s.snapElements[d].item})),s.snapElements[d].snapping=!1):("inner"!==f.snapMode&&(n=g>=Math.abs(c-b),o=g>=Math.abs(u-v),a=g>=Math.abs(l-_),r=g>=Math.abs(h-m),n&&(i.position.top=s._convertPositionTo("relative",{top:c-s.helperProportions.height,left:0}).top),o&&(i.position.top=s._convertPositionTo("relative",{top:u,left:0}).top),a&&(i.position.left=s._convertPositionTo("relative",{top:0,left:l-s.helperProportions.width}).left),r&&(i.position.left=s._convertPositionTo("relative",{top:0,left:h}).left)),p=n||o||a||r,"outer"!==f.snapMode&&(n=g>=Math.abs(c-v),o=g>=Math.abs(u-b),a=g>=Math.abs(l-m),r=g>=Math.abs(h-_),n&&(i.position.top=s._convertPositionTo("relative",{top:c,left:0}).top),o&&(i.position.top=s._convertPositionTo("relative",{top:u-s.helperProportions.height,left:0}).top),a&&(i.position.left=s._convertPositionTo("relative",{top:0,left:l}).left),r&&(i.position.left=s._convertPositionTo("relative",{top:0,left:h-s.helperProportions.width}).left)),!s.snapElements[d].snapping&&(n||o||a||r||p)&&s.options.snap.snap&&s.options.snap.snap.call(s.element,e,t.extend(s._uiHash(),{snapItem:s.snapElements[d].item})),s.snapElements[d].snapping=n||o||a||r||p)}}),t.ui.plugin.add("draggable","stack",{start:function(e,i,s){var n,o=s.options,a=t.makeArray(t(o.stack)).sort(function(e,i){return(parseInt(t(e).css("zIndex"),10)||0)-(parseInt(t(i).css("zIndex"),10)||0)});a.length&&(n=parseInt(t(a[0]).css("zIndex"),10)||0,t(a).each(function(e){t(this).css("zIndex",n+e)}),this.css("zIndex",n+a.length))}}),t.ui.plugin.add("draggable","zIndex",{start:function(e,i,s){var n=t(i.helper),o=s.options;n.css("zIndex")&&(o._zIndex=n.css("zIndex")),n.css("zIndex",o.zIndex)},stop:function(e,i,s){var n=s.options;n._zIndex&&t(i.helper).css("zIndex",n._zIndex)}}),t.ui.draggable,t.widget("ui.resizable",t.ui.mouse,{version:"1.11.4",widgetEventPrefix:"resize",options:{alsoResize:!1,animate:!1,animateDuration:"slow",animateEasing:"swing",aspectRatio:!1,autoHide:!1,containment:!1,ghost:!1,grid:!1,handles:"e,s,se",helper:!1,maxHeight:null,maxWidth:null,minHeight:10,minWidth:10,zIndex:90,resize:null,start:null,stop:null},_num:function(t){return parseInt(t,10)||0 -},_isNumber:function(t){return!isNaN(parseInt(t,10))},_hasScroll:function(e,i){if("hidden"===t(e).css("overflow"))return!1;var s=i&&"left"===i?"scrollLeft":"scrollTop",n=!1;return e[s]>0?!0:(e[s]=1,n=e[s]>0,e[s]=0,n)},_create:function(){var e,i,s,n,o,a=this,r=this.options;if(this.element.addClass("ui-resizable"),t.extend(this,{_aspectRatio:!!r.aspectRatio,aspectRatio:r.aspectRatio,originalElement:this.element,_proportionallyResizeElements:[],_helper:r.helper||r.ghost||r.animate?r.helper||"ui-resizable-helper":null}),this.element[0].nodeName.match(/^(canvas|textarea|input|select|button|img)$/i)&&(this.element.wrap(t("
").css({position:this.element.css("position"),width:this.element.outerWidth(),height:this.element.outerHeight(),top:this.element.css("top"),left:this.element.css("left")})),this.element=this.element.parent().data("ui-resizable",this.element.resizable("instance")),this.elementIsWrapper=!0,this.element.css({marginLeft:this.originalElement.css("marginLeft"),marginTop:this.originalElement.css("marginTop"),marginRight:this.originalElement.css("marginRight"),marginBottom:this.originalElement.css("marginBottom")}),this.originalElement.css({marginLeft:0,marginTop:0,marginRight:0,marginBottom:0}),this.originalResizeStyle=this.originalElement.css("resize"),this.originalElement.css("resize","none"),this._proportionallyResizeElements.push(this.originalElement.css({position:"static",zoom:1,display:"block"})),this.originalElement.css({margin:this.originalElement.css("margin")}),this._proportionallyResize()),this.handles=r.handles||(t(".ui-resizable-handle",this.element).length?{n:".ui-resizable-n",e:".ui-resizable-e",s:".ui-resizable-s",w:".ui-resizable-w",se:".ui-resizable-se",sw:".ui-resizable-sw",ne:".ui-resizable-ne",nw:".ui-resizable-nw"}:"e,s,se"),this._handles=t(),this.handles.constructor===String)for("all"===this.handles&&(this.handles="n,e,s,w,se,sw,ne,nw"),e=this.handles.split(","),this.handles={},i=0;e.length>i;i++)s=t.trim(e[i]),o="ui-resizable-"+s,n=t("
"),n.css({zIndex:r.zIndex}),"se"===s&&n.addClass("ui-icon ui-icon-gripsmall-diagonal-se"),this.handles[s]=".ui-resizable-"+s,this.element.append(n);this._renderAxis=function(e){var i,s,n,o;e=e||this.element;for(i in this.handles)this.handles[i].constructor===String?this.handles[i]=this.element.children(this.handles[i]).first().show():(this.handles[i].jquery||this.handles[i].nodeType)&&(this.handles[i]=t(this.handles[i]),this._on(this.handles[i],{mousedown:a._mouseDown})),this.elementIsWrapper&&this.originalElement[0].nodeName.match(/^(textarea|input|select|button)$/i)&&(s=t(this.handles[i],this.element),o=/sw|ne|nw|se|n|s/.test(i)?s.outerHeight():s.outerWidth(),n=["padding",/ne|nw|n/.test(i)?"Top":/se|sw|s/.test(i)?"Bottom":/^e$/.test(i)?"Right":"Left"].join(""),e.css(n,o),this._proportionallyResize()),this._handles=this._handles.add(this.handles[i])},this._renderAxis(this.element),this._handles=this._handles.add(this.element.find(".ui-resizable-handle")),this._handles.disableSelection(),this._handles.mouseover(function(){a.resizing||(this.className&&(n=this.className.match(/ui-resizable-(se|sw|ne|nw|n|e|s|w)/i)),a.axis=n&&n[1]?n[1]:"se")}),r.autoHide&&(this._handles.hide(),t(this.element).addClass("ui-resizable-autohide").mouseenter(function(){r.disabled||(t(this).removeClass("ui-resizable-autohide"),a._handles.show())}).mouseleave(function(){r.disabled||a.resizing||(t(this).addClass("ui-resizable-autohide"),a._handles.hide())})),this._mouseInit()},_destroy:function(){this._mouseDestroy();var e,i=function(e){t(e).removeClass("ui-resizable ui-resizable-disabled ui-resizable-resizing").removeData("resizable").removeData("ui-resizable").unbind(".resizable").find(".ui-resizable-handle").remove()};return this.elementIsWrapper&&(i(this.element),e=this.element,this.originalElement.css({position:e.css("position"),width:e.outerWidth(),height:e.outerHeight(),top:e.css("top"),left:e.css("left")}).insertAfter(e),e.remove()),this.originalElement.css("resize",this.originalResizeStyle),i(this.originalElement),this},_mouseCapture:function(e){var i,s,n=!1;for(i in this.handles)s=t(this.handles[i])[0],(s===e.target||t.contains(s,e.target))&&(n=!0);return!this.options.disabled&&n},_mouseStart:function(e){var i,s,n,o=this.options,a=this.element;return this.resizing=!0,this._renderProxy(),i=this._num(this.helper.css("left")),s=this._num(this.helper.css("top")),o.containment&&(i+=t(o.containment).scrollLeft()||0,s+=t(o.containment).scrollTop()||0),this.offset=this.helper.offset(),this.position={left:i,top:s},this.size=this._helper?{width:this.helper.width(),height:this.helper.height()}:{width:a.width(),height:a.height()},this.originalSize=this._helper?{width:a.outerWidth(),height:a.outerHeight()}:{width:a.width(),height:a.height()},this.sizeDiff={width:a.outerWidth()-a.width(),height:a.outerHeight()-a.height()},this.originalPosition={left:i,top:s},this.originalMousePosition={left:e.pageX,top:e.pageY},this.aspectRatio="number"==typeof o.aspectRatio?o.aspectRatio:this.originalSize.width/this.originalSize.height||1,n=t(".ui-resizable-"+this.axis).css("cursor"),t("body").css("cursor","auto"===n?this.axis+"-resize":n),a.addClass("ui-resizable-resizing"),this._propagate("start",e),!0},_mouseDrag:function(e){var i,s,n=this.originalMousePosition,o=this.axis,a=e.pageX-n.left||0,r=e.pageY-n.top||0,l=this._change[o];return this._updatePrevProperties(),l?(i=l.apply(this,[e,a,r]),this._updateVirtualBoundaries(e.shiftKey),(this._aspectRatio||e.shiftKey)&&(i=this._updateRatio(i,e)),i=this._respectSize(i,e),this._updateCache(i),this._propagate("resize",e),s=this._applyChanges(),!this._helper&&this._proportionallyResizeElements.length&&this._proportionallyResize(),t.isEmptyObject(s)||(this._updatePrevProperties(),this._trigger("resize",e,this.ui()),this._applyChanges()),!1):!1},_mouseStop:function(e){this.resizing=!1;var i,s,n,o,a,r,l,h=this.options,c=this;return this._helper&&(i=this._proportionallyResizeElements,s=i.length&&/textarea/i.test(i[0].nodeName),n=s&&this._hasScroll(i[0],"left")?0:c.sizeDiff.height,o=s?0:c.sizeDiff.width,a={width:c.helper.width()-o,height:c.helper.height()-n},r=parseInt(c.element.css("left"),10)+(c.position.left-c.originalPosition.left)||null,l=parseInt(c.element.css("top"),10)+(c.position.top-c.originalPosition.top)||null,h.animate||this.element.css(t.extend(a,{top:l,left:r})),c.helper.height(c.size.height),c.helper.width(c.size.width),this._helper&&!h.animate&&this._proportionallyResize()),t("body").css("cursor","auto"),this.element.removeClass("ui-resizable-resizing"),this._propagate("stop",e),this._helper&&this.helper.remove(),!1},_updatePrevProperties:function(){this.prevPosition={top:this.position.top,left:this.position.left},this.prevSize={width:this.size.width,height:this.size.height}},_applyChanges:function(){var t={};return this.position.top!==this.prevPosition.top&&(t.top=this.position.top+"px"),this.position.left!==this.prevPosition.left&&(t.left=this.position.left+"px"),this.size.width!==this.prevSize.width&&(t.width=this.size.width+"px"),this.size.height!==this.prevSize.height&&(t.height=this.size.height+"px"),this.helper.css(t),t},_updateVirtualBoundaries:function(t){var e,i,s,n,o,a=this.options;o={minWidth:this._isNumber(a.minWidth)?a.minWidth:0,maxWidth:this._isNumber(a.maxWidth)?a.maxWidth:1/0,minHeight:this._isNumber(a.minHeight)?a.minHeight:0,maxHeight:this._isNumber(a.maxHeight)?a.maxHeight:1/0},(this._aspectRatio||t)&&(e=o.minHeight*this.aspectRatio,s=o.minWidth/this.aspectRatio,i=o.maxHeight*this.aspectRatio,n=o.maxWidth/this.aspectRatio,e>o.minWidth&&(o.minWidth=e),s>o.minHeight&&(o.minHeight=s),o.maxWidth>i&&(o.maxWidth=i),o.maxHeight>n&&(o.maxHeight=n)),this._vBoundaries=o},_updateCache:function(t){this.offset=this.helper.offset(),this._isNumber(t.left)&&(this.position.left=t.left),this._isNumber(t.top)&&(this.position.top=t.top),this._isNumber(t.height)&&(this.size.height=t.height),this._isNumber(t.width)&&(this.size.width=t.width)},_updateRatio:function(t){var e=this.position,i=this.size,s=this.axis;return this._isNumber(t.height)?t.width=t.height*this.aspectRatio:this._isNumber(t.width)&&(t.height=t.width/this.aspectRatio),"sw"===s&&(t.left=e.left+(i.width-t.width),t.top=null),"nw"===s&&(t.top=e.top+(i.height-t.height),t.left=e.left+(i.width-t.width)),t},_respectSize:function(t){var e=this._vBoundaries,i=this.axis,s=this._isNumber(t.width)&&e.maxWidth&&e.maxWidtht.width,a=this._isNumber(t.height)&&e.minHeight&&e.minHeight>t.height,r=this.originalPosition.left+this.originalSize.width,l=this.position.top+this.size.height,h=/sw|nw|w/.test(i),c=/nw|ne|n/.test(i);return o&&(t.width=e.minWidth),a&&(t.height=e.minHeight),s&&(t.width=e.maxWidth),n&&(t.height=e.maxHeight),o&&h&&(t.left=r-e.minWidth),s&&h&&(t.left=r-e.maxWidth),a&&c&&(t.top=l-e.minHeight),n&&c&&(t.top=l-e.maxHeight),t.width||t.height||t.left||!t.top?t.width||t.height||t.top||!t.left||(t.left=null):t.top=null,t},_getPaddingPlusBorderDimensions:function(t){for(var e=0,i=[],s=[t.css("borderTopWidth"),t.css("borderRightWidth"),t.css("borderBottomWidth"),t.css("borderLeftWidth")],n=[t.css("paddingTop"),t.css("paddingRight"),t.css("paddingBottom"),t.css("paddingLeft")];4>e;e++)i[e]=parseInt(s[e],10)||0,i[e]+=parseInt(n[e],10)||0;return{height:i[0]+i[2],width:i[1]+i[3]}},_proportionallyResize:function(){if(this._proportionallyResizeElements.length)for(var t,e=0,i=this.helper||this.element;this._proportionallyResizeElements.length>e;e++)t=this._proportionallyResizeElements[e],this.outerDimensions||(this.outerDimensions=this._getPaddingPlusBorderDimensions(t)),t.css({height:i.height()-this.outerDimensions.height||0,width:i.width()-this.outerDimensions.width||0})},_renderProxy:function(){var e=this.element,i=this.options;this.elementOffset=e.offset(),this._helper?(this.helper=this.helper||t("
"),this.helper.addClass(this._helper).css({width:this.element.outerWidth()-1,height:this.element.outerHeight()-1,position:"absolute",left:this.elementOffset.left+"px",top:this.elementOffset.top+"px",zIndex:++i.zIndex}),this.helper.appendTo("body").disableSelection()):this.helper=this.element},_change:{e:function(t,e){return{width:this.originalSize.width+e}},w:function(t,e){var i=this.originalSize,s=this.originalPosition;return{left:s.left+e,width:i.width-e}},n:function(t,e,i){var s=this.originalSize,n=this.originalPosition;return{top:n.top+i,height:s.height-i}},s:function(t,e,i){return{height:this.originalSize.height+i}},se:function(e,i,s){return t.extend(this._change.s.apply(this,arguments),this._change.e.apply(this,[e,i,s]))},sw:function(e,i,s){return t.extend(this._change.s.apply(this,arguments),this._change.w.apply(this,[e,i,s]))},ne:function(e,i,s){return t.extend(this._change.n.apply(this,arguments),this._change.e.apply(this,[e,i,s]))},nw:function(e,i,s){return t.extend(this._change.n.apply(this,arguments),this._change.w.apply(this,[e,i,s]))}},_propagate:function(e,i){t.ui.plugin.call(this,e,[i,this.ui()]),"resize"!==e&&this._trigger(e,i,this.ui())},plugins:{},ui:function(){return{originalElement:this.originalElement,element:this.element,helper:this.helper,position:this.position,size:this.size,originalSize:this.originalSize,originalPosition:this.originalPosition}}}),t.ui.plugin.add("resizable","animate",{stop:function(e){var i=t(this).resizable("instance"),s=i.options,n=i._proportionallyResizeElements,o=n.length&&/textarea/i.test(n[0].nodeName),a=o&&i._hasScroll(n[0],"left")?0:i.sizeDiff.height,r=o?0:i.sizeDiff.width,l={width:i.size.width-r,height:i.size.height-a},h=parseInt(i.element.css("left"),10)+(i.position.left-i.originalPosition.left)||null,c=parseInt(i.element.css("top"),10)+(i.position.top-i.originalPosition.top)||null;i.element.animate(t.extend(l,c&&h?{top:c,left:h}:{}),{duration:s.animateDuration,easing:s.animateEasing,step:function(){var s={width:parseInt(i.element.css("width"),10),height:parseInt(i.element.css("height"),10),top:parseInt(i.element.css("top"),10),left:parseInt(i.element.css("left"),10)};n&&n.length&&t(n[0]).css({width:s.width,height:s.height}),i._updateCache(s),i._propagate("resize",e)}})}}),t.ui.plugin.add("resizable","containment",{start:function(){var e,i,s,n,o,a,r,l=t(this).resizable("instance"),h=l.options,c=l.element,u=h.containment,d=u instanceof t?u.get(0):/parent/.test(u)?c.parent().get(0):u;d&&(l.containerElement=t(d),/document/.test(u)||u===document?(l.containerOffset={left:0,top:0},l.containerPosition={left:0,top:0},l.parentData={element:t(document),left:0,top:0,width:t(document).width(),height:t(document).height()||document.body.parentNode.scrollHeight}):(e=t(d),i=[],t(["Top","Right","Left","Bottom"]).each(function(t,s){i[t]=l._num(e.css("padding"+s))}),l.containerOffset=e.offset(),l.containerPosition=e.position(),l.containerSize={height:e.innerHeight()-i[3],width:e.innerWidth()-i[1]},s=l.containerOffset,n=l.containerSize.height,o=l.containerSize.width,a=l._hasScroll(d,"left")?d.scrollWidth:o,r=l._hasScroll(d)?d.scrollHeight:n,l.parentData={element:d,left:s.left,top:s.top,width:a,height:r}))},resize:function(e){var i,s,n,o,a=t(this).resizable("instance"),r=a.options,l=a.containerOffset,h=a.position,c=a._aspectRatio||e.shiftKey,u={top:0,left:0},d=a.containerElement,p=!0;d[0]!==document&&/static/.test(d.css("position"))&&(u=l),h.left<(a._helper?l.left:0)&&(a.size.width=a.size.width+(a._helper?a.position.left-l.left:a.position.left-u.left),c&&(a.size.height=a.size.width/a.aspectRatio,p=!1),a.position.left=r.helper?l.left:0),h.top<(a._helper?l.top:0)&&(a.size.height=a.size.height+(a._helper?a.position.top-l.top:a.position.top),c&&(a.size.width=a.size.height*a.aspectRatio,p=!1),a.position.top=a._helper?l.top:0),n=a.containerElement.get(0)===a.element.parent().get(0),o=/relative|absolute/.test(a.containerElement.css("position")),n&&o?(a.offset.left=a.parentData.left+a.position.left,a.offset.top=a.parentData.top+a.position.top):(a.offset.left=a.element.offset().left,a.offset.top=a.element.offset().top),i=Math.abs(a.sizeDiff.width+(a._helper?a.offset.left-u.left:a.offset.left-l.left)),s=Math.abs(a.sizeDiff.height+(a._helper?a.offset.top-u.top:a.offset.top-l.top)),i+a.size.width>=a.parentData.width&&(a.size.width=a.parentData.width-i,c&&(a.size.height=a.size.width/a.aspectRatio,p=!1)),s+a.size.height>=a.parentData.height&&(a.size.height=a.parentData.height-s,c&&(a.size.width=a.size.height*a.aspectRatio,p=!1)),p||(a.position.left=a.prevPosition.left,a.position.top=a.prevPosition.top,a.size.width=a.prevSize.width,a.size.height=a.prevSize.height)},stop:function(){var e=t(this).resizable("instance"),i=e.options,s=e.containerOffset,n=e.containerPosition,o=e.containerElement,a=t(e.helper),r=a.offset(),l=a.outerWidth()-e.sizeDiff.width,h=a.outerHeight()-e.sizeDiff.height;e._helper&&!i.animate&&/relative/.test(o.css("position"))&&t(this).css({left:r.left-n.left-s.left,width:l,height:h}),e._helper&&!i.animate&&/static/.test(o.css("position"))&&t(this).css({left:r.left-n.left-s.left,width:l,height:h})}}),t.ui.plugin.add("resizable","alsoResize",{start:function(){var e=t(this).resizable("instance"),i=e.options;t(i.alsoResize).each(function(){var e=t(this);e.data("ui-resizable-alsoresize",{width:parseInt(e.width(),10),height:parseInt(e.height(),10),left:parseInt(e.css("left"),10),top:parseInt(e.css("top"),10)})})},resize:function(e,i){var s=t(this).resizable("instance"),n=s.options,o=s.originalSize,a=s.originalPosition,r={height:s.size.height-o.height||0,width:s.size.width-o.width||0,top:s.position.top-a.top||0,left:s.position.left-a.left||0};t(n.alsoResize).each(function(){var e=t(this),s=t(this).data("ui-resizable-alsoresize"),n={},o=e.parents(i.originalElement[0]).length?["width","height"]:["width","height","top","left"];t.each(o,function(t,e){var i=(s[e]||0)+(r[e]||0);i&&i>=0&&(n[e]=i||null)}),e.css(n)})},stop:function(){t(this).removeData("resizable-alsoresize")}}),t.ui.plugin.add("resizable","ghost",{start:function(){var e=t(this).resizable("instance"),i=e.options,s=e.size;e.ghost=e.originalElement.clone(),e.ghost.css({opacity:.25,display:"block",position:"relative",height:s.height,width:s.width,margin:0,left:0,top:0}).addClass("ui-resizable-ghost").addClass("string"==typeof i.ghost?i.ghost:""),e.ghost.appendTo(e.helper)},resize:function(){var e=t(this).resizable("instance");e.ghost&&e.ghost.css({position:"relative",height:e.size.height,width:e.size.width})},stop:function(){var e=t(this).resizable("instance");e.ghost&&e.helper&&e.helper.get(0).removeChild(e.ghost.get(0))}}),t.ui.plugin.add("resizable","grid",{resize:function(){var e,i=t(this).resizable("instance"),s=i.options,n=i.size,o=i.originalSize,a=i.originalPosition,r=i.axis,l="number"==typeof s.grid?[s.grid,s.grid]:s.grid,h=l[0]||1,c=l[1]||1,u=Math.round((n.width-o.width)/h)*h,d=Math.round((n.height-o.height)/c)*c,p=o.width+u,f=o.height+d,g=s.maxWidth&&p>s.maxWidth,m=s.maxHeight&&f>s.maxHeight,_=s.minWidth&&s.minWidth>p,v=s.minHeight&&s.minHeight>f;s.grid=l,_&&(p+=h),v&&(f+=c),g&&(p-=h),m&&(f-=c),/^(se|s|e)$/.test(r)?(i.size.width=p,i.size.height=f):/^(ne)$/.test(r)?(i.size.width=p,i.size.height=f,i.position.top=a.top-d):/^(sw)$/.test(r)?(i.size.width=p,i.size.height=f,i.position.left=a.left-u):((0>=f-c||0>=p-h)&&(e=i._getPaddingPlusBorderDimensions(this)),f-c>0?(i.size.height=f,i.position.top=a.top-d):(f=c-e.height,i.size.height=f,i.position.top=a.top+o.height-f),p-h>0?(i.size.width=p,i.position.left=a.left-u):(p=h-e.width,i.size.width=p,i.position.left=a.left+o.width-p))}}),t.ui.resizable,t.widget("ui.sortable",t.ui.mouse,{version:"1.11.4",widgetEventPrefix:"sort",ready:!1,options:{appendTo:"parent",axis:!1,connectWith:!1,containment:!1,cursor:"auto",cursorAt:!1,dropOnEmpty:!0,forcePlaceholderSize:!1,forceHelperSize:!1,grid:!1,handle:!1,helper:"original",items:"> *",opacity:!1,placeholder:!1,revert:!1,scroll:!0,scrollSensitivity:20,scrollSpeed:20,scope:"default",tolerance:"intersect",zIndex:1e3,activate:null,beforeStop:null,change:null,deactivate:null,out:null,over:null,receive:null,remove:null,sort:null,start:null,stop:null,update:null},_isOverAxis:function(t,e,i){return t>=e&&e+i>t},_isFloating:function(t){return/left|right/.test(t.css("float"))||/inline|table-cell/.test(t.css("display"))},_create:function(){this.containerCache={},this.element.addClass("ui-sortable"),this.refresh(),this.offset=this.element.offset(),this._mouseInit(),this._setHandleClassName(),this.ready=!0},_setOption:function(t,e){this._super(t,e),"handle"===t&&this._setHandleClassName()},_setHandleClassName:function(){this.element.find(".ui-sortable-handle").removeClass("ui-sortable-handle"),t.each(this.items,function(){(this.instance.options.handle?this.item.find(this.instance.options.handle):this.item).addClass("ui-sortable-handle")})},_destroy:function(){this.element.removeClass("ui-sortable ui-sortable-disabled").find(".ui-sortable-handle").removeClass("ui-sortable-handle"),this._mouseDestroy();for(var t=this.items.length-1;t>=0;t--)this.items[t].item.removeData(this.widgetName+"-item");return this},_mouseCapture:function(e,i){var s=null,n=!1,o=this;return this.reverting?!1:this.options.disabled||"static"===this.options.type?!1:(this._refreshItems(e),t(e.target).parents().each(function(){return t.data(this,o.widgetName+"-item")===o?(s=t(this),!1):void 0}),t.data(e.target,o.widgetName+"-item")===o&&(s=t(e.target)),s?!this.options.handle||i||(t(this.options.handle,s).find("*").addBack().each(function(){this===e.target&&(n=!0)}),n)?(this.currentItem=s,this._removeCurrentsFromItems(),!0):!1:!1)},_mouseStart:function(e,i,s){var n,o,a=this.options;if(this.currentContainer=this,this.refreshPositions(),this.helper=this._createHelper(e),this._cacheHelperProportions(),this._cacheMargins(),this.scrollParent=this.helper.scrollParent(),this.offset=this.currentItem.offset(),this.offset={top:this.offset.top-this.margins.top,left:this.offset.left-this.margins.left},t.extend(this.offset,{click:{left:e.pageX-this.offset.left,top:e.pageY-this.offset.top},parent:this._getParentOffset(),relative:this._getRelativeOffset()}),this.helper.css("position","absolute"),this.cssPosition=this.helper.css("position"),this.originalPosition=this._generatePosition(e),this.originalPageX=e.pageX,this.originalPageY=e.pageY,a.cursorAt&&this._adjustOffsetFromHelper(a.cursorAt),this.domPosition={prev:this.currentItem.prev()[0],parent:this.currentItem.parent()[0]},this.helper[0]!==this.currentItem[0]&&this.currentItem.hide(),this._createPlaceholder(),a.containment&&this._setContainment(),a.cursor&&"auto"!==a.cursor&&(o=this.document.find("body"),this.storedCursor=o.css("cursor"),o.css("cursor",a.cursor),this.storedStylesheet=t("").appendTo(o)),a.opacity&&(this.helper.css("opacity")&&(this._storedOpacity=this.helper.css("opacity")),this.helper.css("opacity",a.opacity)),a.zIndex&&(this.helper.css("zIndex")&&(this._storedZIndex=this.helper.css("zIndex")),this.helper.css("zIndex",a.zIndex)),this.scrollParent[0]!==this.document[0]&&"HTML"!==this.scrollParent[0].tagName&&(this.overflowOffset=this.scrollParent.offset()),this._trigger("start",e,this._uiHash()),this._preserveHelperProportions||this._cacheHelperProportions(),!s)for(n=this.containers.length-1;n>=0;n--)this.containers[n]._trigger("activate",e,this._uiHash(this));return t.ui.ddmanager&&(t.ui.ddmanager.current=this),t.ui.ddmanager&&!a.dropBehaviour&&t.ui.ddmanager.prepareOffsets(this,e),this.dragging=!0,this.helper.addClass("ui-sortable-helper"),this._mouseDrag(e),!0},_mouseDrag:function(e){var i,s,n,o,a=this.options,r=!1;for(this.position=this._generatePosition(e),this.positionAbs=this._convertPositionTo("absolute"),this.lastPositionAbs||(this.lastPositionAbs=this.positionAbs),this.options.scroll&&(this.scrollParent[0]!==this.document[0]&&"HTML"!==this.scrollParent[0].tagName?(this.overflowOffset.top+this.scrollParent[0].offsetHeight-e.pageY=0;i--)if(s=this.items[i],n=s.item[0],o=this._intersectsWithPointer(s),o&&s.instance===this.currentContainer&&n!==this.currentItem[0]&&this.placeholder[1===o?"next":"prev"]()[0]!==n&&!t.contains(this.placeholder[0],n)&&("semi-dynamic"===this.options.type?!t.contains(this.element[0],n):!0)){if(this.direction=1===o?"down":"up","pointer"!==this.options.tolerance&&!this._intersectsWithSides(s))break;this._rearrange(e,s),this._trigger("change",e,this._uiHash());break}return this._contactContainers(e),t.ui.ddmanager&&t.ui.ddmanager.drag(this,e),this._trigger("sort",e,this._uiHash()),this.lastPositionAbs=this.positionAbs,!1},_mouseStop:function(e,i){if(e){if(t.ui.ddmanager&&!this.options.dropBehaviour&&t.ui.ddmanager.drop(this,e),this.options.revert){var s=this,n=this.placeholder.offset(),o=this.options.axis,a={};o&&"x"!==o||(a.left=n.left-this.offset.parent.left-this.margins.left+(this.offsetParent[0]===this.document[0].body?0:this.offsetParent[0].scrollLeft)),o&&"y"!==o||(a.top=n.top-this.offset.parent.top-this.margins.top+(this.offsetParent[0]===this.document[0].body?0:this.offsetParent[0].scrollTop)),this.reverting=!0,t(this.helper).animate(a,parseInt(this.options.revert,10)||500,function(){s._clear(e)})}else this._clear(e,i);return!1}},cancel:function(){if(this.dragging){this._mouseUp({target:null}),"original"===this.options.helper?this.currentItem.css(this._storedCSS).removeClass("ui-sortable-helper"):this.currentItem.show();for(var e=this.containers.length-1;e>=0;e--)this.containers[e]._trigger("deactivate",null,this._uiHash(this)),this.containers[e].containerCache.over&&(this.containers[e]._trigger("out",null,this._uiHash(this)),this.containers[e].containerCache.over=0)}return this.placeholder&&(this.placeholder[0].parentNode&&this.placeholder[0].parentNode.removeChild(this.placeholder[0]),"original"!==this.options.helper&&this.helper&&this.helper[0].parentNode&&this.helper.remove(),t.extend(this,{helper:null,dragging:!1,reverting:!1,_noFinalSort:null}),this.domPosition.prev?t(this.domPosition.prev).after(this.currentItem):t(this.domPosition.parent).prepend(this.currentItem)),this},serialize:function(e){var i=this._getItemsAsjQuery(e&&e.connected),s=[];return e=e||{},t(i).each(function(){var i=(t(e.item||this).attr(e.attribute||"id")||"").match(e.expression||/(.+)[\-=_](.+)/);i&&s.push((e.key||i[1]+"[]")+"="+(e.key&&e.expression?i[1]:i[2]))}),!s.length&&e.key&&s.push(e.key+"="),s.join("&")},toArray:function(e){var i=this._getItemsAsjQuery(e&&e.connected),s=[];return e=e||{},i.each(function(){s.push(t(e.item||this).attr(e.attribute||"id")||"")}),s},_intersectsWith:function(t){var e=this.positionAbs.left,i=e+this.helperProportions.width,s=this.positionAbs.top,n=s+this.helperProportions.height,o=t.left,a=o+t.width,r=t.top,l=r+t.height,h=this.offset.click.top,c=this.offset.click.left,u="x"===this.options.axis||s+h>r&&l>s+h,d="y"===this.options.axis||e+c>o&&a>e+c,p=u&&d;return"pointer"===this.options.tolerance||this.options.forcePointerForContainers||"pointer"!==this.options.tolerance&&this.helperProportions[this.floating?"width":"height"]>t[this.floating?"width":"height"]?p:e+this.helperProportions.width/2>o&&a>i-this.helperProportions.width/2&&s+this.helperProportions.height/2>r&&l>n-this.helperProportions.height/2},_intersectsWithPointer:function(t){var e="x"===this.options.axis||this._isOverAxis(this.positionAbs.top+this.offset.click.top,t.top,t.height),i="y"===this.options.axis||this._isOverAxis(this.positionAbs.left+this.offset.click.left,t.left,t.width),s=e&&i,n=this._getDragVerticalDirection(),o=this._getDragHorizontalDirection();return s?this.floating?o&&"right"===o||"down"===n?2:1:n&&("down"===n?2:1):!1},_intersectsWithSides:function(t){var e=this._isOverAxis(this.positionAbs.top+this.offset.click.top,t.top+t.height/2,t.height),i=this._isOverAxis(this.positionAbs.left+this.offset.click.left,t.left+t.width/2,t.width),s=this._getDragVerticalDirection(),n=this._getDragHorizontalDirection();return this.floating&&n?"right"===n&&i||"left"===n&&!i:s&&("down"===s&&e||"up"===s&&!e)},_getDragVerticalDirection:function(){var t=this.positionAbs.top-this.lastPositionAbs.top;return 0!==t&&(t>0?"down":"up")},_getDragHorizontalDirection:function(){var t=this.positionAbs.left-this.lastPositionAbs.left;return 0!==t&&(t>0?"right":"left")},refresh:function(t){return this._refreshItems(t),this._setHandleClassName(),this.refreshPositions(),this},_connectWith:function(){var t=this.options;return t.connectWith.constructor===String?[t.connectWith]:t.connectWith},_getItemsAsjQuery:function(e){function i(){r.push(this)}var s,n,o,a,r=[],l=[],h=this._connectWith();if(h&&e)for(s=h.length-1;s>=0;s--)for(o=t(h[s],this.document[0]),n=o.length-1;n>=0;n--)a=t.data(o[n],this.widgetFullName),a&&a!==this&&!a.options.disabled&&l.push([t.isFunction(a.options.items)?a.options.items.call(a.element):t(a.options.items,a.element).not(".ui-sortable-helper").not(".ui-sortable-placeholder"),a]);for(l.push([t.isFunction(this.options.items)?this.options.items.call(this.element,null,{options:this.options,item:this.currentItem}):t(this.options.items,this.element).not(".ui-sortable-helper").not(".ui-sortable-placeholder"),this]),s=l.length-1;s>=0;s--)l[s][0].each(i);return t(r)},_removeCurrentsFromItems:function(){var e=this.currentItem.find(":data("+this.widgetName+"-item)");this.items=t.grep(this.items,function(t){for(var i=0;e.length>i;i++)if(e[i]===t.item[0])return!1;return!0})},_refreshItems:function(e){this.items=[],this.containers=[this];var i,s,n,o,a,r,l,h,c=this.items,u=[[t.isFunction(this.options.items)?this.options.items.call(this.element[0],e,{item:this.currentItem}):t(this.options.items,this.element),this]],d=this._connectWith();if(d&&this.ready)for(i=d.length-1;i>=0;i--)for(n=t(d[i],this.document[0]),s=n.length-1;s>=0;s--)o=t.data(n[s],this.widgetFullName),o&&o!==this&&!o.options.disabled&&(u.push([t.isFunction(o.options.items)?o.options.items.call(o.element[0],e,{item:this.currentItem}):t(o.options.items,o.element),o]),this.containers.push(o));for(i=u.length-1;i>=0;i--)for(a=u[i][1],r=u[i][0],s=0,h=r.length;h>s;s++)l=t(r[s]),l.data(this.widgetName+"-item",a),c.push({item:l,instance:a,width:0,height:0,left:0,top:0})},refreshPositions:function(e){this.floating=this.items.length?"x"===this.options.axis||this._isFloating(this.items[0].item):!1,this.offsetParent&&this.helper&&(this.offset.parent=this._getParentOffset());var i,s,n,o;for(i=this.items.length-1;i>=0;i--)s=this.items[i],s.instance!==this.currentContainer&&this.currentContainer&&s.item[0]!==this.currentItem[0]||(n=this.options.toleranceElement?t(this.options.toleranceElement,s.item):s.item,e||(s.width=n.outerWidth(),s.height=n.outerHeight()),o=n.offset(),s.left=o.left,s.top=o.top);if(this.options.custom&&this.options.custom.refreshContainers)this.options.custom.refreshContainers.call(this);else for(i=this.containers.length-1;i>=0;i--)o=this.containers[i].element.offset(),this.containers[i].containerCache.left=o.left,this.containers[i].containerCache.top=o.top,this.containers[i].containerCache.width=this.containers[i].element.outerWidth(),this.containers[i].containerCache.height=this.containers[i].element.outerHeight();return this},_createPlaceholder:function(e){e=e||this;var i,s=e.options;s.placeholder&&s.placeholder.constructor!==String||(i=s.placeholder,s.placeholder={element:function(){var s=e.currentItem[0].nodeName.toLowerCase(),n=t("<"+s+">",e.document[0]).addClass(i||e.currentItem[0].className+" ui-sortable-placeholder").removeClass("ui-sortable-helper");return"tbody"===s?e._createTrPlaceholder(e.currentItem.find("tr").eq(0),t("",e.document[0]).appendTo(n)):"tr"===s?e._createTrPlaceholder(e.currentItem,n):"img"===s&&n.attr("src",e.currentItem.attr("src")),i||n.css("visibility","hidden"),n},update:function(t,n){(!i||s.forcePlaceholderSize)&&(n.height()||n.height(e.currentItem.innerHeight()-parseInt(e.currentItem.css("paddingTop")||0,10)-parseInt(e.currentItem.css("paddingBottom")||0,10)),n.width()||n.width(e.currentItem.innerWidth()-parseInt(e.currentItem.css("paddingLeft")||0,10)-parseInt(e.currentItem.css("paddingRight")||0,10)))}}),e.placeholder=t(s.placeholder.element.call(e.element,e.currentItem)),e.currentItem.after(e.placeholder),s.placeholder.update(e,e.placeholder)},_createTrPlaceholder:function(e,i){var s=this;e.children().each(function(){t(" ",s.document[0]).attr("colspan",t(this).attr("colspan")||1).appendTo(i)})},_contactContainers:function(e){var i,s,n,o,a,r,l,h,c,u,d=null,p=null;for(i=this.containers.length-1;i>=0;i--)if(!t.contains(this.currentItem[0],this.containers[i].element[0]))if(this._intersectsWith(this.containers[i].containerCache)){if(d&&t.contains(this.containers[i].element[0],d.element[0]))continue; -d=this.containers[i],p=i}else this.containers[i].containerCache.over&&(this.containers[i]._trigger("out",e,this._uiHash(this)),this.containers[i].containerCache.over=0);if(d)if(1===this.containers.length)this.containers[p].containerCache.over||(this.containers[p]._trigger("over",e,this._uiHash(this)),this.containers[p].containerCache.over=1);else{for(n=1e4,o=null,c=d.floating||this._isFloating(this.currentItem),a=c?"left":"top",r=c?"width":"height",u=c?"clientX":"clientY",s=this.items.length-1;s>=0;s--)t.contains(this.containers[p].element[0],this.items[s].item[0])&&this.items[s].item[0]!==this.currentItem[0]&&(l=this.items[s].item.offset()[a],h=!1,e[u]-l>this.items[s][r]/2&&(h=!0),n>Math.abs(e[u]-l)&&(n=Math.abs(e[u]-l),o=this.items[s],this.direction=h?"up":"down"));if(!o&&!this.options.dropOnEmpty)return;if(this.currentContainer===this.containers[p])return this.currentContainer.containerCache.over||(this.containers[p]._trigger("over",e,this._uiHash()),this.currentContainer.containerCache.over=1),void 0;o?this._rearrange(e,o,null,!0):this._rearrange(e,null,this.containers[p].element,!0),this._trigger("change",e,this._uiHash()),this.containers[p]._trigger("change",e,this._uiHash(this)),this.currentContainer=this.containers[p],this.options.placeholder.update(this.currentContainer,this.placeholder),this.containers[p]._trigger("over",e,this._uiHash(this)),this.containers[p].containerCache.over=1}},_createHelper:function(e){var i=this.options,s=t.isFunction(i.helper)?t(i.helper.apply(this.element[0],[e,this.currentItem])):"clone"===i.helper?this.currentItem.clone():this.currentItem;return s.parents("body").length||t("parent"!==i.appendTo?i.appendTo:this.currentItem[0].parentNode)[0].appendChild(s[0]),s[0]===this.currentItem[0]&&(this._storedCSS={width:this.currentItem[0].style.width,height:this.currentItem[0].style.height,position:this.currentItem.css("position"),top:this.currentItem.css("top"),left:this.currentItem.css("left")}),(!s[0].style.width||i.forceHelperSize)&&s.width(this.currentItem.width()),(!s[0].style.height||i.forceHelperSize)&&s.height(this.currentItem.height()),s},_adjustOffsetFromHelper:function(e){"string"==typeof e&&(e=e.split(" ")),t.isArray(e)&&(e={left:+e[0],top:+e[1]||0}),"left"in e&&(this.offset.click.left=e.left+this.margins.left),"right"in e&&(this.offset.click.left=this.helperProportions.width-e.right+this.margins.left),"top"in e&&(this.offset.click.top=e.top+this.margins.top),"bottom"in e&&(this.offset.click.top=this.helperProportions.height-e.bottom+this.margins.top)},_getParentOffset:function(){this.offsetParent=this.helper.offsetParent();var e=this.offsetParent.offset();return"absolute"===this.cssPosition&&this.scrollParent[0]!==this.document[0]&&t.contains(this.scrollParent[0],this.offsetParent[0])&&(e.left+=this.scrollParent.scrollLeft(),e.top+=this.scrollParent.scrollTop()),(this.offsetParent[0]===this.document[0].body||this.offsetParent[0].tagName&&"html"===this.offsetParent[0].tagName.toLowerCase()&&t.ui.ie)&&(e={top:0,left:0}),{top:e.top+(parseInt(this.offsetParent.css("borderTopWidth"),10)||0),left:e.left+(parseInt(this.offsetParent.css("borderLeftWidth"),10)||0)}},_getRelativeOffset:function(){if("relative"===this.cssPosition){var t=this.currentItem.position();return{top:t.top-(parseInt(this.helper.css("top"),10)||0)+this.scrollParent.scrollTop(),left:t.left-(parseInt(this.helper.css("left"),10)||0)+this.scrollParent.scrollLeft()}}return{top:0,left:0}},_cacheMargins:function(){this.margins={left:parseInt(this.currentItem.css("marginLeft"),10)||0,top:parseInt(this.currentItem.css("marginTop"),10)||0}},_cacheHelperProportions:function(){this.helperProportions={width:this.helper.outerWidth(),height:this.helper.outerHeight()}},_setContainment:function(){var e,i,s,n=this.options;"parent"===n.containment&&(n.containment=this.helper[0].parentNode),("document"===n.containment||"window"===n.containment)&&(this.containment=[0-this.offset.relative.left-this.offset.parent.left,0-this.offset.relative.top-this.offset.parent.top,"document"===n.containment?this.document.width():this.window.width()-this.helperProportions.width-this.margins.left,("document"===n.containment?this.document.width():this.window.height()||this.document[0].body.parentNode.scrollHeight)-this.helperProportions.height-this.margins.top]),/^(document|window|parent)$/.test(n.containment)||(e=t(n.containment)[0],i=t(n.containment).offset(),s="hidden"!==t(e).css("overflow"),this.containment=[i.left+(parseInt(t(e).css("borderLeftWidth"),10)||0)+(parseInt(t(e).css("paddingLeft"),10)||0)-this.margins.left,i.top+(parseInt(t(e).css("borderTopWidth"),10)||0)+(parseInt(t(e).css("paddingTop"),10)||0)-this.margins.top,i.left+(s?Math.max(e.scrollWidth,e.offsetWidth):e.offsetWidth)-(parseInt(t(e).css("borderLeftWidth"),10)||0)-(parseInt(t(e).css("paddingRight"),10)||0)-this.helperProportions.width-this.margins.left,i.top+(s?Math.max(e.scrollHeight,e.offsetHeight):e.offsetHeight)-(parseInt(t(e).css("borderTopWidth"),10)||0)-(parseInt(t(e).css("paddingBottom"),10)||0)-this.helperProportions.height-this.margins.top])},_convertPositionTo:function(e,i){i||(i=this.position);var s="absolute"===e?1:-1,n="absolute"!==this.cssPosition||this.scrollParent[0]!==this.document[0]&&t.contains(this.scrollParent[0],this.offsetParent[0])?this.scrollParent:this.offsetParent,o=/(html|body)/i.test(n[0].tagName);return{top:i.top+this.offset.relative.top*s+this.offset.parent.top*s-("fixed"===this.cssPosition?-this.scrollParent.scrollTop():o?0:n.scrollTop())*s,left:i.left+this.offset.relative.left*s+this.offset.parent.left*s-("fixed"===this.cssPosition?-this.scrollParent.scrollLeft():o?0:n.scrollLeft())*s}},_generatePosition:function(e){var i,s,n=this.options,o=e.pageX,a=e.pageY,r="absolute"!==this.cssPosition||this.scrollParent[0]!==this.document[0]&&t.contains(this.scrollParent[0],this.offsetParent[0])?this.scrollParent:this.offsetParent,l=/(html|body)/i.test(r[0].tagName);return"relative"!==this.cssPosition||this.scrollParent[0]!==this.document[0]&&this.scrollParent[0]!==this.offsetParent[0]||(this.offset.relative=this._getRelativeOffset()),this.originalPosition&&(this.containment&&(e.pageX-this.offset.click.leftthis.containment[2]&&(o=this.containment[2]+this.offset.click.left),e.pageY-this.offset.click.top>this.containment[3]&&(a=this.containment[3]+this.offset.click.top)),n.grid&&(i=this.originalPageY+Math.round((a-this.originalPageY)/n.grid[1])*n.grid[1],a=this.containment?i-this.offset.click.top>=this.containment[1]&&i-this.offset.click.top<=this.containment[3]?i:i-this.offset.click.top>=this.containment[1]?i-n.grid[1]:i+n.grid[1]:i,s=this.originalPageX+Math.round((o-this.originalPageX)/n.grid[0])*n.grid[0],o=this.containment?s-this.offset.click.left>=this.containment[0]&&s-this.offset.click.left<=this.containment[2]?s:s-this.offset.click.left>=this.containment[0]?s-n.grid[0]:s+n.grid[0]:s)),{top:a-this.offset.click.top-this.offset.relative.top-this.offset.parent.top+("fixed"===this.cssPosition?-this.scrollParent.scrollTop():l?0:r.scrollTop()),left:o-this.offset.click.left-this.offset.relative.left-this.offset.parent.left+("fixed"===this.cssPosition?-this.scrollParent.scrollLeft():l?0:r.scrollLeft())}},_rearrange:function(t,e,i,s){i?i[0].appendChild(this.placeholder[0]):e.item[0].parentNode.insertBefore(this.placeholder[0],"down"===this.direction?e.item[0]:e.item[0].nextSibling),this.counter=this.counter?++this.counter:1;var n=this.counter;this._delay(function(){n===this.counter&&this.refreshPositions(!s)})},_clear:function(t,e){function i(t,e,i){return function(s){i._trigger(t,s,e._uiHash(e))}}this.reverting=!1;var s,n=[];if(!this._noFinalSort&&this.currentItem.parent().length&&this.placeholder.before(this.currentItem),this._noFinalSort=null,this.helper[0]===this.currentItem[0]){for(s in this._storedCSS)("auto"===this._storedCSS[s]||"static"===this._storedCSS[s])&&(this._storedCSS[s]="");this.currentItem.css(this._storedCSS).removeClass("ui-sortable-helper")}else this.currentItem.show();for(this.fromOutside&&!e&&n.push(function(t){this._trigger("receive",t,this._uiHash(this.fromOutside))}),!this.fromOutside&&this.domPosition.prev===this.currentItem.prev().not(".ui-sortable-helper")[0]&&this.domPosition.parent===this.currentItem.parent()[0]||e||n.push(function(t){this._trigger("update",t,this._uiHash())}),this!==this.currentContainer&&(e||(n.push(function(t){this._trigger("remove",t,this._uiHash())}),n.push(function(t){return function(e){t._trigger("receive",e,this._uiHash(this))}}.call(this,this.currentContainer)),n.push(function(t){return function(e){t._trigger("update",e,this._uiHash(this))}}.call(this,this.currentContainer)))),s=this.containers.length-1;s>=0;s--)e||n.push(i("deactivate",this,this.containers[s])),this.containers[s].containerCache.over&&(n.push(i("out",this,this.containers[s])),this.containers[s].containerCache.over=0);if(this.storedCursor&&(this.document.find("body").css("cursor",this.storedCursor),this.storedStylesheet.remove()),this._storedOpacity&&this.helper.css("opacity",this._storedOpacity),this._storedZIndex&&this.helper.css("zIndex","auto"===this._storedZIndex?"":this._storedZIndex),this.dragging=!1,e||this._trigger("beforeStop",t,this._uiHash()),this.placeholder[0].parentNode.removeChild(this.placeholder[0]),this.cancelHelperRemoval||(this.helper[0]!==this.currentItem[0]&&this.helper.remove(),this.helper=null),!e){for(s=0;n.length>s;s++)n[s].call(this,t);this._trigger("stop",t,this._uiHash())}return this.fromOutside=!1,!this.cancelHelperRemoval},_trigger:function(){t.Widget.prototype._trigger.apply(this,arguments)===!1&&this.cancel()},_uiHash:function(e){var i=e||this;return{helper:i.helper,placeholder:i.placeholder||t([]),position:i.position,originalPosition:i.originalPosition,offset:i.positionAbs,item:i.currentItem,sender:e?e.element:null}}}),t.widget("ui.slider",t.ui.mouse,{version:"1.11.4",widgetEventPrefix:"slide",options:{animate:!1,distance:0,max:100,min:0,orientation:"horizontal",range:!1,step:1,value:0,values:null,change:null,slide:null,start:null,stop:null},numPages:5,_create:function(){this._keySliding=!1,this._mouseSliding=!1,this._animateOff=!0,this._handleIndex=null,this._detectOrientation(),this._mouseInit(),this._calculateNewMax(),this.element.addClass("ui-slider ui-slider-"+this.orientation+" ui-widget"+" ui-widget-content"+" ui-corner-all"),this._refresh(),this._setOption("disabled",this.options.disabled),this._animateOff=!1},_refresh:function(){this._createRange(),this._createHandles(),this._setupEvents(),this._refreshValue()},_createHandles:function(){var e,i,s=this.options,n=this.element.find(".ui-slider-handle").addClass("ui-state-default ui-corner-all"),o="",a=[];for(i=s.values&&s.values.length||1,n.length>i&&(n.slice(i).remove(),n=n.slice(0,i)),e=n.length;i>e;e++)a.push(o);this.handles=n.add(t(a.join("")).appendTo(this.element)),this.handle=this.handles.eq(0),this.handles.each(function(e){t(this).data("ui-slider-handle-index",e)})},_createRange:function(){var e=this.options,i="";e.range?(e.range===!0&&(e.values?e.values.length&&2!==e.values.length?e.values=[e.values[0],e.values[0]]:t.isArray(e.values)&&(e.values=e.values.slice(0)):e.values=[this._valueMin(),this._valueMin()]),this.range&&this.range.length?this.range.removeClass("ui-slider-range-min ui-slider-range-max").css({left:"",bottom:""}):(this.range=t("
").appendTo(this.element),i="ui-slider-range ui-widget-header ui-corner-all"),this.range.addClass(i+("min"===e.range||"max"===e.range?" ui-slider-range-"+e.range:""))):(this.range&&this.range.remove(),this.range=null)},_setupEvents:function(){this._off(this.handles),this._on(this.handles,this._handleEvents),this._hoverable(this.handles),this._focusable(this.handles)},_destroy:function(){this.handles.remove(),this.range&&this.range.remove(),this.element.removeClass("ui-slider ui-slider-horizontal ui-slider-vertical ui-widget ui-widget-content ui-corner-all"),this._mouseDestroy()},_mouseCapture:function(e){var i,s,n,o,a,r,l,h,c=this,u=this.options;return u.disabled?!1:(this.elementSize={width:this.element.outerWidth(),height:this.element.outerHeight()},this.elementOffset=this.element.offset(),i={x:e.pageX,y:e.pageY},s=this._normValueFromMouse(i),n=this._valueMax()-this._valueMin()+1,this.handles.each(function(e){var i=Math.abs(s-c.values(e));(n>i||n===i&&(e===c._lastChangedValue||c.values(e)===u.min))&&(n=i,o=t(this),a=e)}),r=this._start(e,a),r===!1?!1:(this._mouseSliding=!0,this._handleIndex=a,o.addClass("ui-state-active").focus(),l=o.offset(),h=!t(e.target).parents().addBack().is(".ui-slider-handle"),this._clickOffset=h?{left:0,top:0}:{left:e.pageX-l.left-o.width()/2,top:e.pageY-l.top-o.height()/2-(parseInt(o.css("borderTopWidth"),10)||0)-(parseInt(o.css("borderBottomWidth"),10)||0)+(parseInt(o.css("marginTop"),10)||0)},this.handles.hasClass("ui-state-hover")||this._slide(e,a,s),this._animateOff=!0,!0))},_mouseStart:function(){return!0},_mouseDrag:function(t){var e={x:t.pageX,y:t.pageY},i=this._normValueFromMouse(e);return this._slide(t,this._handleIndex,i),!1},_mouseStop:function(t){return this.handles.removeClass("ui-state-active"),this._mouseSliding=!1,this._stop(t,this._handleIndex),this._change(t,this._handleIndex),this._handleIndex=null,this._clickOffset=null,this._animateOff=!1,!1},_detectOrientation:function(){this.orientation="vertical"===this.options.orientation?"vertical":"horizontal"},_normValueFromMouse:function(t){var e,i,s,n,o;return"horizontal"===this.orientation?(e=this.elementSize.width,i=t.x-this.elementOffset.left-(this._clickOffset?this._clickOffset.left:0)):(e=this.elementSize.height,i=t.y-this.elementOffset.top-(this._clickOffset?this._clickOffset.top:0)),s=i/e,s>1&&(s=1),0>s&&(s=0),"vertical"===this.orientation&&(s=1-s),n=this._valueMax()-this._valueMin(),o=this._valueMin()+s*n,this._trimAlignValue(o)},_start:function(t,e){var i={handle:this.handles[e],value:this.value()};return this.options.values&&this.options.values.length&&(i.value=this.values(e),i.values=this.values()),this._trigger("start",t,i)},_slide:function(t,e,i){var s,n,o;this.options.values&&this.options.values.length?(s=this.values(e?0:1),2===this.options.values.length&&this.options.range===!0&&(0===e&&i>s||1===e&&s>i)&&(i=s),i!==this.values(e)&&(n=this.values(),n[e]=i,o=this._trigger("slide",t,{handle:this.handles[e],value:i,values:n}),s=this.values(e?0:1),o!==!1&&this.values(e,i))):i!==this.value()&&(o=this._trigger("slide",t,{handle:this.handles[e],value:i}),o!==!1&&this.value(i))},_stop:function(t,e){var i={handle:this.handles[e],value:this.value()};this.options.values&&this.options.values.length&&(i.value=this.values(e),i.values=this.values()),this._trigger("stop",t,i)},_change:function(t,e){if(!this._keySliding&&!this._mouseSliding){var i={handle:this.handles[e],value:this.value()};this.options.values&&this.options.values.length&&(i.value=this.values(e),i.values=this.values()),this._lastChangedValue=e,this._trigger("change",t,i)}},value:function(t){return arguments.length?(this.options.value=this._trimAlignValue(t),this._refreshValue(),this._change(null,0),void 0):this._value()},values:function(e,i){var s,n,o;if(arguments.length>1)return this.options.values[e]=this._trimAlignValue(i),this._refreshValue(),this._change(null,e),void 0;if(!arguments.length)return this._values();if(!t.isArray(arguments[0]))return this.options.values&&this.options.values.length?this._values(e):this.value();for(s=this.options.values,n=arguments[0],o=0;s.length>o;o+=1)s[o]=this._trimAlignValue(n[o]),this._change(null,o);this._refreshValue()},_setOption:function(e,i){var s,n=0;switch("range"===e&&this.options.range===!0&&("min"===i?(this.options.value=this._values(0),this.options.values=null):"max"===i&&(this.options.value=this._values(this.options.values.length-1),this.options.values=null)),t.isArray(this.options.values)&&(n=this.options.values.length),"disabled"===e&&this.element.toggleClass("ui-state-disabled",!!i),this._super(e,i),e){case"orientation":this._detectOrientation(),this.element.removeClass("ui-slider-horizontal ui-slider-vertical").addClass("ui-slider-"+this.orientation),this._refreshValue(),this.handles.css("horizontal"===i?"bottom":"left","");break;case"value":this._animateOff=!0,this._refreshValue(),this._change(null,0),this._animateOff=!1;break;case"values":for(this._animateOff=!0,this._refreshValue(),s=0;n>s;s+=1)this._change(null,s);this._animateOff=!1;break;case"step":case"min":case"max":this._animateOff=!0,this._calculateNewMax(),this._refreshValue(),this._animateOff=!1;break;case"range":this._animateOff=!0,this._refresh(),this._animateOff=!1}},_value:function(){var t=this.options.value;return t=this._trimAlignValue(t)},_values:function(t){var e,i,s;if(arguments.length)return e=this.options.values[t],e=this._trimAlignValue(e);if(this.options.values&&this.options.values.length){for(i=this.options.values.slice(),s=0;i.length>s;s+=1)i[s]=this._trimAlignValue(i[s]);return i}return[]},_trimAlignValue:function(t){if(this._valueMin()>=t)return this._valueMin();if(t>=this._valueMax())return this._valueMax();var e=this.options.step>0?this.options.step:1,i=(t-this._valueMin())%e,s=t-i;return 2*Math.abs(i)>=e&&(s+=i>0?e:-e),parseFloat(s.toFixed(5))},_calculateNewMax:function(){var t=this.options.max,e=this._valueMin(),i=this.options.step,s=Math.floor(+(t-e).toFixed(this._precision())/i)*i;t=s+e,this.max=parseFloat(t.toFixed(this._precision()))},_precision:function(){var t=this._precisionOf(this.options.step);return null!==this.options.min&&(t=Math.max(t,this._precisionOf(this.options.min))),t},_precisionOf:function(t){var e=""+t,i=e.indexOf(".");return-1===i?0:e.length-i-1},_valueMin:function(){return this.options.min},_valueMax:function(){return this.max},_refreshValue:function(){var e,i,s,n,o,a=this.options.range,r=this.options,l=this,h=this._animateOff?!1:r.animate,c={};this.options.values&&this.options.values.length?this.handles.each(function(s){i=100*((l.values(s)-l._valueMin())/(l._valueMax()-l._valueMin())),c["horizontal"===l.orientation?"left":"bottom"]=i+"%",t(this).stop(1,1)[h?"animate":"css"](c,r.animate),l.options.range===!0&&("horizontal"===l.orientation?(0===s&&l.range.stop(1,1)[h?"animate":"css"]({left:i+"%"},r.animate),1===s&&l.range[h?"animate":"css"]({width:i-e+"%"},{queue:!1,duration:r.animate})):(0===s&&l.range.stop(1,1)[h?"animate":"css"]({bottom:i+"%"},r.animate),1===s&&l.range[h?"animate":"css"]({height:i-e+"%"},{queue:!1,duration:r.animate}))),e=i}):(s=this.value(),n=this._valueMin(),o=this._valueMax(),i=o!==n?100*((s-n)/(o-n)):0,c["horizontal"===this.orientation?"left":"bottom"]=i+"%",this.handle.stop(1,1)[h?"animate":"css"](c,r.animate),"min"===a&&"horizontal"===this.orientation&&this.range.stop(1,1)[h?"animate":"css"]({width:i+"%"},r.animate),"max"===a&&"horizontal"===this.orientation&&this.range[h?"animate":"css"]({width:100-i+"%"},{queue:!1,duration:r.animate}),"min"===a&&"vertical"===this.orientation&&this.range.stop(1,1)[h?"animate":"css"]({height:i+"%"},r.animate),"max"===a&&"vertical"===this.orientation&&this.range[h?"animate":"css"]({height:100-i+"%"},{queue:!1,duration:r.animate}))},_handleEvents:{keydown:function(e){var i,s,n,o,a=t(e.target).data("ui-slider-handle-index");switch(e.keyCode){case t.ui.keyCode.HOME:case t.ui.keyCode.END:case t.ui.keyCode.PAGE_UP:case t.ui.keyCode.PAGE_DOWN:case t.ui.keyCode.UP:case t.ui.keyCode.RIGHT:case t.ui.keyCode.DOWN:case t.ui.keyCode.LEFT:if(e.preventDefault(),!this._keySliding&&(this._keySliding=!0,t(e.target).addClass("ui-state-active"),i=this._start(e,a),i===!1))return}switch(o=this.options.step,s=n=this.options.values&&this.options.values.length?this.values(a):this.value(),e.keyCode){case t.ui.keyCode.HOME:n=this._valueMin();break;case t.ui.keyCode.END:n=this._valueMax();break;case t.ui.keyCode.PAGE_UP:n=this._trimAlignValue(s+(this._valueMax()-this._valueMin())/this.numPages);break;case t.ui.keyCode.PAGE_DOWN:n=this._trimAlignValue(s-(this._valueMax()-this._valueMin())/this.numPages);break;case t.ui.keyCode.UP:case t.ui.keyCode.RIGHT:if(s===this._valueMax())return;n=this._trimAlignValue(s+o);break;case t.ui.keyCode.DOWN:case t.ui.keyCode.LEFT:if(s===this._valueMin())return;n=this._trimAlignValue(s-o)}this._slide(e,a,n)},keyup:function(e){var i=t(e.target).data("ui-slider-handle-index");this._keySliding&&(this._keySliding=!1,this._stop(e,i),this._change(e,i),t(e.target).removeClass("ui-state-active"))}}});var a="ui-effects-",r=t;t.effects={effect:{}},function(t,e){function i(t,e,i){var s=u[e.type]||{};return null==t?i||!e.def?null:e.def:(t=s.floor?~~t:parseFloat(t),isNaN(t)?e.def:s.mod?(t+s.mod)%s.mod:0>t?0:t>s.max?s.max:t)}function s(i){var s=h(),n=s._rgba=[];return i=i.toLowerCase(),f(l,function(t,o){var a,r=o.re.exec(i),l=r&&o.parse(r),h=o.space||"rgba";return l?(a=s[h](l),s[c[h].cache]=a[c[h].cache],n=s._rgba=a._rgba,!1):e}),n.length?("0,0,0,0"===n.join()&&t.extend(n,o.transparent),s):o[i]}function n(t,e,i){return i=(i+1)%1,1>6*i?t+6*(e-t)*i:1>2*i?e:2>3*i?t+6*(e-t)*(2/3-i):t}var o,a="backgroundColor borderBottomColor borderLeftColor borderRightColor borderTopColor color columnRuleColor outlineColor textDecorationColor textEmphasisColor",r=/^([\-+])=\s*(\d+\.?\d*)/,l=[{re:/rgba?\(\s*(\d{1,3})\s*,\s*(\d{1,3})\s*,\s*(\d{1,3})\s*(?:,\s*(\d?(?:\.\d+)?)\s*)?\)/,parse:function(t){return[t[1],t[2],t[3],t[4]]}},{re:/rgba?\(\s*(\d+(?:\.\d+)?)\%\s*,\s*(\d+(?:\.\d+)?)\%\s*,\s*(\d+(?:\.\d+)?)\%\s*(?:,\s*(\d?(?:\.\d+)?)\s*)?\)/,parse:function(t){return[2.55*t[1],2.55*t[2],2.55*t[3],t[4]]}},{re:/#([a-f0-9]{2})([a-f0-9]{2})([a-f0-9]{2})/,parse:function(t){return[parseInt(t[1],16),parseInt(t[2],16),parseInt(t[3],16)]}},{re:/#([a-f0-9])([a-f0-9])([a-f0-9])/,parse:function(t){return[parseInt(t[1]+t[1],16),parseInt(t[2]+t[2],16),parseInt(t[3]+t[3],16)]}},{re:/hsla?\(\s*(\d+(?:\.\d+)?)\s*,\s*(\d+(?:\.\d+)?)\%\s*,\s*(\d+(?:\.\d+)?)\%\s*(?:,\s*(\d?(?:\.\d+)?)\s*)?\)/,space:"hsla",parse:function(t){return[t[1],t[2]/100,t[3]/100,t[4]]}}],h=t.Color=function(e,i,s,n){return new t.Color.fn.parse(e,i,s,n)},c={rgba:{props:{red:{idx:0,type:"byte"},green:{idx:1,type:"byte"},blue:{idx:2,type:"byte"}}},hsla:{props:{hue:{idx:0,type:"degrees"},saturation:{idx:1,type:"percent"},lightness:{idx:2,type:"percent"}}}},u={"byte":{floor:!0,max:255},percent:{max:1},degrees:{mod:360,floor:!0}},d=h.support={},p=t("

")[0],f=t.each;p.style.cssText="background-color:rgba(1,1,1,.5)",d.rgba=p.style.backgroundColor.indexOf("rgba")>-1,f(c,function(t,e){e.cache="_"+t,e.props.alpha={idx:3,type:"percent",def:1}}),h.fn=t.extend(h.prototype,{parse:function(n,a,r,l){if(n===e)return this._rgba=[null,null,null,null],this;(n.jquery||n.nodeType)&&(n=t(n).css(a),a=e);var u=this,d=t.type(n),p=this._rgba=[];return a!==e&&(n=[n,a,r,l],d="array"),"string"===d?this.parse(s(n)||o._default):"array"===d?(f(c.rgba.props,function(t,e){p[e.idx]=i(n[e.idx],e)}),this):"object"===d?(n instanceof h?f(c,function(t,e){n[e.cache]&&(u[e.cache]=n[e.cache].slice())}):f(c,function(e,s){var o=s.cache;f(s.props,function(t,e){if(!u[o]&&s.to){if("alpha"===t||null==n[t])return;u[o]=s.to(u._rgba)}u[o][e.idx]=i(n[t],e,!0)}),u[o]&&0>t.inArray(null,u[o].slice(0,3))&&(u[o][3]=1,s.from&&(u._rgba=s.from(u[o])))}),this):e},is:function(t){var i=h(t),s=!0,n=this;return f(c,function(t,o){var a,r=i[o.cache];return r&&(a=n[o.cache]||o.to&&o.to(n._rgba)||[],f(o.props,function(t,i){return null!=r[i.idx]?s=r[i.idx]===a[i.idx]:e})),s}),s},_space:function(){var t=[],e=this;return f(c,function(i,s){e[s.cache]&&t.push(i)}),t.pop()},transition:function(t,e){var s=h(t),n=s._space(),o=c[n],a=0===this.alpha()?h("transparent"):this,r=a[o.cache]||o.to(a._rgba),l=r.slice();return s=s[o.cache],f(o.props,function(t,n){var o=n.idx,a=r[o],h=s[o],c=u[n.type]||{};null!==h&&(null===a?l[o]=h:(c.mod&&(h-a>c.mod/2?a+=c.mod:a-h>c.mod/2&&(a-=c.mod)),l[o]=i((h-a)*e+a,n)))}),this[n](l)},blend:function(e){if(1===this._rgba[3])return this;var i=this._rgba.slice(),s=i.pop(),n=h(e)._rgba;return h(t.map(i,function(t,e){return(1-s)*n[e]+s*t}))},toRgbaString:function(){var e="rgba(",i=t.map(this._rgba,function(t,e){return null==t?e>2?1:0:t});return 1===i[3]&&(i.pop(),e="rgb("),e+i.join()+")"},toHslaString:function(){var e="hsla(",i=t.map(this.hsla(),function(t,e){return null==t&&(t=e>2?1:0),e&&3>e&&(t=Math.round(100*t)+"%"),t});return 1===i[3]&&(i.pop(),e="hsl("),e+i.join()+")"},toHexString:function(e){var i=this._rgba.slice(),s=i.pop();return e&&i.push(~~(255*s)),"#"+t.map(i,function(t){return t=(t||0).toString(16),1===t.length?"0"+t:t}).join("")},toString:function(){return 0===this._rgba[3]?"transparent":this.toRgbaString()}}),h.fn.parse.prototype=h.fn,c.hsla.to=function(t){if(null==t[0]||null==t[1]||null==t[2])return[null,null,null,t[3]];var e,i,s=t[0]/255,n=t[1]/255,o=t[2]/255,a=t[3],r=Math.max(s,n,o),l=Math.min(s,n,o),h=r-l,c=r+l,u=.5*c;return e=l===r?0:s===r?60*(n-o)/h+360:n===r?60*(o-s)/h+120:60*(s-n)/h+240,i=0===h?0:.5>=u?h/c:h/(2-c),[Math.round(e)%360,i,u,null==a?1:a]},c.hsla.from=function(t){if(null==t[0]||null==t[1]||null==t[2])return[null,null,null,t[3]];var e=t[0]/360,i=t[1],s=t[2],o=t[3],a=.5>=s?s*(1+i):s+i-s*i,r=2*s-a;return[Math.round(255*n(r,a,e+1/3)),Math.round(255*n(r,a,e)),Math.round(255*n(r,a,e-1/3)),o]},f(c,function(s,n){var o=n.props,a=n.cache,l=n.to,c=n.from;h.fn[s]=function(s){if(l&&!this[a]&&(this[a]=l(this._rgba)),s===e)return this[a].slice();var n,r=t.type(s),u="array"===r||"object"===r?s:arguments,d=this[a].slice();return f(o,function(t,e){var s=u["object"===r?t:e.idx];null==s&&(s=d[e.idx]),d[e.idx]=i(s,e)}),c?(n=h(c(d)),n[a]=d,n):h(d)},f(o,function(e,i){h.fn[e]||(h.fn[e]=function(n){var o,a=t.type(n),l="alpha"===e?this._hsla?"hsla":"rgba":s,h=this[l](),c=h[i.idx];return"undefined"===a?c:("function"===a&&(n=n.call(this,c),a=t.type(n)),null==n&&i.empty?this:("string"===a&&(o=r.exec(n),o&&(n=c+parseFloat(o[2])*("+"===o[1]?1:-1))),h[i.idx]=n,this[l](h)))})})}),h.hook=function(e){var i=e.split(" ");f(i,function(e,i){t.cssHooks[i]={set:function(e,n){var o,a,r="";if("transparent"!==n&&("string"!==t.type(n)||(o=s(n)))){if(n=h(o||n),!d.rgba&&1!==n._rgba[3]){for(a="backgroundColor"===i?e.parentNode:e;(""===r||"transparent"===r)&&a&&a.style;)try{r=t.css(a,"backgroundColor"),a=a.parentNode}catch(l){}n=n.blend(r&&"transparent"!==r?r:"_default")}n=n.toRgbaString()}try{e.style[i]=n}catch(l){}}},t.fx.step[i]=function(e){e.colorInit||(e.start=h(e.elem,i),e.end=h(e.end),e.colorInit=!0),t.cssHooks[i].set(e.elem,e.start.transition(e.end,e.pos))}})},h.hook(a),t.cssHooks.borderColor={expand:function(t){var e={};return f(["Top","Right","Bottom","Left"],function(i,s){e["border"+s+"Color"]=t}),e}},o=t.Color.names={aqua:"#00ffff",black:"#000000",blue:"#0000ff",fuchsia:"#ff00ff",gray:"#808080",green:"#008000",lime:"#00ff00",maroon:"#800000",navy:"#000080",olive:"#808000",purple:"#800080",red:"#ff0000",silver:"#c0c0c0",teal:"#008080",white:"#ffffff",yellow:"#ffff00",transparent:[null,null,null,0],_default:"#ffffff"}}(r),function(){function e(e){var i,s,n=e.ownerDocument.defaultView?e.ownerDocument.defaultView.getComputedStyle(e,null):e.currentStyle,o={};if(n&&n.length&&n[0]&&n[n[0]])for(s=n.length;s--;)i=n[s],"string"==typeof n[i]&&(o[t.camelCase(i)]=n[i]);else for(i in n)"string"==typeof n[i]&&(o[i]=n[i]);return o}function i(e,i){var s,o,a={};for(s in i)o=i[s],e[s]!==o&&(n[s]||(t.fx.step[s]||!isNaN(parseFloat(o)))&&(a[s]=o));return a}var s=["add","remove","toggle"],n={border:1,borderBottom:1,borderColor:1,borderLeft:1,borderRight:1,borderTop:1,borderWidth:1,margin:1,padding:1};t.each(["borderLeftStyle","borderRightStyle","borderBottomStyle","borderTopStyle"],function(e,i){t.fx.step[i]=function(t){("none"!==t.end&&!t.setAttr||1===t.pos&&!t.setAttr)&&(r.style(t.elem,i,t.end),t.setAttr=!0)}}),t.fn.addBack||(t.fn.addBack=function(t){return this.add(null==t?this.prevObject:this.prevObject.filter(t))}),t.effects.animateClass=function(n,o,a,r){var l=t.speed(o,a,r);return this.queue(function(){var o,a=t(this),r=a.attr("class")||"",h=l.children?a.find("*").addBack():a;h=h.map(function(){var i=t(this);return{el:i,start:e(this)}}),o=function(){t.each(s,function(t,e){n[e]&&a[e+"Class"](n[e])})},o(),h=h.map(function(){return this.end=e(this.el[0]),this.diff=i(this.start,this.end),this}),a.attr("class",r),h=h.map(function(){var e=this,i=t.Deferred(),s=t.extend({},l,{queue:!1,complete:function(){i.resolve(e)}});return this.el.animate(this.diff,s),i.promise()}),t.when.apply(t,h.get()).done(function(){o(),t.each(arguments,function(){var e=this.el;t.each(this.diff,function(t){e.css(t,"")})}),l.complete.call(a[0])})})},t.fn.extend({addClass:function(e){return function(i,s,n,o){return s?t.effects.animateClass.call(this,{add:i},s,n,o):e.apply(this,arguments)}}(t.fn.addClass),removeClass:function(e){return function(i,s,n,o){return arguments.length>1?t.effects.animateClass.call(this,{remove:i},s,n,o):e.apply(this,arguments)}}(t.fn.removeClass),toggleClass:function(e){return function(i,s,n,o,a){return"boolean"==typeof s||void 0===s?n?t.effects.animateClass.call(this,s?{add:i}:{remove:i},n,o,a):e.apply(this,arguments):t.effects.animateClass.call(this,{toggle:i},s,n,o)}}(t.fn.toggleClass),switchClass:function(e,i,s,n,o){return t.effects.animateClass.call(this,{add:i,remove:e},s,n,o)}})}(),function(){function e(e,i,s,n){return t.isPlainObject(e)&&(i=e,e=e.effect),e={effect:e},null==i&&(i={}),t.isFunction(i)&&(n=i,s=null,i={}),("number"==typeof i||t.fx.speeds[i])&&(n=s,s=i,i={}),t.isFunction(s)&&(n=s,s=null),i&&t.extend(e,i),s=s||i.duration,e.duration=t.fx.off?0:"number"==typeof s?s:s in t.fx.speeds?t.fx.speeds[s]:t.fx.speeds._default,e.complete=n||i.complete,e}function i(e){return!e||"number"==typeof e||t.fx.speeds[e]?!0:"string"!=typeof e||t.effects.effect[e]?t.isFunction(e)?!0:"object"!=typeof e||e.effect?!1:!0:!0}t.extend(t.effects,{version:"1.11.4",save:function(t,e){for(var i=0;e.length>i;i++)null!==e[i]&&t.data(a+e[i],t[0].style[e[i]])},restore:function(t,e){var i,s;for(s=0;e.length>s;s++)null!==e[s]&&(i=t.data(a+e[s]),void 0===i&&(i=""),t.css(e[s],i))},setMode:function(t,e){return"toggle"===e&&(e=t.is(":hidden")?"show":"hide"),e},getBaseline:function(t,e){var i,s;switch(t[0]){case"top":i=0;break;case"middle":i=.5;break;case"bottom":i=1;break;default:i=t[0]/e.height}switch(t[1]){case"left":s=0;break;case"center":s=.5;break;case"right":s=1;break;default:s=t[1]/e.width}return{x:s,y:i}},createWrapper:function(e){if(e.parent().is(".ui-effects-wrapper"))return e.parent();var i={width:e.outerWidth(!0),height:e.outerHeight(!0),"float":e.css("float")},s=t("

").addClass("ui-effects-wrapper").css({fontSize:"100%",background:"transparent",border:"none",margin:0,padding:0}),n={width:e.width(),height:e.height()},o=document.activeElement;try{o.id}catch(a){o=document.body}return e.wrap(s),(e[0]===o||t.contains(e[0],o))&&t(o).focus(),s=e.parent(),"static"===e.css("position")?(s.css({position:"relative"}),e.css({position:"relative"})):(t.extend(i,{position:e.css("position"),zIndex:e.css("z-index")}),t.each(["top","left","bottom","right"],function(t,s){i[s]=e.css(s),isNaN(parseInt(i[s],10))&&(i[s]="auto")}),e.css({position:"relative",top:0,left:0,right:"auto",bottom:"auto"})),e.css(n),s.css(i).show()},removeWrapper:function(e){var i=document.activeElement;return e.parent().is(".ui-effects-wrapper")&&(e.parent().replaceWith(e),(e[0]===i||t.contains(e[0],i))&&t(i).focus()),e},setTransition:function(e,i,s,n){return n=n||{},t.each(i,function(t,i){var o=e.cssUnit(i);o[0]>0&&(n[i]=o[0]*s+o[1])}),n}}),t.fn.extend({effect:function(){function i(e){function i(){t.isFunction(o)&&o.call(n[0]),t.isFunction(e)&&e()}var n=t(this),o=s.complete,r=s.mode;(n.is(":hidden")?"hide"===r:"show"===r)?(n[r](),i()):a.call(n[0],s,i)}var s=e.apply(this,arguments),n=s.mode,o=s.queue,a=t.effects.effect[s.effect]; -return t.fx.off||!a?n?this[n](s.duration,s.complete):this.each(function(){s.complete&&s.complete.call(this)}):o===!1?this.each(i):this.queue(o||"fx",i)},show:function(t){return function(s){if(i(s))return t.apply(this,arguments);var n=e.apply(this,arguments);return n.mode="show",this.effect.call(this,n)}}(t.fn.show),hide:function(t){return function(s){if(i(s))return t.apply(this,arguments);var n=e.apply(this,arguments);return n.mode="hide",this.effect.call(this,n)}}(t.fn.hide),toggle:function(t){return function(s){if(i(s)||"boolean"==typeof s)return t.apply(this,arguments);var n=e.apply(this,arguments);return n.mode="toggle",this.effect.call(this,n)}}(t.fn.toggle),cssUnit:function(e){var i=this.css(e),s=[];return t.each(["em","px","%","pt"],function(t,e){i.indexOf(e)>0&&(s=[parseFloat(i),e])}),s}})}(),function(){var e={};t.each(["Quad","Cubic","Quart","Quint","Expo"],function(t,i){e[i]=function(e){return Math.pow(e,t+2)}}),t.extend(e,{Sine:function(t){return 1-Math.cos(t*Math.PI/2)},Circ:function(t){return 1-Math.sqrt(1-t*t)},Elastic:function(t){return 0===t||1===t?t:-Math.pow(2,8*(t-1))*Math.sin((80*(t-1)-7.5)*Math.PI/15)},Back:function(t){return t*t*(3*t-2)},Bounce:function(t){for(var e,i=4;((e=Math.pow(2,--i))-1)/11>t;);return 1/Math.pow(4,3-i)-7.5625*Math.pow((3*e-2)/22-t,2)}}),t.each(e,function(e,i){t.easing["easeIn"+e]=i,t.easing["easeOut"+e]=function(t){return 1-i(1-t)},t.easing["easeInOut"+e]=function(t){return.5>t?i(2*t)/2:1-i(-2*t+2)/2}})}(),t.effects,t.effects.effect.slide=function(e,i){var s,n=t(this),o=["position","top","bottom","left","right","width","height"],a=t.effects.setMode(n,e.mode||"show"),r="show"===a,l=e.direction||"left",h="up"===l||"down"===l?"top":"left",c="up"===l||"left"===l,u={};t.effects.save(n,o),n.show(),s=e.distance||n["top"===h?"outerHeight":"outerWidth"](!0),t.effects.createWrapper(n).css({overflow:"hidden"}),r&&n.css(h,c?isNaN(s)?"-"+s:-s:s),u[h]=(r?c?"+=":"-=":c?"-=":"+=")+s,n.animate(u,{queue:!1,duration:e.duration,easing:e.easing,complete:function(){"hide"===a&&n.hide(),t.effects.restore(n,o),t.effects.removeWrapper(n),i()}})}}); \ No newline at end of file diff --git a/data/core.telegram.org/js/telegram-passport2.js b/data/core.telegram.org/js/telegram-passport2.js deleted file mode 100644 index 026006ade7..0000000000 --- a/data/core.telegram.org/js/telegram-passport2.js +++ /dev/null @@ -1,413 +0,0 @@ -(function(window) { - if (!Array.isArray) { - Array.isArray = function(arg) { - return Object.prototype.toString.call(arg) === '[object Array]'; - }; - } - if (!Object.isSimpleObject) { - Object.isSimpleObject = function(arg) { - return arg != null && typeof arg === 'object'; - }; - } - function isFunction(func) { - return func && {}.toString.call(func) === '[object Function]'; - } - function getEl(elOrId) { - if (elOrId.nodeType) return elOrId; - return document.getElementById(elOrId); - } - function preventDefault(event) { - if (window.event) { - window.event.returnValue = false; - } - else if (event.preventDefault) { - event.preventDefault(); - } - else { - event.returnValue = false; - } - } - function addEvent(el, event, handler) { - var events = event.split(/\s+/); - for (var i = 0; i < events.length; i++) { - if (el.addEventListener) { - el.addEventListener(events[i], handler, false); - } else { - el.attachEvent('on' + events[i], handler); - } - } - } - - var UA = window.navigator.userAgent || ''; - var ScopeAliases = { - personal_details: 'pd', - passport: 'pp', - driver_license: 'dl', - identity_card: 'ic', - internal_passport: 'ip', - id_document: 'idd', - address: 'ad', - utility_bill: 'ub', - bank_statement: 'bs', - rental_agreement: 'ra', - passport_registration: 'pr', - temporary_registration: 'tr', - address_document: 'add', - phone_number: 'pn', - email: 'em', - }; - - function openDeepLink(url, tooltipToggle) { - var is_ios = /ios|iphone os|iphone|ipod|ipad/i.test(UA); - var is_firefox = /firefox/i.test(UA); - var use_iframe = (is_ios || is_firefox); - var use_once = (!is_ios && is_firefox); - var timeOpen; - var ttNeedHide = false; - var pageShown = true; - var onPageHide = function() { - pageShown = false; - }; - tooltipToggle = tooltipToggle || function(){}; - var onPageShow = function() { - pageShown = true; - if (ttNeedHide && (+(new Date) - timeOpen) > 5000) { - tooltipToggle(false); - } - }; - addEvent(window, 'pagehide', onPageHide); - addEvent(window, 'pageshow', onPageShow); - addEvent(window, 'blur', onPageHide); - addEvent(window, 'focus', onPageShow); - var showTooltip = function() { - tooltipToggle(true); - if (!pageShown) { - ttNeedHide = true; - } - }; - if (use_iframe) { - var iframeEl = document.createElement('iframe'); - iframeEl.style.position = 'absolute'; - iframeEl.style.left = '-10000px'; - iframeEl.style.top = '-10000px'; - document.body.appendChild(iframeEl); - if (iframeEl !== null) { - timeOpen = +(new Date); - iframeEl.src = url; - setTimeout(showTooltip, 2500); - } - if (!use_once) { - setTimeout(function() { - if (pageShown) { - timeOpen = +(new Date); - window.location = url; - } - }, 2000); - } - } - else { - setTimeout(function() { - timeOpen = +(new Date); - window.location = url; - }, 100); - setTimeout(showTooltip, 1500); - } - } - - function packScope(scope) { - if (scope.data) { - scope.d = scope.data; - delete scope.data; - } - if (!scope.d) { - throw new TypeError('scope data is required'); - } - if (!scope.v) { - throw new TypeError('scope version is required'); - } - for (var i = 0; i < scope.d.length; i++) { - scope.d[i] = packScopeField(scope.d[i]); - } - return JSON.stringify(scope); - } - function packScopeField(field) { - if (field.one_of) { - field._ = field.one_of; - delete field.one_of; - } else if (field.type) { - field._ = field.type; - delete field.type; - } - if (Array.isArray(field._)) { - for (var j = 0; j < field._.length; j++) { - field._[j] = packScopeField(field._[j]); - } - field = packScopeOpts(field); - } else if (field._) { - if (ScopeAliases[field._]) { - field._ = ScopeAliases[field._]; - } - field = packScopeOpts(field); - } else if (ScopeAliases[field]) { - field = ScopeAliases[field]; - } - return field; - } - function packScopeOpts(scope) { - if (scope.selfie) { - scope.s = 1; - delete scope.selfie; - } - if (scope.translation) { - scope.t = 1; - delete scope.translation; - } - if (scope.native_names) { - scope.n = 1; - delete scope.native_names; - } - return scope; - } - - function passportAuth(options, tooltipToggle) { - if (!options.bot_id) { - throw new Error('bot_id is required'); - } - if (!options.scope) { - throw new Error('scope is required'); - } - if (!Object.isSimpleObject(options.scope)) { - throw new TypeError('scope should be an object'); - } - if (!options.public_key) { - throw new Error('public_key is required'); - } - if (!options.nonce) { - throw new Error('nonce is required'); - } - if (options.payload) { - throw new Error('payload is deprecated, use nonce instead'); - } - var is_android = /android/i.test(UA); - var url = (is_android ? 'tg:' : 'tg://') + 'resolve?domain=telegrampassport' - + '&bot_id=' + encodeURIComponent(options.bot_id) - + '&scope=' + encodeURIComponent(packScope(options.scope)) - + '&public_key=' + encodeURIComponent(options.public_key) - + '&nonce=' + encodeURIComponent(options.nonce); - if (options.callback_url) { - url += '&callback_url=' + encodeURIComponent(options.callback_url); - } - url += '&payload=nonce'; // legacy for outdated apps - openDeepLink(url, tooltipToggle); - } - - function createAuthButton(contEl, authDataOrFunc, options) { - contEl = getEl(contEl); - if (!contEl) { - return false; - } - options = options || {}; - var btnText = options.text || 'Log In With Telegram'; - var btnRadius = parseInt(options.radius, 10) || 23; - var tooltipText = options.tooltip_text || 'Please install Telegram to use this option.'; - var tooltipForce = options.tooltip_force || false; - var tooltipPos = options.tooltip_position; - if (tooltipPos == 'top') { - var tooltipWrapClass = 'tooltip-top'; - } else if (tooltipPos == 'left') { - var tooltipWrapClass = 'tooltip-left'; - } else if (tooltipPos == 'right') { - var tooltipWrapClass = 'tooltip-right'; - } else { - var tooltipWrapClass = 'tooltip-bottom'; - } - var btnStyle = '' - + '.telegram-passport {' - + 'display: inline-block;' - + 'position: relative;' - + 'max-width: 100%;' - + '}' - + 'button.telegram-passport-button {' - + 'display: inline-block;' - + 'vertical-align: top;' - + 'font-family: "Lucida Grande", Arial, Helvetica, sans-serif;' - + 'font-size: 16px;' - + 'font-weight: 500;' - + 'line-height: 20px;' - + 'text-align: left;' - + 'border-radius: ' + btnRadius + 'px;' - + 'background-color: #54a9eb;' - + 'text-decoration: none;' - + 'padding: 12px 21px 14px;' - + 'margin: 0;' - + 'white-space: nowrap;' - + 'text-overflow: ellipsis;' - + 'overflow: hidden;' - + 'border: none;' - + 'color: #fff;' - + 'cursor: pointer;' - + 'max-width: 100%;' - + '}' - + 'button.telegram-passport-button:focus {' - + 'outline: none;' - + '}' - + '.telegram-passport-tooltip-wrap {' - + 'position: absolute;' - + 'pointer-events: none;' - + 'text-align: center;' - + 'z-index: 100;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-bottom {' - + 'left: -500px;' - + 'right: -500px;' - + 'top: 100%;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-top {' - + 'left: -500px;' - + 'right: -500px;' - + 'bottom: 100%;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-left {' - + 'right: 100%;' - + 'top: 7px;' - + 'bottom: 7px;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-right {' - + 'left: 100%;' - + 'top: 7px;' - + 'bottom: 7px;' - + '}' - + '.telegram-passport-tooltip {' - + 'position: relative;' - + 'font-family: "Lucida Grande", Arial, Helvetica, sans-serif;' - + 'background: #949494;' - + 'color: #fff;' - + 'white-space: nowrap;' - + 'border-radius: ' + btnRadius + 'px;' - + 'padding: 7px 16px;' - + 'display: inline-block;' - + 'font-size: 14px;' - + 'line-height: 18px;' - + 'text-decoration: none;' - + 'pointer-events: none;' - + 'visibility: hidden;' - + 'opacity: 0;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-bottom .telegram-passport-tooltip {' - + 'margin-top: 32px;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-top .telegram-passport-tooltip {' - + 'margin-bottom: 32px;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-left .telegram-passport-tooltip {' - + 'margin-right: 32px;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-right .telegram-passport-tooltip {' - + 'margin-left: 32px;' - + '}' - + '.telegram-passport-tooltip:hover {' - + 'color: #fff;' - + 'text-decoration: none;' - + '}' - + '.telegram-passport-tooltip-shown {' - + 'transition: all .2s ease;' - + 'pointer-events: auto;' - + 'visibility: visible;' - + 'opacity: 1;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-bottom .telegram-passport-tooltip-shown {' - + 'margin-top: 16px;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-top .telegram-passport-tooltip-shown {' - + 'margin-bottom: 16px;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-left .telegram-passport-tooltip-shown {' - + 'margin-right: 16px;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-right .telegram-passport-tooltip-shown {' - + 'margin-left: 16px;' - + '}' - + '.telegram-passport-button-icon {' - + 'display: inline-block;' - + 'vertical-align: top;' - + "background: url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADYAAAAsCAYAAAFZD3u2AAAAAXNSR0IArs4c6QAAB+FJREFUaAXVWllsVFUYPndm2qG0Q4EipaWspSJbQRYxDWIUHyBqAgYTjUsTNBqN+qAJLg8+ugTlQeITARNQNERcXlyesAxVhOKSSGhLVyi0dDqdznTWznL9/ts5t2fuNrfTEvFP/p5//89/z52z3TJmArIsOyWtDkKZyxxEgE+SkOBMm5/rxlsSxpPpTFPrEJEqKJ4S4PfOgBSMp1QvkqmMSJCryOto6HuUsFwDwbvkRQDZb0rcLEM2JFRklFP1zJaQ0wm1t+FEmjxzQPUcioyxbPcHcyzsMOhXzhNyaZ1gMAeyYVF+visgskp2CYY0CHNzNGD42GxfWaFVKY4u9D1HQ2NGlkYO2QibdJFIgB5I3/zRLx/xXlUCgM8BQyc7QkQ5YceOerBZTGnpJBr2DkXHOK9zguIcV/JW+2IrTlDu5QZie7bdL1/oCogiorupvzpIpzMpit7ji+h0EBTxTG9yLRkTRuLq75GrlFZXj7fNf4ocMplMjqHI6JxIQE40uGZANurPghgRjjb39YI/IspAv6zhx1lv+/ALR73XJuYHiHlWQ4fpFCLRazwZb6ccH4FKgD/xgFbtpJIh0ENAw5eFksSS6Zs0cCawxTQZHA6aOOWIfaOJGCVoxltuBZRImd5gdAH0ZtPMGsVVf5T1DMUUaUVZ0QyLiYl7vkoETYkz0NJkSa0ptPaH2WAooerXLPSwirJilbcisjM/o2k0DsMSrTE68dZfvcH3Q8JqRzYNK+Ywl9P056INQ/wXXJizSnEhb1ta5KJImX+MeAw+W1sziy2cbfkAuKva8qpIYJmMDM60Dn2ICX8/ree+USUviVljQ03G6ZhYYhWh/k8HktVxcd5kZEhv20BojIUTKSxhLLRv2+JyHgCPeznoTs5rWhom/VquMdKxX52/8YNOqBEg8TtADsc06lvPIvMuYBdw9y3JhsDzgBeBIvRPazJEPiRG19AHppwMAZ8EpjSBjdjqgpIh0lJgh1HEdCYTTiTTOtWkEsHbATyuiyIIWroDcsfNsCCZIG0lg/lLEy7GVCiaDNBv8XogZmwgy17TZPBYDxww8xTlv17xK1uckYi6SxPVnN5DydQZBFI3+K+Bj5AiHwwEE+n2gbCT7LYun83cRQpp6MbnRxeS7ITFj4ZWxsK0t93vxNFEib6tbi5zONQ+G3tkpbSeKRtrS6ussnMwwq4HaEUaBxuLJhnGUNlMImhh+ogIK0hl5DSdL3giKsRmIgr7CY+t1o8Cl0L4LXADV1L7T1+IDUeSqsjtcrCttXQwsg2VqEw5n6nJRFckrh1LpU+c6xy5R5TPKnGxDROri6gypfnLQQaGybgn/XY4XTXbzeoqyzhruxWTWW4mYKgma+kJ2k4gGDYJtPlGn4wk5ribG8eSGXb07DUW1myAuN6kPSjKLR8jGfJH2eGLqn53LSjFLkt3IFb1nBAfIcksH6PiJEkj3Jm3SFwDupTzdtu8yTIOtk4M5nI6NzY2LLqOXkezPT8v6gU6ItAKmTfZA3UVfdxJcjh3NzYs/JPz1CLhVjS7RFmWzhkvA72xyHvZt+mz5qvmpxC44bdJ6516ujWO9D+VorC1wAPAG0AtdN/2ZaHHxcA9wO+Algs09BzO3laFoVfVwP3AS7yHBbaP/WeFocPbgIeBwQI7b+bWQ0Xp7ianu1Jk9yDmXmAjcDsw78QPGw7pgeDYSOdguKIap91ldyjbGK4za5VZazJJzAKpchSxEgwV8AyQFoVCINHti2WuDUeV+4QlFSVsyTxbBVEu2vXNwlSdLGjEUAD50baWingUSPvoggG3jLGOwah7IBin9cdNF/2rqz1snsfeDYuQ+BAVRXzeEUMR82H3FJCKWA+cFsA3jVhbf7hE3IwWYzO6rsbDSt0FPW/qVzUKU87RORFQBK22VMATwEltd2GfF+LJTKK1f9QdiikXrerVFW166Q6saHLXU9p8X/KiSEGHl9fRfqy1mi5+NJ5KY2Sc0TH9/U5VuZutqCyl7ct0pNuMOBd5IBqxnCMDV0ylDUSTcnt/WEqkMhRGdxCtQzFVk7zTy9OfM2JRZKs+KowcfSB6Gkiv4b3ASQFdrdJxFPcehn4uHBvX4PdTXjL+ccPQqHDhbhT2veiuFiYKRRoFrwD/eBbVkwx4uuuQenDIMKlFCTOz2KlMCFY3CIph4X+6UFSt1j1vYVoH4k93d89wJDzj1+tGBpDRZfiqqjLbNxUmYeyIX0Fhn2oNCyqMgjRd9jdg6mnWBqSLii3LrO94tD5T4OlMWo7ClGlWjFNwYRTklzbfYUmWnhcD0ux3Izj+KaMev6mNS8qZY3pmPTENpz9AUW9zRmynVNjJkyedC+p3RGUmq1uEUDzNBkcnvtFQsmL8mwJdoC21vzUS+2hFz0dhPiODKRVGAZs6g3UsmWznwUeiSTYkXG1xObUYuEsP11e9ON/jOgx2lagrgD6Oop4188t7N2DmyOX315ZfcUoO9XXAtY8O0IFBR5F0J77YrK2cVdQMfjWQHiotLSGdgz2B5d3DlEeM+oAlQfK2DffglVzcN5Jg+OcWpWsIHmdOaee+hkVNVn2FPy1u7wHfANrp02k8lwetYtoJYuWv6n7+e6C0pNjV3zEU9eCGOc0kx77n7qs5phrYJFDkAph+Dtxh4kJPrRaF9Zrob38xiqwHngLSf3TQh3X6YGXr++q/M6e7wZMmuzIAAAAASUVORK5CYII=') no-repeat;" - + 'background-size: 27px 22px;' - + 'width: 27px;' - + 'height: 22px;' - + 'margin: 0 15px -2px -5px;' - + '}' - + '.telegram-passport-tooltip:before {' - + "content: '';" - + 'display: inline-block;' - + 'position: absolute;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-bottom .telegram-passport-tooltip:before {' - + 'left: 50%;' - + 'top: 0;' - + 'border: 10px solid;' - + 'border-radius: 4px 0 0;' - + 'border-color: #949494 transparent transparent #949494;' - + 'transform: rotateZ(45deg) translate3d(-3px,5px,0);' - + 'transform-origin: 100% 0;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-top .telegram-passport-tooltip:before {' - + 'left: 50%;' - + 'bottom: 0;' - + 'border: 10px solid;' - + 'border-radius: 0 0 4px;' - + 'border-color: transparent #949494 #949494 transparent;' - + 'transform: rotateZ(45deg) translate3d(-11px,9px,0);' - + 'transform-origin: 0 100%;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-left .telegram-passport-tooltip:before {' - + 'top: 50%;' - + 'right: 0;' - + 'border: 8px solid;' - + 'border-radius: 0 2px 0 0;' - + 'border-color: #949494 #949494 transparent transparent;' - + 'transform: rotateZ(45deg) translate3d(4px,-3.5px,0);' - + 'transform-origin: 100% 0;' - + '}' - + '.telegram-passport-tooltip-wrap.tooltip-right .telegram-passport-tooltip:before {' - + 'top: 50%;' - + 'left: 0;' - + 'border: 8px solid;' - + 'border-radius: 0 0 0 2px;' - + 'border-color: transparent transparent #949494 #949494;' - + 'transform: rotateZ(45deg) translate3d(-15px,-7.5px,0);' - + 'transform-origin: 0 100%;' - + '}'; - var tooltipClass = tooltipForce ? 'telegram-passport-tooltip telegram-passport-tooltip-shown' : 'telegram-passport-tooltip'; - var btnHtml = '' - + '' - + '
' - + ''; - var btnContEl = document.createElement('div'); - btnContEl.className = 'telegram-passport'; - btnContEl.innerHTML = btnHtml; - contEl.appendChild(btnContEl); - var buttonEl = btnContEl.getElementsByTagName('button')[0]; - var tooltipEl = btnContEl.getElementsByTagName('a')[0]; - addEvent(buttonEl, 'click', function(e) { - preventDefault(e); - var options = isFunction(authDataOrFunc) ? authDataOrFunc() : authDataOrFunc; - options = options || {}; - var tooltipToggle = function(show) { - if (show) { - tooltipEl.classList.add('telegram-passport-tooltip-shown'); - } else { - tooltipEl.classList.remove('telegram-passport-tooltip-shown'); - } - }; - passportAuth(options, !tooltipForce ? tooltipToggle : null); - }); - } - - if (!window.Telegram) { - window.Telegram = {}; - } - window.Telegram.Passport = { - auth: passportAuth, - createAuthButton: createAuthButton, - }; -})(window); diff --git a/data/core.telegram.org/method/account.acceptAuthorization b/data/core.telegram.org/method/account.acceptAuthorization deleted file mode 100644 index 41d171d863..0000000000 --- a/data/core.telegram.org/method/account.acceptAuthorization +++ /dev/null @@ -1,170 +0,0 @@ - - - - - account.acceptAuthorization - - - - - - - - - - - - - -
- -
-
-
- -

account.acceptAuthorization

- -

Sends a Telegram Passport authorization form, effectively sharing data with the service

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.acceptAuthorization#f3ed4c73 bot_id:long scope:string public_key:string value_hashes:Vector<SecureValueHash> credentials:SecureCredentialsEncrypted = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
bot_idlongBot ID
scopestringTelegram Passport element types requested by the service
public_keystringService's public key
value_hashesVector<SecureValueHash>Types of values sent and their hashes
credentialsSecureCredentialsEncryptedEncrypted values
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.cancelPasswordEmail b/data/core.telegram.org/method/account.cancelPasswordEmail deleted file mode 100644 index 8a425c4876..0000000000 --- a/data/core.telegram.org/method/account.cancelPasswordEmail +++ /dev/null @@ -1,138 +0,0 @@ - - - - - account.cancelPasswordEmail - - - - - - - - - - - - - -
- -
-
-
- -

account.cancelPasswordEmail

- -

Cancel the code that was sent to verify an email to use as 2FA recovery method.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.cancelPasswordEmail#c1cbd5b6 = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Bool

-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.changePhone b/data/core.telegram.org/method/account.changePhone deleted file mode 100644 index 2535f5a017..0000000000 --- a/data/core.telegram.org/method/account.changePhone +++ /dev/null @@ -1,190 +0,0 @@ - - - - - account.changePhone - - - - - - - - - - - - - -
- -
-
-
- -

account.changePhone

- -

Change the phone number of the current account

-

- -
-
userEmpty#d3bc4b7a id:long = User;
-user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
----functions---
-account.changePhone#70c32edb phone_number:string phone_code_hash:string phone_code:string = User;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringNew phone number
phone_code_hashstringPhone code hash received when calling account.sendChangePhoneCode
phone_codestringPhone code received when calling account.sendChangePhoneCode
-

Result

-

User

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PHONE_CODE_EMPTYphone_code is missing.
400PHONE_NUMBER_INVALIDThe phone number is invalid.
400PHONE_NUMBER_OCCUPIEDThe phone number is already in use.
-

Related pages

-

account.sendChangePhoneCode

-

Verify a new phone number to associate to the current account

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.checkUsername b/data/core.telegram.org/method/account.checkUsername deleted file mode 100644 index fd10526b44..0000000000 --- a/data/core.telegram.org/method/account.checkUsername +++ /dev/null @@ -1,167 +0,0 @@ - - - - - account.checkUsername - - - - - - - - - - - - - -
- -
-
-
- -

account.checkUsername

- -

Validates a username and checks availability.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.checkUsername#2714d86c username:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
usernamestringusername
Accepted characters: A-z (case-insensitive), 0-9 and underscores.
Length: 5-32 characters.
-

Result

-

Return Bool result on whether the passed username can be used.

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400USERNAME_INVALIDUnacceptable username.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.confirmPasswordEmail b/data/core.telegram.org/method/account.confirmPasswordEmail deleted file mode 100644 index e4402828e6..0000000000 --- a/data/core.telegram.org/method/account.confirmPasswordEmail +++ /dev/null @@ -1,175 +0,0 @@ - - - - - account.confirmPasswordEmail - - - - - - - - - - - - - -
- -
-
-
- -

account.confirmPasswordEmail

- -

Verify an email to use as 2FA recovery method.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.confirmPasswordEmail#8fdf1920 code:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
codestringThe phone code that was received after setting a recovery email
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CODE_INVALIDCode invalid.
400EMAIL_HASH_EXPIREDEmail hash expired.
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.confirmPhone b/data/core.telegram.org/method/account.confirmPhone deleted file mode 100644 index a0c2ab7eec..0000000000 --- a/data/core.telegram.org/method/account.confirmPhone +++ /dev/null @@ -1,180 +0,0 @@ - - - - - account.confirmPhone - - - - - - - - - - - - - -
- -
-
-
- -

account.confirmPhone

- -

Confirm a phone number to cancel account deletion, for more info click here »

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.confirmPhone#5f2178c3 phone_code_hash:string phone_code:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_code_hashstringPhone code hash, for more info click here »
phone_codestringSMS code, for more info click here »
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CODE_HASH_INVALIDCode hash invalid.
400PHONE_CODE_EMPTYphone_code is missing.
-

Related pages

-

Account deletion

-

How to reset an account if the 2FA password was forgotten.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.createTheme b/data/core.telegram.org/method/account.createTheme deleted file mode 100644 index 80dbc9c1da..0000000000 --- a/data/core.telegram.org/method/account.createTheme +++ /dev/null @@ -1,186 +0,0 @@ - - - - - account.createTheme - - - - - - - - - - - - - -
- -
-
-
- -

account.createTheme

- -

Create a theme

-

- -
-
theme#e802b8dc flags:# creator:flags.0?true default:flags.1?true for_chat:flags.5?true id:long access_hash:long slug:string title:string document:flags.2?Document settings:flags.3?ThemeSettings installs_count:flags.4?int = Theme;
----functions---
-account.createTheme#8432c21f flags:# slug:string title:string document:flags.2?InputDocument settings:flags.3?InputThemeSettings = Theme;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
slugstringUnique theme ID
titlestringTheme name
documentflags.2?InputDocumentTheme file
settingsflags.3?InputThemeSettingsTheme settings
-

Result

-

Theme

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400THEME_MIME_INVALIDThe theme's MIME type is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.declinePasswordReset b/data/core.telegram.org/method/account.declinePasswordReset deleted file mode 100644 index da4fd72fc5..0000000000 --- a/data/core.telegram.org/method/account.declinePasswordReset +++ /dev/null @@ -1,155 +0,0 @@ - - - - - account.declinePasswordReset - - - - - - - - - - - - - -
- -
-
-
- -

account.declinePasswordReset

- -

Abort a pending 2FA password reset, see here for more info »

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.declinePasswordReset#4c9409f6 = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400RESET_REQUEST_MISSINGNo password reset is in progress.
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.deleteAccount b/data/core.telegram.org/method/account.deleteAccount deleted file mode 100644 index 24f85058e8..0000000000 --- a/data/core.telegram.org/method/account.deleteAccount +++ /dev/null @@ -1,170 +0,0 @@ - - - - - account.deleteAccount - - - - - - - - - - - - - -
- -
-
-
- -

account.deleteAccount

- -

Delete the user's account from the telegram servers. Can be used, for example, to delete the account of a user that provided the login code, but forgot the 2FA password and no recovery method is configured.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.deleteAccount#418d4e0b reason:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
reasonstringWhy is the account being deleted, can be empty
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
4202FA_CONFIRM_WAIT_XSince this account is active and protected by a 2FA password, we will delete it in 1 week for security purposes. You can cancel this process at any time, you'll be able to reset your account in X seconds.
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.deleteSecureValue b/data/core.telegram.org/method/account.deleteSecureValue deleted file mode 100644 index e00c9bf5ba..0000000000 --- a/data/core.telegram.org/method/account.deleteSecureValue +++ /dev/null @@ -1,153 +0,0 @@ - - - - - account.deleteSecureValue - - - - - - - - - - - - - -
- -
-
-
- -

account.deleteSecureValue

- -

Delete stored Telegram Passport documents, for more info see the passport docs »

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.deleteSecureValue#b880bc4b types:Vector<SecureValueType> = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
typesVector<SecureValueType>Document types to delete
-

Result

-

Bool

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.finishTakeoutSession b/data/core.telegram.org/method/account.finishTakeoutSession deleted file mode 100644 index cfed1c0658..0000000000 --- a/data/core.telegram.org/method/account.finishTakeoutSession +++ /dev/null @@ -1,172 +0,0 @@ - - - - - account.finishTakeoutSession - - - - - - - - - - - - - -
- -
-
-
- -

account.finishTakeoutSession

- -

Finish account takeout session

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.finishTakeoutSession#1d2652ee flags:# success:flags.0?true = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
successflags.0?trueData exported successfully
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
403TAKEOUT_REQUIREDA takeout session has to be initialized, first.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.getAccountTTL b/data/core.telegram.org/method/account.getAccountTTL deleted file mode 100644 index b45b7c26b5..0000000000 --- a/data/core.telegram.org/method/account.getAccountTTL +++ /dev/null @@ -1,134 +0,0 @@ - - - - - account.getAccountTTL - - - - - - - - - - - - - -
- -
-
-
- -

account.getAccountTTL

- -

Get days to live of account

-

- -
-
accountDaysTTL#b8d0afdf days:int = AccountDaysTTL;
----functions---
-account.getAccountTTL#8fc711d = AccountDaysTTL;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

AccountDaysTTL

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.getAllSecureValues b/data/core.telegram.org/method/account.getAllSecureValues deleted file mode 100644 index 62d4965fd1..0000000000 --- a/data/core.telegram.org/method/account.getAllSecureValues +++ /dev/null @@ -1,136 +0,0 @@ - - - - - account.getAllSecureValues - - - - - - - - - - - - - -
- -
-
-
- -

account.getAllSecureValues

- -

Get all saved Telegram Passport documents, for more info see the passport docs »

-

- -
-
---functions---
-account.getAllSecureValues#b288bc7d = Vector<SecureValue>;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Vector<SecureValue>

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.getAuthorizationForm b/data/core.telegram.org/method/account.getAuthorizationForm deleted file mode 100644 index 70e50136ea..0000000000 --- a/data/core.telegram.org/method/account.getAuthorizationForm +++ /dev/null @@ -1,176 +0,0 @@ - - - - - account.getAuthorizationForm - - - - - - - - - - - - - -
- -
-
-
- -

account.getAuthorizationForm

- -

Returns a Telegram Passport authorization form for sharing data with a service

-

- -
-
account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;
----functions---
-account.getAuthorizationForm#a929597a bot_id:long scope:string public_key:string = account.AuthorizationForm;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
bot_idlongUser identifier of the service's bot
scopestringTelegram Passport element types requested by the service
public_keystringService's public key
-

Result

-

account.AuthorizationForm

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PUBLIC_KEY_REQUIREDA public key is required.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.getAuthorizations b/data/core.telegram.org/method/account.getAuthorizations deleted file mode 100644 index 68575508d2..0000000000 --- a/data/core.telegram.org/method/account.getAuthorizations +++ /dev/null @@ -1,134 +0,0 @@ - - - - - account.getAuthorizations - - - - - - - - - - - - - -
- -
-
-
- -

account.getAuthorizations

- -

Get logged-in sessions

-

- -
-
account.authorizations#1250abde authorizations:Vector<Authorization> = account.Authorizations;
----functions---
-account.getAuthorizations#e320c158 = account.Authorizations;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

account.Authorizations

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.getAutoDownloadSettings b/data/core.telegram.org/method/account.getAutoDownloadSettings deleted file mode 100644 index c39115640f..0000000000 --- a/data/core.telegram.org/method/account.getAutoDownloadSettings +++ /dev/null @@ -1,134 +0,0 @@ - - - - - account.getAutoDownloadSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.getAutoDownloadSettings

- -

Get media autodownload settings

-

- -
-
account.autoDownloadSettings#63cacf26 low:AutoDownloadSettings medium:AutoDownloadSettings high:AutoDownloadSettings = account.AutoDownloadSettings;
----functions---
-account.getAutoDownloadSettings#56da0b3f = account.AutoDownloadSettings;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

account.AutoDownloadSettings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.getChatThemes b/data/core.telegram.org/method/account.getChatThemes deleted file mode 100644 index a5d227a10c..0000000000 --- a/data/core.telegram.org/method/account.getChatThemes +++ /dev/null @@ -1,153 +0,0 @@ - - - - - account.getChatThemes - - - - - - - - - - - - - -
- -
-
-
- -

account.getChatThemes

- -

Get all available chat themes

-

- -
-
account.chatThemesNotModified#e011e1c4 = account.ChatThemes;
-account.chatThemes#fe4cbebd hash:int themes:Vector<ChatTheme> = account.ChatThemes;
----functions---
-account.getChatThemes#d6d71d7b hash:int = account.ChatThemes;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashintHash for pagination, for more info click here
-

Result

-

account.ChatThemes

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.getContactSignUpNotification b/data/core.telegram.org/method/account.getContactSignUpNotification deleted file mode 100644 index b97b7bfed7..0000000000 --- a/data/core.telegram.org/method/account.getContactSignUpNotification +++ /dev/null @@ -1,135 +0,0 @@ - - - - - account.getContactSignUpNotification - - - - - - - - - - - - - -
- -
-
-
- -

account.getContactSignUpNotification

- -

Whether the user will receive notifications when contacts sign up

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.getContactSignUpNotification#9f07c728 = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.getContentSettings b/data/core.telegram.org/method/account.getContentSettings deleted file mode 100644 index ada398bd14..0000000000 --- a/data/core.telegram.org/method/account.getContentSettings +++ /dev/null @@ -1,134 +0,0 @@ - - - - - account.getContentSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.getContentSettings

- -

Get sensitive content settings

-

- -
-
account.contentSettings#57e28221 flags:# sensitive_enabled:flags.0?true sensitive_can_change:flags.1?true = account.ContentSettings;
----functions---
-account.getContentSettings#8b9b4dae = account.ContentSettings;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

account.ContentSettings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.getGlobalPrivacySettings b/data/core.telegram.org/method/account.getGlobalPrivacySettings deleted file mode 100644 index 1079a5c0d9..0000000000 --- a/data/core.telegram.org/method/account.getGlobalPrivacySettings +++ /dev/null @@ -1,134 +0,0 @@ - - - - - account.getGlobalPrivacySettings - - - - - - - - - - - - - -
- -
-
-
- -

account.getGlobalPrivacySettings

- -

Get global privacy settings

-

- -
-
globalPrivacySettings#bea2f424 flags:# archive_and_mute_new_noncontact_peers:flags.0?Bool = GlobalPrivacySettings;
----functions---
-account.getGlobalPrivacySettings#eb2b4cf6 = GlobalPrivacySettings;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

GlobalPrivacySettings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.getMultiWallPapers b/data/core.telegram.org/method/account.getMultiWallPapers deleted file mode 100644 index 4f62e29a73..0000000000 --- a/data/core.telegram.org/method/account.getMultiWallPapers +++ /dev/null @@ -1,148 +0,0 @@ - - - - - account.getMultiWallPapers - - - - - - - - - - - - - -
- -
-
-
- -

account.getMultiWallPapers

- -

Get info about multiple wallpapers

-

- -
-
---functions---
-account.getMultiWallPapers#65ad71dc wallpapers:Vector<InputWallPaper> = Vector<WallPaper>;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
wallpapersVector<InputWallPaper>Wallpapers to fetch info about
-

Result

-

Vector<WallPaper>

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.getNotifyExceptions b/data/core.telegram.org/method/account.getNotifyExceptions deleted file mode 100644 index adaf232fe5..0000000000 --- a/data/core.telegram.org/method/account.getNotifyExceptions +++ /dev/null @@ -1,165 +0,0 @@ - - - - - account.getNotifyExceptions - - - - - - - - - - - - - -
- -
-
-
- -

account.getNotifyExceptions

- -

Returns list of chats with non-default notification settings

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-account.getNotifyExceptions#53577479 flags:# compare_sound:flags.1?true peer:flags.0?InputNotifyPeer = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
compare_soundflags.1?trueIf true, chats with non-default sound will also be returned
peerflags.0?InputNotifyPeerIf specified, only chats of the specified category will be returned
-

Result

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.getPassword b/data/core.telegram.org/method/account.getPassword deleted file mode 100644 index ddf2624189..0000000000 --- a/data/core.telegram.org/method/account.getPassword +++ /dev/null @@ -1,134 +0,0 @@ - - - - - account.getPassword - - - - - - - - - - - - - -
- -
-
-
- -

account.getPassword

- -

Obtain configuration for two-factor authorization with password

-

- -
-
account.password#185b184f flags:# has_recovery:flags.0?true has_secure_values:flags.1?true has_password:flags.2?true current_algo:flags.2?PasswordKdfAlgo srp_B:flags.2?bytes srp_id:flags.2?long hint:flags.3?string email_unconfirmed_pattern:flags.4?string new_algo:PasswordKdfAlgo new_secure_algo:SecurePasswordKdfAlgo secure_random:bytes pending_reset_date:flags.5?int = account.Password;
----functions---
-account.getPassword#548a30f5 = account.Password;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

account.Password

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.getPasswordSettings b/data/core.telegram.org/method/account.getPasswordSettings deleted file mode 100644 index 715b84df6b..0000000000 --- a/data/core.telegram.org/method/account.getPasswordSettings +++ /dev/null @@ -1,170 +0,0 @@ - - - - - account.getPasswordSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.getPasswordSettings

- -

Get private info associated to the password info (recovery email, telegram passport info & so on)

-

- -
-
account.passwordSettings#9a5c33e5 flags:# email:flags.0?string secure_settings:flags.1?SecureSecretSettings = account.PasswordSettings;
----functions---
-account.getPasswordSettings#9cd4eaf9 password:InputCheckPasswordSRP = account.PasswordSettings;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
passwordInputCheckPasswordSRPThe password (see SRP)
-

Result

-

account.PasswordSettings

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PASSWORD_HASH_INVALIDThe provided password hash is invalid.
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.getPrivacy b/data/core.telegram.org/method/account.getPrivacy deleted file mode 100644 index 1f6a41188c..0000000000 --- a/data/core.telegram.org/method/account.getPrivacy +++ /dev/null @@ -1,166 +0,0 @@ - - - - - account.getPrivacy - - - - - - - - - - - - - -
- -
-
-
- -

account.getPrivacy

- -

Get privacy settings of current account

-

- -
-
account.privacyRules#50a04e45 rules:Vector<PrivacyRule> chats:Vector<Chat> users:Vector<User> = account.PrivacyRules;
----functions---
-account.getPrivacy#dadbc950 key:InputPrivacyKey = account.PrivacyRules;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
keyInputPrivacyKeyPeer category whose privacy settings should be fetched
-

Result

-

account.PrivacyRules

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PRIVACY_KEY_INVALIDThe privacy key is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.getSecureValue b/data/core.telegram.org/method/account.getSecureValue deleted file mode 100644 index 0ef660d197..0000000000 --- a/data/core.telegram.org/method/account.getSecureValue +++ /dev/null @@ -1,151 +0,0 @@ - - - - - account.getSecureValue - - - - - - - - - - - - - -
- -
-
-
- -

account.getSecureValue

- -

Get saved Telegram Passport document, for more info see the passport docs »

-

- -
-
---functions---
-account.getSecureValue#73665bc2 types:Vector<SecureValueType> = Vector<SecureValue>;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
typesVector<SecureValueType>Requested value types
-

Result

-

Vector<SecureValue>

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.getTheme b/data/core.telegram.org/method/account.getTheme deleted file mode 100644 index 3dc7e0300c..0000000000 --- a/data/core.telegram.org/method/account.getTheme +++ /dev/null @@ -1,181 +0,0 @@ - - - - - account.getTheme - - - - - - - - - - - - - -
- -
-
-
- -

account.getTheme

- -

Get theme information

-

- -
-
theme#e802b8dc flags:# creator:flags.0?true default:flags.1?true for_chat:flags.5?true id:long access_hash:long slug:string title:string document:flags.2?Document settings:flags.3?ThemeSettings installs_count:flags.4?int = Theme;
----functions---
-account.getTheme#8d9d742b format:string theme:InputTheme document_id:long = Theme;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
formatstringTheme format, a string that identifies the theming engines supported by the client
themeInputThemeTheme
document_idlongDocument ID
-

Result

-

Theme

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400THEME_FORMAT_INVALIDInvalid theme format provided.
400THEME_INVALIDInvalid theme provided.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.getThemes b/data/core.telegram.org/method/account.getThemes deleted file mode 100644 index eb2a65d98a..0000000000 --- a/data/core.telegram.org/method/account.getThemes +++ /dev/null @@ -1,158 +0,0 @@ - - - - - account.getThemes - - - - - - - - - - - - - -
- -
-
-
- -

account.getThemes

- -

Get installed themes

-

- -
-
account.themesNotModified#f41eb622 = account.Themes;
-account.themes#9a3d8c6d hash:long themes:Vector<Theme> = account.Themes;
----functions---
-account.getThemes#7206e458 format:string hash:long = account.Themes;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
formatstringTheme format, a string that identifies the theming engines supported by the client
hashlongHash for pagination, for more info click here
-

Result

-

account.Themes

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.getTmpPassword b/data/core.telegram.org/method/account.getTmpPassword deleted file mode 100644 index cbf1e9907b..0000000000 --- a/data/core.telegram.org/method/account.getTmpPassword +++ /dev/null @@ -1,176 +0,0 @@ - - - - - account.getTmpPassword - - - - - - - - - - - - - -
- -
-
-
- -

account.getTmpPassword

- -

Get temporary payment password

-

- -
-
account.tmpPassword#db64fd34 tmp_password:bytes valid_until:int = account.TmpPassword;
----functions---
-account.getTmpPassword#449e0b51 password:InputCheckPasswordSRP period:int = account.TmpPassword;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
passwordInputCheckPasswordSRPSRP password parameters
periodintTime during which the temporary password will be valid, in seconds; should be between 60 and 86400
-

Result

-

account.TmpPassword

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PASSWORD_HASH_INVALIDThe provided password hash is invalid.
400TMP_PASSWORD_DISABLEDThe temporary password is disabled.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.getWallPaper b/data/core.telegram.org/method/account.getWallPaper deleted file mode 100644 index d604d7a4ae..0000000000 --- a/data/core.telegram.org/method/account.getWallPaper +++ /dev/null @@ -1,167 +0,0 @@ - - - - - account.getWallPaper - - - - - - - - - - - - - -
- -
-
-
- -

account.getWallPaper

- -

Get info about a certain wallpaper

-

- -
-
wallPaper#a437c3ed id:long flags:# creator:flags.0?true default:flags.1?true pattern:flags.3?true dark:flags.4?true access_hash:long slug:string document:Document settings:flags.2?WallPaperSettings = WallPaper;
-wallPaperNoFile#e0804116 id:long flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;
----functions---
-account.getWallPaper#fc8ddbea wallpaper:InputWallPaper = WallPaper;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
wallpaperInputWallPaperThe wallpaper to get info about
-

Result

-

WallPaper

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400WALLPAPER_INVALIDThe specified wallpaper is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.getWallPapers b/data/core.telegram.org/method/account.getWallPapers deleted file mode 100644 index 15839451c4..0000000000 --- a/data/core.telegram.org/method/account.getWallPapers +++ /dev/null @@ -1,153 +0,0 @@ - - - - - account.getWallPapers - - - - - - - - - - - - - -
- -
-
-
- -

account.getWallPapers

- -

Returns a list of available wallpapers.

-

- -
-
account.wallPapersNotModified#1c199183 = account.WallPapers;
-account.wallPapers#cdc3858c hash:long wallpapers:Vector<WallPaper> = account.WallPapers;
----functions---
-account.getWallPapers#7967d36 hash:long = account.WallPapers;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
-

Result

-

Vector<WallPaper>

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.getWebAuthorizations b/data/core.telegram.org/method/account.getWebAuthorizations deleted file mode 100644 index ad5f1dd0b2..0000000000 --- a/data/core.telegram.org/method/account.getWebAuthorizations +++ /dev/null @@ -1,136 +0,0 @@ - - - - - account.getWebAuthorizations - - - - - - - - - - - - - -
- -
-
-
- -

account.getWebAuthorizations

- -

Get web login widget authorizations

-

- -
-
account.webAuthorizations#ed56c9fc authorizations:Vector<WebAuthorization> users:Vector<User> = account.WebAuthorizations;
----functions---
-account.getWebAuthorizations#182e6d6f = account.WebAuthorizations;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

account.WebAuthorizations

-

Related pages

-

Telegram Login Widget

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.initTakeoutSession b/data/core.telegram.org/method/account.initTakeoutSession deleted file mode 100644 index 4fe3de2e8e..0000000000 --- a/data/core.telegram.org/method/account.initTakeoutSession +++ /dev/null @@ -1,204 +0,0 @@ - - - - - account.initTakeoutSession - - - - - - - - - - - - - -
- -
-
-
- -

account.initTakeoutSession

- -

Initialize account takeout session

-

- -
-
account.takeout#4dba4501 id:long = account.Takeout;
----functions---
-account.initTakeoutSession#f05b4804 flags:# contacts:flags.0?true message_users:flags.1?true message_chats:flags.2?true message_megagroups:flags.3?true message_channels:flags.4?true files:flags.5?true file_max_size:flags.5?int = account.Takeout;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
contactsflags.0?trueWhether to export contacts
message_usersflags.1?trueWhether to export messages in private chats
message_chatsflags.2?trueWhether to export messages in legacy groups
message_megagroupsflags.3?trueWhether to export messages in supergroups
message_channelsflags.4?trueWhether to export messages in channels
filesflags.5?trueWhether to export files
file_max_sizeflags.5?intMaximum size of files to export
-

Result

-

account.Takeout

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
420TAKEOUT_INIT_DELAY_XWait X seconds before initing takeout.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.installTheme b/data/core.telegram.org/method/account.installTheme deleted file mode 100644 index cf52d5a670..0000000000 --- a/data/core.telegram.org/method/account.installTheme +++ /dev/null @@ -1,165 +0,0 @@ - - - - - account.installTheme - - - - - - - - - - - - - -
- -
-
-
- -

account.installTheme

- -

Install a theme

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.installTheme#7ae43737 flags:# dark:flags.0?true format:flags.1?string theme:flags.1?InputTheme = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
darkflags.0?trueWhether to install the dark version
formatflags.1?stringTheme format, a string that identifies the theming engines supported by the client
themeflags.1?InputThemeTheme to install
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.installWallPaper b/data/core.telegram.org/method/account.installWallPaper deleted file mode 100644 index 74f3f1f1e0..0000000000 --- a/data/core.telegram.org/method/account.installWallPaper +++ /dev/null @@ -1,172 +0,0 @@ - - - - - account.installWallPaper - - - - - - - - - - - - - -
- -
-
-
- -

account.installWallPaper

- -

Install wallpaper

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.installWallPaper#feed5769 wallpaper:InputWallPaper settings:WallPaperSettings = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
wallpaperInputWallPaperWallpaper to install
settingsWallPaperSettingsWallpaper settings
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400WALLPAPER_INVALIDThe specified wallpaper is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.registerDevice b/data/core.telegram.org/method/account.registerDevice deleted file mode 100644 index 6697495956..0000000000 --- a/data/core.telegram.org/method/account.registerDevice +++ /dev/null @@ -1,217 +0,0 @@ - - - - - account.registerDevice - - - - - - - - - - - - - -
- -
-
-
- -

account.registerDevice

- -

Register device to receive PUSH notifications

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.registerDevice#ec86017a flags:# no_muted:flags.0?true token_type:int token:string app_sandbox:Bool secret:bytes other_uids:Vector<long> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
no_mutedflags.0?trueAvoid receiving (silent and invisible background) notifications. Useful to save battery.
token_typeintDevice 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
tokenstringDevice token
app_sandboxBoolIf (boolTrue) is transmitted, a sandbox-certificate will be used during transmission.
secretbytesFor FCM and APNS VoIP, optional encryption key used to encrypt push notifications
other_uidsVector<long>List of user identifiers of other users currently using the client
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400TOKEN_INVALIDThe provided token is invalid.
400WEBPUSH_AUTH_INVALIDThe specified web push authentication secret is invalid.
400WEBPUSH_KEY_INVALIDThe specified web push elliptic curve Diffie-Hellman public key is invalid.
400WEBPUSH_TOKEN_INVALIDThe 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.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.reportPeer b/data/core.telegram.org/method/account.reportPeer deleted file mode 100644 index 054b3723e4..0000000000 --- a/data/core.telegram.org/method/account.reportPeer +++ /dev/null @@ -1,182 +0,0 @@ - - - - - account.reportPeer - - - - - - - - - - - - - -
- -
-
-
- -

account.reportPeer

- -

Report a peer for violation of telegram's Terms of Service

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.reportPeer#c5ba3d86 peer:InputPeer reason:ReportReason message:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe peer to report
reasonReportReasonThe reason why this peer is being reported
messagestringComment for report moderation
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.reportProfilePhoto b/data/core.telegram.org/method/account.reportProfilePhoto deleted file mode 100644 index 900673fd06..0000000000 --- a/data/core.telegram.org/method/account.reportProfilePhoto +++ /dev/null @@ -1,165 +0,0 @@ - - - - - account.reportProfilePhoto - - - - - - - - - - - - - -
- -
-
-
- -

account.reportProfilePhoto

- -

Report a profile photo of a dialog

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.reportProfilePhoto#fa8cc6f5 peer:InputPeer photo_id:InputPhoto reason:ReportReason message:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe dialog
photo_idInputPhotoDialog photo ID
reasonReportReasonReport reason
messagestringComment for report moderation
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.resendPasswordEmail b/data/core.telegram.org/method/account.resendPasswordEmail deleted file mode 100644 index 7cf2a8b50e..0000000000 --- a/data/core.telegram.org/method/account.resendPasswordEmail +++ /dev/null @@ -1,138 +0,0 @@ - - - - - account.resendPasswordEmail - - - - - - - - - - - - - -
- -
-
-
- -

account.resendPasswordEmail

- -

Resend the code to verify an email to use as 2FA recovery method.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.resendPasswordEmail#7a7f2a15 = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Bool

-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.resetAuthorization b/data/core.telegram.org/method/account.resetAuthorization deleted file mode 100644 index e603b1f203..0000000000 --- a/data/core.telegram.org/method/account.resetAuthorization +++ /dev/null @@ -1,175 +0,0 @@ - - - - - account.resetAuthorization - - - - - - - - - - - - - -
- -
-
-
- -

account.resetAuthorization

- -

Log out an active authorized session by its hash

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.resetAuthorization#df77f3bc hash:long = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashlongSession hash
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
406FRESH_RESET_AUTHORISATION_FORBIDDENYou can't logout other sessions if less than 24 hours have passed since you logged on the current session.
400HASH_INVALIDThe provided hash is invalid.
-

Related pages

-

User Authorization

-

How to register a user's phone to start using the API.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.resetNotifySettings b/data/core.telegram.org/method/account.resetNotifySettings deleted file mode 100644 index 92adca9942..0000000000 --- a/data/core.telegram.org/method/account.resetNotifySettings +++ /dev/null @@ -1,135 +0,0 @@ - - - - - account.resetNotifySettings - - - - - - - - - - - - - -
- -
-
-
- -

account.resetNotifySettings

- -

Resets all notification settings from users and groups.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.resetNotifySettings#db7e1747 = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.resetPassword b/data/core.telegram.org/method/account.resetPassword deleted file mode 100644 index 61198b6eb9..0000000000 --- a/data/core.telegram.org/method/account.resetPassword +++ /dev/null @@ -1,139 +0,0 @@ - - - - - account.resetPassword - - - - - - - - - - - - - -
- -
-
-
- -

account.resetPassword

- -

Initiate a 2FA password reset: can only be used if the user is already logged-in, see here for more info »

-

- -
-
account.resetPasswordFailedWait#e3779861 retry_date:int = account.ResetPasswordResult;
-account.resetPasswordRequestedWait#e9effc7d until_date:int = account.ResetPasswordResult;
-account.resetPasswordOk#e926d63e = account.ResetPasswordResult;
----functions---
-account.resetPassword#9308ce1b = account.ResetPasswordResult;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

account.ResetPasswordResult

-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.resetWebAuthorization b/data/core.telegram.org/method/account.resetWebAuthorization deleted file mode 100644 index ccdd83281b..0000000000 --- a/data/core.telegram.org/method/account.resetWebAuthorization +++ /dev/null @@ -1,171 +0,0 @@ - - - - - account.resetWebAuthorization - - - - - - - - - - - - - -
- -
-
-
- -

account.resetWebAuthorization

- -

Log out an active web telegram login session

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.resetWebAuthorization#2d01b9ef hash:long = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashlongSession hash
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400HASH_INVALIDThe provided hash is invalid.
-

Related pages

-

webAuthorization

-

Represents a bot logged in using the Telegram login widget

-

Telegram Login Widget

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.resetWebAuthorizations b/data/core.telegram.org/method/account.resetWebAuthorizations deleted file mode 100644 index 149c5e8d00..0000000000 --- a/data/core.telegram.org/method/account.resetWebAuthorizations +++ /dev/null @@ -1,137 +0,0 @@ - - - - - account.resetWebAuthorizations - - - - - - - - - - - - - -
- -
-
-
- -

account.resetWebAuthorizations

- -

Reset all active web telegram login sessions

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.resetWebAuthorizations#682d2594 = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Bool

-

Related pages

-

Telegram Login Widget

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.saveSecureValue b/data/core.telegram.org/method/account.saveSecureValue deleted file mode 100644 index 24aa048e70..0000000000 --- a/data/core.telegram.org/method/account.saveSecureValue +++ /dev/null @@ -1,174 +0,0 @@ - - - - - account.saveSecureValue - - - - - - - - - - - - - -
- -
-
-
- -

account.saveSecureValue

- -

Securely save Telegram Passport document, for more info see the passport docs »

-

- -
-
secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;
----functions---
-account.saveSecureValue#899fe31d value:InputSecureValue secure_secret_id:long = SecureValue;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
valueInputSecureValueSecure value, for more info see the passport docs »
secure_secret_idlongPassport secret hash, for more info see the passport docs »
-

Result

-

SecureValue

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PASSWORD_REQUIREDA 2FA password must be configured to use Telegram Passport.
-

Related pages

-

Telegram Passport Encryption Details

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.saveTheme b/data/core.telegram.org/method/account.saveTheme deleted file mode 100644 index 9dcbb739b5..0000000000 --- a/data/core.telegram.org/method/account.saveTheme +++ /dev/null @@ -1,155 +0,0 @@ - - - - - account.saveTheme - - - - - - - - - - - - - -
- -
-
-
- -

account.saveTheme

- -

Save a theme

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.saveTheme#f257106c theme:InputTheme unsave:Bool = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
themeInputThemeTheme to save
unsaveBoolUnsave
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.saveWallPaper b/data/core.telegram.org/method/account.saveWallPaper deleted file mode 100644 index dd980842fd..0000000000 --- a/data/core.telegram.org/method/account.saveWallPaper +++ /dev/null @@ -1,177 +0,0 @@ - - - - - account.saveWallPaper - - - - - - - - - - - - - -
- -
-
-
- -

account.saveWallPaper

- -

Install/uninstall wallpaper

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.saveWallPaper#6c5a5b37 wallpaper:InputWallPaper unsave:Bool settings:WallPaperSettings = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
wallpaperInputWallPaperWallpaper to save
unsaveBoolUninstall wallpaper?
settingsWallPaperSettingsWallpaper settings
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400WALLPAPER_INVALIDThe specified wallpaper is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.sendChangePhoneCode b/data/core.telegram.org/method/account.sendChangePhoneCode deleted file mode 100644 index 1985b88e2b..0000000000 --- a/data/core.telegram.org/method/account.sendChangePhoneCode +++ /dev/null @@ -1,186 +0,0 @@ - - - - - account.sendChangePhoneCode - - - - - - - - - - - - - -
- -
-
-
- -

account.sendChangePhoneCode

- -

Verify a new phone number to associate to the current account

-

- -
-
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
----functions---
-account.sendChangePhoneCode#82574ae5 phone_number:string settings:CodeSettings = auth.SentCode;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringNew phone number
settingsCodeSettingsPhone code settings
-

Result

-

auth.SentCode

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
406FRESH_CHANGE_PHONE_FORBIDDENYou can't change phone number right after logging in, please wait at least 24 hours.
400PHONE_NUMBER_BANNEDThe provided phone number is banned from telegram.
400PHONE_NUMBER_INVALIDThe phone number is invalid.
400PHONE_NUMBER_OCCUPIEDThe phone number is already in use.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.sendConfirmPhoneCode b/data/core.telegram.org/method/account.sendConfirmPhoneCode deleted file mode 100644 index 5f0a68690e..0000000000 --- a/data/core.telegram.org/method/account.sendConfirmPhoneCode +++ /dev/null @@ -1,174 +0,0 @@ - - - - - account.sendConfirmPhoneCode - - - - - - - - - - - - - -
- -
-
-
- -

account.sendConfirmPhoneCode

- -

Send confirmation code to cancel account deletion, for more info click here »

-

- -
-
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
----functions---
-account.sendConfirmPhoneCode#1b3faa88 hash:string settings:CodeSettings = auth.SentCode;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashstringThe hash from the service notification, for more info click here »
settingsCodeSettingsPhone code settings
-

Result

-

auth.SentCode

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400HASH_INVALIDThe provided hash is invalid.
-

Related pages

-

Account deletion

-

How to reset an account if the 2FA password was forgotten.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.sendVerifyEmailCode b/data/core.telegram.org/method/account.sendVerifyEmailCode deleted file mode 100644 index 0d1b49e604..0000000000 --- a/data/core.telegram.org/method/account.sendVerifyEmailCode +++ /dev/null @@ -1,168 +0,0 @@ - - - - - account.sendVerifyEmailCode - - - - - - - - - - - - - -
- -
-
-
- -

account.sendVerifyEmailCode

- -

Send the verification email code for telegram passport.

-

- -
-
account.sentEmailCode#811f854f email_pattern:string length:int = account.SentEmailCode;
----functions---
-account.sendVerifyEmailCode#7011509f email:string = account.SentEmailCode;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
emailstringThe email where to send the code
-

Result

-

account.SentEmailCode

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400EMAIL_INVALIDThe specified email is invalid.
-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.sendVerifyPhoneCode b/data/core.telegram.org/method/account.sendVerifyPhoneCode deleted file mode 100644 index aba57481a3..0000000000 --- a/data/core.telegram.org/method/account.sendVerifyPhoneCode +++ /dev/null @@ -1,173 +0,0 @@ - - - - - account.sendVerifyPhoneCode - - - - - - - - - - - - - -
- -
-
-
- -

account.sendVerifyPhoneCode

- -

Send the verification phone code for telegram passport.

-

- -
-
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
----functions---
-account.sendVerifyPhoneCode#a5a356f9 phone_number:string settings:CodeSettings = auth.SentCode;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringThe phone number to verify
settingsCodeSettingsPhone code settings
-

Result

-

auth.SentCode

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PHONE_NUMBER_INVALIDThe phone number is invalid.
-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.setAccountTTL b/data/core.telegram.org/method/account.setAccountTTL deleted file mode 100644 index 28e965e9bb..0000000000 --- a/data/core.telegram.org/method/account.setAccountTTL +++ /dev/null @@ -1,167 +0,0 @@ - - - - - account.setAccountTTL - - - - - - - - - - - - - -
- -
-
-
- -

account.setAccountTTL

- -

Set account self-destruction period

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.setAccountTTL#2442485e ttl:AccountDaysTTL = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
ttlAccountDaysTTLTime to live in days
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400TTL_DAYS_INVALIDThe provided TTL is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.setContactSignUpNotification b/data/core.telegram.org/method/account.setContactSignUpNotification deleted file mode 100644 index 25408513ca..0000000000 --- a/data/core.telegram.org/method/account.setContactSignUpNotification +++ /dev/null @@ -1,150 +0,0 @@ - - - - - account.setContactSignUpNotification - - - - - - - - - - - - - -
- -
-
-
- -

account.setContactSignUpNotification

- -

Toggle contact sign up notifications

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.setContactSignUpNotification#cff43f61 silent:Bool = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
silentBoolWhether to disable contact sign up notifications
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.setContentSettings b/data/core.telegram.org/method/account.setContentSettings deleted file mode 100644 index f043bdcdaf..0000000000 --- a/data/core.telegram.org/method/account.setContentSettings +++ /dev/null @@ -1,172 +0,0 @@ - - - - - account.setContentSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.setContentSettings

- -

Set sensitive content settings (for viewing or hiding NSFW content)

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.setContentSettings#b574b16b flags:# sensitive_enabled:flags.0?true = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
sensitive_enabledflags.0?trueEnable NSFW content
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
403SENSITIVE_CHANGE_FORBIDDENYou can't change your sensitive content settings.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.setGlobalPrivacySettings b/data/core.telegram.org/method/account.setGlobalPrivacySettings deleted file mode 100644 index 76950fec3c..0000000000 --- a/data/core.telegram.org/method/account.setGlobalPrivacySettings +++ /dev/null @@ -1,166 +0,0 @@ - - - - - account.setGlobalPrivacySettings - - - - - - - - - - - - - -
- -
-
-
- -

account.setGlobalPrivacySettings

- -

Set global privacy settings

-

- -
-
globalPrivacySettings#bea2f424 flags:# archive_and_mute_new_noncontact_peers:flags.0?Bool = GlobalPrivacySettings;
----functions---
-account.setGlobalPrivacySettings#1edaaac2 settings:GlobalPrivacySettings = GlobalPrivacySettings;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
settingsGlobalPrivacySettingsGlobal privacy settings
-

Result

-

GlobalPrivacySettings

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400AUTOARCHIVE_NOT_AVAILABLEThe autoarchive setting is not available at this time: please check the value of the autoarchive_setting_available field in client config » before calling this method.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.setPrivacy b/data/core.telegram.org/method/account.setPrivacy deleted file mode 100644 index 951971b764..0000000000 --- a/data/core.telegram.org/method/account.setPrivacy +++ /dev/null @@ -1,181 +0,0 @@ - - - - - account.setPrivacy - - - - - - - - - - - - - -
- -
-
-
- -

account.setPrivacy

- -

Change privacy settings of current account

-

- -
-
account.privacyRules#50a04e45 rules:Vector<PrivacyRule> chats:Vector<Chat> users:Vector<User> = account.PrivacyRules;
----functions---
-account.setPrivacy#c9f81ce8 key:InputPrivacyKey rules:Vector<InputPrivacyRule> = account.PrivacyRules;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
keyInputPrivacyKeyPeers to which the privacy rules apply
rulesVector<InputPrivacyRule>New privacy rules
-

Result

-

account.PrivacyRules

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PRIVACY_KEY_INVALIDThe privacy key is invalid.
400PRIVACY_TOO_LONGToo many privacy rules were specified, the current limit is 1000.
400PRIVACY_VALUE_INVALIDThe specified privacy rule combination is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.unregisterDevice b/data/core.telegram.org/method/account.unregisterDevice deleted file mode 100644 index 893d7e9322..0000000000 --- a/data/core.telegram.org/method/account.unregisterDevice +++ /dev/null @@ -1,180 +0,0 @@ - - - - - account.unregisterDevice - - - - - - - - - - - - - -
- -
-
-
- -

account.unregisterDevice

- -

Deletes a device by its token, stops sending PUSH-notifications to it.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.unregisterDevice#6a0d3206 token_type:int token:string other_uids:Vector<long> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
token_typeintDevice 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
tokenstringDevice token
other_uidsVector<long>List of user identifiers of other users currently using the client
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400TOKEN_INVALIDThe provided token is invalid.
-

Related pages

-

Handling PUSH-notifications

-

How to subscribe to and handle PUSH notifications

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.updateDeviceLocked b/data/core.telegram.org/method/account.updateDeviceLocked deleted file mode 100644 index 1e2cb58dbf..0000000000 --- a/data/core.telegram.org/method/account.updateDeviceLocked +++ /dev/null @@ -1,153 +0,0 @@ - - - - - account.updateDeviceLocked - - - - - - - - - - - - - -
- -
-
-
- -

account.updateDeviceLocked

- -

When client-side passcode lock feature is enabled, will not show message texts in incoming PUSH notifications.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.updateDeviceLocked#38df3532 period:int = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
periodintInactivity period after which to start hiding message texts in PUSH notifications.
-

Result

-

Bool

-

Related pages

-

Handling PUSH-notifications

-

How to subscribe to and handle PUSH notifications

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.updateNotifySettings b/data/core.telegram.org/method/account.updateNotifySettings deleted file mode 100644 index 39c1fd9be7..0000000000 --- a/data/core.telegram.org/method/account.updateNotifySettings +++ /dev/null @@ -1,192 +0,0 @@ - - - - - account.updateNotifySettings - - - - - - - - - - - - - -
- -
-
-
- -

account.updateNotifySettings

- -

Edits notification settings from a given user/group, from all users/all groups.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.updateNotifySettings#84be5b93 peer:InputNotifyPeer settings:InputPeerNotifySettings = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputNotifyPeerNotification source
settingsInputPeerNotifySettingsNotification settings
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400SETTINGS_INVALIDInvalid settings were provided.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.updatePasswordSettings b/data/core.telegram.org/method/account.updatePasswordSettings deleted file mode 100644 index f01f1f0f37..0000000000 --- a/data/core.telegram.org/method/account.updatePasswordSettings +++ /dev/null @@ -1,207 +0,0 @@ - - - - - account.updatePasswordSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.updatePasswordSettings

- -

Set a new 2FA password

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.updatePasswordSettings#a59b102f password:InputCheckPasswordSRP new_settings:account.PasswordInputSettings = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
passwordInputCheckPasswordSRPThe old password (see SRP)
new_settingsaccount.PasswordInputSettingsThe new password (see SRP)
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400EMAIL_UNCONFIRMEDEmail unconfirmed.
400EMAIL_UNCONFIRMED_XThe provided email isn't confirmed, X is the length of the verification code that was just sent to the email: use account.verifyEmail to enter the received verification code and enable the recovery email.
400NEW_SALT_INVALIDThe new salt is invalid.
400NEW_SETTINGS_INVALIDThe new password settings are invalid.
400PASSWORD_HASH_INVALIDThe old password hash is invalid.
400SRP_ID_INVALIDInvalid SRP ID provided.
400SRP_PASSWORD_CHANGEDPassword has changed.
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

-

account.verifyEmail

-

Verify an email address for telegram passport.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.updateProfile b/data/core.telegram.org/method/account.updateProfile deleted file mode 100644 index 21c5879fd4..0000000000 --- a/data/core.telegram.org/method/account.updateProfile +++ /dev/null @@ -1,187 +0,0 @@ - - - - - account.updateProfile - - - - - - - - - - - - - -
- -
-
-
- -

account.updateProfile

- -

Updates user profile.

-

- -
-
userEmpty#d3bc4b7a id:long = User;
-user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
----functions---
-account.updateProfile#78515775 flags:# first_name:flags.0?string last_name:flags.1?string about:flags.2?string = User;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
first_nameflags.0?stringNew user first name
last_nameflags.1?stringNew user last name
aboutflags.2?stringNew bio
-

Result

-

Returns User object containing the updated current user profile.

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400ABOUT_TOO_LONGAbout string too long.
400FIRSTNAME_INVALIDThe first name is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.updateStatus b/data/core.telegram.org/method/account.updateStatus deleted file mode 100644 index ac302243e0..0000000000 --- a/data/core.telegram.org/method/account.updateStatus +++ /dev/null @@ -1,155 +0,0 @@ - - - - - account.updateStatus - - - - - - - - - - - - - -
- -
-
-
- -

account.updateStatus

- -

Updates online user status.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.updateStatus#6628562c offline:Bool = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
offlineBoolIf (boolTrue) is transmitted, user status will change to (userStatusOffline).
-

Result

-

Bool

-

Related pages

-

boolTrue

-

The constructor can be interpreted as a booleantrue value.

-

userStatusOffline

-

The user's offline status.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.updateTheme b/data/core.telegram.org/method/account.updateTheme deleted file mode 100644 index 65a1ec22dc..0000000000 --- a/data/core.telegram.org/method/account.updateTheme +++ /dev/null @@ -1,196 +0,0 @@ - - - - - account.updateTheme - - - - - - - - - - - - - -
- -
-
-
- -

account.updateTheme

- -

Update theme

-

- -
-
theme#e802b8dc flags:# creator:flags.0?true default:flags.1?true for_chat:flags.5?true id:long access_hash:long slug:string title:string document:flags.2?Document settings:flags.3?ThemeSettings installs_count:flags.4?int = Theme;
----functions---
-account.updateTheme#5cb367d5 flags:# format:string theme:InputTheme slug:flags.0?string title:flags.1?string document:flags.2?InputDocument settings:flags.3?InputThemeSettings = Theme;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
formatstringTheme format, a string that identifies the theming engines supported by the client
themeInputThemeTheme to update
slugflags.0?stringUnique theme ID
titleflags.1?stringTheme name
documentflags.2?InputDocumentTheme file
settingsflags.3?InputThemeSettingsTheme settings
-

Result

-

Theme

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400THEME_INVALIDInvalid theme provided.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.updateUsername b/data/core.telegram.org/method/account.updateUsername deleted file mode 100644 index b9437b2210..0000000000 --- a/data/core.telegram.org/method/account.updateUsername +++ /dev/null @@ -1,182 +0,0 @@ - - - - - account.updateUsername - - - - - - - - - - - - - -
- -
-
-
- -

account.updateUsername

- -

Changes username for the current user.

-

- -
-
userEmpty#d3bc4b7a id:long = User;
-user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
----functions---
-account.updateUsername#3e0bdd7c username:string = User;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
usernamestringusername or empty string if username is to be removed
Accepted characters: a-z (case-insensitive), 0-9 and underscores.
Length: 5-32 characters.
-

Result

-

Returns updated information on the user in a User type object.

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400USERNAME_INVALIDUnacceptable username.
400USERNAME_NOT_MODIFIEDUsername is not different from the current username.
400USERNAME_OCCUPIEDUsername is taken.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.uploadTheme b/data/core.telegram.org/method/account.uploadTheme deleted file mode 100644 index 5b19e84a68..0000000000 --- a/data/core.telegram.org/method/account.uploadTheme +++ /dev/null @@ -1,190 +0,0 @@ - - - - - account.uploadTheme - - - - - - - - - - - - - -
- -
-
-
- -

account.uploadTheme

- -

Upload theme

-

- -
-
documentEmpty#36f8c871 id:long = Document;
-document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
----functions---
-account.uploadTheme#1c3db333 flags:# file:InputFile thumb:flags.0?InputFile file_name:string mime_type:string = Document;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
fileInputFileTheme file uploaded as described in files »
thumbflags.0?InputFileThumbnail
file_namestringFile name
mime_typestringMIME type, must be application/x-tgtheme-{format}, where format depends on the client
-

Result

-

Document

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400THEME_FILE_INVALIDInvalid theme file provided.
-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.uploadWallPaper b/data/core.telegram.org/method/account.uploadWallPaper deleted file mode 100644 index a300f42079..0000000000 --- a/data/core.telegram.org/method/account.uploadWallPaper +++ /dev/null @@ -1,182 +0,0 @@ - - - - - account.uploadWallPaper - - - - - - - - - - - - - -
- -
-
-
- -

account.uploadWallPaper

- -

Create and upload a new wallpaper

-

- -
-
wallPaper#a437c3ed id:long flags:# creator:flags.0?true default:flags.1?true pattern:flags.3?true dark:flags.4?true access_hash:long slug:string document:Document settings:flags.2?WallPaperSettings = WallPaper;
-wallPaperNoFile#e0804116 id:long flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;
----functions---
-account.uploadWallPaper#dd853661 file:InputFile mime_type:string settings:WallPaperSettings = WallPaper;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
fileInputFileThe JPG/PNG wallpaper
mime_typestringMIME type of uploaded wallpaper
settingsWallPaperSettingsWallpaper settings
-

Result

-

WallPaper

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400WALLPAPER_FILE_INVALIDThe specified wallpaper file is invalid.
400WALLPAPER_MIME_INVALIDThe specified wallpaper MIME type is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.verifyEmail b/data/core.telegram.org/method/account.verifyEmail deleted file mode 100644 index d261b1fb3c..0000000000 --- a/data/core.telegram.org/method/account.verifyEmail +++ /dev/null @@ -1,179 +0,0 @@ - - - - - account.verifyEmail - - - - - - - - - - - - - -
- -
-
-
- -

account.verifyEmail

- -

Verify an email address for telegram passport.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.verifyEmail#ecba39db email:string code:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
emailstringThe email to verify
codestringThe verification code that was received
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400EMAIL_INVALIDThe specified email is invalid.
400EMAIL_VERIFY_EXPIREDThe verification email has expired.
-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/account.verifyPhone b/data/core.telegram.org/method/account.verifyPhone deleted file mode 100644 index e2c406a197..0000000000 --- a/data/core.telegram.org/method/account.verifyPhone +++ /dev/null @@ -1,191 +0,0 @@ - - - - - account.verifyPhone - - - - - - - - - - - - - -
- -
-
-
- -

account.verifyPhone

- -

Verify a phone number for telegram passport.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.verifyPhone#4dd3a7f6 phone_number:string phone_code_hash:string phone_code:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number
phone_code_hashstringPhone code hash received from the call to account.sendVerifyPhoneCode
phone_codestringCode received after the call to account.sendVerifyPhoneCode
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PHONE_CODE_EMPTYphone_code is missing.
400PHONE_CODE_EXPIREDThe phone code you provided has expired, this may happen if it was sent to any chat on telegram (if the code is sent through a telegram chat (not the official account) to avoid it append or prepend to the code some chars).
400PHONE_NUMBER_INVALIDThe phone number is invalid.
-

Related pages

-

account.sendVerifyPhoneCode

-

Send the verification phone code for telegram passport.

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/auth.acceptLoginToken b/data/core.telegram.org/method/auth.acceptLoginToken deleted file mode 100644 index caa21a9e6b..0000000000 --- a/data/core.telegram.org/method/auth.acceptLoginToken +++ /dev/null @@ -1,171 +0,0 @@ - - - - - auth.acceptLoginToken - - - - - - - - - - - - - -
- -
-
-
- -

auth.acceptLoginToken

- -

Accept QR code login token, logging in the app that generated it.

-

Returns info about the new session.

-

For more info, see login via QR code.

-

- -
-
authorization#ad01d61d flags:# current:flags.0?true official_app:flags.1?true password_pending:flags.2?true encrypted_requests_disabled:flags.3?true call_requests_disabled:flags.4?true hash:long device_model:string platform:string system_version:string api_id:int app_name:string app_version:string date_created:int date_active:int ip:string country:string region:string = Authorization;
----functions---
-auth.acceptLoginToken#e894ad4d token:bytes = Authorization;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
tokenbytesLogin token embedded in QR code, for more info, see login via QR code.
-

Result

-

Authorization

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400AUTH_TOKEN_INVALIDXThe specified auth token is invalid.
-

Related pages

-

Login via QR code

-

QR code login flow

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/auth.cancelCode b/data/core.telegram.org/method/auth.cancelCode deleted file mode 100644 index 3d60859149..0000000000 --- a/data/core.telegram.org/method/auth.cancelCode +++ /dev/null @@ -1,180 +0,0 @@ - - - - - auth.cancelCode - - - - - - - - - - - - - -
- -
-
-
- -

auth.cancelCode

- -

Cancel the login verification code

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-auth.cancelCode#1f040578 phone_number:string phone_code_hash:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number
phone_code_hashstringPhone code hash from auth.sendCode
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PHONE_CODE_EXPIREDThe phone code you provided has expired, this may happen if it was sent to any chat on telegram (if the code is sent through a telegram chat (not the official account) to avoid it append or prepend to the code some chars).
400PHONE_NUMBER_INVALIDThe phone number is invalid.
-

Related pages

-

auth.sendCode

-

Send the verification code for login

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/auth.checkPassword b/data/core.telegram.org/method/auth.checkPassword deleted file mode 100644 index f989454809..0000000000 --- a/data/core.telegram.org/method/auth.checkPassword +++ /dev/null @@ -1,180 +0,0 @@ - - - - - auth.checkPassword - - - - - - - - - - - - - -
- -
-
-
- -

auth.checkPassword

- -

Try logging to an account protected by a 2FA password.

-

- -
-
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
-auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
----functions---
-auth.checkPassword#d18b4d16 password:InputCheckPasswordSRP = auth.Authorization;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
passwordInputCheckPasswordSRPThe account's password (see SRP)
-

Result

-

auth.Authorization

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PASSWORD_HASH_INVALIDThe provided password isn't valid.
400SRP_ID_INVALIDInvalid SRP ID provided.
400SRP_PASSWORD_CHANGEDPassword has changed.
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/auth.checkPhone b/data/core.telegram.org/method/auth.checkPhone deleted file mode 100644 index 331e76c0da..0000000000 --- a/data/core.telegram.org/method/auth.checkPhone +++ /dev/null @@ -1,176 +0,0 @@ - - - - - auth.checkPhone - - - - - - - - - - - - - -
- -
-
-
- -

auth.checkPhone

- -

Returns information on whether the passed phone number was registered.

-

- -
-
 Method schema is available as of layer 78. Switch »

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number in the international format
-

Result

-

The method returns an auth.CheckedPhone type object with information on whether an account with such a phone number has already been registered, as well as whether invitations were sent to this number (using the auth.sendInvites method).

-

Query example

-
(auth.checkPhone "79123413132")
-=
-(auth.checkedPhone
-  phone_registered:(boolFalse)
-  phone_invited:(boolFalse)
-)
-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PHONE_NUMBER_BANNEDThe provided phone number is banned from telegram
400PHONE_NUMBER_INVALIDInvalid phone number
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/auth.checkRecoveryPassword b/data/core.telegram.org/method/auth.checkRecoveryPassword deleted file mode 100644 index b63f6bf3f7..0000000000 --- a/data/core.telegram.org/method/auth.checkRecoveryPassword +++ /dev/null @@ -1,174 +0,0 @@ - - - - - auth.checkRecoveryPassword - - - - - - - - - - - - - -
- -
-
-
- -

auth.checkRecoveryPassword

- -

Check if the 2FA recovery code sent using auth.requestPasswordRecovery is valid, before passing it to auth.recoverPassword.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-auth.checkRecoveryPassword#d36bf79 code:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
codestringCode received via email
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PASSWORD_RECOVERY_EXPIREDThe recovery code has expired.
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

-

auth.requestPasswordRecovery

-

Request recovery code of a 2FA password, only for accounts with a recovery email configured.

-

auth.recoverPassword

-

Reset the 2FA password using the recovery code sent using auth.requestPasswordRecovery.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/auth.dropTempAuthKeys b/data/core.telegram.org/method/auth.dropTempAuthKeys deleted file mode 100644 index 00f577e8ed..0000000000 --- a/data/core.telegram.org/method/auth.dropTempAuthKeys +++ /dev/null @@ -1,151 +0,0 @@ - - - - - auth.dropTempAuthKeys - - - - - - - - - - - - - -
- -
-
-
- -

auth.dropTempAuthKeys

- -

Delete all temporary authorization keys except for the ones specified

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-auth.dropTempAuthKeys#8e48a188 except_auth_keys:Vector<long> = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
except_auth_keysVector<long>The auth keys that shouldn't be dropped.
-

Result

-

Bool

-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/auth.exportAuthorization b/data/core.telegram.org/method/auth.exportAuthorization deleted file mode 100644 index b0c1f3826c..0000000000 --- a/data/core.telegram.org/method/auth.exportAuthorization +++ /dev/null @@ -1,167 +0,0 @@ - - - - - auth.exportAuthorization - - - - - - - - - - - - - -
- -
-
-
- -

auth.exportAuthorization

- -

Returns data for copying authorization to another data-centre.

-

- -
-
auth.exportedAuthorization#b434e2b8 id:long bytes:bytes = auth.ExportedAuthorization;
----functions---
-auth.exportAuthorization#e5bfffcd dc_id:int = auth.ExportedAuthorization;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
dc_idintNumber of a target data-centre
-

Result

-

auth.ExportedAuthorization

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400DC_ID_INVALIDThe provided DC ID is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/auth.exportLoginToken b/data/core.telegram.org/method/auth.exportLoginToken deleted file mode 100644 index 54a1acf57f..0000000000 --- a/data/core.telegram.org/method/auth.exportLoginToken +++ /dev/null @@ -1,183 +0,0 @@ - - - - - auth.exportLoginToken - - - - - - - - - - - - - -
- -
-
-
- -

auth.exportLoginToken

- -

Generate a login token, for login via QR code.
-The generated login token should be encoded using base64url, then shown as a tg://login?token=base64encodedtoken URL in the QR code.

-

For more info, see login via QR code.

-

- -
-
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
-auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;
-auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;
----functions---
-auth.exportLoginToken#b7e085fe api_id:int api_hash:string except_ids:Vector<long> = auth.LoginToken;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
api_idintApplication identifier (see. App configuration)
api_hashstringApplication identifier hash (see. App configuration)
except_idsVector<long>List of already logged-in user IDs, to prevent logging in twice with the same user
-

Result

-

auth.LoginToken

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400API_ID_INVALIDAPI ID invalid.
-

Related pages

-

Login via QR code

-

QR code login flow

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/auth.importAuthorization b/data/core.telegram.org/method/auth.importAuthorization deleted file mode 100644 index 23da4b4419..0000000000 --- a/data/core.telegram.org/method/auth.importAuthorization +++ /dev/null @@ -1,178 +0,0 @@ - - - - - auth.importAuthorization - - - - - - - - - - - - - -
- -
-
-
- -

auth.importAuthorization

- -

Logs in a user using a key transmitted from his native data-centre.

-

- -
-
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
-auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
----functions---
-auth.importAuthorization#a57a7dad id:long bytes:bytes = auth.Authorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongUser ID
bytesbytesAuthorization key
-

Result

-

auth.Authorization

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400AUTH_BYTES_INVALIDThe provided authorization is invalid.
400USER_ID_INVALIDThe provided user ID is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/auth.importBotAuthorization b/data/core.telegram.org/method/auth.importBotAuthorization deleted file mode 100644 index 7e42ede178..0000000000 --- a/data/core.telegram.org/method/auth.importBotAuthorization +++ /dev/null @@ -1,205 +0,0 @@ - - - - - auth.importBotAuthorization - - - - - - - - - - - - - -
- -
-
-
- -

auth.importBotAuthorization

- -

Login as a bot

-

- -
-
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
-auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
----functions---
-auth.importBotAuthorization#67a3ff2c flags:int api_id:int api_hash:string bot_auth_token:string = auth.Authorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flagsintReserved for future use
api_idintApplication identifier (see. App configuration)
api_hashstringApplication identifier hash (see. App configuration)
bot_auth_tokenstringBot token (see bots)
-

Result

-

Returns an auth.Authorization object with information on the new authorization.

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400ACCESS_TOKEN_EXPIREDBot token expired.
400ACCESS_TOKEN_INVALIDThe provided token is not valid.
400API_ID_INVALIDThe api_id/api_hash combination is invalid.
400API_ID_PUBLISHED_FLOODThis API id was published somewhere, you can't use it now.
401AUTH_KEY_INVALIDAuth key invalid.
-

Bots can use this method

-

Related pages

-

Bots: An introduction for developers

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/auth.importLoginToken b/data/core.telegram.org/method/auth.importLoginToken deleted file mode 100644 index cc69f72695..0000000000 --- a/data/core.telegram.org/method/auth.importLoginToken +++ /dev/null @@ -1,187 +0,0 @@ - - - - - auth.importLoginToken - - - - - - - - - - - - - -
- -
-
-
- -

auth.importLoginToken

- -

Login using a redirected login token, generated in case of DC mismatch during QR code login.

-

For more info, see login via QR code.

-

- -
-
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
-auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;
-auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;
----functions---
-auth.importLoginToken#95ac5ce4 token:bytes = auth.LoginToken;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
tokenbytesLogin token
-

Result

-

auth.LoginToken

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400AUTH_TOKEN_ALREADY_ACCEPTEDThe specified auth token was already accepted.
400AUTH_TOKEN_EXPIREDThe authorization token has expired.
400AUTH_TOKEN_INVALIDThe specified auth token is invalid.
400AUTH_TOKEN_INVALIDXThe specified auth token is invalid.
-

Related pages

-

Login via QR code

-

QR code login flow

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/auth.recoverPassword b/data/core.telegram.org/method/auth.recoverPassword deleted file mode 100644 index d8d1fdfa78..0000000000 --- a/data/core.telegram.org/method/auth.recoverPassword +++ /dev/null @@ -1,187 +0,0 @@ - - - - - auth.recoverPassword - - - - - - - - - - - - - -
- -
-
-
- -

auth.recoverPassword

- -

Reset the 2FA password using the recovery code sent using auth.requestPasswordRecovery.

-

- -
-
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
-auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
----functions---
-auth.recoverPassword#37096c70 flags:# code:string new_settings:flags.0?account.PasswordInputSettings = auth.Authorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
codestringCode received via email
new_settingsflags.0?account.PasswordInputSettingsNew password
-

Result

-

auth.Authorization

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CODE_EMPTYThe provided code is empty.
400NEW_SETTINGS_INVALIDThe new settings are invalid.
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

-

auth.requestPasswordRecovery

-

Request recovery code of a 2FA password, only for accounts with a recovery email configured.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/auth.requestPasswordRecovery b/data/core.telegram.org/method/auth.requestPasswordRecovery deleted file mode 100644 index d7d23e9d16..0000000000 --- a/data/core.telegram.org/method/auth.requestPasswordRecovery +++ /dev/null @@ -1,159 +0,0 @@ - - - - - auth.requestPasswordRecovery - - - - - - - - - - - - - -
- -
-
-
- -

auth.requestPasswordRecovery

- -

Request recovery code of a 2FA password, only for accounts with a recovery email configured.

-

- -
-
auth.passwordRecovery#137948a5 email_pattern:string = auth.PasswordRecovery;
----functions---
-auth.requestPasswordRecovery#d897bc66 = auth.PasswordRecovery;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

auth.PasswordRecovery

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PASSWORD_EMPTYThe provided password is empty.
400PASSWORD_RECOVERY_NANo email was set, can't recover password via email.
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/auth.resendCode b/data/core.telegram.org/method/auth.resendCode deleted file mode 100644 index 852b07fb87..0000000000 --- a/data/core.telegram.org/method/auth.resendCode +++ /dev/null @@ -1,191 +0,0 @@ - - - - - auth.resendCode - - - - - - - - - - - - - -
- -
-
-
- -

auth.resendCode

- -

Resend the login code via another medium, the phone code type is determined by the return value of the previous auth.sendCode/auth.resendCode: see login for more info.

-

- -
-
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
----functions---
-auth.resendCode#3ef1a9bf phone_number:string phone_code_hash:string = auth.SentCode;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringThe phone number
phone_code_hashstringThe phone code hash obtained from auth.sendCode
-

Result

-

auth.SentCode

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PHONE_CODE_EXPIREDThe phone code you provided has expired, this may happen if it was sent to any chat on telegram (if the code is sent through a telegram chat (not the official account) to avoid it append or prepend to the code some chars).
400PHONE_CODE_HASH_EMPTYphone_code_hash is missing.
400PHONE_NUMBER_INVALIDThe phone number is invalid.
406SEND_CODE_UNAVAILABLEReturned when all available options for this type of number were already used (e.g. flash-call, then SMS, then this error might be returned to trigger a second resend).
-

Related pages

-

auth.sendCode

-

Send the verification code for login

-

User Authorization

-

How to register a user's phone to start using the API.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/auth.resetAuthorizations b/data/core.telegram.org/method/auth.resetAuthorizations deleted file mode 100644 index d09fa29b02..0000000000 --- a/data/core.telegram.org/method/auth.resetAuthorizations +++ /dev/null @@ -1,156 +0,0 @@ - - - - - auth.resetAuthorizations - - - - - - - - - - - - - -
- -
-
-
- -

auth.resetAuthorizations

- -

Terminates all user's authorized sessions except for the current one.

-

After calling this method it is necessary to reregister the current device using the method account.registerDevice

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-auth.resetAuthorizations#9fab0d1a = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
406FRESH_RESET_AUTHORISATION_FORBIDDENYou can't logout other sessions if less than 24 hours have passed since you logged on the current session.
-

Related pages

-

account.registerDevice

-

Register device to receive PUSH notifications

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/auth.sendCall b/data/core.telegram.org/method/auth.sendCall deleted file mode 100644 index 894cdd52e2..0000000000 --- a/data/core.telegram.org/method/auth.sendCall +++ /dev/null @@ -1,175 +0,0 @@ - - - - - auth.sendCall - - - - - - - - - - - - - -
- -
-
-
- -

auth.sendCall

- -

Makes a voice call to the passed phone number. A robot will repeat the confirmation code from a previously sent SMS message.

-

{schema}

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number in the international format
phone_code_hashstringSMS-message ID
-

Result

-

Bool

-

Query example

-
(auth.sendCall "79991234567" "2dc02d2cda9e615c84")
-=
-(boolTrue)
-
-03c51564 3939370b 33323139 37363534 63643212 32643230 39616463 35313665 00343863 64e1a61b
-=
-997275b5
-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PHONE_NUMBER_INVALIDInvalid phone number
400PHONE_CODE_HASH_EMPTYphone_code_hash was not sent
400PHONE_CODE_EXPIREDSMS expired
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/auth.sendCode b/data/core.telegram.org/method/auth.sendCode deleted file mode 100644 index 6a54617ae7..0000000000 --- a/data/core.telegram.org/method/auth.sendCode +++ /dev/null @@ -1,236 +0,0 @@ - - - - - auth.sendCode - - - - - - - - - - - - - -
- -
-
-
- -

auth.sendCode

- -

Send the verification code for login

-

- -
-
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
----functions---
-auth.sendCode#a677244f phone_number:string api_id:int api_hash:string settings:CodeSettings = auth.SentCode;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number in international format
api_idintApplication identifier (see App configuration)
api_hashstringApplication secret hash (see App configuration)
settingsCodeSettingsSettings for the code type to send
-

Result

-

The method returns an auth.SentCode object with information on the message sent.

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400API_ID_INVALIDAPI ID invalid.
400API_ID_PUBLISHED_FLOODThis API id was published somewhere, you can't use it now.
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
303NETWORK_MIGRATE_XRepeat the query to data-center X.
303PHONE_MIGRATE_XRepeat the query to data-center X.
400PHONE_NUMBER_APP_SIGNUP_FORBIDDENYou can't sign up using this app.
400PHONE_NUMBER_BANNEDThe provided phone number is banned from telegram.
400PHONE_NUMBER_FLOODYou asked for the code too many times.
400PHONE_NUMBER_INVALIDInvalid phone number.
406PHONE_PASSWORD_FLOODYou have tried logging in too many times.
400PHONE_PASSWORD_PROTECTEDThis phone is password protected.
400SMS_CODE_CREATE_FAILEDAn error occurred while creating the SMS code.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/auth.sendInvites b/data/core.telegram.org/method/auth.sendInvites deleted file mode 100644 index 36ea47ee07..0000000000 --- a/data/core.telegram.org/method/auth.sendInvites +++ /dev/null @@ -1,157 +0,0 @@ - - - - - auth.sendInvites - - - - - - - - - - - - - -
- -
-
-
- -

auth.sendInvites

- -

Saves information that the current user sent SMS-messages with invitations to its unregistered contacts.

-

{schema}

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numbersVector<string>List of phone numbers of message recipients in the international format
messagestringMessage text
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_EMPTYThe provided message is empty
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/auth.sendSms b/data/core.telegram.org/method/auth.sendSms deleted file mode 100644 index ac37879793..0000000000 --- a/data/core.telegram.org/method/auth.sendSms +++ /dev/null @@ -1,167 +0,0 @@ - - - - - auth.sendSms - - - - - - - - - - - - - -
- -
-
-
- -

auth.sendSms

- -

Forces sending an SMS message to the specified phone number. Use this method if auth.sentAppCode was returned as a response to auth.sendCode, but the user can't reach the device with Telegram.

-

{schema}

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number in international format
phone_code_hashstringSMS-message ID
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PHONE_NUMBER_INVALIDInvalid phone number
400PHONE_CODE_HASH_EMPTYphone_code_hash was not sent
400PHONE_CODE_EXPIREDSMS expired
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/auth.signIn b/data/core.telegram.org/method/auth.signIn deleted file mode 100644 index 1177c62e46..0000000000 --- a/data/core.telegram.org/method/auth.signIn +++ /dev/null @@ -1,219 +0,0 @@ - - - - - auth.signIn - - - - - - - - - - - - - -
- -
-
-
- -

auth.signIn

- -

Signs in a user with a validated phone number.

-

- -
-
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
-auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
----functions---
-auth.signIn#bcd51581 phone_number:string phone_code_hash:string phone_code:string = auth.Authorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number in the international format
phone_code_hashstringSMS-message ID, obtained from auth.sendCode
phone_codestringValid numerical code from the SMS-message
-

Result

-

Returns an auth.Authorization object with information on the new authorization.

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PHONE_CODE_EMPTYphone_code from the SMS is empty.
400PHONE_CODE_EXPIREDSMS expired.
400PHONE_CODE_INVALIDInvalid SMS code was sent.
400PHONE_NUMBER_INVALIDInvalid phone number.
400PHONE_NUMBER_UNOCCUPIEDThe code is valid but no user with the given number is registered.
-

Query example

-
(auth.signIn "79991234567" "2dc02d2cda9e615c84" "44444")
-=
-(auth.authorization
-  expires:1403938438
-  user:(userSelf
-    id:603177
-    first_name:"John"
-    last_name:"Doe"
-    phone:"79991234567"
-    photo:(userProfilePhotoEmpty)
-    status:(userStatusEmpty)
-    inactive:(boolTrue)
-  )
-)
-
-bcd51581 3939370b 33323139 37363534 63643212 32643230 39616463 35313665 00343863 34343405 00003434 45ca2b3b
-=
-f6b673a4 53ae6686 720535ec 00093429 686f4a04 0000006e 656f4403 3939370b 33323139 37363534 4f11bae1 09d05049 997275b5 d8487410
-

Related pages

-

auth.sendCode

-

Send the verification code for login

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/auth.signUp b/data/core.telegram.org/method/auth.signUp deleted file mode 100644 index 3eadfe342f..0000000000 --- a/data/core.telegram.org/method/auth.signUp +++ /dev/null @@ -1,236 +0,0 @@ - - - - - auth.signUp - - - - - - - - - - - - - -
- -
-
-
- -

auth.signUp

- -

Registers a validated phone number in the system.

-

- -
-
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
-auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
----functions---
-auth.signUp#80eee427 phone_number:string phone_code_hash:string first_name:string last_name:string = auth.Authorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number in the international format
phone_code_hashstringSMS-message ID
first_namestringNew user first name
last_namestringNew user last name
-

Result

-

Returns an auth.Authorization object with information about the new authorization.

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400FIRSTNAME_INVALIDInvalid first name.
400LASTNAME_INVALIDInvalid last name.
400PHONE_CODE_EMPTYphone_code from a SMS is empty.
400PHONE_CODE_EXPIREDSMS expired.
400PHONE_CODE_INVALIDInvalid SMS code was sent.
400PHONE_NUMBER_FLOODYou asked for the code too many times.
400PHONE_NUMBER_INVALIDInvalid phone number.
400PHONE_NUMBER_OCCUPIEDThe phone number is already in use.
-

Query example

-
(auth.signUp "79991234567" "2dc02d2cda9e615c84" "44444" "John" "Doe")
-=
-(auth.authorization
-  expires:1403938438
-  user:(userSelf
-    id:603177
-    first_name:"John"
-    last_name:"Doe"
-    phone:"79991234567"
-    photo:(userProfilePhotoEmpty)
-    status:(userStatusEmpty)
-    inactive:(boolTrue)
-  )
-)
-
-1b067634 3939370b 33323139 37363534 63643212 32643230 39616463 35313665 00343863 34343405 00003434 686f4a04 0000006e 656f4403 c18027ca
-=
-f6b673a4 53ae6686 720535ec 00093429 686f4a04 0000006e 656f4403 3939370b 33323139 37363534 4f11bae1 09d05049 997275b5 d8487410
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/bots.answerWebhookJSONQuery b/data/core.telegram.org/method/bots.answerWebhookJSONQuery deleted file mode 100644 index 5873dc7be8..0000000000 --- a/data/core.telegram.org/method/bots.answerWebhookJSONQuery +++ /dev/null @@ -1,178 +0,0 @@ - - - - - bots.answerWebhookJSONQuery - - - - - - - - - - - - - -
- -
-
-
- -

bots.answerWebhookJSONQuery

- -

Answers a custom query; for bots only

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-bots.answerWebhookJSONQuery#e6213f4d query_id:long data:DataJSON = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
query_idlongIdentifier of a custom query
dataDataJSONJSON-serialized answer to the query
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400QUERY_ID_INVALIDThe query ID is invalid.
400USER_BOT_INVALIDThis method can only be called by a bot.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/bots.getBotCommands b/data/core.telegram.org/method/bots.getBotCommands deleted file mode 100644 index 0a19b0ad91..0000000000 --- a/data/core.telegram.org/method/bots.getBotCommands +++ /dev/null @@ -1,154 +0,0 @@ - - - - - bots.getBotCommands - - - - - - - - - - - - - -
- -
-
-
- -

bots.getBotCommands

- -

Obtain a list of bot commands for the specified bot scope and language code

-

- -
-
---functions---
-bots.getBotCommands#e34c0dd6 scope:BotCommandScope lang_code:string = Vector<BotCommand>;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
scopeBotCommandScopeCommand scope
lang_codestringLanguage code
-

Result

-

Vector<BotCommand>

-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/bots.resetBotCommands b/data/core.telegram.org/method/bots.resetBotCommands deleted file mode 100644 index 19bc8f9ecf..0000000000 --- a/data/core.telegram.org/method/bots.resetBotCommands +++ /dev/null @@ -1,156 +0,0 @@ - - - - - bots.resetBotCommands - - - - - - - - - - - - - -
- -
-
-
- -

bots.resetBotCommands

- -

Clear bot commands for the specified bot scope and language code

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-bots.resetBotCommands#3d8de0f9 scope:BotCommandScope lang_code:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
scopeBotCommandScopeCommand scope
lang_codestringLanguage code
-

Result

-

Bool

-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/bots.sendCustomRequest b/data/core.telegram.org/method/bots.sendCustomRequest deleted file mode 100644 index 656689fed9..0000000000 --- a/data/core.telegram.org/method/bots.sendCustomRequest +++ /dev/null @@ -1,177 +0,0 @@ - - - - - bots.sendCustomRequest - - - - - - - - - - - - - -
- -
-
-
- -

bots.sendCustomRequest

- -

Sends a custom request; for bots only

-

- -
-
dataJSON#7d748d04 data:string = DataJSON;
----functions---
-bots.sendCustomRequest#aa2769ed custom_method:string params:DataJSON = DataJSON;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
custom_methodstringThe method name
paramsDataJSONJSON-serialized method parameters
-

Result

-

DataJSON

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400METHOD_INVALIDThe specified method is invalid.
400USER_BOT_INVALIDThis method can only be called by a bot.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/bots.setBotCommands b/data/core.telegram.org/method/bots.setBotCommands deleted file mode 100644 index d346a75b97..0000000000 --- a/data/core.telegram.org/method/bots.setBotCommands +++ /dev/null @@ -1,188 +0,0 @@ - - - - - bots.setBotCommands - - - - - - - - - - - - - -
- -
-
-
- -

bots.setBotCommands

- -

Set bot command list

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-bots.setBotCommands#517165a scope:BotCommandScope lang_code:string commands:Vector<BotCommand> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
scopeBotCommandScopeCommand scope
lang_codestringLanguage code
commandsVector<BotCommand>Bot commands
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOT_COMMAND_DESCRIPTION_INVALIDThe specified command description is invalid.
400BOT_COMMAND_INVALIDThe specified command is invalid.
400LANG_CODE_INVALIDThe specified language code is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.checkUsername b/data/core.telegram.org/method/channels.checkUsername deleted file mode 100644 index 2a39082600..0000000000 --- a/data/core.telegram.org/method/channels.checkUsername +++ /dev/null @@ -1,190 +0,0 @@ - - - - - channels.checkUsername - - - - - - - - - - - - - -
- -
-
-
- -

channels.checkUsername

- -

Check if a username is free and can be assigned to a channel/supergroup

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-channels.checkUsername#10e6bd2c channel:InputChannel username:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelThe channel/supergroup that will assigned the specified username
usernamestringThe username to check
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNELS_ADMIN_PUBLIC_TOO_MUCHYou're admin of too many public channels, make some channels private to change the username of this channel.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400USERNAME_INVALIDThe provided username is not valid.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.convertToGigagroup b/data/core.telegram.org/method/channels.convertToGigagroup deleted file mode 100644 index 36f33f87a3..0000000000 --- a/data/core.telegram.org/method/channels.convertToGigagroup +++ /dev/null @@ -1,177 +0,0 @@ - - - - - channels.convertToGigagroup - - - - - - - - - - - - - -
- -
-
-
- -

channels.convertToGigagroup

- -

Convert a supergroup to a gigagroup, when requested by channel suggestions.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.convertToGigagroup#b290c69 channel:InputChannel = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelThe supergroup to convert
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PARTICIPANTS_TOO_FEWNot enough participants.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

Client configuration

-

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.createChannel b/data/core.telegram.org/method/channels.createChannel deleted file mode 100644 index 99c8798677..0000000000 --- a/data/core.telegram.org/method/channels.createChannel +++ /dev/null @@ -1,232 +0,0 @@ - - - - - channels.createChannel - - - - - - - - - - - - - -
- -
-
-
- -

channels.createChannel

- -

Create a supergroup/channel.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.createChannel#3d5fb10f flags:# broadcast:flags.0?true megagroup:flags.1?true for_import:flags.3?true title:string about:string geo_point:flags.2?InputGeoPoint address:flags.2?string = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
broadcastflags.0?trueWhether to create a channel
megagroupflags.1?trueWhether to create a supergroup
for_importflags.3?trueWhether the supergroup is being created to import messages from a foreign chat service using messages.initHistoryImport
titlestringChannel title
aboutstringChannel description
geo_pointflags.2?InputGeoPointGeogroup location
addressflags.2?stringGeogroup address
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNELS_ADMIN_LOCATED_TOO_MUCHThe user has reached the limit of public geogroups.
400CHANNELS_TOO_MUCHYou have joined too many channels/supergroups.
400CHAT_ABOUT_TOO_LONGChat about too long.
400CHAT_TITLE_EMPTYNo chat title provided.
403USER_RESTRICTEDYou're spamreported, you can't create channels or chats.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

messages.initHistoryImport

-

Import chat history from a foreign chat app into a specific Telegram chat, click here for more info about imported chats ».

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.deleteChannel b/data/core.telegram.org/method/channels.deleteChannel deleted file mode 100644 index ede33d8017..0000000000 --- a/data/core.telegram.org/method/channels.deleteChannel +++ /dev/null @@ -1,200 +0,0 @@ - - - - - channels.deleteChannel - - - - - - - - - - - - - -
- -
-
-
- -

channels.deleteChannel

- -

Delete a channel/supergroup

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.deleteChannel#c0111fe3 channel:InputChannel = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel/supergroup to delete
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHANNEL_TOO_LARGEChannel is too large to be deleted; this error is issued when trying to delete channels with more than 1000 members (subject to change).
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.deleteHistory b/data/core.telegram.org/method/channels.deleteHistory deleted file mode 100644 index 370317535f..0000000000 --- a/data/core.telegram.org/method/channels.deleteHistory +++ /dev/null @@ -1,180 +0,0 @@ - - - - - channels.deleteHistory - - - - - - - - - - - - - -
- -
-
-
- -

channels.deleteHistory

- -

Delete the history of a supergroup

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-channels.deleteHistory#af369d42 channel:InputChannel max_id:int = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelSupergroup whose history must be deleted
max_idintID of message up to which the history must be deleted
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.editAdmin b/data/core.telegram.org/method/channels.editAdmin deleted file mode 100644 index 590ba0aff6..0000000000 --- a/data/core.telegram.org/method/channels.editAdmin +++ /dev/null @@ -1,301 +0,0 @@ - - - - - channels.editAdmin - - - - - - - - - - - - - -
- -
-
-
- -

channels.editAdmin

- -

Modify the admin rights of a user in a supergroup/channel.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.editAdmin#d33c8902 channel:InputChannel user_id:InputUser admin_rights:ChatAdminRights rank:string = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelThe supergroup/channel.
user_idInputUserThe ID of the user whose admin rights should be modified
admin_rightsChatAdminRightsThe admin rights
rankstringIndicates the role (rank) of the admin in the group: just an arbitrary string
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400ADMINS_TOO_MUCHThere are too many admins.
400ADMIN_RANK_EMOJI_NOT_ALLOWEDAn admin rank cannot contain emojis.
400ADMIN_RANK_INVALIDThe specified admin rank is invalid.
400BOTS_TOO_MUCHThere are too many bots in this chat/channel.
400BOT_CHANNELS_NABots can't edit admin privileges.
400BOT_GROUPS_BLOCKEDThis bot can't be added to groups.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
403CHAT_ADMIN_INVITE_REQUIREDYou do not have the rights to do this.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
406FRESH_CHANGE_ADMINS_FORBIDDENYou were just elected admin, you can't add or modify other admins yet.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400PEER_ID_INVALIDThe provided peer id is invalid.
403RIGHT_FORBIDDENYour admin rights do not allow you to do this.
400USERS_TOO_MUCHThe maximum number of users has been exceeded (to create a chat, for example).
400USER_BLOCKEDUser blocked.
403USER_CHANNELS_TOO_MUCHOne of the users you tried to add is already in too many channels/supergroups.
400USER_CREATORYou can't leave this channel, because you're its creator.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_NOT_MUTUAL_CONTACTThe provided user is not a mutual contact.
403USER_PRIVACY_RESTRICTEDThe user's privacy settings do not allow you to do this.
403USER_RESTRICTEDYou're spamreported, you can't create channels or chats.
-

Bots can use this method

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.editBanned b/data/core.telegram.org/method/channels.editBanned deleted file mode 100644 index 251020cb2e..0000000000 --- a/data/core.telegram.org/method/channels.editBanned +++ /dev/null @@ -1,241 +0,0 @@ - - - - - channels.editBanned - - - - - - - - - - - - - -
- -
-
-
- -

channels.editBanned

- -

Ban/unban/kick a user in a supergroup/channel.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.editBanned#96e6cd81 channel:InputChannel participant:InputPeer banned_rights:ChatBannedRights = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelThe supergroup/channel.
participantInputPeerParticipant to ban
banned_rightsChatBannedRightsThe banned rights
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_ADD_INVALIDInternal error.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400PARTICIPANT_ID_INVALIDThe specified participant ID is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PINNED_DIALOGS_TOO_MUCHToo many pinned dialogs.
400USER_ADMIN_INVALIDYou're not an admin.
400USER_ID_INVALIDThe provided user ID is invalid.
-

Bots can use this method

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.editLocation b/data/core.telegram.org/method/channels.editLocation deleted file mode 100644 index d0eda63cf8..0000000000 --- a/data/core.telegram.org/method/channels.editLocation +++ /dev/null @@ -1,180 +0,0 @@ - - - - - channels.editLocation - - - - - - - - - - - - - -
- -
-
-
- -

channels.editLocation

- -

Edit location of geogroup

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-channels.editLocation#58e63f6d channel:InputChannel geo_point:InputGeoPoint address:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelGeogroup
geo_pointInputGeoPointNew geolocation
addressstringAddress string
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400MEGAGROUP_REQUIREDYou can only use this method on a supergroup.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.editPhoto b/data/core.telegram.org/method/channels.editPhoto deleted file mode 100644 index 1db5822bae..0000000000 --- a/data/core.telegram.org/method/channels.editPhoto +++ /dev/null @@ -1,221 +0,0 @@ - - - - - channels.editPhoto - - - - - - - - - - - - - -
- -
-
-
- -

channels.editPhoto

- -

Change the photo of a channel/supergroup

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.editPhoto#f12e57c9 channel:InputChannel photo:InputChatPhoto = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel/supergroup whose photo should be edited
photoInputChatPhotoNew photo
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400FILE_REFERENCE_INVALIDThe specified file reference is invalid.
400PHOTO_CROP_SIZE_SMALLPhoto is too small.
400PHOTO_EXT_INVALIDThe extension of the photo is invalid.
400PHOTO_INVALIDPhoto invalid.
-

Bots can use this method

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.editTitle b/data/core.telegram.org/method/channels.editTitle deleted file mode 100644 index 271627a770..0000000000 --- a/data/core.telegram.org/method/channels.editTitle +++ /dev/null @@ -1,206 +0,0 @@ - - - - - channels.editTitle - - - - - - - - - - - - - -
- -
-
-
- -

channels.editTitle

- -

Edit the name of a channel/supergroup

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.editTitle#566decd0 channel:InputChannel title:string = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel/supergroup
titlestringNew name
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400CHAT_TITLE_EMPTYNo chat title provided.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
-

Bots can use this method

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.exportMessageLink b/data/core.telegram.org/method/channels.exportMessageLink deleted file mode 100644 index 3907f2c777..0000000000 --- a/data/core.telegram.org/method/channels.exportMessageLink +++ /dev/null @@ -1,204 +0,0 @@ - - - - - channels.exportMessageLink - - - - - - - - - - - - - -
- -
-
-
- -

channels.exportMessageLink

- -

Get link and embed info of a message in a channel/supergroup

-

- -
-
exportedMessageLink#5dab1af4 link:string html:string = ExportedMessageLink;
----functions---
-channels.exportMessageLink#e63fadeb flags:# grouped:flags.0?true thread:flags.1?true channel:InputChannel id:int = ExportedMessageLink;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
groupedflags.0?trueWhether to include other grouped media (for albums)
threadflags.1?trueWhether to also include a thread ID, if available, inside of the link
channelInputChannelChannel
idintMessage ID
-

Result

-

ExportedMessageLink

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.getAdminLog b/data/core.telegram.org/method/channels.getAdminLog deleted file mode 100644 index 59c02d2c89..0000000000 --- a/data/core.telegram.org/method/channels.getAdminLog +++ /dev/null @@ -1,226 +0,0 @@ - - - - - channels.getAdminLog - - - - - - - - - - - - - -
- -
-
-
- -

channels.getAdminLog

- -

Get the admin log of a channel/supergroup

-

- -
-
channels.adminLogResults#ed8af74d events:Vector<ChannelAdminLogEvent> chats:Vector<Chat> users:Vector<User> = channels.AdminLogResults;
----functions---
-channels.getAdminLog#33ddf480 flags:# channel:InputChannel q:string events_filter:flags.0?ChannelAdminLogEventsFilter admins:flags.1?Vector<InputUser> max_id:long min_id:long limit:int = channels.AdminLogResults;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
channelInputChannelChannel
qstringSearch query, can be empty
events_filterflags.0?ChannelAdminLogEventsFilterEvent filter
adminsflags.1?Vector<InputUser>Only show events from these admins
max_idlongMaximum ID of message to return (see pagination)
min_idlongMinimum ID of message to return (see pagination)
limitintMaximum number of results to return, see pagination
-

Result

-

channels.AdminLogResults

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400MSG_ID_INVALIDInvalid message ID provided.
-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.getAdminedPublicChannels b/data/core.telegram.org/method/channels.getAdminedPublicChannels deleted file mode 100644 index c94d428392..0000000000 --- a/data/core.telegram.org/method/channels.getAdminedPublicChannels +++ /dev/null @@ -1,191 +0,0 @@ - - - - - channels.getAdminedPublicChannels - - - - - - - - - - - - - -
- -
-
-
- -

channels.getAdminedPublicChannels

- -

Get channels/supergroups/geogroups we're admin in. Usually called when the user exceeds the limit for owned public channels/supergroups/geogroups, and the user is given the choice to remove one of his channels/supergroups/geogroups.

-

- -
-
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
-messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
----functions---
-channels.getAdminedPublicChannels#f8b036af flags:# by_location:flags.0?true check_limit:flags.1?true = messages.Chats;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
by_locationflags.0?trueGet geogroups
check_limitflags.1?trueIf set and the user has reached the limit of owned public channels/supergroups/geogroups, instead of returning the channel list one of the specified errors will be returned.
Useful to check if a new public channel can indeed be created, even before asking the user to enter a channel username to use in channels.checkUsername/channels.updateUsername.
-

Result

-

messages.Chats

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNELS_ADMIN_LOCATED_TOO_MUCHReturned if both the check_limit and the by_location flags are set and the user has reached the limit of public geogroups.
400CHANNELS_ADMIN_PUBLIC_TOO_MUCHReturned if the check_limit flag is set and the user has reached the limit of public channels/supergroups.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

channels.checkUsername

-

Check if a username is free and can be assigned to a channel/supergroup

-

channels.updateUsername

-

Change the username of a supergroup/channel

-

config

-

Current configuration

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.getChannels b/data/core.telegram.org/method/channels.getChannels deleted file mode 100644 index 0cb0b547ad..0000000000 --- a/data/core.telegram.org/method/channels.getChannels +++ /dev/null @@ -1,181 +0,0 @@ - - - - - channels.getChannels - - - - - - - - - - - - - -
- -
-
-
- -

channels.getChannels

- -

Get info about channels/supergroups

-

- -
-
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
-messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
----functions---
-channels.getChannels#a7f6bbb id:Vector<InputChannel> = messages.Chats;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idVector<InputChannel>IDs of channels/supergroups to get info about
-

Result

-

messages.Chats

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
-

Bots can use this method

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.getGroupsForDiscussion b/data/core.telegram.org/method/channels.getGroupsForDiscussion deleted file mode 100644 index 6b6534045b..0000000000 --- a/data/core.telegram.org/method/channels.getGroupsForDiscussion +++ /dev/null @@ -1,144 +0,0 @@ - - - - - channels.getGroupsForDiscussion - - - - - - - - - - - - - -
- -
-
-
- -

channels.getGroupsForDiscussion

- -

Get all groups that can be used as discussion groups.

-

Returned legacy group chats must be first upgraded to supergroups before they can be set as a discussion group.
-To set a returned supergroup as a discussion group, access to its old messages must be enabled using channels.togglePreHistoryHidden, first.

-

- -
-
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
-messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
----functions---
-channels.getGroupsForDiscussion#f5dad378 = messages.Chats;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

messages.Chats

-

Related pages

-

Discussion groups

-

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

channels.togglePreHistoryHidden

-

Hide/unhide message history for new channel/supergroup users

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.getInactiveChannels b/data/core.telegram.org/method/channels.getInactiveChannels deleted file mode 100644 index d600060a77..0000000000 --- a/data/core.telegram.org/method/channels.getInactiveChannels +++ /dev/null @@ -1,134 +0,0 @@ - - - - - channels.getInactiveChannels - - - - - - - - - - - - - -
- -
-
-
- -

channels.getInactiveChannels

- -

Get inactive channels and supergroups

-

- -
-
messages.inactiveChats#a927fec5 dates:Vector<int> chats:Vector<Chat> users:Vector<User> = messages.InactiveChats;
----functions---
-channels.getInactiveChannels#11e831ee = messages.InactiveChats;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

messages.InactiveChats

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.getLeftChannels b/data/core.telegram.org/method/channels.getLeftChannels deleted file mode 100644 index 42d9b61911..0000000000 --- a/data/core.telegram.org/method/channels.getLeftChannels +++ /dev/null @@ -1,172 +0,0 @@ - - - - - channels.getLeftChannels - - - - - - - - - - - - - -
- -
-
-
- -

channels.getLeftChannels

- -

Get a list of channels/supergroups we left

-

- -
-
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
-messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
----functions---
-channels.getLeftChannels#8341ecc0 offset:int = messages.Chats;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset for pagination
-

Result

-

messages.Chats

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
403TAKEOUT_REQUIREDA takeout session has to be initialized, first.
-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.getMessages b/data/core.telegram.org/method/channels.getMessages deleted file mode 100644 index 74c1e497d2..0000000000 --- a/data/core.telegram.org/method/channels.getMessages +++ /dev/null @@ -1,193 +0,0 @@ - - - - - channels.getMessages - - - - - - - - - - - - - -
- -
-
-
- -

channels.getMessages

- -

Get channel/supergroup messages

-

- -
-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
----functions---
-channels.getMessages#ad8c9a23 channel:InputChannel id:Vector<InputMessage> = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel/supergroup
idVector<InputMessage>IDs of messages to get
-

Result

-

messages.Messages

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MESSAGE_IDS_EMPTYNo message ids were provided.
400MSG_ID_INVALIDInvalid message ID provided.
-

Bots can use this method

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.getParticipant b/data/core.telegram.org/method/channels.getParticipant deleted file mode 100644 index 979a90ca5a..0000000000 --- a/data/core.telegram.org/method/channels.getParticipant +++ /dev/null @@ -1,205 +0,0 @@ - - - - - channels.getParticipant - - - - - - - - - - - - - -
- -
-
-
- -

channels.getParticipant

- -

Get info about a channel/supergroup participant

-

- -
-
channels.channelParticipant#dfb80317 participant:ChannelParticipant chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipant;
----functions---
-channels.getParticipant#a0ab6cc6 channel:InputChannel participant:InputPeer = channels.ChannelParticipant;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel/supergroup
participantInputPeerParticipant to get info about
-

Result

-

channels.ChannelParticipant

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400MSG_ID_INVALIDInvalid message ID provided.
400PARTICIPANT_ID_INVALIDThe specified participant ID is invalid.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_NOT_PARTICIPANTYou're not a member of this supergroup/channel.
-

Bots can use this method

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.getParticipants b/data/core.telegram.org/method/channels.getParticipants deleted file mode 100644 index b766c94a55..0000000000 --- a/data/core.telegram.org/method/channels.getParticipants +++ /dev/null @@ -1,203 +0,0 @@ - - - - - channels.getParticipants - - - - - - - - - - - - - -
- -
-
-
- -

channels.getParticipants

- -

Get the participants of a supergroup/channel

-

- -
-
channels.channelParticipants#9ab0feaf count:int participants:Vector<ChannelParticipant> chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipants;
-channels.channelParticipantsNotModified#f0173fe9 = channels.ChannelParticipants;
----functions---
-channels.getParticipants#77ced9d0 channel:InputChannel filter:ChannelParticipantsFilter offset:int limit:int hash:long = channels.ChannelParticipants;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel
filterChannelParticipantsFilterWhich participant types to fetch
offsetintOffset
limitintLimit
hashlongHash
-

Result

-

channels.ChannelParticipants

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
-

Bots can use this method

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.getSponsoredMessages b/data/core.telegram.org/method/channels.getSponsoredMessages deleted file mode 100644 index ddb1b37570..0000000000 --- a/data/core.telegram.org/method/channels.getSponsoredMessages +++ /dev/null @@ -1,154 +0,0 @@ - - - - - channels.getSponsoredMessages - - - - - - - - - - - - - -
- -
-
-
- -

channels.getSponsoredMessages

- -

Get a list of sponsored messages

-

- -
-
messages.sponsoredMessages#65a4c7d5 messages:Vector<SponsoredMessage> chats:Vector<Chat> users:Vector<User> = messages.SponsoredMessages;
----functions---
-channels.getSponsoredMessages#ec210fbf channel:InputChannel = messages.SponsoredMessages;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelPeer
-

Result

-

messages.SponsoredMessages

-
-

Related pages

-

Sponsored messages

-

How to implement sponsored messages

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.inviteToChannel b/data/core.telegram.org/method/channels.inviteToChannel deleted file mode 100644 index fa94c15e1c..0000000000 --- a/data/core.telegram.org/method/channels.inviteToChannel +++ /dev/null @@ -1,262 +0,0 @@ - - - - - channels.inviteToChannel - - - - - - - - - - - - - -
- -
-
-
- -

channels.inviteToChannel

- -

Invite users to a channel/supergroup

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.inviteToChannel#199f3a6c channel:InputChannel users:Vector<InputUser> = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel/supergroup
usersVector<InputUser>Users to invite
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOTS_TOO_MUCHThere are too many bots in this chat/channel.
400BOT_GROUPS_BLOCKEDThis bot can't be added to groups.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_INVALIDInvalid chat.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400USERS_TOO_MUCHThe maximum number of users has been exceeded (to create a chat, for example).
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400USER_BLOCKEDUser blocked.
400USER_BOTBots can only be admins in channels.
403USER_CHANNELS_TOO_MUCHOne of the users you tried to add is already in too many channels/supergroups.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_KICKEDThis user was kicked from this supergroup/channel.
400USER_NOT_MUTUAL_CONTACTThe provided user is not a mutual contact.
403USER_PRIVACY_RESTRICTEDThe user's privacy settings do not allow you to do this.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.joinChannel b/data/core.telegram.org/method/channels.joinChannel deleted file mode 100644 index 57b6eba6b8..0000000000 --- a/data/core.telegram.org/method/channels.joinChannel +++ /dev/null @@ -1,227 +0,0 @@ - - - - - channels.joinChannel - - - - - - - - - - - - - -
- -
-
-
- -

channels.joinChannel

- -

Join a channel/supergroup

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.joinChannel#24b524c5 channel:InputChannel = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel/supergroup to join
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNELS_TOO_MUCHYou have joined too many channels/supergroups.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_INVALIDInvalid chat.
400INVITE_HASH_EMPTYThe invite hash is empty.
400INVITE_HASH_EXPIREDThe invite link has expired.
400INVITE_HASH_INVALIDThe invite hash is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USERS_TOO_MUCHThe maximum number of users has been exceeded (to create a chat, for example).
400USER_ALREADY_PARTICIPANTThe user is already in the group.
400USER_CHANNELS_TOO_MUCHOne of the users you tried to add is already in too many channels/supergroups.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.leaveChannel b/data/core.telegram.org/method/channels.leaveChannel deleted file mode 100644 index ab0ac43e4f..0000000000 --- a/data/core.telegram.org/method/channels.leaveChannel +++ /dev/null @@ -1,201 +0,0 @@ - - - - - channels.leaveChannel - - - - - - - - - - - - - -
- -
-
-
- -

channels.leaveChannel

- -

Leave a channel/supergroup

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.leaveChannel#f836aa95 channel:InputChannel = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel/supergroup to leave
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
403CHANNEL_PUBLIC_GROUP_NAchannel/supergroup not available.
400MSG_ID_INVALIDInvalid message ID provided.
400USER_CREATORYou can't leave this channel, because you're its creator.
400USER_NOT_PARTICIPANTYou're not a member of this supergroup/channel.
-

Bots can use this method

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.readMessageContents b/data/core.telegram.org/method/channels.readMessageContents deleted file mode 100644 index 64281416ce..0000000000 --- a/data/core.telegram.org/method/channels.readMessageContents +++ /dev/null @@ -1,185 +0,0 @@ - - - - - channels.readMessageContents - - - - - - - - - - - - - -
- -
-
-
- -

channels.readMessageContents

- -

Mark channel/supergroup message contents as read

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-channels.readMessageContents#eab5dc38 channel:InputChannel id:Vector<int> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel/supergroup
idVector<int>IDs of messages whose contents should be marked as read
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.reportSpam b/data/core.telegram.org/method/channels.reportSpam deleted file mode 100644 index a2d1633f28..0000000000 --- a/data/core.telegram.org/method/channels.reportSpam +++ /dev/null @@ -1,192 +0,0 @@ - - - - - channels.reportSpam - - - - - - - - - - - - - -
- -
-
-
- -

channels.reportSpam

- -

Reports some messages from a user in a supergroup as spam; requires administrator rights in the supergroup

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-channels.reportSpam#fe087810 channel:InputChannel user_id:InputUser id:Vector<int> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelSupergroup
user_idInputUserID of the user that sent the spam messages
idVector<int>IDs of spam messages
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400USER_ID_INVALIDThe provided user ID is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.setDiscussionGroup b/data/core.telegram.org/method/channels.setDiscussionGroup deleted file mode 100644 index edb1b119dd..0000000000 --- a/data/core.telegram.org/method/channels.setDiscussionGroup +++ /dev/null @@ -1,200 +0,0 @@ - - - - - channels.setDiscussionGroup - - - - - - - - - - - - - -
- -
-
-
- -

channels.setDiscussionGroup

- -

Associate a group to a channel as discussion group for that channel

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-channels.setDiscussionGroup#40582bb2 broadcast:InputChannel group:InputChannel = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
broadcastInputChannelChannel
groupInputChannelDiscussion group to associate to the channel
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BROADCAST_ID_INVALIDBroadcast ID invalid.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400LINK_NOT_MODIFIEDDiscussion link not modified.
400MEGAGROUP_ID_INVALIDInvalid supergroup ID.
400MEGAGROUP_PREHISTORY_HIDDENGroup with hidden history for new members can't be set as discussion groups.
-

Related pages

-

Discussion groups

-

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.setStickers b/data/core.telegram.org/method/channels.setStickers deleted file mode 100644 index 23ed15033d..0000000000 --- a/data/core.telegram.org/method/channels.setStickers +++ /dev/null @@ -1,183 +0,0 @@ - - - - - channels.setStickers - - - - - - - - - - - - - -
- -
-
-
- -

channels.setStickers

- -

Associate a stickerset to the supergroup

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-channels.setStickers#ea8ca4f9 channel:InputChannel stickerset:InputStickerSet = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelSupergroup
stickersetInputStickerSetThe stickerset to associate
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400PARTICIPANTS_TOO_FEWNot enough participants.
406STICKERSET_OWNER_ANONYMOUSProvided stickerset can't be installed as group stickerset to prevent admin deanonymisation.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.togglePreHistoryHidden b/data/core.telegram.org/method/channels.togglePreHistoryHidden deleted file mode 100644 index 44a1f39a01..0000000000 --- a/data/core.telegram.org/method/channels.togglePreHistoryHidden +++ /dev/null @@ -1,202 +0,0 @@ - - - - - channels.togglePreHistoryHidden - - - - - - - - - - - - - -
- -
-
-
- -

channels.togglePreHistoryHidden

- -

Hide/unhide message history for new channel/supergroup users

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.togglePreHistoryHidden#eabbb94c channel:InputChannel enabled:Bool = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel/supergroup
enabledBoolHide/unhide
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_LINK_EXISTSThe chat is public, you can't hide the history to new users.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.toggleSignatures b/data/core.telegram.org/method/channels.toggleSignatures deleted file mode 100644 index 0c453ffa44..0000000000 --- a/data/core.telegram.org/method/channels.toggleSignatures +++ /dev/null @@ -1,187 +0,0 @@ - - - - - channels.toggleSignatures - - - - - - - - - - - - - -
- -
-
-
- -

channels.toggleSignatures

- -

Enable/disable message signatures in channels

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.toggleSignatures#1f69b606 channel:InputChannel enabled:Bool = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel
enabledBoolValue
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.toggleSlowMode b/data/core.telegram.org/method/channels.toggleSlowMode deleted file mode 100644 index d95ec4e4a2..0000000000 --- a/data/core.telegram.org/method/channels.toggleSlowMode +++ /dev/null @@ -1,190 +0,0 @@ - - - - - channels.toggleSlowMode - - - - - - - - - - - - - -
- -
-
-
- -

channels.toggleSlowMode

- -

Toggle supergroup slow mode: if enabled, users will only be able to send one message every seconds seconds

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.toggleSlowMode#edd49ef0 channel:InputChannel seconds:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelThe supergroup
secondsintUsers will only be able to send one message every seconds seconds, 0 to disable the limitation
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400SECONDS_INVALIDInvalid duration provided.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/channels.updateUsername b/data/core.telegram.org/method/channels.updateUsername deleted file mode 100644 index 8a65dcc129..0000000000 --- a/data/core.telegram.org/method/channels.updateUsername +++ /dev/null @@ -1,212 +0,0 @@ - - - - - channels.updateUsername - - - - - - - - - - - - - -
- -
-
-
- -

channels.updateUsername

- -

Change the username of a supergroup/channel

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-channels.updateUsername#3514b3de channel:InputChannel username:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel
usernamestringNew username
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNELS_ADMIN_PUBLIC_TOO_MUCHYou're admin of too many public channels, make some channels private to change the username of this channel.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400USERNAME_INVALIDThe provided username is not valid.
400USERNAME_NOT_MODIFIEDThe username was not modified.
400USERNAME_OCCUPIEDThe provided username is already occupied.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/contacts.acceptContact b/data/core.telegram.org/method/contacts.acceptContact deleted file mode 100644 index 77bb6fcbd9..0000000000 --- a/data/core.telegram.org/method/contacts.acceptContact +++ /dev/null @@ -1,190 +0,0 @@ - - - - - contacts.acceptContact - - - - - - - - - - - - - -
- -
-
-
- -

contacts.acceptContact

- -

If the peer settings of a new user allow us to add him as contact, add that user as contact

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-contacts.acceptContact#f831a20f id:InputUser = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idInputUserThe user to add as contact
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CONTACT_ADD_MISSINGContact to add is missing.
400CONTACT_ID_INVALIDThe provided contact ID is invalid.
400CONTACT_REQ_MISSINGMissing contact request.
400MSG_ID_INVALIDInvalid message ID provided.
-

Related pages

-

peerSettings

-

Peer settings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/contacts.block b/data/core.telegram.org/method/contacts.block deleted file mode 100644 index e64d02ebaa..0000000000 --- a/data/core.telegram.org/method/contacts.block +++ /dev/null @@ -1,182 +0,0 @@ - - - - - contacts.block - - - - - - - - - - - - - -
- -
-
-
- -

contacts.block

- -

Adds the user to the blacklist.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-contacts.block#68cc1411 id:InputPeer = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idInputPeerUser ID
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CONTACT_ID_INVALIDThe provided contact ID is invalid.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/contacts.blockFromReplies b/data/core.telegram.org/method/contacts.blockFromReplies deleted file mode 100644 index bdc3625380..0000000000 --- a/data/core.telegram.org/method/contacts.blockFromReplies +++ /dev/null @@ -1,178 +0,0 @@ - - - - - contacts.blockFromReplies - - - - - - - - - - - - - -
- -
-
-
- -

contacts.blockFromReplies

- -

Stop getting notifications about thread replies of a certain user in @replies

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-contacts.blockFromReplies#29a8962c flags:# delete_message:flags.0?true delete_history:flags.1?true report_spam:flags.2?true msg_id:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
delete_messageflags.0?trueWhether to delete the specified message as well
delete_historyflags.1?trueWhether to delete all @replies messages from this user as well
report_spamflags.2?trueWhether to also report this user for spam
msg_idintID of the message in the @replies chat
-

Result

-

Updates

-

Related pages

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/contacts.deleteByPhones b/data/core.telegram.org/method/contacts.deleteByPhones deleted file mode 100644 index fdd9a3949f..0000000000 --- a/data/core.telegram.org/method/contacts.deleteByPhones +++ /dev/null @@ -1,150 +0,0 @@ - - - - - contacts.deleteByPhones - - - - - - - - - - - - - -
- -
-
-
- -

contacts.deleteByPhones

- -

Delete contacts by phone number

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-contacts.deleteByPhones#1013fd9e phones:Vector<string> = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
phonesVector<string>Phone numbers
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/contacts.deleteContacts b/data/core.telegram.org/method/contacts.deleteContacts deleted file mode 100644 index 34a358f690..0000000000 --- a/data/core.telegram.org/method/contacts.deleteContacts +++ /dev/null @@ -1,155 +0,0 @@ - - - - - contacts.deleteContacts - - - - - - - - - - - - - -
- -
-
-
- -

contacts.deleteContacts

- -

Deletes several contacts from the list.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-contacts.deleteContacts#96a0e00 id:Vector<InputUser> = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idVector<InputUser>User ID list
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/contacts.getBlocked b/data/core.telegram.org/method/contacts.getBlocked deleted file mode 100644 index c7b1e35554..0000000000 --- a/data/core.telegram.org/method/contacts.getBlocked +++ /dev/null @@ -1,155 +0,0 @@ - - - - - contacts.getBlocked - - - - - - - - - - - - - -
- -
-
-
- -

contacts.getBlocked

- -

Returns the list of blocked users.

-

- -
-
contacts.blocked#ade1591 blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
-contacts.blockedSlice#e1664194 count:int blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
----functions---
-contacts.getBlocked#f57c350f offset:int limit:int = contacts.Blocked;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintThe number of list elements to be skipped
limitintThe number of list elements to be returned
-

Result

-

contacts.Blocked

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/contacts.getContactIDs b/data/core.telegram.org/method/contacts.getContactIDs deleted file mode 100644 index 0b2d62f294..0000000000 --- a/data/core.telegram.org/method/contacts.getContactIDs +++ /dev/null @@ -1,151 +0,0 @@ - - - - - contacts.getContactIDs - - - - - - - - - - - - - -
- -
-
-
- -

contacts.getContactIDs

- -

Get contact by telegram IDs

-

- -
-
---functions---
-contacts.getContactIDs#7adc669d hash:long = Vector<int>;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
-

Result

-

Vector<int>

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/contacts.getContacts b/data/core.telegram.org/method/contacts.getContacts deleted file mode 100644 index 72e31ea6d7..0000000000 --- a/data/core.telegram.org/method/contacts.getContacts +++ /dev/null @@ -1,155 +0,0 @@ - - - - - contacts.getContacts - - - - - - - - - - - - - -
- -
-
-
- -

contacts.getContacts

- -

Returns the current user's contact list.

-

- -
-
contacts.contactsNotModified#b74ba9d2 = contacts.Contacts;
-contacts.contacts#eae87e42 contacts:Vector<Contact> saved_count:int users:Vector<User> = contacts.Contacts;
----functions---
-contacts.getContacts#5dd69e12 hash:long = contacts.Contacts;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashlongIf there already is a full contact list on the client, a hash of a the list of contact IDs in ascending order may be passed in this parameter. If the contact set was not changed, (contacts.contactsNotModified) will be returned.
-

Result

-

contacts.Contacts

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

-

contacts.contactsNotModified

-

Contact list on the server is the same as the list on the client.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/contacts.getLocated b/data/core.telegram.org/method/contacts.getLocated deleted file mode 100644 index a8252e9443..0000000000 --- a/data/core.telegram.org/method/contacts.getLocated +++ /dev/null @@ -1,197 +0,0 @@ - - - - - contacts.getLocated - - - - - - - - - - - - - -
- -
-
-
- -

contacts.getLocated

- -

Get contacts near you

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-contacts.getLocated#d348bc44 flags:# background:flags.1?true geo_point:InputGeoPoint self_expires:flags.0?int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
backgroundflags.1?trueWhile the geolocation of the current user is public, clients should update it in the background every half-an-hour or so, while setting this flag.
Do this only if the new location is more than 1 KM away from the previous one, or if the previous location is unknown.
geo_pointInputGeoPointGeolocation
self_expiresflags.0?intIf set, the geolocation of the current user will be public for the specified number of seconds; pass 0x7fffffff to disable expiry, 0 to make the current geolocation private; if the flag isn't set, no changes will be applied.
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400GEO_POINT_INVALIDInvalid geoposition provided.
406USERPIC_PRIVACY_REQUIREDYou need to disable privacy settings for your profile picture in order to make your geolocation public.
406USERPIC_UPLOAD_REQUIREDYou must have a profile picture to publish your geolocation.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/contacts.getSaved b/data/core.telegram.org/method/contacts.getSaved deleted file mode 100644 index e74fada5e9..0000000000 --- a/data/core.telegram.org/method/contacts.getSaved +++ /dev/null @@ -1,150 +0,0 @@ - - - - - contacts.getSaved - - - - - - - - - - - - - -
- -
-
-
- -

contacts.getSaved

- -

Get all contacts

-

- -
-
---functions---
-contacts.getSaved#82f1e39f = Vector<SavedContact>;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Vector<SavedContact>

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
403TAKEOUT_REQUIREDA takeout session has to be initialized, first.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/contacts.getStatuses b/data/core.telegram.org/method/contacts.getStatuses deleted file mode 100644 index 5ad7897b45..0000000000 --- a/data/core.telegram.org/method/contacts.getStatuses +++ /dev/null @@ -1,133 +0,0 @@ - - - - - contacts.getStatuses - - - - - - - - - - - - - -
- -
-
-
- -

contacts.getStatuses

- -

Returns the list of contact statuses.

-

- -
-
---functions---
-contacts.getStatuses#c4a353ee = Vector<ContactStatus>;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Vector<ContactStatus>

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/contacts.getTopPeers b/data/core.telegram.org/method/contacts.getTopPeers deleted file mode 100644 index e19f2658ab..0000000000 --- a/data/core.telegram.org/method/contacts.getTopPeers +++ /dev/null @@ -1,226 +0,0 @@ - - - - - contacts.getTopPeers - - - - - - - - - - - - - -
- -
-
-
- -

contacts.getTopPeers

- -

Get most used peers

-

- -
-
contacts.topPeersNotModified#de266ef5 = contacts.TopPeers;
-contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;
-contacts.topPeersDisabled#b52c939d = contacts.TopPeers;
----functions---
-contacts.getTopPeers#973478b6 flags:# correspondents:flags.0?true bots_pm:flags.1?true bots_inline:flags.2?true phone_calls:flags.3?true forward_users:flags.4?true forward_chats:flags.5?true groups:flags.10?true channels:flags.15?true offset:int limit:int hash:long = contacts.TopPeers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
correspondentsflags.0?trueUsers we've chatted most frequently with
bots_pmflags.1?trueMost used bots
bots_inlineflags.2?trueMost used inline bots
phone_callsflags.3?trueMost frequently called users
forward_usersflags.4?trueUsers to which the users often forwards messages to
forward_chatsflags.5?trueChats to which the users often forwards messages to
groupsflags.10?trueOften-opened groups and supergroups
channelsflags.15?trueMost frequently visited channels
offsetintOffset for pagination
limitintMaximum number of results to return, see pagination
hashlongHash for pagination, for more info click here
-

Result

-

contacts.TopPeers

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400TYPES_EMPTYNo top peer type was provided.
-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/contacts.importContacts b/data/core.telegram.org/method/contacts.importContacts deleted file mode 100644 index 279b11ca35..0000000000 --- a/data/core.telegram.org/method/contacts.importContacts +++ /dev/null @@ -1,154 +0,0 @@ - - - - - contacts.importContacts - - - - - - - - - - - - - -
- -
-
-
- -

contacts.importContacts

- -

Imports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.

-

Use contacts.addContact to add Telegram contacts without actually using their phone number.

-

- -
-
contacts.importedContacts#77d01c3b imported:Vector<ImportedContact> popular_invites:Vector<PopularContact> retry_contacts:Vector<long> users:Vector<User> = contacts.ImportedContacts;
----functions---
-contacts.importContacts#2c800be5 contacts:Vector<InputContact> = contacts.ImportedContacts;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
contactsVector<InputContact>List of contacts to import
-

Result

-

contacts.ImportedContacts

-

Related pages

-

contacts.addContact

-

Add an existing telegram user as contact.

-

Use contacts.importContacts to add contacts by phone number, without knowing their Telegram ID.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/contacts.resetSaved b/data/core.telegram.org/method/contacts.resetSaved deleted file mode 100644 index 4fd122e042..0000000000 --- a/data/core.telegram.org/method/contacts.resetSaved +++ /dev/null @@ -1,135 +0,0 @@ - - - - - contacts.resetSaved - - - - - - - - - - - - - -
- -
-
-
- -

contacts.resetSaved

- -

Delete saved contacts

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-contacts.resetSaved#879537f1 = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/contacts.resetTopPeerRating b/data/core.telegram.org/method/contacts.resetTopPeerRating deleted file mode 100644 index dfb2f27f3c..0000000000 --- a/data/core.telegram.org/method/contacts.resetTopPeerRating +++ /dev/null @@ -1,175 +0,0 @@ - - - - - contacts.resetTopPeerRating - - - - - - - - - - - - - -
- -
-
-
- -

contacts.resetTopPeerRating

- -

Reset rating of top peer

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-contacts.resetTopPeerRating#1ae373ac category:TopPeerCategory peer:InputPeer = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
categoryTopPeerCategoryTop peer category
peerInputPeerPeer whose rating should be reset
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

Top peer rating

-

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/contacts.resolveUsername b/data/core.telegram.org/method/contacts.resolveUsername deleted file mode 100644 index 305d565063..0000000000 --- a/data/core.telegram.org/method/contacts.resolveUsername +++ /dev/null @@ -1,182 +0,0 @@ - - - - - contacts.resolveUsername - - - - - - - - - - - - - -
- -
-
-
- -

contacts.resolveUsername

- -

Resolve a @username to get peer info

-

- -
-
contacts.resolvedPeer#7f077ad9 peer:Peer chats:Vector<Chat> users:Vector<User> = contacts.ResolvedPeer;
----functions---
-contacts.resolveUsername#f93ccba3 username:string = contacts.ResolvedPeer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
usernamestring@username to resolve
-

Result

-

contacts.ResolvedPeer

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400CONNECTION_LAYER_INVALIDLayer invalid.
400USERNAME_INVALIDThe provided username is not valid.
400USERNAME_NOT_OCCUPIEDThe provided username is not occupied.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/contacts.search b/data/core.telegram.org/method/contacts.search deleted file mode 100644 index 6c662e25ac..0000000000 --- a/data/core.telegram.org/method/contacts.search +++ /dev/null @@ -1,178 +0,0 @@ - - - - - contacts.search - - - - - - - - - - - - - -
- -
-
-
- -

contacts.search

- -

Returns users found by username substring.

-

- -
-
contacts.found#b3134d9d my_results:Vector<Peer> results:Vector<Peer> chats:Vector<Chat> users:Vector<User> = contacts.Found;
----functions---
-contacts.search#11f812d8 q:string limit:int = contacts.Found;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
qstringTarget substring
limitintMaximum number of users to be returned
-

Result

-

contacts.Found

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400QUERY_TOO_SHORTThe query string is too short.
400SEARCH_QUERY_EMPTYThe search query is empty.
-

Notes

-

This method will exclude the current user's contacts from the search results. It is assumed that searches among the user's contacts can be handled locally by the client.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/contacts.toggleTopPeers b/data/core.telegram.org/method/contacts.toggleTopPeers deleted file mode 100644 index 069a25190b..0000000000 --- a/data/core.telegram.org/method/contacts.toggleTopPeers +++ /dev/null @@ -1,153 +0,0 @@ - - - - - contacts.toggleTopPeers - - - - - - - - - - - - - -
- -
-
-
- -

contacts.toggleTopPeers

- -

Enable/disable top peers

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-contacts.toggleTopPeers#8514bdda enabled:Bool = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
enabledBoolEnable/disable
-

Result

-

Bool

-

Related pages

-

Top peer rating

-

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/contacts.unblock b/data/core.telegram.org/method/contacts.unblock deleted file mode 100644 index deb5563e5c..0000000000 --- a/data/core.telegram.org/method/contacts.unblock +++ /dev/null @@ -1,182 +0,0 @@ - - - - - contacts.unblock - - - - - - - - - - - - - -
- -
-
-
- -

contacts.unblock

- -

Deletes the user from the blacklist.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-contacts.unblock#bea65d50 id:InputPeer = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idInputPeerUser ID
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CONTACT_ID_INVALIDThe provided contact ID is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/folders.deleteFolder b/data/core.telegram.org/method/folders.deleteFolder deleted file mode 100644 index 2e32fc7ff7..0000000000 --- a/data/core.telegram.org/method/folders.deleteFolder +++ /dev/null @@ -1,175 +0,0 @@ - - - - - folders.deleteFolder - - - - - - - - - - - - - -
- -
-
-
- -

folders.deleteFolder

- -

Delete a peer folder

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-folders.deleteFolder#1c295881 folder_id:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
folder_idintPeer folder ID, for more info click here
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400FOLDER_ID_EMPTYAn empty folder ID was specified.
-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/folders.editPeerFolders b/data/core.telegram.org/method/folders.editPeerFolders deleted file mode 100644 index db9e006d61..0000000000 --- a/data/core.telegram.org/method/folders.editPeerFolders +++ /dev/null @@ -1,175 +0,0 @@ - - - - - folders.editPeerFolders - - - - - - - - - - - - - -
- -
-
-
- -

folders.editPeerFolders

- -

Edit peers in peer folder

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-folders.editPeerFolders#6847d0ab folder_peers:Vector<InputFolderPeer> = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
folder_peersVector<InputFolderPeer>New peer list
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400FOLDER_ID_INVALIDInvalid folder ID.
-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/help.acceptTermsOfService b/data/core.telegram.org/method/help.acceptTermsOfService deleted file mode 100644 index d68ffeee0f..0000000000 --- a/data/core.telegram.org/method/help.acceptTermsOfService +++ /dev/null @@ -1,150 +0,0 @@ - - - - - help.acceptTermsOfService - - - - - - - - - - - - - -
- -
-
-
- -

help.acceptTermsOfService

- -

Accept the new terms of service

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-help.acceptTermsOfService#ee72f79a id:DataJSON = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idDataJSONID of terms of service
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/help.dismissSuggestion b/data/core.telegram.org/method/help.dismissSuggestion deleted file mode 100644 index 156c2561d8..0000000000 --- a/data/core.telegram.org/method/help.dismissSuggestion +++ /dev/null @@ -1,160 +0,0 @@ - - - - - help.dismissSuggestion - - - - - - - - - - - - - -
- -
-
-
- -

help.dismissSuggestion

- -

Dismiss a suggestion, see here for more info ».

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-help.dismissSuggestion#f50dbaa1 peer:InputPeer suggestion:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerIn the case of pending suggestions in channels, the channel ID.
suggestionstringSuggestion, see here for more info ».
-

Result

-

Bool

-

Related pages

-

channelFull

-

Full info about a channel/supergroup

-

Client configuration

-

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/help.editUserInfo b/data/core.telegram.org/method/help.editUserInfo deleted file mode 100644 index 32428aed38..0000000000 --- a/data/core.telegram.org/method/help.editUserInfo +++ /dev/null @@ -1,180 +0,0 @@ - - - - - help.editUserInfo - - - - - - - - - - - - - -
- -
-
-
- -

help.editUserInfo

- -

Internal use

-

- -
-
help.userInfoEmpty#f3ae2eed = help.UserInfo;
-help.userInfo#1eb3758 message:string entities:Vector<MessageEntity> author:string date:int = help.UserInfo;
----functions---
-help.editUserInfo#66b91b70 user_id:InputUser message:string entities:Vector<MessageEntity> = help.UserInfo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idInputUserUser
messagestringMessage
entitiesVector<MessageEntity>Message entities for styled text
-

Result

-

help.UserInfo

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400USER_INVALIDInvalid user provided.
-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/help.getAppChangelog b/data/core.telegram.org/method/help.getAppChangelog deleted file mode 100644 index 609fb03651..0000000000 --- a/data/core.telegram.org/method/help.getAppChangelog +++ /dev/null @@ -1,162 +0,0 @@ - - - - - help.getAppChangelog - - - - - - - - - - - - - -
- -
-
-
- -

help.getAppChangelog

- -

Get changelog of current app.
-Typically, an updates constructor will be returned, containing one or more updateServiceNotification updates with app-specific changelogs.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-help.getAppChangelog#9010ef6f prev_app_version:string = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
prev_app_versionstringPrevious app version
-

Result

-

Updates

-

Related pages

-

Updates

-

Full constructor of updates

-

updateServiceNotification

-

A service message for the user.

-

The app must show the message to the user upon receiving this update. In case the popup parameter was passed, the text message must be displayed in a popup alert immediately upon receipt. It is recommended to handle the text as you would an ordinary message in terms of highlighting links, etc. The message must also be stored locally as part of the message history with the user id 777000 (Telegram Notifications).

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/help.getAppConfig b/data/core.telegram.org/method/help.getAppConfig deleted file mode 100644 index ad032c6809..0000000000 --- a/data/core.telegram.org/method/help.getAppConfig +++ /dev/null @@ -1,142 +0,0 @@ - - - - - help.getAppConfig - - - - - - - - - - - - - -
- -
-
-
- -

help.getAppConfig

- -

Get app-specific configuration, see client configuration for more info on the result.

-

- -
-
jsonNull#3f6d7b68 = JSONValue;
-jsonBool#c7345e6a value:Bool = JSONValue;
-jsonNumber#2be0dfa4 value:double = JSONValue;
-jsonString#b71e767a value:string = JSONValue;
-jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;
-jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;
----functions---
-help.getAppConfig#98914110 = JSONValue;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

JSONValue, see client configuration for more info on the result

-

Related pages

-

Client configuration

-

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/help.getAppUpdate b/data/core.telegram.org/method/help.getAppUpdate deleted file mode 100644 index 27088b0ef5..0000000000 --- a/data/core.telegram.org/method/help.getAppUpdate +++ /dev/null @@ -1,150 +0,0 @@ - - - - - help.getAppUpdate - - - - - - - - - - - - - -
- -
-
-
- -

help.getAppUpdate

- -

Returns information on update availability for the current application.

-

- -
-
help.appUpdate#ccbbce30 flags:# can_not_skip:flags.0?true id:int version:string text:string entities:Vector<MessageEntity> document:flags.1?Document url:flags.2?string sticker:flags.3?Document = help.AppUpdate;
-help.noAppUpdate#c45a6536 = help.AppUpdate;
----functions---
-help.getAppUpdate#522d5a7d source:string = help.AppUpdate;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
sourcestringSource
-

Result

-

help.AppUpdate

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/help.getCdnConfig b/data/core.telegram.org/method/help.getCdnConfig deleted file mode 100644 index b3b1d7abf6..0000000000 --- a/data/core.telegram.org/method/help.getCdnConfig +++ /dev/null @@ -1,154 +0,0 @@ - - - - - help.getCdnConfig - - - - - - - - - - - - - -
- -
-
-
- -

help.getCdnConfig

- -

Get configuration for CDN file downloads.

-

- -
-
cdnConfig#5725e40a public_keys:Vector<CdnPublicKey> = CdnConfig;
----functions---
-help.getCdnConfig#52029342 = CdnConfig;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

CdnConfig

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
-

Bots can use this method

-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/help.getConfig b/data/core.telegram.org/method/help.getConfig deleted file mode 100644 index 33d4326faa..0000000000 --- a/data/core.telegram.org/method/help.getConfig +++ /dev/null @@ -1,192 +0,0 @@ - - - - - help.getConfig - - - - - - - - - - - - - -
- -
-
-
- -

help.getConfig

- -

Returns current configuration, including data center configuration.

-

- -
-
config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;
----functions---
-help.getConfig#c4f9186b = Config;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Config

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CONNECTION_API_ID_INVALIDThe provided API id is invalid.
400CONNECTION_APP_VERSION_EMPTYApp version is empty.
400CONNECTION_LAYER_INVALIDLayer invalid.
400CONNECTION_NOT_INITEDConnection not initialized.
400DATA_INVALIDEncrypted data invalid.
400INPUT_LAYER_INVALIDThe provided layer is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400USERNAME_INVALIDThe provided username is not valid.
403USER_PRIVACY_RESTRICTEDThe user's privacy settings do not allow you to do this.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/help.getCountriesList b/data/core.telegram.org/method/help.getCountriesList deleted file mode 100644 index 88f7b8386c..0000000000 --- a/data/core.telegram.org/method/help.getCountriesList +++ /dev/null @@ -1,158 +0,0 @@ - - - - - help.getCountriesList - - - - - - - - - - - - - -
- -
-
-
- -

help.getCountriesList

- -

Get name, ISO code, localized name and phone codes/patterns of all available countries

-

- -
-
help.countriesListNotModified#93cc1f32 = help.CountriesList;
-help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;
----functions---
-help.getCountriesList#735787a8 lang_code:string hash:int = help.CountriesList;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
lang_codestringLanguage code of the current user
hashintHash for pagination, for more info click here
-

Result

-

help.CountriesList

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/help.getDeepLinkInfo b/data/core.telegram.org/method/help.getDeepLinkInfo deleted file mode 100644 index 8396b041bb..0000000000 --- a/data/core.telegram.org/method/help.getDeepLinkInfo +++ /dev/null @@ -1,150 +0,0 @@ - - - - - help.getDeepLinkInfo - - - - - - - - - - - - - -
- -
-
-
- -

help.getDeepLinkInfo

- -

Get info about a t.me link

-

- -
-
help.deepLinkInfoEmpty#66afa166 = help.DeepLinkInfo;
-help.deepLinkInfo#6a4ee832 flags:# update_app:flags.0?true message:string entities:flags.1?Vector<MessageEntity> = help.DeepLinkInfo;
----functions---
-help.getDeepLinkInfo#3fedc75f path:string = help.DeepLinkInfo;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
pathstringPath in t.me/path
-

Result

-

help.DeepLinkInfo

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/help.getInviteText b/data/core.telegram.org/method/help.getInviteText deleted file mode 100644 index 014bbc704d..0000000000 --- a/data/core.telegram.org/method/help.getInviteText +++ /dev/null @@ -1,134 +0,0 @@ - - - - - help.getInviteText - - - - - - - - - - - - - -
- -
-
-
- -

help.getInviteText

- -

Returns localized text of a text message with an invitation.

-

- -
-
help.inviteText#18cb9f78 message:string = help.InviteText;
----functions---
-help.getInviteText#4d392343 = help.InviteText;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

help.InviteText

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/help.getPassportConfig b/data/core.telegram.org/method/help.getPassportConfig deleted file mode 100644 index 46b7e21f94..0000000000 --- a/data/core.telegram.org/method/help.getPassportConfig +++ /dev/null @@ -1,154 +0,0 @@ - - - - - help.getPassportConfig - - - - - - - - - - - - - -
- -
-
-
- -

help.getPassportConfig

- -

Get passport configuration

-

- -
-
help.passportConfigNotModified#bfb9f457 = help.PassportConfig;
-help.passportConfig#a098d6af hash:int countries_langs:DataJSON = help.PassportConfig;
----functions---
-help.getPassportConfig#c661ad08 hash:int = help.PassportConfig;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashintHash for pagination, for more info click here
-

Result

-

help.PassportConfig

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/help.getPromoData b/data/core.telegram.org/method/help.getPromoData deleted file mode 100644 index f34cdff29a..0000000000 --- a/data/core.telegram.org/method/help.getPromoData +++ /dev/null @@ -1,135 +0,0 @@ - - - - - help.getPromoData - - - - - - - - - - - - - -
- -
-
-
- -

help.getPromoData

- -

Get MTProxy/Public Service Announcement information

-

- -
-
help.promoDataEmpty#98f6ac75 expires:int = help.PromoData;
-help.promoData#8c39793f flags:# proxy:flags.0?true expires:int peer:Peer chats:Vector<Chat> users:Vector<User> psa_type:flags.1?string psa_message:flags.2?string = help.PromoData;
----functions---
-help.getPromoData#c0977421 = help.PromoData;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

help.PromoData

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/help.getProxyData b/data/core.telegram.org/method/help.getProxyData deleted file mode 100644 index d46672dd13..0000000000 --- a/data/core.telegram.org/method/help.getProxyData +++ /dev/null @@ -1,132 +0,0 @@ - - - - - help.getProxyData - - - - - - - - - - - - - -
- -
-
-
- -

help.getProxyData

- -

Get promotion info of the currently-used MTProxy

-

- -
-
 Method schema is available as of layer 113. Switch »

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

help.ProxyData

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/help.getRecentMeUrls b/data/core.telegram.org/method/help.getRecentMeUrls deleted file mode 100644 index f60cdd6eee..0000000000 --- a/data/core.telegram.org/method/help.getRecentMeUrls +++ /dev/null @@ -1,149 +0,0 @@ - - - - - help.getRecentMeUrls - - - - - - - - - - - - - -
- -
-
-
- -

help.getRecentMeUrls

- -

Get recently used t.me links

-

- -
-
help.recentMeUrls#e0310d7 urls:Vector<RecentMeUrl> chats:Vector<Chat> users:Vector<User> = help.RecentMeUrls;
----functions---
-help.getRecentMeUrls#3dc0f114 referer:string = help.RecentMeUrls;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
refererstringReferer
-

Result

-

help.RecentMeUrls

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/help.getSupport b/data/core.telegram.org/method/help.getSupport deleted file mode 100644 index e6ec831633..0000000000 --- a/data/core.telegram.org/method/help.getSupport +++ /dev/null @@ -1,134 +0,0 @@ - - - - - help.getSupport - - - - - - - - - - - - - -
- -
-
-
- -

help.getSupport

- -

Returns the support user for the 'ask a question' feature.

-

- -
-
help.support#17c6b5f6 phone_number:string user:User = help.Support;
----functions---
-help.getSupport#9cdf08cd = help.Support;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

help.Support

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/help.getSupportName b/data/core.telegram.org/method/help.getSupportName deleted file mode 100644 index ab4d39e208..0000000000 --- a/data/core.telegram.org/method/help.getSupportName +++ /dev/null @@ -1,151 +0,0 @@ - - - - - help.getSupportName - - - - - - - - - - - - - -
- -
-
-
- -

help.getSupportName

- -

Get localized name of the telegram support user

-

- -
-
help.supportName#8c05f1c9 name:string = help.SupportName;
----functions---
-help.getSupportName#d360e72c = help.SupportName;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

help.SupportName

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
403USER_INVALIDInvalid user provided.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/help.getTermsOfServiceUpdate b/data/core.telegram.org/method/help.getTermsOfServiceUpdate deleted file mode 100644 index 957dbf33c3..0000000000 --- a/data/core.telegram.org/method/help.getTermsOfServiceUpdate +++ /dev/null @@ -1,135 +0,0 @@ - - - - - help.getTermsOfServiceUpdate - - - - - - - - - - - - - -
- -
-
-
- -

help.getTermsOfServiceUpdate

- -

Look for updates of telegram's terms of service

-

- -
-
help.termsOfServiceUpdateEmpty#e3309f7f expires:int = help.TermsOfServiceUpdate;
-help.termsOfServiceUpdate#28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate;
----functions---
-help.getTermsOfServiceUpdate#2ca51fd1 = help.TermsOfServiceUpdate;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

help.TermsOfServiceUpdate

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/help.getUserInfo b/data/core.telegram.org/method/help.getUserInfo deleted file mode 100644 index d8eaf8f75f..0000000000 --- a/data/core.telegram.org/method/help.getUserInfo +++ /dev/null @@ -1,167 +0,0 @@ - - - - - help.getUserInfo - - - - - - - - - - - - - -
- -
-
-
- -

help.getUserInfo

- -

Internal use

-

- -
-
help.userInfoEmpty#f3ae2eed = help.UserInfo;
-help.userInfo#1eb3758 message:string entities:Vector<MessageEntity> author:string date:int = help.UserInfo;
----functions---
-help.getUserInfo#38a08d3 user_id:InputUser = help.UserInfo;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
user_idInputUserUser ID
-

Result

-

help.UserInfo

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
403USER_INVALIDInvalid user provided.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/help.hidePromoData b/data/core.telegram.org/method/help.hidePromoData deleted file mode 100644 index c9a15dcf42..0000000000 --- a/data/core.telegram.org/method/help.hidePromoData +++ /dev/null @@ -1,150 +0,0 @@ - - - - - help.hidePromoData - - - - - - - - - - - - - -
- -
-
-
- -

help.hidePromoData

- -

Hide MTProxy/Public Service Announcement information

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-help.hidePromoData#1e251c95 peer:InputPeer = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer to hide
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/help.saveAppLog b/data/core.telegram.org/method/help.saveAppLog deleted file mode 100644 index 1623540eed..0000000000 --- a/data/core.telegram.org/method/help.saveAppLog +++ /dev/null @@ -1,150 +0,0 @@ - - - - - help.saveAppLog - - - - - - - - - - - - - -
- -
-
-
- -

help.saveAppLog

- -

Saves logs of application on the server.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-help.saveAppLog#6f02f748 events:Vector<InputAppEvent> = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
eventsVector<InputAppEvent>List of input events
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/help.setBotUpdatesStatus b/data/core.telegram.org/method/help.setBotUpdatesStatus deleted file mode 100644 index 067814c280..0000000000 --- a/data/core.telegram.org/method/help.setBotUpdatesStatus +++ /dev/null @@ -1,156 +0,0 @@ - - - - - help.setBotUpdatesStatus - - - - - - - - - - - - - -
- -
-
-
- -

help.setBotUpdatesStatus

- -

Informs the server about the number of pending bot updates if they haven't been processed for a long time; for bots only

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-help.setBotUpdatesStatus#ec22cfcd pending_updates_count:int message:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
pending_updates_countintNumber of pending updates
messagestringError message, if present
-

Result

-

Bool

-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/initConnection.html b/data/core.telegram.org/method/initConnection.html deleted file mode 100644 index 93c0d3cc51..0000000000 --- a/data/core.telegram.org/method/initConnection.html +++ /dev/null @@ -1,216 +0,0 @@ - - - - - initConnection - - - - - - - - - - - - - -
- -
-
-
- -

initConnection

- -

Initialize connection

-

- -
-
---functions---
-initConnection#c1cd5ea9 {X:Type} flags:# api_id:int device_model:string system_version:string app_version:string system_lang_code:string lang_pack:string lang_code:string proxy:flags.0?InputClientProxy params:flags.1?JSONValue query:!X = X;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
api_idintApplication identifier (see. App configuration)
device_modelstringDevice model
system_versionstringOperation system version
app_versionstringApplication version
system_lang_codestringCode for the language used on the device's OS, ISO 639-1 standard
lang_packstringLanguage pack to use
lang_codestringCode for the language used on the client, ISO 639-1 standard
proxyflags.0?InputClientProxyInfo about an MTProto proxy
paramsflags.1?JSONValueAdditional initConnection parameters.
For now, only the tz_offset field is supported, for specifying timezone offset in seconds.
query!XThe query itself
-

Result

-

X

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400CONNECTION_LAYER_INVALIDLayer invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/invokeAfterMsg.html b/data/core.telegram.org/method/invokeAfterMsg.html deleted file mode 100644 index 028d4b4940..0000000000 --- a/data/core.telegram.org/method/invokeAfterMsg.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - invokeAfterMsg - - - - - - - - - - - - - -
- -
-
-
- -

invokeAfterMsg

- -

Invokes a query after successfull completion of one of the previous queries.

-

- -
-
---functions---
-invokeAfterMsg#cb9f372d {X:Type} msg_id:long query:!X = X;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
msg_idlongMessage identifier on which a current query depends
query!XThe query itself
-

Result

-

X

-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/invokeAfterMsgs.html b/data/core.telegram.org/method/invokeAfterMsgs.html deleted file mode 100644 index a0e9cda487..0000000000 --- a/data/core.telegram.org/method/invokeAfterMsgs.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - invokeAfterMsgs - - - - - - - - - - - - - -
- -
-
-
- -

invokeAfterMsgs

- -

Invokes a query after a successfull completion of previous queries

-

- -
-
---functions---
-invokeAfterMsgs#3dc4b4f0 {X:Type} msg_ids:Vector<long> query:!X = X;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
msg_idsVector<long>List of messages on which a current query depends
query!XThe query itself
-

Result

-

X

-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/invokeWithLayer.html b/data/core.telegram.org/method/invokeWithLayer.html deleted file mode 100644 index a5e3c1da29..0000000000 --- a/data/core.telegram.org/method/invokeWithLayer.html +++ /dev/null @@ -1,204 +0,0 @@ - - - - - invokeWithLayer - - - - - - - - - - - - - -
- -
-
-
- -

invokeWithLayer

- -

Invoke the specified query using the specified API layer

-

- -
-
---functions---
-invokeWithLayer#da9b0d0d {X:Type} layer:int query:!X = X;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
layerintThe layer to use
query!XThe query
-

Result

-

X

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400AUTH_BYTES_INVALIDThe provided authorization is invalid.
400CDN_METHOD_INVALIDYou can't call this method in a CDN DC.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400CONNECTION_API_ID_INVALIDThe provided API id is invalid.
400CONNECTION_NOT_INITEDConnection not initialized.
400INPUT_LAYER_INVALIDThe provided layer is invalid.
400INVITE_HASH_EXPIREDThe invite link has expired.
-

Bots can use this method

-

Related pages

-

Calling API Methods

-

Additional options for calling methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/invokeWithTakeout.html b/data/core.telegram.org/method/invokeWithTakeout.html deleted file mode 100644 index d35a60cfc2..0000000000 --- a/data/core.telegram.org/method/invokeWithTakeout.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - invokeWithTakeout - - - - - - - - - - - - - -
- -
-
-
- -

invokeWithTakeout

- -

Invoke a method within a takeout session

-

- -
-
---functions---
-invokeWithTakeout#aca9fd2e {X:Type} takeout_id:long query:!X = X;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
takeout_idlongTakeout session ID
query!XQuery
-

Result

-

X

-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/invokeWithoutUpdates.html b/data/core.telegram.org/method/invokeWithoutUpdates.html deleted file mode 100644 index b6682f675f..0000000000 --- a/data/core.telegram.org/method/invokeWithoutUpdates.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - invokeWithoutUpdates - - - - - - - - - - - - - -
- -
-
-
- -

invokeWithoutUpdates

- -

Invoke a request without subscribing the used connection for updates (this is enabled by default for file queries).

-

- -
-
---functions---
-invokeWithoutUpdates#bf9459b7 {X:Type} query:!X = X;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
query!XThe query
-

Result

-

X

-

Bots can use this method

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/langpack.getDifference b/data/core.telegram.org/method/langpack.getDifference deleted file mode 100644 index 342c0e136f..0000000000 --- a/data/core.telegram.org/method/langpack.getDifference +++ /dev/null @@ -1,176 +0,0 @@ - - - - - langpack.getDifference - - - - - - - - - - - - - -
- -
-
-
- -

langpack.getDifference

- -

Get new strings in languagepack

-

- -
-
langPackDifference#f385c1f6 lang_code:string from_version:int version:int strings:Vector<LangPackString> = LangPackDifference;
----functions---
-langpack.getDifference#cd984aa5 lang_pack:string lang_code:string from_version:int = LangPackDifference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
lang_packstringLanguage pack
lang_codestringLanguage code
from_versionintPrevious localization pack version
-

Result

-

LangPackDifference

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400LANG_PACK_INVALIDThe provided language pack is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/langpack.getLangPack b/data/core.telegram.org/method/langpack.getLangPack deleted file mode 100644 index 2ca79ec8fd..0000000000 --- a/data/core.telegram.org/method/langpack.getLangPack +++ /dev/null @@ -1,171 +0,0 @@ - - - - - langpack.getLangPack - - - - - - - - - - - - - -
- -
-
-
- -

langpack.getLangPack

- -

Get localization pack strings

-

- -
-
langPackDifference#f385c1f6 lang_code:string from_version:int version:int strings:Vector<LangPackString> = LangPackDifference;
----functions---
-langpack.getLangPack#f2f2330a lang_pack:string lang_code:string = LangPackDifference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
lang_packstringLanguage pack name
lang_codestringLanguage code
-

Result

-

LangPackDifference

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400LANG_PACK_INVALIDThe provided language pack is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/langpack.getLanguage b/data/core.telegram.org/method/langpack.getLanguage deleted file mode 100644 index 6baac5a624..0000000000 --- a/data/core.telegram.org/method/langpack.getLanguage +++ /dev/null @@ -1,154 +0,0 @@ - - - - - langpack.getLanguage - - - - - - - - - - - - - -
- -
-
-
- -

langpack.getLanguage

- -

Get information about a language in a localization pack

-

- -
-
langPackLanguage#eeca5ce3 flags:# official:flags.0?true rtl:flags.2?true beta:flags.3?true name:string native_name:string lang_code:string base_lang_code:flags.1?string plural_code:string strings_count:int translated_count:int translations_url:string = LangPackLanguage;
----functions---
-langpack.getLanguage#6a596502 lang_pack:string lang_code:string = LangPackLanguage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
lang_packstringLanguage pack name
lang_codestringLanguage code
-

Result

-

LangPackLanguage

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/langpack.getLanguages b/data/core.telegram.org/method/langpack.getLanguages deleted file mode 100644 index 063a19ea19..0000000000 --- a/data/core.telegram.org/method/langpack.getLanguages +++ /dev/null @@ -1,165 +0,0 @@ - - - - - langpack.getLanguages - - - - - - - - - - - - - -
- -
-
-
- -

langpack.getLanguages

- -

Get information about all languages in a localization pack

-

- -
-
---functions---
-langpack.getLanguages#42c6978f lang_pack:string = Vector<LangPackLanguage>;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
lang_packstringLanguage pack
-

Result

-

Vector<LangPackLanguage>

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400LANG_PACK_INVALIDThe provided language pack is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.acceptEncryption b/data/core.telegram.org/method/messages.acceptEncryption deleted file mode 100644 index 47732802b0..0000000000 --- a/data/core.telegram.org/method/messages.acceptEncryption +++ /dev/null @@ -1,190 +0,0 @@ - - - - - messages.acceptEncryption - - - - - - - - - - - - - -
- -
-
-
- -

messages.acceptEncryption

- -

Confirms creation of a secret chat

-

- -
-
encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;
-encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;
-encryptedChatRequested#48f1d94c flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:long participant_id:long g_a:bytes = EncryptedChat;
-encryptedChat#61f0d4c7 id:int access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long = EncryptedChat;
-encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;
----functions---
-messages.acceptEncryption#3dbc0415 peer:InputEncryptedChat g_b:bytes key_fingerprint:long = EncryptedChat;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputEncryptedChatSecret chat ID
g_bbytesB = g ^ b mod p, see Wikipedia
key_fingerprintlong64-bit fingerprint of the received key
-

Result

-

EncryptedChat

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400ENCRYPTION_ALREADY_ACCEPTEDSecret chat already accepted.
400ENCRYPTION_ALREADY_DECLINEDThe secret chat was already declined.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.addChatUser b/data/core.telegram.org/method/messages.addChatUser deleted file mode 100644 index dec1244912..0000000000 --- a/data/core.telegram.org/method/messages.addChatUser +++ /dev/null @@ -1,237 +0,0 @@ - - - - - messages.addChatUser - - - - - - - - - - - - - -
- -
-
-
- -

messages.addChatUser

- -

Adds a user to a chat and sends a service message on it.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.addChatUser#f24753e3 chat_id:long user_id:InputUser fwd_limit:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongChat ID
user_idInputUserUser ID to be added
fwd_limitintNumber of last messages to be forwarded
-

Result

-

messages.StatedMessage

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USERS_TOO_MUCHThe maximum number of users has been exceeded (to create a chat, for example).
400USER_ALREADY_PARTICIPANTThe user is already in the group.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_IS_BLOCKEDYou were blocked by this user.
403USER_NOT_MUTUAL_CONTACTThe provided user is not a mutual contact.
403USER_PRIVACY_RESTRICTEDThe user's privacy settings do not allow you to do this.
400YOU_BLOCKED_USERYou blocked this user.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.checkHistoryImport b/data/core.telegram.org/method/messages.checkHistoryImport deleted file mode 100644 index 9abec2cbc3..0000000000 --- a/data/core.telegram.org/method/messages.checkHistoryImport +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messages.checkHistoryImport - - - - - - - - - - - - - -
- -
-
-
- -

messages.checkHistoryImport

- -

Obtains information about a chat export file, generated by a foreign chat app, click here for more info about imported chats ».

-

- -
-
messages.historyImportParsed#5e0fb7b9 flags:# pm:flags.0?true group:flags.1?true title:flags.2?string = messages.HistoryImportParsed;
----functions---
-messages.checkHistoryImport#43fe19f3 import_head:string = messages.HistoryImportParsed;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
import_headstringBeginning of the message file; up to 100 lines.
-

Result

-

messages.HistoryImportParsed

-

Related pages

-

Imported messages

-

Telegram allows importing messages and media from foreign chat apps.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.checkHistoryImportPeer b/data/core.telegram.org/method/messages.checkHistoryImportPeer deleted file mode 100644 index a7d5c85a01..0000000000 --- a/data/core.telegram.org/method/messages.checkHistoryImportPeer +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.checkHistoryImportPeer - - - - - - - - - - - - - -
- -
-
-
- -

messages.checkHistoryImportPeer

- -

Check whether chat history exported from another chat app can be imported into a specific Telegram chat, click here for more info ».

-

If the check succeeds, and no RPC errors are returned, a messages.CheckedHistoryImportPeer constructor will be returned, with a confirmation text to be shown to the user, before actually initializing the import.

-

- -
-
messages.checkedHistoryImportPeer#a24de717 confirm_text:string = messages.CheckedHistoryImportPeer;
----functions---
-messages.checkHistoryImportPeer#5dc60f03 peer:InputPeer = messages.CheckedHistoryImportPeer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat where we want to import history ».
-

Result

-

messages.CheckedHistoryImportPeer

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400USER_NOT_MUTUAL_CONTACTThe provided user is not a mutual contact.
-

Related pages

-

Imported messages

-

Telegram allows importing messages and media from foreign chat apps.

-

messages.CheckedHistoryImportPeer

-

Contains a confirmation text to be shown to the user, upon importing chat history, click here for more info ».

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.clearAllDrafts b/data/core.telegram.org/method/messages.clearAllDrafts deleted file mode 100644 index ee8ead09eb..0000000000 --- a/data/core.telegram.org/method/messages.clearAllDrafts +++ /dev/null @@ -1,138 +0,0 @@ - - - - - messages.clearAllDrafts - - - - - - - - - - - - - -
- -
-
-
- -

messages.clearAllDrafts

- -

Clear all drafts.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.clearAllDrafts#7e58ee9c = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Bool

-

Related pages

-

Message drafts

-

How to handle message drafts

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.clearRecentStickers b/data/core.telegram.org/method/messages.clearRecentStickers deleted file mode 100644 index 6245cb4a49..0000000000 --- a/data/core.telegram.org/method/messages.clearRecentStickers +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.clearRecentStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.clearRecentStickers

- -

Clear recent stickers

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.clearRecentStickers#8999602d flags:# attached:flags.0?true = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
attachedflags.0?trueSet this flag to clear the list of stickers recently attached to photo or video files
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.createChat b/data/core.telegram.org/method/messages.createChat deleted file mode 100644 index 459f7e05c8..0000000000 --- a/data/core.telegram.org/method/messages.createChat +++ /dev/null @@ -1,197 +0,0 @@ - - - - - messages.createChat - - - - - - - - - - - - - -
- -
-
-
- -

messages.createChat

- -

Creates a new chat.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.createChat#9cb126e users:Vector<InputUser> title:string = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
usersVector<InputUser>List of user IDs to be invited
titlestringChat name
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_INVALIDInvalid chat.
400CHAT_TITLE_EMPTYNo chat title provided.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400USERS_TOO_FEWNot enough users (to create a chat, for example).
403USER_RESTRICTEDYou're spamreported, you can't create channels or chats.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.deleteChat b/data/core.telegram.org/method/messages.deleteChat deleted file mode 100644 index 953e7e4f9f..0000000000 --- a/data/core.telegram.org/method/messages.deleteChat +++ /dev/null @@ -1,170 +0,0 @@ - - - - - messages.deleteChat - - - - - - - - - - - - - -
- -
-
-
- -

messages.deleteChat

- -

Delete a chat

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.deleteChat#5bd0ee50 chat_id:long = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongChat ID
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.deleteChatUser b/data/core.telegram.org/method/messages.deleteChatUser deleted file mode 100644 index 14c4da06ba..0000000000 --- a/data/core.telegram.org/method/messages.deleteChatUser +++ /dev/null @@ -1,208 +0,0 @@ - - - - - messages.deleteChatUser - - - - - - - - - - - - - -
- -
-
-
- -

messages.deleteChatUser

- -

Deletes a user from a chat and sends a service message on it.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.deleteChatUser#a2185cab flags:# revoke_history:flags.0?true chat_id:long user_id:InputUser = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
revoke_historyflags.0?trueRemove the entire chat history of the specified user in this chat.
chat_idlongChat ID
user_idInputUserUser ID to be deleted
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_NOT_PARTICIPANTYou're not a member of this supergroup/channel.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.deleteExportedChatInvite b/data/core.telegram.org/method/messages.deleteExportedChatInvite deleted file mode 100644 index 65a67e647d..0000000000 --- a/data/core.telegram.org/method/messages.deleteExportedChatInvite +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.deleteExportedChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

messages.deleteExportedChatInvite

- -

Delete a chat invite

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.deleteExportedChatInvite#d464a42b peer:InputPeer link:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
linkstringInvite link
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.deleteHistory b/data/core.telegram.org/method/messages.deleteHistory deleted file mode 100644 index 68124f65bb..0000000000 --- a/data/core.telegram.org/method/messages.deleteHistory +++ /dev/null @@ -1,206 +0,0 @@ - - - - - messages.deleteHistory - - - - - - - - - - - - - -
- -
-
-
- -

messages.deleteHistory

- -

Deletes communication history.

-

- -
-
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
----functions---
-messages.deleteHistory#1c015b09 flags:# just_clear:flags.0?true revoke:flags.1?true peer:InputPeer max_id:int = messages.AffectedHistory;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
just_clearflags.0?trueJust clear history for the current user, without actually removing messages for every chat user
revokeflags.1?trueWhether to delete the message history for all chat participants
peerInputPeerUser or chat, communication history of which will be deleted
max_idintMaximum ID of message to delete
-

Result

-

messages.AffectedHistory

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.deletePhoneCallHistory b/data/core.telegram.org/method/messages.deletePhoneCallHistory deleted file mode 100644 index e47d303edb..0000000000 --- a/data/core.telegram.org/method/messages.deletePhoneCallHistory +++ /dev/null @@ -1,154 +0,0 @@ - - - - - messages.deletePhoneCallHistory - - - - - - - - - - - - - -
- -
-
-
- -

messages.deletePhoneCallHistory

- -

Delete the entire phone call history.

-

- -
-
messages.affectedFoundMessages#ef8d3e6c pts:int pts_count:int offset:int messages:Vector<int> = messages.AffectedFoundMessages;
----functions---
-messages.deletePhoneCallHistory#f9cbe409 flags:# revoke:flags.0?true = messages.AffectedFoundMessages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
revokeflags.0?trueWhether to remove phone call history for participants as well
-

Result

-

messages.AffectedFoundMessages

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.deleteRevokedExportedChatInvites b/data/core.telegram.org/method/messages.deleteRevokedExportedChatInvites deleted file mode 100644 index 3103db9471..0000000000 --- a/data/core.telegram.org/method/messages.deleteRevokedExportedChatInvites +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.deleteRevokedExportedChatInvites - - - - - - - - - - - - - -
- -
-
-
- -

messages.deleteRevokedExportedChatInvites

- -

Delete all revoked chat invites

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.deleteRevokedExportedChatInvites#56987bd5 peer:InputPeer admin_id:InputUser = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerChat
admin_idInputUserID of the admin that originally generated the revoked chat invites
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.deleteScheduledMessages b/data/core.telegram.org/method/messages.deleteScheduledMessages deleted file mode 100644 index e3c959730f..0000000000 --- a/data/core.telegram.org/method/messages.deleteScheduledMessages +++ /dev/null @@ -1,160 +0,0 @@ - - - - - messages.deleteScheduledMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.deleteScheduledMessages

- -

Delete scheduled messages

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.deleteScheduledMessages#59ae2b16 peer:InputPeer id:Vector<int> = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
idVector<int>Scheduled message IDs
-

Result

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.discardEncryption b/data/core.telegram.org/method/messages.discardEncryption deleted file mode 100644 index 9e5b37e730..0000000000 --- a/data/core.telegram.org/method/messages.discardEncryption +++ /dev/null @@ -1,187 +0,0 @@ - - - - - messages.discardEncryption - - - - - - - - - - - - - -
- -
-
-
- -

messages.discardEncryption

- -

Cancels a request for creation and/or delete info on secret chat.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.discardEncryption#f393aea0 flags:# delete_history:flags.0?true chat_id:int = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
delete_historyflags.0?trueWhether to delete the entire chat history for the other user as well
chat_idintSecret chat ID
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ID_EMPTYThe provided chat ID is empty.
400ENCRYPTION_ALREADY_DECLINEDThe secret chat was already declined.
400ENCRYPTION_ID_INVALIDThe provided secret chat ID is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.editChatAbout b/data/core.telegram.org/method/messages.editChatAbout deleted file mode 100644 index 206db20474..0000000000 --- a/data/core.telegram.org/method/messages.editChatAbout +++ /dev/null @@ -1,216 +0,0 @@ - - - - - messages.editChatAbout - - - - - - - - - - - - - -
- -
-
-
- -

messages.editChatAbout

- -

Edit the description of a group/supergroup/channel.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.editChatAbout#def60797 peer:InputPeer about:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe group/supergroup/channel.
aboutstringThe new description
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ABOUT_NOT_MODIFIEDAbout text has not changed.
400CHAT_ABOUT_TOO_LONGChat about too long.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Bots can use this method

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.editChatAdmin b/data/core.telegram.org/method/messages.editChatAdmin deleted file mode 100644 index ee2e67f68a..0000000000 --- a/data/core.telegram.org/method/messages.editChatAdmin +++ /dev/null @@ -1,195 +0,0 @@ - - - - - messages.editChatAdmin - - - - - - - - - - - - - -
- -
-
-
- -

messages.editChatAdmin

- -

Make a user admin in a legacy group.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.editChatAdmin#a85bd1c2 chat_id:long user_id:InputUser is_admin:Bool = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongThe ID of the group
user_idInputUserThe user to make admin
is_adminBoolWhether to make him admin
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_NOT_PARTICIPANTYou're not a member of this supergroup/channel.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.editChatDefaultBannedRights b/data/core.telegram.org/method/messages.editChatDefaultBannedRights deleted file mode 100644 index caf4ce2cba..0000000000 --- a/data/core.telegram.org/method/messages.editChatDefaultBannedRights +++ /dev/null @@ -1,206 +0,0 @@ - - - - - messages.editChatDefaultBannedRights - - - - - - - - - - - - - -
- -
-
-
- -

messages.editChatDefaultBannedRights

- -

Edit the default banned rights of a channel/supergroup/group.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.editChatDefaultBannedRights#a5866b41 peer:InputPeer banned_rights:ChatBannedRights = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe peer
banned_rightsChatBannedRightsThe new global rights
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BANNED_RIGHTS_INVALIDYou provided some invalid flags in the banned rights.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400PEER_ID_INVALIDThe provided peer id is invalid.
400UNTIL_DATE_INVALIDInvalid until date provided.
-

Bots can use this method

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.editChatPhoto b/data/core.telegram.org/method/messages.editChatPhoto deleted file mode 100644 index e5fb3af727..0000000000 --- a/data/core.telegram.org/method/messages.editChatPhoto +++ /dev/null @@ -1,203 +0,0 @@ - - - - - messages.editChatPhoto - - - - - - - - - - - - - -
- -
-
-
- -

messages.editChatPhoto

- -

Changes chat photo and sends a service message on it

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.editChatPhoto#35ddd674 chat_id:long photo:InputChatPhoto = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongChat ID
photoInputChatPhotoPhoto to be set
-

Result

-

Returns a messages.StatedMessage object containing a service message sent during an action.

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PHOTO_CROP_SIZE_SMALLPhoto is too small.
400PHOTO_EXT_INVALIDThe extension of the photo is invalid.
400PHOTO_INVALIDPhoto invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.editChatTitle b/data/core.telegram.org/method/messages.editChatTitle deleted file mode 100644 index 1cd755c064..0000000000 --- a/data/core.telegram.org/method/messages.editChatTitle +++ /dev/null @@ -1,193 +0,0 @@ - - - - - messages.editChatTitle - - - - - - - - - - - - - -
- -
-
-
- -

messages.editChatTitle

- -

Chanages chat name and sends a service message on it.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.editChatTitle#73783ffd chat_id:long title:string = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongChat ID
titlestringNew chat name, different from the old one
-

Result

-

Returns a messages.StatedMessage object containing a service message sent during an action.

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400CHAT_TITLE_EMPTYNo chat title provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.editExportedChatInvite b/data/core.telegram.org/method/messages.editExportedChatInvite deleted file mode 100644 index 7b7792f6d0..0000000000 --- a/data/core.telegram.org/method/messages.editExportedChatInvite +++ /dev/null @@ -1,193 +0,0 @@ - - - - - messages.editExportedChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

messages.editExportedChatInvite

- -

Edit an exported chat invite

-

- -
-
messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
-messages.exportedChatInviteReplaced#222600ef invite:ExportedChatInvite new_invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
----functions---
-messages.editExportedChatInvite#2e4ffbe flags:# revoked:flags.2?true peer:InputPeer link:string expire_date:flags.0?int usage_limit:flags.1?int = messages.ExportedChatInvite;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
revokedflags.2?trueWhether to revoke the chat invite
peerInputPeerChat
linkstringInvite link
expire_dateflags.0?intNew expiration date
usage_limitflags.1?intMaximum number of users that can join using this link
-

Result

-

messages.ExportedChatInvite

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.editInlineBotMessage b/data/core.telegram.org/method/messages.editInlineBotMessage deleted file mode 100644 index a7d7203284..0000000000 --- a/data/core.telegram.org/method/messages.editInlineBotMessage +++ /dev/null @@ -1,206 +0,0 @@ - - - - - messages.editInlineBotMessage - - - - - - - - - - - - - -
- -
-
-
- -

messages.editInlineBotMessage

- -

Edit an inline bot message

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.editInlineBotMessage#83557dba flags:# no_webpage:flags.1?true id:InputBotInlineMessageID message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.1?trueDisable webpage preview
idInputBotInlineMessageIDSent inline message ID
messageflags.11?stringMessage
mediaflags.14?InputMediaMedia
reply_markupflags.2?ReplyMarkupReply markup for inline keyboards
entitiesflags.3?Vector<MessageEntity>Message entities for styled text
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MESSAGE_NOT_MODIFIEDThe message text has not changed.
-

Bots can use this method

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.editMessage b/data/core.telegram.org/method/messages.editMessage deleted file mode 100644 index 136fbdb7ab..0000000000 --- a/data/core.telegram.org/method/messages.editMessage +++ /dev/null @@ -1,338 +0,0 @@ - - - - - messages.editMessage - - - - - - - - - - - - - -
- -
-
-
- -

messages.editMessage

- -

Edit message

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.editMessage#48f71778 flags:# no_webpage:flags.1?true peer:InputPeer id:int message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.15?int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.1?trueDisable webpage preview
peerInputPeerWhere was the message sent
idintID of the message to edit
messageflags.11?stringNew message
mediaflags.14?InputMediaNew attached media
reply_markupflags.2?ReplyMarkupReply markup for inline keyboards
entitiesflags.3?Vector<MessageEntity>Message entities for styled text
schedule_dateflags.15?intScheduled message date for scheduled messages
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BUTTON_DATA_INVALIDThe data of one or more of the buttons you provided is invalid.
400BUTTON_TYPE_INVALIDThe type of one or more of the buttons you provided is invalid.
400BUTTON_URL_INVALIDButton URL invalid.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400ENTITIES_TOO_LONGYou provided too many styled message entities.
403INLINE_BOT_REQUIREDOnly the inline bot can edit message.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MEDIA_CAPTION_TOO_LONGThe caption is too long.
400MEDIA_GROUPED_INVALIDYou tried to send media of different types in an album.
400MEDIA_NEW_INVALIDThe new media is invalid.
400MEDIA_PREV_INVALIDPrevious media invalid.
403MESSAGE_AUTHOR_REQUIREDMessage author required.
400MESSAGE_EDIT_TIME_EXPIREDYou can't edit this message anymore, too much time has passed since its creation.
400MESSAGE_EMPTYThe provided message is empty.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MESSAGE_NOT_MODIFIEDThe message text has not changed.
400MESSAGE_TOO_LONGThe provided message is too long.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400REPLY_MARKUP_INVALIDThe provided reply markup is invalid.
400SCHEDULE_DATE_INVALIDInvalid schedule date provided.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
-

Bots can use this method

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

-

Scheduled messages

-

Telegram allows scheduling messages

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.exportChatInvite b/data/core.telegram.org/method/messages.exportChatInvite deleted file mode 100644 index 3ed5b23341..0000000000 --- a/data/core.telegram.org/method/messages.exportChatInvite +++ /dev/null @@ -1,217 +0,0 @@ - - - - - messages.exportChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

messages.exportChatInvite

- -

Export an invite link for a chat

-

- -
-
chatInviteExported#b18105e8 flags:# revoked:flags.0?true permanent:flags.5?true link:string admin_id:long date:int start_date:flags.4?int expire_date:flags.1?int usage_limit:flags.2?int usage:flags.3?int = ExportedChatInvite;
----functions---
-messages.exportChatInvite#14b9bcd7 flags:# legacy_revoke_permanent:flags.2?true peer:InputPeer expire_date:flags.0?int usage_limit:flags.1?int = ExportedChatInvite;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
legacy_revoke_permanentflags.2?trueLegacy flag, reproducing legacy behavior of this method: if set, revokes all previous links before creating a new one. Kept for bot API BC, should not be used by modern clients.
peerInputPeerChat
expire_dateflags.0?intExpiration date
usage_limitflags.1?intMaximum number of users that can join using this link
-

Result

-

ExportedChatInvite

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400EXPIRE_DATE_INVALIDThe specified expiration date is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USAGE_LIMIT_INVALIDThe specified usage limit is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.faveSticker b/data/core.telegram.org/method/messages.faveSticker deleted file mode 100644 index 6e27b088c1..0000000000 --- a/data/core.telegram.org/method/messages.faveSticker +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.faveSticker - - - - - - - - - - - - - -
- -
-
-
- -

messages.faveSticker

- -

Mark a sticker as favorite

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.faveSticker#b9ffc55b id:InputDocument unfave:Bool = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idInputDocumentSticker to mark as favorite
unfaveBoolUnfavorite
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400STICKER_ID_INVALIDThe provided sticker ID is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.forwardMessage b/data/core.telegram.org/method/messages.forwardMessage deleted file mode 100644 index fd72ffa74f..0000000000 --- a/data/core.telegram.org/method/messages.forwardMessage +++ /dev/null @@ -1,177 +0,0 @@ - - - - - messages.forwardMessage - - - - - - - - - - - - - -
- -
-
-
- -

messages.forwardMessage

- -

Forwards single messages.

-

{schema}

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerUser or chat where a message will be forwarded
idintForwarded message ID
random_idlongUnique client message ID required to prevent message resending
-

Result

-

messages.StatedMessage

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid
400MESSAGE_ID_INVALIDThe provided message id is invalid
400PEER_ID_INVALIDThe provided peer id is invalid
400YOU_BLOCKED_USERYou blocked this user
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.forwardMessages b/data/core.telegram.org/method/messages.forwardMessages deleted file mode 100644 index 35fe91fc45..0000000000 --- a/data/core.telegram.org/method/messages.forwardMessages +++ /dev/null @@ -1,363 +0,0 @@ - - - - - messages.forwardMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.forwardMessages

- -

Forwards messages by their IDs.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.forwardMessages#d9fee60e flags:# silent:flags.5?true background:flags.6?true with_my_score:flags.8?true drop_author:flags.11?true drop_media_captions:flags.12?true from_peer:InputPeer id:Vector<int> random_id:Vector<long> to_peer:InputPeer schedule_date:flags.10?int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.5?trueWhether to send messages silently (no notification will be triggered on the destination clients)
backgroundflags.6?trueWhether to send the message in background
with_my_scoreflags.8?trueWhen forwarding games, whether to include your score in the game
drop_authorflags.11?trueWhether to forward messages without quoting the original author
drop_media_captionsflags.12?trueWhether to strip captions from media
from_peerInputPeerSource of messages
idVector<int>IDs of messages
random_idVector<long>Random ID to prevent resending of messages
to_peerInputPeerDestination peer
schedule_dateflags.10?intScheduled message date for scheduled messages
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BROADCAST_PUBLIC_VOTERS_FORBIDDENYou can't forward polls with public voters.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_RESTRICTEDYou can't send messages in this chat, you were restricted.
403CHAT_SEND_GAME_FORBIDDENYou can't send a game to this chat.
403CHAT_SEND_GIFS_FORBIDDENYou can't send gifs in this chat.
403CHAT_SEND_MEDIA_FORBIDDENYou can't send media in this chat.
403CHAT_SEND_POLL_FORBIDDENYou can't send polls in this chat.
403CHAT_SEND_STICKERS_FORBIDDENYou can't send stickers in this chat.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400GROUPED_MEDIA_INVALIDInvalid grouped media.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MEDIA_EMPTYThe provided media object is invalid.
400MESSAGE_IDS_EMPTYNo message ids were provided.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
420P0NY_FLOODWAIT 
400PEER_ID_INVALIDThe provided peer id is invalid.
400RANDOM_ID_INVALIDA provided random ID is invalid.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
400SLOWMODE_MULTI_MSGS_DISABLEDSlowmode is enabled, you cannot forward multiple messages to this group.
420SLOWMODE_WAIT_XSlowmode is enabled in this chat: you must wait for the specified number of seconds before sending another message to the chat.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400USER_IS_BLOCKEDYou were blocked by this user.
400USER_IS_BOTBots can't send messages to other bots.
400YOU_BLOCKED_USERYou blocked this user.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getAdminsWithInvites b/data/core.telegram.org/method/messages.getAdminsWithInvites deleted file mode 100644 index 26e37e4b8c..0000000000 --- a/data/core.telegram.org/method/messages.getAdminsWithInvites +++ /dev/null @@ -1,149 +0,0 @@ - - - - - messages.getAdminsWithInvites - - - - - - - - - - - - - -
- -
-
-
- -

messages.getAdminsWithInvites

- -

Get info about chat invites generated by admins.

-

- -
-
messages.chatAdminsWithInvites#b69b72d7 admins:Vector<ChatAdminWithInvites> users:Vector<User> = messages.ChatAdminsWithInvites;
----functions---
-messages.getAdminsWithInvites#3920e6ef peer:InputPeer = messages.ChatAdminsWithInvites;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerChat
-

Result

-

messages.ChatAdminsWithInvites

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getAllChats b/data/core.telegram.org/method/messages.getAllChats deleted file mode 100644 index c7d25cad86..0000000000 --- a/data/core.telegram.org/method/messages.getAllChats +++ /dev/null @@ -1,150 +0,0 @@ - - - - - messages.getAllChats - - - - - - - - - - - - - -
- -
-
-
- -

messages.getAllChats

- -

Get all chats, channels and supergroups

-

- -
-
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
-messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
----functions---
-messages.getAllChats#875f74be except_ids:Vector<long> = messages.Chats;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
except_idsVector<long>Except these chats/channels/supergroups
-

Result

-

messages.Chats

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getAllDrafts b/data/core.telegram.org/method/messages.getAllDrafts deleted file mode 100644 index 0b41aefe85..0000000000 --- a/data/core.telegram.org/method/messages.getAllDrafts +++ /dev/null @@ -1,143 +0,0 @@ - - - - - messages.getAllDrafts - - - - - - - - - - - - - -
- -
-
-
- -

messages.getAllDrafts

- -

Save get all message drafts.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.getAllDrafts#6a3f8d65 = Updates;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Updates, contains all the latest updateDraftMessage updates related to all chats with drafts.

-

Related pages

-

Message drafts

-

How to handle message drafts

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getAllStickers b/data/core.telegram.org/method/messages.getAllStickers deleted file mode 100644 index a84ad9cb14..0000000000 --- a/data/core.telegram.org/method/messages.getAllStickers +++ /dev/null @@ -1,153 +0,0 @@ - - - - - messages.getAllStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.getAllStickers

- -

Get all installed stickers

-

- -
-
messages.allStickersNotModified#e86602c3 = messages.AllStickers;
-messages.allStickers#cdbbcebb hash:long sets:Vector<StickerSet> = messages.AllStickers;
----functions---
-messages.getAllStickers#b8a0a1a8 hash:long = messages.AllStickers;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
-

Result

-

messages.AllStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getArchivedStickers b/data/core.telegram.org/method/messages.getArchivedStickers deleted file mode 100644 index 81acf27c79..0000000000 --- a/data/core.telegram.org/method/messages.getArchivedStickers +++ /dev/null @@ -1,167 +0,0 @@ - - - - - messages.getArchivedStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.getArchivedStickers

- -

Get all archived stickers

-

- -
-
messages.archivedStickers#4fcba9c8 count:int sets:Vector<StickerSetCovered> = messages.ArchivedStickers;
----functions---
-messages.getArchivedStickers#57f17692 flags:# masks:flags.0?true offset_id:long limit:int = messages.ArchivedStickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
masksflags.0?trueGet mask stickers
offset_idlongOffsets for pagination, for more info click here
limitintMaximum number of results to return, see pagination
-

Result

-

messages.ArchivedStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getAttachedStickers b/data/core.telegram.org/method/messages.getAttachedStickers deleted file mode 100644 index f5bde49924..0000000000 --- a/data/core.telegram.org/method/messages.getAttachedStickers +++ /dev/null @@ -1,148 +0,0 @@ - - - - - messages.getAttachedStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.getAttachedStickers

- -

Get stickers attached to a photo or video

-

- -
-
---functions---
-messages.getAttachedStickers#cc5b67cc media:InputStickeredMedia = Vector<StickerSetCovered>;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
mediaInputStickeredMediaStickered media
-

Result

-

Vector<StickerSetCovered>

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getBotCallbackAnswer b/data/core.telegram.org/method/messages.getBotCallbackAnswer deleted file mode 100644 index 47db722c11..0000000000 --- a/data/core.telegram.org/method/messages.getBotCallbackAnswer +++ /dev/null @@ -1,226 +0,0 @@ - - - - - messages.getBotCallbackAnswer - - - - - - - - - - - - - -
- -
-
-
- -

messages.getBotCallbackAnswer

- -

Press an inline callback button and get a callback answer from the bot

-

- -
-
messages.botCallbackAnswer#36585ea4 flags:# alert:flags.1?true has_url:flags.3?true native_ui:flags.4?true message:flags.0?string url:flags.2?string cache_time:int = messages.BotCallbackAnswer;
----functions---
-messages.getBotCallbackAnswer#9342ca07 flags:# game:flags.1?true peer:InputPeer msg_id:int data:flags.0?bytes password:flags.2?InputCheckPasswordSRP = messages.BotCallbackAnswer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
gameflags.1?trueWhether this is a "play game" button
peerInputPeerWhere was the inline keyboard sent
msg_idintID of the Message with the inline keyboard
dataflags.0?bytesCallback data
passwordflags.2?InputCheckPasswordSRPFor buttons requiring you to verify your identity with your 2FA password, the SRP payload generated using SRP.
-

Result

-

messages.BotCallbackAnswer

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOT_RESPONSE_TIMEOUTA timeout occurred while fetching data from the bot.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400DATA_INVALIDEncrypted data invalid.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
-503TimeoutTimeout while fetching data.
-

Related pages

-

keyboardButtonCallback

-

Callback button

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getChatInviteImporters b/data/core.telegram.org/method/messages.getChatInviteImporters deleted file mode 100644 index 7ee6e1e7b3..0000000000 --- a/data/core.telegram.org/method/messages.getChatInviteImporters +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.getChatInviteImporters - - - - - - - - - - - - - -
- -
-
-
- -

messages.getChatInviteImporters

- -

Get info about the users that joined the chat using a specific chat invite

-

- -
-
messages.chatInviteImporters#81b6b00a count:int importers:Vector<ChatInviteImporter> users:Vector<User> = messages.ChatInviteImporters;
----functions---
-messages.getChatInviteImporters#26fb7289 peer:InputPeer link:string offset_date:int offset_user:InputUser limit:int = messages.ChatInviteImporters;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerChat
linkstringInvite link
offset_dateintOffsets for pagination, for more info click here
offset_userInputUserUser ID for pagination
limitintMaximum number of results to return, see pagination
-

Result

-

messages.ChatInviteImporters

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getChats b/data/core.telegram.org/method/messages.getChats deleted file mode 100644 index a37b1501e6..0000000000 --- a/data/core.telegram.org/method/messages.getChats +++ /dev/null @@ -1,173 +0,0 @@ - - - - - messages.getChats - - - - - - - - - - - - - -
- -
-
-
- -

messages.getChats

- -

Returns chat basic info on their IDs.

-

- -
-
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
-messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
----functions---
-messages.getChats#49e9528f id:Vector<long> = messages.Chats;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idVector<long>List of chat IDs
-

Result

-

messages.Chats

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getCommonChats b/data/core.telegram.org/method/messages.getCommonChats deleted file mode 100644 index 3cdef9f345..0000000000 --- a/data/core.telegram.org/method/messages.getCommonChats +++ /dev/null @@ -1,185 +0,0 @@ - - - - - messages.getCommonChats - - - - - - - - - - - - - -
- -
-
-
- -

messages.getCommonChats

- -

Get chats in common with a user

-

- -
-
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
-messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
----functions---
-messages.getCommonChats#e40ca104 user_id:InputUser max_id:long limit:int = messages.Chats;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idInputUserUser ID
max_idlongMaximum ID of chat to return (see pagination)
limitintMaximum number of results to return, see pagination
-

Result

-

messages.Chats

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MSG_ID_INVALIDInvalid message ID provided.
400USER_ID_INVALIDThe provided user ID is invalid.
-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getDhConfig b/data/core.telegram.org/method/messages.getDhConfig deleted file mode 100644 index b9adc1ca90..0000000000 --- a/data/core.telegram.org/method/messages.getDhConfig +++ /dev/null @@ -1,175 +0,0 @@ - - - - - messages.getDhConfig - - - - - - - - - - - - - -
- -
-
-
- -

messages.getDhConfig

- -

Returns configuration parameters for Diffie-Hellman key generation. Can also return a random sequence of bytes of required length.

-

- -
-
messages.dhConfigNotModified#c0e24635 random:bytes = messages.DhConfig;
-messages.dhConfig#2c221edd g:int p:bytes version:int random:bytes = messages.DhConfig;
----functions---
-messages.getDhConfig#26cf8950 version:int random_length:int = messages.DhConfig;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
versionintValue of the version parameter from messages.dhConfig, avialable at the client
random_lengthintLength of the required random sequence
-

Result

-

messages.DhConfig

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400RANDOM_LENGTH_INVALIDRandom length invalid.
-

Related pages

-

messages.dhConfig

-

New set of configuring parameters.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getDialogFilters b/data/core.telegram.org/method/messages.getDialogFilters deleted file mode 100644 index cd4956007c..0000000000 --- a/data/core.telegram.org/method/messages.getDialogFilters +++ /dev/null @@ -1,136 +0,0 @@ - - - - - messages.getDialogFilters - - - - - - - - - - - - - -
- -
-
-
- -

messages.getDialogFilters

- -

Get folders

-

- -
-
---functions---
-messages.getDialogFilters#f19ed96d = Vector<DialogFilter>;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Vector<DialogFilter>

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getDialogUnreadMarks b/data/core.telegram.org/method/messages.getDialogUnreadMarks deleted file mode 100644 index 7cf19f4084..0000000000 --- a/data/core.telegram.org/method/messages.getDialogUnreadMarks +++ /dev/null @@ -1,133 +0,0 @@ - - - - - messages.getDialogUnreadMarks - - - - - - - - - - - - - -
- -
-
-
- -

messages.getDialogUnreadMarks

- -

Get dialogs manually marked as unread

-

- -
-
---functions---
-messages.getDialogUnreadMarks#22e24e22 = Vector<DialogPeer>;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Vector<DialogPeer>

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getDialogs b/data/core.telegram.org/method/messages.getDialogs deleted file mode 100644 index 7207b94946..0000000000 --- a/data/core.telegram.org/method/messages.getDialogs +++ /dev/null @@ -1,213 +0,0 @@ - - - - - messages.getDialogs - - - - - - - - - - - - - -
- -
-
-
- -

messages.getDialogs

- -

Returns the current user dialog list.

-

- -
-
messages.dialogs#15ba6c40 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;
-messages.dialogsSlice#71e094f3 count:int dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;
-messages.dialogsNotModified#f0e3e596 count:int = messages.Dialogs;
----functions---
-messages.getDialogs#a0f4cb4f flags:# exclude_pinned:flags.0?true folder_id:flags.1?int offset_date:int offset_id:int offset_peer:InputPeer limit:int hash:long = messages.Dialogs;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
exclude_pinnedflags.0?trueExclude pinned dialogs
folder_idflags.1?intPeer folder ID, for more info click here
offset_dateintOffsets for pagination, for more info click here
offset_idintOffsets for pagination, for more info click here
offset_peerInputPeerOffset peer for pagination
limitintNumber of list elements to be returned
hashlongHash for pagination, for more info click here
-

Result

-

messages.Dialogs

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400FOLDER_ID_INVALIDInvalid folder ID.
400OFFSET_PEER_ID_INVALIDThe provided offset peer is invalid.
-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getDiscussionMessage b/data/core.telegram.org/method/messages.getDiscussionMessage deleted file mode 100644 index cf281a5b58..0000000000 --- a/data/core.telegram.org/method/messages.getDiscussionMessage +++ /dev/null @@ -1,183 +0,0 @@ - - - - - messages.getDiscussionMessage - - - - - - - - - - - - - -
- -
-
-
- -

messages.getDiscussionMessage

- -

Get discussion message from the associated discussion group of a channel to show it on top of the comment section, without actually joining the group

-

- -
-
messages.discussionMessage#a6341782 flags:# messages:Vector<Message> max_id:flags.0?int read_inbox_max_id:flags.1?int read_outbox_max_id:flags.2?int unread_count:int chats:Vector<Chat> users:Vector<User> = messages.DiscussionMessage;
----functions---
-messages.getDiscussionMessage#446972fd peer:InputPeer msg_id:int = messages.DiscussionMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerChannel ID
msg_idintMessage ID
-

Result

-

messages.DiscussionMessage

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

-

Discussion groups

-

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getDocumentByHash b/data/core.telegram.org/method/messages.getDocumentByHash deleted file mode 100644 index e74833bb5d..0000000000 --- a/data/core.telegram.org/method/messages.getDocumentByHash +++ /dev/null @@ -1,178 +0,0 @@ - - - - - messages.getDocumentByHash - - - - - - - - - - - - - -
- -
-
-
- -

messages.getDocumentByHash

- -

Get a document by its SHA256 hash, mainly used for gifs

-

- -
-
documentEmpty#36f8c871 id:long = Document;
-document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
----functions---
-messages.getDocumentByHash#338e2464 sha256:bytes size:int mime_type:string = Document;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
sha256bytesSHA256 of file
sizeintSize of the file in bytes
mime_typestringMime type
-

Result

-

Document

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400SHA256_HASH_INVALIDThe provided SHA256 hash is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getEmojiKeywords b/data/core.telegram.org/method/messages.getEmojiKeywords deleted file mode 100644 index 6eb0c1c9c3..0000000000 --- a/data/core.telegram.org/method/messages.getEmojiKeywords +++ /dev/null @@ -1,149 +0,0 @@ - - - - - messages.getEmojiKeywords - - - - - - - - - - - - - -
- -
-
-
- -

messages.getEmojiKeywords

- -

Get localized emoji keywords

-

- -
-
emojiKeywordsDifference#5cc761bd lang_code:string from_version:int version:int keywords:Vector<EmojiKeyword> = EmojiKeywordsDifference;
----functions---
-messages.getEmojiKeywords#35a0e062 lang_code:string = EmojiKeywordsDifference;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
lang_codestringLanguage code
-

Result

-

EmojiKeywordsDifference

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getEmojiKeywordsDifference b/data/core.telegram.org/method/messages.getEmojiKeywordsDifference deleted file mode 100644 index d2a6bd18dd..0000000000 --- a/data/core.telegram.org/method/messages.getEmojiKeywordsDifference +++ /dev/null @@ -1,154 +0,0 @@ - - - - - messages.getEmojiKeywordsDifference - - - - - - - - - - - - - -
- -
-
-
- -

messages.getEmojiKeywordsDifference

- -

Get changed emoji keywords

-

- -
-
emojiKeywordsDifference#5cc761bd lang_code:string from_version:int version:int keywords:Vector<EmojiKeyword> = EmojiKeywordsDifference;
----functions---
-messages.getEmojiKeywordsDifference#1508b6af lang_code:string from_version:int = EmojiKeywordsDifference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
lang_codestringLanguage code
from_versionintPrevious emoji keyword localization version
-

Result

-

EmojiKeywordsDifference

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getEmojiKeywordsLanguages b/data/core.telegram.org/method/messages.getEmojiKeywordsLanguages deleted file mode 100644 index 7059953ea0..0000000000 --- a/data/core.telegram.org/method/messages.getEmojiKeywordsLanguages +++ /dev/null @@ -1,148 +0,0 @@ - - - - - messages.getEmojiKeywordsLanguages - - - - - - - - - - - - - -
- -
-
-
- -

messages.getEmojiKeywordsLanguages

- -

Get info about an emoji keyword localization

-

- -
-
---functions---
-messages.getEmojiKeywordsLanguages#4e9963b2 lang_codes:Vector<string> = Vector<EmojiLanguage>;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
lang_codesVector<string>Language codes
-

Result

-

Vector<EmojiLanguage>

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getEmojiURL b/data/core.telegram.org/method/messages.getEmojiURL deleted file mode 100644 index f89cca4caf..0000000000 --- a/data/core.telegram.org/method/messages.getEmojiURL +++ /dev/null @@ -1,149 +0,0 @@ - - - - - messages.getEmojiURL - - - - - - - - - - - - - -
- -
-
-
- -

messages.getEmojiURL

- -

Returns an HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation

-

- -
-
emojiURL#a575739d url:string = EmojiURL;
----functions---
-messages.getEmojiURL#d5b10c26 lang_code:string = EmojiURL;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
lang_codestringLanguage code for which the emoji replacements will be suggested
-

Result

-

EmojiURL

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getExportedChatInvite b/data/core.telegram.org/method/messages.getExportedChatInvite deleted file mode 100644 index 26aa13353f..0000000000 --- a/data/core.telegram.org/method/messages.getExportedChatInvite +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.getExportedChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

messages.getExportedChatInvite

- -

Get info about a chat invite

-

- -
-
messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
-messages.exportedChatInviteReplaced#222600ef invite:ExportedChatInvite new_invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
----functions---
-messages.getExportedChatInvite#73746f5c peer:InputPeer link:string = messages.ExportedChatInvite;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerChat
linkstringInvite link
-

Result

-

messages.ExportedChatInvite

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getExportedChatInvites b/data/core.telegram.org/method/messages.getExportedChatInvites deleted file mode 100644 index 381925dcb6..0000000000 --- a/data/core.telegram.org/method/messages.getExportedChatInvites +++ /dev/null @@ -1,182 +0,0 @@ - - - - - messages.getExportedChatInvites - - - - - - - - - - - - - -
- -
-
-
- -

messages.getExportedChatInvites

- -

Get info about the chat invites of a specific chat

-

- -
-
messages.exportedChatInvites#bdc62dcc count:int invites:Vector<ExportedChatInvite> users:Vector<User> = messages.ExportedChatInvites;
----functions---
-messages.getExportedChatInvites#a2b5a3f6 flags:# revoked:flags.3?true peer:InputPeer admin_id:InputUser offset_date:flags.2?int offset_link:flags.2?string limit:int = messages.ExportedChatInvites;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
revokedflags.3?trueWhether to fetch revoked chat invites
peerInputPeerChat
admin_idInputUserWhether to only fetch chat invites from this admin
offset_dateflags.2?intOffsets for pagination, for more info click here
offset_linkflags.2?stringOffsets for pagination, for more info click here
limitintMaximum number of results to return, see pagination
-

Result

-

messages.ExportedChatInvites

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getFeaturedStickers b/data/core.telegram.org/method/messages.getFeaturedStickers deleted file mode 100644 index f9d1ae7496..0000000000 --- a/data/core.telegram.org/method/messages.getFeaturedStickers +++ /dev/null @@ -1,153 +0,0 @@ - - - - - messages.getFeaturedStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.getFeaturedStickers

- -

Get featured stickers

-

- -
-
messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;
-messages.featuredStickers#84c02310 hash:long count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;
----functions---
-messages.getFeaturedStickers#64780b14 hash:long = messages.FeaturedStickers;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
-

Result

-

messages.FeaturedStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getGameHighScores b/data/core.telegram.org/method/messages.getGameHighScores deleted file mode 100644 index 6ba307d512..0000000000 --- a/data/core.telegram.org/method/messages.getGameHighScores +++ /dev/null @@ -1,187 +0,0 @@ - - - - - messages.getGameHighScores - - - - - - - - - - - - - -
- -
-
-
- -

messages.getGameHighScores

- -

Get highscores of a game

-

- -
-
messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;
----functions---
-messages.getGameHighScores#e822649d peer:InputPeer id:int user_id:InputUser = messages.HighScores;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerWhere was the game sent
idintID of message with game media attachment
user_idInputUserGet high scores made by a certain user
-

Result

-

messages.HighScores

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USER_BOT_REQUIREDThis method can only be called by a bot.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getInlineBotResults b/data/core.telegram.org/method/messages.getInlineBotResults deleted file mode 100644 index 160d8caa5c..0000000000 --- a/data/core.telegram.org/method/messages.getInlineBotResults +++ /dev/null @@ -1,226 +0,0 @@ - - - - - messages.getInlineBotResults - - - - - - - - - - - - - -
- -
-
-
- -

messages.getInlineBotResults

- -

Query an inline bot

-

- -
-
messages.botResults#947ca848 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;
----functions---
-messages.getInlineBotResults#514e999d flags:# bot:InputUser peer:InputPeer geo_point:flags.0?InputGeoPoint query:string offset:string = messages.BotResults;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
botInputUserThe bot to query
peerInputPeerThe currently opened chat
geo_pointflags.0?InputGeoPointThe geolocation, if requested
querystringThe query
offsetstringThe offset within the results, will be passed directly as-is to the bot.
-

Result

-

messages.BotResults

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOT_INLINE_DISABLEDThis bot can't be used in inline mode.
400BOT_INVALIDThis is not a valid bot.
400BOT_RESPONSE_TIMEOUTA timeout occurred while fetching data from the bot.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
-503TimeoutTimeout while fetching data.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getInlineGameHighScores b/data/core.telegram.org/method/messages.getInlineGameHighScores deleted file mode 100644 index a8fb43a61e..0000000000 --- a/data/core.telegram.org/method/messages.getInlineGameHighScores +++ /dev/null @@ -1,177 +0,0 @@ - - - - - messages.getInlineGameHighScores - - - - - - - - - - - - - -
- -
-
-
- -

messages.getInlineGameHighScores

- -

Get highscores of a game sent using an inline bot

-

- -
-
messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;
----functions---
-messages.getInlineGameHighScores#f635e1b id:InputBotInlineMessageID user_id:InputUser = messages.HighScores;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idInputBotInlineMessageIDID of inline message
user_idInputUserGet high scores of a certain user
-

Result

-

messages.HighScores

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400USER_BOT_REQUIREDThis method can only be called by a bot.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getMaskStickers b/data/core.telegram.org/method/messages.getMaskStickers deleted file mode 100644 index 59a25592ce..0000000000 --- a/data/core.telegram.org/method/messages.getMaskStickers +++ /dev/null @@ -1,153 +0,0 @@ - - - - - messages.getMaskStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.getMaskStickers

- -

Get installed mask stickers

-

- -
-
messages.allStickersNotModified#e86602c3 = messages.AllStickers;
-messages.allStickers#cdbbcebb hash:long sets:Vector<StickerSet> = messages.AllStickers;
----functions---
-messages.getMaskStickers#640f82b8 hash:long = messages.AllStickers;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
-

Result

-

messages.AllStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getMessageEditData b/data/core.telegram.org/method/messages.getMessageEditData deleted file mode 100644 index a740752192..0000000000 --- a/data/core.telegram.org/method/messages.getMessageEditData +++ /dev/null @@ -1,186 +0,0 @@ - - - - - messages.getMessageEditData - - - - - - - - - - - - - -
- -
-
-
- -

messages.getMessageEditData

- -

Find out if a media message's caption can be edited

-

- -
-
messages.messageEditData#26b5dde6 flags:# caption:flags.0?true = messages.MessageEditData;
----functions---
-messages.getMessageEditData#fda68d36 peer:InputPeer id:int = messages.MessageEditData;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer where the media was sent
idintID of message
-

Result

-

messages.MessageEditData

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403MESSAGE_AUTHOR_REQUIREDMessage author required.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getMessageReactionsList b/data/core.telegram.org/method/messages.getMessageReactionsList deleted file mode 100644 index ef469a7f4c..0000000000 --- a/data/core.telegram.org/method/messages.getMessageReactionsList +++ /dev/null @@ -1,178 +0,0 @@ - - - - - messages.getMessageReactionsList - - - - - - - - - - - - - -
- -
-
-
- -

messages.getMessageReactionsList

- -

Get full message reaction list

-

- -
-
 Method schema is available as of layer 136. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerPeer
idintMessage ID
reactionflags.0?stringGet only reactions of this type (UTF8 emoji)
offsetflags.1?stringOffset (typically taken from the next_offset field of the returned MessageReactionsList)
limitintMaximum number of results to return, see pagination
-

Result

-

MessageReactionsList

-

Bots can use this method

-

Related pages

-

MessageReactionsList

-

List of message reactions

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getMessageReadParticipants b/data/core.telegram.org/method/messages.getMessageReadParticipants deleted file mode 100644 index 2b44d3f516..0000000000 --- a/data/core.telegram.org/method/messages.getMessageReadParticipants +++ /dev/null @@ -1,173 +0,0 @@ - - - - - messages.getMessageReadParticipants - - - - - - - - - - - - - -
- -
-
-
- -

messages.getMessageReadParticipants

- -

Get which users read a specific message: only available for groups and supergroups with less than chat_read_mark_size_threshold members, read receipts will be stored for chat_read_mark_expire_period seconds after the message was sent, see client configuration for more info ».

-

- -
-
---functions---
-messages.getMessageReadParticipants#2c6f97b7 peer:InputPeer msg_id:int = Vector<long>;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerDialog
msg_idintMessage ID
-

Result

-

Vector<long>

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_TOO_BIGThis method is not available for groups with more than chat_read_mark_size_threshold members, see client configuration ».
-

Related pages

-

Client configuration

-

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getMessages b/data/core.telegram.org/method/messages.getMessages deleted file mode 100644 index 59ee1f69d4..0000000000 --- a/data/core.telegram.org/method/messages.getMessages +++ /dev/null @@ -1,153 +0,0 @@ - - - - - messages.getMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.getMessages

- -

Returns the list of messages by their IDs.

-

- -
-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
----functions---
-messages.getMessages#63c66506 id:Vector<InputMessage> = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idVector<InputMessage>Message ID list
-

Result

-

messages.Messages

-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getMessagesReactions b/data/core.telegram.org/method/messages.getMessagesReactions deleted file mode 100644 index 2f5c3d4892..0000000000 --- a/data/core.telegram.org/method/messages.getMessagesReactions +++ /dev/null @@ -1,153 +0,0 @@ - - - - - messages.getMessagesReactions - - - - - - - - - - - - - -
- -
-
-
- -

messages.getMessagesReactions

- -

Get message reactions

-

- -
-
 Method schema is available as of layer 136. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
idVector<int>Message IDs
-

Result

-

Updates

-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getMessagesViews b/data/core.telegram.org/method/messages.getMessagesViews deleted file mode 100644 index a2ab25b93d..0000000000 --- a/data/core.telegram.org/method/messages.getMessagesViews +++ /dev/null @@ -1,199 +0,0 @@ - - - - - messages.getMessagesViews - - - - - - - - - - - - - -
- -
-
-
- -

messages.getMessagesViews

- -

Get and increase the view counter of a message sent or forwarded from a channel

-

- -
-
messages.messageViews#b6c4f543 views:Vector<MessageViews> chats:Vector<Chat> users:Vector<User> = messages.MessageViews;
----functions---
-messages.getMessagesViews#5784d3e1 peer:InputPeer id:Vector<int> increment:Bool = messages.MessageViews;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer where the message was found
idVector<int>ID of message
incrementBoolWhether to mark the message as viewed and increment the view counter
-

Result

-

Vector<int>

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getOldFeaturedStickers b/data/core.telegram.org/method/messages.getOldFeaturedStickers deleted file mode 100644 index 1df560d371..0000000000 --- a/data/core.telegram.org/method/messages.getOldFeaturedStickers +++ /dev/null @@ -1,163 +0,0 @@ - - - - - messages.getOldFeaturedStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.getOldFeaturedStickers

- -

Method for fetching previously featured stickers

-

- -
-
messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;
-messages.featuredStickers#84c02310 hash:long count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;
----functions---
-messages.getOldFeaturedStickers#7ed094a1 offset:int limit:int hash:long = messages.FeaturedStickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset
limitintMaximum number of results to return, see pagination
hashlongHash for pagination, for more info click here
-

Result

-

messages.FeaturedStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getOnlines b/data/core.telegram.org/method/messages.getOnlines deleted file mode 100644 index 8ab9c93408..0000000000 --- a/data/core.telegram.org/method/messages.getOnlines +++ /dev/null @@ -1,171 +0,0 @@ - - - - - messages.getOnlines - - - - - - - - - - - - - -
- -
-
-
- -

messages.getOnlines

- -

Get count of online users in a chat

-

- -
-
chatOnlines#f041e250 onlines:int = ChatOnlines;
----functions---
-messages.getOnlines#6e2be050 peer:InputPeer = ChatOnlines;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat
-

Result

-

ChatOnlines

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getPeerDialogs b/data/core.telegram.org/method/messages.getPeerDialogs deleted file mode 100644 index 35bc3b3a15..0000000000 --- a/data/core.telegram.org/method/messages.getPeerDialogs +++ /dev/null @@ -1,181 +0,0 @@ - - - - - messages.getPeerDialogs - - - - - - - - - - - - - -
- -
-
-
- -

messages.getPeerDialogs

- -

Get dialog info of specified peers

-

- -
-
messages.peerDialogs#3371c354 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> state:updates.State = messages.PeerDialogs;
----functions---
-messages.getPeerDialogs#e470bcfd peers:Vector<InputDialogPeer> = messages.PeerDialogs;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peersVector<InputDialogPeer>Peers
-

Result

-

messages.PeerDialogs

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getPeerSettings b/data/core.telegram.org/method/messages.getPeerSettings deleted file mode 100644 index 91606c866b..0000000000 --- a/data/core.telegram.org/method/messages.getPeerSettings +++ /dev/null @@ -1,171 +0,0 @@ - - - - - messages.getPeerSettings - - - - - - - - - - - - - -
- -
-
-
- -

messages.getPeerSettings

- -

Get peer settings

-

- -
-
peerSettings#733f2961 flags:# report_spam:flags.0?true add_contact:flags.1?true block_contact:flags.2?true share_contact:flags.3?true need_contacts_exception:flags.4?true report_geo:flags.5?true autoarchived:flags.7?true invite_members:flags.8?true geo_distance:flags.6?int = PeerSettings;
----functions---
-messages.getPeerSettings#3672e09c peer:InputPeer = PeerSettings;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe peer
-

Result

-

PeerSettings

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getPinnedDialogs b/data/core.telegram.org/method/messages.getPinnedDialogs deleted file mode 100644 index 64f6c1867a..0000000000 --- a/data/core.telegram.org/method/messages.getPinnedDialogs +++ /dev/null @@ -1,169 +0,0 @@ - - - - - messages.getPinnedDialogs - - - - - - - - - - - - - -
- -
-
-
- -

messages.getPinnedDialogs

- -

Get pinned dialogs

-

- -
-
messages.peerDialogs#3371c354 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> state:updates.State = messages.PeerDialogs;
----functions---
-messages.getPinnedDialogs#d6b94df2 folder_id:int = messages.PeerDialogs;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
folder_idintPeer folder ID, for more info click here
-

Result

-

messages.PeerDialogs

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400FOLDER_ID_INVALIDInvalid folder ID.
-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getPollResults b/data/core.telegram.org/method/messages.getPollResults deleted file mode 100644 index df8aae8cbf..0000000000 --- a/data/core.telegram.org/method/messages.getPollResults +++ /dev/null @@ -1,177 +0,0 @@ - - - - - messages.getPollResults - - - - - - - - - - - - - -
- -
-
-
- -

messages.getPollResults

- -

Get poll results

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.getPollResults#73bb643b peer:InputPeer msg_id:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer where the poll was found
msg_idintMessage ID of poll message
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getPollVotes b/data/core.telegram.org/method/messages.getPollVotes deleted file mode 100644 index 0d08473f1c..0000000000 --- a/data/core.telegram.org/method/messages.getPollVotes +++ /dev/null @@ -1,204 +0,0 @@ - - - - - messages.getPollVotes - - - - - - - - - - - - - -
- -
-
-
- -

messages.getPollVotes

- -

Get poll results for non-anonymous polls

-

- -
-
messages.votesList#823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList;
----functions---
-messages.getPollVotes#b86e380e flags:# peer:InputPeer id:int option:flags.0?bytes offset:flags.1?string limit:int = messages.VotesList;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerChat where the poll was sent
idintMessage ID
optionflags.0?bytesGet only results for the specified poll option
offsetflags.1?stringOffset for results, taken from the next_offset field of messages.votesList, initially an empty string.
Note: if no more results are available, the method call will return an empty next_offset; thus, avoid providing the next_offset returned in messages.votesList if it is empty, to avoid an infinite loop.
limitintNumber of results to return
-

Result

-

messages.VotesList

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
403BROADCAST_FORBIDDENParticipants of polls in channels should stay anonymous.
400MSG_ID_INVALIDInvalid message ID provided.
403POLL_VOTE_REQUIREDCast a vote in the poll before calling this method.
-

Related pages

-

messages.votesList

-

How users voted in a poll

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getRecentLocations b/data/core.telegram.org/method/messages.getRecentLocations deleted file mode 100644 index 2150b8166e..0000000000 --- a/data/core.telegram.org/method/messages.getRecentLocations +++ /dev/null @@ -1,165 +0,0 @@ - - - - - messages.getRecentLocations - - - - - - - - - - - - - -
- -
-
-
- -

messages.getRecentLocations

- -

Get live location history of a certain user

-

- -
-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
----functions---
-messages.getRecentLocations#702a40e0 peer:InputPeer limit:int hash:long = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerUser
limitintMaximum number of results to return, see pagination
hashlongHash for pagination, for more info click here
-

Result

-

messages.Messages

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getReplies b/data/core.telegram.org/method/messages.getReplies deleted file mode 100644 index a6af9cba26..0000000000 --- a/data/core.telegram.org/method/messages.getReplies +++ /dev/null @@ -1,217 +0,0 @@ - - - - - messages.getReplies - - - - - - - - - - - - - -
- -
-
-
- -

messages.getReplies

- -

Get messages in a reply thread

-

- -
-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
----functions---
-messages.getReplies#22ddd30c peer:InputPeer msg_id:int offset_id:int offset_date:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
msg_idintMessage ID
offset_idintOffsets for pagination, for more info click here
offset_dateintOffsets for pagination, for more info click here
add_offsetintOffsets for pagination, for more info click here
limitintMaximum number of results to return, see pagination
max_idintIf a positive value was transferred, the method will return only messages with ID smaller than max_id
min_idintIf a positive value was transferred, the method will return only messages with ID bigger than min_id
hashlongHash for pagination, for more info click here
-

Result

-

messages.Messages

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getSavedGifs b/data/core.telegram.org/method/messages.getSavedGifs deleted file mode 100644 index 9751dc5010..0000000000 --- a/data/core.telegram.org/method/messages.getSavedGifs +++ /dev/null @@ -1,153 +0,0 @@ - - - - - messages.getSavedGifs - - - - - - - - - - - - - -
- -
-
-
- -

messages.getSavedGifs

- -

Get saved GIFs

-

- -
-
messages.savedGifsNotModified#e8025ca2 = messages.SavedGifs;
-messages.savedGifs#84a02a0d hash:long gifs:Vector<Document> = messages.SavedGifs;
----functions---
-messages.getSavedGifs#5cf09635 hash:long = messages.SavedGifs;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
-

Result

-

messages.SavedGifs

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getScheduledHistory b/data/core.telegram.org/method/messages.getScheduledHistory deleted file mode 100644 index fc05c81d9c..0000000000 --- a/data/core.telegram.org/method/messages.getScheduledHistory +++ /dev/null @@ -1,182 +0,0 @@ - - - - - messages.getScheduledHistory - - - - - - - - - - - - - -
- -
-
-
- -

messages.getScheduledHistory

- -

Get scheduled messages

-

- -
-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
----functions---
-messages.getScheduledHistory#f516760b peer:InputPeer hash:long = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
hashlongHash for pagination, for more info click here
-

Result

-

messages.Messages

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getScheduledMessages b/data/core.telegram.org/method/messages.getScheduledMessages deleted file mode 100644 index 361c661224..0000000000 --- a/data/core.telegram.org/method/messages.getScheduledMessages +++ /dev/null @@ -1,179 +0,0 @@ - - - - - messages.getScheduledMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.getScheduledMessages

- -

Get scheduled messages

-

- -
-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
----functions---
-messages.getScheduledMessages#bdbb0464 peer:InputPeer id:Vector<int> = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
idVector<int>IDs of scheduled messages
-

Result

-

messages.Messages

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getSearchCounters b/data/core.telegram.org/method/messages.getSearchCounters deleted file mode 100644 index da24b43d74..0000000000 --- a/data/core.telegram.org/method/messages.getSearchCounters +++ /dev/null @@ -1,173 +0,0 @@ - - - - - messages.getSearchCounters - - - - - - - - - - - - - -
- -
-
-
- -

messages.getSearchCounters

- -

Get the number of results that would be found by a messages.search call with the same parameters

-

- -
-
---functions---
-messages.getSearchCounters#732eef00 peer:InputPeer filters:Vector<MessagesFilter> = Vector<messages.SearchCounter>;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer where to search
filtersVector<MessagesFilter>Search filters
-

Result

-

Vector<messages.SearchCounter>

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

messages.search

-

Gets back found messages

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getSplitRanges b/data/core.telegram.org/method/messages.getSplitRanges deleted file mode 100644 index 1e89a6af54..0000000000 --- a/data/core.telegram.org/method/messages.getSplitRanges +++ /dev/null @@ -1,133 +0,0 @@ - - - - - messages.getSplitRanges - - - - - - - - - - - - - -
- -
-
-
- -

messages.getSplitRanges

- -

Get message ranges for saving the user's chat history

-

- -
-
---functions---
-messages.getSplitRanges#1cff7e08 = Vector<MessageRange>;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Vector<MessageRange>

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getStickerSet b/data/core.telegram.org/method/messages.getStickerSet deleted file mode 100644 index fd7c9375f1..0000000000 --- a/data/core.telegram.org/method/messages.getStickerSet +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.getStickerSet - - - - - - - - - - - - - -
- -
-
-
- -

messages.getStickerSet

- -

Get info about a stickerset

-

- -
-
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
----functions---
-messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
stickersetInputStickerSetStickerset
-

Result

-

messages.StickerSet

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400EMOTICON_STICKERPACK_MISSING 
400STICKERSET_INVALIDThe provided sticker set is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getStickers b/data/core.telegram.org/method/messages.getStickers deleted file mode 100644 index f6ad0f6907..0000000000 --- a/data/core.telegram.org/method/messages.getStickers +++ /dev/null @@ -1,175 +0,0 @@ - - - - - messages.getStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.getStickers

- -

Get stickers by emoji

-

- -
-
messages.stickersNotModified#f1749a22 = messages.Stickers;
-messages.stickers#30a6ec7e hash:long stickers:Vector<Document> = messages.Stickers;
----functions---
-messages.getStickers#d5a5d3a1 emoticon:string hash:long = messages.Stickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
emoticonstringThe emoji
hashlongHash for pagination, for more info click here
-

Result

-

messages.Stickers

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400EMOTICON_EMPTYThe emoji is empty.
-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getSuggestedDialogFilters b/data/core.telegram.org/method/messages.getSuggestedDialogFilters deleted file mode 100644 index 9eac88e7ff..0000000000 --- a/data/core.telegram.org/method/messages.getSuggestedDialogFilters +++ /dev/null @@ -1,136 +0,0 @@ - - - - - messages.getSuggestedDialogFilters - - - - - - - - - - - - - -
- -
-
-
- -

messages.getSuggestedDialogFilters

- -

Get suggested folders

-

- -
-
---functions---
-messages.getSuggestedDialogFilters#a29cd42c = Vector<DialogFilterSuggested>;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Vector<DialogFilterSuggested>

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getUnreadMentions b/data/core.telegram.org/method/messages.getUnreadMentions deleted file mode 100644 index f5edcf0b9b..0000000000 --- a/data/core.telegram.org/method/messages.getUnreadMentions +++ /dev/null @@ -1,212 +0,0 @@ - - - - - messages.getUnreadMentions - - - - - - - - - - - - - -
- -
-
-
- -

messages.getUnreadMentions

- -

Get unread messages where we were mentioned

-

- -
-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
----functions---
-messages.getUnreadMentions#46578472 peer:InputPeer offset_id:int add_offset:int limit:int max_id:int min_id:int = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer where to look for mentions
offset_idintOffsets for pagination, for more info click here
add_offsetintOffsets for pagination, for more info click here
limitintMaximum number of results to return, see pagination
max_idintMaximum message ID to return, see pagination
min_idintMinimum message ID to return, see pagination
-

Result

-

messages.Messages

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getWebPage b/data/core.telegram.org/method/messages.getWebPage deleted file mode 100644 index 5162dd1cc9..0000000000 --- a/data/core.telegram.org/method/messages.getWebPage +++ /dev/null @@ -1,177 +0,0 @@ - - - - - messages.getWebPage - - - - - - - - - - - - - -
- -
-
-
- -

messages.getWebPage

- -

Get instant view page

-

- -
-
webPageEmpty#eb1477e8 id:long = WebPage;
-webPagePending#c586da1c id:long date:int = WebPage;
-webPage#e89c45b2 flags:# id:long url:string display_url:string hash:int type:flags.0?string site_name:flags.1?string title:flags.2?string description:flags.3?string photo:flags.4?Photo embed_url:flags.5?string embed_type:flags.5?string embed_width:flags.6?int embed_height:flags.6?int duration:flags.7?int author:flags.8?string document:flags.9?Document cached_page:flags.10?Page attributes:flags.12?Vector<WebPageAttribute> = WebPage;
-webPageNotModified#7311ca11 flags:# cached_page_views:flags.0?int = WebPage;
----functions---
-messages.getWebPage#32ca8f91 url:string hash:int = WebPage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringURL of IV page to fetch
hashintHash for pagination, for more info click here
-

Result

-

WebPage

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400WC_CONVERT_URL_INVALIDWC convert URL invalid.
-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.getWebPagePreview b/data/core.telegram.org/method/messages.getWebPagePreview deleted file mode 100644 index 1bff9722fb..0000000000 --- a/data/core.telegram.org/method/messages.getWebPagePreview +++ /dev/null @@ -1,191 +0,0 @@ - - - - - messages.getWebPagePreview - - - - - - - - - - - - - -
- -
-
-
- -

messages.getWebPagePreview

- -

Get preview of webpage

-

- -
-
messageMediaEmpty#3ded6320 = MessageMedia;
-messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;
-messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;
-messageMediaContact#70322949 phone_number:string first_name:string last_name:string vcard:string user_id:long = MessageMedia;
-messageMediaUnsupported#9f84f49e = MessageMedia;
-messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;
-messageMediaWebPage#a32dd600 webpage:WebPage = MessageMedia;
-messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;
-messageMediaGame#fdb19008 game:Game = MessageMedia;
-messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
-messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;
-messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
-messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;
----functions---
-messages.getWebPagePreview#8b68b0cc flags:# message:string entities:flags.3?Vector<MessageEntity> = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
messagestringMessage from which to extract the preview
entitiesflags.3?Vector<MessageEntity>Message entities for styled text
-

Result

-

MessageMedia

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_EMPTYThe provided message is empty.
-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.hidePeerSettingsBar b/data/core.telegram.org/method/messages.hidePeerSettingsBar deleted file mode 100644 index 0423a4ffe1..0000000000 --- a/data/core.telegram.org/method/messages.hidePeerSettingsBar +++ /dev/null @@ -1,153 +0,0 @@ - - - - - messages.hidePeerSettingsBar - - - - - - - - - - - - - -
- -
-
-
- -

messages.hidePeerSettingsBar

- -

Should be called after the user hides the report spam/add as contact bar of a new chat, effectively prevents the user from executing the actions specified in the peer's settings.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.hidePeerSettingsBar#4facb138 peer:InputPeer = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
-

Result

-

Bool

-

Related pages

-

peerSettings

-

Peer settings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.importChatInvite b/data/core.telegram.org/method/messages.importChatInvite deleted file mode 100644 index af4e306be1..0000000000 --- a/data/core.telegram.org/method/messages.importChatInvite +++ /dev/null @@ -1,227 +0,0 @@ - - - - - messages.importChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

messages.importChatInvite

- -

Import a chat invite and join a private chat/supergroup/channel

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.importChatInvite#6c50051c hash:string = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashstringhash from t.me/joinchat/hash
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNELS_TOO_MUCHYou have joined too many channels/supergroups.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_INVALIDInvalid chat.
400INVITE_HASH_EMPTYThe invite hash is empty.
400INVITE_HASH_EXPIREDThe invite link has expired.
400INVITE_HASH_INVALIDThe invite hash is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USERS_TOO_MUCHThe maximum number of users has been exceeded (to create a chat, for example).
400USER_ALREADY_PARTICIPANTThe user is already in the group.
400USER_CHANNELS_TOO_MUCHOne of the users you tried to add is already in too many channels/supergroups.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.initHistoryImport b/data/core.telegram.org/method/messages.initHistoryImport deleted file mode 100644 index 247e72e358..0000000000 --- a/data/core.telegram.org/method/messages.initHistoryImport +++ /dev/null @@ -1,191 +0,0 @@ - - - - - messages.initHistoryImport - - - - - - - - - - - - - -
- -
-
-
- -

messages.initHistoryImport

- -

Import chat history from a foreign chat app into a specific Telegram chat, click here for more info about imported chats ».

-

- -
-
messages.historyImport#1662af0b id:long = messages.HistoryImport;
----functions---
-messages.initHistoryImport#34090c3b peer:InputPeer file:InputFile media_count:int = messages.HistoryImport;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe Telegram chat where the history should be imported.
fileInputFileFile with messages to import.
media_countintNumber of media files associated with the chat that will be uploaded using messages.uploadImportedMedia.
-

Result

-

messages.HistoryImport

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400IMPORT_FILE_INVALIDThe specified chat export file is invalid.
400IMPORT_FORMAT_UNRECOGNIZEDThe specified chat export file was exported from an unsupported chat app.
406PREVIOUS_CHAT_IMPORT_ACTIVE_WAIT_5MINImport for this chat is already in progress, wait 5 minutes before starting a new one.
-

Related pages

-

Imported messages

-

Telegram allows importing messages and media from foreign chat apps.

-

messages.uploadImportedMedia

-

Upload a media file associated with an imported chat, click here for more info ».

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.installStickerSet b/data/core.telegram.org/method/messages.installStickerSet deleted file mode 100644 index 514e6bb84f..0000000000 --- a/data/core.telegram.org/method/messages.installStickerSet +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.installStickerSet - - - - - - - - - - - - - -
- -
-
-
- -

messages.installStickerSet

- -

Install a stickerset

-

- -
-
messages.stickerSetInstallResultSuccess#38641628 = messages.StickerSetInstallResult;
-messages.stickerSetInstallResultArchive#35e410a8 sets:Vector<StickerSetCovered> = messages.StickerSetInstallResult;
----functions---
-messages.installStickerSet#c78fe460 stickerset:InputStickerSet archived:Bool = messages.StickerSetInstallResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
stickersetInputStickerSetStickerset to install
archivedBoolWhether to archive stickerset
-

Result

-

messages.StickerSetInstallResult

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400STICKERSET_INVALIDThe provided sticker set is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.markDialogUnread b/data/core.telegram.org/method/messages.markDialogUnread deleted file mode 100644 index 7eaba0110b..0000000000 --- a/data/core.telegram.org/method/messages.markDialogUnread +++ /dev/null @@ -1,160 +0,0 @@ - - - - - messages.markDialogUnread - - - - - - - - - - - - - -
- -
-
-
- -

messages.markDialogUnread

- -

Manually mark dialog as unread

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.markDialogUnread#c286d98f flags:# unread:flags.0?true peer:InputDialogPeer = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
unreadflags.0?trueMark as unread/read
peerInputDialogPeerDialog
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.migrateChat b/data/core.telegram.org/method/messages.migrateChat deleted file mode 100644 index df381825c6..0000000000 --- a/data/core.telegram.org/method/messages.migrateChat +++ /dev/null @@ -1,190 +0,0 @@ - - - - - messages.migrateChat - - - - - - - - - - - - - -
- -
-
-
- -

messages.migrateChat

- -

Turn a legacy group into a supergroup

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.migrateChat#a2875319 chat_id:long = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongLegacy group to migrate
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNELS_TOO_MUCHYou have joined too many channels/supergroups.
403CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.readDiscussion b/data/core.telegram.org/method/messages.readDiscussion deleted file mode 100644 index 48f929fe42..0000000000 --- a/data/core.telegram.org/method/messages.readDiscussion +++ /dev/null @@ -1,180 +0,0 @@ - - - - - messages.readDiscussion - - - - - - - - - - - - - -
- -
-
-
- -

messages.readDiscussion

- -

Mark a thread as read

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.readDiscussion#f731a9f4 peer:InputPeer msg_id:int read_max_id:int = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerGroup ID
msg_idintID of message that started the thread
read_max_idintID up to which thread messages were read
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.readEncryptedHistory b/data/core.telegram.org/method/messages.readEncryptedHistory deleted file mode 100644 index 72e640a26f..0000000000 --- a/data/core.telegram.org/method/messages.readEncryptedHistory +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.readEncryptedHistory - - - - - - - - - - - - - -
- -
-
-
- -

messages.readEncryptedHistory

- -

Marks message history within a secret chat as read.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.readEncryptedHistory#7f4b690a peer:InputEncryptedChat max_date:int = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputEncryptedChatSecret chat ID
max_dateintMaximum date value for received messages in history
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400MSG_WAIT_FAILEDA waiting call returned an error.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.readFeaturedStickers b/data/core.telegram.org/method/messages.readFeaturedStickers deleted file mode 100644 index ad338d9a7e..0000000000 --- a/data/core.telegram.org/method/messages.readFeaturedStickers +++ /dev/null @@ -1,150 +0,0 @@ - - - - - messages.readFeaturedStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.readFeaturedStickers

- -

Mark new featured stickers as read

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.readFeaturedStickers#5b118126 id:Vector<long> = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idVector<long>IDs of stickersets to mark as read
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.readMentions b/data/core.telegram.org/method/messages.readMentions deleted file mode 100644 index 68df81baa7..0000000000 --- a/data/core.telegram.org/method/messages.readMentions +++ /dev/null @@ -1,181 +0,0 @@ - - - - - messages.readMentions - - - - - - - - - - - - - -
- -
-
-
- -

messages.readMentions

- -

Mark mentions as read

-

- -
-
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
----functions---
-messages.readMentions#f0189d3 peer:InputPeer = messages.AffectedHistory;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerDialog
-

Result

-

messages.AffectedHistory

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.readMessageContents b/data/core.telegram.org/method/messages.readMessageContents deleted file mode 100644 index e3951d5ec9..0000000000 --- a/data/core.telegram.org/method/messages.readMessageContents +++ /dev/null @@ -1,149 +0,0 @@ - - - - - messages.readMessageContents - - - - - - - - - - - - - -
- -
-
-
- -

messages.readMessageContents

- -

Notifies the sender about the recipient having listened a voice message or watched a video.

-

- -
-
messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;
----functions---
-messages.readMessageContents#36a73f77 id:Vector<int> = messages.AffectedMessages;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idVector<int>Message ID list
-

Result

-

Returns a list of listened\watched messages as Vector<int>.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.receivedMessages b/data/core.telegram.org/method/messages.receivedMessages deleted file mode 100644 index 84e5989c75..0000000000 --- a/data/core.telegram.org/method/messages.receivedMessages +++ /dev/null @@ -1,148 +0,0 @@ - - - - - messages.receivedMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.receivedMessages

- -

Confirms receipt of messages by a client, cancels PUSH-notification sending.

-

- -
-
---functions---
-messages.receivedMessages#5a954c0 max_id:int = Vector<ReceivedNotifyMessage>;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
max_idintMaximum message ID available in a client.
-

Result

-

The method returns the list of message IDs, for which PUSH-notifications were cancelled.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.receivedQueue b/data/core.telegram.org/method/messages.receivedQueue deleted file mode 100644 index 39debae4f5..0000000000 --- a/data/core.telegram.org/method/messages.receivedQueue +++ /dev/null @@ -1,170 +0,0 @@ - - - - - messages.receivedQueue - - - - - - - - - - - - - -
- -
-
-
- -

messages.receivedQueue

- -

Confirms receipt of messages in a secret chat by client, cancels push notifications.

-

- -
-
---functions---
-messages.receivedQueue#55a5bb66 max_qts:int = Vector<long>;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
max_qtsintMaximum qts value available at the client
-

Result

-

Method returns a list of random_ids of messages for which push notifications were cancelled in Vector<long>.

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MAX_QTS_INVALIDThe specified max_qts is invalid.
400MSG_WAIT_FAILEDA waiting call returned an error.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.reorderPinnedDialogs b/data/core.telegram.org/method/messages.reorderPinnedDialogs deleted file mode 100644 index 0bb8c438db..0000000000 --- a/data/core.telegram.org/method/messages.reorderPinnedDialogs +++ /dev/null @@ -1,185 +0,0 @@ - - - - - messages.reorderPinnedDialogs - - - - - - - - - - - - - -
- -
-
-
- -

messages.reorderPinnedDialogs

- -

Reorder pinned dialogs

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.reorderPinnedDialogs#3b1adf37 flags:# force:flags.0?true folder_id:int order:Vector<InputDialogPeer> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
forceflags.0?trueIf set, dialogs pinned server-side but not present in the order field will be unpinned.
folder_idintPeer folder ID, for more info click here
orderVector<InputDialogPeer>New dialog order
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.reorderStickerSets b/data/core.telegram.org/method/messages.reorderStickerSets deleted file mode 100644 index 58d00ac522..0000000000 --- a/data/core.telegram.org/method/messages.reorderStickerSets +++ /dev/null @@ -1,160 +0,0 @@ - - - - - messages.reorderStickerSets - - - - - - - - - - - - - -
- -
-
-
- -

messages.reorderStickerSets

- -

Reorder installed stickersets

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.reorderStickerSets#78337739 flags:# masks:flags.0?true order:Vector<long> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
masksflags.0?trueReorder mask stickersets
orderVector<long>New stickerset order by stickerset IDs
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.report b/data/core.telegram.org/method/messages.report deleted file mode 100644 index b703f80c9c..0000000000 --- a/data/core.telegram.org/method/messages.report +++ /dev/null @@ -1,187 +0,0 @@ - - - - - messages.report - - - - - - - - - - - - - -
- -
-
-
- -

messages.report

- -

Report a message in a chat for violation of telegram's Terms of Service

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.report#8953ab4e peer:InputPeer id:Vector<int> reason:ReportReason message:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
idVector<int>IDs of messages to report
reasonReportReasonWhy are these messages being reported
messagestringComment for report moderation
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.reportEncryptedSpam b/data/core.telegram.org/method/messages.reportEncryptedSpam deleted file mode 100644 index e9f3d6606a..0000000000 --- a/data/core.telegram.org/method/messages.reportEncryptedSpam +++ /dev/null @@ -1,167 +0,0 @@ - - - - - messages.reportEncryptedSpam - - - - - - - - - - - - - -
- -
-
-
- -

messages.reportEncryptedSpam

- -

Report a secret chat for spam

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.reportEncryptedSpam#4b0c8c0f peer:InputEncryptedChat = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputEncryptedChatThe secret chat to report
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.reportSpam b/data/core.telegram.org/method/messages.reportSpam deleted file mode 100644 index 851db85844..0000000000 --- a/data/core.telegram.org/method/messages.reportSpam +++ /dev/null @@ -1,180 +0,0 @@ - - - - - messages.reportSpam - - - - - - - - - - - - - -
- -
-
-
- -

messages.reportSpam

- -

Report a new incoming chat for spam, if the peer settings of the chat allow us to do that

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.reportSpam#cf1592db peer:InputPeer = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer to report
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

peerSettings

-

Peer settings

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.requestEncryption b/data/core.telegram.org/method/messages.requestEncryption deleted file mode 100644 index aa9cc13fa8..0000000000 --- a/data/core.telegram.org/method/messages.requestEncryption +++ /dev/null @@ -1,185 +0,0 @@ - - - - - messages.requestEncryption - - - - - - - - - - - - - -
- -
-
-
- -

messages.requestEncryption

- -

Sends a request to start a secret chat to the user.

-

- -
-
encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;
-encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;
-encryptedChatRequested#48f1d94c flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:long participant_id:long g_a:bytes = EncryptedChat;
-encryptedChat#61f0d4c7 id:int access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long = EncryptedChat;
-encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;
----functions---
-messages.requestEncryption#f64daf43 user_id:InputUser random_id:int g_a:bytes = EncryptedChat;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idInputUserUser ID
random_idintUnique client request ID required to prevent resending. This also doubles as the chat ID.
g_abytesA = g ^ a mod p, see Wikipedia
-

Result

-

EncryptedChat

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400DH_G_A_INVALIDg_a invalid.
400USER_ID_INVALIDThe provided user ID is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.requestUrlAuth b/data/core.telegram.org/method/messages.requestUrlAuth deleted file mode 100644 index 66f2c025aa..0000000000 --- a/data/core.telegram.org/method/messages.requestUrlAuth +++ /dev/null @@ -1,174 +0,0 @@ - - - - - messages.requestUrlAuth - - - - - - - - - - - - - -
- -
-
-
- -

messages.requestUrlAuth

- -

Get more info about a Seamless Telegram Login authorization request, for more info click here »

-

- -
-
urlAuthResultRequest#92d33a0e flags:# request_write_access:flags.0?true bot:User domain:string = UrlAuthResult;
-urlAuthResultAccepted#8f8c0e4e url:string = UrlAuthResult;
-urlAuthResultDefault#a9d6db1f = UrlAuthResult;
----functions---
-messages.requestUrlAuth#198fb446 flags:# peer:flags.1?InputPeer msg_id:flags.1?int button_id:flags.1?int url:flags.2?string = UrlAuthResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
peerflags.1?InputPeerPeer where the message is located
msg_idflags.1?intThe message
button_idflags.1?intThe ID of the button with the authorization request
urlflags.2?stringURL used for link URL authorization, click here for more info »
-

Result

-

UrlAuthResult

-

Related pages

-

Seamless Telegram Login

-

Handle Seamless Telegram Login URL authorization requests.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.saveDraft b/data/core.telegram.org/method/messages.saveDraft deleted file mode 100644 index 960d382ff7..0000000000 --- a/data/core.telegram.org/method/messages.saveDraft +++ /dev/null @@ -1,202 +0,0 @@ - - - - - messages.saveDraft - - - - - - - - - - - - - -
- -
-
-
- -

messages.saveDraft

- -

Save a message draft associated to a chat.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.saveDraft#bc39e14b flags:# no_webpage:flags.1?true reply_to_msg_id:flags.0?int peer:InputPeer message:string entities:flags.3?Vector<MessageEntity> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.1?trueDisable generation of the webpage preview
reply_to_msg_idflags.0?intMessage ID the message should reply to
peerInputPeerDestination of the message that should be sent
messagestringThe draft
entitiesflags.3?Vector<MessageEntity>Message entities for styled text
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

-

Message drafts

-

How to handle message drafts

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.saveGif b/data/core.telegram.org/method/messages.saveGif deleted file mode 100644 index 45ed9f61ec..0000000000 --- a/data/core.telegram.org/method/messages.saveGif +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.saveGif - - - - - - - - - - - - - -
- -
-
-
- -

messages.saveGif

- -

Add GIF to saved gifs list

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.saveGif#327a30cb id:InputDocument unsave:Bool = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idInputDocumentGIF to save
unsaveBoolWhether to remove GIF from saved gifs list
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400GIF_ID_INVALIDThe provided GIF ID is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.saveRecentSticker b/data/core.telegram.org/method/messages.saveRecentSticker deleted file mode 100644 index af8b20cae8..0000000000 --- a/data/core.telegram.org/method/messages.saveRecentSticker +++ /dev/null @@ -1,182 +0,0 @@ - - - - - messages.saveRecentSticker - - - - - - - - - - - - - -
- -
-
-
- -

messages.saveRecentSticker

- -

Add/remove sticker from recent stickers list

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.saveRecentSticker#392718f8 flags:# attached:flags.0?true id:InputDocument unsave:Bool = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
attachedflags.0?trueWhether to add/remove stickers recently attached to photo or video files
idInputDocumentSticker
unsaveBoolWhether to save or unsave the sticker
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400STICKER_ID_INVALIDThe provided sticker ID is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.search b/data/core.telegram.org/method/messages.search deleted file mode 100644 index 42836278a1..0000000000 --- a/data/core.telegram.org/method/messages.search +++ /dev/null @@ -1,291 +0,0 @@ - - - - - messages.search - - - - - - - - - - - - - -
- -
-
-
- -

messages.search

- -

Gets back found messages

-

- -
-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
----functions---
-messages.search#a0fda762 flags:# peer:InputPeer q:string from_id:flags.0?InputPeer top_msg_id:flags.1?int filter:MessagesFilter min_date:int max_date:int offset_id:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerUser or chat, histories with which are searched, or (inputPeerEmpty) constructor for global search
qstringText search request
from_idflags.0?InputPeerOnly return messages sent by the specified user ID
top_msg_idflags.1?intThread ID
filterMessagesFilterFilter to return only specified message types
min_dateintIf a positive value was transferred, only messages with a sending date bigger than the transferred one will be returned
max_dateintIf a positive value was transferred, only messages with a sending date smaller than the transferred one will be returned
offset_idintOnly return messages starting from the specified message ID
add_offsetintAdditional offset
limitintNumber of results to return
max_idintMaximum message ID to return
min_idintMinimum message ID to return
hashlongHash
-

Result

-

messages.Messages

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400FROM_PEER_INVALIDThe specified from_id is invalid.
400INPUT_FILTER_INVALIDThe specified filter is invalid.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PEER_ID_NOT_SUPPORTEDThe provided peer ID is not supported.
400SEARCH_QUERY_EMPTYThe search query is empty.
400USER_ID_INVALIDThe provided user ID is invalid.
-

Related pages

-

inputPeerEmpty

-

An empty constructor, no user or chat is defined.

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.searchGifs b/data/core.telegram.org/method/messages.searchGifs deleted file mode 100644 index 161693bb23..0000000000 --- a/data/core.telegram.org/method/messages.searchGifs +++ /dev/null @@ -1,177 +0,0 @@ - - - - - messages.searchGifs - - - - - - - - - - - - - -
- -
-
-
- -

messages.searchGifs

- -

Search for GIFs

-

- -
-
 Method schema is available as of layer 114. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
qstringText query
offsetintOffset for pagination »
-

Result

-

messages.FoundGifs

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400METHOD_INVALIDThe specified method is invalid.
400SEARCH_QUERY_EMPTYThe search query is empty.
-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.searchGlobal b/data/core.telegram.org/method/messages.searchGlobal deleted file mode 100644 index e966ef85b3..0000000000 --- a/data/core.telegram.org/method/messages.searchGlobal +++ /dev/null @@ -1,226 +0,0 @@ - - - - - messages.searchGlobal - - - - - - - - - - - - - -
- -
-
-
- -

messages.searchGlobal

- -

Search for messages and peers globally

-

- -
-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
----functions---
-messages.searchGlobal#4bc6589a flags:# folder_id:flags.0?int q:string filter:MessagesFilter min_date:int max_date:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.0?intPeer folder ID, for more info click here
qstringQuery
filterMessagesFilterGlobal search filter
min_dateintIf a positive value was specified, the method will return only messages with date bigger than min_date
max_dateintIf a positive value was transferred, the method will return only messages with date smaller than max_date
offset_rateintInitially 0, then set to the next_rate parameter of messages.messagesSlice
offset_peerInputPeerOffsets for pagination, for more info click here
offset_idintOffsets for pagination, for more info click here
limitintOffsets for pagination, for more info click here
-

Result

-

messages.Messages

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400FOLDER_ID_INVALIDInvalid folder ID.
400SEARCH_QUERY_EMPTYThe search query is empty.
-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

-

messages.messagesSlice

-

Incomplete list of messages and auxiliary data.

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.searchStickerSets b/data/core.telegram.org/method/messages.searchStickerSets deleted file mode 100644 index 2fadab6b4a..0000000000 --- a/data/core.telegram.org/method/messages.searchStickerSets +++ /dev/null @@ -1,168 +0,0 @@ - - - - - messages.searchStickerSets - - - - - - - - - - - - - -
- -
-
-
- -

messages.searchStickerSets

- -

Search for stickersets

-

- -
-
messages.foundStickerSetsNotModified#d54b65d = messages.FoundStickerSets;
-messages.foundStickerSets#8af09dd2 hash:long sets:Vector<StickerSetCovered> = messages.FoundStickerSets;
----functions---
-messages.searchStickerSets#35705b8a flags:# exclude_featured:flags.0?true q:string hash:long = messages.FoundStickerSets;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
exclude_featuredflags.0?trueExclude featured stickersets from results
qstringQuery string
hashlongHash for pagination, for more info click here
-

Result

-

messages.FoundStickerSets

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.sendBroadcast b/data/core.telegram.org/method/messages.sendBroadcast deleted file mode 100644 index 5244109ad0..0000000000 --- a/data/core.telegram.org/method/messages.sendBroadcast +++ /dev/null @@ -1,145 +0,0 @@ - - - - - messages.sendBroadcast - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendBroadcast

- -

Sends multiple messages to contacts.

-

{schema}

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
contactsVector<InputUser>List of user ID to whom a message will be sent
messagestringMessage text
mediaInputMediaMessage media-contents
-

Result

-

messages.StatedMessages

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.sendEncrypted b/data/core.telegram.org/method/messages.sendEncrypted deleted file mode 100644 index b8ff1a69dc..0000000000 --- a/data/core.telegram.org/method/messages.sendEncrypted +++ /dev/null @@ -1,210 +0,0 @@ - - - - - messages.sendEncrypted - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendEncrypted

- -

Sends a text message to a secret chat.

-

- -
-
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;
-messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;
----functions---
-messages.sendEncrypted#44fa7a15 flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.0?trueSend encrypted message without a notification
peerInputEncryptedChatSecret chat ID
random_idlongUnique client message ID, necessary to avoid message resending
databytesTL-serialization of DecryptedMessage type, encrypted with a key that was created during chat initialization
-

Result

-

messages.SentEncryptedMessage

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400DATA_INVALIDEncrypted data invalid.
400ENCRYPTION_DECLINEDThe secret chat was declined.
400MSG_WAIT_FAILEDA waiting call returned an error.
403USER_IS_BLOCKEDYou were blocked by this user.
-

Related pages

-

DecryptedMessage

-

Object describes the contents of an encrypted message.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.sendEncryptedFile b/data/core.telegram.org/method/messages.sendEncryptedFile deleted file mode 100644 index c5d252bc7d..0000000000 --- a/data/core.telegram.org/method/messages.sendEncryptedFile +++ /dev/null @@ -1,215 +0,0 @@ - - - - - messages.sendEncryptedFile - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendEncryptedFile

- -

Sends a message with a file attachment to a secret chat

-

- -
-
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;
-messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;
----functions---
-messages.sendEncryptedFile#5559481d flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes file:InputEncryptedFile = messages.SentEncryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.0?trueWhether to send the file without triggering a notification
peerInputEncryptedChatSecret chat ID
random_idlongUnique client message ID necessary to prevent message resending
databytesTL-serialization of DecryptedMessage type, encrypted with a key generated during chat initialization
fileInputEncryptedFileFile attachment for the secret chat
-

Result

-

messages.SentEncryptedMessage

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400DATA_TOO_LONGData too long.
400ENCRYPTION_DECLINEDThe secret chat was declined.
400FILE_EMTPYAn empty file was provided.
400MD5_CHECKSUM_INVALIDThe MD5 checksums do not match.
400MSG_WAIT_FAILEDA waiting call returned an error.
-

Related pages

-

DecryptedMessage

-

Object describes the contents of an encrypted message.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.sendEncryptedService b/data/core.telegram.org/method/messages.sendEncryptedService deleted file mode 100644 index bc40808518..0000000000 --- a/data/core.telegram.org/method/messages.sendEncryptedService +++ /dev/null @@ -1,205 +0,0 @@ - - - - - messages.sendEncryptedService - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendEncryptedService

- -

Sends a service message to a secret chat.

-

- -
-
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;
-messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;
----functions---
-messages.sendEncryptedService#32d439a4 peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputEncryptedChatSecret chat ID
random_idlongUnique client message ID required to prevent message resending
databytesTL-serialization of DecryptedMessage type, encrypted with a key generated during chat initialization
-

Result

-

messages.SentEncryptedMessage

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400DATA_INVALIDEncrypted data invalid.
400ENCRYPTION_DECLINEDThe secret chat was declined.
400ENCRYPTION_ID_INVALIDThe provided secret chat ID is invalid.
400MSG_WAIT_FAILEDA waiting call returned an error.
403USER_DELETEDYou can't send this secret message because the other participant deleted their account.
403USER_IS_BLOCKEDYou were blocked by this user.
-

Related pages

-

DecryptedMessage

-

Object describes the contents of an encrypted message.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.sendInlineBotResult b/data/core.telegram.org/method/messages.sendInlineBotResult deleted file mode 100644 index ddd4e5d7f4..0000000000 --- a/data/core.telegram.org/method/messages.sendInlineBotResult +++ /dev/null @@ -1,344 +0,0 @@ - - - - - messages.sendInlineBotResult - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendInlineBotResult

- -

Send a result obtained using messages.getInlineBotResults.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.sendInlineBotResult#220815b0 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true hide_via:flags.11?true peer:InputPeer reply_to_msg_id:flags.0?int random_id:long query_id:long id:string schedule_date:flags.10?int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.5?trueWhether to send the message silently (no notification will be triggered on the other client)
backgroundflags.6?trueWhether to send the message in background
clear_draftflags.7?trueWhether to clear the draft
hide_viaflags.11?trueWhether to hide the via @botname in the resulting message (only for bot usernames encountered in the config)
peerInputPeerDestination
reply_to_msg_idflags.0?intID of the message this message should reply to
random_idlongRandom ID to avoid resending the same query
query_idlongQuery ID from messages.getInlineBotResults
idstringResult ID from messages.getInlineBotResults
schedule_dateflags.10?intScheduled message date for scheduled messages
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_RESTRICTEDYou can't send messages in this chat, you were restricted.
403CHAT_SEND_GAME_FORBIDDENYou can't send a game to this chat.
403CHAT_SEND_GIFS_FORBIDDENYou can't send gifs in this chat.
403CHAT_SEND_INLINE_FORBIDDENYou can't send inline messages in this group.
403CHAT_SEND_MEDIA_FORBIDDENYou can't send media in this chat.
403CHAT_SEND_STICKERS_FORBIDDENYou can't send stickers in this chat.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400INLINE_RESULT_EXPIREDThe inline query expired.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MEDIA_EMPTYThe provided media object is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400QUERY_ID_EMPTYThe query ID is empty.
400RESULT_ID_EMPTYResult ID empty.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
420SLOWMODE_WAIT_XSlowmode is enabled in this chat: you must wait for the specified number of seconds before sending another message to the chat.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400WEBPAGE_CURL_FAILEDFailure while fetching the webpage with cURL.
400WEBPAGE_MEDIA_EMPTYWebpage media empty.
400YOU_BLOCKED_USERYou blocked this user.
-

Related pages

-

Message drafts

-

How to handle message drafts

-

config

-

Current configuration

-

messages.getInlineBotResults

-

Query an inline bot

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.sendMedia b/data/core.telegram.org/method/messages.sendMedia deleted file mode 100644 index ca4043c09c..0000000000 --- a/data/core.telegram.org/method/messages.sendMedia +++ /dev/null @@ -1,518 +0,0 @@ - - - - - messages.sendMedia - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendMedia

- -

Send a media

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.5?trueSend message silently (no notification should be triggered)
backgroundflags.6?trueSend message in background
clear_draftflags.7?trueClear the draft
peerInputPeerDestination
reply_to_msg_idflags.0?intMessage ID to which this message should reply to
mediaInputMediaAttached media
messagestringCaption
random_idlongRandom ID to avoid resending the same message
reply_markupflags.2?ReplyMarkupReply markup for bot keyboards
entitiesflags.3?Vector<MessageEntity>Message entities for styled text
schedule_dateflags.10?intScheduled message date for scheduled messages
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOT_PAYMENTS_DISABLEDPlease enable bot payments in botfather before calling this method.
400BOT_POLLS_DISABLED 
400BROADCAST_PUBLIC_VOTERS_FORBIDDENYou can't forward polls with public voters.
400BUTTON_DATA_INVALIDThe data of one or more of the buttons you provided is invalid.
400BUTTON_TYPE_INVALIDThe type of one or more of the buttons you provided is invalid.
400BUTTON_URL_INVALIDButton URL invalid.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_RESTRICTEDYou can't send messages in this chat, you were restricted.
403CHAT_SEND_GIFS_FORBIDDENYou can't send gifs in this chat.
403CHAT_SEND_MEDIA_FORBIDDENYou can't send media in this chat.
403CHAT_SEND_POLL_FORBIDDENYou can't send polls in this chat.
403CHAT_SEND_STICKERS_FORBIDDENYou can't send stickers in this chat.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400CURRENCY_TOTAL_AMOUNT_INVALIDThe total amount of all prices is invalid.
400EMOTICON_INVALIDThe specified emoji is invalid.
400EXTERNAL_URL_INVALIDExternal URL invalid.
400FILE_PARTS_INVALIDThe number of file parts is invalid.
400FILE_PART_LENGTH_INVALIDThe length of a file part is invalid.
400FILE_REFERENCE_EMPTYAn empty file reference was specified.
400FILE_REFERENCE_EXPIREDFile reference expired, it must be refetched as described in https://core.telegram.org/api/file_reference.
400GAME_BOT_INVALIDBots can't send another bot's game.
400IMAGE_PROCESS_FAILEDFailure while processing image.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MD5_CHECKSUM_INVALIDThe MD5 checksums do not match.
400MEDIA_CAPTION_TOO_LONGThe caption is too long.
400MEDIA_EMPTYThe provided media object is invalid.
400MEDIA_INVALIDMedia invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PAYMENT_PROVIDER_INVALIDThe specified payment provider is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PHOTO_EXT_INVALIDThe extension of the photo is invalid.
400PHOTO_INVALID_DIMENSIONSThe photo dimensions are invalid.
400PHOTO_SAVE_FILE_INVALIDInternal issues, try again later.
400POLL_ANSWERS_INVALIDInvalid poll answers were provided.
400POLL_ANSWER_INVALIDOne of the poll answers is not acceptable.
400POLL_OPTION_DUPLICATEDuplicate poll options provided.
400POLL_OPTION_INVALIDInvalid poll option provided.
400POLL_QUESTION_INVALIDOne of the poll questions is not acceptable.
400QUIZ_CORRECT_ANSWERS_EMPTYNo correct quiz answer was specified.
400QUIZ_CORRECT_ANSWERS_TOO_MUCHYou specified too many correct answers in a quiz, quizes can only have one right answer!
400QUIZ_CORRECT_ANSWER_INVALIDAn invalid value was provided to the correct_answers field.
400QUIZ_MULTIPLE_INVALIDQuizes can't have the multiple_choice flag set!
400REPLY_MARKUP_BUY_EMPTYReply markup for buy button empty.
400REPLY_MARKUP_INVALIDThe provided reply markup is invalid.
400SCHEDULE_BOT_NOT_ALLOWEDBots cannot schedule messages.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
420SLOWMODE_WAIT_XSlowmode is enabled in this chat: you must wait for the specified number of seconds before sending another message to the chat.
400TTL_MEDIA_INVALIDInvalid media Time To Live was provided.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400USER_IS_BLOCKEDYou were blocked by this user.
400USER_IS_BOTBots can't send messages to other bots.
400VIDEO_CONTENT_TYPE_INVALIDThe video's content type is invalid.
400WEBPAGE_CURL_FAILEDFailure while fetching the webpage with cURL.
400WEBPAGE_MEDIA_EMPTYWebpage media empty.
400YOU_BLOCKED_USERYou blocked this user.
-

Bots can use this method

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

-

Scheduled messages

-

Telegram allows scheduling messages

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.sendMessage b/data/core.telegram.org/method/messages.sendMessage deleted file mode 100644 index 04af62058d..0000000000 --- a/data/core.telegram.org/method/messages.sendMessage +++ /dev/null @@ -1,398 +0,0 @@ - - - - - messages.sendMessage - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendMessage

- -

Sends a message to a chat

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.sendMessage#520c3870 flags:# no_webpage:flags.1?true silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.1?trueSet this flag to disable generation of the webpage preview
silentflags.5?trueSend this message silently (no notifications for the receivers)
backgroundflags.6?trueSend this message as background message
clear_draftflags.7?trueClear the draft field
peerInputPeerThe destination where the message will be sent
reply_to_msg_idflags.0?intThe message ID to which this message will reply to
messagestringThe message
random_idlongUnique client message ID required to prevent message resending
reply_markupflags.2?ReplyMarkupReply markup for sending bot buttons
entitiesflags.3?Vector<MessageEntity>Message entities for sending styled text
schedule_dateflags.10?intScheduled message date for scheduled messages
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400BOT_DOMAIN_INVALIDBot domain invalid.
400BOT_INVALIDThis is not a valid bot.
400BUTTON_DATA_INVALIDThe data of one or more of the buttons you provided is invalid.
400BUTTON_TYPE_INVALIDThe type of one or more of the buttons you provided is invalid.
400BUTTON_URL_INVALIDButton URL invalid.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_RESTRICTEDYou can't send messages in this chat, you were restricted.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400ENCRYPTION_DECLINEDThe secret chat was declined.
400ENTITIES_TOO_LONGYou provided too many styled message entities.
400ENTITY_MENTION_USER_INVALIDYou mentioned an invalid user.
400FROM_MESSAGE_BOT_DISABLEDBots can't use fromMessage min constructors.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MESSAGE_EMPTYThe provided message is empty.
400MESSAGE_TOO_LONGThe provided message is too long.
400MSG_ID_INVALIDProvided reply_to_msg_id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PINNED_DIALOGS_TOO_MUCHToo many pinned dialogs.
400POLL_OPTION_INVALIDInvalid poll option provided.
400REPLY_MARKUP_INVALIDThe provided reply markup is invalid.
400REPLY_MARKUP_TOO_LONGThe specified reply_markup is too long.
400SCHEDULE_BOT_NOT_ALLOWEDBots cannot schedule messages.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_STATUS_PRIVATECan't schedule until user is online, if the user's last seen timestamp is hidden by their privacy settings.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
420SLOWMODE_WAIT_XSlowmode is enabled in this chat: you must wait for the specified number of seconds before sending another message to the chat.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400USER_IS_BLOCKEDYou were blocked by this user.
400USER_IS_BOTBots can't send messages to other bots.
400YOU_BLOCKED_USERYou blocked this user.
-

Bots can use this method

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

-

Scheduled messages

-

Telegram allows scheduling messages

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.sendMultiMedia b/data/core.telegram.org/method/messages.sendMultiMedia deleted file mode 100644 index cfa150bdf1..0000000000 --- a/data/core.telegram.org/method/messages.sendMultiMedia +++ /dev/null @@ -1,263 +0,0 @@ - - - - - messages.sendMultiMedia - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendMultiMedia

- -

Send an album or grouped media

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.sendMultiMedia#cc0110cb flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int multi_media:Vector<InputSingleMedia> schedule_date:flags.10?int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.5?trueWhether to send the album silently (no notification triggered)
backgroundflags.6?trueSend in background?
clear_draftflags.7?trueWhether to clear drafts
peerInputPeerThe destination chat
reply_to_msg_idflags.0?intThe message to reply to
multi_mediaVector<InputSingleMedia>The medias to send
schedule_dateflags.10?intScheduled message date for scheduled messages
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400MEDIA_CAPTION_TOO_LONGThe caption is too long.
400MEDIA_EMPTYThe provided media object is invalid.
400MEDIA_INVALIDMedia invalid.
400MULTI_MEDIA_TOO_LONGToo many media files for album.
400PEER_ID_INVALIDThe provided peer id is invalid.
400RANDOM_ID_EMPTYRandom ID empty.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
420SLOWMODE_WAIT_XSlowmode is enabled in this chat: wait X seconds before sending another message to this chat.
-

Bots can use this method

-

Related pages

-

Message drafts

-

How to handle message drafts

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.sendReaction b/data/core.telegram.org/method/messages.sendReaction deleted file mode 100644 index b02e1db557..0000000000 --- a/data/core.telegram.org/method/messages.sendReaction +++ /dev/null @@ -1,185 +0,0 @@ - - - - - messages.sendReaction - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendReaction

- -

Send reaction to message

-

- -
-
 Method schema is available as of layer 136. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerPeer
msg_idintMessage ID to react to
reactionflags.0?stringReaction (a UTF8 emoji)
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400REACTION_EMPTYEmpty reaction provided.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.sendScheduledMessages b/data/core.telegram.org/method/messages.sendScheduledMessages deleted file mode 100644 index 92715f213b..0000000000 --- a/data/core.telegram.org/method/messages.sendScheduledMessages +++ /dev/null @@ -1,182 +0,0 @@ - - - - - messages.sendScheduledMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendScheduledMessages

- -

Send scheduled messages right away

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.sendScheduledMessages#bd38850a peer:InputPeer id:Vector<int> = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
idVector<int>Scheduled message IDs
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.sendScreenshotNotification b/data/core.telegram.org/method/messages.sendScreenshotNotification deleted file mode 100644 index c5424b40a3..0000000000 --- a/data/core.telegram.org/method/messages.sendScreenshotNotification +++ /dev/null @@ -1,187 +0,0 @@ - - - - - messages.sendScreenshotNotification - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendScreenshotNotification

- -

Notify the other user in a private chat that a screenshot of the chat was taken

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.sendScreenshotNotification#c97df020 peer:InputPeer reply_to_msg_id:int random_id:long = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerOther user
reply_to_msg_idintID of message that was screenshotted, can be 0
random_idlongRandom ID to avoid message resending
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
400YOU_BLOCKED_USERYou blocked this user.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.sendVote b/data/core.telegram.org/method/messages.sendVote deleted file mode 100644 index 927ebfc9fc..0000000000 --- a/data/core.telegram.org/method/messages.sendVote +++ /dev/null @@ -1,220 +0,0 @@ - - - - - messages.sendVote - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendVote

- -

Vote in a poll

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.sendVote#10ea6184 peer:InputPeer msg_id:int options:Vector<bytes> = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat where the poll was sent
msg_idintThe message ID of the poll
optionsVector<bytes>The options that were chosen
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MESSAGE_POLL_CLOSEDPoll closed.
400OPTIONS_TOO_MUCHToo many options provided.
400OPTION_INVALIDInvalid option selected.
400PEER_ID_INVALIDThe provided peer id is invalid.
400REVOTE_NOT_ALLOWEDYou cannot change your vote.
-

Related pages

-

poll

-

Poll

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.setBotCallbackAnswer b/data/core.telegram.org/method/messages.setBotCallbackAnswer deleted file mode 100644 index befb3bb4a6..0000000000 --- a/data/core.telegram.org/method/messages.setBotCallbackAnswer +++ /dev/null @@ -1,203 +0,0 @@ - - - - - messages.setBotCallbackAnswer - - - - - - - - - - - - - -
- -
-
-
- -

messages.setBotCallbackAnswer

- -

Set the callback answer to a user button press (bots only)

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.setBotCallbackAnswer#d58f130a flags:# alert:flags.1?true query_id:long message:flags.0?string url:flags.2?string cache_time:int = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
alertflags.1?trueWhether to show the message as a popup instead of a toast notification
query_idlongQuery ID
messageflags.0?stringPopup to show
urlflags.2?stringURL to open
cache_timeintCache validity
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_TOO_LONGThe provided message is too long.
400QUERY_ID_INVALIDThe query ID is invalid.
400URL_INVALIDInvalid URL provided.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.setBotPrecheckoutResults b/data/core.telegram.org/method/messages.setBotPrecheckoutResults deleted file mode 100644 index 408b373dc0..0000000000 --- a/data/core.telegram.org/method/messages.setBotPrecheckoutResults +++ /dev/null @@ -1,188 +0,0 @@ - - - - - messages.setBotPrecheckoutResults - - - - - - - - - - - - - -
- -
-
-
- -

messages.setBotPrecheckoutResults

- -

Once the user has confirmed their payment and shipping details, the bot receives an updateBotPrecheckoutQuery update.
-Use this method to respond to such pre-checkout queries.
-Note: Telegram must receive an answer within 10 seconds after the pre-checkout query was sent.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.setBotPrecheckoutResults#9c2dd95 flags:# success:flags.1?true query_id:long error:flags.0?string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
successflags.1?trueSet this flag if everything is alright (goods are available, etc.) and the bot is ready to proceed with the order, otherwise do not set it, and set the error field, instead
query_idlongUnique identifier for the query to be answered
errorflags.0?stringRequired if the success isn't set. Error message in human readable form that explains the reason for failure to proceed with the checkout (e.g. "Sorry, somebody just bought the last of our amazing black T-shirts while you were busy filling out your payment details. Please choose a different color or garment!"). Telegram will display this message to the user.
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400ERROR_TEXT_EMPTYThe provided error message is empty.
-

Bots can use this method

-

Related pages

-

updateBotPrecheckoutQuery

-

This object contains information about an incoming pre-checkout query.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.setBotShippingResults b/data/core.telegram.org/method/messages.setBotShippingResults deleted file mode 100644 index 6b60e9d524..0000000000 --- a/data/core.telegram.org/method/messages.setBotShippingResults +++ /dev/null @@ -1,186 +0,0 @@ - - - - - messages.setBotShippingResults - - - - - - - - - - - - - -
- -
-
-
- -

messages.setBotShippingResults

- -

If you sent an invoice requesting a shipping address and the parameter is_flexible was specified, the bot will receive an updateBotShippingQuery update. Use this method to reply to shipping queries.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.setBotShippingResults#e5f672fa flags:# query_id:long error:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
query_idlongUnique identifier for the query to be answered
errorflags.0?stringError message in human readable form that explains why it is impossible to complete the order (e.g. "Sorry, delivery to your desired address is unavailable'). Telegram will display this message to the user.
shipping_optionsflags.1?Vector<ShippingOption>A vector of available shipping options.
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400QUERY_ID_INVALIDThe query ID is invalid.
-

Bots can use this method

-

Related pages

-

updateBotShippingQuery

-

This object contains information about an incoming shipping query.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.setChatTheme b/data/core.telegram.org/method/messages.setChatTheme deleted file mode 100644 index f581091ac8..0000000000 --- a/data/core.telegram.org/method/messages.setChatTheme +++ /dev/null @@ -1,185 +0,0 @@ - - - - - messages.setChatTheme - - - - - - - - - - - - - -
- -
-
-
- -

messages.setChatTheme

- -

Change the chat theme of a certain chat

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.setChatTheme#e63be13f peer:InputPeer emoticon:string = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPrivate chat where to change theme
emoticonstringEmoji, identifying a specific chat theme; a list of chat themes can be fetched using account.getChatThemes
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400EMOJI_INVALIDThe specified theme emoji is valid.
400EMOJI_NOT_MODIFIEDThe theme wasn't changed.
-

Related pages

-

account.getChatThemes

-

Get all available chat themes

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.setEncryptedTyping b/data/core.telegram.org/method/messages.setEncryptedTyping deleted file mode 100644 index f1aa28dd9d..0000000000 --- a/data/core.telegram.org/method/messages.setEncryptedTyping +++ /dev/null @@ -1,177 +0,0 @@ - - - - - messages.setEncryptedTyping - - - - - - - - - - - - - -
- -
-
-
- -

messages.setEncryptedTyping

- -

Send typing event by the current user to a secret chat.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.setEncryptedTyping#791451ed peer:InputEncryptedChat typing:Bool = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputEncryptedChatSecret chat ID
typingBoolTyping.
Possible values:
(boolTrue), if the user started typing and more than 5 seconds have passed since the last request
(boolFalse), if the user stopped typing
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
-

Related pages

-

boolTrue

-

The constructor can be interpreted as a booleantrue value.

-

boolFalse

-

Constructor may be interpreted as a booleanfalse value.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.setGameScore b/data/core.telegram.org/method/messages.setGameScore deleted file mode 100644 index 7c7540ddc6..0000000000 --- a/data/core.telegram.org/method/messages.setGameScore +++ /dev/null @@ -1,218 +0,0 @@ - - - - - messages.setGameScore - - - - - - - - - - - - - -
- -
-
-
- -

messages.setGameScore

- -

Use this method to set the score of the specified user in a game sent as a normal message (bots only).

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.setGameScore#8ef8ecc0 flags:# edit_message:flags.0?true force:flags.1?true peer:InputPeer id:int user_id:InputUser score:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
edit_messageflags.0?trueSet this flag if the game message should be automatically edited to include the current scoreboard
forceflags.1?trueSet this flag if the high score is allowed to decrease. This can be useful when fixing mistakes or banning cheaters
peerInputPeerUnique identifier of target chat
idintIdentifier of the sent message
user_idInputUserUser identifier
scoreintNew score
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOT_SCORE_NOT_MODIFIEDThe score wasn't modified.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USER_BOT_REQUIREDThis method can only be called by a bot.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.setHistoryTTL b/data/core.telegram.org/method/messages.setHistoryTTL deleted file mode 100644 index 0edfce6a9e..0000000000 --- a/data/core.telegram.org/method/messages.setHistoryTTL +++ /dev/null @@ -1,182 +0,0 @@ - - - - - messages.setHistoryTTL - - - - - - - - - - - - - -
- -
-
-
- -

messages.setHistoryTTL

- -

Set maximum Time-To-Live of all messages in the specified chat

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.setHistoryTTL#b80e5fe4 peer:InputPeer period:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe dialog
periodintAutomatically delete all messages sent in the chat after this many seconds
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400TTL_PERIOD_INVALIDThe specified TTL period is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.setInlineBotResults b/data/core.telegram.org/method/messages.setInlineBotResults deleted file mode 100644 index 7de8b5d0c2..0000000000 --- a/data/core.telegram.org/method/messages.setInlineBotResults +++ /dev/null @@ -1,358 +0,0 @@ - - - - - messages.setInlineBotResults - - - - - - - - - - - - - -
- -
-
-
- -

messages.setInlineBotResults

- -

Answer an inline query, for bots only

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.setInlineBotResults#eb5ea206 flags:# gallery:flags.0?true private:flags.1?true query_id:long results:Vector<InputBotInlineResult> cache_time:int next_offset:flags.2?string switch_pm:flags.3?InlineBotSwitchPM = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
galleryflags.0?trueSet this flag if the results are composed of media files
privateflags.1?trueSet this flag if results may be cached on the server side only for the user that sent the query. By default, results may be returned to any user who sends the same query
query_idlongUnique identifier for the answered query
resultsVector<InputBotInlineResult>Vector of results for the inline query
cache_timeintThe maximum amount of time in seconds that the result of the inline query may be cached on the server. Defaults to 300.
next_offsetflags.2?stringPass the offset that a client should send in the next query with the same text to receive more results. Pass an empty string if there are no more results or if you don‘t support pagination. Offset length can’t exceed 64 bytes.
switch_pmflags.3?InlineBotSwitchPMIf passed, clients will display a button with specified text that switches the user to a private chat with the bot and sends the bot a start message with a certain parameter.
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400ARTICLE_TITLE_EMPTYThe title of the article is empty.
400AUDIO_CONTENT_URL_EMPTYThe remote URL specified in the content field is empty.
400AUDIO_TITLE_EMPTYAn empty audio title was provided.
400BUTTON_DATA_INVALIDThe data of one or more of the buttons you provided is invalid.
400BUTTON_TYPE_INVALIDThe type of one or more of the buttons you provided is invalid.
400BUTTON_URL_INVALIDButton URL invalid.
400DOCUMENT_INVALIDThe specified document is invalid.
400FILE_CONTENT_TYPE_INVALIDFile content-type is invalid.
400FILE_TITLE_EMPTYAn empty file title was specified.
400GIF_CONTENT_TYPE_INVALIDGIF content-type invalid.
400MESSAGE_EMPTYThe provided message is empty.
400MESSAGE_TOO_LONGThe provided message is too long.
400NEXT_OFFSET_INVALIDThe specified offset is longer than 64 bytes.
400PHOTO_CONTENT_TYPE_INVALIDPhoto mime-type invalid.
400PHOTO_CONTENT_URL_EMPTYPhoto URL invalid.
400PHOTO_INVALIDPhoto invalid.
400PHOTO_THUMB_URL_EMPTYPhoto thumbnail URL is empty.
400QUERY_ID_INVALIDThe query ID is invalid.
400REPLY_MARKUP_INVALIDThe provided reply markup is invalid.
400RESULTS_TOO_MUCHToo many results were provided.
400RESULT_ID_DUPLICATEYou provided a duplicate result ID.
400RESULT_TYPE_INVALIDResult type invalid.
400SEND_MESSAGE_MEDIA_INVALIDInvalid media provided.
400SEND_MESSAGE_TYPE_INVALIDThe message type is invalid.
400START_PARAM_INVALIDStart parameter invalid.
400STICKER_DOCUMENT_INVALIDThe specified sticker document is invalid.
403USER_BOT_INVALIDThis method can only be called by a bot.
400VIDEO_TITLE_EMPTYThe specified video title is empty.
400WEBDOCUMENT_INVALIDInvalid webdocument URL provided.
400WEBDOCUMENT_MIME_INVALIDInvalid webdocument mime type provided.
400WEBDOCUMENT_SIZE_TOO_BIGWebdocument is too big!
400WEBDOCUMENT_URL_INVALIDThe specified webdocument URL is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.setInlineGameScore b/data/core.telegram.org/method/messages.setInlineGameScore deleted file mode 100644 index e2c2cd24e2..0000000000 --- a/data/core.telegram.org/method/messages.setInlineGameScore +++ /dev/null @@ -1,198 +0,0 @@ - - - - - messages.setInlineGameScore - - - - - - - - - - - - - -
- -
-
-
- -

messages.setInlineGameScore

- -

Use this method to set the score of the specified user in a game sent as an inline message (bots only).

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.setInlineGameScore#15ad9f64 flags:# edit_message:flags.0?true force:flags.1?true id:InputBotInlineMessageID user_id:InputUser score:int = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
edit_messageflags.0?trueSet this flag if the game message should be automatically edited to include the current scoreboard
forceflags.1?trueSet this flag if the high score is allowed to decrease. This can be useful when fixing mistakes or banning cheaters
idInputBotInlineMessageIDID of the inline message
user_idInputUserUser identifier
scoreintNew score
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400USER_BOT_REQUIREDThis method can only be called by a bot.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.setTyping b/data/core.telegram.org/method/messages.setTyping deleted file mode 100644 index f7f748b7f0..0000000000 --- a/data/core.telegram.org/method/messages.setTyping +++ /dev/null @@ -1,240 +0,0 @@ - - - - - messages.setTyping - - - - - - - - - - - - - -
- -
-
-
- -

messages.setTyping

- -

Sends a current user typing event (see SendMessageAction for all event types) to a conversation partner or group.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.setTyping#58943ee2 flags:# peer:InputPeer top_msg_id:flags.0?int action:SendMessageAction = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerTarget user or group
top_msg_idflags.0?intThread ID
actionSendMessageActionType of action
Parameter added in Layer 17.
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400USER_IS_BLOCKEDYou were blocked by this user.
400USER_IS_BOTBots can't send messages to other bots.
-

Bots can use this method

-

Related pages

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

-

Layers

-

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

-

SendMessageAction

-

User actions. Use this to provide users with detailed info about their chat partners' actions: typing or sending attachments of all kinds.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.startBot b/data/core.telegram.org/method/messages.startBot deleted file mode 100644 index 649ccfb07b..0000000000 --- a/data/core.telegram.org/method/messages.startBot +++ /dev/null @@ -1,224 +0,0 @@ - - - - - messages.startBot - - - - - - - - - - - - - -
- -
-
-
- -

messages.startBot

- -

Start a conversation with a bot using a deep linking parameter

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.startBot#e6df7378 bot:InputUser peer:InputPeer random_id:long start_param:string = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
botInputUserThe bot
peerInputPeerThe chat where to start the bot, can be the bot's private chat or a group
random_idlongRandom ID to avoid resending the same message
start_paramstringDeep linking parameter
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOT_INVALIDThis is not a valid bot.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400START_PARAM_EMPTYThe start parameter is empty.
400START_PARAM_INVALIDStart parameter invalid.
400START_PARAM_TOO_LONGStart parameter is too long.
-

Related pages

-

Bots: An introduction for developers

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.startHistoryImport b/data/core.telegram.org/method/messages.startHistoryImport deleted file mode 100644 index 3bd18a7135..0000000000 --- a/data/core.telegram.org/method/messages.startHistoryImport +++ /dev/null @@ -1,180 +0,0 @@ - - - - - messages.startHistoryImport - - - - - - - - - - - - - -
- -
-
-
- -

messages.startHistoryImport

- -

Complete the history import process, importing all messages into the chat.
-To be called only after initializing the import with messages.initHistoryImport and uploading all files using messages.uploadImportedMedia.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.startHistoryImport#b43df344 peer:InputPeer import_id:long = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe Telegram chat where the messages should be imported, click here for more info »
import_idlongIdentifier of a history import session, returned by messages.initHistoryImport.
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400IMPORT_ID_INVALIDThe specified import ID is invalid.
-

Related pages

-

Imported messages

-

Telegram allows importing messages and media from foreign chat apps.

-

messages.initHistoryImport

-

Import chat history from a foreign chat app into a specific Telegram chat, click here for more info about imported chats ».

-

messages.uploadImportedMedia

-

Upload a media file associated with an imported chat, click here for more info ».

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.toggleDialogPin b/data/core.telegram.org/method/messages.toggleDialogPin deleted file mode 100644 index 9afa039ef5..0000000000 --- a/data/core.telegram.org/method/messages.toggleDialogPin +++ /dev/null @@ -1,187 +0,0 @@ - - - - - messages.toggleDialogPin - - - - - - - - - - - - - -
- -
-
-
- -

messages.toggleDialogPin

- -

Pin/unpin a dialog

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.toggleDialogPin#a731e257 flags:# pinned:flags.0?true peer:InputDialogPeer = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.0?trueWhether to pin or unpin the dialog
peerInputDialogPeerThe dialog to pin
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PINNED_DIALOGS_TOO_MUCHToo many pinned dialogs.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.toggleStickerSets b/data/core.telegram.org/method/messages.toggleStickerSets deleted file mode 100644 index b5ab641ee3..0000000000 --- a/data/core.telegram.org/method/messages.toggleStickerSets +++ /dev/null @@ -1,170 +0,0 @@ - - - - - messages.toggleStickerSets - - - - - - - - - - - - - -
- -
-
-
- -

messages.toggleStickerSets

- -

Apply changes to multiple stickersets

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.toggleStickerSets#b5052fea flags:# uninstall:flags.0?true archive:flags.1?true unarchive:flags.2?true stickersets:Vector<InputStickerSet> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
uninstallflags.0?trueUninstall the specified stickersets
archiveflags.1?trueArchive the specified stickersets
unarchiveflags.2?trueUnarchive the specified stickersets
stickersetsVector<InputStickerSet>Stickersets to act upon
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.uninstallStickerSet b/data/core.telegram.org/method/messages.uninstallStickerSet deleted file mode 100644 index 915b78790f..0000000000 --- a/data/core.telegram.org/method/messages.uninstallStickerSet +++ /dev/null @@ -1,167 +0,0 @@ - - - - - messages.uninstallStickerSet - - - - - - - - - - - - - -
- -
-
-
- -

messages.uninstallStickerSet

- -

Uninstall a stickerset

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.uninstallStickerSet#f96e55de stickerset:InputStickerSet = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
stickersetInputStickerSetThe stickerset to uninstall
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400STICKERSET_INVALIDThe provided sticker set is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.updateDialogFilter b/data/core.telegram.org/method/messages.updateDialogFilter deleted file mode 100644 index 61f26cef9c..0000000000 --- a/data/core.telegram.org/method/messages.updateDialogFilter +++ /dev/null @@ -1,190 +0,0 @@ - - - - - messages.updateDialogFilter - - - - - - - - - - - - - -
- -
-
-
- -

messages.updateDialogFilter

- -

Update folder

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.updateDialogFilter#1ad4a04a flags:# id:int filter:flags.0?DialogFilter = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idintFolder ID
filterflags.0?DialogFilterFolder info
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400FILTER_ID_INVALIDThe specified filter ID is invalid.
400FILTER_INCLUDE_EMPTYThe include_peers vector of the filter is empty.
400FILTER_TITLE_EMPTYThe title field of the filter is empty.
-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.updateDialogFiltersOrder b/data/core.telegram.org/method/messages.updateDialogFiltersOrder deleted file mode 100644 index 53bb20c5f9..0000000000 --- a/data/core.telegram.org/method/messages.updateDialogFiltersOrder +++ /dev/null @@ -1,153 +0,0 @@ - - - - - messages.updateDialogFiltersOrder - - - - - - - - - - - - - -
- -
-
-
- -

messages.updateDialogFiltersOrder

- -

Reorder folders

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.updateDialogFiltersOrder#c563c1e4 order:Vector<int> = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
orderVector<int>New folder order
-

Result

-

Bool

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.updatePinnedMessage b/data/core.telegram.org/method/messages.updatePinnedMessage deleted file mode 100644 index cc90271f29..0000000000 --- a/data/core.telegram.org/method/messages.updatePinnedMessage +++ /dev/null @@ -1,233 +0,0 @@ - - - - - messages.updatePinnedMessage - - - - - - - - - - - - - -
- -
-
-
- -

messages.updatePinnedMessage

- -

Pin a message

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.updatePinnedMessage#d2aaf7ec flags:# silent:flags.0?true unpin:flags.1?true pm_oneside:flags.2?true peer:InputPeer id:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.0?truePin the message silently, without triggering a notification
unpinflags.1?trueWhether the message should unpinned or pinned
pm_onesideflags.2?trueWhether the message should only be pinned on the local side of a one-to-one chat
peerInputPeerThe peer where to pin the message
idintThe message to pin or unpin
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOT_ONESIDE_NOT_AVAILBots can't pin messages in PM just for themselves.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PIN_RESTRICTEDYou can't pin messages.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.uploadEncryptedFile b/data/core.telegram.org/method/messages.uploadEncryptedFile deleted file mode 100644 index 7e41e40df9..0000000000 --- a/data/core.telegram.org/method/messages.uploadEncryptedFile +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.uploadEncryptedFile - - - - - - - - - - - - - -
- -
-
-
- -

messages.uploadEncryptedFile

- -

Upload encrypted file and associate it to a secret chat

-

- -
-
encryptedFileEmpty#c21f497e = EncryptedFile;
-encryptedFile#4a70994c id:long access_hash:long size:int dc_id:int key_fingerprint:int = EncryptedFile;
----functions---
-messages.uploadEncryptedFile#5057c497 peer:InputEncryptedChat file:InputEncryptedFile = EncryptedFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputEncryptedChatThe secret chat to associate the file to
fileInputEncryptedFileThe file
-

Result

-

EncryptedFile

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/messages.uploadMedia b/data/core.telegram.org/method/messages.uploadMedia deleted file mode 100644 index 52cce5e019..0000000000 --- a/data/core.telegram.org/method/messages.uploadMedia +++ /dev/null @@ -1,264 +0,0 @@ - - - - - messages.uploadMedia - - - - - - - - - - - - - -
- -
-
-
- -

messages.uploadMedia

- -

Upload a file and associate it to a chat (without actually sending it to the chat)

-

- -
-
messageMediaEmpty#3ded6320 = MessageMedia;
-messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;
-messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;
-messageMediaContact#70322949 phone_number:string first_name:string last_name:string vcard:string user_id:long = MessageMedia;
-messageMediaUnsupported#9f84f49e = MessageMedia;
-messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;
-messageMediaWebPage#a32dd600 webpage:WebPage = MessageMedia;
-messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;
-messageMediaGame#fdb19008 game:Game = MessageMedia;
-messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
-messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;
-messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
-messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;
----functions---
-messages.uploadMedia#519bc2b1 peer:InputPeer media:InputMedia = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat, can be an inputPeerEmpty for bots
mediaInputMediaFile uploaded in chunks as described in files »
-

Result

-

MessageMedia

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOT_MISSINGThis method can only be run by a bot.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_RESTRICTEDYou can't send messages in this chat, you were restricted.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400FILE_PARTS_INVALIDThe number of file parts is invalid.
400IMAGE_PROCESS_FAILEDFailure while processing image.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MEDIA_INVALIDMedia invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PHOTO_EXT_INVALIDThe extension of the photo is invalid.
400PHOTO_INVALID_DIMENSIONSThe photo dimensions are invalid.
400PHOTO_SAVE_FILE_INVALIDInternal issues, try again later.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400WEBPAGE_CURL_FAILEDFailure while fetching the webpage with cURL.
-

Bots can use this method

-

Related pages

-

inputPeerEmpty

-

An empty constructor, no user or chat is defined.

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/payments.clearSavedInfo b/data/core.telegram.org/method/payments.clearSavedInfo deleted file mode 100644 index efb91efb38..0000000000 --- a/data/core.telegram.org/method/payments.clearSavedInfo +++ /dev/null @@ -1,160 +0,0 @@ - - - - - payments.clearSavedInfo - - - - - - - - - - - - - -
- -
-
-
- -

payments.clearSavedInfo

- -

Clear saved payment information

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-payments.clearSavedInfo#d83d70c1 flags:# credentials:flags.0?true info:flags.1?true = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
credentialsflags.0?trueRemove saved payment credentials
infoflags.1?trueClear the last order settings saved by the user
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/payments.getBankCardData b/data/core.telegram.org/method/payments.getBankCardData deleted file mode 100644 index 258081dcb9..0000000000 --- a/data/core.telegram.org/method/payments.getBankCardData +++ /dev/null @@ -1,166 +0,0 @@ - - - - - payments.getBankCardData - - - - - - - - - - - - - -
- -
-
-
- -

payments.getBankCardData

- -

Get info about a credit card

-

- -
-
payments.bankCardData#3e24e573 title:string open_urls:Vector<BankCardOpenUrl> = payments.BankCardData;
----functions---
-payments.getBankCardData#2e79d779 number:string = payments.BankCardData;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
numberstringCredit card number
-

Result

-

payments.BankCardData

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400BANK_CARD_NUMBER_INVALIDThe specified card number is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/payments.getPaymentForm b/data/core.telegram.org/method/payments.getPaymentForm deleted file mode 100644 index 6eea9d4136..0000000000 --- a/data/core.telegram.org/method/payments.getPaymentForm +++ /dev/null @@ -1,181 +0,0 @@ - - - - - payments.getPaymentForm - - - - - - - - - - - - - -
- -
-
-
- -

payments.getPaymentForm

- -

Get a payment form

-

- -
-
payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
----functions---
-payments.getPaymentForm#8a333c8d flags:# peer:InputPeer msg_id:int theme_params:flags.0?DataJSON = payments.PaymentForm;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerThe peer where the payment form was sent
msg_idintMessage ID of payment form
theme_paramsflags.0?DataJSONA JSON object with the following keys, containing color theme information (integers, RGB24) to pass to the payment provider, to apply in eventual verification pages:
bg_color - Background color
text_color - Text color
hint_color - Hint text color
link_color - Link color
button_color - Button color
button_text_color - Button text color
-

Result

-

payments.PaymentForm

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/payments.getPaymentReceipt b/data/core.telegram.org/method/payments.getPaymentReceipt deleted file mode 100644 index 254a4bea07..0000000000 --- a/data/core.telegram.org/method/payments.getPaymentReceipt +++ /dev/null @@ -1,171 +0,0 @@ - - - - - payments.getPaymentReceipt - - - - - - - - - - - - - -
- -
-
-
- -

payments.getPaymentReceipt

- -

Get payment receipt

-

- -
-
payments.paymentReceipt#70c4fe03 flags:# date:int bot_id:long provider_id:long title:string description:string photo:flags.2?WebDocument invoice:Invoice info:flags.0?PaymentRequestedInfo shipping:flags.1?ShippingOption tip_amount:flags.3?long currency:string total_amount:long credentials_title:string users:Vector<User> = payments.PaymentReceipt;
----functions---
-payments.getPaymentReceipt#2478d1cc peer:InputPeer msg_id:int = payments.PaymentReceipt;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe peer where the payment receipt was sent
msg_idintMessage ID of receipt
-

Result

-

payments.PaymentReceipt

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/payments.getSavedInfo b/data/core.telegram.org/method/payments.getSavedInfo deleted file mode 100644 index 53a1cbbcc1..0000000000 --- a/data/core.telegram.org/method/payments.getSavedInfo +++ /dev/null @@ -1,134 +0,0 @@ - - - - - payments.getSavedInfo - - - - - - - - - - - - - -
- -
-
-
- -

payments.getSavedInfo

- -

Get saved payment information

-

- -
-
payments.savedInfo#fb8fe43c flags:# has_saved_credentials:flags.1?true saved_info:flags.0?PaymentRequestedInfo = payments.SavedInfo;
----functions---
-payments.getSavedInfo#227d824b = payments.SavedInfo;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

payments.SavedInfo

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/payments.sendPaymentForm b/data/core.telegram.org/method/payments.sendPaymentForm deleted file mode 100644 index 775d51218b..0000000000 --- a/data/core.telegram.org/method/payments.sendPaymentForm +++ /dev/null @@ -1,206 +0,0 @@ - - - - - payments.sendPaymentForm - - - - - - - - - - - - - -
- -
-
-
- -

payments.sendPaymentForm

- -

Send compiled payment form

-

- -
-
payments.paymentResult#4e5f810d updates:Updates = payments.PaymentResult;
-payments.paymentVerificationNeeded#d8411139 url:string = payments.PaymentResult;
----functions---
-payments.sendPaymentForm#30c3bc9d flags:# form_id:long peer:InputPeer msg_id:int requested_info_id:flags.0?string shipping_option_id:flags.1?string credentials:InputPaymentCredentials tip_amount:flags.2?long = payments.PaymentResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
form_idlongForm ID
peerInputPeerThe peer where the payment form was sent
msg_idintMessage ID of form
requested_info_idflags.0?stringID of saved and validated order info
shipping_option_idflags.1?stringChosen shipping option ID
credentialsInputPaymentCredentialsPayment credentials
tip_amountflags.2?longTip, in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
-

Result

-

payments.PaymentResult

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
-

Related pages

-

payments.ValidatedRequestedInfo

-

Validated user-provided info

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/payments.validateRequestedInfo b/data/core.telegram.org/method/payments.validateRequestedInfo deleted file mode 100644 index 18b405ddbf..0000000000 --- a/data/core.telegram.org/method/payments.validateRequestedInfo +++ /dev/null @@ -1,186 +0,0 @@ - - - - - payments.validateRequestedInfo - - - - - - - - - - - - - -
- -
-
-
- -

payments.validateRequestedInfo

- -

Submit requested order information for validation

-

- -
-
payments.validatedRequestedInfo#d1451883 flags:# id:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = payments.ValidatedRequestedInfo;
----functions---
-payments.validateRequestedInfo#db103170 flags:# save:flags.0?true peer:InputPeer msg_id:int info:PaymentRequestedInfo = payments.ValidatedRequestedInfo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
saveflags.0?trueSave order information to re-use it for future orders
peerInputPeerPeer where the payment form was sent
msg_idintMessage ID of payment form
infoPaymentRequestedInfoRequested order information
-

Result

-

payments.ValidatedRequestedInfo

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.checkGroupCall b/data/core.telegram.org/method/phone.checkGroupCall deleted file mode 100644 index a576b95a20..0000000000 --- a/data/core.telegram.org/method/phone.checkGroupCall +++ /dev/null @@ -1,154 +0,0 @@ - - - - - phone.checkGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.checkGroupCall

- -

Check whether the group call Server Forwarding Unit is currently receiving the streams with the specified WebRTC source IDs

-

- -
-
---functions---
-phone.checkGroupCall#b59cf977 call:InputGroupCall sources:Vector<int> = Vector<int>;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallGroup call
sourcesVector<int>Source IDs
-

Result

-

Vector<int>

-

Returns an intersection of the source IDs specified in sources, and the source IDs currently being forwarded by the SFU.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.confirmCall b/data/core.telegram.org/method/phone.confirmCall deleted file mode 100644 index 26f29bbc5d..0000000000 --- a/data/core.telegram.org/method/phone.confirmCall +++ /dev/null @@ -1,188 +0,0 @@ - - - - - phone.confirmCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.confirmCall

- -

Complete phone call E2E encryption key exchange »

-

- -
-
phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;
----functions---
-phone.confirmCall#2efe1722 peer:InputPhoneCall g_a:bytes key_fingerprint:long protocol:PhoneCallProtocol = phone.PhoneCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPhoneCallThe phone call
g_abytesParameter for E2E encryption key exchange »
key_fingerprintlongKey fingerprint
protocolPhoneCallProtocolPhone call settings
-

Result

-

phone.PhoneCall

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CALL_ALREADY_DECLINEDThe call was already declined.
400CALL_PEER_INVALIDThe provided call peer object is invalid.
-

Related pages

-

End-to-End Encrypted Voice Calls

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.createGroupCall b/data/core.telegram.org/method/phone.createGroupCall deleted file mode 100644 index 66e6b68e82..0000000000 --- a/data/core.telegram.org/method/phone.createGroupCall +++ /dev/null @@ -1,200 +0,0 @@ - - - - - phone.createGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.createGroupCall

- -

Create a group call or livestream

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.createGroupCall#48cdc6d8 flags:# peer:InputPeer random_id:int title:flags.0?string schedule_date:flags.1?int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerAssociate the group call or livestream to the provided group/supergroup/channel
random_idintUnique client message ID required to prevent creation of duplicate group calls
titleflags.0?stringCall title
schedule_dateflags.1?intFor scheduled group call or livestreams, the absolute date when the group call will start
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400SCHEDULE_DATE_INVALIDInvalid schedule date provided.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.discardCall b/data/core.telegram.org/method/phone.discardCall deleted file mode 100644 index a91a3e61c4..0000000000 --- a/data/core.telegram.org/method/phone.discardCall +++ /dev/null @@ -1,202 +0,0 @@ - - - - - phone.discardCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.discardCall

- -

Refuse or end running call

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.discardCall#b2cbc1c0 flags:# video:flags.0?true peer:InputPhoneCall duration:int reason:PhoneCallDiscardReason connection_id:long = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.0?trueWhether this is a video call
peerInputPhoneCallThe phone call
durationintCall duration
reasonPhoneCallDiscardReasonWhy was the call discarded
connection_idlongPreferred libtgvoip relay ID
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CALL_ALREADY_ACCEPTEDThe call was already accepted.
400CALL_PEER_INVALIDThe provided call peer object is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.editGroupCallMember b/data/core.telegram.org/method/phone.editGroupCallMember deleted file mode 100644 index 168774e042..0000000000 --- a/data/core.telegram.org/method/phone.editGroupCallMember +++ /dev/null @@ -1,167 +0,0 @@ - - - - - phone.editGroupCallMember - - - - - - - - - - - - - -
- -
-
-
- -

phone.editGroupCallMember

- -

Edit information about a given group call participant

-

- -
-
 Method schema is available as of layer 123. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - -
flags#Flags, see TL conditional fields
mutedflags.0?trueWhether to mute or unmute the user
callInputGroupCallGroup call
user_idInputUserThe user in question
-

Result

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.editGroupCallParticipant b/data/core.telegram.org/method/phone.editGroupCallParticipant deleted file mode 100644 index 0b2b587fec..0000000000 --- a/data/core.telegram.org/method/phone.editGroupCallParticipant +++ /dev/null @@ -1,225 +0,0 @@ - - - - - phone.editGroupCallParticipant - - - - - - - - - - - - - -
- -
-
-
- -

phone.editGroupCallParticipant

- -

Edit information about a given group call participant

-

Note: flags.N?Bool parameters can have three possible values:

-
    -
  • If the TL flag is not set, the previous value will not be changed.
  • -
  • If the TL flag is set and contains a boolTrue, the previous value will be overwritten to true.
  • -
  • If the TL flag is set and contains a boolFalse, the previous value will be overwritten to false.
  • -
-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.editGroupCallParticipant#a5273abf flags:# call:InputGroupCall participant:InputPeer muted:flags.0?Bool volume:flags.1?int raise_hand:flags.2?Bool video_stopped:flags.3?Bool video_paused:flags.4?Bool presentation_paused:flags.5?Bool = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
callInputGroupCallThe group call
participantInputPeerThe group call participant (can also be the user itself)
mutedflags.0?BoolWhether to mute or unmute the specified participant
volumeflags.1?intNew volume
raise_handflags.2?BoolRaise or lower hand
video_stoppedflags.3?BoolStart or stop the video stream
video_pausedflags.4?BoolPause or resume the video stream
presentation_pausedflags.5?BoolPause or resume the screen sharing stream
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400USER_VOLUME_INVALIDThe specified user volume is invalid.
-

Related pages

-

Bool

-

Boolean type.

-

boolTrue

-

The constructor can be interpreted as a booleantrue value.

-

boolFalse

-

Constructor may be interpreted as a booleanfalse value.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.editGroupCallTitle b/data/core.telegram.org/method/phone.editGroupCallTitle deleted file mode 100644 index 16bf81792b..0000000000 --- a/data/core.telegram.org/method/phone.editGroupCallTitle +++ /dev/null @@ -1,160 +0,0 @@ - - - - - phone.editGroupCallTitle - - - - - - - - - - - - - -
- -
-
-
- -

phone.editGroupCallTitle

- -

Edit the title of a group call or livestream

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.editGroupCallTitle#1ca6ac0a call:InputGroupCall title:string = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallGroup call
titlestringNew title
-

Result

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.exportGroupCallInvite b/data/core.telegram.org/method/phone.exportGroupCallInvite deleted file mode 100644 index 985569dbde..0000000000 --- a/data/core.telegram.org/method/phone.exportGroupCallInvite +++ /dev/null @@ -1,159 +0,0 @@ - - - - - phone.exportGroupCallInvite - - - - - - - - - - - - - -
- -
-
-
- -

phone.exportGroupCallInvite

- -

Get an invite link for a group call or livestream

-

- -
-
phone.exportedGroupCallInvite#204bd158 link:string = phone.ExportedGroupCallInvite;
----functions---
-phone.exportGroupCallInvite#e6aa647f flags:# can_self_unmute:flags.0?true call:InputGroupCall = phone.ExportedGroupCallInvite;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
can_self_unmuteflags.0?trueFor livestreams, if set, users that join using this link will be able to speak without explicitly requesting permission by (for example by raising their hand).
callInputGroupCallThe group call
-

Result

-

phone.ExportedGroupCallInvite

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.getCallConfig b/data/core.telegram.org/method/phone.getCallConfig deleted file mode 100644 index 0e158854b2..0000000000 --- a/data/core.telegram.org/method/phone.getCallConfig +++ /dev/null @@ -1,134 +0,0 @@ - - - - - phone.getCallConfig - - - - - - - - - - - - - -
- -
-
-
- -

phone.getCallConfig

- -

Get phone call configuration to be passed to libtgvoip's shared config

-

- -
-
dataJSON#7d748d04 data:string = DataJSON;
----functions---
-phone.getCallConfig#55451fa9 = DataJSON;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

DataJSON

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.getGroupCall b/data/core.telegram.org/method/phone.getGroupCall deleted file mode 100644 index f18ff9900e..0000000000 --- a/data/core.telegram.org/method/phone.getGroupCall +++ /dev/null @@ -1,157 +0,0 @@ - - - - - phone.getGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.getGroupCall

- -

Get info about a group call

-

- -
-
phone.groupCall#9e727aad call:GroupCall participants:Vector<GroupCallParticipant> participants_next_offset:string chats:Vector<Chat> users:Vector<User> = phone.GroupCall;
----functions---
-phone.getGroupCall#41845db call:InputGroupCall limit:int = phone.GroupCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallThe group call
limitintMaximum number of results to return, see pagination
-

Result

-

phone.GroupCall

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.getGroupCallJoinAs b/data/core.telegram.org/method/phone.getGroupCallJoinAs deleted file mode 100644 index dea38cc8da..0000000000 --- a/data/core.telegram.org/method/phone.getGroupCallJoinAs +++ /dev/null @@ -1,149 +0,0 @@ - - - - - phone.getGroupCallJoinAs - - - - - - - - - - - - - -
- -
-
-
- -

phone.getGroupCallJoinAs

- -

Get a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.

-

- -
-
phone.joinAsPeers#afe5623f peers:Vector<Peer> chats:Vector<Chat> users:Vector<User> = phone.JoinAsPeers;
----functions---
-phone.getGroupCallJoinAs#ef7c213a peer:InputPeer = phone.JoinAsPeers;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe dialog whose group call or livestream we're trying to join
-

Result

-

phone.JoinAsPeers

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.getGroupParticipants b/data/core.telegram.org/method/phone.getGroupParticipants deleted file mode 100644 index 9e91d3c267..0000000000 --- a/data/core.telegram.org/method/phone.getGroupParticipants +++ /dev/null @@ -1,174 +0,0 @@ - - - - - phone.getGroupParticipants - - - - - - - - - - - - - -
- -
-
-
- -

phone.getGroupParticipants

- -

Get group call participants

-

- -
-
phone.groupParticipants#f47751b6 count:int participants:Vector<GroupCallParticipant> next_offset:string chats:Vector<Chat> users:Vector<User> version:int = phone.GroupParticipants;
----functions---
-phone.getGroupParticipants#c558d8ab call:InputGroupCall ids:Vector<InputPeer> sources:Vector<int> offset:string limit:int = phone.GroupParticipants;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallGroup call
idsVector<InputPeer>If specified, will fetch group participant info about the specified peers
sourcesVector<int>If specified, will fetch group participant info about the specified WebRTC source IDs
offsetstringOffset for results, taken from the next_offset field of phone.groupParticipants, initially an empty string.
Note: if no more results are available, the method call will return an empty next_offset; thus, avoid providing the next_offset returned in phone.groupParticipants if it is empty, to avoid an infinite loop.
limitintMaximum number of results to return, see pagination
-

Result

-

phone.GroupParticipants

-

Related pages

-

phone.groupParticipants

-

Info about the participants of a group call or livestream

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.inviteToGroupCall b/data/core.telegram.org/method/phone.inviteToGroupCall deleted file mode 100644 index 2e2a2a9911..0000000000 --- a/data/core.telegram.org/method/phone.inviteToGroupCall +++ /dev/null @@ -1,177 +0,0 @@ - - - - - phone.inviteToGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.inviteToGroupCall

- -

Invite a set of users to a group call.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.inviteToGroupCall#7b393160 call:InputGroupCall users:Vector<InputUser> = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallThe group call
usersVector<InputUser>The users to invite.
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
403GROUPCALL_FORBIDDENThe group call has already ended.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.joinGroupCall b/data/core.telegram.org/method/phone.joinGroupCall deleted file mode 100644 index 237de0c3d2..0000000000 --- a/data/core.telegram.org/method/phone.joinGroupCall +++ /dev/null @@ -1,202 +0,0 @@ - - - - - phone.joinGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.joinGroupCall

- -

Join a group call

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.joinGroupCall#b132ff7b flags:# muted:flags.0?true video_stopped:flags.2?true call:InputGroupCall join_as:InputPeer invite_hash:flags.1?string params:DataJSON = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
mutedflags.0?trueIf set, the user will be muted by default upon joining.
video_stoppedflags.2?trueIf set, the user's video will be disabled by default upon joining.
callInputGroupCallThe group call
join_asInputPeerJoin the group call, presenting yourself as the specified user/channel
invite_hashflags.1?stringThe invitation hash from the invite link: https://t.me/username?voicechat=hash
paramsDataJSONWebRTC parameters
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400GROUPCALL_SSRC_DUPLICATE_MUCHThe app needs to retry joining the group call with a new SSRC value.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.joinGroupCallPresentation b/data/core.telegram.org/method/phone.joinGroupCallPresentation deleted file mode 100644 index dd564458dc..0000000000 --- a/data/core.telegram.org/method/phone.joinGroupCallPresentation +++ /dev/null @@ -1,180 +0,0 @@ - - - - - phone.joinGroupCallPresentation - - - - - - - - - - - - - -
- -
-
-
- -

phone.joinGroupCallPresentation

- -

Start screen sharing in a call

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.joinGroupCallPresentation#cbea6bc4 call:InputGroupCall params:DataJSON = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallThe group call
paramsDataJSONWebRTC parameters
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
403PARTICIPANT_JOIN_MISSINGTrying to enable a presentation, when the user hasn't joined the Video Chat with phone.joinGroupCall.
-

Related pages

-

phone.joinGroupCall

-

Join a group call

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.leaveGroupCall b/data/core.telegram.org/method/phone.leaveGroupCall deleted file mode 100644 index 30af727e59..0000000000 --- a/data/core.telegram.org/method/phone.leaveGroupCall +++ /dev/null @@ -1,160 +0,0 @@ - - - - - phone.leaveGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.leaveGroupCall

- -

Leave a group call

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.leaveGroupCall#500377f9 call:InputGroupCall source:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallThe group call
sourceintYour source ID
-

Result

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.leaveGroupCallPresentation b/data/core.telegram.org/method/phone.leaveGroupCallPresentation deleted file mode 100644 index 68d2b3a42e..0000000000 --- a/data/core.telegram.org/method/phone.leaveGroupCallPresentation +++ /dev/null @@ -1,155 +0,0 @@ - - - - - phone.leaveGroupCallPresentation - - - - - - - - - - - - - -
- -
-
-
- -

phone.leaveGroupCallPresentation

- -

Stop screen sharing in a group call

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.leaveGroupCallPresentation#1c50d144 call:InputGroupCall = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallThe group call
-

Result

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.receivedCall b/data/core.telegram.org/method/phone.receivedCall deleted file mode 100644 index db38b7ee97..0000000000 --- a/data/core.telegram.org/method/phone.receivedCall +++ /dev/null @@ -1,172 +0,0 @@ - - - - - phone.receivedCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.receivedCall

- -

Optional: notify the server that the user is currently busy in a call: this will automatically refuse all incoming phone calls until the current phone call is ended.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-phone.receivedCall#17d54f61 peer:InputPhoneCall = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPhoneCallThe phone call we're currently in
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CALL_ALREADY_DECLINEDThe call was already declined.
400CALL_PEER_INVALIDThe provided call peer object is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.requestCall b/data/core.telegram.org/method/phone.requestCall deleted file mode 100644 index 7d8637b743..0000000000 --- a/data/core.telegram.org/method/phone.requestCall +++ /dev/null @@ -1,213 +0,0 @@ - - - - - phone.requestCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.requestCall

- -

Start a telegram phone call

-

- -
-
phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;
----functions---
-phone.requestCall#42ff96ed flags:# video:flags.0?true user_id:InputUser random_id:int g_a_hash:bytes protocol:PhoneCallProtocol = phone.PhoneCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.0?trueWhether to start a video call
user_idInputUserDestination of the phone call
random_idintRandom ID to avoid resending the same object
g_a_hashbytesParameter for E2E encryption key exchange »
protocolPhoneCallProtocolPhone call settings
-

Result

-

phone.PhoneCall

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CALL_PROTOCOL_FLAGS_INVALIDCall protocol flags invalid.
400PARTICIPANT_VERSION_OUTDATEDThe other participant does not use an up to date telegram client with support for calls.
400USER_ID_INVALIDThe provided user ID is invalid.
403USER_IS_BLOCKEDYou were blocked by this user.
403USER_PRIVACY_RESTRICTEDThe user's privacy settings do not allow you to do this.
-

Related pages

-

End-to-End Encrypted Voice Calls

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.saveCallDebug b/data/core.telegram.org/method/phone.saveCallDebug deleted file mode 100644 index 43ee57b329..0000000000 --- a/data/core.telegram.org/method/phone.saveCallDebug +++ /dev/null @@ -1,177 +0,0 @@ - - - - - phone.saveCallDebug - - - - - - - - - - - - - -
- -
-
-
- -

phone.saveCallDebug

- -

Send phone call debug data to server

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-phone.saveCallDebug#277add7e peer:InputPhoneCall debug:DataJSON = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPhoneCallPhone call
debugDataJSONDebug statistics obtained from libtgvoip
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CALL_PEER_INVALIDThe provided call peer object is invalid.
400DATA_JSON_INVALIDThe provided JSON data is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.saveDefaultGroupCallJoinAs b/data/core.telegram.org/method/phone.saveDefaultGroupCallJoinAs deleted file mode 100644 index 3882972a27..0000000000 --- a/data/core.telegram.org/method/phone.saveDefaultGroupCallJoinAs +++ /dev/null @@ -1,155 +0,0 @@ - - - - - phone.saveDefaultGroupCallJoinAs - - - - - - - - - - - - - -
- -
-
-
- -

phone.saveDefaultGroupCallJoinAs

- -

Set the default peer that will be used to join a group call in a specific dialog.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-phone.saveDefaultGroupCallJoinAs#575e1f8c peer:InputPeer join_as:InputPeer = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe dialog
join_asInputPeerThe default peer that will be used to join group calls in this dialog, presenting yourself as a specific user/channel.
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.sendSignalingData b/data/core.telegram.org/method/phone.sendSignalingData deleted file mode 100644 index 80a694ced8..0000000000 --- a/data/core.telegram.org/method/phone.sendSignalingData +++ /dev/null @@ -1,155 +0,0 @@ - - - - - phone.sendSignalingData - - - - - - - - - - - - - -
- -
-
-
- -

phone.sendSignalingData

- -

Send VoIP signaling data

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-phone.sendSignalingData#ff7a9383 peer:InputPhoneCall data:bytes = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPhoneCallPhone call
databytesSignaling payload
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.setCallRating b/data/core.telegram.org/method/phone.setCallRating deleted file mode 100644 index f8e8a4a273..0000000000 --- a/data/core.telegram.org/method/phone.setCallRating +++ /dev/null @@ -1,192 +0,0 @@ - - - - - phone.setCallRating - - - - - - - - - - - - - -
- -
-
-
- -

phone.setCallRating

- -

Rate a call

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.setCallRating#59ead627 flags:# user_initiative:flags.0?true peer:InputPhoneCall rating:int comment:string = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
user_initiativeflags.0?trueWhether the user decided on their own initiative to rate the call
peerInputPhoneCallThe call to rate
ratingintRating in 1-5 stars
commentstringAn additional comment
-

Result

-

Updates with info about the rating message sent to the official VoIP bot

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400CALL_PEER_INVALIDThe provided call peer object is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.startScheduledGroupCall b/data/core.telegram.org/method/phone.startScheduledGroupCall deleted file mode 100644 index b39b2f43b0..0000000000 --- a/data/core.telegram.org/method/phone.startScheduledGroupCall +++ /dev/null @@ -1,155 +0,0 @@ - - - - - phone.startScheduledGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.startScheduledGroupCall

- -

Start a scheduled group call.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.startScheduledGroupCall#5680e342 call:InputGroupCall = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallThe scheduled group call
-

Result

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.toggleGroupCallRecord b/data/core.telegram.org/method/phone.toggleGroupCallRecord deleted file mode 100644 index 3cfbb43261..0000000000 --- a/data/core.telegram.org/method/phone.toggleGroupCallRecord +++ /dev/null @@ -1,180 +0,0 @@ - - - - - phone.toggleGroupCallRecord - - - - - - - - - - - - - -
- -
-
-
- -

phone.toggleGroupCallRecord

- -

Start or stop recording a group call: the recorded audio and video streams will be automatically sent to Saved messages (the chat with ourselves).

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.toggleGroupCallRecord#f128c708 flags:# start:flags.0?true video:flags.2?true call:InputGroupCall title:flags.1?string video_portrait:flags.2?Bool = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
startflags.0?trueWhether to start or stop recording
videoflags.2?trueWhether to also record video streams
callInputGroupCallThe group call or livestream
titleflags.1?stringRecording title
video_portraitflags.2?BoolIf video stream recording is enabled, whether to record in portrait or landscape mode
-

Result

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.toggleGroupCallSettings b/data/core.telegram.org/method/phone.toggleGroupCallSettings deleted file mode 100644 index 65aa299bab..0000000000 --- a/data/core.telegram.org/method/phone.toggleGroupCallSettings +++ /dev/null @@ -1,187 +0,0 @@ - - - - - phone.toggleGroupCallSettings - - - - - - - - - - - - - -
- -
-
-
- -

phone.toggleGroupCallSettings

- -

Change group call settings

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.toggleGroupCallSettings#74bbb43d flags:# reset_invite_hash:flags.1?true call:InputGroupCall join_muted:flags.0?Bool = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
reset_invite_hashflags.1?trueInvalidate existing invite links
callInputGroupCallGroup call
join_mutedflags.0?BoolWhether all users will bthat join this group calle muted by default upon joining the group call
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400GROUPCALL_NOT_MODIFIEDGroup call settings weren't modified.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/phone.toggleGroupCallStartSubscription b/data/core.telegram.org/method/phone.toggleGroupCallStartSubscription deleted file mode 100644 index 15d6aff834..0000000000 --- a/data/core.telegram.org/method/phone.toggleGroupCallStartSubscription +++ /dev/null @@ -1,160 +0,0 @@ - - - - - phone.toggleGroupCallStartSubscription - - - - - - - - - - - - - -
- -
-
-
- -

phone.toggleGroupCallStartSubscription

- -

Subscribe or unsubscribe to a scheduled group call

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.toggleGroupCallStartSubscription#219c34e6 call:InputGroupCall subscribed:Bool = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallScheduled group call
subscribedBoolEnable or disable subscription
-

Result

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/photos.deletePhotos b/data/core.telegram.org/method/photos.deletePhotos deleted file mode 100644 index 03ca8188b5..0000000000 --- a/data/core.telegram.org/method/photos.deletePhotos +++ /dev/null @@ -1,148 +0,0 @@ - - - - - photos.deletePhotos - - - - - - - - - - - - - -
- -
-
-
- -

photos.deletePhotos

- -

Deletes profile photos.

-

- -
-
---functions---
-photos.deletePhotos#87cf7f2f id:Vector<InputPhoto> = Vector<long>;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idVector<InputPhoto>Input photos to delete
-

Result

-

Method returns a list of successfully deleted photos in Vector<long>

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/photos.getUserPhotos b/data/core.telegram.org/method/photos.getUserPhotos deleted file mode 100644 index 210930d62c..0000000000 --- a/data/core.telegram.org/method/photos.getUserPhotos +++ /dev/null @@ -1,193 +0,0 @@ - - - - - photos.getUserPhotos - - - - - - - - - - - - - -
- -
-
-
- -

photos.getUserPhotos

- -

Returns the list of user photos.

-

- -
-
photos.photos#8dca6aa5 photos:Vector<Photo> users:Vector<User> = photos.Photos;
-photos.photosSlice#15051f54 count:int photos:Vector<Photo> users:Vector<User> = photos.Photos;
----functions---
-photos.getUserPhotos#91cd32a8 user_id:InputUser offset:int max_id:long limit:int = photos.Photos;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idInputUserUser ID
offsetintNumber of list elements to be skipped
max_idlongIf a positive value was transferred, the method will return only photos with IDs less than the set one
limitintNumber of list elements to be returned
-

Result

-

photos.Photos

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MAX_ID_INVALIDThe provided max ID is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400USER_ID_INVALIDThe provided user ID is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/photos.updateProfilePhoto b/data/core.telegram.org/method/photos.updateProfilePhoto deleted file mode 100644 index 5c51006165..0000000000 --- a/data/core.telegram.org/method/photos.updateProfilePhoto +++ /dev/null @@ -1,196 +0,0 @@ - - - - - photos.updateProfilePhoto - - - - - - - - - - - - - -
- -
-
-
- -

photos.updateProfilePhoto

- -

Installs a previously uploaded photo as a profile photo.

-

- -
-
photos.photo#20212ca8 photo:Photo users:Vector<User> = photos.Photo;
----functions---
-photos.updateProfilePhoto#72d4742c id:InputPhoto = photos.Photo;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idInputPhotoInput photo
-

Result

-

UserProfilePhoto

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400ALBUM_PHOTOS_TOO_MANYToo many.
400FILE_PARTS_INVALIDThe number of file parts is invalid.
400IMAGE_PROCESS_FAILEDFailure while processing image.
400LOCATION_INVALIDThe provided location is invalid.
400PHOTO_CROP_SIZE_SMALLPhoto is too small.
400PHOTO_EXT_INVALIDThe extension of the photo is invalid.
400PHOTO_ID_INVALIDPhoto ID invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/stats.getBroadcastStats b/data/core.telegram.org/method/stats.getBroadcastStats deleted file mode 100644 index 069ce9bb0f..0000000000 --- a/data/core.telegram.org/method/stats.getBroadcastStats +++ /dev/null @@ -1,194 +0,0 @@ - - - - - stats.getBroadcastStats - - - - - - - - - - - - - -
- -
-
-
- -

stats.getBroadcastStats

- -

Get channel statistics

-

- -
-
stats.broadcastStats#bdf78394 period:StatsDateRangeDays followers:StatsAbsValueAndPrev views_per_post:StatsAbsValueAndPrev shares_per_post:StatsAbsValueAndPrev enabled_notifications:StatsPercentValue growth_graph:StatsGraph followers_graph:StatsGraph mute_graph:StatsGraph top_hours_graph:StatsGraph interactions_graph:StatsGraph iv_interactions_graph:StatsGraph views_by_source_graph:StatsGraph new_followers_by_source_graph:StatsGraph languages_graph:StatsGraph recent_message_interactions:Vector<MessageInteractionCounters> = stats.BroadcastStats;
----functions---
-stats.getBroadcastStats#ab42441a flags:# dark:flags.0?true channel:InputChannel = stats.BroadcastStats;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
darkflags.0?trueWhether to enable dark theme for graph colors
channelInputChannelThe channel
-

Result

-

stats.BroadcastStats

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BROADCAST_REQUIREDThis method can only be called on a channel, please use stats.getMegagroupStats for supergroups.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/stats.getMegagroupStats b/data/core.telegram.org/method/stats.getMegagroupStats deleted file mode 100644 index ddc3e8eefd..0000000000 --- a/data/core.telegram.org/method/stats.getMegagroupStats +++ /dev/null @@ -1,191 +0,0 @@ - - - - - stats.getMegagroupStats - - - - - - - - - - - - - -
- -
-
-
- -

stats.getMegagroupStats

- -

Get supergroup statistics

-

- -
-
stats.megagroupStats#ef7ff916 period:StatsDateRangeDays members:StatsAbsValueAndPrev messages:StatsAbsValueAndPrev viewers:StatsAbsValueAndPrev posters:StatsAbsValueAndPrev growth_graph:StatsGraph members_graph:StatsGraph new_members_by_source_graph:StatsGraph languages_graph:StatsGraph messages_graph:StatsGraph actions_graph:StatsGraph top_hours_graph:StatsGraph weekdays_graph:StatsGraph top_posters:Vector<StatsGroupTopPoster> top_admins:Vector<StatsGroupTopAdmin> top_inviters:Vector<StatsGroupTopInviter> users:Vector<User> = stats.MegagroupStats;
----functions---
-stats.getMegagroupStats#dcdf8607 flags:# dark:flags.0?true channel:InputChannel = stats.MegagroupStats;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
darkflags.0?trueWhether to enable dark theme for graph colors
channelInputChannelSupergroup ID
-

Result

-

stats.MegagroupStats

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400MEGAGROUP_REQUIREDYou can only use this method on a supergroup.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/stats.getMessagePublicForwards b/data/core.telegram.org/method/stats.getMessagePublicForwards deleted file mode 100644 index 9fcd2812f4..0000000000 --- a/data/core.telegram.org/method/stats.getMessagePublicForwards +++ /dev/null @@ -1,212 +0,0 @@ - - - - - stats.getMessagePublicForwards - - - - - - - - - - - - - -
- -
-
-
- -

stats.getMessagePublicForwards

- -

Obtains a list of messages, indicating to which other public channels was a channel message forwarded.
-Will return a list of messages with peer_id equal to the public channel to which this message was forwarded.

-

- -
-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
----functions---
-stats.getMessagePublicForwards#5630281b channel:InputChannel msg_id:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelSource channel
msg_idintSource message ID
offset_rateintInitially 0, then set to the next_rate parameter of messages.messagesSlice
offset_peerInputPeerOffsets for pagination, for more info click here
offset_idintOffsets for pagination, for more info click here
limitintMaximum number of results to return, see pagination
-

Result

-

messages.Messages

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
-

Related pages

-

messages.messagesSlice

-

Incomplete list of messages and auxiliary data.

-

Pagination in the API

-

How to fetch results from large lists of objects.

-

message

-

A message

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/stats.getMessageStats b/data/core.telegram.org/method/stats.getMessageStats deleted file mode 100644 index 3c0ffc4335..0000000000 --- a/data/core.telegram.org/method/stats.getMessageStats +++ /dev/null @@ -1,189 +0,0 @@ - - - - - stats.getMessageStats - - - - - - - - - - - - - -
- -
-
-
- -

stats.getMessageStats

- -

Get message statistics

-

- -
-
stats.messageStats#8999f295 views_graph:StatsGraph = stats.MessageStats;
----functions---
-stats.getMessageStats#b6e0a3f5 flags:# dark:flags.0?true channel:InputChannel msg_id:int = stats.MessageStats;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
darkflags.0?trueWhether to enable dark theme for graph colors
channelInputChannelChannel ID
msg_idintMessage ID
-

Result

-

stats.MessageStats

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/stats.loadAsyncGraph b/data/core.telegram.org/method/stats.loadAsyncGraph deleted file mode 100644 index e73034a5ea..0000000000 --- a/data/core.telegram.org/method/stats.loadAsyncGraph +++ /dev/null @@ -1,193 +0,0 @@ - - - - - stats.loadAsyncGraph - - - - - - - - - - - - - -
- -
-
-
- -

stats.loadAsyncGraph

- -

Load channel statistics graph asynchronously

-

- -
-
statsGraphAsync#4a27eb2d token:string = StatsGraph;
-statsGraphError#bedc9822 error:string = StatsGraph;
-statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
----functions---
-stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
tokenstringGraph token from statsGraphAsync constructor
xflags.0?longZoom value, if required
-

Result

-

StatsGraph

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400GRAPH_EXPIRED_RELOADThis graph has expired, please obtain a new graph token.
400GRAPH_INVALID_RELOADInvalid graph token provided, please reload the stats and provide the updated token.
400GRAPH_OUTDATED_RELOADThe graph is outdated, please get a new async token using stats.getBroadcastStats.
-

Related pages

-

statsGraphAsync

-

This channel statistics graph must be generated asynchronously using stats.loadAsyncGraph to reduce server load

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/stickers.addStickerToSet b/data/core.telegram.org/method/stickers.addStickerToSet deleted file mode 100644 index 2225d38b19..0000000000 --- a/data/core.telegram.org/method/stickers.addStickerToSet +++ /dev/null @@ -1,187 +0,0 @@ - - - - - stickers.addStickerToSet - - - - - - - - - - - - - -
- -
-
-
- -

stickers.addStickerToSet

- -

Add a sticker to a stickerset, bots only. The sticker set must have been created by the bot.

-

- -
-
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
----functions---
-stickers.addStickerToSet#8653febe stickerset:InputStickerSet sticker:InputStickerSetItem = messages.StickerSet;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
stickersetInputStickerSetThe stickerset
stickerInputStickerSetItemThe sticker
-

Result

-

messages.StickerSet

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOT_MISSINGThis method can only be run by a bot.
400STICKERSET_INVALIDThe provided sticker set is invalid.
400STICKER_PNG_NOPNGOne of the specified stickers is not a valid PNG file.
400STICKER_TGS_NOTGSInvalid TGS sticker provided.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/stickers.changeStickerPosition b/data/core.telegram.org/method/stickers.changeStickerPosition deleted file mode 100644 index 1b97809f09..0000000000 --- a/data/core.telegram.org/method/stickers.changeStickerPosition +++ /dev/null @@ -1,177 +0,0 @@ - - - - - stickers.changeStickerPosition - - - - - - - - - - - - - -
- -
-
-
- -

stickers.changeStickerPosition

- -

Changes the absolute position of a sticker in the set to which it belongs; for bots only. The sticker set must have been created by the bot

-

- -
-
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
----functions---
-stickers.changeStickerPosition#ffb6d4ca sticker:InputDocument position:int = messages.StickerSet;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
stickerInputDocumentThe sticker
positionintThe new position of the sticker, zero-based
-

Result

-

messages.StickerSet

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOT_MISSINGThis method can only be run by a bot.
400STICKER_INVALIDThe provided sticker is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/stickers.checkShortName b/data/core.telegram.org/method/stickers.checkShortName deleted file mode 100644 index d4fe11206b..0000000000 --- a/data/core.telegram.org/method/stickers.checkShortName +++ /dev/null @@ -1,172 +0,0 @@ - - - - - stickers.checkShortName - - - - - - - - - - - - - -
- -
-
-
- -

stickers.checkShortName

- -

Check whether the given short name is available

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-stickers.checkShortName#284b3639 short_name:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
short_namestringShort name
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400SHORT_NAME_INVALIDThe specified short name is invalid.
400SHORT_NAME_OCCUPIEDThe specified short name is already in use.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/stickers.removeStickerFromSet b/data/core.telegram.org/method/stickers.removeStickerFromSet deleted file mode 100644 index 9b0859defc..0000000000 --- a/data/core.telegram.org/method/stickers.removeStickerFromSet +++ /dev/null @@ -1,172 +0,0 @@ - - - - - stickers.removeStickerFromSet - - - - - - - - - - - - - -
- -
-
-
- -

stickers.removeStickerFromSet

- -

Remove a sticker from the set where it belongs, bots only. The sticker set must have been created by the bot.

-

- -
-
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
----functions---
-stickers.removeStickerFromSet#f7760f51 sticker:InputDocument = messages.StickerSet;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
stickerInputDocumentThe sticker to remove
-

Result

-

messages.StickerSet

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOT_MISSINGThis method can only be run by a bot.
400STICKER_INVALIDThe provided sticker is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/stickers.setStickerSetThumb b/data/core.telegram.org/method/stickers.setStickerSetThumb deleted file mode 100644 index ef8e968631..0000000000 --- a/data/core.telegram.org/method/stickers.setStickerSetThumb +++ /dev/null @@ -1,182 +0,0 @@ - - - - - stickers.setStickerSetThumb - - - - - - - - - - - - - -
- -
-
-
- -

stickers.setStickerSetThumb

- -

Set stickerset thumbnail

-

- -
-
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
----functions---
-stickers.setStickerSetThumb#9a364e30 stickerset:InputStickerSet thumb:InputDocument = messages.StickerSet;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
stickersetInputStickerSetStickerset
thumbInputDocumentThumbnail
-

Result

-

messages.StickerSet

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400STICKERSET_INVALIDThe provided sticker set is invalid.
400STICKER_THUMB_PNG_NOPNGIncorrect stickerset thumb file provided, PNG / WEBP expected.
400STICKER_THUMB_TGS_NOTGSIncorrect stickerset TGS thumb file provided.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/stickers.suggestShortName b/data/core.telegram.org/method/stickers.suggestShortName deleted file mode 100644 index 8fed309902..0000000000 --- a/data/core.telegram.org/method/stickers.suggestShortName +++ /dev/null @@ -1,166 +0,0 @@ - - - - - stickers.suggestShortName - - - - - - - - - - - - - -
- -
-
-
- -

stickers.suggestShortName

- -

Suggests a short name for a given stickerpack name

-

- -
-
stickers.suggestedShortName#85fea03f short_name:string = stickers.SuggestedShortName;
----functions---
-stickers.suggestShortName#4dafc503 title:string = stickers.SuggestedShortName;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
titlestringSticker pack name
-

Result

-

stickers.SuggestedShortName

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400TITLE_INVALIDThe specified stickerpack title is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/updates.getChannelDifference b/data/core.telegram.org/method/updates.getChannelDifference deleted file mode 100644 index c9d897c76a..0000000000 --- a/data/core.telegram.org/method/updates.getChannelDifference +++ /dev/null @@ -1,247 +0,0 @@ - - - - - updates.getChannelDifference - - - - - - - - - - - - - -
- -
-
-
- -

updates.getChannelDifference

- -

Returns the difference between the current state of updates of a certain channel and transmitted.

-

- -
-
updates.channelDifferenceEmpty#3e11affb flags:# final:flags.0?true pts:int timeout:flags.1?int = updates.ChannelDifference;
-updates.channelDifferenceTooLong#a4bcc6fe flags:# final:flags.0?true timeout:flags.1?int dialog:Dialog messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
-updates.channelDifference#2064674e flags:# final:flags.0?true pts:int timeout:flags.1?int new_messages:Vector<Message> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
----functions---
-updates.getChannelDifference#3173d78 flags:# force:flags.0?true channel:InputChannel filter:ChannelMessagesFilter pts:int limit:int = updates.ChannelDifference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
forceflags.0?trueSet to true to skip some possibly unneeded updates and reduce server-side load
channelInputChannelThe channel
filterChannelMessagesFilterMesssage filter
ptsintPersistent timestamp (see updates)
limitintHow many updates to fetch, max 100000
Ordinary (non-bot) users are supposed to pass 10-100
-

Result

-

updates.ChannelDifference

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
403CHANNEL_PUBLIC_GROUP_NAchannel/supergroup not available.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400FROM_MESSAGE_BOT_DISABLEDBots can't use fromMessage min constructors.
400MSG_ID_INVALIDInvalid message ID provided.
400PERSISTENT_TIMESTAMP_EMPTYPersistent timestamp empty.
400PERSISTENT_TIMESTAMP_INVALIDPersistent timestamp invalid.
400PINNED_DIALOGS_TOO_MUCHToo many pinned dialogs.
400RANGES_INVALIDInvalid range provided.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
-

Bots can use this method

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/updates.getDifference b/data/core.telegram.org/method/updates.getDifference deleted file mode 100644 index 3eacfb81e1..0000000000 --- a/data/core.telegram.org/method/updates.getDifference +++ /dev/null @@ -1,225 +0,0 @@ - - - - - updates.getDifference - - - - - - - - - - - - - -
- -
-
-
- -

updates.getDifference

- -

Get new updates.

-

- -
-
updates.differenceEmpty#5d75a138 date:int seq:int = updates.Difference;
-updates.difference#f49ca0 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> state:updates.State = updates.Difference;
-updates.differenceSlice#a8fb1981 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> intermediate_state:updates.State = updates.Difference;
-updates.differenceTooLong#4afe8f6d pts:int = updates.Difference;
----functions---
-updates.getDifference#25939651 flags:# pts:int pts_total_limit:flags.0?int date:int qts:int = updates.Difference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
ptsintPTS, see updates.
pts_total_limitflags.0?intFor fast updating: if provided and pts + pts_total_limit < remote pts, updates.differenceTooLong will be returned.
Simply tells the server to not return the difference if it is bigger than pts_total_limit
If the remote pts is too big (> ~4000000), this field will default to 1000000
dateintdate, see updates.
qtsintQTS, see updates.
-

Result

-

updates.Difference

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400CDN_METHOD_INVALIDYou can't call this method in a CDN DC.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400DATE_EMPTYDate empty.
400MSG_ID_INVALIDInvalid message ID provided.
400PERSISTENT_TIMESTAMP_EMPTYPersistent timestamp empty.
400PERSISTENT_TIMESTAMP_INVALIDPersistent timestamp invalid.
-

Bots can use this method

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

updates.differenceTooLong

-

The difference is too long, and the specified state must be used to refetch updates.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/updates.getState b/data/core.telegram.org/method/updates.getState deleted file mode 100644 index a0ea6efa33..0000000000 --- a/data/core.telegram.org/method/updates.getState +++ /dev/null @@ -1,135 +0,0 @@ - - - - - updates.getState - - - - - - - - - - - - - -
- -
-
-
- -

updates.getState

- -

Returns a current state of updates.

-

- -
-
updates.state#a56c2a3e pts:int qts:int date:int seq:int unread_count:int = updates.State;
----functions---
-updates.getState#edd4882a = updates.State;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

updates.State

-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/upload.getCdnFile b/data/core.telegram.org/method/upload.getCdnFile deleted file mode 100644 index cdae467550..0000000000 --- a/data/core.telegram.org/method/upload.getCdnFile +++ /dev/null @@ -1,162 +0,0 @@ - - - - - upload.getCdnFile - - - - - - - - - - - - - -
- -
-
-
- -

upload.getCdnFile

- -

Download a CDN file.

-

- -
-
upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;
-upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;
----functions---
-upload.getCdnFile#2000bcc3 file_token:bytes offset:int limit:int = upload.CdnFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
file_tokenbytesFile token
offsetintOffset of chunk to download
limitintLength of chunk to download
-

Result

-

upload.CdnFile

-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/upload.getCdnFileHashes b/data/core.telegram.org/method/upload.getCdnFileHashes deleted file mode 100644 index 123454e5dc..0000000000 --- a/data/core.telegram.org/method/upload.getCdnFileHashes +++ /dev/null @@ -1,178 +0,0 @@ - - - - - upload.getCdnFileHashes - - - - - - - - - - - - - -
- -
-
-
- -

upload.getCdnFileHashes

- -

Get SHA256 hashes for verifying downloaded CDN files

-

- -
-
---functions---
-upload.getCdnFileHashes#4da54231 file_token:bytes offset:int = Vector<FileHash>;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
file_tokenbytesFile
offsetintOffset from which to start getting hashes
-

Result

-

Vector<FileHash>

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CDN_METHOD_INVALIDYou can't call this method in a CDN DC.
400RSA_DECRYPT_FAILEDInternal RSA decryption failed.
-

Bots can use this method

-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/upload.getFile b/data/core.telegram.org/method/upload.getFile deleted file mode 100644 index 6ffa2293fd..0000000000 --- a/data/core.telegram.org/method/upload.getFile +++ /dev/null @@ -1,252 +0,0 @@ - - - - - upload.getFile - - - - - - - - - - - - - -
- -
-
-
- -

upload.getFile

- -

Returns content of a whole file or its part.

-

- -
-
upload.file#96a18d5 type:storage.FileType mtime:int bytes:bytes = upload.File;
-upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;
----functions---
-upload.getFile#b15a9afc flags:# precise:flags.0?true cdn_supported:flags.1?true location:InputFileLocation offset:int limit:int = upload.File;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
preciseflags.0?trueDisable some checks on limit and offset values, useful for example to stream videos by keyframes
cdn_supportedflags.1?trueWhether the current client supports CDN downloads
locationInputFileLocationFile location
offsetintNumber of bytes to be skipped
limitintNumber of bytes to be returned
-

Result

-

upload.File

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
406FILEREF_UPGRADE_NEEDEDThe client has to be updated in order to support file references.
400FILE_ID_INVALIDThe provided file id is invalid.
400FILE_REFERENCE_*The file reference expired, it must be refreshed.
400FILE_REFERENCE_EXPIREDFile reference expired, it must be refetched as described in https://core.telegram.org/api/file_reference.
400LIMIT_INVALIDThe provided limit is invalid.
400LOCATION_INVALIDThe provided location is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400OFFSET_INVALIDThe provided offset is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Bots can use this method

-

Related pages

-

Encrypted CDNs for Speed and Security

-

File references

-

How to handle file references.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/upload.getFileHashes b/data/core.telegram.org/method/upload.getFileHashes deleted file mode 100644 index 161326a0cc..0000000000 --- a/data/core.telegram.org/method/upload.getFileHashes +++ /dev/null @@ -1,171 +0,0 @@ - - - - - upload.getFileHashes - - - - - - - - - - - - - -
- -
-
-
- -

upload.getFileHashes

- -

Get SHA256 hashes for verifying downloaded files

-

- -
-
---functions---
-upload.getFileHashes#c7025931 location:InputFileLocation offset:int = Vector<FileHash>;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
locationInputFileLocationFile
offsetintOffset from which to get file hashes
-

Result

-

Vector<FileHash>

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400LOCATION_INVALIDThe provided location is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/upload.getWebFile b/data/core.telegram.org/method/upload.getWebFile deleted file mode 100644 index 8b7d09fef5..0000000000 --- a/data/core.telegram.org/method/upload.getWebFile +++ /dev/null @@ -1,176 +0,0 @@ - - - - - upload.getWebfile - - - - - - - - - - - - - -
- -
-
-
- -

upload.getWebfile

- -

Returns content of an HTTP file or a part, by proxying the request through telegram.

-

- -
-
upload.webFile#21e753bc size:int mime_type:string file_type:storage.FileType mtime:int bytes:bytes = upload.WebFile;
----functions---
-upload.getWebFile#24e6818d location:InputWebFileLocation offset:int limit:int = upload.WebFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
locationInputWebFileLocationThe file to download
offsetintNumber of bytes to be skipped
limitintNumber of bytes to be returned
-

Result

-

upload.WebFile

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400LOCATION_INVALIDThe provided location is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/upload.reuploadCdnFile b/data/core.telegram.org/method/upload.reuploadCdnFile deleted file mode 100644 index 7460bf1287..0000000000 --- a/data/core.telegram.org/method/upload.reuploadCdnFile +++ /dev/null @@ -1,173 +0,0 @@ - - - - - upload.reuploadCdnFile - - - - - - - - - - - - - -
- -
-
-
- -

upload.reuploadCdnFile

- -

Request a reupload of a certain file to a CDN DC.

-

- -
-
---functions---
-upload.reuploadCdnFile#9b2754a8 file_token:bytes request_token:bytes = Vector<FileHash>;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
file_tokenbytesFile token
request_tokenbytesRequest token
-

Result

-

Vector<FileHash>

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400RSA_DECRYPT_FAILEDInternal RSA decryption failed.
-

Bots can use this method

-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/upload.saveBigFilePart b/data/core.telegram.org/method/upload.saveBigFilePart deleted file mode 100644 index 1a3bf68b2b..0000000000 --- a/data/core.telegram.org/method/upload.saveBigFilePart +++ /dev/null @@ -1,208 +0,0 @@ - - - - - upload.saveBigFilePart - - - - - - - - - - - - - -
- -
-
-
- -

upload.saveBigFilePart

- -

Saves a part of a large file (over 10Mb in size) to be later passed to one of the methods.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-upload.saveBigFilePart#de7b673d file_id:long file_part:int file_total_parts:int bytes:bytes = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
file_idlongRandom file id, created by the client
file_partintPart sequence number
file_total_partsintTotal number of parts
bytesbytesBinary data, part contents
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400FILE_PARTS_INVALIDThe number of file parts is invalid.
400FILE_PART_EMPTYThe provided file part is empty.
400FILE_PART_INVALIDThe file part number is invalid.
400FILE_PART_SIZE_CHANGEDProvided file part size has changed.
400FILE_PART_SIZE_INVALIDThe provided file part size is invalid.
400FILE_PART_TOO_BIGThe uploaded file part is too big.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/upload.saveFilePart b/data/core.telegram.org/method/upload.saveFilePart deleted file mode 100644 index f70f3ead83..0000000000 --- a/data/core.telegram.org/method/upload.saveFilePart +++ /dev/null @@ -1,183 +0,0 @@ - - - - - upload.saveFilePart - - - - - - - - - - - - - -
- -
-
-
- -

upload.saveFilePart

- -

Saves a part of file for futher sending to one of the methods.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-upload.saveFilePart#b304a621 file_id:long file_part:int bytes:bytes = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
file_idlongRandom file identifier created by the client
file_partintNumerical order of a part
bytesbytesBinary data, contend of a part
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400FILE_PART_EMPTYThe provided file part is empty.
400FILE_PART_INVALIDThe file part number is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/users.getFullUser b/data/core.telegram.org/method/users.getFullUser deleted file mode 100644 index 2c49abe91b..0000000000 --- a/data/core.telegram.org/method/users.getFullUser +++ /dev/null @@ -1,177 +0,0 @@ - - - - - users.getFullUser - - - - - - - - - - - - - -
- -
-
-
- -

users.getFullUser

- -

Returns extended user info by ID.

-

- -
-
userFull#d697ff05 flags:# blocked:flags.0?true phone_calls_available:flags.4?true phone_calls_private:flags.5?true can_pin_message:flags.7?true has_scheduled:flags.12?true video_calls_available:flags.13?true user:User about:flags.1?string settings:PeerSettings profile_photo:flags.2?Photo notify_settings:PeerNotifySettings bot_info:flags.3?BotInfo pinned_msg_id:flags.6?int common_chats_count:int folder_id:flags.11?int ttl_period:flags.14?int theme_emoticon:flags.15?string = UserFull;
----functions---
-users.getFullUser#ca30a5b1 id:InputUser = UserFull;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idInputUserUser ID
-

Result

-

Returns a UserFull object containing user info.

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400USER_ID_INVALIDThe provided user ID is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/users.getUsers b/data/core.telegram.org/method/users.getUsers deleted file mode 100644 index 4729571195..0000000000 --- a/data/core.telegram.org/method/users.getUsers +++ /dev/null @@ -1,191 +0,0 @@ - - - - - users.getUsers - - - - - - - - - - - - - -
- -
-
-
- -

users.getUsers

- -

Returns basic user info according to their identifiers.

-

- -
-
---functions---
-users.getUsers#d91a548 id:Vector<InputUser> = Vector<User>;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idVector<InputUser>List of user identifiers
-

Result

-

Vector<User>

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CONNECTION_NOT_INITEDConnection not initialized.
400INPUT_LAYER_INVALIDThe provided layer is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/method/users.setSecureValueErrors b/data/core.telegram.org/method/users.setSecureValueErrors deleted file mode 100644 index c592e08479..0000000000 --- a/data/core.telegram.org/method/users.setSecureValueErrors +++ /dev/null @@ -1,176 +0,0 @@ - - - - - users.setSecureValueErrors - - - - - - - - - - - - - -
- -
-
-
- -

users.setSecureValueErrors

- -

Notify the user that the sent passport data contains some errors The user will not be able to re-submit their Passport data to you until the errors are fixed (the contents of the field for which you returned the error must change).

-

Use this if the data submitted by the user doesn't satisfy the standards your service requires for any reason. For example, if a birthday date seems invalid, a submitted document is blurry, a scan shows evidence of tampering, etc. Supply some details in the error message to make sure the user knows how to correct the issues.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-users.setSecureValueErrors#90c894b5 id:InputUser errors:Vector<SecureValueError> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idInputUserThe user
errorsVector<SecureValueError>Errors
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400USER_ID_INVALIDThe provided user ID is invalid.
-

Bots can use this method

-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/methods.html b/data/core.telegram.org/methods.html deleted file mode 100644 index 1b0c6e7f5a..0000000000 --- a/data/core.telegram.org/methods.html +++ /dev/null @@ -1,2306 +0,0 @@ - - - - - Methods - - - - - - - - - - - - - -
- -
-
-
- -

Methods

- -

Accepting the Terms of Service

- - - - - - - - - - - - - - - - - -
NameDescription
help.getTermsOfServiceUpdateLook for updates of telegram's terms of service
help.acceptTermsOfServiceAccept the new terms of service
-

Dealing with spam and ToS violations

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
account.reportPeerReport a peer for violation of telegram's Terms of Service
account.reportProfilePhotoReport a profile photo of a dialog
channels.reportSpamReports some messages from a user in a supergroup as spam; requires administrator rights in the supergroup
messages.reportReport a message in a chat for violation of telegram's Terms of Service
messages.reportSpamReport a new incoming chat for spam, if the peer settings of the chat allow us to do that
messages.reportEncryptedSpamReport a secret chat for spam
-

Fetching configuration

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
help.getAppChangelogGet changelog of current app.
Typically, an updates constructor will be returned, containing one or more updateServiceNotification updates with app-specific changelogs.
help.getAppConfigGet app-specific configuration, see client configuration for more info on the result.
help.getAppUpdateReturns information on update availability for the current application.
help.getConfigReturns current configuration, including data center configuration.
help.getInviteTextReturns localized text of a text message with an invitation.
help.getNearestDcReturns info on data centre nearest to the user.
help.getSupportReturns the support user for the 'ask a question' feature.
help.getSupportNameGet localized name of the telegram support user
help.getCountriesListGet name, ISO code, localized name and phone codes/patterns of all available countries
help.dismissSuggestionDismiss a suggestion, see here for more info ».
-

Login via QR code

- - - - - - - - - - - - - - - - - - - - - -
NameDescription
auth.exportLoginTokenGenerate a login token, for login via QR code.
The generated login token should be encoded using base64url, then shown as a tg://login?token=base64encodedtoken URL in the QR code.

For more info, see login via QR code.
auth.acceptLoginTokenAccept QR code login token, logging in the app that generated it.

Returns info about the new session.

For more info, see login via QR code.
auth.importLoginTokenLogin using a redirected login token, generated in case of DC mismatch during QR code login.

For more info, see login via QR code.
-

Miscellaneous

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
help.saveAppLogSaves logs of application on the server.
initConnectionInitialize connection
invokeAfterMsgInvokes a query after successfull completion of one of the previous queries.
invokeAfterMsgsInvokes a query after a successfull completion of previous queries
invokeWithLayerInvoke the specified query using the specified API layer
invokeWithoutUpdatesInvoke a request without subscribing the used connection for updates (this is enabled by default for file queries).
-

Registration/Authorization

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
auth.bindTempAuthKeyBinds a temporary authorization key temp_auth_key_id to the permanent authorization key perm_auth_key_id. Each permanent key may only be bound to one temporary key at a time, binding a new temporary key overwrites the previous one.

For more information, see Perfect Forward Secrecy.
auth.cancelCodeCancel the login verification code
auth.checkPasswordTry logging to an account protected by a 2FA password.
account.resetPasswordInitiate a 2FA password reset: can only be used if the user is already logged-in, see here for more info »
auth.checkRecoveryPasswordCheck if the 2FA recovery code sent using auth.requestPasswordRecovery is valid, before passing it to auth.recoverPassword.
auth.dropTempAuthKeysDelete all temporary authorization keys except for the ones specified
auth.exportAuthorizationReturns data for copying authorization to another data-centre.
auth.importAuthorizationLogs in a user using a key transmitted from his native data-centre.
auth.importBotAuthorizationLogin as a bot
auth.logOutLogs out the user.
auth.recoverPasswordReset the 2FA password using the recovery code sent using auth.requestPasswordRecovery.
auth.requestPasswordRecoveryRequest recovery code of a 2FA password, only for accounts with a recovery email configured.
auth.resendCodeResend the login code via another medium, the phone code type is determined by the return value of the previous auth.sendCode/auth.resendCode: see login for more info.
auth.resetAuthorizationsTerminates all user's authorized sessions except for the current one.

After calling this method it is necessary to reregister the current device using the method account.registerDevice
auth.sendCodeSend the verification code for login
auth.signInSigns in a user with a validated phone number.
auth.signUpRegisters a validated phone number in the system.
-

Working with GDPR export

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
account.initTakeoutSessionInitialize account takeout session
account.finishTakeoutSessionFinish account takeout session
messages.getSplitRangesGet message ranges for saving the user's chat history
channels.getLeftChannelsGet a list of channels/supergroups we left
invokeWithMessagesRangeInvoke with the given message range
invokeWithTakeoutInvoke a method within a takeout session
-

Working with GIFs (actually MPEG4 GIFs)

- - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.getSavedGifsGet saved GIFs
messages.saveGifAdd GIF to saved gifs list
messages.searchGifsSearch for GIFs
-

Working with Public Service Announcement and MTProxy channels

- - - - - - - - - - - - - - - - - -
NameDescription
help.hidePromoDataHide MTProxy/Public Service Announcement information
help.getPromoDataGet MTProxy/Public Service Announcement information
-

Working with TSF (internal use only)

- - - - - - - - - - - - - - - - - -
NameDescription
help.editUserInfoInternal use
help.getUserInfoInternal use
-

Working with 2FA login

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
account.confirmPasswordEmailVerify an email to use as 2FA recovery method.
account.resendPasswordEmailResend the code to verify an email to use as 2FA recovery method.
account.cancelPasswordEmailCancel the code that was sent to verify an email to use as 2FA recovery method.
account.getPasswordObtain configuration for two-factor authorization with password
account.getPasswordSettingsGet private info associated to the password info (recovery email, telegram passport info & so on)
account.updatePasswordSettingsSet a new 2FA password
account.declinePasswordResetAbort a pending 2FA password reset, see here for more info »
-

Working with Seamless Telegram Login

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.requestUrlAuthGet more info about a Seamless Telegram Login authorization request, for more info click here »
messages.acceptUrlAuthUse this to accept a Seamless Telegram Login authorization request, for more info click here »
account.getWebAuthorizationsGet web login widget authorizations
account.resetWebAuthorizationLog out an active web telegram login session
account.resetWebAuthorizationsReset all active web telegram login sessions
-

Working with VoIP calls

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
phone.acceptCallAccept incoming call
phone.confirmCallComplete phone call E2E encryption key exchange »
phone.discardCallRefuse or end running call
phone.getCallConfigGet phone call configuration to be passed to libtgvoip's shared config
phone.receivedCallOptional: notify the server that the user is currently busy in a call: this will automatically refuse all incoming phone calls until the current phone call is ended.
phone.requestCallStart a telegram phone call
phone.saveCallDebugSend phone call debug data to server
phone.sendSignalingDataSend VoIP signaling data
phone.setCallRatingRate a call
messages.deletePhoneCallHistoryDelete the entire phone call history.
-

Working with channels/supergroups/geogroups

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
channels.createChannelCreate a supergroup/channel.
channels.getInactiveChannelsGet inactive channels and supergroups
channels.deleteChannelDelete a channel/supergroup
channels.deleteHistoryDelete the history of a supergroup
channels.deleteMessagesDelete messages in a channel/supergroup
channels.deleteUserHistoryDelete all messages sent by a certain user in a supergroup
channels.editAdminModify the admin rights of a user in a supergroup/channel.
channels.editBannedBan/unban/kick a user in a supergroup/channel.
channels.editCreatorTransfer channel ownership
channels.editLocationEdit location of geogroup
channels.editPhotoChange the photo of a channel/supergroup
channels.editTitleEdit the name of a channel/supergroup
channels.exportMessageLinkGet link and embed info of a message in a channel/supergroup
channels.getAdminLogGet the admin log of a channel/supergroup
channels.getAdminedPublicChannelsGet channels/supergroups/geogroups we're admin in. Usually called when the user exceeds the limit for owned public channels/supergroups/geogroups, and the user is given the choice to remove one of his channels/supergroups/geogroups.
channels.getChannelsGet info about channels/supergroups
channels.getFullChannelGet full info about a channel
channels.getGroupsForDiscussionGet all groups that can be used as discussion groups.

Returned legacy group chats must be first upgraded to supergroups before they can be set as a discussion group.
To set a returned supergroup as a discussion group, access to its old messages must be enabled using channels.togglePreHistoryHidden, first.
channels.getMessagesGet channel/supergroup messages
channels.getParticipantGet info about a channel/supergroup participant
channels.getParticipantsGet the participants of a supergroup/channel
channels.inviteToChannelInvite users to a channel/supergroup
channels.joinChannelJoin a channel/supergroup
channels.leaveChannelLeave a channel/supergroup
channels.readHistoryMark channel/supergroup history as read
channels.readMessageContentsMark channel/supergroup message contents as read
channels.setDiscussionGroupAssociate a group to a channel as discussion group for that channel
channels.setStickersAssociate a stickerset to the supergroup
channels.togglePreHistoryHiddenHide/unhide message history for new channel/supergroup users
channels.toggleSignaturesEnable/disable message signatures in channels
channels.toggleSlowModeToggle supergroup slow mode: if enabled, users will only be able to send one message every seconds seconds
-

Working with chats/supergroups/channels

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.getMessageReadParticipantsGet which users read a specific message: only available for groups and supergroups with less than chat_read_mark_size_threshold members, read receipts will be stored for chat_read_mark_expire_period seconds after the message was sent, see client configuration for more info ».
messages.addChatUserAdds a user to a chat and sends a service message on it.
messages.checkChatInviteCheck the validity of a chat invite link and get basic info about it
messages.createChatCreates a new chat.
messages.deleteChatUserDeletes a user from a chat and sends a service message on it.
messages.editChatAboutEdit the description of a group/supergroup/channel.
messages.editChatAdminMake a user admin in a legacy group.
messages.editChatDefaultBannedRightsEdit the default banned rights of a channel/supergroup/group.
messages.editChatPhotoChanges chat photo and sends a service message on it
messages.editChatTitleChanages chat name and sends a service message on it.
messages.exportChatInviteExport an invite link for a chat
messages.getAllChatsGet all chats, channels and supergroups
messages.getChatsReturns chat basic info on their IDs.
messages.getAdminsWithInvitesGet info about chat invites generated by admins.
messages.deleteExportedChatInviteDelete a chat invite
messages.getChatInviteImportersGet info about the users that joined the chat using a specific chat invite
messages.deleteRevokedExportedChatInvitesDelete all revoked chat invites
messages.deleteChatDelete a chat
messages.getCommonChatsGet chats in common with a user
messages.getFullChatReturns full chat info according to its ID.
messages.importChatInviteImport a chat invite and join a private chat/supergroup/channel
messages.getExportedChatInviteGet info about a chat invite
messages.editExportedChatInviteEdit an exported chat invite
messages.getExportedChatInvitesGet info about the chat invites of a specific chat
messages.migrateChatTurn a legacy group into a supergroup
channels.convertToGigagroupConvert a supergroup to a gigagroup, when requested by channel suggestions.
-

Working with deep links

- - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.startBotStart a conversation with a bot using a deep linking parameter
help.getDeepLinkInfoGet info about a t.me link
help.getRecentMeUrlsGet recently used t.me links
-

Working with files

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
help.getCdnConfigGet configuration for CDN file downloads.
upload.getCdnFileDownload a CDN file.
upload.getCdnFileHashesGet SHA256 hashes for verifying downloaded CDN files
upload.reuploadCdnFileRequest a reupload of a certain file to a CDN DC.
upload.getFileReturns content of a whole file or its part.
upload.getFileHashesGet SHA256 hashes for verifying downloaded files
upload.getWebFileReturns content of an HTTP file or a part, by proxying the request through telegram.
upload.saveBigFilePartSaves a part of a large file (over 10Mb in size) to be later passed to one of the methods.
upload.saveFilePartSaves a part of file for futher sending to one of the methods.
messages.uploadEncryptedFileUpload encrypted file and associate it to a secret chat
messages.uploadMediaUpload a file and associate it to a chat (without actually sending it to the chat)
messages.getDocumentByHashGet a document by its SHA256 hash, mainly used for gifs
-

Working with instant view pages

- - - - - - - - - - - - - - - - - -
NameDescription
messages.getWebPageGet instant view page
messages.getWebPagePreviewGet preview of webpage
-

Working with secret chats

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.setEncryptedTypingSend typing event by the current user to a secret chat.
messages.readEncryptedHistoryMarks message history within a secret chat as read.
messages.acceptEncryptionConfirms creation of a secret chat
messages.discardEncryptionCancels a request for creation and/or delete info on secret chat.
messages.requestEncryptionSends a request to start a secret chat to the user.
messages.sendEncryptedSends a text message to a secret chat.
messages.sendEncryptedFileSends a message with a file attachment to a secret chat
messages.sendEncryptedServiceSends a service message to a secret chat.
messages.getDhConfigReturns configuration parameters for Diffie-Hellman key generation. Can also return a random sequence of bytes of required length.
messages.receivedQueueConfirms receipt of messages in a secret chat by client, cancels push notifications.
-

Working with telegram passport

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
account.sendVerifyEmailCodeSend the verification email code for telegram passport.
account.verifyEmailVerify an email address for telegram passport.
account.sendVerifyPhoneCodeSend the verification phone code for telegram passport.
account.verifyPhoneVerify a phone number for telegram passport.
account.acceptAuthorizationSends a Telegram Passport authorization form, effectively sharing data with the service
account.getAuthorizationFormReturns a Telegram Passport authorization form for sharing data with a service
account.getAuthorizationsGet logged-in sessions
account.deleteSecureValueDelete stored Telegram Passport documents, for more info see the passport docs »
account.getAllSecureValuesGet all saved Telegram Passport documents, for more info see the passport docs »
account.getSecureValueGet saved Telegram Passport document, for more info see the passport docs »
account.saveSecureValueSecurely save Telegram Passport document, for more info see the passport docs »
help.getPassportConfigGet passport configuration
users.setSecureValueErrorsNotify the user that the sent passport data contains some errors The user will not be able to re-submit their Passport data to you until the errors are fixed (the contents of the field for which you returned the error must change).

Use this if the data submitted by the user doesn't satisfy the standards your service requires for any reason. For example, if a birthday date seems invalid, a submitted document is blurry, a scan shows evidence of tampering, etc. Supply some details in the error message to make sure the user knows how to correct the issues.
-

Working with updates

- - - - - - - - - - - - - - - - - - - - - -
NameDescription
updates.getChannelDifferenceReturns the difference between the current state of updates of a certain channel and transmitted.
updates.getDifferenceGet new updates.
updates.getStateReturns a current state of updates.
-

Working with bot inline queries and callback buttons

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.getInlineBotResultsQuery an inline bot
messages.setInlineBotResultsAnswer an inline query, for bots only
messages.sendInlineBotResultSend a result obtained using messages.getInlineBotResults.
messages.getBotCallbackAnswerPress an inline callback button and get a callback answer from the bot
messages.setBotCallbackAnswerSet the callback answer to a user button press (bots only)
messages.editInlineBotMessageEdit an inline bot message
-

Working with bots

- - - - - - - - - - - - - - - - - - - - - -
NameDescription
bots.resetBotCommandsClear bot commands for the specified bot scope and language code
bots.getBotCommandsObtain a list of bot commands for the specified bot scope and language code
bots.setBotCommandsSet bot command list
-

Working with bots (internal bot API use)

- - - - - - - - - - - - - - - - - - - - - -
NameDescription
bots.answerWebhookJSONQueryAnswers a custom query; for bots only
bots.sendCustomRequestSends a custom request; for bots only
help.setBotUpdatesStatusInforms the server about the number of pending bot updates if they haven't been processed for a long time; for bots only
-

Working with cloud themes

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
account.updateThemeUpdate theme
account.uploadThemeUpload theme
account.getThemesGet installed themes
account.createThemeCreate a theme
account.installThemeInstall a theme
account.saveThemeSave a theme
account.getThemeGet theme information
account.getChatThemesGet all available chat themes
messages.setChatThemeChange the chat theme of a certain chat
-

Working with contacts and top peers

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
account.getContactSignUpNotificationWhether the user will receive notifications when contacts sign up
account.setContactSignUpNotificationToggle contact sign up notifications
contacts.acceptContactIf the peer settings of a new user allow us to add him as contact, add that user as contact
contacts.addContactAdd an existing telegram user as contact.

Use contacts.importContacts to add contacts by phone number, without knowing their Telegram ID.
contacts.blockAdds the user to the blacklist.
contacts.deleteByPhonesDelete contacts by phone number
contacts.deleteContactsDeletes several contacts from the list.
contacts.getBlockedReturns the list of blocked users.
contacts.getContactIDsGet contact by telegram IDs
contacts.getContactsReturns the current user's contact list.
contacts.getLocatedGet contacts near you
contacts.getSavedGet all contacts
contacts.getStatusesReturns the list of contact statuses.
contacts.getTopPeersGet most used peers
contacts.importContactsImports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.

Use contacts.addContact to add Telegram contacts without actually using their phone number.
contacts.resetSavedDelete saved contacts
contacts.resetTopPeerRatingReset rating of top peer
contacts.searchReturns users found by username substring.
contacts.toggleTopPeersEnable/disable top peers
contacts.unblockDeletes the user from the blacklist.
-

Working with credit cards

- - - - - - - - - - - - - -
NameDescription
payments.getBankCardDataGet info about a credit card
-

Working with dialogs

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.getDialogsReturns the current user dialog list.
messages.getPeerDialogsGet dialog info of specified peers
messages.getPinnedDialogsGet pinned dialogs
messages.toggleDialogPinPin/unpin a dialog
messages.reorderPinnedDialogsReorder pinned dialogs
messages.getDialogUnreadMarksGet dialogs manually marked as unread
messages.markDialogUnreadManually mark dialog as unread
messages.getPeerSettingsGet peer settings
messages.hidePeerSettingsBarShould be called after the user hides the report spam/add as contact bar of a new chat, effectively prevents the user from executing the actions specified in the peer's settings.
messages.getOnlinesGet count of online users in a chat
messages.sendScreenshotNotificationNotify the other user in a private chat that a screenshot of the chat was taken
messages.setTypingSends a current user typing event (see SendMessageAction for all event types) to a conversation partner or group.
messages.setHistoryTTLSet maximum Time-To-Live of all messages in the specified chat
-

Working with drafts

- - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.clearAllDraftsClear all drafts.
messages.getAllDraftsSave get all message drafts.
messages.saveDraftSave a message draft associated to a chat.
-

Working with emoji keywords

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.getEmojiKeywordsGet localized emoji keywords
messages.getEmojiKeywordsDifferenceGet changed emoji keywords
messages.getEmojiKeywordsLanguagesGet info about an emoji keyword localization
messages.getEmojiURLReturns an HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation
-

Working with folders

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.updateDialogFiltersOrderReorder folders
messages.getDialogFiltersGet folders
messages.getSuggestedDialogFiltersGet suggested folders
messages.updateDialogFilterUpdate folder
folders.deleteFolderDelete a peer folder
folders.editPeerFoldersEdit peers in peer folder
-

Working with games

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.getGameHighScoresGet highscores of a game
messages.getInlineGameHighScoresGet highscores of a game sent using an inline bot
messages.setGameScoreUse this method to set the score of the specified user in a game sent as a normal message (bots only).
messages.setInlineGameScoreUse this method to set the score of the specified user in a game sent as an inline message (bots only).
-

Working with group calls & live streaming

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
phone.exportGroupCallInviteGet an invite link for a group call or livestream
phone.getGroupCallJoinAsGet a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.
phone.editGroupCallParticipantEdit information about a given group call participant

Note: flags.N?Bool parameters can have three possible values:

- If the TL flag is not set, the previous value will not be changed.
- If the TL flag is set and contains a boolTrue, the previous value will be overwritten to true.
- If the TL flag is set and contains a boolFalse, the previous value will be overwritten to false.
phone.toggleGroupCallRecordStart or stop recording a group call: the recorded audio and video streams will be automatically sent to Saved messages (the chat with ourselves).
phone.editGroupCallTitleEdit the title of a group call or livestream
phone.getGroupParticipantsGet group call participants
phone.checkGroupCallCheck whether the group call Server Forwarding Unit is currently receiving the streams with the specified WebRTC source IDs
phone.createGroupCallCreate a group call or livestream
phone.toggleGroupCallStartSubscriptionSubscribe or unsubscribe to a scheduled group call
phone.leaveGroupCallLeave a group call
phone.toggleGroupCallSettingsChange group call settings
phone.inviteToGroupCallInvite a set of users to a group call.
phone.getGroupCallGet info about a group call
phone.joinGroupCallJoin a group call
phone.leaveGroupCallPresentationStop screen sharing in a group call
phone.discardGroupCallTerminate a group call
phone.joinGroupCallPresentationStart screen sharing in a call
phone.startScheduledGroupCallStart a scheduled group call.
phone.saveDefaultGroupCallJoinAsSet the default peer that will be used to join a group call in a specific dialog.
-

Working with imported chats

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.uploadImportedMediaUpload a media file associated with an imported chat, click here for more info ».
messages.startHistoryImportComplete the history import process, importing all messages into the chat.
To be called only after initializing the import with messages.initHistoryImport and uploading all files using messages.uploadImportedMedia.
messages.checkHistoryImportPeerCheck whether chat history exported from another chat app can be imported into a specific Telegram chat, click here for more info ».

If the check succeeds, and no RPC errors are returned, a messages.CheckedHistoryImportPeer constructor will be returned, with a confirmation text to be shown to the user, before actually initializing the import.
messages.checkHistoryImportObtains information about a chat export file, generated by a foreign chat app, click here for more info about imported chats ».
messages.initHistoryImportImport chat history from a foreign chat app into a specific Telegram chat, click here for more info about imported chats ».
-

Working with localization packs

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
langpack.getDifferenceGet new strings in languagepack
langpack.getLangPackGet localization pack strings
langpack.getLanguageGet information about a language in a localization pack
langpack.getLanguagesGet information about all languages in a localization pack
langpack.getStringsGet strings from a language pack
-

Working with media autodownload settings

- - - - - - - - - - - - - - - - - -
NameDescription
account.getAutoDownloadSettingsGet media autodownload settings
account.saveAutoDownloadSettingsChange media autodownload settings
-

Working with message threads

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.getRepliesGet messages in a reply thread
contacts.blockFromRepliesStop getting notifications about thread replies of a certain user in @replies
messages.getDiscussionMessageGet discussion message from the associated discussion group of a channel to show it on top of the comment section, without actually joining the group
messages.readDiscussionMark a thread as read
-

Working with message reactions

- - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.getMessagesReactionsGet message reactions
messages.sendReactionSend reaction to message
messages.getMessageReactionsListGet full message reaction list
-

Working with messages

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.deleteHistoryDeletes communication history.
messages.deleteMessagesDeletes messages by their identifiers.
messages.editMessageEdit message
messages.forwardMessagesForwards messages by their IDs.
messages.getHistoryGets back the conversation history with one interlocutor / within a chat
messages.getMessageEditDataFind out if a media message's caption can be edited
messages.getMessagesReturns the list of messages by their IDs.
messages.getMessagesViewsGet and increase the view counter of a message sent or forwarded from a channel
messages.getRecentLocationsGet live location history of a certain user
messages.getSearchCountersGet the number of results that would be found by a messages.search call with the same parameters
messages.getUnreadMentionsGet unread messages where we were mentioned
messages.readHistoryMarks message history as read.
messages.readMentionsMark mentions as read
messages.readMessageContentsNotifies the sender about the recipient having listened a voice message or watched a video.
messages.receivedMessagesConfirms receipt of messages by a client, cancels PUSH-notification sending.
messages.searchGets back found messages
messages.searchGlobalSearch for messages and peers globally
messages.sendMediaSend a media
messages.sendMessageSends a message to a chat
messages.sendMultiMediaSend an album or grouped media
messages.updatePinnedMessagePin a message
messages.unpinAllMessagesUnpin all pinned messages
-

Working with notification settings

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
account.registerDeviceRegister device to receive PUSH notifications
account.unregisterDeviceDeletes a device by its token, stops sending PUSH-notifications to it.
account.updateDeviceLockedWhen client-side passcode lock feature is enabled, will not show message texts in incoming PUSH notifications.
account.getNotifyExceptionsReturns list of chats with non-default notification settings
account.getNotifySettingsGets current notification settings for a given user/group, from all users/all groups.
account.updateNotifySettingsEdits notification settings from a given user/group, from all users/all groups.
account.resetNotifySettingsResets all notification settings from users and groups.
-

Working with other users

- - - - - - - - - - - - - - - - - -
NameDescription
users.getFullUserReturns extended user info by ID.
users.getUsersReturns basic user info according to their identifiers.
-

Working with payments

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
payments.getSavedInfoGet saved payment information
payments.clearSavedInfoClear saved payment information
payments.getPaymentFormGet a payment form
payments.validateRequestedInfoSubmit requested order information for validation
messages.setBotShippingResultsIf you sent an invoice requesting a shipping address and the parameter is_flexible was specified, the bot will receive an updateBotShippingQuery update. Use this method to reply to shipping queries.
account.getTmpPasswordGet temporary payment password
payments.sendPaymentFormSend compiled payment form
messages.setBotPrecheckoutResultsOnce the user has confirmed their payment and shipping details, the bot receives an updateBotPrecheckoutQuery update.
Use this method to respond to such pre-checkout queries.
Note: Telegram must receive an answer within 10 seconds after the pre-checkout query was sent.
payments.getPaymentReceiptGet payment receipt
-

Working with polls

- - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.getPollResultsGet poll results
messages.getPollVotesGet poll results for non-anonymous polls
messages.sendVoteVote in a poll
-

Working with scheduled messages

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.sendScheduledMessagesSend scheduled messages right away
messages.getScheduledHistoryGet scheduled messages
messages.deleteScheduledMessagesDelete scheduled messages
messages.getScheduledMessagesGet scheduled messages
-

Working with sensitive content (NSFW)

- - - - - - - - - - - - - - - - - -
NameDescription
account.getContentSettingsGet sensitive content settings
account.setContentSettingsSet sensitive content settings (for viewing or hiding NSFW content)
-

Working with sponsored messages

- - - - - - - - - - - - - - - - - -
NameDescription
channels.getSponsoredMessagesGet a list of sponsored messages
channels.viewSponsoredMessageMark a specific sponsored message as read
-

Working with sponsored proxies

- - - - - - - - - - - - - -
NameDescription
help.getProxyDataGet promotion info of the currently-used MTProxy
-

Working with statistics

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
stats.loadAsyncGraphLoad channel statistics graph asynchronously
stats.getBroadcastStatsGet channel statistics
stats.getMessagePublicForwardsObtains a list of messages, indicating to which other public channels was a channel message forwarded.
Will return a list of messages with peer_id equal to the public channel to which this message was forwarded.
stats.getMegagroupStatsGet supergroup statistics
stats.getMessageStatsGet message statistics
-

Working with stickers

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
messages.getOldFeaturedStickersMethod for fetching previously featured stickers
messages.toggleStickerSetsApply changes to multiple stickersets
stickers.suggestShortNameSuggests a short name for a given stickerpack name
stickers.checkShortNameCheck whether the given short name is available
stickers.setStickerSetThumbSet stickerset thumbnail
stickers.addStickerToSetAdd a sticker to a stickerset, bots only. The sticker set must have been created by the bot.
stickers.changeStickerPositionChanges the absolute position of a sticker in the set to which it belongs; for bots only. The sticker set must have been created by the bot
stickers.createStickerSetCreate a stickerset, bots only.
stickers.removeStickerFromSetRemove a sticker from the set where it belongs, bots only. The sticker set must have been created by the bot.
messages.clearRecentStickersClear recent stickers
messages.faveStickerMark a sticker as favorite
messages.getAllStickersGet all installed stickers
messages.getArchivedStickersGet all archived stickers
messages.getAttachedStickersGet stickers attached to a photo or video
messages.getFavedStickersGet faved stickers
messages.getFeaturedStickersGet featured stickers
messages.getMaskStickersGet installed mask stickers
messages.getRecentStickersGet recent stickers
messages.getStickerSetGet info about a stickerset
messages.getStickersGet stickers by emoji
messages.saveRecentStickerAdd/remove sticker from recent stickers list
messages.installStickerSetInstall a stickerset
messages.readFeaturedStickersMark new featured stickers as read
messages.reorderStickerSetsReorder installed stickersets
messages.searchStickerSetsSearch for stickersets
messages.uninstallStickerSetUninstall a stickerset
-

Working with the user's account

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
account.changePhoneChange the phone number of the current account
account.confirmPhoneConfirm a phone number to cancel account deletion, for more info click here »
account.deleteAccountDelete the user's account from the telegram servers. Can be used, for example, to delete the account of a user that provided the login code, but forgot the 2FA password and no recovery method is configured.
account.getAccountTTLGet days to live of account
account.getPrivacyGet privacy settings of current account
account.resetAuthorizationLog out an active authorized session by its hash
account.sendChangePhoneCodeVerify a new phone number to associate to the current account
account.sendConfirmPhoneCodeSend confirmation code to cancel account deletion, for more info click here »
account.setAccountTTLSet account self-destruction period
account.setPrivacyChange privacy settings of current account
account.setGlobalPrivacySettingsSet global privacy settings
account.getGlobalPrivacySettingsGet global privacy settings
account.updateProfileUpdates user profile.
account.updateStatusUpdates online user status.
-

Working with user profile pictures

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
photos.deletePhotosDeletes profile photos.
photos.getUserPhotosReturns the list of user photos.
photos.updateProfilePhotoInstalls a previously uploaded photo as a profile photo.
photos.uploadProfilePhotoUpdates current user profile photo.
-

Working with usernames

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
channels.checkUsernameCheck if a username is free and can be assigned to a channel/supergroup
channels.updateUsernameChange the username of a supergroup/channel
account.updateUsernameChanges username for the current user.
account.checkUsernameValidates a username and checks availability.
contacts.resolveUsernameResolve a @username to get peer info
-

Working with wallpapers

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameDescription
account.getMultiWallPapersGet info about multiple wallpapers
account.getWallPaperGet info about a certain wallpaper
account.getWallPapersReturns a list of available wallpapers.
account.installWallPaperInstall wallpaper
account.resetWallPapersDelete installed wallpapers
account.saveWallPaperInstall/uninstall wallpaper
account.uploadWallPaperCreate and upload a new wallpaper
-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/mtproto.html b/data/core.telegram.org/mtproto.html deleted file mode 100644 index fc52d378d4..0000000000 --- a/data/core.telegram.org/mtproto.html +++ /dev/null @@ -1,260 +0,0 @@ - - - - - MTProto Mobile Protocol - - - - - - - - - - - - - -
- -
-
-
-
-

MTProto Mobile Protocol

- -
- -
-

Please feel free to check out our FAQ for the Technically Inclined. -Client developers are required to comply with the Security Guidelines.

-
-

Related articles

-

-
-

This page deals with the basic layer of MTProto encryption used for Cloud chats (server-client encryption). See also:

- -

General Description

-

The protocol is designed for access to a server API from applications running on mobile devices. It must be emphasized that a web browser is not such an application.

-

The protocol is subdivided into three virtually independent components:

-
    -
  • High-level component (API query language): defines the method whereby API queries and responses are converted to binary messages.
  • -
  • Cryptographic (authorization) layer: defines the method by which messages are encrypted prior to being transmitted through the transport protocol.
  • -
  • Transport component: defines the method for the client and the server to transmit messages over some other existing network protocol (such as HTTP, HTTPS, WS (plain websockets), WSS (websockets over HTTPS), TCP, UDP).
  • -
- -
-

As of version 4.6, major Telegram clients are using MTProto 2.0, described in this article. -MTProto v1.0 (described here for reference) is deprecated and is currently being phased out.

-
-

Brief Component Summary

-

High-Level Component (RPC Query Language/API)

-

From the standpoint of the high-level component, the client and the server exchange messages inside a session. The session is attached to the client device (the application, to be more exact) rather than a specific websocket/http/https/tcp connection. In addition, each session is attached to a user key ID by which authorization is actually accomplished.

-

Several connections to a server may be open; messages may be sent in either direction through any of the connections (a response to a query is not necessarily returned through the same connection that carried the original query, although most often, that is the case; however, in no case can a message be returned through a connection belonging to a different session). When the UDP protocol is used, a response might be returned by a different IP address than the one to which the query had been sent.

-

There are several types of messages:

-
    -
  • RPC calls (client to server): calls to API methods
  • -
  • RPC responses (server to client): results of RPC calls
  • -
  • Message received acknowledgment (or rather, notification of status of a set of messages)
  • -
  • Message status query
  • -
  • Multipart message or container (a container that holds several messages; needed to send several RPC calls at once over an HTTP connection, for example; also, a container may support gzip).
  • -
-

From the standpoint of lower level protocols, a message is a binary data stream aligned along a 4 or 16-byte boundary. The first several fields in the message are fixed and are used by the cryptographic/authorization system.

-

Each message, either individual or inside a container, consists of a message identifier (64 bits, see below), a message sequence number within a session (32 bits), the length (of the message body in bytes; 32 bits), and a body (any size which is a multiple of 4 bytes). In addition, when a container or a single message is sent, an internal header is added at the top (see below), then the entire message is encrypted, and an external header is placed at the top of the message (a 64-bit key identifier and a 128-bit message key).

-

A message body normally consists of a 32-bit message type followed by type-dependent parameters. In particular, each RPC function has a corresponding message type. For more detail, see Binary Data Serialization, Mobile Protocol: Service Messages.

-

All numbers are written as little endian. However, very large numbers (2048-bit) used in RSA and DH are written in the big endian format because that is how the OpenSSL library does it.

-

Authorization and Encryption

-

Prior to a message (or a multipart message) being transmitted over a network using a transport protocol, it is encrypted in a certain way, and an external header is added at the top of the message which is: a 64-bit key identifier (that uniquely identifies an authorization key for the server as well as the user) and a 128-bit message key. A user key together with the message key defines an actual 256-bit key which is what encrypts the message using AES-256 encryption. Note that the initial part of the message to be encrypted contains variable data (session, message ID, sequence number, server salt) that obviously influences the message key (and thus the AES key and iv). The message key is defined as the 128 middle bits of the SHA256 of the message body (including session, message ID, etc.), including the padding bytes, prepended by 32 bytes taken from the authorization key. Multipart messages are encrypted as a single message.

-
-

For a technical specification, see Mobile Protocol: Detailed Description

-
-

The first thing a client application must do is create an authorization key which is normally generated when it is first run and almost never changes.

-

The protocol’s principal drawback is that an intruder passively intercepting messages and then somehow appropriating the authorization key (for example, by stealing a device) will be able to decrypt all the intercepted messages post factum. This probably is not too much of a problem (by stealing a device, one could also gain access to all the information cached on the device without decrypting anything); however, the following steps could be taken to overcome this weakness:

-
    -
  • Session keys generated using the Diffie-Hellman protocol and used in conjunction with the authorization and the message keys to select AES parameters. To create these, the first thing a client must do after creating a new session is send a special RPC query to the server (“generate session key”) to which the server will respond, whereupon all subsequent messages within the session are encrypted using the session key as well.
  • -
  • Protecting the key stored on the client device with a (text) password; this password is never stored in memory and is entered by a user when starting the application or more frequently (depending on application settings).
  • -
  • Data stored (cached) on the user device can also be protected by encryption using an authorization key which, in turn, is to be password-protected. Then, a password will be required to gain access even to that data.
  • -
-

Time Synchronization

-

If client time diverges widely from server time, a server may start ignoring client messages, or vice versa, because of an invalid message identifier (which is closely related to creation time). Under these circumstances, the server will send the client a special message containing the correct time and a certain 128-bit salt (either explicitly provided by the client in a special RPC synchronization request or equal to the key of the latest message received from the client during the current session). This message could be the first one in a container that includes other messages (if the time discrepancy is significant but does not as yet result in the client’s messages being ignored).

-

Having received such a message or a container holding it, the client first performs a time synchronization (in effect, simply storing the difference between the server’s time and its own to be able to compute the “correct” time in the future) and then verifies that the message identifiers for correctness.

-

Where a correction has been neglected, the client will have to generate a new session to assure the monotonicity of message identifiers.

-

MTProto transport

-

Before being sent using the selected transport protocol, the payload has to be wrapped in a secondary protocol header, defined by the appropriate MTProto transport protocol.

- -

The server recognizes these different protocols (and distinguishes them from HTTP, too) by the header. -Additionally, the following transport features can be used:

- -

Example implementations for these protocols can be seen in tdlib and MadelineProto.

-

Transport

-

Enables the delivery of encrypted containers together with the external header (hereinafter, Payload) from client to server and back. -Multiple transport protocols are defined:

- -

(We shall examine only the first five types.)

-

Recap

-

To recap, using the ISO/OSI stack as comparison:

-
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/mtproto/TL-abstract-types.html b/data/core.telegram.org/mtproto/TL-abstract-types.html deleted file mode 100644 index 4612ecdf00..0000000000 --- a/data/core.telegram.org/mtproto/TL-abstract-types.html +++ /dev/null @@ -1,202 +0,0 @@ - - - - - Binary serialization and abstract TL types - - - - - - - - - - - - - -
- -
-
-
- -

Binary serialization and abstract TL types

- -

TL Language defines abstract data types in the spirit of a general theory of types (more accurately, Martin-Löf’s theories of dependent intuitionistic types) without specifying the values of these types should be represented in memory, when saved to disk, or transmitted over a network. In contrast, the article on binary serialization discusses the problem of effective serialization of values of abstract types. To this end, the concept of a concrete or serialized type has been defined as the sets of serializations of all possible values of the corresponding abstract type. In this case, the serializations take values in the set A of words in the alphabet A*, which consists of 2^32 characters -- 32-bit integers.

-

In order to use a TL schema (e.g. “program”) in the TL language to describe the serialization of values of abstract types, we should explain how the concrete type [T] (subset [T] of A^) is associated with the abstract type T (defined in TL), and how the values of the abstract type T correspond to the values of the concrete type [T] (i.e. the elements of [T]*).

-

Serialization is the process of constructing an element of [T] based on a value of the abstract type T. The reverse process is deserialization.

-

Values of the abstract type T may be represented in a different way. Typically, some sort of trees or graphs are used in memory or, if desired, a set of nodes may be used, each of which contains a certain tag (“node type”) and several pointers to other nodes and/or values of built-in primitive types such as int. However, for general discussions it is useful to write the values of abstract type T as a string, more specifically, an S-expression. Recall that an S-expression is either an atom (the value of a primitive type, for example, an integer or a string constant in quotation marks; or an identifier that corresponds to a built-in or defined function) or a space-delimited list of S-expressions ending in parentheses. In our case, we use S-expressions, the first element of which is a combinator identifier, while the remaining elements (the number of which depends on the combinator’s arity) are S-expressions representing elements of the chosen combinator’s fields (or parameters). Moreover, the type of the arguments’ S-expressions and the type of the S-expressions of the result (e.g. the associated expression) must match.

-

For example, for the schema

-
pair x:int y:int = Pair;
-pnil = PairList;
-pcons hd:Pair tl:PairList = PairList;
-

the following are examples of the abstract type PairList, written as S-expressions:

-
(pnil)
-(pcons (pair 2 3) (pcons (pair 9 4) (pnil)))
-

We usually write E : T (read "E of type T”) when we want to say that E is a value of type T. We assume there is a built-in type Type whose values are types. Thus, writing T : Type means that T is a type.

-

For example, we can write:

-
PairList : Type;
-(pcons (pair 2 3) (pcons (pair 9 4) (pnil))) : PairList;
-

Converting an abstract value to a serialized value, generally speaking, is straightforward (and, if desired, can be defined by induction):

-
    -
  • -

    It is the serialization of values n of the primitive type int (as a single-symbol word in the alphabet A)

    -
  • -
  • -

    The serialization of a string constant (a value of the primitive type string) is a sequence of the 32-bit numbers defined in Binary serialization.

    -
  • -
  • -

    The serialization of the S-expression (C E1 ... Er) : T, where C is a combinator with arity r with argument types T1, ..., Tr and result type T (e.g. C : T1->T2->...->Tr->T) is the concatenation of the combinator number C (a 32-bit number that unambiguously identifies the combinator, usually equal to the CRC-32 of the string of its TL description) and the serializations of the values E1 of type T1, E2 of type T2, ..., Er of type Tr.

    -
  • -
-

If we use [T] to denote the concrete type corresponding to the abstract T, and [E] to denote an element of [T] corresponding to the value E of type T, then the last rule may be written as:

-
    -
  • [T] is the combination, for each constructor of type C T1->T2->...->Tr->T (i.e. that returns a value of type T), of direct products {C} x [T1] x [T2] x ... x [Tr], where {C} is a single-element set consisting of the combinator number C. Because {C}<>{C'} when C<>C’, this defines a mutually single-valued mapping of the values of the abstract type T (written using S-expressions) to the set [T].
  • -
-

Values of the built-in clothed types Int and String and serialized as if they were defined using int x:int = Int; and string s:string = String;, i.e. the serialization of integer constant or a string is preceded by number of the int or string combinator (constructor). In S-expressions, this may be written as (int 5) or (string "Test").

-

However, what has been described above does not account for certain subtleties, such as the existence of naked types, or the difference between functions (active combinators whose application may be reduced, e.g. calculated) and constructors (passive combinators for which there are not and cannot be reduction rules). Furthermore, we have not explained how to handle polymorphic types and optional combinator parameters. We will attempt to explain this now.

-

Constants, surface values, and functional values

-

By dividing combinators into constructors and functions, we can introduce the following classes of expressions (values) of the abstract type T:

-
    -
  • -

    Constant expressions: for the types int and string, these are all integer/string constants; for T, these are all expressions like (C E1 ... Er) : T, where the combinator C : T1->T2->...->Tr->T is a constructor, and Ei : Ti is constant expressions of types Ti. In other words, a constant expression is an S-expression consisting of only constructors and constant of primitive types.

    -
  • -
  • -

    Surface expressions are expressions that outwardly contain a functional combinator whose arguments, however, are constant expressions of the appropriate types. In other words, the functional combinator is resolved only at the outer level. (This is not entirely true; see the full explanation below).

    -
  • -
  • -

    Functional expressions: These are expressions that may contain any combinators or constants at all levels.

    -
  • -
-

In practice, we most frequently need constant values (for storage and passing any data structures, in particular, responses to RPC queries) and surface expressions (for example, as RPC queries: then the functional combinator of the outer level is the name of the RPC function that we want to call, while its parameters are the arguments, which are constant values, for invoking the function). In some cases, arbitrary functional expressions are helpful (for example, it we want to remotely transmit the result of one RPC query to a different RPC query).

-

We will use c(T) to denote a subtype of the abstract type T, whose values are constant expressions of type T. Clearly, c(T) possesses approximately the same constructors as T itself (with the types of all arguments Ti replaced by c(Ti), but it does not have functional combinators.

-

Analogously, we will use f(T) to denote a subtype of T, whose values are surface expressions of type T. Clearly, the combinators of f(T) are essentially functional combinators of type T, but c() applies to the types of these combinators’ arguments: The combinator A : T1->...->Tr->T turns into A' : c(T1)->...->c(Tr)->f(T). (See the clarification of this rule below.)

-

Thus, we have defined two “functionals” c : Type -> Type and f : Type -> Type, such that forall T : Type, c(T) :- T and forall T : Type, f(T) :- T (writing T :- T' means that T is contained in T', or that T is a subtype of T').

-

We will assume that c and f are idempotent.

-

Naked types

-

From the perspective of abstract type theory, naked types (in contrast to built-in primitive types like int and string are unnecessary. However, they are extremely useful in practice.

-

Therefore, TL introduces the (partially defined) idempotent unary operator %, which turns a standard functional (e.g. an expression of type ...->Type or simply Type) into a different standard functional of the same type. If T is a type, then from an abstract theoretical point of view, %T is equivalent to c(T). In other words, the values of %T are the constant values of T. If T is a k-arity standard expression, then T : S1 -> ... -> Sk -> Type, where each Si=Type or #, then by definition %T is a k-arity standard expression with the same arity, which is defined by the equation (%T) a1 ... ak = % (T a1 ... ak).

-

When a constant value of type %T is serialized, it is first serialized as a value of type T (assuming that T is not already a naked type itself). Then the first character of the serialization is discarded (e.g. the name of the enclosing combinator). Therefore, %T is a only a valid type expression if there is not more than one constructor for %T. The expression %T, where T : S1 -> ... -> Sk -> Type, is valid, if for any choice of parameters a1 : S1, ... , ak : Sk, the type T a1 ... ak does not have more than one constructor. Using % in other instances is incorrect.

-

If for every value of the parameters a1 : S1, ..., ak : Sk, there is exactly one constructor C for T a1 ... ak, then TL allows writing C a1 ... ak instead of %T a1 ... ak or %(T a1 .. ak). In other words, in certain situations the identifier C is a synonym for %T. This is only allowed in the context of a type (when specifying the type of a combinator’s field or result).

-

Moreover, it is assumed that %Int = int and %String = string.

-

! modifier

-

In TL, the idempotent operator ! can modify any type, actually making surface values be allowed when its constant values are serialized. However, if T is a standard function like S1->..->Sr->Type, then !T is defined using the equation (!T) a1 ... ar = !(T a1 ... ar), for any a1:S1, ..., ar:Sr.

-

The ! operator is only allowed in a definition of the types of fields of functional combinators. It is usually used as a type prefix, for example:

-
set_timeout {X:Type} timeout:int f:!X = X;
-

In this case, the set_timeout “wrapper” is defined. It takes two explicit parameters: the integer timeout and a surface expression of type X. X : Type is itself an implicit parameter (it is not explicitly stated, rather it is inferred from the values of the other parameters and their types). A similar kind of wrapper may be helpful for modifying the action of RPC queries (which are surface expressions of various types). For example, suppose we have the function

-
factorial n:int = int;
-

then we can wrap the RPC query (factorial 100) as follows: (set_timeout 200 (factorial 100)). This expression is still a surface value of type int, which means it can be passed as an RPC query.

-

A consecutive pair of two computations is another example:

-
pair {X Y : Type} x:X y:Y = Pair X Y;  // constructor
-seq_pair {X Y : Type} x:!X y:!Y = Pair X Y; // functional wrapper for sequential computation
-par_pair {X Y : Type} x:!X y:!Y = Pair X Y; // functional wrapper for parallel computation
-

Now the RPC query (seq_pair (factorial 2) (factorial 3)) : Pair int int first calculates factorial 2, then factorial 3, and returns the pair (pair 2 6). In this case, the sequence of operations isn’t important, because they do not have side effects. It would have been just as well to use (par_pair (factorial 2) (factorial 3)). However, this is not always the case.

-

We can also define an analogy to a “comma” operation:

-
comma {X Y : Type} x:!X y:!Y = Y;
-

For example, this operation could first calculate x, then forget the result, calculate y, and return y.

-

Note that the semantics of the seq_pair, par_pair and comma wrappers are indeed defined where they are implemented (like the semantics of all other functional combinators), not by their TL declaration.

-

In principle, polymorphic wrappers like set_timeout can also be applied, for example, to “annotate” a RPC response’s constant values. For example, the server might return a response to a query together with the time it was calculated. However, a value of type !X must be constant, because that is what is expected as the enclosing expression’s value. In other words, set_timeout 239 E is a constant/surface value of type X if and only if E is such itself.

-

$ modifier

-

The idempotent modifier $ permits the use of arbitrary functional values of an appropriate type in contexts where only constants or surface values are usually allowed. It recursively transforms all combinators for all of the types involved, canceling the action of % and affixing $ to the parameter types and result of all combinators ($ is also added to the front of the transformed combinators). Moreover, built-in types are also transformed (in the final stage): $int = Int and $string = String.

-

This may be useful to create an RPC query that performs a “deep computation” of the expression passed to it:

-
compute {X:Type} expr:$X = X;
-

For example, now we can transmit the following as an RPC query:

-
(compute ($factorial ($factorial (int 3)))) : int
-

(Note that the three has become clothed; the combinator $factorial has type $int -> $int).

-

This is very powerful tool. It does not have to be implemented in very simple versions of TL. $ is not encountered in currently used TL schemas.

-

More on modifiers

-

In fact, at least in terms of its application to serialization, the TL language by default implies the c() modifier around all combinators’ parameter types and results, while ! and $ cancel it (more accurately, ! only cancels, and in some sense $ reverses the meaning). This is why there is no explicit c() modifier in TL and why it is assumed that all functions only accept constant values and return constant results, unless otherwise specified.

-

You may think that some functional combinators may have a type such as partial_factorial n:int = $int; and that the RPC query (partial_factorial 3) might then unexpectedly return ($product (int 3) ($product (int 2) ($product (int 1) (int 1)))) : $int ...

-

It is probably more correct to think about the ! modifier as follows. All types initially include only constant values (and only constructors). The ! modifier makes a new type (it’s twin) out of each type. This new type has no inherent constructors. Functional combinators differ from constructors in that ! is implicitly added in front of their result’s type. After this, the (local or remote) process of calculating the expression can be represented using the polymorphic function eval : !X -> X.

-

Optional combinator parameters and their values

-

See Optional combinator parameters and their values.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/mtproto/TL-combinators.html b/data/core.telegram.org/mtproto/TL-combinators.html deleted file mode 100644 index d064ead04c..0000000000 --- a/data/core.telegram.org/mtproto/TL-combinators.html +++ /dev/null @@ -1,251 +0,0 @@ - - - - - Formal description of TL combinators - - - - - - - - - - - - - -
- -
-
-
- -

Formal description of TL combinators

- -

Formal declaration of TL combinators

-

Main article: Formal description of TL. See also TL Language.

-

Combinators in TL are declared as follows:

-
-

combinator-decl ::= full-combinator-id { opt-args } { args } = result-type ;
-full-combinator-id ::= lc-ident-full | _
-combinator-id ::= lc-ident-ns | _
-opt-args ::= { var-ident { var-ident } : [excl-mark] type-expr }
-args ::= var-ident-opt : [ conditional-arg-def ] [ ! ] type-term
-args ::= [ var-ident-opt : ] [ multiplicity *] [ { args } ]
-args ::= ( var-ident-opt { var-ident-opt } : [!] type-term )
-args ::= [ ! ] type-term
-multiplicity ::= nat-term
-var-ident-opt ::= var-ident | _
-conditional-arg-def ::= var-ident [ . nat-const ] ?
-result-type ::= boxed-type-ident { subexpr }
-result-type ::= boxed-type-ident < subexpr { , subexpr } >

-
-

We shall clarify what all this means.

-
    -
  • -

    A combinator identifier is either an identifier starting with a lowercase Latin letter (lc-ident), or a namespace identifier (also lc-ident) followed by a period and another lc-ident. Therefore, cons and lists.get are valid combinator identifiers.

    -
  • -
  • -

    A combinator has a name, also known as a number (not to be confused with the designation) -- a 32-bit number that unambiguously determines it. It is either calculated automatically (see below) or it is explicitly assigned in the declaration. To do this, a hash mark (#) and exactly 8 hexadecimal digits -- the combinator’s name -- are added to the identifier of the combinator being defined.

    -
  • -
  • -

    A combinator’s declaration begins with its identifier, to which its name (separated by a hash mark) may have been added.

    -
  • -
  • -

    After the combinator identifier comes the main part of the declaration, which consists of declarations of fields (or variables), including an indication of their types.

    -
  • -
  • -

    First come declarations of optional fields (of which there may be several or none at all). Then there are the declarations of the required fields (there may not be any of these either).

    -
  • -
  • -

    Any identifier that begins with an uppercase or lowercase letter and which does not contain references to a namespace can be a field (variable) identifier. Using uc-ident for identifiers of variable types and lc-indent for other variables is good practice.

    -
  • -
  • -

    Next a combinator declaration contains the equals sign (=) and the result type (it may be composite or appearing for the first time). The result type may be polymorphic and/or dependent; any fields of the defined constructor’s fields of type Type or # may be returned (as subexpressions).

    -
  • -
  • -

    A combinator declaration is terminated with a semicolon.

    -
  • -
-

In what follows, a constructor’s fields, variables, and arguments mean the same thing.

-

Optional field declarations

-
    -
  • -

    These have the form { field_1 ... field_k : type-expr }, where field_i is a variable (field) identifier that is unique within the scope of the combinator declaration, and type-expr is a type shared by all of the fields.

    -
  • -
  • -

    If k>1, this entry is functionally equivalent to { field_1 : type-expr } ... { field_k : type-expr }.

    -
  • -
  • -

    All optional fields must be explicitly named (using _ instead of field_i is not allowed).

    -
  • -
  • -

    Moreover, at present the names of all optional fields must share the combinator’s result type (possibly more than once) and themselves be of type # (i,e., nat) or Type. Therefore, if the exact result type is known, it is possible to determine the values of all of the combinator’s implicit parameters (possibly obtaining a contradiction of the form 2=3 in doing so, which means that the combinator is not allowed in the context).

    -
  • -
-

Required field declarations

-
    -
  • -

    These may have the form ( field_1 ... field_k : type-expr ), similar to an optional field declaration, but with parentheses. This entry is equivalent to ( field_1 : type-expr ) ... ( field_k : type-expr ), where the fields are defined one at a time.

    -
  • -
  • -

    The underscore sign (_) can be used as names of one or more fields (field_i), indicating that the field is anonymous (the exact name is unimportant).

    -
  • -
  • -

    One field may be declared without outer parentheses, like this: field_id : type-expr. Here, however, if type-expr is a complex type, parentheses may be necessary around type-expr (this is reflected in BNF).

    -
  • -
  • -

    Furthermore, one anonymous field may be declared using a type-expr entry, functionally equivalent to _ : type-expr.

    -
  • -
  • -

    Required field declarations follow one after another, separated by spaces (by any number of whitespace symbols, to be more precise).

    -
  • -
  • -

    The declared field’s type (type-expr) may use the declared combinator’s previously defined variables (fields) as subexpressions (i.e. parameter values). For example:

    -

    nil {X:Type} = List X; -cons {X:Type} hd:X tl:(list X) = List X; -typed_list (X:Type) (l : list X) = TypedList;

    -
  • -
-

Repetitions

-
    -
  • -

    These may only exist among required parameters. They have the form [ field-id : ] [ multiplicity * ] [ args ], where args has the same format as the combinator’s declaration of (several) required fields, except that all of the enclosing combinator’s previously declared fields may be used in the argument types.

    -
  • -
  • -

    The name of a field of an enclosing combinator that receives a repetition as a value may be specified (field-id), or bypassed, which is equivalent to using the underscore sign as a field-id.

    -
  • -
  • -

    The multiplicity field is an expression of the type # (nat), which can be a real constant, the name of a preceding field of type #, or an expression in the form ( c + v ), where c is a real constant and v is the name of a field of type #. The sense of the multiplicity field is to provide the length of the (repetition) vector, each element of which consists of values of the types enumerated in args.

    -
  • -
  • -

    The multiplicity field may be bypassed. In this case, the last preceding parameter of type # from the enclosing combinator is used (it must be).

    -
  • -
  • -

    Functionally, the repetition field-id : multiplicity * [ args ] is equivalent to the declaration of the single field ( field-id : %Tuple %AuxType multiplicity ), where aux_type is an auxiliary type with a new name defined as aux_type *args* = AuxType. If any of the enclosing type’s fields are used within args, they are added to the auxiliary constructor aux_type and to its AuxType result type as the first (optional) parameters.

    -
  • -
  • -

    If args consists of one anonymous field of type some-type, then some-type can be used directly instead of %AuxType.

    -
  • -
  • -

    If during implementation the repetitions are rewritten as indicated above, it is logical to use instead of aux_type and AuxType, some identifiers that contain the name of the outer combinator being defined and the repetition’s index number inside its definition.

    -
  • -
-

Example:

-
matrix {m n : #} a : m* [ n* [ double ] ] = Matrix m n;
-

is functionally equivalent to

-
aux_type {n : #} (_ : %Tuple double n) = AuxType n;
-matrix {m : #} {n : #} (a : %Tuple %(AuxType n) m) = Matrix m n;
-

Moreover, the built-in types Tuple and Vector could be defined as:

-
tnil {X : Type} = Tuple X 0;
-tcons {X : Type} {n : #} hd:X tl:%(Tuple X n) = Tuple X (S n);
-vector {X : Type} (n : #) (v : %(Tuple X n)) = Vector X;
-

Actually, the following equivalent entry is considered the definition of Vector (i.e. it is specifically this entry that is used to compute the name of the vector constructor and its partial applications):

-
vector {t : Type} # [ t ] = Vector t;
-

If we expand it using Tuple, we obtain the previous definition exactly.

-

Conditional fields

-

The construction

-
-

args ::= var-ident-opt : [ conditional-arg-def ] [ ! ] type-term
-conditional-arg-def ::= var-ident [ . nat-const ] ?

-
-

permits assigning fields which are only present if the value of a preceding mandatory or optional field of type # is not null (or if its chosen bit is not zero if the special binary bit-selection operator . is applied). -Example:

-
-

user {fields:#} id:int first_name:(fields.0?string) last_name:(fields.1?string) friends:(fields.2?%(Vector int)) = User fields;
-get_users req_fields:# ids:%(Vector int) = Vector %(User req_fields)

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/mtproto/TL-dependent.html b/data/core.telegram.org/mtproto/TL-dependent.html deleted file mode 100644 index 987e34555b..0000000000 --- a/data/core.telegram.org/mtproto/TL-dependent.html +++ /dev/null @@ -1,236 +0,0 @@ - - - - - TL-dependent - - - - - - - - - - - - - -
- -
-
-
- -

TL-dependent

- -

Main article: TL Language.

-

In certain cases, types may depend not only on other types (polymorphism), but also on the parameters of another type (dependent types). The TL language provides very limited support for this functionality: dependence is only allowed on a natural parameter whose type is designated using # (alias nat, but this is private -- TL doesn’t currently support this synonym). Values of type # are serialized as 32-bit signed numbers from 0 to 2^31-1.

-

Example: integer tuples (vectors)

-

Suppose we want to use induction to define the types “one integer”, “two integers”, and “three integers”. We could try to define them as follows:

-
empty = Empty;
-single x:int = Single;
-pair x:int y:int = Pair;
-triple x:int y:int z:int = Triple;
-quadruple x:int y:int z:int t:int = Quadruple;
-...
-

or as:

-
empty = Empty;
-single x:int empty = Single;
-pair x:int y:single = Pair;
-triple x:int yz:pair = Triple;
-quadruple x:int yzt:triple = Quadruple;
-

or as:

-
tnil = Tuple0;
-tcons0 hd:int tl:Tuple0 = Tuple1;
-tcons1 hd:int tl:Tuple1 = Tuple2;
-tcons2 hd:int tl:Tuple2 = Tuple3;
-...
-tcons_n hd:int tl:Tuple_n = Tuple_(n+1)
-

The first two variations lead to the same serialization. For example, (2 3 9):%triple and (2 (3 9)):%triple serialize as three 32-bit numbers: 2 3 9. The last variation better emphasizes the inductive version of the definition, but it uses boxed types. This is good from a theoretical perspective, but it leads to “superfluous” constructor names in serialization.

-

Therefore, we will write %Type-Ident to indicate the bare type that corresponds to the boxed type Type-Ident with a single constructor. If this constructor is named constructor, then according to the definition %Type-Ident = %constructor. Now we can write our definition like this:

-
tnil = Tuple0;
-tcons_n hd:int tl:%Tuple_n = Tuple_(n+1)
-

If we now abstract n out of the name of the type name and make it like a parameter for a polymorphic (dependent, to be more exact) type, then something like the following can be written in a suitable functional language:

-
NewType Tuple (n : #) :=
-| tnil = Tuple 0
-| tcons n:# hd:int tl:%(Tuple n) = Tuple (S n)
-EndType;
-

In the TL language, it looks like this:

-
tnil = Tuple 0;
-tcons {n:#} hd:int tl:%(Tuple n) = Tuple (S n);
-

The function S : # -> # and the constant O : # (it is 0) are the function for the next natural number (S n = n + 1) and the constant null. Therefore, the type # (alias nat) behaves as if it were defined in TL using the constructors

-
O = nat;
-S nat = nat;
-

or, using syntax more typical of other functional languages,

-
NewType nat :=
-| O
-| S nat
-EndType;
-

Types of all defined combinators:

-
O : #
-S : # -> #
-Tuple : # -> Type
-tnil : Tuple 0
-tcons : forall n : #, int -> Tuple n -> Tuple (S n)
-

or

-
Tuple : forall n : #, Type;
-tcons : forall n : #, forall hd : int, forall tl : Tuple n, Tuple (S n)
-

Note that in this case the constructor tnil does not depend on the parameter n, while tcons does.

-

In an analogous manner, it is possible to define a complete binary tree of height h with strings in the leaf nodes:

-
tleaf value:string = BinTree 0;
-tnode {h:#} left:(BinTree h) right:(BinTree h) = BinTree (S h);
-

Or a random tree whose leaf nodes are all a distance of h from the root and whose nodes are all labeled with integers:

-
hleaf value:int = Tree 0;
-hnode {n:#} left:(Tree n) next:(Tree (S n)) = Tree (S n)
-hnil {n:#} = Tree (S n)
-

Another version:

-
hleaf' value:int = Tree' 0;
-hnode' {n:#} children:(list (Tree' n)) = Tree' (S n)
-

Polymorphic dependent types

-

Let us try to define a type Tuple X n whose values are n-tuples of type X values. In this way, Tuple will be simultaneously polymorphic and dependent:

-
Tuple : Type -> # -> Type;
-

In the familiar syntax of functional languages:

-
NewType Tuple {X : Type} {n : #} :=
-| vnil : Tuple X 0
-| vcons {n:#} hd:X tl:%(Tuple X n) : Tuple X (S n)
-EndType
-

or, in TL syntax,

-
vnil {X:Type} = Tuple X 0;
-vcons {X:Type} {n:#} tl:(%Tuple X n) = Tuple X S n
-

In the end we obtain terms for the following types:

-
vnil : forall X : Type, Tuple X 0
-vcons : forall X : Type, forall n : #, X -> Tuple X n -> Tuple X (S n)
-

or

-
vnil : forall X : Type, Tuple X 0
-vcons : forall X : Type, forall n : #, forall hd : X, forall tl : Tuple X n, Tuple X (S n)
-

Dependent sums

-

The Tuple we just defined differs from the built-in Vector type. Specifically, the Vector type formally depends on a single argument (a type), but our Tuple depends on two (a type and a number):

-
Tuple : Type -> # -> Type;
-Vector : Type -> Type;
-

The built-in Vector could be defined in terms of our Tuple using “summing across all n : #":

-
vector {X:Type} n:# v:(%Tuple X n) = Vector X;
-

Nevertheless, our Tuple has its advantages. For example, we can define data types such as:

-
matrix_10x10 a:(%Tuple (%Tuple double 10) 10) = Matrix_10x10;
-

In any event, remember that during calculation of the matrix_10x10 combinator’s number, all parentheses must be removed and the CRC32 of the string matrix_10x10 a:%Tuple %Tuple double 10 10 = Matrix_10x10 must be computed.

-

Moreover, we can define arbitrarily-sized matrices:

-
matrix {X:Type} m:# n:# a:(%Tuple (%Tuple X m) n) = Matrix X;
-

In this case using vector would result in storing the length of a row (m) in each row, e.g. n times.

-

Note that the serializations of values of type %Tuple X n and vector X (also known as %vector X and %Vector X) nearly match when n > 0: in both cases we obtain a single 32-bit number (equal to n-1 or n depending on the version) followed by the serializations of n objects of type X. (This is slightly untrue: values of type %Tuple X n can only be serialized if n is a constant or value known from one of the preceding fields of the enclosing entry; but then this n won’t be serialized explicitly anywhere).

-

Special syntax for repetitions

-

In view of the importance of the construction presented above, it is built into the TL language in the following manner. A substructure in the form of [ array-field-name ":" ] [ nat-ident "" ] "[" field-descr ... "]” may be used in the declaration of any combinator, where nat-ident* is the name of any previously encountered field of type # (if it is not explicitly indicated, the most recent is used). In abstract, this substructure is equivalent to:

-
aux_type *field-descr* ... = AuxType;
-*current_constructor* ... [ *array-field-name* ":" ] (%Tuple aux_type *nat-ident*)
-

For example, 10x10 matrices, vectors, and arbitrary matrices may be defined in the following way:

-
matrix {X:Type} m:# n:# a:n*[ m*[ X ] ] = Matrix X;
-matrix_10x10 a:10*[ 10*[ double ]] = Matrix_10x10;
-vector {X:Type} # [ X ] = Vector X;
-

We have already encountered the last version as a “definition” of the “built-in type” Vector.

-

Of course, several fields, as complex as desired, may be within the repeating part. Furthermore, besides using n as a repeat counter, one may use expressions of the form (n+const) and (const+n), where const is a small nonnegative constant, which are shorthand for S (S ( ... (S n) ... )):

-
repeat_np1 n:# a:(S n)*[ key:string value:string ] = Dictionary;
-

To calculate the CRC32 these expressions are converted to expressions of the form (const+X) without internal spaces. Additionally, the * in this case is not set off by spaces on the left and right.

-

Serialization of dependent types

-

Serialization of dependent types and polymorphic types is not a fundamental challenge: we have combinators with non-zero arity with Type values. For example, the type Tuple double 10 : Type serializes to 'Tuple' '%double' 10. Note that at present in practice there is virtually no need to serialize types, whether dependent or not.

-

Optional combinator parameters in TL

-

Optional combinator parameters in TL must possess the following properties:

-
    -
  • -

    Optional parameters must be precisely ythe combinator’s first several arguments;

    -
  • -
  • -

    The value of any optional parameter must be entirely determined by the combinator’s result type.

    -
  • -
-

For example, in cons {X:Type} hd:X tl:(list X) = list X the parameter X may be made optional, because it is located at the very beginning of the argument list and is unambiguously determined by the list X result type. Similarly, in tcons {X:Type} {n:#} hd:X tl:(%Tuple X n) = Tuple X (S n) the values of X and n are completely determined based on the Tuple X (S n) result type, therefore they made be made optional parameters.

-

It usually makes sense to move all of a constructor’s arguments satisfying the second condition to the beginning of the list, arrange them in the order they appear in the result type’s parameters, and make them optional. Given such an approach, the full version of a constructor is rarely needed -- only when we want to transmit the value of the polymorphic or dependent type as a value of type Object. In all other cases, the type of the expected value from the context is already known, which means that all optional parameters can be recovered during decomposition.

-

See also Optional combinator parameters and their values.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/mtproto/TL-formal.html b/data/core.telegram.org/mtproto/TL-formal.html deleted file mode 100644 index 0bd0d20bfd..0000000000 --- a/data/core.telegram.org/mtproto/TL-formal.html +++ /dev/null @@ -1,319 +0,0 @@ - - - - - TL-formal - - - - - - - - - - - - - -
- -
-
-
- -

TL-formal

- -

See also TL Language. -For the syntax of declaring combinators, see in article Formal declaration of TL combinators. -For the syntax of patterns, see in article Formal declaration of TL patterns.

-

Tokens

-

Comments are the same as in C/C++. They are removed by a lexical parser (for example, being replaced by a single space). Whitespace separates tokens. Except for string constants, tokens cannot contain spaces.

-

Character classes:

-
-

lc-letter ::= a | b | ... | z
-uc-letter ::= A | B | ... | Z
-digit ::= 0 | 1 | ... | 9
-hex-digit ::= digit | a | b | c | d | e | f
-underscore ::= _
-letter ::= lc-letter | uc-letter
-ident-char ::= letter | digit | underscore

-
-

Simple identifiers and keywords:

-
-

lc-ident ::= lc-letter { ident-char }
-uc-ident ::= uc-letter { ident-char }
-namespace-ident ::= lc-ident
-lc-ident-ns ::= [ namespace-ident . ] lc-ident
-uc-ident-ns ::= [ namespace-ident . ] uc-ident
-lc-ident-full ::= lc-ident-ns [ # hex-digit *8 ]

-
-

Tokens:

-
-

underscore ::= _
-colon ::= :
-semicolon ::= ;
-open-par ::= (
-close-par ::= )
-open-bracket ::= [
-close-bracket ::= ]
-open-brace ::= {
-close-brace ::= }
-triple-minus ::= ---
-nat-const ::= digit { digit }
-lc-ident-full
-lc-ident
-uc-ident-ns
-equals ::= =
-hash ::= #
-question-mark ::= ?
-percent ::= %
-plus ::= +
-langle ::= <
-rangle ::= >
-comma ::= ,
-dot ::= .
-asterisk ::= *
-excl-mark ::= !
-Final-kw ::= Final
-New-kw ::= New
-Empty-kw ::= Empty

-
-

Final is a reserved keyword, e.g. a special token. Words like Type are not keywords, rather they are identifiers with preset values.

-

Tokens consisting of one or more constant symbols shall be hereafter denoted using terms in quotation marks (for example, --- replaces triple-minus).

-

Syntax

-

General syntax of a TL program

-

Syntactically, a TL program consists of a stream of tokens (separated by spaces, which are ignored at this stage). General program structure:

-
-

TL-program ::= constr-declarations { --- functions --- fun-declarations | --- types --- constr-declarations }

-
-

Here the constructor- and function declarations are nearly identical in their syntax (they are both combinators):

-
-

constr-declarations ::= { declaration }
-fun-declarations ::= { declaration }

-
-

There are various declarations:

-
-

declaration ::= combinator-decl | partial-app-decl | final-decl

-
-

Before explaining how declarations of combinators, partial applications, and type finalization are given, we will introduce additional syntactical categories:

-

Syntactical categories and constructions

-

The concept of an expression (expr) is important. There are type expressions (type-expr) and numeric expressions (nat-expr). However, they are defined the same way. Their correctness as type- or numeric expressions is checked when the type of the analyzed expression is checked.

-
-

type-expr ::= expr
-nat-expr ::= expr
-expr ::= { subexpr }
-subexpr ::= term | nat-const + subexpr | subexpr + nat-const
-term ::= ( expr ) | type-ident | var-ident | nat-const | % term | type-ident < expr { , expr } >
-type-ident ::= boxed-type-ident | lc-ident-ns | #
-boxed-type-ident ::= uc-ident-ns
-var-ident ::= lc-ident | uc-ident
-type-term ::= term
-nat-term ::= term

-
-

Note that writing E = E_1 E_2 ... E_n in the expression for expr means applying the function E_1 to the argument E_2, applying the result to E_3, etc. Specifically, E_1 E_2 E_3 = (E_1 E_2) E_3. A solitary # is included in type-ident, because it is actually the identifier for a built-in type (# alias nat).

-

The expression E<E_1,...,E_n> is syntactic sugar for (E (E_1) ... (E_n)), i.e. both expressions are transformed into the same internal representation.

-

Combinator declarations

-
-

combinator-decl ::= full-combinator-id { opt-args } { args } = result-type ;
-full-combinator-id ::= lc-ident-full | _
-combinator-id ::= lc-ident-ns | _
-opt-args ::= { var-ident { var-ident } : [excl-mark] type-expr }
-args ::= var-ident-opt : [ conditional-def ] [ ! ] type-term
-args ::= [ var-ident-opt : ] [ multiplicity *] [ { args } ]
-args ::= ( var-ident-opt { var-ident-opt } : [!] type-term )
-args ::= [ ! ] type-term
-multiplicity ::= nat-term
-var-ident-opt ::= var-ident | _
-conditional-def ::= var-ident [ . nat-const ] ?
-result-type ::= boxed-type-ident { subexpr }
-result-type ::= boxed-type-ident < subexpr { , subexpr } >

-
-

See Formal declaration of TL combinators for a description of what exactly this means. Here we will only note that when declaring the type of a combinator’s next argument, only the names of previously arranged (more to the left) arguments of the same combinator may be used as variables, but when declaring the result type you can use all of its parameters (of type Type and #).

-

Note that the names of combinators declared in this way may be used in TL itself only as the corresponding bare types. The only combinators that appear in declarations are built-in: O : # and S : # -> #.

-

There are also “pseudo-declarations” that are allowed only to declare built-in types (such as int ? = Int;):

-
-

builtin-combinator-decl ::= full-combinator-id ? = boxed-type-ident ;

-
-

Partial applications (patterns)

-
-

partial-app-decl ::= partial-type-app-decl | partial-comb-app-decl
-partial-type-app-decl ::= boxed-type-ident subexpr { subexpr } ; | boxed-type-ident < expr { , expr } > ;
-partial-comb-app-decl ::= combinator-id subexpr { subexpr } ;

-
-

See Formal declaration of TL patterns.

-

Type finalization

-
-

final-decl ::= New boxed-type-ident ; | Final boxed-type-ident ; | Empty boxed-type-ident ;

-
-

This type of declaration means that there must not be any constructor for the indicated type: before the declaration for New and after the declaration for Final. The keyword Empty enables both effects.

-

Predefined identifiers

-

Nearly all predefined identifiers may be given using the following schema (usually located in common.tl):

-
-

/////
-//
-// Common Types
-//
-/////

-

// Built-in types
-int ? = Int;
-long ? = Long;
-double ? = Double;
-string ? = String;

-

// Boolean emulation
-boolFalse = Bool;
-boolTrue = Bool;

-

// Boolean for diagonal queries
-boolStat statTrue:int statFalse:int statUnknown:int = BoolStat;

-

// Vector
-vector {t:Type} # [t] = Vector t;
-tuple {t:Type} {n:#} [t] = Tuple t n;
-vectorTotal {t:Type} total_count:int vector:%(Vector t) = VectorTotal t;

-

/////
-//
-// Result- (Maybe-) types
-//
-/////

-

resultFalse {t:Type} = Maybe t;
-resultTrue {t:Type} result:t = Maybe t;

-

pair {X:Type} {Y:Type} a:X b:Y = Pair X Y;
-map {X:Type} {Y:Type} key:X value:Y = Map X Y;

-

Empty False;
-true = True;

-

unit = Unit;

-
-
    -
  • -

    Predefined identifier Type: This type signifies the type of all types. It is usually used to specify the types of optional parameters in the constructors of polymorphic types. If strongly desired, it can be used in its own right, but this is very rarely needed in practice.

    -
  • -
  • -

    Identifier #: This type is used to specify a special type of nonnegative integers in the range from 0 to 2^31-1; its main purpose is the same as that of Type. There are two built-in constructors: O : # and S : # -> # (“null” and “next number”, respectively), which work as if # was defined using the schema

    -
  • -
-
-

O = #;
-S # = #;

-
-
    -
  • -

    Identifier Tuple: Type -> # -> Type denotes a set of the specified number of values of the indicated type. In other words, Tuple X n means “a set of n values of type X".

    -
  • -
  • -

    The typeBool, with two constructors boolTrue and boolFalse, is used to transmit Boolean values.

    -
  • -
  • -

    The constructor-less type False may be used instead of undeclared or invalid types in the construction of a TL schema, because any attempt to (de)serialize a value of type False will produce an error. Usage Example:

    -
  • -
-
-

user {flags:#} id:flags.0?string first_name:flags.1?string last_name:flags.2?string reserved3:flags.3?False reserved4:flags.4?False = User flags;
-user_present {flags:#} info:%(User flags) = UserInfo flags;
-user_absent {flags:#} = UserInfo flags;
-getUser flags:# id:int = !UserInfo flags;

-
-

In the future, bits 3 and 4 in the flags field may be used to transmit new fields after changing the names and types of the reserved3 and reserved4 fields. This will change the user constructor’s number, but this isn’t too important, since the User flags type is only used as a bare type. Transmitting bits 3 or 4 in the flags field in a getUser query before these fields have actually been defined will lead to an error in the (de)serialization of the request.

-
    -
  • The type True with a single null constructor true plays a role similar to the void type in C/C++. It is especially useful as a bare type %True, alias true, because its serialization has zero length. For example, the first_name:flags.1?string constructor used above is in fact shorthand for (the as-yet unsupported) alternative-type general constructor first_name:(flags.1?string:true).
  • -
-

When directly used in a conditional field it may simply indicate the presence (absence) of a certain parameter with void type. -If the conditional field exists, the associated parameter will not be populated; the conditional field simply exists and the existance value can be used to perform certain operations, example:

-
user {flags:#} id:flags.0?string first_name:flags.1?string last_name:flags.2?string bot:flags.3?true reserved4:flags.4?False = User flags;
-

If bit 3 of the flags parameter isn't set, the user is a normal user. -If bit 3 of the flags parameter is set, this indicates that the specified user is a bot: however, during deserialization, the bot parameter must not be assigned any value, since true is actually a void type.

-
    -
  • The typeUnit with a single null constructor Unit is similar to the previous type.
  • -
-

ANTLR definition

-

An ANLTR definition of TL grammar can be found here ».

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/mtproto/TL-optargs.html b/data/core.telegram.org/mtproto/TL-optargs.html deleted file mode 100644 index 5c71a8e2bf..0000000000 --- a/data/core.telegram.org/mtproto/TL-optargs.html +++ /dev/null @@ -1,151 +0,0 @@ - - - - - Optional combinator parameters and their values - - - - - - - - - - - - - -
- -
-
-
- -

Optional combinator parameters and their values

- -

TL Language makes it possible to declare a combinator’s first few parameters optional. Subsequently, they are almost never required to be explicitly stated. This is directly related to another important property of TL: polymorphism.

-

All optional parameters are typically required to be part of the result type (at least once).

-

A (sub)expression may be serialized/deserialized in one of two ways:

-
    -
  • -

    The result type is known (for example, we’re parsing the response to a previously sent RPC query and therefore know the value of some type is expected). In this case, the result type may be used to determine the values of the combinator’s implicit parameters.

    -
  • -
  • -

    The result type is not known. It is determined as a result of (de)serialization (for example, we are serializing an RPC query). In this case, it is necessary to explicitly specify (and serialize) all of the combinator’s optional parameters by using the full version of the combinator.

    -
  • -
-

We will assume that the functional combinator only differs from the constructor in that before its result type the ! modifier is implicitly added, and the (remote or local) computation of a functional expression may be presented as the execution of some polymorphic function eval : !X -> X.

-

Moreover, the unknown result type is obviously usually (but not always) bound to the serialization of an expression whose type has been modified by !.

-

We can formulate the following rules. Let there be some constructor

-
C {a1:T1} ... {am:Tm} b1:U1 ... bn:Un = T;
-

Some of its arguments or its result may be marked with the ! modifier (We consider a functional combinator to be a constructor whose result type has been modified by an implicit !).

-

The following conditions must hold:

-
    -
  • -

    Each type T1, ..., Tm, U1, ..., Un, and T may depend on parameters of type Type or #, which have been declared to the left of the use of the given type.

    -
  • -
  • -

    The types of implicit parameters T1, ..., Tm may not be modified by !.

    -
  • -
  • -

    Only implicit parameters of type Type or # are allowed. In other words, Ti is either a Type or a #. (Unlike the previous rule, this rule may be relaxed in the future.)

    -
  • -
  • -

    Each implicit parameter a1, ..., am must be used at least once -- either within one of the Ui types that have a !, or in the result type T, if it does not have an explicit or implicit !.

    -
  • -
  • -

    If an implicit parameter ai is not used in the result type, or if the result type has a !, then its first (leftmost) usage must be within a type Uj that is modified by !.

    -
  • -
-

The idea is this: we assume that during (de)serialization of a value of a type modified by ! that we do not know this type in advance and we will find out what it is only based on the result of the (de)serialization; Conversely, we assume that during (de)serialization of a value of a type that is not modified by ! that we know this type in advance. In this case, complying with the rules stated above lets us always compute the values of all implicit parameters -- either from the (previously known) result type or from the type of one of the bj:!Uj parameters (which was obtained during the serialization process).

-

In fact, ! denotes the direction in which type information is flowing. By default, the result type is the source of information about types (and their parameters), while argument types are the recipients of that information. The use of ! reverses the direction of information flow, making the result type the recipient and the argument type the source of type information.

-

See also Binary serialization and abstract TL types and Polymorphism in TL.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/mtproto/TL-patterns.html b/data/core.telegram.org/mtproto/TL-patterns.html deleted file mode 100644 index bf3f26f51a..0000000000 --- a/data/core.telegram.org/mtproto/TL-patterns.html +++ /dev/null @@ -1,129 +0,0 @@ - - - - - TL-patterns - - - - - - - - - - - - - -
- -
-
-
- -

TL-patterns

- -
-

partial-app-decl ::= partial-type-app-decl | partial-comb-app-decl
-partial-type-app-decl ::= boxed-type-ident subexpr { subexpr } ; | boxed-type-ident < expr { , expr } > ;
-partial-comb-app-decl ::= combinator-id subexpr { subexpr } ;

-
-

According to the original design, templates must be used to replace concrete values in the first few or all of the optional arguments of a constructor or polymorphic type. For example, if Tuple int 10 is used frequently, you can declare a template for it, which will cause the appropriate constructors to be generated automatically. When using such a constructor there may be nowhere to pass an int type or the tuple size 10. Similarly, it was originally planned to declared templates for Vector int, Vector string, etc. in order to generate constructors for each vector type being used type. These constructors would make it possible during deserialization to determine what kind of array is being transmitted.

-

Templates are not used now. Instead, the same universal constructors (for example, vector {t:Type} [t] = Vector t) are used with the values of the optional parameters being inferred from the type of the result (if we already know from the schema that in this location there must be a Vector int during deserialization, we understand that we will see the universal vector constructor in which t is equal to int).

-

This approach is better in that it is not necessary to define Vector SomeType templates in advance for all possible types in order to generate their own constructors for each of these cases. Nevertheless, there is a drawback. If someone wants to transmit the serialization of a value of the clothed type Vector int as a serialization of a value of type Object, a problem arises during serialization: after seeing the universal vector constructor and then reading the vector length, we cannot determine what type of values should be expected next.

-

In theory, this problem can be solved by using the full form of the constructor (@vector) corresponding to vector (it is automatically defined and is different in that all of the optional parameters become required), or by defining

-
-

object X:Type X = TypedObject

-
-

and passing the object type explicitly. Type serialization is required in both cases.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/mtproto/TL-polymorph.html b/data/core.telegram.org/mtproto/TL-polymorph.html deleted file mode 100644 index c2a4b9cde8..0000000000 --- a/data/core.telegram.org/mtproto/TL-polymorph.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - Polymorphism in TL - - - - - - - - - - - - - -
- -
-
-
- -

Polymorphism in TL

- -

It should be noted that in the TL schema of the overwhelming majority of API calls the use of polymorphic types is restricted to the Vector type. Nevertheless, having a view of the big picture is still helpful.

-

Ordinary inductive types

-

For example, let us consider the IntList, which is defined as follows:

-
int_cons hd:int tl:IntList = IntList;
-int_nil = IntList;
-

The “int_cons” and “int_nil” constructors as well as the “IntList” type itself are expressions of the following types (writing A : X means that A is an expression of type X):

-
IntList : Type;
-int_cons : int -> IntList -> IntList;
-int_nil : IntList;
-

The keyword Type is used to denote the type of all types. Note that Type is not Object (Object is the type of all terms). -Here is alternative syntax that could be used in some other functional programming language (but not in TL):

-
NewType IntList :=
-| int_cons hd:int tl:IntList
-| int_nil
-EndType
-

Polymorphic type

-

TL supports the following version (curly brackets indicate optional fields, see below):

-
cons {X:Type} hd:X tl:(List X) = List X;
-nil {X:Type} = List X
-

Here is an alternative formulation in other functional languages with dependent types:

-
NewType List {X:Type} :=
-| cons {X:Type} hd:X tl:(List X)
-| nil {X:Type}
-EndType
-

In any event, these variations are equivalent to one another from the point of view of the formal theory of types and lead to the definition of the following terms:

-
List : Type -> Type;
-cons : forall (X:Type), X -> List X -> List X;
-nil : forall (X:Type), X -> List X;
-

In each case, remember that writing “A -> B” is shorthand for “forall (x : A), B” for any variable x not entering into A and B. For example, the “cons” type could be written as follows:

-
cons : forall (X:Type), forall (hd : X), forall (tl : List X), List X
-

or more compactly:

-
cons : forall (X : Type) (hd : X) (tl : List X), List X
-

See Calculus of constructions. Examples of functional languages with dependent types, which support similar constructions are Coq and Agda.

-

In this case, the entry after a universal quantifier proves to be more content-related than that after an arrow, because the name of a variable bound by the quantifier is used to transmit the name of the corresponding field in the constructor, even if this variable is not used anywhere as it pertains to the expression under the quantifier. Structurally, all of these entries of the “cons” type are equivalent.

-

Serialization of types (values of type Type)

-

As we can see, to serialize a value of type List X, which has been obtained by applying the combinator “cons X:Type hd:X tl:(List X) = List X”, we need to:

-
    -
  1. serialize the name of the “cons” combinator into a 32-bit number;
  2. -
  3. serialize X (as a type, i.e. as a value of type Type) if X is a required parameter;
  4. -
  5. serialize the head of the list (hd) as a value of type X;
  6. -
  7. serialize the tail of the list as a value of the polymorphic type List X.
  8. -
-

In the first step, the natural question is which string exactly will be used to calculate the CRC32. It is proposed to take "cons X:Type hd:X tl:List X = List X” without the terminating semicolon and without any parentheses (closed type expressions are unambiguously reconstructed based on their construction’s prefix).

-

In the last step, we recursively resolve the very same problem of serializing a value of type List X; we will consider it resolved based on the assumption of induction in the construction of the value being serialized. We will similarly consider the third step understandable (induction in the construction of the value being serialized).

-

We still need to describe how to transmit (serialize) types, e.g. values of type Type. Types in TL schemas currently appear only as constructors’ optional parameters and are therefore never serialized explicitly. Rather, their values are inferred from the previously known type of the value being serialized.

-

For completeness we will describe how it would be possible to serialize types (values of type Type). However, keep in mind that for now this information is not useful. See Type serialization.

-

Optional arguments in polymorphic constructors

-

It was stated above that any subset of (the first few) parameters of any constructor can be identified as optional (by enclosing their declarations in curly brackets), but this is not actually entirely accurate. First, these optional parameters can only be of type Type or # (natural numbers). Second, optional parameters must share the return value’s type, otherwise their value cannot be determined.

-

Note that @'''constr-id''' means the constructor’s “full form” (in which all optional parameters become required), while '''constr-id'’ denotes its abbreviated form (without the optional arguments). If there are no optional arguments, then these two forms are the same. Constructors’ full forms are never used at present.

-

Bare polymorphic types

-

There is a small problem: if we want to serialize the value of the bare type ‘%pair string int’ or ‘%pair string Y’ (which in TL is usually denoted simply as “pair”, though the form “%Pair” is preferable), we cannot simultaneously use both the full constructor @pair and the partial pair, because the constructor’s name will not be serialized. Therefore, we must differentiate the bare types %@pair (type X, type Y, value x:X, and value y:Y are serialized) and %pair (only x:X and y:Y are serialized; types X and Y are known from the context). In practice, we nearly almost always need the bare type %pair, and this is precisely what “pair” means in the type’s context in TL. Therefore,

-
record name:string map:(List (pair int string)) = Record;
-

will be serialized approximately like we want it to be (the serialization of list elements will consist of the serialization of int and the serialization of string, without any additional headers, types, or combinator names). -Incidentally, when calculating the “record” combinator’s name 'record' in the example given above, the CRC32 of record name:string map:List pair int string = Record will be computed.

-

Also note that a more precise description of this type would be

-
record name:string map:(List %(Pair int string)) = Record
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/mtproto/TL-tl.html b/data/core.telegram.org/mtproto/TL-tl.html deleted file mode 100644 index 1af3157e11..0000000000 --- a/data/core.telegram.org/mtproto/TL-tl.html +++ /dev/null @@ -1,308 +0,0 @@ - - - - - TL schema for serialization of TL schemas - - - - - - - - - - - - - -
- -
-
-
- -

TL schema for serialization of TL schemas

- -

If necessary, a TL schema can be serialized in binary form. Here, this serialization format is defined by a TL schema (usually stored in the file tl.tl). This can be useful, for example, to make it possible to write a parser one time for converting a TL schema from text form (stored in the file something.tl) to binary form (stored in the file something.tlo). All other programs (for example, auto-generators of TL-(de)serializers for various programming languages) only need to know how to read .tlo files, which only requires generating an automatic deserializer according to the schema presented below.

-

First, a fragment of the file common.tl with certain required built-in types:

-
/////
-//
-// Common Types (source file common.tl, only necessary definitions included)
-//
-/////
-
-// Built-in types
-int ? = Int;
-long ? = Long;
-double ? = Double;
-string ? = String;
-
-// Boolean emulation
-boolFalse = Bool;
-boolTrue = Bool;
-
-// Vector
-vector {t:Type} # [t] = Vector t;
-tuple {t:Type} {n:#} [t] = Tuple t n;
-vectorTotal {t:Type} total_count:int vector:%(Vector t) = VectorTotal t;
-
-Empty False;
-true = True;
-

Next, properly, comes tl.tl itself. Note that the declaration for a fairly complex data type required only twenty lines in TL. This demonstrates the expressiveness and compactness of the TL language.

-
/////
-//
-// Serialized binary TL-schema in TL format, source file tl.tl
-//
-/////
-tls.schema_v2 version:int date:int types_num:# types:types_num*[tls.Type] 
-
-    constructor_num:# constructors:constructor_num*[tls.Combinator] 
-    functions_num:# functions:functions_num*[tls.Combinator] = tls.Schema;
-tls.type name:int id:string constructors_num:int flags:int arity:int params_type:long = tls.Type;
-
-tls.combinator name:int id:string type_name:int left:tls.CombinatorLeft right:tls.CombinatorRight = tls.Combinator;
-tls.combinatorLeftBuiltin = tls.CombinatorLeft;
-tls.combinatorLeft args_num:# args:args_num*[tls.Arg] = tls.CombinatorLeft;
-tls.combinatorRight value:tls.TypeExpr = tls.CombinatorRight;
-
-tls.arg id:string flags:# var_num:flags.1?int exist_var_num:flags.2?int exist_var_bit:flags.2?int type:tls.TypeExpr = tls.Arg;
-
-tls.exprType _:tls.TypeExpr = tls.Expr;
-
-tls.exprNat _:tls.NatExpr = tls.Expr;
-tls.natConst value:int = tls.NatExpr;
-
-tls.natVar dif:int var_num:int = tls.NatExpr;
-tls.typeVar var_num:int flags:int = tls.TypeExpr;
-
-tls.array multiplicity:tls.NatExpr args_num:# args:args_num*[tls.Arg] = tls.TypeExpr;
-tls.typeExpr name:int flags:int children_num:# children:children_num*[tls.Expr] = tls.TypeExpr;
-

Remarks

-

Schema serialization (version 2) always begins with the index number of the tls.schema_v2 constructor for tls.Schema. -Because the CRC32 of the string

-
tls.schema_v2 version:int date:int types_num:# types:types_num*[ tls.Type ] constructor_num:# constructors:constructor_num*[ tls.Combinator ] functions_num:# functions:functions_num*[ tls.Combinator ] = tls.Schema
-

is 0x3a2f9be2, this constant is in fact the magic number for tlo files in the current version’s format. -If the format is extended in the future (for example, if TL’s additional features are supported), then a tls.schema_v3 constructor with a different number will appear.

-

Example

-

If one adds declarations for the used built-in types (like int ? = Int;) from the file common.tl before tl.tl and serialize the resulting schema, the following binary data is obtained (tl.tlo):

-
-

0000: 3a2f9be2 00000000 51fec698 00000015 12eb4386 70659eff 00002301 00000000
-0020: 00000000 00000000 00000000 00000000 12eb4386 250be282 6f6f4204 0000006c
-0040: 00000002 02000010 00000000 00000000 00000000 12eb4386 2210c154 756f4406
-0060: 00656c62 00000001 02000000 00000000 00000000 00000000 12eb4386 00000000
-0080: 6c614605 00006573 00000000 00000401 00000000 00000000 00000000 12eb4386
-00a0: a8509bda 746e4903 00000001 02000001 00000000 00000000 00000000 12eb4386
-00c0: 22076cba 6e6f4c04 00000067 00000001 02000001 00000000 00000000 00000000
-00e0: 12eb4386 b5286e24 72745306 00676e69 00000001 02000001 00000000 00000000
-0100: 00000000 12eb4386 3fedd339 75725404 00000065 00000001 02000000 00000000
-0120: 00000000 00000000 12eb4386 9770768a 70755405 0000656c 00000001 02000000
-0140: 00000002 00000002 00000000 12eb4386 2cecf817 70795404 00000065 00000000
-0160: 00000000 00000000 00000000 00000000 12eb4386 1cb5c415 63655606 00726f74
-0180: 00000001 02000008 00000001 00000000 00000000 12eb4386 10133f47 6365560b
-01a0: 54726f74 6c61746f 00000001 02000000 00000001 00000000 00000000 12eb4386
-01c0: 29dfe61b 736c7407 6772412e 00000001 02000000 00000000 00000000 00000000
-01e0: 12eb4386 5c0a1ed5 736c740e 6d6f432e 616e6962 00726f74 00000001 02000000
-0200: 00000000 00000000 00000000 12eb4386 8133d9ba 736c7412 6d6f432e 616e6962
-0220: 4c726f74 00746665 00000002 02000010 00000000 00000000 00000000 12eb4386
-0240: 2c064372 736c7413 6d6f432e 616e6962 52726f74 74686769 00000001 02000000
-0260: 00000000 00000000 00000000 12eb4386 307d41a0 736c7408 7078452e 00000072
-0280: 00000002 02000010 00000000 00000000 00000000 12eb4386 c2635441 736c740b
-02a0: 74614e2e 72707845 00000002 02000010 00000000 00000000 00000000 12eb4386
-02c0: 3a2f9be2 736c740a 6863532e 00616d65 00000001 02000000 00000000 00000000
-02e0: 00000000 12eb4386 12eb4386 736c7408 7079542e 00000065 00000001 02000000
-0300: 00000000 00000000 00000000 12eb4386 193fd378 736c740c 7079542e 70784565
-0320: 00000072 00000003 02000010 00000000 00000000 00000000 00000018 5c0a1ed5
-0340: bc799737 6f6f6209 6c61466c 00006573 250be282 4c12c6d9 00000000 2c064372
-0360: c1863d08 250be282 00000000 00000000 5c0a1ed5 997275b5 6f6f6208 7572546c
-0380: 00000065 250be282 4c12c6d9 00000000 2c064372 c1863d08 250be282 00000000
-03a0: 00000000 5c0a1ed5 2210c154 756f6406 00656c62 2210c154 cd211f63 2c064372
-03c0: c1863d08 2210c154 00000000 00000000 5c0a1ed5 a8509bda 746e6903 a8509bda
-03e0: cd211f63 2c064372 c1863d08 a8509bda 00000000 00000000 5c0a1ed5 22076cba
-0400: 6e6f6c04 00000067 22076cba cd211f63 2c064372 c1863d08 22076cba 00000000
-0420: 00000000 5c0a1ed5 b5286e24 72747306 00676e69 b5286e24 cd211f63 2c064372
-0440: c1863d08 b5286e24 00000000 00000000 5c0a1ed5 3fedd339 75727404 00000065
-0460: 3fedd339 4c12c6d9 00000000 2c064372 c1863d08 3fedd339 00000000 00000000
-0480: 5c0a1ed5 9770768a 70757405 0000656c 9770768a 4c12c6d9 00000003 29dfe61b
-04a0: 00007401 00020005 00000000 c1863d08 2cecf817 00000000 00000000 29dfe61b
-04c0: 00006e01 00020005 00000001 c1863d08 70659eff 00000000 00000000 29dfe61b
-04e0: 00000000 00000000 d9fb20de 4e8a14f0 00000000 00000001 00000001 29dfe61b
-0500: 00000000 00000000 0142ceae 00000000 00000000 2c064372 c1863d08 9770768a
-0520: 00000000 00000002 ecc9da78 0142ceae 00000000 00000000 dcb49bd8 4e8a14f0
-0540: 00000000 00000001 5c0a1ed5 1cb5c415 63657606 00726f74 1cb5c415 4c12c6d9
-0560: 00000003 29dfe61b 00007401 00020005 00000000 c1863d08 2cecf817 00000000
-0580: 00000000 29dfe61b 00000000 00000004 00000001 c1863d08 70659eff 00000000
-05a0: 00000000 29dfe61b 00000000 00000000 d9fb20de 4e8a14f0 00000000 00000001
-05c0: 00000001 29dfe61b 00000000 00000000 0142ceae 00000000 00000000 2c064372
-05e0: c1863d08 1cb5c415 00000000 00000001 ecc9da78 0142ceae 00000000 00000000
-0600: 5c0a1ed5 10133f47 6365760b 54726f74 6c61746f 10133f47 4c12c6d9 00000003
-0620: 29dfe61b 00007401 00020005 00000000 c1863d08 2cecf817 00000000 00000000
-0640: 29dfe61b 746f740b 635f6c61 746e756f 00000000 c1863d08 a8509bda 00000001
-0660: 00000000 29dfe61b 63657606 00726f74 00000000 c1863d08 1cb5c415 00000001
-0680: 00000001 ecc9da78 0142ceae 00000000 00000000 2c064372 c1863d08 10133f47
-06a0: 00000000 00000001 ecc9da78 0142ceae 00000000 00000000 5c0a1ed5 29dfe61b
-06c0: 736c7407 6772612e 29dfe61b 4c12c6d9 00000006 29dfe61b 00646902 00000000
-06e0: c1863d08 b5286e24 00000001 00000000 29dfe61b 616c6605 00007367 00000004
-0700: 00000000 c1863d08 70659eff 00000000 00000000 29dfe61b 72617607 6d756e5f
-0720: 00000002 00000000 00000001 c1863d08 a8509bda 00000001 00000000 29dfe61b
-0740: 6978650d 765f7473 6e5f7261 00006d75 00000002 00000000 00000002 c1863d08
-0760: a8509bda 00000001 00000000 29dfe61b 6978650d 765f7473 625f7261 00007469
-0780: 00000002 00000000 00000002 c1863d08 a8509bda 00000001 00000000 29dfe61b
-07a0: 70797404 00000065 00000000 c1863d08 193fd378 00000000 00000000 2c064372
-07c0: c1863d08 29dfe61b 00000000 00000000 5c0a1ed5 5c0a1ed5 736c740e 6d6f632e
-07e0: 616e6962 00726f74 5c0a1ed5 4c12c6d9 00000005 29dfe61b 6d616e04 00000065
-0800: 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b 00646902 00000000
-0820: c1863d08 b5286e24 00000001 00000000 29dfe61b 70797409 616e5f65 0000656d
-0840: 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b 66656c04 00000074
-0860: 00000000 c1863d08 8133d9ba 00000000 00000000 29dfe61b 67697205 00007468
-0880: 00000000 c1863d08 2c064372 00000000 00000000 2c064372 c1863d08 5c0a1ed5
-08a0: 00000000 00000000 5c0a1ed5 cd211f63 736c7419 6d6f632e 616e6962 4c726f74
-08c0: 42746665 746c6975 00006e69 8133d9ba 4c12c6d9 00000000 2c064372 c1863d08
-08e0: 8133d9ba 00000000 00000000 5c0a1ed5 4c12c6d9 736c7412 6d6f632e 616e6962
-0900: 4c726f74 00746665 8133d9ba 4c12c6d9 00000002 29dfe61b 67726108 756e5f73
-0920: 0000006d 00000004 00000000 c1863d08 70659eff 00000000 00000000 29dfe61b
-0940: 67726104 00000073 00000000 d9fb20de 4e8a14f0 00000000 00000000 00000001
-0960: 29dfe61b 00000000 00000000 c1863d08 29dfe61b 00000000 00000000 2c064372
-0980: c1863d08 8133d9ba 00000000 00000000 5c0a1ed5 2c064372 736c7413 6d6f632e
-09a0: 616e6962 52726f74 74686769 2c064372 4c12c6d9 00000001 29dfe61b 6c617605
-09c0: 00006575 00000000 c1863d08 193fd378 00000000 00000000 2c064372 c1863d08
-09e0: 2c064372 00000000 00000000 5c0a1ed5 ecc9da78 736c740c 7078652e 70795472
-0a00: 00000065 307d41a0 4c12c6d9 00000001 29dfe61b 00000000 00000000 c1863d08
-0a20: 193fd378 00000000 00000000 2c064372 c1863d08 307d41a0 00000000 00000000
-0a40: 5c0a1ed5 dcb49bd8 736c740b 7078652e 74614e72 307d41a0 4c12c6d9 00000001
-0a60: 29dfe61b 00000000 00000000 c1863d08 c2635441 00000000 00000000 2c064372
-0a80: c1863d08 307d41a0 00000000 00000000 5c0a1ed5 8ce940b1 736c740c 74616e2e
-0aa0: 736e6f43 00000074 c2635441 4c12c6d9 00000001 29dfe61b 6c617605 00006575
-0ac0: 00000000 c1863d08 a8509bda 00000001 00000000 2c064372 c1863d08 c2635441
-0ae0: 00000000 00000000 5c0a1ed5 4e8a14f0 736c740a 74616e2e 00726156 c2635441
-0b00: 4c12c6d9 00000002 29dfe61b 66696403 00000000 c1863d08 a8509bda 00000001
-0b20: 00000000 29dfe61b 72617607 6d756e5f 00000000 c1863d08 a8509bda 00000001
-0b40: 00000000 2c064372 c1863d08 c2635441 00000000 00000000 5c0a1ed5 3a2f9be2
-0b60: 736c740d 6863732e 5f616d65 00003276 3a2f9be2 4c12c6d9 00000008 29dfe61b
-0b80: 72657607 6e6f6973 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b
-0ba0: 74616404 00000065 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b
-0bc0: 70797409 6e5f7365 00006d75 00000004 00000000 c1863d08 70659eff 00000000
-0be0: 00000000 29dfe61b 70797405 00007365 00000000 d9fb20de 4e8a14f0 00000000
-0c00: 00000000 00000001 29dfe61b 00000000 00000000 c1863d08 12eb4386 00000000
-0c20: 00000000 29dfe61b 6e6f630f 75727473 726f7463 6d756e5f 00000004 00000001
-0c40: c1863d08 70659eff 00000000 00000000 29dfe61b 6e6f630c 75727473 726f7463
-0c60: 00000073 00000000 d9fb20de 4e8a14f0 00000000 00000001 00000001 29dfe61b
-0c80: 00000000 00000000 c1863d08 5c0a1ed5 00000000 00000000 29dfe61b 6e75660d
-0ca0: 6f697463 6e5f736e 00006d75 00000004 00000002 c1863d08 70659eff 00000000
-0cc0: 00000000 29dfe61b 6e756609 6f697463 0000736e 00000000 d9fb20de 4e8a14f0
-0ce0: 00000000 00000002 00000001 29dfe61b 00000000 00000000 c1863d08 5c0a1ed5
-0d00: 00000000 00000000 2c064372 c1863d08 3a2f9be2 00000000 00000000 5c0a1ed5
-0d20: 12eb4386 736c7408 7079742e 00000065 12eb4386 4c12c6d9 00000006 29dfe61b
-0d40: 6d616e04 00000065 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b
-0d60: 00646902 00000000 c1863d08 b5286e24 00000001 00000000 29dfe61b 6e6f6310
-0d80: 75727473 726f7463 756e5f73 0000006d 00000000 c1863d08 a8509bda 00000001
-0da0: 00000000 29dfe61b 616c6605 00007367 00000000 c1863d08 a8509bda 00000001
-0dc0: 00000000 29dfe61b 69726105 00007974 00000000 c1863d08 a8509bda 00000001
-0de0: 00000000 29dfe61b 7261700b 5f736d61 65707974 00000000 c1863d08 22076cba
-0e00: 00000001 00000000 2c064372 c1863d08 12eb4386 00000000 00000000 5c0a1ed5
-0e20: 0142ceae 736c740b 7079742e 72615665 193fd378 4c12c6d9 00000002 29dfe61b
-0e40: 72617607 6d756e5f 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b
-0e60: 616c6605 00007367 00000000 c1863d08 a8509bda 00000001 00000000 2c064372
-0e80: c1863d08 193fd378 00000000 00000000 5c0a1ed5 d9fb20de 736c7409 7272612e
-0ea0: 00007961 193fd378 4c12c6d9 00000003 29dfe61b 6c756d0c 6c706974 74696369
-0ec0: 00000079 00000000 c1863d08 c2635441 00000000 00000000 29dfe61b 67726108
-0ee0: 756e5f73 0000006d 00000004 00000000 c1863d08 70659eff 00000000 00000000
-0f00: 29dfe61b 67726104 00000073 00000000 d9fb20de 4e8a14f0 00000000 00000000
-0f20: 00000001 29dfe61b 00000000 00000000 c1863d08 29dfe61b 00000000 00000000
-0f40: 2c064372 c1863d08 193fd378 00000000 00000000 5c0a1ed5 c1863d08 736c740c
-0f60: 7079742e 70784565 00000072 193fd378 4c12c6d9 00000004 29dfe61b 6d616e04
-0f80: 00000065 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b 616c6605
-0fa0: 00007367 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b 6968630c
-0fc0: 6572646c 756e5f6e 0000006d 00000004 00000000 c1863d08 70659eff 00000000
-0fe0: 00000000 29dfe61b 69686308 6572646c 0000006e 00000000 d9fb20de 4e8a14f0
-1000: 00000000 00000000 00000001 29dfe61b 00000000 00000000 c1863d08 307d41a0
-1020: 00000000 00000000 2c064372 c1863d08 193fd378 00000000 00000000 00000000

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/mtproto/TL-types.html b/data/core.telegram.org/mtproto/TL-types.html deleted file mode 100644 index 37ec9451ae..0000000000 --- a/data/core.telegram.org/mtproto/TL-types.html +++ /dev/null @@ -1,124 +0,0 @@ - - - - - Type serialization - - - - - - - - - - - - - -
- -
-
-
- -

Type serialization

- -

See Polymorphism in TL and TL Language.

-

It remains to describe how types, e.g. values of type Type, are transmitted (serialized). In general, there is nothing unexpected going on here: we have type constructors of various arities (for example, List is an arity-1 constructor, but IntList is a 0-arity constructor); and if we know that a 32-bit “name” is assigned to each type constructor, there are no further questions -- values of type Type are serialized exactly like values of any other recursive type with a defined set of constructors of differing arity.

-

How can a 32-bit “name” be assigned to a type (a type constructor, to be more exact) such as List or IntList? -It is proposed to use the sum of the names of all of its constructors, plus the CRC32 of the string with the designation of the type's name and all of its parameters such as “IntList = Type” or “List X:Type = Type”. This way, the List constructor’s “name” is the sum of the CRC32s of the three strings "List X:Type = Type", "cons X:Type hd:X tl:List X = List X", and "nil X:Type = List X". -For “bare” types (which, formally speaking, are subtypes of the corresponding “boxed” type), the situation is somewhat more complicated; the logical negation of the corresponding constructor’s name is used. For built-in bareand boxed types (for example, int and Int), a pseudo-declaration is used (for example, int ? = Int").

-
    -
  • This description is somewhat outdated and may be updated in the future. Specifically, how to treat the ! modifier has not been explained.*
  • -
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/mtproto/TL.html b/data/core.telegram.org/mtproto/TL.html deleted file mode 100644 index fdf733ae29..0000000000 --- a/data/core.telegram.org/mtproto/TL.html +++ /dev/null @@ -1,210 +0,0 @@ - - - - - TL Language - - - - - - - - - - - - - -
- -
-
-
- -

TL Language

- -

TL (Type Language) serves to describe the used system of types, constructors, and existing functions. In fact, the combinator description format presented in Binary Data Serialization is used.

-

See also:

- -

Advanced topics:

- -

Overview

-

A TL program usually consists of two sections separated by keyword ---functions---. The first section consists of declarations of built-in types and aggregate types (i.e. their constructors). The second section consists of the declared functions, i.e. functional combinators.

-

Actually, both the first and second sections consist of combinator declarations, each of which ends with a semicolon. However, the first section contains only constructors, while the second section only involves functions. Each combinator is declared using a “combinator declaration” in the format explained above. However, the combinator number and field names may be explicitly assigned.

-

If additional type declarations are required after functions have been declared, the keyword (section divider) ---types--- is used. Furthermore, a functional combinator may be declared in the type section if its result type begins with an exclamation point (in fact, when the function section is interpreted, this exclamation point is added automatically).

-

To explicitly define 32-bit names of combinators, a hash mark (#) is added immediately after the combinator’s name, followed by 8 hexadecimal digits.

-

Namespaces

-

Composite constructions like <namespace_identifier>.<constructor_identifier> and <namespace_identifier>.<Type_identifier> can be used as constructor- or type identifiers. The portion of the identifier to the left of the period is called the namespace. Moreover, the rule about a first uppercase letter in type identifiers and lowercase letter in constructor identifiers applies to the part of the construction after the period. For example, auth.Message would be a type, while auth.std_message would be a constructor.

-

Namespaces do not require a special declaration.

-

Comments

-

Comments are the same as in C++.

-

Example

-
// built-in types
-int#a8509bda ? = Int;
-long ? = Long;
-double ? = Double;
-string ? = String;
-null = Null;
-
-vector {t:Type} # [ t ] = Vector t;
-coupleInt {alpha:Type} int alpha = CoupleInt<alpha>;
-coupleStr {gamma:Type} string gamma = CoupleStr gamma;  
-/* The name of the type variable is irrelevant: "gamma" could be replaced with "alpha"; 
-   However, the combinator number will depend on the specific choice. */
-
-intHash {alpha:Type} vector<coupleInt<alpha>> = IntHash<alpha>;
-strHash {alpha:Type} (vector (coupleStr alpha)) = StrHash alpha;
-intSortedHash {alpha:Type} intHash<alpha> = IntSortedHash<alpha>;
-strSortedHash {alpha:Type} (strHash alpha) = StrSortedHash alpha;
-
-// custom types
-pair x:Object y:Object = Pair;
-triple x:Object y:Object z:Object = Triple;
-
-user#d23c81a3 id:int first_name:string last_name:string = User;
-no_user#c67599d1 id:int = User;
-group id:int title:string last_name:string = Group;
-no_group = Group;
-
----functions---
-
-// Maybe some built-in arithmetic functions; inverse quotes make "identifiers" out of arbitrary non-alphanumeric strings
-`+` Int Int = Int;
-`-` Int Int = Int;
-`+` Double Double = Double;
-// ...
-
-// API functions (aka RPC functions)
-getUser#b0f732d5 int = User;
-getUsers#2d84d5f5 (Vector int) = Vector User;
-

In this case, the user constructor has been explicitly assigned a number (0xd23c81a3); In fact, this was not necessary, since this value is the CRC32 of the string "user id:int first_name:string last_name:string = User", which would have been used by default.

-

Special constructors are not required for Vector int, Vector User, Vector Object, etc. -- the same universal constructor can be used everywhere:

-
vector#1cb5c415 {t:Type} # [ t ] = Vector t;
-

Note that when the getUsers (Vector int) = Vector User; constructor number is calculated, the CRC32 of the string "getUsers Vector int = Vector User” is computed (from which all parentheses have been removed).

-

Notation T0<T1,T2,...,Tn> is syntactic sugar for (T0 (T1) (T2) ... (Tn)). For example, Vector<User> and (Vector User) are entirely interchangeable.

-

Example of an RPC query

-

Suppose we want to call getUsers([2,3,4]). This query will be serialized into a sequence of 32-bit integers as follows:

-
0x2d84d5f5 0x1cb5c415 0x3 0x2 0x3 0x4
-

Please note that TL serialization yields sequences of 32-bit integers. When it has to be embedded into a byte stream, for example a network packet, each 32-bit integer is represented by four bytes in little-endian order. In this way the above query corresponds to the following byte stream:

-
F5 D5 84 2D 15 C4 B5 1C 03 00 00 00 02 00 00 00 03 00 00 00 04 00 00 00
-

The response might look something like this:

-
0x1cb5c415 0x3 0xd23c81a3 0x2 0x74655005 0x00007265 0x72615006 0x72656b 0xc67599d1 0x3 0xd23c81a3 0x4 0x686f4a04 0x6e 0x656f4403
-

This roughly corresponds to

-
[{"id":2,"first_name":"Peter", "last_name":"Parker"},{},{"id":4,"first_name":"John","last_name":"Doe"}]
-

Note that in both cases the same universal constructor vector#1cb5c415 is used: in the request to serialize the value of type Vector int, and in the serialization of the value of type Vector User in the response. There is no ambiguity because in both cases the type of the value being (de)serialized is known before its (de)serialization begins. For example, after receiving the query, the server sees that the first part is 0x2d84d5f5, which corresponds to the combinator getUsers#2d84d5f5 (Vector int) = Vector User. Thus, it is understood that what follows will be a value of type Vector int. After receiving the response to this query, the client knows that it must receive a value of type Vector User and it deserializes the response accordingly.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/mtproto/auth_key.html b/data/core.telegram.org/mtproto/auth_key.html deleted file mode 100644 index 4b54a1fdaa..0000000000 --- a/data/core.telegram.org/mtproto/auth_key.html +++ /dev/null @@ -1,262 +0,0 @@ - - - - - Creating an Authorization Key - - - - - - - - - - - - - -
- -
-
-
- -

Creating an Authorization Key

- -

The query format is described using Binary Data Serialization and the TL Language. All large numbers are transmitted as strings containing the required sequence of bytes in big endian order. Hash functions, such as SHA1, return strings (of 20 bytes) which can also be interpreted as big endian numbers. Small numbers (int, long, int128, int256) are normally little endian; however, if they are part of SHA1, the bytes are not rearranged. This way, if long x is the 64 lower-order bits of SHA1 of string s, then the final 8 bytes of 20-byte string SHA1(s) are taken and interpreted as a 64-bit integer.

-

Prior to sending off unencrypted messages (required in this instance to generate an authorization key), the client must undergo (p,q) authorization as follows.

-

DH exchange initiation

-
    -
  1. -

    Client sends query to server

    -

    req_pq_multi#be7e8ef1 nonce:int128 = ResPQ;

    -
  2. -
-

The value of nonce is selected randomly by the client (random number) and identifies the client within this communication. Following this step, it is known to all.

-
    -
  1. -

    Server sends response of the form

    -

    resPQ#05162463 nonce:int128 server_nonce:int128 pq:string server_public_key_fingerprints:Vector long = ResPQ;

    -
  2. -
-

Here, string pq is a representation of a natural number (in binary big endian format). This number is the product of two different odd prime numbers. Normally, pq is less than or equal to 2^63-1. The value of server_nonce is selected randomly by the server; following this step, it is known to all.

-

server_public_key_fingerprints is a list of public RSA key fingerprints (64 lower-order bits of SHA1 (server_public_key); the public key is represented as a bare type rsa_public_key n:string e:string = RSAPublicKey, where, as usual, n and е are numbers in big endian format serialized as strings of bytes, following which SHA1 is computed) received by the server.

-

All subsequent messages contain the pair (nonce, server_nonce) both in the plain-text, and the encrypted portions which makes it possible to identify a “temporary session” — one run of the key generation protocol described on this page that uses the same (nonce, server_nonce) pair. An intruder could not create a parallel session with the server with the same parameters and reuse parts of server- or client-encrypted messages for its own purposes in such a parallel session, because a different server_nonce would be selected by the server for any new “temporary session”.

-

Proof of work

-
    -
  1. Client decomposes pq into prime factors such that p < q.
  2. -
-

This starts a round of Diffie-Hellman key exchanges.

-

Presenting proof of work; Server authentication

-
    -
  1. -

    Client sends query to server

    -

    req_DH_params#d712e4be nonce:int128 server_nonce:int128 p:string q:string public_key_fingerprint:long encrypted_data:string = Server_DH_Params

    -
  2. -
-

Here, encrypted_data is obtained as follows:

-
    -
  • -

    new_nonce := another (good) random number generated by the client; after this query, it is known to both client and server;

    -
  • -
  • -

    data := a serialization of

    -
    p_q_inner_data_dc#a9f55f95 pq:string p:string q:string nonce:int128 server_nonce:int128 new_nonce:int256 dc:int = P_Q_inner_data;
    -

    or of

    -
    p_q_inner_data_temp_dc#56fddf88 pq:string p:string q:string nonce:int128 server_nonce:int128 new_nonce:int256 dc:int expires_in:int = P_Q_inner_data;
    -
  • -
  • -

    encrypted_data := RSA_PAD (data, server_public_key), where RSA_PAD is a version of RSA with a variant of OAEP+ padding explained below in 4.1).

    -
  • -
-

Someone might intercept the query and replace it with their own, independently decomposing pq into factors instead of the client. The only field that it makes sense to modify is new_nonce which would be the one an intruder would have to re-generate (because an intruder cannot decrypt the encrypted data sent by the client). Since all subsequent messages are encrypted using new_nonce or contain new_nonce_hash, they will not be processed by the client (an intruder would not be able to make it look as though they had been generated by the server because they would not contain new_nonce). Therefore, this intercept will only result in the intruder’s completing the authorization key generation protocol in place of the client and creating a new key (that has nothing to do with the client); however, the same effect could be achieved simply by creating a new key in one's own name.

-

An alternative form of inner data (p_q_inner_data_temp_dc) is used to create temporary keys, that are only stored in the server RAM and are discarded after at most expires_in seconds. The server is free to discard its copy earlier. In all other respects the temporary key generation protocol is the same. After a temporary key is created, the client usually binds it to its principal authorisation key by means of the auth.bindTempAuthKey method, and uses it for all client-server communication until it expires; then a new temporary key is generated. Thus Perfect Forward Secrecy (PFS) in client-server communication is achieved. Read more about PFS »

-

4.1) RSA_PAD(data, server_public_key) mentioned above is implemented as follows:

-
    -
  • data_with_padding := data + random_padding_bytes; -- where random_padding_bytes are chosen so that the resulting length of data_with_padding is precisely 192 bytes, and data is the TL-serialized data to be encrypted as before. One has to check that data is not longer than 144 bytes.
  • -
  • data_pad_reversed := BYTE_REVERSE(data_with_padding); -- is obtained from data_with_padding by reversing the byte order.
  • -
  • a random 32-byte temp_key is generated.
  • -
  • data_with_hash := data_pad_reversed + SHA256(temp_key + data_with_padding); -- after this assignment, data_with_hash is exactly 224 bytes long.
  • -
  • aes_encrypted := AES256_IGE(data_with_hash, temp_key, 0); -- AES256-IGE encryption with zero IV.
  • -
  • temp_key_xor := temp_key XOR SHA256(aes_encrypted); -- adjusted key, 32 bytes
  • -
  • key_aes_encrypted := temp_key_xor + aes_encrypted; -- exactly 256 bytes (2048 bits) long
  • -
  • The value of key_aes_encrypted is compared with the RSA-modulus of server_pubkey as a big-endian 2048-bit (256-byte) unsigned integer. If key_aes_encrypted turns out to be greater than or equal to the RSA modulus, the previous steps starting from the generation of new random temp_key are repeated. Otherwise the final step is performed:
  • -
  • encrypted_data := RSA(key_aes_encrypted, server_pubkey); -- 256-byte big-endian integer is elevated to the requisite power from the RSA public key modulo the RSA modulus, and the result is stored as a big-endian integer consisting of exactly 256 bytes (with leading zero bytes if required).
  • -
-
    -
  1. -

    Server responds with:

    -

    server_DH_params_ok#d0e8075c nonce:int128 server_nonce:int128 encrypted_answer:string = Server_DH_Params;

    -
  2. -
-
-

If the query is incorrect, the server returns a -404 error and the handshake must be restarted (any subsequent request also returns -404, even if it is correct).

-
-

Here, encrypted_answer is obtained as follows:

-
    -
  • -

    new_nonce_hash := 128 lower-order bits of SHA1 (new_nonce);

    -
  • -
  • -

    answer := serialization

    -
      server_DH_inner_data#b5890dba nonce:int128 server_nonce:int128 g:int dh_prime:string g_a:string server_time:int = Server_DH_inner_data;
    -
  • -
  • -

    answer_with_hash := SHA1(answer) + answer + (0-15 random bytes); such that the length be divisible by 16;

    -
  • -
  • -

    tmp_aes_key := SHA1(new_nonce + server_nonce) + substr (SHA1(server_nonce + new_nonce), 0, 12);

    -
  • -
  • -

    tmp_aes_iv := substr (SHA1(server_nonce + new_nonce), 12, 8) + SHA1(new_nonce + new_nonce) + substr (new_nonce, 0, 4);

    -
  • -
  • -

    encrypted_answer := AES256_ige_encrypt (answer_with_hash, tmp_aes_key, tmp_aes_iv); here, tmp_aes_key is a 256-bit key, and tmp_aes_iv is a 256-bit initialization vector. The same as in all the other instances that use AES encryption, the encrypted data is padded with random bytes to a length divisible by 16 immediately prior to encryption.

    -
  • -
-

Following this step, new_nonce is still known to client and server only. The client is certain that it is the server that responded and that the response was generated specifically in response to client query req_DH_params, since the response data are encrypted using new_nonce.

-

Client is expected to check whether p = dh_prime is a safe 2048-bit prime (meaning that both p and (p-1)/2 are prime, and that 2^2047 < p < 2^2048), and that g generates a cyclic subgroup of prime order (p-1)/2, i.e. is a quadratic residue mod p. Since g is always equal to 2, 3, 4, 5, 6 or 7, this is easily done using quadratic reciprocity law, yielding a simple condition on p mod 4g -- namely, p mod 8 = 7 for g = 2; p mod 3 = 2 for g = 3; no extra condition for g = 4; p mod 5 = 1 or 4 for g = 5; p mod 24 = 19 or 23 for g = 6; and p mod 7 = 3, 5 or 6 for g = 7. After g and p have been checked by the client, it makes sense to cache the result, so as not to repeat lengthy computations in future.

-

If the verification takes too long time (which is the case for older mobile devices), one might initially run only 15 Miller--Rabin iterations for verifying primeness of p and (p - 1)/2 with error probability not exceeding one billionth, and do more iterations later in the background.

-

Another optimization is to embed into the client application code a small table with some known "good" couples (g,p) (or just known safe primes p, since the condition on g is easily verified during execution), checked during code generation phase, so as to avoid doing such verification during runtime altogether. Server changes these values rarely, thus one usually has to put the current value of server's dh_prime into such a table. For example, current value of dh_prime equals (in big-endian byte order)

-
C7 1C AE B9 C6 B1 C9 04 8E 6C 52 2F 70 F1 3F 73 98 0D 40 23 8E 3E 21 C1 49 34 D0 37 56 3D 93 0F 48 19 8A 0A A7 C1 40 58 22 94 93 D2 25 30 F4 DB FA 33 6F 6E 0A C9 25 13 95 43 AE D4 4C CE 7C 37 20 FD 51 F6 94 58 70 5A C6 8C D4 FE 6B 6B 13 AB DC 97 46 51 29 69 32 84 54 F1 8F AF 8C 59 5F 64 24 77 FE 96 BB 2A 94 1D 5B CD 1D 4A C8 CC 49 88 07 08 FA 9B 37 8E 3C 4F 3A 90 60 BE E6 7C F9 A4 A4 A6 95 81 10 51 90 7E 16 27 53 B5 6B 0F 6B 41 0D BA 74 D8 A8 4B 2A 14 B3 14 4E 0E F1 28 47 54 FD 17 ED 95 0D 59 65 B4 B9 DD 46 58 2D B1 17 8D 16 9C 6B C4 65 B0 D6 FF 9C A3 92 8F EF 5B 9A E4 E4 18 FC 15 E8 3E BE A0 F8 7F A9 FF 5E ED 70 05 0D ED 28 49 F4 7B F9 59 D9 56 85 0C E9 29 85 1F 0D 81 15 F6 35 B1 05 EE 2E 4E 15 D0 4B 24 54 BF 6F 4F AD F0 34 B1 04 03 11 9C D8 E3 B9 2F CC 5B
-
    -
  1. -

    Client computes random 2048-bit number b (using a sufficient amount of entropy) and sends the server a message

    -

    set_client_DH_params#f5045f1f nonce:int128 server_nonce:int128 encrypted_data:string = Set_client_DH_params_answer;

    -
  2. -
-

Here, encrypted_data is obtained thus:

-
    -
  • -

    g_b := pow(g, b) mod dh_prime;

    -
  • -
  • -

    data := serialization

    -
      client_DH_inner_data#6643b654 nonce:int128 server_nonce:int128 retry_id:long g_b:string = Client_DH_Inner_Data
    -
  • -
  • -

    data_with_hash := SHA1(data) + data + (0-15 random bytes); such that length be divisible by 16;

    -
  • -
  • -

    encrypted_data := AES256_ige_encrypt (data_with_hash, tmp_aes_key, tmp_aes_iv);

    -
  • -
-

The retry_id field is equal to zero at the time of the first attempt; otherwise, it is equal to auth_key_aux_hash from the previous failed attempt (see Item 9).

-
    -
  1. -

    Thereafter, auth_key equals pow(g, {ab}) mod dh_prime; on the server, it is computed as pow(g_b, a) mod dh_prime, and on the client as (g_a)^b mod dh_prime.

    -
  2. -
  3. -

    auth_key_hash is computed := 64 lower-order bits of SHA1 (auth_key). The server checks whether there already is another key with the same auth_key_hash and responds in one of the following ways.

    -
  4. -
-

DH key exchange complete

-
    -
  1. -

    Server responds in one of three ways:

    -

    dh_gen_ok#3bcbf734 nonce:int128 server_nonce:int128 new_nonce_hash1:int128 = Set_client_DH_params_answer; -dh_gen_retry#46dc1fb9 nonce:int128 server_nonce:int128 new_nonce_hash2:int128 = Set_client_DH_params_answer; -dh_gen_fail#a69dae02 nonce:int128 server_nonce:int128 new_nonce_hash3:int128 = Set_client_DH_params_answer;

    -
  2. -
-
    -
  • new_nonce_hash1, new_nonce_hash2, and new_nonce_hash3 are obtained as the 128 lower-order bits of SHA1 of the byte string derived from the new_nonce string by adding a single byte with the value of 1, 2, or 3, and followed by another 8 bytes with auth_key_aux_hash. Different values are required to prevent an intruder from changing server response dh_gen_ok into dh_gen_retry.
  • -
  • auth_key_aux_hash is the 64 higher-order bits of SHA1(auth_key). It must not be confused with auth_key_hash.
  • -
-

In the other case, the client goes to Item 6) generating a new b. -In the first case, the client and the server have negotiated auth_key, following which they forget all other temporary data, and the client creates another encrypted session using auth_key. At the same time, server_salt is initially set to substr(new_nonce, 0, 8) XOR substr(server_nonce, 0, 8). If required, the client stores the difference between server_time received in 5) and its local time, to be able always to have a good approximation of server time which is required to generate correct message identifiers.

-

IMPORTANT: Apart from the conditions on the Diffie-Hellman prime dh_prime and generator g, both sides are to check that g, g_a and g_b are greater than 1 and less than dh_prime - 1. We recommend checking that g_a and g_b are between 2^{2048-64} and dh_prime - 2^{2048-64} as well.

-

Error Handling (Lost Queries and Responses)

-

If the client fails to receive any response to its query from the server within a certain time interval, it may simply re-send the query. If the server has already sent a response to this query (exactly the same request and not just similar: all the parameters during the repeat request must take on the same values) but it did not get to the client, the server will simply re-send the same response. The server remembers the response for up to 10 minutes after having received the query in 1). If the server has already forgotten the response or the requisite temporary data, the client will have to start from the beginning.

-

The server may consider that if the client has already sent in the next query using the data from the previous server response to the specific client, the response is known to have been received by the client and may be forgotten by the server.

-

Usage Example

-

An example of a complete list of queries required to generate an authorization key is shown on a separate page.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/mtproto/description.html b/data/core.telegram.org/mtproto/description.html deleted file mode 100644 index 7c5054cdcf..0000000000 --- a/data/core.telegram.org/mtproto/description.html +++ /dev/null @@ -1,238 +0,0 @@ - - - - - Mobile Protocol: Detailed Description - - - - - - - - - - - - - -
- -
-
-
- -

Mobile Protocol: Detailed Description

- -
- -
-

As of version 4.6, major Telegram clients are using MTProto 2.0. -MTProto v.1.0 is deprecated and is currently being phased out.

-
-

This article describes the basic layer of the MTProto protocol version 2.0 (Cloud chats, server-client encryption). The principal differences from version 1.0 (described here for reference) are as follows:

-
    -
  • SHA-256 is used instead of SHA-1;
  • -
  • Padding bytes are involved in the computation of msg_key;
  • -
  • msg_key depends not only on the message to be encrypted, but on a portion of auth_key as well;
  • -
  • 12..1024 padding bytes are used instead of 0..15 padding bytes in v.1.0.
  • -
-

See also: MTProto 2.0: Secret Chats, end-to-end encryption

-

Protocol description

-

Before a message (or a multipart message) is transmitted over a network using a transport protocol, it is encrypted in a certain way, and an external header is added at the top of the message that consists of a 64-bit key identifier auth_key_id (that uniquely identifies an authorization key for the server as well as the user) and a 128-bit message key msg_key.

-

The authorization key auth_key combined with the message key msg_key define an actual 256-bit key aes_key and a 256-bit initialization vector aes_iv, which are used to encrypt the message using AES-256 encryption in infinite garble extension (IGE) mode. Note that the initial part of the message to be encrypted contains variable data (session, message ID, sequence number, server salt) that obviously influences the message key (and thus the AES key and iv). In MTProto 2.0, the message key is defined as the 128 middle bits of the SHA-256 of the message body (including session, message ID, padding, etc.) prepended by 32 bytes taken from the authorization key. In the older MTProto 1.0, the message key was computed as the lower 128 bits of SHA-1 of the message body, excluding the padding bytes.

-

Multipart messages are encrypted as a single message.

- -
-

Got questions about this setup? — Check out the Advanced FAQ!

-
-
Note 1
-

Each plaintext message to be encrypted in MTProto always contains the following data to be checked upon decryption in order to make the system robust against known problems with the components:

-
    -
  • server salt (64-Bit)
  • -
  • session id
  • -
  • message sequence number
  • -
  • message length
  • -
  • time
  • -
-
Note 2
-

Telegram's End-to-end encrypted Secret Chats are using an additional layer of encryption on top of the described above. See Secret Chats, End-to-End encryption for details.

-

Terminology

-

Authorization Key (auth_key)

-

A 2048-bit key shared by the client device and the server, created upon user registration directly on the client device by exchanging Diffie-Hellman keys, and never transmitted over a network. Each authorization key is user-specific. There is nothing that prevents a user from having several keys (that correspond to “permanent sessions” on different devices), and some of these may be locked forever in the event the device is lost. See also Creating an Authorization Key.

-

Server Key

-

A 2048-bit RSA key used by the server digitally to sign its own messages while registration is underway and the authorization key is being generated. The application has a built-in public server key which can be used to verify a signature but cannot be used to sign messages. A private server key is stored on the server and changed very infrequently.

-

Key Identifier (auth_key_id)

-

The 64 lower-order bits of the SHA1 hash of the authorization key are used to indicate which particular key was used to encrypt a message. Keys must be uniquely defined by the 64 lower-order bits of their SHA1, and in the event of a collision, an authorization key is regenerated. A zero key identifier means that encryption is not used which is permissible for a limited set of message types used during registration to generate an authorization key in a Diffie-Hellman exchange. For MTProto 2.0, SHA1 is still used here, because auth_key_id should identify the authorization key used independently of the protocol version.

-

Session

-

A (random) 64-bit number generated by the client to distinguish between individual sessions (for example, between different instances of the application, created with the same authorization key). The session in conjunction with the key identifier corresponds to an application instance. The server can maintain session state. Under no circumstances can a message meant for one session be sent into a different session. The server may unilaterally forget any client sessions; clients should be able to handle this.

-

Server Salt

-

A (random) 64-bit number changed every 30 minutes (separately for each session) at the request of the server. All subsequent messages must contain the new salt (although, messages with the old salt are still accepted for a further 1800 seconds). Required to protect against replay attacks and certain tricks associated with adjusting the client clock to a moment in the distant future.

-

Message Identifier (msg_id)

-

A (time-dependent) 64-bit number used uniquely to identify a message within a session. Client message identifiers are divisible by 4, server message identifiers modulo 4 yield 1 if the message is a response to a client message, and 3 otherwise. Client message identifiers must increase monotonically (within a single session), the same as server message identifiers, and must approximately equal unixtime*2^32. This way, a message identifier points to the approximate moment in time the message was created. A message is rejected over 300 seconds after it is created or 30 seconds before it is created (this is needed to protect from replay attacks). In this situation, it must be re-sent with a different identifier (or placed in a container with a higher identifier). The identifier of a message container must be strictly greater than those of its nested messages.

-

Important: to counter replay-attacks the lower 32 bits of msg_id passed by the client must not be empty and must present a fractional part of the time point when the message was created.

-

Content-related Message

-

A message requiring an explicit acknowledgment. These include all the user and many service messages, virtually all with the exception of containers and acknowledgments.

-

Message Sequence Number (msg_seqno)

-

A 32-bit number equal to twice the number of “content-related” messages (those requiring acknowledgment, and in particular those that are not containers) created by the sender prior to this message and subsequently incremented by one if the current message is a content-related message. A container is always generated after its entire contents; therefore, its sequence number is greater than or equal to the sequence numbers of the messages contained in it.

-

Message Key (msg_key)

-

In MTProto 2.0, the middle 128 bits of the SHA-256 hash of the message to be encrypted (including the internal header and the padding bytes for MTProto 2.0), prepended by a 32-byte fragment of the authorization key.

-

In MTProto 1.0, message key was defined differently, as the lower 128 bits of the SHA-1 hash of the message to be encrypted, with padding bytes excluded from the computation of the hash. Authorization key was not involved in this computation.

-

Internal (cryptographic) Header

-

A header (16 bytes) added before a message or a container before it is all encrypted together. Consists of the server salt (64 bits) and the session (64 bits).

-

External (cryptographic) Header

-

A header (24 bytes) added before an encrypted message or a container. Consists of the key identifier auth_key_id (64 bits) and the message key msg_key (128 bits).

-

Payload

-

External header + encrypted message or container.

-

Defining AES Key and Initialization Vector

-

The 2048-bit authorization key (auth_key) and the 128-bit message key (msg_key) are used to compute a 256-bit AES key (aes_key) and a 256-bit initialization vector (aes_iv) which are subsequently used to encrypt the part of the message to be encrypted (i. e. everything with the exception of the external header that is added later) with AES-256 in infinite garble extension (IGE) mode.

-

For MTProto 2.0, the algorithm for computing aes_key and aes_iv from auth_key and msg_key is as follows.

-
    -
  • msg_key_large = SHA256 (substr (auth_key, 88+x, 32) + plaintext + random_padding);
  • -
  • msg_key = substr (msg_key_large, 8, 16);
  • -
  • sha256_a = SHA256 (msg_key + substr (auth_key, x, 36));
  • -
  • sha256_b = SHA256 (substr (auth_key, 40+x, 36) + msg_key);
  • -
  • aes_key = substr (sha256_a, 0, 8) + substr (sha256_b, 8, 16) + substr (sha256_a, 24, 8);
  • -
  • aes_iv = substr (sha256_b, 0, 8) + substr (sha256_a, 8, 16) + substr (sha256_b, 24, 8);
  • -
-

where x = 0 for messages from client to server and x = 8 for those from server to client.

-

For the obsolete MTProto 1.0, msg_key, aes_key, and aes_iv were computed differently (see this document for reference).

-

The lower-order 1024 bits of auth_key are not involved in the computation. They may (together with the remaining bits or separately) be used on the client device to encrypt the local copy of the data received from the server. The 512 lower-order bits of auth_key are not stored on the server; therefore, if the client device uses them to encrypt local data and the user loses the key or the password, data decryption of local data is impossible (even if data from the server could be obtained).

-

In MTProto 1.0, when AES was used to encrypt a block of data of a length not divisible by 16 bytes, the data was padded with 0 to 15 random padding bytes random_padding to a length divisible by 16 bytes prior to encryption. In MTProto 2.0, this padding is taken into account when computing msg_key. Note that MTProto 2.0 requires from 12 to 1024 bytes of padding, still subject to the condition that the resulting message length be divisible by 16 bytes.

-

Using MTProto 2.0 instead of MTProto 1.0

-

A client may either use only MTProto 2.0 or only MTProto 1.0 in the same TCP connection. The server detects the protocol used by the first message received from the client, and then uses the same encryption for its messages, and expects the client to use the same encryption henceforth. We recommend using MTProto 2.0; MTProto 1.0 is deprecated and supported for backward compatibility only.

-

Important Checks

-

When an encrypted message is received, it must be checked that msg_key is in fact equal to the 128 middle bits of the SHA-256 of the decrypted data with a 32-byte fragment of auth_key prepended to it, and that msg_id has even parity for messages from client to server, and odd parity for messages from server to client.

-

In addition, the identifiers (msg_id) of the last N messages received from the other side must be stored, and if a message comes in with msg_id lower than all or equal to any of the stored values, the message is to be ignored. Otherwise, the new message msg_id is added to the set, and, if the number of stored msg_id values is greater than N, the oldest (i. e. the lowest) is forgotten.

-

On top of this, msg_id values that belong over 30 seconds in the future or over 300 seconds in the past are to be ignored. This is especially important for the server. The client would also find this useful (to protect from a replay attack), but only if it is certain of its time (for example, if its time has been synchronized with that of the server).

-

Certain client-to-server service messages containing data sent by the client to the server (for example, msg_id of a recent client query) may, nonetheless, be processed on the client even if the time appears to be “incorrect”. This is especially true of messages to change server_salt and notifications of invalid client time. See Mobile Protocol: Service Messages.

-

Storing an Authorization Key on a Client Device

-

It may be suggested to users concerned with security that they password protect the authorization key in approximately the same way as in ssh. This can be accomplished by prepending the value of cryptographic hash function, such as SHA-256, of the key to the front of the key, following which the entire string is encrypted using AES in CBC mode and a key equal to the user’s (text) password. When the user inputs the password, the stored protected password is decrypted and verified by checking the SHA-256 value. From the user’s standpoint, this is practically the same as using an application or a website password.

-

Unencrypted Messages

-

Special plain-text messages may be used to create an authorization key as well as to perform a time synchronization. They begin with auth_key_id = 0 (64 bits) which means that there is no auth_key. This is followed directly by the message body in serialized format without internal or external headers. A message identifier (64 bits) and body length in bytes (32 bytes) are added before the message body.

-

Only a very limited number of messages of special types can be transmitted as plain text.

-

Schematic Presentation of Messages

-

Encrypted Message

- - - - -
auth_key_id
int64
msg_key
int128
encrypted_data
bytes
-

Encrypted Message: encrypted_data

-

Contains the cypher text for the following data:

- - - - - - - - -
salt
int64
session_id
int64
message_id
int64
seq_no
int32
message_data_length
int32
message_data
bytes
padding12..1024
bytes
-

Unencrypted Message

- - - - - -
auth_key_id = 0
int64
message_id
int64
message_data_length
int32
message_data
bytes
-

MTProto 2.0 uses 12..1024 padding bytes, instead of the 0..15 used in MTProto 1.0

-

Creating an Authorization Key

-

An authorization key is normally created once for every user during the application installation process immediately prior to registration. Registration itself, in actuality, occurs after the authorization key is created. However, a user may be prompted to complete the registration form while the authorization key is being generated in the background. Intervals between user key strokes may be used as a source of entropy in the generation of high-quality random numbers required for the creation of an authorization key.

-

See Creating an Authorization Key.

-

During the creation of the authorization key, the client obtains its server salt (to be used with the new key for all communication in the near future). The client then creates an encrypted session using the newly generated key, and subsequent communication occurs within that session (including the transmission of the user's registration information and phone number validation) unless the client creates a new session. The client is free to create new or additional sessions at any time by choosing a new random session_id.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/mtproto/description_v1.html b/data/core.telegram.org/mtproto/description_v1.html deleted file mode 100644 index 73c7fb0de0..0000000000 --- a/data/core.telegram.org/mtproto/description_v1.html +++ /dev/null @@ -1,205 +0,0 @@ - - - - - Mobile Protocol: Detailed Description (v.1.0, DEPRECATED) - - - - - - - - - - - - - -
- -
-
-
- -

Mobile Protocol: Detailed Description (v.1.0, DEPRECATED)

- -
-

This document describes MTProto v.1.0, its status is DEPRECATED. -For information on encryption used in up-to-date Telegram clients, kindly see this document.

-
-

Prior to a message (or a multipart message) being transmitted over a network using a transport protocol, it is encrypted in a certain way, and an external header is added at the top of the message which is: a 64-bit key identifier (that uniquely identifies an authorization key for the server as well as the user) and a 128-bit message key.

-

A user key together with the message key define an actual 256-bit key and a 256-bit initialization vector, which is what encrypts the message using AES-256 encryption with infinite garble extension (IGE). Note that the initial part of the message to be encrypted contains variable data (session, message ID, sequence number, server salt) that obviously influences the message key (and thus the AES key and iv). The message key is defined as the 128 lower-order bits of the SHA1 of the message body (including session, message ID, etc.) Multipart messages are encrypted as a single message.

- -

Terminology

-

Authorization Key

-

a 2048-bit key shared by the client device and the server, created upon user registration directly on the client device be exchanging Diffie-Hellman keys, and never transmitted over a network. Each authorization key is user-specific. There is nothing that prevents a user from having several keys (that correspond to “permanent sessions” on different devices), and some of these may be locked forever in the event the device is lost. See also Creating an Authorization Key.

-

Server Key

-

a 2048-bit RSA key used by the server digitally to sign its own messages while registration is underway and the authorization key is being generated. The application has a built-in public server key which can be used to verify a signature but cannot be used to sign messages. A private server key is stored on the server and changed very infrequently.

-

Key Identifier

-

The 64 lower-order bits of the SHA1 hash of the authorization key are used to indicate which particular key was used to encrypt a message. Keys must be uniquely defined by the 64 lower-order bits of their SHA1, and in the event of a collision, an authorization key is regenerated. A zero key identifier means that encryption is not used which is permissible for a limited set of message types used during registration to generate an authorization key based on a Diffie-Hellman exchange.

-

Session

-

a (random) 64-bit number generated by the client to distinguish between individual sessions (for example, between different instances of the application, created with the same authorization key). The session in conjunction with the key identifier corresponds to an application instance. The server can maintain session state. Under no circumstances can a message meant for one session be sent into a different session. The server may unilaterally forget any client sessions; clients should be able to handle this.

-

Server Salt

-

a (random) 64-bit number periodically (say, every 24 hours) changed (separately for each session) at the request of the server. All subsequent messages must contain the new salt (although, messages with the old salt are still accepted for a further 300 seconds). Required to protect against replay attacks and certain tricks associated with adjusting the client clock to a moment in the distant future.

-

Message Identifier (msg_id)

-

a (time-dependent) 64-bit number used uniquely to identify a message within a session. Client message identifiers are divisible by 4, server message identifiers modulo 4 yield 1 if the message is a response to a client message, and 3 otherwise. Client message identifiers must increase monotonically (within a single session), the same as server message identifiers, and must approximately equal unixtime*2^32. This way, a message identifier points to the approximate moment in time the message was created. A message is rejected over 300 seconds after it is created or 30 seconds before it is created (this is needed to protect from replay attacks). In this situation, it must be re-sent with a different identifier (or placed in a container with a higher identifier). The identifier of a message container must be strictly greater than those of its nested messages.

-

Important: to counter replay-attacks the lower 32 bits of msg_id passed by the client must not be empty and must present a fractional part of the time point when the message was created. At some point in the nearest future the server will start ignoring messages, in which the lower 32 bits of msg_id contain too many zeroes.

-

Content-related Message

-

A message requiring an explicit acknowledgment. These include all the user and many service messages, virtually all with the exception of containers and acknowledgments.

-

Message Sequence Number (msg_seqno)

-

a 32-bit number equal to twice the number of “content-related” messages (those requiring acknowledgment, and in particular those that are not containers) created by the sender prior to this message and subsequently incremented by one if the current message is a content-related message. A container is always generated after its entire contents; therefore, its sequence number is greater than or equal to the sequence numbers of the messages contained in it.

-

Message Key

-

The lower-order 128 bits of the SHA1 hash of the part of the message to be encrypted (including the internal header and excluding the alignment bytes).

-

Internal (cryptographic) Header

-

A header (16 bytes) added before a message or a container before it is all encrypted together. Consists of the server salt (64 bits) and the session (64 bits).

-

External (cryptographic) Header

-

A header (24 bytes) added before an encrypted message or a container. Consists of a key identifier (64 bits) and a message key (128 bits).

-

Payload

-

External header + encrypted message or container.

-

Defining AES Key and Initialization Vector

-

The 2048-bit authorization key (auth_key) and the 128-bit message key (msg_key) are used to compute a 256-bit AES key (aes_key) and a 256-bit initialization vector (aes_iv) which are subsequently used to encrypt the part of the message to be encrypted (i. e. everything with the exception of the external header which is added later) with AES-256 in infinite garble extension (IGE) mode.

-

The algorithm for computing aes_key and aes_iv from auth_key and msg_key is as follows:

-
    -
  • msg_key = substr (SHA1 (plaintext), 4, 16);
  • -
  • sha1_a = SHA1 (msg_key + substr (auth_key, x, 32));
  • -
  • sha1_b = SHA1 (substr (auth_key, 32+x, 16) + msg_key + substr (auth_key, 48+x, 16));
  • -
  • sha1_с = SHA1 (substr (auth_key, 64+x, 32) + msg_key);
  • -
  • sha1_d = SHA1 (msg_key + substr (auth_key, 96+x, 32));
  • -
  • aes_key = substr (sha1_a, 0, 8) + substr (sha1_b, 8, 12) + substr (sha1_c, 4, 12);
  • -
  • aes_iv = substr (sha1_a, 8, 12) + substr (sha1_b, 0, 8) + substr (sha1_c, 16, 4) + substr (sha1_d, 0, 8);
  • -
-

where x = 0 for messages from client to server and x = 8 for those from server to client.

-

The lower-order 1024 bits of auth_key are not involved in the computation. They may (together with the remaining bits or separately) be used on the client device to encrypt the local copy of the data received from the server. The 512 lower-order bits of auth_key are not stored on the server; therefore, if the client device uses them to encrypt local data and the user loses the key or the password, data decryption of local data is impossible (even if data from the server could be obtained).

-

When AES is used to encrypt a block of data of a length not divisible by 16 bytes, the data is padded with random bytes to the smallest length divisible by 16 bytes immediately prior to being encrypted.

-

Important Tests

-

When an encrypted message is received, it must be checked that msg_key is in fact equal to the 128 lower-order bits of the SHA1 hash of the previously encrypted portion, and that msg_id has even parity for messages from client to server, and odd parity for messages from server to client.

-

In addition, the identifiers (msg_id) of the last N messages received from the other side must be stored, and if a message comes in with msg_id lower than all or equal to any of the stored values, the message is to be ignored. Otherwise, the new message msg_id is added to the set, and, if the number of stored msg_id values is greater than N, the oldest (i. e. the lowest) is forgotten.

-

In addition, msg_id values that belong over 30 seconds in the future or over 300 seconds in the past are to be ignored. This is especially important for the server. The client would also find this useful (to protect from a replay attack), but only if it is certain of its time (for example, if its time has been synchronized with that of the server).

-

Certain client-to-server service messages containing data sent by the client to the server (for example, msg_id of a recent client query) may, nonetheless, be processed on the client even if the time appears to be “incorrect”. This is especially true of messages to change server_salt and notifications of invalid client time. See Mobile Protocol: Service Messages.

-

Storing an Authorization Key on a Client Device

-

It may be suggested to users concerned with security that they password protect the authorization key in approximately the same way as in ssh. This is accomplished by adding the SHA1 of the key to the front of the key, following which the entire string is encrypted using AES in CBC mode and a key equal to the user’s (text) password. When the user inputs the password, the stored protected password is decrypted and verified by being compared with SHA1. From the user’s standpoint, this is practically the same as using an application or a website password.

-

Unencrypted Messages

-

Special plain-text messages may be used to create an authorization key as well as to perform a time synchronization. They begin with auth_key_id = 0 (64 bits) which means that there is no auth_key. This is followed directly by the message body in serialized format without internal or external headers. A message identifier (64 bits) and body length in bytes (32 bytes) are added before the message body.

-

Only a very limited number of messages of special types can be transmitted as plain text.

-

Schematic Presentation of Messages

-

Encrypted Message

- - - - -
auth_key_id
int64
msg_key
int128
encrypted_data
bytes
-

Encrypted Message: encrypted_data

-

Contains the cypher text for the following data:

- - - - - - - - -
salt
int64
session_id
int64
message_id
int64
seq_no
int32
message_data_length
int32
message_data
bytes
padding 0..15
bytes
-

Unencrypted Message

- - - - - -
auth_key_id = 0
int64
message_id
int64
message_data_length
int32
message_data
bytes
-

Creating an Authorization Key

-

An authorization key is normally created once for every user during the application installation process immediately prior to registration. Registration itself, in actuality, occurs after the authorization key is created. However, a user may be prompted to complete the registration form while the authorization key is being generated in the background. Intervals between user key strokes may be used as a source of entropy in the generation of high-quality random numbers required for the creation of an authorization key.

-

See Creating an Authorization Key.

-

During the creation of the authorization key, the client obtains its server salt (to be used with the new key for all communication in the near future). The client then creates an encrypted session using the newly generated key, and subsequent communication occurs within that session (including the transmission of the user's registration information and phone number validation) unless the client creates a new session. The client is free to create new or additional sessions at any time by choosing a new random session_id.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/mtproto/mtproto-transports.html b/data/core.telegram.org/mtproto/mtproto-transports.html deleted file mode 100644 index 838d121472..0000000000 --- a/data/core.telegram.org/mtproto/mtproto-transports.html +++ /dev/null @@ -1,280 +0,0 @@ - - - - - MTProto transports - - - - - - - - - - - - - -
- -
-
-
- -

MTProto transports

- -
- -

Here's a list of MTProto transport protocols (see the ISO/OSI recap for a full explanation):

- -

The server recognizes these different protocols (and distinguishes them from HTTP, too) by the header.
Additionally, the following transport features can be used:

- -

Example implementations for these protocols can be seen in tdlib and MadelineProto.

-

Abridged

-

The lightest protocol available.

-
    -
  • Overhead: Very small
  • -
  • Minimum envelope length: 1 byte
  • -
  • Maximum envelope length: 4 bytes
  • -
-

Payload structure:

-
+-+----...----+
-|l|  payload  |
-+-+----...----+
-OR
-
-+-+---+----...----+
-|h|len|  payload  +
-+-+---+----...----+
-

Before sending anything into the underlying socket (see transports), the client must first send 0xef as the first byte (the server will not send 0xef as the first byte in the first reply).
Then, payloads are wrapped in the following envelope:

-
    -
  • Length: payload length, divided by four, and encoded as a single byte, only if the resulting packet length is a value between 0x01..0x7e.
  • -
  • Payload: the MTProto payload
  • -
-

If the packet length divided by four is bigger than or equal to 127 (>= 0x7f), the following envelope must be used, instead:

-
    -
  • Header: A single byte of value 0x7f
  • -
  • Length: payload length, divided by four, and encoded as 3 length bytes (little endian)
  • -
  • Payload: the MTProto payload
  • -
-

Intermediate

-

In case 4-byte data alignment is needed, an intermediate version of the original protocol may be used.

-
    -
  • Overhead: small
  • -
  • Minimum envelope length: 4 bytes
  • -
  • Maximum envelope length: 4 bytes
  • -
-

Payload structure:

-
+----+----...----+
-+len.+  payload  +
-+----+----...----+
-

Before sending anything into the underlying socket (see transports), the client must first send 0xeeeeeeee as the first int (four bytes, the server will not send 0xeeeeeeee as the first int in the first reply).
Then, payloads are wrapped in the following envelope:

-
    -
  • Length: payload length encoded as 4 length bytes (little endian)
  • -
  • Payload: the MTProto payload
  • -
-

Padded intermediate

-

Padded version of the intermediate protocol, to use with obfuscation enabled to bypass ISP blocks.

-
    -
  • Overhead: small-medium
  • -
  • Minimum envelope length: random
  • -
  • Maximum envelope length: random
  • -
-

Before sending anything into the underlying socket (see transports), the client must first send 0xdddddddd as the first int (four bytes, the server will not send 0xdddddddd as the first int in the first reply).
Then, payloads are wrapped in the following envelope:

-
+----+----...----+----...----+
-|tlen|  payload  |  padding  |
-+----+----...----+----...----+
-

Envelope description:

-
    -
  • Total length: payload+padding length encoded as 4 length bytes (little endian)
  • -
  • Payload: the MTProto payload
  • -
  • Padding: A random padding string of length 0-15
  • -
-

Full

-

The basic MTProto transport protocol

-
    -
  • Overhead: medium
  • -
  • Minimum envelope length: 12 bytes (length+seqno+crc)
  • -
  • Maximum envelope length: 12 bytes (length+seqno+crc)
  • -
-

Payload structure:

-
+----+----+----...----+----+
-|len.|seq.|  payload  |crc.|
-+----+----+----...----+----+
-

Envelope description:

-
    -
  • Length: length+seqno+payload+crc length encoded as 4 length bytes (little endian, the length of the length field must be included, too)
  • -
  • Seqno: the TCP sequence number for this TCP connection (different from the MTProto sequence number): the first packet sent is numbered 0, the next one 1, etc.
  • -
  • payload: MTProto payload
  • -
  • crc: 4 CRC32 bytes computed using length, sequence number, and payload together.
  • -
-

Transport features

-

Additionally, the following transport features can be used:

-

Quick ack

-

These MTProto transport protocols have support for quick acknowledgment.
In this case, the client sets the highest-order length bit in the query packet, and the server responds with a special 4 bytes as a separate packet.
They are the 32 higher-order bits of SHA256 of the encrypted portion of the packet prepended by 32 bytes from the authorization key (the same hash as computed for verifying the message key), with the most significant bit set to make clear that this is not the length of a regular server response packet; if the abridged version is used, bswap is applied to these four bytes.

-

Transport errors

-

In the event of a transport error (missing auth key, transport flood, etc.), the server may send a packet with a signed little-endian number of 4 bytes, whose absolute value contains the error code (the error itself is actually negative).

-

For example, error Code 403 corresponds to situations where the corresponding HTTP error would have been returned by the HTTP protocol.

-

Error 404 (auth key not found) is returned when the specified auth key ID cannot be found by the DC.

-

Error 429 (transport flood) is returned when too many transport connections are established to the same IP in a too short lapse of time, or if any of the container/service message limits are reached.

-

Transport obfuscation

-

Transport obfuscation is required to use the websocket transports.

-

Transport obfuscation to prevent ISP blocks is implemented using the following protocol, situated under the MTProto transport in the ISO/OSI stack, see the recap; this means that the payload is first wrapped in the MTProto transport envelope (all transports are supported), and then obfuscated:

-

Prior to establishing the connection (and eventually sending the protocol header of a specific MTProto transport), a 64-byte (512-bit) random initialization payload is generated.
During the generation process, special care must be taken in order to avoid a situation where that the first int (first four bytes) of the random string are equal to one of the known protocol identifiers (see above).
In particular, the first four bytes must not be equal to 0xdddddddd (padded intermediate), 0xeeeeeeee (intermediate), POST, GET, HEAD, or any of the HTTP methods that are accepted by the MTProto servers.
The first byte must also not be equal to 0xef (abridged).
Bytes 4-8 must also not be equal to 0x00000000, since that would indicate use of the full transport with the initial TCP sequence number (0).

-

The protocol identifier, if present, must be inserted in the initialization payload at byte offset 56: if its length is less than 4, it must be padded using the protocol identifier itself, to make its length 4 (0xef => 0xefefefef): the standalone protocol identifier must be not be sent aftwerwards.

-

This protocol is also (but not exclusively) used when connecting to MTProxies: only in this case, the DC ID in a specially encoded form must also be inserted in the initialization payload at offset 60.
The encoding simply consist of the DC ID in two-byte signed little-endian form; 10000 has to be added to the DC ID to connect to the test servers; it has to be made negative if the DC we're connecting to is a media (not CDN) DC.

-

Next, a secondary initialization payload is generated by reversing the primary initialization payload.

-

Two keys are extracted from both initialization payloads, using bytes at offsets 8-40: the key extracted from the primary payload is used as encryption key, the key extracted from the secondary payload is used as decryption key.

-

Two IVs are extracted from both initialization payloads, using bytes at offsets 40-56: the IV extracted from the primary payload is used as encryption IV, the IV extracted from the secondary payload is used as decryption IV.

-

Only if using MTProxy, the secret is used to provide connection with the MTProxy server.
The secret is a 16-byte string, usually distributed in its hexadecimal form along with the MTProxy host and port.

-

Often, a 17-byte version of the secret can be found: this simply indicates that the client should use a specific MTProto transport (based on the first byte, usually it's 0xdd, to indicate that the padded intermediate protocol should be used 0xdddddddd; however, clients should default to the padded intermediate transport whenever an additional byte in the secret is encountered).

-

The extracted encryption and decryption keys must be concatenated with the secret (the first byte of which should be ignored if it's the 17-byte version), and the SHA256 hash of such string should be used as encryption/decryption key.

-

The obtained encryption and decryption key/IV pairs must then be used with AES-256-CTR to encrypt and decrypt all outgoing and incoming payloads.

-

The first thing that must be encrypted using the encryption key is the initialization payload itself.
Then bytes 56-64 of the encrypted initialization payload are substituted in the original initialization payload: this is the part that contains the constant MTProto transport protocol identifier and the DC ID (only for MTProxies).

-

The final initialization payload must then be sent in the socket as first 64 bytes after the TCP handshake.

-

Example pseudocode for the generation of an MTProxy connection payload (media DC 4) using the obfuscated padded intermediate transport.
Warning: do not use the specified proxy secret in any MTProxy exposed on the internet.

-
protocol := 0xdddddddd
-dc := 0xfcff
-
-while 1:
-    init := (56 random bytes) + protocol + dc + (2 random bytes)
-
-    if init[0] == 0xef:
-      continue
-
-    first_int := substr(init, 0, 4)
-    if first_int == 0x44414548 || first_int == 0x54534f50 || first_int == 0x20544547 || first_int == 0x4954504f || first_int == 0x02010316 || first_int == 0xdddddddd || first_int == 0xeeeeeeee:
-      continue
-
-    second_int := substr(init, 4, 4)
-    if second_int == 0x00000000:
-      continue
-
-    break
-
-initRev := strrev(init)
-
-encryptKey := substr(init, 8, 32)
-encryptIV := substr(init, 40, 16)
-
-decryptKey := substr(initRev, 8, 32)
-decryptIV := substr(initRev, 40, 16)
-
-secret := substr(0xdd99999999999999999999999999999999, 1, 16)
-
-encryptKey = SHA256(encryptKey + secret)
-decryptKey = SHA256(decryptKey + secret)
-
-encryptedInit := CTR(encryptKey, encryptIV, init)
-
-finalInit := substr(init, 0, 56) + substr(encryptedInit, 56, 8)
-
-write(finalInit)
-
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/mtproto/samples-auth_key.html b/data/core.telegram.org/mtproto/samples-auth_key.html deleted file mode 100644 index e327ea0f77..0000000000 --- a/data/core.telegram.org/mtproto/samples-auth_key.html +++ /dev/null @@ -1,748 +0,0 @@ - - - - - samples-auth_key - - - - - - - - - - - - - -
- -
-
-
- -

samples-auth_key

- -

In the examples below, the transport headers are omitted:

-
-

For example, for an abridged version of the transport the client sends 0xef as the first byte (important: only prior to the very first data packet), then packet length is encoded by a single byte (0x01-0x7e = data length divided by 4; or 0x7f followed by 3 bytes (little endian) divided by 4) followed by the data themselves. In this case, server responses have the same form (although the server does not send 0xefas the first byte).

-
-

Detailed documentation on creating authorization keys is available here ».

-

1. Request for (p,q) Authorization

-
req_pq#60469778 nonce:int128 = ResPQ
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851e57ac42770964aExact unixtime * 2^32
message_length16, 420Message body length
%(req_pq)20, 460469778req_pq constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCRandom number
-

The header is 20 bytes long, the message body is 20 bytes long, and the entire message is 40 bytes in length.

-
0000 | 00 00 00 00 00 00 00 00 4A 96 70 27 C4 7A E5 51
-0010 | 14 00 00 00 78 97 46 60 3E 05 49 82 8C CA 27 E9
-0020 | 66 B3 01 A4 8F EC E2 FC
-

2. A response from the server has been received with the following content:

-
0000 | 00 00 00 00 00 00 00 00 01 C8 83 1E C9 7A E5 51
-0010 | 40 00 00 00 63 24 16 05 3E 05 49 82 8C CA 27 E9
-0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
-0030 | 77 BA 4A A5 73 90 73 30 08 17 ED 48 94 1A 08 F9
-0040 | 81 00 00 00 15 C4 B5 1C 01 00 00 00 21 6B E8 6C
-0050 | 02 2B B4 C3
-
Response decomposition using the following formula:
-
resPQ#05162463 nonce:int128 server_nonce:int128 pq:string server_public_key_fingerprints:Vector long = ResPQ 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851E57AC91E83C801Server message ID
message_length16, 464Message body length
%(resPQ)20, 405162463resPQ constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce40, 16A5CF4D33F4A11EA877BA4AA573907330Server-generated random number
pq56, 1217ED48941A08F981Single-byte prefix denoting length, an 8-byte string, and three bytes of padding
%(Vector long)68, 41cb5c415Vector long constructor number from TL schema
count72, 41Number of elements in key fingerprint list
fingerprints[]76, 8c3b42b026ce86b2164 lower-order bits of SHA1 (server_public_key)
-

The server_public_key public key has been selected whose fingerprint corresponds to the only one received from the server: c3b42b026ce86b21.

-

3. Pq = 17ED48941A08F981 decomposed into 2 prime cofactors:

-
p = 494C553B
-q = 53911073
-

4. encrypted_data Generation

-
p_q_inner_data#83c95aec pq:string p:string q:string nonce:int128 server_nonce:int128 new_nonce:int256 = P_Q_inner_data
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterOffset, Length in bytesValueDescription
%(p_q_inner_data)0, 483c95aecp_q_inner_data constructor number from TL schema
pq4, 1217ED48941A08F981Single-byte prefix denoting length, 8-byte string, and three bytes of padding
p16, 8494C553BFirst prime cofactor: single-byte prefix denoting length, 4-byte string, and three bytes of padding
q24, 853911073Second prime cofactor: single-byte prefix denoting length, 4-byte string, and three bytes of padding
nonce32, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce48, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
new_nonce64, 32311C85DB234AA2640AFC4A76A735CF5B 1F0FD68BD17FA181E1229AD867CC024DClient-generated random number
-

The serialization of P_Q_inner_data produces some string data. This is followed by encrypted_data:

-
SHA1 (data) = DB761C27718A2305044F71F2AD951629D78B2449
-RSA (data_with_hash, server_public_key) = 7BB0100A523161904D9C69FA04BC60DECFC5DD74B99995C768EB60D8716E2109BAF2D4601DAB6B09610DC11067BB89021E09471FCFA52DBD0F23204AD8CA8B012BF40A112F44695AB6C266955386114EF5211E6372227ADBD34995D3E0E5FF02EC63A43F9926878962F7C570E6A6E78BF8366AF917A5272675C46064BE62E3E202EFA8B1ADFB1C32A898C2987BE27B5F31D57C9BB963ABCB734B16F652CEDB4293CBB7C878A3A3FFAC9DBEA9DF7C67BC9E9508E111C78FC46E057F5C65ADE381D91FEE430A6B576A99BDF8551FDB1BE2B57069B1A45730618F27427E8A04720B4971EF4A9215983D68F2830C3EAA6E40385562F970D38A05C9F1246DC33438E6
-

The length of the final string was 256 bytes.

-
Request to Start Diffie-Hellman Key Exchange
-
req_DH_params#d712e4be nonce:int128 server_nonce:int128 p:string q:string public_key_fingerprint:long encrypted_data:string = Server_DH_Params
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851e57ac917717a27Exact unixtime * 2^32
message_length16, 4320Message body length
%(req_DH_params)20, 4d712e4bereq_DH_params constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce40, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
p56, 8494C553BFirst prime cofactor: single-byte prefix denoting length, 4-byte string, and three bytes of padding
q64, 853911073Second prime cofactor: single-byte prefix denoting length, 4-byte string, and three bytes of padding
public_key_fingerprint72, 8c3b42b026ce86b21Fingerprint of public key used
encrypted_data80, 260See aboveSee “Generation of encrypted_data"
-
0000 | 00 00 00 00 00 00 00 00 27 7A 71 17 C9 7A E5 51
-0010 | 40 01 00 00 BE E4 12 D7 3E 05 49 82 8C CA 27 E9
-0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
-0030 | 77 BA 4A A5 73 90 73 30 04 49 4C 55 3B 00 00 00
-0040 | 04 53 91 10 73 00 00 00 21 6B E8 6C 02 2B B4 C3
-0050 | FE 00 01 00 7B B0 10 0A 52 31 61 90 4D 9C 69 FA
-0060 | 04 BC 60 DE CF C5 DD 74 B9 99 95 C7 68 EB 60 D8
-0070 | 71 6E 21 09 BA F2 D4 60 1D AB 6B 09 61 0D C1 10
-0080 | 67 BB 89 02 1E 09 47 1F CF A5 2D BD 0F 23 20 4A
-0090 | D8 CA 8B 01 2B F4 0A 11 2F 44 69 5A B6 C2 66 95
-00A0 | 53 86 11 4E F5 21 1E 63 72 22 7A DB D3 49 95 D3
-00B0 | E0 E5 FF 02 EC 63 A4 3F 99 26 87 89 62 F7 C5 70
-00C0 | E6 A6 E7 8B F8 36 6A F9 17 A5 27 26 75 C4 60 64
-00D0 | BE 62 E3 E2 02 EF A8 B1 AD FB 1C 32 A8 98 C2 98
-00E0 | 7B E2 7B 5F 31 D5 7C 9B B9 63 AB CB 73 4B 16 F6
-00F0 | 52 CE DB 42 93 CB B7 C8 78 A3 A3 FF AC 9D BE A9
-0100 | DF 7C 67 BC 9E 95 08 E1 11 C7 8F C4 6E 05 7F 5C
-0110 | 65 AD E3 81 D9 1F EE 43 0A 6B 57 6A 99 BD F8 55
-0120 | 1F DB 1B E2 B5 70 69 B1 A4 57 30 61 8F 27 42 7E
-0130 | 8A 04 72 0B 49 71 EF 4A 92 15 98 3D 68 F2 83 0C
-0140 | 3E AA 6E 40 38 55 62 F9 70 D3 8A 05 C9 F1 24 6D
-0150 | C3 34 38 E6
-

5. A response from the server has been received with the following content:

-
0000 | 00 00 00 00 00 00 00 00 01 54 43 36 CB 7A E5 51
-0010 | 78 02 00 00 5C 07 E8 D0 3E 05 49 82 8C CA 27 E9
-0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
-0030 | 77 BA 4A A5 73 90 73 30 FE 50 02 00 28 A9 2F E2
-0040 | 01 73 B3 47 A8 BB 32 4B 5F AB 26 67 C9 A8 BB CE
-0050 | 64 68 D5 B5 09 A4 CB DD C1 86 24 0A C9 12 CF 70
-0060 | 06 AF 89 26 DE 60 6A 2E 74 C0 49 3C AA 57 74 1E
-0070 | 6C 82 45 1F 54 D3 E0 68 F5 CC C4 9B 44 44 12 4B
-0080 | 96 66 FF B4 05 AA B5 64 A3 D0 1E 67 F6 E9 12 86
-0090 | 7C 8D 20 D9 88 27 07 DC 33 0B 17 B4 E0 DD 57 CB
-00A0 | 53 BF AA FA 9E F5 BE 76 AE 6C 1B 9B 6C 51 E2 D6
-00B0 | 50 2A 47 C8 83 09 5C 46 C8 1E 3B E2 5F 62 42 7B
-00C0 | 58 54 88 BB 3B F2 39 21 3B F4 8E B8 FE 34 C9 A0
-00D0 | 26 CC 84 13 93 40 43 97 4D B0 35 56 63 30 38 39
-00E0 | 2C EC B5 1F 94 82 4E 14 0B 98 63 77 30 A4 BE 79
-00F0 | A8 F9 DA FA 39 BA E8 1E 10 95 84 9E A4 C8 34 67
-0100 | C9 2A 3A 17 D9 97 81 7C 8A 7A C6 1C 3F F4 14 DA
-0110 | 37 B7 D6 6E 94 9C 0A EC 85 8F 04 82 24 21 0F CC
-0120 | 61 F1 1C 3A 91 0B 43 1C CB D1 04 CC CC 8D C6 D2
-0130 | 9D 4A 5D 13 3B E6 39 A4 C3 2B BF F1 53 E6 3A CA
-0140 | 3A C5 2F 2E 47 09 B8 AE 01 84 4B 14 2C 1E E8 9D
-0150 | 07 5D 64 F6 9A 39 9F EB 04 E6 56 FE 36 75 A6 F8
-0160 | F4 12 07 8F 3D 0B 58 DA 15 31 1C 1A 9F 8E 53 B3
-0170 | CD 6B B5 57 2C 29 49 04 B7 26 D0 BE 33 7E 2E 21
-0180 | 97 7D A2 6D D6 E3 32 70 25 1C 2C A2 9D FC C7 02
-0190 | 27 F0 75 5F 84 CF DA 9A C4 B8 DD 5F 84 F1 D1 EB
-01A0 | 36 BA 45 CD DC 70 44 4D 8C 21 3E 4B D8 F6 3B 8A
-01B0 | B9 5A 2D 0B 41 80 DC 91 28 3D C0 63 AC FB 92 D6
-01C0 | A4 E4 07 CD E7 C8 C6 96 89 F7 7A 00 74 41 D4 A6
-01D0 | A8 38 4B 66 65 02 D9 B7 7F C6 8B 5B 43 CC 60 7E
-01E0 | 60 A1 46 22 3E 11 0F CB 43 BC 3C 94 2E F9 81 93
-01F0 | 0C DC 4A 1D 31 0C 0B 64 D5 E5 5D 30 8D 86 32 51
-0200 | AB 90 50 2C 3E 46 CC 59 9E 88 6A 92 7C DA 96 3B
-0210 | 9E B1 6C E6 26 03 B6 85 29 EE 98 F9 F5 20 64 19
-0220 | E0 3F B4 58 EC 4B D9 45 4A A8 F6 BA 77 75 73 CC
-0230 | 54 B3 28 89 5B 1D F2 5E AD 9F B4 CD 51 98 EE 02
-0240 | 2B 2B 81 F3 88 D2 81 D5 E5 BC 58 01 07 CA 01 A5
-0250 | 06 65 C3 2B 55 27 15 F3 35 FD 76 26 4F AD 00 DD
-0260 | D5 AE 45 B9 48 32 AC 79 CE 7C 51 1D 19 4B C4 2B
-0270 | 70 EF A8 50 BB 15 C2 01 2C 52 15 CA BF E9 7C E6
-0280 | 6B 8D 87 34 D0 EE 75 9A 63 8A F0 13
-
Response decomposition using the following formula:
-
server_DH_params_fail#79cb045d nonce:int128 server_nonce:int128 new_nonce_hash:int128 = Server_DH_Params;
-server_DH_params_ok#d0e8075c nonce:int128 server_nonce:int128 encrypted_answer:string = Server_DH_Params;
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851E57ACB36435401Exact unixtime * 2^32
message_length16, 4632Message body length
%(server_DH_params_ok)20, 4d0e8075cserver_DH_params_ok constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce40, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
encrypted_answer56, 596See belowSee “Decomposition of encrypted_answer"
-
Conversion of encrypted_answer into answer:
-
encrypted_answer = 28A92FE20173B347A8BB324B5FAB2667C9A8BBCE6468D5B509A4CBDDC186240AC912CF7006AF8926DE606A2E74C0493CAA57741E6C82451F54D3E068F5CCC49B4444124B9666FFB405AAB564A3D01E67F6E912867C8D20D9882707DC330B17B4E0DD57CB53BFAAFA9EF5BE76AE6C1B9B6C51E2D6502A47C883095C46C81E3BE25F62427B585488BB3BF239213BF48EB8FE34C9A026CC8413934043974DB03556633038392CECB51F94824E140B98637730A4BE79A8F9DAFA39BAE81E1095849EA4C83467C92A3A17D997817C8A7AC61C3FF414DA37B7D66E949C0AEC858F048224210FCC61F11C3A910B431CCBD104CCCC8DC6D29D4A5D133BE639A4C32BBFF153E63ACA3AC52F2E4709B8AE01844B142C1EE89D075D64F69A399FEB04E656FE3675A6F8F412078F3D0B58DA15311C1A9F8E53B3CD6BB5572C294904B726D0BE337E2E21977DA26DD6E33270251C2CA29DFCC70227F0755F84CFDA9AC4B8DD5F84F1D1EB36BA45CDDC70444D8C213E4BD8F63B8AB95A2D0B4180DC91283DC063ACFB92D6A4E407CDE7C8C69689F77A007441D4A6A8384B666502D9B77FC68B5B43CC607E60A146223E110FCB43BC3C942EF981930CDC4A1D310C0B64D5E55D308D863251AB90502C3E46CC599E886A927CDA963B9EB16CE62603B68529EE98F9F5206419E03FB458EC4BD9454AA8F6BA777573CC54B328895B1DF25EAD9FB4CD5198EE022B2B81F388D281D5E5BC580107CA01A50665C32B552715F335FD76264FAD00DDD5AE45B94832AC79CE7C511D194BC42B70EFA850BB15C2012C5215CABFE97CE66B8D8734D0EE759A638AF013
-tmp_aes_key = F011280887C7BB01DF0FC4E17830E0B91FBB8BE4B2267CB985AE25F33B527253
-tmp_aes_iv = 3212D579EE35452ED23E0D0C92841AA7D31B2E9BDEF2151E80D15860311C85DB
-answer = BA0D89B53E0549828CCA27E966B301A48FECE2FCA5CF4D33F4A11EA877BA4AA57390733002000000FE000100C71CAEB9C6B1C9048E6C522F70F13F73980D40238E3E21C14934D037563D930F48198A0AA7C14058229493D22530F4DBFA336F6E0AC925139543AED44CCE7C3720FD51F69458705AC68CD4FE6B6B13ABDC9746512969328454F18FAF8C595F642477FE96BB2A941D5BCD1D4AC8CC49880708FA9B378E3C4F3A9060BEE67CF9A4A4A695811051907E162753B56B0F6B410DBA74D8A84B2A14B3144E0EF1284754FD17ED950D5965B4B9DD46582DB1178D169C6BC465B0D6FF9CA3928FEF5B9AE4E418FC15E83EBEA0F87FA9FF5EED70050DED2849F47BF959D956850CE929851F0D8115F635B105EE2E4E15D04B2454BF6F4FADF034B10403119CD8E3B92FCC5BFE000100262AABA621CC4DF587DC94CF8252258C0B9337DFB47545A49CDD5C9B8EAE7236C6CADC40B24E88590F1CC2CC762EBF1CF11DCC0B393CAAD6CEE4EE5848001C73ACBB1D127E4CB93072AA3D1C8151B6FB6AA6124B7CD782EAF981BDCFCE9D7A00E423BD9D194E8AF78EF6501F415522E44522281C79D906DDB79C72E9C63D83FB2A940FF779DFB5F2FD786FB4AD71C9F08CF48758E534E9815F634F1E3A80A5E1C2AF210C5AB762755AD4B2126DFA61A77FA9DA967D65DFD0AFB5CDF26C4D4E1A88B180F4E0D0B45BA1484F95CB2712B50BF3F5968D9D55C99C0FB9FB67BFF56D7D4481B634514FBA3488C4CDA2FC0659990E8E868B28632875A9AA703BCDCE8FCB7AE551
-
Server_DH_inner_data decomposition using the following formula:
-
server_DH_inner_data#b5890dba nonce:int128 server_nonce:int128 g:int dh_prime:string g_a:string server_time:int = Server_DH_inner_data;
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterOffset, Length in bytesValueDescription
%(server_DH_inner_data)0, 4b5890dbaserver_DH_inner_data constructor number from TL schema
nonce4, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce20, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
g36, 42Value received from server in Step 2
dh_prime40, 260C71CAEB9C6B1C9048E6C522F70F13F73 980D40238E3E21C14934D037563D930F 48198A0AA7C14058229493D22530F4DB FA336F6E0AC925139543AED44CCE7C37 20FD51F69458705AC68CD4FE6B6B13AB DC9746512969328454F18FAF8C595F64 2477FE96BB2A941D5BCD1D4AC8CC4988 0708FA9B378E3C4F3A9060BEE67CF9A4 A4A695811051907E162753B56B0F6B41 0DBA74D8A84B2A14B3144E0EF1284754 FD17ED950D5965B4B9DD46582DB1178D 169C6BC465B0D6FF9CA3928FEF5B9AE4 E418FC15E83EBEA0F87FA9FF5EED7005 0DED2849F47BF959D956850CE929851F 0D8115F635B105EE2E4E15D04B2454BF 6F4FADF034B10403119CD8E3B92FCC5B
g_a300, 260262AABA621CC4DF587DC94CF8252258C 0B9337DFB47545A49CDD5C9B8EAE7236 C6CADC40B24E88590F1CC2CC762EBF1C F11DCC0B393CAAD6CEE4EE5848001C73 ACBB1D127E4CB93072AA3D1C8151B6FB 6AA6124B7CD782EAF981BDCFCE9D7A00 E423BD9D194E8AF78EF6501F415522E4 4522281C79D906DDB79C72E9C63D83FB 2A940FF779DFB5F2FD786FB4AD71C9F0 8CF48758E534E9815F634F1E3A80A5E1 C2AF210C5AB762755AD4B2126DFA61A7 7FA9DA967D65DFD0AFB5CDF26C4D4E1A 88B180F4E0D0B45BA1484F95CB2712B5 0BF3F5968D9D55C99C0FB9FB67BFF56D 7D4481B634514FBA3488C4CDA2FC0659 990E8E868B28632875A9AA703BCDCE8F
server_time560, 41373993675Server time
-

6. Random number b is computed:

-
b = 6F620AFA575C9233EB4C014110A7BCAF49464F798A18A0981FEA1E05E8DA67D9681E0FD6DF0EDF0272AE3492451A84502F2EFC0DA18741A5FB80BD82296919A70FAA6D07CBBBCA2037EA7D3E327B61D585ED3373EE0553A91CBD29B01FA9A89D479CA53D57BDE3A76FBD922A923A0A38B922C1D0701F53FF52D7EA9217080163A64901E766EB6A0F20BC391B64B9D1DD2CD13A7D0C946A3A7DF8CEC9E2236446F646C42CFE2B60A2A8D776E56C8D7519B08B88ED0970E10D12A8C9E355D765F2B7BBB7B4CA9360083435523CB0D57D2B106FD14F94B4EEE79D8AC131CA56AD389C84FE279716F8124A543337FB9EA3D988EC5FA63D90A4BA3970E7A39E5C0DE5
-
Generation of encrypted_data
-
client_DH_inner_data#6643b654 nonce:int128 server_nonce:int128 retry_id:long g_b:string = Client_DH_Inner_Data
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterOffset, Length in bytesValueDescription
%(client_DH_inner_data)0, 46643b654client_DH_inner_data constructor number from TL schema
nonce4, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce20, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
retry_id36, 80First attempt
g_b44, 26073700E7BFC7AEEC828EB8E0DCC04D09A 0DD56A1B4B35F72F0B55FCE7DB7EBB72 D7C33C5D4AA59E1C74D09B01AE536B31 8CFED436AFDB15FE9EB4C70D7F0CB14E 46DBBDE9053A64304361EB358A9BB32E 9D5C2843FE87248B89C3F066A7D5876D 61657ACC52B0D81CD683B2A0FA93E8AD AB20377877F3BC3369BBF57B10F5B589 E65A9C27490F30A0C70FFCFD3453F5B3 79C1B9727A573CFFDCA8D23C721B135B 92E529B1CDD2F7ABD4F34DAC4BE1EEAF 60993DDE8ED45890E4F47C26F2C0B2E0 37BB502739C8824F2A99E2B1E7E41658 3417CC79A8807A4BDAC6A5E9805D4F61 86C37D66F6988C9F9C752896F3D34D25 529263FAF2670A09B2A59CE35264511Fg^b mod dh_prime
-

The serialization of Client_DH_Inner_Data produces some string data. This is followed by encrypted_data:

-
data_with_hash := SHA1(data) + data + (0-15 random bytes); such that the length be divisible by 16;
-AES256_ige_encrypt (data_with_hash, tmp_aes_key, tmp_aes_iv) = 928A4957D0463B525C1CC48AABAA030A256BE5C746792C84CA4C5A0DF60AC799048D98A38A8480EDCF082214DFC79DCB9EE34E206513E2B3BC1504CFE6C9ADA46BF9A03CA74F192EAF8C278454ADABC795A566615462D31817382984039505F71CB33A41E2527A4B1AC05107872FED8E3ABCEE1518AE965B0ED3AED7F67479155BDA8E4C286B64CDF123EC748CF289B1DB02D1907B562DF462D8582BA6F0A3022DC2D3504D69D1BA48B677E3A830BFAFD67584C8AA24E1344A8904E305F9587C92EF964F0083F50F61EAB4A393EAA33C9270294AEDC7732891D4EA1599F52311D74469D2112F4EDF3F342E93C8E87E812DC3989BAECFE6740A46077524C75093F5A5405736DE8937BB6E42C9A0DCF22CA53227D462BCCC2CFE94B6FE86AB7FBFA395021F66661AF7C0024CA2986CA03F3476905407D1EA9C010B763258DB1AA2CC7826D91334EFC1FDC665B67FE45ED0
-

The length of the final string was 336 bytes.

-
Request
-
set_client_DH_params#f5045f1f nonce:int128 server_nonce:int128 encrypted_data:string = Set_client_DH_params_answer;
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851e57acd2aa32c6dExact unixtime * 2^32
message_length16, 4376Message body length
%(set_client_DH_params)20, 4f5045f1fset_client_DH_params constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce40, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
encrypted_data56, 340See aboveSee “Generation of encrypted_data"
-
0000 | 00 00 00 00 00 00 00 00 6D 2C A3 2A CD 7A E5 51
-0010 | 78 01 00 00 1F 5F 04 F5 3E 05 49 82 8C CA 27 E9
-0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
-0030 | 77 BA 4A A5 73 90 73 30 FE 50 01 00 92 8A 49 57
-0040 | D0 46 3B 52 5C 1C C4 8A AB AA 03 0A 25 6B E5 C7
-0050 | 46 79 2C 84 CA 4C 5A 0D F6 0A C7 99 04 8D 98 A3
-0060 | 8A 84 80 ED CF 08 22 14 DF C7 9D CB 9E E3 4E 20
-0070 | 65 13 E2 B3 BC 15 04 CF E6 C9 AD A4 6B F9 A0 3C
-0080 | A7 4F 19 2E AF 8C 27 84 54 AD AB C7 95 A5 66 61
-0090 | 54 62 D3 18 17 38 29 84 03 95 05 F7 1C B3 3A 41
-00A0 | E2 52 7A 4B 1A C0 51 07 87 2F ED 8E 3A BC EE 15
-00B0 | 18 AE 96 5B 0E D3 AE D7 F6 74 79 15 5B DA 8E 4C
-00C0 | 28 6B 64 CD F1 23 EC 74 8C F2 89 B1 DB 02 D1 90
-00D0 | 7B 56 2D F4 62 D8 58 2B A6 F0 A3 02 2D C2 D3 50
-00E0 | 4D 69 D1 BA 48 B6 77 E3 A8 30 BF AF D6 75 84 C8
-00F0 | AA 24 E1 34 4A 89 04 E3 05 F9 58 7C 92 EF 96 4F
-0100 | 00 83 F5 0F 61 EA B4 A3 93 EA A3 3C 92 70 29 4A
-0110 | ED C7 73 28 91 D4 EA 15 99 F5 23 11 D7 44 69 D2
-0120 | 11 2F 4E DF 3F 34 2E 93 C8 E8 7E 81 2D C3 98 9B
-0130 | AE CF E6 74 0A 46 07 75 24 C7 50 93 F5 A5 40 57
-0140 | 36 DE 89 37 BB 6E 42 C9 A0 DC F2 2C A5 32 27 D4
-0150 | 62 BC CC 2C FE 94 B6 FE 86 AB 7F BF A3 95 02 1F
-0160 | 66 66 1A F7 C0 02 4C A2 98 6C A0 3F 34 76 90 54
-0170 | 07 D1 EA 9C 01 0B 76 32 58 DB 1A A2 CC 78 26 D9
-0180 | 13 34 EF C1 FD C6 65 B6 7F E4 5E D0
-

7. Computing auth_key using formula g^{ab} mod dh_prime:

-
auth_key = AB96E207C631300986F30EF97DF55E179E63C112675F0CE502EE76D74BBEE6CBD1E95772818881E9F2FF54BD52C258787474F6A7BEA61EABE49D1D01D55F64FC07BC31685716EC8FB46FEACF9502E42CFD6B9F45A08E90AA5C2B5933AC767CBE1CD50D8E64F89727CA4A1A5D32C0DB80A9FCDBDDD4F8D5A1E774198F1A4299F927C484FEEC395F29647E43C3243986F93609E23538C21871DF50E00070B3B6A8FA9BC15628E8B43FF977409A61CEEC5A21CF7DFB5A4CC28F5257BC30CD8F2FB92FBF21E28924065F50E0BBD5E11A420300E2C136B80E9826C6C5609B5371B7850AA628323B6422F3A94F6DFDE4C3DC1EA60F7E11EE63122B3F39CBD1A8430157
-

8. The server verifies that auth_key_hash is unique.

-

The key is unique.

-

9. A response from the server has been received with the following content:

-
0000 | 00 00 00 00 00 00 00 00 01 30 AA C5 CE 7A E5 51
-0010 | 34 00 00 00 34 F7 CB 3B 3E 05 49 82 8C CA 27 E9
-0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
-0030 | 77 BA 4A A5 73 90 73 30 CC EB C0 21 72 66 E1 ED
-0040 | EC 7F B0 A0 EE D6 C2 20
-

Set_client_DH_params_answer decomposition using the following formula:

-
dh_gen_ok#3bcbf734 nonce:int128 server_nonce:int128 new_nonce_hash1:int128 = Set_client_DH_params_answer;
-dh_gen_retry#46dc1fb9 nonce:int128 server_nonce:int128 new_nonce_hash2:int128 = Set_client_DH_params_answer;
-dh_gen_fail#a69dae02 nonce:int128 server_nonce:int128 new_nonce_hash3:int128 = Set_client_DH_params_answer;
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterOffset, Length in bytesValueDescription
%(dh_gen_ok)0, 43bcbf734dh_gen_ok constructor number from TL schema
nonce4, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce20, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
new_nonce_hash136, 16CCEBC0217266E1EDEC7FB0A0EED6C220
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/mtproto/security_guidelines.html b/data/core.telegram.org/mtproto/security_guidelines.html deleted file mode 100644 index 180cb6991a..0000000000 --- a/data/core.telegram.org/mtproto/security_guidelines.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - Security Guidelines for Client Developers - - - - - - - - - - - - - -
- -
-
-
- -

Security Guidelines for Client Developers

- -
- -

See also:

-

- -

While MTProto is designed to be a reasonably fast and secure protocol, its advantages can be easily negated by careless implementation. We collected some security guidelines for client software developers on this page. All Telegram clients are required to comply.

-
-

Note that as of version 4.6, major Telegram clients are using MTProto 2.0. -MTProto v.1.0 is deprecated and is currently being phased out.

-
-

Diffie-Hellman key exchange

-

We use DH key exchange in two cases:

- -

In both cases, there are some verifications to be done whenever DH is used:

-

Validation of DH parameters

-

Client is expected to check whether p = dh_prime is a safe 2048-bit prime (meaning that both p and (p-1)/2 are prime, and that 2^2047 < p < 2^2048), and that g generates a cyclic subgroup of prime order (p-1)/2, i.e. is a quadratic residue mod p. Since g is always equal to 2, 3, 4, 5, 6 or 7, this is easily done using quadratic reciprocity law, yielding a simple condition on p mod 4g -- namely, p mod 8 = 7 for g = 2; p mod 3 = 2 for g = 3; no extra condition for g = 4; p mod 5 = 1 or 4 for g = 5; p mod 24 = 19 or 23 for g = 6; and p mod 7 = 3, 5 or 6 for g = 7. After g and p have been checked by the client, it makes sense to cache the result, so as not to repeat lengthy computations in future.

-

If the verification takes too long (which is the case for older mobile devices), one might initially run only 15 Miller--Rabin iterations (use parameter 30 in Java) for verifying primeness of p and (p - 1)/2 with error probability not exceeding one billionth, and do more iterations in the background later.

-

Another way to optimize this is to embed into the client application code a small table with some known "good" couples (g,p) (or just known safe primes p, since the condition on g is easily verified during execution), checked during code generation phase, so as to avoid doing such verification during runtime altogether. The server rarely changes these values, thus one usually needs to put the current value of server's dh_prime into such a table. For example, the current value of dh_prime equals (in big-endian byte order)

-
C7 1C AE B9 C6 B1 C9 04 8E 6C 52 2F 70 F1 3F 73 98 0D 40 23 8E 3E 21 C1 49 34 D0 37 56 3D 93 0F 48 19 8A 0A A7 C1 40 58 22 94 93 D2 25 30 F4 DB FA 33 6F 6E 0A C9 25 13 95 43 AE D4 4C CE 7C 37 20 FD 51 F6 94 58 70 5A C6 8C D4 FE 6B 6B 13 AB DC 97 46 51 29 69 32 84 54 F1 8F AF 8C 59 5F 64 24 77 FE 96 BB 2A 94 1D 5B CD 1D 4A C8 CC 49 88 07 08 FA 9B 37 8E 3C 4F 3A 90 60 BE E6 7C F9 A4 A4 A6 95 81 10 51 90 7E 16 27 53 B5 6B 0F 6B 41 0D BA 74 D8 A8 4B 2A 14 B3 14 4E 0E F1 28 47 54 FD 17 ED 95 0D 59 65 B4 B9 DD 46 58 2D B1 17 8D 16 9C 6B C4 65 B0 D6 FF 9C A3 92 8F EF 5B 9A E4 E4 18 FC 15 E8 3E BE A0 F8 7F A9 FF 5E ED 70 05 0D ED 28 49 F4 7B F9 59 D9 56 85 0C E9 29 85 1F 0D 81 15 F6 35 B1 05 EE 2E 4E 15 D0 4B 24 54 BF 6F 4F AD F0 34 B1 04 03 11 9C D8 E3 B9 2F CC 5B
-

g_a and g_b validation

-

Apart from the conditions on the Diffie-Hellman prime dh_prime and generator g, both sides are to check that g, g_a and g_b are greater than 1 and less than dh_prime - 1. We recommend checking that g_a and g_b are between 2^{2048-64} and dh_prime - 2^{2048-64} as well.

-

Checking SHA1 hash values during key generation

-

Once the client receives a server_DH_params_ok answer in step 5) of the Authorization Key generation protocol and decrypts it obtaining answer_with_hash, it MUST check that

-
answer_with_hash := SHA1(answer) + answer + (0-15 random bytes)
-

In other words, the first 20 bytes of answer_with_hash must be equal to SHA1 of the remainder of the decrypted message without the padding random bytes.

-

Checking nonce, server_nonce and new_nonce fields

-

When the client receives and/or decrypts server messages during creation of Authorization Key, and these messages contain some nonce fields already known to the client from messages previously obtained during the same run of the protocol, the client is to check that these fields indeed contain the values previosly known.

-

Using secure pseudorandom number generator to create DH secret parameters a and b

-

Client must use a cryptographically secure PRNG to generate secret exponents a or b for DH key exchange. For secret chats, the client might request some entropy (random bytes) from the server while invoking messages.getDhConfig and feed these random bytes into its PRNG (for example, by PRNG_seed if OpenSSL library is used), but never using these "random" bytes by themselves or replacing by them the local PRNG seed. One should mix bytes received from server into local PRNG seed.

-

MTProto Encrypted Messages

-

Some important checks are to be done while sending and especially receiving encrypted MTProto messages.

-

Checking SHA256 hash value of msg_key

-

msg_key is used not only to compute the AES key and IV to decrypt the received message. After decryption, the client MUST check that msg_key is indeed equal to SHA256 of the plaintext obtained as the result of decryption (including the final 12...1024 padding bytes), prepended with 32 bytes taken from the auth_key, as explained in MTProto 2.0 Description.

-

If an error is encountered before this check could be performed, the client must perform the msg_key check anyway before returning any result. Note that the response to any error encountered before the msg_key check must be the same as the response to a failed msg_key check.

-

Checking message length

-

The client must check that the length of the message or container obtained from the decrypted message (computed from its length field) does not exceed the total size of the plaintext, and that the difference (i.e. the length of the random padding) lies in the range from 12 to 1024 bytes.

-

The length should be always divisible by 4 and non-negative. On no account the client is to access data past the end of the decryption buffer containing the plaintext message.

-

Checking session_id

-

The client is to check that the session_id field in the decrypted message indeed equals to that of an active session created by the client.

-

Checking msg_id

-

The client must check that msg_id has even parity for messages from client to server, and odd parity for messages from server to client.

-

In addition, the identifiers (msg_id) of the last N messages received from the other side must be stored, and if a message comes in with an msg_id lower than all or equal to any of the stored values, that message is to be ignored. Otherwise, the new message msg_id is added to the set, and, if the number of stored msg_id values is greater than N, the oldest (i. e. the lowest) is discarded.

-

In addition, msg_id values that belong over 30 seconds in the future or over 300 seconds in the past are to be ignored (recall that msg_id approximately equals unixtime * 2^32). This is especially important for the server. The client would also find this useful (to protect from a replay attack), but only if it is certain of its time (for example, if its time has been synchronized with that of the server).

-

Certain client-to-server service messages containing data sent by the client to the server (for example, msg_id of a recent client query) may, nonetheless, be processed on the client even if the time appears to be “incorrect”. This is especially true of messages to change server_salt and notifications about invalid time on the client. See Mobile Protocol: Service Messages.

-

Behavior in case of mismatch

-

If one of the checks listed above fails, the client is to completely discard the message obtained from server. We also recommend closing and reestablishing the TCP connection to the server, then retrying the operation or the whole key generation protocol.

-

No information from incorrect messages can be used. Even if the application throws an exception and dies, this is much better than continuing with invalid data.

-

Notice that invalid messages will infrequently appear during normal work even if no malicious tampering is being done. This is due to network transmission errors. We recommend ignoring the invalid message and closing the TCP connection, then creating a new TCP connection to the server and retrying the original query.

-
-

The previous version of security recommendations relevant for MTProto 1.0 clients is available here.

-
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/mtproto/security_guidelines_v1.html b/data/core.telegram.org/mtproto/security_guidelines_v1.html deleted file mode 100644 index bbf0d1a3b5..0000000000 --- a/data/core.telegram.org/mtproto/security_guidelines_v1.html +++ /dev/null @@ -1,175 +0,0 @@ - - - - - Security Guidelines for Client Developers (v.1.0, DEPRECATED) - - - - - - - - - - - - - -
- -
-
-
- -

Security Guidelines for Client Developers (v.1.0, DEPRECATED)

- -
- -
-

This document describes security recommendations for clients using MTProto 1.0, its status is DEPRECATED. -For up-to-date security recommendations, kindly see this document.

-
-

See also:

-

- -

While MTProto is designed to be a reasonably fast and secure protocol, its advantages can be easily negated by careless implementation. We collected some security guidelines for client software developers on this page. All Telegram clients are required to comply with these.

-

Diffie--Hellman key exchange

-

We use DH key exchange in two cases:

- -

In both cases, there are some verifications to be done whenever DH is used:

-

Validation of DH parameters

-

Client is expected to check whether p = dh_prime is a safe 2048-bit prime (meaning that both p and (p-1)/2 are prime, and that 2^2047 < p < 2^2048), and that g generates a cyclic subgroup of prime order (p-1)/2, i.e. is a quadratic residue mod p. Since g is always equal to 2, 3, 4, 5, 6 or 7, this is easily done using quadratic reciprocity law, yielding a simple condition on p mod 4g -- namely, p mod 8 = 7 for g = 2; p mod 3 = 2 for g = 3; no extra condition for g = 4; p mod 5 = 1 or 4 for g = 5; p mod 24 = 19 or 23 for g = 6; and p mod 7 = 3, 5 or 6 for g = 7. After g and p have been checked by the client, it makes sense to cache the result, so as not to repeat lengthy computations in future.

-

If the verification takes too long (which is the case for older mobile devices), one might initially run only 15 Miller--Rabin iterations (use parameter 30 in Java) for verifying primeness of p and (p - 1)/2 with error probability not exceeding one billionth, and do more iterations in the background later.

-

Another way to optimize this is to embed into the client application code a small table with some known "good" couples (g,p) (or just known safe primes p, since the condition on g is easily verified during execution), checked during code generation phase, so as to avoid doing such verification during runtime altogether. The server rarely changes these values, thus one usually needs to put the current value of server's dh_prime into such a table. For example, the current value of dh_prime equals (in big-endian byte order)

-
C7 1C AE B9 C6 B1 C9 04 8E 6C 52 2F 70 F1 3F 73 98 0D 40 23 8E 3E 21 C1 49 34 D0 37 56 3D 93 0F 48 19 8A 0A A7 C1 40 58 22 94 93 D2 25 30 F4 DB FA 33 6F 6E 0A C9 25 13 95 43 AE D4 4C CE 7C 37 20 FD 51 F6 94 58 70 5A C6 8C D4 FE 6B 6B 13 AB DC 97 46 51 29 69 32 84 54 F1 8F AF 8C 59 5F 64 24 77 FE 96 BB 2A 94 1D 5B CD 1D 4A C8 CC 49 88 07 08 FA 9B 37 8E 3C 4F 3A 90 60 BE E6 7C F9 A4 A4 A6 95 81 10 51 90 7E 16 27 53 B5 6B 0F 6B 41 0D BA 74 D8 A8 4B 2A 14 B3 14 4E 0E F1 28 47 54 FD 17 ED 95 0D 59 65 B4 B9 DD 46 58 2D B1 17 8D 16 9C 6B C4 65 B0 D6 FF 9C A3 92 8F EF 5B 9A E4 E4 18 FC 15 E8 3E BE A0 F8 7F A9 FF 5E ED 70 05 0D ED 28 49 F4 7B F9 59 D9 56 85 0C E9 29 85 1F 0D 81 15 F6 35 B1 05 EE 2E 4E 15 D0 4B 24 54 BF 6F 4F AD F0 34 B1 04 03 11 9C D8 E3 B9 2F CC 5B
-

g_a and g_b validation

-

Apart from the conditions on the Diffie-Hellman prime dh_prime and generator g, both sides are to check that g, g_a and g_b are greater than 1 and less than dh_prime - 1. We recommend checking that g_a and g_b are between 2^{2048-64} and dh_prime - 2^{2048-64} as well.

-

Checking SHA1 hash values

-

Once the client receives a server_DH_params_ok answer in step 5) of the Authorization Key generation protocol and decrypts it obtaining answer_with_hash, it MUST check that

-
answer_with_hash := SHA1(answer) + answer + (0-15 random bytes)
-

In other words, the first 20 bytes of answer_with_hash must be equal to SHA1 of the remainder of the decrypted message without the padding random bytes.

-

Checking nonce, server_nonce and new_nonce fields

-

When the client receives and/or decrypts server messages during creation of Authorization Key, and these messages contain some nonce fields already known to the client from messages previously obtained during the same run of the protocol, the client is to check that these fields indeed contain the values previosly known.

-

Using secure pseudorandom number generator to create DH secret parameters a and b

-

Client must use a cryptographically secure PRNG to generate secret exponents a or b for DH key exchange. For secret chats, the client might request some entropy (random bytes) from the server while invoking messages.getDhConfig and feed these random bytes into its PRNG (for example, by PRNG_seed if OpenSSL library is used), but never using these "random" bytes by themselves or replacing by them the local PRNG seed. One should mix bytes received from server into local PRNG seed.

-

MTProto Encrypted Messages

-

Some important checks are to be done while sending and especially receiving encrypted MTProto messages.

-

Checking SHA1 hash value of msg_key

-

msg_key is used not only to compute the AES key and IV to decrypt the received message. After decryption, the client MUST check that msg_key is indeed equal to SHA1 of the plaintext obtained as the result of decryption (without the final padding bytes).

-

If an error is encountered before this check could be performed, the client must perform the msg-key check anyway before returning any result. Note that the response to any error encountered before the msg_key check must be the same as the response to a failed msg_key check.

-

Checking message length

-

The client is to check that the length of the message or container obtained from the decrypted message (computed from its length field) does not exceed the total size of the plaintext, and that the difference is not more than 15 bytes. Apart from this, knowing the total length is important for the previous verification.

-

The length should be always divisible by 4 and non-negative. On no account the client is to access data past the end of the decryption buffer containing the plaintext message.

-

Checking session_id

-

The client is to check that the session_id field in the decrypted message indeed equals to that of an active session created by the client.

-

Checking msg_id

-

The client must check that msg_id has even parity for messages from client to server, and odd parity for messages from server to client.

-

In addition, the identifiers (msg_id) of the last N messages received from the other side must be stored, and if a message comes in with an msg_id lower than all or equal to any of the stored values, that message is to be ignored. Otherwise, the new message msg_id is added to the set, and, if the number of stored msg_id values is greater than N, the oldest (i. e. the lowest) is discarded.

-

In addition, msg_id values that belong over 30 seconds in the future or over 300 seconds in the past are to be ignored (recall that msg_id approximately equals unixtime * 2^32). This is especially important for the server. The client would also find this useful (to protect from a replay attack), but only if it is certain of its time (for example, if its time has been synchronized with that of the server).

-

Certain client-to-server service messages containing data sent by the client to the server (for example, msg_id of a recent client query) may, nonetheless, be processed on the client even if the time appears to be “incorrect”. This is especially true of messages to change server_salt and notifications about invalid time on the client. See Mobile Protocol: Service Messages.

-

Behavior in case of mismatch

-

If one of the checks listed above fails, the client is to completely discard the message obtained from server. We also recommend closing and reestablishing the TCP connection to the server, then retrying the operation or the whole key generation protocol.

-

No information from incorrect messages can be used. Even if the application throws an exception and dies, this is much better than continuing with invalid data.

-

Notice that invalid messages will infrequently appear during normal work even if no malicious tampering is being done. This is due to network transmission errors. We recommend ignoring the invalid message and closing the TCP connection, then creating a new TCP connection to the server and retrying the original query.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/mtproto/serialize.html b/data/core.telegram.org/mtproto/serialize.html deleted file mode 100644 index e014d3aa7c..0000000000 --- a/data/core.telegram.org/mtproto/serialize.html +++ /dev/null @@ -1,240 +0,0 @@ - - - - - Binary Data Serialization - - - - - - - - - - - - - -
- -
-
-
- -

Binary Data Serialization

- -

MTProto operation requires that elementary and composite data types as well as queries to which such data types are passed as arguments or by which they are returned, be transmitted in binary format (i. e. serialized) . -The TL language is used to describe the data types to be serialized.

-

General Definitions

-

For our purposes, we can identify a type with the set of its (serialized) values understood as strings (finite sequences) of 32-bit numbers (transmitted in little endian order).

-

Therefore:

-
    -
  • Alphabet (A), in this case, is a set of 32-bit numbers (normally, signed, i. e. between -2^31 and 2^31 - 1).
  • -
  • Value, in this case, is the same as a string in Alphabet A, i. e. a finite (possibly, empty) sequence of 32-bit numbers. The set of all such sequences is designated as A*.
  • -
  • Type, for our purposes, is the same as the set of legal values of a type, i. e. some set T which is a subset of A* and is a prefix code (i. e. no element of T may be a prefix for any other element). Therefore, any sequence from A* can contain no more than one prefix that is a member of T.
  • -
  • Value of Type T is any sequence (value) which is a member of T as a subset of A*.
  • -
  • Compatible Types are the types T and T’ not intersecting as subsets of A*, such that the union of T and T' is a prefix code.
  • -
  • Coordinated System of Types is a finite or infinite set of types T_1, ..., T_n, ..., such that any two types from this set are compatible.
  • -
  • Data Type is the same as type in the sense of the definition above.
  • -
  • Functional Type is a type describing a function; it is not a type in the sense of the definition above. Initially, we ignore the existence of functional types and describe only the data types; however, in reality, functional types will later be implemented in some extension of this system using the so-called temporary combinators.
  • -
-

Combinators, Constructors, Composite Data Types

-
    -
  • -

    Combinator is a function that takes arguments of certain types and returns a value of some other type. We normally look at combinators whose argument and result types are data types (rather than functional types).

    -
  • -
  • -

    Arity (of combinator) is a non-negative integer, the number of combinator arguments.

    -
  • -
  • -

    Combinator identifier is an identifier beginning with a lowercase Roman letter that uniquely identifies a combinator.

    -
  • -
  • -

    Combinator number or combinator name is a 32-bit number (i.e., an element of A) that uniquely identifies a combinator. Most often, it is CRC32 of the string containing the combinator description without the final semicolon, and with one space between contiguous lexemes. This always falls in the range from 0x01000000 to 0xffffff00. The highest 256 values are reserved for the so-called temporal-logic combinators used to transmit functions. We frequently denote as combinator the combinator name with single quotes: ‘combinator’.

    -
  • -
  • -

    Combinator description is a string of format combinator_name type_arg_1 ... type_arg_N = type_res; where N stands for the arity of the combinator, type_arg_i is the type of the i-th argument (or rather, a string with the combinator name), and type_res is the combinator value type.

    -
  • -
  • -

    Constructor is a combinator that cannot be computed (reduced). This is used to represent composite data types. For example, combinator ‘int_tree’ with description int_tree IntTree int IntTree = IntTree, alongside combinator empty_tree = IntTree, may be used to define a composite data type called “IntTree” that takes on values in the form of binary trees with integers as nodes.

    -
  • -
  • -

    Function (functional combinator) is a combinator which may be computed (reduced) on condition that the requisite number of arguments of requisite types are provided. The result of the computation is an expression consisting of constructors and base type values only.

    -
  • -
  • -

    Normal form is an expression consisting only of constructors and base type values; that which is normally the result of computing a function.

    -
  • -
  • -

    Type identifier is an identifier that normally starts with a capital letter in Roman script and uniquely identifies the type.

    -
  • -
  • -

    Type number or type name is a 32-bit number that uniquely identifies a type; it normally is the sum of the CRC32 values of the descriptions of the type constructors.

    -
  • -
  • -

    Description of (composite) Type T is a collection of the descriptions of all constructors that take on Type T values. This is normally written as text with each string containing the description of a single constructor. Here is a description of Type ‘IntTree’, for example:

    -

    int_tree IntTree int IntTree = IntTree; -empty_tree = IntTree;

    -
  • -
  • -

    Polymorphic type is a type whose description contains parameters (type variables) in lieu of actual types; approximately, what would be a template in C++. Here is a description of Type List alpha where List is a polymorphic type of arity 1 (i. e., dependent on a single argument), and alpha is a type variable which appears as the constructor’s optional parameter (in curly braces):

    -

    cons {alpha:Type} alpha (List alpha) = List alpha; -nil {alpha:Type} = List alpha;

    -
  • -
  • -

    Value of (composite) Type T is any sequence from A* in the format constr_num arg1 ... argN, where constr_num is the index number of some Constructor C which takes on values of Type T, and arg_i is a value of Type T_i which is the type of the i-th argument to Constructor C. For example, let Combinator int_tree have the index number 17, whereas Combinator empty_tree has the index number 239. Then, the value of Type IntTree is, for example, 17 17 239 1 239 2 239 which is more conveniently written as 'int_tree' 'int_tree' 'empty_tree' 1 'empty_tree' 2 ‘empty_tree’. From the standpoint of a high-level language, this is int_tree (int_tree (empty_tree) 1 (empty_tree)) 2 (empty_tree): IntTree.

    -
  • -
  • -

    Schema is a collection of all the (composite) data type descriptions. This is used to define some agreed-to system of types.

    -
  • -
-

Boxed and Bare Types

-
    -
  • Boxed type is a type any value of which starts with the constructor number. Since every constructor has a uniquely determined value type, the first number in any boxed type value uniquely defines its type. This guarantees that the various boxed types in totality make up a coordinated system of types. A boxed type identifier is always capitalized.
  • -
  • Bare type is a type whose values do not contain a constructor number, which is implied instead. A bare type identifier always coincides with the name of the implied constructor (and therefore, begins with a lowercase letter) which may be padded at the front by the percentage sign (%). In addition, if X is a boxed type with no more than a single constructor, then %X refers to the corresponding bare type. The values of a bare type are identical with the set of number sequences obtained by dropping the first number (i. e., the external constructor index number) from the set of values of the corresponding boxed type (which is the result type of the selected constructor), starting with the selected constructor index number. For example, 3 4 is a value of the int_couple bare type, defined using int_couple int int = IntCouple. The corresponding boxed type is IntCouple; if 404 is the constructor index number for int_couple, then 404 3 4 is the value for the IntCouple boxed type which corresponds to the value of the bare type int_couple (also known as %int_couple and %IntCouple; the latter form is conceptually preferable but longer).
  • -
-

Conceptually, only boxed types should be used everywhere. However, for speed and compactness, bare types have to be used (for instance, an array of 10,000 bare int values is 40,000 bytes long, whereas boxed Int values take up twice as much space; therefore, when transmitting a large array of integer identifiers, say, it is more efficient to use the Vector int type rather than Vector Int). In addition, all base types (int, long, double, string) are bare.

-

If a boxed type is polymorphic of type arity r, this is also true of any derived bare type. In other words, if one were to define intCouple {alpha:Type} int alpha = IntCouple alpha, then, thereafter, intCouple as an identifier would also be a polymorphic type of arity 1 in combinator (and consequently, in constructor and type) descriptions. The notations intCouple X, %(IntCouple X), and %IntCouple X are equivalent.

-

Base Types

-

Base types exist both as bare (int, long, double, string) and as boxed (Int, Long, Double, String) versions. Their constructor identifiers coincide with the names of the relevant bare types. Their pseudodescriptions have the following appearance:

-
int ? = Int;
-long ? = Long;
-double ? = Double;
-string ? = String;
-

Consequently, the int constructor index number, for example, is the CRC32 of the string "int ? = Int".

-

The values of bare type int are exactly all the single-element sequences, i. e. numbers between -2^31 and 2^31-1 represent themselves in this case. Values of type long are two-element sequences that are 64-bit signed numbers (little endian again). Values of type double, again, are two-element sequences containing 64-bit real numbers in a standard double format. And finally, the values of type string look differently depending on the length L of the string being serialized:

-
    -
  • If L <= 253, the serialization contains one byte with the value of L, then L bytes of the string followed by 0 to 3 characters containing 0, such that the overall length of the value be divisible by 4, whereupon all of this is interpreted as a sequence of int(L/4)+1 32-bit numbers.
  • -
  • If L >= 254, the serialization contains byte 254, followed by 3 bytes with the string length L, followed by L bytes of the string, further followed by 0 to 3 null padding bytes.
  • -
-

Object Pseudotype

-

The Object pseudotype is a “type” which can take on values that belong to any boxed type in the schema. This helps quickly define such types as list of random items without using polymorphic types. It is best not to abuse this capability since it results in the use of dynamic typing. Nonetheless, it is hard to imagine the data structures that we know from PHP and JSON without using the Object pseudotype.

-

It is recommended to use TypedObject instead whenever possible:

-
object X:Type value:X = TypedObject;
-

Built-In Composite Types: Vectors and Associative Arrays

-

The Vector t polymorphic pseudotype is a “type” whose value is a sequence of values of any type t, either boxed or bare.

-
vector {t:Type} # [ t ] = Vector t;
-

Serialization always uses the same constructor “vector” (const 0x1cb5c415 = crc32("vector t:Type # [ t ] = Vector t”) that is not dependent on the specific value of the variable of type t. The value of the Vector t type is the index number of the relevant constructor number followed by N, the number of elements in the vector, and then by N values of type t. The value of the optional parameter t is not involved in the serialization since it is derived from the result type (always known prior to deserialization).

-

Polymorphic pseudotypes IntHash t and StrHash t are associative arrays mapping integer and string keys to values of type t. They are, in fact, vectors containing bare 2-tuples (int, t) or (string, t):

-
coupleInt {t:Type} int t = CoupleInt t;
-intHash {t:Type} (vector %(CoupleInt t)) = IntHash t;
-coupleStr {t:Type} string t = CoupleStr t;
-strHash {t:Type} (vector %(CoupleStr t)) = StrHash t;
-

The percentage sign, in this case, means that a bare type that corresponds to the boxed type in parentheses is taken; the boxed type in question must have no more than a single constructor, whatever the values of the parameters.

-

The keys may be sorted or be in some other order (as in PHP arrays). For associative arrays with sorted keys, the IntSortedHash or StrSortedHash alias is used:

-
intSortedHash {t:Type} (intHash t) = IntSortedHash t;
-strSortedHash {t:Type} (strHash t) = StrSortedHash t;
-

Polymorphic Type Constructors

-

The constructor of a polymorphic type does not depend on the specific types to which the polymorphic type is applied. When it is computed, optional parameters (normally containing type variables and placed in curly braces) cease to be optional (the curly braces are removed), and, in addition to that, all parenthesis are also removed. Therefore,

-
vector {t:Type} # [ t ] = Vector t;
-

corresponds to the constructor number crc32("vector t:Type # [ t ] = Vector t") = 0x1cb5c415. During (de)serialization, the specific values of the optional variable t are derived from the result type (i. e. the object being serialized or deserialized) that is always known, and are never serialized explicitly.

-

Previously, it had to be known which specific variable types each polymorphic type will apply to. To accomplish this, the type system used strings of the form

-
polymorphic_type_name type_1 ... type_N;
-

For example,

-
Vector int;
-Vector string;
-Vector Object;
-

Now they are ignored.

-

See also polymorphism in TL.

-

In this case, the Object pseudotype permits using Vector Object to store lists of anything (the values of any boxed types). Since bare types are efficient when short, in practice it is unlikely that cases more complex than the ones cited above will be required.

-

Field Names

-

Let us say that we need to represent users as triplets containing one integer (user ID) and two strings (first and last names). The requisite data structure is the triplet int, string, string which may be declared as follows:

-
user int string string = User;
-

On the other hand, a group may be described by a similar triplet consisting of a group ID, its name, and description:

-
group int string string = Group;
-

For the difference between User and Group to be clear, it is convenient to assign names to some or all of the fields:

-
user id:int first_name:string last_name:string = User;
-group id:int title:string description:string = Group;
-

If the User type needs to be extended at a later time by having records with some additional field added to it, it could be accomplished as follows:

-
userv2 id:int unread_messages:int first_name:string last_name:string in_groups:vector int = User;
-

Aside from other things, this approach helps define correct mappings between fields that belong to different constructors of the same type, convert between them as well as convert type values into an associative array with string keys (field names, if defined, are natural choices for such keys).

-

TL Language

-

See TL Language

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/mtproto/service_messages.html b/data/core.telegram.org/mtproto/service_messages.html deleted file mode 100644 index 25e631fce7..0000000000 --- a/data/core.telegram.org/mtproto/service_messages.html +++ /dev/null @@ -1,195 +0,0 @@ - - - - - Service Messages - - - - - - - - - - - - - -
- -
-
-
- -

Service Messages

- -

Response to an RPC query

-

A response to an RPC query is normally wrapped as follows:

-
rpc_result#f35c6d01 req_msg_id:long result:Object = RpcResult;
-

Here req_msg_id is the identifier of the message sent by the other party and containing an RPC query. This way, the recipient knows that the result is a response to the specific RPC query in question. -At the same time, this response serves as acknowledgment of the other party’s receipt of the req_msg_id message.

-

Note that the response to an RPC query must also be acknowledged. Most frequently, this coincides with the transmission of the next message (which may have a container attached to it carrying a service message with the acknowledgment).

-

RPC Error

-

The result field returned in response to any RPC query may also contain an error message in the following format:

-
rpc_error#2144ca19 error_code:int error_message:string = RpcError;
-

Cancellation of an RPC Query

-

In certain situations, the client does not want to receive a response to an already transmitted RPC query, for example because the response turns out to be long and the client has decided to do without it because of insufficient link capacity. Simply interrupting the TCP connection will not have any effect because the server would re-send the missing response at the first opportunity. Therefore, the client needs a way to cancel receipt of the RPC response message, actually acknowledging its receipt prior to it being in fact received, which will settle the server down and prevent it from re-sending the response. However, the client does not know the RPC response’s msg_id prior to receiving the response; the only thing it knows is the req_msg_id. i. e. the msg_id of the relevant RPC query. Therefore, a special query is used:

-
rpc_drop_answer#58e4a740 req_msg_id:long = RpcDropAnswer;
-

The response to this query returns as one of the following messages wrapped in rpc_result and requiring an acknowledgment:

-
rpc_answer_unknown#5e2ad36e = RpcDropAnswer;
-rpc_answer_dropped_running#cd78e586 = RpcDropAnswer;
-rpc_answer_dropped#a43ad8b7 msg_id:long seq_no:int bytes:int = RpcDropAnswer;
-

The first version of the response is used if the server remembers nothing of the incoming req_msg_id (if it has already been responded to, for example). The second version is used if the response was canceled while the RPC query was being processed (where the RPC query itself was still fully processed); in this case, the same rpc_answer_dropped_running is also returned in response to the original query, and both of these responses require an acknowledgment from the client. The final version means that the RPC response was removed from the server’s outgoing queue, and its msg_id, seq_no, and length in bytes are transmitted to the client.

-

Note that rpc_answer_dropped_running and rpc_answer_dropped serve as acknowledgments of the server’s receipt of the original query (the same one, the response to which we wish to forget). In addition, same as for any RPC queries, any response to rpc_drop_answer is an acknowledgment for rpc_drop_answer itself.

-

As an alternative to using rpc_drop_answer, a new session may be created after the connection is reset and the old session is removed through destroy_session.

-

Messages associated with querying, changing, and receiving the status of other messages

-

See Mobile Protocol: Service Messages about Messages

-

Request for several future salts

-

The client may at any time request from the server several (between 1 and 64) future server salts together with their validity periods. Having stored them in persistent memory, the client may use them to send messages in the future even if it changes sessions (a server salt is attached to the authorization key rather than being session-specific).

-
get_future_salts#b921bd04 num:int = FutureSalts;
-future_salt#0949d9dc valid_since:int valid_until:int salt:long = FutureSalt;
-future_salts#ae500895 req_msg_id:long now:int salts:vector<future_salt> = FutureSalts;
-

The client must check to see that the response’s req_msg_id in fact coincides with msg_id of the query for get_future_salts. The server returns a maximum of num future server salts (may return fewer). The response serves as the acknowledgment of the query and does not require an acknowledgment itself.

-

Ping Messages (PING/PONG)

-
ping#7abe77ec ping_id:long = Pong;
-

A response is usually returned to the same connection:

-
pong#347773c5 msg_id:long ping_id:long = Pong;
-

These messages do not require acknowledgments. A pong is transmitted only in response to a ping while a ping can be initiated by either side.

-

Deferred Connection Closure + PING

-
ping_delay_disconnect#f3427b8c ping_id:long disconnect_delay:int = Pong;
-

Works like ping. In addition, after this is received, the server starts a timer which will close the current connection disconnect_delay seconds later unless it receives a new message of the same type which automatically resets all previous timers. If the client sends these pings once every 60 seconds, for example, it may set disconnect_delay equal to 75 seconds.

-

Request to Destroy Session

-

Used by the client to notify the server that it may forget the data from a different session belonging to the same user (i. e. with the same auth_key_id). The result of this being applied to the current session is undefined.

-
destroy_session#e7512126 session_id:long = DestroySessionRes;
-destroy_session_ok#e22045fc session_id:long = DestroySessionRes;
-destroy_session_none#62d350c9 session_id:long = DestroySessionRes;
-

New Session Creation Notification

-

The server notifies the client that a new session (from the server’s standpoint) had to be created to handle a client message. If, after this, the server receives a message with an even smaller msg_id within the same session, a similar notification will be generated for this msg_id as well. No such notifications are generated for high msg_id values.

-
new_session_created#9ec20908 first_msg_id:long unique_id:long server_salt:long = NewSession
-

The unique_id parameter is generated by the server every time a session is (re-)created.

-

This notification must be acknowledged by the client. It is necessary, for instance, for the client to understand that there is, in fact, a “gap” in the stream of long poll notifications received from the server (the user may have failed to receive notifications during some period of time).

-

Notice that the server may unilaterally destroy (close) any existing client sessions with all pending messages and notifications, without sending any notifications. This happens, for example, if the session is inactive for a long time, and the server runs out of memory. If the client at some point decides to send new messages to the server using the old session, already forgotten by the server, such a "new session created" notification will be generated. The client is expected to handle such situations gracefully.

-

Containers

-

Containers are messages containing several other messages. Used for the ability to transmit several RPC queries and/or service messages at the same time, using HTTP or even TCP or UDP protocol. A container may only be accepted or rejected by the other party as a whole.

-

Simple Container

-

A simple container carries several messages as follows:

-
msg_container#73f1f8dc messages:vector message = MessageContainer;
-

Here message refers to any message together with its length and msg_id:

-
message msg_id:long seqno:int bytes:int body:Object = Message;
-

bytes is the number of bytes in the body serialization. -All messages in a container must have msg_id lower than that of the container itself. A container does not require an acknowledgment and may not carry other simple containers. When messages are re-sent, they may be combined into a container in a different manner or sent individually.

-

MTProto container payloads have a limit of 2^15 bytes or 1020 messages, whichever limit is reached first.
-Clients should group acknowledgments, state requests and message resend requests into three separate msgs_ack, msgs_state_req, msg_resend_req service messages with at most 8192 IDs each; these three messages (+http_wait) will not be included in the 1020 message limit.

-

Empty containers are also allowed. They are used by the server, for example, to respond to an HTTP request when the timeout specified in http_wait expires, and there are no messages to transmit.

-

Example implementation.

-

Message Copies

-

In some situations, an old message with a msg_id that is no longer valid needs to be re-sent. Then, it is wrapped in a copy container:

-
msg_copy#e06046b2 orig_message:Message = MessageCopy;
-

Once received, the message is processed as if the wrapper were not there. However, if it is known for certain that the message orig_message.msg_id was received, then the new message is not processed (while at the same time, it and orig_message.msg_id are acknowledged). The value of orig_message.msg_id must be lower than the container’s msg_id.

-

This is not used at this time, because an old message can be wrapped in a simple container with the same result.

-

Packed Object

-

Used to replace any other object (or rather, a serialization thereof) with its archived (gzipped) representation:

-
gzip_packed#3072cfa1 packed_data:string = Object;
-

At the present time, it is supported in the body of an RPC response (i.e., as result in rpc_result) and generated by the server for a limited number of high-level queries. In addition, it may be used to transmit non-service messages (i. e. RPC queries) from client to server.

-

HTTP Wait/Long Poll

-

The following special service query not requiring an acknowledgement (which must be transmitted only through an HTTP connection) is used to enable the server to send messages in the future to the client using HTTP protocol:

-
http_wait#9299359f max_delay:int wait_after:int max_wait:int = HttpWait;
-

When such a message (or a container carrying such a message) is received, the server either waits max_delay milliseconds, whereupon it forwards all the messages that it is holding on to the client if there is at least one message queued in session (if needed, by placing them into a container to which acknowledgments may also be added); or else waits no more than max_wait milliseconds until such a message is available. If a message never appears, an empty container is transmitted.

-

The max_delay parameter denotes the maximum number of milliseconds that has elapsed between the first message for this session and the transmission of an HTTP response. The wait_after parameter works as follows: after the receipt of the latest message for a particular session, the server waits another wait_after milliseconds in case there are more messages. If there are no additional messages, the result is transmitted (a container with all the messages). If more messages appear, the wait_after timer is reset.

-

At the same time, the max_delay parameter has higher priority than wait_after, and max_wait has higher priority than max_delay.

-

This message does not require a response or an acknowledgement. If the container transmitted over HTTP carries several such messages, the behavior is undefined (in fact, the latest parameter will be used).

-

If no http_wait is present in container, default values max_delay=0 (milliseconds), wait_after=0 (milliseconds), and max_wait=25000 (milliseconds) are used.

-

If the client’s ping of the server takes a long time, it may make sense to set max_delay to a value that is comparable in magnitude to ping time.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/mtproto/service_messages_about_messages.html b/data/core.telegram.org/mtproto/service_messages_about_messages.html deleted file mode 100644 index 3a8f6d4ba1..0000000000 --- a/data/core.telegram.org/mtproto/service_messages_about_messages.html +++ /dev/null @@ -1,185 +0,0 @@ - - - - - Service Messages about Messages - - - - - - - - - - - - - -
- -
-
-
- -

Service Messages about Messages

- -

Acknowledgment of Receipt

-

Receipt of virtually all messages (with the exception of some purely service ones as well as the plain-text messages used in the protocol for creating an authorization key) must be acknowledged. -This requires the use of the following service message (not requiring an acknowledgment):

-
msgs_ack#62d6b459 msg_ids:Vector<long> = MsgsAck;
-

A server usually acknowledges the receipt of a message from a client (normally, an RPC query) using an RPC response. If a response is a long time coming, a server may first send a receipt acknowledgment, and somewhat later, the RPC response itself.

-

A client normally acknowledges the receipt of a message from a server (usually, an RPC response) by adding an acknowledgment to the next RPC query if it is not transmitted too late (if it is generated, say, 60-120 seconds following the receipt of a message from the server). However, if for a long period of time there is no reason to send messages to the server or if there is a large number of unacknowledged messages from the server (say, over 16), the client transmits a stand-alone acknowledgment.

-

Max 8192 IDs are allowed per constructor.

-

Notice of Ignored Error Message

-

In certain cases, a server may notify a client that its incoming message was ignored for whatever reason. Note that such a notification cannot be generated unless a message is correctly decoded by the server.

-
bad_msg_notification#a7eff811 bad_msg_id:long bad_msg_seqno:int error_code:int = BadMsgNotification;
-bad_server_salt#edab447b bad_msg_id:long bad_msg_seqno:int error_code:int new_server_salt:long = BadMsgNotification;
-

Here, error_code can also take on the following values:

-
    -
  • 16: msg_id too low (most likely, client time is wrong; it would be worthwhile to synchronize it using msg_id notifications and re-send the original message with the “correct” msg_id or wrap it in a container with a new msg_id if the original message had waited too long on the client to be transmitted)
  • -
  • 17: msg_id too high (similar to the previous case, the client time has to be synchronized, and the message re-sent with the correct msg_id)
  • -
  • 18: incorrect two lower order msg_id bits (the server expects client message msg_id to be divisible by 4)
  • -
  • 19: container msg_id is the same as msg_id of a previously received message (this must never happen)
  • -
  • 20: message too old, and it cannot be verified whether the server has received a message with this msg_id or not
  • -
  • 32: msg_seqno too low (the server has already received a message with a lower msg_id but with either a higher or an equal and odd seqno)
  • -
  • 33: msg_seqno too high (similarly, there is a message with a higher msg_id but with either a lower or an equal and odd seqno)
  • -
  • 34: an even msg_seqno expected (irrelevant message), but odd received
  • -
  • 35: odd msg_seqno expected (relevant message), but even received
  • -
  • 48: incorrect server salt (in this case, the bad_server_salt response is received with the correct salt, and the message is to be re-sent with it)
  • -
  • 64: invalid container.
  • -
-

The intention is that error_code values are grouped (error_code >> 4): for example, the codes 0x40 - 0x4f correspond to errors in container decomposition.

-

Notifications of an ignored message do not require acknowledgment (i.e., are irrelevant).

-

Important: if server_salt has changed on the server or if client time is incorrect, any query will result in a notification in the above format. The client must check that it has, in fact, recently sent a message with the specified msg_id, and if that is the case, update its time correction value (the difference between the client’s and the server’s clocks) and the server salt based on msg_id and the server_salt notification, so as to use these to (re)send future messages. In the meantime, the original message (the one that caused the error message to be returned) must also be re-sent with a better msg_id and/or server_salt.

-

In addition, the client can update the server_salt value used to send messages to the server, based on the values of RPC responses or containers carrying an RPC response, provided that this RPC response is actually a match for the query sent recently. (If there is doubt, it is best not to update since there is risk of a replay attack).

-

Request for Message Status Information

-

If either party has not received information on the status of its outgoing messages for a while, it may explicitly request it from the other party:

-
msgs_state_req#da69fb52 msg_ids:Vector long = MsgsStateReq;
-

Max 8192 IDs are allowed per constructor.

-

The response to the query contains the following information:

-

Informational Message regarding Status of Messages

-
msgs_state_info#04deb57d req_msg_id:long info:string = MsgsStateInfo;
-

Here, info is a string that contains exactly one byte of message status for each message from the incoming msg_ids list:

-
    -
  • 1 = nothing is known about the message (msg_id too low, the other party may have forgotten it)
  • -
  • 2 = message not received (msg_id falls within the range of stored identifiers; however, the other party has certainly not received a message like that)
  • -
  • 3 = message not received (msg_id too high; however, the other party has certainly not received it yet)
  • -
  • 4 = message received (note that this response is also at the same time a receipt acknowledgment)
  • -
  • +8 = message already acknowledged
  • -
  • +16 = message not requiring acknowledgment
  • -
  • +32 = RPC query contained in message being processed or processing already complete
  • -
  • +64 = content-related response to message already generated
  • -
  • +128 = other party knows for a fact that message is already received
  • -
-

This response does not require an acknowledgment. It is an acknowledgment of the relevant msgs_state_req, in and of itself.

-

Note that if it turns out suddenly that the other party is missing a message that appears to have been sent to it, the message must not be re-sent on its own with the same msg_id. Instead, it can be either wrapped in a container, or the status of the message can be checked using msgs_state_req and if the message wasn't received, then it must be re-sent with a new msg_id.

-

Voluntary Communication of Status of Messages

-

Either party may voluntarily inform the other party of the status of the messages transmitted by the other party.

-
msgs_all_info#8cc0d131 msg_ids:Vector long info:string = MsgsAllInfo
-

All message codes known to this party are enumerated, with the exception of those for which the +128 and the +16 flags are set. However, if the +32 flag is set but not +64, then the message status will still be communicated.

-

This message does not require an acknowledgment.

-

Extended Voluntary Communication of Status of One Message

-

Normally used by the server to respond to the receipt of a duplicate msg_id, especially if a response to the message has already been generated and the response is large. If the response is small, the server may re-send the answer itself instead. This message can also be used as a notification instead of resending a large message.

-
msg_detailed_info#276d3ec6 msg_id:long answer_msg_id:long bytes:int status:int = MsgDetailedInfo;
-msg_new_detailed_info#809db6df answer_msg_id:long bytes:int status:int = MsgDetailedInfo;
-

The second version is used to notify of messages that were created on the server not in response to an RPC query (such as notifications of new messages) and were transmitted to the client some time ago, but not acknowledged.

-

Currently, status is always zero. This may change in future.

-

This message does not require an acknowledgment.

-

Explicit Request to Re-Send Messages

-
msg_resend_req#7d861a08 msg_ids:Vector long = MsgResendReq;
-

The remote party immediately responds by re-sending the requested messages, normally using the same connection that was used to transmit the query. If at least one message with requested msg_id does not exist or has already been forgotten, or has been sent by the requesting party (known from parity), MsgsStateInfo is returned for all messages requested as if the MsgResendReq query had been a MsgsStateReq query as well.
-Max 8192 IDs are allowed per constructor.

-

Explicit Request to Re-Send Answers

-
msg_resend_ans_req#8610baeb msg_ids:Vector long = MsgResendReq;
-

The remote party immediately responds by re-sending answers to the requested messages, normally using the same connection that was used to transmit the query. MsgsStateInfo is returned for all messages requested as if the MsgResendReq query had been a MsgsStateReq query as well.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/mtproto_v1.html b/data/core.telegram.org/mtproto_v1.html deleted file mode 100644 index e3cdb7c384..0000000000 --- a/data/core.telegram.org/mtproto_v1.html +++ /dev/null @@ -1,229 +0,0 @@ - - - - - MTProto Mobile Protocol v.1.0 (DEPRECATED) - - - - - - - - - - - - - -
- -
-
-
-
-

MTProto Mobile Protocol v.1.0 (DEPRECATED)

- -
-

This document describes MTProto v1.0, its status is DEPRECATED.
For information on encryption used in up-to-date Telegram clients, kindly see this document.

-
-

Related articles

-

-
-

This page deals with the basic layer of MTProto encryption used for Cloud chats (server-client encryption). See also:

- -

General Description

-

The protocol is designed for access to a server API from applications running on mobile devices. It must be emphasized that a web browser is not such an application.

-

The protocol is subdivided into three virtually independent components:

-
    -
  • High-level component (API query language): defines the method whereby API queries and responses are converted to binary messages.
  • -
  • Cryptographic (authorization) layer: defines the method by which messages are encrypted prior to being transmitted through the transport protocol.
  • -
  • Transport component: defines the method for the client and the server to transmit messages over some other existing network protocol (such as, http, https, tcp, udp).
  • -
- - -
-

Got questions about this setup? — Check out the Advanced FAQ!

-
-
Note 1
-

Each plaintext message to be encrypted in MTProto always contains the following data to be checked upon decryption in order to make the system robust against known problems with the components:

-
    -
  • server salt (64-Bit)
  • -
  • session id
  • -
  • message sequence number
  • -
  • message length
  • -
  • time
  • -
-
Note 2
-

See additional comments on our use of IGE, SHA-1 and message authentication.

-
Note 3
-

Telegram's End-to-end encrypted Secret Chats are using an additional layer of encryption on top of the described above. See Secret Chats, End-to-End encryption for details.

-

Brief Component Summary

-

High-Level Component (RPC Query Language/API)

-

From the standpoint of the high-level component, the client and the server exchange messages inside a session. The session is attached to the client device (the application, to be more exact) rather than a specific http/https/tcp connection. In addition, each session is attached to a user key ID by which authorization is actually accomplished.

-

Several connections to a server may be open; messages may be sent in either direction through any of the connections (a response to a query is not necessarily returned through the same connection that carried the original query, although most often, that is the case; however, in no case can a message be returned through a connection belonging to a different session). When the UDP protocol is used, a response might be returned by a different IP address than the one to which the query had been sent.

-

There are several types of messages:

-
    -
  • RPC calls (client to server): calls to API methods
  • -
  • RPC responses (server to client): results of RPC calls
  • -
  • Message received acknowledgment (or rather, notification of status of a set of messages)
  • -
  • Message status query
  • -
  • Multipart message or container (a container that holds several messages; needed to send several RPC calls at once over an HTTP connection, for example; also, a container may support gzip).
  • -
-

From the standpoint of lower level protocols, a message is a binary data stream aligned along a 4 or 16-byte boundary. The first several fields in the message are fixed and are used by the cryptographic/authorization system.

-

Each message, either individual or inside a container, consists of a message identifier (64 bits, see below), a message sequence number within a session (32 bits), the length (of the message body in bytes; 32 bits), and a body (any size which is a multiple of 4 bytes). In addition, when a container or a single message is sent, an internal header is added at the top (see below), then the entire message is encrypted, and an external header is placed at the top of the message (a 64-bit key identifier and a 128-bit message key).

-

A message body normally consists of a 32-bit message type followed by type-dependent parameters. In particular, each RPC function has a corresponding message type. For more detail, see Binary Data Serialization, Mobile Protocol: Service Messages.

-

All numbers are written as little endian. However, very large numbers (2048-bit) used in RSA and DH are written in the big endian format because that is what the OpenSSL library does.

-

Authorization and Encryption

-

Prior to a message (or a multipart message) being transmitted over a network using a transport protocol, it is encrypted in a certain way, and an external header is added at the top of the message which is: a 64-bit key identifier (that uniquely identifies an authorization key for the server as well as the user) and a 128-bit message key. A user key together with the message key defines an actual 256-bit key which is what encrypts the message using AES-256 encryption. Note that the initial part of the message to be encrypted contains variable data (session, message ID, sequence number, server salt) that obviously influences the message key (and thus the AES key and iv). The message key is defined as the 128 lower-order bits of the SHA1 of the message body (including session, message ID, etc.). Multipart messages are encrypted as a single message.

-

For a technical specification, see Mobile Protocol: Detailed Description
The first thing a client application must do is create an authorization key which is normally generated when it is first run and almost never changes.

-

The protocol’s principal drawback is that an intruder passively intercepting messages and then somehow appropriating the authorization key (for example, by stealing a device) will be able to decrypt all the intercepted messages post factum. This probably is not too much of a problem (by stealing a device, one could also gain access to all the information cached on the device without decrypting anything); however, the following steps could be taken to overcome this weakness:

-
    -
  • Session keys generated using the Diffie-Hellman protocol and used in conjunction with the authorization and the message keys to select AES parameters. To create these, the first thing a client must do after creating a new session is send a special RPC query to the server (“generate session key”) to which the server will respond, whereupon all subsequent messages within the session are encrypted using the session key as well.
  • -
  • Protecting the key stored on the client device with a (text) password; this password is never stored in memory and is entered by a user when starting the application or more frequently (depending on application settings).
  • -
  • Data stored (cached) on the user device can also be protected by encryption using an authorization key which, in turn, is to be password-protected. Then, a password will be required to gain access even to those data.
  • -
-

Time Synchronization

-

If client time diverges widely from server time, a server may start ignoring client messages, or vice versa, because of an invalid message identifier (which is closely related to creation time). Under these circumstances, the server will send the client a special message containing the correct time and a certain 128-bit salt (either explicitly provided by the client in a special RPC synchronization request or equal to the key of the latest message received from the client during the current session). This message could be the first one in a container that includes other messages (if the time discrepancy is significant but does not as yet result in the client’s messages being ignored).

-

Having received such a message or a container holding it, the client first performs a time synchronization (in effect, simply storing the difference between the server’s time and its own to be able to compute the “correct” time in the future) and then verifies that the message identifiers for correctness.

-

Where a correction has been neglected, the client will have to generate a new session to assure the monotonicity of message identifiers.

-

Transport

-

Enables the delivery of encrypted containers together with the external header (hereinafter, Payload) from client to server and back. There are three types of transport:

-
    -
  • HTTP
  • -
  • TCP
  • -
  • UDP
  • -
-

We shall examine the first two types.

-

HTTP Transport

-

Implemented over HTTP/1.1 (with keepalive) running over the traditional TCP Port 80. HTTPS is not used; the above encryption method is used instead.

-

An HTTP connection is attached to a session (or rather, to session + key identifier) specified in the most recent user query received; normally, the session is the same in all queries, but crafty HTTP proxies may corrupt that. A server may not return a message into an HTTP connection unless it belongs to the same session, and unless it is the server’s turn (an HTTP request had been received from the client to which a response has not been sent yet).

-

The overall arrangement is as follows. The client opens one or more keepalive HTTP connections to the server. If one or more messages need to be sent, they are made into a payload which is followed by a POST request to the URL/api to which the payload is transmitted as data. In addition, Content-Length, Keepalive, and Host are valid HTTP headers.

-

Having received the query, the server may either wait a little while (if the query requires a response following a short timeout) or immediately return a dummy response (only acknowledging the receipt of the container). In any case, the response may contain any number of messages. The server may at the same time send out any other messages it might be holding for the session.

-

In addition, there exists a special long poll RPC query (valid for HTTP connections only) which transmits maximum timeout T. If the server has messages for the session, they are returned immediately; otherwise, a wait state is entered until such time as the server has a message for the client or T seconds have elapsed. If no events occur in the span of T seconds, a dummy response is returned (special message).

-

If a server needs to send a message to a client, it checks for an HTTP connection that belongs to the required session and is in the “answering an HTTP request” state (including long poll) whereupon the message is added to the response container for the connection and sent to the user. In a typical case, there is some additional wait time (50 milliseconds) against the eventuality that the server will soon have more messages for the session.

-

If no suitable HTTP connection is available, the messages are placed in the current session’s send queue. However, they find their way there anyway until receipt is explicitly or indirectly confirmed by the client. For the HTTP protocol, sending the next query into the same HTTP connection is regarded as an implicit acknowledgment (not any more, the HTTP protocol also requires that explicit acknowledgments be sent); in other cases, the client must return an explicit acknowledgment within a reasonable time (it can be added to a container for the following request).

-

Important: if the acknowledgment fails to arrive on time, the message can be resent (possibly, in a different container). The parties must autonomously be ready for this and must store the identifiers of the most recent messages received (and ignore such duplicates rather than repeat actions). In order not to have the identifiers stored forever, there exist special garbage collection messages that take advantage of message identifier monotonicity.

-

If the send queue overflows or if messages stay in the queue for over 10 minutes, the server forgets them (or sends them to swap, no genius required). This may happen even faster, if the server is running out of buffer space (for example, because of serious network issues resulting in a large number of connections becoming severed).

-

TCP Transport

-

This is very similar to the HTTP transport. May also be implemented over Port 80 (to penetrate all firewalls) and even use the same server IP addresses. In this situation, the server understands whether HTTP or TCP protocol must be used for the connection, based on the first four incoming bytes (for HTTP, it is POST).

-

When a TCP connection is created, it is assigned to the session (and the authorization key) transmitted in the first user message, and subsequently used exclusively for this session (multiplexing arrangements are not allowed).

-

If a payload (packet) needs to be transmitted from server to client or from client to server, it is encapsulated as follows: 4 length bytes are added at the front (to include the length, the sequence number, and CRC32; always divisible by 4) and 4 bytes with the packet sequence number within this TCP connection (the first packet sent is numbered 0, the next one 1, etc.), and 4 CRC32 bytes at the end (length, sequence number, and payload together).

-

There is an abridged version of the same protocol: if the client sends 0xef as the first byte (important: only prior to the very first data packet), then packet length is encoded by a single byte (0x01..0x7e = data length divided by 4; or 0x7f followed by 3 length bytes (little endian) divided by 4) followed by the data themselves (sequence number and CRC32 not added). In this case, server responses look the same (the server does not send 0xefas the first byte).

-

In case 4-byte data alignment is needed, an intermediate version of the original protocol may be used: if the client sends 0xeeeeeeee as the first int (four bytes), then packet length is encoded always by four bytes as in the original version, but the sequence number and CRC32 are omitted, thus decreasing total packet size by 8 bytes.

-

The full, the intermediate and the abridged versions of the protocol have support for quick acknowledgment. In this case, the client sets the highest-order length bit in the query packet, and the server responds with a special 4 bytes as a separate packet. They are the 32 higher-order SHA1 bits of the encrypted portion of the packet with the most significant bit set to make clear that this is not the length of a regular server response packet; if the abridged version is used, bswap is applied to these four bytes.

-

There are no implicit acknowledgments for the TCP transport: all messages must be acknowledged explicitly. Most frequently, acknowledgments are placed in a container with the next query or response if it is transmitted in short order. For example, this is almost always the case for client messages containing RPC queries: the acknowledgment normally arrives with the RPC response.

-

In the event of an error, the server may send a packet whose payload consists of 4 bytes as the error code. For example, Error Code 403 corresponds to situations where the corresponding HTTP error would have been returned by the HTTP protocol.

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/passport.html b/data/core.telegram.org/passport.html deleted file mode 100644 index 2a175b5ae2..0000000000 --- a/data/core.telegram.org/passport.html +++ /dev/null @@ -1,690 +0,0 @@ - - - - - Telegram Passport Manual - - - - - - - - - - - - - -
- -
-
-
-
-

Telegram Passport Manual

- -
- -

Telegram Passport is a unified authorization method for services that require personal identification. Users can upload their documents once, then instantly share their data with services that require real-world ID (finance, ICOs, etc.). Telegram doesn't have access to the users' personal information thanks to end-to-end encryption.

-

Overview

-

From the perspective of a service that requires real-world ID, the process looks like this:

-
    -
  • A user presses "Log in with Telegram" on your website or in your app.
  • -
  • You request the data you need.
  • -
  • The user accepts your privacy policy and agrees to share their data.
  • -
  • The user's Telegram app downloads and decrypts the data you requested from the end-to-end encrypted storage on Telegram.
  • -
  • If some of the data you requested is missing, the user can add it to their Telegram Passport at this point.
  • -
  • The user's app encrypts the data with your public key and sends it to you.
  • -
  • You decrypt the data, check it for errors and re-request any missing or invalid information.
  • -
  • You sign the user up for your service. Tada!
  • -
-

Check out this example to see Telegram Passport in action.

-
-

To learn more about Telegram Passport from the perspective of a user, please see this blog post and the technical MTProto documentation. -See this page if you're interested in encryption algorithms used on Telegram's side.

-
-

Recent changes

-

August 25, 2018

-

Telegram Passport 1.1 (blog post)

-
    -
  • Added support for requesting several documents of one type. See the new objects PassportScope, PassportScopeElement, PassportScopeElementOneOfSeveral and PassportScopeElementOne.
  • -
  • Added support for middle names.
  • -
  • Added support for requesting certified English translations for documents (see Fields; new field translation also added to the SecureValue object). Note: Please only request translations after you have received a valid document that requires one.
  • -
  • Added support for requesting names in the language of the user's country of residence (if other than English). New fields first_name_native, last_name_native and middle_name_native added to the PersonalDetails object.
  • -
  • Replaced the payload parameter with the new parameter nonce, which serves the same function, to make the purpose more obvious (see Request Parameters and the Credentials object).
  • -
  • Updated the example page to support the new functionality.
  • -
-

Setting Up Telegram Passport

-

To integrate Telegram Passport into your login or verification flow, you need a working Telegram bot (see this page for information on how to get one).

-

To request data from Telegram Passport users, your bot will need to generate a pair of encryption keys.

-

Generating a private key

-

First, use a console to generate a private key:

-
openssl genrsa 2048 > private.key
-

WARNING: Keep your private key SECRET!

-

Generating your public key

-

Then use the console to print the corresponding public key:

-
openssl rsa -in private.key -pubout
-

Use the /setpublickey command with @BotFather to connect this public key with your bot.

-

Privacy Policy

-

Add a link to your Privacy Policy by using the /setprivacypolicy command. Users will see this link when offered to authorize you to access their data.

-

Requesting Information

-

SDK

-

To request information stored in a Telegram Passport, use one of these SDKs:

- -

Request Parameters

-

Use the following parameters to request information with the SDK:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParametersTypeRequired
bot_idIntegerYes
scopePassportScopeYes
public_keyStringYes
nonceStringYes
-

PassportScope

-

This object represents the data to be requested.

- - - - - - - - - - - - - - - - - - -
FieldTypeDescription
dataArray of PassportScopeElementList of requested elements, each type may be used only once in the entire array of PassportScopeElement objects
vIntegerScope version, must be 1
-

PassportScopeElement

-

This object represents a requested element, should be one of:

- -

PassportScopeElementOneOfSeveral

-

This object represents several elements one of which must be provided.

- - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
one_ofArray of PassportScopeElementOneList of elements one of which must be provided; must contain either several of “passport”, “driver_license”, “identity_card”, “internal_passport” or several of “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”
selfieBooleanOptional. Use this parameter if you want to request a selfie with the document from this list that the user chooses to upload.
translationBooleanOptional. Use this parameter if you want to request a translation of the document from this list that the user chooses to upload. Note: We suggest to only request translations after you have received a valid document that requires one.
-

PassportScopeElementOne

-

This object represents one particular element that must be provided. If no options are needed, String can be used instead of this object to specify the type of the element.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringElement type. One of "personal_details", "passport", "driver_license", "identity_card", "internal_passport", "address", "utility_bill", "bank_statement", "rental_agreement", "passport_registration", "temporary_registration", "phone_number", "email"
selfieBooleanOptional. Use this parameter if you want to request a selfie with the document as well. Available for "passport", "driver_license", "identity_card" and "internal_passport"
translationBooleanOptional. Use this parameter if you want to request a translation of the document as well. Available for "passport", "driver_license", "identity_card", "internal_passport", "utility_bill", "bank_statement", "rental_agreement", "passport_registration" and "temporary_registration". Note: We suggest to only request translations after you have received a valid document that requires one.
native_namesBooleanOptional. Use this parameter to request the first, last and middle name of the user in the language of the user's country of residence. Available for "personal_details"
-

You can also use the special type "id_document" as an alias for one of "passport", "driver_license", "identity_card" and the special type "address_document" as an alias for one of "utility_bill", "bank_statement", "rental_agreement". -So {"type":"id_document",selfie:true} is equal to {"one_of":["passport","driver_license","identity_card"],selfie:true}.

-

Fields

-

Your bot can request personal details, one or several types of identity document, residential address, one or several types of proof of address document, a phone number, or an email address. You can also request optional selfies with the document and certified English translations of the document. -This is just a list of data types that can be requested, and the encrypted objects that will contain such data.

-
-

Note: We suggest to only request English translations after you have received a valid document that requires one.

-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameKeyTypeDescription
personal_detailsdataPersonalDetailsPersonal Details
passportdataIdDocumentDataPassport
front_sidePassportFile
selfieOptional. PassportFile
translationOptional. Array of PassportFile
internal_passportdataIdDocumentDataInternal Passport
front_sidePassportFile
selfieOptional. PassportFile
translationOptional. Array of PassportFile
driver_licensedataIdDocumentDataDriver License
front_sidePassportFile
reverse_sidePassportFile
selfieOptional. PassportFile
translationOptional. Array of PassportFile
identity_carddataIdDocumentDataIdentity Card
front_sidePassportFile
reverse_sidePassportFile
selfieOptional. PassportFile
translationOptional. Array of PassportFile
addressdataResidentialAddressAddress
utility_billfilesArray of PassportFileUtility Bill
translationOptional. Array of PassportFile
bank_statementfilesArray of PassportFileBank Statement
translationOptional. Array of PassportFile
rental_agreementfilesArray of PassportFileRental Agreement
translationOptional. Array of PassportFile
passport_registrationfilesArray of PassportFileRegistration Page in the Internal Passport
translationOptional. Array of PassportFile
temporary_registrationfilesArray of PassportFileTemporary Registration
translationOptional. Array of PassportFile
phone_numberStringPhone number
emailStringEmail
-

PersonalDetails

-

This object represents personal details.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
first_nameStringFirst Name
last_nameStringLast Name
middle_nameStringOptional. Middle Name
birth_dateStringDate of birth in DD.MM.YYYY format
genderStringGender, male or female
country_codeStringCitizenship (ISO 3166-1 alpha-2 country code)
residence_country_codeStringCountry of residence (ISO 3166-1 alpha-2 country code)
first_name_nativeStringFirst Name in the language of the user's country of residence
last_name_nativeStringLast Name in the language of the user's country of residence
middle_name_nativeStringOptional. Middle Name in the language of the user's country of residence
-

ResidentialAddress

-

This object represents a residential address.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
street_line1StringFirst line for the address
street_line2StringOptional. Second line for the address
cityStringCity
stateStringOptional. State
country_codeStringISO 3166-1 alpha-2 country code
post_codeStringAddress post code
-

IdDocumentData

-

This object represents the data of an identity document.

- - - - - - - - - - - - - - - - - - -
FieldTypeDescription
document_noStringDocument number
expiry_dateStringOptional. Date of expiry, in DD.MM.YYYY format
-

PassportFile

-

This object represents a PassportFile related to a document. The file is up to 10MB in size and in the .jpg format.

-

Receiving information

-

When the user confirms your request by pressing the 'Authorize' button, the Bot API sends an Update with the field passport_data to the bot that contains encrypted Telegram Passport data.

-
-

Note that all base64-encoded fields should be decoded before use.

-
-

Decrypting data

-

To decrypt the received data, first, decrypt the credentials contained in EncryptedCredentials.

-
    -
  1. -

    Decrypt the credentials secret ( secret field in EncryptedCredentials) using your private key (set OAEP padding option, e.g. OPENSSL_PKCS1_OAEP_PADDING in PHP)

    -
  2. -
  3. -

    Use this secret and the credentials hash ( hash field in EncryptedCredentials) to calculate credentials_key and credentials_iv as described below:

    -
     credentials_secret_hash = SHA512( credentials_secret + credentials_hash )
    - credentials_key = slice( credentials_secret_hash, 0, 32 )
    - credentials_iv = slice( credentials_secret_hash, 32, 16 )
    -
  4. -
  5. -

    Decrypt the credentials data ( data field in EncryptedCredentials) by AES256-CBC using these credentials_key and credentials_iv. IMPORTANT: At this step, make sure that the credentials hash is equal to SHA256( credentials_data )

    -
  6. -
  7. -

    Credentials data is padded with 32 to 255 random padding bytes to make its length divisible by 16 bytes. The first byte contains the length of this padding (including this byte). Remove the padding to get the data.

    -
  8. -
-
-

Note that all hashes represent as raw binary data, not hexits

-
-

Credentials

-

Credentials is a JSON-serialized object.

- - - - - - - - - - - - - - - - - - -
FieldTypeDescription
secure_dataSecureDataCredentials for encrypted data
nonceStringBot-specified nonce
-

IMPORTANT: Make sure that the nonce is the same as was passed in the request.

-

SecureData

-

This object represents the credentials required to decrypt encrypted data. All fields are optional and depend on fields that were requested.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
personal_detailsSecureValueOptional. Credentials for encrypted personal details
passportSecureValueOptional. Credentials for encrypted passport
internal_passportSecureValueOptional. Credentials for encrypted internal passport
driver_licenseSecureValueOptional. Credentials for encrypted driver license
identity_cardSecureValueOptional. Credentials for encrypted ID card
addressSecureValueOptional. Credentials for encrypted residential address
utility_billSecureValueOptional. Credentials for encrypted utility bill
bank_statementSecureValueOptional. Credentials for encrypted bank statement
rental_agreementSecureValueOptional. Credentials for encrypted rental agreement
passport_registrationSecureValueOptional. Credentials for encrypted registration from internal passport
temporary_registrationSecureValueOptional. Credentials for encrypted temporary registration
-

SecureValue

-

This object represents the credentials required to decrypt encrypted values. All fields are optional and depend on the type of fields that were requested.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
dataDataCredentialsOptional. Credentials for encrypted Telegram Passport data. Available for "personal_details", "passport", "driver_license", "identity_card", "internal_passport" and "address" types.
front_sideFileCredentialsOptional. Credentials for an encrypted document's front side. Available for "passport", "driver_license", "identity_card" and "internal_passport".
reverse_sideFileCredentialsOptional. Credentials for an encrypted document's reverse side. Available for "driver_license" and "identity_card".
selfieFileCredentialsOptional. Credentials for an encrypted selfie of the user with a document. Available for "passport", "driver_license", "identity_card" and "internal_passport".
translationArray of FileCredentialsOptional. Credentials for an encrypted translation of the document. Available for "passport", "driver_license", "identity_card", "internal_passport", "utility_bill", "bank_statement", "rental_agreement", "passport_registration" and "temporary_registration".
filesArray of FileCredentialsOptional. Credentials for encrypted files. Available for "utility_bill", "bank_statement", "rental_agreement", "passport_registration" and "temporary_registration" types.
-

DataCredentials

-

These credentials can be used to decrypt encrypted data from the data field in EncryptedPassportElement.

- - - - - - - - - - - - - - - - - - -
FieldTypeDescription
data_hashStringChecksum of encrypted data
secretStringSecret of encrypted data
-
    -
  1. -

    To decrypt data, use the corresponding secret and data_hash from DataCredentials as described below:

    -
     data_secret_hash = SHA512( data_secret + data_hash )
    - data_key = slice( data_secret_hash, 0, 32 )
    - data_iv = slice( data_secret_hash, 32, 16 )
    -
  2. -
  3. -

    Use AES256-CBC with this data_key and data_iv to decrypt the data (the data field in EncryptedPassportElement). IMPORTANT: At this step, make sure that data_hash from the credentials is equal to SHA256( data ).

    -
  4. -
  5. -

    The data is padded with 32 to 255 random padding bytes to make its length divisible by 16 bytes. The first byte contains the length of the padding (including this byte). Remove padding to get the data.

    -
  6. -
  7. -

    The data is a JSON-serialized object of one of the following types: PersonalDetails, IdDocumentData, ResidentialAddress, depending on type.

    -
  8. -
-

FileCredentials

-

These credentials can be used to decrypt encrypted files from the front_side, reverse_side, selfie, files and translation fields in EncryptedPassportElement.

- - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_hashStringChecksum of encrypted file
secretStringSecret of encrypted file
-
    -
  1. -

    To decrypt the file, use the corresponding secret and file_hash from FileCredentials as described below:

    -
     file_secret_hash = SHA512( file_secret + file_hash )
    - file_key = slice( file_secret_hash, 0, 32 )
    - file_iv = slice( file_secret_hash, 32, 16 )
    -
  2. -
  3. -

    Download the encrypted file using the getFile method.

    -
  4. -
  5. -

    Use AES256-CBC with this file_key and file_iv to decrypt the content of the file. IMPORTANT: At this step, make sure that file_hash from the credentials is equal to SHA256( file_content ).

    -
  6. -
  7. -

    The content of the file is padded with 32 to 255 random padding bytes to make its length divisible by 16 bytes. The first byte contains the length of the padding (including that byte). Remove padding to get the file content.

    -
  8. -
-

Fixing errors

-

If the data you received contains errors, the bot can use the setPassportDataErrors method to inform the user and request information again. The user will not be able to resend the data, until all errors are fixed.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/passport/encryption.html b/data/core.telegram.org/passport/encryption.html deleted file mode 100644 index 86a46fec6c..0000000000 --- a/data/core.telegram.org/passport/encryption.html +++ /dev/null @@ -1,606 +0,0 @@ - - - - - Telegram Passport Encryption Details - - - - - - - - - - - - - -
- -
-
-
- -

Telegram Passport Encryption Details

- -
- -

Telegram Passport data is stored encrypted End-to-End which means that the Telegram server does not have access to the data and only functions as a storage for encrypted data it can't decipher. Encryption and decryption are handled exclusively by the Telegram clients, which are open source.

-

Overview

-

To encrypt each particular element of Telegram Passport, the client generates a random secret. The secret is a 32-byte number with the modulo 255 sum of bytes equal to 239. This secret is in turn encrypted with the passport_secret that is generated when the user creates their Telegram Passport. passport_secret is encrypted with the user's password and is stored encrypted in the Telegram Cloud.

-

Passport Secret

-

The passport secret is one of the secret parameters used to encrypt the data uploaded by the user to the Telegram Cloud.

-

When first setting up Telegram Passport it must be created, encrypted and uploaded as described in Passport Secret Encryption.

-

When using Telegram Passport normally, it must be downloaded and decrypted for use as described in Passport Secret Decryption.

-

The passport secret must also be downloaded, re-encrypted and re-uploaded as described in Passport Secret Encryption if a new, more secure encryption algorithm is defined in a newer version of Telegram or the 2FA password is updated.

-

Passport Secret Encryption

-

First of all, server-side passport parameters are fetched, schema:

-
account.password#185b184f flags:# has_recovery:flags.0?true has_secure_values:flags.1?true has_password:flags.2?true current_algo:flags.2?PasswordKdfAlgo srp_B:flags.2?bytes srp_id:flags.2?long hint:flags.3?string email_unconfirmed_pattern:flags.4?string new_algo:PasswordKdfAlgo new_secure_algo:SecurePasswordKdfAlgo secure_random:bytes pending_reset_date:flags.5?int = account.Password;
-
-securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;
-securePasswordKdfAlgoPBKDF2HMACSHA512iter100000#bbf2dda0 salt:bytes = SecurePasswordKdfAlgo;
-securePasswordKdfAlgoSHA512#86471d92 salt:bytes = SecurePasswordKdfAlgo;
-
-
----functions---
-
-account.getPassword#548a30f5 = account.Password;
-

When Telegram Passport is first used, the client generates a passport_secret (a 32-byte number with the modulo 255 sum of bytes equal to 239), using a part of server-generated random secure_random from account.password as an additional source of entropy for OpenSSL (when re-encrypting the passport_secret with a more secure algorithm or after a 2FA password change, the previous passport_secret is used, instead). -Then passport_secret is then encrypted using the user's password and hashed using the schema and parameters specified in the new_algo field of account.password.

-

The server should always return a securePasswordKdfAlgoPBKDF2HMACSHA512iter100000 constructor in the new_algo field. -If securePasswordKdfAlgoUnknown is returned, the remotely stored secret is encrypted using a new algorithm, not supported by the current client: the user should update their app.

-

The other constructors may be used only when decrypting old passport parameters generated by a legacy client; in this case, the passport secret should be re-encrypted and updated using new_algo.

- -

Subsequently, the client receives the encrypted passport_secret from the server and decrypts it after the user enters their password ».

-

In case the password is changed or a more secure algorithm is introduced in an update of the API, the client re-encrypts the passport_secret using the new password. -If the password is disabled, all Telegram Passport data is lost.

-

Passport Secret Decryption

-

Schema:

-
securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;
-securePasswordKdfAlgoPBKDF2HMACSHA512iter100000#bbf2dda0 salt:bytes = SecurePasswordKdfAlgo;
-securePasswordKdfAlgoSHA512#86471d92 salt:bytes = SecurePasswordKdfAlgo;
-
-secureSecretSettings#1527bcac secure_algo:SecurePasswordKdfAlgo secure_secret:bytes secure_secret_id:long = SecureSecretSettings;
-
-account.passwordSettings#9a5c33e5 flags:# email:flags.0?string secure_settings:flags.1?SecureSecretSettings = account.PasswordSettings;
-
----functions---
-
-account.getPasswordSettings#9cd4eaf9 password:InputCheckPasswordSRP = account.PasswordSettings;
-

The client requests the user's 2FA password and generates the SRP paramaters to be passed to account.getPasswordSettings.

-

If the password is correct, an account.passwordSettings constructor with secureSecretSettings is returned.

-

encrypted_passport_secret, passport_secret_fingerprint parameters are extracted from the secureSecretSettings constructor:

-
encrypted_passport_secret = secureSecretSettings.secure_secret
-passport_secret_fingerprint = secureSecretSettings.secure_id
-

The combined passport_secret_salt is extracted from the SecurePasswordKdfAlgo.

-
passport_secret_salt = SecurePasswordKdfAlgo.salt
-

Similar to passport secret encryption, the following process is used to decrypt and verify the encrypted_passport_secret:

-
    -
  • -

    The user's 2FA plaintext password is hashed using the specified algorithm.

    - -
  • -
  • -

    The secret_key and iv parameters are extracted from the generated password_hash

    -
    secret_key = slice( password_hash, 0, 32 )
    -iv = slice( password_hash, 32, 16 )
    -
  • -
  • -

    The encrypted_passport_secret is decrypted using AES256-CBC with the key secret_key and iv:

    -
    passport_secret = AES256_CBC_DEC(encrypted_passport_secret, secret_key, iv)
    -
  • -
  • -

    The passport_secret is verified by generating and checking the fingerprint:

    -
    my_passport_secret_fingerprint = long( slice( SHA256( passport_secret ), 0, 8 ) )
    -

    The client must verify that passport_secret_fingerprint is indeed equal to my_passport_secret_fingerprint.

    -
  • -
-

The passport_secret can now be used to decrypt encrypted passport data stored on telegram servers:

-

Data and File Encryption

-

Encryption

-

To encrypt Telegram Passport data, the client generates a data_secret (a 32-byte number with the modulo 255 sum of bytes equal to 239). The the data is encrypted according to the following scheme:

- -

Packing

-
SecureData
-
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;
-
    -
  • data is an encrypted and padded (see Encryption) JSON-serialized object of one of the following types: PersonalDetails, IdDocumentData, ResidentialAddress, depending on the chosen type. -Data must be in JSON format and not TL, as it has to be passed directly to the service using E2E encryption, without the bot API middleman to convert TL objects.
  • -
  • data_hash is the data_hash
  • -
  • secret is the encrypted_data_secret
  • -
-

Data is an encrypted and padded JSON-serialized object of one of the specified JSON types, depending on the chosen type.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Chosen typeJSON object
secureValueTypePersonalDetailsPersonalDetails
secureValueTypePassportIdDocumentData
secureValueTypeDriverLicenseIdDocumentData
secureValueTypeIdentityCardIdDocumentData
secureValueTypeInternalPassportIdDocumentData
secureValueTypeAddressResidentialAddress
-
InputSecureFile
-
inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;
-inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;
-
----functions---
-
-upload.saveFilePart#b304a621 file_id:long file_part:int bytes:bytes = Bool;
-

Files (JPG format, max. 10MB) are encrypted and padded (see Encryption), and then uploaded chunk by chunk as described in files », except that instead of generating an inputFile, an inputSecureFile should be generated, instead.

-
    -
  • As for secret chat files, the md5_checksum is to be set to the MD5 hash of the encrypted file, for a server-side integrity check.
  • -
  • The file_hash field should be set to the data_hash of the data.
  • -
  • The secret field is the encrypted_data_secret.
  • -
-
SecurePlainData
-
securePlainPhone#7d6099dd phone:string = SecurePlainData;
-securePlainEmail#21ec5a5f email:string = SecurePlainData;
-
----functions---
-
-account.sendVerifyPhoneCode#a5a356f9 phone_number:string settings:CodeSettings = auth.SentCode;
-account.verifyPhone#4dd3a7f6 phone_number:string phone_code_hash:string phone_code:string = Bool;
-account.sendVerifyEmailCode#7011509f email:string = account.SentEmailCode;
-account.verifyEmail#ecba39db email:string code:string = Bool;
-
-auth.resendCode#3ef1a9bf phone_number:string phone_code_hash:string = auth.SentCode;
-auth.cancelCode#1f040578 phone_number:string phone_code_hash:string = Bool;
-

The email/phone is passed in plaintext using the respective SecurePlainData constructor. -To verify a phone number or email and use it in Telegram Passport, use the appropriate methods:

- -

The flow is similar to the one used for logging in:

-
    -
  • Send email/phone code using the appropriate account.sendVerify*Code method
  • -
  • Pass the received code to the appropriate account.verify* method
  • -
  • Only for phone code verification, you can also resend/cancel the phone code using auth.resendCode/auth.cancelCode, as for logging in.
  • -
-

For more info, see the authorization docs.

-

When to use each constructor.

-
inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;
-inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;
-
-secureValueTypePersonalDetails#9d2a81e3 = SecureValueType;
-secureValueTypePassport#3dac6a00 = SecureValueType;
-secureValueTypeDriverLicense#6e425c4 = SecureValueType;
-secureValueTypeIdentityCard#a0d0744b = SecureValueType;
-secureValueTypeInternalPassport#99a48f23 = SecureValueType;
-secureValueTypeAddress#cbe31e26 = SecureValueType;
-secureValueTypeUtilityBill#fc36954e = SecureValueType;
-secureValueTypeBankStatement#89137c0d = SecureValueType;
-secureValueTypeRentalAgreement#8b883488 = SecureValueType;
-secureValueTypePassportRegistration#99e3806a = SecureValueType;
-secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;
-secureValueTypePhone#b320aadb = SecureValueType;
-secureValueTypeEmail#8e3ca7ee = SecureValueType;
-
-securePlainPhone#7d6099dd phone:string = SecurePlainData;
-securePlainEmail#21ec5a5f email:string = SecurePlainData;
-
-secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;
-
-inputSecureValue#db21d0a7 flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?InputSecureFile reverse_side:flags.2?InputSecureFile selfie:flags.3?InputSecureFile translation:flags.6?Vector<InputSecureFile> files:flags.4?Vector<InputSecureFile> plain_data:flags.5?SecurePlainData = InputSecureValue;
-

The schema for the inputSecureValue constructor defines the constructor to use for each field.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeSecure passport value type
dataflags.0?SecureDataEncrypted Telegram Passport element data
front_sideflags.1?InputSecureFileEncrypted passport file with the front side of the document
reverse_sideflags.2?InputSecureFileEncrypted passport file with the reverse side of the document
selfieflags.3?InputSecureFileEncrypted passport file with a selfie of the user holding the document
translationflags.6?Vector<InputSecureFile>Array of encrypted passport files with translated versions of the provided documents
filesflags.4?Vector<InputSecureFile>Array of encrypted passport files with photos the of the documents
plain_dataflags.5?SecurePlainDataPlaintext verified passport data
-

Here's a list of possible SecureValueTypes, and the parameters that can be set/requested when using each type.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TypeAllowed fields
secureValueTypeEmailplain_data
secureValueTypePhoneplain_data
secureValueTypePersonalDetailsdata
secureValueTypePassportdata, front_side, selfie, translation
secureValueTypeDriverLicensedata, front_side, reverse_side, selfie, translation
secureValueTypeIdentityCarddata, front_side, reverse_side, selfie, translation
secureValueTypeInternalPassportdata, front_side, selfie, translation
secureValueTypeAddressdata
secureValueTypeUtilityBillfiles, translation
secureValueTypeBankStatementfiles, translation
secureValueTypeRentalAgreementfiles, translation
secureValueTypePassportRegistrationfiles, translation
secureValueTypeTemporaryRegistrationfiles, translation
-

Fetching and deleting stored passport data

-
---functions---
-
-account.getAllSecureValues#b288bc7d = Vector<SecureValue>;
-account.getSecureValue#73665bc2 types:Vector<SecureValueType> = Vector<SecureValue>;
-account.deleteSecureValue#b880bc4b types:Vector<SecureValueType> = Bool;
-

The above methods can be used to fetch or remove encrypted Telegram Passport files stored in the Telegram Cloud by document type.

-

Passport Credentials

-

When a service requests data, it passes a nonce to the client. The nonce is a cryptographically secure unique identifier which allows the service to identify a request when receiving data as well as confirm the integrity of the data. The Telegram server doesn't have access to this nonce.

-

Once the user authorizes the Telegram Passport data transfer, the client forms the credentials (Credentials JSON object). Credentials contain the data_hash and data_secret from each element of Telegram Passport to which the user has allowed access. In addition to this, the credentials will always contain the nonce that the client received from the service at the initiation of the request.

-

Credentials are then passed to the service through the Bot API in encrypted form. To encrypt the credentials, the client generates a credentials_secret (a 32-byte number with the modulo 255 sum of bytes equal to 239). Then the credentials are encrypted according to the following scheme:

-
    -
  • -

    Credentials are padded to a length which is divisible by 16 bytes. To achieve this, 32 to 255 bytes are added at the beginning, where the first byte always holds the number of added bytes and the rest are random.

    -
  • -
  • -

    A hash of the padded credentials credentials_hash is calculated:

    -
    credentials_hash = SHA256( credentials )
    -
  • -
  • -

    The encryption key credentials_key is calculated:

    -
    credentials_secret_hash = SHA512( credentials_secret + credentials_hash )
    -credentials_key = slice( credentials_secret_hash, 0, 32 )
    -iv = slice( credentials_secret_hash, 32, 16 )
    -
  • -
  • -

    Credentials are encrypted using AES256-CBC with the key credentials_key and iv.

    -
    encrypted_credentials = AES256-CBC-ENC(credentials, credentials_key, iv)
    -
  • -
  • -

    credentials_secret is encrypted with the public RSA-key of the service with OPENSSL_PKCS1_OAEP_PADDING.

    -
    encrypted_credentials_secret = RSA-ENC(credentials_secret, key, OPENSSL_PKCS1_OAEP_PADDING)
    -
  • -
  • -

    The encrypted credentials are passed to the service via the MTProto API together with the encrypred credentials_secret and credentials_hash. Along with the credentials, the service receives from the Telegram Cloud the data it requested in encrypted form. See Submitting the Passport Form and PassportData:

    -
    secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;
    -
  • -
  • -

    data is the encrypted_credentials

    -
  • -
  • -

    hash is the credentials_hash

    -
  • -
  • -

    secret is the encrypted_credentials_secret

    -
  • -
-

Then the service decrypts the data as described here.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/passport/example.html b/data/core.telegram.org/passport/example.html deleted file mode 100644 index 68d5d0c84e..0000000000 --- a/data/core.telegram.org/passport/example.html +++ /dev/null @@ -1,585 +0,0 @@ - - - - - Example - - - - - - - - - - - - - - - -
- -
-
-
-
-

Example

- -

If you'd like to test Telegram Passport, use this page to request data. If you'd like to check out a real-life implementation, please see this blog post for examples of services that have integrated Telegram Passport.

-

Request Telegram Passport Data

-

-

-
-
-
- - -
-
-
-
- -
- -
- -
-
- -
-
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- - -
-
-
-
- -
- -
- -
- -
-
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- - -
-
-
-
- -
- -
- -
-
- -
-
- -
-
- - -
-
-
- -

-
-
-

Note that the passport demo bot will only store data for 1 hour and then discard it. After logging in here, you can use the logout button on this page to reset your session.

-
- -
- -
-
- -
- - - - - - - - - diff --git a/data/core.telegram.org/passport/sdk-android.html b/data/core.telegram.org/passport/sdk-android.html deleted file mode 100644 index 5060a7f97e..0000000000 --- a/data/core.telegram.org/passport/sdk-android.html +++ /dev/null @@ -1,180 +0,0 @@ - - - - - Android SDK - - - - - - - - - - - - - -
- -
-
-
- -

Android SDK

- -
- -

The Android SDK helps you easily integrate Telegram Passport requests into your Android-based apps. Check out our GitHub repository to see samples using this SDK.

-

Installation

-

Installing from Maven

-

Telegram Passport SDK is available from the Maven repository. -Add this line to the dependencies section in your build.gradle:

-
compile 'org.telegram:passport:1.1'
-

and sync your project.

-

Adding as a module

-

Download the library, unzip it and copy the library project to the root of your project directory (the one with settings.gradle and gradle.properties). Then, make the following changes to your Gradle scripts.

-

In settings.gradle, add ':telegrampassport' to includes:

-
include ':app', ':telegrampassport'
-

In the build.gradle file for your app, add this line to the dependencies section:

-
compile ':telegrampassport'
-

and sync your project.

-

Usage

-

Adding the button

-

The SDK provides the "Log in with Telegram" button which we recommend using for a consistent user experience across different apps. You can either add it from your Java code:

-
TelegramLoginButton telegramButton;
-// ...
-telegramButton=new TelegramLoginButton(this);
-// Optionally you can change the roundness of the button corners
-// to better fit your design.
-telegramButton.setCornerRoundness(1f);
-viewGroupOfSomeSort.addView(telegramButton, ViewGroup.LayoutParams.WRAP_CONTENT, ViewGroup.LayoutParams.WRAP_CONTENT);
-

Or from XML:

-
 <org.telegram.passport.TelegramLoginButton
-             android:layout_width="wrap_content"
-             android:layout_height="wrap_content"
-             app:cornerRoundness="0.5"/>
-

Requesting authorization

-

The button doesn't do anything by itself; you need to set an OnClickListener on it to start the authorization flow (replace the comments with actual parameters):

-
private static final int TG_PASSPORT_RESULT=352; // this can be any integer less than 0xFFFF
-// ...
-telegramButton.setOnClickListener(new View.OnClickListener(){
-@Override
-public void onClick(View view){
-    TelegramPassport.AuthRequest req=new TelegramPassport.AuthRequest();
-    req.botID=/* your bot ID here */;
-    req.publicKey=/* your bot public key here */;
-    req.nonce=/* a unique nonce to pass to the bot server */;
-    // Request either a passport or an ID card with selfie, a driver license, personal details with
-    // name as it appears in the documents, address with any address document, and a phone number.
-    // You could also pass a raw JSON object here if that's what works better for you
-    // (for example, if you already get it from your server in the correct format).
-    req.scope=new PassportScope(
-        new PassportScopeElementOneOfSeveral(PassportScope.PASSPORT, PassportScope.IDENTITY_CARD).withSelfie(),
-        new PassportScopeElementOne(PassportScope.PERSONAL_DETAILS).withNativeNames(),
-        PassportScope.DRIVER_LICENSE,
-        PassportScope.ADDRESS,
-        PassportScope.ADDRESS_DOCUMENT,
-        PassportScope.PHONE_NUMBER
-    );
-    TelegramPassport.request(MyActivity.this, req, TG_PASSPORT_RESULT);
-}});
-

If you need more control over the process, the TelegramPassport class contains several more methods:

-
    -
  • getAuthIntent(AuthParams) returns an Intent for you to use in startActivityForResult if you need to do that in some special way. Be sure to check that an app is present that can handle this intent before starting it by using PackageManager or intent.resolveActivity.
  • -
  • showAppInstallAlert(Activity) shows an alert that the user needs to install Telegram in order to continue. This is intended to be used together with the previous method for the cases when the app isn't installed.
  • -
-

Handling the result

-

The result is delivered via the onActivityResult method in your activity with the request code you passed to TelegramPassport.request. Currently, the only meaningful parameter is resultCode, which is RESULT_OK if the authorization was successful and RESULT_CANCELED otherwise.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/passport/sdk-ios-mac.html b/data/core.telegram.org/passport/sdk-ios-mac.html deleted file mode 100644 index 057cfb4e6d..0000000000 --- a/data/core.telegram.org/passport/sdk-ios-mac.html +++ /dev/null @@ -1,246 +0,0 @@ - - - - - iOS & macOS SDK - - - - - - - - - - - - - -
- -
-
-
- -

iOS & macOS SDK

- -
- -

TGPassportKit helps you easily integrate Telegram Passport requests into your iOS & macOS apps. Check out our GitHub repository to see samples using this SDK.

-

Installation

-

Installing using Cocoapods

-

To install TGPassportKit via Cocoapods add the following to your Podfile:

-
target 'MyApp' do
-  pod 'TGPassportKit' 
-end
-

then run pod install in your project root directory.

-

Installing using Carthage

-

Add the following line to your Cartfile:

-
github "telegrammessenger/TGPassportKit"
-

then run carthage update, and you will get the latest version of TGPassportKit in your Carthage folder.

-

Project Setup

-

Configure Your Info.plist

-

Configure your Info.plist by right-clicking it in Project Navigator, choosing Open As > Source Code and adding this snippet: -Replace {bot_id} with your value

-
<key>CFBundleURLTypes</key>
-<array>
-  <dict>
-  <key>CFBundleURLSchemes</key>
-  <array>
-    <string>tgbot{bot_id}</string>
-  </array>
-  </dict>
-</array>
-<key>LSApplicationQueriesSchemes</key>
-<array>
-  <string>tg</string>
-</array>
-

Connect AppDelegate methods

-

Add this code to your UIApplicationDelegate implementation

-
#import <TGPassportKit/TGPAppDelegate.h>
-
-- (BOOL)application:(UIApplication *)application
-            openURL:(NSURL *)url
-            options:(NSDictionary<UIApplicationOpenURLOptionsKey, id> *)options {
-    BOOL handledByPassportKit = [[TGPAppDelegate sharedDelegate] application:application
-                                                                     openURL:url
-                                                                     options:options];
-
-    return YES;
-}
-

If you support iOS 9 and below, also add this method:

-
- (BOOL)application:(UIApplication *)application 
-            openURL:(NSURL *)url 
-  sourceApplication:(nullable NSString *)sourceApplication 
-         annotation:(id)annotation {
-    BOOL handledByPassportKit = [[TGPAppDelegate sharedDelegate] application:application
-                                                                     openURL:url
-                                                           sourceApplication:sourceApplication
-                                                                  annotation:annotation];
-
-    return YES;
-}
-

Usage

-

Add Telegram Passport Button

-

To add the Telegram Passport button, add the following code to your view controller: -Replace {bot_id}, {bot_public_key} and {request_nonce} with your values

-
#import <TGPassportKit/TGPButton.h>
-
-@interface ViewController <TGPButtonDelegate>
-
-@end
-
-@implementation ViewController
-
-- (void)viewDidLoad {
-  [super viewDidLoad];
-
-  TGPButton *button = [[TGPButton alloc] init];
-  button.botConfig = [[TGPBotConfig alloc] initWithBotId:{bot_id} 
-                                               publicKey:@"{bot_public_key}"];
-  button.scope = [[TGPScope alloc] initWithJSONString:@"{\"data\":[\"id_document\",\"address_document\",\"phone_number\"],\"v\":1}"];
-// You can also construct a scope using provided data type classes like this: 
-// button.scope = [[TGPScope alloc] initWithTypes:@[[[TGPPersonalDetails alloc] init], [[TGPIdentityDocument alloc] initWithType:TGPIdentityDocumentTypePassport selfie:true translation:true]]];
-  button.nonce = @"{request_nonce}";
-  button.delegate = self;
-  [self.view addSubview:button];
-}
-
-- (void)passportButton:(TGPButton *)passportButton 
- didCompleteWithResult:(TGPRequestResult)result 
-                 error:(NSError *)error {
-    switch (result) {
-        case TGPRequestResultSucceed:
-            NSLog(@"Succeed");
-            break;
-
-        case TGPRequestResultCancelled:
-            NSLog(@"Cancelled");
-            break;
-
-        default:
-            NSLog(@"Failed");
-            break;
-    }
-}
-
-@end
-

...or Implement Your Own Behavior

-

If you want to design a custom UI and behavior, you can invoke a Passport request like this: -Replace {bot_id}, {bot_public_key} and {request_nonce} with your values

-
#import <TGPassportKit/TGPRequest.h>
-
-- (void)performPassportRequest 
-{
-    TGPBotConfig *botConfig = [[TGPBotConfig alloc] initWithBotId:{bot_id} 
-                                                        publicKey:@"{bot_public_key}"];
-    TGPRequest *request = [[TGPRequest alloc] initWithBotConfig:botConfig];
-    [request performWithScope:[[TGPScope alloc] initWithJSONString:@"{\"data\":[\"id_document\",\"phone_number\"],\"v\":1}"] 
-                      payload:@"{request_nonce}" 
-            completionHandler:^(TGPRequestResult result, NSError * _Nullable error) {
-        switch (result) {
-            case TGPRequestResultSucceed:
-                NSLog(@"Succeed");
-                break;
-
-            case TGPRequestResultCancelled:
-                NSLog(@"Cancelled");
-                break;
-
-            default:
-                NSLog(@"Failed");
-                break;
-        }
-    }];
-}
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/passport/sdk-javascript.html b/data/core.telegram.org/passport/sdk-javascript.html deleted file mode 100644 index 504328eb0c..0000000000 --- a/data/core.telegram.org/passport/sdk-javascript.html +++ /dev/null @@ -1,258 +0,0 @@ - - - - - Javascript SDK - - - - - - - - - - - - - -
- -
-
-
- -

Javascript SDK

- -
- -

The Javascript SDK helps you easily integrate Telegram Passport requests into your website. Check out our GitHub repository to see samples using this SDK.

-

Installation

-

Download and include the Javascript SDK in the head section of your page:

-
<script src="telegram-passport.js"></script>
-

Usage

-

Simply call Telegram.Passport.createAuthButton to create the default Telegram Passport button:

-
<div id="telegram_passport_auth"></div>
-<script>
-  Telegram.Passport.createAuthButton('telegram_passport_auth', {
-    bot_id:       123456, // place id of your bot here
-    scope:        {data: [{type: 'id_document', selfie: true}, 'address_document', 'phone_number', 'email'], v: 1},
-    public_key:   '-----BEGIN PUBLIC KEY----- ...', // place public key of your bot here
-    nonce:        'ab2df83746a87d2f3bd6...', // place nonce here
-    callback_url: 'https://example.com/callback/' // place callback url here
-  });
-</script>
-
-

Note that if you use a Content-Security-Policy (CSP) header with the frame-src/child-src directive you should allow tg: source to prevent errors in some browsers (e.g. Firefox)

-
-

createAuthButton

- - - - - - - - - - - - - - - - - - - - - - - -
ParametersTypeRequired
elementString or DOMNodeYes
auth_paramsAuthParameters or FunctionYes
optionsAuthButtonOptionsOptional
-

AuthParameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
bot_idIntegerUnique identifier for the bot
scopePassportScopeA JSON-serialized object describing the data you want to request
public_keyStringPublic key of your bot
nonceStringBot-specified nonce
callback_urlStringOptional. URL to which the user will be redirected.
-

AuthButtonOptions

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
textStringOptional. Text on the button. Defaults to "Log In With Telegram".
radiusIntegerOptional. Radius of the button and tooltip in px. Defaults to 23.
tooltip_textStringOptional. Text on the tooltip. Defaults to "Please install Telegram to use this option.".
tooltip_positionStringOptional. Tooltip position. One of "top", "bottom", "left", "right". Defaults to "bottom".
tooltip_forceBooleanOptional. Always show a tooltip. Defaults to false.
-

You can also create your custom button. Do not forget about the tooltip. You should add an onclick listener to the button which calls the Telegram.Passport.auth(auth_params, tooltip_toggle); method:

-
<button id="telegram_passport_auth">Log In With Telegram</button>
-<script>
-  var auth_button = document.getElementById('telegram_passport_auth');
-  var auth_params = {
-    bot_id:        XXXXXX, // place id of your bot here
-    scope:         {data: [{type: 'id_document', selfie: true}, 'address_document', 'phone_number', 'email'], v: 1},
-    public_key:    '-----BEGIN PUBLIC KEY----- ...', // place public key of your bot here
-    nonce:         'ab2df83746a87d2f3bd6...', // place nonce here
-    callback_url:  'https://example.com/callback/' // place callback url here
-  };
-  auth_button.addEventListener('click', function() {
-    Telegram.Passport.auth(auth_params, function(show) {
-      if (show) {
-        // some code to show tooltip
-      } else {
-        // some code to hide tooltip
-      }
-    });
-  }, false);
-</script>
-

Receiving information

-

When the user confirms your request by pressing the 'Authorize' button, it will be redirected to the URL specified in the callback_url with the parameter tg_passport=success and the Bot API will send the bot an Update with the field passport_data which contains encrypted Telegram Passport data.

-

If the user cancels your request, it will be redirected to the URL specified in the callback_url with the parameter tg_passport=cancel.

-

If an error occurs during the request, the user will be redirected to the URL specified in the callback_url with the parameter tg_passport=error. The parameter error will contain one of the following values: BOT_INVALID, PUBLIC_KEY_REQUIRED, PUBLIC_KEY_INVALID, SCOPE_EMPTY, NONCE_EMPTY.

- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/reproducible-builds.html b/data/core.telegram.org/reproducible-builds.html deleted file mode 100644 index d0f23db600..0000000000 --- a/data/core.telegram.org/reproducible-builds.html +++ /dev/null @@ -1,488 +0,0 @@ - - - - - Reproducible Builds for iOS and Android - - - - - - - - - - - - - -
- -
-
-
-
-

Reproducible Builds for iOS and Android

- -

This page contains instructions for verifying that Telegram's open source code is exactly the same as the code that is used to build the apps that are available in the App Store, Google Play and directly on the Telegram website.

-

Warning: Telegram supports reproducible builds as of version 5.13. Bear in mind that, at this stage, the verification process should be considered experimental. We will be updating our apps and these instructions to make this process as straightforward as possible.

- -
-

Please read the relevant notes and troubleshooting section carefully.

-
-
-
- Dude in a jacket inspecting the hologram of a mechanical dog to verify it's built according to the blueprints provided. -
- -

Reproducible Builds for Android

-

Step 1. Install Docker

-

Docker can be obtained here. Once the installation is complete, log into your Docker account > Preferences > Advanced and configure the amount of resources Docker may use:

-
- -

Docker Performance

-
- -

We recommend using the maximum amount allowed by your system's hardware, in order to speed up the build time.

-

Step 2. Confirm which version you have installed on your Android device

-

You can find the version/build number at the bottom of the Settings page. Note that Telegram supports reproducible builds starting with version 5.13.

-
- -

App Version

-
- -

The commit tag to checkout source code for the example above will be release-5.13.0_1821.

-
-

Please make sure that you're using the correct version and build number of the version you want to check (and not the one from this example 😈).

-
-

The part after the version number will help you know in which folder to look for the correct APK when you've finished building the app (Step 4):

-
    -
  • “Direct” after version number means that the APK will be inside the “afat/standalone” folder.
  • -
  • “Universal” after version number means that the APK will be inside the “afat/release” folder.
  • -
  • If you have Android Version 6.0 or greater, your APK folder will have the “_SDK23” suffix.
  • -
  • “arm64-v8a” - folder name will start with “arm64”.
  • -
  • “armeabi-v7” - folder name will start with “armv7”.
  • -
  • “x86” - folder name will start with “x86”.
  • -
  • “x86_64” - folder name will start with “x64”.
  • -
-
- -

APK Folders

-
- - -

Step 3. Obtain the source code

-

Open Terminal, run the commands:
git clone https://github.com/DrKLO/Telegram.git $HOME/telegram-android
cd $HOME/telegram-android
git checkout release-{VERSION AND BUILD NUMBER FROM STEP 2}

-

For our example, the command would be:
git checkout release-5.13.0_1821

-
- -
- -

Step 4. Build the app

-

Open Terminal, run the commands:
cd $HOME/telegram-android
docker build -t telegram-build .

-
- -
- -

docker run --rm -v "$PWD":/home/source telegram-build

-
- -
- -

These commands will produce 9 different APKs for different target SDK versions and CPU ABIs.

-

These APKs can be found in:
$HOME/telegram-android/TMessagesProj/build/outputs/apk/

-

Use the folder name from Step 2 to find the correct folder that holds the same APK as installed on your device. For example, for non-universal Android 9.0 arm64-v8a, the path to your APK will be:
$HOME/telegram-android/TMessagesProj/build/outputs/apk/arm64_SDK23/release/app.apk
Copy this APK to the root source directory by running this command in Terminal:
cp $HOME/telegram-android/TMessagesProj/build/outputs/apk/arm64_SDK23/release/app.apk $HOME/telegram-android/telegram_built.apk

-
- -
- -

Step 5. The Telegram APK installed on your device

-

You will need adb for this step.

-
- -

ADB

-
- -
-

If you downloaded your APK directly from Telegram's website, use the package name org.telegram.messenger.web in this step. To verify the Google Play APK, use org.telegram.messenger.

-
-

Connect your device to the computer, open Terminal, run the commands:
adb shell pm path org.telegram.messenger

-
- -
- -

The output will look something like this:
package:/data/app/org.telegram.messenger-_zOSURFEx2GpHM8UDF_PVg==/base.apk
By using this information, pull the APK from your device to $HOME/telegram-android using command:
adb pull /data/app/org.telegram.messenger-_zOSURFEx2GpHM8UDF_PVg==/base.apk $HOME/telegram-android/telegram_store.apk

-

Step 6. Compare the APKs

-

Open Terminal, run the commands:
cd $HOME/telegram-android
python apkdiff.py telegram_store.apk telegram_built.apk
If the APKs are the same, you will see
APKs are the same!

-
- -
-Tada! - -Otherwise, something went wrong. -
- -
- -

If your APKs don't match, please make sure that you chose the correct code version and the right SDK.

-

Check out the Troubleshooting section first in case you run into trouble.

-
-

Reproducible Builds for iOS

-

The verification process for iOS builds is, unfortunately, a lot more complex than for Android. The two main issues with Apple's current policies and infrastructure are as follows:

-
    -
  1. Apple insists on using FairPlay encryption to “protect” even free apps from “app pirates” which makes obtaining the executable code of apps impossible without a jailbroken device. To solve this issue, Apple would simply need to allow submitting unencryptable binaries to the App Store. This would not affect security since the code would still be signed – and would enable anyone to check the integrity of apps supporting reproducible builds without endangering the integrity and security of their devices.

    -
  2. -
  3. Building your own reproducible binaries is difficult because macOS doesn't support containers like Docker. If Apple followed in the footsteps of Linux (and even Microsoft!) and added container support, it would eliminate the need for steps 1-3 in the guide below.

    -
  4. -
-
-

As things stand now, you'll need a jailbroken device, at least 1,5 hours and approximately 90GB of free space to properly set up a virtual machine for the verification process.

-
-

To provide a stable and easily reproducible environment, Telegram iOS builds are compiled on a virtual machine. Parallels is used to verify the builds.

-

Step 1. Install the Parallels virtual machine

-

Parallels can be obtained here, it features a fully-functional trial version.

-

Step 2. Install the latest version of macOS Big Sur

-

To download an image that can be installed on the virtual machine, open the App Store, search for “Catalina” and click “View”.

-
- -

Search for macOS Catalina on App Store > View

-
- -
- -

macOS Catalina > Get -

-
- -

This will open a system pop-up offering to download the OS:

-
- -
-Choose “Download” and wait for the download to finish. - -> If you were not using the latest version of the OS, your system may start updating instead. Please finish updating to download macOS Catalina. - -When done, open Parallels and choose macOS Catalina: - -
- -

Select 'Install Windows or another OS' > Continue

-
- -
- -

Select a file... > Applications (All files) > Install macOS Сatalina

-
- -

Before starting the installation, configure the virtual machine:

-
- -

Checkbox 'Customize settings before installation'

-
- -

Change the name of the virtual machine to macos11_Xcode12_5_1

-
- -

Name VM as macos10_15_Xcode12_2

-
- -

Hardware > Processors: 2-4
Memory > 4GB may suffice but 8GB is recommended

-
- -

At least 2 CPUs + 4 (8 recommended) GB Memory.

-
- -

You will get something like this:

-
- -

Click Continue

-
- -

Parallels may request access to your microphone and camera, this is not required – just press Close.

-
- -

Install macOS > Continue

-
- -

Your Apple ID is also not required, you can choose Set Up Later.

-
- -

Skip Apple ID with 'Set Up Later'

-
- -

Use “telegram” for both the account name and password.

-
-

Do not ever use the password “telegram” for anything else, it's cursed.

-
-
- -

Create a computer account with 'telegram' set both as account name and password

-
- -

Now install Parallels tools from the menu bar:

-
- - -

Install Parallels Tools using menu bar > Parallels icon > Actions > Install (Reinstall) Parallels Tools...

-
- -

After the system restarts, log in.
Open Terminal and run:
sudo visudo
Enter the password “telegram”

-
- -
- -

Find this line at the end of the file:
%admin ALL=(ALL) ALL
Press “i” on your keyboard, add “NOPASSWD:”
%admin ALL=(ALL) NOPASSWD: ALL
Press Escape.
Type in “:wq”
Press Enter

-
- -

Press i to edit the highlighted string.

- -

Enter :wq > press Enter.

-
- -

In the terminal, run:
sudo systemsetup -setcomputersleep Never

-
- -

sudo systemsetup -setcomputersleep Never > press Enter.

-
- -

Step 3. Install SSH keys on the virtual machine

-

In the virtual machine, open System Settings > Sharing and enable Remote Login.

-
- -
- -

In the virtual machine, open Terminal and run:
mkdir -p .ssh; nano .ssh/authorized_keys

-
- -
- -

In your main OS, open Terminal and run:
if [ ! -e ~/.ssh/id_rsa.pub ]; then ssh-keygen -t rsa -b 4096; fi && cat ~/.ssh/id_rsa.pub | pbcopy

-
- -
- -

If you see the line “Enter file in which to save the key (/Users/…/.ssh/id_rsa):”, press Enter
In the virtual machine, press CMD+V
Then Ctrl+O, Ctrl+X

-
- -
- -

Step 4. Install Xcode version 12.5.1

-

In the virtual machine, open Safari and go to https://developer.apple.com
Sign in to your Account:

-
- -

developer.apple.com > Account > sign in with your Apple ID

-
- -

Go to Downloads > More
Enter Xcode in the search field and find the version 12.5.1

-
- -

Downloads > More > Xcode 12.5.1

-
- -

Once the installation is complete, open the file Xcode 12.5.1.xip. The system will unarchive the app into the same folder. Move it to the Applications folder using Finder.

-
- -

Unarchive Xcode > drag the app to Applications folder

-
- -
- -
- -

On the virtual machine, run this command from the terminal:
sudo xcode-select -s /Applications/Xcode.app/Contents/Developer

-
- -
- -

Shut down the virtual machine.

-
- -

Shut down the virtual machine

-
- -

Step 4.1

-

Download the certificates at https://github.com/TelegramMessenger/Telegram-iOS/tree/master/build-system/fake-codesigning/certs/distribution and install them into the virtual machine.

-

Launch Keychain Access and double-click the installed certificate. Under “Trust”, change “When using this certificate” to “Always Trust”.

-

Step 5. Obtaining the source code

-

git clone --recursive https://github.com/TelegramMessenger/telegram-ios.git $HOME/telegram-ios
cd $HOME/telegram-ios
git checkout release-${VERSION_NUMBER}

-

E.g., git checkout release-7.3. Please note that you need to check out the whole git history as the build version depends on the number of commits in the repository.

-
- -
- -

Step 6. Downloading Bazel 3.7.0 to $HOME/bazel/bazel

-

mkdir -p $HOME/bazel && cd $HOME/bazel
curl -O -L https://github.com/bazelbuild/bazel/releases/download/3.7.0/bazel-3.7.0-darwin-x86_64
mv bazel-3.7.0-darwin-x86_64 bazel

-

Check that you have downloaded the correct version:
chmod +x bazel
./bazel --version

-

Step 7. Building the app

-

Open Terminal, run the commands:
cd $HOME/telegram-ios -BAZEL="$HOME/bazel/bazel" sh buildbox/build-telegram.sh verify

-
- -
- -

If the environment has been set up correctly, this will start the building process. Note that this step can easily take 30-40 minutes. The average build time on a MacBook Pro (i9 6 core) is 35 minutes.

-
- - -
- -

Once the process is complete the resulting IPA file can be found in build/artifacts/Telegram.ipa
All the following steps will be made via Terminal on your main system.

-

Step 8. Downloading a decrypted version of the app from the App Store

-

This step requires a jailbroken device equipped with tools for decrypting apps. We‘d love to make this process more simple but that’s what you get for using Apple tech.

-

Step 9. Comparing the AppStore build and the version built in the virtual machine

-

Install the necessary tools:
if ! type brew > /dev/null; - then /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"; fi && brew install python3

-
- -
- -

Run
python3 tools/ipadiff.py build/artifacts/Telegram.ipa PATH-TO-THE-IPA-FILE-FROM-STEP-9

-
    -
  1. cd telegram-ios > Enter
  2. -
  3. python3 tools/ipadiff.py build/artifacts/Telegram.ipa /path/ > Enter
  4. -
-
- -
- -

In case of a successful comparison, you will get a text along these lines:

-
IPAs are equal, except for the files that can't currently be checked:
-    Excluded files that couldn't be checked due to being encrypted:
-        PlugIns/SiriIntents.appex/SiriIntents
-        PlugIns/Widget.appex/Widget
-        PlugIns/NotificationContent.appex/NotificationContent
-        PlugIns/NotificationService.appex/NotificationService
-        PlugIns/Share.appex/Share
-    IPAs contain Watch directory with a Watch app which can't be checked currently.
-    IPAs contain .car (Asset Catalog) files that are compiled by the App Store and can't currently be checked:
-
-        Frameworks/TelegramUI.framework/Assets.car
-        Assets.car
-    IPAs contain .nib (compiled Interface Builder) files that are compiled by the App Store and can't currently be checked:
-        Base.lproj/LaunchScreen.nib
-
- -
- -

In case of any mismatches, you'll get a detailed report.

-
- -
- -

iOS: Notes

-
    -
  1. You will get a warning if the archive created in Step 7 contains encrypted files. If all these files are in the PlugIns subfolder, they represent various system extensions (e.g. external sharing, Siri, 3D touch). Decrypting such files using existing ways of receiving app archives via Jailbreak is non-trivial (but we're working on resolving this issue). If you do manage to decrypt them, e.g. on iOS 8, they will be matched.

    -
  2. -
  3. You will be notified if the archive includes an Apple Watch app. The watch app will soon no longer be included in the archive.

    -
  4. -
  5. Files with the .car extension are app resource archives (images, sounds) which were compiled and processed specifically for the target device. The App Store processes them in non-trivial ways, we're planning on getting rid of them in future versions.

    -
  6. -
  7. The LaunchScreen.nib file is an empty file containing a description of the interface which is displayed by the system before the app is launched. It is processed by the App Store in a non-trivial way but doesn't contain any code and therefore may be ignored.

    -
  8. -
-
-

Troubleshooting

-

If you encounter any issues with obtaining the code, building and comparing the apps, please contact us at @botsupport and include the hashtag #reproducibleBuilds with your message describing the problem.

-

Troubleshooting: Android

-
    -
  1. Make sure that you checkout the correct version of the code.

    -
  2. -
  3. Make sure that you build the app using the right SDK.

    -
  4. -
  5. If the gradle version used in the Dockerfile is not available anymore and building of the Docker image fails, wait for a Dockerfile update or update manually to lastest available version.

    -
  6. -
-

-

We will update this section with information on overcoming other common issues.

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/schema.html b/data/core.telegram.org/schema.html deleted file mode 100644 index 0c7574e3c8..0000000000 --- a/data/core.telegram.org/schema.html +++ /dev/null @@ -1,1800 +0,0 @@ - - - - - Schema - - - - - - - - - - - - - -
- -
-
-
- -

Schema

- -

Below you will find the current TL-schema. More details on TL »

-

See also the detailed schema in JSON »

-

See also TL-Schema for end-to-end encrypted messages »

-
- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
-
-true#3fedd339 = True;
-
-vector#1cb5c415 {t:Type} # [ t ] = Vector t;
-
-error#c4b9f9bb code:int text:string = Error;
-
-null#56730bcc = Null;
-
-inputPeerEmpty#7f3b18ea = InputPeer;
-inputPeerSelf#7da07ec9 = InputPeer;
-inputPeerChat#35a95cb9 chat_id:long = InputPeer;
-inputPeerUser#dde8a54c user_id:long access_hash:long = InputPeer;
-inputPeerChannel#27bcbbfc channel_id:long access_hash:long = InputPeer;
-inputPeerUserFromMessage#a87b0a1c peer:InputPeer msg_id:int user_id:long = InputPeer;
-inputPeerChannelFromMessage#bd2a0840 peer:InputPeer msg_id:int channel_id:long = InputPeer;
-
-inputUserEmpty#b98886cf = InputUser;
-inputUserSelf#f7c1b13f = InputUser;
-inputUser#f21158c6 user_id:long access_hash:long = InputUser;
-inputUserFromMessage#1da448e2 peer:InputPeer msg_id:int user_id:long = InputUser;
-
-inputPhoneContact#f392b7f4 client_id:long phone:string first_name:string last_name:string = InputContact;
-
-inputFile#f52ff27f id:long parts:int name:string md5_checksum:string = InputFile;
-inputFileBig#fa4f0bb5 id:long parts:int name:string = InputFile;
-
-inputMediaEmpty#9664f57f = InputMedia;
-inputMediaUploadedPhoto#1e287d04 flags:# file:InputFile stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
-inputMediaPhoto#b3ba0635 flags:# id:InputPhoto ttl_seconds:flags.0?int = InputMedia;
-inputMediaGeoPoint#f9c44144 geo_point:InputGeoPoint = InputMedia;
-inputMediaContact#f8ab7dfb phone_number:string first_name:string last_name:string vcard:string = InputMedia;
-inputMediaUploadedDocument#5b38c6c1 flags:# nosound_video:flags.3?true force_file:flags.4?true file:InputFile thumb:flags.2?InputFile mime_type:string attributes:Vector<DocumentAttribute> stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
-inputMediaDocument#33473058 flags:# id:InputDocument ttl_seconds:flags.0?int query:flags.1?string = InputMedia;
-inputMediaVenue#c13d1c11 geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string = InputMedia;
-inputMediaPhotoExternal#e5bbfe1a flags:# url:string ttl_seconds:flags.0?int = InputMedia;
-inputMediaDocumentExternal#fb52dc99 flags:# url:string ttl_seconds:flags.0?int = InputMedia;
-inputMediaGame#d33f43f3 id:InputGame = InputMedia;
-inputMediaInvoice#d9799874 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON start_param:flags.1?string = InputMedia;
-inputMediaGeoLive#971fa843 flags:# stopped:flags.0?true geo_point:InputGeoPoint heading:flags.2?int period:flags.1?int proximity_notification_radius:flags.3?int = InputMedia;
-inputMediaPoll#f94e5f1 flags:# poll:Poll correct_answers:flags.0?Vector<bytes> solution:flags.1?string solution_entities:flags.1?Vector<MessageEntity> = InputMedia;
-inputMediaDice#e66fbf7b emoticon:string = InputMedia;
-
-inputChatPhotoEmpty#1ca48f57 = InputChatPhoto;
-inputChatUploadedPhoto#c642724e flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = InputChatPhoto;
-inputChatPhoto#8953ad37 id:InputPhoto = InputChatPhoto;
-
-inputGeoPointEmpty#e4c123d6 = InputGeoPoint;
-inputGeoPoint#48222faf flags:# lat:double long:double accuracy_radius:flags.0?int = InputGeoPoint;
-
-inputPhotoEmpty#1cd7bf0d = InputPhoto;
-inputPhoto#3bb3b94a id:long access_hash:long file_reference:bytes = InputPhoto;
-
-inputFileLocation#dfdaabe1 volume_id:long local_id:int secret:long file_reference:bytes = InputFileLocation;
-inputEncryptedFileLocation#f5235d55 id:long access_hash:long = InputFileLocation;
-inputDocumentFileLocation#bad07584 id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;
-inputSecureFileLocation#cbc7ee28 id:long access_hash:long = InputFileLocation;
-inputTakeoutFileLocation#29be5899 = InputFileLocation;
-inputPhotoFileLocation#40181ffe id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;
-inputPhotoLegacyFileLocation#d83466f3 id:long access_hash:long file_reference:bytes volume_id:long local_id:int secret:long = InputFileLocation;
-inputPeerPhotoFileLocation#37257e99 flags:# big:flags.0?true peer:InputPeer photo_id:long = InputFileLocation;
-inputStickerSetThumb#9d84f3db stickerset:InputStickerSet thumb_version:int = InputFileLocation;
-inputGroupCallStream#598a92a flags:# call:InputGroupCall time_ms:long scale:int video_channel:flags.0?int video_quality:flags.0?int = InputFileLocation;
-
-peerUser#59511722 user_id:long = Peer;
-peerChat#36c6019a chat_id:long = Peer;
-peerChannel#a2a5371e channel_id:long = Peer;
-
-storage.fileUnknown#aa963b05 = storage.FileType;
-storage.filePartial#40bc6f52 = storage.FileType;
-storage.fileJpeg#7efe0e = storage.FileType;
-storage.fileGif#cae1aadf = storage.FileType;
-storage.filePng#a4f63c0 = storage.FileType;
-storage.filePdf#ae1e508d = storage.FileType;
-storage.fileMp3#528a0677 = storage.FileType;
-storage.fileMov#4b09ebbc = storage.FileType;
-storage.fileMp4#b3cea0e4 = storage.FileType;
-storage.fileWebp#1081464c = storage.FileType;
-
-userEmpty#d3bc4b7a id:long = User;
-user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
-
-userProfilePhotoEmpty#4f11bae1 = UserProfilePhoto;
-userProfilePhoto#82d1f706 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = UserProfilePhoto;
-
-userStatusEmpty#9d05049 = UserStatus;
-userStatusOnline#edb93949 expires:int = UserStatus;
-userStatusOffline#8c703f was_online:int = UserStatus;
-userStatusRecently#e26f42f1 = UserStatus;
-userStatusLastWeek#7bf09fc = UserStatus;
-userStatusLastMonth#77ebc742 = UserStatus;
-
-chatEmpty#29562865 id:long = Chat;
-chat#41cbf256 flags:# creator:flags.0?true kicked:flags.1?true left:flags.2?true deactivated:flags.5?true call_active:flags.23?true call_not_empty:flags.24?true noforwards:flags.25?true id:long title:string photo:ChatPhoto participants_count:int date:int version:int migrated_to:flags.6?InputChannel admin_rights:flags.14?ChatAdminRights default_banned_rights:flags.18?ChatBannedRights = Chat;
-chatForbidden#6592a1a7 id:long title:string = Chat;
-channel#8261ac61 flags:# creator:flags.0?true left:flags.2?true broadcast:flags.5?true verified:flags.7?true megagroup:flags.8?true restricted:flags.9?true signatures:flags.11?true min:flags.12?true scam:flags.19?true has_link:flags.20?true has_geo:flags.21?true slowmode_enabled:flags.22?true call_active:flags.23?true call_not_empty:flags.24?true fake:flags.25?true gigagroup:flags.26?true noforwards:flags.27?true id:long access_hash:flags.13?long title:string username:flags.6?string photo:ChatPhoto date:int restriction_reason:flags.9?Vector<RestrictionReason> admin_rights:flags.14?ChatAdminRights banned_rights:flags.15?ChatBannedRights default_banned_rights:flags.18?ChatBannedRights participants_count:flags.17?int = Chat;
-channelForbidden#17d493d5 flags:# broadcast:flags.5?true megagroup:flags.8?true id:long access_hash:long title:string until_date:flags.16?int = Chat;
-
-chatFull#4dbdc099 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:long about:string participants:ChatParticipants chat_photo:flags.2?Photo notify_settings:PeerNotifySettings exported_invite:flags.13?ExportedChatInvite bot_info:flags.3?Vector<BotInfo> pinned_msg_id:flags.6?int folder_id:flags.11?int call:flags.12?InputGroupCall ttl_period:flags.14?int groupcall_default_join_as:flags.15?Peer theme_emoticon:flags.16?string = ChatFull;
-channelFull#e9b27a17 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector<string> groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string = ChatFull;
-
-chatParticipant#c02d4007 user_id:long inviter_id:long date:int = ChatParticipant;
-chatParticipantCreator#e46bcee4 user_id:long = ChatParticipant;
-chatParticipantAdmin#a0933f5b user_id:long inviter_id:long date:int = ChatParticipant;
-
-chatParticipantsForbidden#8763d3e1 flags:# chat_id:long self_participant:flags.0?ChatParticipant = ChatParticipants;
-chatParticipants#3cbc93f8 chat_id:long participants:Vector<ChatParticipant> version:int = ChatParticipants;
-
-chatPhotoEmpty#37c1011c = ChatPhoto;
-chatPhoto#1c6e1c11 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = ChatPhoto;
-
-messageEmpty#90a6ca84 flags:# id:int peer_id:flags.0?Peer = Message;
-message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true noforwards:flags.26?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
-messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;
-
-messageMediaEmpty#3ded6320 = MessageMedia;
-messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;
-messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;
-messageMediaContact#70322949 phone_number:string first_name:string last_name:string vcard:string user_id:long = MessageMedia;
-messageMediaUnsupported#9f84f49e = MessageMedia;
-messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;
-messageMediaWebPage#a32dd600 webpage:WebPage = MessageMedia;
-messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;
-messageMediaGame#fdb19008 game:Game = MessageMedia;
-messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
-messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;
-messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
-messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;
-
-messageActionEmpty#b6aef7b0 = MessageAction;
-messageActionChatCreate#bd47cbad title:string users:Vector<long> = MessageAction;
-messageActionChatEditTitle#b5a1ce5a title:string = MessageAction;
-messageActionChatEditPhoto#7fcb13a8 photo:Photo = MessageAction;
-messageActionChatDeletePhoto#95e3fbef = MessageAction;
-messageActionChatAddUser#15cefd00 users:Vector<long> = MessageAction;
-messageActionChatDeleteUser#a43f30cc user_id:long = MessageAction;
-messageActionChatJoinedByLink#31224c3 inviter_id:long = MessageAction;
-messageActionChannelCreate#95d2ac92 title:string = MessageAction;
-messageActionChatMigrateTo#e1037f92 channel_id:long = MessageAction;
-messageActionChannelMigrateFrom#ea3948e9 title:string chat_id:long = MessageAction;
-messageActionPinMessage#94bd38ed = MessageAction;
-messageActionHistoryClear#9fbab604 = MessageAction;
-messageActionGameScore#92a72876 game_id:long score:int = MessageAction;
-messageActionPaymentSentMe#8f31b327 flags:# currency:string total_amount:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string charge:PaymentCharge = MessageAction;
-messageActionPaymentSent#40699cd0 currency:string total_amount:long = MessageAction;
-messageActionPhoneCall#80e11a7f flags:# video:flags.2?true call_id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = MessageAction;
-messageActionScreenshotTaken#4792929b = MessageAction;
-messageActionCustomAction#fae69f56 message:string = MessageAction;
-messageActionBotAllowed#abe9affe domain:string = MessageAction;
-messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction;
-messageActionSecureValuesSent#d95c6154 types:Vector<SecureValueType> = MessageAction;
-messageActionContactSignUp#f3f25f76 = MessageAction;
-messageActionGeoProximityReached#98e0d697 from_id:Peer to_id:Peer distance:int = MessageAction;
-messageActionGroupCall#7a0d7f42 flags:# call:InputGroupCall duration:flags.0?int = MessageAction;
-messageActionInviteToGroupCall#502f92f7 call:InputGroupCall users:Vector<long> = MessageAction;
-messageActionSetMessagesTTL#aa1afbfd period:int = MessageAction;
-messageActionGroupCallScheduled#b3a07661 call:InputGroupCall schedule_date:int = MessageAction;
-messageActionSetChatTheme#aa786345 emoticon:string = MessageAction;
-
-dialog#2c171f72 flags:# pinned:flags.2?true unread_mark:flags.3?true peer:Peer top_message:int read_inbox_max_id:int read_outbox_max_id:int unread_count:int unread_mentions_count:int notify_settings:PeerNotifySettings pts:flags.0?int draft:flags.1?DraftMessage folder_id:flags.4?int = Dialog;
-dialogFolder#71bd134c flags:# pinned:flags.2?true folder:Folder peer:Peer top_message:int unread_muted_peers_count:int unread_unmuted_peers_count:int unread_muted_messages_count:int unread_unmuted_messages_count:int = Dialog;
-
-photoEmpty#2331b22d id:long = Photo;
-photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;
-
-photoSizeEmpty#e17e23c type:string = PhotoSize;
-photoSize#75c78e60 type:string w:int h:int size:int = PhotoSize;
-photoCachedSize#21e1ad6 type:string w:int h:int bytes:bytes = PhotoSize;
-photoStrippedSize#e0b0bc2e type:string bytes:bytes = PhotoSize;
-photoSizeProgressive#fa3efb95 type:string w:int h:int sizes:Vector<int> = PhotoSize;
-photoPathSize#d8214d41 type:string bytes:bytes = PhotoSize;
-
-geoPointEmpty#1117dd5f = GeoPoint;
-geoPoint#b2a2f663 flags:# long:double lat:double access_hash:long accuracy_radius:flags.0?int = GeoPoint;
-
-auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
-
-auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
-auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
-
-auth.exportedAuthorization#b434e2b8 id:long bytes:bytes = auth.ExportedAuthorization;
-
-inputNotifyPeer#b8bc5b0c peer:InputPeer = InputNotifyPeer;
-inputNotifyUsers#193b4417 = InputNotifyPeer;
-inputNotifyChats#4a95e84e = InputNotifyPeer;
-inputNotifyBroadcasts#b1db7c7e = InputNotifyPeer;
-
-inputPeerNotifySettings#9c3d198e flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = InputPeerNotifySettings;
-
-peerNotifySettings#af509d20 flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = PeerNotifySettings;
-
-peerSettings#733f2961 flags:# report_spam:flags.0?true add_contact:flags.1?true block_contact:flags.2?true share_contact:flags.3?true need_contacts_exception:flags.4?true report_geo:flags.5?true autoarchived:flags.7?true invite_members:flags.8?true geo_distance:flags.6?int = PeerSettings;
-
-wallPaper#a437c3ed id:long flags:# creator:flags.0?true default:flags.1?true pattern:flags.3?true dark:flags.4?true access_hash:long slug:string document:Document settings:flags.2?WallPaperSettings = WallPaper;
-wallPaperNoFile#e0804116 id:long flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;
-
-inputReportReasonSpam#58dbcab8 = ReportReason;
-inputReportReasonViolence#1e22c78d = ReportReason;
-inputReportReasonPornography#2e59d922 = ReportReason;
-inputReportReasonChildAbuse#adf44ee3 = ReportReason;
-inputReportReasonOther#c1e4a2b1 = ReportReason;
-inputReportReasonCopyright#9b89f93a = ReportReason;
-inputReportReasonGeoIrrelevant#dbd4feed = ReportReason;
-inputReportReasonFake#f5ddd6e7 = ReportReason;
-
-userFull#d697ff05 flags:# blocked:flags.0?true phone_calls_available:flags.4?true phone_calls_private:flags.5?true can_pin_message:flags.7?true has_scheduled:flags.12?true video_calls_available:flags.13?true user:User about:flags.1?string settings:PeerSettings profile_photo:flags.2?Photo notify_settings:PeerNotifySettings bot_info:flags.3?BotInfo pinned_msg_id:flags.6?int common_chats_count:int folder_id:flags.11?int ttl_period:flags.14?int theme_emoticon:flags.15?string = UserFull;
-
-contact#145ade0b user_id:long mutual:Bool = Contact;
-
-importedContact#c13e3c50 user_id:long client_id:long = ImportedContact;
-
-contactStatus#16d9703b user_id:long status:UserStatus = ContactStatus;
-
-contacts.contactsNotModified#b74ba9d2 = contacts.Contacts;
-contacts.contacts#eae87e42 contacts:Vector<Contact> saved_count:int users:Vector<User> = contacts.Contacts;
-
-contacts.importedContacts#77d01c3b imported:Vector<ImportedContact> popular_invites:Vector<PopularContact> retry_contacts:Vector<long> users:Vector<User> = contacts.ImportedContacts;
-
-contacts.blocked#ade1591 blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
-contacts.blockedSlice#e1664194 count:int blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
-
-messages.dialogs#15ba6c40 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;
-messages.dialogsSlice#71e094f3 count:int dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;
-messages.dialogsNotModified#f0e3e596 count:int = messages.Dialogs;
-
-messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
-
-messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
-messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
-
-messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.ChatFull;
-
-messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
-
-inputMessagesFilterEmpty#57e2f66c = MessagesFilter;
-inputMessagesFilterPhotos#9609a51c = MessagesFilter;
-inputMessagesFilterVideo#9fc00e65 = MessagesFilter;
-inputMessagesFilterPhotoVideo#56e9f0e4 = MessagesFilter;
-inputMessagesFilterDocument#9eddf188 = MessagesFilter;
-inputMessagesFilterUrl#7ef0dd87 = MessagesFilter;
-inputMessagesFilterGif#ffc86587 = MessagesFilter;
-inputMessagesFilterVoice#50f5c392 = MessagesFilter;
-inputMessagesFilterMusic#3751b49e = MessagesFilter;
-inputMessagesFilterChatPhotos#3a20ecb8 = MessagesFilter;
-inputMessagesFilterPhoneCalls#80c99768 flags:# missed:flags.0?true = MessagesFilter;
-inputMessagesFilterRoundVoice#7a7c17a4 = MessagesFilter;
-inputMessagesFilterRoundVideo#b549da53 = MessagesFilter;
-inputMessagesFilterMyMentions#c1f8e69a = MessagesFilter;
-inputMessagesFilterGeo#e7026d0d = MessagesFilter;
-inputMessagesFilterContacts#e062db83 = MessagesFilter;
-inputMessagesFilterPinned#1bb00451 = MessagesFilter;
-
-updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
-updateMessageID#4e90bfd6 id:int random_id:long = Update;
-updateDeleteMessages#a20db0e5 messages:Vector<int> pts:int pts_count:int = Update;
-updateUserTyping#c01e857f user_id:long action:SendMessageAction = Update;
-updateChatUserTyping#83487af0 chat_id:long from_id:Peer action:SendMessageAction = Update;
-updateChatParticipants#7761198 participants:ChatParticipants = Update;
-updateUserStatus#e5bdf8de user_id:long status:UserStatus = Update;
-updateUserName#c3f202e0 user_id:long first_name:string last_name:string username:string = Update;
-updateUserPhoto#f227868c user_id:long date:int photo:UserProfilePhoto previous:Bool = Update;
-updateNewEncryptedMessage#12bcbd9a message:EncryptedMessage qts:int = Update;
-updateEncryptedChatTyping#1710f156 chat_id:int = Update;
-updateEncryption#b4a2e88d chat:EncryptedChat date:int = Update;
-updateEncryptedMessagesRead#38fe25b7 chat_id:int max_date:int date:int = Update;
-updateChatParticipantAdd#3dda5451 chat_id:long user_id:long inviter_id:long date:int version:int = Update;
-updateChatParticipantDelete#e32f3d77 chat_id:long user_id:long version:int = Update;
-updateDcOptions#8e5e9873 dc_options:Vector<DcOption> = Update;
-updateNotifySettings#bec268ef peer:NotifyPeer notify_settings:PeerNotifySettings = Update;
-updateServiceNotification#ebe46819 flags:# popup:flags.0?true inbox_date:flags.1?int type:string message:string media:MessageMedia entities:Vector<MessageEntity> = Update;
-updatePrivacy#ee3b272a key:PrivacyKey rules:Vector<PrivacyRule> = Update;
-updateUserPhone#5492a13 user_id:long phone:string = Update;
-updateReadHistoryInbox#9c974fdf flags:# folder_id:flags.0?int peer:Peer max_id:int still_unread_count:int pts:int pts_count:int = Update;
-updateReadHistoryOutbox#2f2f21bf peer:Peer max_id:int pts:int pts_count:int = Update;
-updateWebPage#7f891213 webpage:WebPage pts:int pts_count:int = Update;
-updateReadMessagesContents#68c13933 messages:Vector<int> pts:int pts_count:int = Update;
-updateChannelTooLong#108d941f flags:# channel_id:long pts:flags.0?int = Update;
-updateChannel#635b4c09 channel_id:long = Update;
-updateNewChannelMessage#62ba04d9 message:Message pts:int pts_count:int = Update;
-updateReadChannelInbox#922e6e10 flags:# folder_id:flags.0?int channel_id:long max_id:int still_unread_count:int pts:int = Update;
-updateDeleteChannelMessages#c32d5b12 channel_id:long messages:Vector<int> pts:int pts_count:int = Update;
-updateChannelMessageViews#f226ac08 channel_id:long id:int views:int = Update;
-updateChatParticipantAdmin#d7ca61a2 chat_id:long user_id:long is_admin:Bool version:int = Update;
-updateNewStickerSet#688a30aa stickerset:messages.StickerSet = Update;
-updateStickerSetsOrder#bb2d201 flags:# masks:flags.0?true order:Vector<long> = Update;
-updateStickerSets#43ae3dec = Update;
-updateSavedGifs#9375341e = Update;
-updateBotInlineQuery#496f379c flags:# query_id:long user_id:long query:string geo:flags.0?GeoPoint peer_type:flags.1?InlineQueryPeerType offset:string = Update;
-updateBotInlineSend#12f12a07 flags:# user_id:long query:string geo:flags.0?GeoPoint id:string msg_id:flags.1?InputBotInlineMessageID = Update;
-updateEditChannelMessage#1b3f4df7 message:Message pts:int pts_count:int = Update;
-updateBotCallbackQuery#b9cfc48d flags:# query_id:long user_id:long peer:Peer msg_id:int chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
-updateEditMessage#e40370a3 message:Message pts:int pts_count:int = Update;
-updateInlineBotCallbackQuery#691e9052 flags:# query_id:long user_id:long msg_id:InputBotInlineMessageID chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
-updateReadChannelOutbox#b75f99a9 channel_id:long max_id:int = Update;
-updateDraftMessage#ee2bb969 peer:Peer draft:DraftMessage = Update;
-updateReadFeaturedStickers#571d2742 = Update;
-updateRecentStickers#9a422c20 = Update;
-updateConfig#a229dd06 = Update;
-updatePtsChanged#3354678f = Update;
-updateChannelWebPage#2f2ba99f channel_id:long webpage:WebPage pts:int pts_count:int = Update;
-updateDialogPinned#6e6fe51c flags:# pinned:flags.0?true folder_id:flags.1?int peer:DialogPeer = Update;
-updatePinnedDialogs#fa0f3ca2 flags:# folder_id:flags.1?int order:flags.0?Vector<DialogPeer> = Update;
-updateBotWebhookJSON#8317c0c3 data:DataJSON = Update;
-updateBotWebhookJSONQuery#9b9240a6 query_id:long data:DataJSON timeout:int = Update;
-updateBotShippingQuery#b5aefd7d query_id:long user_id:long payload:bytes shipping_address:PostAddress = Update;
-updateBotPrecheckoutQuery#8caa9a96 flags:# query_id:long user_id:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string currency:string total_amount:long = Update;
-updatePhoneCall#ab0f6b1e phone_call:PhoneCall = Update;
-updateLangPackTooLong#46560264 lang_code:string = Update;
-updateLangPack#56022f4d difference:LangPackDifference = Update;
-updateFavedStickers#e511996d = Update;
-updateChannelReadMessagesContents#44bdd535 channel_id:long messages:Vector<int> = Update;
-updateContactsReset#7084a7be = Update;
-updateChannelAvailableMessages#b23fc698 channel_id:long available_min_id:int = Update;
-updateDialogUnreadMark#e16459c3 flags:# unread:flags.0?true peer:DialogPeer = Update;
-updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;
-updateChatDefaultBannedRights#54c01850 peer:Peer default_banned_rights:ChatBannedRights version:int = Update;
-updateFolderPeers#19360dc0 folder_peers:Vector<FolderPeer> pts:int pts_count:int = Update;
-updatePeerSettings#6a7e7366 peer:Peer settings:PeerSettings = Update;
-updatePeerLocated#b4afcfb0 peers:Vector<PeerLocated> = Update;
-updateNewScheduledMessage#39a51dfb message:Message = Update;
-updateDeleteScheduledMessages#90866cee peer:Peer messages:Vector<int> = Update;
-updateTheme#8216fba3 theme:Theme = Update;
-updateGeoLiveViewed#871fb939 peer:Peer msg_id:int = Update;
-updateLoginToken#564fe691 = Update;
-updateMessagePollVote#106395c9 poll_id:long user_id:long options:Vector<bytes> qts:int = Update;
-updateDialogFilter#26ffde7d flags:# id:int filter:flags.0?DialogFilter = Update;
-updateDialogFilterOrder#a5d72105 order:Vector<int> = Update;
-updateDialogFilters#3504914f = Update;
-updatePhoneCallSignalingData#2661bf09 phone_call_id:long data:bytes = Update;
-updateChannelMessageForwards#d29a27f4 channel_id:long id:int forwards:int = Update;
-updateReadChannelDiscussionInbox#d6b19546 flags:# channel_id:long top_msg_id:int read_max_id:int broadcast_id:flags.0?long broadcast_post:flags.0?int = Update;
-updateReadChannelDiscussionOutbox#695c9e7c channel_id:long top_msg_id:int read_max_id:int = Update;
-updatePeerBlocked#246a4b22 peer_id:Peer blocked:Bool = Update;
-updateChannelUserTyping#8c88c923 flags:# channel_id:long top_msg_id:flags.0?int from_id:Peer action:SendMessageAction = Update;
-updatePinnedMessages#ed85eab5 flags:# pinned:flags.0?true peer:Peer messages:Vector<int> pts:int pts_count:int = Update;
-updatePinnedChannelMessages#5bb98608 flags:# pinned:flags.0?true channel_id:long messages:Vector<int> pts:int pts_count:int = Update;
-updateChat#f89a6a4e chat_id:long = Update;
-updateGroupCallParticipants#f2ebdb4e call:InputGroupCall participants:Vector<GroupCallParticipant> version:int = Update;
-updateGroupCall#14b24500 chat_id:long call:GroupCall = Update;
-updatePeerHistoryTTL#bb9bb9a5 flags:# peer:Peer ttl_period:flags.0?int = Update;
-updateChatParticipant#d087663a flags:# chat_id:long date:int actor_id:long user_id:long prev_participant:flags.0?ChatParticipant new_participant:flags.1?ChatParticipant invite:flags.2?ExportedChatInvite qts:int = Update;
-updateChannelParticipant#985d3abb flags:# channel_id:long date:int actor_id:long user_id:long prev_participant:flags.0?ChannelParticipant new_participant:flags.1?ChannelParticipant invite:flags.2?ExportedChatInvite qts:int = Update;
-updateBotStopped#c4870a49 user_id:long date:int stopped:Bool qts:int = Update;
-updateGroupCallConnection#b783982 flags:# presentation:flags.0?true params:DataJSON = Update;
-updateBotCommands#4d712f2e peer:Peer bot_id:long commands:Vector<BotCommand> = Update;
-
-updates.state#a56c2a3e pts:int qts:int date:int seq:int unread_count:int = updates.State;
-
-updates.differenceEmpty#5d75a138 date:int seq:int = updates.Difference;
-updates.difference#f49ca0 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> state:updates.State = updates.Difference;
-updates.differenceSlice#a8fb1981 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> intermediate_state:updates.State = updates.Difference;
-updates.differenceTooLong#4afe8f6d pts:int = updates.Difference;
-
-updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-
-photos.photos#8dca6aa5 photos:Vector<Photo> users:Vector<User> = photos.Photos;
-photos.photosSlice#15051f54 count:int photos:Vector<Photo> users:Vector<User> = photos.Photos;
-
-photos.photo#20212ca8 photo:Photo users:Vector<User> = photos.Photo;
-
-upload.file#96a18d5 type:storage.FileType mtime:int bytes:bytes = upload.File;
-upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;
-
-dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;
-
-config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;
-
-nearestDc#8e1a1775 country:string this_dc:int nearest_dc:int = NearestDc;
-
-help.appUpdate#ccbbce30 flags:# can_not_skip:flags.0?true id:int version:string text:string entities:Vector<MessageEntity> document:flags.1?Document url:flags.2?string sticker:flags.3?Document = help.AppUpdate;
-help.noAppUpdate#c45a6536 = help.AppUpdate;
-
-help.inviteText#18cb9f78 message:string = help.InviteText;
-
-encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;
-encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;
-encryptedChatRequested#48f1d94c flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:long participant_id:long g_a:bytes = EncryptedChat;
-encryptedChat#61f0d4c7 id:int access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long = EncryptedChat;
-encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;
-
-inputEncryptedChat#f141b5e1 chat_id:int access_hash:long = InputEncryptedChat;
-
-encryptedFileEmpty#c21f497e = EncryptedFile;
-encryptedFile#4a70994c id:long access_hash:long size:int dc_id:int key_fingerprint:int = EncryptedFile;
-
-inputEncryptedFileEmpty#1837c364 = InputEncryptedFile;
-inputEncryptedFileUploaded#64bd0306 id:long parts:int md5_checksum:string key_fingerprint:int = InputEncryptedFile;
-inputEncryptedFile#5a17b5e5 id:long access_hash:long = InputEncryptedFile;
-inputEncryptedFileBigUploaded#2dc173c8 id:long parts:int key_fingerprint:int = InputEncryptedFile;
-
-encryptedMessage#ed18c118 random_id:long chat_id:int date:int bytes:bytes file:EncryptedFile = EncryptedMessage;
-encryptedMessageService#23734b06 random_id:long chat_id:int date:int bytes:bytes = EncryptedMessage;
-
-messages.dhConfigNotModified#c0e24635 random:bytes = messages.DhConfig;
-messages.dhConfig#2c221edd g:int p:bytes version:int random:bytes = messages.DhConfig;
-
-messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;
-messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;
-
-inputDocumentEmpty#72f0eaae = InputDocument;
-inputDocument#1abfb575 id:long access_hash:long file_reference:bytes = InputDocument;
-
-documentEmpty#36f8c871 id:long = Document;
-document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
-
-help.support#17c6b5f6 phone_number:string user:User = help.Support;
-
-notifyPeer#9fd40bd8 peer:Peer = NotifyPeer;
-notifyUsers#b4c83b4c = NotifyPeer;
-notifyChats#c007cec3 = NotifyPeer;
-notifyBroadcasts#d612e8ef = NotifyPeer;
-
-sendMessageTypingAction#16bf744e = SendMessageAction;
-sendMessageCancelAction#fd5ec8f5 = SendMessageAction;
-sendMessageRecordVideoAction#a187d66f = SendMessageAction;
-sendMessageUploadVideoAction#e9763aec progress:int = SendMessageAction;
-sendMessageRecordAudioAction#d52f73f7 = SendMessageAction;
-sendMessageUploadAudioAction#f351d7ab progress:int = SendMessageAction;
-sendMessageUploadPhotoAction#d1d34a26 progress:int = SendMessageAction;
-sendMessageUploadDocumentAction#aa0cd9e4 progress:int = SendMessageAction;
-sendMessageGeoLocationAction#176f8ba1 = SendMessageAction;
-sendMessageChooseContactAction#628cbc6f = SendMessageAction;
-sendMessageGamePlayAction#dd6a8f48 = SendMessageAction;
-sendMessageRecordRoundAction#88f27fbc = SendMessageAction;
-sendMessageUploadRoundAction#243e1c66 progress:int = SendMessageAction;
-speakingInGroupCallAction#d92c2285 = SendMessageAction;
-sendMessageHistoryImportAction#dbda9246 progress:int = SendMessageAction;
-sendMessageChooseStickerAction#b05ac6b1 = SendMessageAction;
-sendMessageEmojiInteraction#25972bcb emoticon:string msg_id:int interaction:DataJSON = SendMessageAction;
-sendMessageEmojiInteractionSeen#b665902e emoticon:string = SendMessageAction;
-
-contacts.found#b3134d9d my_results:Vector<Peer> results:Vector<Peer> chats:Vector<Chat> users:Vector<User> = contacts.Found;
-
-inputPrivacyKeyStatusTimestamp#4f96cb18 = InputPrivacyKey;
-inputPrivacyKeyChatInvite#bdfb0426 = InputPrivacyKey;
-inputPrivacyKeyPhoneCall#fabadc5f = InputPrivacyKey;
-inputPrivacyKeyPhoneP2P#db9e70d2 = InputPrivacyKey;
-inputPrivacyKeyForwards#a4dd4c08 = InputPrivacyKey;
-inputPrivacyKeyProfilePhoto#5719bacc = InputPrivacyKey;
-inputPrivacyKeyPhoneNumber#352dafa = InputPrivacyKey;
-inputPrivacyKeyAddedByPhone#d1219bdd = InputPrivacyKey;
-
-privacyKeyStatusTimestamp#bc2eab30 = PrivacyKey;
-privacyKeyChatInvite#500e6dfa = PrivacyKey;
-privacyKeyPhoneCall#3d662b7b = PrivacyKey;
-privacyKeyPhoneP2P#39491cc8 = PrivacyKey;
-privacyKeyForwards#69ec56a3 = PrivacyKey;
-privacyKeyProfilePhoto#96151fed = PrivacyKey;
-privacyKeyPhoneNumber#d19ae46d = PrivacyKey;
-privacyKeyAddedByPhone#42ffd42b = PrivacyKey;
-
-inputPrivacyValueAllowContacts#d09e07b = InputPrivacyRule;
-inputPrivacyValueAllowAll#184b35ce = InputPrivacyRule;
-inputPrivacyValueAllowUsers#131cc67f users:Vector<InputUser> = InputPrivacyRule;
-inputPrivacyValueDisallowContacts#ba52007 = InputPrivacyRule;
-inputPrivacyValueDisallowAll#d66b66c9 = InputPrivacyRule;
-inputPrivacyValueDisallowUsers#90110467 users:Vector<InputUser> = InputPrivacyRule;
-inputPrivacyValueAllowChatParticipants#840649cf chats:Vector<long> = InputPrivacyRule;
-inputPrivacyValueDisallowChatParticipants#e94f0f86 chats:Vector<long> = InputPrivacyRule;
-
-privacyValueAllowContacts#fffe1bac = PrivacyRule;
-privacyValueAllowAll#65427b82 = PrivacyRule;
-privacyValueAllowUsers#b8905fb2 users:Vector<long> = PrivacyRule;
-privacyValueDisallowContacts#f888fa1a = PrivacyRule;
-privacyValueDisallowAll#8b73e763 = PrivacyRule;
-privacyValueDisallowUsers#e4621141 users:Vector<long> = PrivacyRule;
-privacyValueAllowChatParticipants#6b134e8e chats:Vector<long> = PrivacyRule;
-privacyValueDisallowChatParticipants#41c87565 chats:Vector<long> = PrivacyRule;
-
-account.privacyRules#50a04e45 rules:Vector<PrivacyRule> chats:Vector<Chat> users:Vector<User> = account.PrivacyRules;
-
-accountDaysTTL#b8d0afdf days:int = AccountDaysTTL;
-
-documentAttributeImageSize#6c37c15c w:int h:int = DocumentAttribute;
-documentAttributeAnimated#11b58939 = DocumentAttribute;
-documentAttributeSticker#6319d612 flags:# mask:flags.1?true alt:string stickerset:InputStickerSet mask_coords:flags.0?MaskCoords = DocumentAttribute;
-documentAttributeVideo#ef02ce6 flags:# round_message:flags.0?true supports_streaming:flags.1?true duration:int w:int h:int = DocumentAttribute;
-documentAttributeAudio#9852f9c6 flags:# voice:flags.10?true duration:int title:flags.0?string performer:flags.1?string waveform:flags.2?bytes = DocumentAttribute;
-documentAttributeFilename#15590068 file_name:string = DocumentAttribute;
-documentAttributeHasStickers#9801d2f7 = DocumentAttribute;
-
-messages.stickersNotModified#f1749a22 = messages.Stickers;
-messages.stickers#30a6ec7e hash:long stickers:Vector<Document> = messages.Stickers;
-
-stickerPack#12b299d4 emoticon:string documents:Vector<long> = StickerPack;
-
-messages.allStickersNotModified#e86602c3 = messages.AllStickers;
-messages.allStickers#cdbbcebb hash:long sets:Vector<StickerSet> = messages.AllStickers;
-
-messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;
-
-webPageEmpty#eb1477e8 id:long = WebPage;
-webPagePending#c586da1c id:long date:int = WebPage;
-webPage#e89c45b2 flags:# id:long url:string display_url:string hash:int type:flags.0?string site_name:flags.1?string title:flags.2?string description:flags.3?string photo:flags.4?Photo embed_url:flags.5?string embed_type:flags.5?string embed_width:flags.6?int embed_height:flags.6?int duration:flags.7?int author:flags.8?string document:flags.9?Document cached_page:flags.10?Page attributes:flags.12?Vector<WebPageAttribute> = WebPage;
-webPageNotModified#7311ca11 flags:# cached_page_views:flags.0?int = WebPage;
-
-authorization#ad01d61d flags:# current:flags.0?true official_app:flags.1?true password_pending:flags.2?true encrypted_requests_disabled:flags.3?true call_requests_disabled:flags.4?true hash:long device_model:string platform:string system_version:string api_id:int app_name:string app_version:string date_created:int date_active:int ip:string country:string region:string = Authorization;
-
-account.authorizations#1250abde authorizations:Vector<Authorization> = account.Authorizations;
-
-account.password#185b184f flags:# has_recovery:flags.0?true has_secure_values:flags.1?true has_password:flags.2?true current_algo:flags.2?PasswordKdfAlgo srp_B:flags.2?bytes srp_id:flags.2?long hint:flags.3?string email_unconfirmed_pattern:flags.4?string new_algo:PasswordKdfAlgo new_secure_algo:SecurePasswordKdfAlgo secure_random:bytes pending_reset_date:flags.5?int = account.Password;
-
-account.passwordSettings#9a5c33e5 flags:# email:flags.0?string secure_settings:flags.1?SecureSecretSettings = account.PasswordSettings;
-
-account.passwordInputSettings#c23727c9 flags:# new_algo:flags.0?PasswordKdfAlgo new_password_hash:flags.0?bytes hint:flags.0?string email:flags.1?string new_secure_settings:flags.2?SecureSecretSettings = account.PasswordInputSettings;
-
-auth.passwordRecovery#137948a5 email_pattern:string = auth.PasswordRecovery;
-
-receivedNotifyMessage#a384b779 id:int flags:int = ReceivedNotifyMessage;
-
-chatInviteExported#b18105e8 flags:# revoked:flags.0?true permanent:flags.5?true link:string admin_id:long date:int start_date:flags.4?int expire_date:flags.1?int usage_limit:flags.2?int usage:flags.3?int = ExportedChatInvite;
-
-chatInviteAlready#5a686d7c chat:Chat = ChatInvite;
-chatInvite#dfc2f58e flags:# channel:flags.0?true broadcast:flags.1?true public:flags.2?true megagroup:flags.3?true title:string photo:Photo participants_count:int participants:flags.4?Vector<User> = ChatInvite;
-chatInvitePeek#61695cb0 chat:Chat expires:int = ChatInvite;
-
-inputStickerSetEmpty#ffb62b95 = InputStickerSet;
-inputStickerSetID#9de7a269 id:long access_hash:long = InputStickerSet;
-inputStickerSetShortName#861cc8a0 short_name:string = InputStickerSet;
-inputStickerSetAnimatedEmoji#28703c8 = InputStickerSet;
-inputStickerSetDice#e67f520e emoticon:string = InputStickerSet;
-inputStickerSetAnimatedEmojiAnimations#cde3739 = InputStickerSet;
-
-stickerSet#d7df217a flags:# archived:flags.1?true official:flags.2?true masks:flags.3?true animated:flags.5?true videos:flags.6?true installed_date:flags.0?int id:long access_hash:long title:string short_name:string thumbs:flags.4?Vector<PhotoSize> thumb_dc_id:flags.4?int thumb_version:flags.4?int count:int hash:int = StickerSet;
-
-messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
-
-botCommand#c27ac8c7 command:string description:string = BotCommand;
-
-botInfo#1b74b335 user_id:long description:string commands:Vector<BotCommand> = BotInfo;
-
-keyboardButton#a2fa4880 text:string = KeyboardButton;
-keyboardButtonUrl#258aff05 text:string url:string = KeyboardButton;
-keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;
-keyboardButtonRequestPhone#b16a6c29 text:string = KeyboardButton;
-keyboardButtonRequestGeoLocation#fc796b3f text:string = KeyboardButton;
-keyboardButtonSwitchInline#568a748 flags:# same_peer:flags.0?true text:string query:string = KeyboardButton;
-keyboardButtonGame#50f41ccf text:string = KeyboardButton;
-keyboardButtonBuy#afd93fbb text:string = KeyboardButton;
-keyboardButtonUrlAuth#10b78d29 flags:# text:string fwd_text:flags.0?string url:string button_id:int = KeyboardButton;
-inputKeyboardButtonUrlAuth#d02e7fd4 flags:# request_write_access:flags.0?true text:string fwd_text:flags.1?string url:string bot:InputUser = KeyboardButton;
-keyboardButtonRequestPoll#bbc7515d flags:# quiz:flags.0?Bool text:string = KeyboardButton;
-
-keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;
-
-replyKeyboardHide#a03e5b85 flags:# selective:flags.2?true = ReplyMarkup;
-replyKeyboardForceReply#86b40b08 flags:# single_use:flags.1?true selective:flags.2?true placeholder:flags.3?string = ReplyMarkup;
-replyKeyboardMarkup#85dd99d1 flags:# resize:flags.0?true single_use:flags.1?true selective:flags.2?true rows:Vector<KeyboardButtonRow> placeholder:flags.3?string = ReplyMarkup;
-replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;
-
-messageEntityUnknown#bb92ba95 offset:int length:int = MessageEntity;
-messageEntityMention#fa04579d offset:int length:int = MessageEntity;
-messageEntityHashtag#6f635b0d offset:int length:int = MessageEntity;
-messageEntityBotCommand#6cef8ac7 offset:int length:int = MessageEntity;
-messageEntityUrl#6ed02538 offset:int length:int = MessageEntity;
-messageEntityEmail#64e475c2 offset:int length:int = MessageEntity;
-messageEntityBold#bd610bc9 offset:int length:int = MessageEntity;
-messageEntityItalic#826f8b60 offset:int length:int = MessageEntity;
-messageEntityCode#28a20571 offset:int length:int = MessageEntity;
-messageEntityPre#73924be0 offset:int length:int language:string = MessageEntity;
-messageEntityTextUrl#76a6d327 offset:int length:int url:string = MessageEntity;
-messageEntityMentionName#dc7b1140 offset:int length:int user_id:long = MessageEntity;
-inputMessageEntityMentionName#208e68c9 offset:int length:int user_id:InputUser = MessageEntity;
-messageEntityPhone#9b69e34b offset:int length:int = MessageEntity;
-messageEntityCashtag#4c4e743f offset:int length:int = MessageEntity;
-messageEntityUnderline#9c4e7e8b offset:int length:int = MessageEntity;
-messageEntityStrike#bf0693d4 offset:int length:int = MessageEntity;
-messageEntityBlockquote#20df5d0 offset:int length:int = MessageEntity;
-messageEntityBankCard#761e6af4 offset:int length:int = MessageEntity;
-
-inputChannelEmpty#ee8c1e86 = InputChannel;
-inputChannel#f35aec28 channel_id:long access_hash:long = InputChannel;
-inputChannelFromMessage#5b934f9d peer:InputPeer msg_id:int channel_id:long = InputChannel;
-
-contacts.resolvedPeer#7f077ad9 peer:Peer chats:Vector<Chat> users:Vector<User> = contacts.ResolvedPeer;
-
-messageRange#ae30253 min_id:int max_id:int = MessageRange;
-
-updates.channelDifferenceEmpty#3e11affb flags:# final:flags.0?true pts:int timeout:flags.1?int = updates.ChannelDifference;
-updates.channelDifferenceTooLong#a4bcc6fe flags:# final:flags.0?true timeout:flags.1?int dialog:Dialog messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
-updates.channelDifference#2064674e flags:# final:flags.0?true pts:int timeout:flags.1?int new_messages:Vector<Message> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
-
-channelMessagesFilterEmpty#94d42ee7 = ChannelMessagesFilter;
-channelMessagesFilter#cd77d957 flags:# exclude_new_messages:flags.1?true ranges:Vector<MessageRange> = ChannelMessagesFilter;
-
-channelParticipant#c00c07c0 user_id:long date:int = ChannelParticipant;
-channelParticipantSelf#28a8bc67 user_id:long inviter_id:long date:int = ChannelParticipant;
-channelParticipantCreator#2fe601d3 flags:# user_id:long admin_rights:ChatAdminRights rank:flags.0?string = ChannelParticipant;
-channelParticipantAdmin#34c3bb53 flags:# can_edit:flags.0?true self:flags.1?true user_id:long inviter_id:flags.1?long promoted_by:long date:int admin_rights:ChatAdminRights rank:flags.2?string = ChannelParticipant;
-channelParticipantBanned#6df8014e flags:# left:flags.0?true peer:Peer kicked_by:long date:int banned_rights:ChatBannedRights = ChannelParticipant;
-channelParticipantLeft#1b03f006 peer:Peer = ChannelParticipant;
-
-channelParticipantsRecent#de3f3c79 = ChannelParticipantsFilter;
-channelParticipantsAdmins#b4608969 = ChannelParticipantsFilter;
-channelParticipantsKicked#a3b54985 q:string = ChannelParticipantsFilter;
-channelParticipantsBots#b0d1865b = ChannelParticipantsFilter;
-channelParticipantsBanned#1427a5e1 q:string = ChannelParticipantsFilter;
-channelParticipantsSearch#656ac4b q:string = ChannelParticipantsFilter;
-channelParticipantsContacts#bb6ae88d q:string = ChannelParticipantsFilter;
-channelParticipantsMentions#e04b5ceb flags:# q:flags.0?string top_msg_id:flags.1?int = ChannelParticipantsFilter;
-
-channels.channelParticipants#9ab0feaf count:int participants:Vector<ChannelParticipant> chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipants;
-channels.channelParticipantsNotModified#f0173fe9 = channels.ChannelParticipants;
-
-channels.channelParticipant#dfb80317 participant:ChannelParticipant chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipant;
-
-help.termsOfService#780a0310 flags:# popup:flags.0?true id:DataJSON text:string entities:Vector<MessageEntity> min_age_confirm:flags.1?int = help.TermsOfService;
-
-messages.savedGifsNotModified#e8025ca2 = messages.SavedGifs;
-messages.savedGifs#84a02a0d hash:long gifs:Vector<Document> = messages.SavedGifs;
-
-inputBotInlineMessageMediaAuto#3380c786 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageText#3dcd7a87 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageMediaGeo#96929a85 flags:# geo_point:InputGeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageMediaVenue#417bbf11 flags:# geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageMediaContact#a6edbffd flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageGame#4b425864 flags:# reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageMediaInvoice#d7e78225 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-
-inputBotInlineResult#88bf9319 flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?InputWebDocument content:flags.5?InputWebDocument send_message:InputBotInlineMessage = InputBotInlineResult;
-inputBotInlineResultPhoto#a8d864a7 id:string type:string photo:InputPhoto send_message:InputBotInlineMessage = InputBotInlineResult;
-inputBotInlineResultDocument#fff8fdc4 flags:# id:string type:string title:flags.1?string description:flags.2?string document:InputDocument send_message:InputBotInlineMessage = InputBotInlineResult;
-inputBotInlineResultGame#4fa417f2 id:string short_name:string send_message:InputBotInlineMessage = InputBotInlineResult;
-
-botInlineMessageMediaAuto#764cf810 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-botInlineMessageText#8c7f65e2 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-botInlineMessageMediaGeo#51846fd flags:# geo:GeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-botInlineMessageMediaVenue#8a86659c flags:# geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-botInlineMessageMediaContact#18d1cdc2 flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-botInlineMessageMediaInvoice#354a9b09 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument currency:string total_amount:long reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-
-botInlineResult#11965f3a flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?WebDocument content:flags.5?WebDocument send_message:BotInlineMessage = BotInlineResult;
-botInlineMediaResult#17db940b flags:# id:string type:string photo:flags.0?Photo document:flags.1?Document title:flags.2?string description:flags.3?string send_message:BotInlineMessage = BotInlineResult;
-
-messages.botResults#947ca848 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;
-
-exportedMessageLink#5dab1af4 link:string html:string = ExportedMessageLink;
-
-messageFwdHeader#5f777dce flags:# imported:flags.7?true from_id:flags.0?Peer from_name:flags.5?string date:int channel_post:flags.2?int post_author:flags.3?string saved_from_peer:flags.4?Peer saved_from_msg_id:flags.4?int psa_type:flags.6?string = MessageFwdHeader;
-
-auth.codeTypeSms#72a3158c = auth.CodeType;
-auth.codeTypeCall#741cd3e3 = auth.CodeType;
-auth.codeTypeFlashCall#226ccefb = auth.CodeType;
-
-auth.sentCodeTypeApp#3dbb5986 length:int = auth.SentCodeType;
-auth.sentCodeTypeSms#c000bba2 length:int = auth.SentCodeType;
-auth.sentCodeTypeCall#5353e5a7 length:int = auth.SentCodeType;
-auth.sentCodeTypeFlashCall#ab03c6d9 pattern:string = auth.SentCodeType;
-
-messages.botCallbackAnswer#36585ea4 flags:# alert:flags.1?true has_url:flags.3?true native_ui:flags.4?true message:flags.0?string url:flags.2?string cache_time:int = messages.BotCallbackAnswer;
-
-messages.messageEditData#26b5dde6 flags:# caption:flags.0?true = messages.MessageEditData;
-
-inputBotInlineMessageID#890c3d89 dc_id:int id:long access_hash:long = InputBotInlineMessageID;
-inputBotInlineMessageID64#b6d915d7 dc_id:int owner_id:long id:int access_hash:long = InputBotInlineMessageID;
-
-inlineBotSwitchPM#3c20629f text:string start_param:string = InlineBotSwitchPM;
-
-messages.peerDialogs#3371c354 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> state:updates.State = messages.PeerDialogs;
-
-topPeer#edcdc05b peer:Peer rating:double = TopPeer;
-
-topPeerCategoryBotsPM#ab661b5b = TopPeerCategory;
-topPeerCategoryBotsInline#148677e2 = TopPeerCategory;
-topPeerCategoryCorrespondents#637b7ed = TopPeerCategory;
-topPeerCategoryGroups#bd17a14a = TopPeerCategory;
-topPeerCategoryChannels#161d9628 = TopPeerCategory;
-topPeerCategoryPhoneCalls#1e76a78c = TopPeerCategory;
-topPeerCategoryForwardUsers#a8406ca9 = TopPeerCategory;
-topPeerCategoryForwardChats#fbeec0f0 = TopPeerCategory;
-
-topPeerCategoryPeers#fb834291 category:TopPeerCategory count:int peers:Vector<TopPeer> = TopPeerCategoryPeers;
-
-contacts.topPeersNotModified#de266ef5 = contacts.TopPeers;
-contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;
-contacts.topPeersDisabled#b52c939d = contacts.TopPeers;
-
-draftMessageEmpty#1b0c841a flags:# date:flags.0?int = DraftMessage;
-draftMessage#fd8e711f flags:# no_webpage:flags.1?true reply_to_msg_id:flags.0?int message:string entities:flags.3?Vector<MessageEntity> date:int = DraftMessage;
-
-messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;
-messages.featuredStickers#84c02310 hash:long count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;
-
-messages.recentStickersNotModified#b17f890 = messages.RecentStickers;
-messages.recentStickers#88d37c56 hash:long packs:Vector<StickerPack> stickers:Vector<Document> dates:Vector<int> = messages.RecentStickers;
-
-messages.archivedStickers#4fcba9c8 count:int sets:Vector<StickerSetCovered> = messages.ArchivedStickers;
-
-messages.stickerSetInstallResultSuccess#38641628 = messages.StickerSetInstallResult;
-messages.stickerSetInstallResultArchive#35e410a8 sets:Vector<StickerSetCovered> = messages.StickerSetInstallResult;
-
-stickerSetCovered#6410a5d2 set:StickerSet cover:Document = StickerSetCovered;
-stickerSetMultiCovered#3407e51b set:StickerSet covers:Vector<Document> = StickerSetCovered;
-
-maskCoords#aed6dbb2 n:int x:double y:double zoom:double = MaskCoords;
-
-inputStickeredMediaPhoto#4a992157 id:InputPhoto = InputStickeredMedia;
-inputStickeredMediaDocument#438865b id:InputDocument = InputStickeredMedia;
-
-game#bdf9653b flags:# id:long access_hash:long short_name:string title:string description:string photo:Photo document:flags.0?Document = Game;
-
-inputGameID#32c3e77 id:long access_hash:long = InputGame;
-inputGameShortName#c331e80a bot_id:InputUser short_name:string = InputGame;
-
-highScore#73a379eb pos:int user_id:long score:int = HighScore;
-
-messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;
-
-textEmpty#dc3d824f = RichText;
-textPlain#744694e0 text:string = RichText;
-textBold#6724abc4 text:RichText = RichText;
-textItalic#d912a59c text:RichText = RichText;
-textUnderline#c12622c4 text:RichText = RichText;
-textStrike#9bf8bb95 text:RichText = RichText;
-textFixed#6c3f19b9 text:RichText = RichText;
-textUrl#3c2884c1 text:RichText url:string webpage_id:long = RichText;
-textEmail#de5a0dd6 text:RichText email:string = RichText;
-textConcat#7e6260d7 texts:Vector<RichText> = RichText;
-textSubscript#ed6a8504 text:RichText = RichText;
-textSuperscript#c7fb5e01 text:RichText = RichText;
-textMarked#34b8621 text:RichText = RichText;
-textPhone#1ccb966a text:RichText phone:string = RichText;
-textImage#81ccf4f document_id:long w:int h:int = RichText;
-textAnchor#35553762 text:RichText name:string = RichText;
-
-pageBlockUnsupported#13567e8a = PageBlock;
-pageBlockTitle#70abc3fd text:RichText = PageBlock;
-pageBlockSubtitle#8ffa9a1f text:RichText = PageBlock;
-pageBlockAuthorDate#baafe5e0 author:RichText published_date:int = PageBlock;
-pageBlockHeader#bfd064ec text:RichText = PageBlock;
-pageBlockSubheader#f12bb6e1 text:RichText = PageBlock;
-pageBlockParagraph#467a0766 text:RichText = PageBlock;
-pageBlockPreformatted#c070d93e text:RichText language:string = PageBlock;
-pageBlockFooter#48870999 text:RichText = PageBlock;
-pageBlockDivider#db20b188 = PageBlock;
-pageBlockAnchor#ce0d37b0 name:string = PageBlock;
-pageBlockList#e4e88011 items:Vector<PageListItem> = PageBlock;
-pageBlockBlockquote#263d7c26 text:RichText caption:RichText = PageBlock;
-pageBlockPullquote#4f4456d3 text:RichText caption:RichText = PageBlock;
-pageBlockPhoto#1759c560 flags:# photo_id:long caption:PageCaption url:flags.0?string webpage_id:flags.0?long = PageBlock;
-pageBlockVideo#7c8fe7b6 flags:# autoplay:flags.0?true loop:flags.1?true video_id:long caption:PageCaption = PageBlock;
-pageBlockCover#39f23300 cover:PageBlock = PageBlock;
-pageBlockEmbed#a8718dc5 flags:# full_width:flags.0?true allow_scrolling:flags.3?true url:flags.1?string html:flags.2?string poster_photo_id:flags.4?long w:flags.5?int h:flags.5?int caption:PageCaption = PageBlock;
-pageBlockEmbedPost#f259a80b url:string webpage_id:long author_photo_id:long author:string date:int blocks:Vector<PageBlock> caption:PageCaption = PageBlock;
-pageBlockCollage#65a0fa4d items:Vector<PageBlock> caption:PageCaption = PageBlock;
-pageBlockSlideshow#31f9590 items:Vector<PageBlock> caption:PageCaption = PageBlock;
-pageBlockChannel#ef1751b5 channel:Chat = PageBlock;
-pageBlockAudio#804361ea audio_id:long caption:PageCaption = PageBlock;
-pageBlockKicker#1e148390 text:RichText = PageBlock;
-pageBlockTable#bf4dea82 flags:# bordered:flags.0?true striped:flags.1?true title:RichText rows:Vector<PageTableRow> = PageBlock;
-pageBlockOrderedList#9a8ae1e1 items:Vector<PageListOrderedItem> = PageBlock;
-pageBlockDetails#76768bed flags:# open:flags.0?true blocks:Vector<PageBlock> title:RichText = PageBlock;
-pageBlockRelatedArticles#16115a96 title:RichText articles:Vector<PageRelatedArticle> = PageBlock;
-pageBlockMap#a44f3ef6 geo:GeoPoint zoom:int w:int h:int caption:PageCaption = PageBlock;
-
-phoneCallDiscardReasonMissed#85e42301 = PhoneCallDiscardReason;
-phoneCallDiscardReasonDisconnect#e095c1a0 = PhoneCallDiscardReason;
-phoneCallDiscardReasonHangup#57adc690 = PhoneCallDiscardReason;
-phoneCallDiscardReasonBusy#faf7e8c9 = PhoneCallDiscardReason;
-
-dataJSON#7d748d04 data:string = DataJSON;
-
-labeledPrice#cb296bf8 label:string amount:long = LabeledPrice;
-
-invoice#cd886e0 flags:# test:flags.0?true name_requested:flags.1?true phone_requested:flags.2?true email_requested:flags.3?true shipping_address_requested:flags.4?true flexible:flags.5?true phone_to_provider:flags.6?true email_to_provider:flags.7?true currency:string prices:Vector<LabeledPrice> max_tip_amount:flags.8?long suggested_tip_amounts:flags.8?Vector<long> = Invoice;
-
-paymentCharge#ea02c27e id:string provider_charge_id:string = PaymentCharge;
-
-postAddress#1e8caaeb street_line1:string street_line2:string city:string state:string country_iso2:string post_code:string = PostAddress;
-
-paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;
-
-paymentSavedCredentialsCard#cdc27a1f id:string title:string = PaymentSavedCredentials;
-
-webDocument#1c570ed1 url:string access_hash:long size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;
-webDocumentNoProxy#f9c8bcc6 url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;
-
-inputWebDocument#9bed434d url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = InputWebDocument;
-
-inputWebFileLocation#c239d686 url:string access_hash:long = InputWebFileLocation;
-inputWebFileGeoPointLocation#9f2221c9 geo_point:InputGeoPoint access_hash:long w:int h:int zoom:int scale:int = InputWebFileLocation;
-
-upload.webFile#21e753bc size:int mime_type:string file_type:storage.FileType mtime:int bytes:bytes = upload.WebFile;
-
-payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
-
-payments.validatedRequestedInfo#d1451883 flags:# id:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = payments.ValidatedRequestedInfo;
-
-payments.paymentResult#4e5f810d updates:Updates = payments.PaymentResult;
-payments.paymentVerificationNeeded#d8411139 url:string = payments.PaymentResult;
-
-payments.paymentReceipt#70c4fe03 flags:# date:int bot_id:long provider_id:long title:string description:string photo:flags.2?WebDocument invoice:Invoice info:flags.0?PaymentRequestedInfo shipping:flags.1?ShippingOption tip_amount:flags.3?long currency:string total_amount:long credentials_title:string users:Vector<User> = payments.PaymentReceipt;
-
-payments.savedInfo#fb8fe43c flags:# has_saved_credentials:flags.1?true saved_info:flags.0?PaymentRequestedInfo = payments.SavedInfo;
-
-inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;
-inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
-inputPaymentCredentialsApplePay#aa1c39f payment_data:DataJSON = InputPaymentCredentials;
-inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;
-
-account.tmpPassword#db64fd34 tmp_password:bytes valid_until:int = account.TmpPassword;
-
-shippingOption#b6213cdf id:string title:string prices:Vector<LabeledPrice> = ShippingOption;
-
-inputStickerSetItem#ffa0a496 flags:# document:InputDocument emoji:string mask_coords:flags.0?MaskCoords = InputStickerSetItem;
-
-inputPhoneCall#1e36fded id:long access_hash:long = InputPhoneCall;
-
-phoneCallEmpty#5366c915 id:long = PhoneCall;
-phoneCallWaiting#c5226f17 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long protocol:PhoneCallProtocol receive_date:flags.0?int = PhoneCall;
-phoneCallRequested#14b0ed0c flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_hash:bytes protocol:PhoneCallProtocol = PhoneCall;
-phoneCallAccepted#3660c311 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_b:bytes protocol:PhoneCallProtocol = PhoneCall;
-phoneCall#967f7c67 flags:# p2p_allowed:flags.5?true video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long protocol:PhoneCallProtocol connections:Vector<PhoneConnection> start_date:int = PhoneCall;
-phoneCallDiscarded#50ca4de1 flags:# need_rating:flags.2?true need_debug:flags.3?true video:flags.6?true id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = PhoneCall;
-
-phoneConnection#9d4c17c0 id:long ip:string ipv6:string port:int peer_tag:bytes = PhoneConnection;
-phoneConnectionWebrtc#635fe375 flags:# turn:flags.0?true stun:flags.1?true id:long ip:string ipv6:string port:int username:string password:string = PhoneConnection;
-
-phoneCallProtocol#fc878fc8 flags:# udp_p2p:flags.0?true udp_reflector:flags.1?true min_layer:int max_layer:int library_versions:Vector<string> = PhoneCallProtocol;
-
-phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;
-
-upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;
-upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;
-
-cdnPublicKey#c982eaba dc_id:int public_key:string = CdnPublicKey;
-
-cdnConfig#5725e40a public_keys:Vector<CdnPublicKey> = CdnConfig;
-
-langPackString#cad181f6 key:string value:string = LangPackString;
-langPackStringPluralized#6c47ac9f flags:# key:string zero_value:flags.0?string one_value:flags.1?string two_value:flags.2?string few_value:flags.3?string many_value:flags.4?string other_value:string = LangPackString;
-langPackStringDeleted#2979eeb2 key:string = LangPackString;
-
-langPackDifference#f385c1f6 lang_code:string from_version:int version:int strings:Vector<LangPackString> = LangPackDifference;
-
-langPackLanguage#eeca5ce3 flags:# official:flags.0?true rtl:flags.2?true beta:flags.3?true name:string native_name:string lang_code:string base_lang_code:flags.1?string plural_code:string strings_count:int translated_count:int translations_url:string = LangPackLanguage;
-
-channelAdminLogEventActionChangeTitle#e6dfb825 prev_value:string new_value:string = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeAbout#55188a2e prev_value:string new_value:string = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeUsername#6a4afc38 prev_value:string new_value:string = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangePhoto#434bd2af prev_photo:Photo new_photo:Photo = ChannelAdminLogEventAction;
-channelAdminLogEventActionToggleInvites#1b7907ae new_value:Bool = ChannelAdminLogEventAction;
-channelAdminLogEventActionToggleSignatures#26ae0971 new_value:Bool = ChannelAdminLogEventAction;
-channelAdminLogEventActionUpdatePinned#e9e82c18 message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionEditMessage#709b2405 prev_message:Message new_message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionDeleteMessage#42e047bb message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantJoin#183040d3 = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantLeave#f89777f2 = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantInvite#e31c34d8 participant:ChannelParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantToggleBan#e6d83d7e prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantToggleAdmin#d5676710 prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeStickerSet#b1c3caa7 prev_stickerset:InputStickerSet new_stickerset:InputStickerSet = ChannelAdminLogEventAction;
-channelAdminLogEventActionTogglePreHistoryHidden#5f5c95f1 new_value:Bool = ChannelAdminLogEventAction;
-channelAdminLogEventActionDefaultBannedRights#2df5fc0a prev_banned_rights:ChatBannedRights new_banned_rights:ChatBannedRights = ChannelAdminLogEventAction;
-channelAdminLogEventActionStopPoll#8f079643 message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeLinkedChat#50c7ac8 prev_value:long new_value:long = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeLocation#e6b76ae prev_value:ChannelLocation new_value:ChannelLocation = ChannelAdminLogEventAction;
-channelAdminLogEventActionToggleSlowMode#53909779 prev_value:int new_value:int = ChannelAdminLogEventAction;
-channelAdminLogEventActionStartGroupCall#23209745 call:InputGroupCall = ChannelAdminLogEventAction;
-channelAdminLogEventActionDiscardGroupCall#db9f9140 call:InputGroupCall = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantMute#f92424d2 participant:GroupCallParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantUnmute#e64429c0 participant:GroupCallParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionToggleGroupCallSetting#56d6a247 join_muted:Bool = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantJoinByInvite#5cdada77 invite:ExportedChatInvite = ChannelAdminLogEventAction;
-channelAdminLogEventActionExportedInviteDelete#5a50fca4 invite:ExportedChatInvite = ChannelAdminLogEventAction;
-channelAdminLogEventActionExportedInviteRevoke#410a134e invite:ExportedChatInvite = ChannelAdminLogEventAction;
-channelAdminLogEventActionExportedInviteEdit#e90ebb59 prev_invite:ExportedChatInvite new_invite:ExportedChatInvite = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantVolume#3e7f6847 participant:GroupCallParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeHistoryTTL#6e941a38 prev_value:int new_value:int = ChannelAdminLogEventAction;
-
-channelAdminLogEvent#1fad68cd id:long date:int user_id:long action:ChannelAdminLogEventAction = ChannelAdminLogEvent;
-
-channels.adminLogResults#ed8af74d events:Vector<ChannelAdminLogEvent> chats:Vector<Chat> users:Vector<User> = channels.AdminLogResults;
-
-channelAdminLogEventsFilter#ea107ae4 flags:# join:flags.0?true leave:flags.1?true invite:flags.2?true ban:flags.3?true unban:flags.4?true kick:flags.5?true unkick:flags.6?true promote:flags.7?true demote:flags.8?true info:flags.9?true settings:flags.10?true pinned:flags.11?true edit:flags.12?true delete:flags.13?true group_call:flags.14?true invites:flags.15?true send:flags.16?true = ChannelAdminLogEventsFilter;
-
-popularContact#5ce14175 client_id:long importers:int = PopularContact;
-
-messages.favedStickersNotModified#9e8fa6d3 = messages.FavedStickers;
-messages.favedStickers#2cb51097 hash:long packs:Vector<StickerPack> stickers:Vector<Document> = messages.FavedStickers;
-
-recentMeUrlUnknown#46e1d13d url:string = RecentMeUrl;
-recentMeUrlUser#b92c09e2 url:string user_id:long = RecentMeUrl;
-recentMeUrlChat#b2da71d2 url:string chat_id:long = RecentMeUrl;
-recentMeUrlChatInvite#eb49081d url:string chat_invite:ChatInvite = RecentMeUrl;
-recentMeUrlStickerSet#bc0a57dc url:string set:StickerSetCovered = RecentMeUrl;
-
-help.recentMeUrls#e0310d7 urls:Vector<RecentMeUrl> chats:Vector<Chat> users:Vector<User> = help.RecentMeUrls;
-
-inputSingleMedia#1cc6e91f flags:# media:InputMedia random_id:long message:string entities:flags.0?Vector<MessageEntity> = InputSingleMedia;
-
-webAuthorization#a6f8f452 hash:long bot_id:long domain:string browser:string platform:string date_created:int date_active:int ip:string region:string = WebAuthorization;
-
-account.webAuthorizations#ed56c9fc authorizations:Vector<WebAuthorization> users:Vector<User> = account.WebAuthorizations;
-
-inputMessageID#a676a322 id:int = InputMessage;
-inputMessageReplyTo#bad88395 id:int = InputMessage;
-inputMessagePinned#86872538 = InputMessage;
-inputMessageCallbackQuery#acfa1a7e id:int query_id:long = InputMessage;
-
-inputDialogPeer#fcaafeb7 peer:InputPeer = InputDialogPeer;
-inputDialogPeerFolder#64600527 folder_id:int = InputDialogPeer;
-
-dialogPeer#e56dbf05 peer:Peer = DialogPeer;
-dialogPeerFolder#514519e2 folder_id:int = DialogPeer;
-
-messages.foundStickerSetsNotModified#d54b65d = messages.FoundStickerSets;
-messages.foundStickerSets#8af09dd2 hash:long sets:Vector<StickerSetCovered> = messages.FoundStickerSets;
-
-fileHash#6242c773 offset:int limit:int hash:bytes = FileHash;
-
-inputClientProxy#75588b3f address:string port:int = InputClientProxy;
-
-help.termsOfServiceUpdateEmpty#e3309f7f expires:int = help.TermsOfServiceUpdate;
-help.termsOfServiceUpdate#28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate;
-
-inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;
-inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;
-
-secureFileEmpty#64199744 = SecureFile;
-secureFile#e0277a62 id:long access_hash:long size:int dc_id:int date:int file_hash:bytes secret:bytes = SecureFile;
-
-secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;
-
-securePlainPhone#7d6099dd phone:string = SecurePlainData;
-securePlainEmail#21ec5a5f email:string = SecurePlainData;
-
-secureValueTypePersonalDetails#9d2a81e3 = SecureValueType;
-secureValueTypePassport#3dac6a00 = SecureValueType;
-secureValueTypeDriverLicense#6e425c4 = SecureValueType;
-secureValueTypeIdentityCard#a0d0744b = SecureValueType;
-secureValueTypeInternalPassport#99a48f23 = SecureValueType;
-secureValueTypeAddress#cbe31e26 = SecureValueType;
-secureValueTypeUtilityBill#fc36954e = SecureValueType;
-secureValueTypeBankStatement#89137c0d = SecureValueType;
-secureValueTypeRentalAgreement#8b883488 = SecureValueType;
-secureValueTypePassportRegistration#99e3806a = SecureValueType;
-secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;
-secureValueTypePhone#b320aadb = SecureValueType;
-secureValueTypeEmail#8e3ca7ee = SecureValueType;
-
-secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;
-
-inputSecureValue#db21d0a7 flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?InputSecureFile reverse_side:flags.2?InputSecureFile selfie:flags.3?InputSecureFile translation:flags.6?Vector<InputSecureFile> files:flags.4?Vector<InputSecureFile> plain_data:flags.5?SecurePlainData = InputSecureValue;
-
-secureValueHash#ed1ecdb0 type:SecureValueType hash:bytes = SecureValueHash;
-
-secureValueErrorData#e8a40bd9 type:SecureValueType data_hash:bytes field:string text:string = SecureValueError;
-secureValueErrorFrontSide#be3dfa type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorReverseSide#868a2aa5 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorSelfie#e537ced6 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorFile#7a700873 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorFiles#666220e9 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
-secureValueError#869d758f type:SecureValueType hash:bytes text:string = SecureValueError;
-secureValueErrorTranslationFile#a1144770 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorTranslationFiles#34636dd8 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
-
-secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;
-
-account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;
-
-account.sentEmailCode#811f854f email_pattern:string length:int = account.SentEmailCode;
-
-help.deepLinkInfoEmpty#66afa166 = help.DeepLinkInfo;
-help.deepLinkInfo#6a4ee832 flags:# update_app:flags.0?true message:string entities:flags.1?Vector<MessageEntity> = help.DeepLinkInfo;
-
-savedPhoneContact#1142bd56 phone:string first_name:string last_name:string date:int = SavedContact;
-
-account.takeout#4dba4501 id:long = account.Takeout;
-
-passwordKdfAlgoUnknown#d45ab096 = PasswordKdfAlgo;
-passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow#3a912d4a salt1:bytes salt2:bytes g:int p:bytes = PasswordKdfAlgo;
-
-securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;
-securePasswordKdfAlgoPBKDF2HMACSHA512iter100000#bbf2dda0 salt:bytes = SecurePasswordKdfAlgo;
-securePasswordKdfAlgoSHA512#86471d92 salt:bytes = SecurePasswordKdfAlgo;
-
-secureSecretSettings#1527bcac secure_algo:SecurePasswordKdfAlgo secure_secret:bytes secure_secret_id:long = SecureSecretSettings;
-
-inputCheckPasswordEmpty#9880f658 = InputCheckPasswordSRP;
-inputCheckPasswordSRP#d27ff082 srp_id:long A:bytes M1:bytes = InputCheckPasswordSRP;
-
-secureRequiredType#829d99da flags:# native_names:flags.0?true selfie_required:flags.1?true translation_required:flags.2?true type:SecureValueType = SecureRequiredType;
-secureRequiredTypeOneOf#27477b4 types:Vector<SecureRequiredType> = SecureRequiredType;
-
-help.passportConfigNotModified#bfb9f457 = help.PassportConfig;
-help.passportConfig#a098d6af hash:int countries_langs:DataJSON = help.PassportConfig;
-
-inputAppEvent#1d1b1245 time:double type:string peer:long data:JSONValue = InputAppEvent;
-
-jsonObjectValue#c0de1bd9 key:string value:JSONValue = JSONObjectValue;
-
-jsonNull#3f6d7b68 = JSONValue;
-jsonBool#c7345e6a value:Bool = JSONValue;
-jsonNumber#2be0dfa4 value:double = JSONValue;
-jsonString#b71e767a value:string = JSONValue;
-jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;
-jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;
-
-pageTableCell#34566b6a flags:# header:flags.0?true align_center:flags.3?true align_right:flags.4?true valign_middle:flags.5?true valign_bottom:flags.6?true text:flags.7?RichText colspan:flags.1?int rowspan:flags.2?int = PageTableCell;
-
-pageTableRow#e0c0c5e5 cells:Vector<PageTableCell> = PageTableRow;
-
-pageCaption#6f747657 text:RichText credit:RichText = PageCaption;
-
-pageListItemText#b92fb6cd text:RichText = PageListItem;
-pageListItemBlocks#25e073fc blocks:Vector<PageBlock> = PageListItem;
-
-pageListOrderedItemText#5e068047 num:string text:RichText = PageListOrderedItem;
-pageListOrderedItemBlocks#98dd8936 num:string blocks:Vector<PageBlock> = PageListOrderedItem;
-
-pageRelatedArticle#b390dc08 flags:# url:string webpage_id:long title:flags.0?string description:flags.1?string photo_id:flags.2?long author:flags.3?string published_date:flags.4?int = PageRelatedArticle;
-
-page#98657f0d flags:# part:flags.0?true rtl:flags.1?true v2:flags.2?true url:string blocks:Vector<PageBlock> photos:Vector<Photo> documents:Vector<Document> views:flags.3?int = Page;
-
-help.supportName#8c05f1c9 name:string = help.SupportName;
-
-help.userInfoEmpty#f3ae2eed = help.UserInfo;
-help.userInfo#1eb3758 message:string entities:Vector<MessageEntity> author:string date:int = help.UserInfo;
-
-pollAnswer#6ca9c2e9 text:string option:bytes = PollAnswer;
-
-poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;
-
-pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;
-
-pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;
-
-chatOnlines#f041e250 onlines:int = ChatOnlines;
-
-statsURL#47a971e0 url:string = StatsURL;
-
-chatAdminRights#5fb224d5 flags:# change_info:flags.0?true post_messages:flags.1?true edit_messages:flags.2?true delete_messages:flags.3?true ban_users:flags.4?true invite_users:flags.5?true pin_messages:flags.7?true add_admins:flags.9?true anonymous:flags.10?true manage_call:flags.11?true other:flags.12?true = ChatAdminRights;
-
-chatBannedRights#9f120418 flags:# view_messages:flags.0?true send_messages:flags.1?true send_media:flags.2?true send_stickers:flags.3?true send_gifs:flags.4?true send_games:flags.5?true send_inline:flags.6?true embed_links:flags.7?true send_polls:flags.8?true change_info:flags.10?true invite_users:flags.15?true pin_messages:flags.17?true until_date:int = ChatBannedRights;
-
-inputWallPaper#e630b979 id:long access_hash:long = InputWallPaper;
-inputWallPaperSlug#72091c80 slug:string = InputWallPaper;
-inputWallPaperNoFile#967a462e id:long = InputWallPaper;
-
-account.wallPapersNotModified#1c199183 = account.WallPapers;
-account.wallPapers#cdc3858c hash:long wallpapers:Vector<WallPaper> = account.WallPapers;
-
-codeSettings#debebe83 flags:# allow_flashcall:flags.0?true current_number:flags.1?true allow_app_hash:flags.4?true = CodeSettings;
-
-wallPaperSettings#1dc1bca4 flags:# blur:flags.1?true motion:flags.2?true background_color:flags.0?int second_background_color:flags.4?int third_background_color:flags.5?int fourth_background_color:flags.6?int intensity:flags.3?int rotation:flags.4?int = WallPaperSettings;
-
-autoDownloadSettings#e04232f3 flags:# disabled:flags.0?true video_preload_large:flags.1?true audio_preload_next:flags.2?true phonecalls_less_data:flags.3?true photo_size_max:int video_size_max:int file_size_max:int video_upload_maxbitrate:int = AutoDownloadSettings;
-
-account.autoDownloadSettings#63cacf26 low:AutoDownloadSettings medium:AutoDownloadSettings high:AutoDownloadSettings = account.AutoDownloadSettings;
-
-emojiKeyword#d5b3b9f9 keyword:string emoticons:Vector<string> = EmojiKeyword;
-emojiKeywordDeleted#236df622 keyword:string emoticons:Vector<string> = EmojiKeyword;
-
-emojiKeywordsDifference#5cc761bd lang_code:string from_version:int version:int keywords:Vector<EmojiKeyword> = EmojiKeywordsDifference;
-
-emojiURL#a575739d url:string = EmojiURL;
-
-emojiLanguage#b3fb5361 lang_code:string = EmojiLanguage;
-
-folder#ff544e65 flags:# autofill_new_broadcasts:flags.0?true autofill_public_groups:flags.1?true autofill_new_correspondents:flags.2?true id:int title:string photo:flags.3?ChatPhoto = Folder;
-
-inputFolderPeer#fbd2c296 peer:InputPeer folder_id:int = InputFolderPeer;
-
-folderPeer#e9baa668 peer:Peer folder_id:int = FolderPeer;
-
-messages.searchCounter#e844ebff flags:# inexact:flags.1?true filter:MessagesFilter count:int = messages.SearchCounter;
-
-urlAuthResultRequest#92d33a0e flags:# request_write_access:flags.0?true bot:User domain:string = UrlAuthResult;
-urlAuthResultAccepted#8f8c0e4e url:string = UrlAuthResult;
-urlAuthResultDefault#a9d6db1f = UrlAuthResult;
-
-channelLocationEmpty#bfb5ad8b = ChannelLocation;
-channelLocation#209b82db geo_point:GeoPoint address:string = ChannelLocation;
-
-peerLocated#ca461b5d peer:Peer expires:int distance:int = PeerLocated;
-peerSelfLocated#f8ec284b expires:int = PeerLocated;
-
-restrictionReason#d072acb4 platform:string reason:string text:string = RestrictionReason;
-
-inputTheme#3c5693e9 id:long access_hash:long = InputTheme;
-inputThemeSlug#f5890df1 slug:string = InputTheme;
-
-theme#e802b8dc flags:# creator:flags.0?true default:flags.1?true for_chat:flags.5?true id:long access_hash:long slug:string title:string document:flags.2?Document settings:flags.3?ThemeSettings installs_count:flags.4?int = Theme;
-
-account.themesNotModified#f41eb622 = account.Themes;
-account.themes#9a3d8c6d hash:long themes:Vector<Theme> = account.Themes;
-
-auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
-auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;
-auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;
-
-account.contentSettings#57e28221 flags:# sensitive_enabled:flags.0?true sensitive_can_change:flags.1?true = account.ContentSettings;
-
-messages.inactiveChats#a927fec5 dates:Vector<int> chats:Vector<Chat> users:Vector<User> = messages.InactiveChats;
-
-baseThemeClassic#c3a12462 = BaseTheme;
-baseThemeDay#fbd81688 = BaseTheme;
-baseThemeNight#b7b31ea8 = BaseTheme;
-baseThemeTinted#6d5f77ee = BaseTheme;
-baseThemeArctic#5b11125a = BaseTheme;
-
-inputThemeSettings#8fde504f flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int outbox_accent_color:flags.3?int message_colors:flags.0?Vector<int> wallpaper:flags.1?InputWallPaper wallpaper_settings:flags.1?WallPaperSettings = InputThemeSettings;
-
-themeSettings#fa58b6d4 flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int outbox_accent_color:flags.3?int message_colors:flags.0?Vector<int> wallpaper:flags.1?WallPaper = ThemeSettings;
-
-webPageAttributeTheme#54b56617 flags:# documents:flags.0?Vector<Document> settings:flags.1?ThemeSettings = WebPageAttribute;
-
-messageUserVote#34d247b4 user_id:long option:bytes date:int = MessageUserVote;
-messageUserVoteInputOption#3ca5b0ec user_id:long date:int = MessageUserVote;
-messageUserVoteMultiple#8a65e557 user_id:long options:Vector<bytes> date:int = MessageUserVote;
-
-messages.votesList#823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList;
-
-bankCardOpenUrl#f568028a url:string name:string = BankCardOpenUrl;
-
-payments.bankCardData#3e24e573 title:string open_urls:Vector<BankCardOpenUrl> = payments.BankCardData;
-
-dialogFilter#7438f7e8 flags:# contacts:flags.0?true non_contacts:flags.1?true groups:flags.2?true broadcasts:flags.3?true bots:flags.4?true exclude_muted:flags.11?true exclude_read:flags.12?true exclude_archived:flags.13?true id:int title:string emoticon:flags.25?string pinned_peers:Vector<InputPeer> include_peers:Vector<InputPeer> exclude_peers:Vector<InputPeer> = DialogFilter;
-
-dialogFilterSuggested#77744d4a filter:DialogFilter description:string = DialogFilterSuggested;
-
-statsDateRangeDays#b637edaf min_date:int max_date:int = StatsDateRangeDays;
-
-statsAbsValueAndPrev#cb43acde current:double previous:double = StatsAbsValueAndPrev;
-
-statsPercentValue#cbce2fe0 part:double total:double = StatsPercentValue;
-
-statsGraphAsync#4a27eb2d token:string = StatsGraph;
-statsGraphError#bedc9822 error:string = StatsGraph;
-statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
-
-messageInteractionCounters#ad4fc9bd msg_id:int views:int forwards:int = MessageInteractionCounters;
-
-stats.broadcastStats#bdf78394 period:StatsDateRangeDays followers:StatsAbsValueAndPrev views_per_post:StatsAbsValueAndPrev shares_per_post:StatsAbsValueAndPrev enabled_notifications:StatsPercentValue growth_graph:StatsGraph followers_graph:StatsGraph mute_graph:StatsGraph top_hours_graph:StatsGraph interactions_graph:StatsGraph iv_interactions_graph:StatsGraph views_by_source_graph:StatsGraph new_followers_by_source_graph:StatsGraph languages_graph:StatsGraph recent_message_interactions:Vector<MessageInteractionCounters> = stats.BroadcastStats;
-
-help.promoDataEmpty#98f6ac75 expires:int = help.PromoData;
-help.promoData#8c39793f flags:# proxy:flags.0?true expires:int peer:Peer chats:Vector<Chat> users:Vector<User> psa_type:flags.1?string psa_message:flags.2?string = help.PromoData;
-
-videoSize#de33b094 flags:# type:string w:int h:int size:int video_start_ts:flags.0?double = VideoSize;
-
-statsGroupTopPoster#9d04af9b user_id:long messages:int avg_chars:int = StatsGroupTopPoster;
-
-statsGroupTopAdmin#d7584c87 user_id:long deleted:int kicked:int banned:int = StatsGroupTopAdmin;
-
-statsGroupTopInviter#535f779d user_id:long invitations:int = StatsGroupTopInviter;
-
-stats.megagroupStats#ef7ff916 period:StatsDateRangeDays members:StatsAbsValueAndPrev messages:StatsAbsValueAndPrev viewers:StatsAbsValueAndPrev posters:StatsAbsValueAndPrev growth_graph:StatsGraph members_graph:StatsGraph new_members_by_source_graph:StatsGraph languages_graph:StatsGraph messages_graph:StatsGraph actions_graph:StatsGraph top_hours_graph:StatsGraph weekdays_graph:StatsGraph top_posters:Vector<StatsGroupTopPoster> top_admins:Vector<StatsGroupTopAdmin> top_inviters:Vector<StatsGroupTopInviter> users:Vector<User> = stats.MegagroupStats;
-
-globalPrivacySettings#bea2f424 flags:# archive_and_mute_new_noncontact_peers:flags.0?Bool = GlobalPrivacySettings;
-
-help.countryCode#4203c5ef flags:# country_code:string prefixes:flags.0?Vector<string> patterns:flags.1?Vector<string> = help.CountryCode;
-
-help.country#c3878e23 flags:# hidden:flags.0?true iso2:string default_name:string name:flags.1?string country_codes:Vector<help.CountryCode> = help.Country;
-
-help.countriesListNotModified#93cc1f32 = help.CountriesList;
-help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;
-
-messageViews#455b853d flags:# views:flags.0?int forwards:flags.1?int replies:flags.2?MessageReplies = MessageViews;
-
-messages.messageViews#b6c4f543 views:Vector<MessageViews> chats:Vector<Chat> users:Vector<User> = messages.MessageViews;
-
-messages.discussionMessage#a6341782 flags:# messages:Vector<Message> max_id:flags.0?int read_inbox_max_id:flags.1?int read_outbox_max_id:flags.2?int unread_count:int chats:Vector<Chat> users:Vector<User> = messages.DiscussionMessage;
-
-messageReplyHeader#a6d57763 flags:# reply_to_msg_id:int reply_to_peer_id:flags.0?Peer reply_to_top_id:flags.1?int = MessageReplyHeader;
-
-messageReplies#83d60fc2 flags:# comments:flags.0?true replies:int replies_pts:int recent_repliers:flags.1?Vector<Peer> channel_id:flags.0?long max_id:flags.2?int read_max_id:flags.3?int = MessageReplies;
-
-peerBlocked#e8fd8014 peer_id:Peer date:int = PeerBlocked;
-
-stats.messageStats#8999f295 views_graph:StatsGraph = stats.MessageStats;
-
-groupCallDiscarded#7780bcb4 id:long access_hash:long duration:int = GroupCall;
-groupCall#d597650c flags:# join_muted:flags.1?true can_change_join_muted:flags.2?true join_date_asc:flags.6?true schedule_start_subscribed:flags.8?true can_start_video:flags.9?true record_video_active:flags.11?true id:long access_hash:long participants_count:int title:flags.3?string stream_dc_id:flags.4?int record_start_date:flags.5?int schedule_date:flags.7?int unmuted_video_count:flags.10?int unmuted_video_limit:int version:int = GroupCall;
-
-inputGroupCall#d8aa840f id:long access_hash:long = InputGroupCall;
-
-groupCallParticipant#eba636fe flags:# muted:flags.0?true left:flags.1?true can_self_unmute:flags.2?true just_joined:flags.4?true versioned:flags.5?true min:flags.8?true muted_by_you:flags.9?true volume_by_admin:flags.10?true self:flags.12?true video_joined:flags.15?true peer:Peer date:int active_date:flags.3?int source:int volume:flags.7?int about:flags.11?string raise_hand_rating:flags.13?long video:flags.6?GroupCallParticipantVideo presentation:flags.14?GroupCallParticipantVideo = GroupCallParticipant;
-
-phone.groupCall#9e727aad call:GroupCall participants:Vector<GroupCallParticipant> participants_next_offset:string chats:Vector<Chat> users:Vector<User> = phone.GroupCall;
-
-phone.groupParticipants#f47751b6 count:int participants:Vector<GroupCallParticipant> next_offset:string chats:Vector<Chat> users:Vector<User> version:int = phone.GroupParticipants;
-
-inlineQueryPeerTypeSameBotPM#3081ed9d = InlineQueryPeerType;
-inlineQueryPeerTypePM#833c0fac = InlineQueryPeerType;
-inlineQueryPeerTypeChat#d766c50a = InlineQueryPeerType;
-inlineQueryPeerTypeMegagroup#5ec4be43 = InlineQueryPeerType;
-inlineQueryPeerTypeBroadcast#6334ee9a = InlineQueryPeerType;
-
-messages.historyImport#1662af0b id:long = messages.HistoryImport;
-
-messages.historyImportParsed#5e0fb7b9 flags:# pm:flags.0?true group:flags.1?true title:flags.2?string = messages.HistoryImportParsed;
-
-messages.affectedFoundMessages#ef8d3e6c pts:int pts_count:int offset:int messages:Vector<int> = messages.AffectedFoundMessages;
-
-chatInviteImporter#b5cd5f4 user_id:long date:int = ChatInviteImporter;
-
-messages.exportedChatInvites#bdc62dcc count:int invites:Vector<ExportedChatInvite> users:Vector<User> = messages.ExportedChatInvites;
-
-messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
-messages.exportedChatInviteReplaced#222600ef invite:ExportedChatInvite new_invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
-
-messages.chatInviteImporters#81b6b00a count:int importers:Vector<ChatInviteImporter> users:Vector<User> = messages.ChatInviteImporters;
-
-chatAdminWithInvites#f2ecef23 admin_id:long invites_count:int revoked_invites_count:int = ChatAdminWithInvites;
-
-messages.chatAdminsWithInvites#b69b72d7 admins:Vector<ChatAdminWithInvites> users:Vector<User> = messages.ChatAdminsWithInvites;
-
-messages.checkedHistoryImportPeer#a24de717 confirm_text:string = messages.CheckedHistoryImportPeer;
-
-phone.joinAsPeers#afe5623f peers:Vector<Peer> chats:Vector<Chat> users:Vector<User> = phone.JoinAsPeers;
-
-phone.exportedGroupCallInvite#204bd158 link:string = phone.ExportedGroupCallInvite;
-
-groupCallParticipantVideoSourceGroup#dcb118b7 semantics:string sources:Vector<int> = GroupCallParticipantVideoSourceGroup;
-
-groupCallParticipantVideo#67753ac8 flags:# paused:flags.0?true endpoint:string source_groups:Vector<GroupCallParticipantVideoSourceGroup> audio_source:flags.1?int = GroupCallParticipantVideo;
-
-stickers.suggestedShortName#85fea03f short_name:string = stickers.SuggestedShortName;
-
-botCommandScopeDefault#2f6cb2ab = BotCommandScope;
-botCommandScopeUsers#3c4f04d8 = BotCommandScope;
-botCommandScopeChats#6fe1a881 = BotCommandScope;
-botCommandScopeChatAdmins#b9aa606a = BotCommandScope;
-botCommandScopePeer#db9d897d peer:InputPeer = BotCommandScope;
-botCommandScopePeerAdmins#3fd863d1 peer:InputPeer = BotCommandScope;
-botCommandScopePeerUser#a1321f3 peer:InputPeer user_id:InputUser = BotCommandScope;
-
-account.resetPasswordFailedWait#e3779861 retry_date:int = account.ResetPasswordResult;
-account.resetPasswordRequestedWait#e9effc7d until_date:int = account.ResetPasswordResult;
-account.resetPasswordOk#e926d63e = account.ResetPasswordResult;
-
-chatTheme#ed0b5c33 emoticon:string theme:Theme dark_theme:Theme = ChatTheme;
-
-account.chatThemesNotModified#e011e1c4 = account.ChatThemes;
-account.chatThemes#fe4cbebd hash:int themes:Vector<ChatTheme> = account.ChatThemes;
-
-sponsoredMessage#2a3c381f flags:# random_id:bytes from_id:Peer start_param:flags.0?string message:string entities:flags.1?Vector<MessageEntity> = SponsoredMessage;
-
-messages.sponsoredMessages#65a4c7d5 messages:Vector<SponsoredMessage> chats:Vector<Chat> users:Vector<User> = messages.SponsoredMessages;
-
----functions---
-
-invokeAfterMsg#cb9f372d {X:Type} msg_id:long query:!X = X;
-invokeAfterMsgs#3dc4b4f0 {X:Type} msg_ids:Vector<long> query:!X = X;
-initConnection#c1cd5ea9 {X:Type} flags:# api_id:int device_model:string system_version:string app_version:string system_lang_code:string lang_pack:string lang_code:string proxy:flags.0?InputClientProxy params:flags.1?JSONValue query:!X = X;
-invokeWithLayer#da9b0d0d {X:Type} layer:int query:!X = X;
-invokeWithoutUpdates#bf9459b7 {X:Type} query:!X = X;
-invokeWithMessagesRange#365275f2 {X:Type} range:MessageRange query:!X = X;
-invokeWithTakeout#aca9fd2e {X:Type} takeout_id:long query:!X = X;
-
-auth.sendCode#a677244f phone_number:string api_id:int api_hash:string settings:CodeSettings = auth.SentCode;
-auth.signUp#80eee427 phone_number:string phone_code_hash:string first_name:string last_name:string = auth.Authorization;
-auth.signIn#bcd51581 phone_number:string phone_code_hash:string phone_code:string = auth.Authorization;
-auth.logOut#5717da40 = Bool;
-auth.resetAuthorizations#9fab0d1a = Bool;
-auth.exportAuthorization#e5bfffcd dc_id:int = auth.ExportedAuthorization;
-auth.importAuthorization#a57a7dad id:long bytes:bytes = auth.Authorization;
-auth.bindTempAuthKey#cdd42a05 perm_auth_key_id:long nonce:long expires_at:int encrypted_message:bytes = Bool;
-auth.importBotAuthorization#67a3ff2c flags:int api_id:int api_hash:string bot_auth_token:string = auth.Authorization;
-auth.checkPassword#d18b4d16 password:InputCheckPasswordSRP = auth.Authorization;
-auth.requestPasswordRecovery#d897bc66 = auth.PasswordRecovery;
-auth.recoverPassword#37096c70 flags:# code:string new_settings:flags.0?account.PasswordInputSettings = auth.Authorization;
-auth.resendCode#3ef1a9bf phone_number:string phone_code_hash:string = auth.SentCode;
-auth.cancelCode#1f040578 phone_number:string phone_code_hash:string = Bool;
-auth.dropTempAuthKeys#8e48a188 except_auth_keys:Vector<long> = Bool;
-auth.exportLoginToken#b7e085fe api_id:int api_hash:string except_ids:Vector<long> = auth.LoginToken;
-auth.importLoginToken#95ac5ce4 token:bytes = auth.LoginToken;
-auth.acceptLoginToken#e894ad4d token:bytes = Authorization;
-auth.checkRecoveryPassword#d36bf79 code:string = Bool;
-
-account.registerDevice#ec86017a flags:# no_muted:flags.0?true token_type:int token:string app_sandbox:Bool secret:bytes other_uids:Vector<long> = Bool;
-account.unregisterDevice#6a0d3206 token_type:int token:string other_uids:Vector<long> = Bool;
-account.updateNotifySettings#84be5b93 peer:InputNotifyPeer settings:InputPeerNotifySettings = Bool;
-account.getNotifySettings#12b3ad31 peer:InputNotifyPeer = PeerNotifySettings;
-account.resetNotifySettings#db7e1747 = Bool;
-account.updateProfile#78515775 flags:# first_name:flags.0?string last_name:flags.1?string about:flags.2?string = User;
-account.updateStatus#6628562c offline:Bool = Bool;
-account.getWallPapers#7967d36 hash:long = account.WallPapers;
-account.reportPeer#c5ba3d86 peer:InputPeer reason:ReportReason message:string = Bool;
-account.checkUsername#2714d86c username:string = Bool;
-account.updateUsername#3e0bdd7c username:string = User;
-account.getPrivacy#dadbc950 key:InputPrivacyKey = account.PrivacyRules;
-account.setPrivacy#c9f81ce8 key:InputPrivacyKey rules:Vector<InputPrivacyRule> = account.PrivacyRules;
-account.deleteAccount#418d4e0b reason:string = Bool;
-account.getAccountTTL#8fc711d = AccountDaysTTL;
-account.setAccountTTL#2442485e ttl:AccountDaysTTL = Bool;
-account.sendChangePhoneCode#82574ae5 phone_number:string settings:CodeSettings = auth.SentCode;
-account.changePhone#70c32edb phone_number:string phone_code_hash:string phone_code:string = User;
-account.updateDeviceLocked#38df3532 period:int = Bool;
-account.getAuthorizations#e320c158 = account.Authorizations;
-account.resetAuthorization#df77f3bc hash:long = Bool;
-account.getPassword#548a30f5 = account.Password;
-account.getPasswordSettings#9cd4eaf9 password:InputCheckPasswordSRP = account.PasswordSettings;
-account.updatePasswordSettings#a59b102f password:InputCheckPasswordSRP new_settings:account.PasswordInputSettings = Bool;
-account.sendConfirmPhoneCode#1b3faa88 hash:string settings:CodeSettings = auth.SentCode;
-account.confirmPhone#5f2178c3 phone_code_hash:string phone_code:string = Bool;
-account.getTmpPassword#449e0b51 password:InputCheckPasswordSRP period:int = account.TmpPassword;
-account.getWebAuthorizations#182e6d6f = account.WebAuthorizations;
-account.resetWebAuthorization#2d01b9ef hash:long = Bool;
-account.resetWebAuthorizations#682d2594 = Bool;
-account.getAllSecureValues#b288bc7d = Vector<SecureValue>;
-account.getSecureValue#73665bc2 types:Vector<SecureValueType> = Vector<SecureValue>;
-account.saveSecureValue#899fe31d value:InputSecureValue secure_secret_id:long = SecureValue;
-account.deleteSecureValue#b880bc4b types:Vector<SecureValueType> = Bool;
-account.getAuthorizationForm#a929597a bot_id:long scope:string public_key:string = account.AuthorizationForm;
-account.acceptAuthorization#f3ed4c73 bot_id:long scope:string public_key:string value_hashes:Vector<SecureValueHash> credentials:SecureCredentialsEncrypted = Bool;
-account.sendVerifyPhoneCode#a5a356f9 phone_number:string settings:CodeSettings = auth.SentCode;
-account.verifyPhone#4dd3a7f6 phone_number:string phone_code_hash:string phone_code:string = Bool;
-account.sendVerifyEmailCode#7011509f email:string = account.SentEmailCode;
-account.verifyEmail#ecba39db email:string code:string = Bool;
-account.initTakeoutSession#f05b4804 flags:# contacts:flags.0?true message_users:flags.1?true message_chats:flags.2?true message_megagroups:flags.3?true message_channels:flags.4?true files:flags.5?true file_max_size:flags.5?int = account.Takeout;
-account.finishTakeoutSession#1d2652ee flags:# success:flags.0?true = Bool;
-account.confirmPasswordEmail#8fdf1920 code:string = Bool;
-account.resendPasswordEmail#7a7f2a15 = Bool;
-account.cancelPasswordEmail#c1cbd5b6 = Bool;
-account.getContactSignUpNotification#9f07c728 = Bool;
-account.setContactSignUpNotification#cff43f61 silent:Bool = Bool;
-account.getNotifyExceptions#53577479 flags:# compare_sound:flags.1?true peer:flags.0?InputNotifyPeer = Updates;
-account.getWallPaper#fc8ddbea wallpaper:InputWallPaper = WallPaper;
-account.uploadWallPaper#dd853661 file:InputFile mime_type:string settings:WallPaperSettings = WallPaper;
-account.saveWallPaper#6c5a5b37 wallpaper:InputWallPaper unsave:Bool settings:WallPaperSettings = Bool;
-account.installWallPaper#feed5769 wallpaper:InputWallPaper settings:WallPaperSettings = Bool;
-account.resetWallPapers#bb3b9804 = Bool;
-account.getAutoDownloadSettings#56da0b3f = account.AutoDownloadSettings;
-account.saveAutoDownloadSettings#76f36233 flags:# low:flags.0?true high:flags.1?true settings:AutoDownloadSettings = Bool;
-account.uploadTheme#1c3db333 flags:# file:InputFile thumb:flags.0?InputFile file_name:string mime_type:string = Document;
-account.createTheme#8432c21f flags:# slug:string title:string document:flags.2?InputDocument settings:flags.3?InputThemeSettings = Theme;
-account.updateTheme#5cb367d5 flags:# format:string theme:InputTheme slug:flags.0?string title:flags.1?string document:flags.2?InputDocument settings:flags.3?InputThemeSettings = Theme;
-account.saveTheme#f257106c theme:InputTheme unsave:Bool = Bool;
-account.installTheme#7ae43737 flags:# dark:flags.0?true format:flags.1?string theme:flags.1?InputTheme = Bool;
-account.getTheme#8d9d742b format:string theme:InputTheme document_id:long = Theme;
-account.getThemes#7206e458 format:string hash:long = account.Themes;
-account.setContentSettings#b574b16b flags:# sensitive_enabled:flags.0?true = Bool;
-account.getContentSettings#8b9b4dae = account.ContentSettings;
-account.getMultiWallPapers#65ad71dc wallpapers:Vector<InputWallPaper> = Vector<WallPaper>;
-account.getGlobalPrivacySettings#eb2b4cf6 = GlobalPrivacySettings;
-account.setGlobalPrivacySettings#1edaaac2 settings:GlobalPrivacySettings = GlobalPrivacySettings;
-account.reportProfilePhoto#fa8cc6f5 peer:InputPeer photo_id:InputPhoto reason:ReportReason message:string = Bool;
-account.resetPassword#9308ce1b = account.ResetPasswordResult;
-account.declinePasswordReset#4c9409f6 = Bool;
-account.getChatThemes#d6d71d7b hash:int = account.ChatThemes;
-
-users.getUsers#d91a548 id:Vector<InputUser> = Vector<User>;
-users.getFullUser#ca30a5b1 id:InputUser = UserFull;
-users.setSecureValueErrors#90c894b5 id:InputUser errors:Vector<SecureValueError> = Bool;
-
-contacts.getContactIDs#7adc669d hash:long = Vector<int>;
-contacts.getStatuses#c4a353ee = Vector<ContactStatus>;
-contacts.getContacts#5dd69e12 hash:long = contacts.Contacts;
-contacts.importContacts#2c800be5 contacts:Vector<InputContact> = contacts.ImportedContacts;
-contacts.deleteContacts#96a0e00 id:Vector<InputUser> = Updates;
-contacts.deleteByPhones#1013fd9e phones:Vector<string> = Bool;
-contacts.block#68cc1411 id:InputPeer = Bool;
-contacts.unblock#bea65d50 id:InputPeer = Bool;
-contacts.getBlocked#f57c350f offset:int limit:int = contacts.Blocked;
-contacts.search#11f812d8 q:string limit:int = contacts.Found;
-contacts.resolveUsername#f93ccba3 username:string = contacts.ResolvedPeer;
-contacts.getTopPeers#973478b6 flags:# correspondents:flags.0?true bots_pm:flags.1?true bots_inline:flags.2?true phone_calls:flags.3?true forward_users:flags.4?true forward_chats:flags.5?true groups:flags.10?true channels:flags.15?true offset:int limit:int hash:long = contacts.TopPeers;
-contacts.resetTopPeerRating#1ae373ac category:TopPeerCategory peer:InputPeer = Bool;
-contacts.resetSaved#879537f1 = Bool;
-contacts.getSaved#82f1e39f = Vector<SavedContact>;
-contacts.toggleTopPeers#8514bdda enabled:Bool = Bool;
-contacts.addContact#e8f463d0 flags:# add_phone_privacy_exception:flags.0?true id:InputUser first_name:string last_name:string phone:string = Updates;
-contacts.acceptContact#f831a20f id:InputUser = Updates;
-contacts.getLocated#d348bc44 flags:# background:flags.1?true geo_point:InputGeoPoint self_expires:flags.0?int = Updates;
-contacts.blockFromReplies#29a8962c flags:# delete_message:flags.0?true delete_history:flags.1?true report_spam:flags.2?true msg_id:int = Updates;
-
-messages.getMessages#63c66506 id:Vector<InputMessage> = messages.Messages;
-messages.getDialogs#a0f4cb4f flags:# exclude_pinned:flags.0?true folder_id:flags.1?int offset_date:int offset_id:int offset_peer:InputPeer limit:int hash:long = messages.Dialogs;
-messages.getHistory#4423e6c5 peer:InputPeer offset_id:int offset_date:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
-messages.search#a0fda762 flags:# peer:InputPeer q:string from_id:flags.0?InputPeer top_msg_id:flags.1?int filter:MessagesFilter min_date:int max_date:int offset_id:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
-messages.readHistory#e306d3a peer:InputPeer max_id:int = messages.AffectedMessages;
-messages.deleteHistory#1c015b09 flags:# just_clear:flags.0?true revoke:flags.1?true peer:InputPeer max_id:int = messages.AffectedHistory;
-messages.deleteMessages#e58e95d2 flags:# revoke:flags.0?true id:Vector<int> = messages.AffectedMessages;
-messages.receivedMessages#5a954c0 max_id:int = Vector<ReceivedNotifyMessage>;
-messages.setTyping#58943ee2 flags:# peer:InputPeer top_msg_id:flags.0?int action:SendMessageAction = Bool;
-messages.sendMessage#520c3870 flags:# no_webpage:flags.1?true silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-messages.forwardMessages#d9fee60e flags:# silent:flags.5?true background:flags.6?true with_my_score:flags.8?true drop_author:flags.11?true drop_media_captions:flags.12?true from_peer:InputPeer id:Vector<int> random_id:Vector<long> to_peer:InputPeer schedule_date:flags.10?int = Updates;
-messages.reportSpam#cf1592db peer:InputPeer = Bool;
-messages.getPeerSettings#3672e09c peer:InputPeer = PeerSettings;
-messages.report#8953ab4e peer:InputPeer id:Vector<int> reason:ReportReason message:string = Bool;
-messages.getChats#49e9528f id:Vector<long> = messages.Chats;
-messages.getFullChat#aeb00b34 chat_id:long = messages.ChatFull;
-messages.editChatTitle#73783ffd chat_id:long title:string = Updates;
-messages.editChatPhoto#35ddd674 chat_id:long photo:InputChatPhoto = Updates;
-messages.addChatUser#f24753e3 chat_id:long user_id:InputUser fwd_limit:int = Updates;
-messages.deleteChatUser#a2185cab flags:# revoke_history:flags.0?true chat_id:long user_id:InputUser = Updates;
-messages.createChat#9cb126e users:Vector<InputUser> title:string = Updates;
-messages.getDhConfig#26cf8950 version:int random_length:int = messages.DhConfig;
-messages.requestEncryption#f64daf43 user_id:InputUser random_id:int g_a:bytes = EncryptedChat;
-messages.acceptEncryption#3dbc0415 peer:InputEncryptedChat g_b:bytes key_fingerprint:long = EncryptedChat;
-messages.discardEncryption#f393aea0 flags:# delete_history:flags.0?true chat_id:int = Bool;
-messages.setEncryptedTyping#791451ed peer:InputEncryptedChat typing:Bool = Bool;
-messages.readEncryptedHistory#7f4b690a peer:InputEncryptedChat max_date:int = Bool;
-messages.sendEncrypted#44fa7a15 flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;
-messages.sendEncryptedFile#5559481d flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes file:InputEncryptedFile = messages.SentEncryptedMessage;
-messages.sendEncryptedService#32d439a4 peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;
-messages.receivedQueue#55a5bb66 max_qts:int = Vector<long>;
-messages.reportEncryptedSpam#4b0c8c0f peer:InputEncryptedChat = Bool;
-messages.readMessageContents#36a73f77 id:Vector<int> = messages.AffectedMessages;
-messages.getStickers#d5a5d3a1 emoticon:string hash:long = messages.Stickers;
-messages.getAllStickers#b8a0a1a8 hash:long = messages.AllStickers;
-messages.getWebPagePreview#8b68b0cc flags:# message:string entities:flags.3?Vector<MessageEntity> = MessageMedia;
-messages.exportChatInvite#14b9bcd7 flags:# legacy_revoke_permanent:flags.2?true peer:InputPeer expire_date:flags.0?int usage_limit:flags.1?int = ExportedChatInvite;
-messages.checkChatInvite#3eadb1bb hash:string = ChatInvite;
-messages.importChatInvite#6c50051c hash:string = Updates;
-messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;
-messages.installStickerSet#c78fe460 stickerset:InputStickerSet archived:Bool = messages.StickerSetInstallResult;
-messages.uninstallStickerSet#f96e55de stickerset:InputStickerSet = Bool;
-messages.startBot#e6df7378 bot:InputUser peer:InputPeer random_id:long start_param:string = Updates;
-messages.getMessagesViews#5784d3e1 peer:InputPeer id:Vector<int> increment:Bool = messages.MessageViews;
-messages.editChatAdmin#a85bd1c2 chat_id:long user_id:InputUser is_admin:Bool = Bool;
-messages.migrateChat#a2875319 chat_id:long = Updates;
-messages.searchGlobal#4bc6589a flags:# folder_id:flags.0?int q:string filter:MessagesFilter min_date:int max_date:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;
-messages.reorderStickerSets#78337739 flags:# masks:flags.0?true order:Vector<long> = Bool;
-messages.getDocumentByHash#338e2464 sha256:bytes size:int mime_type:string = Document;
-messages.getSavedGifs#5cf09635 hash:long = messages.SavedGifs;
-messages.saveGif#327a30cb id:InputDocument unsave:Bool = Bool;
-messages.getInlineBotResults#514e999d flags:# bot:InputUser peer:InputPeer geo_point:flags.0?InputGeoPoint query:string offset:string = messages.BotResults;
-messages.setInlineBotResults#eb5ea206 flags:# gallery:flags.0?true private:flags.1?true query_id:long results:Vector<InputBotInlineResult> cache_time:int next_offset:flags.2?string switch_pm:flags.3?InlineBotSwitchPM = Bool;
-messages.sendInlineBotResult#220815b0 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true hide_via:flags.11?true peer:InputPeer reply_to_msg_id:flags.0?int random_id:long query_id:long id:string schedule_date:flags.10?int = Updates;
-messages.getMessageEditData#fda68d36 peer:InputPeer id:int = messages.MessageEditData;
-messages.editMessage#48f71778 flags:# no_webpage:flags.1?true peer:InputPeer id:int message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.15?int = Updates;
-messages.editInlineBotMessage#83557dba flags:# no_webpage:flags.1?true id:InputBotInlineMessageID message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> = Bool;
-messages.getBotCallbackAnswer#9342ca07 flags:# game:flags.1?true peer:InputPeer msg_id:int data:flags.0?bytes password:flags.2?InputCheckPasswordSRP = messages.BotCallbackAnswer;
-messages.setBotCallbackAnswer#d58f130a flags:# alert:flags.1?true query_id:long message:flags.0?string url:flags.2?string cache_time:int = Bool;
-messages.getPeerDialogs#e470bcfd peers:Vector<InputDialogPeer> = messages.PeerDialogs;
-messages.saveDraft#bc39e14b flags:# no_webpage:flags.1?true reply_to_msg_id:flags.0?int peer:InputPeer message:string entities:flags.3?Vector<MessageEntity> = Bool;
-messages.getAllDrafts#6a3f8d65 = Updates;
-messages.getFeaturedStickers#64780b14 hash:long = messages.FeaturedStickers;
-messages.readFeaturedStickers#5b118126 id:Vector<long> = Bool;
-messages.getRecentStickers#9da9403b flags:# attached:flags.0?true hash:long = messages.RecentStickers;
-messages.saveRecentSticker#392718f8 flags:# attached:flags.0?true id:InputDocument unsave:Bool = Bool;
-messages.clearRecentStickers#8999602d flags:# attached:flags.0?true = Bool;
-messages.getArchivedStickers#57f17692 flags:# masks:flags.0?true offset_id:long limit:int = messages.ArchivedStickers;
-messages.getMaskStickers#640f82b8 hash:long = messages.AllStickers;
-messages.getAttachedStickers#cc5b67cc media:InputStickeredMedia = Vector<StickerSetCovered>;
-messages.setGameScore#8ef8ecc0 flags:# edit_message:flags.0?true force:flags.1?true peer:InputPeer id:int user_id:InputUser score:int = Updates;
-messages.setInlineGameScore#15ad9f64 flags:# edit_message:flags.0?true force:flags.1?true id:InputBotInlineMessageID user_id:InputUser score:int = Bool;
-messages.getGameHighScores#e822649d peer:InputPeer id:int user_id:InputUser = messages.HighScores;
-messages.getInlineGameHighScores#f635e1b id:InputBotInlineMessageID user_id:InputUser = messages.HighScores;
-messages.getCommonChats#e40ca104 user_id:InputUser max_id:long limit:int = messages.Chats;
-messages.getAllChats#875f74be except_ids:Vector<long> = messages.Chats;
-messages.getWebPage#32ca8f91 url:string hash:int = WebPage;
-messages.toggleDialogPin#a731e257 flags:# pinned:flags.0?true peer:InputDialogPeer = Bool;
-messages.reorderPinnedDialogs#3b1adf37 flags:# force:flags.0?true folder_id:int order:Vector<InputDialogPeer> = Bool;
-messages.getPinnedDialogs#d6b94df2 folder_id:int = messages.PeerDialogs;
-messages.setBotShippingResults#e5f672fa flags:# query_id:long error:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = Bool;
-messages.setBotPrecheckoutResults#9c2dd95 flags:# success:flags.1?true query_id:long error:flags.0?string = Bool;
-messages.uploadMedia#519bc2b1 peer:InputPeer media:InputMedia = MessageMedia;
-messages.sendScreenshotNotification#c97df020 peer:InputPeer reply_to_msg_id:int random_id:long = Updates;
-messages.getFavedStickers#4f1aaa9 hash:long = messages.FavedStickers;
-messages.faveSticker#b9ffc55b id:InputDocument unfave:Bool = Bool;
-messages.getUnreadMentions#46578472 peer:InputPeer offset_id:int add_offset:int limit:int max_id:int min_id:int = messages.Messages;
-messages.readMentions#f0189d3 peer:InputPeer = messages.AffectedHistory;
-messages.getRecentLocations#702a40e0 peer:InputPeer limit:int hash:long = messages.Messages;
-messages.sendMultiMedia#cc0110cb flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int multi_media:Vector<InputSingleMedia> schedule_date:flags.10?int = Updates;
-messages.uploadEncryptedFile#5057c497 peer:InputEncryptedChat file:InputEncryptedFile = EncryptedFile;
-messages.searchStickerSets#35705b8a flags:# exclude_featured:flags.0?true q:string hash:long = messages.FoundStickerSets;
-messages.getSplitRanges#1cff7e08 = Vector<MessageRange>;
-messages.markDialogUnread#c286d98f flags:# unread:flags.0?true peer:InputDialogPeer = Bool;
-messages.getDialogUnreadMarks#22e24e22 = Vector<DialogPeer>;
-messages.clearAllDrafts#7e58ee9c = Bool;
-messages.updatePinnedMessage#d2aaf7ec flags:# silent:flags.0?true unpin:flags.1?true pm_oneside:flags.2?true peer:InputPeer id:int = Updates;
-messages.sendVote#10ea6184 peer:InputPeer msg_id:int options:Vector<bytes> = Updates;
-messages.getPollResults#73bb643b peer:InputPeer msg_id:int = Updates;
-messages.getOnlines#6e2be050 peer:InputPeer = ChatOnlines;
-messages.editChatAbout#def60797 peer:InputPeer about:string = Bool;
-messages.editChatDefaultBannedRights#a5866b41 peer:InputPeer banned_rights:ChatBannedRights = Updates;
-messages.getEmojiKeywords#35a0e062 lang_code:string = EmojiKeywordsDifference;
-messages.getEmojiKeywordsDifference#1508b6af lang_code:string from_version:int = EmojiKeywordsDifference;
-messages.getEmojiKeywordsLanguages#4e9963b2 lang_codes:Vector<string> = Vector<EmojiLanguage>;
-messages.getEmojiURL#d5b10c26 lang_code:string = EmojiURL;
-messages.getSearchCounters#732eef00 peer:InputPeer filters:Vector<MessagesFilter> = Vector<messages.SearchCounter>;
-messages.requestUrlAuth#198fb446 flags:# peer:flags.1?InputPeer msg_id:flags.1?int button_id:flags.1?int url:flags.2?string = UrlAuthResult;
-messages.acceptUrlAuth#b12c7125 flags:# write_allowed:flags.0?true peer:flags.1?InputPeer msg_id:flags.1?int button_id:flags.1?int url:flags.2?string = UrlAuthResult;
-messages.hidePeerSettingsBar#4facb138 peer:InputPeer = Bool;
-messages.getScheduledHistory#f516760b peer:InputPeer hash:long = messages.Messages;
-messages.getScheduledMessages#bdbb0464 peer:InputPeer id:Vector<int> = messages.Messages;
-messages.sendScheduledMessages#bd38850a peer:InputPeer id:Vector<int> = Updates;
-messages.deleteScheduledMessages#59ae2b16 peer:InputPeer id:Vector<int> = Updates;
-messages.getPollVotes#b86e380e flags:# peer:InputPeer id:int option:flags.0?bytes offset:flags.1?string limit:int = messages.VotesList;
-messages.toggleStickerSets#b5052fea flags:# uninstall:flags.0?true archive:flags.1?true unarchive:flags.2?true stickersets:Vector<InputStickerSet> = Bool;
-messages.getDialogFilters#f19ed96d = Vector<DialogFilter>;
-messages.getSuggestedDialogFilters#a29cd42c = Vector<DialogFilterSuggested>;
-messages.updateDialogFilter#1ad4a04a flags:# id:int filter:flags.0?DialogFilter = Bool;
-messages.updateDialogFiltersOrder#c563c1e4 order:Vector<int> = Bool;
-messages.getOldFeaturedStickers#7ed094a1 offset:int limit:int hash:long = messages.FeaturedStickers;
-messages.getReplies#22ddd30c peer:InputPeer msg_id:int offset_id:int offset_date:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
-messages.getDiscussionMessage#446972fd peer:InputPeer msg_id:int = messages.DiscussionMessage;
-messages.readDiscussion#f731a9f4 peer:InputPeer msg_id:int read_max_id:int = Bool;
-messages.unpinAllMessages#f025bc8b peer:InputPeer = messages.AffectedHistory;
-messages.deleteChat#5bd0ee50 chat_id:long = Bool;
-messages.deletePhoneCallHistory#f9cbe409 flags:# revoke:flags.0?true = messages.AffectedFoundMessages;
-messages.checkHistoryImport#43fe19f3 import_head:string = messages.HistoryImportParsed;
-messages.initHistoryImport#34090c3b peer:InputPeer file:InputFile media_count:int = messages.HistoryImport;
-messages.uploadImportedMedia#2a862092 peer:InputPeer import_id:long file_name:string media:InputMedia = MessageMedia;
-messages.startHistoryImport#b43df344 peer:InputPeer import_id:long = Bool;
-messages.getExportedChatInvites#a2b5a3f6 flags:# revoked:flags.3?true peer:InputPeer admin_id:InputUser offset_date:flags.2?int offset_link:flags.2?string limit:int = messages.ExportedChatInvites;
-messages.getExportedChatInvite#73746f5c peer:InputPeer link:string = messages.ExportedChatInvite;
-messages.editExportedChatInvite#2e4ffbe flags:# revoked:flags.2?true peer:InputPeer link:string expire_date:flags.0?int usage_limit:flags.1?int = messages.ExportedChatInvite;
-messages.deleteRevokedExportedChatInvites#56987bd5 peer:InputPeer admin_id:InputUser = Bool;
-messages.deleteExportedChatInvite#d464a42b peer:InputPeer link:string = Bool;
-messages.getAdminsWithInvites#3920e6ef peer:InputPeer = messages.ChatAdminsWithInvites;
-messages.getChatInviteImporters#26fb7289 peer:InputPeer link:string offset_date:int offset_user:InputUser limit:int = messages.ChatInviteImporters;
-messages.setHistoryTTL#b80e5fe4 peer:InputPeer period:int = Updates;
-messages.checkHistoryImportPeer#5dc60f03 peer:InputPeer = messages.CheckedHistoryImportPeer;
-messages.setChatTheme#e63be13f peer:InputPeer emoticon:string = Updates;
-messages.getMessageReadParticipants#2c6f97b7 peer:InputPeer msg_id:int = Vector<long>;
-
-updates.getState#edd4882a = updates.State;
-updates.getDifference#25939651 flags:# pts:int pts_total_limit:flags.0?int date:int qts:int = updates.Difference;
-updates.getChannelDifference#3173d78 flags:# force:flags.0?true channel:InputChannel filter:ChannelMessagesFilter pts:int limit:int = updates.ChannelDifference;
-
-photos.updateProfilePhoto#72d4742c id:InputPhoto = photos.Photo;
-photos.uploadProfilePhoto#89f30f69 flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = photos.Photo;
-photos.deletePhotos#87cf7f2f id:Vector<InputPhoto> = Vector<long>;
-photos.getUserPhotos#91cd32a8 user_id:InputUser offset:int max_id:long limit:int = photos.Photos;
-
-upload.saveFilePart#b304a621 file_id:long file_part:int bytes:bytes = Bool;
-upload.getFile#b15a9afc flags:# precise:flags.0?true cdn_supported:flags.1?true location:InputFileLocation offset:int limit:int = upload.File;
-upload.saveBigFilePart#de7b673d file_id:long file_part:int file_total_parts:int bytes:bytes = Bool;
-upload.getWebFile#24e6818d location:InputWebFileLocation offset:int limit:int = upload.WebFile;
-upload.getCdnFile#2000bcc3 file_token:bytes offset:int limit:int = upload.CdnFile;
-upload.reuploadCdnFile#9b2754a8 file_token:bytes request_token:bytes = Vector<FileHash>;
-upload.getCdnFileHashes#4da54231 file_token:bytes offset:int = Vector<FileHash>;
-upload.getFileHashes#c7025931 location:InputFileLocation offset:int = Vector<FileHash>;
-
-help.getConfig#c4f9186b = Config;
-help.getNearestDc#1fb33026 = NearestDc;
-help.getAppUpdate#522d5a7d source:string = help.AppUpdate;
-help.getInviteText#4d392343 = help.InviteText;
-help.getSupport#9cdf08cd = help.Support;
-help.getAppChangelog#9010ef6f prev_app_version:string = Updates;
-help.setBotUpdatesStatus#ec22cfcd pending_updates_count:int message:string = Bool;
-help.getCdnConfig#52029342 = CdnConfig;
-help.getRecentMeUrls#3dc0f114 referer:string = help.RecentMeUrls;
-help.getTermsOfServiceUpdate#2ca51fd1 = help.TermsOfServiceUpdate;
-help.acceptTermsOfService#ee72f79a id:DataJSON = Bool;
-help.getDeepLinkInfo#3fedc75f path:string = help.DeepLinkInfo;
-help.getAppConfig#98914110 = JSONValue;
-help.saveAppLog#6f02f748 events:Vector<InputAppEvent> = Bool;
-help.getPassportConfig#c661ad08 hash:int = help.PassportConfig;
-help.getSupportName#d360e72c = help.SupportName;
-help.getUserInfo#38a08d3 user_id:InputUser = help.UserInfo;
-help.editUserInfo#66b91b70 user_id:InputUser message:string entities:Vector<MessageEntity> = help.UserInfo;
-help.getPromoData#c0977421 = help.PromoData;
-help.hidePromoData#1e251c95 peer:InputPeer = Bool;
-help.dismissSuggestion#f50dbaa1 peer:InputPeer suggestion:string = Bool;
-help.getCountriesList#735787a8 lang_code:string hash:int = help.CountriesList;
-
-channels.readHistory#cc104937 channel:InputChannel max_id:int = Bool;
-channels.deleteMessages#84c1fd4e channel:InputChannel id:Vector<int> = messages.AffectedMessages;
-channels.deleteUserHistory#d10dd71b channel:InputChannel user_id:InputUser = messages.AffectedHistory;
-channels.reportSpam#fe087810 channel:InputChannel user_id:InputUser id:Vector<int> = Bool;
-channels.getMessages#ad8c9a23 channel:InputChannel id:Vector<InputMessage> = messages.Messages;
-channels.getParticipants#77ced9d0 channel:InputChannel filter:ChannelParticipantsFilter offset:int limit:int hash:long = channels.ChannelParticipants;
-channels.getParticipant#a0ab6cc6 channel:InputChannel participant:InputPeer = channels.ChannelParticipant;
-channels.getChannels#a7f6bbb id:Vector<InputChannel> = messages.Chats;
-channels.getFullChannel#8736a09 channel:InputChannel = messages.ChatFull;
-channels.createChannel#3d5fb10f flags:# broadcast:flags.0?true megagroup:flags.1?true for_import:flags.3?true title:string about:string geo_point:flags.2?InputGeoPoint address:flags.2?string = Updates;
-channels.editAdmin#d33c8902 channel:InputChannel user_id:InputUser admin_rights:ChatAdminRights rank:string = Updates;
-channels.editTitle#566decd0 channel:InputChannel title:string = Updates;
-channels.editPhoto#f12e57c9 channel:InputChannel photo:InputChatPhoto = Updates;
-channels.checkUsername#10e6bd2c channel:InputChannel username:string = Bool;
-channels.updateUsername#3514b3de channel:InputChannel username:string = Bool;
-channels.joinChannel#24b524c5 channel:InputChannel = Updates;
-channels.leaveChannel#f836aa95 channel:InputChannel = Updates;
-channels.inviteToChannel#199f3a6c channel:InputChannel users:Vector<InputUser> = Updates;
-channels.deleteChannel#c0111fe3 channel:InputChannel = Updates;
-channels.exportMessageLink#e63fadeb flags:# grouped:flags.0?true thread:flags.1?true channel:InputChannel id:int = ExportedMessageLink;
-channels.toggleSignatures#1f69b606 channel:InputChannel enabled:Bool = Updates;
-channels.getAdminedPublicChannels#f8b036af flags:# by_location:flags.0?true check_limit:flags.1?true = messages.Chats;
-channels.editBanned#96e6cd81 channel:InputChannel participant:InputPeer banned_rights:ChatBannedRights = Updates;
-channels.getAdminLog#33ddf480 flags:# channel:InputChannel q:string events_filter:flags.0?ChannelAdminLogEventsFilter admins:flags.1?Vector<InputUser> max_id:long min_id:long limit:int = channels.AdminLogResults;
-channels.setStickers#ea8ca4f9 channel:InputChannel stickerset:InputStickerSet = Bool;
-channels.readMessageContents#eab5dc38 channel:InputChannel id:Vector<int> = Bool;
-channels.deleteHistory#af369d42 channel:InputChannel max_id:int = Bool;
-channels.togglePreHistoryHidden#eabbb94c channel:InputChannel enabled:Bool = Updates;
-channels.getLeftChannels#8341ecc0 offset:int = messages.Chats;
-channels.getGroupsForDiscussion#f5dad378 = messages.Chats;
-channels.setDiscussionGroup#40582bb2 broadcast:InputChannel group:InputChannel = Bool;
-channels.editCreator#8f38cd1f channel:InputChannel user_id:InputUser password:InputCheckPasswordSRP = Updates;
-channels.editLocation#58e63f6d channel:InputChannel geo_point:InputGeoPoint address:string = Bool;
-channels.toggleSlowMode#edd49ef0 channel:InputChannel seconds:int = Updates;
-channels.getInactiveChannels#11e831ee = messages.InactiveChats;
-channels.convertToGigagroup#b290c69 channel:InputChannel = Updates;
-channels.viewSponsoredMessage#beaedb94 channel:InputChannel random_id:bytes = Bool;
-channels.getSponsoredMessages#ec210fbf channel:InputChannel = messages.SponsoredMessages;
-
-bots.sendCustomRequest#aa2769ed custom_method:string params:DataJSON = DataJSON;
-bots.answerWebhookJSONQuery#e6213f4d query_id:long data:DataJSON = Bool;
-bots.setBotCommands#517165a scope:BotCommandScope lang_code:string commands:Vector<BotCommand> = Bool;
-bots.resetBotCommands#3d8de0f9 scope:BotCommandScope lang_code:string = Bool;
-bots.getBotCommands#e34c0dd6 scope:BotCommandScope lang_code:string = Vector<BotCommand>;
-
-payments.getPaymentForm#8a333c8d flags:# peer:InputPeer msg_id:int theme_params:flags.0?DataJSON = payments.PaymentForm;
-payments.getPaymentReceipt#2478d1cc peer:InputPeer msg_id:int = payments.PaymentReceipt;
-payments.validateRequestedInfo#db103170 flags:# save:flags.0?true peer:InputPeer msg_id:int info:PaymentRequestedInfo = payments.ValidatedRequestedInfo;
-payments.sendPaymentForm#30c3bc9d flags:# form_id:long peer:InputPeer msg_id:int requested_info_id:flags.0?string shipping_option_id:flags.1?string credentials:InputPaymentCredentials tip_amount:flags.2?long = payments.PaymentResult;
-payments.getSavedInfo#227d824b = payments.SavedInfo;
-payments.clearSavedInfo#d83d70c1 flags:# credentials:flags.0?true info:flags.1?true = Bool;
-payments.getBankCardData#2e79d779 number:string = payments.BankCardData;
-
-stickers.createStickerSet#9021ab67 flags:# masks:flags.0?true animated:flags.1?true videos:flags.4?true user_id:InputUser title:string short_name:string thumb:flags.2?InputDocument stickers:Vector<InputStickerSetItem> software:flags.3?string = messages.StickerSet;
-stickers.removeStickerFromSet#f7760f51 sticker:InputDocument = messages.StickerSet;
-stickers.changeStickerPosition#ffb6d4ca sticker:InputDocument position:int = messages.StickerSet;
-stickers.addStickerToSet#8653febe stickerset:InputStickerSet sticker:InputStickerSetItem = messages.StickerSet;
-stickers.setStickerSetThumb#9a364e30 stickerset:InputStickerSet thumb:InputDocument = messages.StickerSet;
-stickers.checkShortName#284b3639 short_name:string = Bool;
-stickers.suggestShortName#4dafc503 title:string = stickers.SuggestedShortName;
-
-phone.getCallConfig#55451fa9 = DataJSON;
-phone.requestCall#42ff96ed flags:# video:flags.0?true user_id:InputUser random_id:int g_a_hash:bytes protocol:PhoneCallProtocol = phone.PhoneCall;
-phone.acceptCall#3bd2b4a0 peer:InputPhoneCall g_b:bytes protocol:PhoneCallProtocol = phone.PhoneCall;
-phone.confirmCall#2efe1722 peer:InputPhoneCall g_a:bytes key_fingerprint:long protocol:PhoneCallProtocol = phone.PhoneCall;
-phone.receivedCall#17d54f61 peer:InputPhoneCall = Bool;
-phone.discardCall#b2cbc1c0 flags:# video:flags.0?true peer:InputPhoneCall duration:int reason:PhoneCallDiscardReason connection_id:long = Updates;
-phone.setCallRating#59ead627 flags:# user_initiative:flags.0?true peer:InputPhoneCall rating:int comment:string = Updates;
-phone.saveCallDebug#277add7e peer:InputPhoneCall debug:DataJSON = Bool;
-phone.sendSignalingData#ff7a9383 peer:InputPhoneCall data:bytes = Bool;
-phone.createGroupCall#48cdc6d8 flags:# peer:InputPeer random_id:int title:flags.0?string schedule_date:flags.1?int = Updates;
-phone.joinGroupCall#b132ff7b flags:# muted:flags.0?true video_stopped:flags.2?true call:InputGroupCall join_as:InputPeer invite_hash:flags.1?string params:DataJSON = Updates;
-phone.leaveGroupCall#500377f9 call:InputGroupCall source:int = Updates;
-phone.inviteToGroupCall#7b393160 call:InputGroupCall users:Vector<InputUser> = Updates;
-phone.discardGroupCall#7a777135 call:InputGroupCall = Updates;
-phone.toggleGroupCallSettings#74bbb43d flags:# reset_invite_hash:flags.1?true call:InputGroupCall join_muted:flags.0?Bool = Updates;
-phone.getGroupCall#41845db call:InputGroupCall limit:int = phone.GroupCall;
-phone.getGroupParticipants#c558d8ab call:InputGroupCall ids:Vector<InputPeer> sources:Vector<int> offset:string limit:int = phone.GroupParticipants;
-phone.checkGroupCall#b59cf977 call:InputGroupCall sources:Vector<int> = Vector<int>;
-phone.toggleGroupCallRecord#f128c708 flags:# start:flags.0?true video:flags.2?true call:InputGroupCall title:flags.1?string video_portrait:flags.2?Bool = Updates;
-phone.editGroupCallParticipant#a5273abf flags:# call:InputGroupCall participant:InputPeer muted:flags.0?Bool volume:flags.1?int raise_hand:flags.2?Bool video_stopped:flags.3?Bool video_paused:flags.4?Bool presentation_paused:flags.5?Bool = Updates;
-phone.editGroupCallTitle#1ca6ac0a call:InputGroupCall title:string = Updates;
-phone.getGroupCallJoinAs#ef7c213a peer:InputPeer = phone.JoinAsPeers;
-phone.exportGroupCallInvite#e6aa647f flags:# can_self_unmute:flags.0?true call:InputGroupCall = phone.ExportedGroupCallInvite;
-phone.toggleGroupCallStartSubscription#219c34e6 call:InputGroupCall subscribed:Bool = Updates;
-phone.startScheduledGroupCall#5680e342 call:InputGroupCall = Updates;
-phone.saveDefaultGroupCallJoinAs#575e1f8c peer:InputPeer join_as:InputPeer = Bool;
-phone.joinGroupCallPresentation#cbea6bc4 call:InputGroupCall params:DataJSON = Updates;
-phone.leaveGroupCallPresentation#1c50d144 call:InputGroupCall = Updates;
-
-langpack.getLangPack#f2f2330a lang_pack:string lang_code:string = LangPackDifference;
-langpack.getStrings#efea3803 lang_pack:string lang_code:string keys:Vector<string> = Vector<LangPackString>;
-langpack.getDifference#cd984aa5 lang_pack:string lang_code:string from_version:int = LangPackDifference;
-langpack.getLanguages#42c6978f lang_pack:string = Vector<LangPackLanguage>;
-langpack.getLanguage#6a596502 lang_pack:string lang_code:string = LangPackLanguage;
-
-folders.editPeerFolders#6847d0ab folder_peers:Vector<InputFolderPeer> = Updates;
-folders.deleteFolder#1c295881 folder_id:int = Updates;
-
-stats.getBroadcastStats#ab42441a flags:# dark:flags.0?true channel:InputChannel = stats.BroadcastStats;
-stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;
-stats.getMegagroupStats#dcdf8607 flags:# dark:flags.0?true channel:InputChannel = stats.MegagroupStats;
-stats.getMessagePublicForwards#5630281b channel:InputChannel msg_id:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;
-stats.getMessageStats#b6e0a3f5 flags:# dark:flags.0?true channel:InputChannel msg_id:int = stats.MessageStats;
-
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/schema/end-to-end-json.html b/data/core.telegram.org/schema/end-to-end-json.html deleted file mode 100644 index 6c3b4f2cbe..0000000000 --- a/data/core.telegram.org/schema/end-to-end-json.html +++ /dev/null @@ -1 +0,0 @@ -{"constructors":[{"id":"528568095","predicate":"decryptedMessage","params":[{"name":"random_id","type":"long"},{"name":"random_bytes","type":"bytes"},{"name":"message","type":"string"},{"name":"media","type":"DecryptedMessageMedia"}],"type":"DecryptedMessage","layer":8},{"id":"541931640","predicate":"decryptedMessage","params":[{"name":"random_id","type":"long"},{"name":"ttl","type":"int"},{"name":"message","type":"string"},{"name":"media","type":"DecryptedMessageMedia"}],"type":"DecryptedMessage","layer":17},{"id":"917541342","predicate":"decryptedMessage","params":[{"name":"flags","type":"#"},{"name":"random_id","type":"long"},{"name":"ttl","type":"int"},{"name":"message","type":"string"},{"name":"media","type":"flags.9?DecryptedMessageMedia"},{"name":"entities","type":"flags.7?Vector"},{"name":"via_bot_name","type":"flags.11?string"},{"name":"reply_to_random_id","type":"flags.3?long"}],"type":"DecryptedMessage","layer":45},{"id":"-1848883596","predicate":"decryptedMessage","params":[{"name":"flags","type":"#"},{"name":"random_id","type":"long"},{"name":"ttl","type":"int"},{"name":"message","type":"string"},{"name":"media","type":"flags.9?DecryptedMessageMedia"},{"name":"entities","type":"flags.7?Vector"},{"name":"via_bot_name","type":"flags.11?string"},{"name":"reply_to_random_id","type":"flags.3?long"},{"name":"grouped_id","type":"flags.17?long"}],"type":"DecryptedMessage","layer":73},{"id":"-1438109059","predicate":"decryptedMessageService","params":[{"name":"random_id","type":"long"},{"name":"random_bytes","type":"bytes"},{"name":"action","type":"DecryptedMessageAction"}],"type":"DecryptedMessage","layer":8},{"id":"1930838368","predicate":"decryptedMessageService","params":[{"name":"random_id","type":"long"},{"name":"action","type":"DecryptedMessageAction"}],"type":"DecryptedMessage","layer":17},{"id":"144661578","predicate":"decryptedMessageMediaEmpty","params":[],"type":"DecryptedMessageMedia","layer":8},{"id":"846826124","predicate":"decryptedMessageMediaPhoto","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":8},{"id":"-235238024","predicate":"decryptedMessageMediaPhoto","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"},{"name":"caption","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"1290694387","predicate":"decryptedMessageMediaVideo","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"duration","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":8},{"id":"1380598109","predicate":"decryptedMessageMediaVideo","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"duration","type":"int"},{"name":"mime_type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":17},{"id":"-1760785394","predicate":"decryptedMessageMediaVideo","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"duration","type":"int"},{"name":"mime_type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"},{"name":"caption","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"893913689","predicate":"decryptedMessageMediaGeoPoint","params":[{"name":"lat","type":"double"},{"name":"long","type":"double"}],"type":"DecryptedMessageMedia","layer":8},{"id":"1485441687","predicate":"decryptedMessageMediaContact","params":[{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"user_id","type":"int"}],"type":"DecryptedMessageMedia","layer":8},{"id":"-1586283796","predicate":"decryptedMessageActionSetMessageTTL","params":[{"name":"ttl_seconds","type":"int"}],"type":"DecryptedMessageAction","layer":8},{"id":"-1332395189","predicate":"decryptedMessageMediaDocument","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"file_name","type":"string"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":8},{"id":"2063502050","predicate":"decryptedMessageMediaDocument","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"},{"name":"attributes","type":"Vector"},{"name":"caption","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"1619031439","predicate":"decryptedMessageMediaAudio","params":[{"name":"duration","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":8},{"id":"1474341323","predicate":"decryptedMessageMediaAudio","params":[{"name":"duration","type":"int"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":17},{"id":"206520510","predicate":"decryptedMessageActionReadMessages","params":[{"name":"random_ids","type":"Vector"}],"type":"DecryptedMessageAction","layer":8},{"id":"1700872964","predicate":"decryptedMessageActionDeleteMessages","params":[{"name":"random_ids","type":"Vector"}],"type":"DecryptedMessageAction","layer":8},{"id":"-1967000459","predicate":"decryptedMessageActionScreenshotMessages","params":[{"name":"random_ids","type":"Vector"}],"type":"DecryptedMessageAction","layer":8},{"id":"1729750108","predicate":"decryptedMessageActionFlushHistory","params":[],"type":"DecryptedMessageAction","layer":8},{"id":"467867529","predicate":"decryptedMessageLayer","params":[{"name":"random_bytes","type":"bytes"},{"name":"layer","type":"int"},{"name":"in_seq_no","type":"int"},{"name":"out_seq_no","type":"int"},{"name":"message","type":"DecryptedMessage"}],"type":"DecryptedMessageLayer","layer":17},{"id":"381645902","predicate":"sendMessageTypingAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-44119819","predicate":"sendMessageCancelAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-1584933265","predicate":"sendMessageRecordVideoAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-1845219337","predicate":"sendMessageUploadVideoAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-718310409","predicate":"sendMessageRecordAudioAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-424899985","predicate":"sendMessageUploadAudioAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-1727382502","predicate":"sendMessageUploadPhotoAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-1884362354","predicate":"sendMessageUploadDocumentAction","params":[],"type":"SendMessageAction","layer":17},{"id":"393186209","predicate":"sendMessageGeoLocationAction","params":[],"type":"SendMessageAction","layer":17},{"id":"1653390447","predicate":"sendMessageChooseContactAction","params":[],"type":"SendMessageAction","layer":17},{"id":"1360072880","predicate":"decryptedMessageActionResend","params":[{"name":"start_seq_no","type":"int"},{"name":"end_seq_no","type":"int"}],"type":"DecryptedMessageAction","layer":17},{"id":"-217806717","predicate":"decryptedMessageActionNotifyLayer","params":[{"name":"layer","type":"int"}],"type":"DecryptedMessageAction","layer":17},{"id":"-860719551","predicate":"decryptedMessageActionTyping","params":[{"name":"action","type":"SendMessageAction"}],"type":"DecryptedMessageAction","layer":17},{"id":"-204906213","predicate":"decryptedMessageActionRequestKey","params":[{"name":"exchange_id","type":"long"},{"name":"g_a","type":"bytes"}],"type":"DecryptedMessageAction","layer":20},{"id":"1877046107","predicate":"decryptedMessageActionAcceptKey","params":[{"name":"exchange_id","type":"long"},{"name":"g_b","type":"bytes"},{"name":"key_fingerprint","type":"long"}],"type":"DecryptedMessageAction","layer":20},{"id":"-586814357","predicate":"decryptedMessageActionAbortKey","params":[{"name":"exchange_id","type":"long"}],"type":"DecryptedMessageAction","layer":20},{"id":"-332526693","predicate":"decryptedMessageActionCommitKey","params":[{"name":"exchange_id","type":"long"},{"name":"key_fingerprint","type":"long"}],"type":"DecryptedMessageAction","layer":20},{"id":"-1473258141","predicate":"decryptedMessageActionNoop","params":[],"type":"DecryptedMessageAction","layer":20},{"id":"1815593308","predicate":"documentAttributeImageSize","params":[{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute","layer":23},{"id":"297109817","predicate":"documentAttributeAnimated","params":[],"type":"DocumentAttribute","layer":23},{"id":"-83208409","predicate":"documentAttributeSticker","params":[],"type":"DocumentAttribute","layer":23},{"id":"978674434","predicate":"documentAttributeSticker","params":[{"name":"alt","type":"string"},{"name":"stickerset","type":"InputStickerSet"}],"type":"DocumentAttribute","layer":45},{"id":"1494273227","predicate":"documentAttributeVideo","params":[{"name":"duration","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute","layer":23},{"id":"250621158","predicate":"documentAttributeVideo","params":[{"name":"flags","type":"#"},{"name":"duration","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute","layer":66},{"id":"85215461","predicate":"documentAttributeAudio","params":[{"name":"duration","type":"int"}],"type":"DocumentAttribute","layer":23},{"id":"-556656416","predicate":"documentAttributeAudio","params":[{"name":"duration","type":"int"},{"name":"title","type":"string"},{"name":"performer","type":"string"}],"type":"DocumentAttribute","layer":45},{"id":"-1739392570","predicate":"documentAttributeAudio","params":[{"name":"flags","type":"#"},{"name":"duration","type":"int"},{"name":"title","type":"flags.0?string"},{"name":"performer","type":"flags.1?string"},{"name":"waveform","type":"flags.2?bytes"}],"type":"DocumentAttribute","layer":46},{"id":"358154344","predicate":"documentAttributeFilename","params":[{"name":"file_name","type":"string"}],"type":"DocumentAttribute","layer":23},{"id":"236446268","predicate":"photoSizeEmpty","params":[{"name":"type","type":"string"}],"type":"PhotoSize","layer":23},{"id":"2009052699","predicate":"photoSize","params":[{"name":"type","type":"string"},{"name":"location","type":"FileLocation"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"}],"type":"PhotoSize","layer":23},{"id":"-374917894","predicate":"photoCachedSize","params":[{"name":"type","type":"string"},{"name":"location","type":"FileLocation"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"bytes","type":"bytes"}],"type":"PhotoSize","layer":23},{"id":"2086234950","predicate":"fileLocationUnavailable","params":[{"name":"volume_id","type":"long"},{"name":"local_id","type":"int"},{"name":"secret","type":"long"}],"type":"FileLocation","layer":23},{"id":"1406570614","predicate":"fileLocation","params":[{"name":"dc_id","type":"int"},{"name":"volume_id","type":"long"},{"name":"local_id","type":"int"},{"name":"secret","type":"long"}],"type":"FileLocation","layer":23},{"id":"-90853155","predicate":"decryptedMessageMediaExternalDocument","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"thumb","type":"PhotoSize"},{"name":"dc_id","type":"int"},{"name":"attributes","type":"Vector"}],"type":"DecryptedMessageMedia","layer":23},{"id":"-1148011883","predicate":"messageEntityUnknown","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"-100378723","predicate":"messageEntityMention","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1868782349","predicate":"messageEntityHashtag","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1827637959","predicate":"messageEntityBotCommand","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1859134776","predicate":"messageEntityUrl","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1692693954","predicate":"messageEntityEmail","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"-1117713463","predicate":"messageEntityBold","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"-2106619040","predicate":"messageEntityItalic","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"681706865","predicate":"messageEntityCode","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1938967520","predicate":"messageEntityPre","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"language","type":"string"}],"type":"MessageEntity","layer":45},{"id":"1990644519","predicate":"messageEntityTextUrl","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"url","type":"string"}],"type":"MessageEntity","layer":45},{"id":"-2044933984","predicate":"inputStickerSetShortName","params":[{"name":"short_name","type":"string"}],"type":"InputStickerSet","layer":45},{"id":"-4838507","predicate":"inputStickerSetEmpty","params":[],"type":"InputStickerSet","layer":45},{"id":"-1978796689","predicate":"decryptedMessageMediaVenue","params":[{"name":"lat","type":"double"},{"name":"long","type":"double"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"-452652584","predicate":"decryptedMessageMediaWebPage","params":[{"name":"url","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"-1997373508","predicate":"sendMessageRecordRoundAction","params":[],"type":"SendMessageAction","layer":66},{"id":"-1150187996","predicate":"sendMessageUploadRoundAction","params":[],"type":"SendMessageAction","layer":66}],"methods":[]} \ No newline at end of file diff --git a/data/core.telegram.org/schema/end-to-end.html b/data/core.telegram.org/schema/end-to-end.html deleted file mode 100644 index 05edef7f0d..0000000000 --- a/data/core.telegram.org/schema/end-to-end.html +++ /dev/null @@ -1,225 +0,0 @@ - - - - - Current end-to-end TL-schema - - - - - - - - - - - - - -
- -
-
-
- -

Current end-to-end TL-schema

- -
-

Below you will find the current end-to-end TL-schema. More details on TL »

-
-

See also:
-End-to-end encryption in MTProto, Secret Chats
-Detailed schema in JSON

-
- -
-
===8===
-decryptedMessage#1f814f1f random_id:long random_bytes:bytes message:string media:DecryptedMessageMedia = DecryptedMessage;
-decryptedMessageService#aa48327d random_id:long random_bytes:bytes action:DecryptedMessageAction = DecryptedMessage;
-decryptedMessageMediaEmpty#89f5c4a = DecryptedMessageMedia;
-decryptedMessageMediaPhoto#32798a8c thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageMediaVideo#4cee6ef3 thumb:bytes thumb_w:int thumb_h:int duration:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageMediaGeoPoint#35480a59 lat:double long:double = DecryptedMessageMedia;
-decryptedMessageMediaContact#588a0a97 phone_number:string first_name:string last_name:string user_id:int = DecryptedMessageMedia;
-decryptedMessageActionSetMessageTTL#a1733aec ttl_seconds:int = DecryptedMessageAction;
-decryptedMessageMediaDocument#b095434b thumb:bytes thumb_w:int thumb_h:int file_name:string mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageMediaAudio#6080758f duration:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageActionReadMessages#c4f40be random_ids:Vector<long> = DecryptedMessageAction;
-decryptedMessageActionDeleteMessages#65614304 random_ids:Vector<long> = DecryptedMessageAction;
-decryptedMessageActionScreenshotMessages#8ac1f475 random_ids:Vector<long> = DecryptedMessageAction;
-decryptedMessageActionFlushHistory#6719e45c = DecryptedMessageAction;
-
-===17===
-decryptedMessage#204d3878 random_id:long ttl:int message:string media:DecryptedMessageMedia = DecryptedMessage;
-decryptedMessageService#73164160 random_id:long action:DecryptedMessageAction = DecryptedMessage;
-decryptedMessageMediaVideo#524a415d thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageMediaAudio#57e0a9cb duration:int mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageLayer#1be31789 random_bytes:bytes layer:int in_seq_no:int out_seq_no:int message:DecryptedMessage = DecryptedMessageLayer;
-sendMessageTypingAction#16bf744e = SendMessageAction;
-sendMessageCancelAction#fd5ec8f5 = SendMessageAction;
-sendMessageRecordVideoAction#a187d66f = SendMessageAction;
-sendMessageUploadVideoAction#92042ff7 = SendMessageAction;
-sendMessageRecordAudioAction#d52f73f7 = SendMessageAction;
-sendMessageUploadAudioAction#e6ac8a6f = SendMessageAction;
-sendMessageUploadPhotoAction#990a3c1a = SendMessageAction;
-sendMessageUploadDocumentAction#8faee98e = SendMessageAction;
-sendMessageGeoLocationAction#176f8ba1 = SendMessageAction;
-sendMessageChooseContactAction#628cbc6f = SendMessageAction;
-decryptedMessageActionResend#511110b0 start_seq_no:int end_seq_no:int = DecryptedMessageAction;
-decryptedMessageActionNotifyLayer#f3048883 layer:int = DecryptedMessageAction;
-decryptedMessageActionTyping#ccb27641 action:SendMessageAction = DecryptedMessageAction;
-
-===20===
-decryptedMessageActionRequestKey#f3c9611b exchange_id:long g_a:bytes = DecryptedMessageAction;
-decryptedMessageActionAcceptKey#6fe1735b exchange_id:long g_b:bytes key_fingerprint:long = DecryptedMessageAction;
-decryptedMessageActionAbortKey#dd05ec6b exchange_id:long = DecryptedMessageAction;
-decryptedMessageActionCommitKey#ec2e0b9b exchange_id:long key_fingerprint:long = DecryptedMessageAction;
-decryptedMessageActionNoop#a82fdd63 = DecryptedMessageAction;
-
-===23===
-documentAttributeImageSize#6c37c15c w:int h:int = DocumentAttribute;
-documentAttributeAnimated#11b58939 = DocumentAttribute;
-documentAttributeSticker#fb0a5727 = DocumentAttribute;
-documentAttributeVideo#5910cccb duration:int w:int h:int = DocumentAttribute;
-documentAttributeAudio#51448e5 duration:int = DocumentAttribute;
-documentAttributeFilename#15590068 file_name:string = DocumentAttribute;
-photoSizeEmpty#e17e23c type:string = PhotoSize;
-photoSize#77bfb61b type:string location:FileLocation w:int h:int size:int = PhotoSize;
-photoCachedSize#e9a734fa type:string location:FileLocation w:int h:int bytes:bytes = PhotoSize;
-fileLocationUnavailable#7c596b46 volume_id:long local_id:int secret:long = FileLocation;
-fileLocation#53d69076 dc_id:int volume_id:long local_id:int secret:long = FileLocation;
-decryptedMessageMediaExternalDocument#fa95b0dd id:long access_hash:long date:int mime_type:string size:int thumb:PhotoSize dc_id:int attributes:Vector<DocumentAttribute> = DecryptedMessageMedia;
-
-===45===
-decryptedMessage#36b091de flags:# random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long = DecryptedMessage;
-decryptedMessageMediaPhoto#f1fa8d78 thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;
-decryptedMessageMediaVideo#970c8c0e thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;
-decryptedMessageMediaDocument#7afe8ae2 thumb:bytes thumb_w:int thumb_h:int mime_type:string size:int key:bytes iv:bytes attributes:Vector<DocumentAttribute> caption:string = DecryptedMessageMedia;
-documentAttributeSticker#3a556302 alt:string stickerset:InputStickerSet = DocumentAttribute;
-documentAttributeAudio#ded218e0 duration:int title:string performer:string = DocumentAttribute;
-messageEntityUnknown#bb92ba95 offset:int length:int = MessageEntity;
-messageEntityMention#fa04579d offset:int length:int = MessageEntity;
-messageEntityHashtag#6f635b0d offset:int length:int = MessageEntity;
-messageEntityBotCommand#6cef8ac7 offset:int length:int = MessageEntity;
-messageEntityUrl#6ed02538 offset:int length:int = MessageEntity;
-messageEntityEmail#64e475c2 offset:int length:int = MessageEntity;
-messageEntityBold#bd610bc9 offset:int length:int = MessageEntity;
-messageEntityItalic#826f8b60 offset:int length:int = MessageEntity;
-messageEntityCode#28a20571 offset:int length:int = MessageEntity;
-messageEntityPre#73924be0 offset:int length:int language:string = MessageEntity;
-messageEntityTextUrl#76a6d327 offset:int length:int url:string = MessageEntity;
-inputStickerSetShortName#861cc8a0 short_name:string = InputStickerSet;
-inputStickerSetEmpty#ffb62b95 = InputStickerSet;
-decryptedMessageMediaVenue#8a0df56f lat:double long:double title:string address:string provider:string venue_id:string = DecryptedMessageMedia;
-decryptedMessageMediaWebPage#e50511d8 url:string = DecryptedMessageMedia;
-
-===46===
-documentAttributeAudio#9852f9c6 flags:# voice:flags.10?true duration:int title:flags.0?string performer:flags.1?string waveform:flags.2?bytes = DocumentAttribute;
-
-===66===
-documentAttributeVideo#ef02ce6 flags:# round_message:flags.0?true duration:int w:int h:int = DocumentAttribute;
-sendMessageRecordRoundAction#88f27fbc = SendMessageAction;
-sendMessageUploadRoundAction#bb718624 = SendMessageAction;
-
-===73===
-decryptedMessage#91cc4674 flags:# no_webpage:flags.1?true silent:flags.5?true random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long grouped_id:flags.17?long = DecryptedMessage;
-
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/schema/json.html b/data/core.telegram.org/schema/json.html deleted file mode 100644 index a6e0156ccf..0000000000 --- a/data/core.telegram.org/schema/json.html +++ /dev/null @@ -1 +0,0 @@ -{"constructors":[{"id":"-1132882121","predicate":"boolFalse","params":[],"type":"Bool"},{"id":"-1720552011","predicate":"boolTrue","params":[],"type":"Bool"},{"id":"1072550713","predicate":"true","params":[],"type":"True"},{"id":"481674261","predicate":"vector","params":[],"type":"Vector t"},{"id":"-994444869","predicate":"error","params":[{"name":"code","type":"int"},{"name":"text","type":"string"}],"type":"Error"},{"id":"1450380236","predicate":"null","params":[],"type":"Null"},{"id":"2134579434","predicate":"inputPeerEmpty","params":[],"type":"InputPeer"},{"id":"2107670217","predicate":"inputPeerSelf","params":[],"type":"InputPeer"},{"id":"900291769","predicate":"inputPeerChat","params":[{"name":"chat_id","type":"long"}],"type":"InputPeer"},{"id":"-1182234929","predicate":"inputUserEmpty","params":[],"type":"InputUser"},{"id":"-138301121","predicate":"inputUserSelf","params":[],"type":"InputUser"},{"id":"-208488460","predicate":"inputPhoneContact","params":[{"name":"client_id","type":"long"},{"name":"phone","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"}],"type":"InputContact"},{"id":"-181407105","predicate":"inputFile","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"name","type":"string"},{"name":"md5_checksum","type":"string"}],"type":"InputFile"},{"id":"-1771768449","predicate":"inputMediaEmpty","params":[],"type":"InputMedia"},{"id":"505969924","predicate":"inputMediaUploadedPhoto","params":[{"name":"flags","type":"#"},{"name":"file","type":"InputFile"},{"name":"stickers","type":"flags.0?Vector"},{"name":"ttl_seconds","type":"flags.1?int"}],"type":"InputMedia"},{"id":"-1279654347","predicate":"inputMediaPhoto","params":[{"name":"flags","type":"#"},{"name":"id","type":"InputPhoto"},{"name":"ttl_seconds","type":"flags.0?int"}],"type":"InputMedia"},{"id":"-104578748","predicate":"inputMediaGeoPoint","params":[{"name":"geo_point","type":"InputGeoPoint"}],"type":"InputMedia"},{"id":"-122978821","predicate":"inputMediaContact","params":[{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"vcard","type":"string"}],"type":"InputMedia"},{"id":"480546647","predicate":"inputChatPhotoEmpty","params":[],"type":"InputChatPhoto"},{"id":"-968723890","predicate":"inputChatUploadedPhoto","params":[{"name":"flags","type":"#"},{"name":"file","type":"flags.0?InputFile"},{"name":"video","type":"flags.1?InputFile"},{"name":"video_start_ts","type":"flags.2?double"}],"type":"InputChatPhoto"},{"id":"-1991004873","predicate":"inputChatPhoto","params":[{"name":"id","type":"InputPhoto"}],"type":"InputChatPhoto"},{"id":"-457104426","predicate":"inputGeoPointEmpty","params":[],"type":"InputGeoPoint"},{"id":"1210199983","predicate":"inputGeoPoint","params":[{"name":"flags","type":"#"},{"name":"lat","type":"double"},{"name":"long","type":"double"},{"name":"accuracy_radius","type":"flags.0?int"}],"type":"InputGeoPoint"},{"id":"483901197","predicate":"inputPhotoEmpty","params":[],"type":"InputPhoto"},{"id":"1001634122","predicate":"inputPhoto","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"}],"type":"InputPhoto"},{"id":"-539317279","predicate":"inputFileLocation","params":[{"name":"volume_id","type":"long"},{"name":"local_id","type":"int"},{"name":"secret","type":"long"},{"name":"file_reference","type":"bytes"}],"type":"InputFileLocation"},{"id":"1498486562","predicate":"peerUser","params":[{"name":"user_id","type":"long"}],"type":"Peer"},{"id":"918946202","predicate":"peerChat","params":[{"name":"chat_id","type":"long"}],"type":"Peer"},{"id":"-1432995067","predicate":"storage.fileUnknown","params":[],"type":"storage.FileType"},{"id":"1086091090","predicate":"storage.filePartial","params":[],"type":"storage.FileType"},{"id":"8322574","predicate":"storage.fileJpeg","params":[],"type":"storage.FileType"},{"id":"-891180321","predicate":"storage.fileGif","params":[],"type":"storage.FileType"},{"id":"172975040","predicate":"storage.filePng","params":[],"type":"storage.FileType"},{"id":"-1373745011","predicate":"storage.filePdf","params":[],"type":"storage.FileType"},{"id":"1384777335","predicate":"storage.fileMp3","params":[],"type":"storage.FileType"},{"id":"1258941372","predicate":"storage.fileMov","params":[],"type":"storage.FileType"},{"id":"-1278304028","predicate":"storage.fileMp4","params":[],"type":"storage.FileType"},{"id":"276907596","predicate":"storage.fileWebp","params":[],"type":"storage.FileType"},{"id":"-742634630","predicate":"userEmpty","params":[{"name":"id","type":"long"}],"type":"User"},{"id":"1326562017","predicate":"userProfilePhotoEmpty","params":[],"type":"UserProfilePhoto"},{"id":"-2100168954","predicate":"userProfilePhoto","params":[{"name":"flags","type":"#"},{"name":"has_video","type":"flags.0?true"},{"name":"photo_id","type":"long"},{"name":"stripped_thumb","type":"flags.1?bytes"},{"name":"dc_id","type":"int"}],"type":"UserProfilePhoto"},{"id":"164646985","predicate":"userStatusEmpty","params":[],"type":"UserStatus"},{"id":"-306628279","predicate":"userStatusOnline","params":[{"name":"expires","type":"int"}],"type":"UserStatus"},{"id":"9203775","predicate":"userStatusOffline","params":[{"name":"was_online","type":"int"}],"type":"UserStatus"},{"id":"693512293","predicate":"chatEmpty","params":[{"name":"id","type":"long"}],"type":"Chat"},{"id":"1103884886","predicate":"chat","params":[{"name":"flags","type":"#"},{"name":"creator","type":"flags.0?true"},{"name":"kicked","type":"flags.1?true"},{"name":"left","type":"flags.2?true"},{"name":"deactivated","type":"flags.5?true"},{"name":"call_active","type":"flags.23?true"},{"name":"call_not_empty","type":"flags.24?true"},{"name":"noforwards","type":"flags.25?true"},{"name":"id","type":"long"},{"name":"title","type":"string"},{"name":"photo","type":"ChatPhoto"},{"name":"participants_count","type":"int"},{"name":"date","type":"int"},{"name":"version","type":"int"},{"name":"migrated_to","type":"flags.6?InputChannel"},{"name":"admin_rights","type":"flags.14?ChatAdminRights"},{"name":"default_banned_rights","type":"flags.18?ChatBannedRights"}],"type":"Chat"},{"id":"1704108455","predicate":"chatForbidden","params":[{"name":"id","type":"long"},{"name":"title","type":"string"}],"type":"Chat"},{"id":"1304281241","predicate":"chatFull","params":[{"name":"flags","type":"#"},{"name":"can_set_username","type":"flags.7?true"},{"name":"has_scheduled","type":"flags.8?true"},{"name":"id","type":"long"},{"name":"about","type":"string"},{"name":"participants","type":"ChatParticipants"},{"name":"chat_photo","type":"flags.2?Photo"},{"name":"notify_settings","type":"PeerNotifySettings"},{"name":"exported_invite","type":"flags.13?ExportedChatInvite"},{"name":"bot_info","type":"flags.3?Vector"},{"name":"pinned_msg_id","type":"flags.6?int"},{"name":"folder_id","type":"flags.11?int"},{"name":"call","type":"flags.12?InputGroupCall"},{"name":"ttl_period","type":"flags.14?int"},{"name":"groupcall_default_join_as","type":"flags.15?Peer"},{"name":"theme_emoticon","type":"flags.16?string"}],"type":"ChatFull"},{"id":"-1070776313","predicate":"chatParticipant","params":[{"name":"user_id","type":"long"},{"name":"inviter_id","type":"long"},{"name":"date","type":"int"}],"type":"ChatParticipant"},{"id":"-2023500831","predicate":"chatParticipantsForbidden","params":[{"name":"flags","type":"#"},{"name":"chat_id","type":"long"},{"name":"self_participant","type":"flags.0?ChatParticipant"}],"type":"ChatParticipants"},{"id":"1018991608","predicate":"chatParticipants","params":[{"name":"chat_id","type":"long"},{"name":"participants","type":"Vector"},{"name":"version","type":"int"}],"type":"ChatParticipants"},{"id":"935395612","predicate":"chatPhotoEmpty","params":[],"type":"ChatPhoto"},{"id":"476978193","predicate":"chatPhoto","params":[{"name":"flags","type":"#"},{"name":"has_video","type":"flags.0?true"},{"name":"photo_id","type":"long"},{"name":"stripped_thumb","type":"flags.1?bytes"},{"name":"dc_id","type":"int"}],"type":"ChatPhoto"},{"id":"-1868117372","predicate":"messageEmpty","params":[{"name":"flags","type":"#"},{"name":"id","type":"int"},{"name":"peer_id","type":"flags.0?Peer"}],"type":"Message"},{"id":"-2049520670","predicate":"message","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"mentioned","type":"flags.4?true"},{"name":"media_unread","type":"flags.5?true"},{"name":"silent","type":"flags.13?true"},{"name":"post","type":"flags.14?true"},{"name":"from_scheduled","type":"flags.18?true"},{"name":"legacy","type":"flags.19?true"},{"name":"edit_hide","type":"flags.21?true"},{"name":"pinned","type":"flags.24?true"},{"name":"noforwards","type":"flags.26?true"},{"name":"id","type":"int"},{"name":"from_id","type":"flags.8?Peer"},{"name":"peer_id","type":"Peer"},{"name":"fwd_from","type":"flags.2?MessageFwdHeader"},{"name":"via_bot_id","type":"flags.11?long"},{"name":"reply_to","type":"flags.3?MessageReplyHeader"},{"name":"date","type":"int"},{"name":"message","type":"string"},{"name":"media","type":"flags.9?MessageMedia"},{"name":"reply_markup","type":"flags.6?ReplyMarkup"},{"name":"entities","type":"flags.7?Vector"},{"name":"views","type":"flags.10?int"},{"name":"forwards","type":"flags.10?int"},{"name":"replies","type":"flags.23?MessageReplies"},{"name":"edit_date","type":"flags.15?int"},{"name":"post_author","type":"flags.16?string"},{"name":"grouped_id","type":"flags.17?long"},{"name":"restriction_reason","type":"flags.22?Vector"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Message"},{"id":"721967202","predicate":"messageService","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"mentioned","type":"flags.4?true"},{"name":"media_unread","type":"flags.5?true"},{"name":"silent","type":"flags.13?true"},{"name":"post","type":"flags.14?true"},{"name":"legacy","type":"flags.19?true"},{"name":"id","type":"int"},{"name":"from_id","type":"flags.8?Peer"},{"name":"peer_id","type":"Peer"},{"name":"reply_to","type":"flags.3?MessageReplyHeader"},{"name":"date","type":"int"},{"name":"action","type":"MessageAction"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Message"},{"id":"1038967584","predicate":"messageMediaEmpty","params":[],"type":"MessageMedia"},{"id":"1766936791","predicate":"messageMediaPhoto","params":[{"name":"flags","type":"#"},{"name":"photo","type":"flags.0?Photo"},{"name":"ttl_seconds","type":"flags.2?int"}],"type":"MessageMedia"},{"id":"1457575028","predicate":"messageMediaGeo","params":[{"name":"geo","type":"GeoPoint"}],"type":"MessageMedia"},{"id":"1882335561","predicate":"messageMediaContact","params":[{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"vcard","type":"string"},{"name":"user_id","type":"long"}],"type":"MessageMedia"},{"id":"-1618676578","predicate":"messageMediaUnsupported","params":[],"type":"MessageMedia"},{"id":"-1230047312","predicate":"messageActionEmpty","params":[],"type":"MessageAction"},{"id":"-1119368275","predicate":"messageActionChatCreate","params":[{"name":"title","type":"string"},{"name":"users","type":"Vector"}],"type":"MessageAction"},{"id":"-1247687078","predicate":"messageActionChatEditTitle","params":[{"name":"title","type":"string"}],"type":"MessageAction"},{"id":"2144015272","predicate":"messageActionChatEditPhoto","params":[{"name":"photo","type":"Photo"}],"type":"MessageAction"},{"id":"-1780220945","predicate":"messageActionChatDeletePhoto","params":[],"type":"MessageAction"},{"id":"365886720","predicate":"messageActionChatAddUser","params":[{"name":"users","type":"Vector"}],"type":"MessageAction"},{"id":"-1539362612","predicate":"messageActionChatDeleteUser","params":[{"name":"user_id","type":"long"}],"type":"MessageAction"},{"id":"739712882","predicate":"dialog","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.2?true"},{"name":"unread_mark","type":"flags.3?true"},{"name":"peer","type":"Peer"},{"name":"top_message","type":"int"},{"name":"read_inbox_max_id","type":"int"},{"name":"read_outbox_max_id","type":"int"},{"name":"unread_count","type":"int"},{"name":"unread_mentions_count","type":"int"},{"name":"notify_settings","type":"PeerNotifySettings"},{"name":"pts","type":"flags.0?int"},{"name":"draft","type":"flags.1?DraftMessage"},{"name":"folder_id","type":"flags.4?int"}],"type":"Dialog"},{"id":"590459437","predicate":"photoEmpty","params":[{"name":"id","type":"long"}],"type":"Photo"},{"id":"-82216347","predicate":"photo","params":[{"name":"flags","type":"#"},{"name":"has_stickers","type":"flags.0?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"date","type":"int"},{"name":"sizes","type":"Vector"},{"name":"video_sizes","type":"flags.1?Vector"},{"name":"dc_id","type":"int"}],"type":"Photo"},{"id":"236446268","predicate":"photoSizeEmpty","params":[{"name":"type","type":"string"}],"type":"PhotoSize"},{"id":"1976012384","predicate":"photoSize","params":[{"name":"type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"}],"type":"PhotoSize"},{"id":"35527382","predicate":"photoCachedSize","params":[{"name":"type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"bytes","type":"bytes"}],"type":"PhotoSize"},{"id":"286776671","predicate":"geoPointEmpty","params":[],"type":"GeoPoint"},{"id":"-1297942941","predicate":"geoPoint","params":[{"name":"flags","type":"#"},{"name":"long","type":"double"},{"name":"lat","type":"double"},{"name":"access_hash","type":"long"},{"name":"accuracy_radius","type":"flags.0?int"}],"type":"GeoPoint"},{"id":"1577067778","predicate":"auth.sentCode","params":[{"name":"flags","type":"#"},{"name":"type","type":"auth.SentCodeType"},{"name":"phone_code_hash","type":"string"},{"name":"next_type","type":"flags.1?auth.CodeType"},{"name":"timeout","type":"flags.2?int"}],"type":"auth.SentCode"},{"id":"-855308010","predicate":"auth.authorization","params":[{"name":"flags","type":"#"},{"name":"tmp_sessions","type":"flags.0?int"},{"name":"user","type":"User"}],"type":"auth.Authorization"},{"id":"-1271602504","predicate":"auth.exportedAuthorization","params":[{"name":"id","type":"long"},{"name":"bytes","type":"bytes"}],"type":"auth.ExportedAuthorization"},{"id":"-1195615476","predicate":"inputNotifyPeer","params":[{"name":"peer","type":"InputPeer"}],"type":"InputNotifyPeer"},{"id":"423314455","predicate":"inputNotifyUsers","params":[],"type":"InputNotifyPeer"},{"id":"1251338318","predicate":"inputNotifyChats","params":[],"type":"InputNotifyPeer"},{"id":"-1673717362","predicate":"inputPeerNotifySettings","params":[{"name":"flags","type":"#"},{"name":"show_previews","type":"flags.0?Bool"},{"name":"silent","type":"flags.1?Bool"},{"name":"mute_until","type":"flags.2?int"},{"name":"sound","type":"flags.3?string"}],"type":"InputPeerNotifySettings"},{"id":"-1353671392","predicate":"peerNotifySettings","params":[{"name":"flags","type":"#"},{"name":"show_previews","type":"flags.0?Bool"},{"name":"silent","type":"flags.1?Bool"},{"name":"mute_until","type":"flags.2?int"},{"name":"sound","type":"flags.3?string"}],"type":"PeerNotifySettings"},{"id":"1933519201","predicate":"peerSettings","params":[{"name":"flags","type":"#"},{"name":"report_spam","type":"flags.0?true"},{"name":"add_contact","type":"flags.1?true"},{"name":"block_contact","type":"flags.2?true"},{"name":"share_contact","type":"flags.3?true"},{"name":"need_contacts_exception","type":"flags.4?true"},{"name":"report_geo","type":"flags.5?true"},{"name":"autoarchived","type":"flags.7?true"},{"name":"invite_members","type":"flags.8?true"},{"name":"geo_distance","type":"flags.6?int"}],"type":"PeerSettings"},{"id":"-1539849235","predicate":"wallPaper","params":[{"name":"id","type":"long"},{"name":"flags","type":"#"},{"name":"creator","type":"flags.0?true"},{"name":"default","type":"flags.1?true"},{"name":"pattern","type":"flags.3?true"},{"name":"dark","type":"flags.4?true"},{"name":"access_hash","type":"long"},{"name":"slug","type":"string"},{"name":"document","type":"Document"},{"name":"settings","type":"flags.2?WallPaperSettings"}],"type":"WallPaper"},{"id":"1490799288","predicate":"inputReportReasonSpam","params":[],"type":"ReportReason"},{"id":"505595789","predicate":"inputReportReasonViolence","params":[],"type":"ReportReason"},{"id":"777640226","predicate":"inputReportReasonPornography","params":[],"type":"ReportReason"},{"id":"-1376497949","predicate":"inputReportReasonChildAbuse","params":[],"type":"ReportReason"},{"id":"-1041980751","predicate":"inputReportReasonOther","params":[],"type":"ReportReason"},{"id":"-694681851","predicate":"userFull","params":[{"name":"flags","type":"#"},{"name":"blocked","type":"flags.0?true"},{"name":"phone_calls_available","type":"flags.4?true"},{"name":"phone_calls_private","type":"flags.5?true"},{"name":"can_pin_message","type":"flags.7?true"},{"name":"has_scheduled","type":"flags.12?true"},{"name":"video_calls_available","type":"flags.13?true"},{"name":"user","type":"User"},{"name":"about","type":"flags.1?string"},{"name":"settings","type":"PeerSettings"},{"name":"profile_photo","type":"flags.2?Photo"},{"name":"notify_settings","type":"PeerNotifySettings"},{"name":"bot_info","type":"flags.3?BotInfo"},{"name":"pinned_msg_id","type":"flags.6?int"},{"name":"common_chats_count","type":"int"},{"name":"folder_id","type":"flags.11?int"},{"name":"ttl_period","type":"flags.14?int"},{"name":"theme_emoticon","type":"flags.15?string"}],"type":"UserFull"},{"id":"341499403","predicate":"contact","params":[{"name":"user_id","type":"long"},{"name":"mutual","type":"Bool"}],"type":"Contact"},{"id":"-1052885936","predicate":"importedContact","params":[{"name":"user_id","type":"long"},{"name":"client_id","type":"long"}],"type":"ImportedContact"},{"id":"383348795","predicate":"contactStatus","params":[{"name":"user_id","type":"long"},{"name":"status","type":"UserStatus"}],"type":"ContactStatus"},{"id":"-1219778094","predicate":"contacts.contactsNotModified","params":[],"type":"contacts.Contacts"},{"id":"-353862078","predicate":"contacts.contacts","params":[{"name":"contacts","type":"Vector"},{"name":"saved_count","type":"int"},{"name":"users","type":"Vector"}],"type":"contacts.Contacts"},{"id":"2010127419","predicate":"contacts.importedContacts","params":[{"name":"imported","type":"Vector"},{"name":"popular_invites","type":"Vector"},{"name":"retry_contacts","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.ImportedContacts"},{"id":"182326673","predicate":"contacts.blocked","params":[{"name":"blocked","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.Blocked"},{"id":"-513392236","predicate":"contacts.blockedSlice","params":[{"name":"count","type":"int"},{"name":"blocked","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.Blocked"},{"id":"364538944","predicate":"messages.dialogs","params":[{"name":"dialogs","type":"Vector"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Dialogs"},{"id":"1910543603","predicate":"messages.dialogsSlice","params":[{"name":"count","type":"int"},{"name":"dialogs","type":"Vector"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Dialogs"},{"id":"-1938715001","predicate":"messages.messages","params":[{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Messages"},{"id":"978610270","predicate":"messages.messagesSlice","params":[{"name":"flags","type":"#"},{"name":"inexact","type":"flags.1?true"},{"name":"count","type":"int"},{"name":"next_rate","type":"flags.0?int"},{"name":"offset_id_offset","type":"flags.2?int"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Messages"},{"id":"1694474197","predicate":"messages.chats","params":[{"name":"chats","type":"Vector"}],"type":"messages.Chats"},{"id":"-438840932","predicate":"messages.chatFull","params":[{"name":"full_chat","type":"ChatFull"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.ChatFull"},{"id":"-1269012015","predicate":"messages.affectedHistory","params":[{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"offset","type":"int"}],"type":"messages.AffectedHistory"},{"id":"1474492012","predicate":"inputMessagesFilterEmpty","params":[],"type":"MessagesFilter"},{"id":"-1777752804","predicate":"inputMessagesFilterPhotos","params":[],"type":"MessagesFilter"},{"id":"-1614803355","predicate":"inputMessagesFilterVideo","params":[],"type":"MessagesFilter"},{"id":"1458172132","predicate":"inputMessagesFilterPhotoVideo","params":[],"type":"MessagesFilter"},{"id":"-1629621880","predicate":"inputMessagesFilterDocument","params":[],"type":"MessagesFilter"},{"id":"2129714567","predicate":"inputMessagesFilterUrl","params":[],"type":"MessagesFilter"},{"id":"-3644025","predicate":"inputMessagesFilterGif","params":[],"type":"MessagesFilter"},{"id":"522914557","predicate":"updateNewMessage","params":[{"name":"message","type":"Message"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"1318109142","predicate":"updateMessageID","params":[{"name":"id","type":"int"},{"name":"random_id","type":"long"}],"type":"Update"},{"id":"-1576161051","predicate":"updateDeleteMessages","params":[{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1071741569","predicate":"updateUserTyping","params":[{"name":"user_id","type":"long"},{"name":"action","type":"SendMessageAction"}],"type":"Update"},{"id":"-2092401936","predicate":"updateChatUserTyping","params":[{"name":"chat_id","type":"long"},{"name":"from_id","type":"Peer"},{"name":"action","type":"SendMessageAction"}],"type":"Update"},{"id":"125178264","predicate":"updateChatParticipants","params":[{"name":"participants","type":"ChatParticipants"}],"type":"Update"},{"id":"-440534818","predicate":"updateUserStatus","params":[{"name":"user_id","type":"long"},{"name":"status","type":"UserStatus"}],"type":"Update"},{"id":"-1007549728","predicate":"updateUserName","params":[{"name":"user_id","type":"long"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"username","type":"string"}],"type":"Update"},{"id":"-232290676","predicate":"updateUserPhoto","params":[{"name":"user_id","type":"long"},{"name":"date","type":"int"},{"name":"photo","type":"UserProfilePhoto"},{"name":"previous","type":"Bool"}],"type":"Update"},{"id":"-1519637954","predicate":"updates.state","params":[{"name":"pts","type":"int"},{"name":"qts","type":"int"},{"name":"date","type":"int"},{"name":"seq","type":"int"},{"name":"unread_count","type":"int"}],"type":"updates.State"},{"id":"1567990072","predicate":"updates.differenceEmpty","params":[{"name":"date","type":"int"},{"name":"seq","type":"int"}],"type":"updates.Difference"},{"id":"16030880","predicate":"updates.difference","params":[{"name":"new_messages","type":"Vector"},{"name":"new_encrypted_messages","type":"Vector"},{"name":"other_updates","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"state","type":"updates.State"}],"type":"updates.Difference"},{"id":"-1459938943","predicate":"updates.differenceSlice","params":[{"name":"new_messages","type":"Vector"},{"name":"new_encrypted_messages","type":"Vector"},{"name":"other_updates","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"intermediate_state","type":"updates.State"}],"type":"updates.Difference"},{"id":"-484987010","predicate":"updatesTooLong","params":[],"type":"Updates"},{"id":"826001400","predicate":"updateShortMessage","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"mentioned","type":"flags.4?true"},{"name":"media_unread","type":"flags.5?true"},{"name":"silent","type":"flags.13?true"},{"name":"id","type":"int"},{"name":"user_id","type":"long"},{"name":"message","type":"string"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"date","type":"int"},{"name":"fwd_from","type":"flags.2?MessageFwdHeader"},{"name":"via_bot_id","type":"flags.11?long"},{"name":"reply_to","type":"flags.3?MessageReplyHeader"},{"name":"entities","type":"flags.7?Vector"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Updates"},{"id":"1299050149","predicate":"updateShortChatMessage","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"mentioned","type":"flags.4?true"},{"name":"media_unread","type":"flags.5?true"},{"name":"silent","type":"flags.13?true"},{"name":"id","type":"int"},{"name":"from_id","type":"long"},{"name":"chat_id","type":"long"},{"name":"message","type":"string"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"date","type":"int"},{"name":"fwd_from","type":"flags.2?MessageFwdHeader"},{"name":"via_bot_id","type":"flags.11?long"},{"name":"reply_to","type":"flags.3?MessageReplyHeader"},{"name":"entities","type":"flags.7?Vector"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Updates"},{"id":"2027216577","predicate":"updateShort","params":[{"name":"update","type":"Update"},{"name":"date","type":"int"}],"type":"Updates"},{"id":"1918567619","predicate":"updatesCombined","params":[{"name":"updates","type":"Vector"},{"name":"users","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"date","type":"int"},{"name":"seq_start","type":"int"},{"name":"seq","type":"int"}],"type":"Updates"},{"id":"1957577280","predicate":"updates","params":[{"name":"updates","type":"Vector"},{"name":"users","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"date","type":"int"},{"name":"seq","type":"int"}],"type":"Updates"},{"id":"-1916114267","predicate":"photos.photos","params":[{"name":"photos","type":"Vector"},{"name":"users","type":"Vector"}],"type":"photos.Photos"},{"id":"352657236","predicate":"photos.photosSlice","params":[{"name":"count","type":"int"},{"name":"photos","type":"Vector"},{"name":"users","type":"Vector"}],"type":"photos.Photos"},{"id":"539045032","predicate":"photos.photo","params":[{"name":"photo","type":"Photo"},{"name":"users","type":"Vector"}],"type":"photos.Photo"},{"id":"157948117","predicate":"upload.file","params":[{"name":"type","type":"storage.FileType"},{"name":"mtime","type":"int"},{"name":"bytes","type":"bytes"}],"type":"upload.File"},{"id":"414687501","predicate":"dcOption","params":[{"name":"flags","type":"#"},{"name":"ipv6","type":"flags.0?true"},{"name":"media_only","type":"flags.1?true"},{"name":"tcpo_only","type":"flags.2?true"},{"name":"cdn","type":"flags.3?true"},{"name":"static","type":"flags.4?true"},{"name":"id","type":"int"},{"name":"ip_address","type":"string"},{"name":"port","type":"int"},{"name":"secret","type":"flags.10?bytes"}],"type":"DcOption"},{"id":"856375399","predicate":"config","params":[{"name":"flags","type":"#"},{"name":"phonecalls_enabled","type":"flags.1?true"},{"name":"default_p2p_contacts","type":"flags.3?true"},{"name":"preload_featured_stickers","type":"flags.4?true"},{"name":"ignore_phone_entities","type":"flags.5?true"},{"name":"revoke_pm_inbox","type":"flags.6?true"},{"name":"blocked_mode","type":"flags.8?true"},{"name":"pfs_enabled","type":"flags.13?true"},{"name":"date","type":"int"},{"name":"expires","type":"int"},{"name":"test_mode","type":"Bool"},{"name":"this_dc","type":"int"},{"name":"dc_options","type":"Vector"},{"name":"dc_txt_domain_name","type":"string"},{"name":"chat_size_max","type":"int"},{"name":"megagroup_size_max","type":"int"},{"name":"forwarded_count_max","type":"int"},{"name":"online_update_period_ms","type":"int"},{"name":"offline_blur_timeout_ms","type":"int"},{"name":"offline_idle_timeout_ms","type":"int"},{"name":"online_cloud_timeout_ms","type":"int"},{"name":"notify_cloud_delay_ms","type":"int"},{"name":"notify_default_delay_ms","type":"int"},{"name":"push_chat_period_ms","type":"int"},{"name":"push_chat_limit","type":"int"},{"name":"saved_gifs_limit","type":"int"},{"name":"edit_time_limit","type":"int"},{"name":"revoke_time_limit","type":"int"},{"name":"revoke_pm_time_limit","type":"int"},{"name":"rating_e_decay","type":"int"},{"name":"stickers_recent_limit","type":"int"},{"name":"stickers_faved_limit","type":"int"},{"name":"channels_read_media_period","type":"int"},{"name":"tmp_sessions","type":"flags.0?int"},{"name":"pinned_dialogs_count_max","type":"int"},{"name":"pinned_infolder_count_max","type":"int"},{"name":"call_receive_timeout_ms","type":"int"},{"name":"call_ring_timeout_ms","type":"int"},{"name":"call_connect_timeout_ms","type":"int"},{"name":"call_packet_timeout_ms","type":"int"},{"name":"me_url_prefix","type":"string"},{"name":"autoupdate_url_prefix","type":"flags.7?string"},{"name":"gif_search_username","type":"flags.9?string"},{"name":"venue_search_username","type":"flags.10?string"},{"name":"img_search_username","type":"flags.11?string"},{"name":"static_maps_provider","type":"flags.12?string"},{"name":"caption_length_max","type":"int"},{"name":"message_length_max","type":"int"},{"name":"webfile_dc_id","type":"int"},{"name":"suggested_lang_code","type":"flags.2?string"},{"name":"lang_pack_version","type":"flags.2?int"},{"name":"base_lang_pack_version","type":"flags.2?int"}],"type":"Config"},{"id":"-1910892683","predicate":"nearestDc","params":[{"name":"country","type":"string"},{"name":"this_dc","type":"int"},{"name":"nearest_dc","type":"int"}],"type":"NearestDc"},{"id":"-860107216","predicate":"help.appUpdate","params":[{"name":"flags","type":"#"},{"name":"can_not_skip","type":"flags.0?true"},{"name":"id","type":"int"},{"name":"version","type":"string"},{"name":"text","type":"string"},{"name":"entities","type":"Vector"},{"name":"document","type":"flags.1?Document"},{"name":"url","type":"flags.2?string"},{"name":"sticker","type":"flags.3?Document"}],"type":"help.AppUpdate"},{"id":"-1000708810","predicate":"help.noAppUpdate","params":[],"type":"help.AppUpdate"},{"id":"415997816","predicate":"help.inviteText","params":[{"name":"message","type":"string"}],"type":"help.InviteText"},{"id":"314359194","predicate":"updateNewEncryptedMessage","params":[{"name":"message","type":"EncryptedMessage"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"386986326","predicate":"updateEncryptedChatTyping","params":[{"name":"chat_id","type":"int"}],"type":"Update"},{"id":"-1264392051","predicate":"updateEncryption","params":[{"name":"chat","type":"EncryptedChat"},{"name":"date","type":"int"}],"type":"Update"},{"id":"956179895","predicate":"updateEncryptedMessagesRead","params":[{"name":"chat_id","type":"int"},{"name":"max_date","type":"int"},{"name":"date","type":"int"}],"type":"Update"},{"id":"-1417756512","predicate":"encryptedChatEmpty","params":[{"name":"id","type":"int"}],"type":"EncryptedChat"},{"id":"1722964307","predicate":"encryptedChatWaiting","params":[{"name":"id","type":"int"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"}],"type":"EncryptedChat"},{"id":"1223809356","predicate":"encryptedChatRequested","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.0?int"},{"name":"id","type":"int"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_a","type":"bytes"}],"type":"EncryptedChat"},{"id":"1643173063","predicate":"encryptedChat","params":[{"name":"id","type":"int"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_a_or_b","type":"bytes"},{"name":"key_fingerprint","type":"long"}],"type":"EncryptedChat"},{"id":"505183301","predicate":"encryptedChatDiscarded","params":[{"name":"flags","type":"#"},{"name":"history_deleted","type":"flags.0?true"},{"name":"id","type":"int"}],"type":"EncryptedChat"},{"id":"-247351839","predicate":"inputEncryptedChat","params":[{"name":"chat_id","type":"int"},{"name":"access_hash","type":"long"}],"type":"InputEncryptedChat"},{"id":"-1038136962","predicate":"encryptedFileEmpty","params":[],"type":"EncryptedFile"},{"id":"1248893260","predicate":"encryptedFile","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"size","type":"int"},{"name":"dc_id","type":"int"},{"name":"key_fingerprint","type":"int"}],"type":"EncryptedFile"},{"id":"406307684","predicate":"inputEncryptedFileEmpty","params":[],"type":"InputEncryptedFile"},{"id":"1690108678","predicate":"inputEncryptedFileUploaded","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"md5_checksum","type":"string"},{"name":"key_fingerprint","type":"int"}],"type":"InputEncryptedFile"},{"id":"1511503333","predicate":"inputEncryptedFile","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputEncryptedFile"},{"id":"-182231723","predicate":"inputEncryptedFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputFileLocation"},{"id":"-317144808","predicate":"encryptedMessage","params":[{"name":"random_id","type":"long"},{"name":"chat_id","type":"int"},{"name":"date","type":"int"},{"name":"bytes","type":"bytes"},{"name":"file","type":"EncryptedFile"}],"type":"EncryptedMessage"},{"id":"594758406","predicate":"encryptedMessageService","params":[{"name":"random_id","type":"long"},{"name":"chat_id","type":"int"},{"name":"date","type":"int"},{"name":"bytes","type":"bytes"}],"type":"EncryptedMessage"},{"id":"-1058912715","predicate":"messages.dhConfigNotModified","params":[{"name":"random","type":"bytes"}],"type":"messages.DhConfig"},{"id":"740433629","predicate":"messages.dhConfig","params":[{"name":"g","type":"int"},{"name":"p","type":"bytes"},{"name":"version","type":"int"},{"name":"random","type":"bytes"}],"type":"messages.DhConfig"},{"id":"1443858741","predicate":"messages.sentEncryptedMessage","params":[{"name":"date","type":"int"}],"type":"messages.SentEncryptedMessage"},{"id":"-1802240206","predicate":"messages.sentEncryptedFile","params":[{"name":"date","type":"int"},{"name":"file","type":"EncryptedFile"}],"type":"messages.SentEncryptedMessage"},{"id":"-95482955","predicate":"inputFileBig","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"name","type":"string"}],"type":"InputFile"},{"id":"767652808","predicate":"inputEncryptedFileBigUploaded","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"key_fingerprint","type":"int"}],"type":"InputEncryptedFile"},{"id":"1037718609","predicate":"updateChatParticipantAdd","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"long"},{"name":"inviter_id","type":"long"},{"name":"date","type":"int"},{"name":"version","type":"int"}],"type":"Update"},{"id":"-483443337","predicate":"updateChatParticipantDelete","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"long"},{"name":"version","type":"int"}],"type":"Update"},{"id":"-1906403213","predicate":"updateDcOptions","params":[{"name":"dc_options","type":"Vector"}],"type":"Update"},{"id":"1530447553","predicate":"inputMediaUploadedDocument","params":[{"name":"flags","type":"#"},{"name":"nosound_video","type":"flags.3?true"},{"name":"force_file","type":"flags.4?true"},{"name":"file","type":"InputFile"},{"name":"thumb","type":"flags.2?InputFile"},{"name":"mime_type","type":"string"},{"name":"attributes","type":"Vector"},{"name":"stickers","type":"flags.0?Vector"},{"name":"ttl_seconds","type":"flags.1?int"}],"type":"InputMedia"},{"id":"860303448","predicate":"inputMediaDocument","params":[{"name":"flags","type":"#"},{"name":"id","type":"InputDocument"},{"name":"ttl_seconds","type":"flags.0?int"},{"name":"query","type":"flags.1?string"}],"type":"InputMedia"},{"id":"-1666158377","predicate":"messageMediaDocument","params":[{"name":"flags","type":"#"},{"name":"document","type":"flags.0?Document"},{"name":"ttl_seconds","type":"flags.2?int"}],"type":"MessageMedia"},{"id":"1928391342","predicate":"inputDocumentEmpty","params":[],"type":"InputDocument"},{"id":"448771445","predicate":"inputDocument","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"}],"type":"InputDocument"},{"id":"-1160743548","predicate":"inputDocumentFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"thumb_size","type":"string"}],"type":"InputFileLocation"},{"id":"922273905","predicate":"documentEmpty","params":[{"name":"id","type":"long"}],"type":"Document"},{"id":"512177195","predicate":"document","params":[{"name":"flags","type":"#"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"date","type":"int"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"thumbs","type":"flags.0?Vector"},{"name":"video_thumbs","type":"flags.1?Vector"},{"name":"dc_id","type":"int"},{"name":"attributes","type":"Vector"}],"type":"Document"},{"id":"398898678","predicate":"help.support","params":[{"name":"phone_number","type":"string"},{"name":"user","type":"User"}],"type":"help.Support"},{"id":"-1613493288","predicate":"notifyPeer","params":[{"name":"peer","type":"Peer"}],"type":"NotifyPeer"},{"id":"-1261946036","predicate":"notifyUsers","params":[],"type":"NotifyPeer"},{"id":"-1073230141","predicate":"notifyChats","params":[],"type":"NotifyPeer"},{"id":"-1094555409","predicate":"updateNotifySettings","params":[{"name":"peer","type":"NotifyPeer"},{"name":"notify_settings","type":"PeerNotifySettings"}],"type":"Update"},{"id":"381645902","predicate":"sendMessageTypingAction","params":[],"type":"SendMessageAction"},{"id":"-44119819","predicate":"sendMessageCancelAction","params":[],"type":"SendMessageAction"},{"id":"-1584933265","predicate":"sendMessageRecordVideoAction","params":[],"type":"SendMessageAction"},{"id":"-378127636","predicate":"sendMessageUploadVideoAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"-718310409","predicate":"sendMessageRecordAudioAction","params":[],"type":"SendMessageAction"},{"id":"-212740181","predicate":"sendMessageUploadAudioAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"-774682074","predicate":"sendMessageUploadPhotoAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"-1441998364","predicate":"sendMessageUploadDocumentAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"393186209","predicate":"sendMessageGeoLocationAction","params":[],"type":"SendMessageAction"},{"id":"1653390447","predicate":"sendMessageChooseContactAction","params":[],"type":"SendMessageAction"},{"id":"-1290580579","predicate":"contacts.found","params":[{"name":"my_results","type":"Vector"},{"name":"results","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.Found"},{"id":"-337352679","predicate":"updateServiceNotification","params":[{"name":"flags","type":"#"},{"name":"popup","type":"flags.0?true"},{"name":"inbox_date","type":"flags.1?int"},{"name":"type","type":"string"},{"name":"message","type":"string"},{"name":"media","type":"MessageMedia"},{"name":"entities","type":"Vector"}],"type":"Update"},{"id":"-496024847","predicate":"userStatusRecently","params":[],"type":"UserStatus"},{"id":"129960444","predicate":"userStatusLastWeek","params":[],"type":"UserStatus"},{"id":"2011940674","predicate":"userStatusLastMonth","params":[],"type":"UserStatus"},{"id":"-298113238","predicate":"updatePrivacy","params":[{"name":"key","type":"PrivacyKey"},{"name":"rules","type":"Vector"}],"type":"Update"},{"id":"1335282456","predicate":"inputPrivacyKeyStatusTimestamp","params":[],"type":"InputPrivacyKey"},{"id":"-1137792208","predicate":"privacyKeyStatusTimestamp","params":[],"type":"PrivacyKey"},{"id":"218751099","predicate":"inputPrivacyValueAllowContacts","params":[],"type":"InputPrivacyRule"},{"id":"407582158","predicate":"inputPrivacyValueAllowAll","params":[],"type":"InputPrivacyRule"},{"id":"320652927","predicate":"inputPrivacyValueAllowUsers","params":[{"name":"users","type":"Vector"}],"type":"InputPrivacyRule"},{"id":"195371015","predicate":"inputPrivacyValueDisallowContacts","params":[],"type":"InputPrivacyRule"},{"id":"-697604407","predicate":"inputPrivacyValueDisallowAll","params":[],"type":"InputPrivacyRule"},{"id":"-1877932953","predicate":"inputPrivacyValueDisallowUsers","params":[{"name":"users","type":"Vector"}],"type":"InputPrivacyRule"},{"id":"-123988","predicate":"privacyValueAllowContacts","params":[],"type":"PrivacyRule"},{"id":"1698855810","predicate":"privacyValueAllowAll","params":[],"type":"PrivacyRule"},{"id":"-1198497870","predicate":"privacyValueAllowUsers","params":[{"name":"users","type":"Vector"}],"type":"PrivacyRule"},{"id":"-125240806","predicate":"privacyValueDisallowContacts","params":[],"type":"PrivacyRule"},{"id":"-1955338397","predicate":"privacyValueDisallowAll","params":[],"type":"PrivacyRule"},{"id":"-463335103","predicate":"privacyValueDisallowUsers","params":[{"name":"users","type":"Vector"}],"type":"PrivacyRule"},{"id":"1352683077","predicate":"account.privacyRules","params":[{"name":"rules","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"account.PrivacyRules"},{"id":"-1194283041","predicate":"accountDaysTTL","params":[{"name":"days","type":"int"}],"type":"AccountDaysTTL"},{"id":"88680979","predicate":"updateUserPhone","params":[{"name":"user_id","type":"long"},{"name":"phone","type":"string"}],"type":"Update"},{"id":"1815593308","predicate":"documentAttributeImageSize","params":[{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute"},{"id":"297109817","predicate":"documentAttributeAnimated","params":[],"type":"DocumentAttribute"},{"id":"1662637586","predicate":"documentAttributeSticker","params":[{"name":"flags","type":"#"},{"name":"mask","type":"flags.1?true"},{"name":"alt","type":"string"},{"name":"stickerset","type":"InputStickerSet"},{"name":"mask_coords","type":"flags.0?MaskCoords"}],"type":"DocumentAttribute"},{"id":"250621158","predicate":"documentAttributeVideo","params":[{"name":"flags","type":"#"},{"name":"round_message","type":"flags.0?true"},{"name":"supports_streaming","type":"flags.1?true"},{"name":"duration","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute"},{"id":"-1739392570","predicate":"documentAttributeAudio","params":[{"name":"flags","type":"#"},{"name":"voice","type":"flags.10?true"},{"name":"duration","type":"int"},{"name":"title","type":"flags.0?string"},{"name":"performer","type":"flags.1?string"},{"name":"waveform","type":"flags.2?bytes"}],"type":"DocumentAttribute"},{"id":"358154344","predicate":"documentAttributeFilename","params":[{"name":"file_name","type":"string"}],"type":"DocumentAttribute"},{"id":"-244016606","predicate":"messages.stickersNotModified","params":[],"type":"messages.Stickers"},{"id":"816245886","predicate":"messages.stickers","params":[{"name":"hash","type":"long"},{"name":"stickers","type":"Vector"}],"type":"messages.Stickers"},{"id":"313694676","predicate":"stickerPack","params":[{"name":"emoticon","type":"string"},{"name":"documents","type":"Vector"}],"type":"StickerPack"},{"id":"-395967805","predicate":"messages.allStickersNotModified","params":[],"type":"messages.AllStickers"},{"id":"-843329861","predicate":"messages.allStickers","params":[{"name":"hash","type":"long"},{"name":"sets","type":"Vector"}],"type":"messages.AllStickers"},{"id":"-1667805217","predicate":"updateReadHistoryInbox","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.0?int"},{"name":"peer","type":"Peer"},{"name":"max_id","type":"int"},{"name":"still_unread_count","type":"int"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"791617983","predicate":"updateReadHistoryOutbox","params":[{"name":"peer","type":"Peer"},{"name":"max_id","type":"int"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-2066640507","predicate":"messages.affectedMessages","params":[{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"messages.AffectedMessages"},{"id":"2139689491","predicate":"updateWebPage","params":[{"name":"webpage","type":"WebPage"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-350980120","predicate":"webPageEmpty","params":[{"name":"id","type":"long"}],"type":"WebPage"},{"id":"-981018084","predicate":"webPagePending","params":[{"name":"id","type":"long"},{"name":"date","type":"int"}],"type":"WebPage"},{"id":"-392411726","predicate":"webPage","params":[{"name":"flags","type":"#"},{"name":"id","type":"long"},{"name":"url","type":"string"},{"name":"display_url","type":"string"},{"name":"hash","type":"int"},{"name":"type","type":"flags.0?string"},{"name":"site_name","type":"flags.1?string"},{"name":"title","type":"flags.2?string"},{"name":"description","type":"flags.3?string"},{"name":"photo","type":"flags.4?Photo"},{"name":"embed_url","type":"flags.5?string"},{"name":"embed_type","type":"flags.5?string"},{"name":"embed_width","type":"flags.6?int"},{"name":"embed_height","type":"flags.6?int"},{"name":"duration","type":"flags.7?int"},{"name":"author","type":"flags.8?string"},{"name":"document","type":"flags.9?Document"},{"name":"cached_page","type":"flags.10?Page"},{"name":"attributes","type":"flags.12?Vector"}],"type":"WebPage"},{"id":"-1557277184","predicate":"messageMediaWebPage","params":[{"name":"webpage","type":"WebPage"}],"type":"MessageMedia"},{"id":"-1392388579","predicate":"authorization","params":[{"name":"flags","type":"#"},{"name":"current","type":"flags.0?true"},{"name":"official_app","type":"flags.1?true"},{"name":"password_pending","type":"flags.2?true"},{"name":"encrypted_requests_disabled","type":"flags.3?true"},{"name":"call_requests_disabled","type":"flags.4?true"},{"name":"hash","type":"long"},{"name":"device_model","type":"string"},{"name":"platform","type":"string"},{"name":"system_version","type":"string"},{"name":"api_id","type":"int"},{"name":"app_name","type":"string"},{"name":"app_version","type":"string"},{"name":"date_created","type":"int"},{"name":"date_active","type":"int"},{"name":"ip","type":"string"},{"name":"country","type":"string"},{"name":"region","type":"string"}],"type":"Authorization"},{"id":"307276766","predicate":"account.authorizations","params":[{"name":"authorizations","type":"Vector"}],"type":"account.Authorizations"},{"id":"408623183","predicate":"account.password","params":[{"name":"flags","type":"#"},{"name":"has_recovery","type":"flags.0?true"},{"name":"has_secure_values","type":"flags.1?true"},{"name":"has_password","type":"flags.2?true"},{"name":"current_algo","type":"flags.2?PasswordKdfAlgo"},{"name":"srp_B","type":"flags.2?bytes"},{"name":"srp_id","type":"flags.2?long"},{"name":"hint","type":"flags.3?string"},{"name":"email_unconfirmed_pattern","type":"flags.4?string"},{"name":"new_algo","type":"PasswordKdfAlgo"},{"name":"new_secure_algo","type":"SecurePasswordKdfAlgo"},{"name":"secure_random","type":"bytes"},{"name":"pending_reset_date","type":"flags.5?int"}],"type":"account.Password"},{"id":"-1705233435","predicate":"account.passwordSettings","params":[{"name":"flags","type":"#"},{"name":"email","type":"flags.0?string"},{"name":"secure_settings","type":"flags.1?SecureSecretSettings"}],"type":"account.PasswordSettings"},{"id":"-1036572727","predicate":"account.passwordInputSettings","params":[{"name":"flags","type":"#"},{"name":"new_algo","type":"flags.0?PasswordKdfAlgo"},{"name":"new_password_hash","type":"flags.0?bytes"},{"name":"hint","type":"flags.0?string"},{"name":"email","type":"flags.1?string"},{"name":"new_secure_settings","type":"flags.2?SecureSecretSettings"}],"type":"account.PasswordInputSettings"},{"id":"326715557","predicate":"auth.passwordRecovery","params":[{"name":"email_pattern","type":"string"}],"type":"auth.PasswordRecovery"},{"id":"-1052959727","predicate":"inputMediaVenue","params":[{"name":"geo_point","type":"InputGeoPoint"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"},{"name":"venue_type","type":"string"}],"type":"InputMedia"},{"id":"784356159","predicate":"messageMediaVenue","params":[{"name":"geo","type":"GeoPoint"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"},{"name":"venue_type","type":"string"}],"type":"MessageMedia"},{"id":"-1551583367","predicate":"receivedNotifyMessage","params":[{"name":"id","type":"int"},{"name":"flags","type":"int"}],"type":"ReceivedNotifyMessage"},{"id":"-1316944408","predicate":"chatInviteExported","params":[{"name":"flags","type":"#"},{"name":"revoked","type":"flags.0?true"},{"name":"permanent","type":"flags.5?true"},{"name":"link","type":"string"},{"name":"admin_id","type":"long"},{"name":"date","type":"int"},{"name":"start_date","type":"flags.4?int"},{"name":"expire_date","type":"flags.1?int"},{"name":"usage_limit","type":"flags.2?int"},{"name":"usage","type":"flags.3?int"}],"type":"ExportedChatInvite"},{"id":"1516793212","predicate":"chatInviteAlready","params":[{"name":"chat","type":"Chat"}],"type":"ChatInvite"},{"id":"-540871282","predicate":"chatInvite","params":[{"name":"flags","type":"#"},{"name":"channel","type":"flags.0?true"},{"name":"broadcast","type":"flags.1?true"},{"name":"public","type":"flags.2?true"},{"name":"megagroup","type":"flags.3?true"},{"name":"title","type":"string"},{"name":"photo","type":"Photo"},{"name":"participants_count","type":"int"},{"name":"participants","type":"flags.4?Vector"}],"type":"ChatInvite"},{"id":"51520707","predicate":"messageActionChatJoinedByLink","params":[{"name":"inviter_id","type":"long"}],"type":"MessageAction"},{"id":"1757493555","predicate":"updateReadMessagesContents","params":[{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-4838507","predicate":"inputStickerSetEmpty","params":[],"type":"InputStickerSet"},{"id":"-1645763991","predicate":"inputStickerSetID","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputStickerSet"},{"id":"-2044933984","predicate":"inputStickerSetShortName","params":[{"name":"short_name","type":"string"}],"type":"InputStickerSet"},{"id":"-673242758","predicate":"stickerSet","params":[{"name":"flags","type":"#"},{"name":"archived","type":"flags.1?true"},{"name":"official","type":"flags.2?true"},{"name":"masks","type":"flags.3?true"},{"name":"animated","type":"flags.5?true"},{"name":"videos","type":"flags.6?true"},{"name":"installed_date","type":"flags.0?int"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"title","type":"string"},{"name":"short_name","type":"string"},{"name":"thumbs","type":"flags.4?Vector"},{"name":"thumb_dc_id","type":"flags.4?int"},{"name":"thumb_version","type":"flags.4?int"},{"name":"count","type":"int"},{"name":"hash","type":"int"}],"type":"StickerSet"},{"id":"-1240849242","predicate":"messages.stickerSet","params":[{"name":"set","type":"StickerSet"},{"name":"packs","type":"Vector"},{"name":"documents","type":"Vector"}],"type":"messages.StickerSet"},{"id":"1073147056","predicate":"user","params":[{"name":"flags","type":"#"},{"name":"self","type":"flags.10?true"},{"name":"contact","type":"flags.11?true"},{"name":"mutual_contact","type":"flags.12?true"},{"name":"deleted","type":"flags.13?true"},{"name":"bot","type":"flags.14?true"},{"name":"bot_chat_history","type":"flags.15?true"},{"name":"bot_nochats","type":"flags.16?true"},{"name":"verified","type":"flags.17?true"},{"name":"restricted","type":"flags.18?true"},{"name":"min","type":"flags.20?true"},{"name":"bot_inline_geo","type":"flags.21?true"},{"name":"support","type":"flags.23?true"},{"name":"scam","type":"flags.24?true"},{"name":"apply_min_photo","type":"flags.25?true"},{"name":"fake","type":"flags.26?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"flags.0?long"},{"name":"first_name","type":"flags.1?string"},{"name":"last_name","type":"flags.2?string"},{"name":"username","type":"flags.3?string"},{"name":"phone","type":"flags.4?string"},{"name":"photo","type":"flags.5?UserProfilePhoto"},{"name":"status","type":"flags.6?UserStatus"},{"name":"bot_info_version","type":"flags.14?int"},{"name":"restriction_reason","type":"flags.18?Vector"},{"name":"bot_inline_placeholder","type":"flags.19?string"},{"name":"lang_code","type":"flags.22?string"}],"type":"User"},{"id":"-1032140601","predicate":"botCommand","params":[{"name":"command","type":"string"},{"name":"description","type":"string"}],"type":"BotCommand"},{"id":"460632885","predicate":"botInfo","params":[{"name":"user_id","type":"long"},{"name":"description","type":"string"},{"name":"commands","type":"Vector"}],"type":"BotInfo"},{"id":"-1560655744","predicate":"keyboardButton","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"2002815875","predicate":"keyboardButtonRow","params":[{"name":"buttons","type":"Vector"}],"type":"KeyboardButtonRow"},{"id":"-1606526075","predicate":"replyKeyboardHide","params":[{"name":"flags","type":"#"},{"name":"selective","type":"flags.2?true"}],"type":"ReplyMarkup"},{"id":"-2035021048","predicate":"replyKeyboardForceReply","params":[{"name":"flags","type":"#"},{"name":"single_use","type":"flags.1?true"},{"name":"selective","type":"flags.2?true"},{"name":"placeholder","type":"flags.3?string"}],"type":"ReplyMarkup"},{"id":"-2049074735","predicate":"replyKeyboardMarkup","params":[{"name":"flags","type":"#"},{"name":"resize","type":"flags.0?true"},{"name":"single_use","type":"flags.1?true"},{"name":"selective","type":"flags.2?true"},{"name":"rows","type":"Vector"},{"name":"placeholder","type":"flags.3?string"}],"type":"ReplyMarkup"},{"id":"-571955892","predicate":"inputPeerUser","params":[{"name":"user_id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputPeer"},{"id":"-233744186","predicate":"inputUser","params":[{"name":"user_id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputUser"},{"id":"-1148011883","predicate":"messageEntityUnknown","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-100378723","predicate":"messageEntityMention","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1868782349","predicate":"messageEntityHashtag","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1827637959","predicate":"messageEntityBotCommand","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1859134776","predicate":"messageEntityUrl","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1692693954","predicate":"messageEntityEmail","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-1117713463","predicate":"messageEntityBold","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-2106619040","predicate":"messageEntityItalic","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"681706865","predicate":"messageEntityCode","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1938967520","predicate":"messageEntityPre","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"language","type":"string"}],"type":"MessageEntity"},{"id":"1990644519","predicate":"messageEntityTextUrl","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"url","type":"string"}],"type":"MessageEntity"},{"id":"-1877614335","predicate":"updateShortSentMessage","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"id","type":"int"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"date","type":"int"},{"name":"media","type":"flags.9?MessageMedia"},{"name":"entities","type":"flags.7?Vector"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Updates"},{"id":"-292807034","predicate":"inputChannelEmpty","params":[],"type":"InputChannel"},{"id":"-212145112","predicate":"inputChannel","params":[{"name":"channel_id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputChannel"},{"id":"-1566230754","predicate":"peerChannel","params":[{"name":"channel_id","type":"long"}],"type":"Peer"},{"id":"666680316","predicate":"inputPeerChannel","params":[{"name":"channel_id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputPeer"},{"id":"-2107528095","predicate":"channel","params":[{"name":"flags","type":"#"},{"name":"creator","type":"flags.0?true"},{"name":"left","type":"flags.2?true"},{"name":"broadcast","type":"flags.5?true"},{"name":"verified","type":"flags.7?true"},{"name":"megagroup","type":"flags.8?true"},{"name":"restricted","type":"flags.9?true"},{"name":"signatures","type":"flags.11?true"},{"name":"min","type":"flags.12?true"},{"name":"scam","type":"flags.19?true"},{"name":"has_link","type":"flags.20?true"},{"name":"has_geo","type":"flags.21?true"},{"name":"slowmode_enabled","type":"flags.22?true"},{"name":"call_active","type":"flags.23?true"},{"name":"call_not_empty","type":"flags.24?true"},{"name":"fake","type":"flags.25?true"},{"name":"gigagroup","type":"flags.26?true"},{"name":"noforwards","type":"flags.27?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"flags.13?long"},{"name":"title","type":"string"},{"name":"username","type":"flags.6?string"},{"name":"photo","type":"ChatPhoto"},{"name":"date","type":"int"},{"name":"restriction_reason","type":"flags.9?Vector"},{"name":"admin_rights","type":"flags.14?ChatAdminRights"},{"name":"banned_rights","type":"flags.15?ChatBannedRights"},{"name":"default_banned_rights","type":"flags.18?ChatBannedRights"},{"name":"participants_count","type":"flags.17?int"}],"type":"Chat"},{"id":"399807445","predicate":"channelForbidden","params":[{"name":"flags","type":"#"},{"name":"broadcast","type":"flags.5?true"},{"name":"megagroup","type":"flags.8?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"title","type":"string"},{"name":"until_date","type":"flags.16?int"}],"type":"Chat"},{"id":"2131196633","predicate":"contacts.resolvedPeer","params":[{"name":"peer","type":"Peer"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.ResolvedPeer"},{"id":"-374179305","predicate":"channelFull","params":[{"name":"flags","type":"#"},{"name":"can_view_participants","type":"flags.3?true"},{"name":"can_set_username","type":"flags.6?true"},{"name":"can_set_stickers","type":"flags.7?true"},{"name":"hidden_prehistory","type":"flags.10?true"},{"name":"can_set_location","type":"flags.16?true"},{"name":"has_scheduled","type":"flags.19?true"},{"name":"can_view_stats","type":"flags.20?true"},{"name":"blocked","type":"flags.22?true"},{"name":"id","type":"long"},{"name":"about","type":"string"},{"name":"participants_count","type":"flags.0?int"},{"name":"admins_count","type":"flags.1?int"},{"name":"kicked_count","type":"flags.2?int"},{"name":"banned_count","type":"flags.2?int"},{"name":"online_count","type":"flags.13?int"},{"name":"read_inbox_max_id","type":"int"},{"name":"read_outbox_max_id","type":"int"},{"name":"unread_count","type":"int"},{"name":"chat_photo","type":"Photo"},{"name":"notify_settings","type":"PeerNotifySettings"},{"name":"exported_invite","type":"flags.23?ExportedChatInvite"},{"name":"bot_info","type":"Vector"},{"name":"migrated_from_chat_id","type":"flags.4?long"},{"name":"migrated_from_max_id","type":"flags.4?int"},{"name":"pinned_msg_id","type":"flags.5?int"},{"name":"stickerset","type":"flags.8?StickerSet"},{"name":"available_min_id","type":"flags.9?int"},{"name":"folder_id","type":"flags.11?int"},{"name":"linked_chat_id","type":"flags.14?long"},{"name":"location","type":"flags.15?ChannelLocation"},{"name":"slowmode_seconds","type":"flags.17?int"},{"name":"slowmode_next_send_date","type":"flags.18?int"},{"name":"stats_dc","type":"flags.12?int"},{"name":"pts","type":"int"},{"name":"call","type":"flags.21?InputGroupCall"},{"name":"ttl_period","type":"flags.24?int"},{"name":"pending_suggestions","type":"flags.25?Vector"},{"name":"groupcall_default_join_as","type":"flags.26?Peer"},{"name":"theme_emoticon","type":"flags.27?string"}],"type":"ChatFull"},{"id":"182649427","predicate":"messageRange","params":[{"name":"min_id","type":"int"},{"name":"max_id","type":"int"}],"type":"MessageRange"},{"id":"1682413576","predicate":"messages.channelMessages","params":[{"name":"flags","type":"#"},{"name":"inexact","type":"flags.1?true"},{"name":"pts","type":"int"},{"name":"count","type":"int"},{"name":"offset_id_offset","type":"flags.2?int"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Messages"},{"id":"-1781355374","predicate":"messageActionChannelCreate","params":[{"name":"title","type":"string"}],"type":"MessageAction"},{"id":"277713951","predicate":"updateChannelTooLong","params":[{"name":"flags","type":"#"},{"name":"channel_id","type":"long"},{"name":"pts","type":"flags.0?int"}],"type":"Update"},{"id":"1666927625","predicate":"updateChannel","params":[{"name":"channel_id","type":"long"}],"type":"Update"},{"id":"1656358105","predicate":"updateNewChannelMessage","params":[{"name":"message","type":"Message"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1842450928","predicate":"updateReadChannelInbox","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.0?int"},{"name":"channel_id","type":"long"},{"name":"max_id","type":"int"},{"name":"still_unread_count","type":"int"},{"name":"pts","type":"int"}],"type":"Update"},{"id":"-1020437742","predicate":"updateDeleteChannelMessages","params":[{"name":"channel_id","type":"long"},{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-232346616","predicate":"updateChannelMessageViews","params":[{"name":"channel_id","type":"long"},{"name":"id","type":"int"},{"name":"views","type":"int"}],"type":"Update"},{"id":"1041346555","predicate":"updates.channelDifferenceEmpty","params":[{"name":"flags","type":"#"},{"name":"final","type":"flags.0?true"},{"name":"pts","type":"int"},{"name":"timeout","type":"flags.1?int"}],"type":"updates.ChannelDifference"},{"id":"-1531132162","predicate":"updates.channelDifferenceTooLong","params":[{"name":"flags","type":"#"},{"name":"final","type":"flags.0?true"},{"name":"timeout","type":"flags.1?int"},{"name":"dialog","type":"Dialog"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"updates.ChannelDifference"},{"id":"543450958","predicate":"updates.channelDifference","params":[{"name":"flags","type":"#"},{"name":"final","type":"flags.0?true"},{"name":"pts","type":"int"},{"name":"timeout","type":"flags.1?int"},{"name":"new_messages","type":"Vector"},{"name":"other_updates","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"updates.ChannelDifference"},{"id":"-1798033689","predicate":"channelMessagesFilterEmpty","params":[],"type":"ChannelMessagesFilter"},{"id":"-847783593","predicate":"channelMessagesFilter","params":[{"name":"flags","type":"#"},{"name":"exclude_new_messages","type":"flags.1?true"},{"name":"ranges","type":"Vector"}],"type":"ChannelMessagesFilter"},{"id":"-1072953408","predicate":"channelParticipant","params":[{"name":"user_id","type":"long"},{"name":"date","type":"int"}],"type":"ChannelParticipant"},{"id":"682146919","predicate":"channelParticipantSelf","params":[{"name":"user_id","type":"long"},{"name":"inviter_id","type":"long"},{"name":"date","type":"int"}],"type":"ChannelParticipant"},{"id":"803602899","predicate":"channelParticipantCreator","params":[{"name":"flags","type":"#"},{"name":"user_id","type":"long"},{"name":"admin_rights","type":"ChatAdminRights"},{"name":"rank","type":"flags.0?string"}],"type":"ChannelParticipant"},{"id":"-566281095","predicate":"channelParticipantsRecent","params":[],"type":"ChannelParticipantsFilter"},{"id":"-1268741783","predicate":"channelParticipantsAdmins","params":[],"type":"ChannelParticipantsFilter"},{"id":"-1548400251","predicate":"channelParticipantsKicked","params":[{"name":"q","type":"string"}],"type":"ChannelParticipantsFilter"},{"id":"-1699676497","predicate":"channels.channelParticipants","params":[{"name":"count","type":"int"},{"name":"participants","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"channels.ChannelParticipants"},{"id":"-541588713","predicate":"channels.channelParticipant","params":[{"name":"participant","type":"ChannelParticipant"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"channels.ChannelParticipant"},{"id":"-462696732","predicate":"chatParticipantCreator","params":[{"name":"user_id","type":"long"}],"type":"ChatParticipant"},{"id":"-1600962725","predicate":"chatParticipantAdmin","params":[{"name":"user_id","type":"long"},{"name":"inviter_id","type":"long"},{"name":"date","type":"int"}],"type":"ChatParticipant"},{"id":"-674602590","predicate":"updateChatParticipantAdmin","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"long"},{"name":"is_admin","type":"Bool"},{"name":"version","type":"int"}],"type":"Update"},{"id":"-519864430","predicate":"messageActionChatMigrateTo","params":[{"name":"channel_id","type":"long"}],"type":"MessageAction"},{"id":"-365344535","predicate":"messageActionChannelMigrateFrom","params":[{"name":"title","type":"string"},{"name":"chat_id","type":"long"}],"type":"MessageAction"},{"id":"-1328445861","predicate":"channelParticipantsBots","params":[],"type":"ChannelParticipantsFilter"},{"id":"2013922064","predicate":"help.termsOfService","params":[{"name":"flags","type":"#"},{"name":"popup","type":"flags.0?true"},{"name":"id","type":"DataJSON"},{"name":"text","type":"string"},{"name":"entities","type":"Vector"},{"name":"min_age_confirm","type":"flags.1?int"}],"type":"help.TermsOfService"},{"id":"1753886890","predicate":"updateNewStickerSet","params":[{"name":"stickerset","type":"messages.StickerSet"}],"type":"Update"},{"id":"196268545","predicate":"updateStickerSetsOrder","params":[{"name":"flags","type":"#"},{"name":"masks","type":"flags.0?true"},{"name":"order","type":"Vector"}],"type":"Update"},{"id":"1135492588","predicate":"updateStickerSets","params":[],"type":"Update"},{"id":"-402498398","predicate":"messages.savedGifsNotModified","params":[],"type":"messages.SavedGifs"},{"id":"-2069878259","predicate":"messages.savedGifs","params":[{"name":"hash","type":"long"},{"name":"gifs","type":"Vector"}],"type":"messages.SavedGifs"},{"id":"-1821035490","predicate":"updateSavedGifs","params":[],"type":"Update"},{"id":"864077702","predicate":"inputBotInlineMessageMediaAuto","params":[{"name":"flags","type":"#"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"1036876423","predicate":"inputBotInlineMessageText","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.0?true"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"-2000710887","predicate":"inputBotInlineResult","params":[{"name":"flags","type":"#"},{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"title","type":"flags.1?string"},{"name":"description","type":"flags.2?string"},{"name":"url","type":"flags.3?string"},{"name":"thumb","type":"flags.4?InputWebDocument"},{"name":"content","type":"flags.5?InputWebDocument"},{"name":"send_message","type":"InputBotInlineMessage"}],"type":"InputBotInlineResult"},{"id":"1984755728","predicate":"botInlineMessageMediaAuto","params":[{"name":"flags","type":"#"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"-1937807902","predicate":"botInlineMessageText","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.0?true"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"295067450","predicate":"botInlineResult","params":[{"name":"flags","type":"#"},{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"title","type":"flags.1?string"},{"name":"description","type":"flags.2?string"},{"name":"url","type":"flags.3?string"},{"name":"thumb","type":"flags.4?WebDocument"},{"name":"content","type":"flags.5?WebDocument"},{"name":"send_message","type":"BotInlineMessage"}],"type":"BotInlineResult"},{"id":"-1803769784","predicate":"messages.botResults","params":[{"name":"flags","type":"#"},{"name":"gallery","type":"flags.0?true"},{"name":"query_id","type":"long"},{"name":"next_offset","type":"flags.1?string"},{"name":"switch_pm","type":"flags.2?InlineBotSwitchPM"},{"name":"results","type":"Vector"},{"name":"cache_time","type":"int"},{"name":"users","type":"Vector"}],"type":"messages.BotResults"},{"id":"1232025500","predicate":"updateBotInlineQuery","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"query","type":"string"},{"name":"geo","type":"flags.0?GeoPoint"},{"name":"peer_type","type":"flags.1?InlineQueryPeerType"},{"name":"offset","type":"string"}],"type":"Update"},{"id":"317794823","predicate":"updateBotInlineSend","params":[{"name":"flags","type":"#"},{"name":"user_id","type":"long"},{"name":"query","type":"string"},{"name":"geo","type":"flags.0?GeoPoint"},{"name":"id","type":"string"},{"name":"msg_id","type":"flags.1?InputBotInlineMessageID"}],"type":"Update"},{"id":"1358283666","predicate":"inputMessagesFilterVoice","params":[],"type":"MessagesFilter"},{"id":"928101534","predicate":"inputMessagesFilterMusic","params":[],"type":"MessagesFilter"},{"id":"-1107622874","predicate":"inputPrivacyKeyChatInvite","params":[],"type":"InputPrivacyKey"},{"id":"1343122938","predicate":"privacyKeyChatInvite","params":[],"type":"PrivacyKey"},{"id":"1571494644","predicate":"exportedMessageLink","params":[{"name":"link","type":"string"},{"name":"html","type":"string"}],"type":"ExportedMessageLink"},{"id":"1601666510","predicate":"messageFwdHeader","params":[{"name":"flags","type":"#"},{"name":"imported","type":"flags.7?true"},{"name":"from_id","type":"flags.0?Peer"},{"name":"from_name","type":"flags.5?string"},{"name":"date","type":"int"},{"name":"channel_post","type":"flags.2?int"},{"name":"post_author","type":"flags.3?string"},{"name":"saved_from_peer","type":"flags.4?Peer"},{"name":"saved_from_msg_id","type":"flags.4?int"},{"name":"psa_type","type":"flags.6?string"}],"type":"MessageFwdHeader"},{"id":"457133559","predicate":"updateEditChannelMessage","params":[{"name":"message","type":"Message"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1799538451","predicate":"messageActionPinMessage","params":[],"type":"MessageAction"},{"id":"1923290508","predicate":"auth.codeTypeSms","params":[],"type":"auth.CodeType"},{"id":"1948046307","predicate":"auth.codeTypeCall","params":[],"type":"auth.CodeType"},{"id":"577556219","predicate":"auth.codeTypeFlashCall","params":[],"type":"auth.CodeType"},{"id":"1035688326","predicate":"auth.sentCodeTypeApp","params":[{"name":"length","type":"int"}],"type":"auth.SentCodeType"},{"id":"-1073693790","predicate":"auth.sentCodeTypeSms","params":[{"name":"length","type":"int"}],"type":"auth.SentCodeType"},{"id":"1398007207","predicate":"auth.sentCodeTypeCall","params":[{"name":"length","type":"int"}],"type":"auth.SentCodeType"},{"id":"-1425815847","predicate":"auth.sentCodeTypeFlashCall","params":[{"name":"pattern","type":"string"}],"type":"auth.SentCodeType"},{"id":"629866245","predicate":"keyboardButtonUrl","params":[{"name":"text","type":"string"},{"name":"url","type":"string"}],"type":"KeyboardButton"},{"id":"901503851","predicate":"keyboardButtonCallback","params":[{"name":"flags","type":"#"},{"name":"requires_password","type":"flags.0?true"},{"name":"text","type":"string"},{"name":"data","type":"bytes"}],"type":"KeyboardButton"},{"id":"-1318425559","predicate":"keyboardButtonRequestPhone","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"-59151553","predicate":"keyboardButtonRequestGeoLocation","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"90744648","predicate":"keyboardButtonSwitchInline","params":[{"name":"flags","type":"#"},{"name":"same_peer","type":"flags.0?true"},{"name":"text","type":"string"},{"name":"query","type":"string"}],"type":"KeyboardButton"},{"id":"1218642516","predicate":"replyInlineMarkup","params":[{"name":"rows","type":"Vector"}],"type":"ReplyMarkup"},{"id":"911761060","predicate":"messages.botCallbackAnswer","params":[{"name":"flags","type":"#"},{"name":"alert","type":"flags.1?true"},{"name":"has_url","type":"flags.3?true"},{"name":"native_ui","type":"flags.4?true"},{"name":"message","type":"flags.0?string"},{"name":"url","type":"flags.2?string"},{"name":"cache_time","type":"int"}],"type":"messages.BotCallbackAnswer"},{"id":"-1177566067","predicate":"updateBotCallbackQuery","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"peer","type":"Peer"},{"name":"msg_id","type":"int"},{"name":"chat_instance","type":"long"},{"name":"data","type":"flags.0?bytes"},{"name":"game_short_name","type":"flags.1?string"}],"type":"Update"},{"id":"649453030","predicate":"messages.messageEditData","params":[{"name":"flags","type":"#"},{"name":"caption","type":"flags.0?true"}],"type":"messages.MessageEditData"},{"id":"-469536605","predicate":"updateEditMessage","params":[{"name":"message","type":"Message"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1768777083","predicate":"inputBotInlineMessageMediaGeo","params":[{"name":"flags","type":"#"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"heading","type":"flags.0?int"},{"name":"period","type":"flags.1?int"},{"name":"proximity_notification_radius","type":"flags.3?int"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"1098628881","predicate":"inputBotInlineMessageMediaVenue","params":[{"name":"flags","type":"#"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"},{"name":"venue_type","type":"string"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"-1494368259","predicate":"inputBotInlineMessageMediaContact","params":[{"name":"flags","type":"#"},{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"vcard","type":"string"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"85477117","predicate":"botInlineMessageMediaGeo","params":[{"name":"flags","type":"#"},{"name":"geo","type":"GeoPoint"},{"name":"heading","type":"flags.0?int"},{"name":"period","type":"flags.1?int"},{"name":"proximity_notification_radius","type":"flags.3?int"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"-1970903652","predicate":"botInlineMessageMediaVenue","params":[{"name":"flags","type":"#"},{"name":"geo","type":"GeoPoint"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"},{"name":"venue_type","type":"string"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"416402882","predicate":"botInlineMessageMediaContact","params":[{"name":"flags","type":"#"},{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"vcard","type":"string"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"-1462213465","predicate":"inputBotInlineResultPhoto","params":[{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"photo","type":"InputPhoto"},{"name":"send_message","type":"InputBotInlineMessage"}],"type":"InputBotInlineResult"},{"id":"-459324","predicate":"inputBotInlineResultDocument","params":[{"name":"flags","type":"#"},{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"title","type":"flags.1?string"},{"name":"description","type":"flags.2?string"},{"name":"document","type":"InputDocument"},{"name":"send_message","type":"InputBotInlineMessage"}],"type":"InputBotInlineResult"},{"id":"400266251","predicate":"botInlineMediaResult","params":[{"name":"flags","type":"#"},{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"photo","type":"flags.0?Photo"},{"name":"document","type":"flags.1?Document"},{"name":"title","type":"flags.2?string"},{"name":"description","type":"flags.3?string"},{"name":"send_message","type":"BotInlineMessage"}],"type":"BotInlineResult"},{"id":"-1995686519","predicate":"inputBotInlineMessageID","params":[{"name":"dc_id","type":"int"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputBotInlineMessageID"},{"id":"1763610706","predicate":"updateInlineBotCallbackQuery","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"msg_id","type":"InputBotInlineMessageID"},{"name":"chat_instance","type":"long"},{"name":"data","type":"flags.0?bytes"},{"name":"game_short_name","type":"flags.1?string"}],"type":"Update"},{"id":"1008755359","predicate":"inlineBotSwitchPM","params":[{"name":"text","type":"string"},{"name":"start_param","type":"string"}],"type":"InlineBotSwitchPM"},{"id":"863093588","predicate":"messages.peerDialogs","params":[{"name":"dialogs","type":"Vector"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"state","type":"updates.State"}],"type":"messages.PeerDialogs"},{"id":"-305282981","predicate":"topPeer","params":[{"name":"peer","type":"Peer"},{"name":"rating","type":"double"}],"type":"TopPeer"},{"id":"-1419371685","predicate":"topPeerCategoryBotsPM","params":[],"type":"TopPeerCategory"},{"id":"344356834","predicate":"topPeerCategoryBotsInline","params":[],"type":"TopPeerCategory"},{"id":"104314861","predicate":"topPeerCategoryCorrespondents","params":[],"type":"TopPeerCategory"},{"id":"-1122524854","predicate":"topPeerCategoryGroups","params":[],"type":"TopPeerCategory"},{"id":"371037736","predicate":"topPeerCategoryChannels","params":[],"type":"TopPeerCategory"},{"id":"-75283823","predicate":"topPeerCategoryPeers","params":[{"name":"category","type":"TopPeerCategory"},{"name":"count","type":"int"},{"name":"peers","type":"Vector"}],"type":"TopPeerCategoryPeers"},{"id":"-567906571","predicate":"contacts.topPeersNotModified","params":[],"type":"contacts.TopPeers"},{"id":"1891070632","predicate":"contacts.topPeers","params":[{"name":"categories","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.TopPeers"},{"id":"-595914432","predicate":"messageEntityMentionName","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"user_id","type":"long"}],"type":"MessageEntity"},{"id":"546203849","predicate":"inputMessageEntityMentionName","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"user_id","type":"InputUser"}],"type":"MessageEntity"},{"id":"975236280","predicate":"inputMessagesFilterChatPhotos","params":[],"type":"MessagesFilter"},{"id":"-1218471511","predicate":"updateReadChannelOutbox","params":[{"name":"channel_id","type":"long"},{"name":"max_id","type":"int"}],"type":"Update"},{"id":"-299124375","predicate":"updateDraftMessage","params":[{"name":"peer","type":"Peer"},{"name":"draft","type":"DraftMessage"}],"type":"Update"},{"id":"453805082","predicate":"draftMessageEmpty","params":[{"name":"flags","type":"#"},{"name":"date","type":"flags.0?int"}],"type":"DraftMessage"},{"id":"-40996577","predicate":"draftMessage","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"message","type":"string"},{"name":"entities","type":"flags.3?Vector"},{"name":"date","type":"int"}],"type":"DraftMessage"},{"id":"-1615153660","predicate":"messageActionHistoryClear","params":[],"type":"MessageAction"},{"id":"-958657434","predicate":"messages.featuredStickersNotModified","params":[{"name":"count","type":"int"}],"type":"messages.FeaturedStickers"},{"id":"-2067782896","predicate":"messages.featuredStickers","params":[{"name":"hash","type":"long"},{"name":"count","type":"int"},{"name":"sets","type":"Vector"},{"name":"unread","type":"Vector"}],"type":"messages.FeaturedStickers"},{"id":"1461528386","predicate":"updateReadFeaturedStickers","params":[],"type":"Update"},{"id":"186120336","predicate":"messages.recentStickersNotModified","params":[],"type":"messages.RecentStickers"},{"id":"-1999405994","predicate":"messages.recentStickers","params":[{"name":"hash","type":"long"},{"name":"packs","type":"Vector"},{"name":"stickers","type":"Vector"},{"name":"dates","type":"Vector"}],"type":"messages.RecentStickers"},{"id":"-1706939360","predicate":"updateRecentStickers","params":[],"type":"Update"},{"id":"1338747336","predicate":"messages.archivedStickers","params":[{"name":"count","type":"int"},{"name":"sets","type":"Vector"}],"type":"messages.ArchivedStickers"},{"id":"946083368","predicate":"messages.stickerSetInstallResultSuccess","params":[],"type":"messages.StickerSetInstallResult"},{"id":"904138920","predicate":"messages.stickerSetInstallResultArchive","params":[{"name":"sets","type":"Vector"}],"type":"messages.StickerSetInstallResult"},{"id":"1678812626","predicate":"stickerSetCovered","params":[{"name":"set","type":"StickerSet"},{"name":"cover","type":"Document"}],"type":"StickerSetCovered"},{"id":"-1574314746","predicate":"updateConfig","params":[],"type":"Update"},{"id":"861169551","predicate":"updatePtsChanged","params":[],"type":"Update"},{"id":"-440664550","predicate":"inputMediaPhotoExternal","params":[{"name":"flags","type":"#"},{"name":"url","type":"string"},{"name":"ttl_seconds","type":"flags.0?int"}],"type":"InputMedia"},{"id":"-78455655","predicate":"inputMediaDocumentExternal","params":[{"name":"flags","type":"#"},{"name":"url","type":"string"},{"name":"ttl_seconds","type":"flags.0?int"}],"type":"InputMedia"},{"id":"872932635","predicate":"stickerSetMultiCovered","params":[{"name":"set","type":"StickerSet"},{"name":"covers","type":"Vector"}],"type":"StickerSetCovered"},{"id":"-1361650766","predicate":"maskCoords","params":[{"name":"n","type":"int"},{"name":"x","type":"double"},{"name":"y","type":"double"},{"name":"zoom","type":"double"}],"type":"MaskCoords"},{"id":"-1744710921","predicate":"documentAttributeHasStickers","params":[],"type":"DocumentAttribute"},{"id":"1251549527","predicate":"inputStickeredMediaPhoto","params":[{"name":"id","type":"InputPhoto"}],"type":"InputStickeredMedia"},{"id":"70813275","predicate":"inputStickeredMediaDocument","params":[{"name":"id","type":"InputDocument"}],"type":"InputStickeredMedia"},{"id":"-1107729093","predicate":"game","params":[{"name":"flags","type":"#"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"short_name","type":"string"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"Photo"},{"name":"document","type":"flags.0?Document"}],"type":"Game"},{"id":"1336154098","predicate":"inputBotInlineResultGame","params":[{"name":"id","type":"string"},{"name":"short_name","type":"string"},{"name":"send_message","type":"InputBotInlineMessage"}],"type":"InputBotInlineResult"},{"id":"1262639204","predicate":"inputBotInlineMessageGame","params":[{"name":"flags","type":"#"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"-38694904","predicate":"messageMediaGame","params":[{"name":"game","type":"Game"}],"type":"MessageMedia"},{"id":"-750828557","predicate":"inputMediaGame","params":[{"name":"id","type":"InputGame"}],"type":"InputMedia"},{"id":"53231223","predicate":"inputGameID","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputGame"},{"id":"-1020139510","predicate":"inputGameShortName","params":[{"name":"bot_id","type":"InputUser"},{"name":"short_name","type":"string"}],"type":"InputGame"},{"id":"1358175439","predicate":"keyboardButtonGame","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"-1834538890","predicate":"messageActionGameScore","params":[{"name":"game_id","type":"long"},{"name":"score","type":"int"}],"type":"MessageAction"},{"id":"1940093419","predicate":"highScore","params":[{"name":"pos","type":"int"},{"name":"user_id","type":"long"},{"name":"score","type":"int"}],"type":"HighScore"},{"id":"-1707344487","predicate":"messages.highScores","params":[{"name":"scores","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.HighScores"},{"id":"1258196845","predicate":"updates.differenceTooLong","params":[{"name":"pts","type":"int"}],"type":"updates.Difference"},{"id":"791390623","predicate":"updateChannelWebPage","params":[{"name":"channel_id","type":"long"},{"name":"webpage","type":"WebPage"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1663561404","predicate":"messages.chatsSlice","params":[{"name":"count","type":"int"},{"name":"chats","type":"Vector"}],"type":"messages.Chats"},{"id":"-599948721","predicate":"textEmpty","params":[],"type":"RichText"},{"id":"1950782688","predicate":"textPlain","params":[{"name":"text","type":"string"}],"type":"RichText"},{"id":"1730456516","predicate":"textBold","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"-653089380","predicate":"textItalic","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"-1054465340","predicate":"textUnderline","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"-1678197867","predicate":"textStrike","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"1816074681","predicate":"textFixed","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"1009288385","predicate":"textUrl","params":[{"name":"text","type":"RichText"},{"name":"url","type":"string"},{"name":"webpage_id","type":"long"}],"type":"RichText"},{"id":"-564523562","predicate":"textEmail","params":[{"name":"text","type":"RichText"},{"name":"email","type":"string"}],"type":"RichText"},{"id":"2120376535","predicate":"textConcat","params":[{"name":"texts","type":"Vector"}],"type":"RichText"},{"id":"324435594","predicate":"pageBlockUnsupported","params":[],"type":"PageBlock"},{"id":"1890305021","predicate":"pageBlockTitle","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-1879401953","predicate":"pageBlockSubtitle","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-1162877472","predicate":"pageBlockAuthorDate","params":[{"name":"author","type":"RichText"},{"name":"published_date","type":"int"}],"type":"PageBlock"},{"id":"-1076861716","predicate":"pageBlockHeader","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-248793375","predicate":"pageBlockSubheader","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"1182402406","predicate":"pageBlockParagraph","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-1066346178","predicate":"pageBlockPreformatted","params":[{"name":"text","type":"RichText"},{"name":"language","type":"string"}],"type":"PageBlock"},{"id":"1216809369","predicate":"pageBlockFooter","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-618614392","predicate":"pageBlockDivider","params":[],"type":"PageBlock"},{"id":"-837994576","predicate":"pageBlockAnchor","params":[{"name":"name","type":"string"}],"type":"PageBlock"},{"id":"-454524911","predicate":"pageBlockList","params":[{"name":"items","type":"Vector"}],"type":"PageBlock"},{"id":"641563686","predicate":"pageBlockBlockquote","params":[{"name":"text","type":"RichText"},{"name":"caption","type":"RichText"}],"type":"PageBlock"},{"id":"1329878739","predicate":"pageBlockPullquote","params":[{"name":"text","type":"RichText"},{"name":"caption","type":"RichText"}],"type":"PageBlock"},{"id":"391759200","predicate":"pageBlockPhoto","params":[{"name":"flags","type":"#"},{"name":"photo_id","type":"long"},{"name":"caption","type":"PageCaption"},{"name":"url","type":"flags.0?string"},{"name":"webpage_id","type":"flags.0?long"}],"type":"PageBlock"},{"id":"2089805750","predicate":"pageBlockVideo","params":[{"name":"flags","type":"#"},{"name":"autoplay","type":"flags.0?true"},{"name":"loop","type":"flags.1?true"},{"name":"video_id","type":"long"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"972174080","predicate":"pageBlockCover","params":[{"name":"cover","type":"PageBlock"}],"type":"PageBlock"},{"id":"-1468953147","predicate":"pageBlockEmbed","params":[{"name":"flags","type":"#"},{"name":"full_width","type":"flags.0?true"},{"name":"allow_scrolling","type":"flags.3?true"},{"name":"url","type":"flags.1?string"},{"name":"html","type":"flags.2?string"},{"name":"poster_photo_id","type":"flags.4?long"},{"name":"w","type":"flags.5?int"},{"name":"h","type":"flags.5?int"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"-229005301","predicate":"pageBlockEmbedPost","params":[{"name":"url","type":"string"},{"name":"webpage_id","type":"long"},{"name":"author_photo_id","type":"long"},{"name":"author","type":"string"},{"name":"date","type":"int"},{"name":"blocks","type":"Vector"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"1705048653","predicate":"pageBlockCollage","params":[{"name":"items","type":"Vector"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"52401552","predicate":"pageBlockSlideshow","params":[{"name":"items","type":"Vector"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"1930545681","predicate":"webPageNotModified","params":[{"name":"flags","type":"#"},{"name":"cached_page_views","type":"flags.0?int"}],"type":"WebPage"},{"id":"-88417185","predicate":"inputPrivacyKeyPhoneCall","params":[],"type":"InputPrivacyKey"},{"id":"1030105979","predicate":"privacyKeyPhoneCall","params":[],"type":"PrivacyKey"},{"id":"-580219064","predicate":"sendMessageGamePlayAction","params":[],"type":"SendMessageAction"},{"id":"-2048646399","predicate":"phoneCallDiscardReasonMissed","params":[],"type":"PhoneCallDiscardReason"},{"id":"-527056480","predicate":"phoneCallDiscardReasonDisconnect","params":[],"type":"PhoneCallDiscardReason"},{"id":"1471006352","predicate":"phoneCallDiscardReasonHangup","params":[],"type":"PhoneCallDiscardReason"},{"id":"-84416311","predicate":"phoneCallDiscardReasonBusy","params":[],"type":"PhoneCallDiscardReason"},{"id":"1852826908","predicate":"updateDialogPinned","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.0?true"},{"name":"folder_id","type":"flags.1?int"},{"name":"peer","type":"DialogPeer"}],"type":"Update"},{"id":"-99664734","predicate":"updatePinnedDialogs","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.1?int"},{"name":"order","type":"flags.0?Vector"}],"type":"Update"},{"id":"2104790276","predicate":"dataJSON","params":[{"name":"data","type":"string"}],"type":"DataJSON"},{"id":"-2095595325","predicate":"updateBotWebhookJSON","params":[{"name":"data","type":"DataJSON"}],"type":"Update"},{"id":"-1684914010","predicate":"updateBotWebhookJSONQuery","params":[{"name":"query_id","type":"long"},{"name":"data","type":"DataJSON"},{"name":"timeout","type":"int"}],"type":"Update"},{"id":"-886477832","predicate":"labeledPrice","params":[{"name":"label","type":"string"},{"name":"amount","type":"long"}],"type":"LabeledPrice"},{"id":"215516896","predicate":"invoice","params":[{"name":"flags","type":"#"},{"name":"test","type":"flags.0?true"},{"name":"name_requested","type":"flags.1?true"},{"name":"phone_requested","type":"flags.2?true"},{"name":"email_requested","type":"flags.3?true"},{"name":"shipping_address_requested","type":"flags.4?true"},{"name":"flexible","type":"flags.5?true"},{"name":"phone_to_provider","type":"flags.6?true"},{"name":"email_to_provider","type":"flags.7?true"},{"name":"currency","type":"string"},{"name":"prices","type":"Vector"},{"name":"max_tip_amount","type":"flags.8?long"},{"name":"suggested_tip_amounts","type":"flags.8?Vector"}],"type":"Invoice"},{"id":"-646342540","predicate":"inputMediaInvoice","params":[{"name":"flags","type":"#"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.0?InputWebDocument"},{"name":"invoice","type":"Invoice"},{"name":"payload","type":"bytes"},{"name":"provider","type":"string"},{"name":"provider_data","type":"DataJSON"},{"name":"start_param","type":"flags.1?string"}],"type":"InputMedia"},{"id":"-368917890","predicate":"paymentCharge","params":[{"name":"id","type":"string"},{"name":"provider_charge_id","type":"string"}],"type":"PaymentCharge"},{"id":"-1892568281","predicate":"messageActionPaymentSentMe","params":[{"name":"flags","type":"#"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"},{"name":"payload","type":"bytes"},{"name":"info","type":"flags.0?PaymentRequestedInfo"},{"name":"shipping_option_id","type":"flags.1?string"},{"name":"charge","type":"PaymentCharge"}],"type":"MessageAction"},{"id":"-2074799289","predicate":"messageMediaInvoice","params":[{"name":"flags","type":"#"},{"name":"shipping_address_requested","type":"flags.1?true"},{"name":"test","type":"flags.3?true"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.0?WebDocument"},{"name":"receipt_msg_id","type":"flags.2?int"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"},{"name":"start_param","type":"string"}],"type":"MessageMedia"},{"id":"512535275","predicate":"postAddress","params":[{"name":"street_line1","type":"string"},{"name":"street_line2","type":"string"},{"name":"city","type":"string"},{"name":"state","type":"string"},{"name":"country_iso2","type":"string"},{"name":"post_code","type":"string"}],"type":"PostAddress"},{"id":"-1868808300","predicate":"paymentRequestedInfo","params":[{"name":"flags","type":"#"},{"name":"name","type":"flags.0?string"},{"name":"phone","type":"flags.1?string"},{"name":"email","type":"flags.2?string"},{"name":"shipping_address","type":"flags.3?PostAddress"}],"type":"PaymentRequestedInfo"},{"id":"-1344716869","predicate":"keyboardButtonBuy","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"1080663248","predicate":"messageActionPaymentSent","params":[{"name":"currency","type":"string"},{"name":"total_amount","type":"long"}],"type":"MessageAction"},{"id":"-842892769","predicate":"paymentSavedCredentialsCard","params":[{"name":"id","type":"string"},{"name":"title","type":"string"}],"type":"PaymentSavedCredentials"},{"id":"475467473","predicate":"webDocument","params":[{"name":"url","type":"string"},{"name":"access_hash","type":"long"},{"name":"size","type":"int"},{"name":"mime_type","type":"string"},{"name":"attributes","type":"Vector"}],"type":"WebDocument"},{"id":"-1678949555","predicate":"inputWebDocument","params":[{"name":"url","type":"string"},{"name":"size","type":"int"},{"name":"mime_type","type":"string"},{"name":"attributes","type":"Vector"}],"type":"InputWebDocument"},{"id":"-1036396922","predicate":"inputWebFileLocation","params":[{"name":"url","type":"string"},{"name":"access_hash","type":"long"}],"type":"InputWebFileLocation"},{"id":"568808380","predicate":"upload.webFile","params":[{"name":"size","type":"int"},{"name":"mime_type","type":"string"},{"name":"file_type","type":"storage.FileType"},{"name":"mtime","type":"int"},{"name":"bytes","type":"bytes"}],"type":"upload.WebFile"},{"id":"378828315","predicate":"payments.paymentForm","params":[{"name":"flags","type":"#"},{"name":"can_save_credentials","type":"flags.2?true"},{"name":"password_missing","type":"flags.3?true"},{"name":"form_id","type":"long"},{"name":"bot_id","type":"long"},{"name":"invoice","type":"Invoice"},{"name":"provider_id","type":"long"},{"name":"url","type":"string"},{"name":"native_provider","type":"flags.4?string"},{"name":"native_params","type":"flags.4?DataJSON"},{"name":"saved_info","type":"flags.0?PaymentRequestedInfo"},{"name":"saved_credentials","type":"flags.1?PaymentSavedCredentials"},{"name":"users","type":"Vector"}],"type":"payments.PaymentForm"},{"id":"-784000893","predicate":"payments.validatedRequestedInfo","params":[{"name":"flags","type":"#"},{"name":"id","type":"flags.0?string"},{"name":"shipping_options","type":"flags.1?Vector"}],"type":"payments.ValidatedRequestedInfo"},{"id":"1314881805","predicate":"payments.paymentResult","params":[{"name":"updates","type":"Updates"}],"type":"payments.PaymentResult"},{"id":"1891958275","predicate":"payments.paymentReceipt","params":[{"name":"flags","type":"#"},{"name":"date","type":"int"},{"name":"bot_id","type":"long"},{"name":"provider_id","type":"long"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.2?WebDocument"},{"name":"invoice","type":"Invoice"},{"name":"info","type":"flags.0?PaymentRequestedInfo"},{"name":"shipping","type":"flags.1?ShippingOption"},{"name":"tip_amount","type":"flags.3?long"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"},{"name":"credentials_title","type":"string"},{"name":"users","type":"Vector"}],"type":"payments.PaymentReceipt"},{"id":"-74456004","predicate":"payments.savedInfo","params":[{"name":"flags","type":"#"},{"name":"has_saved_credentials","type":"flags.1?true"},{"name":"saved_info","type":"flags.0?PaymentRequestedInfo"}],"type":"payments.SavedInfo"},{"id":"-1056001329","predicate":"inputPaymentCredentialsSaved","params":[{"name":"id","type":"string"},{"name":"tmp_password","type":"bytes"}],"type":"InputPaymentCredentials"},{"id":"873977640","predicate":"inputPaymentCredentials","params":[{"name":"flags","type":"#"},{"name":"save","type":"flags.0?true"},{"name":"data","type":"DataJSON"}],"type":"InputPaymentCredentials"},{"id":"-614138572","predicate":"account.tmpPassword","params":[{"name":"tmp_password","type":"bytes"},{"name":"valid_until","type":"int"}],"type":"account.TmpPassword"},{"id":"-1239335713","predicate":"shippingOption","params":[{"name":"id","type":"string"},{"name":"title","type":"string"},{"name":"prices","type":"Vector"}],"type":"ShippingOption"},{"id":"-1246823043","predicate":"updateBotShippingQuery","params":[{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"payload","type":"bytes"},{"name":"shipping_address","type":"PostAddress"}],"type":"Update"},{"id":"-1934976362","predicate":"updateBotPrecheckoutQuery","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"payload","type":"bytes"},{"name":"info","type":"flags.0?PaymentRequestedInfo"},{"name":"shipping_option_id","type":"flags.1?string"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"}],"type":"Update"},{"id":"-6249322","predicate":"inputStickerSetItem","params":[{"name":"flags","type":"#"},{"name":"document","type":"InputDocument"},{"name":"emoji","type":"string"},{"name":"mask_coords","type":"flags.0?MaskCoords"}],"type":"InputStickerSetItem"},{"id":"-1425052898","predicate":"updatePhoneCall","params":[{"name":"phone_call","type":"PhoneCall"}],"type":"Update"},{"id":"506920429","predicate":"inputPhoneCall","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputPhoneCall"},{"id":"1399245077","predicate":"phoneCallEmpty","params":[{"name":"id","type":"long"}],"type":"PhoneCall"},{"id":"-987599081","predicate":"phoneCallWaiting","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"protocol","type":"PhoneCallProtocol"},{"name":"receive_date","type":"flags.0?int"}],"type":"PhoneCall"},{"id":"347139340","predicate":"phoneCallRequested","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_a_hash","type":"bytes"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"PhoneCall"},{"id":"912311057","predicate":"phoneCallAccepted","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_b","type":"bytes"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"PhoneCall"},{"id":"-1770029977","predicate":"phoneCall","params":[{"name":"flags","type":"#"},{"name":"p2p_allowed","type":"flags.5?true"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_a_or_b","type":"bytes"},{"name":"key_fingerprint","type":"long"},{"name":"protocol","type":"PhoneCallProtocol"},{"name":"connections","type":"Vector"},{"name":"start_date","type":"int"}],"type":"PhoneCall"},{"id":"1355435489","predicate":"phoneCallDiscarded","params":[{"name":"flags","type":"#"},{"name":"need_rating","type":"flags.2?true"},{"name":"need_debug","type":"flags.3?true"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"reason","type":"flags.0?PhoneCallDiscardReason"},{"name":"duration","type":"flags.1?int"}],"type":"PhoneCall"},{"id":"-1655957568","predicate":"phoneConnection","params":[{"name":"id","type":"long"},{"name":"ip","type":"string"},{"name":"ipv6","type":"string"},{"name":"port","type":"int"},{"name":"peer_tag","type":"bytes"}],"type":"PhoneConnection"},{"id":"-58224696","predicate":"phoneCallProtocol","params":[{"name":"flags","type":"#"},{"name":"udp_p2p","type":"flags.0?true"},{"name":"udp_reflector","type":"flags.1?true"},{"name":"min_layer","type":"int"},{"name":"max_layer","type":"int"},{"name":"library_versions","type":"Vector"}],"type":"PhoneCallProtocol"},{"id":"-326966976","predicate":"phone.phoneCall","params":[{"name":"phone_call","type":"PhoneCall"},{"name":"users","type":"Vector"}],"type":"phone.PhoneCall"},{"id":"-2134272152","predicate":"inputMessagesFilterPhoneCalls","params":[{"name":"flags","type":"#"},{"name":"missed","type":"flags.0?true"}],"type":"MessagesFilter"},{"id":"-2132731265","predicate":"messageActionPhoneCall","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.2?true"},{"name":"call_id","type":"long"},{"name":"reason","type":"flags.0?PhoneCallDiscardReason"},{"name":"duration","type":"flags.1?int"}],"type":"MessageAction"},{"id":"2054952868","predicate":"inputMessagesFilterRoundVoice","params":[],"type":"MessagesFilter"},{"id":"-1253451181","predicate":"inputMessagesFilterRoundVideo","params":[],"type":"MessagesFilter"},{"id":"-1997373508","predicate":"sendMessageRecordRoundAction","params":[],"type":"SendMessageAction"},{"id":"608050278","predicate":"sendMessageUploadRoundAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"-242427324","predicate":"upload.fileCdnRedirect","params":[{"name":"dc_id","type":"int"},{"name":"file_token","type":"bytes"},{"name":"encryption_key","type":"bytes"},{"name":"encryption_iv","type":"bytes"},{"name":"file_hashes","type":"Vector"}],"type":"upload.File"},{"id":"-290921362","predicate":"upload.cdnFileReuploadNeeded","params":[{"name":"request_token","type":"bytes"}],"type":"upload.CdnFile"},{"id":"-1449145777","predicate":"upload.cdnFile","params":[{"name":"bytes","type":"bytes"}],"type":"upload.CdnFile"},{"id":"-914167110","predicate":"cdnPublicKey","params":[{"name":"dc_id","type":"int"},{"name":"public_key","type":"string"}],"type":"CdnPublicKey"},{"id":"1462101002","predicate":"cdnConfig","params":[{"name":"public_keys","type":"Vector"}],"type":"CdnConfig"},{"id":"-283684427","predicate":"pageBlockChannel","params":[{"name":"channel","type":"Chat"}],"type":"PageBlock"},{"id":"-892239370","predicate":"langPackString","params":[{"name":"key","type":"string"},{"name":"value","type":"string"}],"type":"LangPackString"},{"id":"1816636575","predicate":"langPackStringPluralized","params":[{"name":"flags","type":"#"},{"name":"key","type":"string"},{"name":"zero_value","type":"flags.0?string"},{"name":"one_value","type":"flags.1?string"},{"name":"two_value","type":"flags.2?string"},{"name":"few_value","type":"flags.3?string"},{"name":"many_value","type":"flags.4?string"},{"name":"other_value","type":"string"}],"type":"LangPackString"},{"id":"695856818","predicate":"langPackStringDeleted","params":[{"name":"key","type":"string"}],"type":"LangPackString"},{"id":"-209337866","predicate":"langPackDifference","params":[{"name":"lang_code","type":"string"},{"name":"from_version","type":"int"},{"name":"version","type":"int"},{"name":"strings","type":"Vector"}],"type":"LangPackDifference"},{"id":"-288727837","predicate":"langPackLanguage","params":[{"name":"flags","type":"#"},{"name":"official","type":"flags.0?true"},{"name":"rtl","type":"flags.2?true"},{"name":"beta","type":"flags.3?true"},{"name":"name","type":"string"},{"name":"native_name","type":"string"},{"name":"lang_code","type":"string"},{"name":"base_lang_code","type":"flags.1?string"},{"name":"plural_code","type":"string"},{"name":"strings_count","type":"int"},{"name":"translated_count","type":"int"},{"name":"translations_url","type":"string"}],"type":"LangPackLanguage"},{"id":"1180041828","predicate":"updateLangPackTooLong","params":[{"name":"lang_code","type":"string"}],"type":"Update"},{"id":"1442983757","predicate":"updateLangPack","params":[{"name":"difference","type":"LangPackDifference"}],"type":"Update"},{"id":"885242707","predicate":"channelParticipantAdmin","params":[{"name":"flags","type":"#"},{"name":"can_edit","type":"flags.0?true"},{"name":"self","type":"flags.1?true"},{"name":"user_id","type":"long"},{"name":"inviter_id","type":"flags.1?long"},{"name":"promoted_by","type":"long"},{"name":"date","type":"int"},{"name":"admin_rights","type":"ChatAdminRights"},{"name":"rank","type":"flags.2?string"}],"type":"ChannelParticipant"},{"id":"1844969806","predicate":"channelParticipantBanned","params":[{"name":"flags","type":"#"},{"name":"left","type":"flags.0?true"},{"name":"peer","type":"Peer"},{"name":"kicked_by","type":"long"},{"name":"date","type":"int"},{"name":"banned_rights","type":"ChatBannedRights"}],"type":"ChannelParticipant"},{"id":"338142689","predicate":"channelParticipantsBanned","params":[{"name":"q","type":"string"}],"type":"ChannelParticipantsFilter"},{"id":"106343499","predicate":"channelParticipantsSearch","params":[{"name":"q","type":"string"}],"type":"ChannelParticipantsFilter"},{"id":"-421545947","predicate":"channelAdminLogEventActionChangeTitle","params":[{"name":"prev_value","type":"string"},{"name":"new_value","type":"string"}],"type":"ChannelAdminLogEventAction"},{"id":"1427671598","predicate":"channelAdminLogEventActionChangeAbout","params":[{"name":"prev_value","type":"string"},{"name":"new_value","type":"string"}],"type":"ChannelAdminLogEventAction"},{"id":"1783299128","predicate":"channelAdminLogEventActionChangeUsername","params":[{"name":"prev_value","type":"string"},{"name":"new_value","type":"string"}],"type":"ChannelAdminLogEventAction"},{"id":"1129042607","predicate":"channelAdminLogEventActionChangePhoto","params":[{"name":"prev_photo","type":"Photo"},{"name":"new_photo","type":"Photo"}],"type":"ChannelAdminLogEventAction"},{"id":"460916654","predicate":"channelAdminLogEventActionToggleInvites","params":[{"name":"new_value","type":"Bool"}],"type":"ChannelAdminLogEventAction"},{"id":"648939889","predicate":"channelAdminLogEventActionToggleSignatures","params":[{"name":"new_value","type":"Bool"}],"type":"ChannelAdminLogEventAction"},{"id":"-370660328","predicate":"channelAdminLogEventActionUpdatePinned","params":[{"name":"message","type":"Message"}],"type":"ChannelAdminLogEventAction"},{"id":"1889215493","predicate":"channelAdminLogEventActionEditMessage","params":[{"name":"prev_message","type":"Message"},{"name":"new_message","type":"Message"}],"type":"ChannelAdminLogEventAction"},{"id":"1121994683","predicate":"channelAdminLogEventActionDeleteMessage","params":[{"name":"message","type":"Message"}],"type":"ChannelAdminLogEventAction"},{"id":"405815507","predicate":"channelAdminLogEventActionParticipantJoin","params":[],"type":"ChannelAdminLogEventAction"},{"id":"-124291086","predicate":"channelAdminLogEventActionParticipantLeave","params":[],"type":"ChannelAdminLogEventAction"},{"id":"-484690728","predicate":"channelAdminLogEventActionParticipantInvite","params":[{"name":"participant","type":"ChannelParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"-422036098","predicate":"channelAdminLogEventActionParticipantToggleBan","params":[{"name":"prev_participant","type":"ChannelParticipant"},{"name":"new_participant","type":"ChannelParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"-714643696","predicate":"channelAdminLogEventActionParticipantToggleAdmin","params":[{"name":"prev_participant","type":"ChannelParticipant"},{"name":"new_participant","type":"ChannelParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"531458253","predicate":"channelAdminLogEvent","params":[{"name":"id","type":"long"},{"name":"date","type":"int"},{"name":"user_id","type":"long"},{"name":"action","type":"ChannelAdminLogEventAction"}],"type":"ChannelAdminLogEvent"},{"id":"-309659827","predicate":"channels.adminLogResults","params":[{"name":"events","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"channels.AdminLogResults"},{"id":"-368018716","predicate":"channelAdminLogEventsFilter","params":[{"name":"flags","type":"#"},{"name":"join","type":"flags.0?true"},{"name":"leave","type":"flags.1?true"},{"name":"invite","type":"flags.2?true"},{"name":"ban","type":"flags.3?true"},{"name":"unban","type":"flags.4?true"},{"name":"kick","type":"flags.5?true"},{"name":"unkick","type":"flags.6?true"},{"name":"promote","type":"flags.7?true"},{"name":"demote","type":"flags.8?true"},{"name":"info","type":"flags.9?true"},{"name":"settings","type":"flags.10?true"},{"name":"pinned","type":"flags.11?true"},{"name":"edit","type":"flags.12?true"},{"name":"delete","type":"flags.13?true"},{"name":"group_call","type":"flags.14?true"},{"name":"invites","type":"flags.15?true"},{"name":"send","type":"flags.16?true"}],"type":"ChannelAdminLogEventsFilter"},{"id":"511092620","predicate":"topPeerCategoryPhoneCalls","params":[],"type":"TopPeerCategory"},{"id":"-2143067670","predicate":"pageBlockAudio","params":[{"name":"audio_id","type":"long"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"1558266229","predicate":"popularContact","params":[{"name":"client_id","type":"long"},{"name":"importers","type":"int"}],"type":"PopularContact"},{"id":"1200788123","predicate":"messageActionScreenshotTaken","params":[],"type":"MessageAction"},{"id":"-1634752813","predicate":"messages.favedStickersNotModified","params":[],"type":"messages.FavedStickers"},{"id":"750063767","predicate":"messages.favedStickers","params":[{"name":"hash","type":"long"},{"name":"packs","type":"Vector"},{"name":"stickers","type":"Vector"}],"type":"messages.FavedStickers"},{"id":"-451831443","predicate":"updateFavedStickers","params":[],"type":"Update"},{"id":"1153291573","predicate":"updateChannelReadMessagesContents","params":[{"name":"channel_id","type":"long"},{"name":"messages","type":"Vector"}],"type":"Update"},{"id":"-1040652646","predicate":"inputMessagesFilterMyMentions","params":[],"type":"MessagesFilter"},{"id":"1887741886","predicate":"updateContactsReset","params":[],"type":"Update"},{"id":"-1312568665","predicate":"channelAdminLogEventActionChangeStickerSet","params":[{"name":"prev_stickerset","type":"InputStickerSet"},{"name":"new_stickerset","type":"InputStickerSet"}],"type":"ChannelAdminLogEventAction"},{"id":"-85549226","predicate":"messageActionCustomAction","params":[{"name":"message","type":"string"}],"type":"MessageAction"},{"id":"178373535","predicate":"inputPaymentCredentialsApplePay","params":[{"name":"payment_data","type":"DataJSON"}],"type":"InputPaymentCredentials"},{"id":"-419271411","predicate":"inputMessagesFilterGeo","params":[],"type":"MessagesFilter"},{"id":"-530392189","predicate":"inputMessagesFilterContacts","params":[],"type":"MessagesFilter"},{"id":"-1304443240","predicate":"updateChannelAvailableMessages","params":[{"name":"channel_id","type":"long"},{"name":"available_min_id","type":"int"}],"type":"Update"},{"id":"1599903217","predicate":"channelAdminLogEventActionTogglePreHistoryHidden","params":[{"name":"new_value","type":"Bool"}],"type":"ChannelAdminLogEventAction"},{"id":"-1759532989","predicate":"inputMediaGeoLive","params":[{"name":"flags","type":"#"},{"name":"stopped","type":"flags.0?true"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"heading","type":"flags.2?int"},{"name":"period","type":"flags.1?int"},{"name":"proximity_notification_radius","type":"flags.3?int"}],"type":"InputMedia"},{"id":"-1186937242","predicate":"messageMediaGeoLive","params":[{"name":"flags","type":"#"},{"name":"geo","type":"GeoPoint"},{"name":"heading","type":"flags.0?int"},{"name":"period","type":"int"},{"name":"proximity_notification_radius","type":"flags.1?int"}],"type":"MessageMedia"},{"id":"1189204285","predicate":"recentMeUrlUnknown","params":[{"name":"url","type":"string"}],"type":"RecentMeUrl"},{"id":"-1188296222","predicate":"recentMeUrlUser","params":[{"name":"url","type":"string"},{"name":"user_id","type":"long"}],"type":"RecentMeUrl"},{"id":"-1294306862","predicate":"recentMeUrlChat","params":[{"name":"url","type":"string"},{"name":"chat_id","type":"long"}],"type":"RecentMeUrl"},{"id":"-347535331","predicate":"recentMeUrlChatInvite","params":[{"name":"url","type":"string"},{"name":"chat_invite","type":"ChatInvite"}],"type":"RecentMeUrl"},{"id":"-1140172836","predicate":"recentMeUrlStickerSet","params":[{"name":"url","type":"string"},{"name":"set","type":"StickerSetCovered"}],"type":"RecentMeUrl"},{"id":"235081943","predicate":"help.recentMeUrls","params":[{"name":"urls","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"help.RecentMeUrls"},{"id":"-266911767","predicate":"channels.channelParticipantsNotModified","params":[],"type":"channels.ChannelParticipants"},{"id":"1951620897","predicate":"messages.messagesNotModified","params":[{"name":"count","type":"int"}],"type":"messages.Messages"},{"id":"482797855","predicate":"inputSingleMedia","params":[{"name":"flags","type":"#"},{"name":"media","type":"InputMedia"},{"name":"random_id","type":"long"},{"name":"message","type":"string"},{"name":"entities","type":"flags.0?Vector"}],"type":"InputSingleMedia"},{"id":"-1493633966","predicate":"webAuthorization","params":[{"name":"hash","type":"long"},{"name":"bot_id","type":"long"},{"name":"domain","type":"string"},{"name":"browser","type":"string"},{"name":"platform","type":"string"},{"name":"date_created","type":"int"},{"name":"date_active","type":"int"},{"name":"ip","type":"string"},{"name":"region","type":"string"}],"type":"WebAuthorization"},{"id":"-313079300","predicate":"account.webAuthorizations","params":[{"name":"authorizations","type":"Vector"},{"name":"users","type":"Vector"}],"type":"account.WebAuthorizations"},{"id":"-1502174430","predicate":"inputMessageID","params":[{"name":"id","type":"int"}],"type":"InputMessage"},{"id":"-1160215659","predicate":"inputMessageReplyTo","params":[{"name":"id","type":"int"}],"type":"InputMessage"},{"id":"-2037963464","predicate":"inputMessagePinned","params":[],"type":"InputMessage"},{"id":"-1687559349","predicate":"messageEntityPhone","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1280209983","predicate":"messageEntityCashtag","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-1410748418","predicate":"messageActionBotAllowed","params":[{"name":"domain","type":"string"}],"type":"MessageAction"},{"id":"-55902537","predicate":"inputDialogPeer","params":[{"name":"peer","type":"InputPeer"}],"type":"InputDialogPeer"},{"id":"-445792507","predicate":"dialogPeer","params":[{"name":"peer","type":"Peer"}],"type":"DialogPeer"},{"id":"223655517","predicate":"messages.foundStickerSetsNotModified","params":[],"type":"messages.FoundStickerSets"},{"id":"-1963942446","predicate":"messages.foundStickerSets","params":[{"name":"hash","type":"long"},{"name":"sets","type":"Vector"}],"type":"messages.FoundStickerSets"},{"id":"1648543603","predicate":"fileHash","params":[{"name":"offset","type":"int"},{"name":"limit","type":"int"},{"name":"hash","type":"bytes"}],"type":"FileHash"},{"id":"-104284986","predicate":"webDocumentNoProxy","params":[{"name":"url","type":"string"},{"name":"size","type":"int"},{"name":"mime_type","type":"string"},{"name":"attributes","type":"Vector"}],"type":"WebDocument"},{"id":"1968737087","predicate":"inputClientProxy","params":[{"name":"address","type":"string"},{"name":"port","type":"int"}],"type":"InputClientProxy"},{"id":"-483352705","predicate":"help.termsOfServiceUpdateEmpty","params":[{"name":"expires","type":"int"}],"type":"help.TermsOfServiceUpdate"},{"id":"686618977","predicate":"help.termsOfServiceUpdate","params":[{"name":"expires","type":"int"},{"name":"terms_of_service","type":"help.TermsOfService"}],"type":"help.TermsOfServiceUpdate"},{"id":"859091184","predicate":"inputSecureFileUploaded","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"md5_checksum","type":"string"},{"name":"file_hash","type":"bytes"},{"name":"secret","type":"bytes"}],"type":"InputSecureFile"},{"id":"1399317950","predicate":"inputSecureFile","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputSecureFile"},{"id":"-876089816","predicate":"inputSecureFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputFileLocation"},{"id":"1679398724","predicate":"secureFileEmpty","params":[],"type":"SecureFile"},{"id":"-534283678","predicate":"secureFile","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"size","type":"int"},{"name":"dc_id","type":"int"},{"name":"date","type":"int"},{"name":"file_hash","type":"bytes"},{"name":"secret","type":"bytes"}],"type":"SecureFile"},{"id":"-1964327229","predicate":"secureData","params":[{"name":"data","type":"bytes"},{"name":"data_hash","type":"bytes"},{"name":"secret","type":"bytes"}],"type":"SecureData"},{"id":"2103482845","predicate":"securePlainPhone","params":[{"name":"phone","type":"string"}],"type":"SecurePlainData"},{"id":"569137759","predicate":"securePlainEmail","params":[{"name":"email","type":"string"}],"type":"SecurePlainData"},{"id":"-1658158621","predicate":"secureValueTypePersonalDetails","params":[],"type":"SecureValueType"},{"id":"1034709504","predicate":"secureValueTypePassport","params":[],"type":"SecureValueType"},{"id":"115615172","predicate":"secureValueTypeDriverLicense","params":[],"type":"SecureValueType"},{"id":"-1596951477","predicate":"secureValueTypeIdentityCard","params":[],"type":"SecureValueType"},{"id":"-1717268701","predicate":"secureValueTypeInternalPassport","params":[],"type":"SecureValueType"},{"id":"-874308058","predicate":"secureValueTypeAddress","params":[],"type":"SecureValueType"},{"id":"-63531698","predicate":"secureValueTypeUtilityBill","params":[],"type":"SecureValueType"},{"id":"-1995211763","predicate":"secureValueTypeBankStatement","params":[],"type":"SecureValueType"},{"id":"-1954007928","predicate":"secureValueTypeRentalAgreement","params":[],"type":"SecureValueType"},{"id":"-1713143702","predicate":"secureValueTypePassportRegistration","params":[],"type":"SecureValueType"},{"id":"-368907213","predicate":"secureValueTypeTemporaryRegistration","params":[],"type":"SecureValueType"},{"id":"-1289704741","predicate":"secureValueTypePhone","params":[],"type":"SecureValueType"},{"id":"-1908627474","predicate":"secureValueTypeEmail","params":[],"type":"SecureValueType"},{"id":"411017418","predicate":"secureValue","params":[{"name":"flags","type":"#"},{"name":"type","type":"SecureValueType"},{"name":"data","type":"flags.0?SecureData"},{"name":"front_side","type":"flags.1?SecureFile"},{"name":"reverse_side","type":"flags.2?SecureFile"},{"name":"selfie","type":"flags.3?SecureFile"},{"name":"translation","type":"flags.6?Vector"},{"name":"files","type":"flags.4?Vector"},{"name":"plain_data","type":"flags.5?SecurePlainData"},{"name":"hash","type":"bytes"}],"type":"SecureValue"},{"id":"-618540889","predicate":"inputSecureValue","params":[{"name":"flags","type":"#"},{"name":"type","type":"SecureValueType"},{"name":"data","type":"flags.0?SecureData"},{"name":"front_side","type":"flags.1?InputSecureFile"},{"name":"reverse_side","type":"flags.2?InputSecureFile"},{"name":"selfie","type":"flags.3?InputSecureFile"},{"name":"translation","type":"flags.6?Vector"},{"name":"files","type":"flags.4?Vector"},{"name":"plain_data","type":"flags.5?SecurePlainData"}],"type":"InputSecureValue"},{"id":"-316748368","predicate":"secureValueHash","params":[{"name":"type","type":"SecureValueType"},{"name":"hash","type":"bytes"}],"type":"SecureValueHash"},{"id":"-391902247","predicate":"secureValueErrorData","params":[{"name":"type","type":"SecureValueType"},{"name":"data_hash","type":"bytes"},{"name":"field","type":"string"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"12467706","predicate":"secureValueErrorFrontSide","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"-2037765467","predicate":"secureValueErrorReverseSide","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"-449327402","predicate":"secureValueErrorSelfie","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"2054162547","predicate":"secureValueErrorFile","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"1717706985","predicate":"secureValueErrorFiles","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"Vector"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"871426631","predicate":"secureCredentialsEncrypted","params":[{"name":"data","type":"bytes"},{"name":"hash","type":"bytes"},{"name":"secret","type":"bytes"}],"type":"SecureCredentialsEncrypted"},{"id":"-1389486888","predicate":"account.authorizationForm","params":[{"name":"flags","type":"#"},{"name":"required_types","type":"Vector"},{"name":"values","type":"Vector"},{"name":"errors","type":"Vector"},{"name":"users","type":"Vector"},{"name":"privacy_policy_url","type":"flags.0?string"}],"type":"account.AuthorizationForm"},{"id":"-2128640689","predicate":"account.sentEmailCode","params":[{"name":"email_pattern","type":"string"},{"name":"length","type":"int"}],"type":"account.SentEmailCode"},{"id":"455635795","predicate":"messageActionSecureValuesSentMe","params":[{"name":"values","type":"Vector"},{"name":"credentials","type":"SecureCredentialsEncrypted"}],"type":"MessageAction"},{"id":"-648257196","predicate":"messageActionSecureValuesSent","params":[{"name":"types","type":"Vector"}],"type":"MessageAction"},{"id":"1722786150","predicate":"help.deepLinkInfoEmpty","params":[],"type":"help.DeepLinkInfo"},{"id":"1783556146","predicate":"help.deepLinkInfo","params":[{"name":"flags","type":"#"},{"name":"update_app","type":"flags.0?true"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"}],"type":"help.DeepLinkInfo"},{"id":"289586518","predicate":"savedPhoneContact","params":[{"name":"phone","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"date","type":"int"}],"type":"SavedContact"},{"id":"1304052993","predicate":"account.takeout","params":[{"name":"id","type":"long"}],"type":"account.Takeout"},{"id":"700340377","predicate":"inputTakeoutFileLocation","params":[],"type":"InputFileLocation"},{"id":"-513517117","predicate":"updateDialogUnreadMark","params":[{"name":"flags","type":"#"},{"name":"unread","type":"flags.0?true"},{"name":"peer","type":"DialogPeer"}],"type":"Update"},{"id":"-253500010","predicate":"messages.dialogsNotModified","params":[{"name":"count","type":"int"}],"type":"messages.Dialogs"},{"id":"-1625153079","predicate":"inputWebFileGeoPointLocation","params":[{"name":"geo_point","type":"InputGeoPoint"},{"name":"access_hash","type":"long"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"zoom","type":"int"},{"name":"scale","type":"int"}],"type":"InputWebFileLocation"},{"id":"-1255369827","predicate":"contacts.topPeersDisabled","params":[],"type":"contacts.TopPeers"},{"id":"-1685456582","predicate":"inputReportReasonCopyright","params":[],"type":"ReportReason"},{"id":"-732254058","predicate":"passwordKdfAlgoUnknown","params":[],"type":"PasswordKdfAlgo"},{"id":"4883767","predicate":"securePasswordKdfAlgoUnknown","params":[],"type":"SecurePasswordKdfAlgo"},{"id":"-1141711456","predicate":"securePasswordKdfAlgoPBKDF2HMACSHA512iter100000","params":[{"name":"salt","type":"bytes"}],"type":"SecurePasswordKdfAlgo"},{"id":"-2042159726","predicate":"securePasswordKdfAlgoSHA512","params":[{"name":"salt","type":"bytes"}],"type":"SecurePasswordKdfAlgo"},{"id":"354925740","predicate":"secureSecretSettings","params":[{"name":"secure_algo","type":"SecurePasswordKdfAlgo"},{"name":"secure_secret","type":"bytes"},{"name":"secure_secret_id","type":"long"}],"type":"SecureSecretSettings"},{"id":"982592842","predicate":"passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow","params":[{"name":"salt1","type":"bytes"},{"name":"salt2","type":"bytes"},{"name":"g","type":"int"},{"name":"p","type":"bytes"}],"type":"PasswordKdfAlgo"},{"id":"-1736378792","predicate":"inputCheckPasswordEmpty","params":[],"type":"InputCheckPasswordSRP"},{"id":"-763367294","predicate":"inputCheckPasswordSRP","params":[{"name":"srp_id","type":"long"},{"name":"A","type":"bytes"},{"name":"M1","type":"bytes"}],"type":"InputCheckPasswordSRP"},{"id":"-2036501105","predicate":"secureValueError","params":[{"name":"type","type":"SecureValueType"},{"name":"hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"-1592506512","predicate":"secureValueErrorTranslationFile","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"878931416","predicate":"secureValueErrorTranslationFiles","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"Vector"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"-2103600678","predicate":"secureRequiredType","params":[{"name":"flags","type":"#"},{"name":"native_names","type":"flags.0?true"},{"name":"selfie_required","type":"flags.1?true"},{"name":"translation_required","type":"flags.2?true"},{"name":"type","type":"SecureValueType"}],"type":"SecureRequiredType"},{"id":"41187252","predicate":"secureRequiredTypeOneOf","params":[{"name":"types","type":"Vector"}],"type":"SecureRequiredType"},{"id":"-1078332329","predicate":"help.passportConfigNotModified","params":[],"type":"help.PassportConfig"},{"id":"-1600596305","predicate":"help.passportConfig","params":[{"name":"hash","type":"int"},{"name":"countries_langs","type":"DataJSON"}],"type":"help.PassportConfig"},{"id":"488313413","predicate":"inputAppEvent","params":[{"name":"time","type":"double"},{"name":"type","type":"string"},{"name":"peer","type":"long"},{"name":"data","type":"JSONValue"}],"type":"InputAppEvent"},{"id":"-1059185703","predicate":"jsonObjectValue","params":[{"name":"key","type":"string"},{"name":"value","type":"JSONValue"}],"type":"JSONObjectValue"},{"id":"1064139624","predicate":"jsonNull","params":[],"type":"JSONValue"},{"id":"-952869270","predicate":"jsonBool","params":[{"name":"value","type":"Bool"}],"type":"JSONValue"},{"id":"736157604","predicate":"jsonNumber","params":[{"name":"value","type":"double"}],"type":"JSONValue"},{"id":"-1222740358","predicate":"jsonString","params":[{"name":"value","type":"string"}],"type":"JSONValue"},{"id":"-146520221","predicate":"jsonArray","params":[{"name":"value","type":"Vector"}],"type":"JSONValue"},{"id":"-1715350371","predicate":"jsonObject","params":[{"name":"value","type":"Vector"}],"type":"JSONValue"},{"id":"-1311015810","predicate":"inputNotifyBroadcasts","params":[],"type":"InputNotifyPeer"},{"id":"-703403793","predicate":"notifyBroadcasts","params":[],"type":"NotifyPeer"},{"id":"-311786236","predicate":"textSubscript","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"-939827711","predicate":"textSuperscript","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"55281185","predicate":"textMarked","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"483104362","predicate":"textPhone","params":[{"name":"text","type":"RichText"},{"name":"phone","type":"string"}],"type":"RichText"},{"id":"136105807","predicate":"textImage","params":[{"name":"document_id","type":"long"},{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"RichText"},{"id":"504660880","predicate":"pageBlockKicker","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"878078826","predicate":"pageTableCell","params":[{"name":"flags","type":"#"},{"name":"header","type":"flags.0?true"},{"name":"align_center","type":"flags.3?true"},{"name":"align_right","type":"flags.4?true"},{"name":"valign_middle","type":"flags.5?true"},{"name":"valign_bottom","type":"flags.6?true"},{"name":"text","type":"flags.7?RichText"},{"name":"colspan","type":"flags.1?int"},{"name":"rowspan","type":"flags.2?int"}],"type":"PageTableCell"},{"id":"-524237339","predicate":"pageTableRow","params":[{"name":"cells","type":"Vector"}],"type":"PageTableRow"},{"id":"-1085412734","predicate":"pageBlockTable","params":[{"name":"flags","type":"#"},{"name":"bordered","type":"flags.0?true"},{"name":"striped","type":"flags.1?true"},{"name":"title","type":"RichText"},{"name":"rows","type":"Vector"}],"type":"PageBlock"},{"id":"1869903447","predicate":"pageCaption","params":[{"name":"text","type":"RichText"},{"name":"credit","type":"RichText"}],"type":"PageCaption"},{"id":"-1188055347","predicate":"pageListItemText","params":[{"name":"text","type":"RichText"}],"type":"PageListItem"},{"id":"635466748","predicate":"pageListItemBlocks","params":[{"name":"blocks","type":"Vector"}],"type":"PageListItem"},{"id":"1577484359","predicate":"pageListOrderedItemText","params":[{"name":"num","type":"string"},{"name":"text","type":"RichText"}],"type":"PageListOrderedItem"},{"id":"-1730311882","predicate":"pageListOrderedItemBlocks","params":[{"name":"num","type":"string"},{"name":"blocks","type":"Vector"}],"type":"PageListOrderedItem"},{"id":"-1702174239","predicate":"pageBlockOrderedList","params":[{"name":"items","type":"Vector"}],"type":"PageBlock"},{"id":"1987480557","predicate":"pageBlockDetails","params":[{"name":"flags","type":"#"},{"name":"open","type":"flags.0?true"},{"name":"blocks","type":"Vector"},{"name":"title","type":"RichText"}],"type":"PageBlock"},{"id":"-1282352120","predicate":"pageRelatedArticle","params":[{"name":"flags","type":"#"},{"name":"url","type":"string"},{"name":"webpage_id","type":"long"},{"name":"title","type":"flags.0?string"},{"name":"description","type":"flags.1?string"},{"name":"photo_id","type":"flags.2?long"},{"name":"author","type":"flags.3?string"},{"name":"published_date","type":"flags.4?int"}],"type":"PageRelatedArticle"},{"id":"370236054","predicate":"pageBlockRelatedArticles","params":[{"name":"title","type":"RichText"},{"name":"articles","type":"Vector"}],"type":"PageBlock"},{"id":"-1538310410","predicate":"pageBlockMap","params":[{"name":"geo","type":"GeoPoint"},{"name":"zoom","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"-1738178803","predicate":"page","params":[{"name":"flags","type":"#"},{"name":"part","type":"flags.0?true"},{"name":"rtl","type":"flags.1?true"},{"name":"v2","type":"flags.2?true"},{"name":"url","type":"string"},{"name":"blocks","type":"Vector"},{"name":"photos","type":"Vector"},{"name":"documents","type":"Vector"},{"name":"views","type":"flags.3?int"}],"type":"Page"},{"id":"-610373422","predicate":"inputPrivacyKeyPhoneP2P","params":[],"type":"InputPrivacyKey"},{"id":"961092808","predicate":"privacyKeyPhoneP2P","params":[],"type":"PrivacyKey"},{"id":"894777186","predicate":"textAnchor","params":[{"name":"text","type":"RichText"},{"name":"name","type":"string"}],"type":"RichText"},{"id":"-1945767479","predicate":"help.supportName","params":[{"name":"name","type":"string"}],"type":"help.SupportName"},{"id":"-206688531","predicate":"help.userInfoEmpty","params":[],"type":"help.UserInfo"},{"id":"32192344","predicate":"help.userInfo","params":[{"name":"message","type":"string"},{"name":"entities","type":"Vector"},{"name":"author","type":"string"},{"name":"date","type":"int"}],"type":"help.UserInfo"},{"id":"-202219658","predicate":"messageActionContactSignUp","params":[],"type":"MessageAction"},{"id":"-1398708869","predicate":"updateMessagePoll","params":[{"name":"flags","type":"#"},{"name":"poll_id","type":"long"},{"name":"poll","type":"flags.0?Poll"},{"name":"results","type":"PollResults"}],"type":"Update"},{"id":"1823064809","predicate":"pollAnswer","params":[{"name":"text","type":"string"},{"name":"option","type":"bytes"}],"type":"PollAnswer"},{"id":"-2032041631","predicate":"poll","params":[{"name":"id","type":"long"},{"name":"flags","type":"#"},{"name":"closed","type":"flags.0?true"},{"name":"public_voters","type":"flags.1?true"},{"name":"multiple_choice","type":"flags.2?true"},{"name":"quiz","type":"flags.3?true"},{"name":"question","type":"string"},{"name":"answers","type":"Vector"},{"name":"close_period","type":"flags.4?int"},{"name":"close_date","type":"flags.5?int"}],"type":"Poll"},{"id":"997055186","predicate":"pollAnswerVoters","params":[{"name":"flags","type":"#"},{"name":"chosen","type":"flags.0?true"},{"name":"correct","type":"flags.1?true"},{"name":"option","type":"bytes"},{"name":"voters","type":"int"}],"type":"PollAnswerVoters"},{"id":"-591909213","predicate":"pollResults","params":[{"name":"flags","type":"#"},{"name":"min","type":"flags.0?true"},{"name":"results","type":"flags.1?Vector"},{"name":"total_voters","type":"flags.2?int"},{"name":"recent_voters","type":"flags.3?Vector"},{"name":"solution","type":"flags.4?string"},{"name":"solution_entities","type":"flags.4?Vector"}],"type":"PollResults"},{"id":"261416433","predicate":"inputMediaPoll","params":[{"name":"flags","type":"#"},{"name":"poll","type":"Poll"},{"name":"correct_answers","type":"flags.0?Vector"},{"name":"solution","type":"flags.1?string"},{"name":"solution_entities","type":"flags.1?Vector"}],"type":"InputMedia"},{"id":"1272375192","predicate":"messageMediaPoll","params":[{"name":"poll","type":"Poll"},{"name":"results","type":"PollResults"}],"type":"MessageMedia"},{"id":"-264117680","predicate":"chatOnlines","params":[{"name":"onlines","type":"int"}],"type":"ChatOnlines"},{"id":"1202287072","predicate":"statsURL","params":[{"name":"url","type":"string"}],"type":"StatsURL"},{"id":"-525288402","predicate":"photoStrippedSize","params":[{"name":"type","type":"string"},{"name":"bytes","type":"bytes"}],"type":"PhotoSize"},{"id":"1605510357","predicate":"chatAdminRights","params":[{"name":"flags","type":"#"},{"name":"change_info","type":"flags.0?true"},{"name":"post_messages","type":"flags.1?true"},{"name":"edit_messages","type":"flags.2?true"},{"name":"delete_messages","type":"flags.3?true"},{"name":"ban_users","type":"flags.4?true"},{"name":"invite_users","type":"flags.5?true"},{"name":"pin_messages","type":"flags.7?true"},{"name":"add_admins","type":"flags.9?true"},{"name":"anonymous","type":"flags.10?true"},{"name":"manage_call","type":"flags.11?true"},{"name":"other","type":"flags.12?true"}],"type":"ChatAdminRights"},{"id":"-1626209256","predicate":"chatBannedRights","params":[{"name":"flags","type":"#"},{"name":"view_messages","type":"flags.0?true"},{"name":"send_messages","type":"flags.1?true"},{"name":"send_media","type":"flags.2?true"},{"name":"send_stickers","type":"flags.3?true"},{"name":"send_gifs","type":"flags.4?true"},{"name":"send_games","type":"flags.5?true"},{"name":"send_inline","type":"flags.6?true"},{"name":"embed_links","type":"flags.7?true"},{"name":"send_polls","type":"flags.8?true"},{"name":"change_info","type":"flags.10?true"},{"name":"invite_users","type":"flags.15?true"},{"name":"pin_messages","type":"flags.17?true"},{"name":"until_date","type":"int"}],"type":"ChatBannedRights"},{"id":"1421875280","predicate":"updateChatDefaultBannedRights","params":[{"name":"peer","type":"Peer"},{"name":"default_banned_rights","type":"ChatBannedRights"},{"name":"version","type":"int"}],"type":"Update"},{"id":"-433014407","predicate":"inputWallPaper","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputWallPaper"},{"id":"1913199744","predicate":"inputWallPaperSlug","params":[{"name":"slug","type":"string"}],"type":"InputWallPaper"},{"id":"-1150621555","predicate":"channelParticipantsContacts","params":[{"name":"q","type":"string"}],"type":"ChannelParticipantsFilter"},{"id":"771095562","predicate":"channelAdminLogEventActionDefaultBannedRights","params":[{"name":"prev_banned_rights","type":"ChatBannedRights"},{"name":"new_banned_rights","type":"ChatBannedRights"}],"type":"ChannelAdminLogEventAction"},{"id":"-1895328189","predicate":"channelAdminLogEventActionStopPoll","params":[{"name":"message","type":"Message"}],"type":"ChannelAdminLogEventAction"},{"id":"471437699","predicate":"account.wallPapersNotModified","params":[],"type":"account.WallPapers"},{"id":"-842824308","predicate":"account.wallPapers","params":[{"name":"hash","type":"long"},{"name":"wallpapers","type":"Vector"}],"type":"account.WallPapers"},{"id":"-557924733","predicate":"codeSettings","params":[{"name":"flags","type":"#"},{"name":"allow_flashcall","type":"flags.0?true"},{"name":"current_number","type":"flags.1?true"},{"name":"allow_app_hash","type":"flags.4?true"}],"type":"CodeSettings"},{"id":"499236004","predicate":"wallPaperSettings","params":[{"name":"flags","type":"#"},{"name":"blur","type":"flags.1?true"},{"name":"motion","type":"flags.2?true"},{"name":"background_color","type":"flags.0?int"},{"name":"second_background_color","type":"flags.4?int"},{"name":"third_background_color","type":"flags.5?int"},{"name":"fourth_background_color","type":"flags.6?int"},{"name":"intensity","type":"flags.3?int"},{"name":"rotation","type":"flags.4?int"}],"type":"WallPaperSettings"},{"id":"-532532493","predicate":"autoDownloadSettings","params":[{"name":"flags","type":"#"},{"name":"disabled","type":"flags.0?true"},{"name":"video_preload_large","type":"flags.1?true"},{"name":"audio_preload_next","type":"flags.2?true"},{"name":"phonecalls_less_data","type":"flags.3?true"},{"name":"photo_size_max","type":"int"},{"name":"video_size_max","type":"int"},{"name":"file_size_max","type":"int"},{"name":"video_upload_maxbitrate","type":"int"}],"type":"AutoDownloadSettings"},{"id":"1674235686","predicate":"account.autoDownloadSettings","params":[{"name":"low","type":"AutoDownloadSettings"},{"name":"medium","type":"AutoDownloadSettings"},{"name":"high","type":"AutoDownloadSettings"}],"type":"account.AutoDownloadSettings"},{"id":"-709641735","predicate":"emojiKeyword","params":[{"name":"keyword","type":"string"},{"name":"emoticons","type":"Vector"}],"type":"EmojiKeyword"},{"id":"594408994","predicate":"emojiKeywordDeleted","params":[{"name":"keyword","type":"string"},{"name":"emoticons","type":"Vector"}],"type":"EmojiKeyword"},{"id":"1556570557","predicate":"emojiKeywordsDifference","params":[{"name":"lang_code","type":"string"},{"name":"from_version","type":"int"},{"name":"version","type":"int"},{"name":"keywords","type":"Vector"}],"type":"EmojiKeywordsDifference"},{"id":"-1519029347","predicate":"emojiURL","params":[{"name":"url","type":"string"}],"type":"EmojiURL"},{"id":"-1275374751","predicate":"emojiLanguage","params":[{"name":"lang_code","type":"string"}],"type":"EmojiLanguage"},{"id":"-1529000952","predicate":"inputPrivacyKeyForwards","params":[],"type":"InputPrivacyKey"},{"id":"1777096355","predicate":"privacyKeyForwards","params":[],"type":"PrivacyKey"},{"id":"1461304012","predicate":"inputPrivacyKeyProfilePhoto","params":[],"type":"InputPrivacyKey"},{"id":"-1777000467","predicate":"privacyKeyProfilePhoto","params":[],"type":"PrivacyKey"},{"id":"1075322878","predicate":"inputPhotoFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"thumb_size","type":"string"}],"type":"InputFileLocation"},{"id":"-667654413","predicate":"inputPhotoLegacyFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"volume_id","type":"long"},{"name":"local_id","type":"int"},{"name":"secret","type":"long"}],"type":"InputFileLocation"},{"id":"925204121","predicate":"inputPeerPhotoFileLocation","params":[{"name":"flags","type":"#"},{"name":"big","type":"flags.0?true"},{"name":"peer","type":"InputPeer"},{"name":"photo_id","type":"long"}],"type":"InputFileLocation"},{"id":"-1652231205","predicate":"inputStickerSetThumb","params":[{"name":"stickerset","type":"InputStickerSet"},{"name":"thumb_version","type":"int"}],"type":"InputFileLocation"},{"id":"-11252123","predicate":"folder","params":[{"name":"flags","type":"#"},{"name":"autofill_new_broadcasts","type":"flags.0?true"},{"name":"autofill_public_groups","type":"flags.1?true"},{"name":"autofill_new_correspondents","type":"flags.2?true"},{"name":"id","type":"int"},{"name":"title","type":"string"},{"name":"photo","type":"flags.3?ChatPhoto"}],"type":"Folder"},{"id":"1908216652","predicate":"dialogFolder","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.2?true"},{"name":"folder","type":"Folder"},{"name":"peer","type":"Peer"},{"name":"top_message","type":"int"},{"name":"unread_muted_peers_count","type":"int"},{"name":"unread_unmuted_peers_count","type":"int"},{"name":"unread_muted_messages_count","type":"int"},{"name":"unread_unmuted_messages_count","type":"int"}],"type":"Dialog"},{"id":"1684014375","predicate":"inputDialogPeerFolder","params":[{"name":"folder_id","type":"int"}],"type":"InputDialogPeer"},{"id":"1363483106","predicate":"dialogPeerFolder","params":[{"name":"folder_id","type":"int"}],"type":"DialogPeer"},{"id":"-70073706","predicate":"inputFolderPeer","params":[{"name":"peer","type":"InputPeer"},{"name":"folder_id","type":"int"}],"type":"InputFolderPeer"},{"id":"-373643672","predicate":"folderPeer","params":[{"name":"peer","type":"Peer"},{"name":"folder_id","type":"int"}],"type":"FolderPeer"},{"id":"422972864","predicate":"updateFolderPeers","params":[{"name":"folder_peers","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"497305826","predicate":"inputUserFromMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"user_id","type":"long"}],"type":"InputUser"},{"id":"1536380829","predicate":"inputChannelFromMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"channel_id","type":"long"}],"type":"InputChannel"},{"id":"-1468331492","predicate":"inputPeerUserFromMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"user_id","type":"long"}],"type":"InputPeer"},{"id":"-1121318848","predicate":"inputPeerChannelFromMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"channel_id","type":"long"}],"type":"InputPeer"},{"id":"55761658","predicate":"inputPrivacyKeyPhoneNumber","params":[],"type":"InputPrivacyKey"},{"id":"-778378131","predicate":"privacyKeyPhoneNumber","params":[],"type":"PrivacyKey"},{"id":"-1472172887","predicate":"topPeerCategoryForwardUsers","params":[],"type":"TopPeerCategory"},{"id":"-68239120","predicate":"topPeerCategoryForwardChats","params":[],"type":"TopPeerCategory"},{"id":"84703944","predicate":"channelAdminLogEventActionChangeLinkedChat","params":[{"name":"prev_value","type":"long"},{"name":"new_value","type":"long"}],"type":"ChannelAdminLogEventAction"},{"id":"-398136321","predicate":"messages.searchCounter","params":[{"name":"flags","type":"#"},{"name":"inexact","type":"flags.1?true"},{"name":"filter","type":"MessagesFilter"},{"name":"count","type":"int"}],"type":"messages.SearchCounter"},{"id":"280464681","predicate":"keyboardButtonUrlAuth","params":[{"name":"flags","type":"#"},{"name":"text","type":"string"},{"name":"fwd_text","type":"flags.0?string"},{"name":"url","type":"string"},{"name":"button_id","type":"int"}],"type":"KeyboardButton"},{"id":"-802258988","predicate":"inputKeyboardButtonUrlAuth","params":[{"name":"flags","type":"#"},{"name":"request_write_access","type":"flags.0?true"},{"name":"text","type":"string"},{"name":"fwd_text","type":"flags.1?string"},{"name":"url","type":"string"},{"name":"bot","type":"InputUser"}],"type":"KeyboardButton"},{"id":"-1831650802","predicate":"urlAuthResultRequest","params":[{"name":"flags","type":"#"},{"name":"request_write_access","type":"flags.0?true"},{"name":"bot","type":"User"},{"name":"domain","type":"string"}],"type":"UrlAuthResult"},{"id":"-1886646706","predicate":"urlAuthResultAccepted","params":[{"name":"url","type":"string"}],"type":"UrlAuthResult"},{"id":"-1445536993","predicate":"urlAuthResultDefault","params":[],"type":"UrlAuthResult"},{"id":"-2079962673","predicate":"inputPrivacyValueAllowChatParticipants","params":[{"name":"chats","type":"Vector"}],"type":"InputPrivacyRule"},{"id":"-380694650","predicate":"inputPrivacyValueDisallowChatParticipants","params":[{"name":"chats","type":"Vector"}],"type":"InputPrivacyRule"},{"id":"1796427406","predicate":"privacyValueAllowChatParticipants","params":[{"name":"chats","type":"Vector"}],"type":"PrivacyRule"},{"id":"1103656293","predicate":"privacyValueDisallowChatParticipants","params":[{"name":"chats","type":"Vector"}],"type":"PrivacyRule"},{"id":"-1672577397","predicate":"messageEntityUnderline","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-1090087980","predicate":"messageEntityStrike","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"34469328","predicate":"messageEntityBlockquote","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1786671974","predicate":"updatePeerSettings","params":[{"name":"peer","type":"Peer"},{"name":"settings","type":"PeerSettings"}],"type":"Update"},{"id":"-1078612597","predicate":"channelLocationEmpty","params":[],"type":"ChannelLocation"},{"id":"547062491","predicate":"channelLocation","params":[{"name":"geo_point","type":"GeoPoint"},{"name":"address","type":"string"}],"type":"ChannelLocation"},{"id":"-901375139","predicate":"peerLocated","params":[{"name":"peer","type":"Peer"},{"name":"expires","type":"int"},{"name":"distance","type":"int"}],"type":"PeerLocated"},{"id":"-1263546448","predicate":"updatePeerLocated","params":[{"name":"peers","type":"Vector"}],"type":"Update"},{"id":"241923758","predicate":"channelAdminLogEventActionChangeLocation","params":[{"name":"prev_value","type":"ChannelLocation"},{"name":"new_value","type":"ChannelLocation"}],"type":"ChannelAdminLogEventAction"},{"id":"-606798099","predicate":"inputReportReasonGeoIrrelevant","params":[],"type":"ReportReason"},{"id":"1401984889","predicate":"channelAdminLogEventActionToggleSlowMode","params":[{"name":"prev_value","type":"int"},{"name":"new_value","type":"int"}],"type":"ChannelAdminLogEventAction"},{"id":"1148485274","predicate":"auth.authorizationSignUpRequired","params":[{"name":"flags","type":"#"},{"name":"terms_of_service","type":"flags.0?help.TermsOfService"}],"type":"auth.Authorization"},{"id":"-666824391","predicate":"payments.paymentVerificationNeeded","params":[{"name":"url","type":"string"}],"type":"payments.PaymentResult"},{"id":"42402760","predicate":"inputStickerSetAnimatedEmoji","params":[],"type":"InputStickerSet"},{"id":"967122427","predicate":"updateNewScheduledMessage","params":[{"name":"message","type":"Message"}],"type":"Update"},{"id":"-1870238482","predicate":"updateDeleteScheduledMessages","params":[{"name":"peer","type":"Peer"},{"name":"messages","type":"Vector"}],"type":"Update"},{"id":"-797791052","predicate":"restrictionReason","params":[{"name":"platform","type":"string"},{"name":"reason","type":"string"},{"name":"text","type":"string"}],"type":"RestrictionReason"},{"id":"1012306921","predicate":"inputTheme","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputTheme"},{"id":"-175567375","predicate":"inputThemeSlug","params":[{"name":"slug","type":"string"}],"type":"InputTheme"},{"id":"-402474788","predicate":"theme","params":[{"name":"flags","type":"#"},{"name":"creator","type":"flags.0?true"},{"name":"default","type":"flags.1?true"},{"name":"for_chat","type":"flags.5?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"slug","type":"string"},{"name":"title","type":"string"},{"name":"document","type":"flags.2?Document"},{"name":"settings","type":"flags.3?ThemeSettings"},{"name":"installs_count","type":"flags.4?int"}],"type":"Theme"},{"id":"-199313886","predicate":"account.themesNotModified","params":[],"type":"account.Themes"},{"id":"-1707242387","predicate":"account.themes","params":[{"name":"hash","type":"long"},{"name":"themes","type":"Vector"}],"type":"account.Themes"},{"id":"-2112423005","predicate":"updateTheme","params":[{"name":"theme","type":"Theme"}],"type":"Update"},{"id":"-786326563","predicate":"inputPrivacyKeyAddedByPhone","params":[],"type":"InputPrivacyKey"},{"id":"1124062251","predicate":"privacyKeyAddedByPhone","params":[],"type":"PrivacyKey"},{"id":"-2027964103","predicate":"updateGeoLiveViewed","params":[{"name":"peer","type":"Peer"},{"name":"msg_id","type":"int"}],"type":"Update"},{"id":"1448076945","predicate":"updateLoginToken","params":[],"type":"Update"},{"id":"1654593920","predicate":"auth.loginToken","params":[{"name":"expires","type":"int"},{"name":"token","type":"bytes"}],"type":"auth.LoginToken"},{"id":"110008598","predicate":"auth.loginTokenMigrateTo","params":[{"name":"dc_id","type":"int"},{"name":"token","type":"bytes"}],"type":"auth.LoginToken"},{"id":"957176926","predicate":"auth.loginTokenSuccess","params":[{"name":"authorization","type":"auth.Authorization"}],"type":"auth.LoginToken"},{"id":"1474462241","predicate":"account.contentSettings","params":[{"name":"flags","type":"#"},{"name":"sensitive_enabled","type":"flags.0?true"},{"name":"sensitive_can_change","type":"flags.1?true"}],"type":"account.ContentSettings"},{"id":"-1456996667","predicate":"messages.inactiveChats","params":[{"name":"dates","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.InactiveChats"},{"id":"-1012849566","predicate":"baseThemeClassic","params":[],"type":"BaseTheme"},{"id":"-69724536","predicate":"baseThemeDay","params":[],"type":"BaseTheme"},{"id":"-1212997976","predicate":"baseThemeNight","params":[],"type":"BaseTheme"},{"id":"1834973166","predicate":"baseThemeTinted","params":[],"type":"BaseTheme"},{"id":"1527845466","predicate":"baseThemeArctic","params":[],"type":"BaseTheme"},{"id":"-1770371538","predicate":"inputWallPaperNoFile","params":[{"name":"id","type":"long"}],"type":"InputWallPaper"},{"id":"-528465642","predicate":"wallPaperNoFile","params":[{"name":"id","type":"long"},{"name":"flags","type":"#"},{"name":"default","type":"flags.1?true"},{"name":"dark","type":"flags.4?true"},{"name":"settings","type":"flags.2?WallPaperSettings"}],"type":"WallPaper"},{"id":"-1881255857","predicate":"inputThemeSettings","params":[{"name":"flags","type":"#"},{"name":"message_colors_animated","type":"flags.2?true"},{"name":"base_theme","type":"BaseTheme"},{"name":"accent_color","type":"int"},{"name":"outbox_accent_color","type":"flags.3?int"},{"name":"message_colors","type":"flags.0?Vector"},{"name":"wallpaper","type":"flags.1?InputWallPaper"},{"name":"wallpaper_settings","type":"flags.1?WallPaperSettings"}],"type":"InputThemeSettings"},{"id":"-94849324","predicate":"themeSettings","params":[{"name":"flags","type":"#"},{"name":"message_colors_animated","type":"flags.2?true"},{"name":"base_theme","type":"BaseTheme"},{"name":"accent_color","type":"int"},{"name":"outbox_accent_color","type":"flags.3?int"},{"name":"message_colors","type":"flags.0?Vector"},{"name":"wallpaper","type":"flags.1?WallPaper"}],"type":"ThemeSettings"},{"id":"1421174295","predicate":"webPageAttributeTheme","params":[{"name":"flags","type":"#"},{"name":"documents","type":"flags.0?Vector"},{"name":"settings","type":"flags.1?ThemeSettings"}],"type":"WebPageAttribute"},{"id":"274961865","predicate":"updateMessagePollVote","params":[{"name":"poll_id","type":"long"},{"name":"user_id","type":"long"},{"name":"options","type":"Vector"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"886196148","predicate":"messageUserVote","params":[{"name":"user_id","type":"long"},{"name":"option","type":"bytes"},{"name":"date","type":"int"}],"type":"MessageUserVote"},{"id":"1017491692","predicate":"messageUserVoteInputOption","params":[{"name":"user_id","type":"long"},{"name":"date","type":"int"}],"type":"MessageUserVote"},{"id":"-1973033641","predicate":"messageUserVoteMultiple","params":[{"name":"user_id","type":"long"},{"name":"options","type":"Vector"},{"name":"date","type":"int"}],"type":"MessageUserVote"},{"id":"136574537","predicate":"messages.votesList","params":[{"name":"flags","type":"#"},{"name":"count","type":"int"},{"name":"votes","type":"Vector"},{"name":"users","type":"Vector"},{"name":"next_offset","type":"flags.0?string"}],"type":"messages.VotesList"},{"id":"-1144565411","predicate":"keyboardButtonRequestPoll","params":[{"name":"flags","type":"#"},{"name":"quiz","type":"flags.0?Bool"},{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"1981704948","predicate":"messageEntityBankCard","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-177732982","predicate":"bankCardOpenUrl","params":[{"name":"url","type":"string"},{"name":"name","type":"string"}],"type":"BankCardOpenUrl"},{"id":"1042605427","predicate":"payments.bankCardData","params":[{"name":"title","type":"string"},{"name":"open_urls","type":"Vector"}],"type":"payments.BankCardData"},{"id":"-118740917","predicate":"peerSelfLocated","params":[{"name":"expires","type":"int"}],"type":"PeerLocated"},{"id":"1949890536","predicate":"dialogFilter","params":[{"name":"flags","type":"#"},{"name":"contacts","type":"flags.0?true"},{"name":"non_contacts","type":"flags.1?true"},{"name":"groups","type":"flags.2?true"},{"name":"broadcasts","type":"flags.3?true"},{"name":"bots","type":"flags.4?true"},{"name":"exclude_muted","type":"flags.11?true"},{"name":"exclude_read","type":"flags.12?true"},{"name":"exclude_archived","type":"flags.13?true"},{"name":"id","type":"int"},{"name":"title","type":"string"},{"name":"emoticon","type":"flags.25?string"},{"name":"pinned_peers","type":"Vector"},{"name":"include_peers","type":"Vector"},{"name":"exclude_peers","type":"Vector"}],"type":"DialogFilter"},{"id":"2004110666","predicate":"dialogFilterSuggested","params":[{"name":"filter","type":"DialogFilter"},{"name":"description","type":"string"}],"type":"DialogFilterSuggested"},{"id":"654302845","predicate":"updateDialogFilter","params":[{"name":"flags","type":"#"},{"name":"id","type":"int"},{"name":"filter","type":"flags.0?DialogFilter"}],"type":"Update"},{"id":"-1512627963","predicate":"updateDialogFilterOrder","params":[{"name":"order","type":"Vector"}],"type":"Update"},{"id":"889491791","predicate":"updateDialogFilters","params":[],"type":"Update"},{"id":"-1237848657","predicate":"statsDateRangeDays","params":[{"name":"min_date","type":"int"},{"name":"max_date","type":"int"}],"type":"StatsDateRangeDays"},{"id":"-884757282","predicate":"statsAbsValueAndPrev","params":[{"name":"current","type":"double"},{"name":"previous","type":"double"}],"type":"StatsAbsValueAndPrev"},{"id":"-875679776","predicate":"statsPercentValue","params":[{"name":"part","type":"double"},{"name":"total","type":"double"}],"type":"StatsPercentValue"},{"id":"1244130093","predicate":"statsGraphAsync","params":[{"name":"token","type":"string"}],"type":"StatsGraph"},{"id":"-1092839390","predicate":"statsGraphError","params":[{"name":"error","type":"string"}],"type":"StatsGraph"},{"id":"-1901828938","predicate":"statsGraph","params":[{"name":"flags","type":"#"},{"name":"json","type":"DataJSON"},{"name":"zoom_token","type":"flags.0?string"}],"type":"StatsGraph"},{"id":"-1387279939","predicate":"messageInteractionCounters","params":[{"name":"msg_id","type":"int"},{"name":"views","type":"int"},{"name":"forwards","type":"int"}],"type":"MessageInteractionCounters"},{"id":"-1107852396","predicate":"stats.broadcastStats","params":[{"name":"period","type":"StatsDateRangeDays"},{"name":"followers","type":"StatsAbsValueAndPrev"},{"name":"views_per_post","type":"StatsAbsValueAndPrev"},{"name":"shares_per_post","type":"StatsAbsValueAndPrev"},{"name":"enabled_notifications","type":"StatsPercentValue"},{"name":"growth_graph","type":"StatsGraph"},{"name":"followers_graph","type":"StatsGraph"},{"name":"mute_graph","type":"StatsGraph"},{"name":"top_hours_graph","type":"StatsGraph"},{"name":"interactions_graph","type":"StatsGraph"},{"name":"iv_interactions_graph","type":"StatsGraph"},{"name":"views_by_source_graph","type":"StatsGraph"},{"name":"new_followers_by_source_graph","type":"StatsGraph"},{"name":"languages_graph","type":"StatsGraph"},{"name":"recent_message_interactions","type":"Vector"}],"type":"stats.BroadcastStats"},{"id":"-428884101","predicate":"inputMediaDice","params":[{"name":"emoticon","type":"string"}],"type":"InputMedia"},{"id":"1065280907","predicate":"messageMediaDice","params":[{"name":"value","type":"int"},{"name":"emoticon","type":"string"}],"type":"MessageMedia"},{"id":"-427863538","predicate":"inputStickerSetDice","params":[{"name":"emoticon","type":"string"}],"type":"InputStickerSet"},{"id":"-1728664459","predicate":"help.promoDataEmpty","params":[{"name":"expires","type":"int"}],"type":"help.PromoData"},{"id":"-1942390465","predicate":"help.promoData","params":[{"name":"flags","type":"#"},{"name":"proxy","type":"flags.0?true"},{"name":"expires","type":"int"},{"name":"peer","type":"Peer"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"psa_type","type":"flags.1?string"},{"name":"psa_message","type":"flags.2?string"}],"type":"help.PromoData"},{"id":"-567037804","predicate":"videoSize","params":[{"name":"flags","type":"#"},{"name":"type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"video_start_ts","type":"flags.0?double"}],"type":"VideoSize"},{"id":"643940105","predicate":"updatePhoneCallSignalingData","params":[{"name":"phone_call_id","type":"long"},{"name":"data","type":"bytes"}],"type":"Update"},{"id":"1634294960","predicate":"chatInvitePeek","params":[{"name":"chat","type":"Chat"},{"name":"expires","type":"int"}],"type":"ChatInvite"},{"id":"-1660637285","predicate":"statsGroupTopPoster","params":[{"name":"user_id","type":"long"},{"name":"messages","type":"int"},{"name":"avg_chars","type":"int"}],"type":"StatsGroupTopPoster"},{"id":"-682079097","predicate":"statsGroupTopAdmin","params":[{"name":"user_id","type":"long"},{"name":"deleted","type":"int"},{"name":"kicked","type":"int"},{"name":"banned","type":"int"}],"type":"StatsGroupTopAdmin"},{"id":"1398765469","predicate":"statsGroupTopInviter","params":[{"name":"user_id","type":"long"},{"name":"invitations","type":"int"}],"type":"StatsGroupTopInviter"},{"id":"-276825834","predicate":"stats.megagroupStats","params":[{"name":"period","type":"StatsDateRangeDays"},{"name":"members","type":"StatsAbsValueAndPrev"},{"name":"messages","type":"StatsAbsValueAndPrev"},{"name":"viewers","type":"StatsAbsValueAndPrev"},{"name":"posters","type":"StatsAbsValueAndPrev"},{"name":"growth_graph","type":"StatsGraph"},{"name":"members_graph","type":"StatsGraph"},{"name":"new_members_by_source_graph","type":"StatsGraph"},{"name":"languages_graph","type":"StatsGraph"},{"name":"messages_graph","type":"StatsGraph"},{"name":"actions_graph","type":"StatsGraph"},{"name":"top_hours_graph","type":"StatsGraph"},{"name":"weekdays_graph","type":"StatsGraph"},{"name":"top_posters","type":"Vector"},{"name":"top_admins","type":"Vector"},{"name":"top_inviters","type":"Vector"},{"name":"users","type":"Vector"}],"type":"stats.MegagroupStats"},{"id":"-1096616924","predicate":"globalPrivacySettings","params":[{"name":"flags","type":"#"},{"name":"archive_and_mute_new_noncontact_peers","type":"flags.0?Bool"}],"type":"GlobalPrivacySettings"},{"id":"1667228533","predicate":"phoneConnectionWebrtc","params":[{"name":"flags","type":"#"},{"name":"turn","type":"flags.0?true"},{"name":"stun","type":"flags.1?true"},{"name":"id","type":"long"},{"name":"ip","type":"string"},{"name":"ipv6","type":"string"},{"name":"port","type":"int"},{"name":"username","type":"string"},{"name":"password","type":"string"}],"type":"PhoneConnection"},{"id":"1107543535","predicate":"help.countryCode","params":[{"name":"flags","type":"#"},{"name":"country_code","type":"string"},{"name":"prefixes","type":"flags.0?Vector"},{"name":"patterns","type":"flags.1?Vector"}],"type":"help.CountryCode"},{"id":"-1014526429","predicate":"help.country","params":[{"name":"flags","type":"#"},{"name":"hidden","type":"flags.0?true"},{"name":"iso2","type":"string"},{"name":"default_name","type":"string"},{"name":"name","type":"flags.1?string"},{"name":"country_codes","type":"Vector"}],"type":"help.Country"},{"id":"-1815339214","predicate":"help.countriesListNotModified","params":[],"type":"help.CountriesList"},{"id":"-2016381538","predicate":"help.countriesList","params":[{"name":"countries","type":"Vector"},{"name":"hash","type":"int"}],"type":"help.CountriesList"},{"id":"1163625789","predicate":"messageViews","params":[{"name":"flags","type":"#"},{"name":"views","type":"flags.0?int"},{"name":"forwards","type":"flags.1?int"},{"name":"replies","type":"flags.2?MessageReplies"}],"type":"MessageViews"},{"id":"-761649164","predicate":"updateChannelMessageForwards","params":[{"name":"channel_id","type":"long"},{"name":"id","type":"int"},{"name":"forwards","type":"int"}],"type":"Update"},{"id":"-96535659","predicate":"photoSizeProgressive","params":[{"name":"type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"sizes","type":"Vector"}],"type":"PhotoSize"},{"id":"-1228606141","predicate":"messages.messageViews","params":[{"name":"views","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.MessageViews"},{"id":"-693004986","predicate":"updateReadChannelDiscussionInbox","params":[{"name":"flags","type":"#"},{"name":"channel_id","type":"long"},{"name":"top_msg_id","type":"int"},{"name":"read_max_id","type":"int"},{"name":"broadcast_id","type":"flags.0?long"},{"name":"broadcast_post","type":"flags.0?int"}],"type":"Update"},{"id":"1767677564","predicate":"updateReadChannelDiscussionOutbox","params":[{"name":"channel_id","type":"long"},{"name":"top_msg_id","type":"int"},{"name":"read_max_id","type":"int"}],"type":"Update"},{"id":"-1506535550","predicate":"messages.discussionMessage","params":[{"name":"flags","type":"#"},{"name":"messages","type":"Vector"},{"name":"max_id","type":"flags.0?int"},{"name":"read_inbox_max_id","type":"flags.1?int"},{"name":"read_outbox_max_id","type":"flags.2?int"},{"name":"unread_count","type":"int"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.DiscussionMessage"},{"id":"-1495959709","predicate":"messageReplyHeader","params":[{"name":"flags","type":"#"},{"name":"reply_to_msg_id","type":"int"},{"name":"reply_to_peer_id","type":"flags.0?Peer"},{"name":"reply_to_top_id","type":"flags.1?int"}],"type":"MessageReplyHeader"},{"id":"-2083123262","predicate":"messageReplies","params":[{"name":"flags","type":"#"},{"name":"comments","type":"flags.0?true"},{"name":"replies","type":"int"},{"name":"replies_pts","type":"int"},{"name":"recent_repliers","type":"flags.1?Vector"},{"name":"channel_id","type":"flags.0?long"},{"name":"max_id","type":"flags.2?int"},{"name":"read_max_id","type":"flags.3?int"}],"type":"MessageReplies"},{"id":"610945826","predicate":"updatePeerBlocked","params":[{"name":"peer_id","type":"Peer"},{"name":"blocked","type":"Bool"}],"type":"Update"},{"id":"-386039788","predicate":"peerBlocked","params":[{"name":"peer_id","type":"Peer"},{"name":"date","type":"int"}],"type":"PeerBlocked"},{"id":"-1937192669","predicate":"updateChannelUserTyping","params":[{"name":"flags","type":"#"},{"name":"channel_id","type":"long"},{"name":"top_msg_id","type":"flags.0?int"},{"name":"from_id","type":"Peer"},{"name":"action","type":"SendMessageAction"}],"type":"Update"},{"id":"-1392895362","predicate":"inputMessageCallbackQuery","params":[{"name":"id","type":"int"},{"name":"query_id","type":"long"}],"type":"InputMessage"},{"id":"453242886","predicate":"channelParticipantLeft","params":[{"name":"peer","type":"Peer"}],"type":"ChannelParticipant"},{"id":"-531931925","predicate":"channelParticipantsMentions","params":[{"name":"flags","type":"#"},{"name":"q","type":"flags.0?string"},{"name":"top_msg_id","type":"flags.1?int"}],"type":"ChannelParticipantsFilter"},{"id":"-309990731","predicate":"updatePinnedMessages","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.0?true"},{"name":"peer","type":"Peer"},{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"1538885128","predicate":"updatePinnedChannelMessages","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.0?true"},{"name":"channel_id","type":"long"},{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"464520273","predicate":"inputMessagesFilterPinned","params":[],"type":"MessagesFilter"},{"id":"-1986399595","predicate":"stats.messageStats","params":[{"name":"views_graph","type":"StatsGraph"}],"type":"stats.MessageStats"},{"id":"-1730095465","predicate":"messageActionGeoProximityReached","params":[{"name":"from_id","type":"Peer"},{"name":"to_id","type":"Peer"},{"name":"distance","type":"int"}],"type":"MessageAction"},{"id":"-668906175","predicate":"photoPathSize","params":[{"name":"type","type":"string"},{"name":"bytes","type":"bytes"}],"type":"PhotoSize"},{"id":"-651419003","predicate":"speakingInGroupCallAction","params":[],"type":"SendMessageAction"},{"id":"2004925620","predicate":"groupCallDiscarded","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"duration","type":"int"}],"type":"GroupCall"},{"id":"-711498484","predicate":"groupCall","params":[{"name":"flags","type":"#"},{"name":"join_muted","type":"flags.1?true"},{"name":"can_change_join_muted","type":"flags.2?true"},{"name":"join_date_asc","type":"flags.6?true"},{"name":"schedule_start_subscribed","type":"flags.8?true"},{"name":"can_start_video","type":"flags.9?true"},{"name":"record_video_active","type":"flags.11?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"participants_count","type":"int"},{"name":"title","type":"flags.3?string"},{"name":"stream_dc_id","type":"flags.4?int"},{"name":"record_start_date","type":"flags.5?int"},{"name":"schedule_date","type":"flags.7?int"},{"name":"unmuted_video_count","type":"flags.10?int"},{"name":"unmuted_video_limit","type":"int"},{"name":"version","type":"int"}],"type":"GroupCall"},{"id":"-659913713","predicate":"inputGroupCall","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputGroupCall"},{"id":"2047704898","predicate":"messageActionGroupCall","params":[{"name":"flags","type":"#"},{"name":"call","type":"InputGroupCall"},{"name":"duration","type":"flags.0?int"}],"type":"MessageAction"},{"id":"1345295095","predicate":"messageActionInviteToGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"users","type":"Vector"}],"type":"MessageAction"},{"id":"-341428482","predicate":"groupCallParticipant","params":[{"name":"flags","type":"#"},{"name":"muted","type":"flags.0?true"},{"name":"left","type":"flags.1?true"},{"name":"can_self_unmute","type":"flags.2?true"},{"name":"just_joined","type":"flags.4?true"},{"name":"versioned","type":"flags.5?true"},{"name":"min","type":"flags.8?true"},{"name":"muted_by_you","type":"flags.9?true"},{"name":"volume_by_admin","type":"flags.10?true"},{"name":"self","type":"flags.12?true"},{"name":"video_joined","type":"flags.15?true"},{"name":"peer","type":"Peer"},{"name":"date","type":"int"},{"name":"active_date","type":"flags.3?int"},{"name":"source","type":"int"},{"name":"volume","type":"flags.7?int"},{"name":"about","type":"flags.11?string"},{"name":"raise_hand_rating","type":"flags.13?long"},{"name":"video","type":"flags.6?GroupCallParticipantVideo"},{"name":"presentation","type":"flags.14?GroupCallParticipantVideo"}],"type":"GroupCallParticipant"},{"id":"-124097970","predicate":"updateChat","params":[{"name":"chat_id","type":"long"}],"type":"Update"},{"id":"-219423922","predicate":"updateGroupCallParticipants","params":[{"name":"call","type":"InputGroupCall"},{"name":"participants","type":"Vector"},{"name":"version","type":"int"}],"type":"Update"},{"id":"347227392","predicate":"updateGroupCall","params":[{"name":"chat_id","type":"long"},{"name":"call","type":"GroupCall"}],"type":"Update"},{"id":"-1636664659","predicate":"phone.groupCall","params":[{"name":"call","type":"GroupCall"},{"name":"participants","type":"Vector"},{"name":"participants_next_offset","type":"string"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"phone.GroupCall"},{"id":"-193506890","predicate":"phone.groupParticipants","params":[{"name":"count","type":"int"},{"name":"participants","type":"Vector"},{"name":"next_offset","type":"string"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"version","type":"int"}],"type":"phone.GroupParticipants"},{"id":"813821341","predicate":"inlineQueryPeerTypeSameBotPM","params":[],"type":"InlineQueryPeerType"},{"id":"-2093215828","predicate":"inlineQueryPeerTypePM","params":[],"type":"InlineQueryPeerType"},{"id":"-681130742","predicate":"inlineQueryPeerTypeChat","params":[],"type":"InlineQueryPeerType"},{"id":"1589952067","predicate":"inlineQueryPeerTypeMegagroup","params":[],"type":"InlineQueryPeerType"},{"id":"1664413338","predicate":"inlineQueryPeerTypeBroadcast","params":[],"type":"InlineQueryPeerType"},{"id":"589338437","predicate":"channelAdminLogEventActionStartGroupCall","params":[{"name":"call","type":"InputGroupCall"}],"type":"ChannelAdminLogEventAction"},{"id":"-610299584","predicate":"channelAdminLogEventActionDiscardGroupCall","params":[{"name":"call","type":"InputGroupCall"}],"type":"ChannelAdminLogEventAction"},{"id":"-115071790","predicate":"channelAdminLogEventActionParticipantMute","params":[{"name":"participant","type":"GroupCallParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"-431740480","predicate":"channelAdminLogEventActionParticipantUnmute","params":[{"name":"participant","type":"GroupCallParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"1456906823","predicate":"channelAdminLogEventActionToggleGroupCallSetting","params":[{"name":"join_muted","type":"Bool"}],"type":"ChannelAdminLogEventAction"},{"id":"-1966921727","predicate":"inputPaymentCredentialsGooglePay","params":[{"name":"payment_token","type":"DataJSON"}],"type":"InputPaymentCredentials"},{"id":"375566091","predicate":"messages.historyImport","params":[{"name":"id","type":"long"}],"type":"messages.HistoryImport"},{"id":"-606432698","predicate":"sendMessageHistoryImportAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"1578088377","predicate":"messages.historyImportParsed","params":[{"name":"flags","type":"#"},{"name":"pm","type":"flags.0?true"},{"name":"group","type":"flags.1?true"},{"name":"title","type":"flags.2?string"}],"type":"messages.HistoryImportParsed"},{"id":"-170010905","predicate":"inputReportReasonFake","params":[],"type":"ReportReason"},{"id":"-275956116","predicate":"messages.affectedFoundMessages","params":[{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"offset","type":"int"},{"name":"messages","type":"Vector"}],"type":"messages.AffectedFoundMessages"},{"id":"-1441072131","predicate":"messageActionSetMessagesTTL","params":[{"name":"period","type":"int"}],"type":"MessageAction"},{"id":"-1147422299","predicate":"updatePeerHistoryTTL","params":[{"name":"flags","type":"#"},{"name":"peer","type":"Peer"},{"name":"ttl_period","type":"flags.0?int"}],"type":"Update"},{"id":"-796432838","predicate":"updateChatParticipant","params":[{"name":"flags","type":"#"},{"name":"chat_id","type":"long"},{"name":"date","type":"int"},{"name":"actor_id","type":"long"},{"name":"user_id","type":"long"},{"name":"prev_participant","type":"flags.0?ChatParticipant"},{"name":"new_participant","type":"flags.1?ChatParticipant"},{"name":"invite","type":"flags.2?ExportedChatInvite"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"-1738720581","predicate":"updateChannelParticipant","params":[{"name":"flags","type":"#"},{"name":"channel_id","type":"long"},{"name":"date","type":"int"},{"name":"actor_id","type":"long"},{"name":"user_id","type":"long"},{"name":"prev_participant","type":"flags.0?ChannelParticipant"},{"name":"new_participant","type":"flags.1?ChannelParticipant"},{"name":"invite","type":"flags.2?ExportedChatInvite"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"-997782967","predicate":"updateBotStopped","params":[{"name":"user_id","type":"long"},{"name":"date","type":"int"},{"name":"stopped","type":"Bool"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"190633460","predicate":"chatInviteImporter","params":[{"name":"user_id","type":"long"},{"name":"date","type":"int"}],"type":"ChatInviteImporter"},{"id":"-1111085620","predicate":"messages.exportedChatInvites","params":[{"name":"count","type":"int"},{"name":"invites","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.ExportedChatInvites"},{"id":"410107472","predicate":"messages.exportedChatInvite","params":[{"name":"invite","type":"ExportedChatInvite"},{"name":"users","type":"Vector"}],"type":"messages.ExportedChatInvite"},{"id":"572915951","predicate":"messages.exportedChatInviteReplaced","params":[{"name":"invite","type":"ExportedChatInvite"},{"name":"new_invite","type":"ExportedChatInvite"},{"name":"users","type":"Vector"}],"type":"messages.ExportedChatInvite"},{"id":"-2118733814","predicate":"messages.chatInviteImporters","params":[{"name":"count","type":"int"},{"name":"importers","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.ChatInviteImporters"},{"id":"-219353309","predicate":"chatAdminWithInvites","params":[{"name":"admin_id","type":"long"},{"name":"invites_count","type":"int"},{"name":"revoked_invites_count","type":"int"}],"type":"ChatAdminWithInvites"},{"id":"-1231326505","predicate":"messages.chatAdminsWithInvites","params":[{"name":"admins","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.ChatAdminsWithInvites"},{"id":"1557846647","predicate":"channelAdminLogEventActionParticipantJoinByInvite","params":[{"name":"invite","type":"ExportedChatInvite"}],"type":"ChannelAdminLogEventAction"},{"id":"1515256996","predicate":"channelAdminLogEventActionExportedInviteDelete","params":[{"name":"invite","type":"ExportedChatInvite"}],"type":"ChannelAdminLogEventAction"},{"id":"1091179342","predicate":"channelAdminLogEventActionExportedInviteRevoke","params":[{"name":"invite","type":"ExportedChatInvite"}],"type":"ChannelAdminLogEventAction"},{"id":"-384910503","predicate":"channelAdminLogEventActionExportedInviteEdit","params":[{"name":"prev_invite","type":"ExportedChatInvite"},{"name":"new_invite","type":"ExportedChatInvite"}],"type":"ChannelAdminLogEventAction"},{"id":"1048537159","predicate":"channelAdminLogEventActionParticipantVolume","params":[{"name":"participant","type":"GroupCallParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"1855199800","predicate":"channelAdminLogEventActionChangeHistoryTTL","params":[{"name":"prev_value","type":"int"},{"name":"new_value","type":"int"}],"type":"ChannelAdminLogEventAction"},{"id":"-1571952873","predicate":"messages.checkedHistoryImportPeer","params":[{"name":"confirm_text","type":"string"}],"type":"messages.CheckedHistoryImportPeer"},{"id":"93890858","predicate":"inputGroupCallStream","params":[{"name":"flags","type":"#"},{"name":"call","type":"InputGroupCall"},{"name":"time_ms","type":"long"},{"name":"scale","type":"int"},{"name":"video_channel","type":"flags.0?int"},{"name":"video_quality","type":"flags.0?int"}],"type":"InputFileLocation"},{"id":"-1343921601","predicate":"phone.joinAsPeers","params":[{"name":"peers","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"phone.JoinAsPeers"},{"id":"541839704","predicate":"phone.exportedGroupCallInvite","params":[{"name":"link","type":"string"}],"type":"phone.ExportedGroupCallInvite"},{"id":"-672693723","predicate":"inputBotInlineMessageMediaInvoice","params":[{"name":"flags","type":"#"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.0?InputWebDocument"},{"name":"invoice","type":"Invoice"},{"name":"payload","type":"bytes"},{"name":"provider","type":"string"},{"name":"provider_data","type":"DataJSON"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"894081801","predicate":"botInlineMessageMediaInvoice","params":[{"name":"flags","type":"#"},{"name":"shipping_address_requested","type":"flags.1?true"},{"name":"test","type":"flags.3?true"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.0?WebDocument"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"-1281329567","predicate":"messageActionGroupCallScheduled","params":[{"name":"call","type":"InputGroupCall"},{"name":"schedule_date","type":"int"}],"type":"MessageAction"},{"id":"-592373577","predicate":"groupCallParticipantVideoSourceGroup","params":[{"name":"semantics","type":"string"},{"name":"sources","type":"Vector"}],"type":"GroupCallParticipantVideoSourceGroup"},{"id":"1735736008","predicate":"groupCallParticipantVideo","params":[{"name":"flags","type":"#"},{"name":"paused","type":"flags.0?true"},{"name":"endpoint","type":"string"},{"name":"source_groups","type":"Vector"},{"name":"audio_source","type":"flags.1?int"}],"type":"GroupCallParticipantVideo"},{"id":"192428418","predicate":"updateGroupCallConnection","params":[{"name":"flags","type":"#"},{"name":"presentation","type":"flags.0?true"},{"name":"params","type":"DataJSON"}],"type":"Update"},{"id":"-2046910401","predicate":"stickers.suggestedShortName","params":[{"name":"short_name","type":"string"}],"type":"stickers.SuggestedShortName"},{"id":"795652779","predicate":"botCommandScopeDefault","params":[],"type":"BotCommandScope"},{"id":"1011811544","predicate":"botCommandScopeUsers","params":[],"type":"BotCommandScope"},{"id":"1877059713","predicate":"botCommandScopeChats","params":[],"type":"BotCommandScope"},{"id":"-1180016534","predicate":"botCommandScopeChatAdmins","params":[],"type":"BotCommandScope"},{"id":"-610432643","predicate":"botCommandScopePeer","params":[{"name":"peer","type":"InputPeer"}],"type":"BotCommandScope"},{"id":"1071145937","predicate":"botCommandScopePeerAdmins","params":[{"name":"peer","type":"InputPeer"}],"type":"BotCommandScope"},{"id":"169026035","predicate":"botCommandScopePeerUser","params":[{"name":"peer","type":"InputPeer"},{"name":"user_id","type":"InputUser"}],"type":"BotCommandScope"},{"id":"-478701471","predicate":"account.resetPasswordFailedWait","params":[{"name":"retry_date","type":"int"}],"type":"account.ResetPasswordResult"},{"id":"-370148227","predicate":"account.resetPasswordRequestedWait","params":[{"name":"until_date","type":"int"}],"type":"account.ResetPasswordResult"},{"id":"-383330754","predicate":"account.resetPasswordOk","params":[],"type":"account.ResetPasswordResult"},{"id":"1299263278","predicate":"updateBotCommands","params":[{"name":"peer","type":"Peer"},{"name":"bot_id","type":"long"},{"name":"commands","type":"Vector"}],"type":"Update"},{"id":"-318022605","predicate":"chatTheme","params":[{"name":"emoticon","type":"string"},{"name":"theme","type":"Theme"},{"name":"dark_theme","type":"Theme"}],"type":"ChatTheme"},{"id":"-535699004","predicate":"account.chatThemesNotModified","params":[],"type":"account.ChatThemes"},{"id":"-28524867","predicate":"account.chatThemes","params":[{"name":"hash","type":"int"},{"name":"themes","type":"Vector"}],"type":"account.ChatThemes"},{"id":"-1434950843","predicate":"messageActionSetChatTheme","params":[{"name":"emoticon","type":"string"}],"type":"MessageAction"},{"id":"-1336228175","predicate":"sendMessageChooseStickerAction","params":[],"type":"SendMessageAction"},{"id":"708589599","predicate":"sponsoredMessage","params":[{"name":"flags","type":"#"},{"name":"random_id","type":"bytes"},{"name":"from_id","type":"Peer"},{"name":"start_param","type":"flags.0?string"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"}],"type":"SponsoredMessage"},{"id":"1705297877","predicate":"messages.sponsoredMessages","params":[{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.SponsoredMessages"},{"id":"215889721","predicate":"inputStickerSetAnimatedEmojiAnimations","params":[],"type":"InputStickerSet"},{"id":"630664139","predicate":"sendMessageEmojiInteraction","params":[{"name":"emoticon","type":"string"},{"name":"msg_id","type":"int"},{"name":"interaction","type":"DataJSON"}],"type":"SendMessageAction"},{"id":"-1234857938","predicate":"sendMessageEmojiInteractionSeen","params":[{"name":"emoticon","type":"string"}],"type":"SendMessageAction"},{"id":"-1227287081","predicate":"inputBotInlineMessageID64","params":[{"name":"dc_id","type":"int"},{"name":"owner_id","type":"long"},{"name":"id","type":"int"},{"name":"access_hash","type":"long"}],"type":"InputBotInlineMessageID"}],"methods":[{"id":"-878758099","method":"invokeAfterMsg","params":[{"name":"msg_id","type":"long"},{"name":"query","type":"!X"}],"type":"X"},{"id":"1036301552","method":"invokeAfterMsgs","params":[{"name":"msg_ids","type":"Vector"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-1502141361","method":"auth.sendCode","params":[{"name":"phone_number","type":"string"},{"name":"api_id","type":"int"},{"name":"api_hash","type":"string"},{"name":"settings","type":"CodeSettings"}],"type":"auth.SentCode"},{"id":"-2131827673","method":"auth.signUp","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"}],"type":"auth.Authorization"},{"id":"-1126886015","method":"auth.signIn","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"},{"name":"phone_code","type":"string"}],"type":"auth.Authorization"},{"id":"1461180992","method":"auth.logOut","params":[],"type":"Bool"},{"id":"-1616179942","method":"auth.resetAuthorizations","params":[],"type":"Bool"},{"id":"-440401971","method":"auth.exportAuthorization","params":[{"name":"dc_id","type":"int"}],"type":"auth.ExportedAuthorization"},{"id":"-1518699091","method":"auth.importAuthorization","params":[{"name":"id","type":"long"},{"name":"bytes","type":"bytes"}],"type":"auth.Authorization"},{"id":"-841733627","method":"auth.bindTempAuthKey","params":[{"name":"perm_auth_key_id","type":"long"},{"name":"nonce","type":"long"},{"name":"expires_at","type":"int"},{"name":"encrypted_message","type":"bytes"}],"type":"Bool"},{"id":"-326762118","method":"account.registerDevice","params":[{"name":"flags","type":"#"},{"name":"no_muted","type":"flags.0?true"},{"name":"token_type","type":"int"},{"name":"token","type":"string"},{"name":"app_sandbox","type":"Bool"},{"name":"secret","type":"bytes"},{"name":"other_uids","type":"Vector"}],"type":"Bool"},{"id":"1779249670","method":"account.unregisterDevice","params":[{"name":"token_type","type":"int"},{"name":"token","type":"string"},{"name":"other_uids","type":"Vector"}],"type":"Bool"},{"id":"-2067899501","method":"account.updateNotifySettings","params":[{"name":"peer","type":"InputNotifyPeer"},{"name":"settings","type":"InputPeerNotifySettings"}],"type":"Bool"},{"id":"313765169","method":"account.getNotifySettings","params":[{"name":"peer","type":"InputNotifyPeer"}],"type":"PeerNotifySettings"},{"id":"-612493497","method":"account.resetNotifySettings","params":[],"type":"Bool"},{"id":"2018596725","method":"account.updateProfile","params":[{"name":"flags","type":"#"},{"name":"first_name","type":"flags.0?string"},{"name":"last_name","type":"flags.1?string"},{"name":"about","type":"flags.2?string"}],"type":"User"},{"id":"1713919532","method":"account.updateStatus","params":[{"name":"offline","type":"Bool"}],"type":"Bool"},{"id":"127302966","method":"account.getWallPapers","params":[{"name":"hash","type":"long"}],"type":"account.WallPapers"},{"id":"-977650298","method":"account.reportPeer","params":[{"name":"peer","type":"InputPeer"},{"name":"reason","type":"ReportReason"},{"name":"message","type":"string"}],"type":"Bool"},{"id":"227648840","method":"users.getUsers","params":[{"name":"id","type":"Vector"}],"type":"Vector"},{"id":"-902781519","method":"users.getFullUser","params":[{"name":"id","type":"InputUser"}],"type":"UserFull"},{"id":"2061264541","method":"contacts.getContactIDs","params":[{"name":"hash","type":"long"}],"type":"Vector"},{"id":"-995929106","method":"contacts.getStatuses","params":[],"type":"Vector"},{"id":"1574346258","method":"contacts.getContacts","params":[{"name":"hash","type":"long"}],"type":"contacts.Contacts"},{"id":"746589157","method":"contacts.importContacts","params":[{"name":"contacts","type":"Vector"}],"type":"contacts.ImportedContacts"},{"id":"157945344","method":"contacts.deleteContacts","params":[{"name":"id","type":"Vector"}],"type":"Updates"},{"id":"269745566","method":"contacts.deleteByPhones","params":[{"name":"phones","type":"Vector"}],"type":"Bool"},{"id":"1758204945","method":"contacts.block","params":[{"name":"id","type":"InputPeer"}],"type":"Bool"},{"id":"-1096393392","method":"contacts.unblock","params":[{"name":"id","type":"InputPeer"}],"type":"Bool"},{"id":"-176409329","method":"contacts.getBlocked","params":[{"name":"offset","type":"int"},{"name":"limit","type":"int"}],"type":"contacts.Blocked"},{"id":"1673946374","method":"messages.getMessages","params":[{"name":"id","type":"Vector"}],"type":"messages.Messages"},{"id":"-1594569905","method":"messages.getDialogs","params":[{"name":"flags","type":"#"},{"name":"exclude_pinned","type":"flags.0?true"},{"name":"folder_id","type":"flags.1?int"},{"name":"offset_date","type":"int"},{"name":"offset_id","type":"int"},{"name":"offset_peer","type":"InputPeer"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Dialogs"},{"id":"1143203525","method":"messages.getHistory","params":[{"name":"peer","type":"InputPeer"},{"name":"offset_id","type":"int"},{"name":"offset_date","type":"int"},{"name":"add_offset","type":"int"},{"name":"limit","type":"int"},{"name":"max_id","type":"int"},{"name":"min_id","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"-1593989278","method":"messages.search","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"q","type":"string"},{"name":"from_id","type":"flags.0?InputPeer"},{"name":"top_msg_id","type":"flags.1?int"},{"name":"filter","type":"MessagesFilter"},{"name":"min_date","type":"int"},{"name":"max_date","type":"int"},{"name":"offset_id","type":"int"},{"name":"add_offset","type":"int"},{"name":"limit","type":"int"},{"name":"max_id","type":"int"},{"name":"min_id","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"238054714","method":"messages.readHistory","params":[{"name":"peer","type":"InputPeer"},{"name":"max_id","type":"int"}],"type":"messages.AffectedMessages"},{"id":"469850889","method":"messages.deleteHistory","params":[{"name":"flags","type":"#"},{"name":"just_clear","type":"flags.0?true"},{"name":"revoke","type":"flags.1?true"},{"name":"peer","type":"InputPeer"},{"name":"max_id","type":"int"}],"type":"messages.AffectedHistory"},{"id":"-443640366","method":"messages.deleteMessages","params":[{"name":"flags","type":"#"},{"name":"revoke","type":"flags.0?true"},{"name":"id","type":"Vector"}],"type":"messages.AffectedMessages"},{"id":"94983360","method":"messages.receivedMessages","params":[{"name":"max_id","type":"int"}],"type":"Vector"},{"id":"1486110434","method":"messages.setTyping","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"top_msg_id","type":"flags.0?int"},{"name":"action","type":"SendMessageAction"}],"type":"Bool"},{"id":"1376532592","method":"messages.sendMessage","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"clear_draft","type":"flags.7?true"},{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"message","type":"string"},{"name":"random_id","type":"long"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"},{"name":"entities","type":"flags.3?Vector"},{"name":"schedule_date","type":"flags.10?int"}],"type":"Updates"},{"id":"881978281","method":"messages.sendMedia","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"clear_draft","type":"flags.7?true"},{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"media","type":"InputMedia"},{"name":"message","type":"string"},{"name":"random_id","type":"long"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"},{"name":"entities","type":"flags.3?Vector"},{"name":"schedule_date","type":"flags.10?int"}],"type":"Updates"},{"id":"-637606386","method":"messages.forwardMessages","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"with_my_score","type":"flags.8?true"},{"name":"drop_author","type":"flags.11?true"},{"name":"drop_media_captions","type":"flags.12?true"},{"name":"from_peer","type":"InputPeer"},{"name":"id","type":"Vector"},{"name":"random_id","type":"Vector"},{"name":"to_peer","type":"InputPeer"},{"name":"schedule_date","type":"flags.10?int"}],"type":"Updates"},{"id":"-820669733","method":"messages.reportSpam","params":[{"name":"peer","type":"InputPeer"}],"type":"Bool"},{"id":"913498268","method":"messages.getPeerSettings","params":[{"name":"peer","type":"InputPeer"}],"type":"PeerSettings"},{"id":"-1991005362","method":"messages.report","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"},{"name":"reason","type":"ReportReason"},{"name":"message","type":"string"}],"type":"Bool"},{"id":"1240027791","method":"messages.getChats","params":[{"name":"id","type":"Vector"}],"type":"messages.Chats"},{"id":"-1364194508","method":"messages.getFullChat","params":[{"name":"chat_id","type":"long"}],"type":"messages.ChatFull"},{"id":"1937260541","method":"messages.editChatTitle","params":[{"name":"chat_id","type":"long"},{"name":"title","type":"string"}],"type":"Updates"},{"id":"903730804","method":"messages.editChatPhoto","params":[{"name":"chat_id","type":"long"},{"name":"photo","type":"InputChatPhoto"}],"type":"Updates"},{"id":"-230206493","method":"messages.addChatUser","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"InputUser"},{"name":"fwd_limit","type":"int"}],"type":"Updates"},{"id":"-1575461717","method":"messages.deleteChatUser","params":[{"name":"flags","type":"#"},{"name":"revoke_history","type":"flags.0?true"},{"name":"chat_id","type":"long"},{"name":"user_id","type":"InputUser"}],"type":"Updates"},{"id":"164303470","method":"messages.createChat","params":[{"name":"users","type":"Vector"},{"name":"title","type":"string"}],"type":"Updates"},{"id":"-304838614","method":"updates.getState","params":[],"type":"updates.State"},{"id":"630429265","method":"updates.getDifference","params":[{"name":"flags","type":"#"},{"name":"pts","type":"int"},{"name":"pts_total_limit","type":"flags.0?int"},{"name":"date","type":"int"},{"name":"qts","type":"int"}],"type":"updates.Difference"},{"id":"1926525996","method":"photos.updateProfilePhoto","params":[{"name":"id","type":"InputPhoto"}],"type":"photos.Photo"},{"id":"-1980559511","method":"photos.uploadProfilePhoto","params":[{"name":"flags","type":"#"},{"name":"file","type":"flags.0?InputFile"},{"name":"video","type":"flags.1?InputFile"},{"name":"video_start_ts","type":"flags.2?double"}],"type":"photos.Photo"},{"id":"-2016444625","method":"photos.deletePhotos","params":[{"name":"id","type":"Vector"}],"type":"Vector"},{"id":"-1291540959","method":"upload.saveFilePart","params":[{"name":"file_id","type":"long"},{"name":"file_part","type":"int"},{"name":"bytes","type":"bytes"}],"type":"Bool"},{"id":"-1319462148","method":"upload.getFile","params":[{"name":"flags","type":"#"},{"name":"precise","type":"flags.0?true"},{"name":"cdn_supported","type":"flags.1?true"},{"name":"location","type":"InputFileLocation"},{"name":"offset","type":"int"},{"name":"limit","type":"int"}],"type":"upload.File"},{"id":"-990308245","method":"help.getConfig","params":[],"type":"Config"},{"id":"531836966","method":"help.getNearestDc","params":[],"type":"NearestDc"},{"id":"1378703997","method":"help.getAppUpdate","params":[{"name":"source","type":"string"}],"type":"help.AppUpdate"},{"id":"1295590211","method":"help.getInviteText","params":[],"type":"help.InviteText"},{"id":"-1848823128","method":"photos.getUserPhotos","params":[{"name":"user_id","type":"InputUser"},{"name":"offset","type":"int"},{"name":"max_id","type":"long"},{"name":"limit","type":"int"}],"type":"photos.Photos"},{"id":"651135312","method":"messages.getDhConfig","params":[{"name":"version","type":"int"},{"name":"random_length","type":"int"}],"type":"messages.DhConfig"},{"id":"-162681021","method":"messages.requestEncryption","params":[{"name":"user_id","type":"InputUser"},{"name":"random_id","type":"int"},{"name":"g_a","type":"bytes"}],"type":"EncryptedChat"},{"id":"1035731989","method":"messages.acceptEncryption","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"g_b","type":"bytes"},{"name":"key_fingerprint","type":"long"}],"type":"EncryptedChat"},{"id":"-208425312","method":"messages.discardEncryption","params":[{"name":"flags","type":"#"},{"name":"delete_history","type":"flags.0?true"},{"name":"chat_id","type":"int"}],"type":"Bool"},{"id":"2031374829","method":"messages.setEncryptedTyping","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"typing","type":"Bool"}],"type":"Bool"},{"id":"2135648522","method":"messages.readEncryptedHistory","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"max_date","type":"int"}],"type":"Bool"},{"id":"1157265941","method":"messages.sendEncrypted","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.0?true"},{"name":"peer","type":"InputEncryptedChat"},{"name":"random_id","type":"long"},{"name":"data","type":"bytes"}],"type":"messages.SentEncryptedMessage"},{"id":"1431914525","method":"messages.sendEncryptedFile","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.0?true"},{"name":"peer","type":"InputEncryptedChat"},{"name":"random_id","type":"long"},{"name":"data","type":"bytes"},{"name":"file","type":"InputEncryptedFile"}],"type":"messages.SentEncryptedMessage"},{"id":"852769188","method":"messages.sendEncryptedService","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"random_id","type":"long"},{"name":"data","type":"bytes"}],"type":"messages.SentEncryptedMessage"},{"id":"1436924774","method":"messages.receivedQueue","params":[{"name":"max_qts","type":"int"}],"type":"Vector"},{"id":"1259113487","method":"messages.reportEncryptedSpam","params":[{"name":"peer","type":"InputEncryptedChat"}],"type":"Bool"},{"id":"-562337987","method":"upload.saveBigFilePart","params":[{"name":"file_id","type":"long"},{"name":"file_part","type":"int"},{"name":"file_total_parts","type":"int"},{"name":"bytes","type":"bytes"}],"type":"Bool"},{"id":"-1043505495","method":"initConnection","params":[{"name":"flags","type":"#"},{"name":"api_id","type":"int"},{"name":"device_model","type":"string"},{"name":"system_version","type":"string"},{"name":"app_version","type":"string"},{"name":"system_lang_code","type":"string"},{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"},{"name":"proxy","type":"flags.0?InputClientProxy"},{"name":"params","type":"flags.1?JSONValue"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-1663104819","method":"help.getSupport","params":[],"type":"help.Support"},{"id":"916930423","method":"messages.readMessageContents","params":[{"name":"id","type":"Vector"}],"type":"messages.AffectedMessages"},{"id":"655677548","method":"account.checkUsername","params":[{"name":"username","type":"string"}],"type":"Bool"},{"id":"1040964988","method":"account.updateUsername","params":[{"name":"username","type":"string"}],"type":"User"},{"id":"301470424","method":"contacts.search","params":[{"name":"q","type":"string"},{"name":"limit","type":"int"}],"type":"contacts.Found"},{"id":"-623130288","method":"account.getPrivacy","params":[{"name":"key","type":"InputPrivacyKey"}],"type":"account.PrivacyRules"},{"id":"-906486552","method":"account.setPrivacy","params":[{"name":"key","type":"InputPrivacyKey"},{"name":"rules","type":"Vector"}],"type":"account.PrivacyRules"},{"id":"1099779595","method":"account.deleteAccount","params":[{"name":"reason","type":"string"}],"type":"Bool"},{"id":"150761757","method":"account.getAccountTTL","params":[],"type":"AccountDaysTTL"},{"id":"608323678","method":"account.setAccountTTL","params":[{"name":"ttl","type":"AccountDaysTTL"}],"type":"Bool"},{"id":"-627372787","method":"invokeWithLayer","params":[{"name":"layer","type":"int"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-113456221","method":"contacts.resolveUsername","params":[{"name":"username","type":"string"}],"type":"contacts.ResolvedPeer"},{"id":"-2108208411","method":"account.sendChangePhoneCode","params":[{"name":"phone_number","type":"string"},{"name":"settings","type":"CodeSettings"}],"type":"auth.SentCode"},{"id":"1891839707","method":"account.changePhone","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"},{"name":"phone_code","type":"string"}],"type":"User"},{"id":"-710552671","method":"messages.getStickers","params":[{"name":"emoticon","type":"string"},{"name":"hash","type":"long"}],"type":"messages.Stickers"},{"id":"-1197432408","method":"messages.getAllStickers","params":[{"name":"hash","type":"long"}],"type":"messages.AllStickers"},{"id":"954152242","method":"account.updateDeviceLocked","params":[{"name":"period","type":"int"}],"type":"Bool"},{"id":"1738800940","method":"auth.importBotAuthorization","params":[{"name":"flags","type":"int"},{"name":"api_id","type":"int"},{"name":"api_hash","type":"string"},{"name":"bot_auth_token","type":"string"}],"type":"auth.Authorization"},{"id":"-1956073268","method":"messages.getWebPagePreview","params":[{"name":"flags","type":"#"},{"name":"message","type":"string"},{"name":"entities","type":"flags.3?Vector"}],"type":"MessageMedia"},{"id":"-484392616","method":"account.getAuthorizations","params":[],"type":"account.Authorizations"},{"id":"-545786948","method":"account.resetAuthorization","params":[{"name":"hash","type":"long"}],"type":"Bool"},{"id":"1418342645","method":"account.getPassword","params":[],"type":"account.Password"},{"id":"-1663767815","method":"account.getPasswordSettings","params":[{"name":"password","type":"InputCheckPasswordSRP"}],"type":"account.PasswordSettings"},{"id":"-1516564433","method":"account.updatePasswordSettings","params":[{"name":"password","type":"InputCheckPasswordSRP"},{"name":"new_settings","type":"account.PasswordInputSettings"}],"type":"Bool"},{"id":"-779399914","method":"auth.checkPassword","params":[{"name":"password","type":"InputCheckPasswordSRP"}],"type":"auth.Authorization"},{"id":"-661144474","method":"auth.requestPasswordRecovery","params":[],"type":"auth.PasswordRecovery"},{"id":"923364464","method":"auth.recoverPassword","params":[{"name":"flags","type":"#"},{"name":"code","type":"string"},{"name":"new_settings","type":"flags.0?account.PasswordInputSettings"}],"type":"auth.Authorization"},{"id":"-1080796745","method":"invokeWithoutUpdates","params":[{"name":"query","type":"!X"}],"type":"X"},{"id":"347716823","method":"messages.exportChatInvite","params":[{"name":"flags","type":"#"},{"name":"legacy_revoke_permanent","type":"flags.2?true"},{"name":"peer","type":"InputPeer"},{"name":"expire_date","type":"flags.0?int"},{"name":"usage_limit","type":"flags.1?int"}],"type":"ExportedChatInvite"},{"id":"1051570619","method":"messages.checkChatInvite","params":[{"name":"hash","type":"string"}],"type":"ChatInvite"},{"id":"1817183516","method":"messages.importChatInvite","params":[{"name":"hash","type":"string"}],"type":"Updates"},{"id":"639215886","method":"messages.getStickerSet","params":[{"name":"stickerset","type":"InputStickerSet"}],"type":"messages.StickerSet"},{"id":"-946871200","method":"messages.installStickerSet","params":[{"name":"stickerset","type":"InputStickerSet"},{"name":"archived","type":"Bool"}],"type":"messages.StickerSetInstallResult"},{"id":"-110209570","method":"messages.uninstallStickerSet","params":[{"name":"stickerset","type":"InputStickerSet"}],"type":"Bool"},{"id":"-421563528","method":"messages.startBot","params":[{"name":"bot","type":"InputUser"},{"name":"peer","type":"InputPeer"},{"name":"random_id","type":"long"},{"name":"start_param","type":"string"}],"type":"Updates"},{"id":"-1877938321","method":"help.getAppChangelog","params":[{"name":"prev_app_version","type":"string"}],"type":"Updates"},{"id":"1468322785","method":"messages.getMessagesViews","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"},{"name":"increment","type":"Bool"}],"type":"messages.MessageViews"},{"id":"-871347913","method":"channels.readHistory","params":[{"name":"channel","type":"InputChannel"},{"name":"max_id","type":"int"}],"type":"Bool"},{"id":"-2067661490","method":"channels.deleteMessages","params":[{"name":"channel","type":"InputChannel"},{"name":"id","type":"Vector"}],"type":"messages.AffectedMessages"},{"id":"-787622117","method":"channels.deleteUserHistory","params":[{"name":"channel","type":"InputChannel"},{"name":"user_id","type":"InputUser"}],"type":"messages.AffectedHistory"},{"id":"-32999408","method":"channels.reportSpam","params":[{"name":"channel","type":"InputChannel"},{"name":"user_id","type":"InputUser"},{"name":"id","type":"Vector"}],"type":"Bool"},{"id":"-1383294429","method":"channels.getMessages","params":[{"name":"channel","type":"InputChannel"},{"name":"id","type":"Vector"}],"type":"messages.Messages"},{"id":"2010044880","method":"channels.getParticipants","params":[{"name":"channel","type":"InputChannel"},{"name":"filter","type":"ChannelParticipantsFilter"},{"name":"offset","type":"int"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"channels.ChannelParticipants"},{"id":"-1599378234","method":"channels.getParticipant","params":[{"name":"channel","type":"InputChannel"},{"name":"participant","type":"InputPeer"}],"type":"channels.ChannelParticipant"},{"id":"176122811","method":"channels.getChannels","params":[{"name":"id","type":"Vector"}],"type":"messages.Chats"},{"id":"141781513","method":"channels.getFullChannel","params":[{"name":"channel","type":"InputChannel"}],"type":"messages.ChatFull"},{"id":"1029681423","method":"channels.createChannel","params":[{"name":"flags","type":"#"},{"name":"broadcast","type":"flags.0?true"},{"name":"megagroup","type":"flags.1?true"},{"name":"for_import","type":"flags.3?true"},{"name":"title","type":"string"},{"name":"about","type":"string"},{"name":"geo_point","type":"flags.2?InputGeoPoint"},{"name":"address","type":"flags.2?string"}],"type":"Updates"},{"id":"-751007486","method":"channels.editAdmin","params":[{"name":"channel","type":"InputChannel"},{"name":"user_id","type":"InputUser"},{"name":"admin_rights","type":"ChatAdminRights"},{"name":"rank","type":"string"}],"type":"Updates"},{"id":"1450044624","method":"channels.editTitle","params":[{"name":"channel","type":"InputChannel"},{"name":"title","type":"string"}],"type":"Updates"},{"id":"-248621111","method":"channels.editPhoto","params":[{"name":"channel","type":"InputChannel"},{"name":"photo","type":"InputChatPhoto"}],"type":"Updates"},{"id":"283557164","method":"channels.checkUsername","params":[{"name":"channel","type":"InputChannel"},{"name":"username","type":"string"}],"type":"Bool"},{"id":"890549214","method":"channels.updateUsername","params":[{"name":"channel","type":"InputChannel"},{"name":"username","type":"string"}],"type":"Bool"},{"id":"615851205","method":"channels.joinChannel","params":[{"name":"channel","type":"InputChannel"}],"type":"Updates"},{"id":"-130635115","method":"channels.leaveChannel","params":[{"name":"channel","type":"InputChannel"}],"type":"Updates"},{"id":"429865580","method":"channels.inviteToChannel","params":[{"name":"channel","type":"InputChannel"},{"name":"users","type":"Vector"}],"type":"Updates"},{"id":"-1072619549","method":"channels.deleteChannel","params":[{"name":"channel","type":"InputChannel"}],"type":"Updates"},{"id":"51854712","method":"updates.getChannelDifference","params":[{"name":"flags","type":"#"},{"name":"force","type":"flags.0?true"},{"name":"channel","type":"InputChannel"},{"name":"filter","type":"ChannelMessagesFilter"},{"name":"pts","type":"int"},{"name":"limit","type":"int"}],"type":"updates.ChannelDifference"},{"id":"-1470377534","method":"messages.editChatAdmin","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"InputUser"},{"name":"is_admin","type":"Bool"}],"type":"Bool"},{"id":"-1568189671","method":"messages.migrateChat","params":[{"name":"chat_id","type":"long"}],"type":"Updates"},{"id":"1271290010","method":"messages.searchGlobal","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.0?int"},{"name":"q","type":"string"},{"name":"filter","type":"MessagesFilter"},{"name":"min_date","type":"int"},{"name":"max_date","type":"int"},{"name":"offset_rate","type":"int"},{"name":"offset_peer","type":"InputPeer"},{"name":"offset_id","type":"int"},{"name":"limit","type":"int"}],"type":"messages.Messages"},{"id":"2016638777","method":"messages.reorderStickerSets","params":[{"name":"flags","type":"#"},{"name":"masks","type":"flags.0?true"},{"name":"order","type":"Vector"}],"type":"Bool"},{"id":"864953444","method":"messages.getDocumentByHash","params":[{"name":"sha256","type":"bytes"},{"name":"size","type":"int"},{"name":"mime_type","type":"string"}],"type":"Document"},{"id":"1559270965","method":"messages.getSavedGifs","params":[{"name":"hash","type":"long"}],"type":"messages.SavedGifs"},{"id":"846868683","method":"messages.saveGif","params":[{"name":"id","type":"InputDocument"},{"name":"unsave","type":"Bool"}],"type":"Bool"},{"id":"1364105629","method":"messages.getInlineBotResults","params":[{"name":"flags","type":"#"},{"name":"bot","type":"InputUser"},{"name":"peer","type":"InputPeer"},{"name":"geo_point","type":"flags.0?InputGeoPoint"},{"name":"query","type":"string"},{"name":"offset","type":"string"}],"type":"messages.BotResults"},{"id":"-346119674","method":"messages.setInlineBotResults","params":[{"name":"flags","type":"#"},{"name":"gallery","type":"flags.0?true"},{"name":"private","type":"flags.1?true"},{"name":"query_id","type":"long"},{"name":"results","type":"Vector"},{"name":"cache_time","type":"int"},{"name":"next_offset","type":"flags.2?string"},{"name":"switch_pm","type":"flags.3?InlineBotSwitchPM"}],"type":"Bool"},{"id":"570955184","method":"messages.sendInlineBotResult","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"clear_draft","type":"flags.7?true"},{"name":"hide_via","type":"flags.11?true"},{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"random_id","type":"long"},{"name":"query_id","type":"long"},{"name":"id","type":"string"},{"name":"schedule_date","type":"flags.10?int"}],"type":"Updates"},{"id":"-432034325","method":"channels.exportMessageLink","params":[{"name":"flags","type":"#"},{"name":"grouped","type":"flags.0?true"},{"name":"thread","type":"flags.1?true"},{"name":"channel","type":"InputChannel"},{"name":"id","type":"int"}],"type":"ExportedMessageLink"},{"id":"527021574","method":"channels.toggleSignatures","params":[{"name":"channel","type":"InputChannel"},{"name":"enabled","type":"Bool"}],"type":"Updates"},{"id":"1056025023","method":"auth.resendCode","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"}],"type":"auth.SentCode"},{"id":"520357240","method":"auth.cancelCode","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"}],"type":"Bool"},{"id":"-39416522","method":"messages.getMessageEditData","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"}],"type":"messages.MessageEditData"},{"id":"1224152952","method":"messages.editMessage","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"},{"name":"message","type":"flags.11?string"},{"name":"media","type":"flags.14?InputMedia"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"},{"name":"entities","type":"flags.3?Vector"},{"name":"schedule_date","type":"flags.15?int"}],"type":"Updates"},{"id":"-2091549254","method":"messages.editInlineBotMessage","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"id","type":"InputBotInlineMessageID"},{"name":"message","type":"flags.11?string"},{"name":"media","type":"flags.14?InputMedia"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"},{"name":"entities","type":"flags.3?Vector"}],"type":"Bool"},{"id":"-1824339449","method":"messages.getBotCallbackAnswer","params":[{"name":"flags","type":"#"},{"name":"game","type":"flags.1?true"},{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"data","type":"flags.0?bytes"},{"name":"password","type":"flags.2?InputCheckPasswordSRP"}],"type":"messages.BotCallbackAnswer"},{"id":"-712043766","method":"messages.setBotCallbackAnswer","params":[{"name":"flags","type":"#"},{"name":"alert","type":"flags.1?true"},{"name":"query_id","type":"long"},{"name":"message","type":"flags.0?string"},{"name":"url","type":"flags.2?string"},{"name":"cache_time","type":"int"}],"type":"Bool"},{"id":"-1758168906","method":"contacts.getTopPeers","params":[{"name":"flags","type":"#"},{"name":"correspondents","type":"flags.0?true"},{"name":"bots_pm","type":"flags.1?true"},{"name":"bots_inline","type":"flags.2?true"},{"name":"phone_calls","type":"flags.3?true"},{"name":"forward_users","type":"flags.4?true"},{"name":"forward_chats","type":"flags.5?true"},{"name":"groups","type":"flags.10?true"},{"name":"channels","type":"flags.15?true"},{"name":"offset","type":"int"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"contacts.TopPeers"},{"id":"451113900","method":"contacts.resetTopPeerRating","params":[{"name":"category","type":"TopPeerCategory"},{"name":"peer","type":"InputPeer"}],"type":"Bool"},{"id":"-462373635","method":"messages.getPeerDialogs","params":[{"name":"peers","type":"Vector"}],"type":"messages.PeerDialogs"},{"id":"-1137057461","method":"messages.saveDraft","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"peer","type":"InputPeer"},{"name":"message","type":"string"},{"name":"entities","type":"flags.3?Vector"}],"type":"Bool"},{"id":"1782549861","method":"messages.getAllDrafts","params":[],"type":"Updates"},{"id":"1685588756","method":"messages.getFeaturedStickers","params":[{"name":"hash","type":"long"}],"type":"messages.FeaturedStickers"},{"id":"1527873830","method":"messages.readFeaturedStickers","params":[{"name":"id","type":"Vector"}],"type":"Bool"},{"id":"-1649852357","method":"messages.getRecentStickers","params":[{"name":"flags","type":"#"},{"name":"attached","type":"flags.0?true"},{"name":"hash","type":"long"}],"type":"messages.RecentStickers"},{"id":"958863608","method":"messages.saveRecentSticker","params":[{"name":"flags","type":"#"},{"name":"attached","type":"flags.0?true"},{"name":"id","type":"InputDocument"},{"name":"unsave","type":"Bool"}],"type":"Bool"},{"id":"-1986437075","method":"messages.clearRecentStickers","params":[{"name":"flags","type":"#"},{"name":"attached","type":"flags.0?true"}],"type":"Bool"},{"id":"1475442322","method":"messages.getArchivedStickers","params":[{"name":"flags","type":"#"},{"name":"masks","type":"flags.0?true"},{"name":"offset_id","type":"long"},{"name":"limit","type":"int"}],"type":"messages.ArchivedStickers"},{"id":"457157256","method":"account.sendConfirmPhoneCode","params":[{"name":"hash","type":"string"},{"name":"settings","type":"CodeSettings"}],"type":"auth.SentCode"},{"id":"1596029123","method":"account.confirmPhone","params":[{"name":"phone_code_hash","type":"string"},{"name":"phone_code","type":"string"}],"type":"Bool"},{"id":"-122669393","method":"channels.getAdminedPublicChannels","params":[{"name":"flags","type":"#"},{"name":"by_location","type":"flags.0?true"},{"name":"check_limit","type":"flags.1?true"}],"type":"messages.Chats"},{"id":"1678738104","method":"messages.getMaskStickers","params":[{"name":"hash","type":"long"}],"type":"messages.AllStickers"},{"id":"-866424884","method":"messages.getAttachedStickers","params":[{"name":"media","type":"InputStickeredMedia"}],"type":"Vector"},{"id":"-1907842680","method":"auth.dropTempAuthKeys","params":[{"name":"except_auth_keys","type":"Vector"}],"type":"Bool"},{"id":"-1896289088","method":"messages.setGameScore","params":[{"name":"flags","type":"#"},{"name":"edit_message","type":"flags.0?true"},{"name":"force","type":"flags.1?true"},{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"},{"name":"user_id","type":"InputUser"},{"name":"score","type":"int"}],"type":"Updates"},{"id":"363700068","method":"messages.setInlineGameScore","params":[{"name":"flags","type":"#"},{"name":"edit_message","type":"flags.0?true"},{"name":"force","type":"flags.1?true"},{"name":"id","type":"InputBotInlineMessageID"},{"name":"user_id","type":"InputUser"},{"name":"score","type":"int"}],"type":"Bool"},{"id":"-400399203","method":"messages.getGameHighScores","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"},{"name":"user_id","type":"InputUser"}],"type":"messages.HighScores"},{"id":"258170395","method":"messages.getInlineGameHighScores","params":[{"name":"id","type":"InputBotInlineMessageID"},{"name":"user_id","type":"InputUser"}],"type":"messages.HighScores"},{"id":"-468934396","method":"messages.getCommonChats","params":[{"name":"user_id","type":"InputUser"},{"name":"max_id","type":"long"},{"name":"limit","type":"int"}],"type":"messages.Chats"},{"id":"-2023787330","method":"messages.getAllChats","params":[{"name":"except_ids","type":"Vector"}],"type":"messages.Chats"},{"id":"-333262899","method":"help.setBotUpdatesStatus","params":[{"name":"pending_updates_count","type":"int"},{"name":"message","type":"string"}],"type":"Bool"},{"id":"852135825","method":"messages.getWebPage","params":[{"name":"url","type":"string"},{"name":"hash","type":"int"}],"type":"WebPage"},{"id":"-1489903017","method":"messages.toggleDialogPin","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.0?true"},{"name":"peer","type":"InputDialogPeer"}],"type":"Bool"},{"id":"991616823","method":"messages.reorderPinnedDialogs","params":[{"name":"flags","type":"#"},{"name":"force","type":"flags.0?true"},{"name":"folder_id","type":"int"},{"name":"order","type":"Vector"}],"type":"Bool"},{"id":"-692498958","method":"messages.getPinnedDialogs","params":[{"name":"folder_id","type":"int"}],"type":"messages.PeerDialogs"},{"id":"-1440257555","method":"bots.sendCustomRequest","params":[{"name":"custom_method","type":"string"},{"name":"params","type":"DataJSON"}],"type":"DataJSON"},{"id":"-434028723","method":"bots.answerWebhookJSONQuery","params":[{"name":"query_id","type":"long"},{"name":"data","type":"DataJSON"}],"type":"Bool"},{"id":"619086221","method":"upload.getWebFile","params":[{"name":"location","type":"InputWebFileLocation"},{"name":"offset","type":"int"},{"name":"limit","type":"int"}],"type":"upload.WebFile"},{"id":"-1976353651","method":"payments.getPaymentForm","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"theme_params","type":"flags.0?DataJSON"}],"type":"payments.PaymentForm"},{"id":"611897804","method":"payments.getPaymentReceipt","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"}],"type":"payments.PaymentReceipt"},{"id":"-619695760","method":"payments.validateRequestedInfo","params":[{"name":"flags","type":"#"},{"name":"save","type":"flags.0?true"},{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"info","type":"PaymentRequestedInfo"}],"type":"payments.ValidatedRequestedInfo"},{"id":"818134173","method":"payments.sendPaymentForm","params":[{"name":"flags","type":"#"},{"name":"form_id","type":"long"},{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"requested_info_id","type":"flags.0?string"},{"name":"shipping_option_id","type":"flags.1?string"},{"name":"credentials","type":"InputPaymentCredentials"},{"name":"tip_amount","type":"flags.2?long"}],"type":"payments.PaymentResult"},{"id":"1151208273","method":"account.getTmpPassword","params":[{"name":"password","type":"InputCheckPasswordSRP"},{"name":"period","type":"int"}],"type":"account.TmpPassword"},{"id":"578650699","method":"payments.getSavedInfo","params":[],"type":"payments.SavedInfo"},{"id":"-667062079","method":"payments.clearSavedInfo","params":[{"name":"flags","type":"#"},{"name":"credentials","type":"flags.0?true"},{"name":"info","type":"flags.1?true"}],"type":"Bool"},{"id":"-436833542","method":"messages.setBotShippingResults","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"error","type":"flags.0?string"},{"name":"shipping_options","type":"flags.1?Vector"}],"type":"Bool"},{"id":"163765653","method":"messages.setBotPrecheckoutResults","params":[{"name":"flags","type":"#"},{"name":"success","type":"flags.1?true"},{"name":"query_id","type":"long"},{"name":"error","type":"flags.0?string"}],"type":"Bool"},{"id":"-1876841625","method":"stickers.createStickerSet","params":[{"name":"flags","type":"#"},{"name":"masks","type":"flags.0?true"},{"name":"animated","type":"flags.1?true"},{"name":"videos","type":"flags.4?true"},{"name":"user_id","type":"InputUser"},{"name":"title","type":"string"},{"name":"short_name","type":"string"},{"name":"thumb","type":"flags.2?InputDocument"},{"name":"stickers","type":"Vector"},{"name":"software","type":"flags.3?string"}],"type":"messages.StickerSet"},{"id":"-143257775","method":"stickers.removeStickerFromSet","params":[{"name":"sticker","type":"InputDocument"}],"type":"messages.StickerSet"},{"id":"-4795190","method":"stickers.changeStickerPosition","params":[{"name":"sticker","type":"InputDocument"},{"name":"position","type":"int"}],"type":"messages.StickerSet"},{"id":"-2041315650","method":"stickers.addStickerToSet","params":[{"name":"stickerset","type":"InputStickerSet"},{"name":"sticker","type":"InputStickerSetItem"}],"type":"messages.StickerSet"},{"id":"1369162417","method":"messages.uploadMedia","params":[{"name":"peer","type":"InputPeer"},{"name":"media","type":"InputMedia"}],"type":"MessageMedia"},{"id":"1430593449","method":"phone.getCallConfig","params":[],"type":"DataJSON"},{"id":"1124046573","method":"phone.requestCall","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.0?true"},{"name":"user_id","type":"InputUser"},{"name":"random_id","type":"int"},{"name":"g_a_hash","type":"bytes"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"phone.PhoneCall"},{"id":"1003664544","method":"phone.acceptCall","params":[{"name":"peer","type":"InputPhoneCall"},{"name":"g_b","type":"bytes"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"phone.PhoneCall"},{"id":"788404002","method":"phone.confirmCall","params":[{"name":"peer","type":"InputPhoneCall"},{"name":"g_a","type":"bytes"},{"name":"key_fingerprint","type":"long"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"phone.PhoneCall"},{"id":"399855457","method":"phone.receivedCall","params":[{"name":"peer","type":"InputPhoneCall"}],"type":"Bool"},{"id":"-1295269440","method":"phone.discardCall","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.0?true"},{"name":"peer","type":"InputPhoneCall"},{"name":"duration","type":"int"},{"name":"reason","type":"PhoneCallDiscardReason"},{"name":"connection_id","type":"long"}],"type":"Updates"},{"id":"1508562471","method":"phone.setCallRating","params":[{"name":"flags","type":"#"},{"name":"user_initiative","type":"flags.0?true"},{"name":"peer","type":"InputPhoneCall"},{"name":"rating","type":"int"},{"name":"comment","type":"string"}],"type":"Updates"},{"id":"662363518","method":"phone.saveCallDebug","params":[{"name":"peer","type":"InputPhoneCall"},{"name":"debug","type":"DataJSON"}],"type":"Bool"},{"id":"536919235","method":"upload.getCdnFile","params":[{"name":"file_token","type":"bytes"},{"name":"offset","type":"int"},{"name":"limit","type":"int"}],"type":"upload.CdnFile"},{"id":"-1691921240","method":"upload.reuploadCdnFile","params":[{"name":"file_token","type":"bytes"},{"name":"request_token","type":"bytes"}],"type":"Vector"},{"id":"1375900482","method":"help.getCdnConfig","params":[],"type":"CdnConfig"},{"id":"-219008246","method":"langpack.getLangPack","params":[{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"}],"type":"LangPackDifference"},{"id":"-269862909","method":"langpack.getStrings","params":[{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"},{"name":"keys","type":"Vector"}],"type":"Vector"},{"id":"-845657435","method":"langpack.getDifference","params":[{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"},{"name":"from_version","type":"int"}],"type":"LangPackDifference"},{"id":"1120311183","method":"langpack.getLanguages","params":[{"name":"lang_pack","type":"string"}],"type":"Vector"},{"id":"-1763259007","method":"channels.editBanned","params":[{"name":"channel","type":"InputChannel"},{"name":"participant","type":"InputPeer"},{"name":"banned_rights","type":"ChatBannedRights"}],"type":"Updates"},{"id":"870184064","method":"channels.getAdminLog","params":[{"name":"flags","type":"#"},{"name":"channel","type":"InputChannel"},{"name":"q","type":"string"},{"name":"events_filter","type":"flags.0?ChannelAdminLogEventsFilter"},{"name":"admins","type":"flags.1?Vector"},{"name":"max_id","type":"long"},{"name":"min_id","type":"long"},{"name":"limit","type":"int"}],"type":"channels.AdminLogResults"},{"id":"1302676017","method":"upload.getCdnFileHashes","params":[{"name":"file_token","type":"bytes"},{"name":"offset","type":"int"}],"type":"Vector"},{"id":"-914493408","method":"messages.sendScreenshotNotification","params":[{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"int"},{"name":"random_id","type":"long"}],"type":"Updates"},{"id":"-359881479","method":"channels.setStickers","params":[{"name":"channel","type":"InputChannel"},{"name":"stickerset","type":"InputStickerSet"}],"type":"Bool"},{"id":"82946729","method":"messages.getFavedStickers","params":[{"name":"hash","type":"long"}],"type":"messages.FavedStickers"},{"id":"-1174420133","method":"messages.faveSticker","params":[{"name":"id","type":"InputDocument"},{"name":"unfave","type":"Bool"}],"type":"Bool"},{"id":"-357180360","method":"channels.readMessageContents","params":[{"name":"channel","type":"InputChannel"},{"name":"id","type":"Vector"}],"type":"Bool"},{"id":"-2020263951","method":"contacts.resetSaved","params":[],"type":"Bool"},{"id":"1180140658","method":"messages.getUnreadMentions","params":[{"name":"peer","type":"InputPeer"},{"name":"offset_id","type":"int"},{"name":"add_offset","type":"int"},{"name":"limit","type":"int"},{"name":"max_id","type":"int"},{"name":"min_id","type":"int"}],"type":"messages.Messages"},{"id":"-1355375294","method":"channels.deleteHistory","params":[{"name":"channel","type":"InputChannel"},{"name":"max_id","type":"int"}],"type":"Bool"},{"id":"1036054804","method":"help.getRecentMeUrls","params":[{"name":"referer","type":"string"}],"type":"help.RecentMeUrls"},{"id":"-356796084","method":"channels.togglePreHistoryHidden","params":[{"name":"channel","type":"InputChannel"},{"name":"enabled","type":"Bool"}],"type":"Updates"},{"id":"251759059","method":"messages.readMentions","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.AffectedHistory"},{"id":"1881817312","method":"messages.getRecentLocations","params":[{"name":"peer","type":"InputPeer"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"-872345397","method":"messages.sendMultiMedia","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"clear_draft","type":"flags.7?true"},{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"multi_media","type":"Vector"},{"name":"schedule_date","type":"flags.10?int"}],"type":"Updates"},{"id":"1347929239","method":"messages.uploadEncryptedFile","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"file","type":"InputEncryptedFile"}],"type":"EncryptedFile"},{"id":"405695855","method":"account.getWebAuthorizations","params":[],"type":"account.WebAuthorizations"},{"id":"755087855","method":"account.resetWebAuthorization","params":[{"name":"hash","type":"long"}],"type":"Bool"},{"id":"1747789204","method":"account.resetWebAuthorizations","params":[],"type":"Bool"},{"id":"896555914","method":"messages.searchStickerSets","params":[{"name":"flags","type":"#"},{"name":"exclude_featured","type":"flags.0?true"},{"name":"q","type":"string"},{"name":"hash","type":"long"}],"type":"messages.FoundStickerSets"},{"id":"-956147407","method":"upload.getFileHashes","params":[{"name":"location","type":"InputFileLocation"},{"name":"offset","type":"int"}],"type":"Vector"},{"id":"749019089","method":"help.getTermsOfServiceUpdate","params":[],"type":"help.TermsOfServiceUpdate"},{"id":"-294455398","method":"help.acceptTermsOfService","params":[{"name":"id","type":"DataJSON"}],"type":"Bool"},{"id":"-1299661699","method":"account.getAllSecureValues","params":[],"type":"Vector"},{"id":"1936088002","method":"account.getSecureValue","params":[{"name":"types","type":"Vector"}],"type":"Vector"},{"id":"-1986010339","method":"account.saveSecureValue","params":[{"name":"value","type":"InputSecureValue"},{"name":"secure_secret_id","type":"long"}],"type":"SecureValue"},{"id":"-1199522741","method":"account.deleteSecureValue","params":[{"name":"types","type":"Vector"}],"type":"Bool"},{"id":"-1865902923","method":"users.setSecureValueErrors","params":[{"name":"id","type":"InputUser"},{"name":"errors","type":"Vector"}],"type":"Bool"},{"id":"-1456907910","method":"account.getAuthorizationForm","params":[{"name":"bot_id","type":"long"},{"name":"scope","type":"string"},{"name":"public_key","type":"string"}],"type":"account.AuthorizationForm"},{"id":"-202552205","method":"account.acceptAuthorization","params":[{"name":"bot_id","type":"long"},{"name":"scope","type":"string"},{"name":"public_key","type":"string"},{"name":"value_hashes","type":"Vector"},{"name":"credentials","type":"SecureCredentialsEncrypted"}],"type":"Bool"},{"id":"-1516022023","method":"account.sendVerifyPhoneCode","params":[{"name":"phone_number","type":"string"},{"name":"settings","type":"CodeSettings"}],"type":"auth.SentCode"},{"id":"1305716726","method":"account.verifyPhone","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"},{"name":"phone_code","type":"string"}],"type":"Bool"},{"id":"1880182943","method":"account.sendVerifyEmailCode","params":[{"name":"email","type":"string"}],"type":"account.SentEmailCode"},{"id":"-323339813","method":"account.verifyEmail","params":[{"name":"email","type":"string"},{"name":"code","type":"string"}],"type":"Bool"},{"id":"1072547679","method":"help.getDeepLinkInfo","params":[{"name":"path","type":"string"}],"type":"help.DeepLinkInfo"},{"id":"-2098076769","method":"contacts.getSaved","params":[],"type":"Vector"},{"id":"-2092831552","method":"channels.getLeftChannels","params":[{"name":"offset","type":"int"}],"type":"messages.Chats"},{"id":"-262453244","method":"account.initTakeoutSession","params":[{"name":"flags","type":"#"},{"name":"contacts","type":"flags.0?true"},{"name":"message_users","type":"flags.1?true"},{"name":"message_chats","type":"flags.2?true"},{"name":"message_megagroups","type":"flags.3?true"},{"name":"message_channels","type":"flags.4?true"},{"name":"files","type":"flags.5?true"},{"name":"file_max_size","type":"flags.5?int"}],"type":"account.Takeout"},{"id":"489050862","method":"account.finishTakeoutSession","params":[{"name":"flags","type":"#"},{"name":"success","type":"flags.0?true"}],"type":"Bool"},{"id":"486505992","method":"messages.getSplitRanges","params":[],"type":"Vector"},{"id":"911373810","method":"invokeWithMessagesRange","params":[{"name":"range","type":"MessageRange"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-1398145746","method":"invokeWithTakeout","params":[{"name":"takeout_id","type":"long"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-1031349873","method":"messages.markDialogUnread","params":[{"name":"flags","type":"#"},{"name":"unread","type":"flags.0?true"},{"name":"peer","type":"InputDialogPeer"}],"type":"Bool"},{"id":"585256482","method":"messages.getDialogUnreadMarks","params":[],"type":"Vector"},{"id":"-2062238246","method":"contacts.toggleTopPeers","params":[{"name":"enabled","type":"Bool"}],"type":"Bool"},{"id":"2119757468","method":"messages.clearAllDrafts","params":[],"type":"Bool"},{"id":"-1735311088","method":"help.getAppConfig","params":[],"type":"JSONValue"},{"id":"1862465352","method":"help.saveAppLog","params":[{"name":"events","type":"Vector"}],"type":"Bool"},{"id":"-966677240","method":"help.getPassportConfig","params":[{"name":"hash","type":"int"}],"type":"help.PassportConfig"},{"id":"1784243458","method":"langpack.getLanguage","params":[{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"}],"type":"LangPackLanguage"},{"id":"-760547348","method":"messages.updatePinnedMessage","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.0?true"},{"name":"unpin","type":"flags.1?true"},{"name":"pm_oneside","type":"flags.2?true"},{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"}],"type":"Updates"},{"id":"-1881204448","method":"account.confirmPasswordEmail","params":[{"name":"code","type":"string"}],"type":"Bool"},{"id":"2055154197","method":"account.resendPasswordEmail","params":[],"type":"Bool"},{"id":"-1043606090","method":"account.cancelPasswordEmail","params":[],"type":"Bool"},{"id":"-748624084","method":"help.getSupportName","params":[],"type":"help.SupportName"},{"id":"59377875","method":"help.getUserInfo","params":[{"name":"user_id","type":"InputUser"}],"type":"help.UserInfo"},{"id":"1723407216","method":"help.editUserInfo","params":[{"name":"user_id","type":"InputUser"},{"name":"message","type":"string"},{"name":"entities","type":"Vector"}],"type":"help.UserInfo"},{"id":"-1626880216","method":"account.getContactSignUpNotification","params":[],"type":"Bool"},{"id":"-806076575","method":"account.setContactSignUpNotification","params":[{"name":"silent","type":"Bool"}],"type":"Bool"},{"id":"1398240377","method":"account.getNotifyExceptions","params":[{"name":"flags","type":"#"},{"name":"compare_sound","type":"flags.1?true"},{"name":"peer","type":"flags.0?InputNotifyPeer"}],"type":"Updates"},{"id":"283795844","method":"messages.sendVote","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"options","type":"Vector"}],"type":"Updates"},{"id":"1941660731","method":"messages.getPollResults","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"}],"type":"Updates"},{"id":"1848369232","method":"messages.getOnlines","params":[{"name":"peer","type":"InputPeer"}],"type":"ChatOnlines"},{"id":"-554301545","method":"messages.editChatAbout","params":[{"name":"peer","type":"InputPeer"},{"name":"about","type":"string"}],"type":"Bool"},{"id":"-1517917375","method":"messages.editChatDefaultBannedRights","params":[{"name":"peer","type":"InputPeer"},{"name":"banned_rights","type":"ChatBannedRights"}],"type":"Updates"},{"id":"-57811990","method":"account.getWallPaper","params":[{"name":"wallpaper","type":"InputWallPaper"}],"type":"WallPaper"},{"id":"-578472351","method":"account.uploadWallPaper","params":[{"name":"file","type":"InputFile"},{"name":"mime_type","type":"string"},{"name":"settings","type":"WallPaperSettings"}],"type":"WallPaper"},{"id":"1817860919","method":"account.saveWallPaper","params":[{"name":"wallpaper","type":"InputWallPaper"},{"name":"unsave","type":"Bool"},{"name":"settings","type":"WallPaperSettings"}],"type":"Bool"},{"id":"-18000023","method":"account.installWallPaper","params":[{"name":"wallpaper","type":"InputWallPaper"},{"name":"settings","type":"WallPaperSettings"}],"type":"Bool"},{"id":"-1153722364","method":"account.resetWallPapers","params":[],"type":"Bool"},{"id":"1457130303","method":"account.getAutoDownloadSettings","params":[],"type":"account.AutoDownloadSettings"},{"id":"1995661875","method":"account.saveAutoDownloadSettings","params":[{"name":"flags","type":"#"},{"name":"low","type":"flags.0?true"},{"name":"high","type":"flags.1?true"},{"name":"settings","type":"AutoDownloadSettings"}],"type":"Bool"},{"id":"899735650","method":"messages.getEmojiKeywords","params":[{"name":"lang_code","type":"string"}],"type":"EmojiKeywordsDifference"},{"id":"352892591","method":"messages.getEmojiKeywordsDifference","params":[{"name":"lang_code","type":"string"},{"name":"from_version","type":"int"}],"type":"EmojiKeywordsDifference"},{"id":"1318675378","method":"messages.getEmojiKeywordsLanguages","params":[{"name":"lang_codes","type":"Vector"}],"type":"Vector"},{"id":"-709817306","method":"messages.getEmojiURL","params":[{"name":"lang_code","type":"string"}],"type":"EmojiURL"},{"id":"1749536939","method":"folders.editPeerFolders","params":[{"name":"folder_peers","type":"Vector"}],"type":"Updates"},{"id":"472471681","method":"folders.deleteFolder","params":[{"name":"folder_id","type":"int"}],"type":"Updates"},{"id":"1932455680","method":"messages.getSearchCounters","params":[{"name":"peer","type":"InputPeer"},{"name":"filters","type":"Vector"}],"type":"Vector"},{"id":"-170208392","method":"channels.getGroupsForDiscussion","params":[],"type":"messages.Chats"},{"id":"1079520178","method":"channels.setDiscussionGroup","params":[{"name":"broadcast","type":"InputChannel"},{"name":"group","type":"InputChannel"}],"type":"Bool"},{"id":"428848198","method":"messages.requestUrlAuth","params":[{"name":"flags","type":"#"},{"name":"peer","type":"flags.1?InputPeer"},{"name":"msg_id","type":"flags.1?int"},{"name":"button_id","type":"flags.1?int"},{"name":"url","type":"flags.2?string"}],"type":"UrlAuthResult"},{"id":"-1322487515","method":"messages.acceptUrlAuth","params":[{"name":"flags","type":"#"},{"name":"write_allowed","type":"flags.0?true"},{"name":"peer","type":"flags.1?InputPeer"},{"name":"msg_id","type":"flags.1?int"},{"name":"button_id","type":"flags.1?int"},{"name":"url","type":"flags.2?string"}],"type":"UrlAuthResult"},{"id":"1336717624","method":"messages.hidePeerSettingsBar","params":[{"name":"peer","type":"InputPeer"}],"type":"Bool"},{"id":"-386636848","method":"contacts.addContact","params":[{"name":"flags","type":"#"},{"name":"add_phone_privacy_exception","type":"flags.0?true"},{"name":"id","type":"InputUser"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"phone","type":"string"}],"type":"Updates"},{"id":"-130964977","method":"contacts.acceptContact","params":[{"name":"id","type":"InputUser"}],"type":"Updates"},{"id":"-1892102881","method":"channels.editCreator","params":[{"name":"channel","type":"InputChannel"},{"name":"user_id","type":"InputUser"},{"name":"password","type":"InputCheckPasswordSRP"}],"type":"Updates"},{"id":"-750207932","method":"contacts.getLocated","params":[{"name":"flags","type":"#"},{"name":"background","type":"flags.1?true"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"self_expires","type":"flags.0?int"}],"type":"Updates"},{"id":"1491484525","method":"channels.editLocation","params":[{"name":"channel","type":"InputChannel"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"address","type":"string"}],"type":"Bool"},{"id":"-304832784","method":"channels.toggleSlowMode","params":[{"name":"channel","type":"InputChannel"},{"name":"seconds","type":"int"}],"type":"Updates"},{"id":"-183077365","method":"messages.getScheduledHistory","params":[{"name":"peer","type":"InputPeer"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"-1111817116","method":"messages.getScheduledMessages","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"}],"type":"messages.Messages"},{"id":"-1120369398","method":"messages.sendScheduledMessages","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"}],"type":"Updates"},{"id":"1504586518","method":"messages.deleteScheduledMessages","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"}],"type":"Updates"},{"id":"473805619","method":"account.uploadTheme","params":[{"name":"flags","type":"#"},{"name":"file","type":"InputFile"},{"name":"thumb","type":"flags.0?InputFile"},{"name":"file_name","type":"string"},{"name":"mime_type","type":"string"}],"type":"Document"},{"id":"-2077048289","method":"account.createTheme","params":[{"name":"flags","type":"#"},{"name":"slug","type":"string"},{"name":"title","type":"string"},{"name":"document","type":"flags.2?InputDocument"},{"name":"settings","type":"flags.3?InputThemeSettings"}],"type":"Theme"},{"id":"1555261397","method":"account.updateTheme","params":[{"name":"flags","type":"#"},{"name":"format","type":"string"},{"name":"theme","type":"InputTheme"},{"name":"slug","type":"flags.0?string"},{"name":"title","type":"flags.1?string"},{"name":"document","type":"flags.2?InputDocument"},{"name":"settings","type":"flags.3?InputThemeSettings"}],"type":"Theme"},{"id":"-229175188","method":"account.saveTheme","params":[{"name":"theme","type":"InputTheme"},{"name":"unsave","type":"Bool"}],"type":"Bool"},{"id":"2061776695","method":"account.installTheme","params":[{"name":"flags","type":"#"},{"name":"dark","type":"flags.0?true"},{"name":"format","type":"flags.1?string"},{"name":"theme","type":"flags.1?InputTheme"}],"type":"Bool"},{"id":"-1919060949","method":"account.getTheme","params":[{"name":"format","type":"string"},{"name":"theme","type":"InputTheme"},{"name":"document_id","type":"long"}],"type":"Theme"},{"id":"1913054296","method":"account.getThemes","params":[{"name":"format","type":"string"},{"name":"hash","type":"long"}],"type":"account.Themes"},{"id":"-1210022402","method":"auth.exportLoginToken","params":[{"name":"api_id","type":"int"},{"name":"api_hash","type":"string"},{"name":"except_ids","type":"Vector"}],"type":"auth.LoginToken"},{"id":"-1783866140","method":"auth.importLoginToken","params":[{"name":"token","type":"bytes"}],"type":"auth.LoginToken"},{"id":"-392909491","method":"auth.acceptLoginToken","params":[{"name":"token","type":"bytes"}],"type":"Authorization"},{"id":"-1250643605","method":"account.setContentSettings","params":[{"name":"flags","type":"#"},{"name":"sensitive_enabled","type":"flags.0?true"}],"type":"Bool"},{"id":"-1952756306","method":"account.getContentSettings","params":[],"type":"account.ContentSettings"},{"id":"300429806","method":"channels.getInactiveChannels","params":[],"type":"messages.InactiveChats"},{"id":"1705865692","method":"account.getMultiWallPapers","params":[{"name":"wallpapers","type":"Vector"}],"type":"Vector"},{"id":"-1200736242","method":"messages.getPollVotes","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"},{"name":"option","type":"flags.0?bytes"},{"name":"offset","type":"flags.1?string"},{"name":"limit","type":"int"}],"type":"messages.VotesList"},{"id":"-1257951254","method":"messages.toggleStickerSets","params":[{"name":"flags","type":"#"},{"name":"uninstall","type":"flags.0?true"},{"name":"archive","type":"flags.1?true"},{"name":"unarchive","type":"flags.2?true"},{"name":"stickersets","type":"Vector"}],"type":"Bool"},{"id":"779736953","method":"payments.getBankCardData","params":[{"name":"number","type":"string"}],"type":"payments.BankCardData"},{"id":"-241247891","method":"messages.getDialogFilters","params":[],"type":"Vector"},{"id":"-1566780372","method":"messages.getSuggestedDialogFilters","params":[],"type":"Vector"},{"id":"450142282","method":"messages.updateDialogFilter","params":[{"name":"flags","type":"#"},{"name":"id","type":"int"},{"name":"filter","type":"flags.0?DialogFilter"}],"type":"Bool"},{"id":"-983318044","method":"messages.updateDialogFiltersOrder","params":[{"name":"order","type":"Vector"}],"type":"Bool"},{"id":"-1421720550","method":"stats.getBroadcastStats","params":[{"name":"flags","type":"#"},{"name":"dark","type":"flags.0?true"},{"name":"channel","type":"InputChannel"}],"type":"stats.BroadcastStats"},{"id":"1646092192","method":"stats.loadAsyncGraph","params":[{"name":"flags","type":"#"},{"name":"token","type":"string"},{"name":"x","type":"flags.0?long"}],"type":"StatsGraph"},{"id":"-1707717072","method":"stickers.setStickerSetThumb","params":[{"name":"stickerset","type":"InputStickerSet"},{"name":"thumb","type":"InputDocument"}],"type":"messages.StickerSet"},{"id":"85399130","method":"bots.setBotCommands","params":[{"name":"scope","type":"BotCommandScope"},{"name":"lang_code","type":"string"},{"name":"commands","type":"Vector"}],"type":"Bool"},{"id":"2127598753","method":"messages.getOldFeaturedStickers","params":[{"name":"offset","type":"int"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"messages.FeaturedStickers"},{"id":"-1063816159","method":"help.getPromoData","params":[],"type":"help.PromoData"},{"id":"505748629","method":"help.hidePromoData","params":[{"name":"peer","type":"InputPeer"}],"type":"Bool"},{"id":"-8744061","method":"phone.sendSignalingData","params":[{"name":"peer","type":"InputPhoneCall"},{"name":"data","type":"bytes"}],"type":"Bool"},{"id":"-589330937","method":"stats.getMegagroupStats","params":[{"name":"flags","type":"#"},{"name":"dark","type":"flags.0?true"},{"name":"channel","type":"InputChannel"}],"type":"stats.MegagroupStats"},{"id":"-349483786","method":"account.getGlobalPrivacySettings","params":[],"type":"GlobalPrivacySettings"},{"id":"517647042","method":"account.setGlobalPrivacySettings","params":[{"name":"settings","type":"GlobalPrivacySettings"}],"type":"GlobalPrivacySettings"},{"id":"-183649631","method":"help.dismissSuggestion","params":[{"name":"peer","type":"InputPeer"},{"name":"suggestion","type":"string"}],"type":"Bool"},{"id":"1935116200","method":"help.getCountriesList","params":[{"name":"lang_code","type":"string"},{"name":"hash","type":"int"}],"type":"help.CountriesList"},{"id":"584962828","method":"messages.getReplies","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"offset_id","type":"int"},{"name":"offset_date","type":"int"},{"name":"add_offset","type":"int"},{"name":"limit","type":"int"},{"name":"max_id","type":"int"},{"name":"min_id","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"1147761405","method":"messages.getDiscussionMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"}],"type":"messages.DiscussionMessage"},{"id":"-147740172","method":"messages.readDiscussion","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"read_max_id","type":"int"}],"type":"Bool"},{"id":"698914348","method":"contacts.blockFromReplies","params":[{"name":"flags","type":"#"},{"name":"delete_message","type":"flags.0?true"},{"name":"delete_history","type":"flags.1?true"},{"name":"report_spam","type":"flags.2?true"},{"name":"msg_id","type":"int"}],"type":"Updates"},{"id":"1445996571","method":"stats.getMessagePublicForwards","params":[{"name":"channel","type":"InputChannel"},{"name":"msg_id","type":"int"},{"name":"offset_rate","type":"int"},{"name":"offset_peer","type":"InputPeer"},{"name":"offset_id","type":"int"},{"name":"limit","type":"int"}],"type":"messages.Messages"},{"id":"-1226791947","method":"stats.getMessageStats","params":[{"name":"flags","type":"#"},{"name":"dark","type":"flags.0?true"},{"name":"channel","type":"InputChannel"},{"name":"msg_id","type":"int"}],"type":"stats.MessageStats"},{"id":"-265962357","method":"messages.unpinAllMessages","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.AffectedHistory"},{"id":"1221445336","method":"phone.createGroupCall","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"random_id","type":"int"},{"name":"title","type":"flags.0?string"},{"name":"schedule_date","type":"flags.1?int"}],"type":"Updates"},{"id":"-1322057861","method":"phone.joinGroupCall","params":[{"name":"flags","type":"#"},{"name":"muted","type":"flags.0?true"},{"name":"video_stopped","type":"flags.2?true"},{"name":"call","type":"InputGroupCall"},{"name":"join_as","type":"InputPeer"},{"name":"invite_hash","type":"flags.1?string"},{"name":"params","type":"DataJSON"}],"type":"Updates"},{"id":"1342404601","method":"phone.leaveGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"source","type":"int"}],"type":"Updates"},{"id":"2067345760","method":"phone.inviteToGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"users","type":"Vector"}],"type":"Updates"},{"id":"2054648117","method":"phone.discardGroupCall","params":[{"name":"call","type":"InputGroupCall"}],"type":"Updates"},{"id":"1958458429","method":"phone.toggleGroupCallSettings","params":[{"name":"flags","type":"#"},{"name":"reset_invite_hash","type":"flags.1?true"},{"name":"call","type":"InputGroupCall"},{"name":"join_muted","type":"flags.0?Bool"}],"type":"Updates"},{"id":"68699611","method":"phone.getGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"limit","type":"int"}],"type":"phone.GroupCall"},{"id":"-984033109","method":"phone.getGroupParticipants","params":[{"name":"call","type":"InputGroupCall"},{"name":"ids","type":"Vector"},{"name":"sources","type":"Vector"},{"name":"offset","type":"string"},{"name":"limit","type":"int"}],"type":"phone.GroupParticipants"},{"id":"-1248003721","method":"phone.checkGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"sources","type":"Vector"}],"type":"Vector"},{"id":"1540419152","method":"messages.deleteChat","params":[{"name":"chat_id","type":"long"}],"type":"Bool"},{"id":"-104078327","method":"messages.deletePhoneCallHistory","params":[{"name":"flags","type":"#"},{"name":"revoke","type":"flags.0?true"}],"type":"messages.AffectedFoundMessages"},{"id":"1140726259","method":"messages.checkHistoryImport","params":[{"name":"import_head","type":"string"}],"type":"messages.HistoryImportParsed"},{"id":"873008187","method":"messages.initHistoryImport","params":[{"name":"peer","type":"InputPeer"},{"name":"file","type":"InputFile"},{"name":"media_count","type":"int"}],"type":"messages.HistoryImport"},{"id":"713433234","method":"messages.uploadImportedMedia","params":[{"name":"peer","type":"InputPeer"},{"name":"import_id","type":"long"},{"name":"file_name","type":"string"},{"name":"media","type":"InputMedia"}],"type":"MessageMedia"},{"id":"-1271008444","method":"messages.startHistoryImport","params":[{"name":"peer","type":"InputPeer"},{"name":"import_id","type":"long"}],"type":"Bool"},{"id":"-1565154314","method":"messages.getExportedChatInvites","params":[{"name":"flags","type":"#"},{"name":"revoked","type":"flags.3?true"},{"name":"peer","type":"InputPeer"},{"name":"admin_id","type":"InputUser"},{"name":"offset_date","type":"flags.2?int"},{"name":"offset_link","type":"flags.2?string"},{"name":"limit","type":"int"}],"type":"messages.ExportedChatInvites"},{"id":"1937010524","method":"messages.getExportedChatInvite","params":[{"name":"peer","type":"InputPeer"},{"name":"link","type":"string"}],"type":"messages.ExportedChatInvite"},{"id":"48562110","method":"messages.editExportedChatInvite","params":[{"name":"flags","type":"#"},{"name":"revoked","type":"flags.2?true"},{"name":"peer","type":"InputPeer"},{"name":"link","type":"string"},{"name":"expire_date","type":"flags.0?int"},{"name":"usage_limit","type":"flags.1?int"}],"type":"messages.ExportedChatInvite"},{"id":"1452833749","method":"messages.deleteRevokedExportedChatInvites","params":[{"name":"peer","type":"InputPeer"},{"name":"admin_id","type":"InputUser"}],"type":"Bool"},{"id":"-731601877","method":"messages.deleteExportedChatInvite","params":[{"name":"peer","type":"InputPeer"},{"name":"link","type":"string"}],"type":"Bool"},{"id":"958457583","method":"messages.getAdminsWithInvites","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.ChatAdminsWithInvites"},{"id":"654013065","method":"messages.getChatInviteImporters","params":[{"name":"peer","type":"InputPeer"},{"name":"link","type":"string"},{"name":"offset_date","type":"int"},{"name":"offset_user","type":"InputUser"},{"name":"limit","type":"int"}],"type":"messages.ChatInviteImporters"},{"id":"-1207017500","method":"messages.setHistoryTTL","params":[{"name":"peer","type":"InputPeer"},{"name":"period","type":"int"}],"type":"Updates"},{"id":"-91437323","method":"account.reportProfilePhoto","params":[{"name":"peer","type":"InputPeer"},{"name":"photo_id","type":"InputPhoto"},{"name":"reason","type":"ReportReason"},{"name":"message","type":"string"}],"type":"Bool"},{"id":"187239529","method":"channels.convertToGigagroup","params":[{"name":"channel","type":"InputChannel"}],"type":"Updates"},{"id":"1573261059","method":"messages.checkHistoryImportPeer","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.CheckedHistoryImportPeer"},{"id":"-248985848","method":"phone.toggleGroupCallRecord","params":[{"name":"flags","type":"#"},{"name":"start","type":"flags.0?true"},{"name":"video","type":"flags.2?true"},{"name":"call","type":"InputGroupCall"},{"name":"title","type":"flags.1?string"},{"name":"video_portrait","type":"flags.2?Bool"}],"type":"Updates"},{"id":"-1524155713","method":"phone.editGroupCallParticipant","params":[{"name":"flags","type":"#"},{"name":"call","type":"InputGroupCall"},{"name":"participant","type":"InputPeer"},{"name":"muted","type":"flags.0?Bool"},{"name":"volume","type":"flags.1?int"},{"name":"raise_hand","type":"flags.2?Bool"},{"name":"video_stopped","type":"flags.3?Bool"},{"name":"video_paused","type":"flags.4?Bool"},{"name":"presentation_paused","type":"flags.5?Bool"}],"type":"Updates"},{"id":"480685066","method":"phone.editGroupCallTitle","params":[{"name":"call","type":"InputGroupCall"},{"name":"title","type":"string"}],"type":"Updates"},{"id":"-277077702","method":"phone.getGroupCallJoinAs","params":[{"name":"peer","type":"InputPeer"}],"type":"phone.JoinAsPeers"},{"id":"-425040769","method":"phone.exportGroupCallInvite","params":[{"name":"flags","type":"#"},{"name":"can_self_unmute","type":"flags.0?true"},{"name":"call","type":"InputGroupCall"}],"type":"phone.ExportedGroupCallInvite"},{"id":"563885286","method":"phone.toggleGroupCallStartSubscription","params":[{"name":"call","type":"InputGroupCall"},{"name":"subscribed","type":"Bool"}],"type":"Updates"},{"id":"1451287362","method":"phone.startScheduledGroupCall","params":[{"name":"call","type":"InputGroupCall"}],"type":"Updates"},{"id":"1465786252","method":"phone.saveDefaultGroupCallJoinAs","params":[{"name":"peer","type":"InputPeer"},{"name":"join_as","type":"InputPeer"}],"type":"Bool"},{"id":"-873829436","method":"phone.joinGroupCallPresentation","params":[{"name":"call","type":"InputGroupCall"},{"name":"params","type":"DataJSON"}],"type":"Updates"},{"id":"475058500","method":"phone.leaveGroupCallPresentation","params":[{"name":"call","type":"InputGroupCall"}],"type":"Updates"},{"id":"676017721","method":"stickers.checkShortName","params":[{"name":"short_name","type":"string"}],"type":"Bool"},{"id":"1303364867","method":"stickers.suggestShortName","params":[{"name":"title","type":"string"}],"type":"stickers.SuggestedShortName"},{"id":"1032708345","method":"bots.resetBotCommands","params":[{"name":"scope","type":"BotCommandScope"},{"name":"lang_code","type":"string"}],"type":"Bool"},{"id":"-481554986","method":"bots.getBotCommands","params":[{"name":"scope","type":"BotCommandScope"},{"name":"lang_code","type":"string"}],"type":"Vector"},{"id":"-1828139493","method":"account.resetPassword","params":[],"type":"account.ResetPasswordResult"},{"id":"1284770294","method":"account.declinePasswordReset","params":[],"type":"Bool"},{"id":"221691769","method":"auth.checkRecoveryPassword","params":[{"name":"code","type":"string"}],"type":"Bool"},{"id":"-690545285","method":"account.getChatThemes","params":[{"name":"hash","type":"int"}],"type":"account.ChatThemes"},{"id":"-432283329","method":"messages.setChatTheme","params":[{"name":"peer","type":"InputPeer"},{"name":"emoticon","type":"string"}],"type":"Updates"},{"id":"-1095836780","method":"channels.viewSponsoredMessage","params":[{"name":"channel","type":"InputChannel"},{"name":"random_id","type":"bytes"}],"type":"Bool"},{"id":"-333377601","method":"channels.getSponsoredMessages","params":[{"name":"channel","type":"InputChannel"}],"type":"messages.SponsoredMessages"},{"id":"745510839","method":"messages.getMessageReadParticipants","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"}],"type":"Vector"}]} \ No newline at end of file diff --git a/data/core.telegram.org/schema/mtproto-json.html b/data/core.telegram.org/schema/mtproto-json.html deleted file mode 100644 index ceca9f3321..0000000000 --- a/data/core.telegram.org/schema/mtproto-json.html +++ /dev/null @@ -1 +0,0 @@ -{"constructors":[{"id":"481674261","predicate":"vector","params":[],"type":"Vector t"},{"id":"85337187","predicate":"resPQ","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"pq","type":"bytes"},{"name":"server_public_key_fingerprints","type":"Vector"}],"type":"ResPQ"},{"id":"-1443537003","predicate":"p_q_inner_data_dc","params":[{"name":"pq","type":"bytes"},{"name":"p","type":"bytes"},{"name":"q","type":"bytes"},{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"new_nonce","type":"int256"},{"name":"dc","type":"int"}],"type":"P_Q_inner_data"},{"id":"1459478408","predicate":"p_q_inner_data_temp_dc","params":[{"name":"pq","type":"bytes"},{"name":"p","type":"bytes"},{"name":"q","type":"bytes"},{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"new_nonce","type":"int256"},{"name":"dc","type":"int"},{"name":"expires_in","type":"int"}],"type":"P_Q_inner_data"},{"id":"-790100132","predicate":"server_DH_params_ok","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"encrypted_answer","type":"bytes"}],"type":"Server_DH_Params"},{"id":"-1249309254","predicate":"server_DH_inner_data","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"g","type":"int"},{"name":"dh_prime","type":"bytes"},{"name":"g_a","type":"bytes"},{"name":"server_time","type":"int"}],"type":"Server_DH_inner_data"},{"id":"1715713620","predicate":"client_DH_inner_data","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"retry_id","type":"long"},{"name":"g_b","type":"bytes"}],"type":"Client_DH_Inner_Data"},{"id":"1003222836","predicate":"dh_gen_ok","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"new_nonce_hash1","type":"int128"}],"type":"Set_client_DH_params_answer"},{"id":"1188831161","predicate":"dh_gen_retry","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"new_nonce_hash2","type":"int128"}],"type":"Set_client_DH_params_answer"},{"id":"-1499615742","predicate":"dh_gen_fail","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"new_nonce_hash3","type":"int128"}],"type":"Set_client_DH_params_answer"},{"id":"1973679973","predicate":"bind_auth_key_inner","params":[{"name":"nonce","type":"long"},{"name":"temp_auth_key_id","type":"long"},{"name":"perm_auth_key_id","type":"long"},{"name":"temp_session_id","type":"long"},{"name":"expires_at","type":"int"}],"type":"BindAuthKeyInner"},{"id":"-212046591","predicate":"rpc_result","params":[{"name":"req_msg_id","type":"long"},{"name":"result","type":"Object"}],"type":"RpcResult"},{"id":"558156313","predicate":"rpc_error","params":[{"name":"error_code","type":"int"},{"name":"error_message","type":"string"}],"type":"RpcError"},{"id":"1579864942","predicate":"rpc_answer_unknown","params":[],"type":"RpcDropAnswer"},{"id":"-847714938","predicate":"rpc_answer_dropped_running","params":[],"type":"RpcDropAnswer"},{"id":"-1539647305","predicate":"rpc_answer_dropped","params":[{"name":"msg_id","type":"long"},{"name":"seq_no","type":"int"},{"name":"bytes","type":"int"}],"type":"RpcDropAnswer"},{"id":"155834844","predicate":"future_salt","params":[{"name":"valid_since","type":"int"},{"name":"valid_until","type":"int"},{"name":"salt","type":"long"}],"type":"FutureSalt"},{"id":"-1370486635","predicate":"future_salts","params":[{"name":"req_msg_id","type":"long"},{"name":"now","type":"int"},{"name":"salts","type":"vector"}],"type":"FutureSalts"},{"id":"880243653","predicate":"pong","params":[{"name":"msg_id","type":"long"},{"name":"ping_id","type":"long"}],"type":"Pong"},{"id":"-501201412","predicate":"destroy_session_ok","params":[{"name":"session_id","type":"long"}],"type":"DestroySessionRes"},{"id":"1658015945","predicate":"destroy_session_none","params":[{"name":"session_id","type":"long"}],"type":"DestroySessionRes"},{"id":"-1631450872","predicate":"new_session_created","params":[{"name":"first_msg_id","type":"long"},{"name":"unique_id","type":"long"},{"name":"server_salt","type":"long"}],"type":"NewSession"},{"id":"1945237724","predicate":"msg_container","params":[{"name":"messages","type":"vector<%Message>"}],"type":"MessageContainer"},{"id":"1538843921","predicate":"message","params":[{"name":"msg_id","type":"long"},{"name":"seqno","type":"int"},{"name":"bytes","type":"int"},{"name":"body","type":"Object"}],"type":"Message"},{"id":"-530561358","predicate":"msg_copy","params":[{"name":"orig_message","type":"Message"}],"type":"MessageCopy"},{"id":"812830625","predicate":"gzip_packed","params":[{"name":"packed_data","type":"bytes"}],"type":"Object"},{"id":"1658238041","predicate":"msgs_ack","params":[{"name":"msg_ids","type":"Vector"}],"type":"MsgsAck"},{"id":"-1477445615","predicate":"bad_msg_notification","params":[{"name":"bad_msg_id","type":"long"},{"name":"bad_msg_seqno","type":"int"},{"name":"error_code","type":"int"}],"type":"BadMsgNotification"},{"id":"-307542917","predicate":"bad_server_salt","params":[{"name":"bad_msg_id","type":"long"},{"name":"bad_msg_seqno","type":"int"},{"name":"error_code","type":"int"},{"name":"new_server_salt","type":"long"}],"type":"BadMsgNotification"},{"id":"2105940488","predicate":"msg_resend_req","params":[{"name":"msg_ids","type":"Vector"}],"type":"MsgResendReq"},{"id":"-630588590","predicate":"msgs_state_req","params":[{"name":"msg_ids","type":"Vector"}],"type":"MsgsStateReq"},{"id":"81704317","predicate":"msgs_state_info","params":[{"name":"req_msg_id","type":"long"},{"name":"info","type":"bytes"}],"type":"MsgsStateInfo"},{"id":"-1933520591","predicate":"msgs_all_info","params":[{"name":"msg_ids","type":"Vector"},{"name":"info","type":"bytes"}],"type":"MsgsAllInfo"},{"id":"661470918","predicate":"msg_detailed_info","params":[{"name":"msg_id","type":"long"},{"name":"answer_msg_id","type":"long"},{"name":"bytes","type":"int"},{"name":"status","type":"int"}],"type":"MsgDetailedInfo"},{"id":"-2137147681","predicate":"msg_new_detailed_info","params":[{"name":"answer_msg_id","type":"long"},{"name":"bytes","type":"int"},{"name":"status","type":"int"}],"type":"MsgDetailedInfo"},{"id":"-161422892","predicate":"destroy_auth_key_ok","params":[],"type":"DestroyAuthKeyRes"},{"id":"178201177","predicate":"destroy_auth_key_none","params":[],"type":"DestroyAuthKeyRes"},{"id":"-368010477","predicate":"destroy_auth_key_fail","params":[],"type":"DestroyAuthKeyRes"}],"methods":[{"id":"-1099002127","method":"req_pq_multi","params":[{"name":"nonce","type":"int128"}],"type":"ResPQ"},{"id":"-686627650","method":"req_DH_params","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"p","type":"bytes"},{"name":"q","type":"bytes"},{"name":"public_key_fingerprint","type":"long"},{"name":"encrypted_data","type":"bytes"}],"type":"Server_DH_Params"},{"id":"-184262881","method":"set_client_DH_params","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"encrypted_data","type":"bytes"}],"type":"Set_client_DH_params_answer"},{"id":"1491380032","method":"rpc_drop_answer","params":[{"name":"req_msg_id","type":"long"}],"type":"RpcDropAnswer"},{"id":"-1188971260","method":"get_future_salts","params":[{"name":"num","type":"int"}],"type":"FutureSalts"},{"id":"2059302892","method":"ping","params":[{"name":"ping_id","type":"long"}],"type":"Pong"},{"id":"-213746804","method":"ping_delay_disconnect","params":[{"name":"ping_id","type":"long"},{"name":"disconnect_delay","type":"int"}],"type":"Pong"},{"id":"-414113498","method":"destroy_session","params":[{"name":"session_id","type":"long"}],"type":"DestroySessionRes"},{"id":"-1835453025","method":"http_wait","params":[{"name":"max_delay","type":"int"},{"name":"wait_after","type":"int"},{"name":"max_wait","type":"int"}],"type":"HttpWait"},{"id":"-784117408","method":"destroy_auth_key","params":[],"type":"DestroyAuthKeyRes"}]} \ No newline at end of file diff --git a/data/core.telegram.org/schema/mtproto.html b/data/core.telegram.org/schema/mtproto.html deleted file mode 100644 index 74d5a9b3d4..0000000000 --- a/data/core.telegram.org/schema/mtproto.html +++ /dev/null @@ -1,204 +0,0 @@ - - - - - Current MTProto TL-schema - - - - - - - - - - - - - -
- -
-
-
- -

Current MTProto TL-schema

- -

Below you will find the current MTProto TL-schema. More details on TL »

-

See also the detailed schema in JSON »

-


-
int ? = Int;
-long ? = Long;
-double ? = Double;
-string ? = String;
-
-vector {t:Type} # [ t ] = Vector t;
-
-int128 4*[ int ] = Int128;
-int256 8*[ int ] = Int256;
-
-resPQ#05162463 nonce:int128 server_nonce:int128 pq:bytes server_public_key_fingerprints:Vector<long> = ResPQ;
-
-p_q_inner_data_dc#a9f55f95 pq:bytes p:bytes q:bytes nonce:int128 server_nonce:int128 new_nonce:int256 dc:int = P_Q_inner_data;
-p_q_inner_data_temp_dc#56fddf88 pq:bytes p:bytes q:bytes nonce:int128 server_nonce:int128 new_nonce:int256 dc:int expires_in:int = P_Q_inner_data;
-
-server_DH_params_ok#d0e8075c nonce:int128 server_nonce:int128 encrypted_answer:bytes = Server_DH_Params;
-
-server_DH_inner_data#b5890dba nonce:int128 server_nonce:int128 g:int dh_prime:bytes g_a:bytes server_time:int = Server_DH_inner_data;
-
-client_DH_inner_data#6643b654 nonce:int128 server_nonce:int128 retry_id:long g_b:bytes = Client_DH_Inner_Data;
-
-dh_gen_ok#3bcbf734 nonce:int128 server_nonce:int128 new_nonce_hash1:int128 = Set_client_DH_params_answer;
-dh_gen_retry#46dc1fb9 nonce:int128 server_nonce:int128 new_nonce_hash2:int128 = Set_client_DH_params_answer;
-dh_gen_fail#a69dae02 nonce:int128 server_nonce:int128 new_nonce_hash3:int128 = Set_client_DH_params_answer;
-
-bind_auth_key_inner#75a3f765 nonce:long temp_auth_key_id:long perm_auth_key_id:long temp_session_id:long expires_at:int = BindAuthKeyInner;
-
-rpc_result#f35c6d01 req_msg_id:long result:Object = RpcResult;
-rpc_error#2144ca19 error_code:int error_message:string = RpcError;
-
-rpc_answer_unknown#5e2ad36e = RpcDropAnswer;
-rpc_answer_dropped_running#cd78e586 = RpcDropAnswer;
-rpc_answer_dropped#a43ad8b7 msg_id:long seq_no:int bytes:int = RpcDropAnswer;
-
-future_salt#0949d9dc valid_since:int valid_until:int salt:long = FutureSalt;
-future_salts#ae500895 req_msg_id:long now:int salts:vector<future_salt> = FutureSalts;
-
-pong#347773c5 msg_id:long ping_id:long = Pong;
-
-destroy_session_ok#e22045fc session_id:long = DestroySessionRes;
-destroy_session_none#62d350c9 session_id:long = DestroySessionRes;
-
-new_session_created#9ec20908 first_msg_id:long unique_id:long server_salt:long = NewSession;
-
-msg_container#73f1f8dc messages:vector<%Message> = MessageContainer;
-message msg_id:long seqno:int bytes:int body:Object = Message;
-msg_copy#e06046b2 orig_message:Message = MessageCopy;
-
-gzip_packed#3072cfa1 packed_data:bytes = Object;
-
-msgs_ack#62d6b459 msg_ids:Vector<long> = MsgsAck;
-
-bad_msg_notification#a7eff811 bad_msg_id:long bad_msg_seqno:int error_code:int = BadMsgNotification;
-bad_server_salt#edab447b bad_msg_id:long bad_msg_seqno:int error_code:int new_server_salt:long = BadMsgNotification;
-
-msg_resend_req#7d861a08 msg_ids:Vector<long> = MsgResendReq;
-msgs_state_req#da69fb52 msg_ids:Vector<long> = MsgsStateReq;
-msgs_state_info#04deb57d req_msg_id:long info:bytes = MsgsStateInfo;
-msgs_all_info#8cc0d131 msg_ids:Vector<long> info:bytes = MsgsAllInfo;
-msg_detailed_info#276d3ec6 msg_id:long answer_msg_id:long bytes:int status:int = MsgDetailedInfo;
-msg_new_detailed_info#809db6df answer_msg_id:long bytes:int status:int = MsgDetailedInfo;
-
-destroy_auth_key_ok#f660e1d4 = DestroyAuthKeyRes;
-destroy_auth_key_none#0a9f2259 = DestroyAuthKeyRes;
-destroy_auth_key_fail#ea109b13 = DestroyAuthKeyRes;
-
----functions---
-
-req_pq_multi#be7e8ef1 nonce:int128 = ResPQ;
-
-req_DH_params#d712e4be nonce:int128 server_nonce:int128 p:bytes q:bytes public_key_fingerprint:long encrypted_data:bytes = Server_DH_Params;
-
-set_client_DH_params#f5045f1f nonce:int128 server_nonce:int128 encrypted_data:bytes = Set_client_DH_params_answer;
-
-rpc_drop_answer#58e4a740 req_msg_id:long = RpcDropAnswer;
-get_future_salts#b921bd04 num:int = FutureSalts;
-ping#7abe77ec ping_id:long = Pong;
-ping_delay_disconnect#f3427b8c ping_id:long disconnect_delay:int = Pong;
-destroy_session#e7512126 session_id:long = DestroySessionRes;
-
-http_wait#9299359f max_delay:int wait_after:int max_wait:int = HttpWait;
-
-destroy_auth_key#d1435160 = DestroyAuthKeyRes;
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/stickers.html b/data/core.telegram.org/stickers.html deleted file mode 100644 index b1683a7d5b..0000000000 --- a/data/core.telegram.org/stickers.html +++ /dev/null @@ -1,249 +0,0 @@ - - - - - Telegram Stickers - - - - - - - - - - - - - -
- -
-
-
-
-

Telegram Stickers

- -

All users can create, send and share custom artwork using Telegram's open Sticker Platform. Stickers take many forms – from basic images to stunning vector animations.

-

To start building your own custom sets, click below:

- -

Animated Stickers

-

Telegram stickers can move with smooth 60 FPS animations to bring your characters to life in high-resolution.

-
-

Animated stickers use Telegram's unique .TGS format – click here for Video Stickers made in .WEBM format.

-
-

Creating Animated Stickers

-

To create vector animated stickers you will need the following:

-
    -
  1. Any vector graphics editor that allows exporting vector objects to Adobe After Effects to turn them into animations.
  2. -
  3. Adobe After Effects.
  4. -
  5. The Bodymovin-TG plugin, a fork of Bodymovin for Adobe After Effects that can be used to export animations to .TGS, the Telegram animated sticker format.
  6. -
-
-

The Lottie-based .TGS format allows for incredibly detailed stickers that are less than 30 KB in size – six times smaller than the average photo.

-
-

Animated Sticker Requirements

-
    -
  • Sticker/canvas size must be 512х512 pixels.
  • -
  • Sticker objects must not leave the canvas.
  • -
  • Animation length must not exceed 3 seconds.
  • -
  • All animations must be looped.
  • -
  • Sticker size must not exceed 64 KB after rendering in Bodymovin.
  • -
  • All animations must run at 60 Frames Per Second.
  • -
  • You must not use the following Adobe After Effects functionality when animating your stickers: Auto-bezier keys, Expressions, Masks, Layer Effects, Images, Solids, Texts, 3D Layers, Merge Paths, Star Shapes, Gradient Strokes, Repeaters, Time Stretching, Time Remapping, Auto-Oriented Layers.
  • -
-

Uploading Animated Stickers

-

When your stickers are ready, send the /newanimated command to the @Stickers bot – then send it the .TGS files.

-

Your set will need an icon. Icons for animated sticker sets must be 100x100 pixels, with a looped animation not exceeding 3 seconds.

-
-

Video Stickers

-

Video Stickers are built with .WEBM – an open-source format that is compatible with many graphics editors to create high-detail images. Requires Telegram 8.5 or higher.

- - -

Creating Video Stickers

-

To create Video Stickers, you only need editing software that lets you export your project as a .WEBM video file (alpha channel no longer required).

-

Video Sticker Requirements

-
-

See this Encoding .WEBM with VP9 Guide for details

-
-
    -
  • One side of the sticker must be exactly 512 pixels in size – the other side can be 512 pixels or less.
  • -
  • Video duration must not exceed 3 seconds.
  • -
  • Frame rate can be up to 30 FPS.
  • -
  • Video must have a transparent layer (this is no longer required).
  • -
  • Video should be looped for optimal user experience.
  • -
  • Video size should not exceed 256 KB.
  • -
  • Video must be in .WEBM format encoded with the VP9 codec.
  • -
  • Video must have no audio stream.
  • -
-

Uploading Video Stickers

-

Once your stickers are ready, send the /newvideo command to the @Stickers bot – then send it the .WEBM files.

-

Your set will need a .WEBM icon. Icons for video sticker sets must be 100x100 pixels, with a looped animation not exceeding 3 seconds.

-
-

Static Stickers

-

Turn your favorite drawings and memes into packs of images that are easily accessible on any device – no more digging through your gallery.

-

Creating Static Stickers

-

To create static stickers for the Telegram platform, you only need an image editor that lets you export in .PNG or .WEBP format.

-

Static Sticker Requirements

-
    -
  • One side of the sticker must be exactly 512 pixels in size – the other side can be 512 pixels or less.
  • -
  • The image file must be in either .PNG or .WEBP format.
  • -
-
-

Tip: a transparent background, white stroke and black shadow effect will make your sticker stand out.

-
-

Uploading Static Stickers

-

Once your stickers are ready, start a chat with the @Stickers bot and send the command /newpack. Your sticker set can also have a custom icon – a 100x100 pixel image in .PNG or .WEBP format.

-
-

For more info about using the @Stickers bot, click here.

-
-
-

Using the @Stickers Bot

-

Publishing and editing sticker packs is simple and automated, thanks to the @Stickers bot. It can also show you detailed stats for stickers and packs.

-

Publishing a Sticker Pack

-

Once you open the bot, press the Start button or send /start. The bot will reply, describing its different commands. It will walk you through step by step, but here's a quick guide:

-
    -
  • Open the bot menu in the message bar and select the /newpack command to start uploading static stickers. For animated stickers use /newanimated, or /newvideo for video stickers.
  • -
  • Give your sticker pack a name – this name will appear as the title for your pack in the sticker panel.
  • -
  • Send your first sticker file – an image file, .TGS file, or .WEBM file. Using one of the Desktop or Web apps is strongly recommended.
  • -
  • Choose an emoji that corresponds to your sticker – this lets users quickly find it with sticker suggestions.
  • -
  • Continue uploading all your sticker files.
  • -
  • When you're done uploading, send the /publish command.
  • -
  • Set an icon for your pack – static sticker packs can /skip this step, but it is required for animated or video stickers.
  • -
  • Choose a short name for your sticker pack – it will be used to create a shareable link for the pack like t.me/addstickers/HotCherry. Congratulations! Your stickers are ready for the world.
  • -
-
-

After your pack is finished, you can send /start again to see the full list of commands, or use the bot menu to create another pack, edit an existing pack, or see statistics.

-
-

Editing a Sticker Pack

-

Once you've created one or more packs, you can add, edit or replace stickers in your existing sets.

-
    -
  • Use /addsticker if you have more artwork you'd like to add to a set. Choose one of your packs from the list – the upload process is exactly the same as before.
  • -
  • Use /editsticker to change the emoji you assigned to a sticker – select the pack and sticker, or simply send the intended sticker from your panel.
  • -
  • Use /replacesticker if you want to swap out an older sticker for an updated version.
  • -
  • Use /ordersticker to change the order of stickers in your pack. Choose the pack and one of the stickers, then choose another sticker to appear before it (to the left) in the panel.
  • -
  • Use /delsticker to remove a sticker from the pack – you can always use /addsticker to add it again if you change your mind.
  • -
  • Use /seticon to set an icon for your pack or to change the icon. Static sticker packs without a custom icon will use the first sticker as its icon.
  • -
-
-

Edits to your sticker packs may take up to an hour to update for all users.

-
-

Sticker Stats

-

There are a number of commands that let you see statistics for your stickers – here's what they all do:

-
    -
  • /packstats shows how many times your pack was used, installed and removed – both recently and overall.
  • -
  • /stats shows how many times an individual sticker has been sent.
  • -
  • /top shows the most popular stickers from all your packs.
  • -
  • /packtop shows your most popular sticker packs and their individual stats.
  • -
  • /topbypack shows the top stickers from a specific sticker pack.
  • -
  • /packusagetop shows your most popular packs by recent usage.
  • -
-
-

You can filter the results of /top, /packtop, /topbypack and /packusagetop. For example /top 20 would show your top 20 stickers, and /topbypack -5 would show the 5 least popular stickers from a pack.

-
-

Importing Stickers From Other Apps

-

Developers can build apps to automate importing stickers using Telegram’s API. With these tools, users can instantly bring their favorite stickers to Telegram.

-

For Developers

-

As of version 7.8, Telegram apps support a simple API for importing stickers. Developers can use this to build apps or add tools to apps that let users instantly transfer stickers to Telegram – or create custom stickers from photos or videos.

-
-

Click here for more information about developing apps for importing stickers.

-
-

For Users

-

Users can find apps that allow them to import stickers or quickly generate their own. They can also easily publish custom stickers with the @Stickers bot using .PNG, .WEBP or .WEBM files for stickers from other apps.

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/stickers/webm-vp9-encoding.html b/data/core.telegram.org/stickers/webm-vp9-encoding.html deleted file mode 100644 index adb9aa235c..0000000000 --- a/data/core.telegram.org/stickers/webm-vp9-encoding.html +++ /dev/null @@ -1,159 +0,0 @@ - - - - - Encoding Video Stickers with .WEBM and VP9 - - - - - - - - - - - - - -
- -
-
-
-
-

Encoding Video Stickers with .WEBM and VP9

- -

The Video Sticker format allows anyone to easily create high-detail animations that users can send and share instantly in Telegram.

-

Video Sticker Requirements

-
    -
  • Video must be in .WEBM format, up to 30 FPS.
  • -
  • Video must be encoded with the VP9 codec.
  • -
  • Video must have no audio stream.
  • -
  • One side must be 512 pixels in size – the other side can be 512 pixels or less.
  • -
  • Duration must not exceed 3 seconds.
  • -
  • Video must have a transparent layer (this is no longer required).
  • -
  • Video should be looped for optimal user experience.
  • -
  • Video size should not exceed 256 KB after encoding.
  • -
-

Encoding Video Files

-

You can design your animation in your preferred app – but depending on the app’s export settings, you may need an encoding program to create the final file.

-
-

Programs like Handbrake or ffmpeg natively support .WEBM encoding with VP9.

-
-

Encoding with Adobe Media Encoder

-

Adobe’s Media Encoder requires a plug-in to support .WEBM encoding. Here is a modified version of a plug-in by fnord software that you can install to render your video stickers with Media Encoder.

- -

After the plug-in is installed, .WEBM will appear in the list of formats in the Queue tab.

-
-

On macOS, you may need to go to Settings > Security & Privacy to approve installation.

-
-

Render Settings

-

If it’s your first time working with encoding software, here are some tips that might help:

-
    -
  • Make sure to check that VP9 is selected in the codec settings – some apps may default to VP8.
  • -
  • Make sure to remove any audio streams (uncheck ‘Export Audio’ in Adobe programs).
  • -
  • Make sure the frame rate is a constant 30 FPS.
  • -
  • Use Constant Quality and a lower (or lowest) quality setting – size dramatically decreases without affecting fidelity.
  • -
  • In Media Encoder, make sure your Renderer is set to ‘Software Only’.
  • -
  • If your file fails to render, try importing it as a PNG Sequence.
  • -
-
-

After Effects projects integrate directly with Media Encoder via File > Export > Add to Media Encoder Queue.

-
-

Uploading Video Stickers

-

The @Stickers bot lets you quickly publish and manage your sticker packs. Start a chat with it on Telegram and it will walk you through the process. For step-by-step instructions and more information, see this guide.

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/tdlib.html b/data/core.telegram.org/tdlib.html deleted file mode 100644 index a48649c3b4..0000000000 --- a/data/core.telegram.org/tdlib.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - Telegram Database Library - - - - - - - - - - - - - -
- -
-
-
-
-

Telegram Database Library

- -
- -
- -

TDLib (Telegram Database Library) is a cross-platform, fully functional Telegram client. We designed it to help third-party developers create their own custom apps using the Telegram platform.

-
-

Read about TDLib on the Telegram blog »

-
-

TDLib Advantages

-
    -
  • Cross-platform. TDLib can be used on Android, iOS, Windows, macOS, Linux, WebAssembly, FreeBSD, Windows Phone, watchOS, tvOS, Tizen, Cygwin. It should also work on other *nix systems with or without minimal effort.
  • -
  • Multilanguage. TDLib can be easily used with any programming language that is able to execute C functions. Additionally it already has native bindings to Java (using JNI) and C# (using C++/CLI).
  • -
  • Easy to use. TDLib takes care of all network implementation details, encryption and local data storage.
  • -
  • High-performance. In the Telegram Bot API, each TDLib instance handles more than 24,000 active bots simultaneously.
  • -
  • Well-documented. All TDLib API methods and public interfaces are fully documented.
  • -
  • Consistent. TDLib guarantees that all updates will be delivered in the right order.
  • -
  • Reliable. TDLib remains stable on slow and unreliable Internet connections.
  • -
  • Secure: All local data is encrypted using a user-provided encryption key.
  • -
  • Fully-asynchronous. Requests to TDLib don't block each other or anything else, responses will be sent when they are available.
  • -
-
-

Getting started with TDLib »

-
-

Resources

-

TDLib is fully open source, all code is available on GitHub.

-

See also:

- -
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/tdlib/getting-started.html b/data/core.telegram.org/tdlib/getting-started.html deleted file mode 100644 index d5ee3a802d..0000000000 --- a/data/core.telegram.org/tdlib/getting-started.html +++ /dev/null @@ -1,198 +0,0 @@ - - - - - Getting started with TDLib - - - - - - - - - - - - - -
- -
-
-
- -

Getting started with TDLib

- -
- -

TDLib is a fully functional Telegram client which takes care of all networking, local storage and data consistency details. In this tutorial we describe the main concepts understanding of which is required for efficient TDLib usage.

-

TDLib interface

-

In this text, Client means an interface for interaction with a TDLib instance and Application means the program that uses TDLib to interact with Telegram.

-

The main TDLib API is fully-asyncronous. An Application can send a request to TDLib through ClientManager.send method and receive a response asynchronously through the ClientManager.receive method when it becomes available. The exact naming of these methods and the way in which requests are matched with responses is different for different TDLib interfaces, but the concept as a whole remains the same. For example, in TDLib JSON interface these methods are called td_send and td_receive, and their @extra field must be used to match requests with the corresponding responses.

-

In a high-level interface used by an Application the matching of responses with corresponding requests is often automated and transformed by some wrapper into a call to a continuation, a callback, a Promise or a Future to simplify the handling of responses.

-

Aside from responses to requests, an Application receives a lot of important data through incoming updates. Updates are used to pass new data from TDLib to the Application and often control the behavior of the Application, leaving no chance to implement something wrong. The correct handling of updates is crucial for creating an Application that is efficient and works correctly.

-
-

You can find a list of all available TDLib API methods in our web-documentation. You can also find the descriptions of all available TDLib methods and classes in the TDLIB API scheme.

-

TDLib can be used from any programming language. You can find a lot of examples of TDLib-based frameworks in various programming languages in our examples section.

-
-

TDLib glossary

-

This section describes the basic notions required for understanding the TDLib API. If you have used the TDLib-based Telegram Bot API most of them should be already familiar to you.

-

Telegram is a messenger, so the main object is a message. Each message belongs to some chat and has a unique identifier within that chat. Messages inside a chat must be sorted by that identifier. Telegram supports many different kinds of messages, so a message can have many different kinds of message content. Currently there are more than 45 different kinds of message content, for example messageText for text messages, messagePhoto for photos, or messageScreenshotTaken for notifications about screenshots taken by the other party.

-

A Telegram user is called user. Each user has a unique identifier and a first name, and can also have an optional last name, username and profile photo among other useful fields. Bot is a special type of user which can be controlled through the Telegram Bot API.

-

Each chat has members, i.e. users that immediately receive all messages sent to the chat. Currently there are 6 possible chat member statuses which describe different rights and restrictions a user can have in a chat, ranging from the owner of the chat who has more rights in the chat than any other user, to a user banned in the chat who is banned in the chat and can't return to it by self or even view chat messages, even if the chat is public.

-

As noted earlier, each message belongs to a chat. Currently there are 4 different types of chats on Telegram:

-
    -
  • Private chats are ordinary one-to-one chats with another user (or with oneself in the case of the special “Saved messages” chat).
  • -
  • Basic groups are basic groups with 0-200 members. Every basic group member has their own copy of the message history, so new basic group members may not see older messages (unless another user forwards their own copy to them).
  • -
  • Supergroups are groups with up to 200000 members who share a common message history, so new supergroup members can see all the previously sent messages (unless this is explicitly forbidden by the chat creator). There are special kinds of supergroups, called broadcast groups and channels, which can have an unlimited number of members and where only the chat creator and some chat administrators can write. All other chat members can only read messages in channel and broadcast group chats.
  • -
  • Secret chats are end-to-end encrypted one-to-one chats with another user, available only on the device which was used to initiate and accept the chat.
  • -
-

Each chat has a unique identifier, a title and an optional chat photo. Chats comprise sorted lists shown to the user, position in which is determined, roughly speaking, by the time of latest activity. The correct order of chats in chat lists is maintained by TDLib, so the Application only needs to listen to updates that change the chat.positions field and sort all chats by the pair (position.order, chat.id) in a given position.list.

-

Messages, chat photos and many other objects can have a file inside of them. Each file has an identifier and may be available locally on a local storage or remotely on a cloud server. A file can be usually downloaded to the local storage or uploaded to Telegram cloud servers.

-

Messages with media content like photos or videos can have a short accompanying text called caption. The texts of text messages and media captions can contain fragments, which must be formatted in some unusual way. These fragments are called text entities and the combination of a text and its entities are referred together as a formatted text.

-

TDLib sends a lot of important data to the Application through updates. For example, if there is a user unknown to the Application, or some data about a user has changed, then TDLib immediately sends an updateUser to the Application.

-
-

You can find list of all currently available updates here »

-
-

User authorization

-

Authorization is an example of a behavior, which is controlled by TDLib through updates. Whenever an action is required to proceed with user authorization, the Application receives an updateAuthorizationState with the description of the current AuthorizationState. The Application only needs to handle this update appropriately to correctly implement user authorization.

-

The first authorization state received by the Application is always of the type authorizationStateWaitTdlibParameters. When it is received, the Application must provide parameters for TDLib initialization by calling the setTdlibParameters method. In this method the Application will need to specify, among other parameters:

-
    -
  • api_id — Application identifier for accessing the Telegram API, which can be obtained at https://my.telegram.org.
  • -
  • api_hash — Hash of the Application identifier for accessing the Telegram API, which can be obtained at https://my.telegram.org.
  • -
  • database_directory — The path to the directory on the local disk where the TDLib database is to be stored; must point to a writable directory.
  • -
  • use_message_database — If set to true, the library will maintain a local cache of chats and messages.
  • -
  • use_secret_chats — If set to true, support for secret chats will be enabled.
  • -
  • system_language_code — IETF language tag of the user's operating system language, like “en-GB”.
  • -
  • device_model — Model of the device the Application is being run on, like “iPhone Z”.
  • -
-

After call to setTdlibParameters in case of success Application will receive updateAuthorizationState with new state and just needs to handle that update, nothing should be done explicitly. If setTdlibParameters fails, then authorization state is not changed and the Application must try to handle the current authorization state again.

-

The second received authorization state is always authorizationStateWaitEncryptionKey. When it is received, the database encryption key must be provided through a call to checkDatabaseEncryptionKey. For most mobile apps, you can provide an empty database encryption key here (more info). If user isn't authorized yet, then some of authorizationStateWaitPhoneNumber, authorizationStateWaitCode, authorizationStateWaitRegistration and authorizationStateWaitPassword authorization states may be received. After completing these authorization steps, the Application will receive authorizationStateReady, meaning that authorization was successful and ordinary requests can be sent now.

-
-

You can find complete examples of user authorization in our Java and C# examples.

-
-

Sending a message

-

To send any kind of message, the Application needs to call the method sendMessage providing a chat identifier and the content of the message to be sent. For example, the Application can send a text message using inputMessageText class as input message content, a photo using inputMessagePhoto, or a location using inputMessageLocation. The Application can use inputFileLocal as InputFile in these objects to send a local file from the local storage.

-
-

You can find examples of sending a text message in our Java and C# examples.

-
-

Handling updates

-

All updates and responses to requests must be handled in the order they are received. Here is a list of the most important updates and how they must be handled:

-
    -
  • updateAuthorizationState — The handling of this update is essential for correct user authorization.
  • -
  • updateNewChat — This update is received whenever a new chat is discovered. This update is guaranteed to come before the chat identifier is returned to the Application. So, whenever an Application receives a chat_id, it never needs to use a getChat request to receive the chat object. Instead it must maintain a cache of chats received through this update and take all the necessary data about chats from this cache.
  • -
  • updateUser — This update is received whenever a new user has been discovered or some data about a known user has changed. This update is guaranteed to come before the user identifier is returned to the Application. So, whenever an Application receives a user_id, it never needs to use the getUser request to receive the user object. Instead it must maintain a cache of users received through this update and take all the necessary data about users from this cache.
  • -
  • updateBasicGroup — This update is received whenever a new basic group has been discovered or some data about a known basic group has changed. This update is guaranteed to come before the basic group identifier is returned to the Application. So, whenever an Application receives a basic_group_id, it never needs to use the getBasicGroup request to receive the basicGroup object. Instead it must maintain a cache of basic groups received through this update and take all the necessary data about basic groups from this cache.
  • -
  • updateSupergroup — This update is received whenever a new supergroup has been discovered or some data about a known supergroup has changed. This update is guaranteed to come before the supergroup identifier is returned to the Application. So, whenever an Application receives a supergroup_id, it never needs to use the getSupergroup request to receive the supergroup object. Instead it must maintain a cache of supergroups received through this update and take all the necessary data about supergroups from this cache.
  • -
  • updateSecretChat — This update is received whenever a new secret chat has been discovered or some data about a known secret chat has changed. This update is guaranteed to come before the secret chat identifier is returned to the Application. So, whenever an Application receives a secret_chat_id, it never needs to use the getSecretChat request to receive the secret chat object. Instead it must maintain a cache of secret chats received through this update and take all the necessary data about secret chats from this cache.
  • -
  • updateNewMessage — This update is received whenever a new message is added to a chat.
  • -
  • updateMessageSendSucceeded — This update is received whenever a message is successfully sent.
  • -
  • updateMessageContent — This update is received whenever the content of a message changes.
  • -
  • updateFile — This update is received whenever information about a file is updated. The handling of this update is essential to follow the progress of files being downloaded or uploaded.
  • -
  • updateChatTitle, updateChatPhoto, updateChatPermissions, updateChatLastMessage, updateChatPosition, updateChatReadInbox, updateChatReadOutbox, updateChatActionBar, updateChatDraftMessage, updateChatMessageSender, updateChatMessageTtl, updateChatNotificationSettings, updateChatPendingJoinRequests, updateChatReplyMarkup, updateChatTheme, updateChatUnreadMentionCount, updateChatVideoChat, updateChatDefaultDisableNotification, updateChatHasProtectedContent, updateChatHasScheduledMessages, updateChatIsBlocked, updateChatIsMarkedAsUnread — These updates are received whenever some information about a chat changes, the chats cache must be updated accordingly
  • -
-
-

For a full list of currently available updates see the documentation for the Update class.

-

You can find an example of correct handling of some updates in our Java example.

-
-

Getting the lists of chats

-

Currently there are 3 different types of chat lists:
- Main chat list.
- Archive chat list.
- A folder chat list.

-

The positions of chats in chat lists are managed by TDLib, so the Application only needs to listen to updates that change the chat.positions field, maintain the list of all chats, sorted by the pair (position.order, chat.id) in descending order, and call loadChats only if more chats are needed. For optimal performance, the number of loaded chats is chosen by TDLib and can be smaller than the specified limit. If the Application needs more chats, it must send another loadChats request.

-
-

You can find an example of retrieving the Main chat list in our Java example.

-
-

Getting chat messages

-

The Application can use the method getChatHistory to get messages in a chat. The messages will be returned in the reverse chronological order (i.e., in descending order of message_id). The Application can pass from_message_id == 0 to get messages from the last message. To get more messages than can be returned in one response, the Application needs to pass the identifier of the last message it has received as from_message_id to next request. For optimal performance, the number of the returned messages is chosen by TDLib and can be smaller than the specified limit. If the Application needs more messages, it needs to adjust the from_message_id parameter and repeat the request.

-
- -
- -
-
- -
- - - - - - - - diff --git a/data/core.telegram.org/tdlib/notification-api.html b/data/core.telegram.org/tdlib/notification-api.html deleted file mode 100644 index f2baabbdb3..0000000000 --- a/data/core.telegram.org/tdlib/notification-api.html +++ /dev/null @@ -1,210 +0,0 @@ - - - - - Notification API - - - - - - - - - - - - - -
- -
-
-
-
-

Notification API

- -

This article describes the TDLib Notification API introduced in TDLib 1.4.0.

-

Notification API overview

-

TDLib takes care of everything that is related to handling notifications (as usually, except for how exactly the notifications will be shown to the user). TDLib controls when notifications are shown to the user, when they are edited and removed, guarantees consistency of notifications with the database state and persistence of active notifications between client restarts.

-

All notifications shown to the user are combined into notification groups. For example, notifications about ordinary messages from the one chat belong to one notification group. This grouping is done automatically by TDLib based on message content and the user's notification settings. Currently, there are 4 different notification group types:

-
    -
  • Messages notification groups contain notifications with ordinary unread messages from a chat.
  • -
  • Mentions notification groups contain notifications with unread mentions of the current user, replies to their messages, and notifications about pinned messages in a chat.
  • -
  • SecretChat notification groups contain a single notification about creating a new secret chat.
  • -
  • Calls notification groups contain notifications about received calls in a chat.
  • -
-

TDLib ensures that the number of notification groups shown to the user any given moment is limited by the value of the notification_group_count_max option and that the number of active notifications, shown to the user in a notification group at any given time, is limited by the value of the notification_group_size_max option. Whenever the number of notification groups with active notifications exceeds notification_group_count_max, TDLib sends an update hiding all notifications from the oldest group. If subsequently all notifications are hidden in some other group, that first group can be silently brought back by an update from TDLib. Similarly, whenever the number of active notifications in a group exceeds notification_group_size_max, TDLib sends an update hiding the oldest notifications in the group. If subsequently some newer notifications are removed from the group, older notifications can be silently brought back by an update from TDLib.

-

To enable the TDLib Notificaition API you need to set option notification_group_count_max to a positive value, to disable the Notification API you can change the option value back to 0 or set the option value to empty.

-

Every notification group has a unique ID, which is a persistent small integer number, assigned consequently from 1. The client should not assume that the group‘s type and other fields are fixed, because TDLib may reuse the notification group ID whenever it’s known that the group will never be used again in the future. Every notification belongs to a notification group and has a globally unique ID, which is a persistent small integer number, assigned consequently from 1. Notification IDs are never reused and can be used together with their notification group ID to uniquely identify a notification. Within a notification group, notifications must be shown in the order defined by their IDs. If notification grouping isn't available in your operating system, the existence of notification groups can be safely ignored and notifications can be handled separately just by their unique ID.

-

Currently, there are 4 different kinds of notifications:

-
    -
  • NewMessage notifications contain the full information about a new incoming message received from the server. They may be located in Messages and Mentions notification groups.
  • -
  • NewPushMessage notifications contain information about a new incoming message received in a push notification. They contain only partial data about the message and will be replaced by NewMessage notifications as soon as the client downloads the necessary data. They may be located in Messages and Mentions notification groups.
  • -
  • NewSecretChat notifications inform about creating a new secret chat. Only one will be located in each SecretChat notification group. The group may be reused as soon as the notification is removed.
  • -
  • NewCall notifications contain information about a new incoming call. They are located in a Calls notification group. The group may be reused as soon as the notifications are removed.
  • -
-

Messages from new push message notifications will not be shown in the chat message list, but their message identifiers are known and they can be replied to and used in ViewMessages calls anyway.

-

Handling Notification API updates

-

Notification API introduced 4 new updates from TDLib, namely updateActiveNotifications, updateNotificationGroup, updateNotification and updateHavePendingNotifications.

-

If Notification API is enabled, the client receives an updateActiveNotifications update on startup, containing all notifications that are to be shown to the user. The client needs to synchronize the list of notifications that is shown to the user with the list received in updateActiveNotifications and save information about all active notifications in memory, because subsequent updates will contain only changes to the list of active notifications.

-

Whenever a notification is added to a group or is removed from a group, TDLib sends an updateNotificationGroup update to the client. Aside from the list of added notifications and list of identifiers of removed notifications, the update contains full information about the new type of the notification group, the identifier of the chat to which all notifications in the group now belong, the identifier of the chat the notification settings of which must be used to show the notification, a flag determining whether the notification must be shown with or without sound and the new total count of unread notifications in the group. Be aware that the total count of unread notifications in a group can be higher than the number of active notifications. Also note that some old notifications can be added through updateNotificationGroup when newer notifications are removed, so the client must ensure the correct notification order based on notification identifiers. Whenever possible, updateNotificationGroup updates for a group are combined into a single update, so the client can apply the changes together. TDLib also controls the delay before notifications are shown to the user in order to give them a chance to read the messages from a different device before the notification is shown, therefore the updates should be processed on the client side immediately without any additional delays.

-

Whenever an active notification is changed, TDLib sends an updateNotification update to the client. The update contains new content of the notification. The client should be ready to handle the change of notification type, for example, from NewPushMessage to NewMessage.

-

Whenever there are some received but delayed notifications or there can be some yet unreceived notifications because of unavailable network connection to the Telegram servers, TDLib informs the client about that via updateHavePendingNotifications update. Client is supposed to keep the application running in order to receive all delayed notifications. If there is no possibility to keep the application running, the client can close the TDLib instance in order to immediately receive all delayed notification updates.

-

TDLib tries to ensure that whenever a notification about a pinned message is sent, the pinned message is already available locally in the memory, so the client can use a new request getMessageLocally to get the pinned message. Also, updateNotification will be sent whenever pinned message is changed, despite that the notification itself wasn't changed.

-

Customizing the Notification API

-

The client controls the maximum number of active notification groups by using the option notification_group_count_max. This option's value defaults to 0, i.e. there are no active notification groups and the Notification API is effectively disabled. Any integer value between 0 and 25 can be used as the value of the option. Values above 25 are not allowed because most operating systems will not show so many notification groups anyway.

-

The client also controls the maximum number of active notifications in a group by using the option notification_group_size_max. This option's value defaults to 10 and can be set to any integer value between 1 and 25. Values above 25 are not allowed, because most operating systems will not show so many notifications in a group anyway.

-

The user may choose to show pinned messages or mentions among ordinary messages in the Messages notification group instead of the Mentions notification group and choose to not apply notification settings from the sender's private chat to them. This can be done on a per chat basis or for the whole chats notification scope via the new options disable_pinned_message_notifications and disable_mention_notifications which were added to chatNotificationSettings and scopeNotificationSettings classes.

-

Handling push notifications

-

In order to support multiple accounts in one app, the method registerDevice now returns a globally unique identifier of the push notification subscription. This identifier can be used to match a push notification with the corresponding account and process the notification only by the account for which the notification was sent.

-

Whenever a push notification is received, the client needs to call the synchronous method getPushReceiverId with the payload of the push notification. The method will return a globally unique identifier of the push notification subscription (aka push receiver ID), which can be used to find the TDLib instance which needs to be launched and used to process the push notification. If the method returns 0 as a push receiver ID, then the push notification should be processed by all clients (this usually happens when there is only one client).

-

To process a notification, the method processPushNotification needs to be called in the TDLib instance (or instances) found by push receiver ID. This method can be called before authorization and its execution will be automatically postponed until TDLib initialization. The method returns the result only after all updates caused by the push notification have been sent and the TDLib instance can be safely closed. If the method returns an error with the code 406, then the push notification is known to be unsupported and connection to the server is required to fetch new data. If any other error is returned, an error occurred while processing the push notification, i.e. the notification payload has failed to decrypt or parse. In that case, connection to the server isn't required, but there can be new notifications there. After a successful response from processPushNotification the TDLib instance can be immediately closed in order to reduce battery usage. Alternatively, the client can wait for an updateHavePendingNotifications update telling that there are no more delayed or unreceived notifications.

-

Android and iOS clients can opt-in to receive end-to-end encrypted push notifications via a Firebase Cloud Messaging or Apple Push Notification service VoIP notifications while subscribing to push notifications through registerDevice method. In case of Firebase Cloud Messaging, if end-to-end encrypted push notifications are disabled, push notifications are sent without content, so there no notifications of the type NewPushMessage will be created, the client will always need to connect to Telegram servers to download new messages whenever a push notification is received.

-

Examples of push notification payloads, which are accepted by TDLib:

-
{
-  "date": 1234567890,
-  "data": {
-    "custom": {
-      "msg_id": "1234567",
-      "from_id": "12345678",
-      "mtpeer": {
-        "ah": "-1234567",
-        "ph": {
-          "volume_id": "987654321",
-          "local_id": "98765",
-          "secret": "998877665544332211",
-          "file_reference": "ABCDEFGHIJKLMNOPQRSTUVWXYZ",
-          "dc_id": 6,
-          "_": "fileLocation"
-        }
-      }
-    },
-    "badge": "239",
-    "loc_key": "MESSAGE_TEXT",
-    "loc_args": [
-      "First name Last name",
-      "qwerty"
-    ],
-    "line1": "First name Last name",
-    "line2": "qwerty",
-    "random_id": 728931540,
-    "text": "First name Last name: qwerty",
-    "system": "Windows 10.0.20573.1"
-  }
-}
-{
-  "google.sent_time": 1234567890123,
-  "p": "jdTXkJnEMUTK6R82AB-55bLA3U_RB-2K-CLDz7mWp7ckjMIfnCoHEcm710SkN"
-}
-{
-  "date": 1234567890,
-  "loc_key": "CHAT_MESSAGE_TEXT",
-  "loc_args": [
-    "First name Last name",
-    "Chat title",
-    "qwerty"
-  ],
-  "custom": {
-    "msg_id": "1234567",
-    "channel_id": "56781234",
-    "chat_from_id": "12345678",
-    "mention": "1"
-  },
-  "badge": "239"
-}
-

Users removing active notifications

-

There are two methods for removing notifications from the list of active notifications when they are hidden by the user. If the user removes a single notification, it can be removed by calling the method removeNotification. If the user dismisses the whole notification group, this can be achieved using the method removeNotificationGroup. Removed notifications will never return to the list of active notifications, but can be still counted in the total count of unread notifications of the group.

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/tdlib/options.html b/data/core.telegram.org/tdlib/options.html deleted file mode 100644 index b7af629b05..0000000000 --- a/data/core.telegram.org/tdlib/options.html +++ /dev/null @@ -1,501 +0,0 @@ - - - - - TDLib options - - - - - - - - - - - - - -
- -
-
-
- -

TDLib options

- -

TDLib has many options that affect the behavior of the library. Each option has a name and a value. Value may be of one of the following types:

- - - - - - - - - - - - - - - - - - - - - - - -
Type of valueDefault valueValue range
Integer064-bit integer
BooleanfalseTrue or false
StringAny Unicode string
-

List of options supported by TDLib

-

Options not mentioned in this list may be safely ignored.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeWritableDescription
always_parse_markdownBooleanYesIf true, text entities will be automatically parsed in all inputMessageText objects
archive_and_mute_new_chats_from_unknown_usersBooleanYesIf true, new chats from non-contacts will be automatically archived and muted. The option can be set only if the option “can_archive_and_mute_new_chats_from_unknown_users” is true. getOption needs to be called explicitly to fetch the latest value of the option, changed from another device
disable_animated_emojiBooleanYesIf true, animated emoji will be disabled and shown as plain emoji
disable_contact_registered_notificationsBooleanYesIf true, notifications about the user's contacts who have joined Telegram will be disabled. User will still receive the corresponding message in the private chat. getOption needs to be called explicitly to fetch the latest value of the option, changed from another device
disable_persistent_network_statisticsBooleanYesIf true, persistent network statistics will be disabled, which significantly reduces disk usage
disable_sent_scheduled_message_notificationsBooleanYesIf true, notifications about outgoing scheduled messages that were sent will be disabled
disable_time_adjustment_protectionBooleanYesIf true, protection from external time adjustment will be disabled, which significantly reduces disk usage
disable_top_chatsBooleanYesIf true, support for top chats and statistics collection is disabled
ignore_background_updatesBooleanYesIf true, allows to skip all updates received while the TDLib instance was not running. The option does nothing if the database or secret chats are used
ignore_default_disable_notificationBooleanYesIf true, the disable_notification value specified in the request will be always used instead of the default value
ignore_inline_thumbnailsBooleanYesIf true, prevents file thumbnails sent by the server along with messages from being saved on the disk
ignore_platform_restrictionsBooleanYesIf true, chat and message restrictions specific to the currently used operating system will be ignored
ignore_sensitive_content_restrictionsBooleanYesIf true, sensitive content will be shown on all user devices. getOption needs to be called explicitly to fetch the latest value of the option, changed from another device
is_location_visibleBooleanYesIf true, other users will be allowed to see the current user's location. getOption needs to be called explicitly to fetch the latest value of the option, changed from another device
language_pack_database_pathStringYesPath to a database for storing language pack strings, so that this database can be shared between different accounts. By default, language pack strings are stored only in memory. Changes of value of this option will be applied only after TDLib restart, so it should be set before call to setTdlibParameters.
language_pack_idStringYesIdentifier of the currently used language pack from the current localization target
localization_targetStringYesName for the current localization target (currently supported: “android”, “android_x”, “ios”, “macos” and “tdesktop”)
message_unload_delayIntegerYesThe maximum time messages are stored in memory before they are unloaded, 60-86400; in seconds. Defaults to 60 for users and 1800 for bots
notification_group_count_maxIntegerYesMaximum number of notification groups to be shown simultaneously, 0-25
notification_group_size_maxIntegerYesMaximum number of simultaneously shown notifications in a group, 1-25. Defaults to 10
onlineBooleanYesOnline status of the current user
prefer_ipv6BooleanYesIf true, IPv6 addresses will be preferred over IPv4 addresses
use_pfsBooleanYesIf true, Perfect Forward Secrecy will be enabled for interaction with the Telegram servers for cloud chats
use_quick_ackBooleanYesIf true, quick acknowledgement will be enabled for outgoing messages
use_storage_optimizerBooleanYesIf true, the background storage optimizer will be enabled
utc_time_offsetIntegerYesA UTC time offset used for splitting messages by days. The option is reset automatically on each TDLib instance launch, so it needs to be set manually only if the time offset is changed during execution.
animation_search_bot_usernameStringNoUsername of a bot which can be used in inline mode for animations search
authentication_tokenStringNoAn authentication token to be used on subsequent authorizations and received when logging out
authorization_dateIntegerNoPoint in time (Unix timestamp) when authorization was received
basic_group_size_maxIntegerNoMaximum number of members in a basic group
call_connect_timeout_msIntegerNoMaximum time to wait for call connection creation to be passed to libtgvoip
call_packet_timeout_msIntegerNoMaximum time to wait for call packet delivery to be passed to libtgvoip
can_archive_and_mute_new_chats_from_unknown_usersBooleanNoIf true, the option “archive_and_mute_new_chats_from_unknown_users” can be changed
can_ignore_sensitive_content_restrictionsBooleanNoIf true, the option “ignore_sensitive_content_restrictions” can be changed
channel_bot_user_idIntegerNoIdentifier of the bot which is shown as the sender of messages sent on behalf of channels when viewed from an outdated client
enabled_proxy_idIntegerNoIdentifier of the enabled proxy
expect_blockingBooleanNoIf true, access to Telegram is likely blocked for the user
favorite_stickers_limitIntegerNoMaximum number of favorite stickers
forwarded_message_count_maxIntegerNoMaximum number of forwarded messages per one request
group_anonymous_bot_user_idIntegerNoIdentifier of the bot which is shown as the sender of anonymous messages in groups when viewed from an outdated client
message_caption_length_maxIntegerNoMaximum length of a message caption
message_text_length_maxIntegerNoMaximum length of a message text
my_idIntegerNoIdentifier of the current user
pinned_archived_chat_count_maxIntegerNoMaximum number of pinned cloud chats in the Archive chat list. The same amount of secret chats can be pinned locally
pinned_chat_count_maxIntegerNoMaximum number of pinned cloud chats in the Main chat list. The same amount of secret chats can be pinned locally
photo_search_bot_usernameStringNoUsername of a bot which can be used in inline mode for photos search
replies_bot_chat_idIntegerNoIdentifier of the @replies bot
suggested_language_pack_idStringNoIdentifier of the language pack, suggested for the user by the server
suggested_video_note_audio_bitrateStringNoSuggested bit rate for audio encoding in video notes
suggested_video_note_lengthStringNoSuggested width and height of the video in video notes
suggested_video_note_video_bitrateStringNoSuggested bit rate for video encoding in video notes
supergroup_size_maxIntegerNoMaximum number of members in a supergroup
t_me_urlStringNoCurrent value of t.me URL, i.e. https://t.me/
telegram_service_notifications_chat_idIntegerNoIdentifier of the Telegram Service Notifications chat
test_modeBooleanNoIf true, the test environment is being used instead of the production environment
unix_timeIntegerNoAn estimation of the current Unix timestamp. The option will not be updated automatically unless the difference between the previous estimation and the locally available monotonic clocks changes significantly
venue_search_bot_usernameStringNoUsername of a bot which can be used in inline mode for venues search
versionStringNoTDLib version. This options is guaranteed to come before all other updates since TDLib 1.4.0
-

Additionally any option beginning with 'x' or 'X' is writeable and can be safely used by the application to persistently store some small amount of data.

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/themes.html b/data/core.telegram.org/themes.html deleted file mode 100644 index bf98edc07e..0000000000 --- a/data/core.telegram.org/themes.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - Creating Custom Cloud Themes - - - - - - - - - - - - - -
- -
-
-
-
-

Creating Custom Cloud Themes

- -

Official Telegram apps support custom cloud themes as of version 5.11. Everyone is welcome to create and share their themes.

-

Creating a theme

-

You can use the Online Theme Editor (use a VPN if it is blocked in your country) to create new Telegram themes from scratch or edit existing ones. Simply log in with your Telegram account and pick a platform to start editing the relevant theme file – or import an existing theme.

-
    -
  • Set a name for your theme using the name attribute
  • -
  • Set colors for elements using hex codes or the color picker
  • -
  • Press ‘Save and apply theme’ to push changes to all users of your theme
  • -
-

Checking your theme in-app

-

Once you have saved a theme for the first time, Telegram will send you a message with its sharing link. Open the link in the app to switch to your theme.

-

You can always switch to your theme in Settings > Chat Settings. On iOS and MacOS native app – Settings > Appearance.

-

Publishing your theme

-

Each theme has a t.me/addtheme link which people can use to switch to your theme. You can choose a beautiful short link (e.g., https://t.me/addtheme/desert) by changing the shortname attribute. If you add support for multiple platforms, the same link can be used for setting your theme on all of them.

-

Updating your theme

-

Your theme gets updated automatically for all its users whenever you save and apply changes.

-

Including a chat background

-

Your themes can include a custom wallpaper. To do this, simply go to Settings > Chat Settings > Chat Background. On iOS and MacOS native app – Settings > Appearance > Chat Background.

-

Open any background and tap the sharing button in the top right corner, then copy its t.me/bg/... link. In the theme file, set this link as the value of the wallpaper attribute.

-

For Telegram Desktop, if you want to make the background tiled, add ?mode=tiled at the end of the link. For example:

-
wallpaper: t.me/bg/-jI7lnO3DFABAAAA1vXcFaZP_Vo?mode=tiled
-

Creating themes in-app

-

If you prefer a more WYSIWYG approach, try creating themes using the in-app tools for customizing appearance. Telegram for Android and Telegram Desktop have advanced in-app theme editors. Telegram for iOS and MacOS allow choosing a custom accent color from the color wheel and a background, then saving the result as a custom theme.

-

Once you have saved a new theme in any of the apps, it also becomes accessible in the online editor.

-

Read more

- -
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/AccountDaysTTL.html b/data/core.telegram.org/type/AccountDaysTTL.html deleted file mode 100644 index de81618068..0000000000 --- a/data/core.telegram.org/type/AccountDaysTTL.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - AccountDaysTTL - - - - - - - - - - - - - -
- -
-
-
- -

AccountDaysTTL

- -

Time-to-live of current account

-

- -
-
accountDaysTTL#b8d0afdf days:int = AccountDaysTTL;
-
----functions---
-
-account.getAccountTTL#8fc711d = AccountDaysTTL;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
accountDaysTTLTime to live in days of the current account
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getAccountTTLGet days to live of account
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Audio.html b/data/core.telegram.org/type/Audio.html deleted file mode 100644 index fcca48232a..0000000000 --- a/data/core.telegram.org/type/Audio.html +++ /dev/null @@ -1,128 +0,0 @@ - - - - - Audio - - - - - - - - - - - - - -
- -
-
-
- -

Audio

- -

Audio file.

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Authorization.html b/data/core.telegram.org/type/Authorization.html deleted file mode 100644 index 4cc237363b..0000000000 --- a/data/core.telegram.org/type/Authorization.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Authorization - - - - - - - - - - - - - -
- -
-
-
- -

Authorization

- -

Represents a logged-in session

-

- -
-
authorization#ad01d61d flags:# current:flags.0?true official_app:flags.1?true password_pending:flags.2?true encrypted_requests_disabled:flags.3?true call_requests_disabled:flags.4?true hash:long device_model:string platform:string system_version:string api_id:int app_name:string app_version:string date_created:int date_active:int ip:string country:string region:string = Authorization;
-
----functions---
-
-auth.acceptLoginToken#e894ad4d token:bytes = Authorization;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
authorizationLogged-in session
-

Methods

- - - - - - - - - - - - - -
MethodDescription
auth.acceptLoginTokenLogin via QR code
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/AutoDownloadSettings.html b/data/core.telegram.org/type/AutoDownloadSettings.html deleted file mode 100644 index 2df1842091..0000000000 --- a/data/core.telegram.org/type/AutoDownloadSettings.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - AutoDownloadSettings - - - - - - - - - - - - - -
- -
-
-
- -

AutoDownloadSettings

- -

Media autodownload settings

-

- -
-
autoDownloadSettings#e04232f3 flags:# disabled:flags.0?true video_preload_large:flags.1?true audio_preload_next:flags.2?true phonecalls_less_data:flags.3?true photo_size_max:int video_size_max:int file_size_max:int video_upload_maxbitrate:int = AutoDownloadSettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
autoDownloadSettingsAutodownload settings
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/BankCardOpenUrl.html b/data/core.telegram.org/type/BankCardOpenUrl.html deleted file mode 100644 index 054636976f..0000000000 --- a/data/core.telegram.org/type/BankCardOpenUrl.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - BankCardOpenUrl - - - - - - - - - - - - - -
- -
-
-
- -

BankCardOpenUrl

- -

Credit card info URL provided by the bank

-

- -
-
bankCardOpenUrl#f568028a url:string name:string = BankCardOpenUrl;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
bankCardOpenUrlCredit card info URL provided by the bank
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/BaseTheme.html b/data/core.telegram.org/type/BaseTheme.html deleted file mode 100644 index e548570717..0000000000 --- a/data/core.telegram.org/type/BaseTheme.html +++ /dev/null @@ -1,163 +0,0 @@ - - - - - BaseTheme - - - - - - - - - - - - - -
- -
-
-
- -

BaseTheme

- -

Basic theme settings

-

- -
-
baseThemeClassic#c3a12462 = BaseTheme;
-baseThemeDay#fbd81688 = BaseTheme;
-baseThemeNight#b7b31ea8 = BaseTheme;
-baseThemeTinted#6d5f77ee = BaseTheme;
-baseThemeArctic#5b11125a = BaseTheme;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
baseThemeClassicClassic theme
baseThemeDayDay theme
baseThemeNightNight theme
baseThemeTintedTinted theme
baseThemeArcticArctic theme
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Bool.html b/data/core.telegram.org/type/Bool.html deleted file mode 100644 index 0f2612e8b6..0000000000 --- a/data/core.telegram.org/type/Bool.html +++ /dev/null @@ -1,718 +0,0 @@ - - - - - Bool - - - - - - - - - - - - - -
- -
-
-
- -

Bool

- -

Boolean type.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
-
----functions---
-
-auth.logOut#5717da40 = Bool;
-auth.resetAuthorizations#9fab0d1a = Bool;
-auth.bindTempAuthKey#cdd42a05 perm_auth_key_id:long nonce:long expires_at:int encrypted_message:bytes = Bool;
-auth.cancelCode#1f040578 phone_number:string phone_code_hash:string = Bool;
-auth.dropTempAuthKeys#8e48a188 except_auth_keys:Vector<long> = Bool;
-auth.checkRecoveryPassword#d36bf79 code:string = Bool;
-
-account.registerDevice#ec86017a flags:# no_muted:flags.0?true token_type:int token:string app_sandbox:Bool secret:bytes other_uids:Vector<long> = Bool;
-account.unregisterDevice#6a0d3206 token_type:int token:string other_uids:Vector<long> = Bool;
-account.updateNotifySettings#84be5b93 peer:InputNotifyPeer settings:InputPeerNotifySettings = Bool;
-account.resetNotifySettings#db7e1747 = Bool;
-account.updateStatus#6628562c offline:Bool = Bool;
-account.reportPeer#c5ba3d86 peer:InputPeer reason:ReportReason message:string = Bool;
-account.checkUsername#2714d86c username:string = Bool;
-account.deleteAccount#418d4e0b reason:string = Bool;
-account.setAccountTTL#2442485e ttl:AccountDaysTTL = Bool;
-account.updateDeviceLocked#38df3532 period:int = Bool;
-account.resetAuthorization#df77f3bc hash:long = Bool;
-account.updatePasswordSettings#a59b102f password:InputCheckPasswordSRP new_settings:account.PasswordInputSettings = Bool;
-account.confirmPhone#5f2178c3 phone_code_hash:string phone_code:string = Bool;
-account.resetWebAuthorization#2d01b9ef hash:long = Bool;
-account.resetWebAuthorizations#682d2594 = Bool;
-account.deleteSecureValue#b880bc4b types:Vector<SecureValueType> = Bool;
-account.acceptAuthorization#f3ed4c73 bot_id:long scope:string public_key:string value_hashes:Vector<SecureValueHash> credentials:SecureCredentialsEncrypted = Bool;
-account.verifyPhone#4dd3a7f6 phone_number:string phone_code_hash:string phone_code:string = Bool;
-account.verifyEmail#ecba39db email:string code:string = Bool;
-account.finishTakeoutSession#1d2652ee flags:# success:flags.0?true = Bool;
-account.confirmPasswordEmail#8fdf1920 code:string = Bool;
-account.resendPasswordEmail#7a7f2a15 = Bool;
-account.cancelPasswordEmail#c1cbd5b6 = Bool;
-account.getContactSignUpNotification#9f07c728 = Bool;
-account.setContactSignUpNotification#cff43f61 silent:Bool = Bool;
-account.saveWallPaper#6c5a5b37 wallpaper:InputWallPaper unsave:Bool settings:WallPaperSettings = Bool;
-account.installWallPaper#feed5769 wallpaper:InputWallPaper settings:WallPaperSettings = Bool;
-account.resetWallPapers#bb3b9804 = Bool;
-account.saveAutoDownloadSettings#76f36233 flags:# low:flags.0?true high:flags.1?true settings:AutoDownloadSettings = Bool;
-account.saveTheme#f257106c theme:InputTheme unsave:Bool = Bool;
-account.installTheme#7ae43737 flags:# dark:flags.0?true format:flags.1?string theme:flags.1?InputTheme = Bool;
-account.setContentSettings#b574b16b flags:# sensitive_enabled:flags.0?true = Bool;
-account.reportProfilePhoto#fa8cc6f5 peer:InputPeer photo_id:InputPhoto reason:ReportReason message:string = Bool;
-account.declinePasswordReset#4c9409f6 = Bool;
-
-contacts.deleteByPhones#1013fd9e phones:Vector<string> = Bool;
-contacts.block#68cc1411 id:InputPeer = Bool;
-contacts.unblock#bea65d50 id:InputPeer = Bool;
-contacts.resetTopPeerRating#1ae373ac category:TopPeerCategory peer:InputPeer = Bool;
-contacts.resetSaved#879537f1 = Bool;
-contacts.toggleTopPeers#8514bdda enabled:Bool = Bool;
-
-messages.setTyping#58943ee2 flags:# peer:InputPeer top_msg_id:flags.0?int action:SendMessageAction = Bool;
-messages.reportSpam#cf1592db peer:InputPeer = Bool;
-messages.report#8953ab4e peer:InputPeer id:Vector<int> reason:ReportReason message:string = Bool;
-messages.discardEncryption#f393aea0 flags:# delete_history:flags.0?true chat_id:int = Bool;
-messages.setEncryptedTyping#791451ed peer:InputEncryptedChat typing:Bool = Bool;
-messages.readEncryptedHistory#7f4b690a peer:InputEncryptedChat max_date:int = Bool;
-messages.reportEncryptedSpam#4b0c8c0f peer:InputEncryptedChat = Bool;
-messages.uninstallStickerSet#f96e55de stickerset:InputStickerSet = Bool;
-messages.editChatAdmin#a85bd1c2 chat_id:long user_id:InputUser is_admin:Bool = Bool;
-messages.reorderStickerSets#78337739 flags:# masks:flags.0?true order:Vector<long> = Bool;
-messages.saveGif#327a30cb id:InputDocument unsave:Bool = Bool;
-messages.setInlineBotResults#eb5ea206 flags:# gallery:flags.0?true private:flags.1?true query_id:long results:Vector<InputBotInlineResult> cache_time:int next_offset:flags.2?string switch_pm:flags.3?InlineBotSwitchPM = Bool;
-messages.editInlineBotMessage#83557dba flags:# no_webpage:flags.1?true id:InputBotInlineMessageID message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> = Bool;
-messages.setBotCallbackAnswer#d58f130a flags:# alert:flags.1?true query_id:long message:flags.0?string url:flags.2?string cache_time:int = Bool;
-messages.saveDraft#bc39e14b flags:# no_webpage:flags.1?true reply_to_msg_id:flags.0?int peer:InputPeer message:string entities:flags.3?Vector<MessageEntity> = Bool;
-messages.readFeaturedStickers#5b118126 id:Vector<long> = Bool;
-messages.saveRecentSticker#392718f8 flags:# attached:flags.0?true id:InputDocument unsave:Bool = Bool;
-messages.clearRecentStickers#8999602d flags:# attached:flags.0?true = Bool;
-messages.setInlineGameScore#15ad9f64 flags:# edit_message:flags.0?true force:flags.1?true id:InputBotInlineMessageID user_id:InputUser score:int = Bool;
-messages.toggleDialogPin#a731e257 flags:# pinned:flags.0?true peer:InputDialogPeer = Bool;
-messages.reorderPinnedDialogs#3b1adf37 flags:# force:flags.0?true folder_id:int order:Vector<InputDialogPeer> = Bool;
-messages.setBotShippingResults#e5f672fa flags:# query_id:long error:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = Bool;
-messages.setBotPrecheckoutResults#9c2dd95 flags:# success:flags.1?true query_id:long error:flags.0?string = Bool;
-messages.faveSticker#b9ffc55b id:InputDocument unfave:Bool = Bool;
-messages.markDialogUnread#c286d98f flags:# unread:flags.0?true peer:InputDialogPeer = Bool;
-messages.clearAllDrafts#7e58ee9c = Bool;
-messages.editChatAbout#def60797 peer:InputPeer about:string = Bool;
-messages.hidePeerSettingsBar#4facb138 peer:InputPeer = Bool;
-messages.toggleStickerSets#b5052fea flags:# uninstall:flags.0?true archive:flags.1?true unarchive:flags.2?true stickersets:Vector<InputStickerSet> = Bool;
-messages.updateDialogFilter#1ad4a04a flags:# id:int filter:flags.0?DialogFilter = Bool;
-messages.updateDialogFiltersOrder#c563c1e4 order:Vector<int> = Bool;
-messages.readDiscussion#f731a9f4 peer:InputPeer msg_id:int read_max_id:int = Bool;
-messages.deleteChat#5bd0ee50 chat_id:long = Bool;
-messages.startHistoryImport#b43df344 peer:InputPeer import_id:long = Bool;
-messages.deleteRevokedExportedChatInvites#56987bd5 peer:InputPeer admin_id:InputUser = Bool;
-messages.deleteExportedChatInvite#d464a42b peer:InputPeer link:string = Bool;
-
-upload.saveFilePart#b304a621 file_id:long file_part:int bytes:bytes = Bool;
-upload.saveBigFilePart#de7b673d file_id:long file_part:int file_total_parts:int bytes:bytes = Bool;
-
-channels.readHistory#cc104937 channel:InputChannel max_id:int = Bool;
-channels.reportSpam#fe087810 channel:InputChannel user_id:InputUser id:Vector<int> = Bool;
-channels.checkUsername#10e6bd2c channel:InputChannel username:string = Bool;
-channels.updateUsername#3514b3de channel:InputChannel username:string = Bool;
-channels.setStickers#ea8ca4f9 channel:InputChannel stickerset:InputStickerSet = Bool;
-channels.readMessageContents#eab5dc38 channel:InputChannel id:Vector<int> = Bool;
-channels.deleteHistory#af369d42 channel:InputChannel max_id:int = Bool;
-channels.setDiscussionGroup#40582bb2 broadcast:InputChannel group:InputChannel = Bool;
-channels.editLocation#58e63f6d channel:InputChannel geo_point:InputGeoPoint address:string = Bool;
-channels.viewSponsoredMessage#beaedb94 channel:InputChannel random_id:bytes = Bool;
-
-help.setBotUpdatesStatus#ec22cfcd pending_updates_count:int message:string = Bool;
-help.acceptTermsOfService#ee72f79a id:DataJSON = Bool;
-help.saveAppLog#6f02f748 events:Vector<InputAppEvent> = Bool;
-help.hidePromoData#1e251c95 peer:InputPeer = Bool;
-help.dismissSuggestion#f50dbaa1 peer:InputPeer suggestion:string = Bool;
-
-bots.answerWebhookJSONQuery#e6213f4d query_id:long data:DataJSON = Bool;
-bots.setBotCommands#517165a scope:BotCommandScope lang_code:string commands:Vector<BotCommand> = Bool;
-bots.resetBotCommands#3d8de0f9 scope:BotCommandScope lang_code:string = Bool;
-
-payments.clearSavedInfo#d83d70c1 flags:# credentials:flags.0?true info:flags.1?true = Bool;
-
-phone.receivedCall#17d54f61 peer:InputPhoneCall = Bool;
-phone.saveCallDebug#277add7e peer:InputPhoneCall debug:DataJSON = Bool;
-phone.sendSignalingData#ff7a9383 peer:InputPhoneCall data:bytes = Bool;
-phone.saveDefaultGroupCallJoinAs#575e1f8c peer:InputPeer join_as:InputPeer = Bool;
-
-users.setSecureValueErrors#90c894b5 id:InputUser errors:Vector<SecureValueError> = Bool;
-
-stickers.checkShortName#284b3639 short_name:string = Bool;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
boolFalseConstructor may be interpreted as a booleanfalse value.
boolTrueThe constructor can be interpreted as a booleantrue value.
-

Methods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
MethodDescription
auth.logOutLogs out the user.
auth.resetAuthorizationsTerminates all user's authorized sessions except for the current one.

After calling this method it is necessary to reregister the current device using the method account.registerDevice
auth.bindTempAuthKeyBinds a temporary authorization key temp_auth_key_id to the permanent authorization key perm_auth_key_id. Each permanent key may only be bound to one temporary key at a time, binding a new temporary key overwrites the previous one.

For more information, see Perfect Forward Secrecy.
account.registerDeviceRegister device to receive PUSH notifications
account.unregisterDeviceDeletes a device by its token, stops sending PUSH-notifications to it.
account.updateNotifySettingsEdits notification settings from a given user/group, from all users/all groups.
account.resetNotifySettingsResets all notification settings from users and groups.
account.updateStatusUpdates online user status.
account.reportPeerReport a peer for violation of telegram's Terms of Service
contacts.deleteByPhonesDelete contacts by phone number
contacts.blockAdds the user to the blacklist.
contacts.unblockDeletes the user from the blacklist.
messages.setTypingSends a current user typing event (see SendMessageAction for all event types) to a conversation partner or group.
messages.reportSpamReport a new incoming chat for spam, if the peer settings of the chat allow us to do that
messages.reportReport a message in a chat for violation of telegram's Terms of Service
upload.saveFilePartSaves a part of file for futher sending to one of the methods.
messages.discardEncryptionCancels a request for creation and/or delete info on secret chat.
messages.setEncryptedTypingSend typing event by the current user to a secret chat.
messages.readEncryptedHistoryMarks message history within a secret chat as read.
messages.reportEncryptedSpamReport a secret chat for spam
upload.saveBigFilePartSaves a part of a large file (over 10Mb in size) to be later passed to one of the methods.
account.checkUsernameValidates a username and checks availability.
account.deleteAccountDelete the user's account from the telegram servers. Can be used, for example, to delete the account of a user that provided the login code, but forgot the 2FA password and no recovery method is configured.
account.setAccountTTLSet account self-destruction period
account.updateDeviceLockedWhen client-side passcode lock feature is enabled, will not show message texts in incoming PUSH notifications.
account.resetAuthorizationLog out an active authorized session by it hash
account.updatePasswordSettingsSet a new 2FA password
messages.uninstallStickerSetUninstall a stickerset
channels.readHistoryMark channel/supergroup history as read
channels.reportSpamReports some messages from a user in a supergroup as spam; requires administrator rights in the supergroup
channels.checkUsernameCheck if a username is free and can be assigned to a channel/supergroup
channels.updateUsernameChange the username of a supergroup/channel
messages.editChatAdminMake a user admin in a legacy group.
messages.reorderStickerSetsReorder installed stickersets
messages.saveGifAdd GIF to saved gifs list
messages.setInlineBotResultsAnswer an inline query, for bots only
auth.cancelCodeCancel the login verification code
messages.editInlineBotMessageEdit an inline bot message
messages.setBotCallbackAnswerSet the callback answer to a user button press (bots only)
contacts.resetTopPeerRatingReset rating of top peer
messages.saveDraftSave a message draft associated to a chat.
messages.readFeaturedStickersMark new featured stickers as read
messages.saveRecentStickerAdd/remove sticker from recent stickers list
messages.clearRecentStickersClear recent stickers
account.confirmPhoneConfirm a phone number to cancel account deletion, for more info click here »
auth.dropTempAuthKeysDelete all temporary authorization keys except for the ones specified
messages.setInlineGameScoreUse this method to set the score of the specified user in a game sent as an inline message (bots only).
help.setBotUpdatesStatusInforms the server about the number of pending bot updates if they haven't been processed for a long time; for bots only
messages.toggleDialogPinPin/unpin a dialog
messages.reorderPinnedDialogsReorder pinned dialogs
bots.answerWebhookJSONQueryAnswers a custom query; for bots only
payments.clearSavedInfoClear saved payment information
messages.setBotShippingResultsIf you sent an invoice requesting a shipping address and the parameter is_flexible was specified, the bot will receive an updateBotShippingQuery update. Use this method to reply to shipping queries.
messages.setBotPrecheckoutResultsOnce the user has confirmed their payment and shipping details, the bot receives an updateBotPrecheckoutQuery update.
Use this method to respond to such pre-checkout queries.
Note: Telegram must receive an answer within 10 seconds after the pre-checkout query was sent.
phone.receivedCallOptional: notify the server that the user is currently busy in a call: this will automatically refuse all incoming phone calls until the current phone call is ended.
phone.saveCallDebugSend phone call debug data to server
channels.setStickersAssociate a stickerset to the supergroup
messages.faveStickerMark a sticker as favorite
channels.readMessageContentsMark channel/supergroup message contents as read
contacts.resetSavedDelete saved contacts
channels.deleteHistoryDelete the history of a supergroup
account.resetWebAuthorizationLog out an active web telegram login session
account.resetWebAuthorizationsReset all active web telegram login sessions
help.acceptTermsOfServiceAccept the new terms of service
account.deleteSecureValueDelete stored telegram passport value
users.setSecureValueErrorsSet secure passport value errors for a user
account.acceptAuthorizationSends a Telegram Passport authorization form, effectively sharing data with the service
account.verifyPhoneVerify a phone number for telegram passport.
account.verifyEmailVerify an email address for telegram passport.
account.finishTakeoutSessionFinish account takeout session
messages.markDialogUnreadManually mark dialog as unread
contacts.toggleTopPeersEnable/disable top peers
messages.clearAllDraftsClear all drafts.
help.saveAppLogSaves logs of application on the server.
account.confirmPasswordEmailVerify an email to use as 2FA recovery method.
account.resendPasswordEmailResend the code to verify an email to use as 2FA recovery method.
account.cancelPasswordEmailCancel the code that was sent to verify an email to use as 2FA recovery method.
account.getContactSignUpNotificationWhether the user will receive notifications when contacts sign up
account.setContactSignUpNotificationToggle contact sign up notifications
messages.editChatAboutEdit the description of a group/supergroup/channel.
account.saveWallPaperInstall/uninstall wallpaper
account.installWallPaperInstall wallpaper
account.resetWallPapersDelete installed wallpapers
account.saveAutoDownloadSettingsChange media autodownload settings
channels.setDiscussionGroupAssociate a group to a channel as discussion group for that channel
messages.hidePeerSettingsBarShould be called after the user hides the report spam/add as contact bar of a new chat, effectively prevents the user from executing the actions specified in the peer's settings.
channels.editLocationEdit location of geogroup
account.saveThemeSave a theme
account.installThemeInstall a theme
account.setContentSettingsSet sensitive content settings (for viewing or hiding NSFW content)
messages.toggleStickerSetsApply changes to multiple stickersets
messages.updateDialogFilterUpdate folder
messages.updateDialogFiltersOrderReorder folders
bots.setBotCommandsSet bot command list
help.hidePromoDataHide MTProxy/Public Service Announcement information
phone.sendSignalingDataSend VoIP signaling data
help.dismissSuggestionDismiss a suggestion
messages.readDiscussionMark a channel discussion as read
messages.deleteChatDelete a chat
messages.startHistoryImportComplete the history import process, importing all messages into the chat.
To be called only after initializing the import with messages.initHistoryImport and uploading all files using messages.uploadImportedMedia.
messages.deleteRevokedExportedChatInvitesDelete all revoked chat invites
messages.deleteExportedChatInviteDelete a chat invite
account.reportProfilePhotoReport a profile photo of a dialog
phone.saveDefaultGroupCallJoinAsSet the default peer that will be used to join a group call in a specific dialog.
stickers.checkShortNameCheck whether the given short name is available
bots.resetBotCommandsClear bot commands for the specified bot scope and language code
account.declinePasswordResetAbort a pending 2FA password reset
auth.checkRecoveryPasswordCheck if the recovery code sent using auth.requestPasswordRecovery is valid, before passing it to auth.recoverPassword.
channels.viewSponsoredMessageMark a specific sponsored message as read
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/BotCommand.html b/data/core.telegram.org/type/BotCommand.html deleted file mode 100644 index 7c27fc5d35..0000000000 --- a/data/core.telegram.org/type/BotCommand.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - BotCommand - - - - - - - - - - - - - -
- -
-
-
- -

BotCommand

- -

Describes a bot command that can be used in a chat

-

- -
-
botCommand#c27ac8c7 command:string description:string = BotCommand;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
botCommandDescribes a bot command that can be used in a chat
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/BotCommandScope.html b/data/core.telegram.org/type/BotCommandScope.html deleted file mode 100644 index a263d67cb5..0000000000 --- a/data/core.telegram.org/type/BotCommandScope.html +++ /dev/null @@ -1,176 +0,0 @@ - - - - - BotCommandScope - - - - - - - - - - - - - -
- -
-
-
- -

BotCommandScope

- -

Represents a scope where the bot commands, specified using bots.setBotCommands will be valid.

-

- -
-
botCommandScopeDefault#2f6cb2ab = BotCommandScope;
-botCommandScopeUsers#3c4f04d8 = BotCommandScope;
-botCommandScopeChats#6fe1a881 = BotCommandScope;
-botCommandScopeChatAdmins#b9aa606a = BotCommandScope;
-botCommandScopePeer#db9d897d peer:InputPeer = BotCommandScope;
-botCommandScopePeerAdmins#3fd863d1 peer:InputPeer = BotCommandScope;
-botCommandScopePeerUser#a1321f3 peer:InputPeer user_id:InputUser = BotCommandScope;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
botCommandScopeDefaultThe commands will be valid in all chats
botCommandScopeUsersThe specified bot commands will only be valid in all private chats with users.
botCommandScopeChatsThe specified bot commands will be valid in all groups and supergroups
botCommandScopeChatAdminsThe specified bot commands will be valid only for chat administrators, in all groups and supergroups.
botCommandScopePeerThe specified bot commands will be valid only in a specific dialog
botCommandScopePeerAdminsThe specified bot commands will be valid for all admins of the specified group or supergroup.
botCommandScopePeerUserThe specified bot commands will be valid only for a specific user in the specified chat
-

Related pages

-

bots.setBotCommands

-

Set bot command list

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/BotInlineMessage.html b/data/core.telegram.org/type/BotInlineMessage.html deleted file mode 100644 index 316feda9a8..0000000000 --- a/data/core.telegram.org/type/BotInlineMessage.html +++ /dev/null @@ -1,168 +0,0 @@ - - - - - BotInlineMessage - - - - - - - - - - - - - -
- -
-
-
- -

BotInlineMessage

- -

Inline message

-

- -
-
botInlineMessageMediaAuto#764cf810 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-botInlineMessageText#8c7f65e2 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-botInlineMessageMediaGeo#51846fd flags:# geo:GeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-botInlineMessageMediaVenue#8a86659c flags:# geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-botInlineMessageMediaContact#18d1cdc2 flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-botInlineMessageMediaInvoice#354a9b09 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument currency:string total_amount:long reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
botInlineMessageMediaAutoSend whatever media is attached to the botInlineMediaResult
botInlineMessageTextSend a simple text message
botInlineMessageMediaGeoSend a geolocation
botInlineMessageMediaVenueSend a venue
botInlineMessageMediaContactSend a contact
botInlineMessageMediaInvoiceSend an invoice
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/BotInlineResult.html b/data/core.telegram.org/type/BotInlineResult.html deleted file mode 100644 index e9e7f7738d..0000000000 --- a/data/core.telegram.org/type/BotInlineResult.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - BotInlineResult - - - - - - - - - - - - - -
- -
-
-
- -

BotInlineResult

- -

Results of an inline query

-

- -
-
botInlineResult#11965f3a flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?WebDocument content:flags.5?WebDocument send_message:BotInlineMessage = BotInlineResult;
-botInlineMediaResult#17db940b flags:# id:string type:string photo:flags.0?Photo document:flags.1?Document title:flags.2?string description:flags.3?string send_message:BotInlineMessage = BotInlineResult;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
botInlineResultGeneric result
botInlineMediaResultMedia result
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/CdnConfig.html b/data/core.telegram.org/type/CdnConfig.html deleted file mode 100644 index 416fe83f25..0000000000 --- a/data/core.telegram.org/type/CdnConfig.html +++ /dev/null @@ -1,164 +0,0 @@ - - - - - CdnConfig - - - - - - - - - - - - - -
- -
-
-
- -

CdnConfig

- -

Configuration for CDN file downloads.

-

- -
-
cdnConfig#5725e40a public_keys:Vector<CdnPublicKey> = CdnConfig;
-
----functions---
-
-help.getCdnConfig#52029342 = CdnConfig;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
cdnConfigConfiguration for CDN file downloads.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getCdnConfigGet configuration for CDN file downloads.
-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/CdnPublicKey.html b/data/core.telegram.org/type/CdnPublicKey.html deleted file mode 100644 index 6ccb82085f..0000000000 --- a/data/core.telegram.org/type/CdnPublicKey.html +++ /dev/null @@ -1,145 +0,0 @@ - - - - - CdnPublicKey - - - - - - - - - - - - - -
- -
-
-
- -

CdnPublicKey

- -

Public key to use only during handshakes to CDN DCs.

-

- -
-
cdnPublicKey#c982eaba dc_id:int public_key:string = CdnPublicKey;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
cdnPublicKeyPublic key to use only during handshakes to CDN DCs.
-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ChannelAdminLogEvent.html b/data/core.telegram.org/type/ChannelAdminLogEvent.html deleted file mode 100644 index 29975d7ffa..0000000000 --- a/data/core.telegram.org/type/ChannelAdminLogEvent.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - ChannelAdminLogEvent - - - - - - - - - - - - - -
- -
-
-
- -

ChannelAdminLogEvent

- -

An event in a channel admin log

-

- -
-
channelAdminLogEvent#1fad68cd id:long date:int user_id:long action:ChannelAdminLogEventAction = ChannelAdminLogEvent;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
channelAdminLogEventAdmin log event
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ChannelAdminLogEventAction.html b/data/core.telegram.org/type/ChannelAdminLogEventAction.html deleted file mode 100644 index dfe31939e3..0000000000 --- a/data/core.telegram.org/type/ChannelAdminLogEventAction.html +++ /dev/null @@ -1,298 +0,0 @@ - - - - - ChannelAdminLogEventAction - - - - - - - - - - - - - -
- -
-
-
- -

ChannelAdminLogEventAction

- -

Channel admin log event

-

- -
-
channelAdminLogEventActionChangeTitle#e6dfb825 prev_value:string new_value:string = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeAbout#55188a2e prev_value:string new_value:string = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeUsername#6a4afc38 prev_value:string new_value:string = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangePhoto#434bd2af prev_photo:Photo new_photo:Photo = ChannelAdminLogEventAction;
-channelAdminLogEventActionToggleInvites#1b7907ae new_value:Bool = ChannelAdminLogEventAction;
-channelAdminLogEventActionToggleSignatures#26ae0971 new_value:Bool = ChannelAdminLogEventAction;
-channelAdminLogEventActionUpdatePinned#e9e82c18 message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionEditMessage#709b2405 prev_message:Message new_message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionDeleteMessage#42e047bb message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantJoin#183040d3 = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantLeave#f89777f2 = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantInvite#e31c34d8 participant:ChannelParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantToggleBan#e6d83d7e prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantToggleAdmin#d5676710 prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeStickerSet#b1c3caa7 prev_stickerset:InputStickerSet new_stickerset:InputStickerSet = ChannelAdminLogEventAction;
-channelAdminLogEventActionTogglePreHistoryHidden#5f5c95f1 new_value:Bool = ChannelAdminLogEventAction;
-channelAdminLogEventActionDefaultBannedRights#2df5fc0a prev_banned_rights:ChatBannedRights new_banned_rights:ChatBannedRights = ChannelAdminLogEventAction;
-channelAdminLogEventActionStopPoll#8f079643 message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeLinkedChat#50c7ac8 prev_value:long new_value:long = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeLocation#e6b76ae prev_value:ChannelLocation new_value:ChannelLocation = ChannelAdminLogEventAction;
-channelAdminLogEventActionToggleSlowMode#53909779 prev_value:int new_value:int = ChannelAdminLogEventAction;
-channelAdminLogEventActionStartGroupCall#23209745 call:InputGroupCall = ChannelAdminLogEventAction;
-channelAdminLogEventActionDiscardGroupCall#db9f9140 call:InputGroupCall = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantMute#f92424d2 participant:GroupCallParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantUnmute#e64429c0 participant:GroupCallParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionToggleGroupCallSetting#56d6a247 join_muted:Bool = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantJoinByInvite#5cdada77 invite:ExportedChatInvite = ChannelAdminLogEventAction;
-channelAdminLogEventActionExportedInviteDelete#5a50fca4 invite:ExportedChatInvite = ChannelAdminLogEventAction;
-channelAdminLogEventActionExportedInviteRevoke#410a134e invite:ExportedChatInvite = ChannelAdminLogEventAction;
-channelAdminLogEventActionExportedInviteEdit#e90ebb59 prev_invite:ExportedChatInvite new_invite:ExportedChatInvite = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantVolume#3e7f6847 participant:GroupCallParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeHistoryTTL#6e941a38 prev_value:int new_value:int = ChannelAdminLogEventAction;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
channelAdminLogEventActionChangeTitleChannel/supergroup title was changed
channelAdminLogEventActionChangeAboutThe description was changed
channelAdminLogEventActionChangeUsernameChannel/supergroup username was changed
channelAdminLogEventActionChangePhotoThe channel/supergroup's picture was changed
channelAdminLogEventActionToggleInvitesInvites were enabled/disabled
channelAdminLogEventActionToggleSignaturesChannel signatures were enabled/disabled
channelAdminLogEventActionUpdatePinnedA message was pinned
channelAdminLogEventActionEditMessageA message was edited
channelAdminLogEventActionDeleteMessageA message was deleted
channelAdminLogEventActionParticipantJoinA user has joined the group (in the case of big groups, info of the user that has joined isn't shown)
channelAdminLogEventActionParticipantLeaveA user left the channel/supergroup (in the case of big groups, info of the user that has joined isn't shown)
channelAdminLogEventActionParticipantInviteA user was invited to the group
channelAdminLogEventActionParticipantToggleBanThe banned rights of a user were changed
channelAdminLogEventActionParticipantToggleAdminThe admin rights of a user were changed
channelAdminLogEventActionChangeStickerSetThe supergroup's stickerset was changed
channelAdminLogEventActionTogglePreHistoryHiddenThe hidden prehistory setting was changed
channelAdminLogEventActionDefaultBannedRightsThe default banned rights were modified
channelAdminLogEventActionStopPollA poll was stopped
channelAdminLogEventActionChangeLinkedChatThe linked chat was changed
channelAdminLogEventActionChangeLocationThe geogroup location was changed
channelAdminLogEventActionToggleSlowModeSlow mode setting for supergroups was changed
channelAdminLogEventActionStartGroupCallA group call was started
channelAdminLogEventActionDiscardGroupCallA group call was terminated
channelAdminLogEventActionParticipantMuteA group call participant was muted
channelAdminLogEventActionParticipantUnmuteA group call participant was unmuted
channelAdminLogEventActionToggleGroupCallSettingGroup call settings were changed
channelAdminLogEventActionParticipantJoinByInviteA user joined the supergroup/channel using a specific invite link
channelAdminLogEventActionExportedInviteDeleteA chat invite was deleted
channelAdminLogEventActionExportedInviteRevokeA specific invite link was revoked
channelAdminLogEventActionExportedInviteEditA chat invite was edited
channelAdminLogEventActionParticipantVolumechannelAdminLogEvent.user_id has set the volume of participant.peer to participant.volume
channelAdminLogEventActionChangeHistoryTTLThe Time-To-Live of messages in this chat was changed
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ChannelAdminLogEventsFilter.html b/data/core.telegram.org/type/ChannelAdminLogEventsFilter.html deleted file mode 100644 index 64712a8d68..0000000000 --- a/data/core.telegram.org/type/ChannelAdminLogEventsFilter.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - ChannelAdminLogEventsFilter - - - - - - - - - - - - - -
- -
-
-
- -

ChannelAdminLogEventsFilter

- -

Filter for fetching events in the channel admin log

-

- -
-
channelAdminLogEventsFilter#ea107ae4 flags:# join:flags.0?true leave:flags.1?true invite:flags.2?true ban:flags.3?true unban:flags.4?true kick:flags.5?true unkick:flags.6?true promote:flags.7?true demote:flags.8?true info:flags.9?true settings:flags.10?true pinned:flags.11?true edit:flags.12?true delete:flags.13?true group_call:flags.14?true invites:flags.15?true send:flags.16?true = ChannelAdminLogEventsFilter;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
channelAdminLogEventsFilterFilter only certain admin log events
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ChannelLocation.html b/data/core.telegram.org/type/ChannelLocation.html deleted file mode 100644 index 5dd2122123..0000000000 --- a/data/core.telegram.org/type/ChannelLocation.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - ChannelLocation - - - - - - - - - - - - - -
- -
-
-
- -

ChannelLocation

- -

Geographical location of supergroup (geogroups)

-

- -
-
channelLocationEmpty#bfb5ad8b = ChannelLocation;
-channelLocation#209b82db geo_point:GeoPoint address:string = ChannelLocation;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
channelLocationEmptyNo location (normal supergroup)
channelLocationGeographical location of supergroup (geogroups)
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ChannelMessagesFilter.html b/data/core.telegram.org/type/ChannelMessagesFilter.html deleted file mode 100644 index 2c4371a0d2..0000000000 --- a/data/core.telegram.org/type/ChannelMessagesFilter.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - ChannelMessagesFilter - - - - - - - - - - - - - -
- -
-
-
- -

ChannelMessagesFilter

- -

Filter for fetching only certain types of channel messages

-

- -
-
channelMessagesFilterEmpty#94d42ee7 = ChannelMessagesFilter;
-channelMessagesFilter#cd77d957 flags:# exclude_new_messages:flags.1?true ranges:Vector<MessageRange> = ChannelMessagesFilter;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
channelMessagesFilterEmptyNo filter
channelMessagesFilterFilter for getting only certain types of channel messages
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ChannelParticipant.html b/data/core.telegram.org/type/ChannelParticipant.html deleted file mode 100644 index d2274b1ba4..0000000000 --- a/data/core.telegram.org/type/ChannelParticipant.html +++ /dev/null @@ -1,168 +0,0 @@ - - - - - ChannelParticipant - - - - - - - - - - - - - -
- -
-
-
- -

ChannelParticipant

- -

Channel participant

-

- -
-
channelParticipant#c00c07c0 user_id:long date:int = ChannelParticipant;
-channelParticipantSelf#28a8bc67 user_id:long inviter_id:long date:int = ChannelParticipant;
-channelParticipantCreator#2fe601d3 flags:# user_id:long admin_rights:ChatAdminRights rank:flags.0?string = ChannelParticipant;
-channelParticipantAdmin#34c3bb53 flags:# can_edit:flags.0?true self:flags.1?true user_id:long inviter_id:flags.1?long promoted_by:long date:int admin_rights:ChatAdminRights rank:flags.2?string = ChannelParticipant;
-channelParticipantBanned#6df8014e flags:# left:flags.0?true peer:Peer kicked_by:long date:int banned_rights:ChatBannedRights = ChannelParticipant;
-channelParticipantLeft#1b03f006 peer:Peer = ChannelParticipant;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
channelParticipantChannel/supergroup participant
channelParticipantSelfMyself
channelParticipantCreatorChannel/supergroup creator
channelParticipantAdminAdmin
channelParticipantBannedBanned/kicked user
channelParticipantLeftA participant that left the channel/supergroup
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ChannelParticipantsFilter.html b/data/core.telegram.org/type/ChannelParticipantsFilter.html deleted file mode 100644 index 6d2090cd0c..0000000000 --- a/data/core.telegram.org/type/ChannelParticipantsFilter.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - ChannelParticipantsFilter - - - - - - - - - - - - - -
- -
-
-
- -

ChannelParticipantsFilter

- -

Filter for fetching channel participants

-

- -
-
channelParticipantsRecent#de3f3c79 = ChannelParticipantsFilter;
-channelParticipantsAdmins#b4608969 = ChannelParticipantsFilter;
-channelParticipantsKicked#a3b54985 q:string = ChannelParticipantsFilter;
-channelParticipantsBots#b0d1865b = ChannelParticipantsFilter;
-channelParticipantsBanned#1427a5e1 q:string = ChannelParticipantsFilter;
-channelParticipantsSearch#656ac4b q:string = ChannelParticipantsFilter;
-channelParticipantsContacts#bb6ae88d q:string = ChannelParticipantsFilter;
-channelParticipantsMentions#e04b5ceb flags:# q:flags.0?string top_msg_id:flags.1?int = ChannelParticipantsFilter;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
channelParticipantsRecentFetch only recent participants
channelParticipantsAdminsFetch only admin participants
channelParticipantsKickedFetch only kicked participants
channelParticipantsBotsFetch only bot participants
channelParticipantsBannedFetch only banned participants
channelParticipantsSearchQuery participants by name
channelParticipantsContactsFetch only participants that are also contacts
channelParticipantsMentionsThis filter is used when looking for members to mention.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Chat.html b/data/core.telegram.org/type/Chat.html deleted file mode 100644 index 593dcf12d5..0000000000 --- a/data/core.telegram.org/type/Chat.html +++ /dev/null @@ -1,163 +0,0 @@ - - - - - Chat - - - - - - - - - - - - - -
- -
-
-
- -

Chat

- -

Object defines a group.

-

- -
-
chatEmpty#29562865 id:long = Chat;
-chat#41cbf256 flags:# creator:flags.0?true kicked:flags.1?true left:flags.2?true deactivated:flags.5?true call_active:flags.23?true call_not_empty:flags.24?true noforwards:flags.25?true id:long title:string photo:ChatPhoto participants_count:int date:int version:int migrated_to:flags.6?InputChannel admin_rights:flags.14?ChatAdminRights default_banned_rights:flags.18?ChatBannedRights = Chat;
-chatForbidden#6592a1a7 id:long title:string = Chat;
-channel#8261ac61 flags:# creator:flags.0?true left:flags.2?true broadcast:flags.5?true verified:flags.7?true megagroup:flags.8?true restricted:flags.9?true signatures:flags.11?true min:flags.12?true scam:flags.19?true has_link:flags.20?true has_geo:flags.21?true slowmode_enabled:flags.22?true call_active:flags.23?true call_not_empty:flags.24?true fake:flags.25?true gigagroup:flags.26?true noforwards:flags.27?true id:long access_hash:flags.13?long title:string username:flags.6?string photo:ChatPhoto date:int restriction_reason:flags.9?Vector<RestrictionReason> admin_rights:flags.14?ChatAdminRights banned_rights:flags.15?ChatBannedRights default_banned_rights:flags.18?ChatBannedRights participants_count:flags.17?int = Chat;
-channelForbidden#17d493d5 flags:# broadcast:flags.5?true megagroup:flags.8?true id:long access_hash:long title:string until_date:flags.16?int = Chat;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
chatEmptyEmpty constructor, group doesn't exist
chatInfo about a group
chatForbiddenA group to which the user has no access. E.g., because the user was kicked from the group.
channelChannel/supergroup info
channelForbiddenIndicates a channel/supergroup we can't access because we were banned, or for some other reason.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ChatAdminRights.html b/data/core.telegram.org/type/ChatAdminRights.html deleted file mode 100644 index 2e585e999d..0000000000 --- a/data/core.telegram.org/type/ChatAdminRights.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - ChatAdminRights - - - - - - - - - - - - - -
- -
-
-
- -

ChatAdminRights

- -

Represents the rights of an admin in a channel/supergroup.

-

- -
-
chatAdminRights#5fb224d5 flags:# change_info:flags.0?true post_messages:flags.1?true edit_messages:flags.2?true delete_messages:flags.3?true ban_users:flags.4?true invite_users:flags.5?true pin_messages:flags.7?true add_admins:flags.9?true anonymous:flags.10?true manage_call:flags.11?true other:flags.12?true = ChatAdminRights;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
chatAdminRightsRepresents the rights of an admin in a channel/supergroup.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ChatAdminWithInvites.html b/data/core.telegram.org/type/ChatAdminWithInvites.html deleted file mode 100644 index de71b94b23..0000000000 --- a/data/core.telegram.org/type/ChatAdminWithInvites.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - ChatAdminWithInvites - - - - - - - - - - - - - -
- -
-
-
- -

ChatAdminWithInvites

- -

Info about chat invites generated by admins.

-

- -
-
chatAdminWithInvites#f2ecef23 admin_id:long invites_count:int revoked_invites_count:int = ChatAdminWithInvites;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
chatAdminWithInvitesInfo about chat invites generated by admins.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ChatBannedRights.html b/data/core.telegram.org/type/ChatBannedRights.html deleted file mode 100644 index ea21b3656a..0000000000 --- a/data/core.telegram.org/type/ChatBannedRights.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - ChatBannedRights - - - - - - - - - - - - - -
- -
-
-
- -

ChatBannedRights

- -

Represents the rights of a normal user in a supergroup/channel/chat.

-

- -
-
chatBannedRights#9f120418 flags:# view_messages:flags.0?true send_messages:flags.1?true send_media:flags.2?true send_stickers:flags.3?true send_gifs:flags.4?true send_games:flags.5?true send_inline:flags.6?true embed_links:flags.7?true send_polls:flags.8?true change_info:flags.10?true invite_users:flags.15?true pin_messages:flags.17?true until_date:int = ChatBannedRights;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
chatBannedRightsRepresents the rights of a normal user in a supergroup/channel/chat. In this case, the flags are inverted: if set, a flag does not allow a user to do X.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ChatFull.html b/data/core.telegram.org/type/ChatFull.html deleted file mode 100644 index 10ce7a0af0..0000000000 --- a/data/core.telegram.org/type/ChatFull.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - ChatFull - - - - - - - - - - - - - -
- -
-
-
- -

ChatFull

- -

Object containing detailed group info

-

- -
-
chatFull#4dbdc099 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:long about:string participants:ChatParticipants chat_photo:flags.2?Photo notify_settings:PeerNotifySettings exported_invite:flags.13?ExportedChatInvite bot_info:flags.3?Vector<BotInfo> pinned_msg_id:flags.6?int folder_id:flags.11?int call:flags.12?InputGroupCall ttl_period:flags.14?int groupcall_default_join_as:flags.15?Peer theme_emoticon:flags.16?string = ChatFull;
-channelFull#e9b27a17 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector<string> groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string = ChatFull;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
chatFullDetailed chat info
channelFullFull info about a channel/supergroup
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ChatInvite.html b/data/core.telegram.org/type/ChatInvite.html deleted file mode 100644 index b018613b36..0000000000 --- a/data/core.telegram.org/type/ChatInvite.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - ChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

ChatInvite

- -

Chat invite

-

- -
-
chatInviteAlready#5a686d7c chat:Chat = ChatInvite;
-chatInvite#dfc2f58e flags:# channel:flags.0?true broadcast:flags.1?true public:flags.2?true megagroup:flags.3?true title:string photo:Photo participants_count:int participants:flags.4?Vector<User> = ChatInvite;
-chatInvitePeek#61695cb0 chat:Chat expires:int = ChatInvite;
-
----functions---
-
-messages.checkChatInvite#3eadb1bb hash:string = ChatInvite;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
chatInviteAlreadyThe user has already joined this chat
chatInviteChat invite info
chatInvitePeekA chat invitation that also allows peeking into the group to read messages without joining it.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.checkChatInviteCheck the validity of a chat invite link and get basic info about it
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ChatInviteImporter.html b/data/core.telegram.org/type/ChatInviteImporter.html deleted file mode 100644 index dcbcf76d68..0000000000 --- a/data/core.telegram.org/type/ChatInviteImporter.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - ChatInviteImporter - - - - - - - - - - - - - -
- -
-
-
- -

ChatInviteImporter

- -

When and which user joined the chat using a chat invite

-

- -
-
chatInviteImporter#b5cd5f4 user_id:long date:int = ChatInviteImporter;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
chatInviteImporterWhen and which user joined the chat using a chat invite
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ChatOnlines.html b/data/core.telegram.org/type/ChatOnlines.html deleted file mode 100644 index 9280a09df5..0000000000 --- a/data/core.telegram.org/type/ChatOnlines.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - ChatOnlines - - - - - - - - - - - - - -
- -
-
-
- -

ChatOnlines

- -

Number of online users in a chat

-

- -
-
chatOnlines#f041e250 onlines:int = ChatOnlines;
-
----functions---
-
-messages.getOnlines#6e2be050 peer:InputPeer = ChatOnlines;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
chatOnlinesNumber of online users in a chat
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getOnlinesGet count of online users in a chat
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ChatParticipant.html b/data/core.telegram.org/type/ChatParticipant.html deleted file mode 100644 index 46c022bc0e..0000000000 --- a/data/core.telegram.org/type/ChatParticipant.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - ChatParticipant - - - - - - - - - - - - - -
- -
-
-
- -

ChatParticipant

- -

Details of a group member.

-

- -
-
chatParticipant#c02d4007 user_id:long inviter_id:long date:int = ChatParticipant;
-chatParticipantCreator#e46bcee4 user_id:long = ChatParticipant;
-chatParticipantAdmin#a0933f5b user_id:long inviter_id:long date:int = ChatParticipant;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
chatParticipantGroup member.
chatParticipantCreatorRepresents the creator of the group
chatParticipantAdminChat admin
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ChatParticipants.html b/data/core.telegram.org/type/ChatParticipants.html deleted file mode 100644 index 2ae72c16fa..0000000000 --- a/data/core.telegram.org/type/ChatParticipants.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - ChatParticipants - - - - - - - - - - - - - -
- -
-
-
- -

ChatParticipants

- -

Object contains info on group members.

-

- -
-
chatParticipantsForbidden#8763d3e1 flags:# chat_id:long self_participant:flags.0?ChatParticipant = ChatParticipants;
-chatParticipants#3cbc93f8 chat_id:long participants:Vector<ChatParticipant> version:int = ChatParticipants;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
chatParticipantsForbiddenInfo on members is unavailable
chatParticipantsGroup members.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ChatPhoto.html b/data/core.telegram.org/type/ChatPhoto.html deleted file mode 100644 index 0c4a5e067e..0000000000 --- a/data/core.telegram.org/type/ChatPhoto.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - ChatPhoto - - - - - - - - - - - - - -
- -
-
-
- -

ChatPhoto

- -

Object defines a group profile photo.

-

- -
-
chatPhotoEmpty#37c1011c = ChatPhoto;
-chatPhoto#1c6e1c11 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = ChatPhoto;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
chatPhotoEmptyGroup photo is not set.
chatPhotoGroup profile photo.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ChatTheme.html b/data/core.telegram.org/type/ChatTheme.html deleted file mode 100644 index 1ca3407fce..0000000000 --- a/data/core.telegram.org/type/ChatTheme.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - ChatTheme - - - - - - - - - - - - - -
- -
-
-
- -

ChatTheme

- -

A chat theme

-

- -
-
chatTheme#ed0b5c33 emoticon:string theme:Theme dark_theme:Theme = ChatTheme;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
chatThemeA chat theme
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/CodeSettings.html b/data/core.telegram.org/type/CodeSettings.html deleted file mode 100644 index 2a4d520361..0000000000 --- a/data/core.telegram.org/type/CodeSettings.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - CodeSettings - - - - - - - - - - - - - -
- -
-
-
- -

CodeSettings

- -

Settings for the code type to send

-

- -
-
codeSettings#debebe83 flags:# allow_flashcall:flags.0?true current_number:flags.1?true allow_app_hash:flags.4?true = CodeSettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
codeSettingsSettings used by telegram servers for sending the confirm code.

Example implementations: telegram for android, tdlib.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Config.html b/data/core.telegram.org/type/Config.html deleted file mode 100644 index d609658f4d..0000000000 --- a/data/core.telegram.org/type/Config.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Config - - - - - - - - - - - - - -
- -
-
-
- -

Config

- -

Object contains info on API configuring parameters.

-

- -
-
config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;
-
----functions---
-
-help.getConfig#c4f9186b = Config;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
configCurrent configuration
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getConfigReturns current configuration, icluding data center configuration.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Contact.html b/data/core.telegram.org/type/Contact.html deleted file mode 100644 index 1908495f25..0000000000 --- a/data/core.telegram.org/type/Contact.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - Contact - - - - - - - - - - - - - -
- -
-
-
- -

Contact

- -

A contact of the current user.

-

- -
-
contact#145ade0b user_id:long mutual:Bool = Contact;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
contactA contact of the current user that is registered in the system.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ContactStatus.html b/data/core.telegram.org/type/ContactStatus.html deleted file mode 100644 index 5479d46446..0000000000 --- a/data/core.telegram.org/type/ContactStatus.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - ContactStatus - - - - - - - - - - - - - -
- -
-
-
- -

ContactStatus

- -

Contact status: online / offline.

-

- -
-
contactStatus#16d9703b user_id:long status:UserStatus = ContactStatus;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
contactStatusContact status: online / offline.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/DataJSON.html b/data/core.telegram.org/type/DataJSON.html deleted file mode 100644 index 1b536eb2f9..0000000000 --- a/data/core.telegram.org/type/DataJSON.html +++ /dev/null @@ -1,168 +0,0 @@ - - - - - DataJSON - - - - - - - - - - - - - -
- -
-
-
- -

DataJSON

- -

Represent a JSON-encoded object

-

- -
-
dataJSON#7d748d04 data:string = DataJSON;
-
----functions---
-
-bots.sendCustomRequest#aa2769ed custom_method:string params:DataJSON = DataJSON;
-
-phone.getCallConfig#55451fa9 = DataJSON;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
dataJSONRepresents a json-encoded object
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
bots.sendCustomRequestSends a custom request; for bots only
phone.getCallConfigGet phone call configuration to be passed to libtgvoip's shared config
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/DcOption.html b/data/core.telegram.org/type/DcOption.html deleted file mode 100644 index dc9fa76764..0000000000 --- a/data/core.telegram.org/type/DcOption.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - DcOption - - - - - - - - - - - - - -
- -
-
-
- -

DcOption

- -

Information for connection to data centre.

-

- -
-
dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
dcOptionData centre
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/DecryptedDataBlock.html b/data/core.telegram.org/type/DecryptedDataBlock.html deleted file mode 100644 index 1ce54fed4a..0000000000 --- a/data/core.telegram.org/type/DecryptedDataBlock.html +++ /dev/null @@ -1,128 +0,0 @@ - - - - - DecryptedDataBlock - - - - - - - - - - - - - -
- -
-
-
- -

DecryptedDataBlock

- -

VoIP decrypted data block

-

- -
-
Type schema is not available in the selected layer.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/DecryptedMessage.html b/data/core.telegram.org/type/DecryptedMessage.html deleted file mode 100644 index 44487a5b19..0000000000 --- a/data/core.telegram.org/type/DecryptedMessage.html +++ /dev/null @@ -1,140 +0,0 @@ - - - - - DecryptedMessage - - - - - - - - - - - - - -
- -
-
-
- -

DecryptedMessage

- -

Object describes the contents of an encrypted message.

-

- -
-
===8===
-decryptedMessage#1f814f1f random_id:long random_bytes:bytes message:string media:DecryptedMessageMedia = DecryptedMessage;
-decryptedMessageService#aa48327d random_id:long random_bytes:bytes action:DecryptedMessageAction = DecryptedMessage;
-
-===17===
-decryptedMessage#204d3878 random_id:long ttl:int message:string media:DecryptedMessageMedia = DecryptedMessage;
-decryptedMessageService#73164160 random_id:long action:DecryptedMessageAction = DecryptedMessage;
-
-===45===
-decryptedMessage#36b091de flags:# random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long = DecryptedMessage;
-
-===73===
-decryptedMessage#91cc4674 flags:# no_webpage:flags.1?true silent:flags.5?true random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long grouped_id:flags.17?long = DecryptedMessage;

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/DecryptedMessageAction.html b/data/core.telegram.org/type/DecryptedMessageAction.html deleted file mode 100644 index 273e9ae356..0000000000 --- a/data/core.telegram.org/type/DecryptedMessageAction.html +++ /dev/null @@ -1,145 +0,0 @@ - - - - - DecryptedMessageAction - - - - - - - - - - - - - -
- -
-
-
- -

DecryptedMessageAction

- -

Object describes the action to which a service message is linked.

-

- -
-
===8===
-decryptedMessageActionSetMessageTTL#a1733aec ttl_seconds:int = DecryptedMessageAction;
-decryptedMessageActionReadMessages#c4f40be random_ids:Vector<long> = DecryptedMessageAction;
-decryptedMessageActionDeleteMessages#65614304 random_ids:Vector<long> = DecryptedMessageAction;
-decryptedMessageActionScreenshotMessages#8ac1f475 random_ids:Vector<long> = DecryptedMessageAction;
-decryptedMessageActionFlushHistory#6719e45c = DecryptedMessageAction;
-
-===17===
-decryptedMessageActionResend#511110b0 start_seq_no:int end_seq_no:int = DecryptedMessageAction;
-decryptedMessageActionNotifyLayer#f3048883 layer:int = DecryptedMessageAction;
-decryptedMessageActionTyping#ccb27641 action:SendMessageAction = DecryptedMessageAction;
-
-===20===
-decryptedMessageActionRequestKey#f3c9611b exchange_id:long g_a:bytes = DecryptedMessageAction;
-decryptedMessageActionAcceptKey#6fe1735b exchange_id:long g_b:bytes key_fingerprint:long = DecryptedMessageAction;
-decryptedMessageActionAbortKey#dd05ec6b exchange_id:long = DecryptedMessageAction;
-decryptedMessageActionCommitKey#ec2e0b9b exchange_id:long key_fingerprint:long = DecryptedMessageAction;
-decryptedMessageActionNoop#a82fdd63 = DecryptedMessageAction;

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/DecryptedMessageLayer.html b/data/core.telegram.org/type/DecryptedMessageLayer.html deleted file mode 100644 index bb15e1cfc6..0000000000 --- a/data/core.telegram.org/type/DecryptedMessageLayer.html +++ /dev/null @@ -1,129 +0,0 @@ - - - - - DecryptedMessageLayer - - - - - - - - - - - - - -
- -
-
-
- -

DecryptedMessageLayer

- -

Object describes encrypted message content in relation to the required layer.

-

- -
-
===17===
-decryptedMessageLayer#1be31789 random_bytes:bytes layer:int in_seq_no:int out_seq_no:int message:DecryptedMessage = DecryptedMessageLayer;

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/DecryptedMessageMedia.html b/data/core.telegram.org/type/DecryptedMessageMedia.html deleted file mode 100644 index 4f281691e6..0000000000 --- a/data/core.telegram.org/type/DecryptedMessageMedia.html +++ /dev/null @@ -1,149 +0,0 @@ - - - - - DecryptedMessageMedia - - - - - - - - - - - - - -
- -
-
-
- -

DecryptedMessageMedia

- -

Object describes media contents of an encrypted message.

-

- -
-
===8===
-decryptedMessageMediaEmpty#89f5c4a = DecryptedMessageMedia;
-decryptedMessageMediaPhoto#32798a8c thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageMediaVideo#4cee6ef3 thumb:bytes thumb_w:int thumb_h:int duration:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageMediaGeoPoint#35480a59 lat:double long:double = DecryptedMessageMedia;
-decryptedMessageMediaContact#588a0a97 phone_number:string first_name:string last_name:string user_id:int = DecryptedMessageMedia;
-decryptedMessageMediaDocument#b095434b thumb:bytes thumb_w:int thumb_h:int file_name:string mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageMediaAudio#6080758f duration:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-
-===17===
-decryptedMessageMediaVideo#524a415d thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageMediaAudio#57e0a9cb duration:int mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
-
-===23===
-decryptedMessageMediaExternalDocument#fa95b0dd id:long access_hash:long date:int mime_type:string size:int thumb:PhotoSize dc_id:int attributes:Vector<DocumentAttribute> = DecryptedMessageMedia;
-
-===45===
-decryptedMessageMediaPhoto#f1fa8d78 thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;
-decryptedMessageMediaVideo#970c8c0e thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;
-decryptedMessageMediaDocument#7afe8ae2 thumb:bytes thumb_w:int thumb_h:int mime_type:string size:int key:bytes iv:bytes attributes:Vector<DocumentAttribute> caption:string = DecryptedMessageMedia;
-decryptedMessageMediaVenue#8a0df56f lat:double long:double title:string address:string provider:string venue_id:string = DecryptedMessageMedia;
-decryptedMessageMediaWebPage#e50511d8 url:string = DecryptedMessageMedia;

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Dialog.html b/data/core.telegram.org/type/Dialog.html deleted file mode 100644 index 0343ee4052..0000000000 --- a/data/core.telegram.org/type/Dialog.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - Dialog - - - - - - - - - - - - - -
- -
-
-
- -

Dialog

- -

Chat info.

-

- -
-
dialog#2c171f72 flags:# pinned:flags.2?true unread_mark:flags.3?true peer:Peer top_message:int read_inbox_max_id:int read_outbox_max_id:int unread_count:int unread_mentions_count:int notify_settings:PeerNotifySettings pts:flags.0?int draft:flags.1?DraftMessage folder_id:flags.4?int = Dialog;
-dialogFolder#71bd134c flags:# pinned:flags.2?true folder:Folder peer:Peer top_message:int unread_muted_peers_count:int unread_unmuted_peers_count:int unread_muted_messages_count:int unread_unmuted_messages_count:int = Dialog;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
dialogChat
dialogFolderDialog in folder
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/DialogFilter.html b/data/core.telegram.org/type/DialogFilter.html deleted file mode 100644 index e3b54f7bef..0000000000 --- a/data/core.telegram.org/type/DialogFilter.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - DialogFilter - - - - - - - - - - - - - -
- -
-
-
- -

DialogFilter

- -

Dialog filter (folders)

-

- -
-
dialogFilter#7438f7e8 flags:# contacts:flags.0?true non_contacts:flags.1?true groups:flags.2?true broadcasts:flags.3?true bots:flags.4?true exclude_muted:flags.11?true exclude_read:flags.12?true exclude_archived:flags.13?true id:int title:string emoticon:flags.25?string pinned_peers:Vector<InputPeer> include_peers:Vector<InputPeer> exclude_peers:Vector<InputPeer> = DialogFilter;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
dialogFilterDialog filter (folder)
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/DialogFilterSuggested.html b/data/core.telegram.org/type/DialogFilterSuggested.html deleted file mode 100644 index f9f20477ee..0000000000 --- a/data/core.telegram.org/type/DialogFilterSuggested.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - DialogFilterSuggested - - - - - - - - - - - - - -
- -
-
-
- -

DialogFilterSuggested

- -

Suggested dialog filters (folders)

-

- -
-
dialogFilterSuggested#77744d4a filter:DialogFilter description:string = DialogFilterSuggested;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
dialogFilterSuggestedSuggested folders
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/DialogPeer.html b/data/core.telegram.org/type/DialogPeer.html deleted file mode 100644 index 02a027396f..0000000000 --- a/data/core.telegram.org/type/DialogPeer.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - DialogPeer - - - - - - - - - - - - - -
- -
-
-
- -

DialogPeer

- -

Peer, or all peers in a folder

-

- -
-
dialogPeer#e56dbf05 peer:Peer = DialogPeer;
-dialogPeerFolder#514519e2 folder_id:int = DialogPeer;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
dialogPeerPeer
dialogPeerFolderFolder
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/DisabledFeature.html b/data/core.telegram.org/type/DisabledFeature.html deleted file mode 100644 index 5cff87c98c..0000000000 --- a/data/core.telegram.org/type/DisabledFeature.html +++ /dev/null @@ -1,128 +0,0 @@ - - - - - DisabledFeature - - - - - - - - - - - - - -
- -
-
-
- -

DisabledFeature

- -

A disabled feature

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Document.html b/data/core.telegram.org/type/Document.html deleted file mode 100644 index 5a922e2dfa..0000000000 --- a/data/core.telegram.org/type/Document.html +++ /dev/null @@ -1,173 +0,0 @@ - - - - - Document - - - - - - - - - - - - - -
- -
-
-
- -

Document

- -

A document.

-

- -
-
documentEmpty#36f8c871 id:long = Document;
-document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
-
----functions---
-
-messages.getDocumentByHash#338e2464 sha256:bytes size:int mime_type:string = Document;
-
-account.uploadTheme#1c3db333 flags:# file:InputFile thumb:flags.0?InputFile file_name:string mime_type:string = Document;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
documentEmptyEmpty constructor, document doesn't exist.
documentDocument
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
messages.getDocumentByHashGet a document by its SHA256 hash, mainly used for gifs
account.uploadThemeUpload theme
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/DocumentAttribute.html b/data/core.telegram.org/type/DocumentAttribute.html deleted file mode 100644 index 3c8f4eb2bc..0000000000 --- a/data/core.telegram.org/type/DocumentAttribute.html +++ /dev/null @@ -1,173 +0,0 @@ - - - - - DocumentAttribute - - - - - - - - - - - - - -
- -
-
-
- -

DocumentAttribute

- -

Various possible attributes of a document (used to define if it's a sticker, a GIF, a video, a mask sticker, an image, an audio, and so on)

-

- -
-
documentAttributeImageSize#6c37c15c w:int h:int = DocumentAttribute;
-documentAttributeAnimated#11b58939 = DocumentAttribute;
-documentAttributeSticker#6319d612 flags:# mask:flags.1?true alt:string stickerset:InputStickerSet mask_coords:flags.0?MaskCoords = DocumentAttribute;
-documentAttributeVideo#ef02ce6 flags:# round_message:flags.0?true supports_streaming:flags.1?true duration:int w:int h:int = DocumentAttribute;
-documentAttributeAudio#9852f9c6 flags:# voice:flags.10?true duration:int title:flags.0?string performer:flags.1?string waveform:flags.2?bytes = DocumentAttribute;
-documentAttributeFilename#15590068 file_name:string = DocumentAttribute;
-documentAttributeHasStickers#9801d2f7 = DocumentAttribute;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
documentAttributeImageSizeDefines the width and height of an image uploaded as document
documentAttributeAnimatedDefines an animated GIF
documentAttributeStickerDefines a sticker
documentAttributeVideoDefines a video
documentAttributeAudioRepresents an audio file
documentAttributeFilenameA simple document with a file name
documentAttributeHasStickersWhether the current document has stickers attached
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/EmojiKeyword.html b/data/core.telegram.org/type/EmojiKeyword.html deleted file mode 100644 index b9a0b64f8a..0000000000 --- a/data/core.telegram.org/type/EmojiKeyword.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - EmojiKeyword - - - - - - - - - - - - - -
- -
-
-
- -

EmojiKeyword

- -

Emoji keyword

-

- -
-
emojiKeyword#d5b3b9f9 keyword:string emoticons:Vector<string> = EmojiKeyword;
-emojiKeywordDeleted#236df622 keyword:string emoticons:Vector<string> = EmojiKeyword;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
emojiKeywordEmoji keyword
emojiKeywordDeletedDeleted emoji keyword
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/EmojiLanguage.html b/data/core.telegram.org/type/EmojiLanguage.html deleted file mode 100644 index d71fa5aba2..0000000000 --- a/data/core.telegram.org/type/EmojiLanguage.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - EmojiLanguage - - - - - - - - - - - - - -
- -
-
-
- -

EmojiLanguage

- -

Emoji language

-

- -
-
emojiLanguage#b3fb5361 lang_code:string = EmojiLanguage;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
emojiLanguageEmoji language
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/EmojiURL.html b/data/core.telegram.org/type/EmojiURL.html deleted file mode 100644 index 83d6f66f1a..0000000000 --- a/data/core.telegram.org/type/EmojiURL.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - EmojiURL - - - - - - - - - - - - - -
- -
-
-
- -

EmojiURL

- -

Emoji URL

-

- -
-
emojiURL#a575739d url:string = EmojiURL;
-
----functions---
-
-messages.getEmojiURL#d5b10c26 lang_code:string = EmojiURL;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
emojiURLAn HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getEmojiURLReturns an HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/EncryptedChat.html b/data/core.telegram.org/type/EncryptedChat.html deleted file mode 100644 index b7d67a122f..0000000000 --- a/data/core.telegram.org/type/EncryptedChat.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - EncryptedChat - - - - - - - - - - - - - -
- -
-
-
- -

EncryptedChat

- -

Object contains info on an encrypted chat.

-

- -
-
encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;
-encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;
-encryptedChatRequested#48f1d94c flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:long participant_id:long g_a:bytes = EncryptedChat;
-encryptedChat#61f0d4c7 id:int access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long = EncryptedChat;
-encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;
-
----functions---
-
-messages.requestEncryption#f64daf43 user_id:InputUser random_id:int g_a:bytes = EncryptedChat;
-messages.acceptEncryption#3dbc0415 peer:InputEncryptedChat g_b:bytes key_fingerprint:long = EncryptedChat;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
encryptedChatEmptyEmpty constructor.
encryptedChatWaitingChat waiting for approval of second participant.
encryptedChatRequestedRequest to create an encrypted chat.
encryptedChatEncrypted chat
encryptedChatDiscardedDiscarded or deleted chat.
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
messages.requestEncryptionSends a request to start a secret chat to the user.
messages.acceptEncryptionConfirms creation of a secret chat
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/EncryptedFile.html b/data/core.telegram.org/type/EncryptedFile.html deleted file mode 100644 index 461b6767b2..0000000000 --- a/data/core.telegram.org/type/EncryptedFile.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - EncryptedFile - - - - - - - - - - - - - -
- -
-
-
- -

EncryptedFile

- -

Seta an encrypted file.

-

- -
-
encryptedFileEmpty#c21f497e = EncryptedFile;
-encryptedFile#4a70994c id:long access_hash:long size:int dc_id:int key_fingerprint:int = EncryptedFile;
-
----functions---
-
-messages.uploadEncryptedFile#5057c497 peer:InputEncryptedChat file:InputEncryptedFile = EncryptedFile;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
encryptedFileEmptyEmpty constructor, unexisitng file.
encryptedFileEncrypted file.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.uploadEncryptedFileUpload encrypted file and associate it to a secret chat
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/EncryptedMessage.html b/data/core.telegram.org/type/EncryptedMessage.html deleted file mode 100644 index 0096c27c9a..0000000000 --- a/data/core.telegram.org/type/EncryptedMessage.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - EncryptedMessage - - - - - - - - - - - - - -
- -
-
-
- -

EncryptedMessage

- -

Object contains encrypted message.

-

- -
-
encryptedMessage#ed18c118 random_id:long chat_id:int date:int bytes:bytes file:EncryptedFile = EncryptedMessage;
-encryptedMessageService#23734b06 random_id:long chat_id:int date:int bytes:bytes = EncryptedMessage;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
encryptedMessageEncrypted message.
encryptedMessageServiceEncrypted service message
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Error.html b/data/core.telegram.org/type/Error.html deleted file mode 100644 index 0bdedb2b31..0000000000 --- a/data/core.telegram.org/type/Error.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - Error - - - - - - - - - - - - - -
- -
-
-
- -

Error

- -

An object containing a query error.

-

- -
-
error#c4b9f9bb code:int text:string = Error;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
errorError.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ExportedChatInvite.html b/data/core.telegram.org/type/ExportedChatInvite.html deleted file mode 100644 index aed3752f1b..0000000000 --- a/data/core.telegram.org/type/ExportedChatInvite.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - ExportedChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

ExportedChatInvite

- -

Exported chat invite

-

- -
-
chatInviteExported#b18105e8 flags:# revoked:flags.0?true permanent:flags.5?true link:string admin_id:long date:int start_date:flags.4?int expire_date:flags.1?int usage_limit:flags.2?int usage:flags.3?int = ExportedChatInvite;
-
----functions---
-
-messages.exportChatInvite#14b9bcd7 flags:# legacy_revoke_permanent:flags.2?true peer:InputPeer expire_date:flags.0?int usage_limit:flags.1?int = ExportedChatInvite;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
chatInviteExportedExported chat invite
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.exportChatInviteExport an invite link for a chat
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ExportedMessageLink.html b/data/core.telegram.org/type/ExportedMessageLink.html deleted file mode 100644 index cd7f496ad9..0000000000 --- a/data/core.telegram.org/type/ExportedMessageLink.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - ExportedMessageLink - - - - - - - - - - - - - -
- -
-
-
- -

ExportedMessageLink

- -

HTTP link and embed info of channel message

-

- -
-
exportedMessageLink#5dab1af4 link:string html:string = ExportedMessageLink;
-
----functions---
-
-channels.exportMessageLink#e63fadeb flags:# grouped:flags.0?true thread:flags.1?true channel:InputChannel id:int = ExportedMessageLink;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
exportedMessageLinkLink to a message in a supergroup/channel
-

Methods

- - - - - - - - - - - - - -
MethodDescription
channels.exportMessageLinkGet link and embed info of a message in a channel/supergroup
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/FileHash.html b/data/core.telegram.org/type/FileHash.html deleted file mode 100644 index 528661d09d..0000000000 --- a/data/core.telegram.org/type/FileHash.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - FileHash - - - - - - - - - - - - - -
- -
-
-
- -

FileHash

- -

Hash of an uploaded file, to be checked for validity after download

-

- -
-
fileHash#6242c773 offset:int limit:int hash:bytes = FileHash;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
fileHashSHA256 Hash of an uploaded file, to be checked for validity after download
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/FileLocation.html b/data/core.telegram.org/type/FileLocation.html deleted file mode 100644 index 7f3f05d54a..0000000000 --- a/data/core.telegram.org/type/FileLocation.html +++ /dev/null @@ -1,128 +0,0 @@ - - - - - FileLocation - - - - - - - - - - - - - -
- -
-
-
- -

FileLocation

- -

Indicates the location of a photo, will be deprecated soon

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Folder.html b/data/core.telegram.org/type/Folder.html deleted file mode 100644 index 39366f9a02..0000000000 --- a/data/core.telegram.org/type/Folder.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - Folder - - - - - - - - - - - - - -
- -
-
-
- -

Folder

- -

A folder

-

- -
-
folder#ff544e65 flags:# autofill_new_broadcasts:flags.0?true autofill_public_groups:flags.1?true autofill_new_correspondents:flags.2?true id:int title:string photo:flags.3?ChatPhoto = Folder;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
folderFolder
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/FolderPeer.html b/data/core.telegram.org/type/FolderPeer.html deleted file mode 100644 index b04a296dcf..0000000000 --- a/data/core.telegram.org/type/FolderPeer.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - FolderPeer - - - - - - - - - - - - - -
- -
-
-
- -

FolderPeer

- -

Peer associated to folder

-

- -
-
folderPeer#e9baa668 peer:Peer folder_id:int = FolderPeer;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
folderPeerPeer in a folder
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Game.html b/data/core.telegram.org/type/Game.html deleted file mode 100644 index dcba7cddad..0000000000 --- a/data/core.telegram.org/type/Game.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - Game - - - - - - - - - - - - - -
- -
-
-
- -

Game

- -

Indicates an already sent game

-

- -
-
game#bdf9653b flags:# id:long access_hash:long short_name:string title:string description:string photo:Photo document:flags.0?Document = Game;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
gameIndicates an already sent game
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/GeoPoint.html b/data/core.telegram.org/type/GeoPoint.html deleted file mode 100644 index 3011f0e13c..0000000000 --- a/data/core.telegram.org/type/GeoPoint.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - GeoPoint - - - - - - - - - - - - - -
- -
-
-
- -

GeoPoint

- -

Object defines a GeoPoint.

-

- -
-
geoPointEmpty#1117dd5f = GeoPoint;
-geoPoint#b2a2f663 flags:# long:double lat:double access_hash:long accuracy_radius:flags.0?int = GeoPoint;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
geoPointEmptyEmpty constructor.
geoPointGeoPoint.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/GlobalPrivacySettings.html b/data/core.telegram.org/type/GlobalPrivacySettings.html deleted file mode 100644 index dd3915ea7e..0000000000 --- a/data/core.telegram.org/type/GlobalPrivacySettings.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - GlobalPrivacySettings - - - - - - - - - - - - - -
- -
-
-
- -

GlobalPrivacySettings

- -

Global privacy settings

-

- -
-
globalPrivacySettings#bea2f424 flags:# archive_and_mute_new_noncontact_peers:flags.0?Bool = GlobalPrivacySettings;
-
----functions---
-
-account.getGlobalPrivacySettings#eb2b4cf6 = GlobalPrivacySettings;
-account.setGlobalPrivacySettings#1edaaac2 settings:GlobalPrivacySettings = GlobalPrivacySettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
globalPrivacySettingsGlobal privacy settings
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
account.getGlobalPrivacySettingsSet global privacy settings
account.setGlobalPrivacySettingsSet global privacy settings
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/GroupCall.html b/data/core.telegram.org/type/GroupCall.html deleted file mode 100644 index 876de85fa7..0000000000 --- a/data/core.telegram.org/type/GroupCall.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - GroupCall - - - - - - - - - - - - - -
- -
-
-
- -

GroupCall

- -

A group call

-

- -
-
groupCallDiscarded#7780bcb4 id:long access_hash:long duration:int = GroupCall;
-groupCall#d597650c flags:# join_muted:flags.1?true can_change_join_muted:flags.2?true join_date_asc:flags.6?true schedule_start_subscribed:flags.8?true can_start_video:flags.9?true record_video_active:flags.11?true id:long access_hash:long participants_count:int title:flags.3?string stream_dc_id:flags.4?int record_start_date:flags.5?int schedule_date:flags.7?int unmuted_video_count:flags.10?int unmuted_video_limit:int version:int = GroupCall;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
groupCallDiscardedAn ended group call
groupCallInfo about a group call or livestream
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/GroupCallParticipant.html b/data/core.telegram.org/type/GroupCallParticipant.html deleted file mode 100644 index b8d2891a5c..0000000000 --- a/data/core.telegram.org/type/GroupCallParticipant.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - GroupCallParticipant - - - - - - - - - - - - - -
- -
-
-
- -

GroupCallParticipant

- -

Info about a group call participant

-

- -
-
groupCallParticipant#eba636fe flags:# muted:flags.0?true left:flags.1?true can_self_unmute:flags.2?true just_joined:flags.4?true versioned:flags.5?true min:flags.8?true muted_by_you:flags.9?true volume_by_admin:flags.10?true self:flags.12?true video_joined:flags.15?true peer:Peer date:int active_date:flags.3?int source:int volume:flags.7?int about:flags.11?string raise_hand_rating:flags.13?long video:flags.6?GroupCallParticipantVideo presentation:flags.14?GroupCallParticipantVideo = GroupCallParticipant;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
groupCallParticipantInfo about a group call participant
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/GroupCallParticipantVideo.html b/data/core.telegram.org/type/GroupCallParticipantVideo.html deleted file mode 100644 index d39d5ab6df..0000000000 --- a/data/core.telegram.org/type/GroupCallParticipantVideo.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - GroupCallParticipantVideo - - - - - - - - - - - - - -
- -
-
-
- -

GroupCallParticipantVideo

- -

Info about a video stream

-

- -
-
groupCallParticipantVideo#67753ac8 flags:# paused:flags.0?true endpoint:string source_groups:Vector<GroupCallParticipantVideoSourceGroup> audio_source:flags.1?int = GroupCallParticipantVideo;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
groupCallParticipantVideoInfo about a video stream
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/GroupCallParticipantVideoSourceGroup.html b/data/core.telegram.org/type/GroupCallParticipantVideoSourceGroup.html deleted file mode 100644 index f170653f12..0000000000 --- a/data/core.telegram.org/type/GroupCallParticipantVideoSourceGroup.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - GroupCallParticipantVideoSourceGroup - - - - - - - - - - - - - -
- -
-
-
- -

GroupCallParticipantVideoSourceGroup

- -

Describes a group of video synchronization source identifiers

-

- -
-
groupCallParticipantVideoSourceGroup#dcb118b7 semantics:string sources:Vector<int> = GroupCallParticipantVideoSourceGroup;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
groupCallParticipantVideoSourceGroupDescribes a group of video synchronization source identifiers
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/HighScore.html b/data/core.telegram.org/type/HighScore.html deleted file mode 100644 index 400288806c..0000000000 --- a/data/core.telegram.org/type/HighScore.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - HighScore - - - - - - - - - - - - - -
- -
-
-
- -

HighScore

- -

Game high score

-

- -
-
highScore#73a379eb pos:int user_id:long score:int = HighScore;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
highScoreGame highscore
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InlineBotSwitchPM.html b/data/core.telegram.org/type/InlineBotSwitchPM.html deleted file mode 100644 index 7e75a42d07..0000000000 --- a/data/core.telegram.org/type/InlineBotSwitchPM.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - InlineBotSwitchPM - - - - - - - - - - - - - -
- -
-
-
- -

InlineBotSwitchPM

- -

The bot requested the user to message him in private

-

- -
-
inlineBotSwitchPM#3c20629f text:string start_param:string = InlineBotSwitchPM;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inlineBotSwitchPMThe bot requested the user to message him in private
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InlineQueryPeerType.html b/data/core.telegram.org/type/InlineQueryPeerType.html deleted file mode 100644 index 8c730017db..0000000000 --- a/data/core.telegram.org/type/InlineQueryPeerType.html +++ /dev/null @@ -1,163 +0,0 @@ - - - - - InlineQueryPeerType - - - - - - - - - - - - - -
- -
-
-
- -

InlineQueryPeerType

- -

Type of the chat from which the inline query was sent.

-

- -
-
inlineQueryPeerTypeSameBotPM#3081ed9d = InlineQueryPeerType;
-inlineQueryPeerTypePM#833c0fac = InlineQueryPeerType;
-inlineQueryPeerTypeChat#d766c50a = InlineQueryPeerType;
-inlineQueryPeerTypeMegagroup#5ec4be43 = InlineQueryPeerType;
-inlineQueryPeerTypeBroadcast#6334ee9a = InlineQueryPeerType;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inlineQueryPeerTypeSameBotPMThe inline query was sent in a private chat with the bot itself
inlineQueryPeerTypePMThe inline query was sent in a private chat
inlineQueryPeerTypeChatThe inline query was sent in a chat
inlineQueryPeerTypeMegagroupThe inline query was sent in a supergroup
inlineQueryPeerTypeBroadcastThe inline query was sent in a channel
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputAppEvent.html b/data/core.telegram.org/type/InputAppEvent.html deleted file mode 100644 index fac7f5bf18..0000000000 --- a/data/core.telegram.org/type/InputAppEvent.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - InputAppEvent - - - - - - - - - - - - - -
- -
-
-
- -

InputAppEvent

- -

Object contains info about an event that occured in the application.

-

- -
-
inputAppEvent#1d1b1245 time:double type:string peer:long data:JSONValue = InputAppEvent;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inputAppEventEvent that occured in the application.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputBotInlineMessage.html b/data/core.telegram.org/type/InputBotInlineMessage.html deleted file mode 100644 index a345efb14a..0000000000 --- a/data/core.telegram.org/type/InputBotInlineMessage.html +++ /dev/null @@ -1,173 +0,0 @@ - - - - - InputBotInlineMessage - - - - - - - - - - - - - -
- -
-
-
- -

InputBotInlineMessage

- -

Represents a sent inline message from the perspective of a bot

-

- -
-
inputBotInlineMessageMediaAuto#3380c786 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageText#3dcd7a87 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageMediaGeo#96929a85 flags:# geo_point:InputGeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageMediaVenue#417bbf11 flags:# geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageMediaContact#a6edbffd flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageGame#4b425864 flags:# reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageMediaInvoice#d7e78225 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputBotInlineMessageMediaAutoA media
inputBotInlineMessageTextSimple text message
inputBotInlineMessageMediaGeoGeolocation
inputBotInlineMessageMediaVenueVenue
inputBotInlineMessageMediaContactA contact
inputBotInlineMessageGameA game
inputBotInlineMessageMediaInvoiceAn invoice
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputBotInlineMessageID.html b/data/core.telegram.org/type/InputBotInlineMessageID.html deleted file mode 100644 index e9fd77229c..0000000000 --- a/data/core.telegram.org/type/InputBotInlineMessageID.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - InputBotInlineMessageID - - - - - - - - - - - - - -
- -
-
-
- -

InputBotInlineMessageID

- -

Represents a sent inline message from the perspective of a bot

-

- -
-
inputBotInlineMessageID#890c3d89 dc_id:int id:long access_hash:long = InputBotInlineMessageID;
-inputBotInlineMessageID64#b6d915d7 dc_id:int owner_id:long id:int access_hash:long = InputBotInlineMessageID;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
inputBotInlineMessageIDRepresents a sent inline message from the perspective of a bot
inputBotInlineMessageID64Represents a sent inline message from the perspective of a bot
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputBotInlineResult.html b/data/core.telegram.org/type/InputBotInlineResult.html deleted file mode 100644 index afc4b9f91f..0000000000 --- a/data/core.telegram.org/type/InputBotInlineResult.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - - InputBotInlineResult - - - - - - - - - - - - - -
- -
-
-
- -

InputBotInlineResult

- -

Inline bot result

-

- -
-
inputBotInlineResult#88bf9319 flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?InputWebDocument content:flags.5?InputWebDocument send_message:InputBotInlineMessage = InputBotInlineResult;
-inputBotInlineResultPhoto#a8d864a7 id:string type:string photo:InputPhoto send_message:InputBotInlineMessage = InputBotInlineResult;
-inputBotInlineResultDocument#fff8fdc4 flags:# id:string type:string title:flags.1?string description:flags.2?string document:InputDocument send_message:InputBotInlineMessage = InputBotInlineResult;
-inputBotInlineResultGame#4fa417f2 id:string short_name:string send_message:InputBotInlineMessage = InputBotInlineResult;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputBotInlineResultAn inline bot result
inputBotInlineResultPhotoPhoto
inputBotInlineResultDocumentDocument (media of any type except for photos)
inputBotInlineResultGameGame
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputChannel.html b/data/core.telegram.org/type/InputChannel.html deleted file mode 100644 index 707ea775f6..0000000000 --- a/data/core.telegram.org/type/InputChannel.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - InputChannel - - - - - - - - - - - - - -
- -
-
-
- -

InputChannel

- -

Represents a channel

-

- -
-
inputChannelEmpty#ee8c1e86 = InputChannel;
-inputChannel#f35aec28 channel_id:long access_hash:long = InputChannel;
-inputChannelFromMessage#5b934f9d peer:InputPeer msg_id:int channel_id:long = InputChannel;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputChannelEmptyRepresents the absence of a channel
inputChannelRepresents a channel
inputChannelFromMessageDefines a min channel that was seen in a certain message of a certain chat.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputChatPhoto.html b/data/core.telegram.org/type/InputChatPhoto.html deleted file mode 100644 index 00b9754a47..0000000000 --- a/data/core.telegram.org/type/InputChatPhoto.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - InputChatPhoto - - - - - - - - - - - - - -
- -
-
-
- -

InputChatPhoto

- -

Defines a new group profile photo.

-

- -
-
inputChatPhotoEmpty#1ca48f57 = InputChatPhoto;
-inputChatUploadedPhoto#c642724e flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = InputChatPhoto;
-inputChatPhoto#8953ad37 id:InputPhoto = InputChatPhoto;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputChatPhotoEmptyEmpty constructor, remove group photo.
inputChatUploadedPhotoNew photo to be set as group profile photo.
inputChatPhotoExisting photo to be set as a chat profile photo.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputCheckPasswordSRP.html b/data/core.telegram.org/type/InputCheckPasswordSRP.html deleted file mode 100644 index 7efd169546..0000000000 --- a/data/core.telegram.org/type/InputCheckPasswordSRP.html +++ /dev/null @@ -1,151 +0,0 @@ - - - - - InputCheckPasswordSRP - - - - - - - - - - - - - -
- -
-
-
- -

InputCheckPasswordSRP

- -

Constructors for checking the validity of a 2FA SRP password

-

- -
-
inputCheckPasswordEmpty#9880f658 = InputCheckPasswordSRP;
-inputCheckPasswordSRP#d27ff082 srp_id:long A:bytes M1:bytes = InputCheckPasswordSRP;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
inputCheckPasswordEmptyThere is no password
inputCheckPasswordSRPConstructor for checking the validity of a 2FA SRP password (see SRP)
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputContact.html b/data/core.telegram.org/type/InputContact.html deleted file mode 100644 index 8992628ec8..0000000000 --- a/data/core.telegram.org/type/InputContact.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - InputContact - - - - - - - - - - - - - -
- -
-
-
- -

InputContact

- -

Object defines a contact from the user's phonebook.

-

- -
-
inputPhoneContact#f392b7f4 client_id:long phone:string first_name:string last_name:string = InputContact;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inputPhoneContactPhone contact. The client_id is just an arbitrary contact ID: it should be set, for example, to an incremental number when using contacts.importContacts, in order to retry importing only the contacts that weren't imported successfully.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputDialogPeer.html b/data/core.telegram.org/type/InputDialogPeer.html deleted file mode 100644 index f1be186d1c..0000000000 --- a/data/core.telegram.org/type/InputDialogPeer.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - InputDialogPeer - - - - - - - - - - - - - -
- -
-
-
- -

InputDialogPeer

- -

Peer, or all peers in a certain folder

-

- -
-
inputDialogPeer#fcaafeb7 peer:InputPeer = InputDialogPeer;
-inputDialogPeerFolder#64600527 folder_id:int = InputDialogPeer;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
inputDialogPeerA peer
inputDialogPeerFolderAll peers in a folder
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputDocument.html b/data/core.telegram.org/type/InputDocument.html deleted file mode 100644 index dbbcccb487..0000000000 --- a/data/core.telegram.org/type/InputDocument.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - InputDocument - - - - - - - - - - - - - -
- -
-
-
- -

InputDocument

- -

Defines a document for subsequent interaction.

-

- -
-
inputDocumentEmpty#72f0eaae = InputDocument;
-inputDocument#1abfb575 id:long access_hash:long file_reference:bytes = InputDocument;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
inputDocumentEmptyEmpty constructor.
inputDocumentDefines a video for subsequent interaction.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputEncryptedChat.html b/data/core.telegram.org/type/InputEncryptedChat.html deleted file mode 100644 index f8a4ee9fd3..0000000000 --- a/data/core.telegram.org/type/InputEncryptedChat.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - InputEncryptedChat - - - - - - - - - - - - - -
- -
-
-
- -

InputEncryptedChat

- -

Object sets an encrypted chat ID.

-

- -
-
inputEncryptedChat#f141b5e1 chat_id:int access_hash:long = InputEncryptedChat;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inputEncryptedChatCreates an encrypted chat.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputEncryptedFile.html b/data/core.telegram.org/type/InputEncryptedFile.html deleted file mode 100644 index 92b7416df6..0000000000 --- a/data/core.telegram.org/type/InputEncryptedFile.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - - InputEncryptedFile - - - - - - - - - - - - - -
- -
-
-
- -

InputEncryptedFile

- -

Object sets encrypted file for attachment

-

- -
-
inputEncryptedFileEmpty#1837c364 = InputEncryptedFile;
-inputEncryptedFileUploaded#64bd0306 id:long parts:int md5_checksum:string key_fingerprint:int = InputEncryptedFile;
-inputEncryptedFile#5a17b5e5 id:long access_hash:long = InputEncryptedFile;
-inputEncryptedFileBigUploaded#2dc173c8 id:long parts:int key_fingerprint:int = InputEncryptedFile;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputEncryptedFileEmptyEmpty constructor.
inputEncryptedFileUploadedSets new encrypted file saved by parts using upload.saveFilePart method.
inputEncryptedFileSets forwarded encrypted file for attachment.
inputEncryptedFileBigUploadedAssigns a new big encrypted file (over 10Mb in size), saved in parts using the method upload.saveBigFilePart.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputFile.html b/data/core.telegram.org/type/InputFile.html deleted file mode 100644 index 3b71dbb92a..0000000000 --- a/data/core.telegram.org/type/InputFile.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - InputFile - - - - - - - - - - - - - -
- -
-
-
- -

InputFile

- -

Defines a file uploaded by the client.

-

- -
-
inputFile#f52ff27f id:long parts:int name:string md5_checksum:string = InputFile;
-inputFileBig#fa4f0bb5 id:long parts:int name:string = InputFile;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
inputFileDefines a file saved in parts using the method upload.saveFilePart.
inputFileBigAssigns a big file (over 10Mb in size), saved in part using the method upload.saveBigFilePart.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputFileLocation.html b/data/core.telegram.org/type/InputFileLocation.html deleted file mode 100644 index 5628c999b6..0000000000 --- a/data/core.telegram.org/type/InputFileLocation.html +++ /dev/null @@ -1,188 +0,0 @@ - - - - - InputFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

InputFileLocation

- -

Defines the location of a file for download.

-

- -
-
inputFileLocation#dfdaabe1 volume_id:long local_id:int secret:long file_reference:bytes = InputFileLocation;
-inputEncryptedFileLocation#f5235d55 id:long access_hash:long = InputFileLocation;
-inputDocumentFileLocation#bad07584 id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;
-inputSecureFileLocation#cbc7ee28 id:long access_hash:long = InputFileLocation;
-inputTakeoutFileLocation#29be5899 = InputFileLocation;
-inputPhotoFileLocation#40181ffe id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;
-inputPhotoLegacyFileLocation#d83466f3 id:long access_hash:long file_reference:bytes volume_id:long local_id:int secret:long = InputFileLocation;
-inputPeerPhotoFileLocation#37257e99 flags:# big:flags.0?true peer:InputPeer photo_id:long = InputFileLocation;
-inputStickerSetThumb#9d84f3db stickerset:InputStickerSet thumb_version:int = InputFileLocation;
-inputGroupCallStream#598a92a flags:# call:InputGroupCall time_ms:long scale:int video_channel:flags.0?int video_quality:flags.0?int = InputFileLocation;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputFileLocationDEPRECATED location of a photo
inputEncryptedFileLocationLocation of encrypted secret chat file.
inputDocumentFileLocationDocument location (video, voice, audio, basically every type except photo)
inputSecureFileLocationLocation of encrypted telegram passport file.
inputTakeoutFileLocationEmpty constructor for takeout
inputPhotoFileLocationUse this object to download a photo with upload.getFile method
inputPhotoLegacyFileLocationLegacy file location
inputPeerPhotoFileLocationLocation of profile photo of channel/group/supergroup/user
inputStickerSetThumbLocation of stickerset thumbnail (see files)
inputGroupCallStreamChunk of a livestream
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputGame.html b/data/core.telegram.org/type/InputGame.html deleted file mode 100644 index 0793c16933..0000000000 --- a/data/core.telegram.org/type/InputGame.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - InputGame - - - - - - - - - - - - - -
- -
-
-
- -

InputGame

- -

A game to send

-

- -
-
inputGameID#32c3e77 id:long access_hash:long = InputGame;
-inputGameShortName#c331e80a bot_id:InputUser short_name:string = InputGame;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
inputGameIDIndicates an already sent game
inputGameShortNameGame by short name
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputGeoPoint.html b/data/core.telegram.org/type/InputGeoPoint.html deleted file mode 100644 index 7cd476bd42..0000000000 --- a/data/core.telegram.org/type/InputGeoPoint.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - InputGeoPoint - - - - - - - - - - - - - -
- -
-
-
- -

InputGeoPoint

- -

Defines a GeoPoint.

-

- -
-
inputGeoPointEmpty#e4c123d6 = InputGeoPoint;
-inputGeoPoint#48222faf flags:# lat:double long:double accuracy_radius:flags.0?int = InputGeoPoint;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
inputGeoPointEmptyEmpty GeoPoint constructor.
inputGeoPointDefines a GeoPoint by its coordinates.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputGroupCall.html b/data/core.telegram.org/type/InputGroupCall.html deleted file mode 100644 index c1dc72f9a4..0000000000 --- a/data/core.telegram.org/type/InputGroupCall.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - InputGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

InputGroupCall

- -

Indicates a group call

-

- -
-
inputGroupCall#d8aa840f id:long access_hash:long = InputGroupCall;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inputGroupCallPoints to a specific group call
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputMedia.html b/data/core.telegram.org/type/InputMedia.html deleted file mode 100644 index 048a3c1d2b..0000000000 --- a/data/core.telegram.org/type/InputMedia.html +++ /dev/null @@ -1,213 +0,0 @@ - - - - - InputMedia - - - - - - - - - - - - - -
- -
-
-
- -

InputMedia

- -

Defines media content of a message.

-

- -
-
inputMediaEmpty#9664f57f = InputMedia;
-inputMediaUploadedPhoto#1e287d04 flags:# file:InputFile stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
-inputMediaPhoto#b3ba0635 flags:# id:InputPhoto ttl_seconds:flags.0?int = InputMedia;
-inputMediaGeoPoint#f9c44144 geo_point:InputGeoPoint = InputMedia;
-inputMediaContact#f8ab7dfb phone_number:string first_name:string last_name:string vcard:string = InputMedia;
-inputMediaUploadedDocument#5b38c6c1 flags:# nosound_video:flags.3?true force_file:flags.4?true file:InputFile thumb:flags.2?InputFile mime_type:string attributes:Vector<DocumentAttribute> stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
-inputMediaDocument#33473058 flags:# id:InputDocument ttl_seconds:flags.0?int query:flags.1?string = InputMedia;
-inputMediaVenue#c13d1c11 geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string = InputMedia;
-inputMediaPhotoExternal#e5bbfe1a flags:# url:string ttl_seconds:flags.0?int = InputMedia;
-inputMediaDocumentExternal#fb52dc99 flags:# url:string ttl_seconds:flags.0?int = InputMedia;
-inputMediaGame#d33f43f3 id:InputGame = InputMedia;
-inputMediaInvoice#d9799874 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON start_param:flags.1?string = InputMedia;
-inputMediaGeoLive#971fa843 flags:# stopped:flags.0?true geo_point:InputGeoPoint heading:flags.2?int period:flags.1?int proximity_notification_radius:flags.3?int = InputMedia;
-inputMediaPoll#f94e5f1 flags:# poll:Poll correct_answers:flags.0?Vector<bytes> solution:flags.1?string solution_entities:flags.1?Vector<MessageEntity> = InputMedia;
-inputMediaDice#e66fbf7b emoticon:string = InputMedia;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputMediaEmptyEmpty media content of a message.
inputMediaUploadedPhotoPhoto
inputMediaPhotoForwarded photo
inputMediaGeoPointMap.
inputMediaContactPhonebook contact
inputMediaUploadedDocumentNew document
inputMediaDocumentForwarded document
inputMediaVenueCan be used to send a venue geolocation.
inputMediaPhotoExternalNew photo that will be uploaded by the server using the specified URL
inputMediaDocumentExternalDocument that will be downloaded by the telegram servers
inputMediaGameA game
inputMediaInvoiceGenerated invoice of a bot payment
inputMediaGeoLiveLive geographical location
inputMediaPollA poll
inputMediaDiceSend a dice in the chat
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputMessage.html b/data/core.telegram.org/type/InputMessage.html deleted file mode 100644 index 07b7c6ef55..0000000000 --- a/data/core.telegram.org/type/InputMessage.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - - InputMessage - - - - - - - - - - - - - -
- -
-
-
- -

InputMessage

- -

A message

-

- -
-
inputMessageID#a676a322 id:int = InputMessage;
-inputMessageReplyTo#bad88395 id:int = InputMessage;
-inputMessagePinned#86872538 = InputMessage;
-inputMessageCallbackQuery#acfa1a7e id:int query_id:long = InputMessage;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputMessageIDMessage by ID
inputMessageReplyToMessage to which the specified message replies to
inputMessagePinnedPinned message
inputMessageCallbackQueryUsed by bots for fetching information about the message that originated a callback query
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputNotifyPeer.html b/data/core.telegram.org/type/InputNotifyPeer.html deleted file mode 100644 index 29b7da1285..0000000000 --- a/data/core.telegram.org/type/InputNotifyPeer.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - - InputNotifyPeer - - - - - - - - - - - - - -
- -
-
-
- -

InputNotifyPeer

- -

Object defines the set of users and/or groups that generate notifications.

-

- -
-
inputNotifyPeer#b8bc5b0c peer:InputPeer = InputNotifyPeer;
-inputNotifyUsers#193b4417 = InputNotifyPeer;
-inputNotifyChats#4a95e84e = InputNotifyPeer;
-inputNotifyBroadcasts#b1db7c7e = InputNotifyPeer;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputNotifyPeerNotifications generated by a certain user or group.
inputNotifyUsersNotifications generated by all users.
inputNotifyChatsNotifications generated by all groups.
inputNotifyBroadcastsAll channels
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputPaymentCredentials.html b/data/core.telegram.org/type/InputPaymentCredentials.html deleted file mode 100644 index a1022825e7..0000000000 --- a/data/core.telegram.org/type/InputPaymentCredentials.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - - InputPaymentCredentials - - - - - - - - - - - - - -
- -
-
-
- -

InputPaymentCredentials

- -

Payment credentials

-

- -
-
inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;
-inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
-inputPaymentCredentialsApplePay#aa1c39f payment_data:DataJSON = InputPaymentCredentials;
-inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputPaymentCredentialsSavedSaved payment credentials
inputPaymentCredentialsPayment credentials
inputPaymentCredentialsApplePayApple pay payment credentials
inputPaymentCredentialsGooglePayGoogle Pay payment credentials
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputPeer.html b/data/core.telegram.org/type/InputPeer.html deleted file mode 100644 index 4ab7b227c0..0000000000 --- a/data/core.telegram.org/type/InputPeer.html +++ /dev/null @@ -1,173 +0,0 @@ - - - - - InputPeer - - - - - - - - - - - - - -
- -
-
-
- -

InputPeer

- -

Peer

-

- -
-
inputPeerEmpty#7f3b18ea = InputPeer;
-inputPeerSelf#7da07ec9 = InputPeer;
-inputPeerChat#35a95cb9 chat_id:long = InputPeer;
-inputPeerUser#dde8a54c user_id:long access_hash:long = InputPeer;
-inputPeerChannel#27bcbbfc channel_id:long access_hash:long = InputPeer;
-inputPeerUserFromMessage#a87b0a1c peer:InputPeer msg_id:int user_id:long = InputPeer;
-inputPeerChannelFromMessage#bd2a0840 peer:InputPeer msg_id:int channel_id:long = InputPeer;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputPeerEmptyAn empty constructor, no user or chat is defined.
inputPeerSelfDefines the current user.
inputPeerChatDefines a chat for further interaction.
inputPeerUserDefines a user for further interaction.
inputPeerChannelDefines a channel for further interaction.
inputPeerUserFromMessageDefines a min user that was seen in a certain message of a certain chat.
inputPeerChannelFromMessageDefines a min channel that was seen in a certain message of a certain chat.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputPeerNotifySettings.html b/data/core.telegram.org/type/InputPeerNotifySettings.html deleted file mode 100644 index 8d9d1ca7d9..0000000000 --- a/data/core.telegram.org/type/InputPeerNotifySettings.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - InputPeerNotifySettings - - - - - - - - - - - - - -
- -
-
-
- -

InputPeerNotifySettings

- -

Notifications settings.

-

- -
-
inputPeerNotifySettings#9c3d198e flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = InputPeerNotifySettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inputPeerNotifySettingsNotification settings.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputPhoneCall.html b/data/core.telegram.org/type/InputPhoneCall.html deleted file mode 100644 index d94189a022..0000000000 --- a/data/core.telegram.org/type/InputPhoneCall.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - InputPhoneCall - - - - - - - - - - - - - -
- -
-
-
- -

InputPhoneCall

- -

Phone call

-

- -
-
inputPhoneCall#1e36fded id:long access_hash:long = InputPhoneCall;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inputPhoneCallPhone call
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputPhoto.html b/data/core.telegram.org/type/InputPhoto.html deleted file mode 100644 index a8c395e2c9..0000000000 --- a/data/core.telegram.org/type/InputPhoto.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - InputPhoto - - - - - - - - - - - - - -
- -
-
-
- -

InputPhoto

- -

Defines a photo for further interaction.

-

- -
-
inputPhotoEmpty#1cd7bf0d = InputPhoto;
-inputPhoto#3bb3b94a id:long access_hash:long file_reference:bytes = InputPhoto;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
inputPhotoEmptyEmpty constructor.
inputPhotoDefines a photo for further interaction.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputPrivacyKey.html b/data/core.telegram.org/type/InputPrivacyKey.html deleted file mode 100644 index ea4b22031f..0000000000 --- a/data/core.telegram.org/type/InputPrivacyKey.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - InputPrivacyKey - - - - - - - - - - - - - -
- -
-
-
- -

InputPrivacyKey

- -

Privacy key

-

- -
-
inputPrivacyKeyStatusTimestamp#4f96cb18 = InputPrivacyKey;
-inputPrivacyKeyChatInvite#bdfb0426 = InputPrivacyKey;
-inputPrivacyKeyPhoneCall#fabadc5f = InputPrivacyKey;
-inputPrivacyKeyPhoneP2P#db9e70d2 = InputPrivacyKey;
-inputPrivacyKeyForwards#a4dd4c08 = InputPrivacyKey;
-inputPrivacyKeyProfilePhoto#5719bacc = InputPrivacyKey;
-inputPrivacyKeyPhoneNumber#352dafa = InputPrivacyKey;
-inputPrivacyKeyAddedByPhone#d1219bdd = InputPrivacyKey;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputPrivacyKeyStatusTimestampWhether we can see the exact last online timestamp of the user
inputPrivacyKeyChatInviteWhether the user can be invited to chats
inputPrivacyKeyPhoneCallWhether the user will accept phone calls
inputPrivacyKeyPhoneP2PWhether the user allows P2P communication during VoIP calls
inputPrivacyKeyForwardsWhether messages forwarded from this user will be anonymous
inputPrivacyKeyProfilePhotoWhether people will be able to see the user's profile picture
inputPrivacyKeyPhoneNumberWhether people will be able to see the user's phone number
inputPrivacyKeyAddedByPhoneWhether people can add you to their contact list by your phone number
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputPrivacyRule.html b/data/core.telegram.org/type/InputPrivacyRule.html deleted file mode 100644 index f69fefd909..0000000000 --- a/data/core.telegram.org/type/InputPrivacyRule.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - InputPrivacyRule - - - - - - - - - - - - - -
- -
-
-
- -

InputPrivacyRule

- -

Privacy rule

-

- -
-
inputPrivacyValueAllowContacts#d09e07b = InputPrivacyRule;
-inputPrivacyValueAllowAll#184b35ce = InputPrivacyRule;
-inputPrivacyValueAllowUsers#131cc67f users:Vector<InputUser> = InputPrivacyRule;
-inputPrivacyValueDisallowContacts#ba52007 = InputPrivacyRule;
-inputPrivacyValueDisallowAll#d66b66c9 = InputPrivacyRule;
-inputPrivacyValueDisallowUsers#90110467 users:Vector<InputUser> = InputPrivacyRule;
-inputPrivacyValueAllowChatParticipants#840649cf chats:Vector<long> = InputPrivacyRule;
-inputPrivacyValueDisallowChatParticipants#e94f0f86 chats:Vector<long> = InputPrivacyRule;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputPrivacyValueAllowContactsAllow only contacts
inputPrivacyValueAllowAllAllow all users
inputPrivacyValueAllowUsersAllow only certain users
inputPrivacyValueDisallowContactsDisallow only contacts
inputPrivacyValueDisallowAllDisallow all
inputPrivacyValueDisallowUsersDisallow only certain users
inputPrivacyValueAllowChatParticipantsAllow only participants of certain chats
inputPrivacyValueDisallowChatParticipantsDisallow only participants of certain chats
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputSecureFile.html b/data/core.telegram.org/type/InputSecureFile.html deleted file mode 100644 index 3d03f4afc7..0000000000 --- a/data/core.telegram.org/type/InputSecureFile.html +++ /dev/null @@ -1,151 +0,0 @@ - - - - - InputSecureFile - - - - - - - - - - - - - -
- -
-
-
- -

InputSecureFile

- -

Secure passport file, for more info see the passport docs »

-

- -
-
inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;
-inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
inputSecureFileUploadedUploaded secure file, for more info see the passport docs »
inputSecureFilePreuploaded passport file, for more info see the passport docs »
-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputSecureValue.html b/data/core.telegram.org/type/InputSecureValue.html deleted file mode 100644 index 6de27de5d0..0000000000 --- a/data/core.telegram.org/type/InputSecureValue.html +++ /dev/null @@ -1,145 +0,0 @@ - - - - - InputSecureValue - - - - - - - - - - - - - -
- -
-
-
- -

InputSecureValue

- -

Secure value, for more info see the passport docs »

-

- -
-
inputSecureValue#db21d0a7 flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?InputSecureFile reverse_side:flags.2?InputSecureFile selfie:flags.3?InputSecureFile translation:flags.6?Vector<InputSecureFile> files:flags.4?Vector<InputSecureFile> plain_data:flags.5?SecurePlainData = InputSecureValue;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inputSecureValueSecure value, for more info see the passport docs »
-

Related pages

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputStickerSet.html b/data/core.telegram.org/type/InputStickerSet.html deleted file mode 100644 index 4683b32505..0000000000 --- a/data/core.telegram.org/type/InputStickerSet.html +++ /dev/null @@ -1,168 +0,0 @@ - - - - - InputStickerSet - - - - - - - - - - - - - -
- -
-
-
- -

InputStickerSet

- -

Represents a stickerset

-

- -
-
inputStickerSetEmpty#ffb62b95 = InputStickerSet;
-inputStickerSetID#9de7a269 id:long access_hash:long = InputStickerSet;
-inputStickerSetShortName#861cc8a0 short_name:string = InputStickerSet;
-inputStickerSetAnimatedEmoji#28703c8 = InputStickerSet;
-inputStickerSetDice#e67f520e emoticon:string = InputStickerSet;
-inputStickerSetAnimatedEmojiAnimations#cde3739 = InputStickerSet;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputStickerSetEmptyEmpty constructor
inputStickerSetIDStickerset by ID
inputStickerSetShortNameStickerset by short name, from tg://addstickers?set=short_name
inputStickerSetAnimatedEmojiAnimated emojis stickerset
inputStickerSetDiceSend a dice
inputStickerSetAnimatedEmojiAnimationsAnimated emoji reaction stickerset (contains animations to play when a user clicks on a given animated emoji)
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputStickerSetItem.html b/data/core.telegram.org/type/InputStickerSetItem.html deleted file mode 100644 index 67da6bdecb..0000000000 --- a/data/core.telegram.org/type/InputStickerSetItem.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - InputStickerSetItem - - - - - - - - - - - - - -
- -
-
-
- -

InputStickerSetItem

- -

Sticker

-

- -
-
inputStickerSetItem#ffa0a496 flags:# document:InputDocument emoji:string mask_coords:flags.0?MaskCoords = InputStickerSetItem;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inputStickerSetItemSticker in a stickerset
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputStickeredMedia.html b/data/core.telegram.org/type/InputStickeredMedia.html deleted file mode 100644 index 0eecf98e65..0000000000 --- a/data/core.telegram.org/type/InputStickeredMedia.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - InputStickeredMedia - - - - - - - - - - - - - -
- -
-
-
- -

InputStickeredMedia

- -

Represents a media with attached stickers

-

- -
-
inputStickeredMediaPhoto#4a992157 id:InputPhoto = InputStickeredMedia;
-inputStickeredMediaDocument#438865b id:InputDocument = InputStickeredMedia;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
inputStickeredMediaPhotoA photo with stickers attached
inputStickeredMediaDocumentA document with stickers attached
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputTheme.html b/data/core.telegram.org/type/InputTheme.html deleted file mode 100644 index 039413483d..0000000000 --- a/data/core.telegram.org/type/InputTheme.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - InputTheme - - - - - - - - - - - - - -
- -
-
-
- -

InputTheme

- -

Cloud theme

-

- -
-
inputTheme#3c5693e9 id:long access_hash:long = InputTheme;
-inputThemeSlug#f5890df1 slug:string = InputTheme;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
inputThemeTheme
inputThemeSlugTheme by theme ID
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputThemeSettings.html b/data/core.telegram.org/type/InputThemeSettings.html deleted file mode 100644 index f605e410c0..0000000000 --- a/data/core.telegram.org/type/InputThemeSettings.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - InputThemeSettings - - - - - - - - - - - - - -
- -
-
-
- -

InputThemeSettings

- -

Theme settings

-

- -
-
inputThemeSettings#8fde504f flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int outbox_accent_color:flags.3?int message_colors:flags.0?Vector<int> wallpaper:flags.1?InputWallPaper wallpaper_settings:flags.1?WallPaperSettings = InputThemeSettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inputThemeSettingsTheme settings
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputUser.html b/data/core.telegram.org/type/InputUser.html deleted file mode 100644 index ed465499f3..0000000000 --- a/data/core.telegram.org/type/InputUser.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - - InputUser - - - - - - - - - - - - - -
- -
-
-
- -

InputUser

- -

Defines a user for subsequent interaction.

-

- -
-
inputUserEmpty#b98886cf = InputUser;
-inputUserSelf#f7c1b13f = InputUser;
-inputUser#f21158c6 user_id:long access_hash:long = InputUser;
-inputUserFromMessage#1da448e2 peer:InputPeer msg_id:int user_id:long = InputUser;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputUserEmptyEmpty constructor, does not define a user.
inputUserSelfDefines the current user.
inputUserDefines a user for further interaction.
inputUserFromMessageDefines a min user that was seen in a certain message of a certain chat.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputWallPaper.html b/data/core.telegram.org/type/InputWallPaper.html deleted file mode 100644 index 050f43dac4..0000000000 --- a/data/core.telegram.org/type/InputWallPaper.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - InputWallPaper - - - - - - - - - - - - - -
- -
-
-
- -

InputWallPaper

- -

Wallpaper

-

- -
-
inputWallPaper#e630b979 id:long access_hash:long = InputWallPaper;
-inputWallPaperSlug#72091c80 slug:string = InputWallPaper;
-inputWallPaperNoFile#967a462e id:long = InputWallPaper;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputWallPaperWallpaper
inputWallPaperSlugWallpaper by slug (a unique ID)
inputWallPaperNoFileWallpaper with no file
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/InputWebFileLocation.html b/data/core.telegram.org/type/InputWebFileLocation.html deleted file mode 100644 index 29e25fee26..0000000000 --- a/data/core.telegram.org/type/InputWebFileLocation.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - InputWebFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

InputWebFileLocation

- -

Location of remote file

-

- -
-
inputWebFileLocation#c239d686 url:string access_hash:long = InputWebFileLocation;
-inputWebFileGeoPointLocation#9f2221c9 geo_point:InputGeoPoint access_hash:long w:int h:int zoom:int scale:int = InputWebFileLocation;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
inputWebFileLocationLocation of a remote HTTP(s) file
inputWebFileGeoPointLocationGeolocation
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Invoice.html b/data/core.telegram.org/type/Invoice.html deleted file mode 100644 index bdf5a48dbc..0000000000 --- a/data/core.telegram.org/type/Invoice.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - Invoice - - - - - - - - - - - - - -
- -
-
-
- -

Invoice

- -

Invoice

-

- -
-
invoice#cd886e0 flags:# test:flags.0?true name_requested:flags.1?true phone_requested:flags.2?true email_requested:flags.3?true shipping_address_requested:flags.4?true flexible:flags.5?true phone_to_provider:flags.6?true email_to_provider:flags.7?true currency:string prices:Vector<LabeledPrice> max_tip_amount:flags.8?long suggested_tip_amounts:flags.8?Vector<long> = Invoice;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
invoiceInvoice
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/JSONObjectValue.html b/data/core.telegram.org/type/JSONObjectValue.html deleted file mode 100644 index c4dfeaee82..0000000000 --- a/data/core.telegram.org/type/JSONObjectValue.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - JSONObjectValue - - - - - - - - - - - - - -
- -
-
-
- -

JSONObjectValue

- -

JSON key: value pair

-

- -
-
jsonObjectValue#c0de1bd9 key:string value:JSONValue = JSONObjectValue;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
jsonObjectValueJSON key: value pair
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/JSONValue.html b/data/core.telegram.org/type/JSONValue.html deleted file mode 100644 index e0179988f3..0000000000 --- a/data/core.telegram.org/type/JSONValue.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - JSONValue - - - - - - - - - - - - - -
- -
-
-
- -

JSONValue

- -

JSON value

-

- -
-
jsonNull#3f6d7b68 = JSONValue;
-jsonBool#c7345e6a value:Bool = JSONValue;
-jsonNumber#2be0dfa4 value:double = JSONValue;
-jsonString#b71e767a value:string = JSONValue;
-jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;
-jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;
-
----functions---
-
-help.getAppConfig#98914110 = JSONValue;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
jsonNullnull JSON value
jsonBoolJSON boolean value
jsonNumberJSON numeric value
jsonStringJSON string
jsonArrayJSON array
jsonObjectJSON object value
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getAppConfigGet app-specific configuration
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/KeyboardButton.html b/data/core.telegram.org/type/KeyboardButton.html deleted file mode 100644 index 61ffafc3b9..0000000000 --- a/data/core.telegram.org/type/KeyboardButton.html +++ /dev/null @@ -1,193 +0,0 @@ - - - - - KeyboardButton - - - - - - - - - - - - - -
- -
-
-
- -

KeyboardButton

- -

Bot or inline keyboard buttons

-

- -
-
keyboardButton#a2fa4880 text:string = KeyboardButton;
-keyboardButtonUrl#258aff05 text:string url:string = KeyboardButton;
-keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;
-keyboardButtonRequestPhone#b16a6c29 text:string = KeyboardButton;
-keyboardButtonRequestGeoLocation#fc796b3f text:string = KeyboardButton;
-keyboardButtonSwitchInline#568a748 flags:# same_peer:flags.0?true text:string query:string = KeyboardButton;
-keyboardButtonGame#50f41ccf text:string = KeyboardButton;
-keyboardButtonBuy#afd93fbb text:string = KeyboardButton;
-keyboardButtonUrlAuth#10b78d29 flags:# text:string fwd_text:flags.0?string url:string button_id:int = KeyboardButton;
-inputKeyboardButtonUrlAuth#d02e7fd4 flags:# request_write_access:flags.0?true text:string fwd_text:flags.1?string url:string bot:InputUser = KeyboardButton;
-keyboardButtonRequestPoll#bbc7515d flags:# quiz:flags.0?Bool text:string = KeyboardButton;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
keyboardButtonBot keyboard button
keyboardButtonUrlURL button
keyboardButtonCallbackCallback button
keyboardButtonRequestPhoneButton to request a user's phone number
keyboardButtonRequestGeoLocationButton to request a user's geolocation
keyboardButtonSwitchInlineButton to force a user to switch to inline mode Pressing the button will prompt the user to select one of their chats, open that chat and insert the bot‘s username and the specified inline query in the input field.
keyboardButtonGameButton to start a game
keyboardButtonBuyButton to buy a product
keyboardButtonUrlAuthButton to request a user to authorize via URL using Seamless Telegram Login. When the user clicks on such a button, messages.requestUrlAuth should be called, providing the button_id and the ID of the container message. The returned urlAuthResultRequest object will contain more details about the authorization request (request_write_access if the bot would like to send messages to the user along with the username of the bot which will be used for user authorization). Finally, the user can choose to call messages.acceptUrlAuth to get a urlAuthResultAccepted with the URL to open instead of the url of this constructor, or a urlAuthResultDefault, in which case the url of this constructor must be opened, instead. If the user refuses the authorization request but still wants to open the link, the url of this constructor must be used.
inputKeyboardButtonUrlAuthButton to request a user to authorize via URL using Seamless Telegram Login.
keyboardButtonRequestPollA button that allows the user to create and send a poll when pressed; available only in private
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/KeyboardButtonRow.html b/data/core.telegram.org/type/KeyboardButtonRow.html deleted file mode 100644 index 9888c0004d..0000000000 --- a/data/core.telegram.org/type/KeyboardButtonRow.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - KeyboardButtonRow - - - - - - - - - - - - - -
- -
-
-
- -

KeyboardButtonRow

- -

Bot or inline keyboard rows

-

- -
-
keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
keyboardButtonRowInline keyboard row
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/LabeledPrice.html b/data/core.telegram.org/type/LabeledPrice.html deleted file mode 100644 index 7eb7f86d98..0000000000 --- a/data/core.telegram.org/type/LabeledPrice.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - LabeledPrice - - - - - - - - - - - - - -
- -
-
-
- -

LabeledPrice

- -

Labeled pricetag

-

- -
-
labeledPrice#cb296bf8 label:string amount:long = LabeledPrice;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
labeledPriceThis object represents a portion of the price for goods or services.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/LangPackDifference.html b/data/core.telegram.org/type/LangPackDifference.html deleted file mode 100644 index 23fbb1494f..0000000000 --- a/data/core.telegram.org/type/LangPackDifference.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - LangPackDifference - - - - - - - - - - - - - -
- -
-
-
- -

LangPackDifference

- -

Language pack changes

-

- -
-
langPackDifference#f385c1f6 lang_code:string from_version:int version:int strings:Vector<LangPackString> = LangPackDifference;
-
----functions---
-
-langpack.getLangPack#f2f2330a lang_pack:string lang_code:string = LangPackDifference;
-langpack.getDifference#cd984aa5 lang_pack:string lang_code:string from_version:int = LangPackDifference;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
langPackDifferenceChanges to the app's localization pack
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
langpack.getLangPackGet localization pack strings
langpack.getDifferenceGet new strings in languagepack
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/LangPackLanguage.html b/data/core.telegram.org/type/LangPackLanguage.html deleted file mode 100644 index 29ef8513d7..0000000000 --- a/data/core.telegram.org/type/LangPackLanguage.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - LangPackLanguage - - - - - - - - - - - - - -
- -
-
-
- -

LangPackLanguage

- -

Language pack language

-

- -
-
langPackLanguage#eeca5ce3 flags:# official:flags.0?true rtl:flags.2?true beta:flags.3?true name:string native_name:string lang_code:string base_lang_code:flags.1?string plural_code:string strings_count:int translated_count:int translations_url:string = LangPackLanguage;
-
----functions---
-
-langpack.getLanguage#6a596502 lang_pack:string lang_code:string = LangPackLanguage;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
langPackLanguageIdentifies a localization pack
-

Methods

- - - - - - - - - - - - - -
MethodDescription
langpack.getLanguageGet information about a language in a localization pack
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/LangPackString.html b/data/core.telegram.org/type/LangPackString.html deleted file mode 100644 index 68ef3edc31..0000000000 --- a/data/core.telegram.org/type/LangPackString.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - LangPackString - - - - - - - - - - - - - -
- -
-
-
- -

LangPackString

- -

Language pack string

-

- -
-
langPackString#cad181f6 key:string value:string = LangPackString;
-langPackStringPluralized#6c47ac9f flags:# key:string zero_value:flags.0?string one_value:flags.1?string two_value:flags.2?string few_value:flags.3?string many_value:flags.4?string other_value:string = LangPackString;
-langPackStringDeleted#2979eeb2 key:string = LangPackString;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
langPackStringTranslated localization string
langPackStringPluralizedA language pack string which has different forms based on the number of some object it mentions. See https://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html for more info
langPackStringDeletedDeleted localization string
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/MaskCoords.html b/data/core.telegram.org/type/MaskCoords.html deleted file mode 100644 index fa939dec50..0000000000 --- a/data/core.telegram.org/type/MaskCoords.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - MaskCoords - - - - - - - - - - - - - -
- -
-
-
- -

MaskCoords

- -

Mask coordinates (if this is a mask sticker, attached to a photo)

-

- -
-
maskCoords#aed6dbb2 n:int x:double y:double zoom:double = MaskCoords;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
maskCoordsPosition on a photo where a mask should be placed

The n position indicates where the mask should be placed:

- 0 => Relative to the forehead
- 1 => Relative to the eyes
- 2 => Relative to the mouth
- 3 => Relative to the chin
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Message.html b/data/core.telegram.org/type/Message.html deleted file mode 100644 index 0f402c6052..0000000000 --- a/data/core.telegram.org/type/Message.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - Message - - - - - - - - - - - - - -
- -
-
-
- -

Message

- -

Object describing a message.

-

- -
-
messageEmpty#90a6ca84 flags:# id:int peer_id:flags.0?Peer = Message;
-message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true noforwards:flags.26?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
-messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
messageEmptyEmpty constructor, non-existent message.
messageA message
messageServiceIndicates a service message
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/MessageAction.html b/data/core.telegram.org/type/MessageAction.html deleted file mode 100644 index 0df8432505..0000000000 --- a/data/core.telegram.org/type/MessageAction.html +++ /dev/null @@ -1,283 +0,0 @@ - - - - - MessageAction - - - - - - - - - - - - - -
- -
-
-
- -

MessageAction

- -

Object describing actions connected to a service message.

-

- -
-
messageActionEmpty#b6aef7b0 = MessageAction;
-messageActionChatCreate#bd47cbad title:string users:Vector<long> = MessageAction;
-messageActionChatEditTitle#b5a1ce5a title:string = MessageAction;
-messageActionChatEditPhoto#7fcb13a8 photo:Photo = MessageAction;
-messageActionChatDeletePhoto#95e3fbef = MessageAction;
-messageActionChatAddUser#15cefd00 users:Vector<long> = MessageAction;
-messageActionChatDeleteUser#a43f30cc user_id:long = MessageAction;
-messageActionChatJoinedByLink#31224c3 inviter_id:long = MessageAction;
-messageActionChannelCreate#95d2ac92 title:string = MessageAction;
-messageActionChatMigrateTo#e1037f92 channel_id:long = MessageAction;
-messageActionChannelMigrateFrom#ea3948e9 title:string chat_id:long = MessageAction;
-messageActionPinMessage#94bd38ed = MessageAction;
-messageActionHistoryClear#9fbab604 = MessageAction;
-messageActionGameScore#92a72876 game_id:long score:int = MessageAction;
-messageActionPaymentSentMe#8f31b327 flags:# currency:string total_amount:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string charge:PaymentCharge = MessageAction;
-messageActionPaymentSent#40699cd0 currency:string total_amount:long = MessageAction;
-messageActionPhoneCall#80e11a7f flags:# video:flags.2?true call_id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = MessageAction;
-messageActionScreenshotTaken#4792929b = MessageAction;
-messageActionCustomAction#fae69f56 message:string = MessageAction;
-messageActionBotAllowed#abe9affe domain:string = MessageAction;
-messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction;
-messageActionSecureValuesSent#d95c6154 types:Vector<SecureValueType> = MessageAction;
-messageActionContactSignUp#f3f25f76 = MessageAction;
-messageActionGeoProximityReached#98e0d697 from_id:Peer to_id:Peer distance:int = MessageAction;
-messageActionGroupCall#7a0d7f42 flags:# call:InputGroupCall duration:flags.0?int = MessageAction;
-messageActionInviteToGroupCall#502f92f7 call:InputGroupCall users:Vector<long> = MessageAction;
-messageActionSetMessagesTTL#aa1afbfd period:int = MessageAction;
-messageActionGroupCallScheduled#b3a07661 call:InputGroupCall schedule_date:int = MessageAction;
-messageActionSetChatTheme#aa786345 emoticon:string = MessageAction;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
messageActionEmptyEmpty constructor.
messageActionChatCreateGroup created
messageActionChatEditTitleGroup name changed.
messageActionChatEditPhotoGroup profile changed
messageActionChatDeletePhotoGroup profile photo removed.
messageActionChatAddUserNew member in the group
messageActionChatDeleteUserUser left the group.
messageActionChatJoinedByLinkA user joined the chat via an invite link
messageActionChannelCreateThe channel was created
messageActionChatMigrateToIndicates the chat was migrated to the specified supergroup
messageActionChannelMigrateFromIndicates the channel was migrated from the specified chat
messageActionPinMessageA message was pinned
messageActionHistoryClearChat history was cleared
messageActionGameScoreSomeone scored in a game
messageActionPaymentSentMeA user just sent a payment to me (a bot)
messageActionPaymentSentA payment was sent
messageActionPhoneCallA phone call
messageActionScreenshotTakenA screenshot of the chat was taken
messageActionCustomActionCustom action (most likely not supported by the current layer, an upgrade might be needed)
messageActionBotAllowedThe domain name of the website on which the user has logged in. More about Telegram Login »
messageActionSecureValuesSentMeSecure telegram passport values were received
messageActionSecureValuesSentRequest for secure telegram passport values was sent
messageActionContactSignUpA contact just signed up to telegram
messageActionGeoProximityReachedWe are now in proximity of this user (triggered by the other user, by sending a live geolocation with the proximity_notification_radius flag)
messageActionGroupCallThe group call has ended
messageActionInviteToGroupCallA set of users was invited to the group call
messageActionSetMessagesTTLYou changed the Time-To-Live of your messages in this chat.
messageActionGroupCallScheduledA group call was scheduled
messageActionSetChatThemeThe chat theme was changed
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/MessageEntity.html b/data/core.telegram.org/type/MessageEntity.html deleted file mode 100644 index f4f6d12e2d..0000000000 --- a/data/core.telegram.org/type/MessageEntity.html +++ /dev/null @@ -1,233 +0,0 @@ - - - - - MessageEntity - - - - - - - - - - - - - -
- -
-
-
- -

MessageEntity

- -

Message entities, representing styled text in a message

-

- -
-
messageEntityUnknown#bb92ba95 offset:int length:int = MessageEntity;
-messageEntityMention#fa04579d offset:int length:int = MessageEntity;
-messageEntityHashtag#6f635b0d offset:int length:int = MessageEntity;
-messageEntityBotCommand#6cef8ac7 offset:int length:int = MessageEntity;
-messageEntityUrl#6ed02538 offset:int length:int = MessageEntity;
-messageEntityEmail#64e475c2 offset:int length:int = MessageEntity;
-messageEntityBold#bd610bc9 offset:int length:int = MessageEntity;
-messageEntityItalic#826f8b60 offset:int length:int = MessageEntity;
-messageEntityCode#28a20571 offset:int length:int = MessageEntity;
-messageEntityPre#73924be0 offset:int length:int language:string = MessageEntity;
-messageEntityTextUrl#76a6d327 offset:int length:int url:string = MessageEntity;
-messageEntityMentionName#dc7b1140 offset:int length:int user_id:long = MessageEntity;
-inputMessageEntityMentionName#208e68c9 offset:int length:int user_id:InputUser = MessageEntity;
-messageEntityPhone#9b69e34b offset:int length:int = MessageEntity;
-messageEntityCashtag#4c4e743f offset:int length:int = MessageEntity;
-messageEntityUnderline#9c4e7e8b offset:int length:int = MessageEntity;
-messageEntityStrike#bf0693d4 offset:int length:int = MessageEntity;
-messageEntityBlockquote#20df5d0 offset:int length:int = MessageEntity;
-messageEntityBankCard#761e6af4 offset:int length:int = MessageEntity;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
messageEntityUnknownUnknown message entity
messageEntityMentionMessage entity mentioning the current user
messageEntityHashtag#hashtag message entity
messageEntityBotCommandMessage entity representing a bot /command
messageEntityUrlMessage entity representing an in-text url: https://google.com; for text urls, use messageEntityTextUrl.
messageEntityEmailMessage entity representing an email@example.com.
messageEntityBoldMessage entity representing bold text.
messageEntityItalicMessage entity representing italic text.
messageEntityCodeMessage entity representing a codeblock.
messageEntityPreMessage entity representing a preformatted codeblock, allowing the user to specify a programming language for the codeblock.
messageEntityTextUrlMessage entity representing a text url: for in-text urls like https://google.com use messageEntityUrl.
messageEntityMentionNameMessage entity representing a user mention: for creating a mention use inputMessageEntityMentionName.
inputMessageEntityMentionNameMessage entity that can be used to create a user user mention: received mentions use the messageEntityMentionName constructor, instead.
messageEntityPhoneMessage entity representing a phone number.
messageEntityCashtagMessage entity representing a $cashtag.
messageEntityUnderlineMessage entity representing underlined text.
messageEntityStrikeMessage entity representing strikethrough text.
messageEntityBlockquoteMessage entity representing a block quote.
messageEntityBankCardIndicates a credit card number
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/MessageFwdHeader.html b/data/core.telegram.org/type/MessageFwdHeader.html deleted file mode 100644 index bbe619ecac..0000000000 --- a/data/core.telegram.org/type/MessageFwdHeader.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - MessageFwdHeader - - - - - - - - - - - - - -
- -
-
-
- -

MessageFwdHeader

- -

Info about a forwarded message

-

- -
-
messageFwdHeader#5f777dce flags:# imported:flags.7?true from_id:flags.0?Peer from_name:flags.5?string date:int channel_post:flags.2?int post_author:flags.3?string saved_from_peer:flags.4?Peer saved_from_msg_id:flags.4?int psa_type:flags.6?string = MessageFwdHeader;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messageFwdHeaderInfo about a forwarded message
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/MessageInteractionCounters.html b/data/core.telegram.org/type/MessageInteractionCounters.html deleted file mode 100644 index e5aa85ea07..0000000000 --- a/data/core.telegram.org/type/MessageInteractionCounters.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - MessageInteractionCounters - - - - - - - - - - - - - -
- -
-
-
- -

MessageInteractionCounters

- -

Message interaction counters

-

- -
-
messageInteractionCounters#ad4fc9bd msg_id:int views:int forwards:int = MessageInteractionCounters;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messageInteractionCountersMessage interaction counters
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/MessageMedia.html b/data/core.telegram.org/type/MessageMedia.html deleted file mode 100644 index d69390ddf4..0000000000 --- a/data/core.telegram.org/type/MessageMedia.html +++ /dev/null @@ -1,232 +0,0 @@ - - - - - MessageMedia - - - - - - - - - - - - - -
- -
-
-
- -

MessageMedia

- -

Media

-

- -
-
messageMediaEmpty#3ded6320 = MessageMedia;
-messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;
-messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;
-messageMediaContact#70322949 phone_number:string first_name:string last_name:string vcard:string user_id:long = MessageMedia;
-messageMediaUnsupported#9f84f49e = MessageMedia;
-messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;
-messageMediaWebPage#a32dd600 webpage:WebPage = MessageMedia;
-messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;
-messageMediaGame#fdb19008 game:Game = MessageMedia;
-messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
-messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;
-messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
-messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;
-
----functions---
-
-messages.getWebPagePreview#8b68b0cc flags:# message:string entities:flags.3?Vector<MessageEntity> = MessageMedia;
-messages.uploadMedia#519bc2b1 peer:InputPeer media:InputMedia = MessageMedia;
-messages.uploadImportedMedia#2a862092 peer:InputPeer import_id:long file_name:string media:InputMedia = MessageMedia;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
messageMediaEmptyEmpty constructor.
messageMediaPhotoAttached photo.
messageMediaGeoAttached map.
messageMediaContactAttached contact.
messageMediaUnsupportedCurrent version of the client does not support this media type.
messageMediaDocumentDocument (video, audio, voice, sticker, any media type except photo)
messageMediaWebPagePreview of webpage
messageMediaVenueVenue
messageMediaGameTelegram game
messageMediaInvoiceInvoice
messageMediaGeoLiveIndicates a live geolocation
messageMediaPollPoll
messageMediaDiceDice
-

Methods

- - - - - - - - - - - - - - - - - - - - - -
MethodDescription
messages.getWebPagePreviewGet preview of webpage
messages.uploadMediaUpload a file and associate it to a chat (without actually sending it to the chat)
messages.uploadImportedMediaUpload a media file associated with an imported chat.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/MessageRange.html b/data/core.telegram.org/type/MessageRange.html deleted file mode 100644 index dda8a5fc9e..0000000000 --- a/data/core.telegram.org/type/MessageRange.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - MessageRange - - - - - - - - - - - - - -
- -
-
-
- -

MessageRange

- -

Indicates a range of chat messages

-

- -
-
messageRange#ae30253 min_id:int max_id:int = MessageRange;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messageRangeIndicates a range of chat messages
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/MessageReactionsList.html b/data/core.telegram.org/type/MessageReactionsList.html deleted file mode 100644 index 364301100e..0000000000 --- a/data/core.telegram.org/type/MessageReactionsList.html +++ /dev/null @@ -1,128 +0,0 @@ - - - - - MessageReactionsList - - - - - - - - - - - - - -
- -
-
-
- -

MessageReactionsList

- -

List of message reactions

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/MessageReplies.html b/data/core.telegram.org/type/MessageReplies.html deleted file mode 100644 index 0d8b600a6e..0000000000 --- a/data/core.telegram.org/type/MessageReplies.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - MessageReplies - - - - - - - - - - - - - -
- -
-
-
- -

MessageReplies

- -

Info about post comments (for channels) or message replies (for groups)

-

- -
-
messageReplies#83d60fc2 flags:# comments:flags.0?true replies:int replies_pts:int recent_repliers:flags.1?Vector<Peer> channel_id:flags.0?long max_id:flags.2?int read_max_id:flags.3?int = MessageReplies;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messageRepliesInfo about the comment section of a channel post, or a simple message thread
-

Related pages

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/MessageReplyHeader.html b/data/core.telegram.org/type/MessageReplyHeader.html deleted file mode 100644 index a619eeefb6..0000000000 --- a/data/core.telegram.org/type/MessageReplyHeader.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - MessageReplyHeader - - - - - - - - - - - - - -
- -
-
-
- -

MessageReplyHeader

- -

Reply information

-

- -
-
messageReplyHeader#a6d57763 flags:# reply_to_msg_id:int reply_to_peer_id:flags.0?Peer reply_to_top_id:flags.1?int = MessageReplyHeader;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messageReplyHeaderMessage thread information
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/MessageUserVote.html b/data/core.telegram.org/type/MessageUserVote.html deleted file mode 100644 index 0b040a9e46..0000000000 --- a/data/core.telegram.org/type/MessageUserVote.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - MessageUserVote - - - - - - - - - - - - - -
- -
-
-
- -

MessageUserVote

- -

How a user voted in a poll

-

- -
-
messageUserVote#34d247b4 user_id:long option:bytes date:int = MessageUserVote;
-messageUserVoteInputOption#3ca5b0ec user_id:long date:int = MessageUserVote;
-messageUserVoteMultiple#8a65e557 user_id:long options:Vector<bytes> date:int = MessageUserVote;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
messageUserVoteUser ID
messageUserVoteInputOptionHow a user voted in a poll (reduced constructor, returned if an option was provided to messages.getPollVotes)
messageUserVoteMultipleHow a user voted in a multiple-choice poll
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/MessageViews.html b/data/core.telegram.org/type/MessageViews.html deleted file mode 100644 index 139d829d0d..0000000000 --- a/data/core.telegram.org/type/MessageViews.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - MessageViews - - - - - - - - - - - - - -
- -
-
-
- -

MessageViews

- -

View, forward counter + info about replies of a specific message

-

- -
-
messageViews#455b853d flags:# views:flags.0?int forwards:flags.1?int replies:flags.2?MessageReplies = MessageViews;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messageViewsView, forward counter + info about replies of a specific message
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/MessagesFilter.html b/data/core.telegram.org/type/MessagesFilter.html deleted file mode 100644 index 343aa14e3c..0000000000 --- a/data/core.telegram.org/type/MessagesFilter.html +++ /dev/null @@ -1,223 +0,0 @@ - - - - - MessagesFilter - - - - - - - - - - - - - -
- -
-
-
- -

MessagesFilter

- -

Object describes message filter.

-

- -
-
inputMessagesFilterEmpty#57e2f66c = MessagesFilter;
-inputMessagesFilterPhotos#9609a51c = MessagesFilter;
-inputMessagesFilterVideo#9fc00e65 = MessagesFilter;
-inputMessagesFilterPhotoVideo#56e9f0e4 = MessagesFilter;
-inputMessagesFilterDocument#9eddf188 = MessagesFilter;
-inputMessagesFilterUrl#7ef0dd87 = MessagesFilter;
-inputMessagesFilterGif#ffc86587 = MessagesFilter;
-inputMessagesFilterVoice#50f5c392 = MessagesFilter;
-inputMessagesFilterMusic#3751b49e = MessagesFilter;
-inputMessagesFilterChatPhotos#3a20ecb8 = MessagesFilter;
-inputMessagesFilterPhoneCalls#80c99768 flags:# missed:flags.0?true = MessagesFilter;
-inputMessagesFilterRoundVoice#7a7c17a4 = MessagesFilter;
-inputMessagesFilterRoundVideo#b549da53 = MessagesFilter;
-inputMessagesFilterMyMentions#c1f8e69a = MessagesFilter;
-inputMessagesFilterGeo#e7026d0d = MessagesFilter;
-inputMessagesFilterContacts#e062db83 = MessagesFilter;
-inputMessagesFilterPinned#1bb00451 = MessagesFilter;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputMessagesFilterEmptyFilter is absent.
inputMessagesFilterPhotosFilter for messages containing photos.
inputMessagesFilterVideoFilter for messages containing videos.
inputMessagesFilterPhotoVideoFilter for messages containing photos or videos.
inputMessagesFilterDocumentFilter for messages containing documents.
inputMessagesFilterUrlReturn only messages containing URLs
inputMessagesFilterGifReturn only messages containing gifs
inputMessagesFilterVoiceReturn only messages containing voice notes
inputMessagesFilterMusicReturn only messages containing audio files
inputMessagesFilterChatPhotosReturn only chat photo changes
inputMessagesFilterPhoneCallsReturn only phone calls
inputMessagesFilterRoundVoiceReturn only round videos and voice notes
inputMessagesFilterRoundVideoReturn only round videos
inputMessagesFilterMyMentionsReturn only messages where the current user was mentioned
inputMessagesFilterGeoReturn only messages containing geolocations
inputMessagesFilterContactsReturn only messages containing contacts
inputMessagesFilterPinnedFetch only pinned messages
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/NotifyPeer.html b/data/core.telegram.org/type/NotifyPeer.html deleted file mode 100644 index 5f9abf093e..0000000000 --- a/data/core.telegram.org/type/NotifyPeer.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - - NotifyPeer - - - - - - - - - - - - - -
- -
-
-
- -

NotifyPeer

- -

Object defines the set of users and/or groups that generate notifications.

-

- -
-
notifyPeer#9fd40bd8 peer:Peer = NotifyPeer;
-notifyUsers#b4c83b4c = NotifyPeer;
-notifyChats#c007cec3 = NotifyPeer;
-notifyBroadcasts#d612e8ef = NotifyPeer;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
notifyPeerNotifications generated by a certain user or group.
notifyUsersNotifications generated by all users.
notifyChatsNotifications generated by all groups.
notifyBroadcastsChannel notification settings
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Null.html b/data/core.telegram.org/type/Null.html deleted file mode 100644 index 1c82eb47c0..0000000000 --- a/data/core.telegram.org/type/Null.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - Null - - - - - - - - - - - - - -
- -
-
-
- -

Null

- -

Object corresponds to an arbitrary empty object.

-

- -
-
null#56730bcc = Null;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
nullCorresponds to an arbitrary empty object.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Page.html b/data/core.telegram.org/type/Page.html deleted file mode 100644 index 93e5d471a9..0000000000 --- a/data/core.telegram.org/type/Page.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - Page - - - - - - - - - - - - - -
- -
-
-
- -

Page

- -

Instant view page

-

- -
-
page#98657f0d flags:# part:flags.0?true rtl:flags.1?true v2:flags.2?true url:string blocks:Vector<PageBlock> photos:Vector<Photo> documents:Vector<Document> views:flags.3?int = Page;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
pageInstant view page
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PageBlock.html b/data/core.telegram.org/type/PageBlock.html deleted file mode 100644 index 7d5299437c..0000000000 --- a/data/core.telegram.org/type/PageBlock.html +++ /dev/null @@ -1,283 +0,0 @@ - - - - - PageBlock - - - - - - - - - - - - - -
- -
-
-
- -

PageBlock

- -

Represents an instant view page element

-

- -
-
pageBlockUnsupported#13567e8a = PageBlock;
-pageBlockTitle#70abc3fd text:RichText = PageBlock;
-pageBlockSubtitle#8ffa9a1f text:RichText = PageBlock;
-pageBlockAuthorDate#baafe5e0 author:RichText published_date:int = PageBlock;
-pageBlockHeader#bfd064ec text:RichText = PageBlock;
-pageBlockSubheader#f12bb6e1 text:RichText = PageBlock;
-pageBlockParagraph#467a0766 text:RichText = PageBlock;
-pageBlockPreformatted#c070d93e text:RichText language:string = PageBlock;
-pageBlockFooter#48870999 text:RichText = PageBlock;
-pageBlockDivider#db20b188 = PageBlock;
-pageBlockAnchor#ce0d37b0 name:string = PageBlock;
-pageBlockList#e4e88011 items:Vector<PageListItem> = PageBlock;
-pageBlockBlockquote#263d7c26 text:RichText caption:RichText = PageBlock;
-pageBlockPullquote#4f4456d3 text:RichText caption:RichText = PageBlock;
-pageBlockPhoto#1759c560 flags:# photo_id:long caption:PageCaption url:flags.0?string webpage_id:flags.0?long = PageBlock;
-pageBlockVideo#7c8fe7b6 flags:# autoplay:flags.0?true loop:flags.1?true video_id:long caption:PageCaption = PageBlock;
-pageBlockCover#39f23300 cover:PageBlock = PageBlock;
-pageBlockEmbed#a8718dc5 flags:# full_width:flags.0?true allow_scrolling:flags.3?true url:flags.1?string html:flags.2?string poster_photo_id:flags.4?long w:flags.5?int h:flags.5?int caption:PageCaption = PageBlock;
-pageBlockEmbedPost#f259a80b url:string webpage_id:long author_photo_id:long author:string date:int blocks:Vector<PageBlock> caption:PageCaption = PageBlock;
-pageBlockCollage#65a0fa4d items:Vector<PageBlock> caption:PageCaption = PageBlock;
-pageBlockSlideshow#31f9590 items:Vector<PageBlock> caption:PageCaption = PageBlock;
-pageBlockChannel#ef1751b5 channel:Chat = PageBlock;
-pageBlockAudio#804361ea audio_id:long caption:PageCaption = PageBlock;
-pageBlockKicker#1e148390 text:RichText = PageBlock;
-pageBlockTable#bf4dea82 flags:# bordered:flags.0?true striped:flags.1?true title:RichText rows:Vector<PageTableRow> = PageBlock;
-pageBlockOrderedList#9a8ae1e1 items:Vector<PageListOrderedItem> = PageBlock;
-pageBlockDetails#76768bed flags:# open:flags.0?true blocks:Vector<PageBlock> title:RichText = PageBlock;
-pageBlockRelatedArticles#16115a96 title:RichText articles:Vector<PageRelatedArticle> = PageBlock;
-pageBlockMap#a44f3ef6 geo:GeoPoint zoom:int w:int h:int caption:PageCaption = PageBlock;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
pageBlockUnsupportedUnsupported IV element
pageBlockTitleTitle
pageBlockSubtitleSubtitle
pageBlockAuthorDateAuthor and date of creation of article
pageBlockHeaderPage header
pageBlockSubheaderSubheader
pageBlockParagraphA paragraph
pageBlockPreformattedPreformatted (<pre> text)
pageBlockFooterPage footer
pageBlockDividerAn empty block separating a page
pageBlockAnchorLink to section within the page itself (like <a href="#target">anchor</a>)
pageBlockListUnordered list of IV blocks
pageBlockBlockquoteQuote (equivalent to the HTML <blockquote>)
pageBlockPullquotePullquote
pageBlockPhotoA photo
pageBlockVideoVideo
pageBlockCoverA page cover
pageBlockEmbedAn embedded webpage
pageBlockEmbedPostAn embedded post
pageBlockCollageCollage of media
pageBlockSlideshowSlideshow
pageBlockChannelReference to a telegram channel
pageBlockAudioAudio
pageBlockKickerKicker
pageBlockTableTable
pageBlockOrderedListOrdered list of IV blocks
pageBlockDetailsA collapsible details block
pageBlockRelatedArticlesRelated articles
pageBlockMapA map
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PageCaption.html b/data/core.telegram.org/type/PageCaption.html deleted file mode 100644 index a90dd9e022..0000000000 --- a/data/core.telegram.org/type/PageCaption.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PageCaption - - - - - - - - - - - - - -
- -
-
-
- -

PageCaption

- -

Page caption

-

- -
-
pageCaption#6f747657 text:RichText credit:RichText = PageCaption;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
pageCaptionPage caption
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PageListItem.html b/data/core.telegram.org/type/PageListItem.html deleted file mode 100644 index 72eaddf3ea..0000000000 --- a/data/core.telegram.org/type/PageListItem.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - PageListItem - - - - - - - - - - - - - -
- -
-
-
- -

PageListItem

- -

Item in block list

-

- -
-
pageListItemText#b92fb6cd text:RichText = PageListItem;
-pageListItemBlocks#25e073fc blocks:Vector<PageBlock> = PageListItem;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
pageListItemTextList item
pageListItemBlocksList item
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PageListOrderedItem.html b/data/core.telegram.org/type/PageListOrderedItem.html deleted file mode 100644 index 044a4e8232..0000000000 --- a/data/core.telegram.org/type/PageListOrderedItem.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - PageListOrderedItem - - - - - - - - - - - - - -
- -
-
-
- -

PageListOrderedItem

- -

Represents an instant view ordered list

-

- -
-
pageListOrderedItemText#5e068047 num:string text:RichText = PageListOrderedItem;
-pageListOrderedItemBlocks#98dd8936 num:string blocks:Vector<PageBlock> = PageListOrderedItem;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
pageListOrderedItemTextOrdered list of text items
pageListOrderedItemBlocksOrdered list of IV blocks
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PageRelatedArticle.html b/data/core.telegram.org/type/PageRelatedArticle.html deleted file mode 100644 index 08c198b179..0000000000 --- a/data/core.telegram.org/type/PageRelatedArticle.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PageRelatedArticle - - - - - - - - - - - - - -
- -
-
-
- -

PageRelatedArticle

- -

Related articles

-

- -
-
pageRelatedArticle#b390dc08 flags:# url:string webpage_id:long title:flags.0?string description:flags.1?string photo_id:flags.2?long author:flags.3?string published_date:flags.4?int = PageRelatedArticle;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
pageRelatedArticleRelated article
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PageTableCell.html b/data/core.telegram.org/type/PageTableCell.html deleted file mode 100644 index 0cd1136272..0000000000 --- a/data/core.telegram.org/type/PageTableCell.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PageTableCell - - - - - - - - - - - - - -
- -
-
-
- -

PageTableCell

- -

Represents a table in an instant view table

-

- -
-
pageTableCell#34566b6a flags:# header:flags.0?true align_center:flags.3?true align_right:flags.4?true valign_middle:flags.5?true valign_bottom:flags.6?true text:flags.7?RichText colspan:flags.1?int rowspan:flags.2?int = PageTableCell;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
pageTableCellTable cell
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PageTableRow.html b/data/core.telegram.org/type/PageTableRow.html deleted file mode 100644 index 4d1c09514a..0000000000 --- a/data/core.telegram.org/type/PageTableRow.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PageTableRow - - - - - - - - - - - - - -
- -
-
-
- -

PageTableRow

- -

Table row

-

- -
-
pageTableRow#e0c0c5e5 cells:Vector<PageTableCell> = PageTableRow;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
pageTableRowTable row
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PasswordKdfAlgo.html b/data/core.telegram.org/type/PasswordKdfAlgo.html deleted file mode 100644 index e22a7ea56b..0000000000 --- a/data/core.telegram.org/type/PasswordKdfAlgo.html +++ /dev/null @@ -1,151 +0,0 @@ - - - - - PasswordKdfAlgo - - - - - - - - - - - - - -
- -
-
-
- -

PasswordKdfAlgo

- -

Key derivation function to use when generating the password hash for SRP two-factor authorization

-

- -
-
passwordKdfAlgoUnknown#d45ab096 = PasswordKdfAlgo;
-passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow#3a912d4a salt1:bytes salt2:bytes g:int p:bytes = PasswordKdfAlgo;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
passwordKdfAlgoUnknownUnknown KDF (most likely, the client is outdated and does not support the specified KDF algorithm)
passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPowThis key derivation algorithm defines that SRP 2FA login must be used
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PaymentCharge.html b/data/core.telegram.org/type/PaymentCharge.html deleted file mode 100644 index 47bb3abbd6..0000000000 --- a/data/core.telegram.org/type/PaymentCharge.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PaymentCharge - - - - - - - - - - - - - -
- -
-
-
- -

PaymentCharge

- -

Charged payment

-

- -
-
paymentCharge#ea02c27e id:string provider_charge_id:string = PaymentCharge;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
paymentChargePayment identifier
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PaymentRequestedInfo.html b/data/core.telegram.org/type/PaymentRequestedInfo.html deleted file mode 100644 index 884f917385..0000000000 --- a/data/core.telegram.org/type/PaymentRequestedInfo.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PaymentRequestedInfo - - - - - - - - - - - - - -
- -
-
-
- -

PaymentRequestedInfo

- -

Requested payment info

-

- -
-
paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
paymentRequestedInfoOrder info provided by the user
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PaymentSavedCredentials.html b/data/core.telegram.org/type/PaymentSavedCredentials.html deleted file mode 100644 index 05f6211577..0000000000 --- a/data/core.telegram.org/type/PaymentSavedCredentials.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PaymentSavedCredentials - - - - - - - - - - - - - -
- -
-
-
- -

PaymentSavedCredentials

- -

Saved payment credentials

-

- -
-
paymentSavedCredentialsCard#cdc27a1f id:string title:string = PaymentSavedCredentials;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
paymentSavedCredentialsCardSaved credit card
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Peer.html b/data/core.telegram.org/type/Peer.html deleted file mode 100644 index 6ba68784c5..0000000000 --- a/data/core.telegram.org/type/Peer.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - Peer - - - - - - - - - - - - - -
- -
-
-
- -

Peer

- -

Chat partner or group.

-

- -
-
peerUser#59511722 user_id:long = Peer;
-peerChat#36c6019a chat_id:long = Peer;
-peerChannel#a2a5371e channel_id:long = Peer;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
peerUserChat partner
peerChatGroup.
peerChannelChannel/supergroup
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PeerBlocked.html b/data/core.telegram.org/type/PeerBlocked.html deleted file mode 100644 index 0bab94d05c..0000000000 --- a/data/core.telegram.org/type/PeerBlocked.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PeerBlocked - - - - - - - - - - - - - -
- -
-
-
- -

PeerBlocked

- -

Info about a blocked user

-

- -
-
peerBlocked#e8fd8014 peer_id:Peer date:int = PeerBlocked;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
peerBlockedInformation about a blocked peer
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PeerLocated.html b/data/core.telegram.org/type/PeerLocated.html deleted file mode 100644 index 09e62c12a8..0000000000 --- a/data/core.telegram.org/type/PeerLocated.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - PeerLocated - - - - - - - - - - - - - -
- -
-
-
- -

PeerLocated

- -

Geolocated peer

-

- -
-
peerLocated#ca461b5d peer:Peer expires:int distance:int = PeerLocated;
-peerSelfLocated#f8ec284b expires:int = PeerLocated;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
peerLocatedPeer geolocated nearby
peerSelfLocatedCurrent peer
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PeerNotifySettings.html b/data/core.telegram.org/type/PeerNotifySettings.html deleted file mode 100644 index c49c82e618..0000000000 --- a/data/core.telegram.org/type/PeerNotifySettings.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - PeerNotifySettings - - - - - - - - - - - - - -
- -
-
-
- -

PeerNotifySettings

- -

Notification settings.

-

- -
-
peerNotifySettings#af509d20 flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = PeerNotifySettings;
-
----functions---
-
-account.getNotifySettings#12b3ad31 peer:InputNotifyPeer = PeerNotifySettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
peerNotifySettingsNotification settings.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getNotifySettingsGets current notification settings for a given user/group, from all users/all groups.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PeerSettings.html b/data/core.telegram.org/type/PeerSettings.html deleted file mode 100644 index a50bfde48e..0000000000 --- a/data/core.telegram.org/type/PeerSettings.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - PeerSettings - - - - - - - - - - - - - -
- -
-
-
- -

PeerSettings

- -

Peer settings

-

- -
-
peerSettings#733f2961 flags:# report_spam:flags.0?true add_contact:flags.1?true block_contact:flags.2?true share_contact:flags.3?true need_contacts_exception:flags.4?true report_geo:flags.5?true autoarchived:flags.7?true invite_members:flags.8?true geo_distance:flags.6?int = PeerSettings;
-
----functions---
-
-messages.getPeerSettings#3672e09c peer:InputPeer = PeerSettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
peerSettingsPeer settings
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getPeerSettingsGet peer settings
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PhoneCall.html b/data/core.telegram.org/type/PhoneCall.html deleted file mode 100644 index 52b4674580..0000000000 --- a/data/core.telegram.org/type/PhoneCall.html +++ /dev/null @@ -1,168 +0,0 @@ - - - - - PhoneCall - - - - - - - - - - - - - -
- -
-
-
- -

PhoneCall

- -

Phone call

-

- -
-
phoneCallEmpty#5366c915 id:long = PhoneCall;
-phoneCallWaiting#c5226f17 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long protocol:PhoneCallProtocol receive_date:flags.0?int = PhoneCall;
-phoneCallRequested#14b0ed0c flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_hash:bytes protocol:PhoneCallProtocol = PhoneCall;
-phoneCallAccepted#3660c311 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_b:bytes protocol:PhoneCallProtocol = PhoneCall;
-phoneCall#967f7c67 flags:# p2p_allowed:flags.5?true video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long protocol:PhoneCallProtocol connections:Vector<PhoneConnection> start_date:int = PhoneCall;
-phoneCallDiscarded#50ca4de1 flags:# need_rating:flags.2?true need_debug:flags.3?true video:flags.6?true id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = PhoneCall;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
phoneCallEmptyEmpty constructor
phoneCallWaitingIncoming phone call
phoneCallRequestedRequested phone call
phoneCallAcceptedAn accepted phone call
phoneCallPhone call
phoneCallDiscardedIndicates a discarded phone call
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PhoneCallDiscardReason.html b/data/core.telegram.org/type/PhoneCallDiscardReason.html deleted file mode 100644 index bdb3fea497..0000000000 --- a/data/core.telegram.org/type/PhoneCallDiscardReason.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - - PhoneCallDiscardReason - - - - - - - - - - - - - -
- -
-
-
- -

PhoneCallDiscardReason

- -

Why was the phone call discarded?

-

- -
-
phoneCallDiscardReasonMissed#85e42301 = PhoneCallDiscardReason;
-phoneCallDiscardReasonDisconnect#e095c1a0 = PhoneCallDiscardReason;
-phoneCallDiscardReasonHangup#57adc690 = PhoneCallDiscardReason;
-phoneCallDiscardReasonBusy#faf7e8c9 = PhoneCallDiscardReason;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
phoneCallDiscardReasonMissedThe phone call was missed
phoneCallDiscardReasonDisconnectThe phone call was disconnected
phoneCallDiscardReasonHangupThe phone call was ended normally
phoneCallDiscardReasonBusyThe phone call was discared because the user is busy in another call
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PhoneCallProtocol.html b/data/core.telegram.org/type/PhoneCallProtocol.html deleted file mode 100644 index 1930d6420d..0000000000 --- a/data/core.telegram.org/type/PhoneCallProtocol.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PhoneCallProtocol - - - - - - - - - - - - - -
- -
-
-
- -

PhoneCallProtocol

- -

Phone call protocol

-

- -
-
phoneCallProtocol#fc878fc8 flags:# udp_p2p:flags.0?true udp_reflector:flags.1?true min_layer:int max_layer:int library_versions:Vector<string> = PhoneCallProtocol;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
phoneCallProtocolProtocol info for libtgvoip
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Photo.html b/data/core.telegram.org/type/Photo.html deleted file mode 100644 index f81614edab..0000000000 --- a/data/core.telegram.org/type/Photo.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - Photo - - - - - - - - - - - - - -
- -
-
-
- -

Photo

- -

Object describes a photo.

-

- -
-
photoEmpty#2331b22d id:long = Photo;
-photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
photoEmptyEmpty constructor, non-existent photo
photoPhoto
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PhotoSize.html b/data/core.telegram.org/type/PhotoSize.html deleted file mode 100644 index a45b1c3618..0000000000 --- a/data/core.telegram.org/type/PhotoSize.html +++ /dev/null @@ -1,168 +0,0 @@ - - - - - PhotoSize - - - - - - - - - - - - - -
- -
-
-
- -

PhotoSize

- -

Location of a certain size of a picture

-

- -
-
photoSizeEmpty#e17e23c type:string = PhotoSize;
-photoSize#75c78e60 type:string w:int h:int size:int = PhotoSize;
-photoCachedSize#21e1ad6 type:string w:int h:int bytes:bytes = PhotoSize;
-photoStrippedSize#e0b0bc2e type:string bytes:bytes = PhotoSize;
-photoSizeProgressive#fa3efb95 type:string w:int h:int sizes:Vector<int> = PhotoSize;
-photoPathSize#d8214d41 type:string bytes:bytes = PhotoSize;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
photoSizeEmptyEmpty constructor. Image with this thumbnail is unavailable.
photoSizeImage description.
photoCachedSizeDescription of an image and its content.
photoStrippedSizeJust the image's content
photoSizeProgressiveProgressively encoded photosize
photoPathSizeMessages with animated stickers can have a compressed svg (< 300 bytes) to show the outline of the sticker before fetching the actual lottie animation.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Poll.html b/data/core.telegram.org/type/Poll.html deleted file mode 100644 index 567314114c..0000000000 --- a/data/core.telegram.org/type/Poll.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - Poll - - - - - - - - - - - - - -
- -
-
-
- -

Poll

- -

Indicates a poll message

-

- -
-
poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
pollPoll
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PollAnswer.html b/data/core.telegram.org/type/PollAnswer.html deleted file mode 100644 index 6715b84997..0000000000 --- a/data/core.telegram.org/type/PollAnswer.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - PollAnswer - - - - - - - - - - - - - -
- -
-
-
- -

PollAnswer

- -

Indicates a possible answer to a poll.

-

- -
-
pollAnswer#6ca9c2e9 text:string option:bytes = PollAnswer;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
pollAnswerA possible answer of a poll
-

Related pages

-

Poll

-

Indicates a poll message

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PollAnswerVoters.html b/data/core.telegram.org/type/PollAnswerVoters.html deleted file mode 100644 index d5f760790c..0000000000 --- a/data/core.telegram.org/type/PollAnswerVoters.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PollAnswerVoters - - - - - - - - - - - - - -
- -
-
-
- -

PollAnswerVoters

- -

How users voted on a certain poll answer

-

- -
-
pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
pollAnswerVotersA poll answer, and how users voted on it
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PollResults.html b/data/core.telegram.org/type/PollResults.html deleted file mode 100644 index 8894dd373c..0000000000 --- a/data/core.telegram.org/type/PollResults.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PollResults - - - - - - - - - - - - - -
- -
-
-
- -

PollResults

- -

Results of poll

-

- -
-
pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
pollResultsResults of poll
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PopularContact.html b/data/core.telegram.org/type/PopularContact.html deleted file mode 100644 index 162e4f02cc..0000000000 --- a/data/core.telegram.org/type/PopularContact.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PopularContact - - - - - - - - - - - - - -
- -
-
-
- -

PopularContact

- -

Popular contact

-

- -
-
popularContact#5ce14175 client_id:long importers:int = PopularContact;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
popularContactPopular contact
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PostAddress.html b/data/core.telegram.org/type/PostAddress.html deleted file mode 100644 index 6df885b58a..0000000000 --- a/data/core.telegram.org/type/PostAddress.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PostAddress - - - - - - - - - - - - - -
- -
-
-
- -

PostAddress

- -

Shipping address

-

- -
-
postAddress#1e8caaeb street_line1:string street_line2:string city:string state:string country_iso2:string post_code:string = PostAddress;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
postAddressShipping address
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PrivacyKey.html b/data/core.telegram.org/type/PrivacyKey.html deleted file mode 100644 index 806a9d1d7d..0000000000 --- a/data/core.telegram.org/type/PrivacyKey.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - PrivacyKey - - - - - - - - - - - - - -
- -
-
-
- -

PrivacyKey

- -

Privacy key

-

- -
-
privacyKeyStatusTimestamp#bc2eab30 = PrivacyKey;
-privacyKeyChatInvite#500e6dfa = PrivacyKey;
-privacyKeyPhoneCall#3d662b7b = PrivacyKey;
-privacyKeyPhoneP2P#39491cc8 = PrivacyKey;
-privacyKeyForwards#69ec56a3 = PrivacyKey;
-privacyKeyProfilePhoto#96151fed = PrivacyKey;
-privacyKeyPhoneNumber#d19ae46d = PrivacyKey;
-privacyKeyAddedByPhone#42ffd42b = PrivacyKey;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
privacyKeyStatusTimestampWhether we can see the last online timestamp
privacyKeyChatInviteWhether the user can be invited to chats
privacyKeyPhoneCallWhether the user accepts phone calls
privacyKeyPhoneP2PWhether P2P connections in phone calls are allowed
privacyKeyForwardsWhether messages forwarded from the user will be anonymously forwarded
privacyKeyProfilePhotoWhether the profile picture of the user is visible
privacyKeyPhoneNumberWhether the user allows us to see his phone number
privacyKeyAddedByPhoneWhether people can add you to their contact list by your phone number
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/PrivacyRule.html b/data/core.telegram.org/type/PrivacyRule.html deleted file mode 100644 index e38fee3c82..0000000000 --- a/data/core.telegram.org/type/PrivacyRule.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - PrivacyRule - - - - - - - - - - - - - -
- -
-
-
- -

PrivacyRule

- -

Privacy rule

-

- -
-
privacyValueAllowContacts#fffe1bac = PrivacyRule;
-privacyValueAllowAll#65427b82 = PrivacyRule;
-privacyValueAllowUsers#b8905fb2 users:Vector<long> = PrivacyRule;
-privacyValueDisallowContacts#f888fa1a = PrivacyRule;
-privacyValueDisallowAll#8b73e763 = PrivacyRule;
-privacyValueDisallowUsers#e4621141 users:Vector<long> = PrivacyRule;
-privacyValueAllowChatParticipants#6b134e8e chats:Vector<long> = PrivacyRule;
-privacyValueDisallowChatParticipants#41c87565 chats:Vector<long> = PrivacyRule;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
privacyValueAllowContactsAllow all contacts
privacyValueAllowAllAllow all users
privacyValueAllowUsersAllow only certain users
privacyValueDisallowContactsDisallow only contacts
privacyValueDisallowAllDisallow all users
privacyValueDisallowUsersDisallow only certain users
privacyValueAllowChatParticipantsAllow all participants of certain chats
privacyValueDisallowChatParticipantsDisallow only participants of certain chats
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ReceivedNotifyMessage.html b/data/core.telegram.org/type/ReceivedNotifyMessage.html deleted file mode 100644 index d281fb997e..0000000000 --- a/data/core.telegram.org/type/ReceivedNotifyMessage.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - ReceivedNotifyMessage - - - - - - - - - - - - - -
- -
-
-
- -

ReceivedNotifyMessage

- -

Confirmation of message receipt

-

- -
-
receivedNotifyMessage#a384b779 id:int flags:int = ReceivedNotifyMessage;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
receivedNotifyMessageMessage ID, for which PUSH-notifications were cancelled.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ReplyMarkup.html b/data/core.telegram.org/type/ReplyMarkup.html deleted file mode 100644 index b15813b492..0000000000 --- a/data/core.telegram.org/type/ReplyMarkup.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - - ReplyMarkup - - - - - - - - - - - - - -
- -
-
-
- -

ReplyMarkup

- -

Reply markup for bot and inline keyboards

-

- -
-
replyKeyboardHide#a03e5b85 flags:# selective:flags.2?true = ReplyMarkup;
-replyKeyboardForceReply#86b40b08 flags:# single_use:flags.1?true selective:flags.2?true placeholder:flags.3?string = ReplyMarkup;
-replyKeyboardMarkup#85dd99d1 flags:# resize:flags.0?true single_use:flags.1?true selective:flags.2?true rows:Vector<KeyboardButtonRow> placeholder:flags.3?string = ReplyMarkup;
-replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
replyKeyboardHideHide sent bot keyboard
replyKeyboardForceReplyForce the user to send a reply
replyKeyboardMarkupBot keyboard
replyInlineMarkupBot or inline keyboard
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ReportReason.html b/data/core.telegram.org/type/ReportReason.html deleted file mode 100644 index 69953d3340..0000000000 --- a/data/core.telegram.org/type/ReportReason.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - ReportReason - - - - - - - - - - - - - -
- -
-
-
- -

ReportReason

- -

Report reason

-

- -
-
inputReportReasonSpam#58dbcab8 = ReportReason;
-inputReportReasonViolence#1e22c78d = ReportReason;
-inputReportReasonPornography#2e59d922 = ReportReason;
-inputReportReasonChildAbuse#adf44ee3 = ReportReason;
-inputReportReasonOther#c1e4a2b1 = ReportReason;
-inputReportReasonCopyright#9b89f93a = ReportReason;
-inputReportReasonGeoIrrelevant#dbd4feed = ReportReason;
-inputReportReasonFake#f5ddd6e7 = ReportReason;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputReportReasonSpamReport for spam
inputReportReasonViolenceReport for violence
inputReportReasonPornographyReport for pornography
inputReportReasonChildAbuseReport for child abuse
inputReportReasonOtherOther
inputReportReasonCopyrightReport for copyrighted content
inputReportReasonGeoIrrelevantReport an irrelevant geogroup
inputReportReasonFakeReport for impersonation
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/RestrictionReason.html b/data/core.telegram.org/type/RestrictionReason.html deleted file mode 100644 index 6abc2362be..0000000000 --- a/data/core.telegram.org/type/RestrictionReason.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - RestrictionReason - - - - - - - - - - - - - -
- -
-
-
- -

RestrictionReason

- -

Restriction reason

-

- -
-
restrictionReason#d072acb4 platform:string reason:string text:string = RestrictionReason;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
restrictionReasonRestriction reason
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/RichText.html b/data/core.telegram.org/type/RichText.html deleted file mode 100644 index 51d5fc0813..0000000000 --- a/data/core.telegram.org/type/RichText.html +++ /dev/null @@ -1,218 +0,0 @@ - - - - - RichText - - - - - - - - - - - - - -
- -
-
-
- -

RichText

- -

Rich text

-

- -
-
textEmpty#dc3d824f = RichText;
-textPlain#744694e0 text:string = RichText;
-textBold#6724abc4 text:RichText = RichText;
-textItalic#d912a59c text:RichText = RichText;
-textUnderline#c12622c4 text:RichText = RichText;
-textStrike#9bf8bb95 text:RichText = RichText;
-textFixed#6c3f19b9 text:RichText = RichText;
-textUrl#3c2884c1 text:RichText url:string webpage_id:long = RichText;
-textEmail#de5a0dd6 text:RichText email:string = RichText;
-textConcat#7e6260d7 texts:Vector<RichText> = RichText;
-textSubscript#ed6a8504 text:RichText = RichText;
-textSuperscript#c7fb5e01 text:RichText = RichText;
-textMarked#34b8621 text:RichText = RichText;
-textPhone#1ccb966a text:RichText phone:string = RichText;
-textImage#81ccf4f document_id:long w:int h:int = RichText;
-textAnchor#35553762 text:RichText name:string = RichText;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
textEmptyEmpty rich text element
textPlainPlain text
textBoldBold text
textItalicItalic text
textUnderlineUnderlined text
textStrikeStrikethrough text
textFixedfixed-width rich text
textUrlLink
textEmailRich text email link
textConcatConcatenation of rich texts
textSubscriptSubscript text
textSuperscriptSuperscript text
textMarkedHighlighted text
textPhoneRich text linked to a phone number
textImageInline image
textAnchorText linking to another section of the page
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/SavedContact.html b/data/core.telegram.org/type/SavedContact.html deleted file mode 100644 index ddbd71d748..0000000000 --- a/data/core.telegram.org/type/SavedContact.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - SavedContact - - - - - - - - - - - - - -
- -
-
-
- -

SavedContact

- -

Saved contact

-

- -
-
savedPhoneContact#1142bd56 phone:string first_name:string last_name:string date:int = SavedContact;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
savedPhoneContactSaved contact
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/SecureCredentialsEncrypted.html b/data/core.telegram.org/type/SecureCredentialsEncrypted.html deleted file mode 100644 index 83969a99fc..0000000000 --- a/data/core.telegram.org/type/SecureCredentialsEncrypted.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - SecureCredentialsEncrypted - - - - - - - - - - - - - -
- -
-
-
- -

SecureCredentialsEncrypted

- -

Encrypted secure credentials

-

- -
-
secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
secureCredentialsEncryptedEncrypted credentials required to decrypt telegram passport data.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/SecureData.html b/data/core.telegram.org/type/SecureData.html deleted file mode 100644 index d5b3aa24db..0000000000 --- a/data/core.telegram.org/type/SecureData.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - SecureData - - - - - - - - - - - - - -
- -
-
-
- -

SecureData

- -

Secure passport data, for more info see the passport docs »

-

- -
-
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
secureDataSecure data
-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/SecureFile.html b/data/core.telegram.org/type/SecureFile.html deleted file mode 100644 index bd82e09aee..0000000000 --- a/data/core.telegram.org/type/SecureFile.html +++ /dev/null @@ -1,151 +0,0 @@ - - - - - SecureFile - - - - - - - - - - - - - -
- -
-
-
- -

SecureFile

- -

Secure passport file, for more info see the passport docs »

-

- -
-
secureFileEmpty#64199744 = SecureFile;
-secureFile#e0277a62 id:long access_hash:long size:int dc_id:int date:int file_hash:bytes secret:bytes = SecureFile;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
secureFileEmptyEmpty constructor
secureFileSecure file
-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/SecurePasswordKdfAlgo.html b/data/core.telegram.org/type/SecurePasswordKdfAlgo.html deleted file mode 100644 index cde415715a..0000000000 --- a/data/core.telegram.org/type/SecurePasswordKdfAlgo.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - SecurePasswordKdfAlgo - - - - - - - - - - - - - -
- -
-
-
- -

SecurePasswordKdfAlgo

- -

KDF algorithm to use for computing telegram passport hash

-

- -
-
securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;
-securePasswordKdfAlgoPBKDF2HMACSHA512iter100000#bbf2dda0 salt:bytes = SecurePasswordKdfAlgo;
-securePasswordKdfAlgoSHA512#86471d92 salt:bytes = SecurePasswordKdfAlgo;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
securePasswordKdfAlgoUnknownUnknown KDF algo (most likely the client has to be updated)
securePasswordKdfAlgoPBKDF2HMACSHA512iter100000PBKDF2 with SHA512 and 100000 iterations KDF algo
securePasswordKdfAlgoSHA512SHA512 KDF algo
-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/SecurePlainData.html b/data/core.telegram.org/type/SecurePlainData.html deleted file mode 100644 index 5f46a9cddf..0000000000 --- a/data/core.telegram.org/type/SecurePlainData.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - SecurePlainData - - - - - - - - - - - - - -
- -
-
-
- -

SecurePlainData

- -

Plaintext verified passport data.

-

- -
-
securePlainPhone#7d6099dd phone:string = SecurePlainData;
-securePlainEmail#21ec5a5f email:string = SecurePlainData;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
securePlainPhonePhone number to use in telegram passport: it must be verified, first ».
securePlainEmailEmail address to use in telegram passport: it must be verified, first ».
-

Related pages

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/SecureRequiredType.html b/data/core.telegram.org/type/SecureRequiredType.html deleted file mode 100644 index 3bec48883d..0000000000 --- a/data/core.telegram.org/type/SecureRequiredType.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - SecureRequiredType - - - - - - - - - - - - - -
- -
-
-
- -

SecureRequiredType

- -

Required secure file type

-

- -
-
secureRequiredType#829d99da flags:# native_names:flags.0?true selfie_required:flags.1?true translation_required:flags.2?true type:SecureValueType = SecureRequiredType;
-secureRequiredTypeOneOf#27477b4 types:Vector<SecureRequiredType> = SecureRequiredType;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
secureRequiredTypeRequired type
secureRequiredTypeOneOfOne of
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/SecureSecretSettings.html b/data/core.telegram.org/type/SecureSecretSettings.html deleted file mode 100644 index f6a2af64f6..0000000000 --- a/data/core.telegram.org/type/SecureSecretSettings.html +++ /dev/null @@ -1,145 +0,0 @@ - - - - - SecureSecretSettings - - - - - - - - - - - - - -
- -
-
-
- -

SecureSecretSettings

- -

Telegram passport settings

-

- -
-
secureSecretSettings#1527bcac secure_algo:SecurePasswordKdfAlgo secure_secret:bytes secure_secret_id:long = SecureSecretSettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
secureSecretSettingsSecure settings
-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/SecureValue.html b/data/core.telegram.org/type/SecureValue.html deleted file mode 100644 index ae0341370c..0000000000 --- a/data/core.telegram.org/type/SecureValue.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - SecureValue - - - - - - - - - - - - - -
- -
-
-
- -

SecureValue

- -

Secure tgpassport value

-

- -
-
secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;
-
----functions---
-
-account.saveSecureValue#899fe31d value:InputSecureValue secure_secret_id:long = SecureValue;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
secureValueSecure value
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.saveSecureValueSave secure passport value
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/SecureValueError.html b/data/core.telegram.org/type/SecureValueError.html deleted file mode 100644 index 57d53fa14e..0000000000 --- a/data/core.telegram.org/type/SecureValueError.html +++ /dev/null @@ -1,183 +0,0 @@ - - - - - SecureValueError - - - - - - - - - - - - - -
- -
-
-
- -

SecureValueError

- -

Secure value error

-

- -
-
secureValueErrorData#e8a40bd9 type:SecureValueType data_hash:bytes field:string text:string = SecureValueError;
-secureValueErrorFrontSide#be3dfa type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorReverseSide#868a2aa5 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorSelfie#e537ced6 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorFile#7a700873 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorFiles#666220e9 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
-secureValueError#869d758f type:SecureValueType hash:bytes text:string = SecureValueError;
-secureValueErrorTranslationFile#a1144770 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorTranslationFiles#34636dd8 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
secureValueErrorDataSecure value error
secureValueErrorFrontSideSecure value error front side
secureValueErrorReverseSideReverse side error
secureValueErrorSelfieSecure value error: invalid selfie
secureValueErrorFileSecure value error file
secureValueErrorFilesSecure value error files
secureValueErrorSecure value error
secureValueErrorTranslationFileTranslation missing
secureValueErrorTranslationFilesTranslation file error
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/SecureValueHash.html b/data/core.telegram.org/type/SecureValueHash.html deleted file mode 100644 index 335491da51..0000000000 --- a/data/core.telegram.org/type/SecureValueHash.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - SecureValueHash - - - - - - - - - - - - - -
- -
-
-
- -

SecureValueHash

- -

Secure value hash

-

- -
-
secureValueHash#ed1ecdb0 type:SecureValueType hash:bytes = SecureValueHash;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
secureValueHashSecure value hash
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/SecureValueType.html b/data/core.telegram.org/type/SecureValueType.html deleted file mode 100644 index f6b8803cab..0000000000 --- a/data/core.telegram.org/type/SecureValueType.html +++ /dev/null @@ -1,203 +0,0 @@ - - - - - SecureValueType - - - - - - - - - - - - - -
- -
-
-
- -

SecureValueType

- -

Secure value type

-

- -
-
secureValueTypePersonalDetails#9d2a81e3 = SecureValueType;
-secureValueTypePassport#3dac6a00 = SecureValueType;
-secureValueTypeDriverLicense#6e425c4 = SecureValueType;
-secureValueTypeIdentityCard#a0d0744b = SecureValueType;
-secureValueTypeInternalPassport#99a48f23 = SecureValueType;
-secureValueTypeAddress#cbe31e26 = SecureValueType;
-secureValueTypeUtilityBill#fc36954e = SecureValueType;
-secureValueTypeBankStatement#89137c0d = SecureValueType;
-secureValueTypeRentalAgreement#8b883488 = SecureValueType;
-secureValueTypePassportRegistration#99e3806a = SecureValueType;
-secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;
-secureValueTypePhone#b320aadb = SecureValueType;
-secureValueTypeEmail#8e3ca7ee = SecureValueType;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
secureValueTypePersonalDetailsPersonal details
secureValueTypePassportPassport
secureValueTypeDriverLicenseDriver's license
secureValueTypeIdentityCardIdentity card
secureValueTypeInternalPassportInternal passport
secureValueTypeAddressAddress
secureValueTypeUtilityBillUtility bill
secureValueTypeBankStatementBank statement
secureValueTypeRentalAgreementRental agreement
secureValueTypePassportRegistrationInternal registration passport
secureValueTypeTemporaryRegistrationTemporary registration
secureValueTypePhonePhone
secureValueTypeEmailEmail
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/SendMessageAction.html b/data/core.telegram.org/type/SendMessageAction.html deleted file mode 100644 index 9fae21a4fe..0000000000 --- a/data/core.telegram.org/type/SendMessageAction.html +++ /dev/null @@ -1,228 +0,0 @@ - - - - - SendMessageAction - - - - - - - - - - - - - -
- -
-
-
- -

SendMessageAction

- -

User actions. Use this to provide users with detailed info about their chat partners' actions: typing or sending attachments of all kinds.

-

- -
-
sendMessageTypingAction#16bf744e = SendMessageAction;
-sendMessageCancelAction#fd5ec8f5 = SendMessageAction;
-sendMessageRecordVideoAction#a187d66f = SendMessageAction;
-sendMessageUploadVideoAction#e9763aec progress:int = SendMessageAction;
-sendMessageRecordAudioAction#d52f73f7 = SendMessageAction;
-sendMessageUploadAudioAction#f351d7ab progress:int = SendMessageAction;
-sendMessageUploadPhotoAction#d1d34a26 progress:int = SendMessageAction;
-sendMessageUploadDocumentAction#aa0cd9e4 progress:int = SendMessageAction;
-sendMessageGeoLocationAction#176f8ba1 = SendMessageAction;
-sendMessageChooseContactAction#628cbc6f = SendMessageAction;
-sendMessageGamePlayAction#dd6a8f48 = SendMessageAction;
-sendMessageRecordRoundAction#88f27fbc = SendMessageAction;
-sendMessageUploadRoundAction#243e1c66 progress:int = SendMessageAction;
-speakingInGroupCallAction#d92c2285 = SendMessageAction;
-sendMessageHistoryImportAction#dbda9246 progress:int = SendMessageAction;
-sendMessageChooseStickerAction#b05ac6b1 = SendMessageAction;
-sendMessageEmojiInteraction#25972bcb emoticon:string msg_id:int interaction:DataJSON = SendMessageAction;
-sendMessageEmojiInteractionSeen#b665902e emoticon:string = SendMessageAction;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
sendMessageTypingActionUser is typing.
sendMessageCancelActionInvalidate all previous action updates. E.g. when user deletes entered text or aborts a video upload.
sendMessageRecordVideoActionUser is recording a video.
sendMessageUploadVideoActionUser is uploading a video.
sendMessageRecordAudioActionUser is recording a voice message.
sendMessageUploadAudioActionUser is uploading a voice message.
sendMessageUploadPhotoActionUser is uploading a photo.
sendMessageUploadDocumentActionUser is uploading a file.
sendMessageGeoLocationActionUser is selecting a location to share.
sendMessageChooseContactActionUser is selecting a contact to share.
sendMessageGamePlayActionUser is playing a game
sendMessageRecordRoundActionUser is recording a round video to share
sendMessageUploadRoundActionUser is uploading a round video
speakingInGroupCallActionUser is currently speaking in the group call
sendMessageHistoryImportActionChat history is being imported
sendMessageChooseStickerActionUser is choosing a sticker
sendMessageEmojiInteractionUser has clicked on an animated emoji, triggering a reaction
sendMessageEmojiInteractionSeenUser has seen the reaction generated by another user
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ShippingOption.html b/data/core.telegram.org/type/ShippingOption.html deleted file mode 100644 index bee95e197d..0000000000 --- a/data/core.telegram.org/type/ShippingOption.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - ShippingOption - - - - - - - - - - - - - -
- -
-
-
- -

ShippingOption

- -

Shipping options

-

- -
-
shippingOption#b6213cdf id:string title:string prices:Vector<LabeledPrice> = ShippingOption;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
shippingOptionShipping option
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/SponsoredMessage.html b/data/core.telegram.org/type/SponsoredMessage.html deleted file mode 100644 index 9902b43556..0000000000 --- a/data/core.telegram.org/type/SponsoredMessage.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - SponsoredMessage - - - - - - - - - - - - - -
- -
-
-
- -

SponsoredMessage

- -

A sponsored message

-

- -
-
sponsoredMessage#2a3c381f flags:# random_id:bytes from_id:Peer start_param:flags.0?string message:string entities:flags.1?Vector<MessageEntity> = SponsoredMessage;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
sponsoredMessageA sponsored message
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/StatsAbsValueAndPrev.html b/data/core.telegram.org/type/StatsAbsValueAndPrev.html deleted file mode 100644 index 5af90cf3ee..0000000000 --- a/data/core.telegram.org/type/StatsAbsValueAndPrev.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - StatsAbsValueAndPrev - - - - - - - - - - - - - -
- -
-
-
- -

StatsAbsValueAndPrev

- -

Channel statistics value pair

-

- -
-
statsAbsValueAndPrev#cb43acde current:double previous:double = StatsAbsValueAndPrev;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
statsAbsValueAndPrevStatistics value couple; initial and final value for period of time currently in consideration
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/StatsGraph.html b/data/core.telegram.org/type/StatsGraph.html deleted file mode 100644 index eb0b4cc0c3..0000000000 --- a/data/core.telegram.org/type/StatsGraph.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - StatsGraph - - - - - - - - - - - - - -
- -
-
-
- -

StatsGraph

- -

Channel statistics graph

-

- -
-
statsGraphAsync#4a27eb2d token:string = StatsGraph;
-statsGraphError#bedc9822 error:string = StatsGraph;
-statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
-
----functions---
-
-stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
statsGraphAsyncThis graph must be generated asynchronously using stats.loadAsyncGraph to reduce server load
statsGraphErrorAn error occurred while generating the statistics graph
statsGraphChannel statistics graph
-

Methods

- - - - - - - - - - - - - -
MethodDescription
stats.loadAsyncGraphLoad channel statistics graph asynchronously
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/StatsGroupTopAdmin.html b/data/core.telegram.org/type/StatsGroupTopAdmin.html deleted file mode 100644 index 27488200b1..0000000000 --- a/data/core.telegram.org/type/StatsGroupTopAdmin.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - StatsGroupTopAdmin - - - - - - - - - - - - - -
- -
-
-
- -

StatsGroupTopAdmin

- -

Most active admin in a supergroup

-

- -
-
statsGroupTopAdmin#d7584c87 user_id:long deleted:int kicked:int banned:int = StatsGroupTopAdmin;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
statsGroupTopAdminInformation about an active admin in a supergroup
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/StatsGroupTopInviter.html b/data/core.telegram.org/type/StatsGroupTopInviter.html deleted file mode 100644 index 1e6ca20091..0000000000 --- a/data/core.telegram.org/type/StatsGroupTopInviter.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - StatsGroupTopInviter - - - - - - - - - - - - - -
- -
-
-
- -

StatsGroupTopInviter

- -

Most active inviter in a supergroup

-

- -
-
statsGroupTopInviter#535f779d user_id:long invitations:int = StatsGroupTopInviter;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
statsGroupTopInviterInformation about an active supergroup inviter
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/StatsGroupTopPoster.html b/data/core.telegram.org/type/StatsGroupTopPoster.html deleted file mode 100644 index 8de718255f..0000000000 --- a/data/core.telegram.org/type/StatsGroupTopPoster.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - StatsGroupTopPoster - - - - - - - - - - - - - -
- -
-
-
- -

StatsGroupTopPoster

- -

Most active user in a supergroup

-

- -
-
statsGroupTopPoster#9d04af9b user_id:long messages:int avg_chars:int = StatsGroupTopPoster;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
statsGroupTopPosterInformation about an active user in a supergroup
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/StatsPercentValue.html b/data/core.telegram.org/type/StatsPercentValue.html deleted file mode 100644 index 6b926097ae..0000000000 --- a/data/core.telegram.org/type/StatsPercentValue.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - StatsPercentValue - - - - - - - - - - - - - -
- -
-
-
- -

StatsPercentValue

- -

Channel statistics percentage

-

- -
-
statsPercentValue#cbce2fe0 part:double total:double = StatsPercentValue;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
statsPercentValueChannel statistics percentage
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/StatsURL.html b/data/core.telegram.org/type/StatsURL.html deleted file mode 100644 index f81ad87e0c..0000000000 --- a/data/core.telegram.org/type/StatsURL.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - StatsURL - - - - - - - - - - - - - -
- -
-
-
- -

StatsURL

- -

URL with chat statistics

-

- -
-
statsURL#47a971e0 url:string = StatsURL;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
statsURLURL with chat statistics
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/StickerPack.html b/data/core.telegram.org/type/StickerPack.html deleted file mode 100644 index 98b7142eca..0000000000 --- a/data/core.telegram.org/type/StickerPack.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - StickerPack - - - - - - - - - - - - - -
- -
-
-
- -

StickerPack

- -

Stickerpack

-

- -
-
stickerPack#12b299d4 emoticon:string documents:Vector<long> = StickerPack;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
stickerPackA stickerpack is a group of stickers associated to the same emoji.
It is not a sticker pack the way it is usually intended, you may be looking for a StickerSet.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/StickerSet.html b/data/core.telegram.org/type/StickerSet.html deleted file mode 100644 index 67c5dd20d1..0000000000 --- a/data/core.telegram.org/type/StickerSet.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - StickerSet - - - - - - - - - - - - - -
- -
-
-
- -

StickerSet

- -

Represents a stickerset (stickerpack)

-

- -
-
stickerSet#d7df217a flags:# archived:flags.1?true official:flags.2?true masks:flags.3?true animated:flags.5?true videos:flags.6?true installed_date:flags.0?int id:long access_hash:long title:string short_name:string thumbs:flags.4?Vector<PhotoSize> thumb_dc_id:flags.4?int thumb_version:flags.4?int count:int hash:int = StickerSet;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
stickerSetRepresents a stickerset (stickerpack)
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/StickerSetCovered.html b/data/core.telegram.org/type/StickerSetCovered.html deleted file mode 100644 index 08031c4dad..0000000000 --- a/data/core.telegram.org/type/StickerSetCovered.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - StickerSetCovered - - - - - - - - - - - - - -
- -
-
-
- -

StickerSetCovered

- -

Stickerset, with a specific sticker as preview

-

- -
-
stickerSetCovered#6410a5d2 set:StickerSet cover:Document = StickerSetCovered;
-stickerSetMultiCovered#3407e51b set:StickerSet covers:Vector<Document> = StickerSetCovered;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
stickerSetCoveredStickerset, with a specific sticker as preview
stickerSetMultiCoveredStickerset, with a specific stickers as preview
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Theme.html b/data/core.telegram.org/type/Theme.html deleted file mode 100644 index a7fbcafad3..0000000000 --- a/data/core.telegram.org/type/Theme.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - Theme - - - - - - - - - - - - - -
- -
-
-
- -

Theme

- -

Cloud theme

-

- -
-
theme#e802b8dc flags:# creator:flags.0?true default:flags.1?true for_chat:flags.5?true id:long access_hash:long slug:string title:string document:flags.2?Document settings:flags.3?ThemeSettings installs_count:flags.4?int = Theme;
-
----functions---
-
-account.createTheme#8432c21f flags:# slug:string title:string document:flags.2?InputDocument settings:flags.3?InputThemeSettings = Theme;
-account.updateTheme#5cb367d5 flags:# format:string theme:InputTheme slug:flags.0?string title:flags.1?string document:flags.2?InputDocument settings:flags.3?InputThemeSettings = Theme;
-account.getTheme#8d9d742b format:string theme:InputTheme document_id:long = Theme;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
themeTheme
-

Methods

- - - - - - - - - - - - - - - - - - - - - -
MethodDescription
account.createThemeCreate a theme
account.updateThemeUpdate theme
account.getThemeGet theme information
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/ThemeSettings.html b/data/core.telegram.org/type/ThemeSettings.html deleted file mode 100644 index 1bc573edcb..0000000000 --- a/data/core.telegram.org/type/ThemeSettings.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - ThemeSettings - - - - - - - - - - - - - -
- -
-
-
- -

ThemeSettings

- -

Theme settings

-

- -
-
themeSettings#fa58b6d4 flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int outbox_accent_color:flags.3?int message_colors:flags.0?Vector<int> wallpaper:flags.1?WallPaper = ThemeSettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
themeSettingsTheme settings
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/TopPeer.html b/data/core.telegram.org/type/TopPeer.html deleted file mode 100644 index 94574c28ac..0000000000 --- a/data/core.telegram.org/type/TopPeer.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - TopPeer - - - - - - - - - - - - - -
- -
-
-
- -

TopPeer

- -

Top peer

-

- -
-
topPeer#edcdc05b peer:Peer rating:double = TopPeer;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
topPeerTop peer
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/TopPeerCategory.html b/data/core.telegram.org/type/TopPeerCategory.html deleted file mode 100644 index dac2ccf4ae..0000000000 --- a/data/core.telegram.org/type/TopPeerCategory.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - TopPeerCategory - - - - - - - - - - - - - -
- -
-
-
- -

TopPeerCategory

- -

Top peer category

-

- -
-
topPeerCategoryBotsPM#ab661b5b = TopPeerCategory;
-topPeerCategoryBotsInline#148677e2 = TopPeerCategory;
-topPeerCategoryCorrespondents#637b7ed = TopPeerCategory;
-topPeerCategoryGroups#bd17a14a = TopPeerCategory;
-topPeerCategoryChannels#161d9628 = TopPeerCategory;
-topPeerCategoryPhoneCalls#1e76a78c = TopPeerCategory;
-topPeerCategoryForwardUsers#a8406ca9 = TopPeerCategory;
-topPeerCategoryForwardChats#fbeec0f0 = TopPeerCategory;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
topPeerCategoryBotsPMMost used bots
topPeerCategoryBotsInlineMost used inline bots
topPeerCategoryCorrespondentsUsers we've chatted most frequently with
topPeerCategoryGroupsOften-opened groups and supergroups
topPeerCategoryChannelsMost frequently visited channels
topPeerCategoryPhoneCallsMost frequently called users
topPeerCategoryForwardUsersUsers to which the users often forwards messages to
topPeerCategoryForwardChatsChats to which the users often forwards messages to
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/TopPeerCategoryPeers.html b/data/core.telegram.org/type/TopPeerCategoryPeers.html deleted file mode 100644 index 53a033e129..0000000000 --- a/data/core.telegram.org/type/TopPeerCategoryPeers.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - TopPeerCategoryPeers - - - - - - - - - - - - - -
- -
-
-
- -

TopPeerCategoryPeers

- -

Top peers by top peer category

-

- -
-
topPeerCategoryPeers#fb834291 category:TopPeerCategory count:int peers:Vector<TopPeer> = TopPeerCategoryPeers;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
topPeerCategoryPeersTop peer category
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/True.html b/data/core.telegram.org/type/True.html deleted file mode 100644 index a3b2316c7f..0000000000 --- a/data/core.telegram.org/type/True.html +++ /dev/null @@ -1,145 +0,0 @@ - - - - - True - - - - - - - - - - - - - -
- -
-
-
- -

True

- -

See predefined identifiers.

-

- -
-
true#3fedd339 = True;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
trueSee predefined identifiers.
-

Related pages

-

TL-formal

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Update.html b/data/core.telegram.org/type/Update.html deleted file mode 100644 index 4b82d7af3a..0000000000 --- a/data/core.telegram.org/type/Update.html +++ /dev/null @@ -1,603 +0,0 @@ - - - - - Update - - - - - - - - - - - - - -
- -
-
-
- -

Update

- -

Object contains info on events occured.

-

- -
-
updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
-updateMessageID#4e90bfd6 id:int random_id:long = Update;
-updateDeleteMessages#a20db0e5 messages:Vector<int> pts:int pts_count:int = Update;
-updateUserTyping#c01e857f user_id:long action:SendMessageAction = Update;
-updateChatUserTyping#83487af0 chat_id:long from_id:Peer action:SendMessageAction = Update;
-updateChatParticipants#7761198 participants:ChatParticipants = Update;
-updateUserStatus#e5bdf8de user_id:long status:UserStatus = Update;
-updateUserName#c3f202e0 user_id:long first_name:string last_name:string username:string = Update;
-updateUserPhoto#f227868c user_id:long date:int photo:UserProfilePhoto previous:Bool = Update;
-updateNewEncryptedMessage#12bcbd9a message:EncryptedMessage qts:int = Update;
-updateEncryptedChatTyping#1710f156 chat_id:int = Update;
-updateEncryption#b4a2e88d chat:EncryptedChat date:int = Update;
-updateEncryptedMessagesRead#38fe25b7 chat_id:int max_date:int date:int = Update;
-updateChatParticipantAdd#3dda5451 chat_id:long user_id:long inviter_id:long date:int version:int = Update;
-updateChatParticipantDelete#e32f3d77 chat_id:long user_id:long version:int = Update;
-updateDcOptions#8e5e9873 dc_options:Vector<DcOption> = Update;
-updateNotifySettings#bec268ef peer:NotifyPeer notify_settings:PeerNotifySettings = Update;
-updateServiceNotification#ebe46819 flags:# popup:flags.0?true inbox_date:flags.1?int type:string message:string media:MessageMedia entities:Vector<MessageEntity> = Update;
-updatePrivacy#ee3b272a key:PrivacyKey rules:Vector<PrivacyRule> = Update;
-updateUserPhone#5492a13 user_id:long phone:string = Update;
-updateReadHistoryInbox#9c974fdf flags:# folder_id:flags.0?int peer:Peer max_id:int still_unread_count:int pts:int pts_count:int = Update;
-updateReadHistoryOutbox#2f2f21bf peer:Peer max_id:int pts:int pts_count:int = Update;
-updateWebPage#7f891213 webpage:WebPage pts:int pts_count:int = Update;
-updateReadMessagesContents#68c13933 messages:Vector<int> pts:int pts_count:int = Update;
-updateChannelTooLong#108d941f flags:# channel_id:long pts:flags.0?int = Update;
-updateChannel#635b4c09 channel_id:long = Update;
-updateNewChannelMessage#62ba04d9 message:Message pts:int pts_count:int = Update;
-updateReadChannelInbox#922e6e10 flags:# folder_id:flags.0?int channel_id:long max_id:int still_unread_count:int pts:int = Update;
-updateDeleteChannelMessages#c32d5b12 channel_id:long messages:Vector<int> pts:int pts_count:int = Update;
-updateChannelMessageViews#f226ac08 channel_id:long id:int views:int = Update;
-updateChatParticipantAdmin#d7ca61a2 chat_id:long user_id:long is_admin:Bool version:int = Update;
-updateNewStickerSet#688a30aa stickerset:messages.StickerSet = Update;
-updateStickerSetsOrder#bb2d201 flags:# masks:flags.0?true order:Vector<long> = Update;
-updateStickerSets#43ae3dec = Update;
-updateSavedGifs#9375341e = Update;
-updateBotInlineQuery#496f379c flags:# query_id:long user_id:long query:string geo:flags.0?GeoPoint peer_type:flags.1?InlineQueryPeerType offset:string = Update;
-updateBotInlineSend#12f12a07 flags:# user_id:long query:string geo:flags.0?GeoPoint id:string msg_id:flags.1?InputBotInlineMessageID = Update;
-updateEditChannelMessage#1b3f4df7 message:Message pts:int pts_count:int = Update;
-updateBotCallbackQuery#b9cfc48d flags:# query_id:long user_id:long peer:Peer msg_id:int chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
-updateEditMessage#e40370a3 message:Message pts:int pts_count:int = Update;
-updateInlineBotCallbackQuery#691e9052 flags:# query_id:long user_id:long msg_id:InputBotInlineMessageID chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
-updateReadChannelOutbox#b75f99a9 channel_id:long max_id:int = Update;
-updateDraftMessage#ee2bb969 peer:Peer draft:DraftMessage = Update;
-updateReadFeaturedStickers#571d2742 = Update;
-updateRecentStickers#9a422c20 = Update;
-updateConfig#a229dd06 = Update;
-updatePtsChanged#3354678f = Update;
-updateChannelWebPage#2f2ba99f channel_id:long webpage:WebPage pts:int pts_count:int = Update;
-updateDialogPinned#6e6fe51c flags:# pinned:flags.0?true folder_id:flags.1?int peer:DialogPeer = Update;
-updatePinnedDialogs#fa0f3ca2 flags:# folder_id:flags.1?int order:flags.0?Vector<DialogPeer> = Update;
-updateBotWebhookJSON#8317c0c3 data:DataJSON = Update;
-updateBotWebhookJSONQuery#9b9240a6 query_id:long data:DataJSON timeout:int = Update;
-updateBotShippingQuery#b5aefd7d query_id:long user_id:long payload:bytes shipping_address:PostAddress = Update;
-updateBotPrecheckoutQuery#8caa9a96 flags:# query_id:long user_id:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string currency:string total_amount:long = Update;
-updatePhoneCall#ab0f6b1e phone_call:PhoneCall = Update;
-updateLangPackTooLong#46560264 lang_code:string = Update;
-updateLangPack#56022f4d difference:LangPackDifference = Update;
-updateFavedStickers#e511996d = Update;
-updateChannelReadMessagesContents#44bdd535 channel_id:long messages:Vector<int> = Update;
-updateContactsReset#7084a7be = Update;
-updateChannelAvailableMessages#b23fc698 channel_id:long available_min_id:int = Update;
-updateDialogUnreadMark#e16459c3 flags:# unread:flags.0?true peer:DialogPeer = Update;
-updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;
-updateChatDefaultBannedRights#54c01850 peer:Peer default_banned_rights:ChatBannedRights version:int = Update;
-updateFolderPeers#19360dc0 folder_peers:Vector<FolderPeer> pts:int pts_count:int = Update;
-updatePeerSettings#6a7e7366 peer:Peer settings:PeerSettings = Update;
-updatePeerLocated#b4afcfb0 peers:Vector<PeerLocated> = Update;
-updateNewScheduledMessage#39a51dfb message:Message = Update;
-updateDeleteScheduledMessages#90866cee peer:Peer messages:Vector<int> = Update;
-updateTheme#8216fba3 theme:Theme = Update;
-updateGeoLiveViewed#871fb939 peer:Peer msg_id:int = Update;
-updateLoginToken#564fe691 = Update;
-updateMessagePollVote#106395c9 poll_id:long user_id:long options:Vector<bytes> qts:int = Update;
-updateDialogFilter#26ffde7d flags:# id:int filter:flags.0?DialogFilter = Update;
-updateDialogFilterOrder#a5d72105 order:Vector<int> = Update;
-updateDialogFilters#3504914f = Update;
-updatePhoneCallSignalingData#2661bf09 phone_call_id:long data:bytes = Update;
-updateChannelMessageForwards#d29a27f4 channel_id:long id:int forwards:int = Update;
-updateReadChannelDiscussionInbox#d6b19546 flags:# channel_id:long top_msg_id:int read_max_id:int broadcast_id:flags.0?long broadcast_post:flags.0?int = Update;
-updateReadChannelDiscussionOutbox#695c9e7c channel_id:long top_msg_id:int read_max_id:int = Update;
-updatePeerBlocked#246a4b22 peer_id:Peer blocked:Bool = Update;
-updateChannelUserTyping#8c88c923 flags:# channel_id:long top_msg_id:flags.0?int from_id:Peer action:SendMessageAction = Update;
-updatePinnedMessages#ed85eab5 flags:# pinned:flags.0?true peer:Peer messages:Vector<int> pts:int pts_count:int = Update;
-updatePinnedChannelMessages#5bb98608 flags:# pinned:flags.0?true channel_id:long messages:Vector<int> pts:int pts_count:int = Update;
-updateChat#f89a6a4e chat_id:long = Update;
-updateGroupCallParticipants#f2ebdb4e call:InputGroupCall participants:Vector<GroupCallParticipant> version:int = Update;
-updateGroupCall#14b24500 chat_id:long call:GroupCall = Update;
-updatePeerHistoryTTL#bb9bb9a5 flags:# peer:Peer ttl_period:flags.0?int = Update;
-updateChatParticipant#d087663a flags:# chat_id:long date:int actor_id:long user_id:long prev_participant:flags.0?ChatParticipant new_participant:flags.1?ChatParticipant invite:flags.2?ExportedChatInvite qts:int = Update;
-updateChannelParticipant#985d3abb flags:# channel_id:long date:int actor_id:long user_id:long prev_participant:flags.0?ChannelParticipant new_participant:flags.1?ChannelParticipant invite:flags.2?ExportedChatInvite qts:int = Update;
-updateBotStopped#c4870a49 user_id:long date:int stopped:Bool qts:int = Update;
-updateGroupCallConnection#b783982 flags:# presentation:flags.0?true params:DataJSON = Update;
-updateBotCommands#4d712f2e peer:Peer bot_id:long commands:Vector<BotCommand> = Update;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
updateNewMessageNew message.
updateMessageIDSent message with random_id client identifier was assigned an identifier.
updateDeleteMessagesMessages were deleted.
updateUserTypingThe user is preparing a message; typing, recording, uploading, etc. This update is valid for 6 seconds. If no repeated update received after 6 seconds, it should be considered that the user stopped doing whatever he's been doing.
updateChatUserTypingThe user is preparing a message in a group; typing, recording, uploading, etc. This update is valid for 6 seconds. If no repeated update received after 6 seconds, it should be considered that the user stopped doing whatever he's been doing.
updateChatParticipantsComposition of chat participants changed.
updateUserStatusContact status update.
updateUserNameChanges the user's first name, last name and username.
updateUserPhotoChange of contact's profile photo.
updateNewEncryptedMessageNew encrypted message.
updateEncryptedChatTypingInterlocutor is typing a message in an encrypted chat. Update period is 6 second. If upon this time there is no repeated update, it shall be considered that the interlocutor stopped typing.
updateEncryptionChange of state in an encrypted chat.
updateEncryptedMessagesReadCommunication history in an encrypted chat was marked as read.
updateChatParticipantAddNew group member.
updateChatParticipantDeleteA member has left the group.
updateDcOptionsChanges in the data center configuration options.
updateNotifySettingsChanges in notification settings.
updateServiceNotificationA service message for the user.

The app must show the message to the user upon receiving this update. In case the popup parameter was passed, the text message must be displayed in a popup alert immediately upon receipt. It is recommended to handle the text as you would an ordinary message in terms of highlighting links, etc. The message must also be stored locally as part of the message history with the user id 777000 (Telegram Notifications).
updatePrivacyPrivacy rules were changed
updateUserPhoneA user's phone number was changed
updateReadHistoryInboxIncoming messages were read
updateReadHistoryOutboxOutgoing messages were read
updateWebPageAn (IV) webpage preview was generated
updateReadMessagesContentsContents of messages in the common message box were read
updateChannelTooLongThere are new updates in the specified channel, the client must fetch them, eventually starting the specified pts if the difference is too long or if the channel isn't currently in the states.
updateChannelA new channel is available
updateNewChannelMessageA new message was sent in a channel/supergroup
updateReadChannelInboxIncoming messages in a channel/supergroup were read
updateDeleteChannelMessagesSome messages in a supergroup/channel were deleted
updateChannelMessageViewsThe view counter of a message in a channel has changed
updateChatParticipantAdminAdmin permissions of a user in a legacy group were changed
updateNewStickerSetA new stickerset was installed
updateStickerSetsOrderThe order of stickersets was changed
updateStickerSetsInstalled stickersets have changed, the client should refetch them using messages.getAllStickers
updateSavedGifsThe saved gif list has changed, the client should refetch it using messages.getSavedGifs
updateBotInlineQueryAn incoming inline query
updateBotInlineSendThe result of an inline query that was chosen by a user and sent to their chat partner. Please see our documentation on the feedback collecting for details on how to enable these updates for your bot.
updateEditChannelMessageA message was edited in a channel/supergroup
updateBotCallbackQueryA callback button was pressed, and the button data was sent to the bot that created the button
updateEditMessageA message was edited
updateInlineBotCallbackQueryThis notification is received by bots when a button is pressed
updateReadChannelOutboxOutgoing messages in a channel/supergroup were read
updateDraftMessageNotifies a change of a message draft.
updateReadFeaturedStickersSome featured stickers were marked as read
updateRecentStickersThe recent sticker list was updated
updateConfigThe server-side configuration has changed; the client should re-fetch the config using help.getConfig
updatePtsChangedCommon message box sequence PTS has changed, state has to be refetched using updates.getState
updateChannelWebPageA webpage preview of a link in a channel/supergroup message was generated
updateDialogPinnedA dialog was pinned/unpinned
updatePinnedDialogsPinned dialogs were updated
updateBotWebhookJSONA new incoming event; for bots only
updateBotWebhookJSONQueryA new incoming query; for bots only
updateBotShippingQueryThis object contains information about an incoming shipping query.
updateBotPrecheckoutQueryThis object contains information about an incoming pre-checkout query.
updatePhoneCallAn incoming phone call
updateLangPackTooLongA language pack has changed, the client should manually fetch the changed strings using langpack.getDifference
updateLangPackLanguage pack updated
updateFavedStickersThe list of favorited stickers was changed, the client should call messages.getFavedStickers to refetch the new list
updateChannelReadMessagesContentsThe specified channel/supergroup messages were read
updateContactsResetAll contacts were deleted
updateChannelAvailableMessagesThe history of a channel/supergroup was hidden.
updateDialogUnreadMarkThe manual unread mark of a chat was changed
updateMessagePollThe results of a poll have changed
updateChatDefaultBannedRightsDefault banned rights in a normal chat were updated
updateFolderPeersThe dialog list of a folder was changed
updatePeerSettingsSettings of a certain peer have changed
updatePeerLocatedList of peers near you was updated
updateNewScheduledMessageNew incoming scheduled message
updateDeleteScheduledMessagesSome scheduled messages were deleted
updateThemeA new cloud theme was installed
updateGeoLiveViewedLive geoposition message was viewed
updateLoginTokenA login token (for login via QR code) was generated
updateMessagePollVoteA specific user has voted in a poll
updateDialogFilterA new folder was added
updateDialogFilterOrderNew chat folders order
updateDialogFiltersUpdate folder list
updatePhoneCallSignalingDataIncoming phone call signaling payload
updateChannelMessageForwardsThe forward counter of a message in a channel has changed
updateReadChannelDiscussionInboxIncoming messages were marked as read
updateReadChannelDiscussionOutboxOutgoing comments in a discussion thread were marked as read
updatePeerBlockedA peer was blocked
updateChannelUserTypinguser is typing in a supergroup, channel or message thread
updatePinnedMessagesSome messages were pinned in a chat
updatePinnedChannelMessagesMessages were pinned/unpinned in a channel/supergroup
updateChatA new chat is available
updateGroupCallParticipantsThe participant list of a certain group call has changed
updateGroupCallA new groupcall was started
updatePeerHistoryTTLThe Time-To-Live for messages sent by the current user in a specific chat has changed
updateChatParticipantA user has joined or left a specific chat
updateChannelParticipantA participant has left/joined a channel or supergroup.
updateBotStoppedA bot was stopped or re-started.
updateGroupCallConnectionNew WebRTC parameters
updateBotCommandsThe command set of a certain bot in a certain chat has changed.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Updates.html b/data/core.telegram.org/type/Updates.html deleted file mode 100644 index a5e8ef3a5e..0000000000 --- a/data/core.telegram.org/type/Updates.html +++ /dev/null @@ -1,508 +0,0 @@ - - - - - Updates - - - - - - - - - - - - - -
- -
-
-
- -

Updates

- -

Object which is perceived by the client without a call on its part when an event occurs.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-
----functions---
-
-contacts.deleteContacts#96a0e00 id:Vector<InputUser> = Updates;
-contacts.addContact#e8f463d0 flags:# add_phone_privacy_exception:flags.0?true id:InputUser first_name:string last_name:string phone:string = Updates;
-contacts.acceptContact#f831a20f id:InputUser = Updates;
-contacts.getLocated#d348bc44 flags:# background:flags.1?true geo_point:InputGeoPoint self_expires:flags.0?int = Updates;
-contacts.blockFromReplies#29a8962c flags:# delete_message:flags.0?true delete_history:flags.1?true report_spam:flags.2?true msg_id:int = Updates;
-
-messages.sendMessage#520c3870 flags:# no_webpage:flags.1?true silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-messages.forwardMessages#d9fee60e flags:# silent:flags.5?true background:flags.6?true with_my_score:flags.8?true drop_author:flags.11?true drop_media_captions:flags.12?true from_peer:InputPeer id:Vector<int> random_id:Vector<long> to_peer:InputPeer schedule_date:flags.10?int = Updates;
-messages.editChatTitle#73783ffd chat_id:long title:string = Updates;
-messages.editChatPhoto#35ddd674 chat_id:long photo:InputChatPhoto = Updates;
-messages.addChatUser#f24753e3 chat_id:long user_id:InputUser fwd_limit:int = Updates;
-messages.deleteChatUser#a2185cab flags:# revoke_history:flags.0?true chat_id:long user_id:InputUser = Updates;
-messages.createChat#9cb126e users:Vector<InputUser> title:string = Updates;
-messages.importChatInvite#6c50051c hash:string = Updates;
-messages.startBot#e6df7378 bot:InputUser peer:InputPeer random_id:long start_param:string = Updates;
-messages.migrateChat#a2875319 chat_id:long = Updates;
-messages.sendInlineBotResult#220815b0 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true hide_via:flags.11?true peer:InputPeer reply_to_msg_id:flags.0?int random_id:long query_id:long id:string schedule_date:flags.10?int = Updates;
-messages.editMessage#48f71778 flags:# no_webpage:flags.1?true peer:InputPeer id:int message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.15?int = Updates;
-messages.getAllDrafts#6a3f8d65 = Updates;
-messages.setGameScore#8ef8ecc0 flags:# edit_message:flags.0?true force:flags.1?true peer:InputPeer id:int user_id:InputUser score:int = Updates;
-messages.sendScreenshotNotification#c97df020 peer:InputPeer reply_to_msg_id:int random_id:long = Updates;
-messages.sendMultiMedia#cc0110cb flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int multi_media:Vector<InputSingleMedia> schedule_date:flags.10?int = Updates;
-messages.updatePinnedMessage#d2aaf7ec flags:# silent:flags.0?true unpin:flags.1?true pm_oneside:flags.2?true peer:InputPeer id:int = Updates;
-messages.sendVote#10ea6184 peer:InputPeer msg_id:int options:Vector<bytes> = Updates;
-messages.getPollResults#73bb643b peer:InputPeer msg_id:int = Updates;
-messages.editChatDefaultBannedRights#a5866b41 peer:InputPeer banned_rights:ChatBannedRights = Updates;
-messages.sendScheduledMessages#bd38850a peer:InputPeer id:Vector<int> = Updates;
-messages.deleteScheduledMessages#59ae2b16 peer:InputPeer id:Vector<int> = Updates;
-messages.setHistoryTTL#b80e5fe4 peer:InputPeer period:int = Updates;
-messages.setChatTheme#e63be13f peer:InputPeer emoticon:string = Updates;
-
-help.getAppChangelog#9010ef6f prev_app_version:string = Updates;
-
-channels.createChannel#3d5fb10f flags:# broadcast:flags.0?true megagroup:flags.1?true for_import:flags.3?true title:string about:string geo_point:flags.2?InputGeoPoint address:flags.2?string = Updates;
-channels.editAdmin#d33c8902 channel:InputChannel user_id:InputUser admin_rights:ChatAdminRights rank:string = Updates;
-channels.editTitle#566decd0 channel:InputChannel title:string = Updates;
-channels.editPhoto#f12e57c9 channel:InputChannel photo:InputChatPhoto = Updates;
-channels.joinChannel#24b524c5 channel:InputChannel = Updates;
-channels.leaveChannel#f836aa95 channel:InputChannel = Updates;
-channels.inviteToChannel#199f3a6c channel:InputChannel users:Vector<InputUser> = Updates;
-channels.deleteChannel#c0111fe3 channel:InputChannel = Updates;
-channels.toggleSignatures#1f69b606 channel:InputChannel enabled:Bool = Updates;
-channels.editBanned#96e6cd81 channel:InputChannel participant:InputPeer banned_rights:ChatBannedRights = Updates;
-channels.togglePreHistoryHidden#eabbb94c channel:InputChannel enabled:Bool = Updates;
-channels.editCreator#8f38cd1f channel:InputChannel user_id:InputUser password:InputCheckPasswordSRP = Updates;
-channels.toggleSlowMode#edd49ef0 channel:InputChannel seconds:int = Updates;
-channels.convertToGigagroup#b290c69 channel:InputChannel = Updates;
-
-phone.discardCall#b2cbc1c0 flags:# video:flags.0?true peer:InputPhoneCall duration:int reason:PhoneCallDiscardReason connection_id:long = Updates;
-phone.setCallRating#59ead627 flags:# user_initiative:flags.0?true peer:InputPhoneCall rating:int comment:string = Updates;
-phone.createGroupCall#48cdc6d8 flags:# peer:InputPeer random_id:int title:flags.0?string schedule_date:flags.1?int = Updates;
-phone.joinGroupCall#b132ff7b flags:# muted:flags.0?true video_stopped:flags.2?true call:InputGroupCall join_as:InputPeer invite_hash:flags.1?string params:DataJSON = Updates;
-phone.leaveGroupCall#500377f9 call:InputGroupCall source:int = Updates;
-phone.inviteToGroupCall#7b393160 call:InputGroupCall users:Vector<InputUser> = Updates;
-phone.discardGroupCall#7a777135 call:InputGroupCall = Updates;
-phone.toggleGroupCallSettings#74bbb43d flags:# reset_invite_hash:flags.1?true call:InputGroupCall join_muted:flags.0?Bool = Updates;
-phone.toggleGroupCallRecord#f128c708 flags:# start:flags.0?true video:flags.2?true call:InputGroupCall title:flags.1?string video_portrait:flags.2?Bool = Updates;
-phone.editGroupCallParticipant#a5273abf flags:# call:InputGroupCall participant:InputPeer muted:flags.0?Bool volume:flags.1?int raise_hand:flags.2?Bool video_stopped:flags.3?Bool video_paused:flags.4?Bool presentation_paused:flags.5?Bool = Updates;
-phone.editGroupCallTitle#1ca6ac0a call:InputGroupCall title:string = Updates;
-phone.toggleGroupCallStartSubscription#219c34e6 call:InputGroupCall subscribed:Bool = Updates;
-phone.startScheduledGroupCall#5680e342 call:InputGroupCall = Updates;
-phone.joinGroupCallPresentation#cbea6bc4 call:InputGroupCall params:DataJSON = Updates;
-phone.leaveGroupCallPresentation#1c50d144 call:InputGroupCall = Updates;
-
-account.getNotifyExceptions#53577479 flags:# compare_sound:flags.1?true peer:flags.0?InputNotifyPeer = Updates;
-
-folders.editPeerFolders#6847d0ab folder_peers:Vector<InputFolderPeer> = Updates;
-folders.deleteFolder#1c295881 folder_id:int = Updates;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
updatesTooLongToo many updates, it is necessary to execute updates.getDifference.
updateShortMessageInfo about a message sent to (received from) another user
updateShortChatMessageShortened constructor containing info on one new incoming text message from a chat
updateShortShortened constructor containing info on one update not requiring auxiliary data
updatesCombinedConstructor for a group of updates.
updatesFull constructor of updates
updateShortSentMessageShortened constructor containing info on one outgoing message to a contact (the destination chat has to be extracted from the method call that returned this object).
-

Methods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
MethodDescription
contacts.deleteContactsDeletes several contacts from the list.
messages.sendMessageSends a message to a chat
messages.sendMediaSend a media
messages.forwardMessagesForwards messages by their IDs.
messages.editChatTitleChanages chat name and sends a service message on it.
messages.editChatPhotoChanges chat photo and sends a service message on it
messages.addChatUserAdds a user to a chat and sends a service message on it.
messages.deleteChatUserDeletes a user from a chat and sends a service message on it.
messages.createChatCreates a new chat.
messages.importChatInviteImport a chat invite and join a private chat/supergroup/channel
messages.startBotStart a conversation with a bot using a deep linking parameter
help.getAppChangelogGet changelog of current app
channels.createChannelCreate a supergroup/channel.
channels.editAdminModify the admin rights of a user in a supergroup/channel.
channels.editTitleEdit the name of a channel/supergroup
channels.editPhotoChange the photo of a channel/supergroup
channels.joinChannelJoin a channel/supergroup
channels.leaveChannelLeave a channel/supergroup
channels.inviteToChannelInvite users to a channel/supergroup
channels.deleteChannelDelete a channel/supergroup
messages.migrateChatTurn a legacy group into a supergroup
messages.sendInlineBotResultSend a result obtained using messages.getInlineBotResults.
channels.toggleSignaturesEnable/disable message signatures in channels
messages.editMessageEdit message
messages.getAllDraftsSave get all message drafts.
messages.setGameScoreUse this method to set the score of the specified user in a game sent as a normal message (bots only).
phone.discardCallRefuse or end running call
phone.setCallRatingRate a call
channels.editBannedBan/unban/kick a user in a supergroup/channel.
messages.sendScreenshotNotificationNotify the other user in a private chat that a screenshot of the chat was taken
channels.togglePreHistoryHiddenHide/unhide message history for new channel/supergroup users
messages.sendMultiMediaSend an album of media
messages.updatePinnedMessagePin a message
account.getNotifyExceptionsReturns list of chats with non-default notification settings
messages.sendVoteVote in a poll
messages.getPollResultsGet poll results
messages.editChatDefaultBannedRightsEdit the default banned rights of a channel/supergroup/group.
folders.editPeerFoldersEdit peers in folder
folders.deleteFolderDelete a folder
contacts.addContactAdd an existing telegram user as contact
contacts.acceptContactIf the peer settings of a new user allow us to add him as contact, add that user as contact
channels.editCreatorTransfer channel ownership
contacts.getLocatedGet contacts near you
channels.toggleSlowModeToggle supergroup slow mode: if enabled, users will only be able to send one message every seconds seconds
messages.sendScheduledMessagesSend scheduled messages
messages.deleteScheduledMessagesDelete scheduled messages
contacts.blockFromRepliesStop getting notifications about thread replies of a certain user in @replies
phone.createGroupCallCreate a group call or livestream
phone.joinGroupCallJoin a group call
phone.leaveGroupCallLeave a group call
phone.inviteToGroupCallInvite a set of users to a group call.
phone.discardGroupCallTerminate a group call
phone.toggleGroupCallSettingsChange group call settings
messages.setHistoryTTLSet maximum Time-To-Live of all messages in the specified chat
channels.convertToGigagroupConvert a supergroup to a gigagroup
phone.toggleGroupCallRecordStart or stop recording a group call
phone.editGroupCallParticipantEdit information about a given group call participant
phone.editGroupCallTitleEdit the title of a group call or livestream
phone.toggleGroupCallStartSubscriptionSubscribe or unsubscribe to a scheduled group call
phone.startScheduledGroupCallStart a scheduled group call.
phone.joinGroupCallPresentationStart screen sharing in a call
phone.leaveGroupCallPresentationStop screen sharing in a group call
messages.setChatThemeChange the chat theme of a certain chat
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/UrlAuthResult.html b/data/core.telegram.org/type/UrlAuthResult.html deleted file mode 100644 index a0b6f055e5..0000000000 --- a/data/core.telegram.org/type/UrlAuthResult.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - UrlAuthResult - - - - - - - - - - - - - -
- -
-
-
- -

UrlAuthResult

- -

URL authorization result

-

- -
-
urlAuthResultRequest#92d33a0e flags:# request_write_access:flags.0?true bot:User domain:string = UrlAuthResult;
-urlAuthResultAccepted#8f8c0e4e url:string = UrlAuthResult;
-urlAuthResultDefault#a9d6db1f = UrlAuthResult;
-
----functions---
-
-messages.requestUrlAuth#198fb446 flags:# peer:flags.1?InputPeer msg_id:flags.1?int button_id:flags.1?int url:flags.2?string = UrlAuthResult;
-messages.acceptUrlAuth#b12c7125 flags:# write_allowed:flags.0?true peer:flags.1?InputPeer msg_id:flags.1?int button_id:flags.1?int url:flags.2?string = UrlAuthResult;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
urlAuthResultRequestDetails about the authorization request, for more info click here »
urlAuthResultAcceptedDetails about an accepted authorization request, for more info click here »
urlAuthResultDefaultDetails about an accepted authorization request, for more info click here »
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
messages.requestUrlAuthGet more info about a Seamless Telegram Login authorization request, for more info click here »
messages.acceptUrlAuthUse this to accept a Seamless Telegram Login authorization request, for more info click here »
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/User.html b/data/core.telegram.org/type/User.html deleted file mode 100644 index 20e0c4bbb0..0000000000 --- a/data/core.telegram.org/type/User.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - User - - - - - - - - - - - - - -
- -
-
-
- -

User

- -

Object defines a user.

-

- -
-
userEmpty#d3bc4b7a id:long = User;
-user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
-
----functions---
-
-account.updateProfile#78515775 flags:# first_name:flags.0?string last_name:flags.1?string about:flags.2?string = User;
-account.updateUsername#3e0bdd7c username:string = User;
-account.changePhone#70c32edb phone_number:string phone_code_hash:string phone_code:string = User;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
userEmptyEmpty constructor, non-existent user.
userIndicates info about a certain user
-

Methods

- - - - - - - - - - - - - - - - - - - - - -
MethodDescription
account.updateProfileUpdates user profile.
account.updateUsernameChanges username for the current user.
account.changePhoneChange the phone number of the current account
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/UserFull.html b/data/core.telegram.org/type/UserFull.html deleted file mode 100644 index 719ddade41..0000000000 --- a/data/core.telegram.org/type/UserFull.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - UserFull - - - - - - - - - - - - - -
- -
-
-
- -

UserFull

- -

Object contains extended user info.

-

- -
-
userFull#d697ff05 flags:# blocked:flags.0?true phone_calls_available:flags.4?true phone_calls_private:flags.5?true can_pin_message:flags.7?true has_scheduled:flags.12?true video_calls_available:flags.13?true user:User about:flags.1?string settings:PeerSettings profile_photo:flags.2?Photo notify_settings:PeerNotifySettings bot_info:flags.3?BotInfo pinned_msg_id:flags.6?int common_chats_count:int folder_id:flags.11?int ttl_period:flags.14?int theme_emoticon:flags.15?string = UserFull;
-
----functions---
-
-users.getFullUser#ca30a5b1 id:InputUser = UserFull;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
userFullExtended user info
-

Methods

- - - - - - - - - - - - - -
MethodDescription
users.getFullUserReturns extended user info by ID.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/UserProfilePhoto.html b/data/core.telegram.org/type/UserProfilePhoto.html deleted file mode 100644 index a7ec0d4121..0000000000 --- a/data/core.telegram.org/type/UserProfilePhoto.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - UserProfilePhoto - - - - - - - - - - - - - -
- -
-
-
- -

UserProfilePhoto

- -

Object contains info on the user's profile photo.

-

- -
-
userProfilePhotoEmpty#4f11bae1 = UserProfilePhoto;
-userProfilePhoto#82d1f706 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = UserProfilePhoto;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
userProfilePhotoEmptyProfile photo has not been set, or was hidden.
userProfilePhotoUser profile photo.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/UserStatus.html b/data/core.telegram.org/type/UserStatus.html deleted file mode 100644 index 8f1327ddc3..0000000000 --- a/data/core.telegram.org/type/UserStatus.html +++ /dev/null @@ -1,168 +0,0 @@ - - - - - UserStatus - - - - - - - - - - - - - -
- -
-
-
- -

UserStatus

- -

User online status

-

- -
-
userStatusEmpty#9d05049 = UserStatus;
-userStatusOnline#edb93949 expires:int = UserStatus;
-userStatusOffline#8c703f was_online:int = UserStatus;
-userStatusRecently#e26f42f1 = UserStatus;
-userStatusLastWeek#7bf09fc = UserStatus;
-userStatusLastMonth#77ebc742 = UserStatus;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
userStatusEmptyUser status has not been set yet.
userStatusOnlineOnline status of the user.
userStatusOfflineThe user's offline status.
userStatusRecentlyOnline status: last seen recently
userStatusLastWeekOnline status: last seen last week
userStatusLastMonthOnline status: last seen last month
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Vector t.html b/data/core.telegram.org/type/Vector t.html deleted file mode 100644 index 54de2ffb2d..0000000000 --- a/data/core.telegram.org/type/Vector t.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - Vector t - - - - - - - - - - - - - -
- -
-
-
- -

Vector t

- -

Universal vector.

-

- -
-
vector#1cb5c415 {t:Type} # [ t ] = Vector t;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
vectorA universal vector constructor.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/Video.html b/data/core.telegram.org/type/Video.html deleted file mode 100644 index e4aac783bc..0000000000 --- a/data/core.telegram.org/type/Video.html +++ /dev/null @@ -1,128 +0,0 @@ - - - - - Video - - - - - - - - - - - - - -
- -
-
-
- -

Video

- -

Video.

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/VideoSize.html b/data/core.telegram.org/type/VideoSize.html deleted file mode 100644 index 96f57dfd75..0000000000 --- a/data/core.telegram.org/type/VideoSize.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - VideoSize - - - - - - - - - - - - - -
- -
-
-
- -

VideoSize

- -

Represents an animated video thumbnail

-

- -
-
videoSize#de33b094 flags:# type:string w:int h:int size:int video_start_ts:flags.0?double = VideoSize;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
videoSizeAnimated profile picture in MPEG4 format
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/WallPaper.html b/data/core.telegram.org/type/WallPaper.html deleted file mode 100644 index ca67900ae6..0000000000 --- a/data/core.telegram.org/type/WallPaper.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - WallPaper - - - - - - - - - - - - - -
- -
-
-
- -

WallPaper

- -

Object contains info on a wallpaper.

-

- -
-
wallPaper#a437c3ed id:long flags:# creator:flags.0?true default:flags.1?true pattern:flags.3?true dark:flags.4?true access_hash:long slug:string document:Document settings:flags.2?WallPaperSettings = WallPaper;
-wallPaperNoFile#e0804116 id:long flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;
-
----functions---
-
-account.getWallPaper#fc8ddbea wallpaper:InputWallPaper = WallPaper;
-account.uploadWallPaper#dd853661 file:InputFile mime_type:string settings:WallPaperSettings = WallPaper;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
wallPaperWallpaper settings.
wallPaperNoFileNo file wallpaper
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
account.getWallPaperGet info about a certain wallpaper
account.uploadWallPaperCreate and upload a new wallpaper
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/WallPaperSettings.html b/data/core.telegram.org/type/WallPaperSettings.html deleted file mode 100644 index 62dc8c381f..0000000000 --- a/data/core.telegram.org/type/WallPaperSettings.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - WallPaperSettings - - - - - - - - - - - - - -
- -
-
-
- -

WallPaperSettings

- -

Wallpaper settings

-

- -
-
wallPaperSettings#1dc1bca4 flags:# blur:flags.1?true motion:flags.2?true background_color:flags.0?int second_background_color:flags.4?int third_background_color:flags.5?int fourth_background_color:flags.6?int intensity:flags.3?int rotation:flags.4?int = WallPaperSettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
wallPaperSettingsWallpaper settings
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/WebAuthorization.html b/data/core.telegram.org/type/WebAuthorization.html deleted file mode 100644 index 722bc888c0..0000000000 --- a/data/core.telegram.org/type/WebAuthorization.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - WebAuthorization - - - - - - - - - - - - - -
- -
-
-
- -

WebAuthorization

- -

Web authorization

-

- -
-
webAuthorization#a6f8f452 hash:long bot_id:long domain:string browser:string platform:string date_created:int date_active:int ip:string region:string = WebAuthorization;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
webAuthorizationRepresents a bot logged in using the Telegram login widget
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/WebDocument.html b/data/core.telegram.org/type/WebDocument.html deleted file mode 100644 index ab8dd84eaf..0000000000 --- a/data/core.telegram.org/type/WebDocument.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - WebDocument - - - - - - - - - - - - - -
- -
-
-
- -

WebDocument

- -

Remote document

-

- -
-
webDocument#1c570ed1 url:string access_hash:long size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;
-webDocumentNoProxy#f9c8bcc6 url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
webDocumentRemote document
webDocumentNoProxyRemote document that can be downloaded without proxying through telegram
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/WebPage.html b/data/core.telegram.org/type/WebPage.html deleted file mode 100644 index d3d5f7337f..0000000000 --- a/data/core.telegram.org/type/WebPage.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - WebPage - - - - - - - - - - - - - -
- -
-
-
- -

WebPage

- -

Instant View webpage preview

-

- -
-
webPageEmpty#eb1477e8 id:long = WebPage;
-webPagePending#c586da1c id:long date:int = WebPage;
-webPage#e89c45b2 flags:# id:long url:string display_url:string hash:int type:flags.0?string site_name:flags.1?string title:flags.2?string description:flags.3?string photo:flags.4?Photo embed_url:flags.5?string embed_type:flags.5?string embed_width:flags.6?int embed_height:flags.6?int duration:flags.7?int author:flags.8?string document:flags.9?Document cached_page:flags.10?Page attributes:flags.12?Vector<WebPageAttribute> = WebPage;
-webPageNotModified#7311ca11 flags:# cached_page_views:flags.0?int = WebPage;
-
----functions---
-
-messages.getWebPage#32ca8f91 url:string hash:int = WebPage;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
webPageEmptyNo preview is available for the webpage
webPagePendingA preview of the webpage is currently being generated
webPageWebpage preview
webPageNotModifiedThe preview of the webpage hasn't changed
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getWebPageGet instant view page
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/WebPageAttribute.html b/data/core.telegram.org/type/WebPageAttribute.html deleted file mode 100644 index 81e361ff36..0000000000 --- a/data/core.telegram.org/type/WebPageAttribute.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - WebPageAttribute - - - - - - - - - - - - - -
- -
-
-
- -

WebPageAttribute

- -

Webpage attributes

-

- -
-
webPageAttributeTheme#54b56617 flags:# documents:flags.0?Vector<Document> settings:flags.1?ThemeSettings = WebPageAttribute;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
webPageAttributeThemePage theme
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/account.AuthorizationForm b/data/core.telegram.org/type/account.AuthorizationForm deleted file mode 100644 index c91c97ca35..0000000000 --- a/data/core.telegram.org/type/account.AuthorizationForm +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Account.AuthorizationForm - - - - - - - - - - - - - -
- -
-
-
- -

Account.AuthorizationForm

- -

Authorization form

-

- -
-
account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;
-
----functions---
-
-account.getAuthorizationForm#a929597a bot_id:long scope:string public_key:string = account.AuthorizationForm;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.authorizationFormAuthorization form
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getAuthorizationFormReturns a Telegram Passport authorization form for sharing data with a service
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/account.Authorizations b/data/core.telegram.org/type/account.Authorizations deleted file mode 100644 index 9546f70b64..0000000000 --- a/data/core.telegram.org/type/account.Authorizations +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Account.Authorizations - - - - - - - - - - - - - -
- -
-
-
- -

Account.Authorizations

- -

Logged-in sessions

-

- -
-
account.authorizations#1250abde authorizations:Vector<Authorization> = account.Authorizations;
-
----functions---
-
-account.getAuthorizations#e320c158 = account.Authorizations;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.authorizationsLogged-in sessions
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getAuthorizationsGet logged-in sessions
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/account.AutoDownloadSettings b/data/core.telegram.org/type/account.AutoDownloadSettings deleted file mode 100644 index a71f740e6a..0000000000 --- a/data/core.telegram.org/type/account.AutoDownloadSettings +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Account.AutoDownloadSettings - - - - - - - - - - - - - -
- -
-
-
- -

Account.AutoDownloadSettings

- -

Media autodownload settings

-

- -
-
account.autoDownloadSettings#63cacf26 low:AutoDownloadSettings medium:AutoDownloadSettings high:AutoDownloadSettings = account.AutoDownloadSettings;
-
----functions---
-
-account.getAutoDownloadSettings#56da0b3f = account.AutoDownloadSettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.autoDownloadSettingsMedia autodownload settings
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getAutoDownloadSettingsGet media autodownload settings
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/account.ChatThemes b/data/core.telegram.org/type/account.ChatThemes deleted file mode 100644 index 61a5efdf2e..0000000000 --- a/data/core.telegram.org/type/account.ChatThemes +++ /dev/null @@ -1,167 +0,0 @@ - - - - - account.ChatThemes - - - - - - - - - - - - - -
- -
-
-
- -

account.ChatThemes

- -

Available chat themes

-

- -
-
account.chatThemesNotModified#e011e1c4 = account.ChatThemes;
-account.chatThemes#fe4cbebd hash:int themes:Vector<ChatTheme> = account.ChatThemes;
-
----functions---
-
-account.getChatThemes#d6d71d7b hash:int = account.ChatThemes;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
account.chatThemesNotModifiedThe available chat themes were not modified
account.chatThemesAvailable chat themes
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getChatThemesGet all available chat themes
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/account.ContentSettings b/data/core.telegram.org/type/account.ContentSettings deleted file mode 100644 index e8ffd73307..0000000000 --- a/data/core.telegram.org/type/account.ContentSettings +++ /dev/null @@ -1,162 +0,0 @@ - - - - - account.ContentSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.ContentSettings

- -

Sensitive content settings

-

- -
-
account.contentSettings#57e28221 flags:# sensitive_enabled:flags.0?true sensitive_can_change:flags.1?true = account.ContentSettings;
-
----functions---
-
-account.getContentSettings#8b9b4dae = account.ContentSettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.contentSettingsSensitive content settings
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getContentSettingsGet sensitive content settings
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/account.Password b/data/core.telegram.org/type/account.Password deleted file mode 100644 index 5305af021c..0000000000 --- a/data/core.telegram.org/type/account.Password +++ /dev/null @@ -1,162 +0,0 @@ - - - - - account.Password - - - - - - - - - - - - - -
- -
-
-
- -

account.Password

- -

Configuration for two-factor authorization

-

- -
-
account.password#185b184f flags:# has_recovery:flags.0?true has_secure_values:flags.1?true has_password:flags.2?true current_algo:flags.2?PasswordKdfAlgo srp_B:flags.2?bytes srp_id:flags.2?long hint:flags.3?string email_unconfirmed_pattern:flags.4?string new_algo:PasswordKdfAlgo new_secure_algo:SecurePasswordKdfAlgo secure_random:bytes pending_reset_date:flags.5?int = account.Password;
-
----functions---
-
-account.getPassword#548a30f5 = account.Password;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.passwordConfiguration for two-factor authorization
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getPasswordObtain configuration for two-factor authorization with password
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/account.PasswordInputSettings b/data/core.telegram.org/type/account.PasswordInputSettings deleted file mode 100644 index 94972c9aed..0000000000 --- a/data/core.telegram.org/type/account.PasswordInputSettings +++ /dev/null @@ -1,146 +0,0 @@ - - - - - account.PasswordInputSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.PasswordInputSettings

- -

Constructor for setting up a new 2FA SRP password

-

- -
-
account.passwordInputSettings#c23727c9 flags:# new_algo:flags.0?PasswordKdfAlgo new_password_hash:flags.0?bytes hint:flags.0?string email:flags.1?string new_secure_settings:flags.2?SecureSecretSettings = account.PasswordInputSettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.passwordInputSettingsSettings for setting up a new password
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/account.PasswordSettings b/data/core.telegram.org/type/account.PasswordSettings deleted file mode 100644 index 576f249b87..0000000000 --- a/data/core.telegram.org/type/account.PasswordSettings +++ /dev/null @@ -1,164 +0,0 @@ - - - - - account.PasswordSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.PasswordSettings

- -

Private info associated to the password info (recovery email, telegram passport info & so on)

-

- -
-
account.passwordSettings#9a5c33e5 flags:# email:flags.0?string secure_settings:flags.1?SecureSecretSettings = account.PasswordSettings;
-
----functions---
-
-account.getPasswordSettings#9cd4eaf9 password:InputCheckPasswordSRP = account.PasswordSettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.passwordSettingsPrivate info associated to the password info (recovery email, telegram passport info & so on)
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getPasswordSettingsGet private info associated to the password info (recovery email, telegram passport info & so on)
-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/account.PrivacyRules b/data/core.telegram.org/type/account.PrivacyRules deleted file mode 100644 index 01a30770aa..0000000000 --- a/data/core.telegram.org/type/account.PrivacyRules +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Account.PrivacyRules - - - - - - - - - - - - - -
- -
-
-
- -

Account.PrivacyRules

- -

Privacy rules

-

- -
-
account.privacyRules#50a04e45 rules:Vector<PrivacyRule> chats:Vector<Chat> users:Vector<User> = account.PrivacyRules;
-
----functions---
-
-account.getPrivacy#dadbc950 key:InputPrivacyKey = account.PrivacyRules;
-account.setPrivacy#c9f81ce8 key:InputPrivacyKey rules:Vector<InputPrivacyRule> = account.PrivacyRules;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.privacyRulesPrivacy rules
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
account.getPrivacyGet privacy settings of current account
account.setPrivacyChange privacy settings of current account
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/account.ResetPasswordResult b/data/core.telegram.org/type/account.ResetPasswordResult deleted file mode 100644 index a5c2a6ec9c..0000000000 --- a/data/core.telegram.org/type/account.ResetPasswordResult +++ /dev/null @@ -1,175 +0,0 @@ - - - - - account.ResetPasswordResult - - - - - - - - - - - - - -
- -
-
-
- -

account.ResetPasswordResult

- -

Result of an account.resetPassword request.

-

- -
-
account.resetPasswordFailedWait#e3779861 retry_date:int = account.ResetPasswordResult;
-account.resetPasswordRequestedWait#e9effc7d until_date:int = account.ResetPasswordResult;
-account.resetPasswordOk#e926d63e = account.ResetPasswordResult;
-
----functions---
-
-account.resetPassword#9308ce1b = account.ResetPasswordResult;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
account.resetPasswordFailedWaitYou requested a password reset too many times, please wait until the specified date before retrying the reset.
account.resetPasswordRequestedWaitYou already requested a password reset, please wait until the specified date before retrying the reset.
account.resetPasswordOkThe 2FA password was reset successfully.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.resetPasswordInitiate a 2FA password reset
-

Related pages

-

account.resetPassword

-

Initiate a 2FA password reset: can only be used if the user is already logged-in, see here for more info »

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/account.SentChangePhoneCode b/data/core.telegram.org/type/account.SentChangePhoneCode deleted file mode 100644 index c0ce024e0b..0000000000 --- a/data/core.telegram.org/type/account.SentChangePhoneCode +++ /dev/null @@ -1,128 +0,0 @@ - - - - - Account.SentChangePhoneCode - - - - - - - - - - - - - -
- -
-
-
- -

Account.SentChangePhoneCode

- -

Sent phone code

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/account.SentEmailCode b/data/core.telegram.org/type/account.SentEmailCode deleted file mode 100644 index f5659893af..0000000000 --- a/data/core.telegram.org/type/account.SentEmailCode +++ /dev/null @@ -1,162 +0,0 @@ - - - - - account.SentEmailCode - - - - - - - - - - - - - -
- -
-
-
- -

account.SentEmailCode

- -

The email code that was sent

-

- -
-
account.sentEmailCode#811f854f email_pattern:string length:int = account.SentEmailCode;
-
----functions---
-
-account.sendVerifyEmailCode#7011509f email:string = account.SentEmailCode;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.sentEmailCodeThe sent email code
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.sendVerifyEmailCodeSend the verification email code for telegram passport.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/account.Takeout b/data/core.telegram.org/type/account.Takeout deleted file mode 100644 index 2608c74cd5..0000000000 --- a/data/core.telegram.org/type/account.Takeout +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Account.Takeout - - - - - - - - - - - - - -
- -
-
-
- -

Account.Takeout

- -

Takeout info

-

- -
-
account.takeout#4dba4501 id:long = account.Takeout;
-
----functions---
-
-account.initTakeoutSession#f05b4804 flags:# contacts:flags.0?true message_users:flags.1?true message_chats:flags.2?true message_megagroups:flags.3?true message_channels:flags.4?true files:flags.5?true file_max_size:flags.5?int = account.Takeout;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.takeoutTakout info
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.initTakeoutSessionInitialize account takeout session
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/account.Themes b/data/core.telegram.org/type/account.Themes deleted file mode 100644 index 21b17f67c2..0000000000 --- a/data/core.telegram.org/type/account.Themes +++ /dev/null @@ -1,167 +0,0 @@ - - - - - account.Themes - - - - - - - - - - - - - -
- -
-
-
- -

account.Themes

- -

Installed themes

-

- -
-
account.themesNotModified#f41eb622 = account.Themes;
-account.themes#9a3d8c6d hash:long themes:Vector<Theme> = account.Themes;
-
----functions---
-
-account.getThemes#7206e458 format:string hash:long = account.Themes;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
account.themesNotModifiedNo new themes were installed
account.themesInstalled themes
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getThemesGet installed themes
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/account.TmpPassword b/data/core.telegram.org/type/account.TmpPassword deleted file mode 100644 index 3a97076220..0000000000 --- a/data/core.telegram.org/type/account.TmpPassword +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Account.TmpPassword - - - - - - - - - - - - - -
- -
-
-
- -

Account.TmpPassword

- -

Temporary password

-

- -
-
account.tmpPassword#db64fd34 tmp_password:bytes valid_until:int = account.TmpPassword;
-
----functions---
-
-account.getTmpPassword#449e0b51 password:InputCheckPasswordSRP period:int = account.TmpPassword;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.tmpPasswordTemporary payment password
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getTmpPasswordGet temporary payment password
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/account.WallPapers b/data/core.telegram.org/type/account.WallPapers deleted file mode 100644 index 1494bd7c95..0000000000 --- a/data/core.telegram.org/type/account.WallPapers +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Account.WallPapers - - - - - - - - - - - - - -
- -
-
-
- -

Account.WallPapers

- -

Wallpapers

-

- -
-
account.wallPapersNotModified#1c199183 = account.WallPapers;
-account.wallPapers#cdc3858c hash:long wallpapers:Vector<WallPaper> = account.WallPapers;
-
----functions---
-
-account.getWallPapers#7967d36 hash:long = account.WallPapers;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
account.wallPapersNotModifiedNo new wallpapers were found
account.wallPapersInstalled wallpapers
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getWallPapersReturns a list of available wallpapers.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/account.WebAuthorizations b/data/core.telegram.org/type/account.WebAuthorizations deleted file mode 100644 index 687072af52..0000000000 --- a/data/core.telegram.org/type/account.WebAuthorizations +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Account.WebAuthorizations - - - - - - - - - - - - - -
- -
-
-
- -

Account.WebAuthorizations

- -

Web authorizations

-

- -
-
account.webAuthorizations#ed56c9fc authorizations:Vector<WebAuthorization> users:Vector<User> = account.WebAuthorizations;
-
----functions---
-
-account.getWebAuthorizations#182e6d6f = account.WebAuthorizations;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.webAuthorizationsWeb authorizations
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getWebAuthorizationsGet web login widget authorizations
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/auth.Authorization b/data/core.telegram.org/type/auth.Authorization deleted file mode 100644 index 5fca033406..0000000000 --- a/data/core.telegram.org/type/auth.Authorization +++ /dev/null @@ -1,192 +0,0 @@ - - - - - auth.Authorization - - - - - - - - - - - - - -
- -
-
-
- -

auth.Authorization

- -

Oject contains info on user authorization.

-

- -
-
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
-auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
-
----functions---
-
-auth.signUp#80eee427 phone_number:string phone_code_hash:string first_name:string last_name:string = auth.Authorization;
-auth.signIn#bcd51581 phone_number:string phone_code_hash:string phone_code:string = auth.Authorization;
-auth.importAuthorization#a57a7dad id:long bytes:bytes = auth.Authorization;
-auth.importBotAuthorization#67a3ff2c flags:int api_id:int api_hash:string bot_auth_token:string = auth.Authorization;
-auth.checkPassword#d18b4d16 password:InputCheckPasswordSRP = auth.Authorization;
-auth.recoverPassword#37096c70 flags:# code:string new_settings:flags.0?account.PasswordInputSettings = auth.Authorization;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
auth.authorizationContains user authorization info.
auth.authorizationSignUpRequiredAn account with this phone number doesn't exist on telegram: the user has to enter basic information and sign up
-

Methods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
MethodDescription
auth.signUpRegisters a validated phone number in the system.
auth.signInSigns in a user with a validated phone number.
auth.importAuthorizationLogs in a user using a key transmitted from his native data-centre.
auth.importBotAuthorizationLogin as a bot
auth.checkPasswordTry logging to an account protected by a 2FA password.
auth.recoverPasswordReset the 2FA password using the recovery code sent using auth.requestPasswordRecovery.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/auth.CheckedPhone b/data/core.telegram.org/type/auth.CheckedPhone deleted file mode 100644 index de79f5c4ec..0000000000 --- a/data/core.telegram.org/type/auth.CheckedPhone +++ /dev/null @@ -1,128 +0,0 @@ - - - - - Auth.CheckedPhone - - - - - - - - - - - - - -
- -
-
-
- -

Auth.CheckedPhone

- -

Checked phone

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/auth.CodeType b/data/core.telegram.org/type/auth.CodeType deleted file mode 100644 index d652fe1f1e..0000000000 --- a/data/core.telegram.org/type/auth.CodeType +++ /dev/null @@ -1,153 +0,0 @@ - - - - - auth.CodeType - - - - - - - - - - - - - -
- -
-
-
- -

auth.CodeType

- -

Type of verification code that will be sent next if you call the resendCode method

-

- -
-
auth.codeTypeSms#72a3158c = auth.CodeType;
-auth.codeTypeCall#741cd3e3 = auth.CodeType;
-auth.codeTypeFlashCall#226ccefb = auth.CodeType;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
auth.codeTypeSmsType of verification code that will be sent next if you call the resendCode method: SMS code
auth.codeTypeCallType of verification code that will be sent next if you call the resendCode method: SMS code
auth.codeTypeFlashCallType of verification code that will be sent next if you call the resendCode method: SMS code
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/auth.ExportedAuthorization b/data/core.telegram.org/type/auth.ExportedAuthorization deleted file mode 100644 index be1bcc28cb..0000000000 --- a/data/core.telegram.org/type/auth.ExportedAuthorization +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Auth.ExportedAuthorization - - - - - - - - - - - - - -
- -
-
-
- -

Auth.ExportedAuthorization

- -

Exported authorization

-

- -
-
auth.exportedAuthorization#b434e2b8 id:long bytes:bytes = auth.ExportedAuthorization;
-
----functions---
-
-auth.exportAuthorization#e5bfffcd dc_id:int = auth.ExportedAuthorization;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
auth.exportedAuthorizationData for copying of authorization between data centres.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
auth.exportAuthorizationReturns data for copying authorization to another data-centre.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/auth.LoginToken b/data/core.telegram.org/type/auth.LoginToken deleted file mode 100644 index d2fbae7b30..0000000000 --- a/data/core.telegram.org/type/auth.LoginToken +++ /dev/null @@ -1,177 +0,0 @@ - - - - - auth.LoginToken - - - - - - - - - - - - - -
- -
-
-
- -

auth.LoginToken

- -

Login token (for QR code login)

-

- -
-
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
-auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;
-auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;
-
----functions---
-
-auth.exportLoginToken#b7e085fe api_id:int api_hash:string except_ids:Vector<long> = auth.LoginToken;
-auth.importLoginToken#95ac5ce4 token:bytes = auth.LoginToken;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
auth.loginTokenLogin token (for QR code login)
auth.loginTokenMigrateToRepeat the query to the specified DC
auth.loginTokenSuccessLogin via token (QR code) succeded!
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
auth.exportLoginTokenExport login token (for login via QR code)
auth.importLoginTokenLogin using a redirected login token, generated in case of DC mismatch during QR code login.

For more info, see login via QR code.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/auth.PasswordRecovery b/data/core.telegram.org/type/auth.PasswordRecovery deleted file mode 100644 index 94ec06ba24..0000000000 --- a/data/core.telegram.org/type/auth.PasswordRecovery +++ /dev/null @@ -1,165 +0,0 @@ - - - - - auth.PasswordRecovery - - - - - - - - - - - - - -
- -
-
-
- -

auth.PasswordRecovery

- -

Recovery info of a 2FA password, only for accounts with a recovery email configured.

-

- -
-
auth.passwordRecovery#137948a5 email_pattern:string = auth.PasswordRecovery;
-
----functions---
-
-auth.requestPasswordRecovery#d897bc66 = auth.PasswordRecovery;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
auth.passwordRecoveryRecovery info of a 2FA password, only for accounts with a recovery email configured.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
auth.requestPasswordRecoveryRequest recovery code of a 2FA password, only for accounts with a recovery email configured.
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/auth.SentCode b/data/core.telegram.org/type/auth.SentCode deleted file mode 100644 index 1f1481338f..0000000000 --- a/data/core.telegram.org/type/auth.SentCode +++ /dev/null @@ -1,183 +0,0 @@ - - - - - auth.SentCode - - - - - - - - - - - - - -
- -
-
-
- -

auth.SentCode

- -

Contains info on a confirmation code message sent via SMS, phone call or Telegram.

-

- -
-
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
-
----functions---
-
-auth.sendCode#a677244f phone_number:string api_id:int api_hash:string settings:CodeSettings = auth.SentCode;
-auth.resendCode#3ef1a9bf phone_number:string phone_code_hash:string = auth.SentCode;
-
-account.sendChangePhoneCode#82574ae5 phone_number:string settings:CodeSettings = auth.SentCode;
-account.sendConfirmPhoneCode#1b3faa88 hash:string settings:CodeSettings = auth.SentCode;
-account.sendVerifyPhoneCode#a5a356f9 phone_number:string settings:CodeSettings = auth.SentCode;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
auth.sentCodeContains info about a sent verification code.
-

Methods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
MethodDescription
auth.sendCodeSend the verification code for login
account.sendChangePhoneCodeVerify a new phone number to associate to the current account
auth.resendCodeResend the login code via another medium, the phone code type is determined by the return value of the previous auth.sendCode/auth.resendCode: see login for more info.
account.sendConfirmPhoneCodeSend confirmation code to cancel account deletion, for more info click here »
account.sendVerifyPhoneCodeSend the verification phone code for telegram passport.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/auth.SentCodeType b/data/core.telegram.org/type/auth.SentCodeType deleted file mode 100644 index f8c320c6f0..0000000000 --- a/data/core.telegram.org/type/auth.SentCodeType +++ /dev/null @@ -1,158 +0,0 @@ - - - - - auth.SentCodeType - - - - - - - - - - - - - -
- -
-
-
- -

auth.SentCodeType

- -

Type of the verification code that was sent

-

- -
-
auth.sentCodeTypeApp#3dbb5986 length:int = auth.SentCodeType;
-auth.sentCodeTypeSms#c000bba2 length:int = auth.SentCodeType;
-auth.sentCodeTypeCall#5353e5a7 length:int = auth.SentCodeType;
-auth.sentCodeTypeFlashCall#ab03c6d9 pattern:string = auth.SentCodeType;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
auth.sentCodeTypeAppThe code was sent through the telegram app
auth.sentCodeTypeSmsThe code was sent via SMS
auth.sentCodeTypeCallThe code will be sent via a phone call: a synthesized voice will tell the user which verification code to input.
auth.sentCodeTypeFlashCallThe code will be sent via a flash phone call, that will be closed immediately. The phone code will then be the phone number itself, just make sure that the phone number matches the specified pattern.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/bytes.html b/data/core.telegram.org/type/bytes.html deleted file mode 100644 index 898629893f..0000000000 --- a/data/core.telegram.org/type/bytes.html +++ /dev/null @@ -1,125 +0,0 @@ - - - - - bytes - - - - - - - - - - - - - -
- -
-
-
- -

bytes

- -

Basic bare type. It is an alias of the string type, with the difference that the value may contain arbitrary byte sequences, including invalid UTF-8 sequences.

-

When computing crc32 for a constructor or method it is necessary to replace all byte types with string types.

-

Related pages

-

string

-

A basic bare type. Values of type string look differently depending on the length L of the string being serialized:

-
    -
  • If L <= 253, the serialization contains one byte with the value of L, then L bytes of the string followed by 0 to 3 characters containing 0, such that the overall length of the value be divisible by 4, whereupon all of this is interpreted as a sequence of int(L/4)+1 32-bit little-endian integers.
  • -
  • If L >= 254, the serialization contains byte 254, followed by 3 bytes with the string length L in little-endian order, followed by L bytes of the string, further followed by 0 to 3 null padding bytes.
  • -
-

All strings passed to the API must be encoded in UTF-8. When arbitrary byte sequences have to be serialized, bytes alias is to be used.

-

Further details on basic types»

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/channels.AdminLogResults b/data/core.telegram.org/type/channels.AdminLogResults deleted file mode 100644 index 27b366ed1f..0000000000 --- a/data/core.telegram.org/type/channels.AdminLogResults +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Channels.AdminLogResults - - - - - - - - - - - - - -
- -
-
-
- -

Channels.AdminLogResults

- -

Admin log events

-

- -
-
channels.adminLogResults#ed8af74d events:Vector<ChannelAdminLogEvent> chats:Vector<Chat> users:Vector<User> = channels.AdminLogResults;
-
----functions---
-
-channels.getAdminLog#33ddf480 flags:# channel:InputChannel q:string events_filter:flags.0?ChannelAdminLogEventsFilter admins:flags.1?Vector<InputUser> max_id:long min_id:long limit:int = channels.AdminLogResults;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
channels.adminLogResultsAdmin log events
-

Methods

- - - - - - - - - - - - - -
MethodDescription
channels.getAdminLogGet the admin log of a channel/supergroup
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/channels.ChannelParticipant b/data/core.telegram.org/type/channels.ChannelParticipant deleted file mode 100644 index d52b701832..0000000000 --- a/data/core.telegram.org/type/channels.ChannelParticipant +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Channels.ChannelParticipant - - - - - - - - - - - - - -
- -
-
-
- -

Channels.ChannelParticipant

- -

Channel participant

-

- -
-
channels.channelParticipant#dfb80317 participant:ChannelParticipant chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipant;
-
----functions---
-
-channels.getParticipant#a0ab6cc6 channel:InputChannel participant:InputPeer = channels.ChannelParticipant;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
channels.channelParticipantRepresents a channel participant
-

Methods

- - - - - - - - - - - - - -
MethodDescription
channels.getParticipantGet info about a channel/supergroup participant
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/channels.ChannelParticipants b/data/core.telegram.org/type/channels.ChannelParticipants deleted file mode 100644 index f740392bcc..0000000000 --- a/data/core.telegram.org/type/channels.ChannelParticipants +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Channels.ChannelParticipants - - - - - - - - - - - - - -
- -
-
-
- -

Channels.ChannelParticipants

- -

Channel/supergroup participants

-

- -
-
channels.channelParticipants#9ab0feaf count:int participants:Vector<ChannelParticipant> chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipants;
-channels.channelParticipantsNotModified#f0173fe9 = channels.ChannelParticipants;
-
----functions---
-
-channels.getParticipants#77ced9d0 channel:InputChannel filter:ChannelParticipantsFilter offset:int limit:int hash:long = channels.ChannelParticipants;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
channels.channelParticipantsRepresents multiple channel participants
channels.channelParticipantsNotModifiedNo new participant info could be found
-

Methods

- - - - - - - - - - - - - -
MethodDescription
channels.getParticipantsGet the participants of a channel
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/contacts.Blocked b/data/core.telegram.org/type/contacts.Blocked deleted file mode 100644 index 9ce9e6f2e9..0000000000 --- a/data/core.telegram.org/type/contacts.Blocked +++ /dev/null @@ -1,167 +0,0 @@ - - - - - contacts.Blocked - - - - - - - - - - - - - -
- -
-
-
- -

contacts.Blocked

- -

Info on users from the current user's black list.

-

- -
-
contacts.blocked#ade1591 blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
-contacts.blockedSlice#e1664194 count:int blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
-
----functions---
-
-contacts.getBlocked#f57c350f offset:int limit:int = contacts.Blocked;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
contacts.blockedFull list of blocked users.
contacts.blockedSliceIncomplete list of blocked users.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
contacts.getBlockedReturns the list of blocked users.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/contacts.Contacts b/data/core.telegram.org/type/contacts.Contacts deleted file mode 100644 index 11c346b49f..0000000000 --- a/data/core.telegram.org/type/contacts.Contacts +++ /dev/null @@ -1,167 +0,0 @@ - - - - - contacts.Contacts - - - - - - - - - - - - - -
- -
-
-
- -

contacts.Contacts

- -

Info on the current user's contact list.

-

- -
-
contacts.contactsNotModified#b74ba9d2 = contacts.Contacts;
-contacts.contacts#eae87e42 contacts:Vector<Contact> saved_count:int users:Vector<User> = contacts.Contacts;
-
----functions---
-
-contacts.getContacts#5dd69e12 hash:long = contacts.Contacts;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
contacts.contactsNotModifiedContact list on the server is the same as the list on the client.
contacts.contactsThe current user's contact list and info on users.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
contacts.getContactsReturns the current user's contact list.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/contacts.Found b/data/core.telegram.org/type/contacts.Found deleted file mode 100644 index a68139410f..0000000000 --- a/data/core.telegram.org/type/contacts.Found +++ /dev/null @@ -1,162 +0,0 @@ - - - - - contacts.Found - - - - - - - - - - - - - -
- -
-
-
- -

contacts.Found

- -

Object contains info on users found by name substring and auxiliary data.

-

- -
-
contacts.found#b3134d9d my_results:Vector<Peer> results:Vector<Peer> chats:Vector<Chat> users:Vector<User> = contacts.Found;
-
----functions---
-
-contacts.search#11f812d8 q:string limit:int = contacts.Found;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
contacts.foundUsers found by name substring and auxiliary data.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
contacts.searchReturns users found by username substring.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/contacts.ImportedContacts b/data/core.telegram.org/type/contacts.ImportedContacts deleted file mode 100644 index 12b11e5739..0000000000 --- a/data/core.telegram.org/type/contacts.ImportedContacts +++ /dev/null @@ -1,162 +0,0 @@ - - - - - contacts.ImportedContacts - - - - - - - - - - - - - -
- -
-
-
- -

contacts.ImportedContacts

- -

Object contains info on succesfully imported contacts.

-

- -
-
contacts.importedContacts#77d01c3b imported:Vector<ImportedContact> popular_invites:Vector<PopularContact> retry_contacts:Vector<long> users:Vector<User> = contacts.ImportedContacts;
-
----functions---
-
-contacts.importContacts#2c800be5 contacts:Vector<InputContact> = contacts.ImportedContacts;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
contacts.importedContactsInfo on succesfully imported contacts.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
contacts.importContactsImports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/contacts.Link b/data/core.telegram.org/type/contacts.Link deleted file mode 100644 index 48ca844de4..0000000000 --- a/data/core.telegram.org/type/contacts.Link +++ /dev/null @@ -1,128 +0,0 @@ - - - - - contacts.Link - - - - - - - - - - - - - -
- -
-
-
- -

contacts.Link

- -

Object describes the connection between a certain user and the current authorized user.

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/contacts.ResolvedPeer b/data/core.telegram.org/type/contacts.ResolvedPeer deleted file mode 100644 index bd6365796a..0000000000 --- a/data/core.telegram.org/type/contacts.ResolvedPeer +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Contacts.ResolvedPeer - - - - - - - - - - - - - -
- -
-
-
- -

Contacts.ResolvedPeer

- -

Peer returned after resolving a @username

-

- -
-
contacts.resolvedPeer#7f077ad9 peer:Peer chats:Vector<Chat> users:Vector<User> = contacts.ResolvedPeer;
-
----functions---
-
-contacts.resolveUsername#f93ccba3 username:string = contacts.ResolvedPeer;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
contacts.resolvedPeerResolved peer
-

Methods

- - - - - - - - - - - - - -
MethodDescription
contacts.resolveUsernameResolve a @username to get peer info
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/contacts.TopPeers b/data/core.telegram.org/type/contacts.TopPeers deleted file mode 100644 index cc6018dd40..0000000000 --- a/data/core.telegram.org/type/contacts.TopPeers +++ /dev/null @@ -1,172 +0,0 @@ - - - - - Contacts.TopPeers - - - - - - - - - - - - - -
- -
-
-
- -

Contacts.TopPeers

- -

Top peers

-

- -
-
contacts.topPeersNotModified#de266ef5 = contacts.TopPeers;
-contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;
-contacts.topPeersDisabled#b52c939d = contacts.TopPeers;
-
----functions---
-
-contacts.getTopPeers#973478b6 flags:# correspondents:flags.0?true bots_pm:flags.1?true bots_inline:flags.2?true phone_calls:flags.3?true forward_users:flags.4?true forward_chats:flags.5?true groups:flags.10?true channels:flags.15?true offset:int limit:int hash:long = contacts.TopPeers;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
contacts.topPeersNotModifiedTop peer info hasn't changed
contacts.topPeersTop peers
contacts.topPeersDisabledTop peers disabled
-

Methods

- - - - - - - - - - - - - -
MethodDescription
contacts.getTopPeersGet most used peers
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/double.html b/data/core.telegram.org/type/double.html deleted file mode 100644 index b1a3a9ae88..0000000000 --- a/data/core.telegram.org/type/double.html +++ /dev/null @@ -1,118 +0,0 @@ - - - - - double - - - - - - - - - - - - - -
- -
-
-
- -

double

- -

A basic bare type, values of which correspond two-element sequences containing 64-bit real numbers in a standard double format.

-

More on basic types»

-

Related pages

-

Binary Data Serialization

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/help.AppUpdate b/data/core.telegram.org/type/help.AppUpdate deleted file mode 100644 index 4c9a203e8d..0000000000 --- a/data/core.telegram.org/type/help.AppUpdate +++ /dev/null @@ -1,167 +0,0 @@ - - - - - help.AppUpdate - - - - - - - - - - - - - -
- -
-
-
- -

help.AppUpdate

- -

Contains info on app update availability.

-

- -
-
help.appUpdate#ccbbce30 flags:# can_not_skip:flags.0?true id:int version:string text:string entities:Vector<MessageEntity> document:flags.1?Document url:flags.2?string sticker:flags.3?Document = help.AppUpdate;
-help.noAppUpdate#c45a6536 = help.AppUpdate;
-
----functions---
-
-help.getAppUpdate#522d5a7d source:string = help.AppUpdate;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
help.appUpdateAn update is available for the application.
help.noAppUpdateNo updates are available for the application.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getAppUpdateReturns information on update availability for the current application.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/help.CountriesList b/data/core.telegram.org/type/help.CountriesList deleted file mode 100644 index 00d0dee1cc..0000000000 --- a/data/core.telegram.org/type/help.CountriesList +++ /dev/null @@ -1,167 +0,0 @@ - - - - - help.CountriesList - - - - - - - - - - - - - -
- -
-
-
- -

help.CountriesList

- -

Name, ISO code, localized name and phone codes/patterns of all available countries

-

- -
-
help.countriesListNotModified#93cc1f32 = help.CountriesList;
-help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;
-
----functions---
-
-help.getCountriesList#735787a8 lang_code:string hash:int = help.CountriesList;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
help.countriesListNotModifiedThe country list has not changed
help.countriesListName, ISO code, localized name and phone codes/patterns of all available countries
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getCountriesListGet name, ISO code, localized name and phone codes/patterns of all available countries
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/help.CountryCode b/data/core.telegram.org/type/help.CountryCode deleted file mode 100644 index 1307f9054a..0000000000 --- a/data/core.telegram.org/type/help.CountryCode +++ /dev/null @@ -1,143 +0,0 @@ - - - - - help.CountryCode - - - - - - - - - - - - - -
- -
-
-
- -

help.CountryCode

- -

Country code and phone number pattern of a specific country

-

- -
-
help.countryCode#4203c5ef flags:# country_code:string prefixes:flags.0?Vector<string> patterns:flags.1?Vector<string> = help.CountryCode;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
help.countryCodeCountry code and phone number pattern of a specific country
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/help.PassportConfig b/data/core.telegram.org/type/help.PassportConfig deleted file mode 100644 index c553d378fb..0000000000 --- a/data/core.telegram.org/type/help.PassportConfig +++ /dev/null @@ -1,169 +0,0 @@ - - - - - Help.PassportConfig - - - - - - - - - - - - - -
- -
-
-
- -

Help.PassportConfig

- -

Telegram passport configuration

-

- -
-
help.passportConfigNotModified#bfb9f457 = help.PassportConfig;
-help.passportConfig#a098d6af hash:int countries_langs:DataJSON = help.PassportConfig;
-
----functions---
-
-help.getPassportConfig#c661ad08 hash:int = help.PassportConfig;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
help.passportConfigNotModifiedPassword configuration not modified
help.passportConfigTelegram passport configuration
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getPassportConfigGet passport configuration
-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/help.PromoData b/data/core.telegram.org/type/help.PromoData deleted file mode 100644 index 2b20632203..0000000000 --- a/data/core.telegram.org/type/help.PromoData +++ /dev/null @@ -1,167 +0,0 @@ - - - - - help.PromoData - - - - - - - - - - - - - -
- -
-
-
- -

help.PromoData

- -

Info about pinned MTProxy or Public Service Announcement peers.

-

- -
-
help.promoDataEmpty#98f6ac75 expires:int = help.PromoData;
-help.promoData#8c39793f flags:# proxy:flags.0?true expires:int peer:Peer chats:Vector<Chat> users:Vector<User> psa_type:flags.1?string psa_message:flags.2?string = help.PromoData;
-
----functions---
-
-help.getPromoData#c0977421 = help.PromoData;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
help.promoDataEmptyNo PSA/MTProxy info is available
help.promoDataMTProxy/Public Service Announcement information
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getPromoDataGet MTProxy/Public Service Announcement information
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/help.ProxyData b/data/core.telegram.org/type/help.ProxyData deleted file mode 100644 index aa1148fcf4..0000000000 --- a/data/core.telegram.org/type/help.ProxyData +++ /dev/null @@ -1,130 +0,0 @@ - - - - - Help.ProxyData - - - - - - - - - - - - - -
- -
-
-
- -

Help.ProxyData

- -

Info about an MTProxy

-

- -
-

-

Related pages

-

MTProto transports

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/help.Support b/data/core.telegram.org/type/help.Support deleted file mode 100644 index 9bf3bd3706..0000000000 --- a/data/core.telegram.org/type/help.Support +++ /dev/null @@ -1,162 +0,0 @@ - - - - - help.Support - - - - - - - - - - - - - -
- -
-
-
- -

help.Support

- -

Info about the support user, relevant to the current user.

-

- -
-
help.support#17c6b5f6 phone_number:string user:User = help.Support;
-
----functions---
-
-help.getSupport#9cdf08cd = help.Support;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
help.supportInfo on support user.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getSupportReturns the support user for the 'ask a question' feature.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/help.SupportName b/data/core.telegram.org/type/help.SupportName deleted file mode 100644 index 9dc768c76a..0000000000 --- a/data/core.telegram.org/type/help.SupportName +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Help.SupportName - - - - - - - - - - - - - -
- -
-
-
- -

Help.SupportName

- -

Get localized name for support user

-

- -
-
help.supportName#8c05f1c9 name:string = help.SupportName;
-
----functions---
-
-help.getSupportName#d360e72c = help.SupportName;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
help.supportNameLocalized name for telegram support
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getSupportNameGet localized name of the telegram support user
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/help.TermsOfService b/data/core.telegram.org/type/help.TermsOfService deleted file mode 100644 index 8d4d3ac168..0000000000 --- a/data/core.telegram.org/type/help.TermsOfService +++ /dev/null @@ -1,143 +0,0 @@ - - - - - help.TermsOfService - - - - - - - - - - - - - -
- -
-
-
- -

help.TermsOfService

- -

Contains info about the latest telegram Terms Of Service.

-

- -
-
help.termsOfService#780a0310 flags:# popup:flags.0?true id:DataJSON text:string entities:Vector<MessageEntity> min_age_confirm:flags.1?int = help.TermsOfService;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
help.termsOfServiceInfo about the latest telegram Terms Of Service
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/help.TermsOfServiceUpdate b/data/core.telegram.org/type/help.TermsOfServiceUpdate deleted file mode 100644 index 77e24f1d4d..0000000000 --- a/data/core.telegram.org/type/help.TermsOfServiceUpdate +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Help.TermsOfServiceUpdate - - - - - - - - - - - - - -
- -
-
-
- -

Help.TermsOfServiceUpdate

- -

Update of Telegram's terms of service

-

- -
-
help.termsOfServiceUpdateEmpty#e3309f7f expires:int = help.TermsOfServiceUpdate;
-help.termsOfServiceUpdate#28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate;
-
----functions---
-
-help.getTermsOfServiceUpdate#2ca51fd1 = help.TermsOfServiceUpdate;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
help.termsOfServiceUpdateEmptyNo changes were made to telegram's terms of service
help.termsOfServiceUpdateInfo about an update of telegram's terms of service. If the terms of service are declined, then the account.deleteAccount method should be called with the reason "Decline ToS update"
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getTermsOfServiceUpdateLook for updates of telegram's terms of service
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/help.UserInfo b/data/core.telegram.org/type/help.UserInfo deleted file mode 100644 index 3e21ed83d3..0000000000 --- a/data/core.telegram.org/type/help.UserInfo +++ /dev/null @@ -1,172 +0,0 @@ - - - - - Help.UserInfo - - - - - - - - - - - - - -
- -
-
-
- -

Help.UserInfo

- -

User info

-

- -
-
help.userInfoEmpty#f3ae2eed = help.UserInfo;
-help.userInfo#1eb3758 message:string entities:Vector<MessageEntity> author:string date:int = help.UserInfo;
-
----functions---
-
-help.getUserInfo#38a08d3 user_id:InputUser = help.UserInfo;
-help.editUserInfo#66b91b70 user_id:InputUser message:string entities:Vector<MessageEntity> = help.UserInfo;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
help.userInfoEmptyInternal use
help.userInfoInternal use
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
help.getUserInfoInternal use
help.editUserInfoInternal use
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/int.html b/data/core.telegram.org/type/int.html deleted file mode 100644 index e80540da18..0000000000 --- a/data/core.telegram.org/type/int.html +++ /dev/null @@ -1,118 +0,0 @@ - - - - - int - - - - - - - - - - - - - -
- -
-
-
- -

int

- -

A basic bare type, the values of which correspond to single-element sequences, i.e. numbers from -2^31 to 2^31-1 which in this case represent themselves.

-

More on basic types »

-

Related pages

-

Binary Data Serialization

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.AffectedFoundMessages b/data/core.telegram.org/type/messages.AffectedFoundMessages deleted file mode 100644 index 9e8a731077..0000000000 --- a/data/core.telegram.org/type/messages.AffectedFoundMessages +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.AffectedFoundMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.AffectedFoundMessages

- -

Messages found and affected by changes

-

- -
-
messages.affectedFoundMessages#ef8d3e6c pts:int pts_count:int offset:int messages:Vector<int> = messages.AffectedFoundMessages;
-
----functions---
-
-messages.deletePhoneCallHistory#f9cbe409 flags:# revoke:flags.0?true = messages.AffectedFoundMessages;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.affectedFoundMessagesMessages found and affected by changes
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.deletePhoneCallHistoryDelete the phone call history with a user
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.AffectedHistory b/data/core.telegram.org/type/messages.AffectedHistory deleted file mode 100644 index e1f95a5960..0000000000 --- a/data/core.telegram.org/type/messages.AffectedHistory +++ /dev/null @@ -1,178 +0,0 @@ - - - - - messages.AffectedHistory - - - - - - - - - - - - - -
- -
-
-
- -

messages.AffectedHistory

- -

Object contains info on affected part of communication history with the user or in a chat.

-

- -
-
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
-
----functions---
-
-messages.deleteHistory#1c015b09 flags:# just_clear:flags.0?true revoke:flags.1?true peer:InputPeer max_id:int = messages.AffectedHistory;
-messages.readMentions#f0189d3 peer:InputPeer = messages.AffectedHistory;
-messages.unpinAllMessages#f025bc8b peer:InputPeer = messages.AffectedHistory;
-
-channels.deleteUserHistory#d10dd71b channel:InputChannel user_id:InputUser = messages.AffectedHistory;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.affectedHistoryAffected part of communication history with the user or in a chat.
-

Methods

- - - - - - - - - - - - - - - - - - - - - - - - - -
MethodDescription
messages.deleteHistoryDeletes communication history.
channels.deleteUserHistoryDelete all messages sent by a certain user in a supergroup
messages.readMentionsMark mentions as read
messages.unpinAllMessagesUnpin all pinned messages
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.AffectedMessages b/data/core.telegram.org/type/messages.AffectedMessages deleted file mode 100644 index d5a4cd5b2c..0000000000 --- a/data/core.telegram.org/type/messages.AffectedMessages +++ /dev/null @@ -1,178 +0,0 @@ - - - - - Messages.AffectedMessages - - - - - - - - - - - - - -
- -
-
-
- -

Messages.AffectedMessages

- -

Messages affected by changes

-

- -
-
messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;
-
----functions---
-
-messages.readHistory#e306d3a peer:InputPeer max_id:int = messages.AffectedMessages;
-messages.deleteMessages#e58e95d2 flags:# revoke:flags.0?true id:Vector<int> = messages.AffectedMessages;
-messages.readMessageContents#36a73f77 id:Vector<int> = messages.AffectedMessages;
-
-channels.deleteMessages#84c1fd4e channel:InputChannel id:Vector<int> = messages.AffectedMessages;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.affectedMessagesEvents affected by operation
-

Methods

- - - - - - - - - - - - - - - - - - - - - - - - - -
MethodDescription
messages.readHistoryMarks message history as read.
messages.deleteMessagesDeletes messages by their identifiers.
messages.readMessageContentsNotifies the sender about the recipient having listened a voice message or watched a video.
channels.deleteMessagesDelete messages in a channel/supergroup
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.AllStickers b/data/core.telegram.org/type/messages.AllStickers deleted file mode 100644 index 6571f62fe4..0000000000 --- a/data/core.telegram.org/type/messages.AllStickers +++ /dev/null @@ -1,172 +0,0 @@ - - - - - Messages.AllStickers - - - - - - - - - - - - - -
- -
-
-
- -

Messages.AllStickers

- -

All stickers

-

- -
-
messages.allStickersNotModified#e86602c3 = messages.AllStickers;
-messages.allStickers#cdbbcebb hash:long sets:Vector<StickerSet> = messages.AllStickers;
-
----functions---
-
-messages.getAllStickers#b8a0a1a8 hash:long = messages.AllStickers;
-messages.getMaskStickers#640f82b8 hash:long = messages.AllStickers;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.allStickersNotModifiedInfo about all installed stickers hasn't changed
messages.allStickersInfo about all installed stickers
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
messages.getAllStickersGet all installed stickers
messages.getMaskStickersGet installed mask stickers
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.ArchivedStickers b/data/core.telegram.org/type/messages.ArchivedStickers deleted file mode 100644 index 573b9cb6cb..0000000000 --- a/data/core.telegram.org/type/messages.ArchivedStickers +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Messages.ArchivedStickers - - - - - - - - - - - - - -
- -
-
-
- -

Messages.ArchivedStickers

- -

Archived stickers

-

- -
-
messages.archivedStickers#4fcba9c8 count:int sets:Vector<StickerSetCovered> = messages.ArchivedStickers;
-
----functions---
-
-messages.getArchivedStickers#57f17692 flags:# masks:flags.0?true offset_id:long limit:int = messages.ArchivedStickers;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.archivedStickersArchived stickersets
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getArchivedStickersGet all archived stickers
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.BotCallbackAnswer b/data/core.telegram.org/type/messages.BotCallbackAnswer deleted file mode 100644 index bd5f776ff5..0000000000 --- a/data/core.telegram.org/type/messages.BotCallbackAnswer +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Messages.BotCallbackAnswer - - - - - - - - - - - - - -
- -
-
-
- -

Messages.BotCallbackAnswer

- -

Callback answer of bot

-

- -
-
messages.botCallbackAnswer#36585ea4 flags:# alert:flags.1?true has_url:flags.3?true native_ui:flags.4?true message:flags.0?string url:flags.2?string cache_time:int = messages.BotCallbackAnswer;
-
----functions---
-
-messages.getBotCallbackAnswer#9342ca07 flags:# game:flags.1?true peer:InputPeer msg_id:int data:flags.0?bytes password:flags.2?InputCheckPasswordSRP = messages.BotCallbackAnswer;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.botCallbackAnswerCallback answer sent by the bot in response to a button press
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getBotCallbackAnswerPress an inline callback button and get a callback answer from the bot
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.BotResults b/data/core.telegram.org/type/messages.BotResults deleted file mode 100644 index 3d8d43a6e4..0000000000 --- a/data/core.telegram.org/type/messages.BotResults +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.BotResults - - - - - - - - - - - - - -
- -
-
-
- -

messages.BotResults

- -

Result of a query to an inline bot

-

- -
-
messages.botResults#947ca848 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;
-
----functions---
-
-messages.getInlineBotResults#514e999d flags:# bot:InputUser peer:InputPeer geo_point:flags.0?InputGeoPoint query:string offset:string = messages.BotResults;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.botResultsResult of a query to an inline bot
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getInlineBotResultsQuery an inline bot
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.ChatFull b/data/core.telegram.org/type/messages.ChatFull deleted file mode 100644 index 497bad2b59..0000000000 --- a/data/core.telegram.org/type/messages.ChatFull +++ /dev/null @@ -1,168 +0,0 @@ - - - - - messages.ChatFull - - - - - - - - - - - - - -
- -
-
-
- -

messages.ChatFull

- -

Object contains extended info on chat with auxiliary data.

-

- -
-
messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.ChatFull;
-
----functions---
-
-messages.getFullChat#aeb00b34 chat_id:long = messages.ChatFull;
-
-channels.getFullChannel#8736a09 channel:InputChannel = messages.ChatFull;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.chatFullExtended info on chat and auxiliary data.
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
messages.getFullChatReturns full chat info according to its ID.
channels.getFullChannelGet full info about a channel
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.ChatInviteImporters b/data/core.telegram.org/type/messages.ChatInviteImporters deleted file mode 100644 index da87a3270d..0000000000 --- a/data/core.telegram.org/type/messages.ChatInviteImporters +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.ChatInviteImporters - - - - - - - - - - - - - -
- -
-
-
- -

messages.ChatInviteImporters

- -

List of users that imported a chat invitation link.

-

- -
-
messages.chatInviteImporters#81b6b00a count:int importers:Vector<ChatInviteImporter> users:Vector<User> = messages.ChatInviteImporters;
-
----functions---
-
-messages.getChatInviteImporters#26fb7289 peer:InputPeer link:string offset_date:int offset_user:InputUser limit:int = messages.ChatInviteImporters;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.chatInviteImportersInfo about the users that joined the chat using a specific chat invite
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getChatInviteImportersGet info about the users that joined the chat using a specific chat invite
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.Chats b/data/core.telegram.org/type/messages.Chats deleted file mode 100644 index 89288e129c..0000000000 --- a/data/core.telegram.org/type/messages.Chats +++ /dev/null @@ -1,198 +0,0 @@ - - - - - messages.Chats - - - - - - - - - - - - - -
- -
-
-
- -

messages.Chats

- -

Object contains list of chats with auxiliary data.

-

- -
-
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
-messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
-
----functions---
-
-messages.getChats#49e9528f id:Vector<long> = messages.Chats;
-messages.getCommonChats#e40ca104 user_id:InputUser max_id:long limit:int = messages.Chats;
-messages.getAllChats#875f74be except_ids:Vector<long> = messages.Chats;
-
-channels.getChannels#a7f6bbb id:Vector<InputChannel> = messages.Chats;
-channels.getAdminedPublicChannels#f8b036af flags:# by_location:flags.0?true check_limit:flags.1?true = messages.Chats;
-channels.getLeftChannels#8341ecc0 offset:int = messages.Chats;
-channels.getGroupsForDiscussion#f5dad378 = messages.Chats;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.chatsList of chats with auxiliary data.
messages.chatsSlicePartial list of chats, more would have to be fetched with pagination
-

Methods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
MethodDescription
messages.getChatsReturns chat basic info on their IDs.
channels.getChannelsGet info about channels/supergroups
channels.getAdminedPublicChannelsGet channels/supergroups/geogroups we're admin in. Usually called when the user exceeds the limit for owned public channels/supergroups/geogroups, and the user is given the choice to remove one of his channels/supergroups/geogroups.
messages.getCommonChatsGet chats in common with a user
messages.getAllChatsGet all chats, channels and supergroups
channels.getLeftChannelsGet a list of channels/supergroups we left
channels.getGroupsForDiscussionGet all groups that can be used as discussion groups
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.CheckedHistoryImportPeer b/data/core.telegram.org/type/messages.CheckedHistoryImportPeer deleted file mode 100644 index 0996418f17..0000000000 --- a/data/core.telegram.org/type/messages.CheckedHistoryImportPeer +++ /dev/null @@ -1,165 +0,0 @@ - - - - - messages.CheckedHistoryImportPeer - - - - - - - - - - - - - -
- -
-
-
- -

messages.CheckedHistoryImportPeer

- -

Contains a confirmation text to be shown to the user, upon importing chat history, click here for more info ».

-

- -
-
messages.checkedHistoryImportPeer#a24de717 confirm_text:string = messages.CheckedHistoryImportPeer;
-
----functions---
-
-messages.checkHistoryImportPeer#5dc60f03 peer:InputPeer = messages.CheckedHistoryImportPeer;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.checkedHistoryImportPeerContains a confirmation text to be shown to the user, upon importing chat history.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.checkHistoryImportPeerCheck whether chat history exported from another chat app can be imported into a specific Telegram chat.

If the check succeeds, and no RPC errors are returned, a messages.CheckedHistoryImportPeer constructor will be returned, with a confirmation text to be shown to the user, before actually initializing the import.
-

Related pages

-

Imported messages

-

Telegram allows importing messages and media from foreign chat apps.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.DhConfig b/data/core.telegram.org/type/messages.DhConfig deleted file mode 100644 index 83405aa313..0000000000 --- a/data/core.telegram.org/type/messages.DhConfig +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Messages.DhConfig - - - - - - - - - - - - - -
- -
-
-
- -

Messages.DhConfig

- -

Contains info on cofiguring parameters for key generation by Diffie-Hellman protocol.

-

- -
-
messages.dhConfigNotModified#c0e24635 random:bytes = messages.DhConfig;
-messages.dhConfig#2c221edd g:int p:bytes version:int random:bytes = messages.DhConfig;
-
----functions---
-
-messages.getDhConfig#26cf8950 version:int random_length:int = messages.DhConfig;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.dhConfigNotModifiedConfiguring parameters did not change.
messages.dhConfigNew set of configuring parameters.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getDhConfigReturns configuration parameters for Diffie-Hellman key generation. Can also return a random sequence of bytes of required length.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.Dialogs b/data/core.telegram.org/type/messages.Dialogs deleted file mode 100644 index 6532ae3ba4..0000000000 --- a/data/core.telegram.org/type/messages.Dialogs +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.Dialogs - - - - - - - - - - - - - -
- -
-
-
- -

messages.Dialogs

- -

Object contains a list of chats with messages and auxiliary data.

-

- -
-
messages.dialogs#15ba6c40 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;
-messages.dialogsSlice#71e094f3 count:int dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;
-messages.dialogsNotModified#f0e3e596 count:int = messages.Dialogs;
-
----functions---
-
-messages.getDialogs#a0f4cb4f flags:# exclude_pinned:flags.0?true folder_id:flags.1?int offset_date:int offset_id:int offset_peer:InputPeer limit:int hash:long = messages.Dialogs;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.dialogsFull list of chats with messages and auxiliary data.
messages.dialogsSliceIncomplete list of dialogs with messages and auxiliary data.
messages.dialogsNotModifiedDialogs haven't changed
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getDialogsReturns the current user dialog list.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.DiscussionMessage b/data/core.telegram.org/type/messages.DiscussionMessage deleted file mode 100644 index bbd699a196..0000000000 --- a/data/core.telegram.org/type/messages.DiscussionMessage +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.DiscussionMessage - - - - - - - - - - - - - -
- -
-
-
- -

messages.DiscussionMessage

- -

Info about a message thread

-

- -
-
messages.discussionMessage#a6341782 flags:# messages:Vector<Message> max_id:flags.0?int read_inbox_max_id:flags.1?int read_outbox_max_id:flags.2?int unread_count:int chats:Vector<Chat> users:Vector<User> = messages.DiscussionMessage;
-
----functions---
-
-messages.getDiscussionMessage#446972fd peer:InputPeer msg_id:int = messages.DiscussionMessage;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.discussionMessageInformation about a message thread
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getDiscussionMessageGet discussion message from the associated discussion group of a channel to show it on top of the comment section, without actually joining the group
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.ExportedChatInvite b/data/core.telegram.org/type/messages.ExportedChatInvite deleted file mode 100644 index 998e30f4f6..0000000000 --- a/data/core.telegram.org/type/messages.ExportedChatInvite +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.ExportedChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

messages.ExportedChatInvite

- -

Contains info about a chat invite, and eventually a pointer to the newest chat invite.

-

- -
-
messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
-messages.exportedChatInviteReplaced#222600ef invite:ExportedChatInvite new_invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
-
----functions---
-
-messages.getExportedChatInvite#73746f5c peer:InputPeer link:string = messages.ExportedChatInvite;
-messages.editExportedChatInvite#2e4ffbe flags:# revoked:flags.2?true peer:InputPeer link:string expire_date:flags.0?int usage_limit:flags.1?int = messages.ExportedChatInvite;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.exportedChatInviteInfo about a chat invite
messages.exportedChatInviteReplacedThe specified chat invite was replaced with another one
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
messages.getExportedChatInviteGet info about a chat invite
messages.editExportedChatInviteEdit an exported chat invite
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.ExportedChatInvites b/data/core.telegram.org/type/messages.ExportedChatInvites deleted file mode 100644 index 0b10b1e633..0000000000 --- a/data/core.telegram.org/type/messages.ExportedChatInvites +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.ExportedChatInvites - - - - - - - - - - - - - -
- -
-
-
- -

messages.ExportedChatInvites

- -

Info about chat invites exported by a certain admin.

-

- -
-
messages.exportedChatInvites#bdc62dcc count:int invites:Vector<ExportedChatInvite> users:Vector<User> = messages.ExportedChatInvites;
-
----functions---
-
-messages.getExportedChatInvites#a2b5a3f6 flags:# revoked:flags.3?true peer:InputPeer admin_id:InputUser offset_date:flags.2?int offset_link:flags.2?string limit:int = messages.ExportedChatInvites;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.exportedChatInvitesInfo about chat invites exported by a certain admin.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getExportedChatInvitesGet info about the chat invites of a specific chat
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.FavedStickers b/data/core.telegram.org/type/messages.FavedStickers deleted file mode 100644 index e76cb717e7..0000000000 --- a/data/core.telegram.org/type/messages.FavedStickers +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Messages.FavedStickers - - - - - - - - - - - - - -
- -
-
-
- -

Messages.FavedStickers

- -

Favorited stickers

-

- -
-
messages.favedStickersNotModified#9e8fa6d3 = messages.FavedStickers;
-messages.favedStickers#2cb51097 hash:long packs:Vector<StickerPack> stickers:Vector<Document> = messages.FavedStickers;
-
----functions---
-
-messages.getFavedStickers#4f1aaa9 hash:long = messages.FavedStickers;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.favedStickersNotModifiedNo new favorited stickers were found
messages.favedStickersFavorited stickers
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getFavedStickersGet faved stickers
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.FeaturedStickers b/data/core.telegram.org/type/messages.FeaturedStickers deleted file mode 100644 index 60b6c4c0f3..0000000000 --- a/data/core.telegram.org/type/messages.FeaturedStickers +++ /dev/null @@ -1,172 +0,0 @@ - - - - - Messages.FeaturedStickers - - - - - - - - - - - - - -
- -
-
-
- -

Messages.FeaturedStickers

- -

Featured stickers

-

- -
-
messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;
-messages.featuredStickers#84c02310 hash:long count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;
-
----functions---
-
-messages.getFeaturedStickers#64780b14 hash:long = messages.FeaturedStickers;
-messages.getOldFeaturedStickers#7ed094a1 offset:int limit:int hash:long = messages.FeaturedStickers;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.featuredStickersNotModifiedFeatured stickers haven't changed
messages.featuredStickersFeatured stickersets
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
messages.getFeaturedStickersGet featured stickers
messages.getOldFeaturedStickersOld method for fetching featured sticker
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.FoundGifs b/data/core.telegram.org/type/messages.FoundGifs deleted file mode 100644 index 01f4ddc619..0000000000 --- a/data/core.telegram.org/type/messages.FoundGifs +++ /dev/null @@ -1,128 +0,0 @@ - - - - - Messages.FoundGifs - - - - - - - - - - - - - -
- -
-
-
- -

Messages.FoundGifs

- -

Found GIFs

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.FoundStickerSets b/data/core.telegram.org/type/messages.FoundStickerSets deleted file mode 100644 index a04e8a7921..0000000000 --- a/data/core.telegram.org/type/messages.FoundStickerSets +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Messages.FoundStickerSets - - - - - - - - - - - - - -
- -
-
-
- -

Messages.FoundStickerSets

- -

Found stickersets

-

- -
-
messages.foundStickerSetsNotModified#d54b65d = messages.FoundStickerSets;
-messages.foundStickerSets#8af09dd2 hash:long sets:Vector<StickerSetCovered> = messages.FoundStickerSets;
-
----functions---
-
-messages.searchStickerSets#35705b8a flags:# exclude_featured:flags.0?true q:string hash:long = messages.FoundStickerSets;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.foundStickerSetsNotModifiedNo further results were found
messages.foundStickerSetsFound stickersets
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.searchStickerSetsSearch for stickersets
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.HighScores b/data/core.telegram.org/type/messages.HighScores deleted file mode 100644 index c950349984..0000000000 --- a/data/core.telegram.org/type/messages.HighScores +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Messages.HighScores - - - - - - - - - - - - - -
- -
-
-
- -

Messages.HighScores

- -

High scores (in games)

-

- -
-
messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;
-
----functions---
-
-messages.getGameHighScores#e822649d peer:InputPeer id:int user_id:InputUser = messages.HighScores;
-messages.getInlineGameHighScores#f635e1b id:InputBotInlineMessageID user_id:InputUser = messages.HighScores;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.highScoresHighscores in a game
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
messages.getGameHighScoresGet highscores of a game
messages.getInlineGameHighScoresGet highscores of a game sent using an inline bot
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.HistoryImport b/data/core.telegram.org/type/messages.HistoryImport deleted file mode 100644 index c1bde8eef5..0000000000 --- a/data/core.telegram.org/type/messages.HistoryImport +++ /dev/null @@ -1,165 +0,0 @@ - - - - - messages.HistoryImport - - - - - - - - - - - - - -
- -
-
-
- -

messages.HistoryImport

- -

Identifier of a history import session, click here for more info ».

-

- -
-
messages.historyImport#1662af0b id:long = messages.HistoryImport;
-
----functions---
-
-messages.initHistoryImport#34090c3b peer:InputPeer file:InputFile media_count:int = messages.HistoryImport;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.historyImportID of a specific chat import session
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.initHistoryImportImport chat history from a foreign chat app into a specific Telegram chat.
Make sure to call messages.checkHistoryImportPeer, first, to make sure you have the rights to import history into this chat, and to show an additional confirmation prompt to the user with useful information returned by the RPC call.
Typically, history imports are allowed for private chats with a mutual contact or supergroups with change_info administrator rights ».

After initializing the history import process and uploading all media files associated with the chat using messages.uploadImportedMedia, call messages.startHistoryImport to complete the history import process, importing all messages into the chat.
-

Related pages

-

Imported messages

-

Telegram allows importing messages and media from foreign chat apps.

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.HistoryImportParsed b/data/core.telegram.org/type/messages.HistoryImportParsed deleted file mode 100644 index ee4a11bc8d..0000000000 --- a/data/core.telegram.org/type/messages.HistoryImportParsed +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.HistoryImportParsed - - - - - - - - - - - - - -
- -
-
-
- -

messages.HistoryImportParsed

- -

Contains information about a chat export file, generated by a foreign chat app.

-

- -
-
messages.historyImportParsed#5e0fb7b9 flags:# pm:flags.0?true group:flags.1?true title:flags.2?string = messages.HistoryImportParsed;
-
----functions---
-
-messages.checkHistoryImport#43fe19f3 import_head:string = messages.HistoryImportParsed;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.historyImportParsedContains information about a chat export file, generated by a foreign chat app. If neither the pm or group flags are set, the specified chat export was generated from a chat of unknown type.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.checkHistoryImportObtains information about a chat export file, generated by a foreign chat app.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.MessageEditData b/data/core.telegram.org/type/messages.MessageEditData deleted file mode 100644 index 8ba8a76e4a..0000000000 --- a/data/core.telegram.org/type/messages.MessageEditData +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Messages.MessageEditData - - - - - - - - - - - - - -
- -
-
-
- -

Messages.MessageEditData

- -

Message edit data for media

-

- -
-
messages.messageEditData#26b5dde6 flags:# caption:flags.0?true = messages.MessageEditData;
-
----functions---
-
-messages.getMessageEditData#fda68d36 peer:InputPeer id:int = messages.MessageEditData;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.messageEditDataMessage edit data for media
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getMessageEditDataFind out if a media message's caption can be edited
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.MessageViews b/data/core.telegram.org/type/messages.MessageViews deleted file mode 100644 index 4dd41b1614..0000000000 --- a/data/core.telegram.org/type/messages.MessageViews +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.MessageViews - - - - - - - - - - - - - -
- -
-
-
- -

messages.MessageViews

- -

View, forward counter + info about replies

-

- -
-
messages.messageViews#b6c4f543 views:Vector<MessageViews> chats:Vector<Chat> users:Vector<User> = messages.MessageViews;
-
----functions---
-
-messages.getMessagesViews#5784d3e1 peer:InputPeer id:Vector<int> increment:Bool = messages.MessageViews;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.messageViewsView, forward counter + info about replies
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getMessagesViewsGet and increase the view counter of a message sent or forwarded from a channel
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.PeerDialogs b/data/core.telegram.org/type/messages.PeerDialogs deleted file mode 100644 index b4eb333f5b..0000000000 --- a/data/core.telegram.org/type/messages.PeerDialogs +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Messages.PeerDialogs - - - - - - - - - - - - - -
- -
-
-
- -

Messages.PeerDialogs

- -

List of dialogs

-

- -
-
messages.peerDialogs#3371c354 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> state:updates.State = messages.PeerDialogs;
-
----functions---
-
-messages.getPeerDialogs#e470bcfd peers:Vector<InputDialogPeer> = messages.PeerDialogs;
-messages.getPinnedDialogs#d6b94df2 folder_id:int = messages.PeerDialogs;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.peerDialogsDialog info of multiple peers
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
messages.getPeerDialogsGet dialog info of specified peers
messages.getPinnedDialogsGet pinned dialogs
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.RecentStickers b/data/core.telegram.org/type/messages.RecentStickers deleted file mode 100644 index d5a5435b1b..0000000000 --- a/data/core.telegram.org/type/messages.RecentStickers +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Messages.RecentStickers - - - - - - - - - - - - - -
- -
-
-
- -

Messages.RecentStickers

- -

Recent stickers

-

- -
-
messages.recentStickersNotModified#b17f890 = messages.RecentStickers;
-messages.recentStickers#88d37c56 hash:long packs:Vector<StickerPack> stickers:Vector<Document> dates:Vector<int> = messages.RecentStickers;
-
----functions---
-
-messages.getRecentStickers#9da9403b flags:# attached:flags.0?true hash:long = messages.RecentStickers;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.recentStickersNotModifiedNo new recent sticker was found
messages.recentStickersRecently used stickers
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getRecentStickersGet recent stickers
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.SavedGifs b/data/core.telegram.org/type/messages.SavedGifs deleted file mode 100644 index 6ed1af0ac6..0000000000 --- a/data/core.telegram.org/type/messages.SavedGifs +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Messages.SavedGifs - - - - - - - - - - - - - -
- -
-
-
- -

Messages.SavedGifs

- -

Saved GIFs

-

- -
-
messages.savedGifsNotModified#e8025ca2 = messages.SavedGifs;
-messages.savedGifs#84a02a0d hash:long gifs:Vector<Document> = messages.SavedGifs;
-
----functions---
-
-messages.getSavedGifs#5cf09635 hash:long = messages.SavedGifs;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.savedGifsNotModifiedNo new saved gifs were found
messages.savedGifsSaved gifs
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getSavedGifsGet saved GIFs
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.SearchCounter b/data/core.telegram.org/type/messages.SearchCounter deleted file mode 100644 index 61cfea4766..0000000000 --- a/data/core.telegram.org/type/messages.SearchCounter +++ /dev/null @@ -1,143 +0,0 @@ - - - - - Messages.SearchCounter - - - - - - - - - - - - - -
- -
-
-
- -

Messages.SearchCounter

- -

Number of results that would be returned by a search

-

- -
-
messages.searchCounter#e844ebff flags:# inexact:flags.1?true filter:MessagesFilter count:int = messages.SearchCounter;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.searchCounterIndicates how many results would be found by a messages.search call with the same parameters
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.SentEncryptedMessage b/data/core.telegram.org/type/messages.SentEncryptedMessage deleted file mode 100644 index dfd39de2f3..0000000000 --- a/data/core.telegram.org/type/messages.SentEncryptedMessage +++ /dev/null @@ -1,177 +0,0 @@ - - - - - Messages.SentEncryptedMessage - - - - - - - - - - - - - -
- -
-
-
- -

Messages.SentEncryptedMessage

- -

Contains info on message sent to an encrypted chat.

-

- -
-
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;
-messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;
-
----functions---
-
-messages.sendEncrypted#44fa7a15 flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;
-messages.sendEncryptedFile#5559481d flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes file:InputEncryptedFile = messages.SentEncryptedMessage;
-messages.sendEncryptedService#32d439a4 peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.sentEncryptedMessageMessage without file attachemts sent to an encrypted file.
messages.sentEncryptedFileMessage with a file enclosure sent to a protected chat
-

Methods

- - - - - - - - - - - - - - - - - - - - - -
MethodDescription
messages.sendEncryptedSends a text message to a secret chat.
messages.sendEncryptedFileSends a message with a file attachment to a secret chat
messages.sendEncryptedServiceSends a service message to a secret chat.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.SentMessage b/data/core.telegram.org/type/messages.SentMessage deleted file mode 100644 index 485855df94..0000000000 --- a/data/core.telegram.org/type/messages.SentMessage +++ /dev/null @@ -1,128 +0,0 @@ - - - - - messages.SentMessage - - - - - - - - - - - - - -
- -
-
-
- -

messages.SentMessage

- -

Info on a successfully sent message.

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.SponsoredMessages b/data/core.telegram.org/type/messages.SponsoredMessages deleted file mode 100644 index f4ee16bf07..0000000000 --- a/data/core.telegram.org/type/messages.SponsoredMessages +++ /dev/null @@ -1,166 +0,0 @@ - - - - - messages.SponsoredMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.SponsoredMessages

- -

A set of sponsored messages associated with a channel

-

- -
-
messages.sponsoredMessages#65a4c7d5 messages:Vector<SponsoredMessage> chats:Vector<Chat> users:Vector<User> = messages.SponsoredMessages;
-
----functions---
-
-channels.getSponsoredMessages#ec210fbf channel:InputChannel = messages.SponsoredMessages;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.sponsoredMessagesA set of sponsored messages associated with a channel
-

Methods

- - - - - - - - - - - - - -
MethodDescription
channels.getSponsoredMessagesGet a list of sponsored messages
-

Related pages

-

Sponsored messages

-

How to implement sponsored messages

-
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.StatedMessage b/data/core.telegram.org/type/messages.StatedMessage deleted file mode 100644 index a133d679e0..0000000000 --- a/data/core.telegram.org/type/messages.StatedMessage +++ /dev/null @@ -1,128 +0,0 @@ - - - - - messages.StatedMessage - - - - - - - - - - - - - -
- -
-
-
- -

messages.StatedMessage

- -

Object contains info on one message with auxiliary data and data on the current state of updates.

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.StatedMessages b/data/core.telegram.org/type/messages.StatedMessages deleted file mode 100644 index 1943721b20..0000000000 --- a/data/core.telegram.org/type/messages.StatedMessages +++ /dev/null @@ -1,128 +0,0 @@ - - - - - messages.StatedMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.StatedMessages

- -

Object contains info on the list of messages with auxiliary data and data on current state of updates.

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.StickerSet b/data/core.telegram.org/type/messages.StickerSet deleted file mode 100644 index 88abddd05a..0000000000 --- a/data/core.telegram.org/type/messages.StickerSet +++ /dev/null @@ -1,188 +0,0 @@ - - - - - Messages.StickerSet - - - - - - - - - - - - - -
- -
-
-
- -

Messages.StickerSet

- -

Stickerset

-

- -
-
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
-
----functions---
-
-messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;
-
-stickers.createStickerSet#9021ab67 flags:# masks:flags.0?true animated:flags.1?true videos:flags.4?true user_id:InputUser title:string short_name:string thumb:flags.2?InputDocument stickers:Vector<InputStickerSetItem> software:flags.3?string = messages.StickerSet;
-stickers.removeStickerFromSet#f7760f51 sticker:InputDocument = messages.StickerSet;
-stickers.changeStickerPosition#ffb6d4ca sticker:InputDocument position:int = messages.StickerSet;
-stickers.addStickerToSet#8653febe stickerset:InputStickerSet sticker:InputStickerSetItem = messages.StickerSet;
-stickers.setStickerSetThumb#9a364e30 stickerset:InputStickerSet thumb:InputDocument = messages.StickerSet;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.stickerSetStickerset and stickers inside it
-

Methods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
MethodDescription
messages.getStickerSetGet info about a stickerset
stickers.createStickerSetCreate a stickerset, bots only.
stickers.removeStickerFromSetRemove a sticker from the set where it belongs, bots only. The sticker set must have been created by the bot.
stickers.changeStickerPositionChanges the absolute position of a sticker in the set to which it belongs; for bots only. The sticker set must have been created by the bot
stickers.addStickerToSetAdd a sticker to a stickerset, bots only. The sticker set must have been created by the bot.
stickers.setStickerSetThumbSet stickerset thumbnail
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.StickerSetInstallResult b/data/core.telegram.org/type/messages.StickerSetInstallResult deleted file mode 100644 index 027c42e510..0000000000 --- a/data/core.telegram.org/type/messages.StickerSetInstallResult +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Messages.StickerSetInstallResult - - - - - - - - - - - - - -
- -
-
-
- -

Messages.StickerSetInstallResult

- -

Result of stickerset installation process

-

- -
-
messages.stickerSetInstallResultSuccess#38641628 = messages.StickerSetInstallResult;
-messages.stickerSetInstallResultArchive#35e410a8 sets:Vector<StickerSetCovered> = messages.StickerSetInstallResult;
-
----functions---
-
-messages.installStickerSet#c78fe460 stickerset:InputStickerSet archived:Bool = messages.StickerSetInstallResult;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.stickerSetInstallResultSuccessThe stickerset was installed successfully
messages.stickerSetInstallResultArchiveThe stickerset was installed, but since there are too many stickersets some were archived
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.installStickerSetInstall a stickerset
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.Stickers b/data/core.telegram.org/type/messages.Stickers deleted file mode 100644 index c0b1c1f658..0000000000 --- a/data/core.telegram.org/type/messages.Stickers +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Messages.Stickers - - - - - - - - - - - - - -
- -
-
-
- -

Messages.Stickers

- -

Stickers

-

- -
-
messages.stickersNotModified#f1749a22 = messages.Stickers;
-messages.stickers#30a6ec7e hash:long stickers:Vector<Document> = messages.Stickers;
-
----functions---
-
-messages.getStickers#d5a5d3a1 emoticon:string hash:long = messages.Stickers;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.stickersNotModifiedNo new stickers were found for the given query
messages.stickersFound stickers
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getStickersGet stickers by emoji
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.VotesList b/data/core.telegram.org/type/messages.VotesList deleted file mode 100644 index ad699b77ee..0000000000 --- a/data/core.telegram.org/type/messages.VotesList +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.VotesList - - - - - - - - - - - - - -
- -
-
-
- -

messages.VotesList

- -

How users voted in a poll

-

- -
-
messages.votesList#823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList;
-
----functions---
-
-messages.getPollVotes#b86e380e flags:# peer:InputPeer id:int option:flags.0?bytes offset:flags.1?string limit:int = messages.VotesList;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.votesListHow users voted in a poll
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getPollVotesGet poll results for non-anonymous polls
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/payments.BankCardData b/data/core.telegram.org/type/payments.BankCardData deleted file mode 100644 index 6268d3ffbb..0000000000 --- a/data/core.telegram.org/type/payments.BankCardData +++ /dev/null @@ -1,162 +0,0 @@ - - - - - payments.BankCardData - - - - - - - - - - - - - -
- -
-
-
- -

payments.BankCardData

- -

Credit card info, provided by the card's bank(s)

-

- -
-
payments.bankCardData#3e24e573 title:string open_urls:Vector<BankCardOpenUrl> = payments.BankCardData;
-
----functions---
-
-payments.getBankCardData#2e79d779 number:string = payments.BankCardData;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
payments.bankCardDataCredit card info, provided by the card's bank(s)
-

Methods

- - - - - - - - - - - - - -
MethodDescription
payments.getBankCardDataGet info about a credit card
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/payments.PaymentForm b/data/core.telegram.org/type/payments.PaymentForm deleted file mode 100644 index 9306c2e712..0000000000 --- a/data/core.telegram.org/type/payments.PaymentForm +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Payments.PaymentForm - - - - - - - - - - - - - -
- -
-
-
- -

Payments.PaymentForm

- -

Payment form

-

- -
-
payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
-
----functions---
-
-payments.getPaymentForm#8a333c8d flags:# peer:InputPeer msg_id:int theme_params:flags.0?DataJSON = payments.PaymentForm;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
payments.paymentFormPayment form
-

Methods

- - - - - - - - - - - - - -
MethodDescription
payments.getPaymentFormGet a payment form
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/payments.PaymentReceipt b/data/core.telegram.org/type/payments.PaymentReceipt deleted file mode 100644 index 9e1b997c17..0000000000 --- a/data/core.telegram.org/type/payments.PaymentReceipt +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Payments.PaymentReceipt - - - - - - - - - - - - - -
- -
-
-
- -

Payments.PaymentReceipt

- -

Payment receipt

-

- -
-
payments.paymentReceipt#70c4fe03 flags:# date:int bot_id:long provider_id:long title:string description:string photo:flags.2?WebDocument invoice:Invoice info:flags.0?PaymentRequestedInfo shipping:flags.1?ShippingOption tip_amount:flags.3?long currency:string total_amount:long credentials_title:string users:Vector<User> = payments.PaymentReceipt;
-
----functions---
-
-payments.getPaymentReceipt#2478d1cc peer:InputPeer msg_id:int = payments.PaymentReceipt;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
payments.paymentReceiptReceipt
-

Methods

- - - - - - - - - - - - - -
MethodDescription
payments.getPaymentReceiptGet payment receipt
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/payments.PaymentResult b/data/core.telegram.org/type/payments.PaymentResult deleted file mode 100644 index 35a3f18083..0000000000 --- a/data/core.telegram.org/type/payments.PaymentResult +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Payments.PaymentResult - - - - - - - - - - - - - -
- -
-
-
- -

Payments.PaymentResult

- -

Payment result

-

- -
-
payments.paymentResult#4e5f810d updates:Updates = payments.PaymentResult;
-payments.paymentVerificationNeeded#d8411139 url:string = payments.PaymentResult;
-
----functions---
-
-payments.sendPaymentForm#30c3bc9d flags:# form_id:long peer:InputPeer msg_id:int requested_info_id:flags.0?string shipping_option_id:flags.1?string credentials:InputPaymentCredentials tip_amount:flags.2?long = payments.PaymentResult;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
payments.paymentResultPayment result
payments.paymentVerificationNeededPayment was not successful, additional verification is needed
-

Methods

- - - - - - - - - - - - - -
MethodDescription
payments.sendPaymentFormSend compiled payment form
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/payments.SavedInfo b/data/core.telegram.org/type/payments.SavedInfo deleted file mode 100644 index 878a4c65fd..0000000000 --- a/data/core.telegram.org/type/payments.SavedInfo +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Payments.SavedInfo - - - - - - - - - - - - - -
- -
-
-
- -

Payments.SavedInfo

- -

Saved payment info

-

- -
-
payments.savedInfo#fb8fe43c flags:# has_saved_credentials:flags.1?true saved_info:flags.0?PaymentRequestedInfo = payments.SavedInfo;
-
----functions---
-
-payments.getSavedInfo#227d824b = payments.SavedInfo;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
payments.savedInfoSaved server-side order information
-

Methods

- - - - - - - - - - - - - -
MethodDescription
payments.getSavedInfoGet saved payment information
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/payments.ValidatedRequestedInfo b/data/core.telegram.org/type/payments.ValidatedRequestedInfo deleted file mode 100644 index 499f1e45a1..0000000000 --- a/data/core.telegram.org/type/payments.ValidatedRequestedInfo +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Payments.ValidatedRequestedInfo - - - - - - - - - - - - - -
- -
-
-
- -

Payments.ValidatedRequestedInfo

- -

Validated requested info

-

- -
-
payments.validatedRequestedInfo#d1451883 flags:# id:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = payments.ValidatedRequestedInfo;
-
----functions---
-
-payments.validateRequestedInfo#db103170 flags:# save:flags.0?true peer:InputPeer msg_id:int info:PaymentRequestedInfo = payments.ValidatedRequestedInfo;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
payments.validatedRequestedInfoValidated user-provided info
-

Methods

- - - - - - - - - - - - - -
MethodDescription
payments.validateRequestedInfoSubmit requested order information for validation
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/phone.ExportedGroupCallInvite b/data/core.telegram.org/type/phone.ExportedGroupCallInvite deleted file mode 100644 index a7b6c923fd..0000000000 --- a/data/core.telegram.org/type/phone.ExportedGroupCallInvite +++ /dev/null @@ -1,162 +0,0 @@ - - - - - phone.ExportedGroupCallInvite - - - - - - - - - - - - - -
- -
-
-
- -

phone.ExportedGroupCallInvite

- -

An exported group call invitation.

-

- -
-
phone.exportedGroupCallInvite#204bd158 link:string = phone.ExportedGroupCallInvite;
-
----functions---
-
-phone.exportGroupCallInvite#e6aa647f flags:# can_self_unmute:flags.0?true call:InputGroupCall = phone.ExportedGroupCallInvite;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
phone.exportedGroupCallInviteAn invite to a group call or livestream
-

Methods

- - - - - - - - - - - - - -
MethodDescription
phone.exportGroupCallInviteGet an invite link for a group call or livestream
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/phone.GroupCall b/data/core.telegram.org/type/phone.GroupCall deleted file mode 100644 index 12704f8752..0000000000 --- a/data/core.telegram.org/type/phone.GroupCall +++ /dev/null @@ -1,162 +0,0 @@ - - - - - phone.GroupCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.GroupCall

- -

Contains info about a group call, and partial info about its participants.

-

- -
-
phone.groupCall#9e727aad call:GroupCall participants:Vector<GroupCallParticipant> participants_next_offset:string chats:Vector<Chat> users:Vector<User> = phone.GroupCall;
-
----functions---
-
-phone.getGroupCall#41845db call:InputGroupCall limit:int = phone.GroupCall;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
phone.groupCallContains info about a group call, and partial info about its participants.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
phone.getGroupCallGet info about a group call
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/phone.GroupParticipants b/data/core.telegram.org/type/phone.GroupParticipants deleted file mode 100644 index d1e3205fc7..0000000000 --- a/data/core.telegram.org/type/phone.GroupParticipants +++ /dev/null @@ -1,162 +0,0 @@ - - - - - phone.GroupParticipants - - - - - - - - - - - - - -
- -
-
-
- -

phone.GroupParticipants

- -

Info about the participants of a group call or livestream

-

- -
-
phone.groupParticipants#f47751b6 count:int participants:Vector<GroupCallParticipant> next_offset:string chats:Vector<Chat> users:Vector<User> version:int = phone.GroupParticipants;
-
----functions---
-
-phone.getGroupParticipants#c558d8ab call:InputGroupCall ids:Vector<InputPeer> sources:Vector<int> offset:string limit:int = phone.GroupParticipants;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
phone.groupParticipantsInfo about the participants of a group call or livestream
-

Methods

- - - - - - - - - - - - - -
MethodDescription
phone.getGroupParticipantsGet group call participants
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/phone.JoinAsPeers b/data/core.telegram.org/type/phone.JoinAsPeers deleted file mode 100644 index fb077eb86c..0000000000 --- a/data/core.telegram.org/type/phone.JoinAsPeers +++ /dev/null @@ -1,162 +0,0 @@ - - - - - phone.JoinAsPeers - - - - - - - - - - - - - -
- -
-
-
- -

phone.JoinAsPeers

- -

A list of peers that can be used to join a group call, presenting yourself as a specific user/channel.

-

- -
-
phone.joinAsPeers#afe5623f peers:Vector<Peer> chats:Vector<Chat> users:Vector<User> = phone.JoinAsPeers;
-
----functions---
-
-phone.getGroupCallJoinAs#ef7c213a peer:InputPeer = phone.JoinAsPeers;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
phone.joinAsPeersA list of peers that can be used to join a group call, presenting yourself as a specific user/channel.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
phone.getGroupCallJoinAsGet a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/photos.Photo b/data/core.telegram.org/type/photos.Photo deleted file mode 100644 index e849b14b6a..0000000000 --- a/data/core.telegram.org/type/photos.Photo +++ /dev/null @@ -1,167 +0,0 @@ - - - - - photos.Photo - - - - - - - - - - - - - -
- -
-
-
- -

photos.Photo

- -

Photo with auxiliary data.

-

- -
-
photos.photo#20212ca8 photo:Photo users:Vector<User> = photos.Photo;
-
----functions---
-
-photos.updateProfilePhoto#72d4742c id:InputPhoto = photos.Photo;
-photos.uploadProfilePhoto#89f30f69 flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = photos.Photo;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
photos.photoPhoto with auxiliary data.
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
photos.updateProfilePhotoInstalls a previously uploaded photo as a profile photo.
photos.uploadProfilePhotoUpdates current user profile photo.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/photos.Photos b/data/core.telegram.org/type/photos.Photos deleted file mode 100644 index 9647b8ce0f..0000000000 --- a/data/core.telegram.org/type/photos.Photos +++ /dev/null @@ -1,167 +0,0 @@ - - - - - photos.Photos - - - - - - - - - - - - - -
- -
-
-
- -

photos.Photos

- -

Object contains list of photos with auxiliary data.

-

- -
-
photos.photos#8dca6aa5 photos:Vector<Photo> users:Vector<User> = photos.Photos;
-photos.photosSlice#15051f54 count:int photos:Vector<Photo> users:Vector<User> = photos.Photos;
-
----functions---
-
-photos.getUserPhotos#91cd32a8 user_id:InputUser offset:int max_id:long limit:int = photos.Photos;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
photos.photosFull list of photos with auxiliary data.
photos.photosSliceIncomplete list of photos with auxiliary data.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
photos.getUserPhotosReturns the list of user photos.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/stats.BroadcastStats b/data/core.telegram.org/type/stats.BroadcastStats deleted file mode 100644 index 0b6f833163..0000000000 --- a/data/core.telegram.org/type/stats.BroadcastStats +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Stats.BroadcastStats - - - - - - - - - - - - - -
- -
-
-
- -

Stats.BroadcastStats

- -

Channel statistics

-

- -
-
stats.broadcastStats#bdf78394 period:StatsDateRangeDays followers:StatsAbsValueAndPrev views_per_post:StatsAbsValueAndPrev shares_per_post:StatsAbsValueAndPrev enabled_notifications:StatsPercentValue growth_graph:StatsGraph followers_graph:StatsGraph mute_graph:StatsGraph top_hours_graph:StatsGraph interactions_graph:StatsGraph iv_interactions_graph:StatsGraph views_by_source_graph:StatsGraph new_followers_by_source_graph:StatsGraph languages_graph:StatsGraph recent_message_interactions:Vector<MessageInteractionCounters> = stats.BroadcastStats;
-
----functions---
-
-stats.getBroadcastStats#ab42441a flags:# dark:flags.0?true channel:InputChannel = stats.BroadcastStats;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
stats.broadcastStatsChannel statistics
-

Methods

- - - - - - - - - - - - - -
MethodDescription
stats.getBroadcastStatsGet channel statistics
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/stats.MegagroupStats b/data/core.telegram.org/type/stats.MegagroupStats deleted file mode 100644 index e109a88bee..0000000000 --- a/data/core.telegram.org/type/stats.MegagroupStats +++ /dev/null @@ -1,162 +0,0 @@ - - - - - stats.MegagroupStats - - - - - - - - - - - - - -
- -
-
-
- -

stats.MegagroupStats

- -

Supergroup statistics

-

- -
-
stats.megagroupStats#ef7ff916 period:StatsDateRangeDays members:StatsAbsValueAndPrev messages:StatsAbsValueAndPrev viewers:StatsAbsValueAndPrev posters:StatsAbsValueAndPrev growth_graph:StatsGraph members_graph:StatsGraph new_members_by_source_graph:StatsGraph languages_graph:StatsGraph messages_graph:StatsGraph actions_graph:StatsGraph top_hours_graph:StatsGraph weekdays_graph:StatsGraph top_posters:Vector<StatsGroupTopPoster> top_admins:Vector<StatsGroupTopAdmin> top_inviters:Vector<StatsGroupTopInviter> users:Vector<User> = stats.MegagroupStats;
-
----functions---
-
-stats.getMegagroupStats#dcdf8607 flags:# dark:flags.0?true channel:InputChannel = stats.MegagroupStats;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
stats.megagroupStatsSupergroup statistics
-

Methods

- - - - - - - - - - - - - -
MethodDescription
stats.getMegagroupStatsGet supergroup statistics
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/stats.MessageStats b/data/core.telegram.org/type/stats.MessageStats deleted file mode 100644 index 454c91154a..0000000000 --- a/data/core.telegram.org/type/stats.MessageStats +++ /dev/null @@ -1,162 +0,0 @@ - - - - - stats.MessageStats - - - - - - - - - - - - - -
- -
-
-
- -

stats.MessageStats

- -

Message statistics

-

- -
-
stats.messageStats#8999f295 views_graph:StatsGraph = stats.MessageStats;
-
----functions---
-
-stats.getMessageStats#b6e0a3f5 flags:# dark:flags.0?true channel:InputChannel msg_id:int = stats.MessageStats;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
stats.messageStatsMessage statistics
-

Methods

- - - - - - - - - - - - - -
MethodDescription
stats.getMessageStatsGet message statistics
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/stickers.SuggestedShortName b/data/core.telegram.org/type/stickers.SuggestedShortName deleted file mode 100644 index 694c2ba182..0000000000 --- a/data/core.telegram.org/type/stickers.SuggestedShortName +++ /dev/null @@ -1,162 +0,0 @@ - - - - - stickers.SuggestedShortName - - - - - - - - - - - - - -
- -
-
-
- -

stickers.SuggestedShortName

- -

A suggested short name for the specified stickerpack

-

- -
-
stickers.suggestedShortName#85fea03f short_name:string = stickers.SuggestedShortName;
-
----functions---
-
-stickers.suggestShortName#4dafc503 title:string = stickers.SuggestedShortName;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
stickers.suggestedShortNameA suggested short name for a stickerpack
-

Methods

- - - - - - - - - - - - - -
MethodDescription
stickers.suggestShortNameSuggests a short name for a given stickerpack name
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/storage.FileType b/data/core.telegram.org/type/storage.FileType deleted file mode 100644 index 10f85871df..0000000000 --- a/data/core.telegram.org/type/storage.FileType +++ /dev/null @@ -1,188 +0,0 @@ - - - - - storage.FileType - - - - - - - - - - - - - -
- -
-
-
- -

storage.FileType

- -

Object describes the file type.

-

- -
-
storage.fileUnknown#aa963b05 = storage.FileType;
-storage.filePartial#40bc6f52 = storage.FileType;
-storage.fileJpeg#7efe0e = storage.FileType;
-storage.fileGif#cae1aadf = storage.FileType;
-storage.filePng#a4f63c0 = storage.FileType;
-storage.filePdf#ae1e508d = storage.FileType;
-storage.fileMp3#528a0677 = storage.FileType;
-storage.fileMov#4b09ebbc = storage.FileType;
-storage.fileMp4#b3cea0e4 = storage.FileType;
-storage.fileWebp#1081464c = storage.FileType;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
storage.fileUnknownUnknown type.
storage.filePartialPart of a bigger file.
storage.fileJpegJPEG image. MIME type: image/jpeg.
storage.fileGifGIF image. MIME type: image/gif.
storage.filePngPNG image. MIME type: image/png.
storage.filePdfPDF document image. MIME type: application/pdf.
storage.fileMp3Mp3 audio. MIME type: audio/mpeg.
storage.fileMovQuicktime video. MIME type: video/quicktime.
storage.fileMp4MPEG-4 video. MIME type: video/mp4.
storage.fileWebpWEBP image. MIME type: image/webp.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/string.html b/data/core.telegram.org/type/string.html deleted file mode 100644 index ad86e71f6b..0000000000 --- a/data/core.telegram.org/type/string.html +++ /dev/null @@ -1,126 +0,0 @@ - - - - - string - - - - - - - - - - - - - -
- -
-
-
- -

string

- -

A basic bare type. Values of type string look differently depending on the length L of the string being serialized:

-
    -
  • If L <= 253, the serialization contains one byte with the value of L, then L bytes of the string followed by 0 to 3 characters containing 0, such that the overall length of the value be divisible by 4, whereupon all of this is interpreted as a sequence of int(L/4)+1 32-bit little-endian integers.
  • -
  • If L >= 254, the serialization contains byte 254, followed by 3 bytes with the string length L in little-endian order, followed by L bytes of the string, further followed by 0 to 3 null padding bytes.
  • -
-

All strings passed to the API must be encoded in UTF-8. When arbitrary byte sequences have to be serialized, bytes alias is to be used.

-

Further details on basic types»

-

Related pages

-

bytes

-

Basic bare type. It is an alias of the string type, with the difference that the value may contain arbitrary byte sequences, including invalid UTF-8 sequences.

-

When computing crc32 for a constructor or method it is necessary to replace all byte types with string types.

-

Binary Data Serialization

- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/updates.ChannelDifference b/data/core.telegram.org/type/updates.ChannelDifference deleted file mode 100644 index 59315ec131..0000000000 --- a/data/core.telegram.org/type/updates.ChannelDifference +++ /dev/null @@ -1,172 +0,0 @@ - - - - - updates.ChannelDifference - - - - - - - - - - - - - -
- -
-
-
- -

updates.ChannelDifference

- -

Contains the difference (new messages) between our local channel state and the remote state

-

- -
-
updates.channelDifferenceEmpty#3e11affb flags:# final:flags.0?true pts:int timeout:flags.1?int = updates.ChannelDifference;
-updates.channelDifferenceTooLong#a4bcc6fe flags:# final:flags.0?true timeout:flags.1?int dialog:Dialog messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
-updates.channelDifference#2064674e flags:# final:flags.0?true pts:int timeout:flags.1?int new_messages:Vector<Message> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
-
----functions---
-
-updates.getChannelDifference#3173d78 flags:# force:flags.0?true channel:InputChannel filter:ChannelMessagesFilter pts:int limit:int = updates.ChannelDifference;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
updates.channelDifferenceEmptyThere are no new updates
updates.channelDifferenceTooLongThe provided pts + limit < remote pts. Simply, there are too many updates to be fetched (more than limit), the client has to resolve the update gap in one of the following ways:

1. Delete all known messages in the chat, begin from scratch by refetching all messages manually with getHistory. It is easy to implement, but suddenly disappearing messages looks awful for the user.
2. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to getHistory. It looks much smoother for the user, they will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of getHistory and getMessages must be used to update state of deleted and edited messages left in the memory.
3. Save all messages loaded in the memory and stored in the database without saving that some messages form continuous ranges. Messages in the database will be excluded from results of getChatHistory and searchChatMessages after application restart and will be available only through getMessage. Every message should still be checked using getHistory. It has more disadvantages over 2) than advantages.
4. Save all messages with saving all data about continuous message ranges. Messages from the database may be used as results of getChatHistory and (if implemented continuous ranges support for searching shared media) searchChatMessages. The messages should still be lazily checked using getHistory, but they are still available offline. It is the best way for gaps support, but it is pretty hard to implement correctly. It should be also noted that some messages like live location messages shouldn't be deleted.
updates.channelDifferenceThe new updates
-

Methods

- - - - - - - - - - - - - -
MethodDescription
updates.getChannelDifferenceReturns the difference between the current state of updates of a certain channel and transmitted.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/updates.Difference b/data/core.telegram.org/type/updates.Difference deleted file mode 100644 index df743e954b..0000000000 --- a/data/core.telegram.org/type/updates.Difference +++ /dev/null @@ -1,177 +0,0 @@ - - - - - updates.Difference - - - - - - - - - - - - - -
- -
-
-
- -

updates.Difference

- -

Occurred changes.

-

- -
-
updates.differenceEmpty#5d75a138 date:int seq:int = updates.Difference;
-updates.difference#f49ca0 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> state:updates.State = updates.Difference;
-updates.differenceSlice#a8fb1981 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> intermediate_state:updates.State = updates.Difference;
-updates.differenceTooLong#4afe8f6d pts:int = updates.Difference;
-
----functions---
-
-updates.getDifference#25939651 flags:# pts:int pts_total_limit:flags.0?int date:int qts:int = updates.Difference;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
updates.differenceEmptyNo events.
updates.differenceFull list of occurred events.
updates.differenceSliceIncomplete list of occurred events.
updates.differenceTooLongThe difference is too long, and the specified state must be used to refetch updates.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
updates.getDifferenceGet new updates.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/updates.State b/data/core.telegram.org/type/updates.State deleted file mode 100644 index ab92b162ad..0000000000 --- a/data/core.telegram.org/type/updates.State +++ /dev/null @@ -1,162 +0,0 @@ - - - - - updates.State - - - - - - - - - - - - - -
- -
-
-
- -

updates.State

- -

Object contains info on state for further updates.

-

- -
-
updates.state#a56c2a3e pts:int qts:int date:int seq:int unread_count:int = updates.State;
-
----functions---
-
-updates.getState#edd4882a = updates.State;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
updates.stateUpdates state.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
updates.getStateReturns a current state of updates.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/upload.CdnFile b/data/core.telegram.org/type/upload.CdnFile deleted file mode 100644 index 0c1b0cbfdf..0000000000 --- a/data/core.telegram.org/type/upload.CdnFile +++ /dev/null @@ -1,167 +0,0 @@ - - - - - upload.CdnFile - - - - - - - - - - - - - -
- -
-
-
- -

upload.CdnFile

- -

Represents the download status of a CDN file

-

- -
-
upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;
-upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;
-
----functions---
-
-upload.getCdnFile#2000bcc3 file_token:bytes offset:int limit:int = upload.CdnFile;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
upload.cdnFileReuploadNeededThe file was cleared from the temporary RAM cache of the CDN and has to be reuploaded.
upload.cdnFileRepresent a chunk of a CDN file.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
upload.getCdnFileDownload a CDN file.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/upload.File b/data/core.telegram.org/type/upload.File deleted file mode 100644 index 8a195440cf..0000000000 --- a/data/core.telegram.org/type/upload.File +++ /dev/null @@ -1,167 +0,0 @@ - - - - - upload.File - - - - - - - - - - - - - -
- -
-
-
- -

upload.File

- -

Contains info on file.

-

- -
-
upload.file#96a18d5 type:storage.FileType mtime:int bytes:bytes = upload.File;
-upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;
-
----functions---
-
-upload.getFile#b15a9afc flags:# precise:flags.0?true cdn_supported:flags.1?true location:InputFileLocation offset:int limit:int = upload.File;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
upload.fileFile content.
upload.fileCdnRedirectThe file must be downloaded from a CDN DC.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
upload.getFileReturns content of a whole file or its part.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/upload.WebFile b/data/core.telegram.org/type/upload.WebFile deleted file mode 100644 index 2e1bcb3ec0..0000000000 --- a/data/core.telegram.org/type/upload.WebFile +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Upload.WebFile - - - - - - - - - - - - - -
- -
-
-
- -

Upload.WebFile

- -

Remote file

-

- -
-
upload.webFile#21e753bc size:int mime_type:string file_type:storage.FileType mtime:int bytes:bytes = upload.WebFile;
-
----functions---
-
-upload.getWebFile#24e6818d location:InputWebFileLocation offset:int limit:int = upload.WebFile;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
upload.webFileRepresents a chunk of an HTTP webfile downloaded through telegram's secure MTProto servers
-

Methods

- - - - - - - - - - - - - -
MethodDescription
upload.getWebFileReturns content of an HTTP file or a part, by proxying the request through telegram.
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/video_stickers.html b/data/core.telegram.org/video_stickers.html deleted file mode 100644 index abf48687bc..0000000000 --- a/data/core.telegram.org/video_stickers.html +++ /dev/null @@ -1,115 +0,0 @@ - - - - - Page not found - - - - - - - - - - - - - -
- -
-
-
-
-

Page not found

- -
The page has not been saved
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/widgets.html b/data/core.telegram.org/widgets.html deleted file mode 100644 index 8099284b07..0000000000 --- a/data/core.telegram.org/widgets.html +++ /dev/null @@ -1,141 +0,0 @@ - - - - - Telegram Widgets - - - - - - - - - - - - - -
- -
-
-
-
-

Telegram Widgets

- -

Telegram widgets offer a quick way to add a sharing button to your pages, embed posts from public channels or groups. Widgets can also help your users log in with Telegram or view Telegram Discussions on your website.

-
-
-
- - -
-
- - -
-
- - -
-
- - -
-
-
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/widgets/discussion.html b/data/core.telegram.org/widgets/discussion.html deleted file mode 100644 index 0c0a699ca6..0000000000 --- a/data/core.telegram.org/widgets/discussion.html +++ /dev/null @@ -1,226 +0,0 @@ - - - - - Discussion Widget - - - - - - - - - - - - - - - -
- -
-
-
- -

Discussion Widget

- -

You can embed discussions from any public channel on your website. You only need a link to a post with comments to embed it together with all discussion.

-

If you have a website with articles and a telegram channel where you post links to these articles, you can use this widget to show discussions from that channel on your website. In this case you only need a link to the channel. Discussions will be available on your website as soon as you post a link into the channel. For this to work, you should add the <link rel="canonical" href="%page_url%"> tag to the page header where %page_url% is the canonical URL of the current page.

-

Configure widget

-

You can choose options for your widget using the form below.

-

-
- -
-
- -
- -
-
-
- -
- -
-
- -
-
-
- -
-
- -
-
-
-
- -
- -
-
- - - - - - - -
- - -
-
- -
- -
- -
Make sure you have a <link rel="canonical" href="%page_url%"> tag in the page header with the canonical url of the current page.
-
-
- -
-
-
-
-
-

-

Basic comments

-

If you're looking to simply add Telegram comments to pages on your website, without linking them with a channel, you can use our basic comments solution.

-
- -
- -
-
- -
- - - - - - - - - - diff --git a/data/core.telegram.org/widgets/login.html b/data/core.telegram.org/widgets/login.html deleted file mode 100644 index 67d03f408b..0000000000 --- a/data/core.telegram.org/widgets/login.html +++ /dev/null @@ -1,404 +0,0 @@ - - - - - Telegram Login Widget - - - - - - - - - - - - - - -
- -
-
-
- -

Telegram Login Widget

- -
-

The Telegram login widget is a simple way to authorize users on your website.
Check out this post for a general overview of the widget.

-
-

Setting up a bot

-

To use the login widget, you'll need a Telegram bot.

-

We strongly recommend that the profile picture of the bot you use for authorization corresponds with your website‘s logo, and that the bot’s name reflects that connection.

-

Users will see this message when they log into your website:

-
- -
- -

It is more likely that users will log in if your bot has a name and logo they expect to see.

-

Linking your domain to the bot

-

Once you have chosen a bot, send the /setdomain command to @Botfather to link your website's domain to the bot. Then configure your widget below and embed the code on your website.

-

Widget configuration

-

-
- -
-
-
- -
- -
- - -
- Log in below to load your bots with linked domains -
-
- -
- -
- - - -
-
- -
-
- -
- -
- - -
-
- -
- -
- - -
-
- -
- -
- -
-
- -
- -
- -
-
- -
-
-
-
-
-

-

Receiving authorization data

-

After a successful authorization, the widget can return data in two ways:

-
    -
  • by redirecting the user to the URL specified in the data-auth-url attribute with the following parameters: id, first_name, last_name, username, photo_url, auth_date and hash;
  • -
  • by calling the callback function data-onauth with the JSON-object containing id, first_name, last_name, username, photo_url, auth_date and hash fields.
  • -
-

Checking authorization

-

You can verify the authentication and the integrity of the data received by comparing the received hash parameter with the hexadecimal representation of the HMAC-SHA-256 signature of the data-check-string with the SHA256 hash of the bot's token used as a secret key.

-

Data-check-string is a concatenation of all received fields, sorted in alphabetical order, in the format key=<value> with a line feed character ('\n', 0x0A) used as separator – e.g., 'auth_date=<auth_date>\nfirst_name=<first_name>\nid=<id>\nusername=<username>'.

-

The full check might look like:

-
data_check_string = ...
-secret_key = SHA256(<bot_token>)
-if (hex(HMAC_SHA256(data_check_string, secret_key)) == hash) {
-  // data is from Telegram
-}
-

To prevent the use of outdated data, you can additionally check the auth_date field, which contains a Unix timestamp when the authentication was received.

-

Sample implementation

-

You can find sample PHP code for checking authorization and receiving data about a logged in user on this page.

-
- -
- -
-
- -
- - - - - - - - - diff --git a/data/core.telegram.org/widgets/post.html b/data/core.telegram.org/widgets/post.html deleted file mode 100644 index a5a36f8a8e..0000000000 --- a/data/core.telegram.org/widgets/post.html +++ /dev/null @@ -1,240 +0,0 @@ - - - - - Post Widget - - - - - - - - - - - - - - - -
- -
-
-
- -

Post Widget

- -

You can embed messages from public groups and channels anywhere. Here’s what an embed of a Telegram message looks like when included on a web page:

-

- -

-
- -

To get the HTML-code for embedding a message, just open its t.me link (e.g., t.me/durov/43) in a web browser and click < > EMBED:

-
- -
- -

Configure widget

-

You can choose more options using the form below.

-

-
- -
-
- -
- -
-
-
- -
- -
-
- -
-
-
-
- -
- -
- - - -
-
- -
- -
-
- - - - - - - -
- - -
-
- -
- -
- -
-
- -
-
-
-
-
-

-
- -
- -
-
- -
- - - - - - - - - - diff --git a/data/core.telegram.org/widgets/share.html b/data/core.telegram.org/widgets/share.html deleted file mode 100644 index 0f1e2ca268..0000000000 --- a/data/core.telegram.org/widgets/share.html +++ /dev/null @@ -1,250 +0,0 @@ - - - - - Sharing Button - - - - - - - - - - - - - - -
- -
-
-
- -

Sharing Button

- -

A Telegram Sharing Button is an easy way to let users forward content from your website or app to their friends, Channels or Saved Messages on Telegram.

-
- TITLE -
- -

When a user presses the button, Telegram asks them to choose a chat, group or channel where your link will be shared. You can also add some text that describes the link – the user will be able to edit it before sending the message.

-
- TITLE -
- -
-

Check out posts on the Telegram Blog for working examples of sharing buttons.

-
-

Adding Telegram sharing buttons to your website

-

Widget Constructor

-

Use this constructor to get embeddable code for your website.

-


- -

-
- -
-
- -
- -
-
-
- -
- -
-
- -
-
-
-
- -
- -
- - -
-
- -
- -
- - -
-
- -
- -
- -
-
- -
-
-
-
-
-

-

Custom buttons

-

Feel free to create your own custom UI for the button. The only thing you need to make it work is to point the user to this URL on click:

-
https://t.me/share/url?url={url}&text={text}
-

where {url} is the URL the user will be sharing and {text} is an optional description that will be included with the link. Both values should be URL-encoded.

-

Here is a sample code for PHP:

-
/**
- * @param string $url Absolute URL to share, e.g. "https://example.com/path/to/article?with=params"
- * @param string $text Optional comment to share URL with, e.g. "Check out this article!"
- * @return string Button HTML markup, feel free to modify to your taste
- */
-function telegramForwardButton($url, $text = '') {
-  $share_url = 'https://t.me/share/url?url='.rawurlencode($url).'&text='.rawurlencode($text);
-  return "<a href=\"{$share_url}\">Share</a>";
-}
-

You are welcome to use the Telegram Logos in your custom button design.

-

Integrations and libraries

- -

If you have a library, plugin or integration script for Telegram sharing buttons, please contact @BotSupport and we'll add you to this list.

-
- -
- -
-
- -
- - - - - - - - - diff --git a/data/corefork.telegram.org/api.html b/data/corefork.telegram.org/api.html deleted file mode 100644 index a082817b82..0000000000 --- a/data/corefork.telegram.org/api.html +++ /dev/null @@ -1,253 +0,0 @@ - - - - - Telegram APIs - - - - - - - - - - - - - -
- -
-
-
-
-

Telegram APIs

- -

We offer two kinds of APIs for developers. The Bot API allows you to easily create programs that use Telegram messages for an interface. The Telegram API and TDLib allow you to build your own customized Telegram clients. You are welcome to use both APIs free of charge.

-

You can also add Telegram Widgets to your website.

-

Designers are welcome to create Animated Stickers or Custom Themes for Telegram.

-
-

Bot API

-
- -
-

This API allows you to connect bots to our system. Telegram Bots are special accounts that do not require an additional phone number to set up. These accounts serve as an interface for code running somewhere on your server.

-

To use this, you don't need to know anything about how our MTProto encryption protocol works — our intermediary server will handle all encryption and communication with the Telegram API for you. You communicate with this server via a simple HTTPS-interface that offers a simplified version of the Telegram API.

-
-

Learn more about the Bot API here »

-
-

Bot developers can also make use of our Payments API to accept payments from Telegram users around the world.

-
-

TDLib – build your own Telegram

-

Even if you're looking for maximum customization, you don't have to create your app from scratch. Try our Telegram Database Library (or simply TDLib), a tool for third-party developers that makes it easy to build fast, secure and feature-rich Telegram apps.

-

TDLib takes care of all network implementation details, encryption and local data storage, so that you can dedicate more time to design, responsive interfaces and beautiful animations.

-

TDLib supports all Telegram features and makes developing Telegram apps a breeze on any platform. It can be used on Android, iOS, Windows, macOS, Linux and virtually any other system. The library is open source and compatible with virtually any programming language.

-
-

Learn more about TDLib here »

-
-
-

Telegram API

-

This API allows you to build your own customized Telegram clients. It is 100% open for all developers who wish to create Telegram applications on our platform. Feel free to study the open source code of existing Telegram applications for examples of how things work here. Don't forget to register your application in our system.

- -

Getting started

-

Creating an application

-

How to get your application identifier and create a new Telegram app.

-

User authorization

-

How to register a user's phone to start using the API.

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

-

QR code login

-

QR code login flow

-

Error handling

-

How to handle API return errors correctly.

-

Handling different data centers

-

How to connect to the closest DC access point for faster interaction with the API, and things to watch out for when developing a client.

-

Handling updates

-

How to subscribe to updates and handle them properly.

-

Handling PUSH-notifications

-

How to subscribe and handle them properly.

-

Channels, supergroups and groups

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

-

Calling methods

-

Additional options for calling methods.

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

-

Pagination

-

How to fetch results from large lists of objects.

-

Client configuration

-

The MTProto API has multiple client configuration parameters that can be fetched with the appropriate methods.

-

Security

-

Secret chats, end-to-end encryption

-

End-to-end-encrypted messaging.

-

Security guidelines

-

Important checks required in your client application.

-

Perfect Forward Secrecy

-

Binding temporary authorization key to permanent ones.

-

End-to-End Encryption in Voice and Video Calls

-

End-to-end-encrypted calls.

-

Optimization

-

Client optimization

-

Ways to boost API interactions.

-

API methods

-

Available method list

-

A list of available high-level methods.

-

API TL-schema, as JSON

-

Text and JSON-presentation of types and methods used in API.

-

Available layer list

-

A list of available schema versions.

-

Other articles

-

Working with bots, using the MTProto API

-

How to work with bots using the MTProto API.

-

Commands

-

Bots offer a set of commands that can be used by users in private, or in a chat.

-

Buttons

-

Users can interact with your bot via buttons or even inline buttons, straight from inline messages in any chat.

-

Inline queries

-

Users can interact with your bot via inline queries, straight from the text input field in any chat.

-

Games

-

Bots can offer users HTML5 games to play solo or to compete against each other in groups and one-on-one chats; how to work with games in the MTProto API.

-

Search & filters

-

Telegram allows applying detailed message filters while looking for messages in chats. -This allows the server to filter messages based on a text query, and even on their type, and this feature is often used by graphical clients to implement features like the chat gallery, chat profile pictures and more.

-

Polls

-

Telegram allows sending polls and quizes, that can be voted on by thousands, if not milions of users in chats and channels.

-

Admin, banned and default rights for channels, supergroups and groups

-

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

-

Discussion groups

-

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

-

Channel comments and message threads

-

Telegram allows commenting on a channel post or on a generic group message, thanks to message threads.

-

Admin log

-

Both supergroups and channels offer a so-called admin log, a log of recent relevant supergroup and channel actions, like the modification of group/channel settings or information on behalf of an admin, user kicks and bans, and more.

-

Pinned messages

-

Telegram allows pinning multiple messages on top of a specific chat.

-

Mentions

-

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

-

Scheduled messages

-

Telegram allows scheduling messages.

-

Live geolocations

-

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

-

Min constructors

-

Sometimes, user and channel constructors met in group chat updates may not contain full info about the user: how to handle such constructors.

-

Account deletion

-

How to reset an account if the 2FA password was forgotten.

-

Imported messages

-

Telegram allows importing messages and media from foreign chat apps.

-

Telegram Passport

-

How to work with Telegram Passport directly using the MTProto API.

-

Telegram Payments

-

How to work with Telegram Payments directly using the MTProto API.

-

Styled text with message entities

-

How to create styled text with message entities

-

Working with animated emojis

-

Graphical telegram clients should transform emojis into their respective animated version.

-

Working with animated dice

-

Telegram supports sending animated dice emojis.

-

Message drafts

-

How to handle message drafts

-

Folders

-

Working with folders

-

Top peer rating

-

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

-

Handling file references

-

How to handle file references.

-

Seamless Telegram Login

-

Handle Seamless Telegram Login URL authorization requests.

-

Web events

-

When interacting with HTML5 games and the websites of payment gateways, Telegram apps should expose the following JS APIs.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/api/account-deletion.html b/data/corefork.telegram.org/api/account-deletion.html deleted file mode 100644 index 632a361da8..0000000000 --- a/data/corefork.telegram.org/api/account-deletion.html +++ /dev/null @@ -1,129 +0,0 @@ - - - - - Account deletion - - - - - - - - - - - - - -
- -
-
-
- -

Account deletion

- -

If the user has successfully provided the login code, but they forgot the 2FA password, the account should be reset: this can be done using account.deleteAccount.

-

If the account's 2FA password was modified more than 7 days ago and was active in the last 7 days, account deletion will be delayed for 7 days, and a service message will be sent to the user, containing a link in one of the following formats:

-
    -
  • https://telegram.me/confirmphone?phone=XXX&hash=YYYY
  • -
  • tg://confirmphone?phone=XXX&hash=YYYY
  • -
-

When clicked, account.sendConfirmPhoneCode must be called with the specified hash, using the account with the specified phone number. -This will send a phone number verification code to the phone number associated with the account. -The phone code settings are the same as for the login code, and auth.cancelCode with auth.resendCode can be used as well, to resend or cancel the phone code as for the login code.

-

Once the SMS code is received, the account.confirmPhone method will have to be called with the SMS code and the phone hash received from the account.sendConfirmPhoneCode method.

-

This will cancel deletion of the account and will log out the user that tried to reset it. -Otherwise, if the number isn't confirmed in 7 days, the account will be deleted and the user will be free to recreate it.

-

Related articles

-

User Authorization

-

How to register a user's phone to start using the API.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/api/animated-emojis.html b/data/corefork.telegram.org/api/animated-emojis.html deleted file mode 100644 index f4c1402574..0000000000 --- a/data/corefork.telegram.org/api/animated-emojis.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - Animated Emojis - - - - - - - - - - - - - -
- -
-
-
- -

Animated Emojis

- -

Graphical telegram clients should transform emojis into their respective animated version.

-
inputStickerSetAnimatedEmoji#28703c8 = InputStickerSet;
-
-messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
-
----functions---
-
-messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;
-

On startup, clients should fetch the animated emoji stickerset by calling the messages.getStickerSet method, providing inputStickerSetAnimatedEmoji to the stickerset field.
-The returned stickerset will contain a set of animated stickers, one for each of the supported emojis.

-

Clients should substitute messages containing only one instance of one of the allowed emojis with the respective animated sticker.

-

Animated emojis should loop only once when first sent or received, or when clicked.
-For supported emojis, clients on both sides of private chats with users are supposed to show a reaction animation when any of the two users clicks on the animated emoji: click here for more info ».

-

For special dice emojis like 🎲, 🎯, or 🏀, clients are supposed to behave differently both when sending and receiving such emojis: click here for more info ».

-

Emojis with sounds

-

Certained animated emojis should play sound when clicked, as specified by server-side configuration.

-

The returned JSON object will contain the following map, with a list of file IDs to download:

-
    "emojies_sounds": {
-        "\ud83c\udf83": {
-            "id": "4956223179606458539",
-            "access_hash": "-2107001400913062971",
-            "file_reference_base64": "AF-4ApC7ukC0UWEPZN0TeSJURe7T"
-        },
-        "\u26b0": {
-            "id": "4956223179606458540",
-            "access_hash": "-1498869544183595185",
-            "file_reference_base64": "AF-4ApCLKMGt96WCvLm58kbqZHd3"
-        },
-        "\ud83e\udddf\u200d\u2642": {
-            "id": "4960929110848176331",
-            "access_hash": "3986395821757915468",
-            "file_reference_base64": "AF-4ApAedNln3IMEHH-SUQuH8L9g"
-        },
-    }
-

The file reference field should be base64-decoded before downloading the file.

-

Emoji reactions

-
inputStickerSetAnimatedEmojiAnimations#cde3739 = InputStickerSet;
-
-messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
-
-stickerPack#12b299d4 emoticon:string documents:Vector<long> = StickerPack;
-
-sendMessageEmojiInteraction#25972bcb emoticon:string msg_id:int interaction:DataJSON = SendMessageAction;
-sendMessageEmojiInteractionSeen#b665902e emoticon:string = SendMessageAction;
-
-updateUserTyping#c01e857f user_id:long action:SendMessageAction = Update;
-
----functions---
-
-messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;
-
-messages.setTyping#58943ee2 flags:# peer:InputPeer top_msg_id:flags.0?int action:SendMessageAction = Bool;
-

On startup, clients should fetch the animated reaction emoji stickerset by calling the messages.getStickerSet method, providing inputStickerSetAnimatedEmojiAnimations to the stickerset field.
-The returned stickerset will contain a set of animated emoji reactions, one or more for each of the supported emojis.
-If a set of reactions for the ❤ emoji is returned, the same reactions should also be assigned to the 🧡, 💛, 💚, 💙, 💜, 🖤, 🤍 and 🤎 emojis.

-

Clients on both sides of private chats with users should overlay one of the appropriate reaction animations over the animated sticker when any of the two users clicks on a supported animated emoji.
-The reaction animation for each separate tap should be chosen randomly from all the available reactions for a given emoji, and multiple taps should be aggregated and sent to the other user as follows:

-

At each tap, clients should store all occurred taps in a local list.
-After 1 second has elapsed with no more taps, the local list should be cleared and stored taps should be sent using messages.setTyping, passing a sendMessageEmojiInteraction constructor with the following fields:

-
    -
  • emoticon - The emoji we're reacting to
  • -
  • msg_id - Message ID of the animated emoji that was clicked
  • -
  • interaction - A JSON object with interaction info, containing the following keys:
      -
    • v - An integer indicating the object version, currently 1
    • -
    • a - An array of JSON objects, each containing the following keys:
        -
      • t - float, number of seconds that passed since the previous tap in the array, the first tap uses a value of 0.0.
      • -
      • i - integer, 1-based index of the randomly chosen animation for the tap (equivalent to the index of a specific emoji-related animation in stickerPack + 1).
      • -
      -
    • -
    -
  • -
-

1 second after the receiving user has seen the last reaction animation for a specific emoji, an acknowledgement must be sent using messages.setTyping, passing a sendMessageEmojiInteractionSeen with that emoji.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/api/auth.html b/data/corefork.telegram.org/api/auth.html deleted file mode 100644 index aee36a6995..0000000000 --- a/data/corefork.telegram.org/api/auth.html +++ /dev/null @@ -1,202 +0,0 @@ - - - - - User Authorization - - - - - - - - - - - - - -
- -
-
-
- -

User Authorization

- -
- -

Authorization is associated with a client’s encryption key identifier: auth_key_id. No additional parameters need to be passed into methods following authorization.

-

To log in as a bot, follow these instructions ».

-

Sending a verification code

-

Example implementations: telegram for android, tdlib.

-

To show a nicely formatted and validated phone number field, the help.countriesList constructor can be obtained using the help.getCountriesList method.
The help.countriesList config is then used as described here ».

-

Authorization requires that a text message containing an authorization code first be sent to the user’s phone.
This may be done using the auth.sendCode method.
The system will automatically choose how to send the authorization code; there are four possible ways the code can arrive:

-
    -
  • Telegram code
  • -
  • SMS code
  • -
  • Phone call: a synthesized voice will tell the user which verification code to input
  • -
  • Flash phone call: the code will be sent via a flash phone call, that will be closed immediately.
    In the last case, the phone code will then be the phone number itself, just make sure that the phone number matches the specified pattern (see auth.sentCodeTypeFlashCall).
  • -
-

The auth.sendCode method also has parameters for enabling/disabling use of flash calls, and allows passing an SMS token that will be included in the sent SMS.
For example, the latter is required in newer versions of android, to use the android SMS receiver APIs.

-

The returned auth.SentCode object will contain multiple parameters:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
flags#Flags, see TL conditional fields
typeauth.SentCodeTypePhone code type
phone_code_hashstringPhone code hash, to be stored and later re-used with auth.signIn
next_typeflags.1?auth.CodeTypePhone code type that will be sent next, if the phone code is not received within timeout seconds: to send it use auth.resendCode
timeoutflags.2?intTimeout for reception of the phone code
-

If the message takes too long (timeout seconds) to arrive at the phone, the auth.resendCode method may be invoked to resend a code of type next_type.
If the same happens again, you can use auth.resendCode with the next_type returned by the previous call to auth.resendCode.
To cancel the verification code use auth.cancelCode.

-

Sign in/sign up

-

When user enters verification code, the auth.signIn method must be used to validate it and possibly sign user in.

-

If the code was entered correctly, but the method returns auth.authorizationSignUpRequired, it means that account with this phone number doesn't exist yet: user needs to provide basic information, accept terms of service and then the new user registration method (auth.signUp) must be invoked.

-

2FA

-

When trying to sign in using auth.signIn, an error 400 SESSION_PASSWORD_NEEDED may be returned, if the user has two-factor authentication enabled.
In this case, instructions for SRP 2FA authentication must be followed.

-

To set up two-factor authorization on an already authorized account, follow the SRP 2FA authentication docs.

-

Test Accounts

-

Each phone number is limited to only a certain amount of logins per day (e.g. 5, but this is subject to change) after which the API will return a FLOOD error until the next day. This might not be enough for testing the implementation of User Authorization flows in client applications.

-

There are several reserved phone number prefixes for testing that your application handles redirects between DCs, sign up, sign in and 2FA flows correctly. These numbers are only available on Test DCs (their IP addresses for TCP transport are availble in API development tools panel after api_id was obtained, URI format for HTTPS/Websocket transport).

-

If you wish to emulate an application of a user associated with DC number X, it is sufficient to specify the phone number as 99966XYYYY, where YYYY are random numbers, when registering the user. A user like this would always get XXXXX as the login confirmation code (the DC number, repeated five times). Note that the value of X must be in the range of 1-3 because there are only 3 Test DCs. When the flood limit is reached for any particular test number, just choose another number (changing the YYYY random part).

-

Do not store any important or private information in the messages of such test accounts; anyone can make use of the simplified authorization mechanism – and we periodically wipe all information stored there.

-

Proceed with User Authorization flows in Production DCs only after you make sure everything works correctly on Test DCs first to avoid reaching flood limits.

-
-

To help you with working on production DCs, logins with the same phone number with which the api_id was registered have more generous flood limits.

-
-

We are authorized

-

As a result of authorization, the client key, auth_key_id, becomes associated with the user, and each subsequent API call with this key will be executed with that user’s identity. The authorization method itself returns the relevant user. It is best to immediately store the User ID locally in a binding with the key.

-

Only a small portion of the API methods are available to unauthorized users:

- -

Other methods will result in an error: 401 UNAUTHORIZED.

-
- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/bots.html b/data/corefork.telegram.org/api/bots.html deleted file mode 100644 index cacdbd775b..0000000000 --- a/data/corefork.telegram.org/api/bots.html +++ /dev/null @@ -1,142 +0,0 @@ - - - - - Bots - - - - - - - - - - - - - -
- -
-
-
- -

Bots

- -
- -

Working with bots, using the MTProto API.

-

See here for more info about bots.

-

Please note that you can also use the simplified HTTP Bot API to use bots, see here for more info ».

-

Login

-
---functions---
-
-auth.importBotAuthorization#67a3ff2c flags:int api_id:int api_hash:string bot_auth_token:string = auth.Authorization;
-

In order to login as a bot, instead of using the standard login code flow, simply provide the bot token generated by @botfather.
-You must still provide your API ID, as per user logins.

-

After successful authorization, you will be able to use most MTProto API methods, just as any normal user.
-Methods that can be called by bots will have a Bots can use this method notice.

-

Commands

-

Bots offer a set of commands that can be used by users in private, or in a chat.

-

Buttons

-

Users can interact with your bot via buttons or even inline buttons, straight from inline messages in any chat.

-

Inline queries

-

Users can interact with your bot via inline queries, straight from the text input field in any chat.

-

Games

-

Bots can offer users HTML5 games to play solo or to compete against each other in groups and one-on-one chats; how to work with games in the MTProto API.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/bots/buttons.html b/data/corefork.telegram.org/api/bots/buttons.html deleted file mode 100644 index f96e195248..0000000000 --- a/data/corefork.telegram.org/api/bots/buttons.html +++ /dev/null @@ -1,242 +0,0 @@ - - - - - Buttons - - - - - - - - - - - - - -
- -
-
-
- -

Buttons

- -
- -

Users can interact with your bot via buttons or even inline buttons, straight from inline messages in any chat.
-This article describes the full button flow, using the MTProto API.

-

For a simplified description using the HTTP bot API, see here ».

-

Buttons

-
keyboardButton#a2fa4880 text:string = KeyboardButton;
-keyboardButtonUrl#258aff05 text:string url:string = KeyboardButton;
-keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;
-keyboardButtonRequestPhone#b16a6c29 text:string = KeyboardButton;
-keyboardButtonRequestGeoLocation#fc796b3f text:string = KeyboardButton;
-keyboardButtonSwitchInline#568a748 flags:# same_peer:flags.0?true text:string query:string = KeyboardButton;
-keyboardButtonGame#50f41ccf text:string = KeyboardButton;
-keyboardButtonBuy#afd93fbb text:string = KeyboardButton;
-keyboardButtonUrlAuth#10b78d29 flags:# text:string fwd_text:flags.0?string url:string button_id:int = KeyboardButton;
-inputKeyboardButtonUrlAuth#d02e7fd4 flags:# request_write_access:flags.0?true text:string fwd_text:flags.1?string url:string bot:InputUser = KeyboardButton;
-keyboardButtonRequestPoll#bbc7515d flags:# quiz:flags.0?Bool text:string = KeyboardButton;
-
-keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;
-
-replyKeyboardHide#a03e5b85 flags:# selective:flags.2?true = ReplyMarkup;
-replyKeyboardForceReply#86b40b08 flags:# single_use:flags.1?true selective:flags.2?true placeholder:flags.3?string = ReplyMarkup;
-replyKeyboardMarkup#85dd99d1 flags:# resize:flags.0?true single_use:flags.1?true selective:flags.2?true rows:Vector<KeyboardButtonRow> placeholder:flags.3?string = ReplyMarkup;
-replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;
-
-message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
-
----functions---
-
-messages.sendMessage#520c3870 flags:# no_webpage:flags.1?true silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-

Bots can attach a ReplyMarkup constructor to outgoing messages, to attach an inline keyboard or a custom reply keyboard:

- -

Pressing buttons

-
keyboardButton#a2fa4880 text:string = KeyboardButton;
-keyboardButtonUrl#258aff05 text:string url:string = KeyboardButton;
-keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;
-keyboardButtonRequestPhone#b16a6c29 text:string = KeyboardButton;
-keyboardButtonRequestGeoLocation#fc796b3f text:string = KeyboardButton;
-keyboardButtonRequestPoll#bbc7515d flags:# quiz:flags.0?Bool text:string = KeyboardButton;
-keyboardButtonSwitchInline#568a748 flags:# same_peer:flags.0?true text:string query:string = KeyboardButton;
-keyboardButtonGame#50f41ccf text:string = KeyboardButton;
-keyboardButtonBuy#afd93fbb text:string = KeyboardButton;
-keyboardButtonUrlAuth#10b78d29 flags:# text:string fwd_text:flags.0?string url:string button_id:int = KeyboardButton;
-
-// Used by bots to send a keyboardButtonUrlAuth
-inputKeyboardButtonUrlAuth#d02e7fd4 flags:# request_write_access:flags.0?true text:string fwd_text:flags.1?string url:string bot:InputUser = KeyboardButton;
-
-keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;
-

Both reply and inline keyboards are composed of a vector of rows, each row containing a vector of buttons, for each column.
-Each row can have a different number of columns, and user clients should properly handle clicking buttons of every type.

-

Buttons available only in reply keyboards:

- -

Buttons available only in inline keyboards:

- -

Callback queries

-

keyboardButtonCallback buttons can be used to send the specified data payload back to the bot, when they are clicked.
-Additionally, a bot can verify a user's identity by requiring they verify their 2FA password with SRP.

-

Sending a callback query

-
keyboardButtonGame#50f41ccf text:string = KeyboardButton;
-keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;
-
-messages.botCallbackAnswer#36585ea4 flags:# alert:flags.1?true has_url:flags.3?true native_ui:flags.4?true message:flags.0?string url:flags.2?string cache_time:int = messages.BotCallbackAnswer;
-
----functions---
-
-messages.getBotCallbackAnswer#9342ca07 flags:# game:flags.1?true peer:InputPeer msg_id:int data:flags.0?bytes password:flags.2?InputCheckPasswordSRP = messages.BotCallbackAnswer;
-

When the user clicks on a keyboardButtonCallback in a message sent by a bot, or generated by an inline query, messages.getBotCallbackAnswer should be called, passing the peer and ID of the message.
-The same should happen when clicking on keyboardButtonGame buttons, with the difference that the game flag must be set instead of the data parameter.

-

Make sure to properly handle bot timeouts in the form of BOT_RESPONSE_TIMEOUT RPC errors, as the bot may be offline and unable to reply.

-

The returned messages.botCallbackAnswer constructor contains:

-
    -
  • message if specified, a message that should be shown in a non-blocking toast notification
  • -
  • alert indicates whether the message should be shown as a dismissable prompt, instead of a simple toast notification
  • -
  • has_url Whether an URL is present
  • -
  • url if specified, the client should open the URL, without showing a confirmation prompt.
    This is safe and allowed, because here, bots can only return:
      -
    • URLs to themselves with added query parameters (t.me/bot?start=aaa)
    • -
    • URLs to a valid game, if the bot has manually configured games, and the clicked button was a keyboardButtonGame.
    • -
    -
  • -
  • native_ui whether to open game URLs in a WebView or in native UI.
  • -
  • cache_time specifies for how long should this answer be cached, client-side
  • -
-
SRP verification
-

If the requires_password flag is set, the SRP 2FA payload must also be generated and attached to the query, to verify the identity of the user.

-

Note that the bot will NOT be able to access your password or the SRP payload.

-

The SRP payload will be processed exclusively on the Telegram's servers, simply returning an RPC error without passing the query to the bot if the verification fails.
-This is just a way of verifying the identity of the user, mainly used by the official @botfather bot to allow securely transferring the ownership of a bot to another user.

-

Answering a callback query

-
updateBotCallbackQuery#b9cfc48d flags:# query_id:long user_id:long peer:Peer msg_id:int chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
-
-updateInlineBotCallbackQuery#691e9052 flags:# query_id:long user_id:long msg_id:InputBotInlineMessageID chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
-
----functions---
-
-messages.setBotCallbackAnswer#d58f130a flags:# alert:flags.1?true query_id:long message:flags.0?string url:flags.2?string cache_time:int = Bool;
-

After the user invokes messages.getBotCallbackAnswer, an updateBotCallbackQuery or updateInlineBotCallbackQuery is generated and sent to the bot, depending on whether the query originated from a normal message sent by the bot, or from a message sent from an inline query.

-

Either way, bots must reply to the query as quickly as possible using messages.setBotCallbackAnswer:

- -

If a game_short_name is present in the update, the bot should return the URL of the game with the specified name.
-The messages.setBotCallbackAnswer method must be called anyway, even if no message or url is returned, to avoid timeouts on the client.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/bots/commands.html b/data/corefork.telegram.org/api/bots/commands.html deleted file mode 100644 index 4a0e8fd99d..0000000000 --- a/data/corefork.telegram.org/api/bots/commands.html +++ /dev/null @@ -1,140 +0,0 @@ - - - - - Commands - - - - - - - - - - - - - -
- -
-
-
- -

Commands

- -
- -

Bots offer a set of commands that can be used by users in private, or in a chat.

-

For a simplified description using the HTTP bot API, see here ».

-

Getting commands

-
botCommand#c27ac8c7 command:string description:string = BotCommand;
-
-botInfo#1b74b335 user_id:long description:string commands:Vector<BotCommand> = BotInfo;
-
-channelFull#e9b27a17 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector<string> groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string = ChatFull;
-userFull#d697ff05 flags:# blocked:flags.0?true phone_calls_available:flags.4?true phone_calls_private:flags.5?true can_pin_message:flags.7?true has_scheduled:flags.12?true video_calls_available:flags.13?true user:User about:flags.1?string settings:PeerSettings profile_photo:flags.2?Photo notify_settings:PeerNotifySettings bot_info:flags.3?BotInfo pinned_msg_id:flags.6?int common_chats_count:int folder_id:flags.11?int ttl_period:flags.14?int theme_emoticon:flags.15?string = UserFull;
-
-user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
-

The botInfo constructors contained in the userFull, chatFull, channelFull contain a list of commands, and for groups, the ID and a description of each bot.

-

In graphical clients, when users begin a message with a /, a list of commands supported by all bots present in the current chat should be shown; the same should be done for one-to-one chats with the bot itself.

-

If the command list of a bot changes, the bot_info_version contained in the user constructor received in updates will change; this indicates that the client should refetch full bot information using users.getFullUser.

-

Setting commands

-
botCommand#c27ac8c7 command:string description:string = BotCommand;
-
----functions---
-
-bots.setBotCommands#517165a scope:BotCommandScope lang_code:string commands:Vector<BotCommand> = Bool;
-

The command list can be changed by the owner of the bot through @botfather, but bots can also change their own command list by invoking bots.setBotCommands.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/bots/games.html b/data/corefork.telegram.org/api/bots/games.html deleted file mode 100644 index cbda184569..0000000000 --- a/data/corefork.telegram.org/api/bots/games.html +++ /dev/null @@ -1,171 +0,0 @@ - - - - - Games - - - - - - - - - - - - - -
- -
-
-
- -

Games

- -
- -

Bots can offer users HTML5 games to play solo or to compete against each other in groups and one-on-one chats.

-

Sending a game

-
inputUserSelf#f7c1b13f = InputUser;
-
-inputGameID#32c3e77 id:long access_hash:long = InputGame;
-inputGameShortName#c331e80a bot_id:InputUser short_name:string = InputGame;
-
-inputMediaGame#d33f43f3 id:InputGame = InputMedia;
-
-game#bdf9653b flags:# id:long access_hash:long short_name:string title:string description:string photo:Photo document:flags.0?Document = Game;
-messageMediaGame#fdb19008 game:Game = MessageMedia;
-
----functions---
-
-messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-

Bots can directly send a game using messages.sendMedia, providing:

-
    -
  • The bot's shortname obtained from @BotFather to inputGameShortName.short_name
  • -
  • The current bot's info to inputGameShortName.bot_id
  • -
-

The sent message will contain a messageMediaGame with a game, that can then be used by users to forward the game using sendMedia with inputGameID.

-

Starting a game

-

Games are started clicking on the button, which triggers an callback query that returns the game URL, for more info see here &raquo.
-The game should then be opened in a WebView or in native UI (specified by the native_ui flag), exposing the appropriate HTML5 APIs in order to receive various JS game events directly from the code of the game, as described here ».

-

Setting highscores

-
---functions---
-
-messages.setGameScore#8ef8ecc0 flags:# edit_message:flags.0?true force:flags.1?true peer:InputPeer id:int user_id:InputUser score:int = Updates;
-messages.setInlineGameScore#15ad9f64 flags:# edit_message:flags.0?true force:flags.1?true id:InputBotInlineMessageID user_id:InputUser score:int = Bool;
-

Games are supposed to report back to the MTProto API every time the user looses a game with a new highscore.
-Since games run in the browser, they cannot directly report data to the API using the bot token, which must be kept secret.
-Instead, they should send highscores to an intermediate server, that will then report scores using messages.setGameScore or messages.setInlineGameScore, depending on the source of the game.

-
    -
  • The edit_message flag should be set if the game message should be automatically edited to include the current scoreboard
  • -
  • The force flag should be set if the high score is allowed to decrease. This can be useful when fixing mistakes or banning cheaters.
  • -
-

Getting highscores

-
messageActionGameScore#92a72876 game_id:long score:int = MessageAction;
-
-messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;
-
-highScore#73a379eb pos:int user_id:long score:int = HighScore;
-
-messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;
-
----functions---
-
-messages.getGameHighScores#e822649d peer:InputPeer id:int user_id:InputUser = messages.HighScores;
-messages.getInlineGameHighScores#f635e1b id:InputBotInlineMessageID user_id:InputUser = messages.HighScores;
-

Every time a highscore is reached, and the edit_message flag is set when reporting the score, a messageService with a messageActionGameScore is generated, indicating that the highscore of a certain game has changed, thanks to a certain user_id.
-Our own current position of the scoreboard is also reported as pos.

-

When receiving such an update, graphical clients should refetch the scoreboard using messages.getGameHighScores or messages.getInlineGameHighScores.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/bots/inline.html b/data/corefork.telegram.org/api/bots/inline.html deleted file mode 100644 index 8daa00d149..0000000000 --- a/data/corefork.telegram.org/api/bots/inline.html +++ /dev/null @@ -1,215 +0,0 @@ - - - - - Inline - - - - - - - - - - - - - -
- -
-
-
-
-

Inline

- -
- -

Users can interact with your bot via inline queries, straight from the text input field in any chat.
-This article describes the full inline bot flow, using the MTProto API.

-

For a simplified description using the HTTP bot API, see here ».

-

Making an inline query

-
messages.botResults#947ca848 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;
-
----functions---
-
-messages.getInlineBotResults#514e999d flags:# bot:InputUser peer:InputPeer geo_point:flags.0?InputGeoPoint query:string offset:string = messages.BotResults;
-

When, in a graphical client, the user starts a message with an @, clients should:

-
    -
  • Use the cached top peer rating for inline bots to show a list of frequently used inline bots.
  • -
  • If the user chooses a bot from the recent bot list or:
  • -
  • Finishes typing a full username followed by a whitespace, and if the username resolves to a valid bot
  • -
  • messages.getInlineBotResults is called, with the following parameters:
      -
    • bot - The bot peer
    • -
    • peer - The chat where the user made the query
    • -
    • geo_point - The user's current geolocation, if the bot requires location-based inline results (the bot_inline_geo flag of the bot's user constructor will be set)
    • -
    • query - What the user typed after the bot's username
    • -
    • offset - If the user scrolls past the first len(results) results, and next_offset field is set, the inline query should be repeated with this offset.
    • -
    -
  • -
-

Answering to an inline query

-
inputBotInlineMessageMediaAuto#3380c786 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageText#3dcd7a87 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageMediaGeo#96929a85 flags:# geo_point:InputGeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageMediaVenue#417bbf11 flags:# geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageMediaContact#a6edbffd flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageGame#4b425864 flags:# reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-
-inputBotInlineResult#88bf9319 flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?InputWebDocument content:flags.5?InputWebDocument send_message:InputBotInlineMessage = InputBotInlineResult;
-inputBotInlineResultPhoto#a8d864a7 id:string type:string photo:InputPhoto send_message:InputBotInlineMessage = InputBotInlineResult;
-inputBotInlineResultDocument#fff8fdc4 flags:# id:string type:string title:flags.1?string description:flags.2?string document:InputDocument send_message:InputBotInlineMessage = InputBotInlineResult;
-inputBotInlineResultGame#4fa417f2 id:string short_name:string send_message:InputBotInlineMessage = InputBotInlineResult;
-
-updateBotInlineQuery#496f379c flags:# query_id:long user_id:long query:string geo:flags.0?GeoPoint peer_type:flags.1?InlineQueryPeerType offset:string = Update;
-
----functions---
-
-messages.setInlineBotResults#eb5ea206 flags:# gallery:flags.0?true private:flags.1?true query_id:long results:Vector<InputBotInlineResult> cache_time:int next_offset:flags.2?string switch_pm:flags.3?InlineBotSwitchPM = Bool;
-

Bots can answer to incoming updateBotInlineQuery updates using messages.setInlineBotResults.
-Just like its bot API counterpart, the method can be used to send a set of inline results to the user; see the constructor page for more info on the MTProto method parameters ».

-

In general, the method accepts a vector of InputBotInlineResult constructors, that when chosen, generates a message with optionally attached media, and even inline buttons.

-

Sending the inline query result

-
botInlineMessageMediaAuto#764cf810 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-botInlineMessageText#8c7f65e2 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-botInlineMessageMediaGeo#51846fd flags:# geo:GeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-botInlineMessageMediaVenue#8a86659c flags:# geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-botInlineMessageMediaContact#18d1cdc2 flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-
-botInlineResult#11965f3a flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?WebDocument content:flags.5?WebDocument send_message:BotInlineMessage = BotInlineResult;
-botInlineMediaResult#17db940b flags:# id:string type:string photo:flags.0?Photo document:flags.1?Document title:flags.2?string description:flags.3?string send_message:BotInlineMessage = BotInlineResult;
-
-messages.botResults#947ca848 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;
-
----functions---
-
-messages.sendInlineBotResult#220815b0 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true hide_via:flags.11?true peer:InputPeer reply_to_msg_id:flags.0?int random_id:long query_id:long id:string schedule_date:flags.10?int = Updates;
-

The user client should display the results obtained during querying in a list, making sure to handle eventual bot timeouts in the form of a BOT_RESPONSE_TIMEOUT RPC error, by simply not displaying anything.

-

If the user then chooses a specific BotInlineResult, the messages.sendInlineBotResult method should be invoked, passing:

-
    -
  • The query_id from messages.botResults
  • -
  • The id of the chosen result
  • -
  • The peer where to send the chosen result
  • -
-

The resulting message will have the via_bot_id field set, to indicate that the result was generated by the bot that generated the inline result.
-Graphical clients should display the bot @username in the header of the message, allowing the user to click on it, automatically starting an inline query by inserting @username in the text bar.

-

Inline feedback

-
inputBotInlineMessageID#890c3d89 dc_id:int id:long access_hash:long = InputBotInlineMessageID;
-
-updateBotInlineSend#12f12a07 flags:# user_id:long query:string geo:flags.0?GeoPoint id:string msg_id:flags.1?InputBotInlineMessageID = Update;
-

If feedback collection is enabled, the bot may receive an updateBotInlineSend when the user chooses and sends an inline result.

-

Even if the probability setting is set to 100%, not all inline results may be reported due to caching (see the cache_time parameter in Answering a callback query).
-Feedback collection can also create load issues for popular bots, so adjust the probability setting to a lower value in such cases.

-

Either way, feedback collection should only be used for statistical purposes rather than functional.

-

The updateBotInlineSend will contain:

-
    -
  • id - The ID of the chosen result
  • -
  • msg_id - The ID of the sent inline message
  • -
  • user_id - The ID of the user that chose the result
  • -
  • query - The query string that was used to obtain the result
  • -
  • geo - For bots requiring location-based inline results, the user's location
  • -
-

Editing sent inline messages

-
updateInlineBotCallbackQuery#691e9052 flags:# query_id:long user_id:long msg_id:InputBotInlineMessageID chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
-
-inputBotInlineMessageID#890c3d89 dc_id:int id:long access_hash:long = InputBotInlineMessageID;
-
----functions---
-
-messages.editInlineBotMessage#83557dba flags:# no_webpage:flags.1?true id:InputBotInlineMessageID message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> = Bool;
-

Sent inline messages can be edited by the bot, for example in response to a button press callback query.

-

Simply pass the inputBotInlineMessageID specified in the updateInlineBotCallbackQuery to messages.editInlineBotMessage along with the new message, making sure to send the query to the datacenter specified in inputBotInlineMessageID.dc_id.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/channel.html b/data/corefork.telegram.org/api/channel.html deleted file mode 100644 index dadc7ad4f6..0000000000 --- a/data/corefork.telegram.org/api/channel.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - Channels - - - - - - - - - - - - - -
- -
-
-
- -

Channels

- -
- -

Channels, chats, supergroups & gigagroups

-

Channels are a tool for broadcasting your messages to large audiences. They can have an unlimited number of subscribers, they can be public with a permanent URL and each post in a channel has its own view counter.
-Technically, they are represented by channel constructors.

-

Supergroups are a powerful tool for building communities and can support up to 200,000 members each.
-Technically, supergroups are actually channels: they are represented by channel constructors, with the megagroup flag set to true.

-

Gigagroups are something inbetween a channel and a supergroup.
-An admin, when prompted by the API using suggestions », can convert a megagroup into a gigagroup using channels.convertToGigagroup (one way only).
-After that, only admins will be able to write in the group (like when send_messages rights are disabled for all group participants by default), but the participant limit is removed and the group can become much bigger than a supergroup (e.g. >200,000 currently).
-Also, one can't invite people into gigagroups and participants of voice chats in gigagroups are muted by default.

-

Channels and supergroups can be created using the channels.createChannel method, by setting the appropriate broadcast or megagroup flags.
-Supergroups can also be assigned a geo_point to become geochats.

-

In previous versions of telegram, only normal groups (represented by chat constructors) could be created using messages.createChat: these groups have fewer features, and can only have 200 members at max.

-

Migration

-

To upgrade a legacy group to a supergroup, messages.migrateChat can be used. -The chats field of the result will have two objects:

-
    -
  • A chat constructor with a migrated_to field, indicating the address of the new supergroup
  • -
  • The new channel megagroup constructor
  • -
-

When getting full info about the migrated channel, the channelFull object will have migrated_from_chat_id and migrated_from_max_id fields indicating the original ID of the chat, and the message ID in the original chat at which the group was migrated.

-

All users of the chat will receive an updateNewMessage from the old chat with a messageService containing a messageActionChatMigrateTo constructor.

-

All new messages have to be sent to the new supergroup.

-

When working with migrated groups clients need to handle loading of the message history (as well as search results et cetera) from both the legacy group and the new supergroup. This is done by merging the two messages lists (requested with different Peer values) client side.

-

Rights

-

Channels, legacy groups and supergroups allow setting granular permissions both for admins and specific users; channels, supergroups and legacy groups also allow setting global granular permissions for users.

-

For more info on how to set and modify rights, see here ».

-

Pinned messages

-

Telegram allows pinning multiple messages on top in a chat, group, supergroup or channel.

-

See here » for more info on pinning and unpinning messages.

-

Discussion

-

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

-

For more info on how to set a discussion group in channel, see here »

-

Recent actions

-

Both supergroups and channels offer a so-called admin log, a log of recent relevant supergroup and channel actions, like the modification of group/channel settings or information on behalf of an admin, user kicks and bans, and more.

-

See here » for more info.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/config.html b/data/corefork.telegram.org/api/config.html deleted file mode 100644 index 7cc87667f9..0000000000 --- a/data/corefork.telegram.org/api/config.html +++ /dev/null @@ -1,422 +0,0 @@ - - - - - Client configuration - - - - - - - - - - - - - -
- -
-
-
- -

Client configuration

- -
- -

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

-

MTProto configuration

-
config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;
-nearestDc#8e1a1775 country:string this_dc:int nearest_dc:int = NearestDc;
-
----functions---
-
-help.getConfig#c4f9186b = Config;
-help.getNearestDc#1fb33026 = NearestDc;
-

The huge config constructor contains lots of useful information, from chat and message size limitations, to privacy settings, online status refresh interval and timeout, VoIP configuration, default inline bot usernames for GIF, image and venue lookup, and lots of other global and user-specific information, check out the constructor page for more information.

-

Client configuration

-
jsonObjectValue#c0de1bd9 key:string value:JSONValue = JSONObjectValue;
-
-jsonNull#3f6d7b68 = JSONValue;
-jsonBool#c7345e6a value:Bool = JSONValue;
-jsonNumber#2be0dfa4 value:double = JSONValue;
-jsonString#b71e767a value:string = JSONValue;
-jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;
-jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;
-
----functions---
-
-help.getAppConfig#98914110 = JSONValue;
-

The help.getAppConfig method returns a JSON object containing rapidly evolving, client-specific configuration parameters.
-While help.getConfig returns MTProto-specific configuration with information about server-side limitations and other MTProto-related information, help.getAppConfig returns configuration parameters useful for graphical Telegram clients.

-

Typical fields included in the resulting JSON object are:

-
    -
  • emojies_animated_zoom - Animated emojis and animated dice should be scaled by this factor before being shown to the user (float)
  • -
  • keep_alive_service - Whether app clients should start a keepalive service to keep the app running and fetch updates even when the app is closed (boolean)
  • -
  • background_connection - Whether app clients should start a background TCP connection for MTProto update fetching (boolean)
  • -
  • emojies_send_dice - A list of supported animated dice stickers (array of strings).
  • -
  • emojies_send_dice_success - For animated dice emojis other than the basic 🎲, indicates the winning dice value and the final frame of the animated sticker, at which to show the fireworks 🎆 (object with emoji keys and object values, containing value and frame_start float values)
  • -
  • emojies_sounds - A map of soundbites to be played when the user clicks on the specified animated emoji; the file reference field should be base64-decoded before downloading the file (map of file IDs, with emoji string keys)
  • -
  • gif_search_branding - Specifies the name of the service providing GIF search through gif_search_username (string)
  • -
  • gif_search_emojies - Specifies a list of emojies that should be suggested as search term in a bar above the GIF search box (array of string emojis)
  • -
  • stickers_emoji_suggest_only_api - Specifies that the app should not display local sticker suggestions for emojis at all and just use the result of messages.getStickers (bool)
  • -
  • stickers_emoji_cache_time - Specifies the validity period of the local cache of messages.getStickers, also relevant when generating the pagination hash when invoking the method. (int)
  • -
  • qr_login_camera - Whether the Settings->Devices menu should show an option to scan a QR login code (boolean)
  • -
  • qr_login_code - Whether the login screen should show a QR code login option, possibly as default login method (string, "disabled", "primary" or "secondary")
  • -
  • dialog_filters_enabled - Whether clients should show an option for managing dialog filters AKA folders (boolean)
  • -
  • dialog_filters_tooltip - Whether clients should actively show a tooltip, inviting the user to configure dialog filters AKA folders; typically this happens when the chat list is long enough to start getting cluttered. (boolean)
  • -
  • autoarchive_setting_available - Whether clients can invoke account.setGlobalPrivacySettings with globalPrivacySettings.archive_and_mute_new_noncontact_peers = boolTrue, to automatically archive and mute new incoming chats from non-contacts. (boolean)
  • -
  • pending_suggestions - Contains a list of suggestions that should be actively shown as a tooltip to the user. (Array of strings, possible values shown in the suggestions section ».
  • -
  • url_auth_domains - A list of domains that support automatic login with manual user confirmation, click here for more info on URL authorization ». (array of strings)
  • -
  • autologin_domains - A list of Telegram domains that support automatic login with no user confirmation, click here for more info on URL authorization ». (array of strings)
  • -
  • autologin_token - Autologin token, click here for more info on URL authorization ». (string)
  • -
  • round_video_encoding - Contains a set of recommended codec parameters for round videos.
  • -
  • chat_read_mark_size_threshold - Per-user read receipts, fetchable using messages.getMessageReadParticipants will be available in groups with less than chat_read_mark_size_threshold participants. (int)
  • -
  • chat_read_mark_expire_period - To protect user privacy, read receipts are only stored for chat_read_mark_expire_period seconds after the message was sent. (int)
  • -
-

Example value:

-
{
-    "test": 1,
-    "emojies_animated_zoom": 0.625,
-    "emojies_send_dice": [
-        "\ud83c\udfb2",
-        "\ud83c\udfaf",
-        "\ud83c\udfc0",
-        "\u26bd",
-        "\u26bd\ufe0f",
-        "\ud83c\udfb0",
-        "\ud83c\udfb3"
-    ],
-    "emojies_send_dice_success": {
-        "\ud83c\udfaf": {
-            "value": 6,
-            "frame_start": 62
-        },
-        "\ud83c\udfc0": {
-            "value": 5,
-            "frame_start": 110
-        },
-        "\u26bd": {
-            "value": 5,
-            "frame_start": 110
-        },
-        "\u26bd\ufe0f": {
-            "value": 5,
-            "frame_start": 110
-        },
-        "\ud83c\udfb0": {
-            "value": 64,
-            "frame_start": 110
-        },
-        "\ud83c\udfb3": {
-            "value": 6,
-            "frame_start": 110
-        }
-    },
-    "emojies_sounds": {
-        "\ud83c\udf83": {
-            "id": "4956223179606458539",
-            "access_hash": "-2107001400913062971",
-            "file_reference_base64": "AGFhvoKbftK5O9K9RpgN1ZtgSzWy"
-        },
-        "\u26b0": {
-            "id": "4956223179606458540",
-            "access_hash": "-1498869544183595185",
-            "file_reference_base64": "AGFhvoJIm8Uz0qSMIdm3AsKlK7wJ"
-        },
-        "\ud83e\udddf\u200d\u2642": {
-            "id": "4960929110848176331",
-            "access_hash": "3986395821757915468",
-            "file_reference_base64": "AGFhvoLtXSSIclmvfg6ePz3KsHQF"
-        },
-        "\ud83e\udddf": {
-            "id": "4960929110848176332",
-            "access_hash": "-8929417974289765626",
-            "file_reference_base64": "AGFhvoImaz5Umt4GvMUD5nocIu0W"
-        },
-        "\ud83e\udddf\u200d\u2640": {
-            "id": "4960929110848176333",
-            "access_hash": "9161696144162881753",
-            "file_reference_base64": "AGFhvoIm1QZsb48xlpRfh4Mq7EMG"
-        },
-        "\ud83c\udf51": {
-            "id": "4963180910661861548",
-            "access_hash": "-7431729439735063448",
-            "file_reference_base64": "AGFhvoKLrwl_WKr5LR0Jjs7o3RyT"
-        },
-        "\ud83c\udf8a": {
-            "id": "5094064004578410732",
-            "access_hash": "8518192996098758509",
-            "file_reference_base64": "AGFhvoKMNffRV2J3vKED0O6d8e42"
-        },
-        "\ud83c\udf84": {
-            "id": "5094064004578410733",
-            "access_hash": "-4142643820629256996",
-            "file_reference_base64": "AGFhvoJ1ulPBbXEURlTZWwJFx6xZ"
-        },
-        "\ud83e\uddbe": {
-            "id": "5094064004578410734",
-            "access_hash": "-8934384022571962340",
-            "file_reference_base64": "AGFhvoL4zdMRmYv9z3L8KPaX4JQL"
-        }
-    },
-    "gif_search_branding": "tenor",
-    "gif_search_emojies": [
-        "\ud83d\udc4d",
-        "\ud83d\ude18",
-        "\ud83d\ude0d",
-        "\ud83d\ude21",
-        "\ud83e\udd73",
-        "\ud83d\ude02",
-        "\ud83d\ude2e",
-        "\ud83d\ude44",
-        "\ud83d\ude0e",
-        "\ud83d\udc4e"
-    ],
-    "stickers_emoji_suggest_only_api": false,
-    "stickers_emoji_cache_time": 86400,
-    "qr_login_camera": false,
-    "qr_login_code": "disabled",
-    "dialog_filters_enabled": true,
-    "dialog_filters_tooltip": false,
-    "autoarchive_setting_available": false,
-    "pending_suggestions": [
-        "AUTOARCHIVE_POPULAR",
-        "VALIDATE_PASSWORD",
-        "VALIDATE_PHONE_NUMBER",
-        "NEWCOMER_TICKS"
-    ],
-    "autologin_token": "string",
-    "autologin_domains": [
-        "instantview.telegram.org",
-        "translations.telegram.org",
-        "contest.dev",
-        "contest.com",
-        "bugs.telegram.org",
-        "suggestions.telegram.org",
-        "themes.telegram.org"
-    ],
-    "url_auth_domains": [
-        "somedomain.telegram.org"
-    ],
-    "round_video_encoding": {
-        "diameter": 384,
-        "video_bitrate": 1000,
-        "audio_bitrate": 64,
-        "max_size": 12582912
-    },
-    "chat_read_mark_size_threshold": 50,
-    "chat_read_mark_expire_period": 604800
-}
-

Suggestions

-

The API can return a set of useful suggestions for users of graphical clients.

-

Basic suggestions

-
jsonObjectValue#c0de1bd9 key:string value:JSONValue = JSONObjectValue;
-
-jsonNull#3f6d7b68 = JSONValue;
-jsonBool#c7345e6a value:Bool = JSONValue;
-jsonNumber#2be0dfa4 value:double = JSONValue;
-jsonString#b71e767a value:string = JSONValue;
-jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;
-jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;
-
----functions---
-
-help.getAppConfig#98914110 = JSONValue;
-

The help.getAppConfig method returns a JSON object containing rapidly evolving, client-specific configuration parameters.
-A full list of these parameters can be seen in the Client Configuration section », but we're mostly interested in the pending_suggestions and autoarchive_setting_available fields of the returned JSON object:

- -

Channel suggestions

-
messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.ChatFull;
-
-channelFull#e9b27a17 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector<string> groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string = ChatFull;
-
----functions---
-
-channels.getFullChannel#8736a09 channel:InputChannel = messages.ChatFull;
-

Some channel/supergroup-related suggestions can also be contained in the pending_suggestions field of the channelFull constructor, returned by channels.getFullChannel.
-Here's a list of possible suggestions:

- -

Dismissing suggestions

-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
-
----functions---
-
-help.dismissSuggestion#f50dbaa1 peer:InputPeer suggestion:string = Bool;
-

help.dismissSuggestion can be used to dismiss a suggestion.
-Pass inputPeerEmpty to peer for basic suggestions and the channel/supergroup's peer for channel suggestions.

-

App-specific configuration

-
help.appUpdate#ccbbce30 flags:# can_not_skip:flags.0?true id:int version:string text:string entities:Vector<MessageEntity> document:flags.1?Document url:flags.2?string sticker:flags.3?Document = help.AppUpdate;
-help.noAppUpdate#c45a6536 = help.AppUpdate;
-
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateServiceNotification#ebe46819 flags:# popup:flags.0?true inbox_date:flags.1?int type:string message:string media:MessageMedia entities:Vector<MessageEntity> = Update;
-
-help.inviteText#18cb9f78 message:string = help.InviteText;
-
----functions---
-
-help.getAppUpdate#522d5a7d source:string = help.AppUpdate;
-help.getAppChangelog#9010ef6f prev_app_version:string = Updates;
-
-help.getInviteText#4d392343 = help.InviteText;
-
    -
  • help.getAppUpdate - Get info about an application update, can contain the updated application binary in the attached document
  • -
  • help.getAppChangelog - Get a list of service messages with app-specific changelogs
  • -
  • help.getInviteText - Returns a localized invitation message that can be sent via SMS to contacts that haven't signed up to Telegram yet
  • -
-

Terms of service

-
help.termsOfServiceUpdateEmpty#e3309f7f expires:int = help.TermsOfServiceUpdate;
-help.termsOfServiceUpdate#28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate;
-
-help.termsOfService#780a0310 flags:# popup:flags.0?true id:DataJSON text:string entities:Vector<MessageEntity> min_age_confirm:flags.1?int = help.TermsOfService;
-
-auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
-
----functions---
-
-help.getTermsOfServiceUpdate#2ca51fd1 = help.TermsOfServiceUpdate;
-help.acceptTermsOfService#ee72f79a id:DataJSON = Bool;
-
-auth.signIn#bcd51581 phone_number:string phone_code_hash:string phone_code:string = auth.Authorization;
-
-account.deleteAccount#418d4e0b reason:string = Bool;
-

These methods can be used for managing consent to Telegram's Terms Of Service.

-

Typically, before a user signs up by invoking auth.signUp, apps should show a pop-up (if the popup flag of the help.termsOfService method is set), asking the user to accept Telegram's terms of service; in case of denial, the user is to be returned to the initial page of the login flow.

-

When signing up for the first time, the help.termsOfService is to be obtained from the auth.authorizationSignUpRequired constructor returned by the auth.signIn.

-

After signing up, or when logging in as an existing user, apps are supposed to call help.getTermsOfServiceUpdate to check for any updates to the Terms of Service; this call should be repeated after expires seconds have elapsed.
-If an update to the Terms Of Service is available, clients are supposed to show a consent popup; if accepted, clients should call help.acceptTermsOfService, providing the termsOfService id JSON object; in case of denial, clients are to delete the account using account.deleteAccount, providing Decline ToS update as deletion reason.

-

Example implementation: android (signup), android (after login)

-

Telegram support info

-
user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
-
-help.support#17c6b5f6 phone_number:string user:User = help.Support;
-help.supportName#8c05f1c9 name:string = help.SupportName;
-
----functions---
-
-help.getSupport#9cdf08cd = help.Support;
-help.getSupportName#d360e72c = help.SupportName;
-

These methods can be used for fetching info about Telegram's support user, that users can use to get support and ask questions about the app.

- -

Country information and login phone patterns

-
help.countryCode#4203c5ef flags:# country_code:string prefixes:flags.0?Vector<string> patterns:flags.1?Vector<string> = help.CountryCode;
-
-help.country#c3878e23 flags:# hidden:flags.0?true iso2:string default_name:string name:flags.1?string country_codes:Vector<help.CountryCode> = help.Country;
-
-help.countriesListNotModified#93cc1f32 = help.CountriesList;
-help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;
-
----functions---
-help.getCountriesList#735787a8 lang_code:string hash:int = help.CountriesList;
-

help.getCountriesList can be used to fetch a list of localized names for all available countries and phone code patterns for logging in.

-

The phone code pattern should be used when showing the login screen, or when changing phone number: for example, a pattern value of XXX XXX XXX with country_code +39 indicates that the phone field for login should accept a spaced pattern like +39 123 456 789.
-Also, the beginning of the national part of the phone number (123 456 789) should match one of the prefixes, if any were returned.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/datacenter.html b/data/corefork.telegram.org/api/datacenter.html deleted file mode 100644 index b6e3c15dbb..0000000000 --- a/data/corefork.telegram.org/api/datacenter.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - Working with Different Data Centers - - - - - - - - - - - - - -
- -
-
-
- -

Working with Different Data Centers

- -

The servers are divided into several data centers (hereinafter “DCs”) in different parts of the world.
A complete list of proxy access points for these DCs may be obtained using help.getConfig:

-
dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;
-config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;
----functions---
-help.getConfig#c4f9186b = Config;
-

In this context, this_dc is the number of the current DC, dc_options is a list of all DCs available at the moment, each of which has an id, ip, and port for establishing a connection. Please note that ip and port may change frequently, based on proxy server load and the user's current location.
Typically, each DC has at least one IPv4 and one IPv6 endpoint available.

-

To optimize client communication with the API, each client must use the connection to the closest access point for its main queries (sending messages, getting contacts, etc.). Therefore, knowing how to select a DC is required before communicating with the API.

-

Registration/Authorization

-

The auth.sendCode method is the basic entry point when registering a new user or authorizing an existing user. 95% of all redirection cases to a different DC will occur when invoking this method.

-

The client does not yet know which DC it will be associated with; therefore, it establishes an encrypted connection to a random address and sends its query to that address.
Having received a phone_number from a client, we can find out whether or not it is registered in the system. If it is, then, if necessary, instead of sending a text message, we request that it establish a connection with a different DC first (PHONE_MIGRATE_X error).
If we do not yet have a user with this number, we examine its IP-address. We can use it to identify the closest DC. Again, if necessary, we redirect the user to a different DC (NETWORK_MIGRATE_X error).

-

Testing Redirects

-

There are reserved phone number prefixes to test the correctness of the application’s handling of redirects between DCs. Read more in User Authorization article.

-

File Access

-

A file saved by a user with upload.saveFilePart will be available for direct download only from the DC where the query was executed. That is why each file has a dc_id parameter:

-
document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
-photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;
-
-encryptedFile#4a70994c id:long access_hash:long size:int dc_id:int key_fingerprint:int = EncryptedFile;
-
-userProfilePhoto#82d1f706 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = UserProfilePhoto;
-chatPhoto#1c6e1c11 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = ChatPhoto;
-

To download the file, an encrypted connection to DC dc_id must be established and used to execute the upload.getFile query.
If an attempt is made to download the file over a wrong connection, the FILE_MIGRATE_X error will be returned.

-

Please note that encryption keys are not copied between DCs; therefore, the process of establishing an encrypted connection is started from the very beginning for each new DC. An issued auth_key can be associated with the current authorized user by using an authorization transfer.

-

User Migration

-

During the process of working with the API, user information is accumulated in the DC with which the user is associated. This is the reason a user cannot be associated with a different DC by means of the client. However, in the future, during prolonged communication from an unusual location, we may decide that the user’s data must be moved to a different DC. After some time, the data will be copied and the association will be updated. Once this happens, when executing any query transmitted to the old DC, the API will return the USER_MIGRATE_X error. The client will then have to establish a connection with the new DC and repeat the query.

-

Authorization Transfer

-

The following methods can be used to eliminate the need for users to enter the code from a text message every time:

-
auth.exportedAuthorization#b434e2b8 id:long bytes:bytes = auth.ExportedAuthorization;
-auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
----functions---
-auth.importAuthorization#a57a7dad id:long bytes:bytes = auth.Authorization;
-auth.exportAuthorization#e5bfffcd dc_id:int = auth.ExportedAuthorization;
-

auth.exportAuthorization must be executed in the current DC (the DC with which a connection has already been established), passing in dc_id as the value for the new DC. The method should return the user identifier and a long string of random data. An import operation can be performed at the new DC by sending it what was received. Queries requiring authorization can then be successfully executed in the new DC.

-
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/api/dice.html b/data/corefork.telegram.org/api/dice.html deleted file mode 100644 index 89db5f5186..0000000000 --- a/data/corefork.telegram.org/api/dice.html +++ /dev/null @@ -1,149 +0,0 @@ - - - - - Dice - - - - - - - - - - - - - -
- -
-
-
- -

Dice

- -

Telegram supports sending animated dice emojis.
-This is implemented by using the dice constructors:

-
inputMediaDice#e66fbf7b emoticon:string = InputMedia;
-messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;
-
-inputStickerSetDice#e67f520e emoticon:string = InputStickerSet;
-
-messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
-
----functions---
-
-messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-
-messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;
-
-help.getAppConfig#98914110 = JSONValue;
-

On startup, clients should fetch app configuration using help.getAppConfig.
-Then, for each dice emoji contained in the emojies_send_dice field, clients should fetch the dice emoji stickerset by calling the messages.getStickerSet method, providing the properly populated inputStickerSetDice to the stickerset field.
-The returned stickerset will contain a set of animated stickers, one for each of the dice outcomes, plus a first looping sticker that should be shown as preview to the user before actually sending the dice.

-

If a user attempts to send a single emoji from the ones specified in emojies_send_dice, the dice should be sent using messages.sendMedia, providing the dice emoji to the emoticon field.

-

Incoming dice stickers will be received as a messageMediaDice constructor, along with a randomly generated server-side value, ranging from 1 to the maximum allowed value for this type of dice.
-Clients should display the correct dice animated sticker for the specified value: since dice values start from 1, and the first animated sticker in dice stickerset is the preview, value can be used to directly index the documents sticker array from the animated stickerset.

-

The emojies_send_dice_success configuration parameter contains more info about dice emojis other than the basic 🎲:

-
    "emojies_send_dice_success": {
-        "\ud83c\udfaf": {
-            "value": 6,
-            "frame_start": 62
-        },
-        "\ud83c\udfc0": {
-            "value": 5,
-            "frame_start": 110
-        }
-    }
-

For each of the dice emojis, a maximum "winning" value is specified, along with the frame number at which to show the fireworks 🎆.
-Please note that dice animated stickers should loop only once, right after being sent/received for the first time; clicking on the dice sticker should bring up a popup, inviting the user to send a new dice of the same type.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/api/discussion.html b/data/corefork.telegram.org/api/discussion.html deleted file mode 100644 index 70271a7f45..0000000000 --- a/data/corefork.telegram.org/api/discussion.html +++ /dev/null @@ -1,151 +0,0 @@ - - - - - Discussion groups - - - - - - - - - - - - - -
- -
-
-
- -

Discussion groups

- -
- -

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
-
-channelFull#e9b27a17 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector<string> groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string = ChatFull;
-
-messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
-
----functions---
-
-channels.setDiscussionGroup#40582bb2 broadcast:InputChannel group:InputChannel = Bool;
-channels.getGroupsForDiscussion#f5dad378 = messages.Chats;
-

A discussion group can be associated to a channel using channels.setDiscussionGroup.
-The discussion group can be accessed in the client by clicking on the discuss button of the channel, or by accessing the comment section of a specific post; the discussion group ID is also present in the linked_chat_id field of the channelFull constructor.

-

All messages sent to the channel will also be sent to the linked group (with sender peer from_id equal to the peer of the linked channel); those messages will also be automatically pinned in the group.

-

Linking a discussion group

-

To obtain a list of admined supergroups that a channel admin can possibly associate to a channel, use channels.getGroupsForDiscussion.
-Returned legacy group chats must be first upgraded to supergroups before they can be set as a discussion group.
-Before linking a supergroup to a channel, access to the supergroup's old messages must also be enabled using channels.togglePreHistoryHidden.

-

To set a returned supergroup as a discussion group use channels.setDiscussionGroup.

-

Schema:

-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
-
-messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
-
----functions---
-
-channels.setDiscussionGroup#40582bb2 broadcast:InputChannel group:InputChannel = Bool;
-channels.getGroupsForDiscussion#f5dad378 = messages.Chats;
-
-channels.togglePreHistoryHidden#eabbb94c channel:InputChannel enabled:Bool = Updates;
- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/drafts.html b/data/corefork.telegram.org/api/drafts.html deleted file mode 100644 index 8770c19a7e..0000000000 --- a/data/corefork.telegram.org/api/drafts.html +++ /dev/null @@ -1,131 +0,0 @@ - - - - - Message drafts - - - - - - - - - - - - - -
- -
-
-
- -

Message drafts

- -
- -

Message drafts in Telegram allow syncing the text typed into message fields between devices.

-

Drafts

-

Drafts are represented by the DraftMessage constructors. -The parameters of the peer-specific draft should be used as defaults when composing a message to be sent to a certain peer (in the case of media, the same draft should still be used as base, the message will become the caption). -If the user exits the app before sending the message, the message should be saved as a draft:

-

Saving drafts

-

Drafts can be saved using the messages.saveDraft method.

-

Downloading drafts

-

New drafts are automatically sent to all devices via updateDraftMessage updates.

-

Dialog objects fetched via the API also contain the draft associated with the dialog.

-

Clearing drafts

-

Drafts can be cleared by setting the clear_draft flag when sending messages or media using messages.sendMessage, messages.sendMedia, messages.sendMultiMedia, messages.sendInlineBotResult and similar or manually by passing empty values to messages.saveDraft.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/end-to-end.html b/data/corefork.telegram.org/api/end-to-end.html deleted file mode 100644 index 27fd5216fd..0000000000 --- a/data/corefork.telegram.org/api/end-to-end.html +++ /dev/null @@ -1,244 +0,0 @@ - - - - - End-to-End Encryption, Secret Chats - - - - - - - - - - - - - -
- -
-
-
- -

End-to-End Encryption, Secret Chats

- -
- -
-

This article on MTProto's End-to-End encryption is meant for advanced users. -If you want to learn more about Secret Chats from a less intimidating source, kindly see our general FAQ.

-
-
-

Note that as of version 4.6, major Telegram clients are using MTProto 2.0. -MTProto v.1.0 is deprecated and is currently being phased out.

-
-
-
Related articles
-

-
-

Secret Chats are one-on-one chats wherein messages are encrypted with a key held only by the chat’s participants. Note that the schema for these end-to-end encrypted Secret Chats is different from what is used for cloud chats:

-
- -
-

A note on MTProto 2.0

-

This article describes the end-to-end encryption layer in the MTProto protocol version 2.0. -The principal differences from version 1.0 (described here for reference) are as follows:

-
    -
  • SHA-256 is used instead of SHA-1;
  • -
  • Padding bytes are involved in the computation of msg_key;
  • -
  • msg_key depends not only on the message to be encrypted, but on a portion of the secret chat key as well;
  • -
  • 12..1024 padding bytes are used instead of 0..15 padding bytes in v.1.0.
  • -
-

See also: MTProto 2.0: Cloud Chats, server-client encryption

-

Key Generation

-

Keys are generated using the Diffie-Hellman protocol.

-

Let us consider the following scenario: User A would like to initiate end-to-end encrypted communication with User B.

-

Sending a Request

-

User A executes messages.getDhConfig to obtain the Diffie-Hellman parameters: a prime p, and a high order element g.

-

Executing this method before each new key generation procedure is of vital importance. It makes sense to cache the values of the parameters together with the version in order to avoid having to receive all of the values every time. If the version stored on the client is still up-to-date, the server will return the constructor messages.dhConfigNotModified.

-

Client is expected to check whether p is a safe 2048-bit prime (meaning that both p and (p-1)/2 are prime, and that 2^2047 < p < 2^2048), and that g generates a cyclic subgroup of prime order (p-1)/2, i.e. is a quadratic residue mod p. Since g is always equal to 2, 3, 4, 5, 6 or 7, this is easily done using quadratic reciprocity law, yielding a simple condition on p mod 4g -- namely, p mod 8 = 7 for g = 2; p mod 3 = 2 for g = 3; no extra condition for g = 4; p mod 5 = 1 or 4 for g = 5; p mod 24 = 19 or 23 for g = 6; and p mod 7 = 3, 5 or 6 for g = 7. After g and p have been checked by the client, it makes sense to cache the result, so as to avoid repeating lengthy computations in future. This cache might be shared with one used for Authorization Key generation.

-

If the client needs additional entropy for the random number generator, it can pass the random_length parameter (random_length> 0) so the server generates its own random sequence random of the appropriate length. -Important: using the server’s random sequence in its raw form may be unsafe, it must be combined with a client sequence.

-

Client A computes a 2048-bit number a (using sufficient entropy or the server’s random; see above) and executes messages.requestEncryption after passing in g_a := pow(g, a) mod dh_prime.

-

User B receives the update updateEncryption for all associated authorization keys (all authorized devices) with the chat constructor encryptedChatRequested. The user must be shown basic information about User A and must be prompted to accept or reject the request.

-

Both clients are to check that g, g_a and g_b are greater than one and smaller than p-1. We recommend checking that g_a and g_b are between 2^{2048-64} and p - 2^{2048-64} as well.

-

Accepting a Request

-

After User B confirms the creation of a secret chat with A in the client interface, Client B also receives up-to-date configuration parameters for the Diffie-Hellman method. Thereafter, it generates a random 2048-bit number, b, using rules similar to those for a.

-

Having received g_a from the update with encryptedChatRequested, it can immediately generate the final shared key: key = (pow(g_a, b) mod dh_prime). If key length < 256 bytes, add several leading zero bytes as padding — so that the key is exactly 256 bytes long. Its fingerprint, key_fingerprint, is equal to the 64 last bits of SHA1 (key).

-

Note 1: in this particular case SHA1 is used here even for MTProto 2.0 secret chats.

-

Note 2: this fingerprint is used as a sanity check for the key exchange procedure to detect bugs when developing client software — it is not connected to the key visualization used on the clients as means of external authentication in secret chats. Key visualizations on the clients are generated using the first 128 bits of SHA1(initial key) followed by the first 160 bits of SHA256(key used when secret chat was updated to layer 46).

-

Client B executes messages.acceptEncryption after passing it g_b := pow(g, b) mod dh_prime and key_fingerprint.

-

For all of Client B’s authorized devices, except the current one, updateEncryption updates are sent with the constructor encryptedChatDiscarded. Thereafter, the only device that will be able to access the secret chat is Device B, which made the call to messages.acceptEncryption.

-

User A will be sent an updateEncryption update with the constructor encryptedChat, for the authorization key that initiated the chat.

-

With g_b from the update, Client A can also compute the shared key key = (pow(g_b, a) mod dh_prime). If key length < 256 bytes, add several leading zero bytes as padding — so that the key is exactly 256 bytes long. If the fingerprint for the received key is identical to the one that was passed to encryptedChat, incoming messages can be sent and processed. Otherwise, messages.discardEncryption must be executed and the user notified.

-

Perfect Forward Secrecy

-

In order to keep past communications safe, official Telegram clients will initiate re-keying once a key has been used to decrypt and encrypt more than 100 messages, or has been in use for more than one week, provided the key has been used to encrypt at least one message. Old keys are then securely discarded and cannot be reconstructed, even with access to the new keys currently in use.

-
-

The re-keying protocol is further described in this article: Perfect Forward Secrecy in Secret Chats.

-
-

Please note that your client must support Forward Secrecy in Secret Chats to be compatible with official Telegram clients.

-

Sending and Receiving Messages in a Secret Chat

-

Serialization and Encryption of Outgoing Messages

-

A TL object of type DecryptedMessage is created and contains the message in plain text. For backward compatibility, the object must be wrapped in the constructor decryptedMessageLayer with an indication of the supported layer (starting with 46).

-
-

The TL-Schema for the contents of end-to-end encrypted messages is available here »

-
-

The resulting construct is serialized as an array of bytes using generic TL rules. The resulting array is prepended by 4 bytes containing the array length not counting these 4 bytes.

-

The byte array is padded with 12 to 1024 random padding bytes to make its length divisible by 16 bytes. (In the older MTProto 1.0 encryption, only 0 to 15 padding bytes were used.)

-

Message key, msg_key, is computed as the 128 middle bits of the SHA256 of the data obtained in the previous step, prepended by 32 bytes from the shared key key. (For the older MTProto 1.0 encryption, msg_key was computed differently, as the 128 lower bits of SHA1 of the data obtained in the previous steps, excluding the padding bytes.)

-

For MTProto 2.0, the AES key aes_key and initialization vector aes_iv are computed ( key is the shared key obtained during Key Generation ) as follows:

-
    -
  • msg_key_large = SHA256 (substr (key, 88+x, 32) + plaintext + random_padding);
  • -
  • msg_key = substr (msg_key_large, 8, 16);
  • -
  • sha256_a = SHA256 (msg_key + substr (key, x, 36));
  • -
  • sha256_b = SHA256 (substr (key, 40+x, 36) + msg_key);
  • -
  • aes_key = substr (sha256_a, 0, 8) + substr (sha256_b, 8, 16) + substr (sha256_a, 24, 8);
  • -
  • aes_iv = substr (sha256_b, 0, 8) + substr (sha256_a, 8, 16) + substr (sha256_b, 24, 8);
  • -
-

For MTProto 2.0, x=0 for messages from the originator of the secret chat, x=8 for the messages in the opposite direction.

-

For the obsolete MTProto 1.0, msg_key, aes_key, and aes_iv were computed differently (see this document for reference).

-

Data is encrypted with a 256-bit key, aes_key, and a 256-bit initialization vector, aes-iv, using AES-256 encryption with infinite garble extension (IGE). Encryption key fingerprint key_fingerprint and the message key msg_key are added at the top of the resulting byte array.

-

Encrypted data is embedded into a messages.sendEncrypted API call and passed to Telegram server for delivery to the other party of the Secret Chat.

-

Upgrading to MTProto 2.0 from MTProto 1.0

-

As soon as both parties in a secret chat are using at least Layer 73, they should only use MTProto 2.0 for all outgoing messages. Some of the first received messages may use MTProto 1.0, if a sufficiently high starting layer has not been negotiated during the creation of the secret chat. After the first message encrypted with MTProto 2.0 (or the first message with Layer 73 or higher) is received, all messages with higher sequence numbers must be encrypted with MTProto 2.0 as well.

-

As long as the current layer is lower than 73, each party should try to decrypt received messages with MTProto 1.0, and if this is not successfull (msg_key does not match), try MTProto 2.0. Once the first MTProto 2.0-encrypted message arrives (or the layer is upgraded to 73), there is no need to try MTProto 1.0 decryption for any of the further messages (unless the client is still waiting for some gaps to be closed).

-

Decrypting an Incoming Message

-

The steps above are performed in reverse order. -When an encrypted message is received, you must check that msg_key is in fact equal to the 128 middle bits of the SHA256 hash of the decrypted message, prepended by 32 bytes taken from the shared key. -If the message layer is greater than the one supported by the client, the user must be notified that the client version is out of date and prompted to update.

-

Sequence numbers

-

It is necessary to interpret all messages in their original order to protect against possible manipulations. Secret chats support a special mechanism for handling seq_no counters independently from the server.

-
-

Proper handling of these counters is further described in this article: Sequence numbers in Secret Chats.

-
-

Please note that your client must support sequence numbers in Secret Chats to be compatible with official Telegram clients.

-

Sending Encrypted Files

-

All files sent to secret chats are encrypted with one-time keys that are in no way related to the chat’s shared key. Before an encrypted file is sent, it is assumed that the encrypted file’s address will be attached to the outside of an encrypted message using the file parameter of the messages.sendEncryptedFile method and that the key for direct decryption will be sent in the body of the message (the key parameter in the constructors decryptedMessageMediaPhoto, decryptedMessageMediaVideo and decryptedMessageMediaFile.

-

Prior to a file being sent to a secret chat, 2 random 256-bit numbers are computed which will serve as the AES key and initialization vector used to encrypt the file. AES-256 encryption with infinite garble extension (IGE) is used in like manner.

-

The key fingerprint is computed as follows:

-
    -
  • digest = md5(key + iv)
  • -
  • fingerprint = substr(digest, 0, 4) XOR substr(digest, 4, 4)
  • -
-

The encrypted contents of a file are stored on the server in much the same way as those of a file in cloud chats: piece by piece using calls to upload.saveFilePart. -A subsequent call to messages.sendEncryptedFile will assign an identifier to the stored file and send the address together with the message. The recipient will receive an update with encryptedMessage, and the file parameter will contain file information.

-

Incoming and outgoing encrypted files can be forwarded to other secret chats using the constructor inputEncryptedFile to avoid saving the same content on the server twice.

-

Working with an Update Box

-

Secret chats are associated with specific devices (or rather with authorization keys), not users. A conventional message box, which uses pts to describe the client’s status, is not suitable, because it is designed for long-term message storage and message access from different devices.

-

An additional temporary message queue is introduced as a solution to this problem. When an update regarding a message from a secret chat is sent, a new value of qts is sent, which helps reconstruct the difference if there has been a long break in the connection or in case of loss of an update.

-

As the number of events increases, the value of qts increases by 1 with each new event. The initial value may not (and will not) be equal to 0.

-

The fact that events from the temporary queue have been received and stored by the client is acknowledged explicitly by a call to the messages.receivedQueue method or implicitly by a call to updates.getDifference (the value of qts passed, not the final state). All messages acknowledged as delivered by the client, as well as any messages older than 7 days, may (and will) be deleted from the server.

-

Upon de-authorization, the event queue of the corresponding device will be forcibly cleared, and the value of qts will become irrelevant.

-

Updating to new layers

-

Your client should always store the maximal layer that is known to be supported by the client on the other side of a secret chat. When the secret chat is first created, this value should be initialized to 46. This remote layer value must always be updated immediately after receiving any packet containing information of an upper layer, i.e.:

-
    -
  • any secret chat message containing layer_no in its decryptedMessageLayer with layer>=46, or
  • -
  • a decryptedMessageActionNotifyLayer service message, wrapped as if it were the decryptedMessageService constructor of the obsolete layer 8 (constructor decryptedMessageService#aa48327d).
  • -
-

Notifying the remote client about your local layer

-

In order to notify the remote client of your local layer, your client must send a message of the decryptedMessageActionNotifyLayer type. This notification must be wrapped in a constructor of an appropriate layer.

-

There are two cases when your client must notify the remote client about its local layer:

-
    -
  1. As soon as a new secret chat has been created, immediately after the secret key has been successfully exchanged.
  2. -
  3. Immediately after the local client has been updated to support a new secret chat layer. In this case notifications must be sent to all currently existing secret chats. Note that this is only necessary when updating to new layers that contain changes in the secret chats implementation (e.g. you don’t need to do this when your client is updated from Layer 46 to Layer 47).
  4. -
- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/end-to-end/pfs.html b/data/corefork.telegram.org/api/end-to-end/pfs.html deleted file mode 100644 index 8447ceee85..0000000000 --- a/data/corefork.telegram.org/api/end-to-end/pfs.html +++ /dev/null @@ -1,176 +0,0 @@ - - - - - Perfect Forward Secrecy - - - - - - - - - - - - - -
- -
-
-
- -

Perfect Forward Secrecy

- -
-

Telegram supports Perfect Forward Secrecy (PFS) in Secret Chats as of Layer 20. See updating to new layers.

-
-

In order to keep past communications safe, official Telegram clients will initiate re-keying once a key has been used to decrypt and encrypt more than 100 messages, or has been in use for more than one week, provided the key has been used to encrypt at least one message. Old keys are then securely discarded and cannot be reconstructed, even with access to the new keys currently in use.

-

Any client participating in a Secret Chat can initiate re-keying as soon as it perceives that the current key has been used for too long or for encrypting too many messages. Please note that you should never initiate a new instance of the re-keying protocol if an uncompleted instance exists, initiated by either party.

-

Note: third-party developers are required to maintain the same level of security. All clients with secret chat support must be able to initiate re-keying and accept relevant service messages. See Security Guidelines.

-

Re-keying protocol

-

New keys are generated by exchanging special messages, using previously established keys for encryption. The re-keying protocol between parties A and B normally consists of four steps:

-
1. decryptedMessageActionRequestKey
-

A (re-keying initiator) generates a new value of a, subject to the same limitations as for the initial Diffie-Hellman key exchange, and sends the value of pow(g,a) to B, embedded in a decryptedMessageService:

-
decryptedMessageActionRequestKey exchange_id:long g_a:string = DecryptedMessageAction;
-
    -
  • exchange_id is a random number identifying this instance of the Re-Keying Protocol for both parties
  • -
  • g_a is the value of pow(g,a) mod p
  • -
-

Note that the same Diffie--Hellman parameters (p,g) as for the initial Diffie--Hellman key exchange in this secret chat are used. They do not need to be re-transmitted explicitly.

-
2. decryptedMessageActionAcceptKey
-

Upon receipt of the above service message, B checks its content, and generates a response with same exchange_id, for a newly generated value of b:

-
decryptedMessageActionAcceptKey exchange_id:long g_b:string key_fingerprint:long = DecryptedMessageAction;
-
    -
  • exchange_id is the same as in the received decryptedMessageActionRequestKey
  • -
  • g_b is the value of pow(g,b) mod p
  • -
  • key_fingerprint is the 64-bit fingerprint of the newly generated key = pow(g_a, b) mod p, used as a sanity check of the implementation
  • -
-

At this stage, B can already compute the new key key = pow(g_a, b) mod p and its key_fingerprint (last 64 bits of its SHA-1). However, it continues using the previous key until the completion of the exchange.

-

Once side B sends decryptedMessageActionAcceptKey, it cannot abort the key exchange; it must be ready to switch to the new key immediately after a decryptedMessageActionCommitKey is received. Therefore, if side B wishes to delay the usage of new key, for example in order to fill some seq_no gaps first, it must delay the decryptedMessageActionAcceptKey answer accordingly.

-
3. decryptedMessageActionCommitKey
-

Once A receives a valid decryptedMessageActionAcceptKey, it performs all necessary checks, and "commits" the new key by means of the following service message:

-
decryptedMessageActionCommitKey exchange_id:long key_fingerprint:long = DecryptedMessageAction;
-
    -
  • exchange_id is the same as in the two previous messages
  • -
  • key_fingerprint is the value of the hash (last 64 bits of SHA-1) of the new key computed by A, for implementation sanity check
  • -
-

After that, A can (and must) encrypt all following messages with the new key.

-

If side A wishes to delay installation of the new key, for example because there are some seq_no gaps that it wants to fill first, it must delay decryptedMessageActionCommitKey answer accordingly.

-
4. Final step
-

When B receives either a decryptedMessageActionCommitKey or a message encrypted by the new key, recognized by the value of key_fingerprint prepended to the encrypted message (it may happen that the decryptedMessageActionCommitKey has been lost and will be re-requested later), it assumes that A has started using the new key for encryption, and does the same.

-

However, the previous key may be kept until there are no gaps in received messages up to the switch to the new key. Once all the gaps have been filled, the old key must be securely discarded.

-

There is one exception to this rule — the SHA-1 of the original key (generated during the establishment of Secret Chat in question) is always stored, in order to show key visualizations on the clients.

-

Aborting protocol

-

Any of the parties may abort any instance of an uncompleted re-keying protocol, unless decryptedMessageActionCommitKey or decryptedMessageActionAcceptKey has been already sent by the party in question. In order to abort re-keying, send

-
decryptedMessageActionAbortKey exchange_id:long = DecryptedMessageAction;
-

This could be done, for example, if the party is already participating in a different instance of the re-keying protocol, or if the received values of g_a, g_b and other parameters do not pass security checks. In the latter case, it might be advisable to abort the Secret Chat altogether.

-

Discarding Previous Keys

-

Once B receives decryptedMessageActionCommitKey, it can safely discard the previous key provided there are no gaps. However, A may only discard the previous key after a message encrypted with the new key has been received. If no ordinary messages are scheduled to be sent, a special no-op message should sent by B for this purpose:

-
decryptedMessageActionNoop = DecryptedMessageAction;
-

Concurrent Re-Keying

-

It may happen that both parties concurrently initiate re-keying by sending decryptedMessageActionRequestKey without knowing that the other party has already done so. If each side aborts re-keying because it is already participating in another instance of the protocol initiated by itself, the re-keying will never happen.

-

Because of this possibility, we suggest that only the instance with the smaller exchange_id is aborted, with the option to re-use its (a,g_a) for the re-keying protocol instance with the larger exchange_id (when compared as a long, i.e. signed little-endian 64-bit integer).

-

In other words, if a decryptedMessageActionRequestKey is received after A has sent its decryptedMessageActionRequestKey, but has not yet received decryptedMessageActionAcceptKey, the following is to be done:

-
    -
  • if exchange_id in the sent decryptedMessageActionRequestKey was larger than that in the decryptionActionRequestKey just received, abort the newly-suggested re-keying protocol instance without sending explicit decryptedMessageActionAbortKey (the other side will do the same according to the next rule).
  • -
  • if exchange_id in our decryptedMessageActionRequestKey was smaller, respond to the newly-received decryptedMessageActionRequestKey with a decryptedMessageActionAcceptKey, and participate only in the re-keying protocol instance initiated by the other side. It is possible to re-use at this stage the value of g_a (now called g_b) that was generated for the original decryptedMessageActionRequestKey, now abandoned, or totally new (b,g_b) can be generated.
  • -
  • in the unlikely (2^{-64}) case both exchange_id are equal, abort both instances without sending an explicit decryptedMessageActionAbortKey. The other side will do the same.
  • -
-
Key Visualization
-

Since all re-keying instances are carried over the secure channel established when the secret chat is created, it is necessary for the user to confirm that no MITM attack had taken place during the initial exchange. The key visualization on the clients uses the first 128-bits of the SHA-1 of the original key created when the Secret Chat was first established, followed by the first 160 bits of the SHA-256 of the key in use when the secret chat was updated to layer 46 (coincides with the original key if chat was created using layer 46).

-
-

Please note that the key_fingerprint parameter was introduced as a maintenance tool (with a misleading name) and is not related to key visualization on the clients.

-
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/api/end-to-end/seq_no.html b/data/corefork.telegram.org/api/end-to-end/seq_no.html deleted file mode 100644 index ed84d5f923..0000000000 --- a/data/corefork.telegram.org/api/end-to-end/seq_no.html +++ /dev/null @@ -1,173 +0,0 @@ - - - - - Sequence numbers in Secret Chats - - - - - - - - - - - - - -
- -
-
-
- -

Sequence numbers in Secret Chats

- -

It is necessary to interpret all messages in their original order to protect against reordering, reflection, replay, omission and other manipulations (decryptedMessageActionResend messages are the only exception to this rule, see avoiding concurrent gaps). Secret chats support a special mechanism for handling seq_no counters independently from the server. Note that any service messages in secret chats must also increment the seq_no.

-

All Secret Chats messages in clients using Layer 17 or higher are wrapped in decryptedMessageLayer and have seq_no (sequence number) counters attached to them. The seq_no counters in their raw form are initialized with (out_seq_no, in_seq_no) := (0,0), and incremented strictly by 1 after any message (service or not) is sent/received and processed. They must be protected from mirroring before being sent to the remote client by transformation according to formula 2*raw_seq_no+x, where x is 0 or 1, determined by the following rule:

- - - - - - - - - - - - - - - - - -
in_seq_noout_seq_no
secret chat initiated by sender01
secret chat initiated by recipient10
-

In this way the least significant bit of each seq_no field included in the message is different for incoming and outgoing messages. This is done to prevent a possible attacker from mirroring the messages. If any of the received in_seq_no or out_seq_no are not consistent in terms of parity (see table above), the client is required to immediately abort the secret chat.

-
-

E.g., the first message the local client sends to any secret chat will have out_seq_no of 0+x_out, the second one will have out_seq_no of 2*1+x_out, and so on, where x_out is 0 if the chat was initiated by the remote client, 1 otherwise; similarly for the received messages, but there x_in is used instead of x_out and is equal to 0 if the chat was initiated by the local client, 1 otherwise.

-
-

Raw sequence numbers will be used in the remaining part of this text, unless otherwise specified.

-

Preventing gaps

-

Your client must ensure that all outgoing secret chat messages are queued on the server in the correct order. This is achieved by correctly placing them into the invokeAfterMsgs chain. Failure to do this may result in gaps on the remote client, which may in turn lead to aborted secret chats. The local client must maintain the correct sequence of in_seq_no for the remote client. To achieve this, assign in_seq_no and out_seq_no to each message at the exact moment when the message is created, and never change them in the future.

-

Security checks

-

Checking out_seq_no

-

Your client must check that it has received each message with the sequence number out_seq_no starting from 0 to some current point C. It should then expect the next message to have the sequence number out_seq_no=C+1. If the out_seq_no in the received message does not match this, the following needs to be done:

-
    -
  • If the received out_seq_no<=C, the local client must drop the message (repeated message). The client should not check the contents of the message because the original message could have been deleted (see Deleting unacknowledged messages).
  • -
  • If the received out_seq_no>C+1, it most likely means that the server left out some messages due to a technical failure or due to the messages becoming obsolete. A temporary solution to this is to simply abort the secret chat. But since this may cause some existing older secret chats to be aborted, it is strongly recommended for the client to properly handle such seq_no gaps. Note that in_seq_no is not increased upon receipt of such a message; it is advanced only after all preceding gaps are filled.
  • -
-

Proper handling of gaps

-

In order to correctly handle incoming messages after a hole has been identified (when received out_seq_no>C+1), it is necessary to put received messages with the wrong seq_no into a "waiting queue" on the local client, and to re-request the missing messages using the special constructor decryptedMessageActionResend start_seq_no:int end_seq_no:int = DecryptedMessageAction;. The sequence numbers used in this constructor must be ready for interpretation by the remote client and therefore cannot be in their raw form: you can easily get the necessary start_seq_no by adding 2 to the out_seq_no of the last message before the hole and the end_seq_no by subtracting 2 from the out_seq_no of the received message with the wrong sequence number.

-

Each hole normally requires only one request to resend messages — if the remote client keeps sending out of sync messages, they should be put into the queue without sending a new request. Having received the missing messages, the local client must first interpret these messages in the right order by their seq_no. Once this is done, the client can proceed to interpret messages from the queue (again, in the right seq_no order).

-

Special cases:

-
    -
  • Note that having two gaps simultaneously is very rare (provided that the remote client and server are operating normally) and it is acceptable to abort the secret chat in this situation.
  • -
  • If a local client receives decryptedMessageActionResend but is unable to satisfy the request, it must abort the secret chat.
  • -
-

Avoiding concurrent gaps

-

In order to avoid getting stuck with concurrent gaps on both sides, decryptedMessageActionResend must always be interpreted immediately upon receipt in all cases, even if its out_seq_no>=C+1. Note that each decryptedMessageActionResend must only be handled once, it must not be interpreted again when we interpret messages in the queue.

-

Checking and handling in_seq_no

-

in_seq_no of all received messages must be valid. To ensure this, perform the following checks:

-
    -
  • in_seq_no must form a non-decreasing sequence of non-negative integer numbers.
  • -
  • in_seq_no must be valid at the moment of receiving the message, that is, if D is the out_seq_no of last message we sent, the received in_seq_no should not be greater than D + 1. This also allows us to insert the received message into its correct place in the secret chat. For example, imagine that the local client has sent 5 secret chat messages, and then receives a secret chat message with the text "Yes" and in_seq_no=2. In this situation the local client must place that message after the second message it sent. This makes manipulations with delayed messages impossible.
  • -
-

If in_seq_no contradicts these criteria, the local client is required to immediately abort the secret chat. This could happen only in case of malicious or buggy behaviour on either server or remote client side.

-

Deleting unacknowledged messages

-

In case the user on the local client has deleted a message before the server (or the remote client, if decryptedMessageActionResend is handled correctly) could acknowledge the message, for security reasons, you must:

-
    -
  • securely destroy the contents of the message (as in case of any other deleted Secret Chat message);
  • -
  • change the local copy of the original message to decryptedMessageActionDeleteMessages with random_id equal to its own random_id;
  • -
  • create a new outgoing message deleting the original message.
  • -
-

This must be done because your client doesn't know whether the remote client really received the message or not. In the case the message was already received, it will be deleted by the second message; otherwise it must arrive as a "self-delete" message to maintain the correct sequence of seq_no.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/api/end-to-end/video-calls.html b/data/corefork.telegram.org/api/end-to-end/video-calls.html deleted file mode 100644 index 3561fafe1d..0000000000 --- a/data/corefork.telegram.org/api/end-to-end/video-calls.html +++ /dev/null @@ -1,215 +0,0 @@ - - - - - End-to-End Encrypted Voice and Video Calls - - - - - - - - - - - - - -
- -
-
-
- -

End-to-End Encrypted Voice and Video Calls

- -

This article describes the end-to-end encryption used for Telegram voice and video calls.

-
Related Articles
-

- -
-

Establishing Calls

-

Before a call is ready, some preliminary actions have to be performed. The calling party needs to contact the party to be called and check whether it is ready to accept the call. Besides that, the parties have to negotiate the protocols to be used, learn the IP addresses of each other or of the Telegram relay servers to be used (so-called reflectors), and generate a one-time encryption key for this voice call with the aid of Diffie--Hellman key exchange. All of this is accomplished in parallel with the aid of several Telegram API methods and related notifications. This document covers details related to key generation, encryption and security.

-

Key Generation

-

The Diffie-Hellman key exchange, as well as the whole protocol used to create a new voice call, is quite similar to the one used for Secret Chats. We recommend studying the linked article before proceeding.

-

However, we have introduced some important changes to facilitate the key verification process. Below is the entire exchange between the two communicating parties, the Caller (A) and the Callee (B), through the Telegram servers (S).

-
    -
  • A executes messages.getDhConfig to find out the 2048-bit Diffie-Hellman prime p and generator g. The client is expected to check whether p is a safe prime and perform all the security checks necessary for secret chats.
  • -
  • A chooses a random value of a, 1 < a < p-1, and computes g_a:=power(g,a) mod p (a 256-byte number) and g_a_hash:=SHA256(g_a) (32 bytes long).
  • -
  • A invokes (sends to server S) phone.requestCall, which has the field g_a_hash:bytes, among others. For this call, this field is to be filled with g_a_hash, not g_a itself.
  • -
  • The Server S performs privacy checks and sends an updatePhoneCall update with a phoneCallRequested constructor to all of B's active devices. This update, apart from the identity of A and other relevant parameters, contains the g_a_hash field, filled with the value obtained from A.
  • -
  • B accepts the call on one of their devices, stores the received value of g_a_hash for this instance of the voice call creation protocol, chooses a random value of b, 1 < b < p-1, computes g_b:=power(g,b) mod p, performs all the required security checks, and invokes the phone.acceptCall method, which has a g_b:bytes field (among others), to be filled with the value of g_b itself (not its hash).
  • -
  • The Server S sends an updatePhoneCall with the phoneCallDiscarded constructor to all other devices B has authorized, to prevent accepting the same call on any of the other devices. From this point on, the server S works only with that of B's devices which has invoked phone.acceptCall first.
  • -
  • The Server S sends to A an updatePhoneCall update with phoneCallAccepted constructor, containing the value of g_b received from B.
  • -
  • A performs all the usual security checks on g_b and a, computes the Diffie--Hellman key key:=power(g_b,a) mod p and its fingerprint key_fingerprint:long, equal to the lower 64 bits of SHA1(key), the same as with secret chats. Then A invokes the phone.confirmCall method, containing g_a:bytes and key_fingerprint:long.
  • -
  • The Server S sends to B an updatePhoneCall update with the phoneCall constructor, containing the value of g_a in g_a_or_b:bytes field, and key_fingerprint:long
  • -
  • At this point B receives the value of g_a. It checks that SHA256(g_a) is indeed equal to the previously received value of g_a_hash, performs all the usual Diffie-Hellman security checks, and computes the key key:=power(g_a,b) mod p and its fingerprint, equal to the lower 64 bits of SHA1(key). Then it checks that this fingerprint equals the value of key_fingerprint:long received from the other side, as an implementation sanity check.
  • -
-

At this point, the Diffie--Hellman key exchange is complete, and both parties have a 256-byte shared secret key key which is used to encrypt all further exchanges between A and B.

-

It is of paramount importance to accept each update only once for each instance of the key generation protocol, discarding any duplicates or alternative versions of already received and processed messages (updates).

-

Encryption

-
-

This document describes encryption in voice and video calls as implemented in Telegram apps with versions 7.0 and above. See this document for details on encryption used in voice calls in app versions released before August 14, 2020.

-
-

The Telegram Voice and Video Call Library uses an optimized version of MTProto 2.0 to send and receive packets, consisting of one or more end-to-end encrypted messages of various types (ice candidates list, video formats, remote video status, audio stream data, video stream data, message ack or empty).

-

This document describes only the encryption process, leaving out encoding and network-dependent parts.

-

The library starts working with:

-
    -
  • An encryption key key shared between the parties, as generated above.
  • -
  • Information whether the call is outgoing or incoming.
  • -
  • Two data transfer channels: signaling, offered by the Telegram API, and transport based on WebRTC.
  • -
-

Both data transfer channels are unreliable (messages may get lost), but signaling is slower and more reliable.

-

Encrypting Call Data

-

The body of a packet (decrypted_body) consists of several messages and their respective seq numbers concatenated together.

-
    -
  • decrypted_body = message_seq1 + message_body1 + message_seq2 + message_body2
  • -
-

Each decrypted_body is unique because no two seq numbers of the first message can be the same. If only old messages need to be re-sent, an empty message with new unique seq is added to the packet first.

-

The encryption key key is used to compute a 128-bit msg_key and then a 256-bit aes_key and a 128-bit aes_iv:

-
    -
  • msg_key_large = SHA256 (substr(key, 88+x, 32) + decrypted_body);
  • -
  • msg_key = substr (msg_key_large, 8, 16);
  • -
  • sha256_a = SHA256 (msg_key + substr (key, x, 36));
  • -
  • sha256_b = SHA256 (substr (key, 40+x, 36) + msg_key);
  • -
  • aes_key = substr (sha256_a, 0, 8) + substr (sha256_b, 8, 16) + substr (sha256_a, 24, 8);
  • -
  • aes_iv = substr (sha256_b, 0, 4) + substr (sha256_a, 8, 8) + substr (sha256_b, 24, 4);
  • -
-

x depends on whether the call is outgoing or incoming and on the connection type:

-
    -
  • x = 0 for outgoing + transport
  • -
  • x = 8 for incoming + transport
  • -
  • x = 128 for outgoing + signaling
  • -
  • x = 136 for incoming + signaling
  • -
-

This allows apps to decide which packet types will be sent to which connections and work in these connections independently (with each having its own seq counter).

-

The resulting aes_key and aes_iv are used to encrypt decrypted_body:

-
    -
  • encrypted_body = AES_CTR (decrypted_body, aes_key, aes_iv)
  • -
-

The packet that gets sent consists of msg_key and encrypted_body:

-
    -
  • packet_bytes = msg_key + encrypted_body
  • -
-

When received, the packet gets decrypted using key and msg_key, after which msg_key is checked against the relevant SHA256 substring. If the check fails, the packet must be discarded.

-

Protecting Against Replay Attacks

-

Each of the peers maintains its own 32-bit monotonically increasing counter for outgoing messages, seq, starting with 1. This seq counter is prepended to each sent message and increased by 1 for each new message. No two seq numbers of the first message in a packet can be the same. If only old messages need to be re-sent, an empty message with a new unique seq is added to the packet first. When the seq counter reaches 2^30, the call must be aborted. Each peer stores seq values of all the messages it has received (and processed) which are larger than max_received_seq - 64, where max_received_seq is the largest seq number received so far.

-

If a packet is received, the first message of which has a seq that is smaller or equal to max_received_seq - 64 or its seq had already been received, the message is discarded. Otherwise, the seq values of all incoming messages are memorized and max_received_seq is adjusted. This guarantees that no two packets will be processed twice.

-

Key Verification

-

To verify the key, and ensure that no MITM attack is taking place, both parties concatenate the secret key key with the value g_a of the Caller ( A ), compute SHA256 and use it to generate a sequence of emoticons. More precisely, the SHA256 hash is split into four 64-bit integers; each of them is divided by the total number of emoticons used (currently 333), and the remainder is used to select specific emoticons. The specifics of the protocol guarantee that comparing four emoticons out of a set of 333 is sufficient to prevent eavesdropping (MiTM attack on DH) with a probability of 0.9999999999.

-

This is because instead of the standard Diffie-Hellman key exchange which requires only two messages between the parties:

-
    -
  • A->B : (generates a and) sends g_a := g^a
  • -
  • B->A : (generates b and true key (g_a)^b, then) sends g_b := g^b
  • -
  • A : computes key (g_b)^a
  • -
-

we use a three-message modification thereof that works well when both parties are online (which also happens to be a requirement for voice calls):

-
    -
  • A->B : (generates a and) sends g_a_hash := hash(g^a)
  • -
  • B->A : (stores g_a_hash, generates b and) sends g_b := g^b
  • -
  • A->B : (computes key (g_b)^a, then) sends g_a := g^a
  • -
  • B : checks hash(g_a) == g_a_hash, then computes key (g_a)^b
  • -
-

The idea here is that A commits to a specific value of a (and of g_a) without disclosing it to B. B has to choose its value of b and g_b without knowing the true value of g_a, so that it cannot try different values of b to force the final key (g_a)^b to have any specific properties (such as fixed lower 32 bits of SHA256(key)). At this point, B commits to a specific value of g_b without knowing g_a. Then A has to send its value g_a; it cannot change it even though it knows g_b now, because the other party B would accept only a value of g_a that has a hash specified in the very first message of the exchange.

-

If some impostor is pretending to be either A or B and tries to perform a Man-in-the-Middle Attack on this Diffie--Hellman key exchange, the above still holds. Party A will generate a shared key with B -- or whoever pretends to be B -- without having a second chance to change its exponent a depending on the value g_b received from the other side; and the impostor will not have a chance to adapt his value of b depending on g_a, because it has to commit to a value of g_b before learning g_a. The same is valid for the key generation between the impostor and the party B.

-

The use of hash commitment in the DH exchange constrains the attacker to only one guess to generate the correct visualization in their attack, which means that using just over 33 bits of entropy represented by four emoji in the visualization is enough to make a successful attack highly improbable.

-
-

For a slightly more user-friendly explanation of the above see: How are calls authenticated?

-
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/api/end-to-end/voice-calls.html b/data/corefork.telegram.org/api/end-to-end/voice-calls.html deleted file mode 100644 index 2743024d71..0000000000 --- a/data/corefork.telegram.org/api/end-to-end/voice-calls.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - End-to-End Encrypted Voice Calls - - - - - - - - - - - - - -
- -
-
-
- -

End-to-End Encrypted Voice Calls

- -
-

This document describes encryption in voice calls as implemented in Telegram apps with versions < 7.0. See this document for details on encryption used in voice and video calls in app versions released on August 14, 2020 and later.

-
-
Related articles
-

- -

Establishing voice calls

-

Before a voice call is ready, some preliminary actions have to be performed. The calling party needs to contact the party to be called and check whether it is ready to accept the call. Besides that, the parties have to negotiate the protocols to be used, learn the IP addresses of each other or of the Telegram relay servers to be used (so-called reflectors), and generate a one-time encryption key for this voice call with the aid of Diffie--Hellman key exchange. All of this is accomplished in parallel with the aid of several Telegram API methods and related notifications. This document details the generation of the encryption key. Other negotiations will be eventually documented elsewhere.

-

Key Generation

-

The Diffie-Hellman key exchange, as well as the whole protocol used to create a new voice call, is quite similar to the one used for Secret Chats. We recommend studying the linked article before proceeding.

-

However, we have introduced some important changes to facilitate the key verification process. Below is the entire exchange between the two communicating parties, the Caller (A) and the Callee (B), through the Telegram servers (S).

-
    -
  • A executes messages.getDhConfig to find out the 2048-bit Diffie-Hellman prime p and generator g. The client is expected to check whether p is a safe prime and perform all the security checks necessary for secret chats.
  • -
  • A chooses a random value of a, 1 < a < p-1, and computes g_a:=power(g,a) mod p (a 256-byte number) and g_a_hash:=SHA256(g_a) (32 bytes long).
  • -
  • A invokes (sends to server S) phone.requestCall, which has the field g_a_hash:bytes, among others. For this call, this field is to be filled with g_a_hash, not g_a itself.
  • -
  • The Server S performs privacy checks and sends an updatePhoneCall update with a phoneCallRequested constructor to all of B's active devices. This update, apart from the identity of A and other relevant parameters, contains the g_a_hash field, filled with the value obtained from A.
  • -
  • B accepts the call on one of their devices, stores the received value of g_a_hash for this instance of the voice call creation protocol, chooses a random value of b, 1 < b < p-1, computes g_b:=power(g,b) mod p, performs all the required security checks, and invokes the phone.acceptCall method, which has a g_b:bytes field (among others), to be filled with the value of g_b itself (not its hash).
  • -
  • The Server S sends an updatePhoneCall with the phoneCallDiscarded constructor to all other devices B has authorized, to prevent accepting the same call on any of the other devices. From this point on, the server S works only with that of B's devices which has invoked phone.acceptCall first.
  • -
  • The Server S sends to A an updatePhoneCall update with phoneCallAccepted constructor, containing the value of g_b received from B.
  • -
  • A performs all the usual security checks on g_b and a, computes the Diffie--Hellman key key:=power(g_b,a) mod p and its fingerprint key_fingerprint:long, equal to the lower 64 bits of SHA1(key), the same as with secret chats. Then A invokes the phone.confirmCall method, containing g_a:bytes and key_fingerprint:long.
  • -
  • The Server S sends to B an updatePhoneCall update with the phoneCall constructor, containing the value of g_a in g_a_or_b:bytes field, and key_fingerprint:long
  • -
  • At this point B receives the value of g_a. It checks that SHA256(g_a) is indeed equal to the previously received value of g_a_hash, performs all the usual Diffie-Hellman security checks, and computes the key key:=power(g_a,b) mod p and its fingerprint, equal to the lower 64 bits of SHA1(key). Then it checks that this fingerprint equals the value of key_fingerprint:long received from the other side, as an implementation sanity check.
  • -
-

At this point, the Diffie--Hellman key exchange is complete, and both parties have a 256-byte shared secret key key which is used to encrypt all further exchanges between A and B.

-

It is of paramount importance to accept each update only once for each instance of the key generation protocol, discarding any duplicates or alternative versions of already received and processed messages (updates).

-

Encryption of voice data

-

Both parties A (the Caller) and B (the Callee) transform the voice information into a sequence of small chunks or packets, not more than 1 kilobyte each. This information is to be encrypted using the shared key key generated during the initial exchange, and sent to the other party, either directly (P2P) or through Telegram's relay servers (so-called reflectors). This document describes only the encryption process for each chunk, leaving out voice encoding and the network-dependent parts.

-

Encapsulation of low-level voice data

-

The low-level data chunk raw_data:string, obtained from voice encoder, is first encapsulated into one of the two constructors for the DecryptedDataBlock type, similar to DecryptedMessage used in secret chats:

-
decryptedDataBlock#dbf948c1 random_id:long random_bytes:string flags:# voice_call_id:flags.2?int128 in_seq_no:flags.4?int out_seq_no:flags.4?int recent_received_mask:flags.5?int proto:flags.3?int extra:flags.1?string raw_data:flags.0?string = DecryptedDataBlock;
-simpleDataBlock#cc0d0e76 random_id:long random_bytes:string raw_data:string = DecryptedDataBlock;
-

Here out_seq_no is the chunk's sequence number among all sent by this party (starting from one), in_seq_no -- the highest known out_seq_no from the received packets. The parameter recent_received_mask is a 32-bit mask, used to track delivery of the last 32 packets sent by the other party. The bit i is set if a packet with out_seq_no equal to in_seq_no-i has been received.

-

The higher 8 bits in flags are reserved for use by the lower-level protocol (the one which generates and interprets raw_data), and will never be used for future extensions of decryptedDataBlock.

-

The parameters voice_call_id and proto are mandatory until the other side confirms reception of at least one packet by sending a packet with a non-zero in_seq_no. After that, they become optional, and the simpleDataBlock constructor can be used if the lower level protocol wants to.

-

The parameter voice_call_id is computed from the key key and equals the lower 128 bits of its SHA-256.

-

The random_bytes string should contain at least 7 bytes of random data. The field random_id also contains 8 random bytes, which can be used as a unique packet identifier if necessary.

-

MTProto encryption

-

Once the data is encapsulated in DecryptedDataBlock, it is TL-serialized and encrypted with MTProto, using key instead of auth_key; the parameter x is to be set to 0 for messages from A to B, and to 8 for messages in the opposite direction. Encrypted data are prepended by the 128-bit msg_key (usual for MTProto); before that, either the 128-bit voice_call_id (if P2P is used) or the peer_tag (if reflectors are used) is prepended. The resulting data packet is sent by UDP either directly to the other party (if P2P is possible) or to the Telegram relay servers (reflectors).

-

Key Verification

-

To verify the key, both parties concatenate the secret key key with the value g_a of the Caller ( A ), compute SHA256 and use it to generate a sequence of emoticons. More precisely, the SHA256 hash is split into four 64-bit integers; each of them is divided by the total number of emoticons used (currently 333), and the remainder is used to select specific emoticons. The specifics of the protocol guarantee that comparing four emoticons out of a set of 333 is sufficient to prevent eavesdropping (MiTM attack on DH) with a probability of 0.9999999999.

-

This is because instead of the standard Diffie-Hellman key exchange which requires only two messages between the parties:

-
    -
  • A->B : (generates a and) sends g_a := g^a
  • -
  • B->A : (generates b and true key (g_a)^b, then) sends g_b := g^b
  • -
  • A : computes key (g_b)^a
  • -
-

we use a three-message modification thereof that works well when both parties are online (which also happens to be a requirement for voice calls):

-
    -
  • A->B : (generates a and) sends g_a_hash := hash(g^a)
  • -
  • B->A : (stores g_a_hash, generates b and) sends g_b := g^b
  • -
  • A->B : (computes key (g_b)^a, then) sends g_a := g^a
  • -
  • B : checks hash(g_a) == g_a_hash, then computes key (g_a)^b
  • -
-

The idea here is that A commits to a specific value of a (and of g_a) without disclosing it to B. B has to choose its value of b and g_b without knowing the true value of g_a, so that it cannot try different values of b to force the final key (g_a)^b to have any specific properties (such as fixed lower 32 bits of SHA256(key)). At this point, B commits to a specific value of g_b without knowing g_a. Then A has to send its value g_a; it cannot change it even though it knows g_b now, because the other party B would accept only a value of g_a that has a hash specified in the very first message of the exchange.

-

If some impostor is pretending to be either A or B and tries to perform a Man-in-the-Middle Attack on this Diffie--Hellman key exchange, the above still holds. Party A will generate a shared key with B -- or whoever pretends to be B -- without having a second chance to change its exponent a depending on the value g_b received from the other side; and the impostor will not have a chance to adapt his value of b depending on g_a, because it has to commit to a value of g_b before learning g_a. The same is valid for the key generation between the impostor and the party B.

-

The use of hash commitment in the DH exchange constrains the attacker to only one guess to generate the correct visualization in their attack, which means that using just over 33 bits of entropy represented by four emoji in the visualization is enough to make a successful attack highly improbable.

-
-

For a slightly more user-friendly explanation of the above see: How are calls authenticated?

-
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/api/end-to-end_v1.html b/data/corefork.telegram.org/api/end-to-end_v1.html deleted file mode 100644 index 6cd75973a3..0000000000 --- a/data/corefork.telegram.org/api/end-to-end_v1.html +++ /dev/null @@ -1,225 +0,0 @@ - - - - - Secret chats, end-to-end encryption (v. 1.0, DEPRECATED) - - - - - - - - - - - - - -
- -
-
-
- -

Secret chats, end-to-end encryption (v. 1.0, DEPRECATED)

- -
-

This document describes end-to-end encrypted Secret Chats in MTProto 1.0, its status is DEPRECATED. -For information on end-to-end encryption used in up-to-date Telegram clients, kindly see this document.

-
-
Related articles
-

-
-

Secret Chats are one-on-one chats wherein messages are encrypted with a key held only by the chat’s participants. Please note that the schema for end-to-end encrypted Secret Chats is different from what is used for cloud chats:

-
- -
-

Key Generation

-

The Diffie-Hellman protocol is used for key generation. For more information, see Wikipedia.

-

Let us consider the following scenario: User A would like to initiate encrypted communication with User B.

-

Sending a Request

-

User A executes messages.getDhConfig to obtain the Diffie-Hellman parameters: a prime p, and a high order element g.

-

Executing this method before each new key generation procedure is of vital importance. It makes sense to cache the values of the parameters together with the version in order to avoid having to receive all of the values every time. If the version stored on the client is still up-to-date, the server will return the constructor messages.dhConfigNotModified.

-

Client is expected to check whether p is a safe 2048-bit prime (meaning that both p and (p-1)/2 are prime, and that 2^2047 < p < 2^2048), and that g generates a cyclic subgroup of prime order (p-1)/2, i.e. is a quadratic residue mod p. Since g is always equal to 2, 3, 4, 5, 6 or 7, this is easily done using quadratic reciprocity law, yielding a simple condition on p mod 4g -- namely, p mod 8 = 7 for g = 2; p mod 3 = 2 for g = 3; no extra condition for g = 4; p mod 5 = 1 or 4 for g = 5; p mod 24 = 19 or 23 for g = 6; and p mod 7 = 3, 5 or 6 for g = 7. After g and p have been checked by the client, it makes sense to cache the result, so as to avoid repeating lengthy computations in future. This cache might be shared with one used for Authorization Key generation.

-

If the client has an inadequate random number generator, it makes sense to pass the random_length parameter (random_length> 0) so the server generates its own random sequence random of the appropriate length. -Important: using the server’s random sequence in its raw form may be unsafe. It must be combined with a client sequence, for example, by generating a client random number of the same length (client_random) and using final_random := random XOR client_random.

-

Client A computes a 2048-bit number a (using sufficient entropy or the server’s random; see above) and executes messages.requestEncryption after passing in g_a := pow(g, a) mod dh_prime.

-

User B receives the update updateEncryption for all associated authorization keys (all authorized devices) with the chat constructor encryptedChatRequested. The user must be shown basic information about User A and must be prompted to accept or reject the request.

-

Both clients are to check that g, g_a and g_b are greater than one and smaller than p-1. We recommend checking that g_a and g_b are between 2^{2048-64} and p - 2^{2048-64} as well.

-

Accepting a Request

-

After User B confirms the creation of a secret chat with A in the client interface, Client B also receives up-to-date configuration parameters for the Diffie-Hellman method. Thereafter, it generates a random 2048-bit number, b, using rules similar to those for a.

-

Having received g_a from the update with encryptedChatRequested, it can immediately generate the final shared key: key = (pow(g_a, b) mod dh_prime). If key length < 256 bytes, add several leading zero bytes as padding — so that the key is exactly 256 bytes long. Its fingerprint, key_fingerprint, is equal to the 64 last bits of SHA1 (key).

-

Note: this fingerprint is used as a sanity check for the key exchange procedure to detect bugs while developing client software — it is not connected to the key visualization used on the clients as means of external authentication in secret chats. Key visualizations on the clients are generated using the first 128 bits of SHA1(initial key) followed by the first 160 bits of SHA256(key used when secret chat was updated to layer 46).

-

Client B executes messages.acceptEncryption after passing it g_b := pow(g, b) mod dh_prime and key_fingerprint.

-

For all of Client B’s authorized devices, except the current one, updateEncryption updates are sent with the constructor encryptedChatDiscarded. Thereafter, the only device that will be able to access the secret chat is Device B, which made the call to messages.acceptEncryption.

-

User A will be sent an updateEncryption update with the constructor encryptedChat, for the authorization key that initiated the chat.

-

With g_b from the update, Client A can also receive the shared key key = (pow(g_b, a) mod dh_prime). If key length < 256 bytes, add several leading zero bytes as padding — so that the key is exactly 256 bytes long. If the fingerprint for the received key is identical to the one that was passed to encryptedChat, incoming messages can be sent and processed. Otherwise, messages.discardEncryption must be executed and the user notified.

-

Perfect Forward Secrecy

-

In order to keep past communications safe, official Telegram clients will initiate re-keying once a key has been used to decrypt and encrypt more than 100 messages, or has been in use for more than one week, provided the key has been used to encrypt at least one message. Old keys are then securely discarded and cannot be reconstructed, even with access to the new keys currently in use.

-
-

The re-keying protocol is further described in this article: Perfect Forward Secrecy in Secret Chats.

-
-

Please note that your client must support Forward Secrecy in Secret Chats to be compatible with official Telegram clients.

-

Sending and Receiving Messages in a Secret Chat

-

Serialization and Encryption of Outgoing Messages

-

A TL object of type DecryptedMessage is created and contains the message in plain text. For backward compatibility, the object must be wrapped in the constructor decryptedMessageLayer with an indication of the supported layer (starting with 8). -The TL-Schema for end-to-end encrypted messages contents is represented here ».

-

The resulting construct is serialized as an array of bytes using generic TL rules. The resulting array is padded at the top with 4 bytes of the array length not counting these 4 bytes. -A message key, msg_key, is computed as the 128 low-order bits of the SHA1 of the data obtained in the previous step. -The byte array is padded with random data until its length is divisible by 16 bytes. -An AES key and an initialization vector are computed ( key is the shared key obtained during Key Generation; in MTProto 1.0, x = 0 ):

-
    -
  • msg_key = substr (SHA1 (plaintext), 4, 16);
  • -
  • sha1_a = SHA1 (msg_key + substr (key, x, 32));
  • -
  • sha1_b = SHA1 (substr (key, 32+x, 16) + msg_key + substr (key, 48+x, 16));
  • -
  • sha1_с = SHA1 (substr (key, 64+x, 32) + msg_key);
  • -
  • sha1_d = SHA1 (msg_key + substr (key, 96+x, 32));
  • -
  • aes_key = substr (sha1_a, 0, 8) + substr (sha1_b, 8, 12) + substr (sha1_c, 4, 12);
  • -
  • aes_iv = substr (sha1_a, 8, 12) + substr (sha1_b, 0, 8) + substr (sha1_c, 16, 4) + substr (sha1_d, 0, 8);
  • -
-

Data is encrypted with a 256-bit key, aes_key, and a 256-bit initialization vector, aes-iv, using AES-256 encryption with infinite garble extension (IGE). Encryption key fingerprint key_fingerprint and the message key msg_key are added at the top of the resulting byte array.

-

Encrypted data is embedded into a messages.sendEncrypted API call and passed to Telegram server for delivery to the other party of the Secret Chat.

-

Decrypting an Incoming Message

-

The steps above are performed in reverse order. -When an encrypted message is received, you must check that msg_key is in fact equal to the 128 low-order bits of the SHA1 hash of the decrypted message. -If the message layer is greater than the one supported by the client, the user must be notified that the client version is out of date and prompted to update.

-

Sequence numbers

-

It is necessary to interpret all messages in their original order to protect against possible manipulations. Secret chats support a special mechanism for handling seq_no counters independently from the server.

-
-

Proper handling of these counters is further described in this article: Sequence numbers in Secret Chats.

-
-

Please note that your client must support sequence numbers in Secret Chats to be compatible with official Telegram clients.

-

Sending Encrypted Files

-

All files sent to secret chats are encrypted with one-time keys that are in no way related to the chat’s shared key. Before an encrypted file is sent, it is assumed that the encrypted file’s address will be attached to the outside of an encrypted message using the file parameter of the messages.sendEncryptedFile method and that the key for direct decryption will be sent in the body of the message (the key parameter in the constructors decryptedMessageMediaPhoto, decryptedMessageMediaVideo and decryptedMessageMediaFile.

-

Prior to a file being sent to a secret chat, 2 random 256-bit numbers are computed which will serve as the AES key and initialization vector used to encrypt the file. AES-256 encryption with infinite garble extension (IGE) is used in like manner.

-

The key fingerprint is computed as follows:

-
    -
  • digest = md5(key + iv)
  • -
  • fingerprint = substr(digest, 0, 4) XOR substr(digest, 4, 4)
  • -
-

The encrypted contents of a file are stored on the server in much the same way as those of a file in cloud chats: piece by piece using calls to upload.saveFilePart. -A subsequent call to messages.sendEncryptedFile will assign an identifier to the stored file and send the address together with the message. The recipient will receive an update with encryptedMessage, and the file parameter will contain file information.

-

Incoming and outgoing encrypted files can be forwarded to other secret chats using the constructor inputEncryptedFile to avoid saving the same content on the server twice.

-

Working with an Update Box

-

Secret chats are associated with specific devices (or rather with authorization keys), not users. A conventional message box, which uses pts to describe the client’s status, is not suitable, because it is designed for long-term message storage and message access from different devices.

-

An additional temporary message queue is introduced as a solution to this problem. When an update regarding a message from a secret chat is sent, a new value of qts is sent, which helps reconstruct the difference if there has been a long break in the connection or in case of loss of an update.

-

As the number of events increases, the value of qts increases monotonically (not always by 1). The initial value may not (and will not) be equal to 0.

-

The fact that events from the temporary queue have been received and stored by the client is acknowledged explicitly by a call to the messages.receivedQueue method or implicitly by a call to updates.getDifference (the value of qts passed, not the final state). All messages acknowledged as delivered by the client, as well as any messages older than 7 days, may (and will) be deleted from the server.

-

Upon de-authorization, the event queue of the corresponding device will be forcibly cleared, and the value of qts will become irrelevant.

-

Updating to new layers

-

Your client should always store the maximal layer that is known to be supported by the client on the other side of a secret chat. When the secret chat is first created, this value should be initialized to 8, the first layer where Secret Chats became available. This remote layer value must always be updated immediately after receiving any packet containing information of an upper layer, i.e.:

-
    -
  • any secret chat message containing layer_no in its decryptedMessageLayer with layer>=17, or
  • -
  • a decryptedMessageActionNotifyLayer service message, wrapped as if it were the decryptedMessageService constructor of the obsolete layer 8 (constructor decryptedMessageService#aa48327d).
  • -
-

Notifying the remote client about your local layer

-

In order to notify the remote client of your local layer, your client must send a message of the decryptedMessageActionNotifyLayer type. This notification must be wrapped in a constructor of an appropriate layer. For instance, if the remote layer for the chat in question is deemed to be lower than 17, the notification must be wrapped as if it were the decryptedMessageService constructor of the obsolete layer 8 (constructor decryptedMessageService#aa48327d), despite the fact that the decryptedMessageActionNotifyLayer constructor is actually not present in Layer 8.

-

There are three cases when your client must notify the remote client about its local layer:

-
    -
  1. As soon as a new secret chat has been created, immediately after the secret key has been successfully exchanged.
  2. -
  3. Immediately after the remote layer value is updated to layer 17 or higher. An exception to this case is when the secret chat in question has been created less than 15 seconds ago. In this case the notification was already sent (see 1).
  4. -
  5. Immediately after the local client has been updated to support a new secret chat layer. In this case notifications must be sent to all currently existing secret chats. Note that this is only necessary when updating to new layers that contain changes in the secret chats implementation (e.g. you don’t need to do this when your client is updated from Layer 17 to Layer 18).
  6. -
-
-

Note that all pending obsolete layer messages must be sent prior to the layer update notification (more on this in Handling Sequence numbers).

-
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/api/errors.html b/data/corefork.telegram.org/api/errors.html deleted file mode 100644 index a7f8aeec7d..0000000000 --- a/data/corefork.telegram.org/api/errors.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - Error handling - - - - - - - - - - - - - -
- -
-
-
- -

Error handling

- -

There will be errors when working with the API, and they must be correctly handled on the client.

-

An error is characterized by several parameters:

-

Error Code

-

Numerical value similar to HTTP status. Contains information on the type of error that occurred: for example, a data input error, privacy error, or server error. This is a required parameter.

-

Error Type

-

A string literal in the form of /[A-Z_0-9]+/, which summarizes the problem. For example, AUTH_KEY_UNREGISTERED. This is an optional parameter.

-
-

Error Constructors

-

There should be a way to handle errors that are returned in rpc_error constructors.

-

Below is a list of error codes and their meanings:

-

303 SEE_OTHER

-

The request must be repeated, but directed to a different data center.

-

Examples of Errors:

-
    -
  • FILE_MIGRATE_X: the file to be accessed is currently stored in a different data center.
  • -
  • PHONE_MIGRATE_X: the phone number a user is trying to use for authorization is associated with a different data center.
  • -
  • NETWORK_MIGRATE_X: the source IP address is associated with a different data center (for registration)
  • -
  • USER_MIGRATE_X: the user whose identity is being used to execute queries is associated with a different data center (for registration)
  • -
-

In all these cases, the error description’s string literal contains the number of the data center (instead of the X) to which the repeated query must be sent. -More information about redirects between data centers »

-

400 BAD_REQUEST

-

The query contains errors. In the event that a request was created using a form and contains user generated data, the user should be notified that the data must be corrected before the query is repeated.

-

Examples of Errors:

-
    -
  • FIRSTNAME_INVALID: The first name is invalid
  • -
  • LASTNAME_INVALID: The last name is invalid
  • -
  • PHONE_NUMBER_INVALID: The phone number is invalid
  • -
  • PHONE_CODE_HASH_EMPTY: phone_code_hash is missing
  • -
  • PHONE_CODE_EMPTY: phone_code is missing
  • -
  • PHONE_CODE_EXPIRED: The confirmation code has expired
  • -
  • API_ID_INVALID: The api_id/api_hash combination is invalid
  • -
  • PHONE_NUMBER_OCCUPIED: The phone number is already in use
  • -
  • PHONE_NUMBER_UNOCCUPIED: The phone number is not yet being used
  • -
  • USERS_TOO_FEW: Not enough users (to create a chat, for example)
  • -
  • USERS_TOO_MUCH: The maximum number of users has been exceeded (to create a chat, for example)
  • -
  • TYPE_CONSTRUCTOR_INVALID: The type constructor is invalid
  • -
  • FILE_PART_INVALID: The file part number is invalid
  • -
  • FILE_PARTS_INVALID: The number of file parts is invalid
  • -
  • FILE_PART_Х_MISSING: Part X (where X is a number) of the file is missing from storage
  • -
  • MD5_CHECKSUM_INVALID: The MD5 checksums do not match
  • -
  • PHOTO_INVALID_DIMENSIONS: The photo dimensions are invalid
  • -
  • FIELD_NAME_INVALID: The field with the name FIELD_NAME is invalid
  • -
  • FIELD_NAME_EMPTY: The field with the name FIELD_NAME is missing
  • -
  • MSG_WAIT_FAILED: A request that must be completed before processing the current request returned an error
  • -
  • MSG_WAIT_TIMEOUT: A request that must be completed before processing the current request didn't finish processing yet
  • -
-

401 UNAUTHORIZED

-

There was an unauthorized attempt to use functionality available only to authorized users.

-

Examples of Errors:

-
    -
  • AUTH_KEY_UNREGISTERED: The key is not registered in the system
  • -
  • AUTH_KEY_INVALID: The key is invalid
  • -
  • USER_DEACTIVATED: The user has been deleted/deactivated
  • -
  • SESSION_REVOKED: The authorization has been invalidated, because of the user terminating all sessions
  • -
  • SESSION_EXPIRED: The authorization has expired
  • -
  • AUTH_KEY_PERM_EMPTY: The method is unavailble for temporary authorization key, not bound to permanent
  • -
-

403 FORBIDDEN

-

Privacy violation. For example, an attempt to write a message to someone who has blacklisted the current user.

-

404 NOT_FOUND

-

An attempt to invoke a non-existent object, such as a method.

-

406 NOT_ACCEPTABLE

-

Similar to 400 BAD_REQUEST, but the app should not display any error messages to user in UI as a result of this response. The error message will be delivered via updateServiceNotification instead.

-

420 FLOOD

-

The maximum allowed number of attempts to invoke the given method with the given input parameters has been exceeded. For example, in an attempt to request a large number of text messages (SMS) for the same phone number.

-

Error Example:

-
    -
  • FLOOD_WAIT_X: A wait of X seconds is required (where X is a number)
  • -
-

500 INTERNAL

-

An internal server error occurred while a request was being processed; for example, there was a disruption while accessing a database or file storage.

-

If a client receives a 500 error, or you believe this error should not have occurred, please collect as much information as possible about the query and error and send it to the developers.

-

Other Error Codes

-

If a server returns an error with a code other than the ones listed above, it may be considered the same as a 500 error and treated as an internal server error.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/api/files.html b/data/corefork.telegram.org/api/files.html deleted file mode 100644 index 5cb328b3b2..0000000000 --- a/data/corefork.telegram.org/api/files.html +++ /dev/null @@ -1,568 +0,0 @@ - - - - - Uploading and Downloading Files - - - - - - - - - - - - - -
- -
-
-
- -

Uploading and Downloading Files

- -
- -

When working with the API, it is sometimes necessary to send a relatively large file to the server. For example, when sending a message with a photo/video attachment or when setting the current user’s profile picture.

-

Uploading files

-

There are a number of API methods to save files. The schema of the types and methods used is presented below:

-
inputFile#f52ff27f id:long parts:int name:string md5_checksum:string = InputFile;
-inputFileBig#fa4f0bb5 id:long parts:int name:string = InputFile;
-
-
-inputEncryptedFileUploaded#64bd0306 id:long parts:int md5_checksum:string key_fingerprint:int = InputEncryptedFile;
-inputEncryptedFileBigUploaded#2dc173c8 id:long parts:int key_fingerprint:int = InputEncryptedFile;
-
-inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;
-inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;
-
-inputMediaUploadedPhoto#1e287d04 flags:# file:InputFile stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
-inputMediaUploadedDocument#5b38c6c1 flags:# nosound_video:flags.3?true force_file:flags.4?true file:InputFile thumb:flags.2?InputFile mime_type:string attributes:Vector<DocumentAttribute> stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
-
-inputChatUploadedPhoto#c642724e flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = InputChatPhoto;
-
-
----functions---
-
-messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-messages.uploadMedia#519bc2b1 peer:InputPeer media:InputMedia = MessageMedia;
-messages.sendEncryptedFile#5559481d flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes file:InputEncryptedFile = messages.SentEncryptedMessage;
-
-photos.uploadProfilePhoto#89f30f69 flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = photos.Photo;    
-
-upload.saveFilePart#b304a621 file_id:long file_part:int bytes:bytes = Bool;
-upload.saveBigFilePart#de7b673d file_id:long file_part:int file_total_parts:int bytes:bytes = Bool;
-

Before transmitting the contents of the file itself, the file has to be assigned a unique 64-bit client identifier: file_id.

-

The file’s binary content is then split into parts. All parts must have the same size ( part_size ) and the following conditions must be met:

-
    -
  • part_size % 1024 = 0 (divisible by 1KB)
  • -
  • 524288 % part_size = 0 (512KB must be evenly divisible by part_size)
  • -
-

The last part does not have to satisfy these conditions, provided its size is less than part_size.

-

Each part should have a sequence number, file_part, with a value ranging from 0 to 2,999.

-

After the file has been partitioned you need to choose a method for saving it on the server. Use upload.saveBigFilePart in case the full size of the file is more than 10 MB and upload.saveFilePart for smaller files.

-

Each call saves a portion of the data in a temporary location on the server to be used later. The storage life of each portion of data is between several minutes and several hours (depending on how busy the storage area is). After this time, the file part will become unavailable. To increase the time efficiency of a file save operation, we recommend using a call queue, so X pieces of the file are being saved at any given moment in time. Each successful operation to save a part invokes the method call to save the next part. The value of X can be tuned to achieve maximum performance.

-

When using one of the methods mentioned above to save file parts, one of the following data input errors may be returned:

-
    -
  • FILE_PARTS_INVALID - Invalid number of parts. The value is not between 1..3000
  • -
  • FILE_PART_INVALID: The file part number is invalid. The value is not between 0 and 2,999.
  • -
  • FILE_PART_TOO_BIG: The size limit (512 KB) for the content of the file part has been exceeded
  • -
  • FILE_PART_EMPTY: The file part sent is empty
  • -
  • FILE_PART_SIZE_INVALID - 512KB cannot be evenly divided by part_size
  • -
  • FILE_PART_SIZE_CHANGED - The part size is different from the size of one of the previous parts in the same file
  • -
-

While the parts are being uploaded, an MD5 hash of the file contents can also be computed to be used later as the md5_checksum parameter in the inputFile constructor (since it is checked only by the server, for encrypted secret chat files it must be generated from the encrypted file). -After the entire file is successfully saved, the final method may be called and passed the generated inputFile object. In case the upload.saveBigFilePart method is used, the inputFileBig constructor must be passed, in other cases use inputFile.

- -

The file save operation may return one of the following data input errors:

-
    -
  • FILE_PARTS_INVALID: The number of file parts is invalid The value is not between 1 and 3,000.
  • -
  • FILE_PART_Х_MISSING: Part X (where X is a number) of the file is missing from storage. Try repeating the method call to resave the part.
  • -
  • MD5_CHECKSUM_INVALID: The file’s checksum did not match the md5_checksum parameter
  • -
-

Albums, grouped media

-
inputMediaUploadedPhoto#1e287d04 flags:# file:InputFile stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
-inputMediaUploadedDocument#5b38c6c1 flags:# nosound_video:flags.3?true force_file:flags.4?true file:InputFile thumb:flags.2?InputFile mime_type:string attributes:Vector<DocumentAttribute> stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
-
-inputSingleMedia#1cc6e91f flags:# media:InputMedia random_id:long message:string entities:flags.0?Vector<MessageEntity> = InputSingleMedia;
-
----functions---
-
-messages.sendMultiMedia#cc0110cb flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int multi_media:Vector<InputSingleMedia> schedule_date:flags.10?int = Updates;
-

Telegram allows grouping photos into albums and generic files (audio, docuemnts) into media groups.

-

To do this, messages.sendMultiMedia is used, wrapping each InputMedia constructor (uploaded or pre-existing, maximum 10 per media group) into an inputSingleMedia constructor, optionally providing a custom per-file caption in message.

-

For photo albums, clients should display an album caption only if exactly one photo in the group has a caption, otherwise no album caption should be displayed, and only when viewing in detail a specific photo of the group the caption should be shown.
-Other grouped media can display a caption under each file.

-

Re-using pre-uploaded files

-
document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
-
----functions---
-
-messages.getDocumentByHash#338e2464 sha256:bytes size:int mime_type:string = Document;
-

For some types of documents like GIFs, messages.getDocumentByHash can be used to search for the document on Telegram servers. -The SHA256 hash of the file is computed, and it is passed along with the file's mime type and size to the method: if the file type is correct and the file is found, a document is returned.

-

Uploading profile or chat pictures

-
photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;
-
-photos.photo#20212ca8 photo:Photo users:Vector<User> = photos.Photo;
-
-inputPhoto#3bb3b94a id:long access_hash:long file_reference:bytes = InputPhoto;
-
-inputFile#f52ff27f id:long parts:int name:string md5_checksum:string = InputFile;
-
-inputChatUploadedPhoto#c642724e flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = InputChatPhoto;
-inputChatPhoto#8953ad37 id:InputPhoto = InputChatPhoto;
-
----functions---
-
-photos.updateProfilePhoto#72d4742c id:InputPhoto = photos.Photo;
-photos.uploadProfilePhoto#89f30f69 flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = photos.Photo;
-
-messages.editChatPhoto#35ddd674 chat_id:long photo:InputChatPhoto = Updates;
-
-channels.editPhoto#f12e57c9 channel:InputChannel photo:InputChatPhoto = Updates;
-

User profile pictures can be uploaded using the photos.uploadProfilePhoto method: the actual profile picture has to be uploaded as for normal files.
-photos.uploadProfilePhoto can also be used to reupload previously uploaded profile pictures.

-

Animated profile pictures

-

Animated profile pictures are also supported, by populating the video constructor: square MPEG4 videos up to 1080x1080 are supported, 800x800 is the recommended resolution.
-The video_start_ts is a floating point UNIX timestamp in seconds, indicating the frame of the video that should be used as static preview.

-

Chat, channel and supergroup profile photos and videos can be uploaded using messages.editChatPhoto (legacy groups) or channels.editPhoto (channels, supergroups).
-Use the inputChatPhoto to reuse previously uploaded profile pictures.

-

Downloading files

-

There are methods available to download files which have been successfully uploaded. The schema of the types and methods used is presented below:

-
upload.file#96a18d5 type:storage.FileType mtime:int bytes:bytes = upload.File;
-upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;
-
-storage.fileUnknown#aa963b05 = storage.FileType;
-storage.fileJpeg#7efe0e = storage.FileType;
-storage.fileGif#cae1aadf = storage.FileType;
-storage.filePng#a4f63c0 = storage.FileType;
-storage.fileMp3#528a0677 = storage.FileType;
-storage.fileMov#4b09ebbc = storage.FileType;
-storage.filePartial#40bc6f52 = storage.FileType;
-storage.fileMp4#b3cea0e4 = storage.FileType;
-storage.fileWebp#1081464c = storage.FileType;
-
----functions---
-
-upload.getFile#b15a9afc flags:# precise:flags.0?true cdn_supported:flags.1?true location:InputFileLocation offset:int limit:int = upload.File;
-

Any file can be downloaded by calling upload.getFile. -The data for the input parameter of the InputFileLocation type is generated as follows:

-
inputFileLocation#dfdaabe1 volume_id:long local_id:int secret:long file_reference:bytes = InputFileLocation;
-inputEncryptedFileLocation#f5235d55 id:long access_hash:long = InputFileLocation;
-inputDocumentFileLocation#bad07584 id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;
-inputSecureFileLocation#cbc7ee28 id:long access_hash:long = InputFileLocation;
-inputTakeoutFileLocation#29be5899 = InputFileLocation;
-inputPhotoFileLocation#40181ffe id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;
-inputPhotoLegacyFileLocation#d83466f3 id:long access_hash:long file_reference:bytes volume_id:long local_id:int secret:long = InputFileLocation;
-inputPeerPhotoFileLocation#37257e99 flags:# big:flags.0?true peer:InputPeer photo_id:long = InputFileLocation;
-inputStickerSetThumb#9d84f3db stickerset:InputStickerSet thumb_version:int = InputFileLocation;
-inputGroupCallStream#598a92a flags:# call:InputGroupCall time_ms:long scale:int video_channel:flags.0?int video_quality:flags.0?int = InputFileLocation;
-
-inputStickerSetEmpty#ffb62b95 = InputStickerSet;
-inputStickerSetID#9de7a269 id:long access_hash:long = InputStickerSet;
-inputStickerSetShortName#861cc8a0 short_name:string = InputStickerSet;
-inputStickerSetAnimatedEmoji#28703c8 = InputStickerSet;
-inputStickerSetDice#e67f520e emoticon:string = InputStickerSet;
-inputStickerSetAnimatedEmojiAnimations#cde3739 = InputStickerSet;
-
-inputPeerSelf#7da07ec9 = InputPeer;
-inputPeerChat#35a95cb9 chat_id:long = InputPeer;
-inputPeerUser#dde8a54c user_id:long access_hash:long = InputPeer;
-inputPeerChannel#27bcbbfc channel_id:long access_hash:long = InputPeer;
-
-photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;
-document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
-
-photoSize#75c78e60 type:string w:int h:int size:int = PhotoSize;
-photoCachedSize#21e1ad6 type:string w:int h:int bytes:bytes = PhotoSize;
-
-chatPhoto#1c6e1c11 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = ChatPhoto;
-userProfilePhoto#82d1f706 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = UserProfilePhoto;
-
    -
  • -

    For photos, inputPhotoFileLocation is used:

    -
      -
    • id, file_reference and access_hash taken from the photo constructor
    • -
    • thumb_size taken from the type field of the desired PhotoSize of the photo
    • -
    -
  • -
  • -

    For profile pictures of users, channels, supergroups and groups, inputPeerPhotoFileLocation has to be used:

    -
      -
    • peer is the identifier of the peer whose photo we want to download
    • -
    • big is used to choose whether to download the full-resolution picture, or just the thumbnail
    • -
    • photo_id is extracted from the chatPhoto or userProfilePhoto of the desired profile photo
    • -
    -
  • -
  • -

    For documents, inputDocumentFileLocation is used:

    -
      -
    • id, file_reference and access_hash taken from the document constructor
    • -
    • If downloading the thumbnail of a document, thumb_size should be taken from the type field of the desired PhotoSize of the photo; otherwise, provide an empty string.
    • -
    -
  • -
  • -

    For previews of sticker sets, inputStickerSetThumb is used (note: to download stickers and previews of stickers use the document method described above for documents):

    - -
  • -
  • -

    For encrypted secret chat and telegram passport documents, respectively inputEncryptedFileLocation and inputSecureFileLocation have to be used, with parameters extracted from encryptedFile and secureFile (passport docs).

    -
  • -
  • -

    For livestream chunks, inputGroupCallStream is used:

    -
      -
    • call contains the related group call ID+access hash, taken from the groupCall constructor.
    • -
    • time_ms specifies the timestamp to fetch
    • -
    • scale specifies the duration of the video segment to fetch in milliseconds, by bitshifting 1000 to the right scale times: duration_ms := 1000 >> scale
    • -
    • video_channel specifies the video channel to fetch
    • -
    • video_quality specifies the selected video quality (0 = lowest, 1 = medium, 2 = best)
    • -
    -
  • -
  • -

    For old deprecated photos, if the client has cached some old fileLocations with the deprecated secret identifier, inputFileLocation or inputPhotoLegacyFileLocation is used (this is mainly used for backwards compatiblity with bot API file IDs, all user clients must use the modern inputPhotoFileLocation file IDs):

    -
      -
    • All fields are taken from the previously cached fileLocation except for file_reference, access_hash and id, which are taken from the photo constructor (the last two fields are used only if available, in which case inputPhotoLegacyFileLocation is used instead of inputFileLocation).
    • -
    -
  • -
-

The size of each file in bytes is available, which makes it possible to download the file in parts using the parameters offset and limit, similar to the way files are uploaded.

-

If precise flag is not specified, then

-
    -
  • The parameter offset must be divisible by 4 KB.
  • -
  • The parameter limit must be divisible by 4 KB.
  • -
  • 1048576 (1 MB) must be divisible by limit.
  • -
-

If precise is specified, then

-
    -
  • The parameter offset must be divisible by 1 KB.
  • -
  • The parameter limit must be divisible by 1 KB.
  • -
  • limit must not exceed 1048576 (1 MB).
  • -
-

In any case the requested part should be within one 1 MB chunk from the beginning of the file, i. e.

-
    -
  • offset / (1024 * 1024) == (offset + limit - 1) / (1024 * 1024).
  • -
-

The file download operation may return a FILE_REFERENCE_EXPIRED error (or another error starting with FILE_REFERENCE_): in this case, the file_reference field of the input location must be refreshed. -The file download operation may return an upload.fileCdnRedirect constructor: in this case, these instructions must be followed for downloading CDN files. -The file download operation may also return one of the following data input errors:

-
    -
  • FILE_ID_INVALID: The file address is invalid
  • -
  • OFFSET_INVALID: The offset value is invalid
  • -
  • LIMIT_INVALID: The limit value is invalid
  • -
  • FILE_MIGRATE_X: The file is in the datacenter No. X
  • -
-

Verifying downloaded chunks

-
fileHash#6242c773 offset:int limit:int hash:bytes = FileHash;
-
----functions---
-
-upload.getFileHashes#c7025931 location:InputFileLocation offset:int = Vector<FileHash>;
-

In order to confirm the integrity of the downloaded file, clients are recommended to verify hashes for each downloaded part, as for CDN DCs. -upload.getFileHashes contain FileHash constructors. Each of these constructors contains the SHA-256 hash of a part of the file that starts with offset and takes limit bytes.

-

Before saving each portion of the data received from the DC into the file, the client can confirm that its hash matches the hash that was received from the master DC. If missing a hash for any file part, client developers must use the upload.getFileHashes method to obtain the missing hash.

-

Handling audio, video and vector previews

-

Schema:

-
photoSizeEmpty#e17e23c type:string = PhotoSize;
-photoSize#75c78e60 type:string w:int h:int size:int = PhotoSize;
-photoCachedSize#21e1ad6 type:string w:int h:int bytes:bytes = PhotoSize;
-photoStrippedSize#e0b0bc2e type:string bytes:bytes = PhotoSize;
-photoSizeProgressive#fa3efb95 type:string w:int h:int sizes:Vector<int> = PhotoSize;
-photoPathSize#d8214d41 type:string bytes:bytes = PhotoSize;
-
-videoSize#de33b094 flags:# type:string w:int h:int size:int video_start_ts:flags.0?double = VideoSize;
-
-document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
-photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;
-
-photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;
-

Telegram attaches a vector of thumbnails with reduced resolution to all uploaded media.
-The server also generates a trimmed and scaled down video preview for videos, GIFs and animated profile pictures.

-

Image thumbnail types

-

Each photo preview has a specific type, indicating the resolution and image transform that was applied server-side.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TypeImage filterSize
sbox100x100
mbox320x320
xbox800x800
ybox1280x1280
wbox2560x2560
acrop160x160
bcrop320x320
ccrop640x640
dcrop1280x1280
-

Special types:

- - - - - - - - - - - - - - - - - -
TypeImage filter
istrip
joutline
-

Stripped thumbnails

-
photoStrippedSize#e0b0bc2e type:string bytes:bytes = PhotoSize;
-

A photoStrippedSize (with type i) is an extremely low-res thumbnail, embedded directly inside media location objects.
-It should be shown to the user in chat message previews, or while still downloading the most appropriately sized photoSize through the media DCs as described above.

-

The stripped bytes payload should be inflated to a JPG payload as seen here ».

-

Vector thumbnails

-
photoPathSize#d8214d41 type:string bytes:bytes = PhotoSize;
-

Messages with animated stickers can have a compressed svg (< 300 bytes) to show the outline of the sticker before fetching the actual lottie animation. -Animated sticker outlines will have a j type photoPathSize thumbnail.

-

This specific vector thumbnail consists in an SVG path, specially encoded to save space.
-This path will be the outline of the animated sticker, and should be shown to the user while downloading the actual sticker.

-

As for stripped sizes, the payload should be inflated using the following algorithm:

-
encoded := photoPathSize.bytes
-
-lookup := "AACAAAAHAAALMAAAQASTAVAAAZaacaaaahaaalmaaaqastava.az0123456789-,"
-
-path := "M"
-
-len := strlen(encoded)
-for (i = 0; i < len; i++) {
-  num := ord(encoded[i])
-  if (num >= 128 + 64) {
-    path += lookup[num - 128 - 64]
-  } else {
-    if (num >= 128) {
-      path += ','
-    } else if (num >= 64) {
-      path += '-'
-    }
-    path += itoa(num & 63)
-  }
-}
-path += "z"
-

path will contain the actual SVG path that can be directly inserted in the d attribute of an svg <path> element:

-
<?xml version="1.0" encoding="utf-8"?>
-<svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink"
-   viewBox="0 0 512 512" xml:space="preserve">
-<path d="{$path}"/>
-</svg>
-

Video types

-
videoSize#de33b094 flags:# type:string w:int h:int size:int video_start_ts:flags.0?double = VideoSize;
-

A videoSize constructor is typically used for animated profile pictures and video previews.

- - - - - - - - - - - - - - - - - - - - -
TypeDescriptionFormat
uAnimated profile pictureMPEG4
vVideo previewMPEG4
-

Downloading webfiles

-

Remote HTTP files sent by inline bots in response to inline queries and in other places are represented by WebDocument constructors. -When forwarding such remote HTTP files, they should be sent using external InputMedia constructors. -Remote HTTP files can only be downloaded directly by the client if contained in a webDocumentNoProxy constructor: in this case, the file is deemed safe to download (this is the case for HTTPS files from certain trusted domains).

-

However, if the remote file is contained in a webDocument, to avoid leaking sensitive information the file must be downloaded through telegram's servers. -This can be done in a manner similar to normal files, with the difference that upload.getWebFile must be used, instead.

-
upload.webFile#21e753bc size:int mime_type:string file_type:storage.FileType mtime:int bytes:bytes = upload.WebFile;
-
-storage.fileUnknown#aa963b05 = storage.FileType;
-storage.fileJpeg#7efe0e = storage.FileType;
-storage.fileGif#cae1aadf = storage.FileType;
-storage.filePng#a4f63c0 = storage.FileType;
-storage.fileMp3#528a0677 = storage.FileType;
-storage.fileMov#4b09ebbc = storage.FileType;
-storage.filePartial#40bc6f52 = storage.FileType;
-storage.fileMp4#b3cea0e4 = storage.FileType;
-storage.fileWebp#1081464c = storage.FileType;
-
- ---functions---
-
-upload.getWebFile#24e6818d location:InputWebFileLocation offset:int limit:int = upload.WebFile;
-

The InputWebFileLocation constructor is generated as follows.

-
inputWebFileLocation#c239d686 url:string access_hash:long = InputWebFileLocation;
-inputWebFileGeoPointLocation#9f2221c9 geo_point:InputGeoPoint access_hash:long w:int h:int zoom:int scale:int = InputWebFileLocation;
-
-webDocument#1c570ed1 url:string access_hash:long size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;
-
-inputGeoPoint#48222faf flags:# lat:double long:double accuracy_radius:flags.0?int = InputGeoPoint;
-
-geoPoint#b2a2f663 flags:# long:double lat:double access_hash:long accuracy_radius:flags.0?int = GeoPoint;
-
    -
  • inputWebFileLocation is simply generated by taking the url and access_hash fields of the webDocument constructor.
  • -
  • inputWebFileGeoPointLocation is used to download a server-generated image with the map preview from a geoPoint.
      -
    • geo_point is generated from the lat, long accuracy_radius parameters of the geoPoint
    • -
    • access_hash is the access hash of the geoPoint
    • -
    • w - Map width in pixels before applying scale; 16-1024
    • -
    • h - Map height in pixels before applying scale; 16-1024
    • -
    • zoom - Map zoom level; 13-20
    • -
    • scale - Map scale; 1-3
    • -
    -
  • -
-

General Considerations

-

It is recommended that large queries (upload.getFile, upload.saveFilePart, upload.getWebFile) be handled through a separate session and a separate connection, in which no methods other than these should be executed. If this is done, then data transfer will cause less interference with getting updates and other method calls.

-

Related articles

-

Handling file references

-

How to handle file references.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/folders.html b/data/corefork.telegram.org/api/folders.html deleted file mode 100644 index 238f3f4636..0000000000 --- a/data/corefork.telegram.org/api/folders.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - Folders - - - - - - - - - - - - - -
- -
-
-
- -

Folders

- -
- -

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.
-In the API, folders are called "dialog filters"; in the UI, they are typically represented as tabs.

-

Schema:

-
dialogFilter#7438f7e8 flags:# contacts:flags.0?true non_contacts:flags.1?true groups:flags.2?true broadcasts:flags.3?true bots:flags.4?true exclude_muted:flags.11?true exclude_read:flags.12?true exclude_archived:flags.13?true id:int title:string emoticon:flags.25?string pinned_peers:Vector<InputPeer> include_peers:Vector<InputPeer> exclude_peers:Vector<InputPeer> = DialogFilter;
-
-dialogFilterSuggested#77744d4a filter:DialogFilter description:string = DialogFilterSuggested;
-
-updateDialogFilter#26ffde7d flags:# id:int filter:flags.0?DialogFilter = Update;
-updateDialogFilterOrder#a5d72105 order:Vector<int> = Update;
-updateDialogFilters#3504914f = Update;
-
----functions---
-
-messages.getDialogFilters#f19ed96d = Vector<DialogFilter>;
-messages.getSuggestedDialogFilters#a29cd42c = Vector<DialogFilterSuggested>;
-messages.updateDialogFilter#1ad4a04a flags:# id:int filter:flags.0?DialogFilter = Bool;
-messages.updateDialogFiltersOrder#c563c1e4 order:Vector<int> = Bool;
-
-help.getAppConfig#98914110 = JSONValue;
-

Folders

-

On startup, clients call:

- -

The boolean under the dialog_filters_tooltip JSON key in the result of help.getAppConfig can be used to determine whether a folder tooltip should be presented to the user right away.
-The UI should then show a list of suggested folder combinations.

-

Once configuration is finished, apps call messages.updateDialogFilter to create or update existing folders.
-As per the dialogFilter constructor, folders have multiple flags that can be combined to determine which chats should be included in (or excluded from) the folder.
-Folders can also have unlimited pinned chats, as determined by the pinned_peers field.

-

To reorder existing folders, messages.updateDialogFiltersOrder should be used with the IDs of the various dialog filters.

-

To delete folders, use messages.updateDialogFilter without populating the filter flag field.

-

Clients can receive updateDialogFilter, updateDialogFilterOrder updates with new filter information, generated by other clients when modifying folder info.
-Clients can also receive updateDialogFilters, in which case folder info should be refetched manually using messages.getDialogFilters.

-

Peer folders

-

The API also has another method for identifying groups of peers, typically used only by archived chats.

-

Schema:

-
inputDialogPeer#fcaafeb7 peer:InputPeer = InputDialogPeer;
-inputDialogPeerFolder#64600527 folder_id:int = InputDialogPeer;
-
-dialogPeer#e56dbf05 peer:Peer = DialogPeer;
-dialogPeerFolder#514519e2 folder_id:int = DialogPeer;
-
-updateFolderPeers#19360dc0 folder_peers:Vector<FolderPeer> pts:int pts_count:int = Update;
-
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-
----functions---
-
-folders.editPeerFolders#6847d0ab folder_peers:Vector<InputFolderPeer> = Updates;
-folders.deleteFolder#1c295881 folder_id:int = Updates;
-

API peer folders are typically used only by archived chats, and are really handy for distinguishing groups of peers, since most peer-related constructors (updates, chat info) will contain the folder_id assigned the the specified chat.

-

In Telegram apps, API peer folders are used only to implement the chat archive, identified by folder_id 1; all other peers are in folder_id 0 by default; no other folder_id is allowed at the moment.

-
    -
  • folders.editPeerFolders can be used to add and remove peers from peer folders.
  • -
  • folders.deleteFolder can be used to delete peer folders, moving all peers previously present in that folder to the default 0 folder.
  • -
-

Both methods return an updates constructor, containing a single updateFolderPeers with the new folder_id of moved peers.
-Clients can also receive updateFolderPeers as a normal update, generated by other clients when modifying peer folders.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/geochats.html b/data/corefork.telegram.org/api/geochats.html deleted file mode 100644 index ca5cba3792..0000000000 --- a/data/corefork.telegram.org/api/geochats.html +++ /dev/null @@ -1,115 +0,0 @@ - - - - - Nope - - - - - - - - - - - - - -
- -
-
-
- -

Nope

- -

Deprecated old docs. This was definitely not the droid you were looking for.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/api/import.html b/data/corefork.telegram.org/api/import.html deleted file mode 100644 index 8ebb0f6140..0000000000 --- a/data/corefork.telegram.org/api/import.html +++ /dev/null @@ -1,173 +0,0 @@ - - - - - Imported messages - - - - - - - - - - - - - -
- -
-
-
- -

Imported messages

- -
- -

Telegram allows importing messages and media from foreign chat apps.

-
-

Note: This article is intended for MTProto API developers. If you're looking for a way to move history from other chat apps into Telegram, check out the related Telegram blog post.

-
-

1. Validate the chat export file

-
messages.historyImportParsed#5e0fb7b9 flags:# pm:flags.0?true group:flags.1?true title:flags.2?string = messages.HistoryImportParsed;
-
----functions---
-
-messages.checkHistoryImport#43fe19f3 import_head:string = messages.HistoryImportParsed;
-

The import process begins by calling messages.checkHistoryImport, passing to import_head up to 100 lines of the chat export file, starting from the beginning of the file.

-

The returned constructor contains information about the exported chat, including its title or type. -If the pm flag is set, the chat export file was generated from a private chat. -If the group flag is set, the chat export file was generated from a group chat. -If neither the pm or group flags are set, the specified chat export was generated from a chat of unknown type.

-

2. Choosing a destination Telegram chat

-
messages.checkedHistoryImportPeer#a24de717 confirm_text:string = messages.CheckedHistoryImportPeer;
-
----functions---
-
-messages.checkHistoryImportPeer#5dc60f03 peer:InputPeer = messages.CheckedHistoryImportPeer;
-

Using messages.checkHistoryImportPeer, check whether chat history exported from another chat app can be imported into a specific Telegram peer, chosen by the user.
-Typically, history imports are allowed for private chats with a mutual contact or supergroups with change_info administrator rights ».

-

If the check succeeds, and no RPC errors are returned, a messages.CheckedHistoryImportPeer constructor will be returned, with a confirmation text to be shown to the user in a confirmation prompt.
-Upon final user confirmation, the import process is initialized.

-

3. Initialize the import

-
messages.historyImport#1662af0b id:long = messages.HistoryImport;
-
----functions---
-
-messages.initHistoryImport#34090c3b peer:InputPeer file:InputFile media_count:int = messages.HistoryImport;
-

Use messages.initHistoryImport to initialize the import process, passing the following parameters:

-
    -
  • peer - The Telegram chat where the history should be imported.
  • -
  • file - The chat export file.
  • -
  • media_count - The number of media files associated with the export, to be uploaded in the next step.
  • -
-

4. Uploading media

-
---functions---
-
-messages.uploadImportedMedia#2a862092 peer:InputPeer import_id:long file_name:string media:InputMedia = MessageMedia;
-

Use messages.uploadImportedMedia to upload media files eventually associated with the chat export.
-import_id is the id contained in the messages.historyImport constructor, returned by messages.initHistoryImport in the previous step.

-

5. Finalize the import

-
message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
-
-messageFwdHeader#5f777dce flags:# imported:flags.7?true from_id:flags.0?Peer from_name:flags.5?string date:int channel_post:flags.2?int post_author:flags.3?string saved_from_peer:flags.4?Peer saved_from_msg_id:flags.4?int psa_type:flags.6?string = MessageFwdHeader;
-
----functions---
-
-messages.startHistoryImport#b43df344 peer:InputPeer import_id:long = Bool;
-

Finally, invoke messages.startHistoryImport to complete the history import process, importing all messages into the chat.
-As usual, import_id is the id contained in the messages.historyImport constructor, returned by messages.initHistoryImport.

-

Imported messages will show in the chat history as messages containing a fwd_from messageFwdHeader constructor with the imported flag, and should be appropriately marked in the UI as messages imported from a foreign chat app.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/invoking.html b/data/corefork.telegram.org/api/invoking.html deleted file mode 100644 index 1095dbc4d0..0000000000 --- a/data/corefork.telegram.org/api/invoking.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - Calling API Methods - - - - - - - - - - - - - -
- -
-
-
- -

Calling API Methods

- -
- -

Layers

-

Versioning in the API is supported by so-called TL layers.

-

The need to add a new object constructor or to add/remove a field in a constructor creates a backwards compatibility problem for previous versions of API clients. After all, simply changing a constructor in a schema also changes its number. To address this problem, each schema update is separated into a layer.

-

A layer is a collection of updated methods or constructors in a TL schema. Each layer is numbered with sequentially increasing numbers starting with 2. The first layer is the base layer -- the TL schema without any changes.

-

There is a helper method to let the API know that a client supports the Layer layer:

-
invokeWithLayer#da9b0d0d {X:Type} layer:int query:!X = X;
-

The helper method invokeWithLayer can be used only together with initConnection: the present layer will be saved with all other parameters of the client and any future requests will be using this saved value. See more below.

-

List of Available Layers

-

Saving Client Info

-

It is possible to save information about the current client on the server in conjunction with an authorization key. This may help eliminate client-side problems with certain releases on certain devices or with certain localizations, as well as eliminate the need for sending layer information in each request.

-

The helper method initConnection accepts client parameters. This method must be called when first calling the API after the application has restarted or in case the value of one of the parameters could have changed.

-

initConnection must also be called after each auth.bindTempAuthKey.

-

When calling this method, the current layer used by the client is also saved (the layer in which initConnection was wrapped is used). After a successful call to initConnection it is no longer necessary to wrap each API call in invokeWithLayerN.

-

Disabling updates

-
invokeWithoutUpdates#bf9459b7 {X:Type} query:!X = X;
-

invokeWithoutUpdates can be used to invoke a request without subscribing the used connection for updates (this is enabled by default for file queries).

-

Sequential Requests

-

By default, the server processes parallel requests in arbitrary order. Two helper methods exist for cases when the client needs certain requests to be processed in a certain order and intends to send a new request before the previous one is completed:

-
-

invokeAfterMsg#cb9f372d {X:Type} msg_id:long query:!X = X;
-invokeAfterMsgs#3dc4b4f0 {X:Type} msg_ids:Vector query:!X = X;

-
-

They may be used, for example, when a client attempts to send messages that accumulated while waiting for the Internet connection to be restored for a long time. In this case, the 32-bit number 0xcb9f372d must be added before the method number in each request, followed by a 64-bit message identifier, msg_id, which contains the previous request in the queue.

-

The second method is similar, except it takes several messages that must be successfully processed before the current one.

-

If the waiting period exceeds 0.5 seconds (this value may change in the future) and no result has appeared, the method will return the 400 MSG_WAIT_TIMEOUT error.

-

Helper Method Sequence

-

Important: if the helper methods invokeAfterMsg / invokeAfterMsgs are used together with invokeWithLayerN or other helper methods, invokeAfterMsg / invokeAfterMsgs must always be the outermost wrapper.

-

Data Compression

-

We recommend using gzip compression when calling methods to reduce the amount of network traffic.

-

The schema and constructor information are given in the protocol documentation.

-

Data Compression when Making a Request

-

Before transmitting a query, the string containing the entire body of the serialized high-level query (starting with the method number) must be compressed using gzip. If the resulting string is smaller than the original, it makes sense to transmit the gzip_packed constructor.

-

There is no point in doing the above when transmitting binary multimedia data (photos, videos) or small messages (up to 255 bytes).

-

Uncompressing Data

-

By default, the server compresses the response to any request as well as updates, in accordance with the rules stated above. If the gzip_packed constructor is received as a response in rpc_result, then the string that follows must be extracted and uncompressed. Processing then continues on the resulting new string.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/live-location.html b/data/corefork.telegram.org/api/live-location.html deleted file mode 100644 index f72bb2e16a..0000000000 --- a/data/corefork.telegram.org/api/live-location.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - Live geolocation - - - - - - - - - - - - - -
- -
-
-
- -

Live geolocation

- -
- -

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

-

Sending live locations

-
inputGeoPointEmpty#e4c123d6 = InputGeoPoint;
-
-inputGeoPoint#48222faf flags:# lat:double long:double accuracy_radius:flags.0?int = InputGeoPoint;
-
-inputMediaGeoLive#971fa843 flags:# stopped:flags.0?true geo_point:InputGeoPoint heading:flags.2?int period:flags.1?int proximity_notification_radius:flags.3?int = InputMedia;
-
----functions---
-
-messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-
-messages.editMessage#48f71778 flags:# no_webpage:flags.1?true peer:InputPeer id:int message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.15?int = Updates;
-

To send a live geolocation, use messages.sendMedia with an inputMediaGeoLive media .

-

The inputMediaGeoLive allows sending the geolocation as an inputGeoPoint with floating point latitude and longitude, with an optional accuracy_radius in meters.
-Clients can also provide a heading, a direction in degrees (1-360) that can be used to indicate the direction of the user, a validity period for the current location, and a proximity_notification_radius .

-

The sent geolocation should be updated perioducally using messages.editMessage at most every period seconds, in order to implement the "live" part of live geolocations.

-

To stop sharing the location, pass inputGeoPointEmpty as location and set the stopped flag to true in a last messages.editMessage call.

-

Receiving live locations

-
geoPoint#b2a2f663 flags:# long:double lat:double access_hash:long accuracy_radius:flags.0?int = GeoPoint;
-messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;
-
-updateGeoLiveViewed#871fb939 peer:Peer msg_id:int = Update;
-

Clients will receive a message with a messageMediaGeoLive, containing the information passed by the sender; when the geolocation message is marked as read, an updateGeoLiveViewed is generated.

-

Periodically, the geolocation will be updated with updateEditMessage/updateEditChannelMessage updates.

-

Live location previews

-
inputWebFileGeoPointLocation#9f2221c9 geo_point:InputGeoPoint access_hash:long w:int h:int zoom:int scale:int = InputWebFileLocation;
-
-inputGeoPoint#48222faf flags:# lat:double long:double accuracy_radius:flags.0?int = InputGeoPoint;
-
----functions---
-
-upload.getWebFile#24e6818d location:InputWebFileLocation offset:int limit:int = upload.WebFile;
-

A map preview can be generated by passing the received geoPoint to upload.getWebFile, to download an image preview of the map.

-
    -
  • geo_point is generated from the lat , long accuracy_radius parameters of the geoPoint
  • -
  • access_hash is the access hash of the geoPoint
  • -
  • w - Map width in pixels before applying scale; 16-1024
  • -
  • h - Map height in pixels before applying scale; 16-1024
  • -
  • zoom - Map zoom level; 13-20
  • -
  • scale - Map scale; 1-3
  • -
-

The image is then downloaded as specified here »

-

Proximity alert

-
messageActionGeoProximityReached#98e0d697 from_id:Peer to_id:Peer distance:int = MessageAction;
-
-messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;
-

If:

-
    -
  • A user sets a proximity_notification_radius when sending a location
  • -
  • Multiple users share their location within the same chat
  • -
  • One of the other users comes within proximity_notification_radius meters of the first user, and updates their location accordingly
  • -
-

An updateNewMessage/updateNewChannelMessage is generated for all chat members, containing a messageService with action messageActionGeoProximityReached:

-
    -
  • messageActionGeoProximityReached.to_id is the peer that enabled proximity alerts
  • -
  • messageActionGeoProximityReached.from_id is the peer that is now in proximity of messageActionGeoProximityReached.to_id
  • -
  • messageActionGeoProximityReached.distance is the distance between them, in meters
  • -
- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/mentions.html b/data/corefork.telegram.org/api/mentions.html deleted file mode 100644 index b89ac3f48f..0000000000 --- a/data/corefork.telegram.org/api/mentions.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - Mentions - - - - - - - - - - - - - -
- -
-
-
- -

Mentions

- -
- -

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

-
messageEntityMention#fa04579d offset:int length:int = MessageEntity;
-messageEntityMentionName#dc7b1140 offset:int length:int user_id:long = MessageEntity;
-inputMessageEntityMentionName#208e68c9 offset:int length:int user_id:InputUser = MessageEntity;
-
-message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
-
-channelParticipantsMentions#e04b5ceb flags:# q:flags.0?string top_msg_id:flags.1?int = ChannelParticipantsFilter;
-
----functions---
-
-messages.sendMessage#520c3870 flags:# no_webpage:flags.1?true silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-
-channels.getParticipants#77ced9d0 channel:InputChannel filter:ChannelParticipantsFilter offset:int limit:int hash:long = channels.ChannelParticipants;
-

Mentions are implemented as message entities, passed to the messages.sendMessage method:

- -

Incoming messages mentioning to the current user will have the mentioned flag set, and will contain one or more messageEntityMention and messageEntityMentionName constructors.

-

Graphical clients can show a list of mentionable users when the user starts entering an @ in the text bar; for this purpose, the channelParticipantsMentions filter can be used in channels.getParticipants.
-This filter can be enhanced by providing an additional query string q (anything the user enters after @); it will also return non-participant users, in case of channel users commenting in post comment sections.

-

Dialog mentions

-
dialog#2c171f72 flags:# pinned:flags.2?true unread_mark:flags.3?true peer:Peer top_message:int read_inbox_max_id:int read_outbox_max_id:int unread_count:int unread_mentions_count:int notify_settings:PeerNotifySettings pts:flags.0?int draft:flags.1?DraftMessage folder_id:flags.4?int = Dialog;
-
----functions---
-
-messages.getUnreadMentions#46578472 peer:InputPeer offset_id:int add_offset:int limit:int max_id:int min_id:int = messages.Messages;
-messages.readMentions#f0189d3 peer:InputPeer = messages.AffectedHistory;
-

Graphical clients are supposed to show a blue mention indicator next to the message counter of chats in the dialog list.
-The dialog constructor contains an unread_mentions_count field to isolate chats with unread mentions; the actual mention counter should be shown inside of the chat itself, above an @ button that can be used, by clicking multiple times, to navigate back (using messages.getUnreadMentions) through the mention history.

-

When the last unread mention is read, or when long-clicking on the @ button, all mentions for a chat should marked as read using messages.readMentions.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/min.html b/data/corefork.telegram.org/api/min.html deleted file mode 100644 index b19b2c4ab0..0000000000 --- a/data/corefork.telegram.org/api/min.html +++ /dev/null @@ -1,142 +0,0 @@ - - - - - Min constructors - - - - - - - - - - - - - -
- -
-
-
- -

Min constructors

- -

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set. This is done for performance and privacy reasons.

-

When receiving said constructors, the client must first check if user or chat object without min flag is already present in local cache. If it is present, then the client should just ignore constructors with min flag and use local one instead.

-

The rest of article assumes the client receives min-constructor without full object in local cache.

-

The client must store the context (similar to file references) in which the user/channel was seen. Later, when the client needs to pass the user/channel as input argument (e.g. fetch profile, mute, ban etc), the context is used to generate the input*FromMessage constructor, instead of normal inputUser, inputChannel or inputPeer.

- -

The access_hash value, if present, is only suitable to use in inputPeerPhotoFileLocation, to directly download the profile pictures of channels and users without having to generate an inputPeer*FromMessage, simply using inputPeer* with the specified access hash.

-

Usually min constructors are encountered in messages inside of groups or channels. -When a message mentioning (sender, forwarder or forwardee, et cetera) such a user or channel is found, the constuctor must be associated with the message ID of the message and with the chat where the message was seen.

-

Example

-

Assume a message with id 34 is received from supergroup (actually channel) 123456789. -Said message was sent by from_id 102424212. -The updates container that contained the message has a user with ID 102424212 in the users field, but it has the min flag set, and the provided access_hash may be absent, or otherwise can't be used to generate a typical inputPeerUser constructor to send messages or do other actions.

-

What the client does is associate 102424212 with the channel 123456789 and message ID 34. -When and if the client will need to interact with user 102424212, it will generate one of the *FromMessage constructors mentioned above, setting:

-
    -
  • msg_id to 34
  • -
  • peer to the InputPeer associated with channel 123456789
  • -
  • user_id to 102424212
  • -
-

user_id can also be set to the IDs of users met in the fwd_header (messages forwarded from a user can be used to interact with the original sender, if they don't have privacy settings for forwards enabled). -Users mentioned via messageEntityMentionName in a message can also be used.

-

The same can be done with min channels.

-

Example implementations: Telegram for iOS, tdlib.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/api/obtaining_api_id.html b/data/corefork.telegram.org/api/obtaining_api_id.html deleted file mode 100644 index ed6d7eb7ab..0000000000 --- a/data/corefork.telegram.org/api/obtaining_api_id.html +++ /dev/null @@ -1,140 +0,0 @@ - - - - - Creating your Telegram Application - - - - - - - - - - - - - -
- -
-
-
- -

Creating your Telegram Application

- -

We welcome all developers to use our API and source code to create Telegram-like messaging applications on our platform free of charge.

-
-

In order to ensure consistency and security across the Telegram ecosystem, -all third-party client apps must comply with the API Terms of Service.

-
-

Obtaining api_id

-

In order to obtain an API id and develop your own application using the Telegram API you need to do the following:

-
    -
  • Sign up for Telegram using any application.
  • -
  • Log in to your Telegram core: https://my.telegram.org.
  • -
  • Go to 'API development tools' and fill out the form.
  • -
  • You will get basic addresses as well as the api_id and api_hash parameters required for user authorization.
  • -
  • For the moment each number can only have one api_id connected to it.
  • -
-

We will be sending important developer notifications to the phone number that you use in this process, so please use an up-to-date number connected to your active Telegram account.

-

Using the api_id

-

Before using the MTProto Telegram API, please note that all API client libraries are strictly monitored to prevent abuse.

-

If you use the Telegram API for flooding, spamming, faking subscriber and view counters of channels, you will be banned forever.

-

Due to excessive abuse of the Telegram API, all accounts that sign up or log in using unofficial Telegram API clients are automatically put under observation to avoid violations of the Terms of Service.

-

If you didn't violate the Terms of Service but your account does get banned after using the API, write to recover@telegram.org explaining what you intend to do with the API, asking to unban your account.
-Please note that emails are checked by a human, so automatically generated emails will be detected and banned.

-

Using Telegram's open source code

-

Everyone is welcome to use our open source code. We have included a sample API id with the code. This API id is limited on the server side and is not suitable for apps released to end-users — using it for anything but testing purposes will result in the API_ID_PUBLISHED_FLOOD error for your users. It is necessary that you obtain your own API id before you publish your app.

-
-

Please remember to publish your code as well in order to comply with the GNU GPL licences.

-
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/api/offsets.html b/data/corefork.telegram.org/api/offsets.html deleted file mode 100644 index f61d92bc36..0000000000 --- a/data/corefork.telegram.org/api/offsets.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - Pagination in the API - - - - - - - - - - - - - -
- -
-
-
- -

Pagination in the API

- -
- -

Lots of Telegram API methods provide access to potentially large lists of objects, which requires pagination.

-

In order to fetch only relevant subset of results for each request there is a number of available input parameters. Here is a list in order how they are applied in API.

-

Typically, results are returned in antichronological order with descending object ID values.

-

limit parameter

-

A limit on the number of objects to be returned, typically between 1 and 100. When 0 is provided the limit will often default to an intermediate value like ~20.

-

offset-based pagination

-

For a few methods with mostly static data this parameter allows to skip offset elements from the beginning of list; negative values are ignored.

-

offset_id-based pagination

-

For most methods where results are real-time data (e.g. any chat history) offset value is not passed directly. Instead it is calculated from the passed offset_id and add_offset parameter values as offsetFromID(offset_id) + add_offset, where offsetFromID(offset_id) is a number of results from the beginning of list up to the result with ID offset_id, inclusive.

-

Sample use cases:

-
    -
  • -

    Loading 20 messages, older than message with ID MSGID:

    -

    messages.getHistory({offset_id: MSGID, add_offset: 0, limit: 20})

    -
  • -
  • -

    Loading 20 messages, newer than message with ID MSGID:

    -

    messages.getHistory({offset_id: MSGID, add_offset: -20, limit: 20})

    -
  • -
  • -

    Loading 20 messages around message with ID MSGID:

    -

    messages.getHistory({offset_id: MSGID, add_offset: -10, limit: 20})

    -
  • -
-

Additional filtering

-

There is a number of parameters, which are applied to the list after slicing with offset and limit, to reduce the result subset even more:

-
    -
  • max_id: Can be used to only return results with ID strictly smaller than max_id (e.g. message ID)
  • -
  • min_id: Can be used to only return results with ID strictly greater than min_id(e.g. message ID)
  • -
  • max_date: Can be used to only return results that are older than max_date:
  • -
  • min_date: Can be used to only return results with are newer than min_date:
  • -
  • hash: See below.
  • -
-

Hash generation

-

To further reduce the result subset, there is a mechanism to avoid fetching data if the resulting list hasn't changed from the one stored on client, similar to ETag.

-

When the client has cached results for API request, it can calculate the hash value for it by taking the result IDs (message IDs or other fields with name id) and using them to compute a 64-bit hash with the following algorithm:

-
# Here, ^ indicates a bitwise XOR
-
-hash = 0
-for id in ids:
-    hash = hash ^ (id >> 21)
-    hash = hash ^ (id << 35)
-    hash = hash ^ (id >> 4)
-    hash = hash + id
-

In some cases, the result container already has a hash field, that can be used instead.

-

When the client passes a correct value, the API will return one of *NotModified constructors, e.g. messages.messagesNotModified instead of the actual results.

-

Example methods

-
    -
  • messages.getHistory supports all result navigation parameters including message ID hashes and except filters
  • -
  • channels.getParticipants supports simple navigation using limit and offset, along with filtering and hash reducing using the user IDs of returned participants
  • -
- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/optimisation.html b/data/corefork.telegram.org/api/optimisation.html deleted file mode 100644 index 35d3848e85..0000000000 --- a/data/corefork.telegram.org/api/optimisation.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - Client-Side Optimization - - - - - - - - - - - - - -
- -
-
-
- -

Client-Side Optimization

- -

Simplified Acknowledgment of Message Delivery

-

An outgoing message may be considered sent once the server has assigned it an identifier. Normally, a client would learn of this from the result of the messages.sendMessage method. -The MTProto server provides a mechanism for “quick acknowledgments". Upon receiving such an acknowledgment, the client may be certain that the call to the send message method has at least been fully received by the server and placed in a processing queue, and can inform the user that the delivery was successful. -It is possible that the server’s actual response will never be received by the client (an interrupted connection; or the app restarts at exactly the wrong time). To correctly handle these situations, you can use a special type of notification generated by the server when updates.getDifference is called: updateMessageID. When processing this notification, the client can use the random_id identifier to associate the previously transmitted message with the one delivered to the server. -If such a notification is not issued when updates.getDifference is called for one of the previously sent messages, the message must be marked as undelivered.

-

Server Salt

-

Server salt is a 64-bit number added to every outgoing and incoming message. At present, a single salt’s lifespan is 1 hour, following which it is considered invalid and the server will return an error for all the messages that contain it. The error message will contain the correct salt, which may be immediately used for sending. Given this approach, there will always be a period of waiting before the client receives a new salt if it connects to the server less frequently than once an hour. -For improved performance, there is a special get_future_salts method, which fetches in advance a list of the salts that will be valid during the course of a specified period of time following the call (1 day, for example). A start time and an end time are specified for each salt. The salts overlap one another by half an hour. We recommend always using the record with the longest remaining lifespan.

-

Downloading Files and Uploading Data to the Server

-

We recommend that separate connections and sessions be created for these tasks. Remember that the extra sessions must be deleted when no longer needed. -It makes sense to download files over several connections (optimally to have a pool). When uploading data to a server one connection is enough to achieve the best results.

-

The file handling API is designed to perform data operations in parts. In its simplest implementation, the process of uploading files to a server looks like this: send a query, wait for a response, send the next query, etc. This approach does not optimize the use of network resources and the ping time has a huge effect. -The upload and download process is optimal when two or more queries are continuously being executed through one connection. In this arrangement, uploading to the server would look like this:

-
    -
  1. Send Query 1
  2. -
  3. Send Query 2
  4. -
  5. Wait for a response to Query 1
  6. -
  7. Send Query 3
  8. -
  9. Wait for a response to Query 2
  10. -
  11. Send Query 4
  12. -
  13. etc.
  14. -
-

This will help reduce the effect of ping latency and maximize the channel workload.

-

Sending Messages in Bulk

-

Sometimes a client needs to transmit several send message method calls to the server all at once in a single message or in several consecutive messages. However, the server may execute these requests out of order (queries are handled by different servers to improve performance, which introduces a degree of randomness to the process). -This requires that dependencies be explicitly stated when processing queries by using the function

-
invokeAfterMsg#cb9f372d {X:Type} msg_id:long query:!X = X;
-

Actually, this means padding the beginning of the query with the 32-bit number 0xcb9f372d and the 64-bit message identifier of the query on which the current query is dependent.

-

Grouping Updates

-

Generating updates (notifications about various server events) and delivering them to the client form two different parts of the system (respectively, the messenger API and MTProto). By itself, MTProto cannot modify in any way the data transmitted to the client, and the server API cannot respond to client-MTProto connection events. -Imagine the situation where a client loses its connection (or is intentionally disconnected from the network) for some time. If lots of different events occur before a new connection is established (contacts come online, typing event messages are sent), then when a connection is established the client will receive lots of data containing all of the intervening events, despite the fact that most of the data is obsolete. -The grouping of messages has been introduced to optimize such situations. If new events occur and the client has not managed to “collect” the previously generated updates, then the server API can combine them into a single package.

-

A client is able to control when the MTProto server begins to consider that the connection has been lost and grouping can begin (the earlier this occurs when there is no connection, the better for the client). This functionality is implemented through a special type of Ping message, ping_delay_disconnect, which specifies a time delay following which the server will close the current connection and start grouping messages.

-

It makes sense to combine the transmission of ping_delay_disconnect with that of other recurring tasks, such as updating the user status (account.updateStatus).

-

Setting the Typing Status

-

If a contact is not online, there is no need to invoke messages.setTyping.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/api/passport.html b/data/corefork.telegram.org/api/passport.html deleted file mode 100644 index 0aaa487f89..0000000000 --- a/data/corefork.telegram.org/api/passport.html +++ /dev/null @@ -1,674 +0,0 @@ - - - - - Telegram passport - - - - - - - - - - - - - -
- -
-
-
- -

Telegram passport

- -
- -

Telegram Passport is a unified authorization method for services that require personal identification. Users can upload their documents once, then instantly share their data with services that require real-world ID (finance, ICOs, etc.). Telegram doesn‘t have access to the users’ personal information thanks to end-to-end encryption.

-

This page describes the request flow that client apps must used to send the requested data to the service.

-

Overview

-

From the perspective of a service that requires real-world ID, the process looks like this:

-
    -
  • A user presses “Log in with Telegram” on your website or in your app.
  • -
  • You request the data you need.
  • -
  • The user accepts your privacy policy and agrees to share their data.
  • -
  • The user's Telegram app downloads and decrypts the data you requested from the end-to-end encrypted storage on Telegram.
  • -
  • If some of the data you requested is missing, the user can add it to their Telegram Passport at this point.
  • -
  • The user's app encrypts the data with your public key and sends it to you.
  • -
  • You decrypt the data, check it for errors and re-request any missing or invalid information.
  • -
  • You sign the user up for your service. Tada!
  • -
-

See As a bot to see how to request passport data using a bot, through the MTProto API. -Look at the Passport Manual to see how to request passport data using a bot, through the simplified bot API.

-

From the perspective of a user, the process looks something like this:

-
    -
  • Your app receives an event/intent from one of the SDKs, or from a custom source.
  • -
  • The user accepts your privacy policy and agrees to share their data.
  • -
  • The user's Telegram app downloads the data you requested from the end-to-end encrypted storage on Telegram.
  • -
  • If some of the data you requested is missing, the user can add it to their Telegram Passport at this point.
  • -
  • The user's app encrypts the data with your public key and sends it to the service.
  • -
  • You sign the user up for your service. Tada!
  • -
-

See As a user to see how user client apps should send passport data to a service, through the MTProto API.

-

As a bot

-

A simplified version of this process can be used using the bot API, for more info see the Passport Manual.

-

Using the MTProto API, the process is pretty much the same, up until the actual API calls.

-
-

Note that all binary fields are in raw binary format, unlike in the bot API where they are base64-encoded

-
-

Setting Up Telegram Passport

-

As per the bot API.

-

Requesting Information

-

As per the bot API.

-

Receiving information

-

Schema:

-
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;
-
-securePlainPhone#7d6099dd phone:string = SecurePlainData;
-securePlainEmail#21ec5a5f email:string = SecurePlainData;
-
-secureFile#e0277a62 id:long access_hash:long size:int dc_id:int date:int file_hash:bytes secret:bytes = SecureFile;
-
-secureValueTypePersonalDetails#9d2a81e3 = SecureValueType;
-secureValueTypePassport#3dac6a00 = SecureValueType;
-secureValueTypeDriverLicense#6e425c4 = SecureValueType;
-secureValueTypeIdentityCard#a0d0744b = SecureValueType;
-secureValueTypeInternalPassport#99a48f23 = SecureValueType;
-secureValueTypeAddress#cbe31e26 = SecureValueType;
-secureValueTypeUtilityBill#fc36954e = SecureValueType;
-secureValueTypeBankStatement#89137c0d = SecureValueType;
-secureValueTypeRentalAgreement#8b883488 = SecureValueType;
-secureValueTypePassportRegistration#99e3806a = SecureValueType;
-secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;
-secureValueTypePhone#b320aadb = SecureValueType;
-secureValueTypeEmail#8e3ca7ee = SecureValueType;
-
-secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;
-
-secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;
-
-messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction; 
-messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;
-
-updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
-

When the user confirms your request by pressing the 'Authorize' button, the MTProto API sends an updateNewMessage from the user, with a messageService constructor, containing a messageActionSecureValuesSentMe constructor that contains the encrypted Telegram Passport data.

-

Decrypting data

-
secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;
-
-messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction; 
-

To decrypt the received data, first, decrypt the credentials contained in secureCredentialsEncrypted.

-
    -
  1. -

    Decrypt the credentials secret ( secret field in secureCredentialsEncrypted) using your private key (set OAEP padding option, e.g. OPENSSL_PKCS1_OAEP_PADDING in PHP)

    -
  2. -
  3. -

    Use this secret and the credentials hash ( hash field in secureCredentialsEncrypted) to calculate credentials_key and credentials_iv as described below:

    -
     credentials_secret_hash = SHA512( credentials_secret + credentials_hash )
    - credentials_key = slice( credentials_secret_hash, 0, 32 )
    - credentials_iv = slice( credentials_secret_hash, 32, 16 )
    -
  4. -
  5. -

    Decrypt the credentials data ( data field in secureCredentialsEncrypted) by AES256-CBC using these credentials_key and credentials_iv. IMPORTANT: At this step, make sure that the credentials hash is equal to SHA256( credentials_data )

    -
  6. -
  7. -

    Credentials data is padded with 32 to 255 random padding bytes to make its length divisible by 16 bytes. The first byte contains the length of this padding (including this byte). Remove the padding to get the data.

    -
  8. -
-
-

Note that all hashes are raw binary data, not hexits

-
-

Credentials

-

The credentials are a JSON-serialized object, structured exactly as in the bot API ». -Since decryption credentials are E2E encrypted, apps have to store the decryption credentials as JSON and not TL payloads.

-

The credentials are used as described in the Passport Manual to decrypt the files attached to the secureValue. -In this case, the container for the E2E encrypted data is in TL, while the encrypted data itself is in JSON.

-
secureValue
-
secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;
-
-messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction; 
-

The schema for the secureValue constructor defines the constructor that can be found in each field.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeSecure passport value type
dataflags.0?SecureDataEncrypted Telegram Passport element data
front_sideflags.1?SecureFileEncrypted passport file with the front side of the document
reverse_sideflags.2?SecureFileEncrypted passport file with the reverse side of the document
selfieflags.3?SecureFileEncrypted passport file with a selfie of the user holding the document
translationflags.6?Vector<SecureFile>Array of encrypted passport files with translated versions of the provided documents
filesflags.4?Vector<SecureFile>Array of encrypted passport files with photos the of the documents
plain_dataflags.5?SecurePlainDataPlaintext verified passport data
hashbytesData hash
-

Here's a list of possible SecureValueTypes, and the parameters that can be set/requested when using each type.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TypeAllowed fields
secureValueTypeEmailplain_data
secureValueTypePhoneplain_data
secureValueTypePersonalDetailsdata
secureValueTypePassportdata, front_side, selfie, translation
secureValueTypeDriverLicensedata, front_side, reverse_side, selfie, translation
secureValueTypeIdentityCarddata, front_side, reverse_side, selfie, translation
secureValueTypeInternalPassportdata, front_side, selfie, translation
secureValueTypeAddressdata
secureValueTypeUtilityBillfiles, translation
secureValueTypeBankStatementfiles, translation
secureValueTypeRentalAgreementfiles, translation
secureValueTypePassportRegistrationfiles, translation
secureValueTypeTemporaryRegistrationfiles, translation
-
SecureData
-
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;
-

Data is an encrypted and padded JSON-serialized object of one of the specified JSON types, depending on the chosen type.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Chosen typeJSON object
secureValueTypePersonalDetailsPersonalDetails
secureValueTypePassportIdDocumentData
secureValueTypeDriverLicenseIdDocumentData
secureValueTypeIdentityCardIdDocumentData
secureValueTypeInternalPassportIdDocumentData
secureValueTypeAddressResidentialAddress
-

DataCredentials extracted from the credentials can then be used to decrypt encrypted data from the data field in secureData. -For more info on how to decrypt the data field, see the passport manual.

-
SecureFile
-
secureFile#e0277a62 id:long access_hash:long size:int dc_id:int date:int file_hash:bytes secret:bytes = SecureFile; 
-
-inputSecureFileLocation#cbc7ee28 id:long access_hash:long = InputFileLocation;
-
----functions---
-
-upload.getFile#b15a9afc flags:# precise:flags.0?true cdn_supported:flags.1?true location:InputFileLocation offset:int limit:int = upload.File;
-

Files (JPG format when decrypted, max. 10MB) are downloaded chunk by chunk as described in files », except that instead of generating an inputFileLocation, an inputFileLocation should be generated, instead.

-
    -
  • The id field is the id of the secureFile
  • -
  • The access_hash field is the access_hash of the secureFile
  • -
-

FileCredentials extracted from the credentials can then be used to decrypt downloaded encrypted data. -For more info on how to decrypt passport files, see the passport manual.

-
SecurePlainData
-
securePlainPhone#7d6099dd phone:string = SecurePlainData;
-securePlainEmail#21ec5a5f email:string = SecurePlainData;
-

The email/phone is passed in plaintext using the respective SecurePlainData constructor. -Emails and phone numbers sent using telegram passport are already verified as described in the passport manual.

-

Fixing errors

-
secureValueErrorData#e8a40bd9 type:SecureValueType data_hash:bytes field:string text:string = SecureValueError;
-secureValueErrorFrontSide#be3dfa type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorReverseSide#868a2aa5 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorSelfie#e537ced6 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorFile#7a700873 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorFiles#666220e9 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
-secureValueError#869d758f type:SecureValueType hash:bytes text:string = SecureValueError;
-secureValueErrorTranslationFile#a1144770 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorTranslationFiles#34636dd8 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
-
-inputUser#f21158c6 user_id:long access_hash:long = InputUser;
-
-
----functions---
-
-users.setSecureValueErrors#90c894b5 id:InputUser errors:Vector<SecureValueError> = Bool;
-

If the data you received contains errors, the bot can use the users.setSecureValueErrors method to inform the user and request information again. The user will not be able to resend the data, until all errors are fixed.

-

Descriptions of the method parameters can be found in the method's documentation page ».

-

As a user

-

Receiving requests

-

The process starts when your app receives an event from one of the SDKs, or from a custom source.

-

URI format

-

The SDKs trigger a passport authorization request by opening the following Telegram-specific URI:

-
tg://resolve?params
-

With the following query string parameters:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParametersTypeRequired
domainStringYes
bot_idIntegerYes
scopeUriPassportScopeYes
public_keyStringYes
nonceStringYes
callback_urlStringOptional
payloadStringOptional
-

Example URI, generated by the Telegram Passport Example page:

-
tg://resolve?domain=telegrampassport&bot_id=543260180&scope=%7B%22v%22%3A1%2C%22d%22%3A%5B%7B%22_%22%3A%22pd%22%2C%22n%22%3A1%7D%2C%22ad%22%2C%22pn%22%2C%22em%22%2C%7B%22_%22%3A%5B%7B%22_%22%3A%22pp%22%2C%22s%22%3A1%2C%22t%22%3A1%7D%2C%22ip%22%2C%22dl%22%2C%22ic%22%5D%7D%2C%7B%22_%22%3A%5B%22ub%22%2C%22bs%22%2C%22ra%22%2C%22pr%22%2C%22tr%22%5D%7D%5D%7D&public_key=-----BEGIN%20PUBLIC%20KEY-----%0AMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv6m1zBF8lZOCqcxf8hnj%0AkvHwuWdU8s4rBWaxKXH%2FvDDUklcCS5uhSnmjhxWca9suubaG3lW4HxlCilkeJPVf%0Ajimg5Q8ZqWrR3OoOihEpcG9iJZTOEpsEk7VtEiabgacBG3Quv9JslTrDe95Fn801%0At9d21HXwgMrHeHpWDOn31Dr%2BwoEH%2BkwySUWa6L%2FZbnGwSNP7eeDTE7Amz1RMDk3t%0A8EWGq58u0IQatPcEH09aUQlKzk6MIiALkZ9ILBKCBk6d2WCokKnsdBctovNbxwSx%0AhP1qst1r%2BYc8iPBZozsDC0ZsC5jXCkcODI3OC0tkNtYzN2XKalW5R0DjDRUDmGhT%0AzQIDAQAB%0A-----END%20PUBLIC%20KEY-----%0A&nonce=b8e892dc2e0afe63424d101b964f1256_32858210_708614a4585b84872e&callback_url=https%3A%2F%2Fcore.telegram.org%2Fpassport%2Fexample%3Fpassport_ssid%3Db8e892dc2e0afe63424d101b964f1256_32858210_db259b427f200751ce&payload=b8e892dc2e0afe63424d101b964f1256_32858210_708614a4585b84872e
-

UriPassportScope

-

This object represents the data to be requested.

- - - - - - - - - - - - - - - - - - -
FieldTypeDescription
dArray of UriPassportScopeElementList of requested elements, each type may be used only once in the entire array of UriPassportScopeElement objects
vIntegerScope version, must be 1
-
UriPassportScopeElement
-

This object represents a requested element, should be one of:

- -

Passport document type identifiers are aliased with the following reduced type identifiers:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FullAlias
personal_detailspd
passportpp
driver_licensedl
identity_cardic
internal_passportip
id_documentidd
addressad
utility_billub
bank_statementbs
rental_agreementra
passport_registrationpr
temporary_registrationtr
address_documentadd
phone_numberpn
emailem
-

You can use the special type "idd" as an alias for one of "pp", "dl", "ic" and the special type "add" as an alias for one of "ub", "bs", "ra".

-

UriPassportScopeElementOneOfSeveral

-

This object represents several elements one of which must be provided.

- - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
_Array of UriPassportScopeElementOneList of elements one of which must be provided; must contain either several of “pp”, “dl”, “ic”, “ip” or several of “ub”, “bs”, “ra”, “pr”, “tr”
sBooleanOptional. Use this parameter if you want to request a selfie with the document from this list that the user chooses to upload.
tBooleanOptional. Use this parameter if you want to request a translation of the document from this list that the user chooses to upload. Note: We suggest to only request translations after you have received a valid document that requires one.
-

UriPassportScopeElementOne

-

This object represents one particular element that must be provided. If no options are needed, String can be used instead of this object to specify the type of the element.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
_StringElement type. One of "pd", "pp", "dl", "ic", "ip", "ad", "ub", "bs", "ra", "pr", "tr", "pn", "em"
sBooleanOptional. Use this parameter if you want to request a selfie with the document as well. Available for "pp", "dl", "ic" and "ip"
tBooleanOptional. Use this parameter if you want to request a translation of the document as well. Available for "pp", "dl", "ic", "ip", "ub", "bs", "ra", "pr" and "tr". Note: We suggest to only request translations after you have received a valid document that requires one.
nBooleanOptional. Use this parameter to request the first, last and middle name of the user in the language of the user's country of residence. Available for "pd"
-

You can also use the special type "idd" as an alias for one of "pp", "dl", "ic" and the special type "add" as an alias for one of "ub", "bs", "ra".

-

Setting up Telegram Passport

-

The next step for the client app is to request the user's 2FA passport, and configure Telegram Passport/fetch and decrypt remotely saved Telegram Passport parameters as described in the Encryption article ».

-

Fetching the passport form

-
account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;
-
----functions---
-
-account.getAuthorizationForm#a929597a bot_id:long scope:string public_key:string = account.AuthorizationForm;
-

Then, the client app passes the bot ID, scope and public key from the passport authorization request to the Telegram servers using the account.getAuthorizationForm method.

-

The response will be an account.authorizationForm constructor, with info about the required document types, the URL of the service's privacy policy, as well as info about the bot to which the form should be sent. -If the form was already submitted at least once, the constructor will also contain a list of already submitted data, along with eventual errors.

-

The user should accept the privacy policy and proceed to fill in the required data, and the client should encrypt and upload it as described in the Encryption article ».

-

Submitting the passport form

-
secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;
-
-secureValueHash#ed1ecdb0 type:SecureValueType hash:bytes = SecureValueHash;
-
----functions---
-
-account.acceptAuthorization#f3ed4c73 bot_id:long scope:string public_key:string value_hashes:Vector<SecureValueHash> credentials:SecureCredentialsEncrypted = Bool;
-

Once the user finishes uploading the required documents and clicks on the submit button, the client calls account.acceptAuthorization, submitting the documents to the bot associated to the service.

-
    -
  • As before, bot_id, scope and public_key are taken from the authorization request URI.
  • -
  • value_hashes is used by the server to choose which document of which type to send to the bot: the type field should be set to the document type, and the hash field should be set to the data_hash/file_hash generated when uploading encrypting the data ».
  • -
  • credentials contains the encrypted credentials required by the service to decrypt the sent E2E encrypted secure values: it is generated as described in Passport Credentials ».
  • -
-

Finally, the client opens the callback URL (if present).

-

Handling invalid forms

-
secureValueErrorData#e8a40bd9 type:SecureValueType data_hash:bytes field:string text:string = SecureValueError;
-secureValueErrorFrontSide#be3dfa type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorReverseSide#868a2aa5 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorSelfie#e537ced6 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorFile#7a700873 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorFiles#666220e9 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
-secureValueError#869d758f type:SecureValueType hash:bytes text:string = SecureValueError;
-secureValueErrorTranslationFile#a1144770 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorTranslationFiles#34636dd8 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
-
-account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;
-
----functions---
-
-account.getAuthorizationForm#a929597a bot_id:long scope:string public_key:string = account.AuthorizationForm;
-

If any of the values of the submitted form are rejected by the service, the bot calls the appropriate method to set information about errors.

-

The user can find out about these errors directly from the service, or, if they decide to restart the process and resend the corrected data, directly from the authorization form (errors field).

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/pattern.html b/data/corefork.telegram.org/api/pattern.html deleted file mode 100644 index df161b3548..0000000000 --- a/data/corefork.telegram.org/api/pattern.html +++ /dev/null @@ -1,122 +0,0 @@ - - - - - Pattern matching - - - - - - - - - - - - - -
- -
-
-
- -

Pattern matching

- -

Some methods require the client to verify if the data obtained from an external source matches a certain pattern.

-

For example, when requesting a login code, if the chosen verification method is a flash call, it is required that the phone number (which is the login code) matches the specified pattern.

-

Same with email verification codes.

-

In all cases, the pattern is a string of the same length as the string to verify: and matching is as simple as checking if all chars in the source string are the same as in the pattern string. -Some chars in the pattern string may be censored using an asterisk *, in this case any char in the source string is considered valid.

-

The pattern string can also be a single asterisk, in this case all patterns are considered valid.

-

If the source string is a phone number, it has to be sanitized first to include only the following chars: 0123456789.

-

Example implementation: telegram for android.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/api/payments.html b/data/corefork.telegram.org/api/payments.html deleted file mode 100644 index 72e75765a8..0000000000 --- a/data/corefork.telegram.org/api/payments.html +++ /dev/null @@ -1,366 +0,0 @@ - - - - - Payments API - - - - - - - - - - - - - -
- -
-
-
- -

Payments API

- -
- -

You can accept payments from Telegram users via Telegram Bots.

-
-

Note: This article is intended for MTProto API developers. If you're looking for a general overview of Telegram Payments, check out the Telegram blog and the bot API payment manual.

-
-

Introducing Payments

-

Telegram bots can accept payments for goods and services from users. -For more info on how payments work, check out the Telegram Blog and the bot API payment manual.

-

This page will elaborate on the actions required to work with payments using the MTProto API.

-
-

A simplified version of the process is available only for bots using the bot API.

-
-

The first step for bots is enable payments as described here ».

-

Then, we work with payments as follows.

-

1. Create Invoice

-
inputWebDocument#9bed434d url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = InputWebDocument;
-
-labeledPrice#cb296bf8 label:string amount:long = LabeledPrice;
-
-invoice#cd886e0 flags:# test:flags.0?true name_requested:flags.1?true phone_requested:flags.2?true email_requested:flags.3?true shipping_address_requested:flags.4?true flexible:flags.5?true phone_to_provider:flags.6?true email_to_provider:flags.7?true currency:string prices:Vector<LabeledPrice> max_tip_amount:flags.8?long suggested_tip_amounts:flags.8?Vector<long> = Invoice;
-
-inputMediaInvoice#d9799874 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON start_param:flags.1?string = InputMedia;
-
----functions---
-
-messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-

The user contacts the bot and requests to purchase something. -The bot forms an inputMediaInvoice with an invoice constructor with a description of the goods or service, amount to be paid, as well as requested shipping info. -The provider parameter of the inputMediaInvoice constructor is where you put the token value that you've obtained earlier via Botfather. It is possible for one merchant bot to use several different tokens for different users or different goods and services.

-

Use the messages.sendMedia method to send the invoice. -You can also attach an inline keyboard to the message using the reply_markup field: if provided, the first button must be a keyboardButtonBuy button. Otherwise, an inline keyboard will be generated automatically, with a Pay 'total price' keyboardButtonBuy as only button.

-

An invoice message with a pay button can only be sent to a private chat with the user. Groups and channels are not supported.

-

2. Order information

-

2.1 Invoice message

-
keyboardButtonBuy#afd93fbb text:string = KeyboardButton;
-
-keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;
-replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;
-
-webDocument#1c570ed1 url:string access_hash:long size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;
-webDocumentNoProxy#f9c8bcc6 url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;
-
-messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
-
-message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
-
-updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
-

The user receives an updateNewMessage constructor from the bot, containing a messageMediaInvoice constructor with basic info about the product.

-

The message will also have a replyInlineMarkup keyboard attached to it. -The the first button of the keyboard will always be a keyboardButtonBuy button.

-

2.2 Getting invoice info about the product

-
invoice#cd886e0 flags:# test:flags.0?true name_requested:flags.1?true phone_requested:flags.2?true email_requested:flags.3?true shipping_address_requested:flags.4?true flexible:flags.5?true phone_to_provider:flags.6?true email_to_provider:flags.7?true currency:string prices:Vector<LabeledPrice> max_tip_amount:flags.8?long suggested_tip_amounts:flags.8?Vector<long> = Invoice;
-
-paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;
-
-paymentSavedCredentialsCard#cdc27a1f id:string title:string = PaymentSavedCredentials;
-
-payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
-
----functions---
-
-payments.getPaymentForm#8a333c8d flags:# peer:InputPeer msg_id:int theme_params:flags.0?DataJSON = payments.PaymentForm;
-

If the user clicks on the keyboardButtonBuy button, the client proceeds to call payments.getPaymentForm with the message ID of the invoice preview message to get the payment form.

-

The returned form will contain fields that should be passed to the payment provider along with the full invoice. -The payment form also contains info about previously saved payment credentials and order information (name, phone number, email, shipping address & so on).

-

The full invoice contains info about the information required for the order, the price and the currency, and whether this is a test order.

-

2.3 Verifying information

-
invoice#cd886e0 flags:# test:flags.0?true name_requested:flags.1?true phone_requested:flags.2?true email_requested:flags.3?true shipping_address_requested:flags.4?true flexible:flags.5?true phone_to_provider:flags.6?true email_to_provider:flags.7?true currency:string prices:Vector<LabeledPrice> max_tip_amount:flags.8?long suggested_tip_amounts:flags.8?Vector<long> = Invoice;
-
-postAddress#1e8caaeb street_line1:string street_line2:string city:string state:string country_iso2:string post_code:string = PostAddress;
-
-paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;
-
-payments.validatedRequestedInfo#d1451883 flags:# id:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = payments.ValidatedRequestedInfo;
-
----functions---
-
-payments.validateRequestedInfo#db103170 flags:# save:flags.0?true peer:InputPeer msg_id:int info:PaymentRequestedInfo = payments.ValidatedRequestedInfo;
-

If any data at all is requested by the invoice (name_requested, phone_requested, email_requested, shipping_address_requested), the user must call payments.validateRequestedInfo, providing the required data (as usual, msg_id is the ID of the invoice message). -The user can choose to save order information for future use by setting the save flag. -Data can be autofilled as described in autofill.

-

If no errors are found in the submitted info, the response of the method will contain an id flag, to be used later to complete the payment.

-

If the flexible flag of the invoice is set, calling the payments.validateRequestedInfo method will send a shipping query update to the bot, to which the bot will reply with the available shipping options for the specified address as described here ». -The return value in this case will also contain a shipping_options field with the available shipping options.

-

If any errors are found in the submmitted data, a service notification will be sent to the user, with a description of the error from the bot.

-

2.3.1 Autofill

-
payments.savedInfo#fb8fe43c flags:# has_saved_credentials:flags.1?true saved_info:flags.0?PaymentRequestedInfo = payments.SavedInfo;
-
----functions---
-
-payments.getSavedInfo#227d824b = payments.SavedInfo;
-payments.clearSavedInfo#d83d70c1 flags:# credentials:flags.0?true info:flags.1?true = Bool;
-

The requested fields can be autofilled with the info provided in the saved_info field of the payment form, or with the info fetched manually using payments.getSavedInfo.

-

Saved order information can also be cleared using payments.clearSavedInfo.

-

2.4 Select delivery option

-
labeledPrice#cb296bf8 label:string amount:long = LabeledPrice;
-
-shippingOption#b6213cdf id:string title:string prices:Vector<LabeledPrice> = ShippingOption;
-
-updateBotShippingQuery#b5aefd7d query_id:long user_id:long payload:bytes shipping_address:PostAddress = Update;
-
----functions---
-
-messages.setBotShippingResults#e5f672fa flags:# query_id:long error:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = Bool;
-

If a shipping address was requested and the bot included the parameter flexible, when the user validates order information the Telegram API will send an updateBotShippingQuery to the bot. -The bot must respond using messages.setBotShippingResults either with a list of possible delivery options and the relevant delivery prices, or with an error (for example, if delivery to the specified address is not possible).

-

The returned shipping options or the shipping error will be returned to the user while validating order information.

-

3. Payment

-
inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;
-inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
-inputPaymentCredentialsApplePay#aa1c39f payment_data:DataJSON = InputPaymentCredentials;
-inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;
-
-
-payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
-

3.1 Web payment

-
inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
-
-payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
-

Typically, payment takes place by opening the url in the specified payment form, which leads to a payment form on the website of the payment gateway. -Once the user finishes entering their payment credentials, a payment_form_submit web event is generated by the payment gateway, containing data and title JSON fields.

-

The title is used by the client app to represent the payment credentials (typically a censored version of credit card information). -The data is used to generate an inputPaymentCredentials constructor. -Eventually, you can set the save flag to save the credit card info for future use, only if 2FA is enabled.

-

Telegram does not have access to your card information. Credit card details will be handled only by the payment system.

-

3.2 Native payment

-
inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
-
-payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
-

Most telegram apps support working natively with the native APIs of some payment providers, without opening the website of the payment and receiving a JS event.

-

This is done using the JSON native_params parameters field of the payments.paymentForm constructor, which contains an object, which can contain one or more of the following fields:

-
    -
  • publishable_key: Stripe API publishable key
  • -
  • apple_pay_merchant_id: Apple Pay merchant ID
  • -
  • android_pay_public_key: Android Pay public key
  • -
  • android_pay_bgcolor: Android Pay form background color
  • -
  • android_pay_inverse: Whether to use the dark theme in the Android Pay form
  • -
  • need_country: True, if the user country must be provided,
  • -
  • need_zip: True, if the user ZIP/postal code must be provided,
  • -
  • need_cardholder_name: True, if the cardholder name must be provided
  • -
-

The payment gateway to use is decided based on the value of the native_provider field.

-
3.2.1 Stripe
-
inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
-
-payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
-

If the native_provider field is set and equal to stripe, the client can make use of the native Stripe token APIs with the publishable_key from the native_params to add a payment method to Stripe, and then use the token type and id to generate a JSON object:

-
{"type":"token.type", "id":"token.id"}"
-

The generated JSON object can then be passed to the data field of the inputPaymentCredentials. -Eventually, you can set the save flag to save the credit card info for future use, only if 2FA is enabled.

-

Telegram does not have access to your card information. Credit card details will be handled only by the payment system.

-

Example implementation: Telegram for Android.

-

3.3 Apple pay

-
inputPaymentCredentialsApplePay#aa1c39f payment_data:DataJSON = InputPaymentCredentials;
-

On iOS devices, Apple Pay can be used to generate payment data, which is then sent using the inputPaymentCredentialsApplePay constructor.

-

Example implementation: Telegram for iOS.

-

3.4 Android pay

-
inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;
-

On Android devices, Google Pay can be used to generate payment data, which is then sent using the inputPaymentCredentialsGooglePay constructor.

-

Example implementation: Telegram for Android.

-

3.5 Using saved payment credentials

-
inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;
-
-paymentSavedCredentialsCard#cdc27a1f id:string title:string = PaymentSavedCredentials;
-
-payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
-
-account.tmpPassword#db64fd34 tmp_password:bytes valid_until:int = account.TmpPassword;
-
----functions---
-
-account.getTmpPassword#449e0b51 password:InputCheckPasswordSRP period:int = account.TmpPassword;
-

To reuse saved payment methods, the saved_credentials field of the payment form is used. -The title of the paymentSavedCredentialsCard can be used to preview a censored version of credit card info. -The id field is provided by the payment provider directly to the Telegram servers when saving the payment method, and identifies the payment method. -Full credit card info is not saved on Telegram Servers, and cannot be fetched by the user.

-

In order to use the saved payment method, 2FA must be enabled: the user must verify their identity by entering their 2FA password, which is then used as described in the SRP docs to generate SRP parameters which must be passed to account.getTmpPassword.

-

The generated temporary password can then be used to make payments using the saved credentials using the inputPaymentCredentialsSaved constructor.

- -

Example implementation: Telegram for Android.

-

4. Pre-Checkout

-
inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;
-inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
-inputPaymentCredentialsApplePay#aa1c39f payment_data:DataJSON = InputPaymentCredentials;
-inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;
-
-payments.paymentResult#4e5f810d updates:Updates = payments.PaymentResult;
-payments.paymentVerificationNeeded#d8411139 url:string = payments.PaymentResult;
-
----functions---
-
-payments.sendPaymentForm#30c3bc9d flags:# form_id:long peer:InputPeer msg_id:int requested_info_id:flags.0?string shipping_option_id:flags.1?string credentials:InputPaymentCredentials tip_amount:flags.2?long = payments.PaymentResult;
-

After verifying order information, the final step for the client is to call payments.sendPaymentForm, with the following parameters:

-
    -
  • The msg_id is set to the ID of the invoice message
  • -
  • requested_info_id is set to the id of the verified order information, if it was requested
  • -
  • shipping_option_id is set to the selected delivery option, if shipping was requested.
  • -
  • credentials are the payment credentials generated by the payment provider, required to complete the order.
  • -
-

Payment method info can also be saved to the Telegram Servers and reused, by setting the save flag of inputPaymentCredentials when sending the form. -This is only possible on accounts with 2FA enabled.

-

The bot then replies to the received precheckout query, finally the user proceeds to checkout.

-

Please note that if the result of the method is a payments.paymentVerificationNeeded, before proceeding to checkout the payment provider requires the user to verify his identity by opening the provided url and following instructions. -Once the user finishes working with the webpage, the client can proceed to checkout.

-

Eventual errors are returned in the form of RPC errors, with the description of the error by the bot contained in service updates.

-

4.1 Receiving pre-checkout query

-
paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;
-
-updateBotPrecheckoutQuery#8caa9a96 flags:# query_id:long user_id:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string currency:string total_amount:long = Update;
-
----functions---
-
-messages.setBotPrecheckoutResults#9c2dd95 flags:# success:flags.1?true query_id:long error:flags.0?string = Bool;
-

The user enters their payment information as described above and presses the final pay button. -At this moment the Telegram API sends an updateBotPrecheckoutQuery constructor that contains all the available information about the order to the bot. -The bot must reply using messages.setBotPrecheckoutResults within 10 seconds after receiving this update or the transaction is canceled.

-

The bot may return an error if it can‘t process the order for any reason. We highly recommend specifying a reason for failure to complete the order in human readable form (e.g. "Sorry, we’re all out of rubber ducks! Would you be interested in a steel bear instead?"). Telegram will display this reason to the user.

-

5. Checkout

-
keyboardButtonBuy#afd93fbb text:string = KeyboardButton;
-
-keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;
-replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;
-
-messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
-
-message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
-
-updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
-
-payments.paymentReceipt#70c4fe03 flags:# date:int bot_id:long provider_id:long title:string description:string photo:flags.2?WebDocument invoice:Invoice info:flags.0?PaymentRequestedInfo shipping:flags.1?ShippingOption tip_amount:flags.3?long currency:string total_amount:long credentials_title:string users:Vector<User> = payments.PaymentReceipt;
-
----functions---
-
-payments.getPaymentReceipt#2478d1cc peer:InputPeer msg_id:int = payments.PaymentReceipt;
-

In case the bot confirms the order, Telegram requests the payment provider to complete the transaction. If the payment information was entered correctly and the payment goes through, the Telegram API will modify the invoice message and send a service message as described below. Once your bot receives this message, it should proceed with delivering the goods or services purchased by the user.

-

If all is OK, the user receives a payments.paymentResult in reply to the payments.sendPaymentForm query, containing info about the updated invoice message in the form of an updateEditMessage.

-

The invoice message will be updated as follows: the attached messageMediaInvoice will now have a receipt_msg_id field. -Clients should treat invoice messages with a receipt_msg_id field as receipt messages, locally modifying the label of the keyboardButtonBuy button to a localized version of the word Receipt. -From this point, clicking on the Receipt button should trigger a call to payments.getPaymentReceipt, providing the receipt_msg_id to the msg_id field, which will return info about the transaction.

-

The payment will also generate one service message of type messageActionPaymentSent or messageActionPaymentSentMe, replying to the invoice. -For bots, the service message will be of type messageActionPaymentSentMe, for users it will be a messageActionPaymentSent.

-
messageActionPaymentSentMe#8f31b327 flags:# currency:string total_amount:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string charge:PaymentCharge = MessageAction;
-messageActionPaymentSent#40699cd0 currency:string total_amount:long = MessageAction;
- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/pfs.html b/data/corefork.telegram.org/api/pfs.html deleted file mode 100644 index e6e26fd151..0000000000 --- a/data/corefork.telegram.org/api/pfs.html +++ /dev/null @@ -1,138 +0,0 @@ - - - - - Perfect Forward Secrecy - - - - - - - - - - - - - -
- -
-
-
- -

Perfect Forward Secrecy

- -
Related articles
-

-
-

This article is about Perfect Forward Secrecy in cloud chats, see also PFS in Secret Chats.

-
-
-

Telegram supports Perfect Forward Secrecy (PFS).

-

To make this possible, the client generates a permanent authorization key using p_q_inner_data and a temporary key using p_q_inner_data_temp. (See Creating an Authorization Key for more info.) These 2 operations may be done in parallel and even using the same connection. The client must save an expires_at unix timestamp expires_at = time + expires_in.

-

Important: in order to achieve PFS, the client must never use the permanent auth_key_id directly. Every message that is sent to MTProto, must be encrypted by a temp_auth_key_id, that was bound to the perm_auth_key_id.

-

An unbound temp_auth_key_id may only be used with the following methods:

- -

In order to bind a temporary authorization key to the permanent key the client creates a special binding message and executes the auth.bindTempAuthKey method using temp_auth_key. Once auth.bindTempAuthKey has been executed successfully, the client may signUp / signIn using other auth.* methods and continue using the API as usual; the client must also rewrite client info using initConnection after each binding. Each permanent key may only be bound to one temporary key at a time, binding a new temporary key overwrites the previous one.

-

Once the temporary key expires, the client needs to generate a new temporary key using p_q_inner_data_temp. Then it needs to re-bind that new temporary key to the initial permanent key. A new key can also be generated in advance, so that the client has a new key ready by the time the old one has expired.

-

For additional security, the client can store the temporary authorization key in RAM only and never save it in persistent storage.

-

A temporary authorization key may expire at any moment before expires_at, since such keys are also stored only in the RAM on the server-side. Be prepared to handle resulting MTProto errors correctly (non-existent auth_key_id results in a 404 error).

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/api/pin.html b/data/corefork.telegram.org/api/pin.html deleted file mode 100644 index 501034af11..0000000000 --- a/data/corefork.telegram.org/api/pin.html +++ /dev/null @@ -1,149 +0,0 @@ - - - - - Pinned messages - - - - - - - - - - - - - -
- -
-
-
- -

Pinned messages

- -
- -

Telegram allows pinning multiple messages on top of a specific chat.

-
message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
-
-updatePinnedMessages#ed85eab5 flags:# pinned:flags.0?true peer:Peer messages:Vector<int> pts:int pts_count:int = Update;
-updatePinnedChannelMessages#5bb98608 flags:# pinned:flags.0?true channel_id:long messages:Vector<int> pts:int pts_count:int = Update;
-
----functions---
-
-messages.updatePinnedMessage#d2aaf7ec flags:# silent:flags.0?true unpin:flags.1?true pm_oneside:flags.2?true peer:InputPeer id:int = Updates;
-messages.unpinAllMessages#f025bc8b peer:InputPeer = messages.AffectedHistory;
-
-messages.getMessages#63c66506 id:Vector<InputMessage> = messages.Messages;
-channels.getMessages#ad8c9a23 channel:InputChannel id:Vector<InputMessage> = messages.Messages;
-

The messages.updatePinnedMessage method can be used to pin or unpin a specific message in an arbitrary chat.
-The unpin flags specifies whether to unpin or pin the message, and pm_oneside specifies whether the message should only be pinned on the local side of a one-to-one chat.

-

messages.unpinAllMessages can be used to unpin all messages in a chat.

-

When (un)pinning messages, a updatePinnedMessages or updatePinnedChannelMessages update will be emitted, containing IDs of pinned or unpinned messages.

-

Pinned messages will also have the will also have the pinned flag of message set.

-

Getting pinned messages

-
userFull#d697ff05 flags:# blocked:flags.0?true phone_calls_available:flags.4?true phone_calls_private:flags.5?true can_pin_message:flags.7?true has_scheduled:flags.12?true video_calls_available:flags.13?true user:User about:flags.1?string settings:PeerSettings profile_photo:flags.2?Photo notify_settings:PeerNotifySettings bot_info:flags.3?BotInfo pinned_msg_id:flags.6?int common_chats_count:int folder_id:flags.11?int ttl_period:flags.14?int theme_emoticon:flags.15?string = UserFull;
-chatFull#4dbdc099 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:long about:string participants:ChatParticipants chat_photo:flags.2?Photo notify_settings:PeerNotifySettings exported_invite:flags.13?ExportedChatInvite bot_info:flags.3?Vector<BotInfo> pinned_msg_id:flags.6?int folder_id:flags.11?int call:flags.12?InputGroupCall ttl_period:flags.14?int groupcall_default_join_as:flags.15?Peer theme_emoticon:flags.16?string = ChatFull;
-channelFull#e9b27a17 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector<string> groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string = ChatFull;
-
-inputMessagesFilterPinned#1bb00451 = MessagesFilter;
-
----functions---
-
-messages.search#a0fda762 flags:# peer:InputPeer q:string from_id:flags.0?InputPeer top_msg_id:flags.1?int filter:MessagesFilter min_date:int max_date:int offset_id:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
-

The pinned_msg_id of userFull, chatFull, channelFull contains the ID of only the latest pinned message.
-To obtain a full list, use messages.search with inputMessagesFilterPinned filter.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/poll.html b/data/corefork.telegram.org/api/poll.html deleted file mode 100644 index 63d157426f..0000000000 --- a/data/corefork.telegram.org/api/poll.html +++ /dev/null @@ -1,199 +0,0 @@ - - - - - Poll - - - - - - - - - - - - - -
- -
-
-
- -

Poll

- -
- -

Telegram allows sending polls and quizes, that can be voted on by thousands, if not milions of users in chats and channels.

-

Sending a poll

-
pollAnswer#6ca9c2e9 text:string option:bytes = PollAnswer;
-
-poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;
-
-inputMediaPoll#f94e5f1 flags:# poll:Poll correct_answers:flags.0?Vector<bytes> solution:flags.1?string solution_entities:flags.1?Vector<MessageEntity> = InputMedia;
-
----functions---
-
-messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-

To send a poll in a chat, call messages.sendMedia, providing an inputMediaPoll:

-
    -
  • -

    poll is the actual poll constructor, containing:

    -
      -
    • question - The poll title, aka the poll's title
    • -
    • answers - A vector of possible answers (2-10), each with a visible title text , and a unique option identifier (1-100 bytes)
    • -
    • closed - Whether the poll is closed
    • -
    • public_voters - Whether cast votes are publicly visible to all users (non-anonymous poll)
    • -
    • multiple_choice - Whether multiple options can be chosen as answer
    • -
    • quiz - Whether this is a quiz with correct answer IDs specified in inputMediaPoll.correct_answers
    • -
    • close_period - Amount of time in seconds the poll will be active after creation, 5-600. Can't be used together with close_date .
    • -
    • close_date - Point in time (Unix timestamp) when the poll will be automatically closed. Must be at least 5 and no more than 600 seconds in the future; can't be used together with close_period .
      -These last two parameters are exactly the same, except that one uses absolute, the other relative unixtime.
    • -
    -
  • -
  • -

    correct_answers - For quizes, option ID of the only correct answer

    -
  • -
  • -

    solution - Text that is shown when a user chooses an incorrect answer or taps on the lamp icon in a quiz-style poll, 0-200 characters with at most 2 line feeds

    -
  • -
  • -

    solution_entities - Styled text message entities for the solution explanation

    -
  • -
-

In order to prematurely close the poll, preventing further votes, use messages.editMessage, setting the poll.closed flag to true.

-

Voting in polls

-
pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;
-
-pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;
-
-poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;
-
-messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
-
-updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;
-
----functions---
-
-messages.sendVote#10ea6184 peer:InputPeer msg_id:int options:Vector<bytes> = Updates;
-

When receiving a message with a messageMediaPoll, users can vote in it using messages.sendVote, specifying the chosen option identifiers.

-

The method will return an updateMessagePoll, containing an updated pollResults constructor, with the chosen flag set on the options we chose, and the correct flag set on the correct answers.

-

Getting poll votes

-
pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;
-
-pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;
-
-updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;
-
----functions---
-
-messages.getPollResults#73bb643b peer:InputPeer msg_id:int = Updates;
-

Regularly, if new users have voted in polls available to the user, they will receive an updateMessagePoll, with updated pollResults.

-

The same constructor can also be fetched manually using messages.getPollResults.

-

Getting poll voters in non-anonymous polls

-
messageUserVote#34d247b4 user_id:long option:bytes date:int = MessageUserVote;
-messageUserVoteInputOption#3ca5b0ec user_id:long date:int = MessageUserVote;
-messageUserVoteMultiple#8a65e557 user_id:long options:Vector<bytes> date:int = MessageUserVote;
-
-messages.votesList#823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList; 
-
-updateMessagePollVote#106395c9 poll_id:long user_id:long options:Vector<bytes> qts:int = Update;
-
----functions---
-
-messages.getPollVotes#b86e380e flags:# peer:InputPeer id:int option:flags.0?bytes offset:flags.1?string limit:int = messages.VotesList; 
-

messages.getPollVotes can be used to get poll results for non-anonymous polls, to see how each user voted for a poll option.
-Bots will also receive an updateMessagePollVote every time a user their answer in a non-anonymous poll. Bots receive new votes only in polls that were sent by the bot itself.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/push-updates.html b/data/corefork.telegram.org/api/push-updates.html deleted file mode 100644 index 4e96c82bd4..0000000000 --- a/data/corefork.telegram.org/api/push-updates.html +++ /dev/null @@ -1,1009 +0,0 @@ - - - - - Handling PUSH-notifications - - - - - - - - - - - - - -
- -
-
-
- -

Handling PUSH-notifications

- -
- -

Configuring the application

-

To be able to send APNS notifications to Apple servers or GCM notifications to Google servers, application certificates (APNS) or an application key (GCM) must be specified in the application settings.

-

Subscribing to notifications

-

To subscribe to notifications, the client must invoke the account.registerDevice query, passing in token_type and token as parameters that identify the current device. It is useful to repeat this query at least once every 24 hours or when restarting the application. Use account.unregisterDevice to unsubscribe.

-

The following modes are supported:

-
    -
  • 1 - APNS (device token for apple push)
  • -
  • 2 - FCM (firebase token for google firebase)
  • -
  • 3 - MPNS (channel URI for microsoft push)
  • -
  • 4 - Deprecated: Simple push (endpoint for firefox's simple push API)
  • -
  • 5 - Ubuntu phone (token for ubuntu push)
  • -
  • 6 - Blackberry (token for blackberry push)
  • -
  • 7 - MTProto separate session
  • -
  • 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 with the following keys:

-
    -
  • endpoint: Absolute URL exposed by the push service where the application server can send push messages
  • -
  • keys: P-256 elliptic curve Diffie-Hellman parameters in the following object
      -
    • p256dh: Base64url-encoded P-256 elliptic curve Diffie-Hellman public key
    • -
    • auth: Base64url-encoded authentication secret
    • -
    -
  • -
-

Notification encryption

-

For FCM and APNS VoIP, an optional encryption key used to encrypt push notifications can be passed to account.registerDevice (secret). This key (auth_key) is used to encrypt the payloads using MTProto v2.

-

The FCM payload will be a JSON payload, containing a p field with the base64-encoded encrypted MTProto payload. After decryption, the result will be a JSON object, prefixed by a 32-bit little-endian integer with the length of the JSON payload. As usual, make sure to follow all security checks as described in the MTProto docs.

-

Example implementation.

-

As mentioned above, payloads can also be encrypted using P-256 Elliptic Curve Diffie-Hellman when using web push.

-

Notification structure

-

An (optionally encrypted) notification is provided as a JSON object in the following format:

-
{
-  "data": {
-    "loc_key": "CHAT_MESSAGE_CONTACT",
-    "loc_args": ["John Doe", "My magical group", "Contact Exchange"],
-    "user_id": 14124122,
-    "custom": {
-      "chat_id": 241233,
-      "msg_id": 123
-    },
-    "sound": "sound1.mp3",
-  }
-}
-

Each notification has several parameters that describe it.

-

Notification type

-

data.loc_key - A string literal in the form /[A-Z_0-9]+/, which summarizes the notification. For example, CHAT_MESSAGE_TEXT.

-

Notification text arguments

-

data.loc_args - A list or arguments which, when inserted into a template, produce a readable notification.

-

Custom parameters

-

data.custom - Parameters which are be passed into the application when a notification is opened.

-

Sound

-

data.sound - The name of an audio file to be played.

-

User id

-

data.user_id - ID of the account to which the PUSH notification should be delivered, in case of clients with multiple accounts active and running.

-

Processing notifications

-

In principle, data.loc_key, data.custom, and an Internet connection are sufficient to generate a notification. Obviously, if possible, when generating a visual notification you need not use all of the transmitted data and may rely on the information already stored on the client. But if a user or a chat is not cached locally, the values passed in loc_args may also be used. data.user_id is the ID of the account to which the PUSH notification should be delivered, in case of clients with multiple accounts active and running.

-

Service notifications

-

The following notifications can be used to update app settings.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TypeExtra custom argumentsDescription
DC_UPDATEdc - number of the data-center
addr - server address with port number in the format 111.112.113.114:443
In case the client gets this notification, it is necessary to add the received server address to the list of possible addresses. In case the address of the first DC was passed (dc=1), it is recommended to call it immediately using help.getConfig to update dc-configuration.
MESSAGE_DELETEDchannel_id: For channels and supergroups, Channel/supergroup identifier
chat_id: For chats, Chat identifier
from_id: For PMs, Author identifier
messages: Comma-separated IDs of messages that were deleted
Messages were deleted, remove multiple notifications for this chat
READ_HISTORYchannel_id: For channels and supergroups, Channel/supergroup identifier
chat_id: For chats, Chat identifier
from_id: For PMs, Author identifier
max_id: Maximum ID of read messages
Message history was read, remove multiple notifications for this chat
GEO_LIVE_PENDING Any of the live locations currently being shared should be updated
SESSION_REVOKE Logout and remove DB for specified session by data.user_id, only apply if coming from an MTProto-encrypted payload
MESSAGE_MUTED Sent rarely, every 10th message in chats or once per 15 sec in PM, to update badge or download messages
-

Possible Notifications

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TypeTemplate exampleArgumentsExtra custom arguments
AUTH_REGIONNew login from unrecognized device {1}, location: {2}1. Device name
2. Location
 
AUTH_UNKNOWNNew login from unrecognized device {1}1. Device name 
CHANNEL_MESSAGES{1} posted an album1. Message authorattachb64: Base64-encoded version of the attached media (related to the first message)
channel_id: Channel/supergroup identifier (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHANNEL_MESSAGE_AUDIO{1} posted a voice message1. Message authorattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_CONTACT{1} posted a contact {2}1. Message author
2. Contact name
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_DOC{1} posted a file1. Message authorattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_DOCS{1} posted {2} files1. Channel name
2. Number of documents that were posted
attachb64: Base64-encoded version of the attached media (related to the first message)
channel_id: Channel/supergroup identifier (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHANNEL_MESSAGE_FWDS{1} posted {2} forwarded messages1. Message author
2. Number of forwarded messages
attachb64: Base64-encoded version of the attached media (related to the first message)
channel_id: Channel/supergroup identifier (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHANNEL_MESSAGE_GAME{1} invited you to play {2}1. Message author
2. Game name
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_GAME_SCORE{1} scored {3} in game {2}1. User
2. Game name
3. Score
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_GEO{1} posted a location1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_GEOLIVE{1} posted a live location1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_GIF{1} posted a GIF1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_NOTEXT{1} posted a message1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_PHOTO{1} posted a photo1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_PHOTOS{1} posted {2} photos1. Channel name
2. Number of photos that was sent
attachb64: Base64-encoded version of the attached media (related to the first message)
channel_id: Channel/supergroup identifier (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHANNEL_MESSAGE_PLAYLIST{1} posted {2} music files1. Channel name
2. Number of audio files that were posted
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_POLL{1} posted a poll {2}1. Channel name
2. Poll name
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_QUIZ{1} posted a quiz {2}1. Channel name
2. Quiz name
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_ROUND{1} posted a video message1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_STICKER{1} posted a {2} sticker1. Channel name
2. Sticker emoji
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_TEXT{1}: {2}1. Channel name
2. Message body
attachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_VIDEO{1} posted a video1. Channel nameattachb64: Base64-encoded version of the attached media
channel_id: Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHANNEL_MESSAGE_VIDEOS{1} posted {2} videos1. Channel name
2. Number of videos that were posted
attachb64: Base64-encoded version of the attached media (related to the first message)
channel_id: Channel/supergroup identifier (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHAT_ADD_MEMBER{1} invited {3} to the group {2}1. Message author
2. Chat name
3. New participant name
chat_id: chat identifier
CHAT_ADD_YOU{1} invited you to the group {2}1. User name
2. Group name
chat_id: chat identifier
CHAT_CREATED{1} invited you to the group {2}1. Message author
2. Chat name
chat_id: chat identifier
CHAT_DELETE_MEMBER{1} removed {3} from the group {2}1. Message author
2. Chat name
3. Dropped participant name
chat_id: chat identifier
CHAT_DELETE_YOU{1} removed you from the group {2}1. Message author
2. Chat name
chat_id: chat identifier
CHAT_JOINED{1} joined the group {2}1. User name
2. Group name
chat_id: chat identifier
CHAT_LEFT{1} left the group {2}1. Message author
2. Chat name
chat_id: chat identifier
CHAT_MESSAGES{1} sent an album to the group {2}1. User name
2. Group name
chat_from_id: Message author identifier
chat_id: chat identifier
mention: Whether the user was mentioned in the message
CHAT_MESSAGE_AUDIO{1} sent a voice message to the group {2}1. Message author
2. Chat name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_CONTACT{1} shared a contact {3} in the group {2}1. User name
2. Group name
3. Contact name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_DOC{1} sent a file to the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_DOCS{1} sent {3} files to the group {2}1. User name
2. Group name
3. Number of documents that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
chat_id: Chat identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHAT_MESSAGE_FWDS{1} forwarded {3} messages to the group {2}1. User name
2. Group name
3. Number of messages that were forwarded
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
chat_id: Chat identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHAT_MESSAGE_GAME{1} invited the group {2} to play {3}1. User name
2. Group name
3. Game name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_GAME_SCORE{1} scored {4} in game {3} in the group {2}1. User name
2. Group name
3. Game name
4. Score
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_GEO{1} sent a location to the group {2}1. Message author
2. Chat name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_GEOLIVE{1} shared a live location with the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_GIF{1} sent a GIF to the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_INVOICE{1} sent an invoice to the group {2} for {3}1. User name
2. Group name
3. Product name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_NOTEXT{1} sent a message to the group {2}1. Message author
2. Chat name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_PHOTO{1} sent a photo to the group {2}1. Message author
2. Chat name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_PHOTOS{1} sent {3} photos to the group {2}1. User name
2. Group name
3. Number of photos that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
chat_id: Chat identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHAT_MESSAGE_PLAYLIST{1} sent {3} music files to the group {2}1. User name
2. Group name
3. Number of audio files that were sent
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_POLL{1} sent a poll {3} to the group {2}1. User name
2. Group name
3. Poll name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_QUIZ{1} sent a quiz {3} to the group {2}1. User name
2. Group name
3. Quiz name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_ROUND{1} sent a video message to the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_STICKER{1} sent a {3} sticker to the group {2}1. User name
2. Group name
3. Sticker emoji
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_TEXT{1} @ {2}: {3}1. Message author
2. Chat name
3. Message body
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_VIDEO{1} sent a video to the group {2}1. Message author
2. Chat name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
chat_id: Chat identifier
edit_date: When was the message last edited
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
CHAT_MESSAGE_VIDEOS{1} sent {3} videos to the group {2}1. User name
2. Group name
3. Number of videos that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
chat_id: Chat identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
CHAT_PHOTO_EDITED{1} changed the group photo for {2}1. Message author
2. Chat name
chat_from_id: Message author identifier
chat_id: chat identifier
msg_id: ID of the message
CHAT_RETURNED{1} returned to the group {2}1. Message author
2. Chat name
chat_id: chat identifier
CHAT_TITLE_EDITED{1} renamed the group {2}1. User name
2. Group name
chat_id: chat identifier
CHAT_VOICECHAT_END{1} ended a voice chat in the group {2}1. User name
2. Chat name
 
CHAT_VOICECHAT_INVITE{1} invited {3} to a voice chat in the group {2}1. User name
2. Chat name
3. Invited users
 
CHAT_VOICECHAT_INVITE_YOU{1} invited you to a voice chat in the group {2}1. User name
2. Chat name
 
CHAT_VOICECHAT_START{1} started a voice chat in the group {2}1. User name
2. Chat name
 
CONTACT_JOINED{1} joined Telegram!1. Contact namecontact_id: contact identifier
ENCRYPTED_MESSAGEYou have a new message encryption_id: secret chat identifier
random_id: message identifier
ENCRYPTION_ACCEPTYou have a new message encryption_id: secret chat identifier
ENCRYPTION_REQUESTYou have a new message encryption_id: secret chat identifier
LOCKED_MESSAGEYou have a new message  
MESSAGES{1} sent you an album1. User namefrom_id: author identifier
MESSAGE_ANNOUNCEMENT{1}1. Announcementannouncement: Announcement: roughly equivalent to a message received from the service notifications (Telegram Notifications, id 777000) user, but must be delivered via push notifications, without contacting the API.
MESSAGE_AUDIO{1} sent you a voice message1. Message authorattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_CONTACT{1} shared a contact {2} with you1. User name
2. Contact name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_DOC{1} sent you a file1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_DOCS{1} sent you {2} files1. User name
2. Number of documents that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
from_id: Author identifier (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
MESSAGE_FWDS{1} forwarded you {2} messages1. User name
2. Number of messages that were forwarded
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
from_id: Author identifier (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
MESSAGE_GAME{1} invited you to play {2}1. User name
2. Game name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_GAME_SCORE{1} scored {3} in game {2}1. User name
2. Game name
3. Score
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_GEO{1} sent you a location1. Message authorattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_GEOLIVE{1} sent you a live location1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_GIF{1} sent you a GIF1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_INVOICE{1} sent you an invoice for {2}1. User name
2. Product
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_NOTEXT{1} sent you a message1. Message authorattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_PHOTO{1} sent you a photo1. Message authorattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_PHOTOS{1} sent you {2} photos1. User name
2. Number of photos that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
from_id: Author identifier (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
MESSAGE_PHOTO_SECRET{1} sent you a self-destructing photo1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_PLAYLIST{1} sent you {2} music files1. User name
2. Number of audio files that were sent
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_POLL{1} sent you a poll {2}1. User name
2. Poll name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_QUIZ{1} sent you a quiz {2}1. User name
2. Quiz name
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_ROUND{1} sent you a video message1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_SCREENSHOT{1} took a screenshot1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_STICKER{1} sent you a {2} sticker1. User name
2. Sticker emoji
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_TEXT{1}: {2}1. Message author
2. Message body
attachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_VIDEO{1} sent you a video1. Message authorattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
MESSAGE_VIDEOS{1} sent you {2} videos1. User name
2. Number of videos that were sent
attachb64: Base64-encoded version of the attached media (related to the first message)
chat_from_id: Groups only, message author identifier (related to the first message)
edit_date: When was the message last edited (related to the first message)
from_id: Author identifier (related to the first message)
mention: Whether the user was mentioned in the message (related to the first message)
msg_id: ID of the message (related to the first message)
silent: Whether the message was posted silently (no notification should be issued) (related to the first message)
MESSAGE_VIDEO_SECRET{1} sent you a self-destructing video1. User nameattachb64: Base64-encoded version of the attached media
chat_from_id: Groups only, message author identifier
edit_date: When was the message last edited
from_id: Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
scheduled: Whether this is a scheduled message
silent: Whether the message was posted silently (no notification should be issued)
PHONE_CALL_MISSEDYou missed a call from {1}1. User name 
PHONE_CALL_REQUEST{1} is calling you!1. User namecall_ah: Call access hash
call_id: Call ID
PINNED_AUDIO{1} pinned a voice message1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_AUDIO{1} pinned a voice message in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_CONTACT{1} pinned a contact {2}1. User name
2. Contact name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_CONTACT{1} pinned a contact {3} in the group {2}1. User name
2. Group name
3. Contact name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_DOC{1} pinned a file1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_DOC{1} pinned a file in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GAME{1} pinned a game1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GAME{1} pinned a game in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GAME_SCORE{1} pinned a game score1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GAME_SCORE{1} pinned a game score in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GEO{1} pinned a map1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GEO{1} pinned a map in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GEOLIVE{1} pinned a live location1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GEOLIVE{1} pinned a live location in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GIF{1} pinned a GIF1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_GIF{1} pinned a GIF in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_INVOICE{1} pinned an invoice1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_INVOICE{1} pinned an invoice in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_NOTEXT{1} pinned a message1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_NOTEXT{1} pinned a message in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_PHOTO{1} pinned a photo1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_PHOTO{1} pinned a photo in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_POLL{1} pinned a poll {2}1. User name
2. Poll name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_POLL{1} pinned a poll {3} in the group {2}1. User name
2. Group name
3. Poll name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_QUIZ{1} pinned a quiz {2}1. User name
2. Quiz name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_QUIZ{1} pinned a quiz {3} in the group {2}1. User name
2. Group name
3. Quiz name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_ROUND{1} pinned a video message1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_ROUND{1} pinned a video message in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_STICKER{1} pinned a {2} sticker1. User name
2. Sticker emoji
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_STICKER{1} pinned a {3} sticker in the group {2}1. User name
2. Group name
3. Sticker emoji
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_TEXT{1} pinned "{2}"1. User name
2. Message body
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_TEXT{1} pinned "{3}" in the group {2}1. User name
2. Group name
3. Message body
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_VIDEO{1} pinned a video1. User nameattachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
PINNED_VIDEO{1} pinned a video in the group {2}1. User name
2. Group name
attachb64: Base64-encoded version of the attached media
channel_id: For channels and supergroups, Channel/supergroup identifier
chat_from_id: Groups only, message author identifier
chat_id: For chats, Chat identifier
edit_date: When was the message last edited
from_id: For PMs, Author identifier
mention: Whether the user was mentioned in the message
msg_id: ID of the message
silent: Whether the message was posted silently (no notification should be issued)
- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/qr-login.html b/data/corefork.telegram.org/api/qr-login.html deleted file mode 100644 index 1371a834c2..0000000000 --- a/data/corefork.telegram.org/api/qr-login.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - Login via QR code - - - - - - - - - - - - - -
- -
-
-
- -

Login via QR code

- -
- -

QR code login flow.

-

Related TL schema:

-
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
-auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;
-auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;
-
-updateLoginToken#564fe691 = Update;
-
-authorization#ad01d61d flags:# current:flags.0?true official_app:flags.1?true password_pending:flags.2?true hash:long device_model:string platform:string system_version:string api_id:int app_name:string app_version:string date_created:int date_active:int ip:string country:string region:string = Authorization;
-
----functions---
-
-auth.exportLoginToken#b7e085fe api_id:int api_hash:string except_ids:Vector<long> = auth.LoginToken;
-auth.acceptLoginToken#e894ad4d token:bytes = Authorization;
-auth.importLoginToken#95ac5ce4 token:bytes = auth.LoginToken;
-

Exporting a login token

-

First of all, auth.exportLoginToken must be called by the app that wants to log in to an existing Telegram account.
-The method will return an auth.loginToken constructor, containing a binary login token and an expiry date (usually 30 seconds).

-

The login token must be encoded using base64url, embedded in a tg://login?token=base64encodedtoken URL and shown in the form of a QR code to the user.
-After the expiration of the current QR code, the auth.exportLoginToken method must be recalled and a new QR code must be generated automatically.

-

Accepting a login token

-

In order to log in, the QR code must be scanned and accepted by an already logged-in Telegram app using auth.acceptLoginToken.
-The token must be extracted from the tg://login URI and base64url-decoded before using it in the method.

-

Possible errors returned by the method are:

-
    -
  • 400 - AUTH_TOKEN_INVALID, an invalid authorization token was provided
  • -
  • 400 - AUTH_TOKEN_EXPIRED, the provided authorization token has expired and the updated QR-code must be re-scanned
  • -
  • 400 - AUTH_TOKEN_ALREADY_ACCEPTED, the authorization token was already used
  • -
-

The method will return an authorization object, containing info about the app and session that we just authorized.

-

Confirming (importing) the login token

-

After the logged-in app calls auth.acceptLoginToken and accepts the login token, the app that is trying to login will receive an updateLoginToken update, which should trigger a second call to the auth.exportLoginToken method.

-

This second call should then return an auth.loginTokenSuccess constructor, indicating successful login, essentially allowing further authorized interaction with the API.

-

If, however, there is a DC mismatch between the two apps, auth.loginTokenMigrateTo is returned instead, to which the app that is trying to login should respond by calling auth.importLoginToken with the specified token, to the specified DC.

-

This call should then finally return a auth.loginTokenSuccess constructor.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/recent-actions.html b/data/corefork.telegram.org/api/recent-actions.html deleted file mode 100644 index f3ca80fe01..0000000000 --- a/data/corefork.telegram.org/api/recent-actions.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - Admin log - - - - - - - - - - - - - -
- -
-
-
- -

Admin log

- -
- -

Both supergroups and channels offer a so-called admin log, a log of recent relevant supergroup and channel actions, like the modification of group/channel settings or information on behalf of an admin, user kicks and bans, and more.

-
channelAdminLogEventActionChangeTitle#e6dfb825 prev_value:string new_value:string = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeAbout#55188a2e prev_value:string new_value:string = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeUsername#6a4afc38 prev_value:string new_value:string = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangePhoto#434bd2af prev_photo:Photo new_photo:Photo = ChannelAdminLogEventAction;
-channelAdminLogEventActionToggleInvites#1b7907ae new_value:Bool = ChannelAdminLogEventAction;
-channelAdminLogEventActionToggleSignatures#26ae0971 new_value:Bool = ChannelAdminLogEventAction;
-channelAdminLogEventActionUpdatePinned#e9e82c18 message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionEditMessage#709b2405 prev_message:Message new_message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionDeleteMessage#42e047bb message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantJoin#183040d3 = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantLeave#f89777f2 = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantInvite#e31c34d8 participant:ChannelParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantToggleBan#e6d83d7e prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantToggleAdmin#d5676710 prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeStickerSet#b1c3caa7 prev_stickerset:InputStickerSet new_stickerset:InputStickerSet = ChannelAdminLogEventAction;
-channelAdminLogEventActionTogglePreHistoryHidden#5f5c95f1 new_value:Bool = ChannelAdminLogEventAction;
-channelAdminLogEventActionDefaultBannedRights#2df5fc0a prev_banned_rights:ChatBannedRights new_banned_rights:ChatBannedRights = ChannelAdminLogEventAction;
-channelAdminLogEventActionStopPoll#8f079643 message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeLinkedChat#50c7ac8 prev_value:long new_value:long = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeLocation#e6b76ae prev_value:ChannelLocation new_value:ChannelLocation = ChannelAdminLogEventAction;
-channelAdminLogEventActionToggleSlowMode#53909779 prev_value:int new_value:int = ChannelAdminLogEventAction;
-
-channelAdminLogEvent#1fad68cd id:long date:int user_id:long action:ChannelAdminLogEventAction = ChannelAdminLogEvent;
-
-channels.adminLogResults#ed8af74d events:Vector<ChannelAdminLogEvent> chats:Vector<Chat> users:Vector<User> = channels.AdminLogResults;
-
-channelAdminLogEventsFilter#ea107ae4 flags:# join:flags.0?true leave:flags.1?true invite:flags.2?true ban:flags.3?true unban:flags.4?true kick:flags.5?true unkick:flags.6?true promote:flags.7?true demote:flags.8?true info:flags.9?true settings:flags.10?true pinned:flags.11?true edit:flags.12?true delete:flags.13?true group_call:flags.14?true invites:flags.15?true = ChannelAdminLogEventsFilter;
-
----functions---
-
-channels.getAdminLog#33ddf480 flags:# channel:InputChannel q:string events_filter:flags.0?ChannelAdminLogEventsFilter admins:flags.1?Vector<InputUser> max_id:long min_id:long limit:int = channels.AdminLogResults;
-

channels.getAdminLog can be used to list recent admin activity.
-A channelAdminLogEventsFilter can be used to filter out actions of a certain type, and the admins field can be used to show only actions by certain admins.
-q can also be used to filter only logs matching a query string.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/rights.html b/data/corefork.telegram.org/api/rights.html deleted file mode 100644 index 603681a672..0000000000 --- a/data/corefork.telegram.org/api/rights.html +++ /dev/null @@ -1,133 +0,0 @@ - - - - - Admin, banned, default rights - - - - - - - - - - - - - -
- -
-
-
- -

Admin, banned, default rights

- -
- -

Channels and supergroups allow setting granular permissions both for admins and specific users. -Channels, supergroups and legacy groups also allow setting global granular permissions for users.

-

They can be modified as follows:

-

Admin rights

-

channels.editAdmin can be used to modify the admin rights of a user in a channel or supergroup. -Legacy groups do not allow setting granular admin permissions, messages.editChatAdmin has to be used, instead.

-

Permissions are defined by the chatAdminRights constructor, some admin rights can only be used for channels, others both for channels and supergroups (see the constructor page).

-

Banned rights

-

channels.editBanned can be used to modify the rights of a user in a channel or supergroup, to ban/kick a user from the group, or restrict the user from doing certain things. -Legacy groups do not allow setting granular user permissions for single users, single users can only be removed from groups using messages.deleteChatUser: however, setting global granular permissions with legacy groups is supported.

-

Permissions are defined by the chatBannedRights constructor, for more info see the constructor page.

-

Default rights

-

messages.editChatDefaultBannedRights can be used to modify the rights of all users in a channel, supergroup or legacy group, to restrict them from doing certain things.

-

Permissions are defined by the chatBannedRights constructor: all flags can be used except for view_messages, for more info see the constructor page.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/scheduled-messages.html b/data/corefork.telegram.org/api/scheduled-messages.html deleted file mode 100644 index 7cb326abe1..0000000000 --- a/data/corefork.telegram.org/api/scheduled-messages.html +++ /dev/null @@ -1,156 +0,0 @@ - - - - - Scheduled messages - - - - - - - - - - - - - -
- -
-
-
- -

Scheduled messages

- -

Telegram allows scheduling messages.

-
message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
-
-updateNewScheduledMessage#39a51dfb message:Message = Update;
-updateDeleteScheduledMessages#90866cee peer:Peer messages:Vector<int> = Update;
-
----functions---
-
-messages.sendMessage#520c3870 flags:# no_webpage:flags.1?true silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-
-messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-

To schedule a message, simply provide a future unixtime in the schedule_date flag of messages.sendMessage or messages.sendMedia.

-

The specified message or media will be added to a server-side schedule queue for the current chat, and will be automatically sent at the specified time.
-The method call generates the following updates:

-
    -
  • Immediately, an updateNewScheduledMessage, with ID equal to the ID of the message in the schedule queue for the current chat (each PM, chat, supergroup and channel has its own schedule queue and ID sequence).
  • -
  • At schedule_date, an updateNewMessage or updateNewChannelMessage with the from_scheduled flag set, indicating to the sender that the specified scheduled message was sent.
  • -
  • At schedule_date, an updateDeleteScheduledMessages, indicating that the message was flushed from the schedule queue.
  • -
-

If the schedule_date is less than 10 seconds in the future, the message will be sent immediately, generating a normal updateNewMessage/updateNewChannelMessage .

-

Manipulating the schedule queue

-
updateNewScheduledMessage#39a51dfb message:Message = Update;
-updateDeleteScheduledMessages#90866cee peer:Peer messages:Vector<int> = Update;
-
----functions---
-
-messages.getScheduledHistory#f516760b peer:InputPeer hash:long = messages.Messages;
-messages.getScheduledMessages#bdbb0464 peer:InputPeer id:Vector<int> = messages.Messages;
-messages.sendScheduledMessages#bd38850a peer:InputPeer id:Vector<int> = Updates;
-messages.deleteScheduledMessages#59ae2b16 peer:InputPeer id:Vector<int> = Updates;
-
-messages.editMessage#48f71778 flags:# no_webpage:flags.1?true peer:InputPeer id:int message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.15?int = Updates;
-

Clients can manually edit the schedule queue of a certain chat, providing the scheduled message ID obtained from updateNewScheduledMessage.

- -

Modifying scheduled messages will generate an updateNewScheduledMessage with the same ID, and updated information.
-Deleting scheduled messages will generate an updateDeleteScheduledMessages.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/api/search.html b/data/corefork.telegram.org/api/search.html deleted file mode 100644 index 017d38c3db..0000000000 --- a/data/corefork.telegram.org/api/search.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - Search - - - - - - - - - - - - - -
- -
-
-
- -

Search

- -
- -

Telegram allows applying detailed message filters while looking for messages in chats.

-

Search filters

-
inputMessagesFilterEmpty#57e2f66c = MessagesFilter;
-inputMessagesFilterPhotos#9609a51c = MessagesFilter;
-inputMessagesFilterVideo#9fc00e65 = MessagesFilter;
-inputMessagesFilterPhotoVideo#56e9f0e4 = MessagesFilter;
-inputMessagesFilterDocument#9eddf188 = MessagesFilter;
-inputMessagesFilterUrl#7ef0dd87 = MessagesFilter;
-inputMessagesFilterGif#ffc86587 = MessagesFilter;
-inputMessagesFilterVoice#50f5c392 = MessagesFilter;
-inputMessagesFilterMusic#3751b49e = MessagesFilter;
-inputMessagesFilterChatPhotos#3a20ecb8 = MessagesFilter;
-inputMessagesFilterPhoneCalls#80c99768 flags:# missed:flags.0?true = MessagesFilter;
-inputMessagesFilterRoundVoice#7a7c17a4 = MessagesFilter;
-inputMessagesFilterRoundVideo#b549da53 = MessagesFilter;
-inputMessagesFilterMyMentions#c1f8e69a = MessagesFilter;
-inputMessagesFilterGeo#e7026d0d = MessagesFilter;
-inputMessagesFilterContacts#e062db83 = MessagesFilter;
-inputMessagesFilterPinned#1bb00451 = MessagesFilter;
-
-messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
-
----functions---
-
-messages.search#a0fda762 flags:# peer:InputPeer q:string from_id:flags.0?InputPeer top_msg_id:flags.1?int filter:MessagesFilter min_date:int max_date:int offset_id:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
-
-messages.searchGlobal#4bc6589a flags:# folder_id:flags.0?int q:string filter:MessagesFilter min_date:int max_date:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;
-

When using messages.search or messages.searchGlobal, a certain message filter may be applied.
-This allows the server to filter messages based on a text query, and even on their type, and this feature is often used by graphical clients to implement features like the chat gallery, chat profile pictures and more. -Available filters:

- -

The returned messages.Messages constructors contain parameters for pagination, the messages themselves and two offset_id_offset/count parameters that can be used to display a progress/total counter like photo 134 of 200.
-For example, when displaying the chat photo gallery, we could display a photo ${offset_id_offset} of ${count} indicator on top.

-

Search counters

-
messages.searchCounter#e844ebff flags:# inexact:flags.1?true filter:MessagesFilter count:int = messages.SearchCounter;
-
----functions---
-
-messages.getSearchCounters#732eef00 peer:InputPeer filters:Vector<MessagesFilter> = Vector<messages.SearchCounter>;
-

Chat counters with filters can also be returned without fetching the actual messages, as seen in the schema above.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/sponsored-messages.html b/data/corefork.telegram.org/api/sponsored-messages.html deleted file mode 100644 index aa679e2b2c..0000000000 --- a/data/corefork.telegram.org/api/sponsored-messages.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - Sponsored messages - - - - - - - - - - - - - -
- -
-
-
- -

Sponsored messages

- -

Related TL schema:

-
sponsoredMessage flags:# random_id:bytes from_id:Peer channel_post:flags.2?int start_param:flags.0?string message:string entities:flags.1?Vector<MessageEntity> = SponsoredMessage;
-messages.sponsoredMessages messages:Vector<SponsoredMessage> chats:Vector<Chat> users:Vector<User> = messages.SponsoredMessages;
-
----functions---
-
-channels.getSponsoredMessages channel:InputChannel = messages.SponsoredMessages;
-channels.viewSponsoredMessage channel:InputChannel random_id:bytes = Bool;
-

Getting sponsored messages

-

Each time the user opens a channel, channels.getSponsoredMessages must be called to receive sponsored messages available for this channel. The result must be cached for 5 minutes.

-
-

More about sponsored messages on Telegram

-
-

Displaying sponsored messages

-

Sponsored messages must be displayed below all other posts in the channel, after the user scrolls futher down, past the last message. The promoted channel or bot specified in the from_id field must be displayed as the author of the message. The message should also contain one of the following buttons at the bottom:

-
    -
  • View Bot — if a bot is being promoted. Tapping the button must open the chat with the bot. If start_param is specified, the app must use the deep linking mechanism to open the bot.
  • -
  • View Channel — if a channel is being promoted. Tapping the button must open the channel.
  • -
  • View Post — if a channel is being promoted and channel_post is specified. Tapping the button must open the particular channel post.
  • -
-

Counting sponsored message views

-

Once the entire text is shown on the screen (excluding the button), channels.viewSponsoredMessage must be called with the random_id of this sponsored message.

-

Testing sponsored messages

-

For the channel https://t.me/SecretAdTestChannel the system will always return a sponsored message: promoting either a channel, a particular message in a channel, or a bot with a start parameter.

-
-

Sponsored messages in third-party apps

-

Telegram continues to grow worldwide, in part thanks to third-party apps using the Telegram API. To cover the increasing costs that come with this growth, Telegram added sponsored messages – a paid privacy-friendly way to promote bots and channels.

-

If their app allows its users to access content from Telegram channels, third-party developers using the Telegam API are required to support and properly display official sponsored messages in their apps by January 1, 2022. Unfortunately, Telegram cannot financially sustain third-party apps that do not display sponsored messages and they will have to be disconnected.

-

Telegram's API usage will continue to be free of charge for all developers. The rules regarding monetization in third-party apps remain the same: developers are allowed to monetize their coding efforts through advertising of their own or other legitimate means, provided that all the methods of monetization used in their apps are prominently mentioned in their app store descriptions.

-
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/api/srp.html b/data/corefork.telegram.org/api/srp.html deleted file mode 100644 index 94f2217ee9..0000000000 --- a/data/corefork.telegram.org/api/srp.html +++ /dev/null @@ -1,307 +0,0 @@ - - - - - Two-factor authentication - - - - - - - - - - - - - -
- -
-
-
- -

Two-factor authentication

- -
- -

Telegram uses the Secure Remote Password protocol version 6a to implement 2FA.

-

Example impementation: tdlib.

-

Checking the password with SRP

-

To login to an account protected by a 2FA password or to perform some other actions (like changing channel owner), you will need to verify the user's knowledge of the current 2FA account password.

-

To do this, first the client needs to obtain SRP parameters and the KDF algorithm to use to check the validity of the password via account.getPassword method. For now, only the passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow algorithm is supported, so we'll only explain that.

-

Then, after the user provides a password, the client should generate an InputCheckPasswordSRP object using SRP and a specific KDF algorithm as shown below and pass it to appropriate method (e.g. auth.checkPassword in case of authorization).

-

This extension of the SRP protocol uses the password-based PBKDF2 with 100000 iterations using sha512 (PBKDF2HMACSHA512iter100000). -PBKDF2 is used to additionally rehash the x parameter, obtained using a method similar to the one described in RFC 2945 (H(s | H ( I | password | I) | s) instead of H(s | H ( I | ":" | password)) (see below).

-

Here, | denotes concatenation and + denotes the arithmetical operator +. -In all cases where concatenation of numbers passed to hashing functions is done, the numbers must be used in big-endian form, padded to 2048 bits; all maths is modulo p. -Instead of I, salt1 will be used (see SRP protocol). -Instead of s, salt2 will be used (see SRP protocol).

-

The main hashing function H is sha256:

-
    -
  • H(data) := sha256(data)
  • -
-

The salting hashing function SH is defined as follows:

-
    -
  • SH(data, salt) := H(salt | data | salt)
  • -
-

The primary password hashing function is defined as follows:

-
    -
  • PH1(password, salt1, salt2) := SH(SH(password, salt1), salt2)
  • -
-

The secondary password hashing function is defined as follows:

-
    -
  • PH2(password, salt1, salt2) := SH(pbkdf2(sha512, PH1(password, salt1, salt2), salt1, 100000), salt2)
  • -
-

Client-side, the following parameters are extracted from the passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow object, contained in the account.password object.

-
    -
  • -

    g := algo.g

    -
  • -
  • -

    p := algo.p -The client is expected to check whether p is a safe 2048-bit prime (meaning that both p and (p-1)/2 are prime, and that 2^2047 < p < 2^2048), and that g generates a cyclic subgroup of prime order (p-1)/2, i.e. is a quadratic residue mod p. Since g is always equal to 2, 3, 4, 5, 6 or 7, this is easily done using quadratic reciprocity law, yielding a simple condition on p mod 4g -- namely, p mod 8 = 7 for g = 2; p mod 3 = 2 for g = 3; no extra condition for g = 4; p mod 5 = 1 or 4 for g = 5; p mod 24 = 19 or 23 for g = 6; and p mod 7 = 3, 5 or 6 for g = 7. After g and p have been checked by the client, it makes sense to cache the result, so as to avoid repeating lengthy computations in future. This cache might be shared with one used for Authorization Key generation.

    -

    If the client has an inadequate random number generator, it makes sense to use the secure_random of account.password as additional seed.

    -
  • -
  • -

    password := (user-provided password)

    -
  • -
  • -

    salt1 := algo.salt1

    -
  • -
  • -

    salt2 := algo.salt2

    -
  • -
  • -

    g_b := srp_B -srp_B and srp_id are extracted from the account.password object.

    -
  • -
-

The k parameter is generated, both on client and server:

-
    -
  • k := H(p | g)
  • -
-

The shared param u is generated: the client does this, and the server does the same with the g_a we will send him later (see below)

-
    -
  • u := H(g_a | g_b)
  • -
-

The final parameters are generated client-side only:

-
    -
  • x := PH2(password, salt1, salt2)
  • -
  • v := pow(g, x) mod p
  • -
-

The server already has v, from when we set the password.

-

A final shared param is generated, for commodity:

-
    -
  • k_v := (k * v) mod p
  • -
-

Finally, the key exchange process starts on both parties.

-

The client computes a 2048-bit number a (using sufficient entropy or the server’s random; see above) and generates:

-
    -
  • g_a := pow(g, a) mod p.
  • -
-

The server computes a 2048-bit number b using sufficient entropy and generates the g_b parameter that was sent to us (see above).

-
    -
  • g_b := (k_v + (pow(g, b) mod p)) mod p
  • -
-

Finally, the SRP session keys are generated:

-

Client side:

-
    -
  • t := (g_b - k_v) mod p (positive modulo, if the result is negative increment by p)
  • -
  • s_a := pow(t, a + u * x) mod p
  • -
  • k_a := H(s_a)
  • -
-

Server side:

-
    -
  • s_b := pow(g_a * (pow(v, u) mod p), b) mod p
  • -
  • k_b := H(s_b)
  • -
-

Since:

-
    -
  • g_b := (k_v + (pow(g, b) mod p)) mod p
  • -
  • t := (g_b - k_v) mod p
  • -
  • t := ((k_v + (pow(g, b) mod p)) - k_v) mod p
  • -
  • t := pow(g, b) mod p
  • -
  • s_a := pow(t, a + u * x) mod p
  • -
  • s_a := pow(pow(g, b) mod p, a + u * x) mod p
  • -
-

And:

-
    -
  • -

    g_a := pow(g, a) mod p

    -
  • -
  • -

    v := pow(g, x) mod p

    -
  • -
  • -

    s_b := pow(g_a * (pow(v, u) mod p), b) mod p

    -
  • -
  • -

    s_b := pow((pow(g, a) mod p) * (pow(pow(g, x) mod p, u) mod p), b) mod p

    -
  • -
  • -

    s_b := pow(pow(g, a + x * u) mod p, b) mod p

    -
  • -
  • -

    s_b := pow(pow(g, b) mod p, a + u * x) mod p

    -
  • -
  • -

    s_a := pow(pow(g, b) mod p, a + u * x) mod p

    -
  • -
-

This means:

-
    -
  • s_b === s_a
  • -
  • k_b === k_a
  • -
-

Finally, as per SRP:

-
    -
  • M1 := H(H(p) xor H(g) | H(salt1) | H(salt2) | g_a | g_b | k_a)
  • -
-

M1 is passed to inputCheckPasswordSRP, along with g_a (as A parameter) and the srp_id, extracted from the account.password object.

-

The server then computes:

-
    -
  • M2 := H(H(p) xor H(g) | H(salt1) | H(salt2) | g_a | g_b | k_b)
  • -
-

Since we said that:

-
    -
  • s_b === s_a
  • -
  • k_b === k_a
  • -
-

This means, if everything was done correctly,

-
    -
  • M1 === M2
  • -
-

If the password isn't correct, 400 PASSWORD_HASH_INVALID will be returned.

-

Setting a new 2FA password

-

To set a new 2FA password use the account.updatePasswordSettings method.
-If a password is already set, generate an InputCheckPasswordSRP object as per checking passwords with SRP, and insert it in the password field of the account.updatePasswordSettings method.
-To remove the current password, pass an empty new_password_hash in the account.PasswordInputSettings object.

-

To set a new password, use the SRP parameters and the KDF algorithm obtained using account.getPassword when generating the password field. -Then generate a new new_password_hash using the KDF algorithm specified in the new_settings, just append 32 sufficiently random bytes to the salt1, first. -Proceed as for checking passwords with SRP, just stop at the generation of the v parameter, and use it as new_password_hash:

-
    -
  • v := pow(g, x) mod p
  • -
-

As usual in big endian form, padded to 2048 bits.

-

Email verification

-

When setting up two-factor authorization, it is recommended to set up a recovery email, to allow recovery of the password through the user's email address, in case they forget it.

-

To set up a recovery email, it must first be verified. -This can be done directly when setting the new password using account.updatePasswordSettings by setting the email parameter and flag in the account.passwordInputSettings constructor. -If the email isn't verified, an EMAIL_UNCONFIRMED_X 400 error will be returned, where X is the length of the verification code that was just sent to the email. -Use account.confirmPasswordEmail to enter the received verification code and enable the recovery email. -Use account.resendPasswordEmail to resend the verification code. -Use account.cancelPasswordEmail to cancel the verification code.

-

To get the current recovery email, use account.getPasswordSettings.

-

Email recovery

-

In order to recover a forgotten 2FA password, an email must be sent to the previously specified address using the auth.requestPasswordRecovery method.
-Use auth.checkRecoveryPassword to make sure that the user provided a valid code.
-Then use auth.recoverPassword with the received code to delete the current 2FA password, to set a new one follow these instructions.

-

Password reset

-
account.resetPasswordFailedWait#e3779861 retry_date:int = account.ResetPasswordResult;
-account.resetPasswordRequestedWait#e9effc7d until_date:int = account.ResetPasswordResult;
-account.resetPasswordOk#e926d63e = account.ResetPasswordResult;
-
----functions---
-
-account.resetPassword#9308ce1b = account.ResetPasswordResult;
-account.declinePasswordReset#4c9409f6 = Bool;
-

If the user is already logged in and has forgotten their 2FA password, account.resetPassword can be used to initiate a password reset.
-On success, the call will initially return a account.resetPasswordRequestedWait constructor and start a 7-day server-side timer, during which the user can abort the reset process using a button sent by the Telegram service account or directly in-UI using account.declinePasswordReset.

-

When the time comes, account.resetPassword is invoked once more, returning a account.resetPasswordOk to indicate that the password was successfully reset.

-

If the user recently requested a password reset that was canceled, account.resetPasswordFailedWait will be returned by the initial account.resetPassword call, and they must wait until the specified date before requesting another reset.

-

Note that if the user already knows their 2FA password and simply wants to disable 2FA, the same process used to enable the password must also be used to disable it ».

-

Related pages

-

SRP design

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/stats.html b/data/corefork.telegram.org/api/stats.html deleted file mode 100644 index 52dda65ee3..0000000000 --- a/data/corefork.telegram.org/api/stats.html +++ /dev/null @@ -1,297 +0,0 @@ - - - - - Channel statistics - - - - - - - - - - - - - -
- -
-
-
- -

Channel statistics

- -
- -

Telegram offers detailed channel statistics for channels and supergroups.

-

Channel statistics

-

Schema:

-
statsDateRangeDays#b637edaf min_date:int max_date:int = StatsDateRangeDays;
-
-statsAbsValueAndPrev#cb43acde current:double previous:double = StatsAbsValueAndPrev;
-
-statsPercentValue#cbce2fe0 part:double total:double = StatsPercentValue;
-
-statsGraphAsync#4a27eb2d token:string = StatsGraph;
-statsGraphError#bedc9822 error:string = StatsGraph;
-statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
-
-messageInteractionCounters#ad4fc9bd msg_id:int views:int forwards:int = MessageInteractionCounters;
-
-stats.broadcastStats#bdf78394 period:StatsDateRangeDays followers:StatsAbsValueAndPrev views_per_post:StatsAbsValueAndPrev shares_per_post:StatsAbsValueAndPrev enabled_notifications:StatsPercentValue growth_graph:StatsGraph followers_graph:StatsGraph mute_graph:StatsGraph top_hours_graph:StatsGraph interactions_graph:StatsGraph iv_interactions_graph:StatsGraph views_by_source_graph:StatsGraph new_followers_by_source_graph:StatsGraph languages_graph:StatsGraph recent_message_interactions:Vector<MessageInteractionCounters> = stats.BroadcastStats;
-
----functions---
-
-stats.getBroadcastStats#ab42441a flags:# dark:flags.0?true channel:InputChannel = stats.BroadcastStats;
-stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;
-

Administrators of channels of a certain size (the exact limit is a server-side config, returned in the can_view_stats flag of channelFull) can call stats.getBroadcastStats to get detailed channel statistics.
-The returned stats.broadcastStats contains multiple statistics:

-
    -
  • Period-related statistics: a pair of values, one at the beginning and one at the end of the period in consideration (period).
    The period typically depends on channel activity.
      -
    • Absolute follower count (followers)
    • -
    • total_viewcount/postcount, for posts posted during the period in consideration (views_per_post).
      -Note that in this case, current refers to the period in consideration (min_date till max_date), and prev refers to the previous period ((min_date - (max_date - min_date)) till min_date).
    • -
    • total_sharecount/postcount, for posts posted during the period in consideration (shares_per_post).
      -Note that in this case, current refers to the period in consideration (min_date till max_date), and prev refers to the previous period ((min_date - (max_date - min_date)) till min_date).
    • -
    -
  • -
  • Percentage statistics
      -
    • Percentage of subscribers with enabled notifications (enabled_notifications)
    • -
    -
  • -
  • Graphs: graphs are described below ».
  • -
-

Supergroup statistics

-

Schema:

-
statsGroupTopPoster#9d04af9b user_id:long messages:int avg_chars:int = StatsGroupTopPoster;
-statsGroupTopInviter#535f779d user_id:long invitations:int = StatsGroupTopInviter;
-statsGroupTopAdmin#d7584c87 user_id:long deleted:int kicked:int banned:int = StatsGroupTopAdmin;
-
-stats.megagroupStats#ef7ff916 period:StatsDateRangeDays members:StatsAbsValueAndPrev messages:StatsAbsValueAndPrev viewers:StatsAbsValueAndPrev posters:StatsAbsValueAndPrev growth_graph:StatsGraph members_graph:StatsGraph new_members_by_source_graph:StatsGraph languages_graph:StatsGraph messages_graph:StatsGraph actions_graph:StatsGraph top_hours_graph:StatsGraph weekdays_graph:StatsGraph top_posters:Vector<StatsGroupTopPoster> top_admins:Vector<StatsGroupTopAdmin> top_inviters:Vector<StatsGroupTopInviter> users:Vector<User> = stats.MegagroupStats;
-
----functions---
-
-stats.getMegagroupStats#dcdf8607 flags:# dark:flags.0?true channel:InputChannel = stats.MegagroupStats;
-

Administrators of supergroups of a certain size (the exact limit is a server-side config, returned in the can_view_stats flag of channelFull) can call stats.getMegagroupStats to get detailed supergroup statistics.
-The returned stats.broadcastStats contains multiple statistics, see the constructor page for more info ».

-

Message statistics

-
stats.messageStats#8999f295 views_graph:StatsGraph = stats.MessageStats;
-
----functions---
-
-stats.getMessageStats#b6e0a3f5 flags:# dark:flags.0?true channel:InputChannel msg_id:int = stats.MessageStats;
-

Administrators of channels of a certain size (the exact limit is a server-side config, returned in the can_view_stats flag of channelFull) can call stats.getMessageStats to get statistics of a specific message.
-The returned stats.messageStats contains the view graph of the message.

-

Graph visualization

-

There are four available visualizations for graph types:

- -

Graph modifiers (see various graphs for examples):

-
    -
  • y_scaled - Indicates that each of the two (!) lines in a step graph must be visualized on its own scale, with two different tick axes on the left and right parts of the graph
  • -
  • percentage - Indicates whether value percentages should be shown in labels
  • -
  • stacked - Depending on the graph type, indicates stacking of multiple columns in the same graph
  • -
-

Graph syntax

-
statsGraphAsync#4a27eb2d token:string = StatsGraph;
-statsGraphError#bedc9822 error:string = StatsGraph;
-statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
-
-dataJSON#7d748d04 data:string = DataJSON;
-
----functions---
-
-stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;
-

Certain graphs are not directly sent in the stats.broadcastStats constructor to reduce server load: instead, those graphs will be sent as a statsGraphAsync constructor, and should be fetched separately using stats.loadAsyncGraph.

-

After obtaining the full statsGraph constructor, clients should parse the JSON graph object in the json field.

-

Object structure:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
KeyGraph title
columnsArray of all data column arrays in the chart. Each column array has its label at position 0, followed by values.
typesGraphs types for each of the column arrays (object, "label": "type"):
- line - line graph
- area - area graph
- step - step graph
- bar - bar graph
- x - x axis values for each of the charts at the corresponding positions, UNIX timestamps in milliseconds.
colorsColor for each type (object, "label": "colorKey#AAAAAA"; see chart colors).
namesLocalized name for each variable (object, "label": "Name")
subchartObject indicating the default zoom range for the graph, this is object's structure:
- show - Whether to use the specified zoom range (boolean)
- defaultZoom - An array with two x values, indicating the two ends of the default zoom range
y_scaledIndicates that each of the two (!) lines in a step graph must be visualized on its own scale, with two different tick axes on the left and right parts of the graph (boolean, see various graphs for examples)
percentageIndicates whether value percentages should be shown in labels (boolean, see various graphs for examples)
stackedDepending on the graph type, indicates stacking of multiple columns in the same graph (boolean, see various graphs for examples)
- -

The following chart restrictions apply:

-
    -
  • Up to 50 columns on one graph must be supported.
  • -
  • Chart types are always the same for every column in the graph.
  • -
  • The bar chart type and stacked option are always used together.
  • -
  • percentage is always used with the area graph. - -
  • -
-

Chart zooming

-
statsGraphError#bedc9822 error:string = StatsGraph;
-statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
-
-dataJSON#7d748d04 data:string = DataJSON;
-
----functions---
-
-stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;
-

Graphs that support zooming will contain a zoom_token in the statsGraph constructor.
-Said token should be then used as token in a new stats.loadAsyncGraph call triggered when the user clicks on the label, related to a certain x axis in the graph (see graph examples).
-The x coordinate of the label should be provided to the x parameter; the method will then return (if available) a more detailed subgraph.
-If not enough data is available, a localized statsGraphError will be returned.

-

Typical zoom visualization rules:

- -

Chart colors

-

Chart colors can be provided as a color key, followed by the primary color value in hex format:

-
red#e05356
-

The color key can be one of red, lightblue, lightgreen, golden, green, orange, blue, indigo.
-Apps can choose to use a color value specified by the currently loaded theme: for example, the android app uses statisticChartLine_* themekeys for each of the color keys, check out the assets directory for a bunch of default themes with various colors for channel statistics.

-

However, the server may also choose to return just a plain color value in hex format:

-
#e05356
-

In this case, the dark flag of the stats.getBroadcastStats method can be used to choose the palette of returned colors.

-

Graph examples

-

Line graph

-

Simple single line graph

-

Step graph

-

Step graph, always "stacked" (to indicate multiple lines)

-

Bar graph

-

Bar graph with multiple lines, always "stacked" (to indicate actual stacked bars, biggest bars first)

-

Area graph

-

Mixed bar/line graph, always "stacked" (to indicate actual stacked bars, biggest bars first)

-

Piechart

-

Piechart, typically obtained only when zooming into percentage graphs

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/terms.html b/data/corefork.telegram.org/api/terms.html deleted file mode 100644 index a049063beb..0000000000 --- a/data/corefork.telegram.org/api/terms.html +++ /dev/null @@ -1,133 +0,0 @@ - - - - - Telegram API Terms of Service - - - - - - - - - - - - - -
- -
-
-
- -

Telegram API Terms of Service

- -
- -

We welcome all developers to use our API and source code to create Telegram-like messaging applications on our platform free of charge. In order to ensure consistency and security across the Telegram ecosystem, all third-party client apps must comply with the following Terms of Service.

-

1. Privacy & Security

-

1.1. Telegram is a privacy-oriented platform. All client apps must, therefore, guard their users' privacy with utmost care and comply with our Security Guidelines.
1.2. Developers are welcome to add new features or improve and extend existing Telegram features provided that these modifications do not violate these Terms of Service.
1.3. As a client developer, you must make sure that all the basic features of the main Telegram apps function correctly and in an expected way both in your app and when users of your app communicate with other Telegram users. It is forbidden to force users of other Telegram clients to download your app in order to view certain messages and content sent using your app.
1.4. It is forbidden to interfere with the basic functionality of Telegram. This includes but is not limited to: making actions on behalf of the user without the user's knowledge and consent, preventing self-destructing content from disappearing, preventing last seen and online statuses from being displayed correctly, tampering with the 'read' statuses of messages (e.g. implementing a 'ghost mode'), preventing typing statuses from being sent/displayed, etc.

-

2. Transparency

-

2.1. You must obtain your own api_id for your application.
2.2. We offer our API free of charge, but your users must be aware of the fact that your app uses the Telegram API and is part of the Telegram ecosystem. This fact must be featured prominently in the app's description in the app stores and in the in-app intro if your app has it.
2.3. To avoid confusion, the title of your app must not include the word “Telegram”. An exception can be made if the word “Telegram” is preceded with the word “Unofficial” in the title.
2.4. You must not use the official Telegram logo for your app. Both the Telegram brand and its logo are registered trademarks protected by law in almost every country.

-

3. Advertising & Monetization

-

3.1. Developers are allowed to monetize their coding efforts through advertising or other legitimate means.
3.2. If you decide to monetize your app, you must clearly mention all the methods of monetization that are used in your app in all its app store descriptions.
3.3. If your app allows accessing content from Telegram channels, you must include support for official sponsored messages in Telegram channels and may not interefere with this functionality.

-

4. Breach of terms

-

4.1. If your app violates these terms, we will notify the Telegram account responsible for the app about the breach of terms.
4.2. If you do not update the app to fix the highlighted issues within 10 days, we will have to discontinue your access to Telegram API and contact the app stores about the removal of your apps that are using the Telegram API in violation of these terms.

-

We reserve the right to expand these terms and guidelines as the need arises. We will inform client developers of such changes via an in-app notification to their accounts connected to the app in question.

-
-

Back to Creating Your Telegram Application »

-
-
- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/top-rating.html b/data/corefork.telegram.org/api/top-rating.html deleted file mode 100644 index 2ac9ea8ff4..0000000000 --- a/data/corefork.telegram.org/api/top-rating.html +++ /dev/null @@ -1,145 +0,0 @@ - - - - - Top peer rating - - - - - - - - - - - - - -
- -
-
-
- -

Top peer rating

- -

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

-

Schema:

-
topPeer#edcdc05b peer:Peer rating:double = TopPeer;
-
-topPeerCategoryBotsPM#ab661b5b = TopPeerCategory;
-topPeerCategoryBotsInline#148677e2 = TopPeerCategory;
-topPeerCategoryCorrespondents#637b7ed = TopPeerCategory;
-topPeerCategoryGroups#bd17a14a = TopPeerCategory;
-topPeerCategoryChannels#161d9628 = TopPeerCategory;
-topPeerCategoryPhoneCalls#1e76a78c = TopPeerCategory;
-topPeerCategoryForwardUsers#a8406ca9 = TopPeerCategory;
-topPeerCategoryForwardChats#fbeec0f0 = TopPeerCategory;
-
-topPeerCategoryPeers#fb834291 category:TopPeerCategory count:int peers:Vector<TopPeer> = TopPeerCategoryPeers;
-
-contacts.topPeersNotModified#de266ef5 = contacts.TopPeers;
-contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;
-contacts.topPeersDisabled#b52c939d = contacts.TopPeers;
-
----functions---
-
-contacts.getTopPeers#973478b6 flags:# correspondents:flags.0?true bots_pm:flags.1?true bots_inline:flags.2?true phone_calls:flags.3?true forward_users:flags.4?true forward_chats:flags.5?true groups:flags.10?true channels:flags.15?true offset:int limit:int hash:long = contacts.TopPeers;
-

The rate delta is computed by taking the time delta between the last time the user used a certain peer and the last time the rating for that peer was received and dividing it by the exponential decay from config.

-

Example: -Client-side, every time a user opens chat 123456789 the following operation must be done on the cached top peer info.

-
    -
  • dateOpened indicates when was the peer used
  • -
  • normalizeRate is an arbitrary time in the recent past. -When ratings are received from the server using contacts.getTopPeers and the schema described above, it is the time when they were received.
  • -
-
topPeer.rating += e^((dateOpened - normalizeRate) / config.rating_e_decay)
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/api/updates.html b/data/corefork.telegram.org/api/updates.html deleted file mode 100644 index 46c6067ad9..0000000000 --- a/data/corefork.telegram.org/api/updates.html +++ /dev/null @@ -1,226 +0,0 @@ - - - - - Working with Updates - - - - - - - - - - - - - -
- -
-
-
- -

Working with Updates

- -
- -

When a client is being actively used, events will occur that affect the current user and that they must learn about as soon as possible, e.g. when a new message is received. To eliminate the need for the client itself to periodically download these events, there is an update delivery mechanism in which the server sends the user notifications over one of its available connections with the client.

-

Subscribing to Updates

-

Update events are sent to an authorized user into the last active connection (except for connections needed for downloading / uploading files).

-

So to start receiving updates the client needs to init connection and call API method, e.g. to fetch current state.

-

Event sequences

-

All events are received from the socket as a sequence of TL-serialized Updates objects, which might be optionally gzip-compressed in the same way as responses to queries.

-

Each Updates object may contain single or multiple Update objects, representing different events happening.

-

In order to apply all updates in precise order and to guarantee that no update is missed or applied twice there is seq attribute in Updates constructors, and pts (with pts_count) or qts attributes in Update constructors. The client must use those attributes values in combination with locally stored state to correctly apply incoming updates.

-

When a gap in updates sequence occurs, it must be filled via calling one of the API methods. More below »

-

Updates sequence

-

As said earlier, each payload with updates has a TL-type Updates. It can be seen from the schema below that this type has several constructors.

-
updatesTooLong#e317af7e = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-

updatesTooLong indicates that there are too many events pending to be pushed to the client, so one needs to fetch them manually.

-

Events inside updateShort constructors, normally, have lower priority and are broadcast to a large number of users, i.e. one of the chat participants started entering text in a big conversation (updateChatUserTyping).

-

The updateShortMessage, updateShortSentMessage and updateShortChatMessage constructors are redundant but help significantly reduce the transmitted message size for 90% of the updates. They should be transformed to updateShort upon receiving.

-

Two remaining constructors updates and updatesCombined are part of the Updates sequence. Both of them have seq attribute, which indicates the remote Updates state after the generation of the Updates, and seq_start indicates the remote Updates state after the first of the Updates in the packet is generated. For updates, seq_start attribute is omitted, because it is assumed that it is always equal to seq.

-

Message-related event sequences

-

Each event related to a message box (message created, message edited, message deleted, etc) is identified by a unique autoincremented pts, or qts in case of secret chat updates, certain bot updates, etc.

-

Each message box can be considered as some server-side DB table that stores messages and events associated with them. -All boxes are completely independent, and each pts sequence is tied to just one box (see below).

-

Update object may contain info about multiple events (for example, updateDeleteMessages). -That's why all single updates might have pts_count parameter indicating the number of events contained in the received update (with some exceptions, in this case, the pts_count is considered to be 0).

-

Each channel and supergroup has its message box and its event sequence as a result; private chats and legacy groups of one user have another common event sequence. -Secret chats, certain bot events and other kinds of updates have yet another common secondary event sequence.

-

To recap, the client has to take care of the integrity of the following sequences to properly handle updates:

-
    -
  • Updates sequence (seq)
      -
    • Common message box sequence (pts)
    • -
    • Secondary event sequence (qts)
    • -
    • Channel message box sequence 1 (pts)
    • -
    • Channel message box sequence 2 (pts)
    • -
    • Channel message box sequence 3 (pts)
    • -
    • and so on...
    • -
    -
  • -
-

Fetching state

-

The common update state is represented by the updates.State constructor. -When the user logs in for the first time, call to updates.getState has to be made to store the latest update state (which will not be the absolute initial state, just the latest state at the current time). -The common update state can also be fetched from updates.differenceTooLong.

-

The channel update state is represented simply by the pts of the event sequence: when first logging in, the initial channel state can be obtained from the dialog constructor when fetching dialogs, from the full channel info, or it can be received as an updateChannelTooLong update.

-

The secondary update state is represented by the qts of the secret event sequence, it is contained in the updates.State of the common update state.

-

The Updates sequence state is represented by the date and seq of the Updates sequence, it is contained in the updates.State of the common update state.

-

Update handling

-

Update handling in Telegram clients consists of receiving events, making sure there were no gaps and no events were missed based on the locally stored state of the correspondent event sequence, and then updating the locally stored state based on the parameters received.

-

When the client receives payload with serialized updates, first of all, it needs to walk through all of the nested Update objects and check if they belong to any of message box sequences (have pts or qts parameters). Those updates need to be handled separately according to corresponding local state and new pts/qts values. Details below »

-

After message box updates are handled, if there are any other updates remaining the client needs to handle them with respect to seq. Details below »

-

pts: checking and applying

-

Here, local_pts will be the local state, pts will be the remote state, pts_count will be the number of events in the update.

-

If local_pts + pts_count === pts, the update can be applied. -If local_pts + pts_count > pts, the update was already applied, and must be ignored. -If local_pts + pts_count < pts, there's an update gap that must be filled.

-

For example, let's assume the client has the following local state for the channel 123456789:

-
local_pts = 131
-

Now let's assume an updateNewChannelMessage from channel 123456789 is received with pts = 132 and pts_count=1. -Since local_pts + pts_count === pts, the total number of events since the last stored state is, in fact, equal to pts_count: this means the update can be safely accepted and the remote pts applied:

-
local_pts = 132
-

Since:

-
    -
  • pts indicates the server state after the new channel message events are generated
  • -
  • pts_count indicates the number of events in the new channel update
  • -
  • The server state before the new channel message event was generated has to be: pts_before = pts - pts_count = 131, which is, in fact, equal to our local state.
  • -
-

Now let's assume an updateNewChannelMessage from channel 123456789 is received with pts = 132 and pts_count=1. -Since local_pts + pts_count > pts (133 > 132), the update is skipped because we've already handled this update (in fact, our current local_pts was set by this same update, and it was resent twice due to network issues or other issues).

-

Now let's assume an updateDeleteChannelMessages from channel 123456789 is received with pts = 140 and pts_count=5. -Since local_pts + pts_count < pts (137 < 140), this means that updates were missed, and the gap must be recovered.

-
Secret chats & bots
-

The whole process is very similar for secret chats and certain bot updates, but there is qts instead of pts, and events are never grouped, so it's assumed that qts_count is always equal to 1.

-

seq: checking and applying

-

On top level when handling received updates and updatesCombined there are three possible cases: -If local_seq + 1 === seq_start, the updates can be applied. -If local_seq + 1 > seq_start, the updates were already applied, and must be ignored. -If local_seq + 1 < seq_start, there's an updates gap that must be filled (updates.getDifference must be used as with common and secret event sequences).

-

If the updates were applied, local Updates state must be updated with seq and date from the constructor.

-

For all the other Updates type constructors there is no need to check seq or change a local state.

-

Recovering gaps

-

To do this, updates.getDifference (common/secret state) or updates.getChannelDifference (channel state) with the respective local states must be called. -These methods should also be called on startup, to fetch new updates (preferably with some flags to reduce server load, see the method's docs). -Manually obtaining updates is also required in the following situations:

-
    -
  • Loss of sync: a gap was found in seq / pts / qts (as described above). It may be useful to wait up to 0.5 seconds in this situation and abort the sync in case a new update arrives, that fills the gap.
  • -
  • Session loss on the server: the client receives a new session created notification. This can be caused by garbage collection on the MTProto server or a server reboot.
  • -
  • Incorrect update: the client cannot deserialize the received data.
  • -
  • Incomplete update: the client is missing data about a chat/user from one of the shortened constructors, such as updateShortChatMessage, etc.
  • -
  • Long period without updates: no updates for 15 minutes or longer.
  • -
  • The server requests the client to fetch the difference using updateChannelTooLong or updatesTooLong.
  • -
-

When calling updates.getDifference if the updates.differenceSlice constructor is returned in response, the full difference was too large to be received in one request. The intermediate status, intermediate_state, must be saved on the client and the query must be repeated, using the intermediate status as the current status.

-

To fetch the updates difference of a channel, updates.getChannelDifference is used. -If the difference is too large to be received in one request, the final flag of the result is not set (see docs). -The intermediate status, represented by the pts, must be saved on the client and the query must be repeated, using the intermediate status as the current status.

-

For perfomance reasons and for better user experience, client can set maximum gap size to be filled: pts_total_limit parameter of updates.getDifference and limit parameter for updates.getChannelDifference can be used.

-

If the gap is too large and there are too many updates to fetch, a *TooLong constructor will be returned. In this case, the client must re-fetch the state, re-start fetching updates from that state and follow the instructions that can be found here.

-

It is recommended to use limit 10-100 for channels and 1000-10000 otherwise.

-

Example implementations

-

Implementations also have to take care to postpone updates received via the socket while filling gaps in the event and Update sequences, as well as avoid filling gaps in the same sequence.

-

Example implementations: tdlib, MadelineProto.

-

An interesting and easy way this can be implemented, instead of using various locks, is by running background loops, like in MadelineProto ».

-

PUSH Notifications about Updates

-

If a client does not have an active connection at the time of an event, PUSH Notifications will also be useful.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/url-authorization.html b/data/corefork.telegram.org/api/url-authorization.html deleted file mode 100644 index 365eb87458..0000000000 --- a/data/corefork.telegram.org/api/url-authorization.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - Seamless Telegram Login - - - - - - - - - - - - - -
- -
-
-
- -

Seamless Telegram Login

- -
- -

Bots or Telegram websites may ask users to login to a certain website via Telegram when clicking on certain links or URL buttons in inline keyboards.

-

Bot URL authorization

-

When the user clicks on keyboardButtonUrlAuth, messages.requestUrlAuth should be called, providing the button_id of the button and the ID and peer of the container message. -The returned urlAuthResultRequest object will contain more details about the authorization request:

-
    -
  • The domain parameter will contain the domain name of the website on which the user will log in (example: comments.app).
  • -
  • The bot parameter will contain info about the bot which will be used for user authorization (example: DiscussBot).
  • -
  • The request_write_access will be set if the bot would like to send messages to the user.
  • -
-

The info should be shown in a prompt:

-
- TITLE -
-

If the user agrees to login to the URL, messages.acceptUrlAuth should be called (eventually setting the write_allowed if the permission was requested and the user consented). -The result will be a urlAuthResultAccepted with the final URL to open, which will include a query string with the requested info and a hash that must be verified upon receival by the service.

-

urlAuthResultDefault could also be returned, instead, in which case the url of the keyboardButtonUrlAuth must be opened, instead. -The same must be done if the user opens the link while refusing the authorization request.

-

Link URL authorization

-

Telegram supports automatic authorization on certain websites upon opening an HTTP URL in-app, upon clicking a link in a message or clicking on a keyboardButtonUrl.

-

Automatic authorization

-

Clients should automatically authenticate users when opening official Telegram websites, listed in the url_auth_domains key of the client configuration object ».

-

Upon clicking a link, the URL must be modified by appending the autologin_token from the client configuration object » to the query string, like so:

-

Original URL: https://somedomain.telegram.org/path?query=string#fragment=value
-Modified URL: https://somedomain.telegram.org/path?query=string&autologin_token=$autologin_token#fragment=value

-

Make sure that the used autologin_token is no more than 10000 seconds old, if it is older it must be refetched before use as described in the client configuration section ».

-

Manual authorization

-

Clients should show a confirmation prompt similar to the one used for bots, to authenticate users when opening certain Telegram websites, listed in the url_auth_domains key of the client configuration object ».

-

messages.requestUrlAuth should be called, providing only the original url. -The returned urlAuthResultRequest object will contain more details about the authorization request:

-
    -
  • The domain parameter will contain the domain name of the website on which the user will log in (example: comments.app).
  • -
  • The request_write_access will be set if the website would like to send messages to the user.
  • -
-

The info should be shown in a prompt.

-

If the user agrees to login to the URL, messages.acceptUrlAuth should be called (eventually setting the write_allowed if the permission was requested and the user consented). -The result will be a urlAuthResultAccepted with the final URL to open.

-

urlAuthResultDefault could also be returned, instead, in which case the original URL must be opened, instead. -The same must be done if the user opens the link while refusing the authorization request.

-

Related articles

-

Client configuration

-

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/api/web-events.html b/data/corefork.telegram.org/api/web-events.html deleted file mode 100644 index ffe0ed4019..0000000000 --- a/data/corefork.telegram.org/api/web-events.html +++ /dev/null @@ -1,175 +0,0 @@ - - - - - Web events - - - - - - - - - - - - - -
- -
-
-
- -

Web events

- -
- -

When interacting with HTML5 games and the websites of payment gateways, Telegram apps should expose APIs to allow receiving data and events from the websites.

-

Event APIs

-

Games and payment gateways can generate events that are meant to be received by the Telegram apps.
Typically events are generated by using the postEvent method of the GamingCommunication library.
The postEvent function will try sending the event to the Telegram app in a number of different ways.

-

WebviewProxy

-

In mobile apps, the event receiver API should be typically exposed as a window.TelegramWebviewProxy object with a postEvent method.

-
window.TelegramWebviewProxy.postEvent(eventType, eventData)
-

window.external

-

Alternatively, a window.external.notify method can be exposed, accepting a string JSON payload with the event type and payload:

-
window.external.notify(JSON.stringify({eventType: eventType, eventData: eventData}));
-

postMessage API

-

Finally, web MTProto clients that need to open a game or process a payment in an iframe can use the postMessage API to receive events from iframes.
The GamingCommunication library by default will use '*' as targetOrigin, sending messages to parent pages regardless of the origin of the embedder.

-
window.parent.postMessage(JSON.stringify({eventType: eventType, eventData: eventData}), targetOrigin);
-

Event types

-

eventType is a simple string indicating the event type, and eventData is a payload with an object that will be parsed by the Telegram app.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
eventTypeeventDataDescription
payment_form_submitJSON object with data and title fieldstitle is the censored credit card title.
data is a service-specific JSON payload with information about the payment credentials provided by the user to the payment system.
Neither Telegram, nor bots will have access to your credit card information.
Credit card details will be handled only by the payment system.
share_scorenullWill be called by games when the user explicitly clicks on the share score button to share the game, along with his score.
Typically done by using messages.forwardMessages on the game message with the with_my_score flag.
share_gamenullWill be called by games when the user explicitly clicks on the share game button to share the game, without sharing his score.
Typically done by using messages.forwardMessages on the game message without the with_my_score flag, or by sharing the game's short URL.
game_overnullCan be called by games when the user loses a game
game_loadednullCan be called by games once the game fully loads
resize_frameJSON object with height fieldCalled by supported pages inside of IV iframe embeds, indicates the new size of the embed frame.
-
- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html b/data/corefork.telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html deleted file mode 100644 index 97d4e3ec39..0000000000 --- a/data/corefork.telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html +++ /dev/null @@ -1,115 +0,0 @@ - - - - - Page not found - - - - - - - - - - - - - -
- -
-
-
-
-

Page not found

- -
The page has not been saved
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/bots.html b/data/corefork.telegram.org/bots.html deleted file mode 100644 index c2070b62dc..0000000000 --- a/data/corefork.telegram.org/bots.html +++ /dev/null @@ -1,420 +0,0 @@ - - - - - Bots: An introduction for developers - - - - - - - - - - - - - -
- -
-
-
-
-

Bots: An introduction for developers

- -
- -

Bots are third-party applications that run inside Telegram. Users can interact with bots by sending them messages, commands and inline requests. You control your bots using HTTPS requests to our Bot API.

-

1. What can I do with bots?

-
- -
-

To name just a few things, you could use bots to:

-
    -
  • -

    Get customized notifications and news. A bot can act as a smart newspaper, sending you relevant content as soon as it's published.

    -
  • -
  • -

    Integrate with other services. A bot can enrich Telegram chats with content from external services. -Gmail Bot, GIF bot, IMDB bot, Wiki bot, Music bot, Youtube bot, GitHubBot

    -
  • -
  • -

    Accept payments from Telegram users. A bot can offer paid services or work as a virtual storefront. Read more » -Demo Shop Bot, Demo Store

    -
  • -
  • -

    Create custom tools. A bot may provide you with alerts, weather forecasts, translations, formatting or other services. -Markdown bot, Sticker bot, Vote bot, Like bot

    -
  • -
  • -

    Build single- and multiplayer games. A bot can offer rich HTML5 experiences, from simple arcades and puzzles to 3D-shooters and real-time strategy games. -GameBot, Gamee

    -
  • -
  • -

    Build social services. A bot could connect people looking for conversation partners based on common interests or proximity.

    -
  • -
  • -

    Do virtually anything else. Except for dishes — bots are terrible at doing the dishes.

    -
  • -
-

2. How do bots work?

-

At the core, Telegram Bots are special accounts that do not require an additional phone number to set up. Users can interact with bots in two ways:

-
    -
  • Send messages and commands to bots by opening a chat with them or by adding them to groups.
  • -
  • Send requests directly from the input field by typing the bot's @username and a query. This allows sending content from inline bots directly into any chat, group or channel.
  • -
-

Messages, commands and requests sent by users are passed to the software running on your servers. Our intermediary server handles all encryption and communication with the Telegram API for you. You communicate with this server via a simple HTTPS-interface that offers a simplified version of the Telegram API. We call that interface our Bot API.

-
-

A detailed description of the Bot API is available on this page »

-
-

3. How do I create a bot?

-
- -
-

There's a... bot for that. Just talk to BotFather (described below) and follow a few simple steps. Once you've created a bot and received your authentication token, head down to the Bot API manual to see what you can teach your bot to do.

-
-

You may also like to check out some code examples here »

-
-

4. How are bots different from humans?

-
    -
  • Bots have no online status and no last seen timestamps, the interface shows the label 'bot' instead.
  • -
  • Bots have limited cloud storage — older messages may be removed by the server shortly after they have been processed.
  • -
  • Bots can't initiate conversations with users. A user must either add them to a group or send them a message first. People can use t.me/<bot_username> links or username search to find your bot.
  • -
  • Bot usernames always end in 'bot' (e.g. @TriviaBot, @GitHub_bot).
  • -
  • When added to a group, bots do not receive all messages by default (see Privacy mode).
  • -
  • Bots never eat, sleep or complain (unless expressly programmed otherwise).
  • -
-
-

5. Bot perks

-

Telegram bots are unique in many ways — we offer two kinds of keyboards, additional interfaces for default commands and deep linking as well as text formatting, integrated payments and more.

-

Inline mode

- -

Users can interact with your bot via inline queries straight from the text input field in any chat. All they need to do is start a message with your bot's username and then type a query.

-

Having received the query, your bot can return some results. As soon as the user taps one of them, it is sent to the user's currently opened chat. This way, people can request content from your bot in any of their chats, groups or channels.

-

Check out this blog to see a sample inline bot in action. You can also try the @sticker and @music bots to see for yourself.

-
-
-
-

We've also implemented an easy way for your bot to switch between inline and PM modes.

-
-

Read more about the Inline Mode »

-
-

Payment platform

- -

You can use bots to accept payments from Telegram users around the world.

-
    -
  • Send invoices to any chat, including to groups and channels.
  • -
  • Create invoices that can be forwarded and used by multiple buyers to order things.
  • -
  • Use inline mode to help users show your goods and services to their friends and communities.
  • -
  • Allow tips from users with preset and custom amounts.
  • -
  • Accept payments from users on mobile or desktop apps.
  • -
  • Try @ShopBot to create a test invoice – or start a message with @ShopBot ... in any chat for an inline invoice.
  • -
  • Check out Demo Shop for an example of a Telegram Channel used as virtual storefront.
  • -
-
- -
-
-

Read more about the Payments Platform »

-
-

Gaming platform

-

Bots can offer their users HTML5 games to play solo or to compete against each other in groups and one-on-one chats. The platform allows your bot to keep track of high scores for every game played in every chat. Whenever there’s a new leader in the game, other playing members in the chat are notified that they need to step it up.

-
- - -
-
-

Since the underlying technology is HTML5, the games can be anything from simple arcades and puzzles to multiplayer 3D-shooters and real-time strategy games. Our team has created a couple of simple demos for you to try out:

- -

You can also check out the @gamee bot that has more than 20 games.

-
-

Read more about the Gaming Platform »

-
-

Keyboards

-

Traditional chat bots can of course be taught to understand human language. But sometimes you want some more formal input from the user — and this is where custom keyboards can become extremely useful.

-

Whenever your bot sends a message, it can pass along a special keyboard with predefined reply options (see ReplyKeyboardMarkup). Telegram apps that receive the message will display your keyboard to the user. Tapping any of the buttons will immediately send the respective command. This way you can drastically simplify user interaction with your bot.

-

We currently support text and emoji for your buttons. Here are some custom keyboard examples:

-
-
- -
<a href="/file/811140880/1/jS-YSVkDCNQ/b397dfcefc6da0dc70" target="_blank"><img src="/file/811140880/1/jS-YSVkDCNQ/b397dfcefc6da0dc70" title="Keyboard for a calculator bot. Because you can." style="max-height: 300px; padding: 10px 5px" /></a>
-
-<a href="/file/811140733/2/KoysqJKQ_kI/a1ee46a377796c3961" target="_blank"><img src="/file/811140733/2/KoysqJKQ_kI/a1ee46a377796c3961" title="Keyboard for a trivia bot" style="max-height: 300px; padding: 10px 5px" /></a>
-
-
-

For more technical information on custom keyboards, please consult the Bot API manual (see sendMessage).

-
-

Inline keyboards and on-the-fly updating

-

There are times when you'd prefer to do things without sending any messages to the chat. For example, when your user is changing settings or flipping through search results. In such cases you can use Inline Keyboards that are integrated directly into the messages they belong to.

-

Unlike with custom reply keyboards, pressing buttons on inline keyboards doesn't result in messages sent to the chat. Instead, inline keyboards support buttons that work behind the scenes: callback buttons, URL buttons and switch to inline buttons.

-
- - - -
-
-

When callback buttons are used, your bot can update its existing messages (or just their keyboards) so that the chat remains tidy. Check out these sample bots to see inline keyboards in action: @music, @vote, @like.

-
-

Read more about inline keyboards and on-the-fly editing »

-
-

Commands

-

Commands present a more flexible way to communicate with your bot. The following syntax may be used:

-
/command
-

A command must always start with the '/' symbol and may not be longer than 32 characters. Commands can use latin letters, numbers and underscores. Here are a few examples:

-
/get_messages_stats
-/set_timer 10min Alarm!
-/get_timezone London, UK
-

Messages that start with a slash are always passed to the bot (along with replies to its messages and messages that @mention the bot by username). Telegram apps will:

-
    -
  • Suggest a list of supported commands with descriptions when the user enters a '/' (for this to work, you need to have provided a list of commands to the BotFather). Tapping on a command in the list immediately sends the command.
  • -
  • Show an additional (/) button in the input field in all chats with bots. Tapping it types a '/' and shows the list of commands.
  • -
  • Highlight /commands in messages. When the user taps a highlighted command, the command is sent at once.
  • -
-
- -
<a href="/file/811140315/2/gf7_D2HbeyM/e3ca2de4de7918f826" target="_blank"><img src="/file/811140315/2/gf7_D2HbeyM/e3ca2de4de7918f826" title="Notice the new button in the input field, right next to the sticker button" style="width: 230px; padding: 10px 5px" /></a>
-
-
-<a href="/file/811140029/1/s5zv4fbWdhw/a04aefa0ee0557f16a" target="_blank"><img src="/file/811140029/1/s5zv4fbWdhw/a04aefa0ee0557f16a" title="Suggested commands for multiple bots" style="width: 230px; padding: 10px 5px" /></a>
-
-

If multiple bots are in a group, it is possible to add bot usernames to commands in order to avoid confusion:

-
/start@TriviaBot
-/start@ApocalypseBot
-

This is done automatically when commands are selected via the list of suggestions. Please remember that your bot needs to be able to process commands that are followed by its username.

-
Global commands
-

In order to make it easier for users to navigate the bot multiverse, we ask all developers to support a few basic commands. Telegram apps will have interface shortcuts for these commands.

-
    -
  • /start - begins interaction with the user, e.g., by sending a greeting message. This command can also be used to pass additional parameters to the bot (see Deep linking)
  • -
  • /help - returns a help message. It can be a short text about what your bot can do and a list of commands.
  • -
  • /settings - (if applicable) returns the bot's settings for this user and suggests commands to edit these settings.
  • -
-

Users will see a Start button when they first open a conversation with your bot. Help and Settings links will be available in the menu on the bot's profile page.

-
- -
<a href="/file/811140479/2/1c2zUWhR7sA/98889b2a45f8e42a35" target="_blank"><img src="/file/811140479/2/1c2zUWhR7sA/98889b2a45f8e42a35" title="A bot's profile page, featuring 'Help' and 'Settings' buttons" style="width: 250px; padding: 10px 5px" /></a>
-
-

Formatting: bold, italic, fixed-width text and inline links

-

You can use bold, italic or fixed-width text, as well as inline links in your bots' messages. Telegram clients will render them accordingly.

-
-

Read more in the Bot API manual »

-
-

Privacy mode

-

Bots are frequently added to groups in order to augment communication between human users, e.g. by providing news, notifications from external services or additional search functionality. This is especially true for work-related groups. Now, when you share a group with a bot, you tend to ask yourself "How can I be sure that the little rascal isn't selling my chat history to my competitors?" The answer is — privacy mode.

-

A bot running in privacy mode will not receive all messages that people send to the group. Instead, it will only receive:

-
    -
  • Messages that start with a slash '/' (see Commands above)
  • -
  • Replies to the bot's own messages
  • -
  • Service messages (people added or removed from the group, etc.)
  • -
  • Messages from channels where it's a member
  • -
-

On one hand, this helps some of us sleep better at night (in our tinfoil nightcaps), on the other — it allows the bot developer to save a lot of resources, since they won't need to process tens of thousands irrelevant messages each day.

-

Privacy mode is enabled by default for all bots, except bots that were added to the group as admins (bot admins always receive all messages). It can be disabled, so that the bot receives all messages like an ordinary user (the bot will need to be re-added to the group for this change to take effect). We only recommend doing this in cases where it is absolutely necessary for your bot to work — users can always see a bot's current privacy setting in the group members list. In most cases, using the force reply option for the bot's messages should be more than enough.

-

So what messages exactly will my bot get? »

-

Deep linking

-

Telegram bots have a deep linking mechanism, that allows for passing additional parameters to the bot on startup. It could be a command that launches the bot — or an authentication token to connect the user's Telegram account to their account on some external service.

-

Each bot has a link that opens a conversation with it in Telegram — https://t.me/<bot username>. You can add the parameters start or startgroup to this link, with values up to 64 characters long. For example:

-
https://t.me/triviabot?startgroup=test
-

A-Z, a-z, 0-9, _ and - are allowed. We recommend using base64url to encode parameters with binary and other types of content.

-

Following a link with the start parameter will open a one-on-one conversation with the bot, showing a START button in the place of the input field. If the startgroup parameter is used, the user is prompted to select a group to add the bot to. As soon as a user confirms the action (presses the START button in their app or selects a group to add the bot to), your bot will receive a message from that user in this format:

-
/start PAYLOAD
-

PAYLOAD stands for the value of the start or startgroup parameter that was passed in the link.

-
Deep linking Example
-

Suppose the website example.com would like to send notifications to its users via a Telegram bot. Here's what they could do to enable notifications for a user with the ID 123.

-
    -
  1. Create a bot with a suitable username, e.g. @ExampleComBot
  2. -
  3. Set up a webhook for incoming messages
  4. -
  5. Generate a random string of a sufficient length, e.g. $memcache_key = "vCH1vGWJxfSeofSAs0K5PA"
  6. -
  7. Put the value 123 with the key $memcache_key into Memcache for 3600 seconds (one hour)
  8. -
  9. Show our user the button https://t.me/ExampleComBot?start=vCH1vGWJxfSeofSAs0K5PA
  10. -
  11. Configure the webhook processor to query Memcached with the parameter that is passed in incoming messages beginning with /start. If the key exists, record the chat_id passed to the webhook as telegram_chat_id for the user 123. Remove the key from Memcache.
  12. -
  13. Now when we want to send a notification to the user 123, check if they have the field telegram_chat_id. If yes, use the sendMessage method in the Bot API to send them a message in Telegram.
  14. -
-

Location and Number

-

Some bots need extra data from the user to work properly. For example, knowing the user's location helps provide more relevant geo-specific results. The user's phone number can be very useful for integrations with other services, like banks, etc.

-

Bots can ask a user for their location and phone number using special buttons. Note that both phone number and location request buttons will only work in private chats.

-
-
-
-

When these buttons are pressed, Telegram clients will display a confirmation alert that tells the user what's about to happen.

-
-

Manual: Number and location buttons »

-
-
-

6. BotFather

-
-

Jump to top to learn everything about Telegram bots »

-
-

BotFather is the one bot to rule them all. It will help you create new bots and change settings for existing ones.

-

Creating a new bot

-

Use the /newbot command to create a new bot. The BotFather will ask you for a name and username, then generate an authentication token for your new bot.

-

The name of your bot is displayed in contact details and elsewhere.

-

The Username is a short name, to be used in mentions and t.me links. Usernames are 5-32 characters long and are case insensitive, but may only include Latin characters, numbers, and underscores. Your bot's username must end in 'bot', e.g. 'tetris_bot' or 'TetrisBot'.

-

The token is a string along the lines of 110201543:AAHdqTcvCH1vGWJxfSeofSAs0K5PALDsaw that is required to authorize the bot and send requests to the Bot API. Keep your token secure and store it safely, it can be used by anyone to control your bot.

-

Generating an authentication token

-

If your existing token is compromised or you lost it for some reason, use the /token command to generate a new one.

-

Botfather commands

-

The remaining commands are pretty self-explanatory:

-
    -
  • /mybots — returns a list of your bots with handy controls to edit their settings
  • -
  • /mygames — does the same for your games
  • -
-

Edit bots

-
    -
  • /setname – change your bot's name.
  • -
  • /setdescription — change the bot's description, a short text of up to 512 characters, describing your bot. Users will see this text at the beginning of the conversation with the bot, titled 'What can this bot do?'.
  • -
  • /setabouttext — change the bot's about info, an even shorter text of up to 120 characters. Users will see this text on the bot's profile page. When they share your bot with someone, this text is sent together with the link.
  • -
  • /setuserpic — change the bot's profile pictures. It's always nice to put a face to a name.
  • -
  • /setcommands — change the list of commands supported by your bot. Users will see these commands as suggestions when they type / in the chat with your bot. Each command has a name (must start with a slash ‘/’, alphanumeric plus underscores, no more than 32 characters, case-insensitive), parameters, and a text description. Users will see the list of commands whenever they type '/' in a conversation with your bot.
  • -
  • /deletebot — delete your bot and free its username.
  • -
-

Edit settings

-
    -
  • /setinline — toggle inline mode for your bot.
  • -
  • /setinlinegeo - request location data to provide location-based inline results.
  • -
  • /setjoingroups — toggle whether your bot can be added to groups or not. Any bot must be able to process private messages, but if your bot was not designed to work in groups, you can disable this.
  • -
  • /setprivacy — set which messages your bot will receive when added to a group. With privacy mode disabled, the bot will receive all messages. We recommend leaving privacy mode enabled. You will need to re-add the bot to existing groups for this change to take effect.
  • -
-

Manage games

-
    -
  • /newgame — create a new game.
  • -
  • /listgames — get a list of your games.
  • -
  • /editgame — edit a game.
  • -
  • /deletegame — delete an existing game.
  • -
-
-

Please note, that it may take a few minutes for changes to take effect.

-
-

Status alerts

-

Millions choose Telegram for its speed. To stay competitive in this environment, your bot also needs to be responsive. In order to help developers keep their bots in shape, Botfather will send status alerts if it sees something is wrong.

-

We will be checking the number of replies and the request/response conversion rate for popular bots (~300 requests per minute: but don't write this down as the value may change in the future). If we get abnormally low readings, you will receive a notification from Botfather.

-
Responding to alerts
-

By default, you will only get one alert per bot per hour. Each alert has the following buttons:

-
    -
  • Fixed. Use this if you found an issue with your bot and fixed it. If you press the fix button, we will resume sending alerts in the regular way so that you can see if your fix worked within 5-10 minutes instead of having to wait for an hour.
  • -
  • Support. Use this to open a chat with @BotSupport if you don't see any issues with your bot or if you think the problem is on our side.
  • -
  • Mute for 8h/1w. Use this if you can't fix your bot at the moment. This will disable all alerts for the bot in question for the specified period of time. We do not recommend using this option since your users may migrate to a more stable bot. You can unmute alerts in your bot's settings via Botfather.
  • -
-
Monitored issues
-

We will currently notify you about the following issues:

-

1.

-
Too few **private messages** are sent compared to previous weeks: **{value}**
-

Your bot is sending much fewer messages than it did in the previous weeks. This is useful for newsletter-style bots that send out messages without prompts from the users. The larger the value, the more significant the difference.

-

2.

-
Too few replies to incoming **private messages**. Conversion rate: **{value}**
-

Your bot is not replying to all messages that are being sent to it (the request/response conversion rate for your bot was too low for at least two of the last three 5-minute periods). To provide a good user experience, please respond to all messages that are sent to your bot. Respond to message updates by calling send... methods (e.g. sendMessage).

-

3.

-
Too few answers to **inline queries**. Conversion rate: **{value}**
-

Your bot is not replying to all inline queries that are being sent to it, calculated in the same way as above. Respond to inline_query updates by calling answerInlineQuery.

-

4.

-
Too few answers to **callback queries**. Conversion rate: **{value}**
-Too few answers to **callback game queries**. Conversion rate: **{value}**
-

Your bot is not replying to all callback queries that are being sent to it (with or without games), calculated in the same way as above. Respond to callback_query updates by calling answerCallbackQuery.

-
-

Please note that the status alerts feature is still being tested and will be improved in the future.

-
-
-

That's it for the introduction. You are now definitely ready to proceed to the BOT API MANUAL.

-

If you've got any questions, please check out our Bot FAQ »

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/bots/2-0-intro.html b/data/corefork.telegram.org/bots/2-0-intro.html deleted file mode 100644 index 626344e3a0..0000000000 --- a/data/corefork.telegram.org/bots/2-0-intro.html +++ /dev/null @@ -1,230 +0,0 @@ - - - - - Introducing Bot API 2.0 - - - - - - - - - - - - - -
- -
-
-
-
-

Introducing Bot API 2.0

- -
- -
-

Howdy! This text assumes that you‘re familiar with Telegram’s bot platform.
If this is not the case, kindly check out our Introduction to Bots.

-
-

Today we‘re introducing the biggest change to Telegram’s Bot Platform since June 2015. These new tools will help you create fluid and intuitive interfaces for your bots. And bots are becoming a lot more capable. They can now send any type of content supported on Telegram, provide location-based services and integrate with other services deeply based on users' phone numbers.

-

If you'd like a more concise changelog, you can find one in the Bot API Manual.

-

New Inline Keyboards

-

To begin with, we're adding a new type of keyboard that is integrated directly into the message it belongs to. Inline keyboards are available for messages sent both in chat mode and inline mode.

-
- - - -

- - - -
- -

Unlike with custom reply keyboards, pressing buttons on inline keyboards doesn't result in messages sent to the chat. Instead, inline keyboards support buttons that work behind the scenes: callback buttons, URL buttons and switch to inline buttons.

-
-

Manual: Inline keyboards »

-
-

Callback buttons

-

When a user presses a callback button, no messages are sent to the chat. Instead, your bot simply receives the relevant query. Upon receiving the query, your bot can display some result in a notification at the top of the chat screen or in an alert.

-
-

-
- -

Sample bot
@music – This sample music bot uses inline callback buttons to flip pages and reload random results.

-

Read on to updating messages to find out how callback buttons can get even cooler.

-

URL buttons

-

Buttons of this type have a small arrow icon to help the user understand that tapping on a URL button will open an external link. Naturally, we'll show them a confirmation alert before opening the link in the browser.

-
-
-
- -

Switch to Inline buttons

-

Pressing a switch to inline button prompts the user to select a chat, opens it and inserts the bot's username into the input field. You can also pass a query that will be inserted along with the username – this way your users will immediately get some inline results they can share.

-
-

-
- -

Sample bot
@sticker – This sticker search bot offers a ‘switch to inline’ button to teach users how to use it in inline mode.

-

Updating Messages

-

Since inline keyboards don‘t send additional messages to the chat, it made sense to give bots a way of manipulating their existing messages, so that they don’t have to send a new message each time they need to update something. This helps reduce clutter and build more fluid interfaces.

-
-
- -
-
- -

Sample bot
@music – Watch how the music bot updates its messages with search results when you press the navigation buttons.

-
-

Manual: Updating messages »

-
-

Locations and Numbers

-

Some bots need extra data from the user to work properly. For example, knowing the user‘s location helps provide more relevant geo-specific results. The user’s phone number can be very useful for integrations with other services, like banks, etc.

-

We've added an easy way for bots to ask the user for their location and phone number using special buttons. Note that both phone number and location request buttons will only work in private chats.

-
-

-
- -

When these buttons are pressed, Telegram clients will display a confirmation alert that tells the user what's about to happen.

-
-

Manual: Number and location buttons »

-
-

Inline bots can also request location data from their users. Use the /setinlinegeo command with @BotFather to enable this. Your bot will ask the user for permission to access their location whenever they send an inline request.

-

Sample bot
@foursquare – This bot will ask for permission to access the user's location, then provide geo-targeted results.

-

Inline Bots 2.0

-

Speaking of inline bots, they are also getting a major upgrade today.

-

New types of content

-

Inline bots now support all types of content available in Telegram (19 in all), they are now capable of sending stickers, videos, music, locations, documents and more.

-
-

-
- -

Sample bots
@sticker – This sticker bot will accept one or more emoji and search for relevant stickers.
@music – The music bot allows users to send mp3 tracks from a database of public domain classical music.

-
-

Manual: Types of inline content »

-
-

Switching between inline mode and private chat

-

Some inline bots can benefit from an initial setup process, like connecting them to an account on an external service (e.g., YouTube). We've added an easy way of switching between the private chat with a bot and whatever chat the user wants to share inline results in.

-
-

-
- -

You can now display a special ‘Switch to PM’ button above the inline results (or instead of them). This button will open a private chat with the bot and pass a parameter of your choosing, so that you can prompt the user for the relevant setup actions. Once done, you can use an inline keyboard with a switch_inline_query button to send the user back to the original chat.

-

Sample bots
@youtube – Shows a ‘Sign in to YouTube’ button, then suggests personalized results.

-
-

Manual: Switch to PM

-
-

Better inline UI

-

Since sending content via inline bots works differently from sending ordinary messages, we‘ve changed the interface a little. There’s hardly a more effective way of explaining that there‘s no need to hit ’Send':

-
-

-
- -

Tapping on the cross icon once will clear the query, tapping twice will give the ‘Send’ button back to the user.

-

Group Admins

-

As a dessert, we‘re beginning to roll out tools that will allow you to create bot solutions for group admins. As the first step, we’ve added methods to remove members from groups and supergroups.

-
-

Manual: Group management »

-
-

And that's about it for now. Stay tuned for more updates and subscribe to our official @Botnews channel on Telegram.

-
-

Read the full changelog for this update »

-
-
- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/bots/api-changelog.html b/data/corefork.telegram.org/bots/api-changelog.html deleted file mode 100644 index 1a3bf096bd..0000000000 --- a/data/corefork.telegram.org/bots/api-changelog.html +++ /dev/null @@ -1,670 +0,0 @@ - - - - - Bot API changelog - - - - - - - - - - - - - -
- -
-
-
-
-

Bot API changelog

- -
- -
-

The Bot API is an HTTP-based interface created for developers keen on building bots for Telegram.
To learn how to create and set up a bot, please consult our Introduction to Bots »

-
-

You will find all changes to our Bot API on this page.

-

Recent changes

-
-

Subscribe to @BotNews to be the first to know about the latest updates and join the discussion in @BotTalk

-
-

January 31, 2022

-

Bot API 5.7

- -

December 30, 2021

-

Bot API 5.6

- -

December 7, 2021

-

Bot API 5.5

-
    -
  • Bots are now allowed to contact users who sent a join request to a chat where the bot is an administrator with the can_invite_users administrator right – even if the user never interacted with the bot before.
  • -
  • Added support for mentioning users by their ID in inline keyboards. This will only work in Telegram versions released after December 7, 2021. Older clients will display unsupported message.
  • -
  • Added the methods banChatSenderChat and unbanChatSenderChat for banning and unbanning channel chats in supergroups and channels.
  • -
  • Added the field has_private_forwards to the class Chat for private chats, which can be used to check the possibility of mentioning the user by their ID.
  • -
  • Added the field has_protected_content to the classes Chat and Message.
  • -
  • Added the field is_automatic_forward to the class Message.
  • -
-

Note: After this update it will become impossible to forward messages from some chats. Use the fields has_protected_content in the classes Message and Chat to check this.

-

Note: After this update users are able to send messages on behalf of channels they own. Bots are expected to use the field sender_chat in the class Message to correctly support such messages.

-

Note: As previously announced, user identifiers can now have up to 52 significant bits and require a 64-bit integer or double-precision float type to be stored safely.

-

November 5, 2021

-

Bot API 5.4

- -
-
-

⚠️ WARNING! ⚠️
User identifiers will become bigger than 2^31 - 1 before the end of this year and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

-
-
-

June 25, 2021

-

Bot API 5.3

-

Personalized Commands

-
    -
  • Bots can now show lists of commands tailored to specific situations - including localized commands for users with different languages, as well as different commands based on chat type or for specific chats, and special lists of commands for chat admins.
  • -
  • Added the class BotCommandScope, describing the scope to which bot commands apply.
  • -
  • Added the parameters scope and language_code to the method setMyCommands to allow bots specify different commands for different chats and users.
  • -
  • Added the parameters scope and language_code to the method getMyCommands.
  • -
  • Added the method deleteMyCommands to allow deletion of the bot's commands for the given scope and user language.
  • -
  • Improved visibility of bot commands in Telegram apps with the new 'Menu' button in chats with bots, read more on the blog.
  • -
-

Custom Placeholders

- -

And More

-
    -
  • Improved documentation of the class ChatMember by splitting it into 6 subclasses.
  • -
  • Renamed the method kickChatMember to banChatMember. The old method name can still be used.
  • -
  • Renamed the method getChatMembersCount to getChatMemberCount. The old method name can still be used.
  • -
  • Values of the field file_unique_id in objects of the type PhotoSize and of the fields small_file_unique_id and big_file_unique_id in objects of the type ChatPhoto were changed.
  • -
-
-
-

⚠️ WARNING! ⚠️
After one of the upcoming Bot API updates, user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

-
-
-

April 26, 2021

-

Bot API 5.2

-
    -
  • Support for Payments 2.0, see this manual for more details about the Bot Payments API.
  • -
  • Added the type InputInvoiceMessageContent to support sending invoices as inline query results.
  • -
  • Allowed sending invoices to group, supergroup and channel chats.
  • -
  • Added the fields max_tip_amount and suggested_tip_amounts to the method sendInvoice to allow adding optional tips to the payment.
  • -
  • The parameter start_parameter of the method sendInvoice became optional. If the parameter isn't specified, the invoice can be paid directly from forwarded messages.
  • -
  • Added the field chat_type to the class InlineQuery, containing the type of the chat, from which the inline request was sent.
  • -
  • Added the type VoiceChatScheduled and the field voice_chat_scheduled to the class Message.
  • -
  • Fixed an error in sendChatAction documentation to correctly mention “record_voice” and “upload_voice” instead of “record_audio” and “upload_audio” for related to voice note actions. Old action names will still work for backward compatibility.
  • -
-
-
-

⚠️ WARNING! ⚠️
After the next Bot API update (Bot API 5.3) there will be a one-time change of the value of the field file_unique_id in objects of the type PhotoSize and of the fields small_file_unique_id and big_file_unique_id in objects of the type ChatPhoto.

-
-
-
-

⚠️ WARNING! ⚠️
Service messages about non-bot users joining the chat will be soon removed from large groups. We recommend using the “chat_member” update as a replacement.

-
-
-
-

⚠️ WARNING! ⚠️
After one of the upcoming Bot API updates, user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

-
-
-

March 9, 2021

-

Bot API 5.1

-

Added two new update types

-
    -
  • Added updates about member status changes in chats, represented by the class ChatMemberUpdated and the fields my_chat_member and chat_member in the Update class. The bot must be an administrator in the chat to receive chat_member updates about other chat members. By default, only my_chat_member updates about the bot itself are received.
  • -
-

Improved Invite Links

-
    -
  • Added the class ChatInviteLink, representing an invite link to a chat.
  • -
  • Added the method createChatInviteLink, which can be used to create new invite links in addition to the primary invite link.
  • -
  • Added the method editChatInviteLink, which can be used to edit non-primary invite links created by the bot.
  • -
  • Added the method revokeChatInviteLink, which can be used to revoke invite links created by the bot.
  • -
-

Voice Chat Info

- -

And More

-
    -
  • Added the type MessageAutoDeleteTimerChanged and the field message_auto_delete_timer_changed to the class Message.
  • -
  • Added the parameter revoke_messages to the method kickChatMember, allowing to delete all messages from a group for the user who is being removed.
  • -
  • Added the new administrator privilege can_manage_chat to the class ChatMember and parameter can_manage_chat to the method promoteChatMember. This administrator right is implied by any other administrator privilege.
  • -
  • Supported the new bowling animation for the random dice. Choose between different animations (dice, darts, basketball, football, bowling, slot machine) by specifying the emoji parameter in the method sendDice.
  • -
-
-
-

⚠️ WARNING! ⚠️
After one of the upcoming Bot API updates, some user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

-
-
-

November 4, 2020

-

Introducing Bot API 5.0

-

Run Your Own Bot API Server

-
    -
  • Bot API source code is now available at telegram-bot-api. You can now run your own Bot API server locally, boosting your bots' performance.
  • -
  • Added the method logOut, which can be used to log out from the cloud Bot API server before launching your bot locally. You must log out the bot before running it locally, otherwise there is no guarantee that the bot will receive all updates.
  • -
  • Added the method close, which can be used to close the bot instance before moving it from one local server to another.
  • -
-

Transfer Bot Ownership

-
    -
  • You can now use @BotFather to transfer your existing bots to another Telegram account.
  • -
-

Webhooks

-
    -
  • Added the parameter ip_address to the method setWebhook, allowing to bypass DNS resolving and use the specified fixed IP address to send webhook requests.
  • -
  • Added the field ip_address to the class WebhookInfo, containing the current IP address used for webhook connections creation.
  • -
  • Added the ability to drop all pending updates when changing webhook URL using the parameter drop_pending_updates in the methods setWebhook and deleteWebhook.
  • -
-

Working with Groups

-
    -
  • The getChat request now returns the user's bio for private chats if available.
  • -
  • The getChat request now returns the identifier of the linked chat for supergroups and channels, i.e. the discussion group identifier for a channel and vice versa.
  • -
  • The getChat request now returns the location to which the supergroup is connected (see Local Groups). Added the class ChatLocation to represent the location.
  • -
  • Added the parameter only_if_banned to the method unbanChatMember to allow safe unban.
  • -
-

Working with Files

-
    -
  • Added the field file_name to the classes Audio and Video, containing the name of the original file.
  • -
  • Added the ability to disable server-side file content type detection using the parameter disable_content_type_detection in the method sendDocument and the class inputMediaDocument.
  • -
-

Multiple Pinned Messages

-
    -
  • Added the ability to pin messages in private chats.
  • -
  • Added the parameter message_id to the method unpinChatMessage to allow unpinning of the specific pinned message.
  • -
  • Added the method unpinAllChatMessages, which can be used to unpin all pinned messages in a chat.
  • -
-

File Albums

-
    -
  • Added support for sending and receiving audio and document albums in the method sendMediaGroup.
  • -
-

Live Locations

- -

Anonymous Admins

-
    -
  • Added the field sender_chat to the class Message, containing the sender of a message which is a chat (group or channel). For backward compatibility in non-channel chats, the field from in such messages will contain the user 777000 for messages automatically forwarded to the discussion group and the user 1087968824 (@GroupAnonymousBot) for messages from anonymous group administrators.
  • -
  • Added the field is_anonymous to the class chatMember, which can be used to distinguish anonymous chat administrators.
  • -
  • Added the parameter is_anonymous to the method promoteChatMember, which allows to promote anonymous chat administrators. The bot itself should have the is_anonymous right to do this. Despite the fact that bots can have the is_anonymous right, they will never appear as anonymous in the chat. Bots can use the right only for passing to other administrators.
  • -
  • Added the custom title of an anonymous message sender to the class Message as author_signature.
  • -
-

And More

- -

And Last but not Least

-
    -
  • Supported the new football and slot machine animations for the random dice. Choose between different animations (dice, darts, basketball, football, slot machine) by specifying the emoji parameter in the method sendDice.
  • -
-

June 4, 2020

-

Bot API 4.9

-
    -
  • Added the new field via_bot to the Message object. You can now know which bot was used to send a message.
  • -
  • Supported video thumbnails for inline GIF and MPEG4 animations.
  • -
  • Supported the new basketball animation for the random dice. Choose between different animations (dice, darts, basketball) by specifying the emoji parameter in the method sendDice.
  • -
-

April 24, 2020

-

Bot API 4.8

-
    -
  • Supported explanations for Quizzes 2.0. Add explanations by specifying the parameters explanation and explanation_parse_mode in the method sendPoll.
  • -
  • Added the fields explanation and explanation_entities to the Poll object.
  • -
  • Supported timed polls that automatically close at a certain date and time. Set up by specifying the parameter open_period or close_date in the method sendPoll.
  • -
  • Added the fields open_period and close_date to the Poll object.
  • -
  • Supported the new darts animation for the dice mini-game. Choose between the default dice animation and darts animation by specifying the parameter emoji in the method sendDice.
  • -
  • Added the field emoji to the Dice object.
  • -
-

March 30, 2020

-

Bot API 4.7

-
    -
  • Added the method sendDice for sending a dice message, which will have a random value from 1 to 6. (Yes, we're aware of the “proper” singular of die. But it's awkward, and we decided to help it change. One dice at a time!)
  • -
  • Added the field dice to the Message object.
  • -
  • Added the method getMyCommands for getting the current list of the bot's commands.
  • -
  • Added the method setMyCommands for changing the list of the bot's commands through the Bot API instead of @BotFather.
  • -
  • Added the ability to create animated sticker sets by specifying the parameter tgs_sticker instead of png_sticker in the method createNewStickerSet.
  • -
  • Added the ability to add animated stickers to sets created by the bot by specifying the parameter tgs_sticker instead of png_sticker in the method addStickerToSet.
  • -
  • Added the field thumb to the StickerSet object.
  • -
  • Added the ability to change thumbnails of sticker sets created by the bot using the method setStickerSetThumb.
  • -
-

January 23, 2020

-

Bot API 4.6

-
    -
  • Supported Polls 2.0.
  • -
  • Added the ability to send non-anonymous, multiple answer, and quiz-style polls: added the parameters is_anonymous, type, allows_multiple_answers, correct_option_id, is_closed options to the method sendPoll.
  • -
  • Added the object KeyboardButtonPollType and the field request_poll to the object KeyboardButton.
  • -
  • Added updates about changes of user answers in non-anonymous polls, represented by the object PollAnswer and the field poll_answer in the Update object.
  • -
  • Added the fields total_voter_count, is_anonymous, type, allows_multiple_answers, correct_option_id to the Poll object.
  • -
  • Bots can now send polls to private chats.
  • -
  • Added more information about the bot in response to the getMe request: added the fields can_join_groups, can_read_all_group_messages and supports_inline_queries to the User object.
  • -
  • Added the optional field language to the MessageEntity object.
  • -
-

December 31, 2019

-

Bot API 4.5

-
    -
  • Added support for two new MessageEntity types, underline and strikethrough.
  • -
  • Added support for nested MessageEntity objects. Entities can now contain other entities. If two entities have common characters then one of them is fully contained inside the other.
  • -
  • Added support for nested entities and the new tags <u>/<ins> (for underlined text) and <s>/<strike>/<del> (for strikethrough text) in parse mode HTML.
  • -
  • Added a new parse mode, MarkdownV2, which supports nested entities and two new entities __ (for underlined text) and ~ (for strikethrough text). Parse mode Markdown remains unchanged for backward compatibility.
  • -
  • Added the field file_unique_id to the objects Animation, Audio, Document, PassportFile, PhotoSize, Sticker, Video, VideoNote, Voice, File and the fields small_file_unique_id and big_file_unique_id to the object ChatPhoto. The new fields contain a unique file identifier, which is supposed to be the same over time and for different bots, but can't be used to download or reuse the file.
  • -
  • Added the field custom_title to the ChatMember object.
  • -
  • Added the new method setChatAdministratorCustomTitle to manage the custom titles of administrators promoted by the bot.
  • -
  • Added the field slow_mode_delay to the Chat object.
  • -
-

July 29, 2019

-

Bot API 4.4

-
    -
  • Added support for animated stickers. New field is_animated in Sticker and StickerSet objects, animated stickers can now be used in sendSticker and InlineQueryResultCachedSticker.
  • -
  • Added support for default permissions in groups. New object ChatPermissions, containing actions which a member can take in a chat. New field permissions in the Chat object; new method setChatPermissions.
  • -
  • The field all_members_are_administrators has been removed from the documentation for the Chat object. The field is still returned in the object for backward compatibility, but new bots should use the permissions field instead.
  • -
  • Added support for more permissions for group and supergroup members: added the new field can_send_polls to ChatMember object, added can_change_info, can_invite_users, can_pin_messages in ChatMember object for restricted users (previously available only for administrators).
  • -
  • The method restrictChatMember now takes the new user permissions in a single argument of the type ChatPermissions. The old way of passing parameters will keep working for a while for backward compatibility.
  • -
  • Added description support for basic groups (previously available in supergroups and channel chats). You can pass a group's chat_id to setChatDescription and receive the group's description in the Chat object in the response to getChat method.
  • -
  • Added invite_link support for basic groups (previously available in supergroups and channel chats). You can pass a group's chat_id to exportChatInviteLink and receive the group's invite link in the Chat object in the response to getChat method.
  • -
  • File identifiers from the ChatPhoto object are now invalidated and can no longer be used whenever the photo is changed.
  • -
  • All webhook requests from the Bot API are now coming from the subnets 149.154.160.0/20 and 91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.
  • -
  • As of the next Bot API update (version 4.5), nested MessageEntity objects will be allowed in message texts and captions. Please make sure that your code can correctly handle such entities.
  • -
-

May 31, 2019

-

Bot API 4.3

-
    -
  • Added support for Seamless Telegram Login on external websites.
  • -
  • Added the new object LoginUrl and the new field login_url to the InlineKeyboardButton object which allows to automatically authorize users before they go to a URL specified by the bot. Users will be asked to confirm authorization in their Telegram app (needs version 5.7 or higher) when they press the button:
  • -
-
- TITLE -
- -

Also in this update:

-
    -
  • Added the field reply_markup to the Message object, containing the inline keyboard attached to the message.
  • -
  • If a message with an inline keyboard is forwarded, the forwarded message will now have an inline keyboard if the keyboard contained only url and login_url buttons or if the message was sent via a bot and the keyboard contained only url, login_url, switch_inline_query or switch_inline_query_current_chat buttons. In the latter case, switch_inline_query_current_chat buttons are replaced with switch_inline_query buttons.
  • -
  • Bots now receive the edited_message Update even if only Message.reply_markup has changed.
  • -
  • Bots that have the can_edit_messages right in a channel can now use the method editMessageReplyMarkup for messages written by other administrators forever without the 48 hours limit.
  • -
  • Don't forget that starting in July 2019, webhook requests from Bot API will be coming from the subnets 149.154.160.0/20 and 91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.
  • -
-

April 14, 2019

-

Bot API 4.2

-
    -
  • Added support for native polls: added the object Poll, the methods sendPoll and stopPoll and the field poll in the Message and Update objects.
  • -
  • The method deleteMessage can now be used to delete messages sent by a user to the bot in private chats within 48 hours.
  • -
  • Added support for pinned messages in basic groups in addition to supergroups and channel chats: you can pass group's chat_id to pinChatMessage and unpinChatMessage, and receive the pinned group message in Chat object.
  • -
  • Added the field is_member to the ChatMember object, which can be used to find whether a restricted user is a member of the chat.
  • -
  • Added the field forward_sender_name to the Message object, containing name of the sender who has opted to hide their account.
  • -
  • Starting in July 2019, webhook requests from Bot API will be coming from the subnets 149.154.160.0/20 and 91.108.4.0/22. Most users won't need to do anything to continue receiving webhooks. If you control inbound access with a firewall, you may need to update your configuration. You can always find the list of actual IP addresses of servers used to send webhooks there: https://core.telegram.org/bots/webhooks.
  • -
  • Document thumbnails now should be inscribed in a 320x320 square instead of 90x90.
  • -
-

August 27, 2018

-

Bot API 4.1

- -

July 26, 2018

-

Bot API 4.0.

-
    -
  • Added support for Telegram Passport. See the official announcement on the blog and the manual for details.
  • -
  • Added support for editing the media content of messages: added the method editMessageMedia and new types InputMediaAnimation, InputMediaAudio, and InputMediaDocument.
  • -
  • Added the field thumb to the Audio object to contain the thumbnail of the album cover to which the music file belongs.
  • -
  • Added support for attaching custom thumbnails to uploaded files. For animations, audios, videos and video notes, which are less than 10 MB in size, thumbnails are generated automatically.
  • -
  • tg:// URLs now can be used in inline keyboard url buttons and text_link message entities.
  • -
  • Added the method sendAnimation, which can be used instead of sendDocument to send animations, specifying their duration, width and height.
  • -
  • Added the field animation to the Message object. For backward compatibility, when this field is set, the document field will be also set.
  • -
  • Added two new MessageEntity types: cashtag and phone_number.
  • -
  • Added support for Foursquare venues: added the new field foursquare_type to the objects Venue, InlineQueryResultVenue and InputVenueMessageContent, and the parameter foursquare_type to the sendVenue method.
  • -
  • You can now create inline mentions of users, who have pressed your bot's callback buttons.
  • -
  • You can now use the Retry-After response header to configure the delay after which the Bot API will retry the request after an unsuccessful response from a webhook.
  • -
  • If a webhook returns the HTTP error 410 Gone for all requests for more than 23 hours successively, it can be automatically removed.
  • -
  • Added vCard support when sharing contacts: added the field vcard to the objects Contact, InlineQueryResultContact, InputContactMessageContent and the method sendContact.
  • -
-

February 13, 2018

-

Bot API 3.6.

-
    -
  • Supported text formatting in media captions. Specify the desired parse_mode (Markdown or HTML) when you provide a caption.
  • -
  • In supergroups, if the bot receives a message that is a reply, it will also receive the message to which that message is replying – even if the original message is inaccessible due to the bot's privacy settings. (In other words, replying to any message in a supergroup with a message that mentions the bot or features a command for it acts as forwarding the original message to the bot).
  • -
  • Added the new field connected_website to Message. The bot will receive a message with this field in a private chat when a user logs in on the bot's connected website using the Login Widget and allows sending messages from your bot.
  • -
  • Added the new parameter supports_streaming to the sendVideo method and a field with the same name to the InputMediaVideo object.
  • -
-

November 17, 2017

-

Bot API 3.5.

- -

October 11, 2017

-

Bot API 3.4.

- -

August 23, 2017

-

Bot API 3.3.

-
    -
  • Bots can now mention users via inline mentions, without using usernames.
  • -
  • getChat now also returns pinned messages in supergroups, if present. Added the new field pinned_message to the Chat object.
  • -
  • Added the new fields author_signature and forward_signature to the Message object.
  • -
  • Added the new field is_bot to the User object.
  • -
-

July 21, 2017

-

Bot API 3.2. Teach your bot to handle stickers and sticker sets.

- -

June 30, 2017

-

Bot API 3.1. Build your own robotic police force for supergoups with these new methods for admin bots:

- -

May 18, 2017

-

Introducing Bot API 3.0.

-

NEW Payment Platform

-

See Introduction to Bot Payments for a brief overview. If you're not a developer, you may like this user-friendly blog post better.

- -

NEW Video Messages

-
    -
  • As of Telegram v.4.0, users can send short rounded video messages, using an interface similar to that of voice notes.
  • -
  • Added the sendVideoNote method, the new field video_note to Message, the fields record_video_note or upload_video_note to sendChatAction.
  • -
-

NEW Multilingual Bots

-
    -
  • The User object now may have a language_code field that contains the IETF language tag of the user's language.
  • -
  • Thanks to this, your bot can now offer localized responses to users that speak different languages.
  • -
-

More power to admin bots

-
    -
  • unbanChatMemeber now also works in channels!
  • -
  • New method deleteMessage that allows the bot to delete its own messages, as well as messages posted by other in groups and channels where the bot is an administrator.
  • -
-

Minor Changes

-
    -
  • Replaced the field new_chat_member in Message with new_chat_members (the old field will still be available for a while for compatibility purposes).
  • -
  • Inline keyboards with switch_inline_query and switch_inline_query_current_chat can no longer be sent to channels because they are useless there.
  • -
  • New fields gif_duration in InlineQueryResultGif and mpeg4_duration in InlineQueryResultMpeg4Gif.
  • -
-

December 4, 2016

-

Introducing Bot API 2.3.1, a nifty little update that will give you more control over how your bot gets its updates.

-
    -
  • Use the new field max_connections in setWebhook to optimize your bot's server load
  • -
  • Use allowed_updates in setWebhook and getUpdates to selectively subscribe to updates of a certain type. Among other things, this allows you to stop getting updates about new posts in channels where your bot is an admin.
  • -
  • deleteWebhook moved out of setWebhook to get a whole separate method for itself.
  • -
-

November 21, 2016

-

Bot API 2.3

-
    -
  • Modified bot privacy mode for the sake of consistency.
  • -
  • Your bot can now get updates about posts in channels. Added new fields channel_post and edited_channel_post to Update.

    -
  • -
  • You can now update high scores to a lower value by using the new force parameter in setGameScore. Handy for punishing cheaters or fixing errors in your game's High Score table.

    -
  • -
  • Starting today, messages with high scores will be updated with new high scores by default. Use disable_edit_message in setGameScore if you don't want this.
  • -
  • The edit_message parameter from setGameScore is no longer in use. For backward compatibility, it will be taken into account for a while, unless disable_edit_message is passed explicitly.
  • -
  • Added the new field forward_from_message_id to Message.
  • -
  • Added the new parameter cache_time to answerCallbackQuery. Will eventually work in Telegram apps — somewhere after version 3.14, maybe 3.15.
  • -
  • Renamed hide_keyboard to remove_keyboard in ReplyKeyboardRemove for clarity. hide_keyboard will still work for a while for backward compatibility.
  • -
-

October 3, 2016

-

Bot API 2.2. Introducing a new Gaming Platform! See this introduction for a brief overview.
If you're not a developer, you may like this user-friendly blog post better.

- -

Other changes

- -
    -
  • New field all_members_are_administrators in the Chat object.
  • -
  • Certain server responses may now contain the new parameters field with expanded info on errors that occurred while processing your requests.
  • -
-

May 25, 2016

- -

May 22, 2016

- -

May 12, 2016

- -

May 6, 2016

-
    -
  • Added the field emoji to the Sticker object. Your bot can now know the emoji a sticker corresponds to.
  • -
  • Added the field forward_from_chat to the Message object for messages forwarded from channels.
  • -
-

April 9, 2016

-

Introducing Bot API 2.0. Check out this page for a review of this major update.

- -

Inline bots

-
    -
  • Added support for all content types available on Telegram. 19 types of InlineQueryResult objects are now supported.
  • -
  • Inline bots can now substitute all kinds of content with text. Added 4 types of InputMessageContent objects.
  • -
  • Your inline bot can also ask users for permission to use their location. Added the new Botfather command /setinlinegeo, added field location to the InlineQuery object, added fields location and inline_message_id to the ChosenInlineResult object.
  • -
  • Added an easy way to switch between inline mode and a private chat with the bot – useful for settings, establishing external connections and teaching users how to use your bot in inline mode. Added parameters switch_pm_text and switch_pm_parameter to the method answerInlineQuery.
  • -
-

Miscellaneous

- -

February 20, 2016

-
    -
  • Added the disable_notification parameter to all methods that send messages or any kind.
  • -
  • Removed backward compatibility from the method sendAudio. Voice messages now must be sent using the method sendVoice. There is no more need to specify a non-empty title or performer while sending the audio by file_id.
  • -
-

January 20, 2016

-
    -
  • By the way, you can use both HTML-style and markdown-style formatting in your bot's messages to send bold, italic or fixed-width text and inline links. All official Telegram clients support this. See Formatting options for details.
  • -
-

January 14, 2016

-
    -
  • You can now collect feedback on which results provided by your inline bot get chosen by the users. Added the setinlinefeedback command for Botfather, new type ChosenInlineResult, new field chosen_inline_result to the Update object.
  • -
-

January 4, 2016

- -

November, 2015

-
    -
  • Added support for supergroups. The Type field in the Chat object can now contain 'supergroup'.
  • -
  • New optional fields added to the Message object: supergroup_chat_created, migrate_to_chat_id, migrate_from_chat_id and channel_chat_created.
  • -
-

October 8, 2015

-
    -
  • Added initial channel support for bots (no Telegram clients support this at the moment, please wait for updates):
  • -
  • The Chat field in the Message is now of the new type Chat.
  • -
  • You can now pass a channel username (in the format @channelusername) in the place of chat_id in all methods (and instead of from_chat_id in forwardMessage). For this to work, the bot must be an administrator in the channel (and that's exactly what Telegram clients don't support yet — adding bots as administrators coming soon).
  • -
-

September 18, 2015

-
    -
  • Bots can now download files and media sent by users.
  • -
  • Added getFile and File.
  • -
-

September 7, 2015

-
    -
  • You can now pass parameters using application/json (please note that this doesn't work for file uploads: use multipart/form-data to upload files).
  • -
  • Added very basic markdown support. New field parse_mode added to sendMessage. For the moment messages with markdown will be displayed correctly only in Telegram for Android. Other official apps will catch up soon.
  • -
-

August 29, 2015

-
    -
  • Added support for self-signed certificates: upload your certificate using the certificate parameter in the setWebhook method.
  • -
  • You can now make new requests when responding to webhook updates.
  • -
-

August 15, 2015

-
    -
  • Added new type Voice and new method sendVoice for sending voice messages.
  • -
  • Earlier Audio and sendAudio should now be used for sending music files. Telegram clients will show such files in the in-app music player. If you were using sendAudio for your bot to send voice messages, please use sendVoice instead.
  • -
  • Added optional fields performer, title to the Audio object and sendAudio method.
  • -
  • Added optional field voice to the Message object.
  • -
-

July 2015

-
    -
  • The thumb field is now optional for Video, Sticker and Document objects
  • -
  • The API now supports both video and photo captions. The caption field has been removed from the Video object and added to the Message object instead.
  • -
  • caption and duration optional fields have been added to the sendVideo method.
  • -
  • Fixed typo: user_id in the Contact object is now correctly labeled as Integer, not String
  • -
-

June 24, 2015

-

The bot platform was officially launched.

-
-

Back to the Bot API Manual »

-
-
- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/bots/api.html b/data/corefork.telegram.org/bots/api.html deleted file mode 100644 index a01ae0c040..0000000000 --- a/data/corefork.telegram.org/bots/api.html +++ /dev/null @@ -1,9288 +0,0 @@ - - - - - Telegram Bot API - - - - - - - - - - - - - -
- -
-
-
- -

Telegram Bot API

- -
- -
-

The Bot API is an HTTP-based interface created for developers keen on building bots for Telegram. -To learn how to create and set up a bot, please consult our Introduction to Bots and Bot FAQ.

-
-

Recent changes

-
-

Subscribe to @BotNews to be the first to know about the latest updates and join the discussion in @BotTalk

-
-

June 25, 2021

-

Bot API 5.3

-

Personalized Commands

-
    -
  • Bots can now show lists of commands tailored to specific situations - including localized commands for users with different languages, as well as different commands based on chat type or for specific chats, and special lists of commands for chat admins.
  • -
  • Added the class BotCommandScope, describing the scope to which bot commands apply.
  • -
  • Added the parameters scope and language_code to the method setMyCommands to allow bots specify different commands for different chats and users.
  • -
  • Added the parameters scope and language_code to the method getMyCommands.
  • -
  • Added the method deleteMyCommands to allow deletion of the bot's commands for the given scope and user language.
  • -
  • Improved visibility of bot commands in Telegram apps with the new 'Menu' button in chats with bots, read more on the blog.
  • -
-

Custom Placeholders

- -

And More

-
    -
  • Improved documentation of the class ChatMember by splitting it into 6 subclasses.
  • -
  • Renamed the method kickChatMember to banChatMember. The old method name can still be used.
  • -
  • Renamed the method getChatMembersCount to getChatMemberCount. The old method name can still be used.
  • -
  • Values of the field file_unique_id in objects of the type PhotoSize and of the fields small_file_unique_id and big_file_unique_id in objects of the type ChatPhoto were changed.
  • -
-
-
-

⚠️ WARNING! ⚠️ -After one of the upcoming Bot API updates, user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

-
-
-

April 26, 2021

-

Bot API 5.2

-
    -
  • Support for Payments 2.0, see this manual for more details about the Bot Payments API.
  • -
  • Added the type InputInvoiceMessageContent to support sending invoices as inline query results.
  • -
  • Allowed sending invoices to group, supergroup and channel chats.
  • -
  • Added the fields max_tip_amount and suggested_tip_amounts to the method sendInvoice to allow adding optional tips to the payment.
  • -
  • The parameter start_parameter of the method sendInvoice became optional. If the parameter isn't specified, the invoice can be paid directly from forwarded messages.
  • -
  • Added the field chat_type to the class InlineQuery, containing the type of the chat, from which the inline request was sent.
  • -
  • Added the type VoiceChatScheduled and the field voice_chat_scheduled to the class Message.
  • -
  • Fixed an error in sendChatAction documentation to correctly mention "record_voice" and "upload_voice" instead of "record_audio" and "upload_audio" for related to voice note actions. Old action names will still work for backward compatibility.
  • -
-
-
-

⚠️ WARNING! ⚠️ -After the next Bot API update (Bot API 5.3) there will be a one-time change of the value of the field file_unique_id in objects of the type PhotoSize and of the fields small_file_unique_id and big_file_unique_id in objects of the type ChatPhoto.

-
-
-
-

⚠️ WARNING! ⚠️ -Service messages about non-bot users joining the chat will be soon removed from large groups. We recommend using the "chat_member" update as a replacement.

-
-
-
-

⚠️ WARNING! ⚠️ -After one of the upcoming Bot API updates, user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

-
-
-

March 9, 2021

-

Bot API 5.1

-

Added two new update types

-
    -
  • Added updates about member status changes in chats, represented by the class ChatMemberUpdated and the fields my_chat_member and chat_member in the Update class. The bot must be an administrator in the chat to receive chat_member updates about other chat members. By default, only my_chat_member updates about the bot itself are received.
  • -
-

Improved Invite Links

-
    -
  • Added the class ChatInviteLink, representing an invite link to a chat.
  • -
  • Added the method createChatInviteLink, which can be used to create new invite links in addition to the primary invite link.
  • -
  • Added the method editChatInviteLink, which can be used to edit non-primary invite links created by the bot.
  • -
  • Added the method revokeChatInviteLink, which can be used to revoke invite links created by the bot.
  • -
-

Voice Chat Info

- -

And More

-
    -
  • Added the type MessageAutoDeleteTimerChanged and the field message_auto_delete_timer_changed to the class Message.
  • -
  • Added the parameter revoke_messages to the method kickChatMember, allowing to delete all messages from a group for the user who is being removed.
  • -
  • Added the new administrator privilege can_manage_chat to the class ChatMember and parameter can_manage_chat to the method promoteChatMember. This administrator right is implied by any other administrator privilege.
  • -
  • Supported the new bowling animation for the random dice. Choose between different animations (dice, darts, basketball, football, bowling, slot machine) by specifying the emoji parameter in the method sendDice.
  • -
-
-
-

⚠️ WARNING! ⚠️ -After one of the upcoming Bot API updates, some user identifiers will become bigger than 2^31 - 1 and it will be no longer possible to store them in a signed 32-bit integer type. User identifiers will have up to 52 significant bits, so a 64-bit integer or double-precision float type would still be safe for storing them. Please make sure that your code can correctly handle such user identifiers.

-
-
-

November 4, 2020

-

Introducing Bot API 5.0

-

Run Your Own Bot API Server

-
    -
  • Bot API source code is now available at telegram-bot-api. You can now run your own Bot API server locally, boosting your bots' performance (check this out to see if this will benefit your project).
  • -
  • Added the method logOut, which can be used to log out from the cloud Bot API server before launching your bot locally. You must log out the bot before running it locally, otherwise there is no guarantee that the bot will receive all updates.
  • -
  • Added the method close, which can be used to close the bot instance before moving it from one local server to another.
  • -
-

Transfer Bot Ownership

-
    -
  • You can now use @BotFather to transfer your existing bots to another Telegram account.
  • -
-

Webhooks

-
    -
  • Added the parameter ip_address to the method setWebhook, allowing to bypass DNS resolving and use the specified fixed IP address to send webhook requests.
  • -
  • Added the field ip_address to the class WebhookInfo, containing the current IP address used for webhook connections creation.
  • -
  • Added the ability to drop all pending updates when changing webhook URL using the parameter drop_pending_updates in the methods setWebhook and deleteWebhook.
  • -
-

Working with Groups

-
    -
  • The getChat request now returns the user's bio for private chats if available.
  • -
  • The getChat request now returns the identifier of the linked chat for supergroups and channels, i.e. the discussion group identifier for a channel and vice versa.
  • -
  • The getChat request now returns the location to which the supergroup is connected (see Local Groups). Added the class ChatLocation to represent the location.
  • -
  • Added the parameter only_if_banned to the method unbanChatMember to allow safe unban.
  • -
-

Working with Files

-
    -
  • Added the field file_name to the classes Audio and Video, containing the name of the original file.
  • -
  • Added the ability to disable server-side file content type detection using the parameter disable_content_type_detection in the method sendDocument and the class inputMediaDocument.
  • -
-

Multiple Pinned Messages

-
    -
  • Added the ability to pin messages in private chats.
  • -
  • Added the parameter message_id to the method unpinChatMessage to allow unpinning of the specific pinned message.
  • -
  • Added the method unpinAllChatMessages, which can be used to unpin all pinned messages in a chat.
  • -
-

File Albums

-
    -
  • Added support for sending and receiving audio and document albums in the method sendMediaGroup.
  • -
-

Live Locations

- -

Anonymous Admins

-
    -
  • Added the field sender_chat to the class Message, containing the sender of a message which is a chat (group or channel). For backward compatibility in non-channel chats, the field from in such messages will contain the user 777000 for messages automatically forwarded to the discussion group and the user 1087968824 (@GroupAnonymousBot) for messages from anonymous group administrators.
  • -
  • Added the field is_anonymous to the class chatMember, which can be used to distinguish anonymous chat administrators.
  • -
  • Added the parameter is_anonymous to the method promoteChatMember, which allows to promote anonymous chat administrators. The bot itself should have the is_anonymous right to do this. Despite the fact that bots can have the is_anonymous right, they will never appear as anonymous in the chat. Bots can use the right only for passing to other administrators.
  • -
  • Added the custom title of an anonymous message sender to the class Message as author_signature.
  • -
-

And More

- -

And Last but bot Least

-
    -
  • Supported the new football and slot machine animations for the random dice. Choose between different animations (dice, darts, basketball, football, slot machine) by specifying the emoji parameter in the method sendDice.
  • -
-

See earlier changes »

-

Authorizing your bot

-

Each bot is given a unique authentication token when it is created. The token looks something like 123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11, but we'll use simply <token> in this document instead. You can learn about obtaining tokens and generating new ones in this document.

-

Making requests

-

All queries to the Telegram Bot API must be served over HTTPS and need to be presented in this form: https://api.telegram.org/bot<token>/METHOD_NAME. Like this for example:

-
https://api.telegram.org/bot123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11/getMe
-

We support GET and POST HTTP methods. We support four ways of passing parameters in Bot API requests:

-
    -
  • URL query string
  • -
  • application/x-www-form-urlencoded
  • -
  • application/json (except for uploading files)
  • -
  • multipart/form-data (use to upload files)
  • -
-

The response contains a JSON object, which always has a Boolean field 'ok' and may have an optional String field 'description' with a human-readable description of the result. If 'ok' equals true, the request was successful and the result of the query can be found in the 'result' field. In case of an unsuccessful request, 'ok' equals false and the error is explained in the 'description'. An Integer 'error_code' field is also returned, but its contents are subject to change in the future. Some errors may also have an optional field 'parameters' of the type ResponseParameters, which can help to automatically handle the error.

-
    -
  • All methods in the Bot API are case-insensitive.
  • -
  • All queries must be made using UTF-8.
  • -
-

Making requests when getting updates

-

If you're using webhooks, you can perform a request to the Bot API while sending an answer to the webhook. Use either application/json or application/x-www-form-urlencoded or multipart/form-data response content type for passing parameters. Specify the method to be invoked in the method parameter of the request. It's not possible to know that such a request was successful or get its result.

-
-

Please see our FAQ for examples.

-
-

Using a Local Bot API Server

-

The Bot API server source code is available at telegram-bot-api. You can run it locally and send the requests to your own server instead of https://api.telegram.org. If you switch to a local Bot API server, your bot will be able to:

-
    -
  • Download files without a size limit.
  • -
  • Upload files up to 2000 MB.
  • -
  • Upload files using their local path and the file URI scheme.
  • -
  • Use an HTTP URL for the webhook.
  • -
  • Use any local IP address for the webhook.
  • -
  • Use any port for the webhook.
  • -
  • Set max_webhook_connections up to 100000.
  • -
  • Receive the absolute local path as a value of the file_path field without the need to download the file after a getFile request.
  • -
-

Do I need a Local Bot API Server

-

The majority of bots will be OK with the default configuration, running on our servers. But if you feel that you need one of these features, you're welcome to switch to your own at any time.

-

Getting updates

-

There are two mutually exclusive ways of receiving updates for your bot — the getUpdates method on one hand and Webhooks on the other. Incoming updates are stored on the server until the bot receives them either way, but they will not be kept longer than 24 hours.

-

Regardless of which option you choose, you will receive JSON-serialized Update objects as a result.

-

Update

-

This object represents an incoming update. -At most one of the optional parameters can be present in any given update.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
update_idIntegerThe update's unique identifier. Update identifiers start from a certain positive number and increase sequentially. This ID becomes especially handy if you're using Webhooks, since it allows you to ignore repeated updates or to restore the correct update sequence, should they get out of order. If there are no new updates for at least a week, then identifier of the next update will be chosen randomly instead of sequentially.
messageMessageOptional. New incoming message of any kind — text, photo, sticker, etc.
edited_messageMessageOptional. New version of a message that is known to the bot and was edited
channel_postMessageOptional. New incoming channel post of any kind — text, photo, sticker, etc.
edited_channel_postMessageOptional. New version of a channel post that is known to the bot and was edited
inline_queryInlineQueryOptional. New incoming inline query
chosen_inline_resultChosenInlineResultOptional. The result of an inline query that was chosen by a user and sent to their chat partner. Please see our documentation on the feedback collecting for details on how to enable these updates for your bot.
callback_queryCallbackQueryOptional. New incoming callback query
shipping_queryShippingQueryOptional. New incoming shipping query. Only for invoices with flexible price
pre_checkout_queryPreCheckoutQueryOptional. New incoming pre-checkout query. Contains full information about checkout
pollPollOptional. New poll state. Bots receive only updates about stopped polls and polls, which are sent by the bot
poll_answerPollAnswerOptional. A user changed their answer in a non-anonymous poll. Bots receive new votes only in polls that were sent by the bot itself.
my_chat_memberChatMemberUpdatedOptional. The bot's chat member status was updated in a chat. For private chats, this update is received only when the bot is blocked or unblocked by the user.
chat_memberChatMemberUpdatedOptional. A chat member's status was updated in a chat. The bot must be an administrator in the chat and must explicitly specify "chat_member" in the list of allowed_updates to receive these updates.
-

getUpdates

-

Use this method to receive incoming updates using long polling (wiki). An Array of Update objects is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
offsetIntegerOptionalIdentifier of the first update to be returned. Must be greater by one than the highest among the identifiers of previously received updates. By default, updates starting with the earliest unconfirmed update are returned. An update is considered confirmed as soon as getUpdates is called with an offset higher than its update_id. The negative offset can be specified to retrieve updates starting from -offset update from the end of the updates queue. All previous updates will forgotten.
limitIntegerOptionalLimits the number of updates to be retrieved. Values between 1-100 are accepted. Defaults to 100.
timeoutIntegerOptionalTimeout in seconds for long polling. Defaults to 0, i.e. usual short polling. Should be positive, short polling should be used for testing purposes only.
allowed_updatesArray of StringOptionalA JSON-serialized list of the update types you want your bot to receive. For example, specify ["message", "edited_channel_post", "callback_query"] to only receive updates of these types. See Update for a complete list of available update types. Specify an empty list to receive all update types except chat_member (default). If not specified, the previous setting will be used.

Please note that this parameter doesn't affect updates created before the call to the getUpdates, so unwanted updates may be received for a short period of time.
-
-

Notes -1. This method will not work if an outgoing webhook is set up. -2. In order to avoid getting duplicate updates, recalculate offset after each server response.

-
-

setWebhook

-

Use this method to specify a url and receive incoming updates via an outgoing webhook. Whenever there is an update for the bot, we will send an HTTPS POST request to the specified url, containing a JSON-serialized Update. In case of an unsuccessful request, we will give up after a reasonable amount of attempts. Returns True on success.

-

If you'd like to make sure that the Webhook request comes from Telegram, we recommend using a secret path in the URL, e.g. https://www.example.com/<token>. Since nobody else knows your bot's token, you can be pretty sure it's us.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
urlStringYesHTTPS url to send updates to. Use an empty string to remove webhook integration
certificateInputFileOptionalUpload your public key certificate so that the root certificate in use can be checked. See our self-signed guide for details.
ip_addressStringOptionalThe fixed IP address which will be used to send webhook requests instead of the IP address resolved through DNS
max_connectionsIntegerOptionalMaximum allowed number of simultaneous HTTPS connections to the webhook for update delivery, 1-100. Defaults to 40. Use lower values to limit the load on your bot's server, and higher values to increase your bot's throughput.
allowed_updatesArray of StringOptionalA JSON-serialized list of the update types you want your bot to receive. For example, specify ["message", "edited_channel_post", "callback_query"] to only receive updates of these types. See Update for a complete list of available update types. Specify an empty list to receive all update types except chat_member (default). If not specified, the previous setting will be used.
Please note that this parameter doesn't affect updates created before the call to the setWebhook, so unwanted updates may be received for a short period of time.
drop_pending_updatesBooleanOptionalPass True to drop all pending updates
-
-

Notes -1. You will not be able to receive updates using getUpdates for as long as an outgoing webhook is set up. -2. To use a self-signed certificate, you need to upload your public key certificate using certificate parameter. Please upload as InputFile, sending a String will not work. -3. Ports currently supported for Webhooks: 443, 80, 88, 8443.

-
-
-

NEW! If you're having any trouble setting up webhooks, please check out this amazing guide to Webhooks.

-
-

deleteWebhook

-

Use this method to remove webhook integration if you decide to switch back to getUpdates. Returns True on success.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
drop_pending_updatesBooleanOptionalPass True to drop all pending updates
-

getWebhookInfo

-

Use this method to get current webhook status. Requires no parameters. On success, returns a WebhookInfo object. If the bot is using getUpdates, will return an object with the url field empty.

-

WebhookInfo

-

Contains information about the current status of a webhook.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
urlStringWebhook URL, may be empty if webhook is not set up
has_custom_certificateBooleanTrue, if a custom certificate was provided for webhook certificate checks
pending_update_countIntegerNumber of updates awaiting delivery
ip_addressStringOptional. Currently used webhook IP address
last_error_dateIntegerOptional. Unix time for the most recent error that happened when trying to deliver an update via webhook
last_error_messageStringOptional. Error message in human-readable format for the most recent error that happened when trying to deliver an update via webhook
max_connectionsIntegerOptional. Maximum allowed number of simultaneous HTTPS connections to the webhook for update delivery
allowed_updatesArray of StringOptional. A list of update types the bot is subscribed to. Defaults to all update types except chat_member
-

Available types

-

All types used in the Bot API responses are represented as JSON-objects.

-

It is safe to use 32-bit signed integers for storing all Integer fields unless otherwise noted.

-
-

Optional fields may be not returned when irrelevant.

-
-

User

-

This object represents a Telegram user or bot.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
idIntegerUnique identifier for this user or bot. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a 64-bit integer or double-precision float type are safe for storing this identifier.
is_botBooleanTrue, if this user is a bot
first_nameStringUser's or bot's first name
last_nameStringOptional. User's or bot's last name
usernameStringOptional. User's or bot's username
language_codeStringOptional. IETF language tag of the user's language
can_join_groupsBooleanOptional. True, if the bot can be invited to groups. Returned only in getMe.
can_read_all_group_messagesBooleanOptional. True, if privacy mode is disabled for the bot. Returned only in getMe.
supports_inline_queriesBooleanOptional. True, if the bot supports inline queries. Returned only in getMe.
-

Chat

-

This object represents a chat.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
idIntegerUnique identifier for this chat. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier.
typeStringType of chat, can be either "private", "group", "supergroup" or "channel"
titleStringOptional. Title, for supergroups, channels and group chats
usernameStringOptional. Username, for private chats, supergroups and channels if available
first_nameStringOptional. First name of the other party in a private chat
last_nameStringOptional. Last name of the other party in a private chat
photoChatPhotoOptional. Chat photo. Returned only in getChat.
bioStringOptional. Bio of the other party in a private chat. Returned only in getChat.
descriptionStringOptional. Description, for groups, supergroups and channel chats. Returned only in getChat.
invite_linkStringOptional. Primary invite link, for groups, supergroups and channel chats. Returned only in getChat.
pinned_messageMessageOptional. The most recent pinned message (by sending date). Returned only in getChat.
permissionsChatPermissionsOptional. Default chat member permissions, for groups and supergroups. Returned only in getChat.
slow_mode_delayIntegerOptional. For supergroups, the minimum allowed delay between consecutive messages sent by each unpriviledged user. Returned only in getChat.
message_auto_delete_timeIntegerOptional. The time after which all messages sent to the chat will be automatically deleted; in seconds. Returned only in getChat.
sticker_set_nameStringOptional. For supergroups, name of group sticker set. Returned only in getChat.
can_set_sticker_setBooleanOptional. True, if the bot can change the group sticker set. Returned only in getChat.
linked_chat_idIntegerOptional. Unique identifier for the linked chat, i.e. the discussion group identifier for a channel and vice versa; for supergroups and channel chats. This identifier may be greater than 32 bits and some programming languages may have difficulty/silent defects in interpreting it. But it is smaller than 52 bits, so a signed 64 bit integer or double-precision float type are safe for storing this identifier. Returned only in getChat.
locationChatLocationOptional. For supergroups, the location to which the supergroup is connected. Returned only in getChat.
-

Message

-

This object represents a message.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
message_idIntegerUnique message identifier inside this chat
fromUserOptional. Sender, empty for messages sent to channels
sender_chatChatOptional. Sender of the message, sent on behalf of a chat. The channel itself for channel messages. The supergroup itself for messages from anonymous group administrators. The linked channel for messages automatically forwarded to the discussion group
dateIntegerDate the message was sent in Unix time
chatChatConversation the message belongs to
forward_fromUserOptional. For forwarded messages, sender of the original message
forward_from_chatChatOptional. For messages forwarded from channels or from anonymous administrators, information about the original sender chat
forward_from_message_idIntegerOptional. For messages forwarded from channels, identifier of the original message in the channel
forward_signatureStringOptional. For messages forwarded from channels, signature of the post author if present
forward_sender_nameStringOptional. Sender's name for messages forwarded from users who disallow adding a link to their account in forwarded messages
forward_dateIntegerOptional. For forwarded messages, date the original message was sent in Unix time
reply_to_messageMessageOptional. For replies, the original message. Note that the Message object in this field will not contain further reply_to_message fields even if it itself is a reply.
via_botUserOptional. Bot through which the message was sent
edit_dateIntegerOptional. Date the message was last edited in Unix time
media_group_idStringOptional. The unique identifier of a media message group this message belongs to
author_signatureStringOptional. Signature of the post author for messages in channels, or the custom title of an anonymous group administrator
textStringOptional. For text messages, the actual UTF-8 text of the message, 0-4096 characters
entitiesArray of MessageEntityOptional. For text messages, special entities like usernames, URLs, bot commands, etc. that appear in the text
animationAnimationOptional. Message is an animation, information about the animation. For backward compatibility, when this field is set, the document field will also be set
audioAudioOptional. Message is an audio file, information about the file
documentDocumentOptional. Message is a general file, information about the file
photoArray of PhotoSizeOptional. Message is a photo, available sizes of the photo
stickerStickerOptional. Message is a sticker, information about the sticker
videoVideoOptional. Message is a video, information about the video
video_noteVideoNoteOptional. Message is a video note, information about the video message
voiceVoiceOptional. Message is a voice message, information about the file
captionStringOptional. Caption for the animation, audio, document, photo, video or voice, 0-1024 characters
caption_entitiesArray of MessageEntityOptional. For messages with a caption, special entities like usernames, URLs, bot commands, etc. that appear in the caption
contactContactOptional. Message is a shared contact, information about the contact
diceDiceOptional. Message is a dice with random value
gameGameOptional. Message is a game, information about the game. More about games »
pollPollOptional. Message is a native poll, information about the poll
venueVenueOptional. Message is a venue, information about the venue. For backward compatibility, when this field is set, the location field will also be set
locationLocationOptional. Message is a shared location, information about the location
new_chat_membersArray of UserOptional. New members that were added to the group or supergroup and information about them (the bot itself may be one of these members)
left_chat_memberUserOptional. A member was removed from the group, information about them (this member may be the bot itself)
new_chat_titleStringOptional. A chat title was changed to this value
new_chat_photoArray of PhotoSizeOptional. A chat photo was change to this value
delete_chat_photoTrueOptional. Service message: the chat photo was deleted
group_chat_createdTrueOptional. Service message: the group has been created
supergroup_chat_createdTrueOptional. Service message: the supergroup has been created. This field can't be received in a message coming through updates, because bot can't be a member of a supergroup when it is created. It can only be found in reply_to_message if someone replies to a very first message in a directly created supergroup.
channel_chat_createdTrueOptional. Service message: the channel has been created. This field can't be received in a message coming through updates, because bot can't be a member of a channel when it is created. It can only be found in reply_to_message if someone replies to a very first message in a channel.
message_auto_delete_timer_changedMessageAutoDeleteTimerChangedOptional. Service message: auto-delete timer settings changed in the chat
migrate_to_chat_idIntegerOptional. The group has been migrated to a supergroup with the specified identifier. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier.
migrate_from_chat_idIntegerOptional. The supergroup has been migrated from a group with the specified identifier. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier.
pinned_messageMessageOptional. Specified message was pinned. Note that the Message object in this field will not contain further reply_to_message fields even if it is itself a reply.
invoiceInvoiceOptional. Message is an invoice for a payment, information about the invoice. More about payments »
successful_paymentSuccessfulPaymentOptional. Message is a service message about a successful payment, information about the payment. More about payments »
connected_websiteStringOptional. The domain name of the website on which the user has logged in. More about Telegram Login »
passport_dataPassportDataOptional. Telegram Passport data
proximity_alert_triggeredProximityAlertTriggeredOptional. Service message. A user in the chat triggered another user's proximity alert while sharing Live Location.
voice_chat_scheduledVoiceChatScheduledOptional. Service message: voice chat scheduled
voice_chat_startedVoiceChatStartedOptional. Service message: voice chat started
voice_chat_endedVoiceChatEndedOptional. Service message: voice chat ended
voice_chat_participants_invitedVoiceChatParticipantsInvitedOptional. Service message: new participants invited to a voice chat
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message. login_url buttons are represented as ordinary url buttons.
-

MessageId

-

This object represents a unique message identifier.

- - - - - - - - - - - - - - - -
FieldTypeDescription
message_idIntegerUnique message identifier
-

MessageEntity

-

This object represents one special entity in a text message. For example, hashtags, usernames, URLs, etc.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the entity. Can be "mention" (@username), "hashtag" (#hashtag), "cashtag" ($USD), "bot_command" (/start@jobs_bot), "url" (https://telegram.org), "email" (do-not-reply@telegram.org), "phone_number" (+1-212-555-0123), "bold" (bold text), "italic" (italic text), "underline" (underlined text), "strikethrough" (strikethrough text), "code" (monowidth string), "pre" (monowidth block), "text_link" (for clickable text URLs), "text_mention" (for users without usernames)
offsetIntegerOffset in UTF-16 code units to the start of the entity
lengthIntegerLength of the entity in UTF-16 code units
urlStringOptional. For "text_link" only, url that will be opened after user taps on the text
userUserOptional. For "text_mention" only, the mentioned user
languageStringOptional. For "pre" only, the programming language of the entity text
-

PhotoSize

-

This object represents one size of a photo or a file / sticker thumbnail.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
widthIntegerPhoto width
heightIntegerPhoto height
file_sizeIntegerOptional. File size in bytes
-

Animation

-

This object represents an animation file (GIF or H.264/MPEG-4 AVC video without sound).

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
widthIntegerVideo width as defined by sender
heightIntegerVideo height as defined by sender
durationIntegerDuration of the video in seconds as defined by sender
thumbPhotoSizeOptional. Animation thumbnail as defined by sender
file_nameStringOptional. Original animation filename as defined by sender
mime_typeStringOptional. MIME type of the file as defined by sender
file_sizeIntegerOptional. File size in bytes
-

Audio

-

This object represents an audio file to be treated as music by the Telegram clients.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
durationIntegerDuration of the audio in seconds as defined by sender
performerStringOptional. Performer of the audio as defined by sender or by audio tags
titleStringOptional. Title of the audio as defined by sender or by audio tags
file_nameStringOptional. Original filename as defined by sender
mime_typeStringOptional. MIME type of the file as defined by sender
file_sizeIntegerOptional. File size in bytes
thumbPhotoSizeOptional. Thumbnail of the album cover to which the music file belongs
-

Document

-

This object represents a general file (as opposed to photos, voice messages and audio files).

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
thumbPhotoSizeOptional. Document thumbnail as defined by sender
file_nameStringOptional. Original filename as defined by sender
mime_typeStringOptional. MIME type of the file as defined by sender
file_sizeIntegerOptional. File size in bytes
-

Video

-

This object represents a video file.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
widthIntegerVideo width as defined by sender
heightIntegerVideo height as defined by sender
durationIntegerDuration of the video in seconds as defined by sender
thumbPhotoSizeOptional. Video thumbnail
file_nameStringOptional. Original filename as defined by sender
mime_typeStringOptional. Mime type of a file as defined by sender
file_sizeIntegerOptional. File size in bytes
-

VideoNote

-

This object represents a video message (available in Telegram apps as of v.4.0).

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
lengthIntegerVideo width and height (diameter of the video message) as defined by sender
durationIntegerDuration of the video in seconds as defined by sender
thumbPhotoSizeOptional. Video thumbnail
file_sizeIntegerOptional. File size in bytes
-

Voice

-

This object represents a voice note.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
durationIntegerDuration of the audio in seconds as defined by sender
mime_typeStringOptional. MIME type of the file as defined by sender
file_sizeIntegerOptional. File size in bytes
-

Contact

-

This object represents a phone contact.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
phone_numberStringContact's phone number
first_nameStringContact's first name
last_nameStringOptional. Contact's last name
user_idIntegerOptional. Contact's user identifier in Telegram. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a 64-bit integer or double-precision float type are safe for storing this identifier.
vcardStringOptional. Additional data about the contact in the form of a vCard
-

Dice

-

This object represents an animated emoji that displays a random value.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
emojiStringEmoji on which the dice throw animation is based
valueIntegerValue of the dice, 1-6 for "🎲", "🎯" and "🎳" base emoji, 1-5 for "🏀" and "⚽" base emoji, 1-64 for "🎰" base emoji
-

PollOption

-

This object contains information about one answer option in a poll.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
textStringOption text, 1-100 characters
voter_countIntegerNumber of users that voted for this option
-

PollAnswer

-

This object represents an answer of a user in a non-anonymous poll.

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
poll_idStringUnique poll identifier
userUserThe user, who changed the answer to the poll
option_idsArray of Integer0-based identifiers of answer options, chosen by the user. May be empty if the user retracted their vote.
-

Poll

-

This object contains information about a poll.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
idStringUnique poll identifier
questionStringPoll question, 1-300 characters
optionsArray of PollOptionList of poll options
total_voter_countIntegerTotal number of users that voted in the poll
is_closedBooleanTrue, if the poll is closed
is_anonymousBooleanTrue, if the poll is anonymous
typeStringPoll type, currently can be "regular" or "quiz"
allows_multiple_answersBooleanTrue, if the poll allows multiple answers
correct_option_idIntegerOptional. 0-based identifier of the correct answer option. Available only for polls in the quiz mode, which are closed, or was sent (not forwarded) by the bot or to the private chat with the bot.
explanationStringOptional. Text that is shown when a user chooses an incorrect answer or taps on the lamp icon in a quiz-style poll, 0-200 characters
explanation_entitiesArray of MessageEntityOptional. Special entities like usernames, URLs, bot commands, etc. that appear in the explanation
open_periodIntegerOptional. Amount of time in seconds the poll will be active after creation
close_dateIntegerOptional. Point in time (Unix timestamp) when the poll will be automatically closed
-

Location

-

This object represents a point on the map.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
longitudeFloatLongitude as defined by sender
latitudeFloatLatitude as defined by sender
horizontal_accuracyFloat numberOptional. The radius of uncertainty for the location, measured in meters; 0-1500
live_periodIntegerOptional. Time relative to the message sending date, during which the location can be updated, in seconds. For active live locations only.
headingIntegerOptional. The direction in which user is moving, in degrees; 1-360. For active live locations only.
proximity_alert_radiusIntegerOptional. Maximum distance for proximity alerts about approaching another chat member, in meters. For sent live locations only.
-

Venue

-

This object represents a venue.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
locationLocationVenue location. Can't be a live location
titleStringName of the venue
addressStringAddress of the venue
foursquare_idStringOptional. Foursquare identifier of the venue
foursquare_typeStringOptional. Foursquare type of the venue. (For example, "arts_entertainment/default", "arts_entertainment/aquarium" or "food/icecream".)
google_place_idStringOptional. Google Places identifier of the venue
google_place_typeStringOptional. Google Places type of the venue. (See supported types.)
-

ProximityAlertTriggered

-

This object represents the content of a service message, sent whenever a user in the chat triggers a proximity alert set by another user.

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
travelerUserUser that triggered the alert
watcherUserUser that set the alert
distanceIntegerThe distance between the users
-

MessageAutoDeleteTimerChanged

-

This object represents a service message about a change in auto-delete timer settings.

- - - - - - - - - - - - - - - -
FieldTypeDescription
message_auto_delete_timeIntegerNew auto-delete time for messages in the chat
-

VoiceChatScheduled

-

This object represents a service message about a voice chat scheduled in the chat.

- - - - - - - - - - - - - - - -
FieldTypeDescription
start_dateIntegerPoint in time (Unix timestamp) when the voice chat is supposed to be started by a chat administrator
-

VoiceChatStarted

-

This object represents a service message about a voice chat started in the chat. Currently holds no information.

-

VoiceChatEnded

-

This object represents a service message about a voice chat ended in the chat.

- - - - - - - - - - - - - - - -
FieldTypeDescription
durationIntegerVoice chat duration in seconds
-

VoiceChatParticipantsInvited

-

This object represents a service message about new members invited to a voice chat.

- - - - - - - - - - - - - - - -
FieldTypeDescription
usersArray of UserOptional. New members that were invited to the voice chat
-

UserProfilePhotos

-

This object represent a user's profile pictures.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
total_countIntegerTotal number of profile pictures the target user has
photosArray of Array of PhotoSizeRequested profile pictures (in up to 4 sizes each)
-

File

-

This object represents a file ready to be downloaded. The file can be downloaded via the link https://api.telegram.org/file/bot<token>/<file_path>. It is guaranteed that the link will be valid for at least 1 hour. When the link expires, a new one can be requested by calling getFile.

-
-

Maximum file size to download is 20 MB

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
file_sizeIntegerOptional. File size in bytes, if known
file_pathStringOptional. File path. Use https://api.telegram.org/file/bot<token>/<file_path> to get the file.
-

ReplyKeyboardMarkup

-

This object represents a custom keyboard with reply options (see Introduction to bots for details and examples).

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
keyboardArray of Array of KeyboardButtonArray of button rows, each represented by an Array of KeyboardButton objects
resize_keyboardBooleanOptional. Requests clients to resize the keyboard vertically for optimal fit (e.g., make the keyboard smaller if there are just two rows of buttons). Defaults to false, in which case the custom keyboard is always of the same height as the app's standard keyboard.
one_time_keyboardBooleanOptional. Requests clients to hide the keyboard as soon as it's been used. The keyboard will still be available, but clients will automatically display the usual letter-keyboard in the chat – the user can press a special button in the input field to see the custom keyboard again. Defaults to false.
input_field_placeholderStringOptional. The placeholder to be shown in the input field when the keyboard is active; 1-64 characters
selectiveBooleanOptional. Use this parameter if you want to show the keyboard to specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.

Example: A user requests to change the bot's language, bot replies to the request with a keyboard to select the new language. Other users in the group don't see the keyboard.
-

KeyboardButton

-

This object represents one button of the reply keyboard. For simple text buttons String can be used instead of this object to specify text of the button. Optional fields request_contact, request_location, and request_poll are mutually exclusive.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
textStringText of the button. If none of the optional fields are used, it will be sent as a message when the button is pressed
request_contactBooleanOptional. If True, the user's phone number will be sent as a contact when the button is pressed. Available in private chats only
request_locationBooleanOptional. If True, the user's current location will be sent when the button is pressed. Available in private chats only
request_pollKeyboardButtonPollTypeOptional. If specified, the user will be asked to create a poll and send it to the bot when the button is pressed. Available in private chats only
-

Note: request_contact and request_location options will only work in Telegram versions released after 9 April, 2016. Older clients will display unsupported message. -Note: request_poll option will only work in Telegram versions released after 23 January, 2020. Older clients will display unsupported message.

-

KeyboardButtonPollType

-

This object represents type of a poll, which is allowed to be created and sent when the corresponding button is pressed.

- - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringOptional. If quiz is passed, the user will be allowed to create only polls in the quiz mode. If regular is passed, only regular polls will be allowed. Otherwise, the user will be allowed to create a poll of any type.
-

ReplyKeyboardRemove

-

Upon receiving a message with this object, Telegram clients will remove the current custom keyboard and display the default letter-keyboard. By default, custom keyboards are displayed until a new keyboard is sent by a bot. An exception is made for one-time keyboards that are hidden immediately after the user presses a button (see ReplyKeyboardMarkup).

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
remove_keyboardTrueRequests clients to remove the custom keyboard (user will not be able to summon this keyboard; if you want to hide the keyboard from sight but keep it accessible, use one_time_keyboard in ReplyKeyboardMarkup)
selectiveBooleanOptional. Use this parameter if you want to remove the keyboard for specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.

Example: A user votes in a poll, bot returns confirmation message in reply to the vote and removes the keyboard for that user, while still showing the keyboard with poll options to users who haven't voted yet.
-

InlineKeyboardMarkup

-

This object represents an inline keyboard that appears right next to the message it belongs to.

- - - - - - - - - - - - - - - -
FieldTypeDescription
inline_keyboardArray of Array of InlineKeyboardButtonArray of button rows, each represented by an Array of InlineKeyboardButton objects
-

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will display unsupported message.

-

InlineKeyboardButton

-

This object represents one button of an inline keyboard. You must use exactly one of the optional fields.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
textStringLabel text on the button
urlStringOptional. HTTP or tg:// url to be opened when button is pressed
login_urlLoginUrlOptional. An HTTP URL used to automatically authorize the user. Can be used as a replacement for the Telegram Login Widget.
callback_dataStringOptional. Data to be sent in a callback query to the bot when button is pressed, 1-64 bytes
switch_inline_queryStringOptional. If set, pressing the button will prompt the user to select one of their chats, open that chat and insert the bot's username and the specified inline query in the input field. Can be empty, in which case just the bot's username will be inserted.

Note: This offers an easy way for users to start using your bot in inline mode when they are currently in a private chat with it. Especially useful when combined with switch_pm... actions – in this case the user will be automatically returned to the chat they switched from, skipping the chat selection screen.
switch_inline_query_current_chatStringOptional. If set, pressing the button will insert the bot's username and the specified inline query in the current chat's input field. Can be empty, in which case only the bot's username will be inserted.

This offers a quick way for the user to open your bot in inline mode in the same chat – good for selecting something from multiple options.
callback_gameCallbackGameOptional. Description of the game that will be launched when the user presses the button.

NOTE: This type of button must always be the first button in the first row.
payBooleanOptional. Specify True, to send a Pay button.

NOTE: This type of button must always be the first button in the first row.
-

LoginUrl

-

This object represents a parameter of the inline keyboard button used to automatically authorize a user. Serves as a great replacement for the Telegram Login Widget when the user is coming from Telegram. All the user needs to do is tap/click a button and confirm that they want to log in:

-
- TITLE -
-

Telegram apps support these buttons as of version 5.7.

-
-

Sample bot: @discussbot

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
urlStringAn HTTP URL to be opened with user authorization data added to the query string when the button is pressed. If the user refuses to provide authorization data, the original URL without information about the user will be opened. The data added is the same as described in Receiving authorization data.

NOTE: You must always check the hash of the received data to verify the authentication and the integrity of the data as described in Checking authorization.
forward_textStringOptional. New text of the button in forwarded messages.
bot_usernameStringOptional. Username of a bot, which will be used for user authorization. See Setting up a bot for more details. If not specified, the current bot's username will be assumed. The url's domain must be the same as the domain linked with the bot. See Linking your domain to the bot for more details.
request_write_accessBooleanOptional. Pass True to request the permission for your bot to send messages to the user.
-

CallbackQuery

-

This object represents an incoming callback query from a callback button in an inline keyboard. If the button that originated the query was attached to a message sent by the bot, the field message will be present. If the button was attached to a message sent via the bot (in inline mode), the field inline_message_id will be present. Exactly one of the fields data or game_short_name will be present.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
idStringUnique identifier for this query
fromUserSender
messageMessageOptional. Message with the callback button that originated the query. Note that message content and message date will not be available if the message is too old
inline_message_idStringOptional. Identifier of the message sent via the bot in inline mode, that originated the query.
chat_instanceStringGlobal identifier, uniquely corresponding to the chat to which the message with the callback button was sent. Useful for high scores in games.
dataStringOptional. Data associated with the callback button. Be aware that a bad client can send arbitrary data in this field.
game_short_nameStringOptional. Short name of a Game to be returned, serves as the unique identifier for the game
-
-

NOTE: After the user presses a callback button, Telegram clients will display a progress bar until you call answerCallbackQuery. It is, therefore, necessary to react by calling answerCallbackQuery even if no notification to the user is needed (e.g., without specifying any of the optional parameters).

-
-

ForceReply

-

Upon receiving a message with this object, Telegram clients will display a reply interface to the user (act as if the user has selected the bot's message and tapped 'Reply'). This can be extremely useful if you want to create user-friendly step-by-step interfaces without having to sacrifice privacy mode.

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
force_replyTrueShows reply interface to the user, as if they manually selected the bot's message and tapped 'Reply'
input_field_placeholderStringOptional. The placeholder to be shown in the input field when the reply is active; 1-64 characters
selectiveBooleanOptional. Use this parameter if you want to force reply from specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.
-
-

Example: A poll bot for groups runs in privacy mode (only receives commands, replies to its messages and mentions). There could be two ways to create a new poll:

-
    -
  • Explain the user how to send a command with parameters (e.g. /newpoll question answer1 answer2). May be appealing for hardcore users but lacks modern day polish.
  • -
  • Guide the user through a step-by-step process. 'Please send me your question', 'Cool, now let's add the first answer option', 'Great. Keep adding answer options, then send /done when you're ready'.
  • -
-

The last option is definitely more attractive. And if you use ForceReply in your bot's questions, it will receive the user's answers even if it only receives replies, commands and mentions — without any extra work for the user.

-
-

ChatPhoto

-

This object represents a chat photo.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
small_file_idStringFile identifier of small (160x160) chat photo. This file_id can be used only for photo download and only for as long as the photo is not changed.
small_file_unique_idStringUnique file identifier of small (160x160) chat photo, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
big_file_idStringFile identifier of big (640x640) chat photo. This file_id can be used only for photo download and only for as long as the photo is not changed.
big_file_unique_idStringUnique file identifier of big (640x640) chat photo, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
-

ChatInviteLink

-

Represents an invite link for a chat.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
invite_linkStringThe invite link. If the link was created by another chat administrator, then the second part of the link will be replaced with "...".
creatorUserCreator of the link
is_primaryBooleanTrue, if the link is primary
is_revokedBooleanTrue, if the link is revoked
expire_dateIntegerOptional. Point in time (Unix timestamp) when the link will expire or has been expired
member_limitIntegerOptional. Maximum number of users that can be members of the chat simultaneously after joining the chat via this invite link; 1-99999
-

ChatMember

-

This object contains information about one member of a chat. Currently, the following 6 types of chat members are supported:

- -

ChatMemberOwner

-

Represents a chat member that owns the chat and has all administrator privileges.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
statusStringThe member's status in the chat, always "creator"
userUserInformation about the user
is_anonymousBooleanTrue, if the user's presence in the chat is hidden
custom_titleStringOptional. Custom title for this user
-

ChatMemberAdministrator

-

Represents a chat member that has some additional privileges.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
statusStringThe member's status in the chat, always "administrator"
userUserInformation about the user
can_be_editedBooleanTrue, if the bot is allowed to edit administrator privileges of that user
is_anonymousBooleanTrue, if the user's presence in the chat is hidden
can_manage_chatBooleanTrue, if the administrator can access the chat event log, chat statistics, message statistics in channels, see channel members, see anonymous administrators in supergroups and ignore slow mode. Implied by any other administrator privilege
can_delete_messagesBooleanTrue, if the administrator can delete messages of other users
can_manage_voice_chatsBooleanTrue, if the administrator can manage voice chats
can_restrict_membersBooleanTrue, if the administrator can restrict, ban or unban chat members
can_promote_membersBooleanTrue, if the administrator can add new administrators with a subset of their own privileges or demote administrators that he has promoted, directly or indirectly (promoted by administrators that were appointed by the user)
can_change_infoBooleanTrue, if the user is allowed to change the chat title, photo and other settings
can_invite_usersBooleanTrue, if the user is allowed to invite new users to the chat
can_post_messagesBooleanOptional. True, if the administrator can post in the channel; channels only
can_edit_messagesBooleanOptional. True, if the administrator can edit messages of other users and can pin messages; channels only
can_pin_messagesBooleanOptional. True, if the user is allowed to pin messages; groups and supergroups only
custom_titleStringOptional. Custom title for this user
-

ChatMemberMember

-

Represents a chat member that has no additional privileges or restrictions.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
statusStringThe member's status in the chat, always "member"
userUserInformation about the user
-

ChatMemberRestricted

-

Represents a chat member that is under certain restrictions in the chat. Supergroups only.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
statusStringThe member's status in the chat, always "restricted"
userUserInformation about the user
is_memberBooleanTrue, if the user is a member of the chat at the moment of the request
can_change_infoBooleanTrue, if the user is allowed to change the chat title, photo and other settings
can_invite_usersBooleanTrue, if the user is allowed to invite new users to the chat
can_pin_messagesBooleanTrue, if the user is allowed to pin messages
can_send_messagesBooleanTrue, if the user is allowed to send text messages, contacts, locations and venues
can_send_media_messagesBooleanTrue, if the user is allowed to send audios, documents, photos, videos, video notes and voice notes
can_send_pollsBooleanTrue, if the user is allowed to send polls
can_send_other_messagesBooleanTrue, if the user is allowed to send animations, games, stickers and use inline bots
can_add_web_page_previewsBooleanTrue, if the user is allowed to add web page previews to their messages
until_dateIntegerDate when restrictions will be lifted for this user; unix time. If 0, then the user is restricted forever
-

ChatMemberLeft

-

Represents a chat member that isn't currently a member of the chat, but may join it themselves.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
statusStringThe member's status in the chat, always "left"
userUserInformation about the user
-

ChatMemberBanned

-

Represents a chat member that was banned in the chat and can't return to the chat or view chat messages.

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
statusStringThe member's status in the chat, always "kicked"
userUserInformation about the user
until_dateIntegerDate when restrictions will be lifted for this user; unix time. If 0, then the user is banned forever
-

ChatMemberUpdated

-

This object represents changes in the status of a chat member.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
chatChatChat the user belongs to
fromUserPerformer of the action, which resulted in the change
dateIntegerDate the change was done in Unix time
old_chat_memberChatMemberPrevious information about the chat member
new_chat_memberChatMemberNew information about the chat member
invite_linkChatInviteLinkOptional. Chat invite link, which was used by the user to join the chat; for joining by invite link events only.
-

ChatPermissions

-

Describes actions that a non-administrator user is allowed to take in a chat.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
can_send_messagesBooleanOptional. True, if the user is allowed to send text messages, contacts, locations and venues
can_send_media_messagesBooleanOptional. True, if the user is allowed to send audios, documents, photos, videos, video notes and voice notes, implies can_send_messages
can_send_pollsBooleanOptional. True, if the user is allowed to send polls, implies can_send_messages
can_send_other_messagesBooleanOptional. True, if the user is allowed to send animations, games, stickers and use inline bots, implies can_send_media_messages
can_add_web_page_previewsBooleanOptional. True, if the user is allowed to add web page previews to their messages, implies can_send_media_messages
can_change_infoBooleanOptional. True, if the user is allowed to change the chat title, photo and other settings. Ignored in public supergroups
can_invite_usersBooleanOptional. True, if the user is allowed to invite new users to the chat
can_pin_messagesBooleanOptional. True, if the user is allowed to pin messages. Ignored in public supergroups
-

ChatLocation

-

Represents a location to which a chat is connected.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
locationLocationThe location to which the supergroup is connected. Can't be a live location.
addressStringLocation address; 1-64 characters, as defined by the chat owner
-

BotCommand

-

This object represents a bot command.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
commandStringText of the command, 1-32 characters. Can contain only lowercase English letters, digits and underscores.
descriptionStringDescription of the command, 3-256 characters.
-

BotCommandScope

-

This object represents the scope to which bot commands are applied. Currently, the following 7 scopes are supported:

- -

Determining list of commands

-

The following algorithm is used to determine the list of commands for a particular user viewing the bot menu. The first list of commands which is set is returned:

-

Commands in the chat with the bot

-
    -
  • botCommandScopeChat + language_code
  • -
  • botCommandScopeChat
  • -
  • botCommandScopeAllPrivateChats + language_code
  • -
  • botCommandScopeAllPrivateChats
  • -
  • botCommandScopeDefault + language_code
  • -
  • botCommandScopeDefault
  • -
-

Commands in group and supergroup chats

-
    -
  • botCommandScopeChatMember + language_code
  • -
  • botCommandScopeChatMember
  • -
  • botCommandScopeChatAdministrators + language_code (admins only)
  • -
  • botCommandScopeChatAdministrators (admins only)
  • -
  • botCommandScopeChat + language_code
  • -
  • botCommandScopeChat
  • -
  • botCommandScopeAllChatAdministrators + language_code (admins only)
  • -
  • botCommandScopeAllChatAdministrators (admins only)
  • -
  • botCommandScopeAllGroupChats + language_code
  • -
  • botCommandScopeAllGroupChats
  • -
  • botCommandScopeDefault + language_code
  • -
  • botCommandScopeDefault
  • -
-

BotCommandScopeDefault

-

Represents the default scope of bot commands. Default commands are used if no commands with a narrower scope are specified for the user.

- - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringScope type, must be default
-

BotCommandScopeAllPrivateChats

-

Represents the scope of bot commands, covering all private chats.

- - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringScope type, must be all_private_chats
-

BotCommandScopeAllGroupChats

-

Represents the scope of bot commands, covering all group and supergroup chats.

- - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringScope type, must be all_group_chats
-

BotCommandScopeAllChatAdministrators

-

Represents the scope of bot commands, covering all group and supergroup chat administrators.

- - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringScope type, must be all_chat_administrators
-

BotCommandScopeChat

-

Represents the scope of bot commands, covering a specific chat.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringScope type, must be chat
chat_idInteger or StringUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
-

BotCommandScopeChatAdministrators

-

Represents the scope of bot commands, covering all administrators of a specific group or supergroup chat.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringScope type, must be chat_administrators
chat_idInteger or StringUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
-

BotCommandScopeChatMember

-

Represents the scope of bot commands, covering a specific member of a group or supergroup chat.

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringScope type, must be chat_member
chat_idInteger or StringUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
user_idIntegerUnique identifier of the target user
-

ResponseParameters

-

Contains information about why a request was unsuccessful.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
migrate_to_chat_idIntegerOptional. The group has been migrated to a supergroup with the specified identifier. This number may have more than 32 significant bits and some programming languages may have difficulty/silent defects in interpreting it. But it has at most 52 significant bits, so a signed 64-bit integer or double-precision float type are safe for storing this identifier.
retry_afterIntegerOptional. In case of exceeding flood control, the number of seconds left to wait before the request can be repeated
-

InputMedia

-

This object represents the content of a media message to be sent. It should be one of

- -

InputMediaPhoto

-

Represents a photo to be sent.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be photo
mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass "attach://<file_attach_name>" to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
captionStringOptional. Caption of the photo to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the photo caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
-

InputMediaVideo

-

Represents a video to be sent.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be video
mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass "attach://<file_attach_name>" to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
thumbInputFile or StringOptional. Thumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass "attach://<file_attach_name>" if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptional. Caption of the video to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the video caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
widthIntegerOptional. Video width
heightIntegerOptional. Video height
durationIntegerOptional. Video duration in seconds
supports_streamingBooleanOptional. Pass True, if the uploaded video is suitable for streaming
-

InputMediaAnimation

-

Represents an animation file (GIF or H.264/MPEG-4 AVC video without sound) to be sent.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be animation
mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass "attach://<file_attach_name>" to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
thumbInputFile or StringOptional. Thumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass "attach://<file_attach_name>" if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptional. Caption of the animation to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the animation caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
widthIntegerOptional. Animation width
heightIntegerOptional. Animation height
durationIntegerOptional. Animation duration in seconds
-

InputMediaAudio

-

Represents an audio file to be treated as music to be sent.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be audio
mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass "attach://<file_attach_name>" to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
thumbInputFile or StringOptional. Thumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass "attach://<file_attach_name>" if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptional. Caption of the audio to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the audio caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
durationIntegerOptional. Duration of the audio in seconds
performerStringOptional. Performer of the audio
titleStringOptional. Title of the audio
-

InputMediaDocument

-

Represents a general file to be sent.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be document
mediaStringFile to send. Pass a file_id to send a file that exists on the Telegram servers (recommended), pass an HTTP URL for Telegram to get a file from the Internet, or pass "attach://<file_attach_name>" to upload a new one using multipart/form-data under <file_attach_name> name. More info on Sending Files »
thumbInputFile or StringOptional. Thumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass "attach://<file_attach_name>" if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptional. Caption of the document to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the document caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
disable_content_type_detectionBooleanOptional. Disables automatic server-side content type detection for files uploaded using multipart/form-data. Always true, if the document is sent as part of an album.
-

InputFile

-

This object represents the contents of a file to be uploaded. Must be posted using multipart/form-data in the usual way that files are uploaded via the browser.

-

Sending files

-

There are three ways to send files (photos, stickers, audio, media, etc.):

-
    -
  1. If the file is already stored somewhere on the Telegram servers, you don't need to reupload it: each file object has a file_id field, simply pass this file_id as a parameter instead of uploading. There are no limits for files sent this way.
  2. -
  3. Provide Telegram with an HTTP URL for the file to be sent. Telegram will download and send the file. 5 MB max size for photos and 20 MB max for other types of content.
  4. -
  5. Post the file using multipart/form-data in the usual way that files are uploaded via the browser. 10 MB max size for photos, 50 MB for other files.
  6. -
-

Sending by file_id

-
    -
  • It is not possible to change the file type when resending by file_id. I.e. a video can't be sent as a photo, a photo can't be sent as a document, etc.
  • -
  • It is not possible to resend thumbnails.
  • -
  • Resending a photo by file_id will send all of its sizes.
  • -
  • file_id is unique for each individual bot and can't be transferred from one bot to another.
  • -
  • file_id uniquely identifies a file, but a file can have different valid file_ids even for the same bot.
  • -
-

Sending by URL

-
    -
  • When sending by URL the target file must have the correct MIME type (e.g., audio/mpeg for sendAudio, etc.).
  • -
  • In sendDocument, sending by URL will currently only work for GIF, PDF and ZIP files.
  • -
  • To use sendVoice, the file must have the type audio/ogg and be no more than 1MB in size. 1-20MB voice notes will be sent as files.
  • -
  • Other configurations may work but we can't guarantee that they will.
  • -
-

Inline mode objects

-

Objects and methods used in the inline mode are described in the Inline mode section.

-

Available methods

-
-

All methods in the Bot API are case-insensitive. We support GET and POST HTTP methods. Use either URL query string or application/json or application/x-www-form-urlencoded or multipart/form-data for passing parameters in Bot API requests. -On successful call, a JSON-object containing the result will be returned.

-
-

getMe

-

A simple method for testing your bot's authentication token. Requires no parameters. Returns basic information about the bot in form of a User object.

-

logOut

-

Use this method to log out from the cloud Bot API server before launching the bot locally. You must log out the bot before running it locally, otherwise there is no guarantee that the bot will receive updates. After a successful call, you can immediately log in on a local server, but will not be able to log in back to the cloud Bot API server for 10 minutes. Returns True on success. Requires no parameters.

-

close

-

Use this method to close the bot instance before moving it from one local server to another. You need to delete the webhook before calling this method to ensure that the bot isn't launched again after server restart. The method will return error 429 in the first 10 minutes after the bot is launched. Returns True on success. Requires no parameters.

-

sendMessage

-

Use this method to send text messages. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
textStringYesText of the message to be sent, 1-4096 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the message text. See formatting options for more details.
entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in message text, which can be specified instead of parse_mode
disable_web_page_previewBooleanOptionalDisables link previews for links in this message
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

Formatting options

-

The Bot API supports basic formatting for messages. You can use bold, italic, underlined and strikethrough text, as well as inline links and pre-formatted code in your bots' messages. Telegram clients will render them accordingly. You can use either markdown-style or HTML-style formatting.

-

Note that Telegram clients will display an alert to the user before opening an inline link ('Open this link?' together with the full URL).

-

Message entities can be nested, providing following restrictions are met:

-
    -
  • If two entities has common characters then one of them is fully contained inside another.
  • -
  • bold, italic, underline and strikethrough entities can contain and to be contained in any other entities, except pre and code.
  • -
  • All other entities can't contain each other.
  • -
-

Links tg://user?id=<user_id> can be used to mention a user by their ID without using a username. Please note:

-
    -
  • These links will work only if they are used inside an inline link. For example, they will not work, when used in an inline keyboard button or in a message text.
  • -
  • These mentions are only guaranteed to work if the user has contacted the bot in the past, has sent a callback query to the bot via inline button or is a member in the group where he was mentioned.
  • -
-
MarkdownV2 style
-

To use this mode, pass MarkdownV2 in the parse_mode field. Use the following syntax in your message:

-
*bold \*text*
-_italic \*text_
-__underline__
-~strikethrough~
-*bold _italic bold ~italic bold strikethrough~ __underline italic bold___ bold*
-[inline URL](http://www.example.com/)
-[inline mention of a user](tg://user?id=123456789)
-`inline fixed-width code`
-```
-pre-formatted fixed-width code block
-```
-```python
-pre-formatted fixed-width code block written in the Python programming language
-```
-

Please note:

-
    -
  • Any character with code between 1 and 126 inclusively can be escaped anywhere with a preceding '\' character, in which case it is treated as an ordinary character and not a part of the markup. This implies that '\' character usually must be escaped with a preceding '\' character.
  • -
  • Inside pre and code entities, all '`' and '\' characters must be escaped with a preceding '\' character.
  • -
  • Inside (...) part of inline link definition, all ')' and '\' must be escaped with a preceding '\' character.
  • -
  • In all other places characters '_', '*', '[', ']', '(', ')', '~', '`', '>', '#', '+', '-', '=', '|', '{', '}', '.', '!' must be escaped with the preceding character '\'.
  • -
  • In case of ambiguity between italic and underline entities __ is always greadily treated from left to right as beginning or end of underline entity, so instead of ___italic underline___ use ___italic underline_\r__, where \r is a character with code 13, which will be ignored.
  • -
-
HTML style
-

To use this mode, pass HTML in the parse_mode field. The following tags are currently supported:

-
<b>bold</b>, <strong>bold</strong>
-<i>italic</i>, <em>italic</em>
-<u>underline</u>, <ins>underline</ins>
-<s>strikethrough</s>, <strike>strikethrough</strike>, <del>strikethrough</del>
-<b>bold <i>italic bold <s>italic bold strikethrough</s> <u>underline italic bold</u></i> bold</b>
-<a href="http://www.example.com/">inline URL</a>
-<a href="tg://user?id=123456789">inline mention of a user</a>
-<code>inline fixed-width code</code>
-<pre>pre-formatted fixed-width code block</pre>
-<pre><code class="language-python">pre-formatted fixed-width code block written in the Python programming language</code></pre>
-

Please note:

-
    -
  • Only the tags mentioned above are currently supported.
  • -
  • All <, > and & symbols that are not a part of a tag or an HTML entity must be replaced with the corresponding HTML entities (< with &lt;, > with &gt; and & with &amp;).
  • -
  • All numerical HTML entities are supported.
  • -
  • The API currently supports only the following named HTML entities: &lt;, &gt;, &amp; and &quot;.
  • -
  • Use nested pre and code tags, to define programming language for pre entity.
  • -
  • Programming language can't be specified for standalone code tags.
  • -
-
Markdown style
-

This is a legacy mode, retained for backward compatibility. To use this mode, pass Markdown in the parse_mode field. Use the following syntax in your message:

-
*bold text*
-_italic text_
-[inline URL](http://www.example.com/)
-[inline mention of a user](tg://user?id=123456789)
-`inline fixed-width code`
-```
-pre-formatted fixed-width code block
-```
-```python
-pre-formatted fixed-width code block written in the Python programming language
-```
-

Please note:

-
    -
  • Entities must not be nested, use parse mode MarkdownV2 instead.
  • -
  • There is no way to specify underline and strikethrough entities, use parse mode MarkdownV2 instead.
  • -
  • To escape characters '_', '*', '`', '[' outside of an entity, prepend the characters '\' before them.
  • -
  • Escaping inside entities is not allowed, so entity must be closed first and reopened again: use _snake_\__case_ for italic snake_case and *2*\**2=4* for bold 2*2=4.
  • -
-

forwardMessage

-

Use this method to forward messages of any kind. Service messages can't be forwarded. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
from_chat_idInteger or StringYesUnique identifier for the chat where the original message was sent (or channel username in the format @channelusername)
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
message_idIntegerYesMessage identifier in the chat specified in from_chat_id
-

copyMessage

-

Use this method to copy messages of any kind. Service messages and invoice messages can't be copied. The method is analogous to the method forwardMessage, but the copied message doesn't have a link to the original message. Returns the MessageId of the sent message on success.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
from_chat_idInteger or StringYesUnique identifier for the chat where the original message was sent (or channel username in the format @channelusername)
message_idIntegerYesMessage identifier in the chat specified in from_chat_id
captionStringOptionalNew caption for media, 0-1024 characters after entities parsing. If not specified, the original caption is kept
parse_modeStringOptionalMode for parsing entities in the new caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the new caption, which can be specified instead of parse_mode
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

sendPhoto

-

Use this method to send photos. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
photoInputFile or StringYesPhoto to send. Pass a file_id as String to send a photo that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a photo from the Internet, or upload a new photo using multipart/form-data. The photo must be at most 10 MB in size. The photo's width and height must not exceed 10000 in total. Width and height ratio must be at most 20. More info on Sending Files »
captionStringOptionalPhoto caption (may also be used when resending photos by file_id), 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the photo caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

sendAudio

-

Use this method to send audio files, if you want Telegram clients to display them in the music player. Your audio must be in the .MP3 or .M4A format. On success, the sent Message is returned. Bots can currently send audio files of up to 50 MB in size, this limit may be changed in the future.

-

For sending voice messages, use the sendVoice method instead.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
audioInputFile or StringYesAudio file to send. Pass a file_id as String to send an audio file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get an audio file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
captionStringOptionalAudio caption, 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the audio caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
durationIntegerOptionalDuration of the audio in seconds
performerStringOptionalPerformer
titleStringOptionalTrack name
thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass "attach://<file_attach_name>" if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

sendDocument

-

Use this method to send general files. On success, the sent Message is returned. Bots can currently send files of any type of up to 50 MB in size, this limit may be changed in the future.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
documentInputFile or StringYesFile to send. Pass a file_id as String to send a file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass "attach://<file_attach_name>" if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptionalDocument caption (may also be used when resending documents by file_id), 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the document caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
disable_content_type_detectionBooleanOptionalDisables automatic server-side content type detection for files uploaded using multipart/form-data
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

sendVideo

-

Use this method to send video files, Telegram clients support mp4 videos (other formats may be sent as Document). On success, the sent Message is returned. Bots can currently send video files of up to 50 MB in size, this limit may be changed in the future.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
videoInputFile or StringYesVideo to send. Pass a file_id as String to send a video that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a video from the Internet, or upload a new video using multipart/form-data. More info on Sending Files »
durationIntegerOptionalDuration of sent video in seconds
widthIntegerOptionalVideo width
heightIntegerOptionalVideo height
thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass "attach://<file_attach_name>" if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptionalVideo caption (may also be used when resending videos by file_id), 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the video caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
supports_streamingBooleanOptionalPass True, if the uploaded video is suitable for streaming
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

sendAnimation

-

Use this method to send animation files (GIF or H.264/MPEG-4 AVC video without sound). On success, the sent Message is returned. Bots can currently send animation files of up to 50 MB in size, this limit may be changed in the future.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
animationInputFile or StringYesAnimation to send. Pass a file_id as String to send an animation that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get an animation from the Internet, or upload a new animation using multipart/form-data. More info on Sending Files »
durationIntegerOptionalDuration of sent animation in seconds
widthIntegerOptionalAnimation width
heightIntegerOptionalAnimation height
thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass "attach://<file_attach_name>" if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
captionStringOptionalAnimation caption (may also be used when resending animation by file_id), 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the animation caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

sendVoice

-

Use this method to send audio files, if you want Telegram clients to display the file as a playable voice message. For this to work, your audio must be in an .OGG file encoded with OPUS (other formats may be sent as Audio or Document). On success, the sent Message is returned. Bots can currently send voice messages of up to 50 MB in size, this limit may be changed in the future.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
voiceInputFile or StringYesAudio file to send. Pass a file_id as String to send a file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
captionStringOptionalVoice message caption, 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the voice message caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
durationIntegerOptionalDuration of the voice message in seconds
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

sendVideoNote

-

As of v.4.0, Telegram clients support rounded square mp4 videos of up to 1 minute long. Use this method to send video messages. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
video_noteInputFile or StringYesVideo note to send. Pass a file_id as String to send a video note that exists on the Telegram servers (recommended) or upload a new video using multipart/form-data. More info on Sending Files ». Sending video notes by a URL is currently unsupported
durationIntegerOptionalDuration of sent video in seconds
lengthIntegerOptionalVideo width and height, i.e. diameter of the video message
thumbInputFile or StringOptionalThumbnail of the file sent; can be ignored if thumbnail generation for the file is supported server-side. The thumbnail should be in JPEG format and less than 200 kB in size. A thumbnail's width and height should not exceed 320. Ignored if the file is not uploaded using multipart/form-data. Thumbnails can't be reused and can be only uploaded as a new file, so you can pass "attach://<file_attach_name>" if the thumbnail was uploaded using multipart/form-data under <file_attach_name>. More info on Sending Files »
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

sendMediaGroup

-

Use this method to send a group of photos, videos, documents or audios as an album. Documents and audio files can be only grouped in an album with messages of the same type. On success, an array of Messages that were sent is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
mediaArray of InputMediaAudio, InputMediaDocument, InputMediaPhoto and InputMediaVideoYesA JSON-serialized array describing messages to be sent, must include 2-10 items
disable_notificationBooleanOptionalSends messages silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the messages are a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
-

sendLocation

-

Use this method to send point on the map. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
latitudeFloat numberYesLatitude of the location
longitudeFloat numberYesLongitude of the location
horizontal_accuracyFloat numberOptionalThe radius of uncertainty for the location, measured in meters; 0-1500
live_periodIntegerOptionalPeriod in seconds for which the location will be updated (see Live Locations, should be between 60 and 86400.
headingIntegerOptionalFor live locations, a direction in which the user is moving, in degrees. Must be between 1 and 360 if specified.
proximity_alert_radiusIntegerOptionalFor live locations, a maximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

editMessageLiveLocation

-

Use this method to edit live location messages. A location can be edited until its live_period expires or editing is explicitly disabled by a call to stopMessageLiveLocation. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
latitudeFloat numberYesLatitude of new location
longitudeFloat numberYesLongitude of new location
horizontal_accuracyFloat numberOptionalThe radius of uncertainty for the location, measured in meters; 0-1500
headingIntegerOptionalDirection in which the user is moving, in degrees. Must be between 1 and 360 if specified.
proximity_alert_radiusIntegerOptionalMaximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for a new inline keyboard.
-

stopMessageLiveLocation

-

Use this method to stop updating a live location message before live_period expires. On success, if the message is not an inline message, the edited Message is returned, otherwise True is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message with live location to stop
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for a new inline keyboard.
-

sendVenue

-

Use this method to send information about a venue. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
latitudeFloat numberYesLatitude of the venue
longitudeFloat numberYesLongitude of the venue
titleStringYesName of the venue
addressStringYesAddress of the venue
foursquare_idStringOptionalFoursquare identifier of the venue
foursquare_typeStringOptionalFoursquare type of the venue, if known. (For example, "arts_entertainment/default", "arts_entertainment/aquarium" or "food/icecream".)
google_place_idStringOptionalGoogle Places identifier of the venue
google_place_typeStringOptionalGoogle Places type of the venue. (See supported types.)
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

sendContact

-

Use this method to send phone contacts. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
phone_numberStringYesContact's phone number
first_nameStringYesContact's first name
last_nameStringOptionalContact's last name
vcardStringOptionalAdditional data about the contact in the form of a vCard, 0-2048 bytes
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove keyboard or to force a reply from the user.
-

sendPoll

-

Use this method to send a native poll. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
questionStringYesPoll question, 1-300 characters
optionsArray of StringYesA JSON-serialized list of answer options, 2-10 strings 1-100 characters each
is_anonymousBooleanOptionalTrue, if the poll needs to be anonymous, defaults to True
typeStringOptionalPoll type, "quiz" or "regular", defaults to "regular"
allows_multiple_answersBooleanOptionalTrue, if the poll allows multiple answers, ignored for polls in quiz mode, defaults to False
correct_option_idIntegerOptional0-based identifier of the correct answer option, required for polls in quiz mode
explanationStringOptionalText that is shown when a user chooses an incorrect answer or taps on the lamp icon in a quiz-style poll, 0-200 characters with at most 2 line feeds after entities parsing
explanation_parse_modeStringOptionalMode for parsing entities in the explanation. See formatting options for more details.
explanation_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the poll explanation, which can be specified instead of parse_mode
open_periodIntegerOptionalAmount of time in seconds the poll will be active after creation, 5-600. Can't be used together with close_date.
close_dateIntegerOptionalPoint in time (Unix timestamp) when the poll will be automatically closed. Must be at least 5 and no more than 600 seconds in the future. Can't be used together with open_period.
is_closedBooleanOptionalPass True, if the poll needs to be immediately closed. This can be useful for poll preview.
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

sendDice

-

Use this method to send an animated emoji that will display a random value. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
emojiStringOptionalEmoji on which the dice throw animation is based. Currently, must be one of "🎲", "🎯", "🏀", "⚽", "🎳", or "🎰". Dice can have values 1-6 for "🎲", "🎯" and "🎳", values 1-5 for "🏀" and "⚽", and values 1-64 for "🎰". Defaults to "🎲"
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

sendChatAction

-

Use this method when you need to tell the user that something is happening on the bot's side. The status is set for 5 seconds or less (when a message arrives from your bot, Telegram clients clear its typing status). Returns True on success.

-
-

Example: The ImageBot needs some time to process a request and upload the image. Instead of sending a text message along the lines of "Retrieving image, please wait...", the bot may use sendChatAction with action = upload_photo. The user will see a "sending photo" status for the bot.

-
-

We only recommend using this method when a response from the bot will take a noticeable amount of time to arrive.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
actionStringYesType of action to broadcast. Choose one, depending on what the user is about to receive: typing for text messages, upload_photo for photos, record_video or upload_video for videos, record_voice or upload_voice for voice notes, upload_document for general files, find_location for location data, record_video_note or upload_video_note for video notes.
-

getUserProfilePhotos

-

Use this method to get a list of profile pictures for a user. Returns a UserProfilePhotos object.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
user_idIntegerYesUnique identifier of the target user
offsetIntegerOptionalSequential number of the first photo to be returned. By default, all photos are returned.
limitIntegerOptionalLimits the number of photos to be retrieved. Values between 1-100 are accepted. Defaults to 100.
-

getFile

-

Use this method to get basic info about a file and prepare it for downloading. For the moment, bots can download files of up to 20MB in size. On success, a File object is returned. The file can then be downloaded via the link https://api.telegram.org/file/bot<token>/<file_path>, where <file_path> is taken from the response. It is guaranteed that the link will be valid for at least 1 hour. When the link expires, a new one can be requested by calling getFile again.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
file_idStringYesFile identifier to get info about
-

Note: This function may not preserve the original file name and MIME type. You should save the file's MIME type and name (if available) when the File object is received.

-

banChatMember

-

Use this method to ban a user in a group, a supergroup or a channel. In the case of supergroups and channels, the user will not be able to return to the chat on their own using invite links, etc., unless unbanned first. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target group or username of the target supergroup or channel (in the format @channelusername)
user_idIntegerYesUnique identifier of the target user
until_dateIntegerOptionalDate when the user will be unbanned, unix time. If user is banned for more than 366 days or less than 30 seconds from the current time they are considered to be banned forever. Applied for supergroups and channels only.
revoke_messagesBooleanOptionalPass True to delete all messages from the chat for the user that is being removed. If False, the user will be able to see messages in the group that were sent before the user was removed. Always True for supergroups and channels.
-

unbanChatMember

-

Use this method to unban a previously banned user in a supergroup or channel. The user will not return to the group or channel automatically, but will be able to join via link, etc. The bot must be an administrator for this to work. By default, this method guarantees that after the call the user is not a member of the chat, but will be able to join it. So if the user is a member of the chat they will also be removed from the chat. If you don't want this, use the parameter only_if_banned. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target group or username of the target supergroup or channel (in the format @username)
user_idIntegerYesUnique identifier of the target user
only_if_bannedBooleanOptionalDo nothing if the user is not banned
-

restrictChatMember

-

Use this method to restrict a user in a supergroup. The bot must be an administrator in the supergroup for this to work and must have the appropriate admin rights. Pass True for all permissions to lift restrictions from a user. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
user_idIntegerYesUnique identifier of the target user
permissionsChatPermissionsYesA JSON-serialized object for new user permissions
until_dateIntegerOptionalDate when restrictions will be lifted for the user, unix time. If user is restricted for more than 366 days or less than 30 seconds from the current time, they are considered to be restricted forever
-

promoteChatMember

-

Use this method to promote or demote a user in a supergroup or a channel. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. Pass False for all boolean parameters to demote a user. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
user_idIntegerYesUnique identifier of the target user
is_anonymousBooleanOptionalPass True, if the administrator's presence in the chat is hidden
can_manage_chatBooleanOptionalPass True, if the administrator can access the chat event log, chat statistics, message statistics in channels, see channel members, see anonymous administrators in supergroups and ignore slow mode. Implied by any other administrator privilege
can_post_messagesBooleanOptionalPass True, if the administrator can create channel posts, channels only
can_edit_messagesBooleanOptionalPass True, if the administrator can edit messages of other users and can pin messages, channels only
can_delete_messagesBooleanOptionalPass True, if the administrator can delete messages of other users
can_manage_voice_chatsBooleanOptionalPass True, if the administrator can manage voice chats
can_restrict_membersBooleanOptionalPass True, if the administrator can restrict, ban or unban chat members
can_promote_membersBooleanOptionalPass True, if the administrator can add new administrators with a subset of their own privileges or demote administrators that he has promoted, directly or indirectly (promoted by administrators that were appointed by him)
can_change_infoBooleanOptionalPass True, if the administrator can change chat title, photo and other settings
can_invite_usersBooleanOptionalPass True, if the administrator can invite new users to the chat
can_pin_messagesBooleanOptionalPass True, if the administrator can pin messages, supergroups only
-

setChatAdministratorCustomTitle

-

Use this method to set a custom title for an administrator in a supergroup promoted by the bot. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
user_idIntegerYesUnique identifier of the target user
custom_titleStringYesNew custom title for the administrator; 0-16 characters, emoji are not allowed
-

setChatPermissions

-

Use this method to set default chat permissions for all members. The bot must be an administrator in the group or a supergroup for this to work and must have the can_restrict_members admin rights. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
permissionsChatPermissionsYesA JSON-serialized object for new default chat permissions
-

exportChatInviteLink

-

Use this method to generate a new primary invite link for a chat; any previously generated primary link is revoked. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. Returns the new invite link as String on success.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
-
-

Note: Each administrator in a chat generates their own invite links. Bots can't use invite links generated by other administrators. If you want your bot to work with invite links, it will need to generate its own link using exportChatInviteLink or by calling the getChat method. If your bot needs to generate a new primary invite link replacing its previous one, use exportChatInviteLink again.

-
-

createChatInviteLink

-

Use this method to create an additional invite link for a chat. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. The link can be revoked using the method revokeChatInviteLink. Returns the new invite link as ChatInviteLink object.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
expire_dateIntegerOptionalPoint in time (Unix timestamp) when the link will expire
member_limitIntegerOptionalMaximum number of users that can be members of the chat simultaneously after joining the chat via this invite link; 1-99999
-

editChatInviteLink

-

Use this method to edit a non-primary invite link created by the bot. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. Returns the edited invite link as a ChatInviteLink object.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
invite_linkStringYesThe invite link to edit
expire_dateIntegerOptionalPoint in time (Unix timestamp) when the link will expire
member_limitIntegerOptionalMaximum number of users that can be members of the chat simultaneously after joining the chat via this invite link; 1-99999
-

revokeChatInviteLink

-

Use this method to revoke an invite link created by the bot. If the primary link is revoked, a new link is automatically generated. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. Returns the revoked invite link as ChatInviteLink object.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier of the target chat or username of the target channel (in the format @channelusername)
invite_linkStringYesThe invite link to revoke
-

setChatPhoto

-

Use this method to set a new profile photo for the chat. Photos can't be changed for private chats. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
photoInputFileYesNew chat photo, uploaded using multipart/form-data
-

deleteChatPhoto

-

Use this method to delete a chat photo. Photos can't be changed for private chats. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. Returns True on success.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
-

setChatTitle

-

Use this method to change the title of a chat. Titles can't be changed for private chats. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
titleStringYesNew chat title, 1-255 characters
-

setChatDescription

-

Use this method to change the description of a group, a supergroup or a channel. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
descriptionStringOptionalNew chat description, 0-255 characters
-

pinChatMessage

-

Use this method to add a message to the list of pinned messages in a chat. If the chat is not a private chat, the bot must be an administrator in the chat for this to work and must have the 'can_pin_messages' admin right in a supergroup or 'can_edit_messages' admin right in a channel. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerYesIdentifier of a message to pin
disable_notificationBooleanOptionalPass True, if it is not necessary to send a notification to all chat members about the new pinned message. Notifications are always disabled in channels and private chats.
-

unpinChatMessage

-

Use this method to remove a message from the list of pinned messages in a chat. If the chat is not a private chat, the bot must be an administrator in the chat for this to work and must have the 'can_pin_messages' admin right in a supergroup or 'can_edit_messages' admin right in a channel. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalIdentifier of a message to unpin. If not specified, the most recent pinned message (by sending date) will be unpinned.
-

unpinAllChatMessages

-

Use this method to clear the list of pinned messages in a chat. If the chat is not a private chat, the bot must be an administrator in the chat for this to work and must have the 'can_pin_messages' admin right in a supergroup or 'can_edit_messages' admin right in a channel. Returns True on success.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
-

leaveChat

-

Use this method for your bot to leave a group, supergroup or channel. Returns True on success.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
-

getChat

-

Use this method to get up to date information about the chat (current name of the user for one-on-one conversations, current username of a user, group or channel, etc.). Returns a Chat object on success.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
-

getChatAdministrators

-

Use this method to get a list of administrators in a chat. On success, returns an Array of ChatMember objects that contains information about all chat administrators except other bots. If the chat is a group or a supergroup and no administrators were appointed, only the creator will be returned.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
-

getChatMemberCount

-

Use this method to get the number of members in a chat. Returns Int on success.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
-

getChatMember

-

Use this method to get information about a member of a chat. Returns a ChatMember object on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup or channel (in the format @channelusername)
user_idIntegerYesUnique identifier of the target user
-

setChatStickerSet

-

Use this method to set a new group sticker set for a supergroup. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. Use the field can_set_sticker_set optionally returned in getChat requests to check if the bot can use this method. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
sticker_set_nameStringYesName of the sticker set to be set as the group sticker set
-

deleteChatStickerSet

-

Use this method to delete a group sticker set from a supergroup. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights. Use the field can_set_sticker_set optionally returned in getChat requests to check if the bot can use this method. Returns True on success.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target supergroup (in the format @supergroupusername)
-

answerCallbackQuery

-

Use this method to send answers to callback queries sent from inline keyboards. The answer will be displayed to the user as a notification at the top of the chat screen or as an alert. On success, True is returned.

-
-

Alternatively, the user can be redirected to the specified Game URL. For this option to work, you must first create a game for your bot via @Botfather and accept the terms. Otherwise, you may use links like t.me/your_bot?start=XXXX that open your bot with a parameter.

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
callback_query_idStringYesUnique identifier for the query to be answered
textStringOptionalText of the notification. If not specified, nothing will be shown to the user, 0-200 characters
show_alertBooleanOptionalIf true, an alert will be shown by the client instead of a notification at the top of the chat screen. Defaults to false.
urlStringOptionalURL that will be opened by the user's client. If you have created a Game and accepted the conditions via @Botfather, specify the URL that opens your game — note that this will only work if the query comes from a callback_game button.

Otherwise, you may use links like t.me/your_bot?start=XXXX that open your bot with a parameter.
cache_timeIntegerOptionalThe maximum amount of time in seconds that the result of the callback query may be cached client-side. Telegram apps will support caching starting in version 3.14. Defaults to 0.
-

setMyCommands

-

Use this method to change the list of the bot's commands. See https://core.telegram.org/bots#commands for more details about bot commands. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
commandsArray of BotCommandYesA JSON-serialized list of bot commands to be set as the list of the bot's commands. At most 100 commands can be specified.
scopeBotCommandScopeOptionalA JSON-serialized object, describing scope of users for which the commands are relevant. Defaults to BotCommandScopeDefault.
language_codeStringOptionalA two-letter ISO 639-1 language code. If empty, commands will be applied to all users from the given scope, for whose language there are no dedicated commands
-

deleteMyCommands

-

Use this method to delete the list of the bot's commands for the given scope and user language. After deletion, higher level commands will be shown to affected users. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
scopeBotCommandScopeOptionalA JSON-serialized object, describing scope of users for which the commands are relevant. Defaults to BotCommandScopeDefault.
language_codeStringOptionalA two-letter ISO 639-1 language code. If empty, commands will be applied to all users from the given scope, for whose language there are no dedicated commands
-

getMyCommands

-

Use this method to get the current list of the bot's commands for the given scope and user language. Returns Array of BotCommand on success. If commands aren't set, an empty list is returned.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
scopeBotCommandScopeOptionalA JSON-serialized object, describing scope of users. Defaults to BotCommandScopeDefault.
language_codeStringOptionalA two-letter ISO 639-1 language code or an empty string
-

Inline mode methods

-

Methods and objects used in the inline mode are described in the Inline mode section.

-

Updating messages

-

The following methods allow you to change an existing message in the message history instead of sending a new one with a result of an action. This is most useful for messages with inline keyboards using callback queries, but can also help reduce clutter in conversations with regular chat bots.

-

Please note, that it is currently only possible to edit messages without reply_markup or with inline keyboards.

-

editMessageText

-

Use this method to edit text and game messages. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
textStringYesNew text of the message, 1-4096 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the message text. See formatting options for more details.
entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in message text, which can be specified instead of parse_mode
disable_web_page_previewBooleanOptionalDisables link previews for links in this message
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard.
-

editMessageCaption

-

Use this method to edit captions of messages. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
captionStringOptionalNew caption of the message, 0-1024 characters after entities parsing
parse_modeStringOptionalMode for parsing entities in the message caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptionalA JSON-serialized list of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard.
-

editMessageMedia

-

Use this method to edit animation, audio, document, photo, or video messages. If a message is part of a message album, then it can be edited only to an audio for audio albums, only to a document for document albums and to a photo or a video otherwise. When an inline message is edited, a new file can't be uploaded; use a previously uploaded file via its file_id or specify a URL. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
mediaInputMediaYesA JSON-serialized object for a new media content of the message
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for a new inline keyboard.
-

editMessageReplyMarkup

-

Use this method to edit only the reply markup of messages. On success, if the edited message is not an inline message, the edited Message is returned, otherwise True is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the message to edit
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard.
-

stopPoll

-

Use this method to stop a poll which was sent by the bot. On success, the stopped Poll is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerYesIdentifier of the original message with the poll
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for a new message inline keyboard.
-

deleteMessage

-

Use this method to delete a message, including service messages, with the following limitations:

-
    -
  • A message can only be deleted if it was sent less than 48 hours ago.
  • -
  • A dice message in a private chat can only be deleted if it was sent more than 24 hours ago.
  • -
  • Bots can delete outgoing messages in private chats, groups, and supergroups.
  • -
  • Bots can delete incoming messages in private chats.
  • -
  • Bots granted can_post_messages permissions can delete outgoing messages in channels.
  • -
  • If the bot is an administrator of a group, it can delete any message there.
  • -
  • If the bot has can_delete_messages permission in a supergroup or a channel, it can delete any message there. -Returns True on success.
  • -
- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
message_idIntegerYesIdentifier of the message to delete
-

Stickers

-

The following methods and objects allow your bot to handle stickers and sticker sets.

-

Sticker

-

This object represents a sticker.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
widthIntegerSticker width
heightIntegerSticker height
is_animatedBooleanTrue, if the sticker is animated
thumbPhotoSizeOptional. Sticker thumbnail in the .WEBP or .JPG format
emojiStringOptional. Emoji associated with the sticker
set_nameStringOptional. Name of the sticker set to which the sticker belongs
mask_positionMaskPositionOptional. For mask stickers, the position where the mask should be placed
file_sizeIntegerOptional. File size in bytes
-

StickerSet

-

This object represents a sticker set.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
nameStringSticker set name
titleStringSticker set title
is_animatedBooleanTrue, if the sticker set contains animated stickers
contains_masksBooleanTrue, if the sticker set contains masks
stickersArray of StickerList of all set stickers
thumbPhotoSizeOptional. Sticker set thumbnail in the .WEBP or .TGS format
-

MaskPosition

-

This object describes the position on faces where a mask should be placed by default.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
pointStringThe part of the face relative to which the mask should be placed. One of "forehead", "eyes", "mouth", or "chin".
x_shiftFloat numberShift by X-axis measured in widths of the mask scaled to the face size, from left to right. For example, choosing -1.0 will place mask just to the left of the default mask position.
y_shiftFloat numberShift by Y-axis measured in heights of the mask scaled to the face size, from top to bottom. For example, 1.0 will place the mask just below the default mask position.
scaleFloat numberMask scaling coefficient. For example, 2.0 means double size.
-

sendSticker

-

Use this method to send static .WEBP or animated .TGS stickers. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
stickerInputFile or StringYesSticker to send. Pass a file_id as String to send a file that exists on the Telegram servers (recommended), pass an HTTP URL as a String for Telegram to get a .WEBP file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkup or ReplyKeyboardMarkup or ReplyKeyboardRemove or ForceReplyOptionalAdditional interface options. A JSON-serialized object for an inline keyboard, custom reply keyboard, instructions to remove reply keyboard or to force a reply from the user.
-

getStickerSet

-

Use this method to get a sticker set. On success, a StickerSet object is returned.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
nameStringYesName of the sticker set
-

uploadStickerFile

-

Use this method to upload a .PNG file with a sticker for later use in createNewStickerSet and addStickerToSet methods (can be used multiple times). Returns the uploaded File on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
user_idIntegerYesUser identifier of sticker file owner
png_stickerInputFileYesPNG image with the sticker, must be up to 512 kilobytes in size, dimensions must not exceed 512px, and either width or height must be exactly 512px. More info on Sending Files »
-

createNewStickerSet

-

Use this method to create a new sticker set owned by a user. The bot will be able to edit the sticker set thus created. You must use exactly one of the fields png_sticker or tgs_sticker. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
user_idIntegerYesUser identifier of created sticker set owner
nameStringYesShort name of sticker set, to be used in t.me/addstickers/ URLs (e.g., animals). Can contain only english letters, digits and underscores. Must begin with a letter, can't contain consecutive underscores and must end in "by<bot username>". <bot_username> is case insensitive. 1-64 characters.
titleStringYesSticker set title, 1-64 characters
png_stickerInputFile or StringOptionalPNG image with the sticker, must be up to 512 kilobytes in size, dimensions must not exceed 512px, and either width or height must be exactly 512px. Pass a file_id as a String to send a file that already exists on the Telegram servers, pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
tgs_stickerInputFileOptionalTGS animation with the sticker, uploaded using multipart/form-data. See https://core.telegram.org/animated_stickers#technical-requirements for technical requirements
emojisStringYesOne or more emoji corresponding to the sticker
contains_masksBooleanOptionalPass True, if a set of mask stickers should be created
mask_positionMaskPositionOptionalA JSON-serialized object for position where the mask should be placed on faces
-

addStickerToSet

-

Use this method to add a new sticker to a set created by the bot. You must use exactly one of the fields png_sticker or tgs_sticker. Animated stickers can be added to animated sticker sets and only to them. Animated sticker sets can have up to 50 stickers. Static sticker sets can have up to 120 stickers. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
user_idIntegerYesUser identifier of sticker set owner
nameStringYesSticker set name
png_stickerInputFile or StringOptionalPNG image with the sticker, must be up to 512 kilobytes in size, dimensions must not exceed 512px, and either width or height must be exactly 512px. Pass a file_id as a String to send a file that already exists on the Telegram servers, pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files »
tgs_stickerInputFileOptionalTGS animation with the sticker, uploaded using multipart/form-data. See https://core.telegram.org/animated_stickers#technical-requirements for technical requirements
emojisStringYesOne or more emoji corresponding to the sticker
mask_positionMaskPositionOptionalA JSON-serialized object for position where the mask should be placed on faces
-

setStickerPositionInSet

-

Use this method to move a sticker in a set created by the bot to a specific position. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
stickerStringYesFile identifier of the sticker
positionIntegerYesNew sticker position in the set, zero-based
-

deleteStickerFromSet

-

Use this method to delete a sticker from a set created by the bot. Returns True on success.

- - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
stickerStringYesFile identifier of the sticker
-

setStickerSetThumb

-

Use this method to set the thumbnail of a sticker set. Animated thumbnails can be set for animated sticker sets only. Returns True on success.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
nameStringYesSticker set name
user_idIntegerYesUser identifier of the sticker set owner
thumbInputFile or StringOptionalA PNG image with the thumbnail, must be up to 128 kilobytes in size and have width and height exactly 100px, or a TGS animation with the thumbnail up to 32 kilobytes in size; see https://core.telegram.org/animated_stickers#technical-requirements for animated sticker technical requirements. Pass a file_id as a String to send a file that already exists on the Telegram servers, pass an HTTP URL as a String for Telegram to get a file from the Internet, or upload a new one using multipart/form-data. More info on Sending Files ». Animated sticker set thumbnail can't be uploaded via HTTP URL.
-

Inline mode

-

The following methods and objects allow your bot to work in inline mode. -Please see our Introduction to Inline bots for more details.

-

To enable this option, send the /setinline command to @BotFather and provide the placeholder text that the user will see in the input field after typing your bot's name.

-

InlineQuery

-

This object represents an incoming inline query. When the user sends an empty query, your bot could return some default or trending results.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
idStringUnique identifier for this query
fromUserSender
queryStringText of the query (up to 256 characters)
offsetStringOffset of the results to be returned, can be controlled by the bot
chat_typeStringOptional. Type of the chat, from which the inline query was sent. Can be either "sender" for a private chat with the inline query sender, "private", "group", "supergroup", or "channel". The chat type should be always known for requests sent from official clients and most third-party clients, unless the request was sent from a secret chat
locationLocationOptional. Sender location, only for bots that request user location
-

answerInlineQuery

-

Use this method to send answers to an inline query. On success, True is returned. -No more than 50 results per query are allowed.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
inline_query_idStringYesUnique identifier for the answered query
resultsArray of InlineQueryResultYesA JSON-serialized array of results for the inline query
cache_timeIntegerOptionalThe maximum amount of time in seconds that the result of the inline query may be cached on the server. Defaults to 300.
is_personalBooleanOptionalPass True, if results may be cached on the server side only for the user that sent the query. By default, results may be returned to any user who sends the same query
next_offsetStringOptionalPass the offset that a client should send in the next query with the same text to receive more results. Pass an empty string if there are no more results or if you don't support pagination. Offset length can't exceed 64 bytes.
switch_pm_textStringOptionalIf passed, clients will display a button with specified text that switches the user to a private chat with the bot and sends the bot a start message with the parameter switch_pm_parameter
switch_pm_parameterStringOptionalDeep-linking parameter for the /start message sent to the bot when user presses the switch button. 1-64 characters, only A-Z, a-z, 0-9, _ and - are allowed.

Example: An inline bot that sends YouTube videos can ask the user to connect the bot to their YouTube account to adapt search results accordingly. To do this, it displays a 'Connect your YouTube account' button above the results, or even before showing any. The user presses the button, switches to a private chat with the bot and, in doing so, passes a start parameter that instructs the bot to return an OAuth link. Once done, the bot can offer a switch_inline button so that the user can easily return to the chat where they wanted to use the bot's inline capabilities.
-

InlineQueryResult

-

This object represents one result of an inline query. Telegram clients currently support results of the following 20 types:

- -

Note: All URLs passed in inline query results will be available to end users and therefore must be assumed to be public.

-

InlineQueryResultArticle

-

Represents a link to an article or web page.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be article
idStringUnique identifier for this result, 1-64 Bytes
titleStringTitle of the result
input_message_contentInputMessageContentContent of the message to be sent
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
urlStringOptional. URL of the result
hide_urlBooleanOptional. Pass True, if you don't want the URL to be shown in the message
descriptionStringOptional. Short description of the result
thumb_urlStringOptional. Url of the thumbnail for the result
thumb_widthIntegerOptional. Thumbnail width
thumb_heightIntegerOptional. Thumbnail height
-

InlineQueryResultPhoto

-

Represents a link to a photo. By default, this photo will be sent by the user with optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the photo.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be photo
idStringUnique identifier for this result, 1-64 bytes
photo_urlStringA valid URL of the photo. Photo must be in JPEG format. Photo size must not exceed 5MB
thumb_urlStringURL of the thumbnail for the photo
photo_widthIntegerOptional. Width of the photo
photo_heightIntegerOptional. Height of the photo
titleStringOptional. Title for the result
descriptionStringOptional. Short description of the result
captionStringOptional. Caption of the photo to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the photo caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the photo
-

InlineQueryResultGif

-

Represents a link to an animated GIF file. By default, this animated GIF file will be sent by the user with optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the animation.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be gif
idStringUnique identifier for this result, 1-64 bytes
gif_urlStringA valid URL for the GIF file. File size must not exceed 1MB
gif_widthIntegerOptional. Width of the GIF
gif_heightIntegerOptional. Height of the GIF
gif_durationIntegerOptional. Duration of the GIF in seconds
thumb_urlStringURL of the static (JPEG or GIF) or animated (MPEG4) thumbnail for the result
thumb_mime_typeStringOptional. MIME type of the thumbnail, must be one of "image/jpeg", "image/gif", or "video/mp4". Defaults to "image/jpeg"
titleStringOptional. Title for the result
captionStringOptional. Caption of the GIF file to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the GIF animation
-

InlineQueryResultMpeg4Gif

-

Represents a link to a video animation (H.264/MPEG-4 AVC video without sound). By default, this animated MPEG-4 file will be sent by the user with optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the animation.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be mpeg4_gif
idStringUnique identifier for this result, 1-64 bytes
mpeg4_urlStringA valid URL for the MP4 file. File size must not exceed 1MB
mpeg4_widthIntegerOptional. Video width
mpeg4_heightIntegerOptional. Video height
mpeg4_durationIntegerOptional. Video duration in seconds
thumb_urlStringURL of the static (JPEG or GIF) or animated (MPEG4) thumbnail for the result
thumb_mime_typeStringOptional. MIME type of the thumbnail, must be one of "image/jpeg", "image/gif", or "video/mp4". Defaults to "image/jpeg"
titleStringOptional. Title for the result
captionStringOptional. Caption of the MPEG-4 file to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the video animation
-

InlineQueryResultVideo

-

Represents a link to a page containing an embedded video player or a video file. By default, this video file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the video.

-
-

If an InlineQueryResultVideo message contains an embedded video (e.g., YouTube), you must replace its content using input_message_content.

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be video
idStringUnique identifier for this result, 1-64 bytes
video_urlStringA valid URL for the embedded video player or video file
mime_typeStringMime type of the content of video url, "text/html" or "video/mp4"
thumb_urlStringURL of the thumbnail (JPEG only) for the video
titleStringTitle for the result
captionStringOptional. Caption of the video to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the video caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
video_widthIntegerOptional. Video width
video_heightIntegerOptional. Video height
video_durationIntegerOptional. Video duration in seconds
descriptionStringOptional. Short description of the result
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the video. This field is required if InlineQueryResultVideo is used to send an HTML-page as a result (e.g., a YouTube video).
-

InlineQueryResultAudio

-

Represents a link to an MP3 audio file. By default, this audio file will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the audio.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be audio
idStringUnique identifier for this result, 1-64 bytes
audio_urlStringA valid URL for the audio file
titleStringTitle
captionStringOptional. Caption, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the audio caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
performerStringOptional. Performer
audio_durationIntegerOptional. Audio duration in seconds
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the audio
-

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

-

InlineQueryResultVoice

-

Represents a link to a voice recording in an .OGG container encoded with OPUS. By default, this voice recording will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the the voice message.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be voice
idStringUnique identifier for this result, 1-64 bytes
voice_urlStringA valid URL for the voice recording
titleStringRecording title
captionStringOptional. Caption, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the voice message caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
voice_durationIntegerOptional. Recording duration in seconds
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the voice recording
-

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

-

InlineQueryResultDocument

-

Represents a link to a file. By default, this file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the file. Currently, only .PDF and .ZIP files can be sent using this method.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be document
idStringUnique identifier for this result, 1-64 bytes
titleStringTitle for the result
captionStringOptional. Caption of the document to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the document caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
document_urlStringA valid URL for the file
mime_typeStringMime type of the content of the file, either "application/pdf" or "application/zip"
descriptionStringOptional. Short description of the result
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the file
thumb_urlStringOptional. URL of the thumbnail (JPEG only) for the file
thumb_widthIntegerOptional. Thumbnail width
thumb_heightIntegerOptional. Thumbnail height
-

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

-

InlineQueryResultLocation

-

Represents a location on a map. By default, the location will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the location.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be location
idStringUnique identifier for this result, 1-64 Bytes
latitudeFloat numberLocation latitude in degrees
longitudeFloat numberLocation longitude in degrees
titleStringLocation title
horizontal_accuracyFloat numberOptional. The radius of uncertainty for the location, measured in meters; 0-1500
live_periodIntegerOptional. Period in seconds for which the location can be updated, should be between 60 and 86400.
headingIntegerOptional. For live locations, a direction in which the user is moving, in degrees. Must be between 1 and 360 if specified.
proximity_alert_radiusIntegerOptional. For live locations, a maximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the location
thumb_urlStringOptional. Url of the thumbnail for the result
thumb_widthIntegerOptional. Thumbnail width
thumb_heightIntegerOptional. Thumbnail height
-

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

-

InlineQueryResultVenue

-

Represents a venue. By default, the venue will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the venue.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be venue
idStringUnique identifier for this result, 1-64 Bytes
latitudeFloatLatitude of the venue location in degrees
longitudeFloatLongitude of the venue location in degrees
titleStringTitle of the venue
addressStringAddress of the venue
foursquare_idStringOptional. Foursquare identifier of the venue if known
foursquare_typeStringOptional. Foursquare type of the venue, if known. (For example, "arts_entertainment/default", "arts_entertainment/aquarium" or "food/icecream".)
google_place_idStringOptional. Google Places identifier of the venue
google_place_typeStringOptional. Google Places type of the venue. (See supported types.)
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the venue
thumb_urlStringOptional. Url of the thumbnail for the result
thumb_widthIntegerOptional. Thumbnail width
thumb_heightIntegerOptional. Thumbnail height
-

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

-

InlineQueryResultContact

-

Represents a contact with a phone number. By default, this contact will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the contact.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be contact
idStringUnique identifier for this result, 1-64 Bytes
phone_numberStringContact's phone number
first_nameStringContact's first name
last_nameStringOptional. Contact's last name
vcardStringOptional. Additional data about the contact in the form of a vCard, 0-2048 bytes
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the contact
thumb_urlStringOptional. Url of the thumbnail for the result
thumb_widthIntegerOptional. Thumbnail width
thumb_heightIntegerOptional. Thumbnail height
-

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

-

InlineQueryResultGame

-

Represents a Game.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be game
idStringUnique identifier for this result, 1-64 bytes
game_short_nameStringShort name of the game
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
-

Note: This will only work in Telegram versions released after October 1, 2016. Older clients will not display any inline results if a game result is among them.

-

InlineQueryResultCachedPhoto

-

Represents a link to a photo stored on the Telegram servers. By default, this photo will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the photo.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be photo
idStringUnique identifier for this result, 1-64 bytes
photo_file_idStringA valid file identifier of the photo
titleStringOptional. Title for the result
descriptionStringOptional. Short description of the result
captionStringOptional. Caption of the photo to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the photo caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the photo
-

InlineQueryResultCachedGif

-

Represents a link to an animated GIF file stored on the Telegram servers. By default, this animated GIF file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with specified content instead of the animation.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be gif
idStringUnique identifier for this result, 1-64 bytes
gif_file_idStringA valid file identifier for the GIF file
titleStringOptional. Title for the result
captionStringOptional. Caption of the GIF file to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the GIF animation
-

InlineQueryResultCachedMpeg4Gif

-

Represents a link to a video animation (H.264/MPEG-4 AVC video without sound) stored on the Telegram servers. By default, this animated MPEG-4 file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the animation.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be mpeg4_gif
idStringUnique identifier for this result, 1-64 bytes
mpeg4_file_idStringA valid file identifier for the MP4 file
titleStringOptional. Title for the result
captionStringOptional. Caption of the MPEG-4 file to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the video animation
-

InlineQueryResultCachedSticker

-

Represents a link to a sticker stored on the Telegram servers. By default, this sticker will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the sticker.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be sticker
idStringUnique identifier for this result, 1-64 bytes
sticker_file_idStringA valid file identifier of the sticker
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the sticker
-

Note: This will only work in Telegram versions released after 9 April, 2016 for static stickers and after 06 July, 2019 for animated stickers. Older clients will ignore them.

-

InlineQueryResultCachedDocument

-

Represents a link to a file stored on the Telegram servers. By default, this file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the file.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be document
idStringUnique identifier for this result, 1-64 bytes
titleStringTitle for the result
document_file_idStringA valid file identifier for the file
descriptionStringOptional. Short description of the result
captionStringOptional. Caption of the document to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the document caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the file
-

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

-

InlineQueryResultCachedVideo

-

Represents a link to a video file stored on the Telegram servers. By default, this video file will be sent by the user with an optional caption. Alternatively, you can use input_message_content to send a message with the specified content instead of the video.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be video
idStringUnique identifier for this result, 1-64 bytes
video_file_idStringA valid file identifier for the video file
titleStringTitle for the result
descriptionStringOptional. Short description of the result
captionStringOptional. Caption of the video to be sent, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the video caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the video
-

InlineQueryResultCachedVoice

-

Represents a link to a voice message stored on the Telegram servers. By default, this voice message will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the voice message.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be voice
idStringUnique identifier for this result, 1-64 bytes
voice_file_idStringA valid file identifier for the voice message
titleStringVoice message title
captionStringOptional. Caption, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the voice message caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the voice message
-

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

-

InlineQueryResultCachedAudio

-

Represents a link to an MP3 audio file stored on the Telegram servers. By default, this audio file will be sent by the user. Alternatively, you can use input_message_content to send a message with the specified content instead of the audio.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringType of the result, must be audio
idStringUnique identifier for this result, 1-64 bytes
audio_file_idStringA valid file identifier for the audio file
captionStringOptional. Caption, 0-1024 characters after entities parsing
parse_modeStringOptional. Mode for parsing entities in the audio caption. See formatting options for more details.
caption_entitiesArray of MessageEntityOptional. List of special entities that appear in the caption, which can be specified instead of parse_mode
reply_markupInlineKeyboardMarkupOptional. Inline keyboard attached to the message
input_message_contentInputMessageContentOptional. Content of the message to be sent instead of the audio
-

Note: This will only work in Telegram versions released after 9 April, 2016. Older clients will ignore them.

-

InputMessageContent

-

This object represents the content of a message to be sent as a result of an inline query. Telegram clients currently support the following 5 types:

- -

InputTextMessageContent

-

Represents the content of a text message to be sent as the result of an inline query.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
message_textStringText of the message to be sent, 1-4096 characters
parse_modeStringOptional. Mode for parsing entities in the message text. See formatting options for more details.
entitiesArray of MessageEntityOptional. List of special entities that appear in message text, which can be specified instead of parse_mode
disable_web_page_previewBooleanOptional. Disables link previews for links in the sent message
-

InputLocationMessageContent

-

Represents the content of a location message to be sent as the result of an inline query.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
latitudeFloatLatitude of the location in degrees
longitudeFloatLongitude of the location in degrees
horizontal_accuracyFloat numberOptional. The radius of uncertainty for the location, measured in meters; 0-1500
live_periodIntegerOptional. Period in seconds for which the location can be updated, should be between 60 and 86400.
headingIntegerOptional. For live locations, a direction in which the user is moving, in degrees. Must be between 1 and 360 if specified.
proximity_alert_radiusIntegerOptional. For live locations, a maximum distance for proximity alerts about approaching another chat member, in meters. Must be between 1 and 100000 if specified.
-

InputVenueMessageContent

-

Represents the content of a venue message to be sent as the result of an inline query.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
latitudeFloatLatitude of the venue in degrees
longitudeFloatLongitude of the venue in degrees
titleStringName of the venue
addressStringAddress of the venue
foursquare_idStringOptional. Foursquare identifier of the venue, if known
foursquare_typeStringOptional. Foursquare type of the venue, if known. (For example, "arts_entertainment/default", "arts_entertainment/aquarium" or "food/icecream".)
google_place_idStringOptional. Google Places identifier of the venue
google_place_typeStringOptional. Google Places type of the venue. (See supported types.)
-

InputContactMessageContent

-

Represents the content of a contact message to be sent as the result of an inline query.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
phone_numberStringContact's phone number
first_nameStringContact's first name
last_nameStringOptional. Contact's last name
vcardStringOptional. Additional data about the contact in the form of a vCard, 0-2048 bytes
-

InputInvoiceMessageContent

-

Represents the content of an invoice message to be sent as the result of an inline query.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
titleStringProduct name, 1-32 characters
descriptionStringProduct description, 1-255 characters
payloadStringBot-defined invoice payload, 1-128 bytes. This will not be displayed to the user, use for your internal processes.
provider_tokenStringPayment provider token, obtained via Botfather
currencyStringThree-letter ISO 4217 currency code, see more on currencies
pricesArray of LabeledPricePrice breakdown, a JSON-serialized list of components (e.g. product price, tax, discount, delivery cost, delivery tax, bonus, etc.)
max_tip_amountIntegerOptional. The maximum accepted amount for tips in the smallest units of the currency (integer, not float/double). For example, for a maximum tip of US$ 1.45 pass max_tip_amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies). Defaults to 0
suggested_tip_amountsArray of IntegerOptional. A JSON-serialized array of suggested amounts of tip in the smallest units of the currency (integer, not float/double). At most 4 suggested tip amounts can be specified. The suggested tip amounts must be positive, passed in a strictly increased order and must not exceed max_tip_amount.
provider_dataStringOptional. A JSON-serialized object for data about the invoice, which will be shared with the payment provider. A detailed description of the required fields should be provided by the payment provider.
photo_urlStringOptional. URL of the product photo for the invoice. Can be a photo of the goods or a marketing image for a service. People like it better when they see what they are paying for.
photo_sizeIntegerOptional. Photo size
photo_widthIntegerOptional. Photo width
photo_heightIntegerOptional. Photo height
need_nameBooleanOptional. Pass True, if you require the user's full name to complete the order
need_phone_numberBooleanOptional. Pass True, if you require the user's phone number to complete the order
need_emailBooleanOptional. Pass True, if you require the user's email address to complete the order
need_shipping_addressBooleanOptional. Pass True, if you require the user's shipping address to complete the order
send_phone_number_to_providerBooleanOptional. Pass True, if user's phone number should be sent to provider
send_email_to_providerBooleanOptional. Pass True, if user's email address should be sent to provider
is_flexibleBooleanOptional. Pass True, if the final price depends on the shipping method
-

ChosenInlineResult

-

Represents a result of an inline query that was chosen by the user and sent to their chat partner.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
result_idStringThe unique identifier for the result that was chosen
fromUserThe user that chose the result
locationLocationOptional. Sender location, only for bots that require user location
inline_message_idStringOptional. Identifier of the sent inline message. Available only if there is an inline keyboard attached to the message. Will be also received in callback queries and can be used to edit the message.
queryStringThe query that was used to obtain the result
-

Note: It is necessary to enable inline feedback via @Botfather in order to receive these objects in updates.

-

Payments

-

Your bot can accept payments from Telegram users. Please see the introduction to payments for more details on the process and how to set up payments for your bot. Please note that users will need Telegram v.4.0 or higher to use payments (released on May 18, 2017).

-

sendInvoice

-

Use this method to send invoices. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idInteger or StringYesUnique identifier for the target chat or username of the target channel (in the format @channelusername)
titleStringYesProduct name, 1-32 characters
descriptionStringYesProduct description, 1-255 characters
payloadStringYesBot-defined invoice payload, 1-128 bytes. This will not be displayed to the user, use for your internal processes.
provider_tokenStringYesPayments provider token, obtained via Botfather
currencyStringYesThree-letter ISO 4217 currency code, see more on currencies
pricesArray of LabeledPriceYesPrice breakdown, a JSON-serialized list of components (e.g. product price, tax, discount, delivery cost, delivery tax, bonus, etc.)
max_tip_amountIntegerOptionalThe maximum accepted amount for tips in the smallest units of the currency (integer, not float/double). For example, for a maximum tip of US$ 1.45 pass max_tip_amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies). Defaults to 0
suggested_tip_amountsArray of IntegerOptionalA JSON-serialized array of suggested amounts of tips in the smallest units of the currency (integer, not float/double). At most 4 suggested tip amounts can be specified. The suggested tip amounts must be positive, passed in a strictly increased order and must not exceed max_tip_amount.
start_parameterStringOptionalUnique deep-linking parameter. If left empty, forwarded copies of the sent message will have a Pay button, allowing multiple users to pay directly from the forwarded message, using the same invoice. If non-empty, forwarded copies of the sent message will have a URL button with a deep link to the bot (instead of a Pay button), with the value used as the start parameter
provider_dataStringOptionalA JSON-serialized data about the invoice, which will be shared with the payment provider. A detailed description of required fields should be provided by the payment provider.
photo_urlStringOptionalURL of the product photo for the invoice. Can be a photo of the goods or a marketing image for a service. People like it better when they see what they are paying for.
photo_sizeIntegerOptionalPhoto size
photo_widthIntegerOptionalPhoto width
photo_heightIntegerOptionalPhoto height
need_nameBooleanOptionalPass True, if you require the user's full name to complete the order
need_phone_numberBooleanOptionalPass True, if you require the user's phone number to complete the order
need_emailBooleanOptionalPass True, if you require the user's email address to complete the order
need_shipping_addressBooleanOptionalPass True, if you require the user's shipping address to complete the order
send_phone_number_to_providerBooleanOptionalPass True, if user's phone number should be sent to provider
send_email_to_providerBooleanOptionalPass True, if user's email address should be sent to provider
is_flexibleBooleanOptionalPass True, if the final price depends on the shipping method
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard. If empty, one 'Pay total price' button will be shown. If not empty, the first button must be a Pay button.
-

answerShippingQuery

-

If you sent an invoice requesting a shipping address and the parameter is_flexible was specified, the Bot API will send an Update with a shipping_query field to the bot. Use this method to reply to shipping queries. On success, True is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
shipping_query_idStringYesUnique identifier for the query to be answered
okBooleanYesSpecify True if delivery to the specified address is possible and False if there are any problems (for example, if delivery to the specified address is not possible)
shipping_optionsArray of ShippingOptionOptionalRequired if ok is True. A JSON-serialized array of available shipping options.
error_messageStringOptionalRequired if ok is False. Error message in human readable form that explains why it is impossible to complete the order (e.g. "Sorry, delivery to your desired address is unavailable'). Telegram will display this message to the user.
-

answerPreCheckoutQuery

-

Once the user has confirmed their payment and shipping details, the Bot API sends the final confirmation in the form of an Update with the field pre_checkout_query. Use this method to respond to such pre-checkout queries. On success, True is returned. Note: The Bot API must receive an answer within 10 seconds after the pre-checkout query was sent.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
pre_checkout_query_idStringYesUnique identifier for the query to be answered
okBooleanYesSpecify True if everything is alright (goods are available, etc.) and the bot is ready to proceed with the order. Use False if there are any problems.
error_messageStringOptionalRequired if ok is False. Error message in human readable form that explains the reason for failure to proceed with the checkout (e.g. "Sorry, somebody just bought the last of our amazing black T-shirts while you were busy filling out your payment details. Please choose a different color or garment!"). Telegram will display this message to the user.
-

LabeledPrice

-

This object represents a portion of the price for goods or services.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
labelStringPortion label
amountIntegerPrice of the product in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
-

Invoice

-

This object contains basic information about an invoice.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
titleStringProduct name
descriptionStringProduct description
start_parameterStringUnique bot deep-linking parameter that can be used to generate this invoice
currencyStringThree-letter ISO 4217 currency code
total_amountIntegerTotal price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
-

ShippingAddress

-

This object represents a shipping address.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
country_codeStringISO 3166-1 alpha-2 country code
stateStringState, if applicable
cityStringCity
street_line1StringFirst line for the address
street_line2StringSecond line for the address
post_codeStringAddress post code
-

OrderInfo

-

This object represents information about an order.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
nameStringOptional. User name
phone_numberStringOptional. User's phone number
emailStringOptional. User email
shipping_addressShippingAddressOptional. User shipping address
-

ShippingOption

-

This object represents one shipping option.

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
idStringShipping option identifier
titleStringOption title
pricesArray of LabeledPriceList of price portions
-

SuccessfulPayment

-

This object contains basic information about a successful payment.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
currencyStringThree-letter ISO 4217 currency code
total_amountIntegerTotal price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
invoice_payloadStringBot specified invoice payload
shipping_option_idStringOptional. Identifier of the shipping option chosen by the user
order_infoOrderInfoOptional. Order info provided by the user
telegram_payment_charge_idStringTelegram payment identifier
provider_payment_charge_idStringProvider payment identifier
-

ShippingQuery

-

This object contains information about an incoming shipping query.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
idStringUnique query identifier
fromUserUser who sent the query
invoice_payloadStringBot specified invoice payload
shipping_addressShippingAddressUser specified shipping address
-

PreCheckoutQuery

-

This object contains information about an incoming pre-checkout query.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
idStringUnique query identifier
fromUserUser who sent the query
currencyStringThree-letter ISO 4217 currency code
total_amountIntegerTotal price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
invoice_payloadStringBot specified invoice payload
shipping_option_idStringOptional. Identifier of the shipping option chosen by the user
order_infoOrderInfoOptional. Order info provided by the user
-

Telegram Passport

-

Telegram Passport is a unified authorization method for services that require personal identification. Users can upload their documents once, then instantly share their data with services that require real-world ID (finance, ICOs, etc.). Please see the manual for details.

-

PassportData

-

Contains information about Telegram Passport data shared with the bot by the user.

- - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
dataArray of EncryptedPassportElementArray with information about documents and other Telegram Passport elements that was shared with the bot
credentialsEncryptedCredentialsEncrypted credentials required to decrypt the data
-

PassportFile

-

This object represents a file uploaded to Telegram Passport. Currently all Telegram Passport files are in JPEG format when decrypted and don't exceed 10MB.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_idStringIdentifier for this file, which can be used to download or reuse the file
file_unique_idStringUnique identifier for this file, which is supposed to be the same over time and for different bots. Can't be used to download or reuse the file.
file_sizeIntegerFile size in bytes
file_dateIntegerUnix time when the file was uploaded
-

EncryptedPassportElement

-

Contains information about documents or other Telegram Passport elements shared with the bot by the user.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringElement type. One of "personal_details", "passport", "driver_license", "identity_card", "internal_passport", "address", "utility_bill", "bank_statement", "rental_agreement", "passport_registration", "temporary_registration", "phone_number", "email".
dataStringOptional. Base64-encoded encrypted Telegram Passport element data provided by the user, available for "personal_details", "passport", "driver_license", "identity_card", "internal_passport" and "address" types. Can be decrypted and verified using the accompanying EncryptedCredentials.
phone_numberStringOptional. User's verified phone number, available only for "phone_number" type
emailStringOptional. User's verified email address, available only for "email" type
filesArray of PassportFileOptional. Array of encrypted files with documents provided by the user, available for "utility_bill", "bank_statement", "rental_agreement", "passport_registration" and "temporary_registration" types. Files can be decrypted and verified using the accompanying EncryptedCredentials.
front_sidePassportFileOptional. Encrypted file with the front side of the document, provided by the user. Available for "passport", "driver_license", "identity_card" and "internal_passport". The file can be decrypted and verified using the accompanying EncryptedCredentials.
reverse_sidePassportFileOptional. Encrypted file with the reverse side of the document, provided by the user. Available for "driver_license" and "identity_card". The file can be decrypted and verified using the accompanying EncryptedCredentials.
selfiePassportFileOptional. Encrypted file with the selfie of the user holding a document, provided by the user; available for "passport", "driver_license", "identity_card" and "internal_passport". The file can be decrypted and verified using the accompanying EncryptedCredentials.
translationArray of PassportFileOptional. Array of encrypted files with translated versions of documents provided by the user. Available if requested for "passport", "driver_license", "identity_card", "internal_passport", "utility_bill", "bank_statement", "rental_agreement", "passport_registration" and "temporary_registration" types. Files can be decrypted and verified using the accompanying EncryptedCredentials.
hashStringBase64-encoded element hash for using in PassportElementErrorUnspecified
-

EncryptedCredentials

-

Contains data required for decrypting and authenticating EncryptedPassportElement. See the Telegram Passport Documentation for a complete description of the data decryption and authentication processes.

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
dataStringBase64-encoded encrypted JSON-serialized data with unique user's payload, data hashes and secrets required for EncryptedPassportElement decryption and authentication
hashStringBase64-encoded data hash for data authentication
secretStringBase64-encoded secret, encrypted with the bot's public RSA key, required for data decryption
-

setPassportDataErrors

-

Informs a user that some of the Telegram Passport elements they provided contains errors. The user will not be able to re-submit their Passport to you until the errors are fixed (the contents of the field for which you returned the error must change). Returns True on success.

-

Use this if the data submitted by the user doesn't satisfy the standards your service requires for any reason. For example, if a birthday date seems invalid, a submitted document is blurry, a scan shows evidence of tampering, etc. Supply some details in the error message to make sure the user knows how to correct the issues.

- - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
user_idIntegerYesUser identifier
errorsArray of PassportElementErrorYesA JSON-serialized array describing the errors
-

PassportElementError

-

This object represents an error in the Telegram Passport element which was submitted that should be resolved by the user. It should be one of:

- -

PassportElementErrorDataField

-

Represents an issue in one of the data fields that was provided by the user. The error is considered resolved when the field's value changes.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
sourceStringError source, must be data
typeStringThe section of the user's Telegram Passport which has the error, one of "personal_details", "passport", "driver_license", "identity_card", "internal_passport", "address"
field_nameStringName of the data field which has the error
data_hashStringBase64-encoded data hash
messageStringError message
-

PassportElementErrorFrontSide

-

Represents an issue with the front side of a document. The error is considered resolved when the file with the front side of the document changes.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
sourceStringError source, must be front_side
typeStringThe section of the user's Telegram Passport which has the issue, one of "passport", "driver_license", "identity_card", "internal_passport"
file_hashStringBase64-encoded hash of the file with the front side of the document
messageStringError message
-

PassportElementErrorReverseSide

-

Represents an issue with the reverse side of a document. The error is considered resolved when the file with reverse side of the document changes.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
sourceStringError source, must be reverse_side
typeStringThe section of the user's Telegram Passport which has the issue, one of "driver_license", "identity_card"
file_hashStringBase64-encoded hash of the file with the reverse side of the document
messageStringError message
-

PassportElementErrorSelfie

-

Represents an issue with the selfie with a document. The error is considered resolved when the file with the selfie changes.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
sourceStringError source, must be selfie
typeStringThe section of the user's Telegram Passport which has the issue, one of "passport", "driver_license", "identity_card", "internal_passport"
file_hashStringBase64-encoded hash of the file with the selfie
messageStringError message
-

PassportElementErrorFile

-

Represents an issue with a document scan. The error is considered resolved when the file with the document scan changes.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
sourceStringError source, must be file
typeStringThe section of the user's Telegram Passport which has the issue, one of "utility_bill", "bank_statement", "rental_agreement", "passport_registration", "temporary_registration"
file_hashStringBase64-encoded file hash
messageStringError message
-

PassportElementErrorFiles

-

Represents an issue with a list of scans. The error is considered resolved when the list of files containing the scans changes.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
sourceStringError source, must be files
typeStringThe section of the user's Telegram Passport which has the issue, one of "utility_bill", "bank_statement", "rental_agreement", "passport_registration", "temporary_registration"
file_hashesArray of StringList of base64-encoded file hashes
messageStringError message
-

PassportElementErrorTranslationFile

-

Represents an issue with one of the files that constitute the translation of a document. The error is considered resolved when the file changes.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
sourceStringError source, must be translation_file
typeStringType of element of the user's Telegram Passport which has the issue, one of "passport", "driver_license", "identity_card", "internal_passport", "utility_bill", "bank_statement", "rental_agreement", "passport_registration", "temporary_registration"
file_hashStringBase64-encoded file hash
messageStringError message
-

PassportElementErrorTranslationFiles

-

Represents an issue with the translated version of a document. The error is considered resolved when a file with the document translation change.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
sourceStringError source, must be translation_files
typeStringType of element of the user's Telegram Passport which has the issue, one of "passport", "driver_license", "identity_card", "internal_passport", "utility_bill", "bank_statement", "rental_agreement", "passport_registration", "temporary_registration"
file_hashesArray of StringList of base64-encoded file hashes
messageStringError message
-

PassportElementErrorUnspecified

-

Represents an issue in an unspecified place. The error is considered resolved when new data is added.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
sourceStringError source, must be unspecified
typeStringType of element of the user's Telegram Passport which has the issue
element_hashStringBase64-encoded element hash
messageStringError message
-

Games

-

Your bot can offer users HTML5 games to play solo or to compete against each other in groups and one-on-one chats. Create games via @BotFather using the /newgame command. Please note that this kind of power requires responsibility: you will need to accept the terms for each game that your bots will be offering.

-
    -
  • Games are a new type of content on Telegram, represented by the Game and InlineQueryResultGame objects.
  • -
  • Once you've created a game via BotFather, you can send games to chats as regular messages using the sendGame method, or use inline mode with InlineQueryResultGame.
  • -
  • If you send the game message without any buttons, it will automatically have a 'Play GameName' button. When this button is pressed, your bot gets a CallbackQuery with the game_short_name of the requested game. You provide the correct URL for this particular user and the app opens the game in the in-app browser.
  • -
  • You can manually add multiple buttons to your game message. Please note that the first button in the first row must always launch the game, using the field callback_game in InlineKeyboardButton. You can add extra buttons according to taste: e.g., for a description of the rules, or to open the game's official community.
  • -
  • To make your game more attractive, you can upload a GIF animation that demostrates the game to the users via BotFather (see Lumberjack for example).
  • -
  • A game message will also display high scores for the current chat. Use setGameScore to post high scores to the chat with the game, add the edit_message parameter to automatically update the message with the current scoreboard.
  • -
  • Use getGameHighScores to get data for in-game high score tables.
  • -
  • You can also add an extra sharing button for users to share their best score to different chats.
  • -
  • For examples of what can be done using this new stuff, check the @gamebot and @gamee bots.
  • -
-

sendGame

-

Use this method to send a game. On success, the sent Message is returned.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
chat_idIntegerYesUnique identifier for the target chat
game_short_nameStringYesShort name of the game, serves as the unique identifier for the game. Set up your games via Botfather.
disable_notificationBooleanOptionalSends the message silently. Users will receive a notification with no sound.
reply_to_message_idIntegerOptionalIf the message is a reply, ID of the original message
allow_sending_without_replyBooleanOptionalPass True, if the message should be sent even if the specified replied-to message is not found
reply_markupInlineKeyboardMarkupOptionalA JSON-serialized object for an inline keyboard. If empty, one 'Play game_title' button will be shown. If not empty, the first button must launch the game.
-

Game

-

This object represents a game. Use BotFather to create and edit games, their short names will act as unique identifiers.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
titleStringTitle of the game
descriptionStringDescription of the game
photoArray of PhotoSizePhoto that will be displayed in the game message in chats.
textStringOptional. Brief description of the game or high scores included in the game message. Can be automatically edited to include current high scores for the game when the bot calls setGameScore, or manually edited using editMessageText. 0-4096 characters.
text_entitiesArray of MessageEntityOptional. Special entities that appear in text, such as usernames, URLs, bot commands, etc.
animationAnimationOptional. Animation that will be displayed in the game message in chats. Upload via BotFather
-

CallbackGame

-

A placeholder, currently holds no information. Use BotFather to set up your game.

-

setGameScore

-

Use this method to set the score of the specified user in a game message. On success, if the message is not an inline message, the Message is returned, otherwise True is returned. Returns an error, if the new score is not greater than the user's current score in the chat and force is False.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
user_idIntegerYesUser identifier
scoreIntegerYesNew score, must be non-negative
forceBooleanOptionalPass True, if the high score is allowed to decrease. This can be useful when fixing mistakes or banning cheaters
disable_edit_messageBooleanOptionalPass True, if the game message should not be automatically edited to include the current scoreboard
chat_idIntegerOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the sent message
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
-

getGameHighScores

-

Use this method to get data for high score tables. Will return the score of the specified user and several of their neighbors in a game. On success, returns an Array of GameHighScore objects.

-
-

This method will currently return scores for the target user, plus two of their closest neighbors on each side. Will also return the top three users if the user and his neighbors are not among them. Please note that this behavior is subject to change.

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterTypeRequiredDescription
user_idIntegerYesTarget user id
chat_idIntegerOptionalRequired if inline_message_id is not specified. Unique identifier for the target chat
message_idIntegerOptionalRequired if inline_message_id is not specified. Identifier of the sent message
inline_message_idStringOptionalRequired if chat_id and message_id are not specified. Identifier of the inline message
-

GameHighScore

-

This object represents one row of the high scores table for a game.

- - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
positionIntegerPosition in high score table for the game
userUserUser
scoreIntegerScore
-
-

And that's about all we've got for now. -If you've got any questions, please check out our Bot FAQ »

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/bots/faq.html b/data/corefork.telegram.org/bots/faq.html deleted file mode 100644 index dce13598de..0000000000 --- a/data/corefork.telegram.org/bots/faq.html +++ /dev/null @@ -1,243 +0,0 @@ - - - - - Bots FAQ - - - - - - - - - - - - - -
- -
-
-
- -

Bots FAQ

- -
-

If you are new to Telegram bots, we recommend checking out our Introduction to Bots first.
You may also find the Bot API Manual useful.

-
-

- -
-

General Questions

-

How do I create a bot?

-

Creating Telegram bots is super-easy, but you will need at least some skills at computer programming. In order for a bot to work, set up a bot account with @BotFather, then connect it to your backend server via our API.

-

Unfortunately, there are no out-of-the-box ways to create a working bot if you are not a developer. But we're sure you'll soon find plenty of bots created by other people to play with.

-

I'm a developer. Where can I find some examples?

-

Here are two sample bots, both written in PHP:

-
    -
  • Hello Bot demonstrates the basics of the Telegram bot API.
  • -
  • Simple Poll bot is a more complete example, it supports both long-polling and Webhooks for updates.
  • -
-
-

Many members of our community are building bots and publishing sources.
We're collecting them on this page »

-
-

Ping us on @BotSupport if you've built a bot and would like to share it with others.

-

Will you add X to the Bot API?

-

The bot API is still pretty young. There are many potential features to consider and implement. We'll be studying what people do with their bots for a while to see which directions will be most important for the platform.

-

All bot developers are welcome to share ideas for our Bot API with our @BotSupport account.

-

What messages will my bot get?

-

1. All bots, regardless of settings, will receive:

-
    -
  • All service messages.
  • -
  • All messages from private chats with users.
  • -
  • All messages from channels where they are a member.
  • -
-

2. Bot admins and bots with privacy mode disabled will receive all messages except messages sent by other bots.

-

3. Bots with privacy mode enabled will receive:

-
    -
  • Commands explicitly meant for them (e.g., /command@this_bot).
  • -
  • General commands from users (e.g. /start) if the bot was the last bot to send a message to the group.
  • -
  • Messages sent via this bot.
  • -
  • Replies to any messages implicitly or explicitly meant for this bot.
  • -
-

Note that each particular message can only be available to one privacy-enabled bot at a time, i.e., a reply to bot A containing an explicit command for bot B or sent via bot C will only be available to bot A. Replies have the highest priority.

-

Why doesn't my bot see messages from other bots?

-

Bots talking to each other could potentially get stuck in unwelcome loops. To avoid this, we decided that bots will not be able to see messages from other bots regardless of mode.

-

Getting Updates

-

How do I get updates?

-

There are currently two ways of getting updates. You can either use long polling or Webhooks. Please note that it's not possible to get updates via long polling while an outgoing Webhook is set.

-

Long polling gives me the same updates again and again!

-

The getUpdates method returns the earliest 100 unconfirmed updates. To confirm an update, use the offset parameter when calling getUpdates like this:

-
offset = update_id of last processed update + 1
-

All updates with update_id less than or equal to offset will be marked as confirmed on the server and will no longer be returned.

-

I'm having problems with Webhooks.

-

If you've set up your webhook successfully, but are not getting any updates, please remember:

-
    -
  • You need a valid SSL certificate for webhooks to work.
  • -
  • To use a self-signed certificate, you need to upload your public key certificate using the certificate parameter in setWebhook. Please upload as InputFile, sending a String will not work.
  • -
  • Ports currently supported for Webhooks: 443, 80, 88, 8443.
  • -
  • Wildcard certificates may not be supported.
  • -
  • Redirects are not supported.
  • -
  • CN must exactly match your domain.
  • -
-
-

Please check out this new WEBHOOK GUIDE to learn all there is to know about webhooks!

-
-

I'm having trouble with my self-signed certificate!

-

Please take a look at this self-signed certificate guide we made just for you. If you've read it and still have a question, ping us on botsupport.

-

How can I make sure that Webhook requests are coming from Telegram?

-

If you'd like to make sure that the Webhook request comes from Telegram, we recommend using a secret path in the URL you give us, e.g. www.example.com/your_token. Since nobody else knows your bot's token, you can be pretty sure it's us.

-

How can I make requests in response to updates?

-

This is possible if you're using webhooks. The upside is that you need less requests, the downside — that in this case it's not possible to know that such a request was successful or get its result.

-

Whenever you receive a webhook update, you have two options:

-

1. Issue POST to https://api.telegram.org/bot<token>/method

-
- -
- -

2. Reply directly and give method as JSON payload in the reply

-
-
- -
-

You may also want to look at our sample HelloBot, it offers a PHP implementation of this.

-
-

Handling Media

-

How do I download files?

-

Use the getFile method. Please note that this will only work with files of up to 20 MB in size.

-

How do I upload a large file?

-

Bots can currently send files of any type of up to 50 MB in size, so yes, very large files won't work for now. Sorry. This limit may be changed in the future.

-

Can I count on file_ids to be persistent?

-

Yes, file_ids can be treated as persistent.

-

Broadcasting to Users

-

My bot is hitting limits, how do I avoid this?

-

When sending messages inside a particular chat, avoid sending more than one message per second. We may allow short bursts that go over this limit, but eventually you'll begin receiving 429 errors.

-

If you're sending bulk notifications to multiple users, the API will not allow more than 30 messages per second or so. Consider spreading out notifications over large intervals of 8—12 hours for best results.

-

Also note that your bot will not be able to send more than 20 messages per minute to the same group.

-

How can I message all of my bot's subscribers at once?

-

Unfortunately, at this moment we don't have methods for sending bulk messages, e.g. notifications. We may add something along these lines in the future.

-

In order to avoid hitting our limits when sending out mass notifications, consider spreading them over longer intervals, e.g. 8-12 hours. The API will not allow bulk notifications to more than ~30 users per second, if you go over that, you'll start getting 429 errors.

-

See also: How to avoid hitting limits?

-
-
-

If you've got questions that are not answered on this page, ping us at @BotSupport in Telegram.
We welcome any suggestions for the Bot Platform and API.

-
-
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/bots/inline.html b/data/corefork.telegram.org/bots/inline.html deleted file mode 100644 index 1ff0aeee96..0000000000 --- a/data/corefork.telegram.org/bots/inline.html +++ /dev/null @@ -1,181 +0,0 @@ - - - - - Inline Bots - - - - - - - - - - - - - -
- -
-
-
- -

Inline Bots

- -
- -
- -
-

Beyond sending commands in private messages or groups, users can interact with your bot via inline queries. If inline queries are enabled, users can call your bot by typing its username and a query in the text input field in any chat. The query is sent to your bot in an update. This way, people can request content from your bot in any of their chats, groups, or channels without sending any messages at all.

-
-
-
-

To enable this option, send the /setinline command to @BotFather and provide the placeholder text that the user will see in the input field after typing your bot’s name.

-
-

See the Bot API Manual for the relevant methods and objects.

-
-

Inline results

-

Inline bots support all types of content available in Telegram (20 in all). They are capable of sending stickers, videos, music, locations, documents and more.

-
-

-
-

Clients can display the results with vertical or horizontal scrolling, depending on the type of content:

-
-
<a href="/file/811140049/2/M2mzqjZoiUw/2d872f0df2aed182d6" target="_blank"><img src="/file/811140049/2/M2mzqjZoiUw/2d872f0df2aed182d6" title="Vertical scrolling"  style="width: 295px; padding: 0px 20px;" /></a>
-

-
-
-

As soon as the user taps on an item, it's immediately sent to the recipient, and the input field is cleared.

-

Switching inline/PM modes

-

Some inline bots can benefit from an initial setup process, like connecting them to an account on an external service (e.g., YouTube). We've added an easy way of switching between the private chat with a bot and whatever chat the user wants to share inline results in.

-
-

-
-

You can display a special 'Switch to PM' button above the inline results (or instead of them). This button will open a private chat with the bot and pass a parameter of your choosing, so that you can prompt the user for the relevant setup actions. Once done, you can use an inline keyboard with a switch_inline_query button to send the user back to the original chat.

-

Sample bots -@youtube – Shows a 'Sign in to YouTube' button, then suggests personalized results.

-
-

Manual: Switch to PM

-
-

Location-based results

-

Inline bots can request location data from their users. Use the /setinlinegeo command with @BotFather to enable this. Your bot will ask the user for permission to access their location whenever they send an inline request.

-

Sample bot -@foursquare – This bot will ask for permission to access the user's location, then provide geo-targeted results.

-

Spreading virally

-

Messages sent with the help of your bot will show its username next to the sender's name.

-
-
<a href="/file/811140680/2/P3E5RVFzGZ8/5ae6f9c9610b0cbace" target="_blank"><img src="/file/811140680/2/P3E5RVFzGZ8/5ae6f9c9610b0cbace" title="Gif shared via a bot" style="width: 295px; padding: 0px 20px;" /></a>
-

-



-

When a user taps on the bot username in the message header, the mention is automatically inserted into the input field. Entering the @ symbol in the input field brings up a list of suggestions, featuring recently used inline bots.

-

Collecting feedback

-

To know which of the provided results your users are sending to their chat partners, send @Botfather the /setinlinefeedback command. With this enabled, you will receive updates on the results chosen by your users.

-

Please note that this can create load issues for popular bots – you may receive more results than actual requests due to caching (see the cache_time parameter in answerInlineQuery). For these cases, we recommend adjusting the probability setting to receive 1/10, 1/100 or 1/1000 of the results.

-

Inline bot samples

-

Here are some sample inline bots, in case you’re curious to see one in action. Try any of these: -@gif – GIF search -@vid – Video search -@pic – Yandex image search -@bing – Bing image search -@wiki – Wikipedia search -@imdb – IMDB search -@bold – Make bold, italic or fixed sys text

-

NEW -@youtube - Connect your account for personalized results -@music - Search and send classical music -@foursquare – Find and send venue addresses -@sticker – Find and send stickers based on emoji

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/bots/samples.html b/data/corefork.telegram.org/bots/samples.html deleted file mode 100644 index dda0121b96..0000000000 --- a/data/corefork.telegram.org/bots/samples.html +++ /dev/null @@ -1,249 +0,0 @@ - - - - - Bot Code Examples - - - - - - - - - - - - - -
- -
-
-
- -

Bot Code Examples

- -
-

If you want to learn more about Telegram bots, start with our Introduction to Bots »
Check out the FAQ, if you have questions.

-
-

Many members of our community are building bots and libraries and publishing their source code. We collect these examples here. Ping us on BotSupport if you've built a bot and would like to share its code with others.

-

PHP

- -

Node.js

- -

Rust

- -

Python

- -

Ruby

- -

Swift

- -

Kotlin

- -

Java

- -

Go

- -

Other Languages

- -
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/bots/samples/hellobot.html b/data/corefork.telegram.org/bots/samples/hellobot.html deleted file mode 100644 index 5ad7bd1cf8..0000000000 --- a/data/corefork.telegram.org/bots/samples/hellobot.html +++ /dev/null @@ -1,287 +0,0 @@ - - - - - Hellobot - - - - - - - - - - - - - -
- -
-
-
- -

Hellobot

- -
-

This sample PHP bot demonstrates the basics of the Telegram Bot API.
If you have questions, try our FAQ or check out this page for more examples.

-
-

- -
<?php
-
-define('BOT_TOKEN', '12345678:replace-me-with-real-token');
-define('API_URL', 'https://api.telegram.org/bot'.BOT_TOKEN.'/');
-
-function apiRequestWebhook($method, $parameters) {
-  if (!is_string($method)) {
-    error_log("Method name must be a string\n");
-    return false;
-  }
-
-  if (!$parameters) {
-    $parameters = array();
-  } else if (!is_array($parameters)) {
-    error_log("Parameters must be an array\n");
-    return false;
-  }
-
-  $parameters["method"] = $method;
-
-  $payload = json_encode($parameters);
-  header('Content-Type: application/json');
-  header('Content-Length: '.strlen($payload));
-  echo $payload;
-
-  return true;
-}
-
-function exec_curl_request($handle) {
-  $response = curl_exec($handle);
-
-  if ($response === false) {
-    $errno = curl_errno($handle);
-    $error = curl_error($handle);
-    error_log("Curl returned error $errno: $error\n");
-    curl_close($handle);
-    return false;
-  }
-
-  $http_code = intval(curl_getinfo($handle, CURLINFO_HTTP_CODE));
-  curl_close($handle);
-
-  if ($http_code >= 500) {
-    // do not wat to DDOS server if something goes wrong
-    sleep(10);
-    return false;
-  } else if ($http_code != 200) {
-    $response = json_decode($response, true);
-    error_log("Request has failed with error {$response['error_code']}: {$response['description']}\n");
-    if ($http_code == 401) {
-      throw new Exception('Invalid access token provided');
-    }
-    return false;
-  } else {
-    $response = json_decode($response, true);
-    if (isset($response['description'])) {
-      error_log("Request was successful: {$response['description']}\n");
-    }
-    $response = $response['result'];
-  }
-
-  return $response;
-}
-
-function apiRequest($method, $parameters) {
-  if (!is_string($method)) {
-    error_log("Method name must be a string\n");
-    return false;
-  }
-
-  if (!$parameters) {
-    $parameters = array();
-  } else if (!is_array($parameters)) {
-    error_log("Parameters must be an array\n");
-    return false;
-  }
-
-  foreach ($parameters as $key => &$val) {
-    // encoding to JSON array parameters, for example reply_markup
-    if (!is_numeric($val) && !is_string($val)) {
-      $val = json_encode($val);
-    }
-  }
-  $url = API_URL.$method.'?'.http_build_query($parameters);
-
-  $handle = curl_init($url);
-  curl_setopt($handle, CURLOPT_RETURNTRANSFER, true);
-  curl_setopt($handle, CURLOPT_CONNECTTIMEOUT, 5);
-  curl_setopt($handle, CURLOPT_TIMEOUT, 60);
-
-  return exec_curl_request($handle);
-}
-
-function apiRequestJson($method, $parameters) {
-  if (!is_string($method)) {
-    error_log("Method name must be a string\n");
-    return false;
-  }
-
-  if (!$parameters) {
-    $parameters = array();
-  } else if (!is_array($parameters)) {
-    error_log("Parameters must be an array\n");
-    return false;
-  }
-
-  $parameters["method"] = $method;
-
-  $handle = curl_init(API_URL);
-  curl_setopt($handle, CURLOPT_RETURNTRANSFER, true);
-  curl_setopt($handle, CURLOPT_CONNECTTIMEOUT, 5);
-  curl_setopt($handle, CURLOPT_TIMEOUT, 60);
-  curl_setopt($handle, CURLOPT_POST, true);
-  curl_setopt($handle, CURLOPT_POSTFIELDS, json_encode($parameters));
-  curl_setopt($handle, CURLOPT_HTTPHEADER, array("Content-Type: application/json"));
-
-  return exec_curl_request($handle);
-}
-
-function processMessage($message) {
-  // process incoming message
-  $message_id = $message['message_id'];
-  $chat_id = $message['chat']['id'];
-  if (isset($message['text'])) {
-    // incoming text message
-    $text = $message['text'];
-
-    if (strpos($text, "/start") === 0) {
-      apiRequestJson("sendMessage", array('chat_id' => $chat_id, "text" => 'Hello', 'reply_markup' => array(
-        'keyboard' => array(array('Hello', 'Hi')),
-        'one_time_keyboard' => true,
-        'resize_keyboard' => true)));
-    } else if ($text === "Hello" || $text === "Hi") {
-      apiRequest("sendMessage", array('chat_id' => $chat_id, "text" => 'Nice to meet you'));
-    } else if (strpos($text, "/stop") === 0) {
-      // stop now
-    } else {
-      apiRequestWebhook("sendMessage", array('chat_id' => $chat_id, "reply_to_message_id" => $message_id, "text" => 'Cool'));
-    }
-  } else {
-    apiRequest("sendMessage", array('chat_id' => $chat_id, "text" => 'I understand only text messages'));
-  }
-}
-
-
-define('WEBHOOK_URL', 'https://my-site.example.com/secret-path-for-webhooks/');
-
-if (php_sapi_name() == 'cli') {
-  // if run from console, set or delete webhook
-  apiRequest('setWebhook', array('url' => isset($argv[1]) && $argv[1] == 'delete' ? '' : WEBHOOK_URL));
-  exit;
-}
-
-
-$content = file_get_contents("php://input");
-$update = json_decode($content, true);
-
-if (!$update) {
-  // receive wrong update, must not happen
-  exit;
-}
-
-if (isset($update["message"])) {
-  processMessage($update["message"]);
-}
-
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/bots/self-signed.html b/data/corefork.telegram.org/bots/self-signed.html deleted file mode 100644 index f52296c4f2..0000000000 --- a/data/corefork.telegram.org/bots/self-signed.html +++ /dev/null @@ -1,161 +0,0 @@ - - - - - Using self-signed certificates - - - - - - - - - - - - - -
- -
-
-
- -

Using self-signed certificates

- -

Upload your certificate using the certificate parameter in the setWebhook method. The certificate supplied should be PEM encoded (ASCII BASE64), the pem file should only contain the public key (including BEGIN and END portions). When converting from a bundle format, please split the file to only include the public key.

-

Generating a self-signed certificate pair (PEM):

-

Openssl

-
-

Windows binaries for Openssl are available online

-
-

openssl req -newkey rsa:2048 -sha256 -nodes -keyout YOURPRIVATE.key -x509 -days 365 -out YOURPUBLIC.pem -subj "/C=US/ST=New York/L=Brooklyn/O=Example Brooklyn Company/CN=YOURDOMAIN.EXAMPLE"

-

YOURPUBLIC.pem has to be used as input for setting the self-signed webhook.

-

You can inspect the generated certificate with:
openssl x509 -text -noout -in YOURPUBLIC.pem

-

Converting from a previously generated DER:
openssl x509 -inform der -in YOURDER.der -out YOURPEM.pem

-

Converting from a previously generated PKCS12:
openssl pkcs12 -in YOURPKCS.p12 -out YOURPEM.pem

-
-

More information: https://www.openssl.org/

-
-

Java keystore

-

Generate self-signed JKS:
keytool -genkey -keyalg RSA -alias YOURDOMAIN.EXAMPLE -keystore YOURJKS.jks -storepass YOURPASSWORD -validity 360 -keysize 2048

-

Converting JKS to pkcs12 (intermediate step for conversion to PEM):
keytool -importkeystore -srckeystore YOURJKS.jks -destkeystore YOURPKCS.p12 -srcstoretype jks -deststoretype pkcs12

-

Convert PKCS12 to PEM (requires openssl):
openssl pkcs12 -in YOURPKCS.p12 -out YOURPEM.pem

-
-

More information: https://docs.oracle.com

-
-

Windows

-

Creating a self-signed certificate using Windows native utilities is also possible, although OpenSSL binaries for Windows are available online.

-

On the commandline:
certreq -new TEMPLATE.txt RequestFileOut

-

TEMPLATE.txt example file:

-
[NewRequest]
-
-; At least one value must be set in this section
-Subject = "CN=DOMAIN.EXAMPLE"
-KeyLength = 2048
-KeyAlgorithm = RSA
-HashAlgorithm = sha256
-;MachineKeySet = true
-RequestType = Cert
-UseExistingKeySet=false ;generates a new private key (for export)
-Exportable = true ;makes the private key exportable with the PFX
-

A self-signed certificate will be generated and installed, to view the certificate:
certutil -store -user my

-

To export in DER format (intermediate step for conversion to PEM)
certutil -user -store -split my SERIALNUMBER YOURDER.crt

-

Converting to PEM (used for setting the webhook)
certutil -encode YOURDER.crt YOURPEM.cer

-

To delete a certificate from your store:
certutil -delstore -user my SERIALNUMBER (from view)

-

To export in PFX(PKCS12) format
certutil -exportpfx -user YOURDOMAIN.EXAMPLE YOURPKCS.pfx NoChain

-
-

More information: https://technet.microsoft.com

-
-

Converting YOURPKCS.pfx to PEM including the private key is best done with OpenSSL:
openssl pkcs12 -in YOURPKCS.pfx -out YOURPEM.cer

-

Remember that only the public key is needed as input for the self-signed webhook certificate parameter. certmgr.msc can also be used as a GUI to export the public part of self-signed certificates to PEM.

-
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/bots/webhooks.html b/data/corefork.telegram.org/bots/webhooks.html deleted file mode 100644 index 1aa78ec5c3..0000000000 --- a/data/corefork.telegram.org/bots/webhooks.html +++ /dev/null @@ -1,827 +0,0 @@ - - - - - Marvin's Marvellous Guide to All Things Webhook - - - - - - - - - - - - - -
- -
-
-
- -

Marvin's Marvellous Guide to All Things Webhook

- -
- -

We currently support two ways of processing bot updates, getUpdates and setWebhook. getUpdates is a pull mechanism, setwebhook is push. Although the concept of a webhook is fairly simple, the setup of the individual components has proven to be tricky for many. This guide provides some extra information for those of you brave enough to venture into the art of the webhook.

-

There are some advantages of using a webhook over getUpdates. As soon as an update arrives, we’ll kindly deliver it to your bot for processing.

-

This:

-
1. Avoids your bot having to ask for updates frequently.
-2. Avoids the need for some kind of polling mechanism in your code.
-

Other advantages may include saving some potential CPU cycles and an increase in response time, these things however depend heavily on the usage pattern of your bot.

-

Setting a webhook means you supplying Telegram with a location in the form of a URL, on which your bot listens for updates. We need to be able to connect and post updates to that URL.

-

To ensure that we can do that, there are some basic requirements:

-

The short version

-

You'll need a server that:

-
    -
  • Supports IPv4, IPv6 is currently not supported for webhooks.
  • -
  • Accepts incoming POSTs from subnets 149.154.160.0/20 and 91.108.4.0/22 on port 443, 80, 88, or 8443.
  • -
  • Is able to handle TLS1.2(+) HTTPS-traffic.
  • -
  • Provides a supported, verified or self-signed certificate.
  • -
  • Uses a CN or SAN that matches the domain you’ve supplied on setup.
  • -
  • Supplies all intermediate certificates to complete a verification chain.
  • -
-

That’s almost all there’s to it.
If you decide to limit traffic to our specific range of addresses, keep an eye on this document whenever you seem to run into trouble. Our IP-range might change in the future.

-

The longer version

-
    -
  • A domain name

    -

    Setting a webhook needs a URL for us to post to. For that you'll need a server with a domain name. If you don't have one, you'll need to obtain one first. Telegram currently doesn't offer hosting or domain name services. There are quite a few VPS/Web hosting providers around the internet, feel free to pick one to your liking.
    If you're using a self-signed certificate, you may use the IP as a CN, instead of the domain name.
    How do I get a server with a domain name?

    -
  • -
  • An open port

    -

    A webhook needs an open port on your server. We currently support the following ports: 443, 80, 88 and 8443. Other ports are not supported and will not work. Make sure your bot is running on one of those supported ports, and that the bot is reachable via its public address.

    -
    If you want to limit access to Telegram only, please allow traffic from 149.154.167.197-233 (starting July 2019 please use: 149.154.160.0/20 and 91.108.4.0/22). 
    -Whenever something stops working in the future, please check this document again as 
    -the range might expand or change.
    -

    How do I check for open ports or limit access to my bot?

    -
  • -
  • Always SSL/TLS

    -

    A webhook requires SSL/TLS encryption, no matter which port is used. It's not possible to use a plain-text HTTP webhook. You shouldn't want to either, for the sake of your bot and users.
    SSL/TLS, why do I have to handle this for a webhook?

    -
  • -
  • Not all SSL/TLS is equal

    -

    We support any SSL/TLS version TLS1.2 and up for your webhook. This means that SSLV2/3/TLS1.0/TSL1.1 are NOT supported, due to security issues associated with those older versions.
    How do I check that I’m handling the right version?

    -
  • -
  • SSL needs a certificate

    -

    The common name (CN) of your certificate (self-signed or verified) has to match the domain name where your bot is hosted. You may also use a subject alternative name (SAN), that matches the domain for your webhook. Server Name Indication (SNI)-routing is supported. If you're using a self-signed certificate, you may use the IP as a CN, instead of the domain name.
    A certificate, where do I get one, and how?

    -
  • -
  • Verified or self-signed

    -

    A certificate can either be verified or self-signed. Setting a webhook with a self-signed certificate differs a little from setting a webhook with a verified certificate. Ensure you're using the correct setup for the type of certificate you've chosen for your webhook.
    How do I set a webhook for either type?

    -
  • -
  • Supported certificates

    -

    Not all verified certificates are supported. Certificates are based on a network of trust and come in a chain. Trusting your verified certificate means we have to trust the provider of that certificate, the Certificate Authority (and hence its root certificate). Before you pick a certificate provider, Check this list to make sure that we actually trust their root certificate.
    What if my root certificate isn’t on that list?

    -
  • -
  • An Untrusted root

    -

    Ok, so you already had a certificate installed and just discovered it’s not on our list.
    Start by ignoring it, and just try to set it. We occasionally add extra root certificates to keep up with popular demand, so the list isn't always exhaustive. Unlucky after all? We'll allow you to supply an unsupported root certificate when setting the webhook. This method is nearly identical to setting a self-signed certificate webhook. Instead of your self-signed certificate you'll be sending us the root certificate as inputFile.
    Setting a verified webhook with an untrusted root

    -
  • -
  • Intermediate certificates

    -

    Some verified certificates require an intermediate certificate. In this construction the provider of your verified certificate has used their root certificate to sign an intermediate certificate. This intermediate certificate is then used to sign your verified certificate. You'll need to provide the intermediate certificate for us to be able to verify the chain of trust. CA's that use this type of chain supply an intermediate certificate.
    Supplying an intermediate certificate

    -
  • -
  • More information

    -

    Since we know webhooks can be a tad overwhelming, we’re working on a little digital assistant that’ll try and help you with the most common problems, it's not nearly perfect, but you may try using @CanOfWormsBot to check if your chain of certificates is installed correctly before contacting support.

    -
  • -
  • Testing your bot

    -

    We took the liberty of adding a set of example updates. They come in handy when testing your bot, no matter which method of getting updates you might be using.

    -
  • -
  • Don't panic.

    -

    If by now you're looking for your fishing gear because we've mentioned ports and hooks or you're about to Google what kind of bait URL and TLS exactly are, this guide might not be completely for you. You’re quite likely still a brilliant bot programmer, don’t worry. Perhaps this whole webhook thing is just new to you, not all is lost. If you currently have a working getUpdates situation, it's a good idea to pick up this guide again on a rainy Sunday afternoon and take your time to read up on some subjects around the internet. This guide can only contain a finite amount of information after all.

    -
  • -
-

The verbose version

-
How do I get a server with a domain name?
-

If you use a webhook, we have to deliver requests to your bot to a server we can reach. So yes, you need a server we can connect to. It can be anywhere in the galaxy, if you ensure we can reach the server by domain name (or at least via IP for a self-signed certificate), it will work just fine.

-

There are quite a few ways to get this done, as a novice however it's likely that you're not directly jumping at the chance of crafting this from scratch. Actually, as a novice, we recommend you don't. It's likely to be a complex and long ride.

-

If you got stuck here, make a choice:

-
    -
  • You use getUpdates at the moment and it works, keep it that way. Especially if you're running your bot from a nice machine that does well. There is nothing wrong with using getUpdates.

    -
  • -
  • Go with a hosted service and let a bunch of professionals worry about things like registering a domain, setting up DNS, a web server, securing it and so on.

    -
  • -
-
If you're going with a hosted service, make sure to look for a hosting provider that 
-not only supports your code’s needs, for example: support for your PHP version,
-but one that also handles SSL and allows you to create/deploy certificates.
-
    -
  • Go crazy, dive on the internet and start reading. Once you’re confident that you’ve got all the basic theories down, find yourself a nice hosted VPS or roll your own machine at home and get back to us here.
  • -
-
How do I check for open ports or limit access to my bot?
-

So you have the hosting thing down and all is good so far, however, when you enter the address of your bot in your browser it seems unreachable.

-

Explaining every firewall or web server solution in detail isn't possible for us, which we hope you understand. If you’re running a hosted solution, you’re more likely to have a nice UI where you configure these settings. Head to your configuration panel and check all of them. If you’re on a Linux based VPS with shell access, we have some tips for you:

-
    -
  • Make sure your bot process is indeed configured to listen on the port you're using.
    netstat –ln | grep portnumber
    Shows you if your bot is actually listening for incoming requests on the port you expect.
    sudo lsof -i | grep process name
    Is a simple way to check if that’s actually being listened on by the process your bot is using.
  • -
-
    -
  • Make sure it’s listening correctly.
    Your bot has to listen on the address you’ve exposed to the outside (your public IP), it can also listen on all addresses (*: or 0.0.0.0).
    The netstat and lsof-commands mentioned above assist in checking this. If nothing shows up, it is time to check your configuration and fix it. Set the correct IP, make sure it’s listening on a supported port and fire away! Just use a Web Browser to check if you’re reachable. The problem can be in the configuration of your bot, your web server virtual host configuration, or the servers binding configuration.
  • -
-
    -
  • If you still can’t reach your address, check your firewall.
    sudo iptables –L
    OR
    sudo ufw status verbose (Ubuntu)
    Gives you some insight in the current firewall settings.

    -
  • -
  • If it looks like you’re blocking incoming traffic, let’s fix that.
    sudo iptables –A INPUT –p tcp –m tcp –dport portnumber -j ACCEPT
    OR
    sudo ufw allow portnumber/tcp
    Allows incoming traffic on all interfaces to the specified tcp port.
    sudo iptables –A INPUT –i interfacename –p tcp –m tcp –dport portnumber -j ACCEPT
    OR
    sudo ufw allow in on interfacename to any port portnumber proto tcp
    Allows incoming traffic to a specific interface and a specific port from everywhere.
    sudo ifconfig
    Helps you find the interface with the public address you’re going to use.

    -
  • -
-
If you use iptables, make sure to actually SAVE after changing the configuration.
-On a Debian based system the iptables-persistent package is be a good option.
-RHEL/CentOS offers a service iptables save -command.
-A quick online search for "YOUROPERATINGSYSTEM save iptables" also helps.
-
    -
  • If you’re just looking for some hints on how to limit incoming traffic:
    sudo iptables –A INPUT –i interfacename –p tcp –m iprange –src-range 149.154.167.197-149.154.167.233 –dport portnumber -j ACCEPT
    OR
    sudo ufw allow in on interfacename to any port portnumber proto tcp from 149.154.167.192/26
    Allows incoming traffic to a specific interface and a specific port from a specific range of addresses. (ufw is using a subnet mask in the example, ranging from 192-255)
  • -
-

That’s all for our examples. More information on best practices for setting up your firewall, on whichever operating system you prefer for your bot, is best found on the internet.

-
SSL/TLS, what is it and why do I have to handle this for a webhook?
-

You’re already familiar with it in some form or another. Whenever you see that (nicely green) lock in your browser bar, you know it’s reasonably safe to assume that you’ve landed on the site you actually wanted to visit. If you see the green lock, that's SSL/TLS in action. If you want to learn more about how SSL/TLS works in general, it's best to search the internet.

-

The main difference between getUpdates and a webhook is the way the connection takes place. getUpdates means you'll connect to our server, a webhook means we'll be connecting to your server instead. Connecting to your server has to be done secure, we have to know for sure it's you we're talking to after all. This means you'll have to handle all that server side encryption stuff, virtually presenting us with a green lock. If you use a web server for us to post to, you need to support SSL/TLS handling on the port/virtual host of your choice. An online search for “YOURWEBSERVER enable HTTPS” will help you.

-

Not using a regular web server? Have a look at our example page, most examples there include code for handling SSL/TLS in a webhook setup.

-
How do I check that I’m handling the right version?
-

You just read up on the whole SSL/TLS stuff, figured out that it’s not all that bad to setup and we add some more requirements. Here are some tips to check if you’re indeed supporting at least TLS1.2.

-
    -
  • Several online services exist that allow you to check your certificate installation,
    They give you an overview of your supported TLS versions/Cipher suites and other details. Search online for Symantec crypto report or Qualys ssl. Both supply tools to verify your setup.

    -
  • -
  • Checking locally can also be done, in several ways, here are three options,

    -
      -
    • Go simple:
      Using Chrome as a browser? Open up the URL to your bot and inspect the certificate details. If you’re supporting TLS Chrome tells you so in the security overview tab. Other browsers are likely able to give you similar basic information.

      -
    • -
    • Using curl:
      curl --tlsv1.2 -v -k https://yourbotdomain:yourbotport/
      You can add --tlsv1.2 to force curl into using TLS1.2 when trying to connect. -k is optional and used to check against a self-signed certificate. yourbotdomain is the public hostname your webhook is running on. For local testing purposes you can also use the IP. yourbotport is the port you’re using.

      -
    • -
    • Using OpenSSL
      openssl s_client -tls1_2 -connect yourbotdomain:yourbotport -servername yourbotdomain
      You can add -tls1_2 to force OpenSSL into using TLS1.2 when trying to connect. yourbotdomain is the public hostname your webhook is running on. For local testing purposes you can also use the IP. yourbotport is the port you’re using. Note that https:// isn’t used for OpenSSL. -servername is optional, and included here for some shared hosters, which use SNI to route traffic to the correct domain. When SNI is used you’ll notice that your server appears to be returning a certificate for a different domain than your own. Adding -servername yourbotdomain ensures that SNI negotiation is done, and the correct certificate is returned.

      -
    • -
    -
  • -
  • Some additional configuration pointers

    -
      -
    • Forcing TLS in your virtual host on Apache:
      SSLProtocol -all +TLSv1.2
    • -
    • Forcing TLS in your virtual host on Nginx:
      ssl_protocols TLSv1.2;
    • -
    • Force TLS for your Java virtual machine through system properties:
      -Dhttps.protocols=TLSv1.2 -Djdk.tls.client.protocols=TLSv1.2
    • -
    • Enabling ssl debug for your JVM:
      -Djavax.net.debug=ssl,handshake,record
    • -
    -
  • -
  • Other tools that may help in debugging issues:

    -
      -
    • Wireshark: excellent packet capturing
    • -
    • Tcpdump: equally excellent and doesn’t need a GUI
    • -
    • Charles: web debugging proxy
    • -
    • Fiddler: web debugging proxy
    • -
    -
  • -
-
A certificate, where do I get one and how?
-

You need a certificate, pick on of these types;

-
    -
  • A verified, supported certificate
  • -
  • A self-signed certificate

    -
  • -
  • A verified, supported certificate
    -

    Using a verified certificate means you already have, or will obtain, a certificate backed by a trusted certificate authority (CA). There are many ways to acquire a verified certificate, paid or free. Two popular examples of free suppliers are StartSSL and Let’s Encrypt. You’re welcome to pick another. Just make sure first the supplier is likely to be supported.
    Check this list before selecting a CA.
    Once you’ve picked a CA and validated your identity with them, you can craft your certificate. This frequently starts by generating a CSR (Certificate Signing Request). Generating a CSR is done either through your host machine, or online via the tools provided by the CA.

    -
  • -
  • Here is an example (PEM format output).

    -
      -
    • Using OpenSSL:
      openssl req -newkey rsa:2048 -keyout yourprivatekey.key -out yoursigningrequest.csr
    • -
    -
  • -
-
----
-Generating a 2048 bit RSA private keywriting new private key to yourprivatekey.key
-Enter PEM pass phrase: enter a password for your key here 
-Verifying - Enter PEM pass phrase: confirm the entered password
------
-You are about to be asked to enter information that will be incorporated
-into your certificate request.
-What you are about to enter is what is called a Distinguished Name or a DN.
-There are quite a few fields but you can leave some blank
-For some fields there will be a default value,If you enter '.',
-the field will be left blank.-----
-Country Name (2 letter code) [AU]:
-State or Province Name (full name) [Some-State]:
-Locality Name (eg, city) []:
-Organization Name (eg, company) [Internet Widgits Pty Ltd]:
-Organizational Unit Name (eg, section) []:
-Common Name (e.g. server FQDN or YOUR name) []: yourbotdomainname
-Email Address []:
-Please enter the following 'extra' attributes
-to be sent with your certificate request
-A challenge password []:
-An optional company name []:
----
-
    -
  • Another example:

    -
      -
    • Using Java keytool:
      keytool -genkey -alias yourbotdomainname -keyalg RSA -keystore yourkeystore.jks -keysize 2048
    • -
    -
  • -
-
---
-Enter keystore password:  
-Re-enter new password: 
-What is your first and last name?  [Unknown]: yourbotdomainname
-What is the name of your organizational unit?  [Unknown]:  
-What is the name of your organization?  [Unknown]:  
-What is the name of your City or Locality?  [Unknown]:  
-What is the name of your State or Province?  [Unknown]:  
-What is the two-letter country code for this unit?  [Unknown]:  
-Is CN=test.telegram.org, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown correct?  
-[no]:  yes
-Enter key password for yourbotdomainname   
-(RETURN if same as keystore password): 
----
-

This generates the initial keystore, from which you can then create a CSR like this:

-

keytool -certreq -alias yourbotdomainname -keystore yourkeystore.jks -file yourbotdomainname.csr

-
---
-Enter keystore password:
----
-

To validate your certificate the Common Name (CN) has to match your webhook domain. Example, if you’re using https://www.example.com/example.php as a webhook address, the certificate CN has to be www.example.com.
So you need an exact match of the FQDN you’re setting for the webhook

-

There is an exception, if you’re using a SAN (Subject Alternative Name) the webhook address can either match the CN of your certificate, OR one of the SANs provided in the certificate. In most cases you’ll be using the CN.

-

Create your CSR and supply the contents of the file to your CA. Most CA’s are kind enough to give you an example command of the input format they expect.

-

cat yoursigningrequest.csr or cat yourbotdomainname.csr
Lets you have a look at the CSR we just generated:

-
- -
- -

That doesn’t seem to informative, but we can deduce that the file is in PEM format (ASCII base64 encoded) and contains a certificate signing request. Luckily it is possible to look at the human readable contents of the CSR. Use the following commands to double check if all fields are set correctly.

-
    -
  • Using OpenSSL
    openssl req -text -noout -verify -in yoursigningrequest.csr

    -
  • -
  • Using Java keytool
    keytool -printcertreq -v -file yourbotdomainname.csr

    -
  • -
-

Verify your CSR and supply it to your CA to get a certificate. We’ll use StartSSL as an example here. StartSSL allows you to set up to 5 names (SAN), Their intermediate certificate is also needed for a webhook to work, which makes for a nice complete example.

-

Go to the certificates wizard, enter the required hostname(s) for your SSL certificate (this is the CN you’ve also set in the CSR and an optional SAN).

-
- -
- -

In the example above we’ve chosen to set a CN (test.telegram.org), but also a SAN (sanexample.telegram.org) The CN given has to match the CN used for generating the CSR.
Set your CN (and optional SAN) and copy the contents of the yoursigningrequest.csr file.

-
- -
- -

Paste the contents, submit and you’re done.

-
- -
- -

Now you can download the created certificate directly. In the example used above you’ll receive a zip file with several PEM certificates. The root, intermediate and yourdomain certificate.
You need the intermediate and yourdomain to set a webhook with a StartSSL certificate.

-

You can inspect the set of certificates you’ve just downloaded.

-
    -
  • Here are some example commands:

    -
      -
    • Using OpenSSL:
      openssl x509 -in yourdomain.crt -text -noout

      -
    • -
    • Using Java keytool:
      keytool -printcert -v -yourdomain.crt

      -
    • -
    • Using Windows:
      StartSSL supplies certificates in PEM format with a .crt extension, on Windows you can view the contents of them with a quick double click. Extract the files or open the “Otherserver.zip” and double click each of the certificates for inspection. The details tab supplies you with extra information.
      Make sure you have a correct CN in the Subject-field of the yourdomain-certificate. If you're using a SAN, make sure that it is listed in the Subject Alternative Name-field.

      -
    • -
    -
  • -
-
- -
- -

With your fresh certificates at hand, you can now continue setting your webhook.

-
    -
  • A self-signed certificate
    -

    Using a self-signed certificate means you’ll forfeit on the chain of trust backed by a CA. Instead you are the CA. For this to work, a slight difference in setup is required. Because Telegram will have no chain of trust to verify your certificate, you have to use the generated public certificate as an input file when setting the webhook. Keep in mind that the certificate file has to be uploaded as multipart/form data in PEM encoded (ASCII BASE64) format.

    -
  • -
  • First let’s generate some certificates:

    -
      -
    • Using OpenSSL:
      openssl req -newkey rsa:2048 -sha256 -nodes -keyout YOURPRIVATE.key -x509 -days 365 -out YOURPUBLIC.pem -subj "/C=US/ST=New York/L=Brooklyn/O=Example Brooklyn Company/CN=YOURDOMAIN.EXAMPLE"
      You’ll end up with 2 files, a private key and the public certificate file. Use YOURPUBLIC.PEM as input file for setting the webhook.

      -
    • -
    • Using Java keytool:
      keytool -genkey -keyalg RSA -alias YOURDOMAIN.EXAMPLE -keystore YOURJKS.jks -storepass YOURPASSWORD -validity 360 -keysize 2048

      -
      What is your first and last name?
      -[test.telegram.org]:
      -What is the name of your organizational unit?
      -[Unknown]:  
      -What is the name of your organization?
      -[Unknown]:  
      -What is the name of your City or Locality?
      -[Unknown]:  
      -What is the name of your State or Province?
      -[Unknown]:  
      -What is the two-letter country code for this unit?
      -[Unknown]:  
      -Is CN=test.telegram.org, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown correct?
      -[no]: yes
      -

      Once done you’ll need 2 more commands to export the public certificate file from the generated store (you’ll be using the store for your JVM and the PEM for setting the webhook)

      -
    • -
    • Convert the JKS to pkcs12 (intermediate step for conversion to PEM):
      keytool -importkeystore -srckeystore YOURJKS.jks -destkeystore YOURPKCS.p12 -srcstoretype jks -deststoretype pkcs12

      -
    • -
    • Convert PKCS12 to PEM (requires OpenSSL)
      openssl pkcs12 -in YOURPKCS.p12 -out YOURPEM.pem -nokeys

      -
    • -
    • Using Windows:
      Creating a self-signed certificate using Windows native utilities is also possible, although OpenSSL binaries for Windows are available online.
      certreq -new TEMPLATE.txt RequestFileOut generates a CSR.

      -
    • -
    • TEMPLATE.txt example file:

      -
      [NewRequest]
      -; At least one value must be set in this section
      -Subject = "CN=DOMAIN.EXAMPLE"
      -KeyLength = 2048
      -KeyAlgorithm = RSA
      -HashAlgorithm = sha256
      -;MachineKeySet = true
      -RequestType = Cert
      -UseExistingKeySet=false ;generates a new private key (for export)
      -Exportable = true ;makes the private key exportable with the PFX
      -
    • -
    -
  • -
-

A self-signed certificate is generated and installed, to use the certificate for a self-signed webhook you'll have to export it in PEM format.

-
    -
  • Windows continued:

    -
      -
    • You can have a look at the certificates in your store with:
      certutil -store -user my

      -
    • -
    • To export the installed certificate in DER format (intermediate step for conversion to PEM):
      certutil -user -store -split my SERIALNUMBER YOURDER.der

      -
    • -
    • Now you can convert the certificate to PEM:
      certutil -encode YOURDER.der YOURPEM.pem
      Remember that only the public certificate is needed as input for the self-signed webhook certificate parameter.
      certmgr.msc can also be used as a GUI to export the public part of self-signed certificate to PEM.

      -
    • -
    -
  • -
-

After following the above you'll end up with a nice self-signed certificate. You’ll still have to set the webhook, and handle SSL correctly.

-
How do I set a webhook for either type?
-

The setWebhook method is needed for both types. For a verified certificate with a trusted root CA, it’s enough to use the setWebhook method with just the URL parameter.

-
    -
  • A curl example for a verified certificate:
    curl -F "url=https://<YOURDOMAIN.EXAMPLE>/<WEBHOOKLOCATION>" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
  • -
-

For a self-signed certificate an extra parameter is needed, certificate, with the public certificate in PEM format as data.

-
    -
  • A curl example for a self-signed certificate:
    curl -F "url=https://<YOURDOMAIN.EXAMPLE>/<WEBHOOKLOCATION>" -F "certificate=@<YOURCERTIFICATE>.pem" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
  • -
-

The -F means we’re using the multipart/form-data-type to supply the certificate, the type of the certificate parameter is inputFile. Make sure that you’re supplying the correct type.

-

Both parameters for the setWebhook method are classed as optional. Calling the method with an empty URL parameter can be used to clear a previously set webhook.

-
    -
  • A curl example to clear a previous webhook :
    curl -F "url=" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
  • -
-

Keep in mind that the URL parameter starts with https:// when setting a webhook. By default that means we’re knocking at your door on port 443. If you want to use another port (80,88 or 8443), you’ll have to specify the port in the URL parameter.

-
    -
  • Example:
    url=https://<YOURDOMAIN.EXAMPLE>:88/<WEBHOOKLOCATION>
  • -
-
Setting a verified webhook with an untrusted root
-

If you already have a verified certificate and our servers don’t trust your root CA, we have an alternative way for you to set a webhook. Instead of using the setWebhook method without the certificate parameter, you can use the self-signed method. Your CA's root certificate has to be used as an inputFile for the certificate parameter.

-
    -
  • A curl example to supply an untrusted root certificate:
    curl -F "url=https://<YOURDOMAIN.EXAMPLE>" -F "certificate=@<YOURCAROOTCERTIFICATE>.pem" https://api.telegram.org/bot<YOURTOKEN>/setWebhook
    Before you can do this, you need the root certificate of your certificate’s CA. Most CA’s supply their root certificates in several different formats (PEM/DER/etc.). Visit your CA’s website, and download the Root certificate indicated for your verified certificate.
  • -
-

You can use these commands to quickly convert a DER formatted root certificate to PEM:

-
    -
  • Using OpenSSL:
    openssl x509 -inform der -in root.cer -out root.pem

    -
  • -
  • Using Java keytool:
    keytool -import -alias Root -keystore YOURKEYSTORE.JKS -trustcacerts -file ROOTCERT.CER
    The root certificate needs to be imported in your keystore first:
    keytool -exportcert -alias Root -file <YOURROOTPEMFILE.PEM> -rfc -keystore YOURKEYSTORE.JKS

    -
  • -
-

Once done, set your webhook with the root-pem-file and you’ll be good to go. If you need more pointers, have a look at the self-signed part of this guide.

-
Supplying an intermediate certificate
-

Once you’ve crafted your certificate, your CA might present you with a nice bundle. Most bundles contain a root certificate, your public certificate and sometimes an intermediate certificate. StartSSL is one of many CA’s that’ll supply such an intermediate beast. This certificate has to be supplied in the chain of certificates you’re presenting to us when we connect to your server. If an intermediate was used to sign your certificate but isn’t supplied to our servers, we won’t be able to verify the chain of trust and your webhook will not work.

-

If your webhook isn’t working and you’re wondering if the chain is complete:

-
    -
  • Check with your certificate provider if you need an intermediate certificate.
  • -
  • Verify your certificate chain.
    Search online for Symantec crypto report or Qualys ssl. 
    -Both supply tools to verify your setup.
    -
  • -
-

Here’s an example of a complete chain, note that in this case 2 intermediate certificates have been supplied.

-
- -
- -

Even though your browser might not complain when visiting your page, an incomplete chain will not work for your webhook. If your chain is incomplete we have some tips to add them to your current setup:

-
    -
  • Apache:
    Add the intermediate certificate to the end of the file configured in the SSLCertificateFile directive of your virtual host configuration. If you’re using an older version than Apache 2.4.8, you may use the SSLCertificateChainFile directive instead.

    -
  • -
  • Nginx:
    Add the intermediate certificate to the end of the file configured in the ssl_certificate_key directive of your virtual host configuration.

    -
  • -
  • A quick command for doing this correctly:
    cat your_domain_name.pem intermediate.pem >> bundle.pem
    Make sure the order is correct, expect failure otherwise.

    -
  • -
  • Java keytool:
    keytool -import -trustcacerts -alias intermediate -file intermediate.pem -keystore YOURKEYSTORE.jks

    -
  • -
-

The end result of all this is a complete certificate chain, backed by either a root certificate we trust or, in the case of an untrusted root, a root certificate you're supplying to us. Make sure to verify your setup again after adding the intermediate, once done, you're good to go!

-
Testing your bot with updates
-
    -
  • Update examples
    A set of example updates, which comes in handy for testing your bot.

    -
      -
    • Message with text using curl:

      -
      curl --tlsv1.2 -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test",
      -     "username":"Test"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test",
      -     "username":"Test"
      -  },
      -  "text":"/start"
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -

      --tlsv1.2 will force using TLS1.2.

      -
    • -
    • Message with text using Postman:

      -
      - -
      -
    • -
    -
  • -
  • More examples in curl:

    -
      -
    • Message with text:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "type": "private",
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "text":"/start"
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Forwarded message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "type": "private",
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "forward_from": {
      -     "last_name":"Forward Lastname",
      -     "id": 222222,
      -     "first_name":"Forward Firstname"
      -  },
      -  "forward_date":1441645550,
      -  "text":"/start"
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Forwarded channel message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "forward_from": {
      -     "id": -10000000000,
      -     "type": "channel",
      -     "title": "Test channel"
      -  },
      -  "forward_date":1441645550,
      -  "text":"/start"
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Message with a reply:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "text":"/start",
      -  "reply_to_message":{
      -      "date":1441645000,
      -      "chat":{
      -          "last_name":"Reply Lastname",
      -          "type": "private",
      -          "id":1111112,
      -          "first_name":"Reply Firstname",
      -          "username":"Testusername"
      -      },
      -      "message_id":1334,
      -      "text":"Original"
      -  }
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Edited message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"edited_message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "text":"Edited text",
      -  "edit_date": 1441646600
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Message with entities:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "text":"Bold and italics",
      -  "entities": [
      -      {
      -          "type": "italic",
      -          "offset": 9,
      -          "length": 7
      -      },
      -      {
      -          "type": "bold",
      -          "offset": 0,
      -          "length": 4
      -      }
      -      ]
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Message with audio:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "audio": {
      -      "file_id": "AwADBAADbXXXXXXXXXXXGBdhD2l6_XX",
      -      "duration": 243,
      -      "mime_type": "audio/mpeg",
      -      "file_size": 3897500,
      -      "title": "Test music file"
      -  }
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Voice message:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "voice": {
      -      "file_id": "AwADBAADbXXXXXXXXXXXGBdhD2l6_XX",
      -      "duration": 5,
      -      "mime_type": "audio/ogg",
      -      "file_size": 23000
      -  }
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Message with a document:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"message":{
      -  "date":1441645532,
      -  "chat":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "message_id":1365,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "document": {
      -      "file_id": "AwADBAADbXXXXXXXXXXXGBdhD2l6_XX",
      -      "file_name": "Testfile.pdf",
      -      "mime_type": "application/pdf",
      -      "file_size": 536392
      -  }
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Inline query:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"inline_query":{
      -  "id": 134567890097,
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "query": "inline query",
      -  "offset": ""
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Chosen inline query:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"chosen_inline_result":{
      -  "result_id": "12",
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "query": "inline query",
      -  "inline_message_id": "1234csdbsk4839"
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -
    • -
    • Callback query:
      curl -v -k -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache"  -d '{
      -"update_id":10000,
      -"callback_query":{
      -  "id": "4382bfdwdsb323b2d9",
      -  "from":{
      -     "last_name":"Test Lastname",
      -     "type": "private",
      -     "id":1111111,
      -     "first_name":"Test Firstname",
      -     "username":"Testusername"
      -  },
      -  "data": "Data from button callback",
      -  "inline_message_id": "1234csdbsk4839"
      -}
      -}' "https://YOUR.BOT.URL:YOURPORT/"
      -That's all we have for now!
    • -
    -
  • -
-
- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/cdn.html b/data/corefork.telegram.org/cdn.html deleted file mode 100644 index 0e92683de7..0000000000 --- a/data/corefork.telegram.org/cdn.html +++ /dev/null @@ -1,210 +0,0 @@ - - - - - Encrypted CDNs for Speed and Security - - - - - - - - - - - - - -
- -
-
-
-
-

Encrypted CDNs for Speed and Security

- -

Following the launch of version 4.2 of the official apps, Telegram client apps may be required to download popular files that were published in public channels with more than 100,000 members from secondary Content Delivery Network data centers. These CDN DCs are located in regions with significant Telegram traffic where we wouldn't want to place Telegram servers for various reasons.

-

The CDN DCs are not a part of the Telegram cloud and should be considered enemy territory. For this reason, each file that is to be sent to these CDN DCs is encrypted with a unique key using AES-256-CTR encryption. The CDN can't access the data it stores because these keys are only accessible to the main MTProto server and to the authorized client.

-
-

See also: More about CDNs and governments in the Advanced FAQ

-
-

How this works

-

When a file from a public channel with ~100,000 members becomes popular in a particular region, the Telegram server may encrypt this file with a unique AES-256-CTR key and send it to a relevant CDN DC for storage.

-

When a file is stored in a CDN DC close to the end user, the download speed will be much higher because the data needs to travel smaller distances and will likely avoid many bottlenecks that exist between regions.

-

This is secure because CDN DCs are treated the same way as internet providers / random third parties:

-
    -
  • CDN DCs don‘t have the keys to decrypt files that are stored there, so they can’t access the data even if a DC becomes compromised.
  • -
  • Encrypted files fragments are protected from tampering by their SHA-256 hash which is checked on the client upon receipt.
  • -
  • No private data is stored in or passed to the CDN DCs.
  • -
  • The server only allows media from public channels with more than 100,000 subscribers to be cached in CDN DCs (this includes media forwarded from those channels and viral media that originated from other large public channels).
  • -
-
- -
- -

CDNs are very limited when it comes to communication: the master data center only uploads encrypted files for storage and will accept no data from the CDN. The client apps only download encrypted files and accept no other updates. The client apps obtain the keys necessary to decrypt the file from the main Telegram server and verify the integrity of the file by its hash, which means that the CDN may only supply the correct file – anything different will be immediately discarded by the client.

-

CDN DCs do not store files on hard disks – only in memory. When a CDN server runs out of memory, a simple LRU algorithm is used to replace the least popular files with new ones.

-

How CDN DCs are different from the master DCs

-
    -
  • CDNs may not be trusted.
  • -
  • Client developers can use help.getCdnConfig to obtain a list of public RSA keys for CDN DCs, which are different from public RSA keys of the master DCs.
  • -
  • CDNs support only the following methods: upload.getCdnFile, initConnection, invokeWithLayer.
  • -
  • When working with CDNs, client developers must remember that auth_key may be deleted at any given moment (resulting in a -404 error, in which case a new key must be generated).
  • -
  • Client apps must not accept updates from CDN DCs (apps should only accept updates from their main connection to the master DC).
  • -
  • Clients must not allow the CDN DCs to substitute replies to queries sent to other DCs.
  • -
  • Clients must not send private user info that is passed in initConnection to the CDNs.
  • -
-

Getting files from a CDN

-

The API may return the upload.fileCdnRedirect constructor after an upload.getFile query. In this case, the client must request the required file from a CDN DC. The dc_id in the response is the id of the new CDN. The IP address for the connection will be available in help.getConfig, same as with the master DCs. The corresponding dcOption will have the flag cdn:flags.3?true.

-

Once a successful connection to the CDN-dc_id is established, the client must generate an auth_key (after confirming that the public RSA MTProto key of the CDN DC matches one from the list returned in help.getCdnConfig). Then the client must perform an upload.getCdnFile for each offset. For files of an unknown size it is necessary to repeat the query until an empty reply is returned.

-

upload.getCdnFile may return the upload.cdnFileReuploadNeeded constructor. In this case, the client needs to send an upload.reuploadCdnFile request to the DC that got the original upload.getFile request. Once upload.reuploadCdnFile is successfull, the app needs to request the file from the CDN DC again.

-

The main DC for a file is the DC where its main copy is stored (not to be confused with the main DC of the user) – either userProfilePhoto.dc_id, chatPhoto.dc_id, photo.dc_id, or document.dc_id.

-

Decrypting files

-

In upload.fileCdnRedirect, the server sends a decryption key and IV for the file (the fields encryption_key:bytes and encryption_iv:bytes respectively).

-

Having received a portion of encrypted data from the CDN DC inside upload.cdnFile, the client must decrypt this data using AES-256-CTR. For IV, it should use the value of encryption_iv, modified in the following manner: for each offset replace the last 4 bytes of the encryption_iv with offset / 16 in big-endian. This allows to effectively decrypt a file and to use random access to a file's content (e.g., for streaming).

-

Verifying files

-

In order to confirm that the CDN DC passed an untampered file, clients must verify hashes for each downloaded part. upload.fileCdnRedirect, upload.reuploadCdnFile and upload.getCdnFileHashes contain FileHash constructors. Each of these constructors contains the SHA-256 hash of a part of the file that starts with offset and takes limit bytes.

-

Before saving each portion of the data received from the CDN DC into the file, the client must confirm that its hash matches the hash that was received from the master DC. If missing a hash for any file part, client developers must use the upload.getCdnFileHashes method to obtain the missing hash.

-

Schema

-
fileHash#6242c773 offset:int limit:int hash:bytes = FileHash;
-
-upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;
-
-upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;
-upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;
-
-
-dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;
-
-cdnPublicKey#c982eaba dc_id:int public_key:string = CdnPublicKey;
-
-
-cdnConfig#5725e40a public_keys:Vector<CdnPublicKey> = CdnConfig;
-
----functions---
-
-// CDN DC
-upload.getCdnFile#2000bcc3 file_token:bytes offset:int limit:int = upload.CdnFile;
-
-// Master DC
-upload.reuploadCdnFile#9b2754a8 file_token:bytes request_token:bytes = Vector<FileHash>;
-upload.getCdnFileHashes#4da54231 file_token:bytes offset:int = Vector<FileHash>;
-
-help.getCdnConfig#52029342 = CdnConfig;
-

Restrictions on upload.getFile and upload.getCdnFile parameters

-
    -
  • offset must be divisible by 4096 bytes
  • -
  • limit must be divisible by 4096 bytes
  • -
  • 1048576 (1MB) must be divisible by limit
  • -
  • offset / (1024 * 1024) == (offset + limit - 1) / (1024 * 1024)
    (file parts that are being downloaded must always be inside the same megabyte-sized fragment)
  • -
-

Possible errors and their meanings

- - - - - - - - - - - - - - - - - - -
upload.getCdnFileFILE_TOKEN_INVALIDThe CDN DC did not accept the file_token (e.g., the token has expired). Continue downloading the file from the master DC using upload.getFile.
upload.reuploadCdnFileFILE_TOKEN_INVALIDThe master DC did not accept the file_token (e.g., the token has expired). Continue downloading the file from the master DC using upload.getFile.
upload.reuploadCdnFileREQUEST_TOKEN_INVALIDThe master DC did not accept the request_token from the CDN DC. Continue downloading the file from the master DC using upload.getFile.
-
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/account.authorizationForm b/data/corefork.telegram.org/constructor/account.authorizationForm deleted file mode 100644 index 7e64f72a2c..0000000000 --- a/data/corefork.telegram.org/constructor/account.authorizationForm +++ /dev/null @@ -1,174 +0,0 @@ - - - - - account.authorizationForm - - - - - - - - - - - - - -
- -
-
-
- -

account.authorizationForm

- -

Telegram Passport authorization form

-

- -
-
account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
required_typesVector<SecureRequiredType>Required Telegram Passport documents
valuesVector<SecureValue>Already submitted Telegram Passport documents
errorsVector<SecureValueError>Telegram Passport errors
usersVector<User>Info about the bot to which the form will be submitted
privacy_policy_urlflags.0?stringURL of the service's privacy policy
-

Type

-

account.AuthorizationForm

-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/account.authorizations b/data/corefork.telegram.org/constructor/account.authorizations deleted file mode 100644 index 88fc6c4aa7..0000000000 --- a/data/corefork.telegram.org/constructor/account.authorizations +++ /dev/null @@ -1,147 +0,0 @@ - - - - - account.authorizations - - - - - - - - - - - - - -
- -
-
-
- -

account.authorizations

- -

Logged-in sessions

-

- -
-
account.authorizations#1250abde authorizations:Vector<Authorization> = account.Authorizations;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
authorizationsVector<Authorization>Logged-in sessions
-

Type

-

account.Authorizations

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/account.autoDownloadSettings b/data/corefork.telegram.org/constructor/account.autoDownloadSettings deleted file mode 100644 index 6a0aea848a..0000000000 --- a/data/corefork.telegram.org/constructor/account.autoDownloadSettings +++ /dev/null @@ -1,157 +0,0 @@ - - - - - account.autoDownloadSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.autoDownloadSettings

- -

Media autodownload settings

-

- -
-
account.autoDownloadSettings#63cacf26 low:AutoDownloadSettings medium:AutoDownloadSettings high:AutoDownloadSettings = account.AutoDownloadSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
lowAutoDownloadSettingsLow data usage preset
mediumAutoDownloadSettingsMedium data usage preset
highAutoDownloadSettingsHigh data usage preset
-

Type

-

account.AutoDownloadSettings

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/account.chatThemes b/data/corefork.telegram.org/constructor/account.chatThemes deleted file mode 100644 index 70edb79cda..0000000000 --- a/data/corefork.telegram.org/constructor/account.chatThemes +++ /dev/null @@ -1,155 +0,0 @@ - - - - - account.chatThemes - - - - - - - - - - - - - -
- -
-
-
- -

account.chatThemes

- -

Available chat themes

-

- -
-
account.chatThemes#fe4cbebd hash:int themes:Vector<ChatTheme> = account.ChatThemes;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashintHash for pagination, for more info click here
themesVector<ChatTheme>Available chat themes
-

Type

-

account.ChatThemes

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/account.chatThemesNotModified b/data/corefork.telegram.org/constructor/account.chatThemesNotModified deleted file mode 100644 index 7a375aed64..0000000000 --- a/data/corefork.telegram.org/constructor/account.chatThemesNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - account.chatThemesNotModified - - - - - - - - - - - - - -
- -
-
-
- -

account.chatThemesNotModified

- -

The available chat themes were not modified

-

- -
-
account.chatThemesNotModified#e011e1c4 = account.ChatThemes;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

account.ChatThemes

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/account.contentSettings b/data/corefork.telegram.org/constructor/account.contentSettings deleted file mode 100644 index 3787f9e71a..0000000000 --- a/data/corefork.telegram.org/constructor/account.contentSettings +++ /dev/null @@ -1,157 +0,0 @@ - - - - - account.contentSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.contentSettings

- -

Sensitive content settings

-

- -
-
account.contentSettings#57e28221 flags:# sensitive_enabled:flags.0?true sensitive_can_change:flags.1?true = account.ContentSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
sensitive_enabledflags.0?trueWhether viewing of sensitive (NSFW) content is enabled
sensitive_can_changeflags.1?trueWhether the current client can change the sensitive content settings to view NSFW content
-

Type

-

account.ContentSettings

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/account.password b/data/corefork.telegram.org/constructor/account.password deleted file mode 100644 index 3d030ade78..0000000000 --- a/data/corefork.telegram.org/constructor/account.password +++ /dev/null @@ -1,213 +0,0 @@ - - - - - account.password - - - - - - - - - - - - - -
- -
-
-
- -

account.password

- -

Configuration for two-factor authorization

-

- -
-
account.password#185b184f flags:# has_recovery:flags.0?true has_secure_values:flags.1?true has_password:flags.2?true current_algo:flags.2?PasswordKdfAlgo srp_B:flags.2?bytes srp_id:flags.2?long hint:flags.3?string email_unconfirmed_pattern:flags.4?string new_algo:PasswordKdfAlgo new_secure_algo:SecurePasswordKdfAlgo secure_random:bytes pending_reset_date:flags.5?int = account.Password;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
has_recoveryflags.0?trueWhether the user has a recovery method configured
has_secure_valuesflags.1?trueWhether telegram passport is enabled
has_passwordflags.2?trueWhether the user has a password
current_algoflags.2?PasswordKdfAlgoThe KDF algorithm for SRP two-factor authentication of the current password
srp_Bflags.2?bytesSrp B param for SRP authorization
srp_idflags.2?longSrp ID param for SRP authorization
hintflags.3?stringText hint for the password
email_unconfirmed_patternflags.4?stringA password recovery email with the specified pattern is still awaiting verification
new_algoPasswordKdfAlgoThe KDF algorithm for SRP two-factor authentication to use when creating new passwords
new_secure_algoSecurePasswordKdfAlgoThe KDF algorithm for telegram passport
secure_randombytesSecure random string
pending_reset_dateflags.5?intThe 2FA password will be automatically removed at this date, unless the user cancels the operation
-

Type

-

account.Password

-

Related pages

-

Telegram Passport Manual

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

-

Pattern matching

-

Some methods require the client to verify if the data obtained from an external source matches a certain pattern.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/account.passwordInputSettings b/data/corefork.telegram.org/constructor/account.passwordInputSettings deleted file mode 100644 index b26e9ebc31..0000000000 --- a/data/corefork.telegram.org/constructor/account.passwordInputSettings +++ /dev/null @@ -1,176 +0,0 @@ - - - - - account.passwordInputSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.passwordInputSettings

- -

Settings for setting up a new password

-

- -
-
account.passwordInputSettings#c23727c9 flags:# new_algo:flags.0?PasswordKdfAlgo new_password_hash:flags.0?bytes hint:flags.0?string email:flags.1?string new_secure_settings:flags.2?SecureSecretSettings = account.PasswordInputSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
new_algoflags.0?PasswordKdfAlgoThe SRP algorithm to use
new_password_hashflags.0?bytesThe computed password hash
hintflags.0?stringText hint for the password
emailflags.1?stringPassword recovery email
new_secure_settingsflags.2?SecureSecretSettingsTelegram passport settings
-

Type

-

account.PasswordInputSettings

-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/account.passwordSettings b/data/corefork.telegram.org/constructor/account.passwordSettings deleted file mode 100644 index 2613d9e512..0000000000 --- a/data/corefork.telegram.org/constructor/account.passwordSettings +++ /dev/null @@ -1,161 +0,0 @@ - - - - - account.passwordSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.passwordSettings

- -

Private info associated to the password info (recovery email, telegram passport info & so on)

-

- -
-
account.passwordSettings#9a5c33e5 flags:# email:flags.0?string secure_settings:flags.1?SecureSecretSettings = account.PasswordSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
emailflags.0?string2FA Recovery email
secure_settingsflags.1?SecureSecretSettingsTelegram passport settings
-

Type

-

account.PasswordSettings

-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/account.privacyRules b/data/corefork.telegram.org/constructor/account.privacyRules deleted file mode 100644 index 6315922982..0000000000 --- a/data/corefork.telegram.org/constructor/account.privacyRules +++ /dev/null @@ -1,157 +0,0 @@ - - - - - account.privacyRules - - - - - - - - - - - - - -
- -
-
-
- -

account.privacyRules

- -

Privacy rules

-

- -
-
account.privacyRules#50a04e45 rules:Vector<PrivacyRule> chats:Vector<Chat> users:Vector<User> = account.PrivacyRules;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
rulesVector<PrivacyRule>Privacy rules
chatsVector<Chat>Chats to which the rules apply
usersVector<User>Users to which the rules apply
-

Type

-

account.PrivacyRules

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/account.resetPasswordRequestedWait b/data/corefork.telegram.org/constructor/account.resetPasswordRequestedWait deleted file mode 100644 index 2f3a926f76..0000000000 --- a/data/corefork.telegram.org/constructor/account.resetPasswordRequestedWait +++ /dev/null @@ -1,147 +0,0 @@ - - - - - account.resetPasswordRequestedWait - - - - - - - - - - - - - -
- -
-
-
- -

account.resetPasswordRequestedWait

- -

You successfully requested a password reset, please wait until the specified date before finalizing the reset.

-

- -
-
account.resetPasswordRequestedWait#e9effc7d until_date:int = account.ResetPasswordResult;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
until_dateintWait until this date before finalizing the reset.
-

Type

-

account.ResetPasswordResult

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/account.sentChangePhoneCode b/data/corefork.telegram.org/constructor/account.sentChangePhoneCode deleted file mode 100644 index 9e2c9e679d..0000000000 --- a/data/corefork.telegram.org/constructor/account.sentChangePhoneCode +++ /dev/null @@ -1,161 +0,0 @@ - - - - - account.sentChangePhoneCode - - - - - - - - - - - - - -
- -
-
-
- -

account.sentChangePhoneCode

- -

Sent change phone code

-

- -
-
Constructor schema is available as of layer 50. Switch »

-

Parameters

- - - - - - - - - - - - - -
phone_code_hashstringChange phone code hash
send_call_timeoutintCall timeout
-

Type

-

account.SentChangePhoneCode

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/account.sentEmailCode b/data/corefork.telegram.org/constructor/account.sentEmailCode deleted file mode 100644 index edf18429e3..0000000000 --- a/data/corefork.telegram.org/constructor/account.sentEmailCode +++ /dev/null @@ -1,155 +0,0 @@ - - - - - account.sentEmailCode - - - - - - - - - - - - - -
- -
-
-
- -

account.sentEmailCode

- -

The sent email code

-

- -
-
account.sentEmailCode#811f854f email_pattern:string length:int = account.SentEmailCode;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
email_patternstringThe email (to which the code was sent) must match this pattern
lengthintThe length of the verification code
-

Type

-

account.SentEmailCode

-

Related pages

-

Pattern matching

-

Some methods require the client to verify if the data obtained from an external source matches a certain pattern.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/account.takeout b/data/corefork.telegram.org/constructor/account.takeout deleted file mode 100644 index 1d4c025776..0000000000 --- a/data/corefork.telegram.org/constructor/account.takeout +++ /dev/null @@ -1,147 +0,0 @@ - - - - - account.takeout - - - - - - - - - - - - - -
- -
-
-
- -

account.takeout

- -

Takout info

-

- -
-
account.takeout#4dba4501 id:long = account.Takeout;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idlongTakeout ID
-

Type

-

account.Takeout

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/account.themes b/data/corefork.telegram.org/constructor/account.themes deleted file mode 100644 index 92e43f4e79..0000000000 --- a/data/corefork.telegram.org/constructor/account.themes +++ /dev/null @@ -1,155 +0,0 @@ - - - - - account.themes - - - - - - - - - - - - - -
- -
-
-
- -

account.themes

- -

Installed themes

-

- -
-
account.themes#9a3d8c6d hash:long themes:Vector<Theme> = account.Themes;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
themesVector<Theme>Themes
-

Type

-

account.Themes

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/account.themesNotModified b/data/corefork.telegram.org/constructor/account.themesNotModified deleted file mode 100644 index bb3eae8da3..0000000000 --- a/data/corefork.telegram.org/constructor/account.themesNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - account.themesNotModified - - - - - - - - - - - - - -
- -
-
-
- -

account.themesNotModified

- -

No new themes were installed

-

- -
-
account.themesNotModified#f41eb622 = account.Themes;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

account.Themes

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/account.tmpPassword b/data/corefork.telegram.org/constructor/account.tmpPassword deleted file mode 100644 index 516130a344..0000000000 --- a/data/corefork.telegram.org/constructor/account.tmpPassword +++ /dev/null @@ -1,152 +0,0 @@ - - - - - account.tmpPassword - - - - - - - - - - - - - -
- -
-
-
- -

account.tmpPassword

- -

Temporary payment password

-

- -
-
account.tmpPassword#db64fd34 tmp_password:bytes valid_until:int = account.TmpPassword;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
tmp_passwordbytesTemporary password
valid_untilintValidity period
-

Type

-

account.TmpPassword

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/account.wallPapers b/data/corefork.telegram.org/constructor/account.wallPapers deleted file mode 100644 index cc463c5259..0000000000 --- a/data/corefork.telegram.org/constructor/account.wallPapers +++ /dev/null @@ -1,155 +0,0 @@ - - - - - account.wallPapers - - - - - - - - - - - - - -
- -
-
-
- -

account.wallPapers

- -

Installed wallpapers

-

- -
-
account.wallPapers#cdc3858c hash:long wallpapers:Vector<WallPaper> = account.WallPapers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
wallpapersVector<WallPaper>Wallpapers
-

Type

-

account.WallPapers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/account.wallPapersNotModified b/data/corefork.telegram.org/constructor/account.wallPapersNotModified deleted file mode 100644 index e2ceba74e3..0000000000 --- a/data/corefork.telegram.org/constructor/account.wallPapersNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - account.wallPapersNotModified - - - - - - - - - - - - - -
- -
-
-
- -

account.wallPapersNotModified

- -

No new wallpapers were found

-

- -
-
account.wallPapersNotModified#1c199183 = account.WallPapers;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

account.WallPapers

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/account.webAuthorizations b/data/corefork.telegram.org/constructor/account.webAuthorizations deleted file mode 100644 index 38f69217ee..0000000000 --- a/data/corefork.telegram.org/constructor/account.webAuthorizations +++ /dev/null @@ -1,152 +0,0 @@ - - - - - account.webAuthorizations - - - - - - - - - - - - - -
- -
-
-
- -

account.webAuthorizations

- -

Web authorizations

-

- -
-
account.webAuthorizations#ed56c9fc authorizations:Vector<WebAuthorization> users:Vector<User> = account.WebAuthorizations;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
authorizationsVector<WebAuthorization>Web authorization list
usersVector<User>Users
-

Type

-

account.WebAuthorizations

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/auth.authorization b/data/corefork.telegram.org/constructor/auth.authorization deleted file mode 100644 index 5d0bc41df5..0000000000 --- a/data/corefork.telegram.org/constructor/auth.authorization +++ /dev/null @@ -1,159 +0,0 @@ - - - - - auth.authorization - - - - - - - - - - - - - -
- -
-
-
- -

auth.authorization

- -

Contains user authorization info.

-

- -
-
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
tmp_sessionsflags.0?intTemporary passport sessions
userUserInfo on authorized user
-

Type

-

auth.Authorization

-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/auth.authorizationSignUpRequired b/data/corefork.telegram.org/constructor/auth.authorizationSignUpRequired deleted file mode 100644 index 380b3b31a3..0000000000 --- a/data/corefork.telegram.org/constructor/auth.authorizationSignUpRequired +++ /dev/null @@ -1,155 +0,0 @@ - - - - - auth.authorizationSignUpRequired - - - - - - - - - - - - - -
- -
-
-
- -

auth.authorizationSignUpRequired

- -

An account with this phone number doesn't exist on telegram: the user has to enter basic information and sign up

-

- -
-
auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
terms_of_serviceflags.0?help.TermsOfServiceTelegram's terms of service: the user must read and accept the terms of service before signing up to telegram
-

Type

-

auth.Authorization

-

Related pages

-

User Authorization

-

How to register a user's phone to start using the API.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/auth.codeTypeCall b/data/corefork.telegram.org/constructor/auth.codeTypeCall deleted file mode 100644 index 5c64f53e7b..0000000000 --- a/data/corefork.telegram.org/constructor/auth.codeTypeCall +++ /dev/null @@ -1,132 +0,0 @@ - - - - - auth.codeTypeCall - - - - - - - - - - - - - -
- -
-
-
- -

auth.codeTypeCall

- -

Type of verification code that will be sent next if you call the resendCode method: SMS code

-

- -
-
auth.codeTypeCall#741cd3e3 = auth.CodeType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

auth.CodeType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/auth.codeTypeFlashCall b/data/corefork.telegram.org/constructor/auth.codeTypeFlashCall deleted file mode 100644 index 5be494073f..0000000000 --- a/data/corefork.telegram.org/constructor/auth.codeTypeFlashCall +++ /dev/null @@ -1,132 +0,0 @@ - - - - - auth.codeTypeFlashCall - - - - - - - - - - - - - -
- -
-
-
- -

auth.codeTypeFlashCall

- -

Type of verification code that will be sent next if you call the resendCode method: SMS code

-

- -
-
auth.codeTypeFlashCall#226ccefb = auth.CodeType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

auth.CodeType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/auth.codeTypeSms b/data/corefork.telegram.org/constructor/auth.codeTypeSms deleted file mode 100644 index b847ec9683..0000000000 --- a/data/corefork.telegram.org/constructor/auth.codeTypeSms +++ /dev/null @@ -1,132 +0,0 @@ - - - - - auth.codeTypeSms - - - - - - - - - - - - - -
- -
-
-
- -

auth.codeTypeSms

- -

Type of verification code that will be sent next if you call the resendCode method: SMS code

-

- -
-
auth.codeTypeSms#72a3158c = auth.CodeType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

auth.CodeType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/auth.exportedAuthorization b/data/corefork.telegram.org/constructor/auth.exportedAuthorization deleted file mode 100644 index 5437d75f47..0000000000 --- a/data/corefork.telegram.org/constructor/auth.exportedAuthorization +++ /dev/null @@ -1,152 +0,0 @@ - - - - - auth.exportedAuthorization - - - - - - - - - - - - - -
- -
-
-
- -

auth.exportedAuthorization

- -

Data for copying of authorization between data centres.

-

- -
-
auth.exportedAuthorization#b434e2b8 id:long bytes:bytes = auth.ExportedAuthorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongcurrent user identifier
bytesbytesauthorizes key
-

Type

-

auth.ExportedAuthorization

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/auth.loginToken b/data/corefork.telegram.org/constructor/auth.loginToken deleted file mode 100644 index b50034225b..0000000000 --- a/data/corefork.telegram.org/constructor/auth.loginToken +++ /dev/null @@ -1,155 +0,0 @@ - - - - - auth.loginToken - - - - - - - - - - - - - -
- -
-
-
- -

auth.loginToken

- -

Login token (for QR code login)

-

- -
-
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
expiresintExpiry date of QR code
tokenbytesToken to render in QR code
-

Type

-

auth.LoginToken

-

Related pages

-

Login via QR code

-

QR code login flow

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/auth.loginTokenMigrateTo b/data/corefork.telegram.org/constructor/auth.loginTokenMigrateTo deleted file mode 100644 index 4566afdc13..0000000000 --- a/data/corefork.telegram.org/constructor/auth.loginTokenMigrateTo +++ /dev/null @@ -1,152 +0,0 @@ - - - - - auth.loginTokenMigrateTo - - - - - - - - - - - - - -
- -
-
-
- -

auth.loginTokenMigrateTo

- -

Repeat the query to the specified DC

-

- -
-
auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
dc_idintDC ID
tokenbytesToken to use for login
-

Type

-

auth.LoginToken

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/auth.loginTokenSuccess b/data/corefork.telegram.org/constructor/auth.loginTokenSuccess deleted file mode 100644 index 5de5f5b8f6..0000000000 --- a/data/corefork.telegram.org/constructor/auth.loginTokenSuccess +++ /dev/null @@ -1,147 +0,0 @@ - - - - - auth.loginTokenSuccess - - - - - - - - - - - - - -
- -
-
-
- -

auth.loginTokenSuccess

- -

Login via token (QR code) succeded!

-

- -
-
auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
authorizationauth.AuthorizationAuthorization info
-

Type

-

auth.LoginToken

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/auth.passwordRecovery b/data/corefork.telegram.org/constructor/auth.passwordRecovery deleted file mode 100644 index 56939d5320..0000000000 --- a/data/corefork.telegram.org/constructor/auth.passwordRecovery +++ /dev/null @@ -1,152 +0,0 @@ - - - - - auth.passwordRecovery - - - - - - - - - - - - - -
- -
-
-
- -

auth.passwordRecovery

- -

Recovery info of a 2FA password, only for accounts with a recovery email configured.

-

- -
-
auth.passwordRecovery#137948a5 email_pattern:string = auth.PasswordRecovery;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
email_patternstringThe email to which the recovery code was sent must match this pattern.
-

Type

-

auth.PasswordRecovery

-

Related pages

-

Pattern matching

-

Some methods require the client to verify if the data obtained from an external source matches a certain pattern.

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/auth.sentCode b/data/corefork.telegram.org/constructor/auth.sentCode deleted file mode 100644 index b10e667322..0000000000 --- a/data/corefork.telegram.org/constructor/auth.sentCode +++ /dev/null @@ -1,172 +0,0 @@ - - - - - auth.sentCode - - - - - - - - - - - - - -
- -
-
-
- -

auth.sentCode

- -

Contains info about a sent verification code.

-

- -
-
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
typeauth.SentCodeTypePhone code type
phone_code_hashstringPhone code hash, to be stored and later re-used with auth.signIn
next_typeflags.1?auth.CodeTypePhone code type that will be sent next, if the phone code is not received within timeout seconds: to send it use auth.resendCode
timeoutflags.2?intTimeout for reception of the phone code
-

Type

-

auth.SentCode

-

Related pages

-

auth.signIn

-

Signs in a user with a validated phone number.

-

auth.resendCode

-

Resend the login code via another medium, the phone code type is determined by the return value of the previous auth.sendCode/auth.resendCode: see login for more info.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/auth.sentCodeTypeApp b/data/corefork.telegram.org/constructor/auth.sentCodeTypeApp deleted file mode 100644 index 16c24bac5b..0000000000 --- a/data/corefork.telegram.org/constructor/auth.sentCodeTypeApp +++ /dev/null @@ -1,147 +0,0 @@ - - - - - auth.sentCodeTypeApp - - - - - - - - - - - - - -
- -
-
-
- -

auth.sentCodeTypeApp

- -

The code was sent through the telegram app

-

- -
-
auth.sentCodeTypeApp#3dbb5986 length:int = auth.SentCodeType;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
lengthintLength of the code in bytes
-

Type

-

auth.SentCodeType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/auth.sentCodeTypeCall b/data/corefork.telegram.org/constructor/auth.sentCodeTypeCall deleted file mode 100644 index 94fdfe3be2..0000000000 --- a/data/corefork.telegram.org/constructor/auth.sentCodeTypeCall +++ /dev/null @@ -1,147 +0,0 @@ - - - - - auth.sentCodeTypeCall - - - - - - - - - - - - - -
- -
-
-
- -

auth.sentCodeTypeCall

- -

The code will be sent via a phone call: a synthesized voice will tell the user which verification code to input.

-

- -
-
auth.sentCodeTypeCall#5353e5a7 length:int = auth.SentCodeType;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
lengthintLength of the verification code
-

Type

-

auth.SentCodeType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/auth.sentCodeTypeFlashCall b/data/corefork.telegram.org/constructor/auth.sentCodeTypeFlashCall deleted file mode 100644 index 8882216515..0000000000 --- a/data/corefork.telegram.org/constructor/auth.sentCodeTypeFlashCall +++ /dev/null @@ -1,150 +0,0 @@ - - - - - auth.sentCodeTypeFlashCall - - - - - - - - - - - - - -
- -
-
-
- -

auth.sentCodeTypeFlashCall

- -

The code will be sent via a flash phone call, that will be closed immediately. The phone code will then be the phone number itself, just make sure that the phone number matches the specified pattern.

-

- -
-
auth.sentCodeTypeFlashCall#ab03c6d9 pattern:string = auth.SentCodeType;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
patternstringpattern to match
-

Type

-

auth.SentCodeType

-

Related pages

-

Pattern matching

-

Some methods require the client to verify if the data obtained from an external source matches a certain pattern.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/auth.sentCodeTypeSms b/data/corefork.telegram.org/constructor/auth.sentCodeTypeSms deleted file mode 100644 index 29fee12135..0000000000 --- a/data/corefork.telegram.org/constructor/auth.sentCodeTypeSms +++ /dev/null @@ -1,147 +0,0 @@ - - - - - auth.sentCodeTypeSms - - - - - - - - - - - - - -
- -
-
-
- -

auth.sentCodeTypeSms

- -

The code was sent via SMS

-

- -
-
auth.sentCodeTypeSms#c000bba2 length:int = auth.SentCodeType;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
lengthintLength of the code in bytes
-

Type

-

auth.SentCodeType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/authorization.html b/data/corefork.telegram.org/constructor/authorization.html deleted file mode 100644 index 07db698688..0000000000 --- a/data/corefork.telegram.org/constructor/authorization.html +++ /dev/null @@ -1,225 +0,0 @@ - - - - - authorization - - - - - - - - - - - - - -
- -
-
-
- -

authorization

- -

Logged-in session

-

- -
-
authorization#ad01d61d flags:# current:flags.0?true official_app:flags.1?true password_pending:flags.2?true encrypted_requests_disabled:flags.3?true call_requests_disabled:flags.4?true hash:long device_model:string platform:string system_version:string api_id:int app_name:string app_version:string date_created:int date_active:int ip:string country:string region:string = Authorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
currentflags.0?trueWhether this is the current session
official_appflags.1?trueWhether the session is from an official app
password_pendingflags.2?trueWhether the session is still waiting for a 2FA password
hashlongIdentifier
device_modelstringDevice model
platformstringPlatform
system_versionstringSystem version
api_idintAPI ID
app_namestringApp name
app_versionstringApp version
date_createdintWhen was the session created
date_activeintWhen was the session last active
ipstringLast known IP
countrystringCountry determined from IP
regionstringRegion determined from IP
-

Type

-

Authorization

-

Related pages

-

Creating your Telegram Application

-

How to get your application identifier and create a new Telegram app.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/bankCardOpenUrl.html b/data/corefork.telegram.org/constructor/bankCardOpenUrl.html deleted file mode 100644 index dc316ee3c4..0000000000 --- a/data/corefork.telegram.org/constructor/bankCardOpenUrl.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - bankCardOpenUrl - - - - - - - - - - - - - -
- -
-
-
- -

bankCardOpenUrl

- -

Credit card info URL provided by the bank

-

- -
-
bankCardOpenUrl#f568028a url:string name:string = BankCardOpenUrl;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringInfo URL
namestringBank name
-

Type

-

BankCardOpenUrl

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/baseThemeArctic.html b/data/corefork.telegram.org/constructor/baseThemeArctic.html deleted file mode 100644 index 70a64bca99..0000000000 --- a/data/corefork.telegram.org/constructor/baseThemeArctic.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - baseThemeArctic - - - - - - - - - - - - - -
- -
-
-
- -

baseThemeArctic

- -

Arctic theme

-

- -
-
baseThemeArctic#5b11125a = BaseTheme;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

BaseTheme

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/baseThemeClassic.html b/data/corefork.telegram.org/constructor/baseThemeClassic.html deleted file mode 100644 index c87acb89bc..0000000000 --- a/data/corefork.telegram.org/constructor/baseThemeClassic.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - baseThemeClassic - - - - - - - - - - - - - -
- -
-
-
- -

baseThemeClassic

- -

Classic theme

-

- -
-
baseThemeClassic#c3a12462 = BaseTheme;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

BaseTheme

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/baseThemeDay.html b/data/corefork.telegram.org/constructor/baseThemeDay.html deleted file mode 100644 index d98cba4473..0000000000 --- a/data/corefork.telegram.org/constructor/baseThemeDay.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - baseThemeDay - - - - - - - - - - - - - -
- -
-
-
- -

baseThemeDay

- -

Day theme

-

- -
-
baseThemeDay#fbd81688 = BaseTheme;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

BaseTheme

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/baseThemeNight.html b/data/corefork.telegram.org/constructor/baseThemeNight.html deleted file mode 100644 index ab45fc29ff..0000000000 --- a/data/corefork.telegram.org/constructor/baseThemeNight.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - baseThemeNight - - - - - - - - - - - - - -
- -
-
-
- -

baseThemeNight

- -

Night theme

-

- -
-
baseThemeNight#b7b31ea8 = BaseTheme;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

BaseTheme

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/baseThemeTinted.html b/data/corefork.telegram.org/constructor/baseThemeTinted.html deleted file mode 100644 index 44b988f03e..0000000000 --- a/data/corefork.telegram.org/constructor/baseThemeTinted.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - baseThemeTinted - - - - - - - - - - - - - -
- -
-
-
- -

baseThemeTinted

- -

Tinted theme

-

- -
-
baseThemeTinted#6d5f77ee = BaseTheme;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

BaseTheme

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/boolFalse.html b/data/corefork.telegram.org/constructor/boolFalse.html deleted file mode 100644 index ba2b0ff4bd..0000000000 --- a/data/corefork.telegram.org/constructor/boolFalse.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - boolFalse - - - - - - - - - - - - - -
- -
-
-
- -

boolFalse

- -

Constructor may be interpreted as a booleanfalse value.

-

- -
-
boolFalse#bc799737 = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/boolTrue.html b/data/corefork.telegram.org/constructor/boolTrue.html deleted file mode 100644 index de78d1a286..0000000000 --- a/data/corefork.telegram.org/constructor/boolTrue.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - boolTrue - - - - - - - - - - - - - -
- -
-
-
- -

boolTrue

- -

The constructor can be interpreted as a booleantrue value.

-

- -
-
boolTrue#997275b5 = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/botCommand.html b/data/corefork.telegram.org/constructor/botCommand.html deleted file mode 100644 index f35acaddef..0000000000 --- a/data/corefork.telegram.org/constructor/botCommand.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - botCommand - - - - - - - - - - - - - -
- -
-
-
- -

botCommand

- -

Describes a bot command that can be used in a chat

-

- -
-
botCommand#c27ac8c7 command:string description:string = BotCommand;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
commandstring/command name
descriptionstringDescription of the command
-

Type

-

BotCommand

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/botCommandScopeChats.html b/data/corefork.telegram.org/constructor/botCommandScopeChats.html deleted file mode 100644 index a442dfee09..0000000000 --- a/data/corefork.telegram.org/constructor/botCommandScopeChats.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - botCommandScopeChats - - - - - - - - - - - - - -
- -
-
-
- -

botCommandScopeChats

- -

The specified bot commands will be valid in all groups and supergroups.

-

- -
-
botCommandScopeChats#6fe1a881 = BotCommandScope;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

BotCommandScope

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/botCommandScopeDefault.html b/data/corefork.telegram.org/constructor/botCommandScopeDefault.html deleted file mode 100644 index bcb91f1f75..0000000000 --- a/data/corefork.telegram.org/constructor/botCommandScopeDefault.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - botCommandScopeDefault - - - - - - - - - - - - - -
- -
-
-
- -

botCommandScopeDefault

- -

The commands will be valid in all dialogs

-

- -
-
botCommandScopeDefault#2f6cb2ab = BotCommandScope;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

BotCommandScope

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/botCommandScopePeer.html b/data/corefork.telegram.org/constructor/botCommandScopePeer.html deleted file mode 100644 index eaac529e45..0000000000 --- a/data/corefork.telegram.org/constructor/botCommandScopePeer.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - botCommandScopePeer - - - - - - - - - - - - - -
- -
-
-
- -

botCommandScopePeer

- -

The specified bot commands will be valid only in a specific dialog.

-

- -
-
botCommandScopePeer#db9d897d peer:InputPeer = BotCommandScope;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe dialog
-

Type

-

BotCommandScope

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/botCommandScopePeerAdmins.html b/data/corefork.telegram.org/constructor/botCommandScopePeerAdmins.html deleted file mode 100644 index 6196f57bac..0000000000 --- a/data/corefork.telegram.org/constructor/botCommandScopePeerAdmins.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - botCommandScopePeerAdmins - - - - - - - - - - - - - -
- -
-
-
- -

botCommandScopePeerAdmins

- -

The specified bot commands will be valid for all admins of the specified group or supergroup.

-

- -
-
botCommandScopePeerAdmins#3fd863d1 peer:InputPeer = BotCommandScope;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat
-

Type

-

BotCommandScope

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/botCommandScopePeerUser.html b/data/corefork.telegram.org/constructor/botCommandScopePeerUser.html deleted file mode 100644 index ed0751e342..0000000000 --- a/data/corefork.telegram.org/constructor/botCommandScopePeerUser.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - botCommandScopePeerUser - - - - - - - - - - - - - -
- -
-
-
- -

botCommandScopePeerUser

- -

The specified bot commands will be valid only for a specific user in the specified group or supergroup.

-

- -
-
botCommandScopePeerUser#a1321f3 peer:InputPeer user_id:InputUser = BotCommandScope;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat
user_idInputUserThe user
-

Type

-

BotCommandScope

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/botCommandScopeUsers.html b/data/corefork.telegram.org/constructor/botCommandScopeUsers.html deleted file mode 100644 index ae835358a3..0000000000 --- a/data/corefork.telegram.org/constructor/botCommandScopeUsers.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - botCommandScopeUsers - - - - - - - - - - - - - -
- -
-
-
- -

botCommandScopeUsers

- -

The specified bot commands will only be valid in all private chats with users.

-

- -
-
botCommandScopeUsers#3c4f04d8 = BotCommandScope;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

BotCommandScope

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/botInfo.html b/data/corefork.telegram.org/constructor/botInfo.html deleted file mode 100644 index 4ee38aa232..0000000000 --- a/data/corefork.telegram.org/constructor/botInfo.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - botInfo - - - - - - - - - - - - - -
- -
-
-
- -

botInfo

- -

Info about bots (available bot commands, etc)

-

- -
-
botInfo#1b74b335 user_id:long description:string commands:Vector<BotCommand> = BotInfo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongID of the bot
descriptionstringDescription of the bot
commandsVector<BotCommand>Bot commands that can be used in the chat
-

Type

-

BotInfo

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/botInlineMediaResult.html b/data/corefork.telegram.org/constructor/botInlineMediaResult.html deleted file mode 100644 index bf908c01e1..0000000000 --- a/data/corefork.telegram.org/constructor/botInlineMediaResult.html +++ /dev/null @@ -1,186 +0,0 @@ - - - - - botInlineMediaResult - - - - - - - - - - - - - -
- -
-
-
- -

botInlineMediaResult

- -

Media result

-

- -
-
botInlineMediaResult#17db940b flags:# id:string type:string photo:flags.0?Photo document:flags.1?Document title:flags.2?string description:flags.3?string send_message:BotInlineMessage = BotInlineResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idstringResult ID
typestringResult type (see bot API docs)
photoflags.0?PhotoIf type is photo, the photo to send
documentflags.1?DocumentIf type is document, the document to send
titleflags.2?stringResult title
descriptionflags.3?stringDescription
send_messageBotInlineMessageDepending on the type and on the constructor, contains the caption of the media or the content of the message to be sent instead of the media
-

Type

-

BotInlineResult

-

Related pages

-

Telegram Bot API

-

BotInlineMessage

-

Inline message

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/botInlineMessageMediaAuto.html b/data/corefork.telegram.org/constructor/botInlineMessageMediaAuto.html deleted file mode 100644 index 7ca5c925b7..0000000000 --- a/data/corefork.telegram.org/constructor/botInlineMessageMediaAuto.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - botInlineMessageMediaAuto - - - - - - - - - - - - - -
- -
-
-
- -

botInlineMessageMediaAuto

- -

Send whatever media is attached to the botInlineMediaResult

-

- -
-
botInlineMessageMediaAuto#764cf810 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
messagestringCaption
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

BotInlineMessage

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

-

botInlineMediaResult

-

Media result

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/botInlineMessageMediaContact.html b/data/corefork.telegram.org/constructor/botInlineMessageMediaContact.html deleted file mode 100644 index 398dd81e87..0000000000 --- a/data/corefork.telegram.org/constructor/botInlineMessageMediaContact.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - botInlineMessageMediaContact - - - - - - - - - - - - - -
- -
-
-
- -

botInlineMessageMediaContact

- -

Send a contact

-

- -
-
botInlineMessageMediaContact#18d1cdc2 flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
phone_numberstringPhone number
first_namestringFirst name
last_namestringLast name
vcardstringVCard info
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

BotInlineMessage

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/botInlineMessageMediaInvoice.html b/data/corefork.telegram.org/constructor/botInlineMessageMediaInvoice.html deleted file mode 100644 index 12e018dc1c..0000000000 --- a/data/corefork.telegram.org/constructor/botInlineMessageMediaInvoice.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - botInlineMessageMediaInvoice - - - - - - - - - - - - - -
- -
-
-
- -

botInlineMessageMediaInvoice

- -

Send an invoice

-

- -
-
botInlineMessageMediaInvoice#354a9b09 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument currency:string total_amount:long reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
shipping_address_requestedflags.1?trueSet this flag if you require the user's shipping address to complete the order
testflags.3?trueTest invoice
titlestringProduct name, 1-32 characters
descriptionstringProduct description, 1-255 characters
photoflags.0?WebDocumentProduct photo
currencystringThree-letter ISO 4217 currency code
total_amountlongTotal price in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

BotInlineMessage

-

Related pages

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/botInlineMessageMediaVenue.html b/data/corefork.telegram.org/constructor/botInlineMessageMediaVenue.html deleted file mode 100644 index 3826313788..0000000000 --- a/data/corefork.telegram.org/constructor/botInlineMessageMediaVenue.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - botInlineMessageMediaVenue - - - - - - - - - - - - - -
- -
-
-
- -

botInlineMessageMediaVenue

- -

Send a venue

-

- -
-
botInlineMessageMediaVenue#8a86659c flags:# geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
geoGeoPointGeolocation of venue
titlestringVenue name
addressstringAddress
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
venue_typestringVenue type in the provider's database
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

BotInlineMessage

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/botInlineMessageText.html b/data/corefork.telegram.org/constructor/botInlineMessageText.html deleted file mode 100644 index ec94a66618..0000000000 --- a/data/corefork.telegram.org/constructor/botInlineMessageText.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - botInlineMessageText - - - - - - - - - - - - - -
- -
-
-
- -

botInlineMessageText

- -

Send a simple text message

-

- -
-
botInlineMessageText#8c7f65e2 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.0?trueDisable webpage preview
messagestringThe message
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

BotInlineMessage

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/botInlineResult.html b/data/corefork.telegram.org/constructor/botInlineResult.html deleted file mode 100644 index e390ffac6e..0000000000 --- a/data/corefork.telegram.org/constructor/botInlineResult.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - botInlineResult - - - - - - - - - - - - - -
- -
-
-
- -

botInlineResult

- -

Generic result

-

- -
-
botInlineResult#11965f3a flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?WebDocument content:flags.5?WebDocument send_message:BotInlineMessage = BotInlineResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idstringResult ID
typestringResult type (see bot API docs)
titleflags.1?stringResult title
descriptionflags.2?stringResult description
urlflags.3?stringURL of article or webpage
thumbflags.4?WebDocumentThumbnail for the result
contentflags.5?WebDocumentContent of the result
send_messageBotInlineMessageMessage to send
-

Type

-

BotInlineResult

-

Related pages

-

Telegram Bot API

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/cdnConfig.html b/data/corefork.telegram.org/constructor/cdnConfig.html deleted file mode 100644 index 23e34018d8..0000000000 --- a/data/corefork.telegram.org/constructor/cdnConfig.html +++ /dev/null @@ -1,149 +0,0 @@ - - - - - cdnConfig - - - - - - - - - - - - - -
- -
-
-
- -

cdnConfig

- -

Configuration for CDN file downloads.

-

- -
-
cdnConfig#5725e40a public_keys:Vector<CdnPublicKey> = CdnConfig;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
public_keysVector<CdnPublicKey>Vector of public keys to use only during handshakes to CDN DCs.
-

Type

-

CdnConfig

-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/cdnPublicKey.html b/data/corefork.telegram.org/constructor/cdnPublicKey.html deleted file mode 100644 index d2145a66a5..0000000000 --- a/data/corefork.telegram.org/constructor/cdnPublicKey.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - cdnPublicKey - - - - - - - - - - - - - -
- -
-
-
- -

cdnPublicKey

- -

Public key to use only during handshakes to CDN DCs.

-

- -
-
cdnPublicKey#c982eaba dc_id:int public_key:string = CdnPublicKey;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
dc_idintCDN DC ID
public_keystringRSA public key
-

Type

-

CdnPublicKey

-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channel.html b/data/corefork.telegram.org/constructor/channel.html deleted file mode 100644 index f1a4bd2e91..0000000000 --- a/data/corefork.telegram.org/constructor/channel.html +++ /dev/null @@ -1,289 +0,0 @@ - - - - - channel - - - - - - - - - - - - - -
- -
-
-
- -

channel

- -

Channel/supergroup info

-

- -
-
channel#8261ac61 flags:# creator:flags.0?true left:flags.2?true broadcast:flags.5?true verified:flags.7?true megagroup:flags.8?true restricted:flags.9?true signatures:flags.11?true min:flags.12?true scam:flags.19?true has_link:flags.20?true has_geo:flags.21?true slowmode_enabled:flags.22?true call_active:flags.23?true call_not_empty:flags.24?true fake:flags.25?true gigagroup:flags.26?true noforwards:flags.27?true id:long access_hash:flags.13?long title:string username:flags.6?string photo:ChatPhoto date:int restriction_reason:flags.9?Vector<RestrictionReason> admin_rights:flags.14?ChatAdminRights banned_rights:flags.15?ChatBannedRights default_banned_rights:flags.18?ChatBannedRights participants_count:flags.17?int = Chat;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
creatorflags.0?trueWhether the current user is the creator of this channel
leftflags.2?trueWhether the current user has left this channel
broadcastflags.5?trueIs this a channel?
verifiedflags.7?trueIs this channel verified by telegram?
megagroupflags.8?trueIs this a supergroup?
restrictedflags.9?trueWhether viewing/writing in this channel for a reason (see restriction_reason
signaturesflags.11?trueWhether signatures are enabled (channels)
minflags.12?trueSee min
scamflags.19?trueThis channel/supergroup is probably a scam
has_linkflags.20?trueWhether this channel has a private join link
has_geoflags.21?trueWhether this chanel has a geoposition
slowmode_enabledflags.22?trueWhether slow mode is enabled for groups to prevent flood in chat
call_activeflags.23?trueWhether a group call or livestream is currently active
call_not_emptyflags.24?trueWhether there's anyone in the group call or livestream
fakeflags.25?trueIf set, this supergroup/channel was reported by many users as a fake or scam: be careful when interacting with it.
gigagroupflags.26?trueWhether this supergroup is a gigagroup
idlongID of the channel
access_hashflags.13?longAccess hash
titlestringTitle
usernameflags.6?stringUsername
photoChatPhotoProfile photo
dateintDate when the user joined the supergroup/channel, or if the user isn't a member, its creation date
restriction_reasonflags.9?Vector<RestrictionReason>Contains the reason why access to this channel must be restricted.
admin_rightsflags.14?ChatAdminRightsAdmin rights of the user in this channel (see rights)
banned_rightsflags.15?ChatBannedRightsBanned rights of the user in this channel (see rights)
default_banned_rightsflags.18?ChatBannedRightsDefault chat rights (see rights)
participants_countflags.17?intParticipant count
-

Type

-

Chat

-

Related pages

-

Min constructors

-

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

Admin, banned, default rights

-

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEvent.html b/data/corefork.telegram.org/constructor/channelAdminLogEvent.html deleted file mode 100644 index 6324192588..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEvent.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - channelAdminLogEvent - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEvent

- -

Admin log event

-

- -
-
channelAdminLogEvent#1fad68cd id:long date:int user_id:long action:ChannelAdminLogEventAction = ChannelAdminLogEvent;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongEvent ID
dateintDate
user_idlongUser ID
actionChannelAdminLogEventActionAction
-

Type

-

ChannelAdminLogEvent

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeAbout.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeAbout.html deleted file mode 100644 index 9d201a2d4a..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeAbout.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionChangeAbout - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionChangeAbout

- -

The description was changed

-

- -
-
channelAdminLogEventActionChangeAbout#55188a2e prev_value:string new_value:string = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_valuestringPrevious description
new_valuestringNew description
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeHistoryTTL.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeHistoryTTL.html deleted file mode 100644 index cdb898d581..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeHistoryTTL.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionChangeHistoryTTL - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionChangeHistoryTTL

- -

The Time-To-Live of messages in this chat was changed

-

- -
-
channelAdminLogEventActionChangeHistoryTTL#6e941a38 prev_value:int new_value:int = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_valueintPrevious value
new_valueintNew value
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html deleted file mode 100644 index 19bd232664..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeLinkedChat.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionChangeLinkedChat - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionChangeLinkedChat

- -

The linked chat was changed

-

- -
-
channelAdminLogEventActionChangeLinkedChat#50c7ac8 prev_value:long new_value:long = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_valuelongPrevious linked chat
new_valuelongNew linked chat
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html deleted file mode 100644 index c0769c088f..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionChangeLocation - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionChangeLocation

- -

The geogroup location was changed

-

- -
-
channelAdminLogEventActionChangeLocation#e6b76ae prev_value:ChannelLocation new_value:ChannelLocation = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_valueChannelLocationPrevious location
new_valueChannelLocationNew location
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangePhoto.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangePhoto.html deleted file mode 100644 index 2d5f5b0564..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangePhoto.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionChangePhoto - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionChangePhoto

- -

The channel/supergroup's picture was changed

-

- -
-
channelAdminLogEventActionChangePhoto#434bd2af prev_photo:Photo new_photo:Photo = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_photoPhotoPrevious picture
new_photoPhotoNew picture
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html deleted file mode 100644 index 6426609bff..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeStickerSet.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionChangeStickerSet - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionChangeStickerSet

- -

The supergroup's stickerset was changed

-

- -
-
channelAdminLogEventActionChangeStickerSet#b1c3caa7 prev_stickerset:InputStickerSet new_stickerset:InputStickerSet = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_stickersetInputStickerSetPrevious stickerset
new_stickersetInputStickerSetNew stickerset
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeTitle.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeTitle.html deleted file mode 100644 index 159bdb5153..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeTitle.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionChangeTitle - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionChangeTitle

- -

Channel/supergroup title was changed

-

- -
-
channelAdminLogEventActionChangeTitle#e6dfb825 prev_value:string new_value:string = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_valuestringPrevious title
new_valuestringNew title
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html deleted file mode 100644 index 2f23e33046..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeUsername.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionChangeUsername - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionChangeUsername

- -

Channel/supergroup username was changed

-

- -
-
channelAdminLogEventActionChangeUsername#6a4afc38 prev_value:string new_value:string = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_valuestringOld username
new_valuestringNew username
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionDefaultBannedRights.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionDefaultBannedRights.html deleted file mode 100644 index d420422b56..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionDefaultBannedRights.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - channelAdminLogEventActionDefaultBannedRights - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionDefaultBannedRights

- -

The default banned rights were modified

-

- -
-
channelAdminLogEventActionDefaultBannedRights#2df5fc0a prev_banned_rights:ChatBannedRights new_banned_rights:ChatBannedRights = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_banned_rightsChatBannedRightsPrevious global banned rights
new_banned_rightsChatBannedRightsNew glboal banned rights.
-

Type

-

ChannelAdminLogEventAction

-

Related pages

-

Admin, banned, default rights

-

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionDeleteMessage.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionDeleteMessage.html deleted file mode 100644 index 50663f36d4..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionDeleteMessage.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionDeleteMessage - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionDeleteMessage

- -

A message was deleted

-

- -
-
channelAdminLogEventActionDeleteMessage#42e047bb message:Message = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageThe message that was deleted
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionDiscardGroupCall.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionDiscardGroupCall.html deleted file mode 100644 index 417be37bc8..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionDiscardGroupCall.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionDiscardGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionDiscardGroupCall

- -

A group call was terminated

-

- -
-
channelAdminLogEventActionDiscardGroupCall#db9f9140 call:InputGroupCall = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallThe group call that was terminated
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionEditMessage.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionEditMessage.html deleted file mode 100644 index 5f81277fc4..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionEditMessage.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionEditMessage - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionEditMessage

- -

A message was edited

-

- -
-
channelAdminLogEventActionEditMessage#709b2405 prev_message:Message new_message:Message = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_messageMessageOld message
new_messageMessageNew message
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteDelete.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteDelete.html deleted file mode 100644 index 95c8e3fa63..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteDelete.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionExportedInviteDelete - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionExportedInviteDelete

- -

A chat invite was deleted

-

- -
-
channelAdminLogEventActionExportedInviteDelete#5a50fca4 invite:ExportedChatInvite = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
inviteExportedChatInviteThe deleted chat invite
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteEdit.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteEdit.html deleted file mode 100644 index 3f322f37eb..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteEdit.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelAdminLogEventActionExportedInviteEdit - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionExportedInviteEdit

- -

A chat invite was edited

-

- -
-
channelAdminLogEventActionExportedInviteEdit#e90ebb59 prev_invite:ExportedChatInvite new_invite:ExportedChatInvite = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_inviteExportedChatInvitePrevious chat invite information
new_inviteExportedChatInviteNew chat invite information
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteRevoke.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteRevoke.html deleted file mode 100644 index 1928957df8..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteRevoke.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionExportedInviteRevoke - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionExportedInviteRevoke

- -

A specific invite link was revoked

-

- -
-
channelAdminLogEventActionExportedInviteRevoke#410a134e invite:ExportedChatInvite = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
inviteExportedChatInviteThe invite link that was revoked
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantInvite.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantInvite.html deleted file mode 100644 index 17772dc116..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantInvite.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionParticipantInvite - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionParticipantInvite

- -

A user was invited to the group

-

- -
-
channelAdminLogEventActionParticipantInvite#e31c34d8 participant:ChannelParticipant = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
participantChannelParticipantThe user that was invited
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html deleted file mode 100644 index 4c5b22d846..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoin.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channelAdminLogEventActionParticipantJoin - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionParticipantJoin

- -

A user has joined the group (in the case of big groups, info of the user that has joined isn't shown)

-

- -
-
channelAdminLogEventActionParticipantJoin#183040d3 = ChannelAdminLogEventAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html deleted file mode 100644 index 14c2697d92..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantJoinByInvite.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - channelAdminLogEventActionParticipantJoinByInvite - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionParticipantJoinByInvite

- -

A user joined the supergroup/channel using a specific invite link

-

- -
-
channelAdminLogEventActionParticipantJoinByInvite#5cdada77 invite:ExportedChatInvite = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
inviteExportedChatInviteThe invite link used to join the supergroup/channel
-

Type

-

ChannelAdminLogEventAction

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantLeave.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantLeave.html deleted file mode 100644 index 3545d60d84..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantLeave.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channelAdminLogEventActionParticipantLeave - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionParticipantLeave

- -

A user left the channel/supergroup (in the case of big groups, info of the user that has joined isn't shown)

-

- -
-
channelAdminLogEventActionParticipantLeave#f89777f2 = ChannelAdminLogEventAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantMute.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantMute.html deleted file mode 100644 index 764b1e4df9..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantMute.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionParticipantMute - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionParticipantMute

- -

A group call participant was muted

-

- -
-
channelAdminLogEventActionParticipantMute#f92424d2 participant:GroupCallParticipant = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
participantGroupCallParticipantThe participant that was muted
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantToggleAdmin.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantToggleAdmin.html deleted file mode 100644 index 2942d29b74..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantToggleAdmin.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - channelAdminLogEventActionParticipantToggleAdmin - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionParticipantToggleAdmin

- -

The admin rights of a user were changed

-

- -
-
channelAdminLogEventActionParticipantToggleAdmin#d5676710 prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_participantChannelParticipantPrevious admin rights
new_participantChannelParticipantNew admin rights
-

Type

-

ChannelAdminLogEventAction

-

Related pages

-

Admin, banned, default rights

-

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantToggleBan.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantToggleBan.html deleted file mode 100644 index 650111db02..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantToggleBan.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - channelAdminLogEventActionParticipantToggleBan - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionParticipantToggleBan

- -

The banned rights of a user were changed

-

- -
-
channelAdminLogEventActionParticipantToggleBan#e6d83d7e prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_participantChannelParticipantOld banned rights of user
new_participantChannelParticipantNew banned rights of user
-

Type

-

ChannelAdminLogEventAction

-

Related pages

-

Admin, banned, default rights

-

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantUnmute.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantUnmute.html deleted file mode 100644 index 8a02aa5cec..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantUnmute.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionParticipantUnmute - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionParticipantUnmute

- -

A group call participant was unmuted

-

- -
-
channelAdminLogEventActionParticipantUnmute#e64429c0 participant:GroupCallParticipant = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
participantGroupCallParticipantThe participant that was unmuted
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantVolume.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantVolume.html deleted file mode 100644 index 85557acfff..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantVolume.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionParticipantVolume - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionParticipantVolume

- -

channelAdminLogEvent.user_id has set the volume of participant.peer to participant.volume

-

- -
-
channelAdminLogEventActionParticipantVolume#3e7f6847 participant:GroupCallParticipant = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
participantGroupCallParticipantThe participant whose volume was changed
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionStartGroupCall.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionStartGroupCall.html deleted file mode 100644 index 927c8c6bef..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionStartGroupCall.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionStartGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionStartGroupCall

- -

A group call was started

-

- -
-
channelAdminLogEventActionStartGroupCall#23209745 call:InputGroupCall = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallGroup call
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionStopPoll.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionStopPoll.html deleted file mode 100644 index 1c0667e2fc..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionStopPoll.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionStopPoll - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionStopPoll

- -

A poll was stopped

-

- -
-
channelAdminLogEventActionStopPoll#8f079643 message:Message = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageThe poll that was stopped
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html deleted file mode 100644 index c7543fb13c..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleGroupCallSetting.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionToggleGroupCallSetting - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionToggleGroupCallSetting

- -

Group call settings were changed

-

- -
-
channelAdminLogEventActionToggleGroupCallSetting#56d6a247 join_muted:Bool = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
join_mutedBoolWhether all users are muted by default upon joining
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleInvites.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleInvites.html deleted file mode 100644 index 1d303e7820..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleInvites.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionToggleInvites - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionToggleInvites

- -

Invites were enabled/disabled

-

- -
-
channelAdminLogEventActionToggleInvites#1b7907ae new_value:Bool = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
new_valueBoolNew value
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionTogglePreHistoryHidden.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionTogglePreHistoryHidden.html deleted file mode 100644 index 3f4be13f62..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionTogglePreHistoryHidden.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - channelAdminLogEventActionTogglePreHistoryHidden - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionTogglePreHistoryHidden

- -

The hidden prehistory setting was changed

-

- -
-
channelAdminLogEventActionTogglePreHistoryHidden#5f5c95f1 new_value:Bool = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
new_valueBoolNew value
-

Type

-

ChannelAdminLogEventAction

-

Related pages

-

channels.togglePreHistoryHidden

-

Hide/unhide message history for new channel/supergroup users

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleSignatures.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleSignatures.html deleted file mode 100644 index 834a29954e..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleSignatures.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionToggleSignatures - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionToggleSignatures

- -

Channel signatures were enabled/disabled

-

- -
-
channelAdminLogEventActionToggleSignatures#26ae0971 new_value:Bool = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
new_valueBoolNew value
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleSlowMode.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleSlowMode.html deleted file mode 100644 index 4fcb9b3860..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionToggleSlowMode.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - channelAdminLogEventActionToggleSlowMode - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionToggleSlowMode

- -

Slow mode setting for supergroups was changed

-

- -
-
channelAdminLogEventActionToggleSlowMode#53909779 prev_value:int new_value:int = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
prev_valueintPrevious slow mode value
new_valueintNew slow mode value
-

Type

-

ChannelAdminLogEventAction

-

Related pages

-

channels.toggleSlowMode

-

Toggle supergroup slow mode: if enabled, users will only be able to send one message every seconds seconds

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventActionUpdatePinned.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionUpdatePinned.html deleted file mode 100644 index 6eb2ee5400..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventActionUpdatePinned.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelAdminLogEventActionUpdatePinned - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventActionUpdatePinned

- -

A message was pinned

-

- -
-
channelAdminLogEventActionUpdatePinned#e9e82c18 message:Message = ChannelAdminLogEventAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageThe message that was pinned
-

Type

-

ChannelAdminLogEventAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelAdminLogEventsFilter.html b/data/corefork.telegram.org/constructor/channelAdminLogEventsFilter.html deleted file mode 100644 index 1545f4e686..0000000000 --- a/data/corefork.telegram.org/constructor/channelAdminLogEventsFilter.html +++ /dev/null @@ -1,266 +0,0 @@ - - - - - channelAdminLogEventsFilter - - - - - - - - - - - - - -
- -
-
-
- -

channelAdminLogEventsFilter

- -

Filter only certain admin log events

-

- -
-
channelAdminLogEventsFilter#ea107ae4 flags:# join:flags.0?true leave:flags.1?true invite:flags.2?true ban:flags.3?true unban:flags.4?true kick:flags.5?true unkick:flags.6?true promote:flags.7?true demote:flags.8?true info:flags.9?true settings:flags.10?true pinned:flags.11?true edit:flags.12?true delete:flags.13?true group_call:flags.14?true invites:flags.15?true send:flags.16?true = ChannelAdminLogEventsFilter;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
joinflags.0?trueJoin events
leaveflags.1?trueLeave events
inviteflags.2?trueInvite events
banflags.3?trueBan events
unbanflags.4?trueUnban events
kickflags.5?trueKick events
unkickflags.6?trueUnkick events
promoteflags.7?trueAdmin promotion events
demoteflags.8?trueAdmin demotion events
infoflags.9?trueInfo change events (when about, linked chat, location, photo, stickerset, title or username data of a channel gets modified)
settingsflags.10?trueSettings change events (invites, hidden prehistory, signatures, default banned rights)
pinnedflags.11?trueMessage pin events
editflags.12?trueMessage edit events
deleteflags.13?trueMessage deletion events
group_callflags.14?trueGroup call events
invitesflags.15?trueInvite events
-

Type

-

ChannelAdminLogEventsFilter

-

Related pages

-

channelAdminLogEventActionParticipantJoin

-

A user has joined the group (in the case of big groups, info of the user that has joined isn't shown)

-

channelAdminLogEventActionParticipantLeave

-

A user left the channel/supergroup (in the case of big groups, info of the user that has joined isn't shown)

-

channelAdminLogEventActionParticipantInvite

-

A user was invited to the group

-

channelAdminLogEventActionParticipantToggleBan

-

The banned rights of a user were changed

-

channelAdminLogEventActionParticipantToggleAdmin

-

The admin rights of a user were changed

-

channelAdminLogEventActionChangeAbout

-

The description was changed

-

channelAdminLogEventActionChangeLinkedChat

-

The linked chat was changed

-

channelAdminLogEventActionChangeLocation

-

The geogroup location was changed

-

channelAdminLogEventActionChangePhoto

-

The channel/supergroup's picture was changed

-

channelAdminLogEventActionChangeStickerSet

-

The supergroup's stickerset was changed

-

channelAdminLogEventActionChangeTitle

-

Channel/supergroup title was changed

-

channelAdminLogEventActionChangeUsername

-

Channel/supergroup username was changed

-

channelAdminLogEventActionToggleInvites

-

Invites were enabled/disabled

-

channelAdminLogEventActionTogglePreHistoryHidden

-

The hidden prehistory setting was changed

-

channelAdminLogEventActionToggleSignatures

-

Channel signatures were enabled/disabled

-

channelAdminLogEventActionDefaultBannedRights

-

The default banned rights were modified

-

channelAdminLogEventActionUpdatePinned

-

A message was pinned

-

channelAdminLogEventActionEditMessage

-

A message was edited

-

channelAdminLogEventActionDeleteMessage

-

A message was deleted

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelForbidden.html b/data/corefork.telegram.org/constructor/channelForbidden.html deleted file mode 100644 index 0ea611fefb..0000000000 --- a/data/corefork.telegram.org/constructor/channelForbidden.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - channelForbidden - - - - - - - - - - - - - -
- -
-
-
- -

channelForbidden

- -

Indicates a channel/supergroup we can't access because we were banned, or for some other reason.

-

- -
-
channelForbidden#17d493d5 flags:# broadcast:flags.5?true megagroup:flags.8?true id:long access_hash:long title:string until_date:flags.16?int = Chat;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
broadcastflags.5?trueIs this a channel
megagroupflags.8?trueIs this a supergroup
idlongChannel ID
access_hashlongAccess hash
titlestringTitle
until_dateflags.16?intThe ban is valid until the specified date
-

Type

-

Chat

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelFull.html b/data/corefork.telegram.org/constructor/channelFull.html deleted file mode 100644 index e926a01647..0000000000 --- a/data/corefork.telegram.org/constructor/channelFull.html +++ /dev/null @@ -1,363 +0,0 @@ - - - - - channelFull - - - - - - - - - - - - - -
- -
-
-
- -

channelFull

- -

Full info about a channel/supergroup

-

- -
-
channelFull#e9b27a17 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector<string> groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string = ChatFull;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
can_view_participantsflags.3?trueCan we vew the participant list?
can_set_usernameflags.6?trueCan we set the channel's username?
can_set_stickersflags.7?trueCan we associate a stickerpack to the supergroup?
hidden_prehistoryflags.10?trueIs the history before we joined hidden to us?
can_set_locationflags.16?trueCan we set the geolocation of this group (for geogroups)
has_scheduledflags.19?trueWhether scheduled messages are available
can_view_statsflags.20?trueCan the user view channel/supergroup statistics
blockedflags.22?trueWhether any anonymous admin of this supergroup was blocked: if set, you won't receive messages from anonymous group admins in discussion replies via @replies
idlongID of the channel
aboutstringInfo about the channel
participants_countflags.0?intNumber of participants of the channel
admins_countflags.1?intNumber of channel admins
kicked_countflags.2?intNumber of users kicked from the channel
banned_countflags.2?intNumber of users banned from the channel
online_countflags.13?intNumber of users currently online
read_inbox_max_idintPosition up to which all incoming messages are read.
read_outbox_max_idintPosition up to which all outgoing messages are read.
unread_countintCount of unread messages
chat_photoPhotoChannel picture
notify_settingsPeerNotifySettingsNotification settings
exported_inviteflags.23?ExportedChatInviteInvite link
bot_infoVector<BotInfo>Info about bots in the channel/supergrup
migrated_from_chat_idflags.4?longThe chat ID from which this group was migrated
migrated_from_max_idflags.4?intThe message ID in the original chat at which this group was migrated
pinned_msg_idflags.5?intMessage ID of the last pinned message
stickersetflags.8?StickerSetAssociated stickerset
available_min_idflags.9?intIdentifier of a maximum unavailable message in a channel due to hidden history.
folder_idflags.11?intPeer folder ID, for more info click here
linked_chat_idflags.14?longID of the linked discussion chat for channels
locationflags.15?ChannelLocationLocation of the geogroup
slowmode_secondsflags.17?intIf specified, users in supergroups will only be able to send one message every slowmode_seconds seconds
slowmode_next_send_dateflags.18?intIndicates when the user will be allowed to send another message in the supergroup (unixdate)
stats_dcflags.12?intIf set, specifies the DC to use for fetching channel statistics
ptsintLatest PTS for this channel
callflags.21?InputGroupCallLivestream or group call information
ttl_periodflags.24?intTime-To-Live of messages in this channel or supergroup
pending_suggestionsflags.25?Vector<string>A list of suggested actions for the supergroup admin, see here for more info ».
groupcall_default_join_asflags.26?PeerWhen using phone.getGroupCallJoinAs to get a list of peers that can be used to join a group call, this field indicates the peer that should be selected by default.
theme_emoticonflags.27?stringEmoji representing a specific chat theme
-

Type

-

ChatFull

-

Related pages

-

channels.setStickers

-

Associate a stickerset to the supergroup

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

-

Discussion groups

-

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

-

Admin, banned, default rights

-

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

Pinned messages

-

Telegram allows pinning multiple messages on top of a specific chat.

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Client configuration

-

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

-

phone.getGroupCallJoinAs

-

Get a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelLocation.html b/data/corefork.telegram.org/constructor/channelLocation.html deleted file mode 100644 index 2d18618150..0000000000 --- a/data/corefork.telegram.org/constructor/channelLocation.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelLocation - - - - - - - - - - - - - -
- -
-
-
- -

channelLocation

- -

Geographical location of supergroup (geogroups)

-

- -
-
channelLocation#209b82db geo_point:GeoPoint address:string = ChannelLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
geo_pointGeoPointGeographical location of supergrup
addressstringTextual description of the address
-

Type

-

ChannelLocation

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelLocationEmpty.html b/data/corefork.telegram.org/constructor/channelLocationEmpty.html deleted file mode 100644 index f21756bf36..0000000000 --- a/data/corefork.telegram.org/constructor/channelLocationEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channelLocationEmpty - - - - - - - - - - - - - -
- -
-
-
- -

channelLocationEmpty

- -

No location (normal supergroup)

-

- -
-
channelLocationEmpty#bfb5ad8b = ChannelLocation;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ChannelLocation

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelMessagesFilter.html b/data/corefork.telegram.org/constructor/channelMessagesFilter.html deleted file mode 100644 index e447907790..0000000000 --- a/data/corefork.telegram.org/constructor/channelMessagesFilter.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - channelMessagesFilter - - - - - - - - - - - - - -
- -
-
-
- -

channelMessagesFilter

- -

Filter for getting only certain types of channel messages

-

- -
-
channelMessagesFilter#cd77d957 flags:# exclude_new_messages:flags.1?true ranges:Vector<MessageRange> = ChannelMessagesFilter;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
exclude_new_messagesflags.1?trueWhether to exclude new messages from the search
rangesVector<MessageRange>A range of messages to fetch
-

Type

-

ChannelMessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelMessagesFilterEmpty.html b/data/corefork.telegram.org/constructor/channelMessagesFilterEmpty.html deleted file mode 100644 index f749412f99..0000000000 --- a/data/corefork.telegram.org/constructor/channelMessagesFilterEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channelMessagesFilterEmpty - - - - - - - - - - - - - -
- -
-
-
- -

channelMessagesFilterEmpty

- -

No filter

-

- -
-
channelMessagesFilterEmpty#94d42ee7 = ChannelMessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ChannelMessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelParticipant.html b/data/corefork.telegram.org/constructor/channelParticipant.html deleted file mode 100644 index f9a3d5006d..0000000000 --- a/data/corefork.telegram.org/constructor/channelParticipant.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - channelParticipant - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipant

- -

Channel/supergroup participant

-

- -
-
channelParticipant#c00c07c0 user_id:long date:int = ChannelParticipant;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongPariticipant user ID
dateintDate joined
-

Type

-

ChannelParticipant

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelParticipantAdmin.html b/data/corefork.telegram.org/constructor/channelParticipantAdmin.html deleted file mode 100644 index 7cc55f3d0b..0000000000 --- a/data/corefork.telegram.org/constructor/channelParticipantAdmin.html +++ /dev/null @@ -1,190 +0,0 @@ - - - - - channelParticipantAdmin - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantAdmin

- -

Admin

-

- -
-
channelParticipantAdmin#34c3bb53 flags:# can_edit:flags.0?true self:flags.1?true user_id:long inviter_id:flags.1?long promoted_by:long date:int admin_rights:ChatAdminRights rank:flags.2?string = ChannelParticipant;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
can_editflags.0?trueCan this admin promote other admins with the same permissions?
selfflags.1?trueIs this the current user
user_idlongAdmin user ID
inviter_idflags.1?longUser that invited the admin to the channel/group
promoted_bylongUser that promoted the user to admin
dateintWhen did the user join
admin_rightsChatAdminRightsAdmin rights
rankflags.2?stringThe role (rank) of the admin in the group: just an arbitrary string, admin by default
-

Type

-

ChannelParticipant

-

Related pages

-

Admin, banned, default rights

-

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelParticipantBanned.html b/data/corefork.telegram.org/constructor/channelParticipantBanned.html deleted file mode 100644 index e429895a88..0000000000 --- a/data/corefork.telegram.org/constructor/channelParticipantBanned.html +++ /dev/null @@ -1,175 +0,0 @@ - - - - - channelParticipantBanned - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantBanned

- -

Banned/kicked user

-

- -
-
channelParticipantBanned#6df8014e flags:# left:flags.0?true peer:Peer kicked_by:long date:int banned_rights:ChatBannedRights = ChannelParticipant;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
leftflags.0?trueWhether the user has left the group
peerPeerThe banned peer
kicked_bylongUser was kicked by the specified admin
dateintWhen did the user join the group
banned_rightsChatBannedRightsBanned rights
-

Type

-

ChannelParticipant

-

Related pages

-

Admin, banned, default rights

-

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelParticipantCreator.html b/data/corefork.telegram.org/constructor/channelParticipantCreator.html deleted file mode 100644 index 27585a0886..0000000000 --- a/data/corefork.telegram.org/constructor/channelParticipantCreator.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - channelParticipantCreator - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantCreator

- -

Channel/supergroup creator

-

- -
-
channelParticipantCreator#2fe601d3 flags:# user_id:long admin_rights:ChatAdminRights rank:flags.0?string = ChannelParticipant;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
user_idlongUser ID
admin_rightsChatAdminRightsCreator admin rights
rankflags.0?stringThe role (rank) of the group creator in the group: just an arbitrary string, admin by default
-

Type

-

ChannelParticipant

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelParticipantLeft.html b/data/corefork.telegram.org/constructor/channelParticipantLeft.html deleted file mode 100644 index 2f74e9a91e..0000000000 --- a/data/corefork.telegram.org/constructor/channelParticipantLeft.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelParticipantLeft - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantLeft

- -

A participant that left the channel/supergroup

-

- -
-
channelParticipantLeft#1b03f006 peer:Peer = ChannelParticipant;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerThe peer that left
-

Type

-

ChannelParticipant

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelParticipantSelf.html b/data/corefork.telegram.org/constructor/channelParticipantSelf.html deleted file mode 100644 index 9ae037f9f2..0000000000 --- a/data/corefork.telegram.org/constructor/channelParticipantSelf.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - channelParticipantSelf - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantSelf

- -

Myself

-

- -
-
channelParticipantSelf#28a8bc67 user_id:long inviter_id:long date:int = ChannelParticipant;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser ID
inviter_idlongUser that invited me to the channel/supergroup
dateintWhen did I join the channel/supergroup
-

Type

-

ChannelParticipant

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelParticipantsAdmins.html b/data/corefork.telegram.org/constructor/channelParticipantsAdmins.html deleted file mode 100644 index 3ccf34c775..0000000000 --- a/data/corefork.telegram.org/constructor/channelParticipantsAdmins.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channelParticipantsAdmins - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsAdmins

- -

Fetch only admin participants

-

- -
-
channelParticipantsAdmins#b4608969 = ChannelParticipantsFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ChannelParticipantsFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelParticipantsBanned.html b/data/corefork.telegram.org/constructor/channelParticipantsBanned.html deleted file mode 100644 index 19b3882962..0000000000 --- a/data/corefork.telegram.org/constructor/channelParticipantsBanned.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelParticipantsBanned - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsBanned

- -

Fetch only banned participants

-

- -
-
channelParticipantsBanned#1427a5e1 q:string = ChannelParticipantsFilter;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
qstringOptional filter for searching banned participants by name (otherwise empty)
-

Type

-

ChannelParticipantsFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelParticipantsBots.html b/data/corefork.telegram.org/constructor/channelParticipantsBots.html deleted file mode 100644 index 166869a4d8..0000000000 --- a/data/corefork.telegram.org/constructor/channelParticipantsBots.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channelParticipantsBots - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsBots

- -

Fetch only bot participants

-

- -
-
channelParticipantsBots#b0d1865b = ChannelParticipantsFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ChannelParticipantsFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelParticipantsContacts.html b/data/corefork.telegram.org/constructor/channelParticipantsContacts.html deleted file mode 100644 index 376476d575..0000000000 --- a/data/corefork.telegram.org/constructor/channelParticipantsContacts.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelParticipantsContacts - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsContacts

- -

Fetch only participants that are also contacts

-

- -
-
channelParticipantsContacts#bb6ae88d q:string = ChannelParticipantsFilter;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
qstringOptional search query for searching contact participants by name
-

Type

-

ChannelParticipantsFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelParticipantsKicked.html b/data/corefork.telegram.org/constructor/channelParticipantsKicked.html deleted file mode 100644 index 001fe0376f..0000000000 --- a/data/corefork.telegram.org/constructor/channelParticipantsKicked.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelParticipantsKicked - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsKicked

- -

Fetch only kicked participants

-

- -
-
channelParticipantsKicked#a3b54985 q:string = ChannelParticipantsFilter;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
qstringOptional filter for searching kicked participants by name (otherwise empty)
-

Type

-

ChannelParticipantsFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelParticipantsMentions.html b/data/corefork.telegram.org/constructor/channelParticipantsMentions.html deleted file mode 100644 index cc4d465f7a..0000000000 --- a/data/corefork.telegram.org/constructor/channelParticipantsMentions.html +++ /dev/null @@ -1,161 +0,0 @@ - - - - - channelParticipantsMentions - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsMentions

- -

This filter is used when looking for supergroup members to mention.
-This filter will automatically remove anonymous admins, and return even non-participant users that replied to a specific thread through the comment section of a channel.

-

- -
-
channelParticipantsMentions#e04b5ceb flags:# q:flags.0?string top_msg_id:flags.1?int = ChannelParticipantsFilter;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
qflags.0?stringFilter by user name or username
top_msg_idflags.1?intLook only for users that posted in this thread
-

Type

-

ChannelParticipantsFilter

-

Related pages

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelParticipantsRecent.html b/data/corefork.telegram.org/constructor/channelParticipantsRecent.html deleted file mode 100644 index bc70ccb0a8..0000000000 --- a/data/corefork.telegram.org/constructor/channelParticipantsRecent.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channelParticipantsRecent - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsRecent

- -

Fetch only recent participants

-

- -
-
channelParticipantsRecent#de3f3c79 = ChannelParticipantsFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ChannelParticipantsFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channelParticipantsSearch.html b/data/corefork.telegram.org/constructor/channelParticipantsSearch.html deleted file mode 100644 index aa42384590..0000000000 --- a/data/corefork.telegram.org/constructor/channelParticipantsSearch.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - channelParticipantsSearch - - - - - - - - - - - - - -
- -
-
-
- -

channelParticipantsSearch

- -

Query participants by name

-

- -
-
channelParticipantsSearch#656ac4b q:string = ChannelParticipantsFilter;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
qstringSearch query
-

Type

-

ChannelParticipantsFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channels.adminLogResults b/data/corefork.telegram.org/constructor/channels.adminLogResults deleted file mode 100644 index 6861020045..0000000000 --- a/data/corefork.telegram.org/constructor/channels.adminLogResults +++ /dev/null @@ -1,157 +0,0 @@ - - - - - channels.adminLogResults - - - - - - - - - - - - - -
- -
-
-
- -

channels.adminLogResults

- -

Admin log events

-

- -
-
channels.adminLogResults#ed8af74d events:Vector<ChannelAdminLogEvent> chats:Vector<Chat> users:Vector<User> = channels.AdminLogResults;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
eventsVector<ChannelAdminLogEvent>Admin log events
chatsVector<Chat>Chats mentioned in events
usersVector<User>Users mentioned in events
-

Type

-

channels.AdminLogResults

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channels.channelParticipants b/data/corefork.telegram.org/constructor/channels.channelParticipants deleted file mode 100644 index e0b69d4037..0000000000 --- a/data/corefork.telegram.org/constructor/channels.channelParticipants +++ /dev/null @@ -1,162 +0,0 @@ - - - - - channels.channelParticipants - - - - - - - - - - - - - -
- -
-
-
- -

channels.channelParticipants

- -

Represents multiple channel participants

-

- -
-
channels.channelParticipants#9ab0feaf count:int participants:Vector<ChannelParticipant> chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipants;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countintTotal number of participants that correspond to the given query
participantsVector<ChannelParticipant>Participants
chatsVector<Chat>Mentioned chats
usersVector<User>Users mentioned in participant info
-

Type

-

channels.ChannelParticipants

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/channels.channelParticipantsNotModified b/data/corefork.telegram.org/constructor/channels.channelParticipantsNotModified deleted file mode 100644 index cda44b9cc3..0000000000 --- a/data/corefork.telegram.org/constructor/channels.channelParticipantsNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - channels.channelParticipantsNotModified - - - - - - - - - - - - - -
- -
-
-
- -

channels.channelParticipantsNotModified

- -

No new participant info could be found

-

- -
-
channels.channelParticipantsNotModified#f0173fe9 = channels.ChannelParticipants;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

channels.ChannelParticipants

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/chat.html b/data/corefork.telegram.org/constructor/chat.html deleted file mode 100644 index f97df0825d..0000000000 --- a/data/corefork.telegram.org/constructor/chat.html +++ /dev/null @@ -1,227 +0,0 @@ - - - - - chat - - - - - - - - - - - - - -
- -
-
-
- -

chat

- -

Info about a group

-

- -
-
chat#41cbf256 flags:# creator:flags.0?true kicked:flags.1?true left:flags.2?true deactivated:flags.5?true call_active:flags.23?true call_not_empty:flags.24?true noforwards:flags.25?true id:long title:string photo:ChatPhoto participants_count:int date:int version:int migrated_to:flags.6?InputChannel admin_rights:flags.14?ChatAdminRights default_banned_rights:flags.18?ChatBannedRights = Chat;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
creatorflags.0?trueWhether the current user is the creator of the group
kickedflags.1?trueWhether the current user was kicked from the group
leftflags.2?trueWhether the current user has left the group
deactivatedflags.5?trueWhether the group was migrated
call_activeflags.23?trueWhether a group call is currently active
call_not_emptyflags.24?trueWhether there's anyone in the group call
idlongID of the group
titlestringTitle
photoChatPhotoChat photo
participants_countintParticipant count
dateintDate of creation of the group
versionintUsed in basic groups to reorder updates and make sure that all of them were received.
migrated_toflags.6?InputChannelMeans this chat was upgraded to a supergroup
admin_rightsflags.14?ChatAdminRightsAdmin rights of the user in the group
default_banned_rightsflags.18?ChatBannedRightsDefault banned rights of all users in the group
-

Type

-

Chat

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

Admin, banned, default rights

-

How to handle admin permissions, granular bans and global permissions in channels, groups and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/chatAdminRights.html b/data/corefork.telegram.org/constructor/chatAdminRights.html deleted file mode 100644 index 32d62c20c3..0000000000 --- a/data/corefork.telegram.org/constructor/chatAdminRights.html +++ /dev/null @@ -1,205 +0,0 @@ - - - - - chatAdminRights - - - - - - - - - - - - - -
- -
-
-
- -

chatAdminRights

- -

Represents the rights of an admin in a channel/supergroup.

-

- -
-
chatAdminRights#5fb224d5 flags:# change_info:flags.0?true post_messages:flags.1?true edit_messages:flags.2?true delete_messages:flags.3?true ban_users:flags.4?true invite_users:flags.5?true pin_messages:flags.7?true add_admins:flags.9?true anonymous:flags.10?true manage_call:flags.11?true other:flags.12?true = ChatAdminRights;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
change_infoflags.0?trueIf set, allows the admin to modify the description of the channel/supergroup
post_messagesflags.1?trueIf set, allows the admin to post messages in the channel
edit_messagesflags.2?trueIf set, allows the admin to also edit messages from other admins in the channel
delete_messagesflags.3?trueIf set, allows the admin to also delete messages from other admins in the channel
ban_usersflags.4?trueIf set, allows the admin to ban users from the channel/supergroup
invite_usersflags.5?trueIf set, allows the admin to invite users in the channel/supergroup
pin_messagesflags.7?trueIf set, allows the admin to pin messages in the channel/supergroup
add_adminsflags.9?trueIf set, allows the admin to add other admins with the same (or more limited) permissions in the channel/supergroup
anonymousflags.10?trueWhether this admin is anonymous
manage_callflags.11?trueIf set, allows the admin to change group call/livestream settings
otherflags.12?trueSet this flag if none of the other flags are set, but you stil want the user to be an admin.
-

Type

-

ChatAdminRights

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/chatAdminWithInvites.html b/data/corefork.telegram.org/constructor/chatAdminWithInvites.html deleted file mode 100644 index e1f77ae845..0000000000 --- a/data/corefork.telegram.org/constructor/chatAdminWithInvites.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - chatAdminWithInvites - - - - - - - - - - - - - -
- -
-
-
- -

chatAdminWithInvites

- -

Info about chat invites generated by admins.

-

- -
-
chatAdminWithInvites#f2ecef23 admin_id:long invites_count:int revoked_invites_count:int = ChatAdminWithInvites;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
admin_idlongThe admin
invites_countintNumber of invites generated by the admin
revoked_invites_countintNumber of revoked invites
-

Type

-

ChatAdminWithInvites

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/chatBannedRights.html b/data/corefork.telegram.org/constructor/chatBannedRights.html deleted file mode 100644 index 673aa2fe31..0000000000 --- a/data/corefork.telegram.org/constructor/chatBannedRights.html +++ /dev/null @@ -1,216 +0,0 @@ - - - - - chatBannedRights - - - - - - - - - - - - - -
- -
-
-
- -

chatBannedRights

- -

Represents the rights of a normal user in a supergroup/channel/chat. In this case, the flags are inverted: if set, a flag does not allow a user to do X.

-

- -
-
chatBannedRights#9f120418 flags:# view_messages:flags.0?true send_messages:flags.1?true send_media:flags.2?true send_stickers:flags.3?true send_gifs:flags.4?true send_games:flags.5?true send_inline:flags.6?true embed_links:flags.7?true send_polls:flags.8?true change_info:flags.10?true invite_users:flags.15?true pin_messages:flags.17?true until_date:int = ChatBannedRights;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
view_messagesflags.0?trueIf set, does not allow a user to view messages in a supergroup/channel/chat
send_messagesflags.1?trueIf set, does not allow a user to send messages in a supergroup/chat
send_mediaflags.2?trueIf set, does not allow a user to send any media in a supergroup/chat
send_stickersflags.3?trueIf set, does not allow a user to send stickers in a supergroup/chat
send_gifsflags.4?trueIf set, does not allow a user to send gifs in a supergroup/chat
send_gamesflags.5?trueIf set, does not allow a user to send games in a supergroup/chat
send_inlineflags.6?trueIf set, does not allow a user to use inline bots in a supergroup/chat
embed_linksflags.7?trueIf set, does not allow a user to embed links in the messages of a supergroup/chat
send_pollsflags.8?trueIf set, does not allow a user to send polls in a supergroup/chat
change_infoflags.10?trueIf set, does not allow any user to change the description of a supergroup/chat
invite_usersflags.15?trueIf set, does not allow any user to invite users in a supergroup/chat
pin_messagesflags.17?trueIf set, does not allow any user to pin messages in a supergroup/chat
until_dateintValidity of said permissions (it is considered forever any value less then 30 seconds or more then 366 days).
-

Type

-

ChatBannedRights

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/chatEmpty.html b/data/corefork.telegram.org/constructor/chatEmpty.html deleted file mode 100644 index c3379dfd9d..0000000000 --- a/data/corefork.telegram.org/constructor/chatEmpty.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - chatEmpty - - - - - - - - - - - - - -
- -
-
-
- -

chatEmpty

- -

Empty constructor, group doesn't exist

-

- -
-
chatEmpty#29562865 id:long = Chat;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idlongGroup identifier
-

Type

-

Chat

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/chatForbidden.html b/data/corefork.telegram.org/constructor/chatForbidden.html deleted file mode 100644 index a21dc5244b..0000000000 --- a/data/corefork.telegram.org/constructor/chatForbidden.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - chatForbidden - - - - - - - - - - - - - -
- -
-
-
- -

chatForbidden

- -

A group to which the user has no access. E.g., because the user was kicked from the group.

-

- -
-
chatForbidden#6592a1a7 id:long title:string = Chat;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongUser identifier
titlestringGroup name
-

Type

-

Chat

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/chatFull.html b/data/corefork.telegram.org/constructor/chatFull.html deleted file mode 100644 index 9e961c7abc..0000000000 --- a/data/corefork.telegram.org/constructor/chatFull.html +++ /dev/null @@ -1,231 +0,0 @@ - - - - - chatFull - - - - - - - - - - - - - -
- -
-
-
- -

chatFull

- -

Detailed chat info

-

- -
-
chatFull#4dbdc099 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:long about:string participants:ChatParticipants chat_photo:flags.2?Photo notify_settings:PeerNotifySettings exported_invite:flags.13?ExportedChatInvite bot_info:flags.3?Vector<BotInfo> pinned_msg_id:flags.6?int folder_id:flags.11?int call:flags.12?InputGroupCall ttl_period:flags.14?int groupcall_default_join_as:flags.15?Peer theme_emoticon:flags.16?string = ChatFull;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
can_set_usernameflags.7?trueCan we change the username of this chat
has_scheduledflags.8?trueWhether scheduled messages are available
idlongID of the chat
aboutstringAbout string for this chat
participantsChatParticipantsParticipant list
chat_photoflags.2?PhotoChat photo
notify_settingsPeerNotifySettingsNotification settings
exported_inviteflags.13?ExportedChatInviteChat invite
bot_infoflags.3?Vector<BotInfo>Info about bots that are in this chat
pinned_msg_idflags.6?intMessage ID of the last pinned message
folder_idflags.11?intPeer folder ID, for more info click here
callflags.12?InputGroupCallGroup call information
ttl_periodflags.14?intTime-To-Live of messages sent by the current user to this chat
groupcall_default_join_asflags.15?PeerWhen using phone.getGroupCallJoinAs to get a list of peers that can be used to join a group call, this field indicates the peer that should be selected by default.
theme_emoticonflags.16?stringEmoji representing a specific chat theme
-

Type

-

ChatFull

-

Related pages

-

Scheduled messages

-

Telegram allows scheduling messages

-

Pinned messages

-

Telegram allows pinning multiple messages on top of a specific chat.

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

-

phone.getGroupCallJoinAs

-

Get a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/chatInvite.html b/data/corefork.telegram.org/constructor/chatInvite.html deleted file mode 100644 index 2c986755b9..0000000000 --- a/data/corefork.telegram.org/constructor/chatInvite.html +++ /dev/null @@ -1,190 +0,0 @@ - - - - - chatInvite - - - - - - - - - - - - - -
- -
-
-
- -

chatInvite

- -

Chat invite info

-

- -
-
chatInvite#dfc2f58e flags:# channel:flags.0?true broadcast:flags.1?true public:flags.2?true megagroup:flags.3?true title:string photo:Photo participants_count:int participants:flags.4?Vector<User> = ChatInvite;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
channelflags.0?trueWhether this is a channel/supergroup or a normal group
broadcastflags.1?trueWhether this is a channel
publicflags.2?trueWhether this is a public channel/supergroup
megagroupflags.3?trueWhether this is a supergroup
titlestringChat/supergroup/channel title
photoPhotoChat/supergroup/channel photo
participants_countintParticipant count
participantsflags.4?Vector<User>A few of the participants that are in the group
-

Type

-

ChatInvite

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/chatInviteAlready.html b/data/corefork.telegram.org/constructor/chatInviteAlready.html deleted file mode 100644 index 030e7c5253..0000000000 --- a/data/corefork.telegram.org/constructor/chatInviteAlready.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - chatInviteAlready - - - - - - - - - - - - - -
- -
-
-
- -

chatInviteAlready

- -

The user has already joined this chat

-

- -
-
chatInviteAlready#5a686d7c chat:Chat = ChatInvite;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chatChatThe chat connected to the invite
-

Type

-

ChatInvite

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/chatInviteExported.html b/data/corefork.telegram.org/constructor/chatInviteExported.html deleted file mode 100644 index aadd78dfe8..0000000000 --- a/data/corefork.telegram.org/constructor/chatInviteExported.html +++ /dev/null @@ -1,192 +0,0 @@ - - - - - chatInviteExported - - - - - - - - - - - - - -
- -
-
-
- -

chatInviteExported

- -

Exported chat invite

-

- -
-
chatInviteExported#b18105e8 flags:# revoked:flags.0?true permanent:flags.5?true link:string admin_id:long date:int start_date:flags.4?int expire_date:flags.1?int usage_limit:flags.2?int usage:flags.3?int = ExportedChatInvite;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
revokedflags.0?trueWhether this chat invite was revoked
permanentflags.5?trueWhether this chat invite has no expiration
linkstringChat invitation link
admin_idlongID of the admin that created this chat invite
dateintWhen was this chat invite created
start_dateflags.4?intWhen was this chat invite last modified
expire_dateflags.1?intWhen does this chat invite expire
usage_limitflags.2?intMaximum number of users that can join using this link
usageflags.3?intHow many users joined using this link
-

Type

-

ExportedChatInvite

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/chatInvitePeek.html b/data/corefork.telegram.org/constructor/chatInvitePeek.html deleted file mode 100644 index 5925aef809..0000000000 --- a/data/corefork.telegram.org/constructor/chatInvitePeek.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - chatInvitePeek - - - - - - - - - - - - - -
- -
-
-
- -

chatInvitePeek

- -

A chat invitation that also allows peeking into the group to read messages without joining it.

-

- -
-
chatInvitePeek#61695cb0 chat:Chat expires:int = ChatInvite;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chatChatChat information
expiresintRead-only anonymous access to this group will be revoked at this date
-

Type

-

ChatInvite

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/chatOnlines.html b/data/corefork.telegram.org/constructor/chatOnlines.html deleted file mode 100644 index 83a320b919..0000000000 --- a/data/corefork.telegram.org/constructor/chatOnlines.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - chatOnlines - - - - - - - - - - - - - -
- -
-
-
- -

chatOnlines

- -

Number of online users in a chat

-

- -
-
chatOnlines#f041e250 onlines:int = ChatOnlines;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
onlinesintNumber of online users
-

Type

-

ChatOnlines

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/chatParticipant.html b/data/corefork.telegram.org/constructor/chatParticipant.html deleted file mode 100644 index 53224584c0..0000000000 --- a/data/corefork.telegram.org/constructor/chatParticipant.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - chatParticipant - - - - - - - - - - - - - -
- -
-
-
- -

chatParticipant

- -

Group member.

-

- -
-
chatParticipant#c02d4007 user_id:long inviter_id:long date:int = ChatParticipant;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongMember user ID
inviter_idlongID of the user that added the member to the group
dateintDate added to the group
-

Type

-

ChatParticipant

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/chatParticipantAdmin.html b/data/corefork.telegram.org/constructor/chatParticipantAdmin.html deleted file mode 100644 index 81f72416b8..0000000000 --- a/data/corefork.telegram.org/constructor/chatParticipantAdmin.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - chatParticipantAdmin - - - - - - - - - - - - - -
- -
-
-
- -

chatParticipantAdmin

- -

Chat admin

-

- -
-
chatParticipantAdmin#a0933f5b user_id:long inviter_id:long date:int = ChatParticipant;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongID of a group member that is admin
inviter_idlongID of the user that added the member to the group
dateintDate when the user was added
-

Type

-

ChatParticipant

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/chatParticipantCreator.html b/data/corefork.telegram.org/constructor/chatParticipantCreator.html deleted file mode 100644 index 818a359235..0000000000 --- a/data/corefork.telegram.org/constructor/chatParticipantCreator.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - chatParticipantCreator - - - - - - - - - - - - - -
- -
-
-
- -

chatParticipantCreator

- -

Represents the creator of the group

-

- -
-
chatParticipantCreator#e46bcee4 user_id:long = ChatParticipant;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongID of the user that created the group
-

Type

-

ChatParticipant

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/chatParticipants.html b/data/corefork.telegram.org/constructor/chatParticipants.html deleted file mode 100644 index 7c9977afcd..0000000000 --- a/data/corefork.telegram.org/constructor/chatParticipants.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - chatParticipants - - - - - - - - - - - - - -
- -
-
-
- -

chatParticipants

- -

Group members.

-

- -
-
chatParticipants#3cbc93f8 chat_id:long participants:Vector<ChatParticipant> version:int = ChatParticipants;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongGroup identifier
participantsVector<ChatParticipant>List of group members
versionintGroup version number
-

Type

-

ChatParticipants

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/chatParticipantsForbidden.html b/data/corefork.telegram.org/constructor/chatParticipantsForbidden.html deleted file mode 100644 index 1bab439ab2..0000000000 --- a/data/corefork.telegram.org/constructor/chatParticipantsForbidden.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - chatParticipantsForbidden - - - - - - - - - - - - - -
- -
-
-
- -

chatParticipantsForbidden

- -

Info on members is unavailable

-

- -
-
chatParticipantsForbidden#8763d3e1 flags:# chat_id:long self_participant:flags.0?ChatParticipant = ChatParticipants;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
chat_idlongGroup ID
self_participantflags.0?ChatParticipantInfo about the group membership of the current user
-

Type

-

ChatParticipants

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/chatPhoto.html b/data/corefork.telegram.org/constructor/chatPhoto.html deleted file mode 100644 index 6716a3b475..0000000000 --- a/data/corefork.telegram.org/constructor/chatPhoto.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - chatPhoto - - - - - - - - - - - - - -
- -
-
-
- -

chatPhoto

- -

Group profile photo.

-

- -
-
chatPhoto#1c6e1c11 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = ChatPhoto;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
has_videoflags.0?trueWhether the user has an animated profile picture
photo_idlongPhoto ID
stripped_thumbflags.1?bytesStripped thumbnail
dc_idintDC where this photo is stored
-

Type

-

ChatPhoto

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/chatPhotoEmpty.html b/data/corefork.telegram.org/constructor/chatPhotoEmpty.html deleted file mode 100644 index 97aaf443d2..0000000000 --- a/data/corefork.telegram.org/constructor/chatPhotoEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - chatPhotoEmpty - - - - - - - - - - - - - -
- -
-
-
- -

chatPhotoEmpty

- -

Group photo is not set.

-

- -
-
chatPhotoEmpty#37c1011c = ChatPhoto;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ChatPhoto

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/chatTheme.html b/data/corefork.telegram.org/constructor/chatTheme.html deleted file mode 100644 index 32dba8826e..0000000000 --- a/data/corefork.telegram.org/constructor/chatTheme.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - chatTheme - - - - - - - - - - - - - -
- -
-
-
- -

chatTheme

- -

A chat theme

-

- -
-
chatTheme#ed0b5c33 emoticon:string theme:Theme dark_theme:Theme = ChatTheme;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
emoticonstringEmoji, identifying this specific chat theme
themeThemeTheme
dark_themeThemeDark mode theme
-

Type

-

ChatTheme

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/codeSettings.html b/data/corefork.telegram.org/constructor/codeSettings.html deleted file mode 100644 index 1d4bd52e0b..0000000000 --- a/data/corefork.telegram.org/constructor/codeSettings.html +++ /dev/null @@ -1,166 +0,0 @@ - - - - - codeSettings - - - - - - - - - - - - - -
- -
-
-
- -

codeSettings

- -

Settings used by telegram servers for sending the confirm code.

-

Example implementations: telegram for android, tdlib.

-

- -
-
codeSettings#debebe83 flags:# allow_flashcall:flags.0?true current_number:flags.1?true allow_app_hash:flags.4?true = CodeSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
allow_flashcallflags.0?trueWhether to allow phone verification via phone calls.
current_numberflags.1?truePass true if the phone number is used on the current device. Ignored if allow_flashcall is not set.
allow_app_hashflags.4?trueIf a token that will be included in eventually sent SMSs is required: required in newer versions of android, to use the android SMS receiver APIs
-

Type

-

CodeSettings

-

Related pages

-

User Authorization

-

How to register a user's phone to start using the API.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/config.html b/data/corefork.telegram.org/constructor/config.html deleted file mode 100644 index 9838795bc9..0000000000 --- a/data/corefork.telegram.org/constructor/config.html +++ /dev/null @@ -1,420 +0,0 @@ - - - - - config - - - - - - - - - - - - - -
- -
-
-
- -

config

- -

Current configuration

-

- -
-
config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
phonecalls_enabledflags.1?trueWhether phone calls can be used
default_p2p_contactsflags.3?trueWhether the client should use P2P by default for phone calls with contacts
preload_featured_stickersflags.4?trueWhether the client should preload featured stickers
ignore_phone_entitiesflags.5?trueWhether the client should ignore phone entities
revoke_pm_inboxflags.6?trueWhether incoming private messages can be deleted for both participants
blocked_modeflags.8?trueIndicates that telegram is probably censored by governments/ISPs in the current region
pfs_enabledflags.13?trueWhether pfs was used
dateintCurrent date at the server
expiresintExpiration date of this config: when it expires it'll have to be refetched using help.getConfig
test_modeBoolWhether we're connected to the test DCs
this_dcintID of the DC that returned the reply
dc_optionsVector<DcOption>DC IP list
dc_txt_domain_namestringDomain name for fetching encrypted DC list from DNS TXT record
chat_size_maxintMaximum member count for normal groups
megagroup_size_maxintMaximum member count for supergroups
forwarded_count_maxintMaximum number of messages that can be forwarded at once using messages.forwardMessages.
online_update_period_msintThe client should update its online status every N milliseconds
offline_blur_timeout_msintDelay before offline status needs to be sent to the server
offline_idle_timeout_msintTime without any user activity after which it should be treated offline
online_cloud_timeout_msintIf we are offline, but were online from some other client in last online_cloud_timeout_ms milliseconds after we had gone offline, then delay offline notification for notify_cloud_delay_ms milliseconds.
notify_cloud_delay_msintIf we are offline, but online from some other client then delay sending the offline notification for notify_cloud_delay_ms milliseconds.
notify_default_delay_msintIf some other client is online, then delay notification for notification_default_delay_ms milliseconds
push_chat_period_msintNot for client use
push_chat_limitintNot for client use
saved_gifs_limitintMaximum count of saved gifs
edit_time_limitintOnly messages with age smaller than the one specified can be edited
revoke_time_limitintOnly channel/supergroup messages with age smaller than the specified can be deleted
revoke_pm_time_limitintOnly private messages with age smaller than the specified can be deleted
rating_e_decayintExponential decay rate for computing top peer rating
stickers_recent_limitintMaximum number of recent stickers
stickers_faved_limitintMaximum number of faved stickers
channels_read_media_periodintIndicates that round videos (video notes) and voice messages sent in channels and older than the specified period must be marked as read
tmp_sessionsflags.0?intTemporary passport sessions
pinned_dialogs_count_maxintMaximum count of pinned dialogs
pinned_infolder_count_maxintMaximum count of dialogs per folder
call_receive_timeout_msintMaximum allowed outgoing ring time in VoIP calls: if the user we're calling doesn't reply within the specified time (in milliseconds), we should hang up the call
call_ring_timeout_msintMaximum allowed incoming ring time in VoIP calls: if the current user doesn't reply within the specified time (in milliseconds), the call will be automatically refused
call_connect_timeout_msintVoIP connection timeout: if the instance of libtgvoip on the other side of the call doesn't connect to our instance of libtgvoip within the specified time (in milliseconds), the call must be aborted
call_packet_timeout_msintIf during a VoIP call a packet isn't received for the specified period of time, the call must be aborted
me_url_prefixstringThe domain to use to parse in-app links.
For example t.me indicates that t.me/username links should parsed to @username, t.me/addsticker/name should be parsed to the appropriate stickerset and so on...
autoupdate_url_prefixflags.7?stringURL to use to auto-update the current app
gif_search_usernameflags.9?stringUsername of the bot to use to search for GIFs
venue_search_usernameflags.10?stringUsername of the bot to use to search for venues
img_search_usernameflags.11?stringUsername of the bot to use for image search
static_maps_providerflags.12?stringID of the map provider to use for venues
caption_length_maxintMaximum length of caption (length in utf8 codepoints)
message_length_maxintMaximum length of messages (length in utf8 codepoints)
webfile_dc_idintDC ID to use to download webfiles
suggested_lang_codeflags.2?stringSuggested language code
lang_pack_versionflags.2?intLanguage pack version
base_lang_pack_versionflags.2?intBasic language pack version
-

Type

-

Config

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

-

Perfect Forward Secrecy

-

Binding temporary authorization key to permanent ones.

-

help.getConfig

-

Returns current configuration, including data center configuration.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

messages.forwardMessages

-

Forwards messages by their IDs.

-

account.updateStatus

-

Updates online user status.

-

Top peer rating

-

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

-

Telegram Passport Manual

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/contact.html b/data/corefork.telegram.org/constructor/contact.html deleted file mode 100644 index 80af6b9ea4..0000000000 --- a/data/corefork.telegram.org/constructor/contact.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - contact - - - - - - - - - - - - - -
- -
-
-
- -

contact

- -

A contact of the current user that is registered in the system.

-

- -
-
contact#145ade0b user_id:long mutual:Bool = Contact;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser identifier
mutualBoolCurrent user is in the user's contact list
-

Type

-

Contact

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/contactStatus.html b/data/corefork.telegram.org/constructor/contactStatus.html deleted file mode 100644 index 388d96d925..0000000000 --- a/data/corefork.telegram.org/constructor/contactStatus.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - contactStatus - - - - - - - - - - - - - -
- -
-
-
- -

contactStatus

- -

Contact status: online / offline.

-

- -
-
contactStatus#16d9703b user_id:long status:UserStatus = ContactStatus;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser identifier
statusUserStatusOnline status
-

Type

-

ContactStatus

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/contacts.blocked b/data/corefork.telegram.org/constructor/contacts.blocked deleted file mode 100644 index 5faa344659..0000000000 --- a/data/corefork.telegram.org/constructor/contacts.blocked +++ /dev/null @@ -1,157 +0,0 @@ - - - - - contacts.blocked - - - - - - - - - - - - - -
- -
-
-
- -

contacts.blocked

- -

Full list of blocked users.

-

- -
-
contacts.blocked#ade1591 blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
blockedVector<PeerBlocked>List of blocked users
chatsVector<Chat>Blocked chats
usersVector<User>List of users
-

Type

-

contacts.Blocked

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/contacts.blockedSlice b/data/corefork.telegram.org/constructor/contacts.blockedSlice deleted file mode 100644 index 96935a43c1..0000000000 --- a/data/corefork.telegram.org/constructor/contacts.blockedSlice +++ /dev/null @@ -1,162 +0,0 @@ - - - - - contacts.blockedSlice - - - - - - - - - - - - - -
- -
-
-
- -

contacts.blockedSlice

- -

Incomplete list of blocked users.

-

- -
-
contacts.blockedSlice#e1664194 count:int blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countintTotal number of elements in the list
blockedVector<PeerBlocked>List of blocked users
chatsVector<Chat>Blocked chats
usersVector<User>List of users
-

Type

-

contacts.Blocked

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/contacts.contacts b/data/corefork.telegram.org/constructor/contacts.contacts deleted file mode 100644 index ac4586ec0b..0000000000 --- a/data/corefork.telegram.org/constructor/contacts.contacts +++ /dev/null @@ -1,157 +0,0 @@ - - - - - contacts.contacts - - - - - - - - - - - - - -
- -
-
-
- -

contacts.contacts

- -

The current user's contact list and info on users.

-

- -
-
contacts.contacts#eae87e42 contacts:Vector<Contact> saved_count:int users:Vector<User> = contacts.Contacts;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
contactsVector<Contact>Contact list
saved_countintNumber of contacts that were saved successfully
usersVector<User>User list
-

Type

-

contacts.Contacts

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/contacts.contactsNotModified b/data/corefork.telegram.org/constructor/contacts.contactsNotModified deleted file mode 100644 index 98df318600..0000000000 --- a/data/corefork.telegram.org/constructor/contacts.contactsNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - contacts.contactsNotModified - - - - - - - - - - - - - -
- -
-
-
- -

contacts.contactsNotModified

- -

Contact list on the server is the same as the list on the client.

-

- -
-
contacts.contactsNotModified#b74ba9d2 = contacts.Contacts;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

contacts.Contacts

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/contacts.found b/data/corefork.telegram.org/constructor/contacts.found deleted file mode 100644 index d2c24126ab..0000000000 --- a/data/corefork.telegram.org/constructor/contacts.found +++ /dev/null @@ -1,162 +0,0 @@ - - - - - contacts.found - - - - - - - - - - - - - -
- -
-
-
- -

contacts.found

- -

Users found by name substring and auxiliary data.

-

- -
-
contacts.found#b3134d9d my_results:Vector<Peer> results:Vector<Peer> chats:Vector<Chat> users:Vector<User> = contacts.Found;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
my_resultsVector<Peer>Personalized results
resultsVector<Peer>List of found user identifiers
chatsVector<Chat>Found chats
usersVector<User>List of users
-

Type

-

contacts.Found

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/contacts.importedContacts b/data/corefork.telegram.org/constructor/contacts.importedContacts deleted file mode 100644 index 9d383b0e7a..0000000000 --- a/data/corefork.telegram.org/constructor/contacts.importedContacts +++ /dev/null @@ -1,165 +0,0 @@ - - - - - contacts.importedContacts - - - - - - - - - - - - - -
- -
-
-
- -

contacts.importedContacts

- -

Info on succesfully imported contacts.

-

- -
-
contacts.importedContacts#77d01c3b imported:Vector<ImportedContact> popular_invites:Vector<PopularContact> retry_contacts:Vector<long> users:Vector<User> = contacts.ImportedContacts;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
importedVector<ImportedContact>List of succesfully imported contacts
popular_invitesVector<PopularContact>Popular contacts
retry_contactsVector<long>List of contact ids that could not be imported due to system limitation and will need to be imported at a later date.
Parameter added in Layer 13
usersVector<User>List of users
-

Type

-

contacts.ImportedContacts

-

Related pages

-

Layers

-

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/contacts.resolvedPeer b/data/corefork.telegram.org/constructor/contacts.resolvedPeer deleted file mode 100644 index 4b06a3e5a0..0000000000 --- a/data/corefork.telegram.org/constructor/contacts.resolvedPeer +++ /dev/null @@ -1,157 +0,0 @@ - - - - - contacts.resolvedPeer - - - - - - - - - - - - - -
- -
-
-
- -

contacts.resolvedPeer

- -

Resolved peer

-

- -
-
contacts.resolvedPeer#7f077ad9 peer:Peer chats:Vector<Chat> users:Vector<User> = contacts.ResolvedPeer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerThe peer
chatsVector<Chat>Chats
usersVector<User>Users
-

Type

-

contacts.ResolvedPeer

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/contacts.topPeers b/data/corefork.telegram.org/constructor/contacts.topPeers deleted file mode 100644 index 417aabb081..0000000000 --- a/data/corefork.telegram.org/constructor/contacts.topPeers +++ /dev/null @@ -1,157 +0,0 @@ - - - - - contacts.topPeers - - - - - - - - - - - - - -
- -
-
-
- -

contacts.topPeers

- -

Top peers

-

- -
-
contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
categoriesVector<TopPeerCategoryPeers>Top peers by top peer category
chatsVector<Chat>Chats
usersVector<User>Users
-

Type

-

contacts.TopPeers

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/contacts.topPeersDisabled b/data/corefork.telegram.org/constructor/contacts.topPeersDisabled deleted file mode 100644 index d95b887f61..0000000000 --- a/data/corefork.telegram.org/constructor/contacts.topPeersDisabled +++ /dev/null @@ -1,132 +0,0 @@ - - - - - contacts.topPeersDisabled - - - - - - - - - - - - - -
- -
-
-
- -

contacts.topPeersDisabled

- -

Top peers disabled

-

- -
-
contacts.topPeersDisabled#b52c939d = contacts.TopPeers;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

contacts.TopPeers

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/contacts.topPeersNotModified b/data/corefork.telegram.org/constructor/contacts.topPeersNotModified deleted file mode 100644 index b3bc044139..0000000000 --- a/data/corefork.telegram.org/constructor/contacts.topPeersNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - contacts.topPeersNotModified - - - - - - - - - - - - - -
- -
-
-
- -

contacts.topPeersNotModified

- -

Top peer info hasn't changed

-

- -
-
contacts.topPeersNotModified#de266ef5 = contacts.TopPeers;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

contacts.TopPeers

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/dataJSON.html b/data/corefork.telegram.org/constructor/dataJSON.html deleted file mode 100644 index 269c65468e..0000000000 --- a/data/corefork.telegram.org/constructor/dataJSON.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - dataJSON - - - - - - - - - - - - - -
- -
-
-
- -

dataJSON

- -

Represents a json-encoded object

-

- -
-
dataJSON#7d748d04 data:string = DataJSON;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
datastringJSON-encoded object
-

Type

-

DataJSON

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/dcOption.html b/data/corefork.telegram.org/constructor/dcOption.html deleted file mode 100644 index 37365d5639..0000000000 --- a/data/corefork.telegram.org/constructor/dcOption.html +++ /dev/null @@ -1,197 +0,0 @@ - - - - - dcOption - - - - - - - - - - - - - -
- -
-
-
- -

dcOption

- -

Data centre

-

- -
-
dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
ipv6flags.0?trueWhether the specified IP is an IPv6 address
media_onlyflags.1?trueWhether this DC should only be used to download or upload files
tcpo_onlyflags.2?trueWhether this DC only supports connection with transport obfuscation
cdnflags.3?trueWhether this is a CDN DC.
staticflags.4?trueIf set, this IP should be used when connecting through a proxy
idintDC ID
ip_addressstringIP address of DC
portintPort
secretflags.10?bytesIf the tcpo_only flag is set, specifies the secret to use when connecting using transport obfuscation
-

Type

-

DcOption

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

-

MTProto transports

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/decryptedMessage.html b/data/corefork.telegram.org/constructor/decryptedMessage.html deleted file mode 100644 index 7554483446..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessage.html +++ /dev/null @@ -1,217 +0,0 @@ - - - - - decryptedMessage - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessage

- -

Contents of an encrypted message.

-

- -
-
===8===
-decryptedMessage#1f814f1f random_id:long random_bytes:bytes message:string media:DecryptedMessageMedia = DecryptedMessage;
-
-===17===
-decryptedMessage#204d3878 random_id:long ttl:int message:string media:DecryptedMessageMedia = DecryptedMessage;
-
-===45===
-decryptedMessage#36b091de flags:# random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long = DecryptedMessage;
-
-===73===
-decryptedMessage#91cc4674 flags:# no_webpage:flags.1?true silent:flags.5?true random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long grouped_id:flags.17?long = DecryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields (added in layer 45)
no_webpageflags.1?trueWhether the webpage preview is disabled
silentflags.5?trueWhether this is a silent message (no notification triggered)
random_idlongRandom message ID, assigned by the author of message.
Must be equal to the ID passed to sending method.
ttlintMessage lifetime. Has higher priority than decryptedMessageActionSetMessageTTL.
Parameter added in Layer 17.
messagestringMessage text
mediaflags.9?DecryptedMessageMediaMedia content
entitiesflags.7?Vector<MessageEntity>Message entities for styled text (parameter added in layer 45)
via_bot_nameflags.11?stringSpecifies the ID of the inline bot that generated the message (parameter added in layer 45)
reply_to_random_idflags.3?longRandom message ID of the message this message replies to (parameter added in layer 45)
grouped_idflags.17?longRandom group ID, assigned by the author of message.
Multiple encrypted messages with a photo attached and with the same group ID indicate an album or grouped media (parameter added in layer 45)
-

Type

-

DecryptedMessage

-

Related pages

-

decryptedMessageActionSetMessageTTL

-

Setting of a message lifetime after reading.

-

Upon receiving such message the client shall start deleting of all messages of an encrypted chat ttl_seconds seconds after the messages were read by user.

-

Layers

-

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

-

Styled text with message entities

-

How to create styled text with message entities

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionCommitKey.html b/data/corefork.telegram.org/constructor/decryptedMessageActionCommitKey.html deleted file mode 100644 index 8c83312adc..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessageActionCommitKey.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - decryptedMessageActionCommitKey - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionCommitKey

- -

Commit new key, see rekeying process

-

- -
-
===20===
-decryptedMessageActionCommitKey#ec2e0b9b exchange_id:long key_fingerprint:long = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
exchange_idlongExchange ID, see rekeying process
key_fingerprintlongKey fingerprint, see rekeying process
-

Type

-

DecryptedMessageAction

-

Related pages

-

Perfect Forward Secrecy

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionDeleteMessages.html b/data/corefork.telegram.org/constructor/decryptedMessageActionDeleteMessages.html deleted file mode 100644 index d344876129..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessageActionDeleteMessages.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - decryptedMessageActionDeleteMessages - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionDeleteMessages

- -

Deleted messages.

-

- -
-
===8===
-decryptedMessageActionDeleteMessages#65614304 random_ids:Vector<long> = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
random_idsVector<long>List of deleted message IDs
-

Type

-

DecryptedMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionFlushHistory.html b/data/corefork.telegram.org/constructor/decryptedMessageActionFlushHistory.html deleted file mode 100644 index 9f6a0b104b..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessageActionFlushHistory.html +++ /dev/null @@ -1,133 +0,0 @@ - - - - - decryptedMessageActionFlushHistory - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionFlushHistory

- -

The entire message history has been deleted.

-

- -
-
===8===
-decryptedMessageActionFlushHistory#6719e45c = DecryptedMessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

DecryptedMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionNotifyLayer.html b/data/corefork.telegram.org/constructor/decryptedMessageActionNotifyLayer.html deleted file mode 100644 index d1f8f0e6b9..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessageActionNotifyLayer.html +++ /dev/null @@ -1,151 +0,0 @@ - - - - - decryptedMessageActionNotifyLayer - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionNotifyLayer

- -

A notification stating the API layer that is used by the client. You should use your current layer and take notice of the layer used on the other side of a conversation when sending messages.

-

- -
-
===17===
-decryptedMessageActionNotifyLayer#f3048883 layer:int = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
layerintLayer number, must be 17 or higher (this contructor was introduced in Layer 17).
-

Type

-

DecryptedMessageAction

-

Related pages

-

Layers

-

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionReadMessages.html b/data/corefork.telegram.org/constructor/decryptedMessageActionReadMessages.html deleted file mode 100644 index 9425a41915..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessageActionReadMessages.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - decryptedMessageActionReadMessages - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionReadMessages

- -

Messages marked as read.

-

- -
-
===8===
-decryptedMessageActionReadMessages#c4f40be random_ids:Vector<long> = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
random_idsVector<long>List of message IDs
-

Type

-

DecryptedMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionRequestKey.html b/data/corefork.telegram.org/constructor/decryptedMessageActionRequestKey.html deleted file mode 100644 index 93c0839c72..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessageActionRequestKey.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - decryptedMessageActionRequestKey - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionRequestKey

- -

Request rekeying, see rekeying process

-

- -
-
===20===
-decryptedMessageActionRequestKey#f3c9611b exchange_id:long g_a:bytes = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
exchange_idlongExchange ID
g_abytesg_a, see rekeying process
-

Type

-

DecryptedMessageAction

-

Related pages

-

Perfect Forward Secrecy

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionResend.html b/data/corefork.telegram.org/constructor/decryptedMessageActionResend.html deleted file mode 100644 index 99518e6e15..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessageActionResend.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - decryptedMessageActionResend - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionResend

- -

Request for the other party in a Secret Chat to automatically resend a contiguous range of previously sent messages, as explained in Sequence number is Secret Chats.

-

- -
-
===17===
-decryptedMessageActionResend#511110b0 start_seq_no:int end_seq_no:int = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
start_seq_nointout_seq_no of the first message to be resent, with correct parity
end_seq_nointout_seq_no of the last message to be resent, with same parity.
-

Type

-

DecryptedMessageAction

-

Related pages

-

Sequence numbers in Secret Chats

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionScreenshotMessages.html b/data/corefork.telegram.org/constructor/decryptedMessageActionScreenshotMessages.html deleted file mode 100644 index d06a9336db..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessageActionScreenshotMessages.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - decryptedMessageActionScreenshotMessages - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionScreenshotMessages

- -

A screenshot was taken.

-

- -
-
===8===
-decryptedMessageActionScreenshotMessages#8ac1f475 random_ids:Vector<long> = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
random_idsVector<long>List of affected message ids (that appeared on the screenshot)
-

Type

-

DecryptedMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionSetMessageTTL.html b/data/corefork.telegram.org/constructor/decryptedMessageActionSetMessageTTL.html deleted file mode 100644 index cc3520fbaf..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessageActionSetMessageTTL.html +++ /dev/null @@ -1,149 +0,0 @@ - - - - - decryptedMessageActionSetMessageTTL - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionSetMessageTTL

- -

Setting of a message lifetime after reading.

-

Upon receiving such message the client shall start deleting of all messages of an encrypted chat ttl_seconds seconds after the messages were read by user.

-

- -
-
===8===
-decryptedMessageActionSetMessageTTL#a1733aec ttl_seconds:int = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
ttl_secondsintLifetime in seconds
-

Type

-

DecryptedMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/decryptedMessageActionTyping.html b/data/corefork.telegram.org/constructor/decryptedMessageActionTyping.html deleted file mode 100644 index 3b3a132586..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessageActionTyping.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - decryptedMessageActionTyping - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageActionTyping

- -

User is preparing a message: typing, recording, uploading, etc.

-

- -
-
===17===
-decryptedMessageActionTyping#ccb27641 action:SendMessageAction = DecryptedMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
actionSendMessageActionType of action
-

Type

-

DecryptedMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/decryptedMessageLayer.html b/data/corefork.telegram.org/constructor/decryptedMessageLayer.html deleted file mode 100644 index 91eb77ea6e..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessageLayer.html +++ /dev/null @@ -1,173 +0,0 @@ - - - - - decryptedMessageLayer - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageLayer

- -

Sets the layer number for the contents of an encrypted message.

-

- -
-
===17===
-decryptedMessageLayer#1be31789 random_bytes:bytes layer:int in_seq_no:int out_seq_no:int message:DecryptedMessage = DecryptedMessageLayer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
random_bytesbytesSet of random bytes to prevent content recognition in short encrypted messages.
Clients are required to check that there are at least 15 random bytes included in each message. Messages with less than 15 random bytes must be ignored.
Parameter moved here from decryptedMessage in Layer 17.
layerintLayer number. Mimimal value - 17 (the layer in which the constructor was added).
in_seq_noint2x the number of messages in the sender's inbox (including deleted and service messages), incremented by 1 if current user was not the chat creator
Parameter added in Layer 17.
out_seq_noint2x the number of messages in the recipient's inbox (including deleted and service messages), incremented by 1 if current user was the chat creator
Parameter added in Layer 17.
messageDecryptedMessageThe content of message itself
-

Type

-

DecryptedMessageLayer

-

Related pages

-

decryptedMessage

-

Contents of an encrypted message.

-

Layers

-

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaAudio.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaAudio.html deleted file mode 100644 index c851b4dcd3..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessageMediaAudio.html +++ /dev/null @@ -1,174 +0,0 @@ - - - - - decryptedMessageMediaAudio - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaAudio

- -

Audio file attached to a secret chat message.

-

- -
-
===8===
-decryptedMessageMediaAudio#6080758f duration:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-
-===17===
-decryptedMessageMediaAudio#57e0a9cb duration:int mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
durationintAudio duration in seconds
mime_typestringMIME-type of the audio file
Parameter added in Layer 13.
sizeintFile size
keybytesKey to decrypt the attached media file
ivbytesInitialization vector
-

Type

-

DecryptedMessageMedia

-

Related pages

-

Layers

-

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaContact.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaContact.html deleted file mode 100644 index ff7d3c3315..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessageMediaContact.html +++ /dev/null @@ -1,163 +0,0 @@ - - - - - decryptedMessageMediaContact - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaContact

- -

Contact attached to an encrypted message.

-

- -
-
===8===
-decryptedMessageMediaContact#588a0a97 phone_number:string first_name:string last_name:string user_id:int = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number
first_namestringContact's first name
last_namestringContact's last name
user_idintTelegram User ID of signed-up contact
-

Type

-

DecryptedMessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaDocument.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaDocument.html deleted file mode 100644 index 1cef20c97e..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessageMediaDocument.html +++ /dev/null @@ -1,191 +0,0 @@ - - - - - decryptedMessageMediaDocument - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaDocument

- -

Document attached to a message in a secret chat.

-

- -
-
===8===
-decryptedMessageMediaDocument#b095434b thumb:bytes thumb_w:int thumb_h:int file_name:string mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
-
-===45===
-decryptedMessageMediaDocument#7afe8ae2 thumb:bytes thumb_w:int thumb_h:int mime_type:string size:int key:bytes iv:bytes attributes:Vector<DocumentAttribute> caption:string = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
thumbbytesThumbnail-file contents (JPEG-file, quality 55, set in a 90x90 square)
thumb_wintThumbnail width
thumb_hintThumbnail height
mime_typestringFile MIME-type
sizeintDocument size
keybytesKey to decrypt the attached document file
ivbytesInitialization
attributesVector<DocumentAttribute>Document attributes for media types
captionstringCaption
-

Type

-

DecryptedMessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaEmpty.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaEmpty.html deleted file mode 100644 index c98cd0bdb7..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessageMediaEmpty.html +++ /dev/null @@ -1,133 +0,0 @@ - - - - - decryptedMessageMediaEmpty - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaEmpty

- -

Empty constructor, no media content.

-

- -
-
===8===
-decryptedMessageMediaEmpty#89f5c4a = DecryptedMessageMedia;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

DecryptedMessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaExternalDocument.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaExternalDocument.html deleted file mode 100644 index a55dd1e305..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessageMediaExternalDocument.html +++ /dev/null @@ -1,183 +0,0 @@ - - - - - decryptedMessageMediaExternalDocument - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaExternalDocument

- -

Non-e2e documented forwarded from non-secret chat

-

- -
-
===23===
-decryptedMessageMediaExternalDocument#fa95b0dd id:long access_hash:long date:int mime_type:string size:int thumb:PhotoSize dc_id:int attributes:Vector<DocumentAttribute> = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongDocument ID
access_hashlongaccess hash
dateintDate
mime_typestringMime type
sizeintSize
thumbPhotoSizeThumbnail
dc_idintDC ID
attributesVector<DocumentAttribute>Attributes for media types
-

Type

-

DecryptedMessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaGeoPoint.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaGeoPoint.html deleted file mode 100644 index 5ba4c6c0ed..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessageMediaGeoPoint.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - decryptedMessageMediaGeoPoint - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaGeoPoint

- -

GeoPont attached to an encrypted message.

-

- -
-
===8===
-decryptedMessageMediaGeoPoint#35480a59 lat:double long:double = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
latdoubleLatitude of point
longdoubleLongtitude of point
-

Type

-

DecryptedMessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaPhoto.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaPhoto.html deleted file mode 100644 index 540a8d5ba9..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessageMediaPhoto.html +++ /dev/null @@ -1,191 +0,0 @@ - - - - - decryptedMessageMediaPhoto - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaPhoto

- -

Photo attached to an encrypted message.

-

- -
-
===8===
-decryptedMessageMediaPhoto#32798a8c thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-
-===45===
-decryptedMessageMediaPhoto#f1fa8d78 thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
thumbbytesContent of thumbnail file (JPEGfile, quality 55, set in a square 90x90)
thumb_wintThumbnail width
thumb_hintThumbnail height
wintPhoto width
hintPhoto height
sizeintSize of the photo in bytes
keybytesKey to decrypt an attached file with a full version
ivbytesInitialization vector
captionstringCaption
-

Type

-

DecryptedMessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaVenue.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaVenue.html deleted file mode 100644 index 1937498189..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessageMediaVenue.html +++ /dev/null @@ -1,173 +0,0 @@ - - - - - decryptedMessageMediaVenue - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaVenue

- -

Venue

-

- -
-
===45===
-decryptedMessageMediaVenue#8a0df56f lat:double long:double title:string address:string provider:string venue_id:string = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
latdoubleLatitude of venue
longdoubleLongitude of venue
titlestringVenue name
addressstringAddress
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
-

Type

-

DecryptedMessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaVideo.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaVideo.html deleted file mode 100644 index c4f8f7d41f..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessageMediaVideo.html +++ /dev/null @@ -1,207 +0,0 @@ - - - - - decryptedMessageMediaVideo - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaVideo

- -

Video attached to an encrypted message.

-

- -
-
===8===
-decryptedMessageMediaVideo#4cee6ef3 thumb:bytes thumb_w:int thumb_h:int duration:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-
-===17===
-decryptedMessageMediaVideo#524a415d thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-
-===45===
-decryptedMessageMediaVideo#970c8c0e thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
thumbbytesContent of thumbnail file (JPEG file, quality 55, set in a square 90x90)
thumb_wintThumbnail width
thumb_hintThumbnail height
durationintDuration of video in seconds
mime_typestringMIME-type of the video file
Parameter added in Layer 17.
wintImage width
hintImage height
sizeintFile size
keybytesKey to decrypt the attached video file
ivbytesInitialization vector
captionstringCaption
-

Type

-

DecryptedMessageMedia

-

Related pages

-

Layers

-

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/decryptedMessageMediaWebPage.html b/data/corefork.telegram.org/constructor/decryptedMessageMediaWebPage.html deleted file mode 100644 index 30c07438dc..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessageMediaWebPage.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - decryptedMessageMediaWebPage - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageMediaWebPage

- -

Webpage preview

-

- -
-
===45===
-decryptedMessageMediaWebPage#e50511d8 url:string = DecryptedMessageMedia;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
urlstringURL of webpage
-

Type

-

DecryptedMessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/decryptedMessageService.html b/data/corefork.telegram.org/constructor/decryptedMessageService.html deleted file mode 100644 index 5671030eee..0000000000 --- a/data/corefork.telegram.org/constructor/decryptedMessageService.html +++ /dev/null @@ -1,156 +0,0 @@ - - - - - decryptedMessageService - - - - - - - - - - - - - -
- -
-
-
- -

decryptedMessageService

- -

Contents of an encrypted service message.

-

- -
-
===8===
-decryptedMessageService#aa48327d random_id:long random_bytes:bytes action:DecryptedMessageAction = DecryptedMessage;
-
-===17===
-decryptedMessageService#73164160 random_id:long action:DecryptedMessageAction = DecryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
random_idlongRandom message ID, assigned by the message author.
Must be equal to the ID passed to the sending method.
actionDecryptedMessageActionAction relevant to the service message
-

Type

-

DecryptedMessage

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/dialogFilter.html b/data/corefork.telegram.org/constructor/dialogFilter.html deleted file mode 100644 index d626f4f8a4..0000000000 --- a/data/corefork.telegram.org/constructor/dialogFilter.html +++ /dev/null @@ -1,220 +0,0 @@ - - - - - dialogFilter - - - - - - - - - - - - - -
- -
-
-
- -

dialogFilter

- -

Dialog filter AKA folder

-

- -
-
dialogFilter#7438f7e8 flags:# contacts:flags.0?true non_contacts:flags.1?true groups:flags.2?true broadcasts:flags.3?true bots:flags.4?true exclude_muted:flags.11?true exclude_read:flags.12?true exclude_archived:flags.13?true id:int title:string emoticon:flags.25?string pinned_peers:Vector<InputPeer> include_peers:Vector<InputPeer> exclude_peers:Vector<InputPeer> = DialogFilter;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
contactsflags.0?trueWhether to include all contacts in this folder
non_contactsflags.1?trueWhether to include all non-contacts in this folder
groupsflags.2?trueWhether to include all groups in this folder
broadcastsflags.3?trueWhether to include all channels in this folder
botsflags.4?trueWhether to include all bots in this folder
exclude_mutedflags.11?trueWhether to exclude muted chats from this folder
exclude_readflags.12?trueWhether to exclude read chats from this folder
exclude_archivedflags.13?trueWhether to exclude archived chats from this folder
idintFolder ID
titlestringFolder name
emoticonflags.25?stringFolder emoticon
pinned_peersVector<InputPeer>Pinned chats, folders can have unlimited pinned chats
include_peersVector<InputPeer>Include the following chats in this folder
exclude_peersVector<InputPeer>Exclude the following chats from this folder
-

Type

-

DialogFilter

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/dialogFilterSuggested.html b/data/corefork.telegram.org/constructor/dialogFilterSuggested.html deleted file mode 100644 index a2478b77f9..0000000000 --- a/data/corefork.telegram.org/constructor/dialogFilterSuggested.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - dialogFilterSuggested - - - - - - - - - - - - - -
- -
-
-
- -

dialogFilterSuggested

- -

Suggested folders

-

- -
-
dialogFilterSuggested#77744d4a filter:DialogFilter description:string = DialogFilterSuggested;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
filterDialogFilterFolder info
descriptionstringFolder description
-

Type

-

DialogFilterSuggested

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/dialogFolder.html b/data/corefork.telegram.org/constructor/dialogFolder.html deleted file mode 100644 index 429c0136a0..0000000000 --- a/data/corefork.telegram.org/constructor/dialogFolder.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - dialogFolder - - - - - - - - - - - - - -
- -
-
-
- -

dialogFolder

- -

Dialog in folder

-

- -
-
dialogFolder#71bd134c flags:# pinned:flags.2?true folder:Folder peer:Peer top_message:int unread_muted_peers_count:int unread_unmuted_peers_count:int unread_muted_messages_count:int unread_unmuted_messages_count:int = Dialog;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.2?trueIs this folder pinned
folderFolderThe folder
peerPeerPeer in folder
top_messageintLatest message ID of dialog
unread_muted_peers_countintNumber of unread muted peers in folder
unread_unmuted_peers_countintNumber of unread unmuted peers in folder
unread_muted_messages_countintNumber of unread messages from muted peers in folder
unread_unmuted_messages_countintNumber of unread messages from unmuted peers in folder
-

Type

-

Dialog

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/dialogPeer.html b/data/corefork.telegram.org/constructor/dialogPeer.html deleted file mode 100644 index 2f4d085903..0000000000 --- a/data/corefork.telegram.org/constructor/dialogPeer.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - dialogPeer - - - - - - - - - - - - - -
- -
-
-
- -

dialogPeer

- -

Peer

-

- -
-
dialogPeer#e56dbf05 peer:Peer = DialogPeer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerPeer
-

Type

-

DialogPeer

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/dialogPeerFolder.html b/data/corefork.telegram.org/constructor/dialogPeerFolder.html deleted file mode 100644 index 597fa26ac2..0000000000 --- a/data/corefork.telegram.org/constructor/dialogPeerFolder.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - dialogPeerFolder - - - - - - - - - - - - - -
- -
-
-
- -

dialogPeerFolder

- -

Peer folder

-

- -
-
dialogPeerFolder#514519e2 folder_id:int = DialogPeer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
folder_idintPeer folder ID, for more info click here
-

Type

-

DialogPeer

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/document.html b/data/corefork.telegram.org/constructor/document.html deleted file mode 100644 index c1b6cfaa38..0000000000 --- a/data/corefork.telegram.org/constructor/document.html +++ /dev/null @@ -1,200 +0,0 @@ - - - - - document - - - - - - - - - - - - - -
- -
-
-
- -

document

- -

Document

-

- -
-
document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idlongDocument ID
access_hashlongCheck sum, dependant on document ID
file_referencebytesFile reference
dateintCreation date
mime_typestringMIME type
sizeintSize
thumbsflags.0?Vector<PhotoSize>Thumbnails
video_thumbsflags.1?Vector<VideoSize>Video thumbnails
dc_idintDC ID
attributesVector<DocumentAttribute>Attributes
-

Type

-

Document

-

Related pages

-

File references

-

How to handle file references.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/documentAttributeAnimated.html b/data/corefork.telegram.org/constructor/documentAttributeAnimated.html deleted file mode 100644 index 3b20d03ff2..0000000000 --- a/data/corefork.telegram.org/constructor/documentAttributeAnimated.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - documentAttributeAnimated - - - - - - - - - - - - - -
- -
-
-
- -

documentAttributeAnimated

- -

Defines an animated GIF

-

- -
-
documentAttributeAnimated#11b58939 = DocumentAttribute;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

DocumentAttribute

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/documentAttributeAudio.html b/data/corefork.telegram.org/constructor/documentAttributeAudio.html deleted file mode 100644 index 0013fe324e..0000000000 --- a/data/corefork.telegram.org/constructor/documentAttributeAudio.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - documentAttributeAudio - - - - - - - - - - - - - -
- -
-
-
- -

documentAttributeAudio

- -

Represents an audio file

-

- -
-
documentAttributeAudio#9852f9c6 flags:# voice:flags.10?true duration:int title:flags.0?string performer:flags.1?string waveform:flags.2?bytes = DocumentAttribute;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
voiceflags.10?trueWhether this is a voice message
durationintDuration in seconds
titleflags.0?stringName of song
performerflags.1?stringPerformer
waveformflags.2?bytesWaveform
-

Type

-

DocumentAttribute

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/documentAttributeFilename.html b/data/corefork.telegram.org/constructor/documentAttributeFilename.html deleted file mode 100644 index c494a33e0d..0000000000 --- a/data/corefork.telegram.org/constructor/documentAttributeFilename.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - documentAttributeFilename - - - - - - - - - - - - - -
- -
-
-
- -

documentAttributeFilename

- -

A simple document with a file name

-

- -
-
documentAttributeFilename#15590068 file_name:string = DocumentAttribute;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
file_namestringThe file name
-

Type

-

DocumentAttribute

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/documentAttributeHasStickers.html b/data/corefork.telegram.org/constructor/documentAttributeHasStickers.html deleted file mode 100644 index da3e566b36..0000000000 --- a/data/corefork.telegram.org/constructor/documentAttributeHasStickers.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - documentAttributeHasStickers - - - - - - - - - - - - - -
- -
-
-
- -

documentAttributeHasStickers

- -

Whether the current document has stickers attached

-

- -
-
documentAttributeHasStickers#9801d2f7 = DocumentAttribute;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

DocumentAttribute

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/documentAttributeImageSize.html b/data/corefork.telegram.org/constructor/documentAttributeImageSize.html deleted file mode 100644 index 731d162f44..0000000000 --- a/data/corefork.telegram.org/constructor/documentAttributeImageSize.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - documentAttributeImageSize - - - - - - - - - - - - - -
- -
-
-
- -

documentAttributeImageSize

- -

Defines the width and height of an image uploaded as document

-

- -
-
documentAttributeImageSize#6c37c15c w:int h:int = DocumentAttribute;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
wintWidth of image
hintHeight of image
-

Type

-

DocumentAttribute

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/documentAttributeSticker.html b/data/corefork.telegram.org/constructor/documentAttributeSticker.html deleted file mode 100644 index 9938523728..0000000000 --- a/data/corefork.telegram.org/constructor/documentAttributeSticker.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - documentAttributeSticker - - - - - - - - - - - - - -
- -
-
-
- -

documentAttributeSticker

- -

Defines a sticker

-

- -
-
documentAttributeSticker#6319d612 flags:# mask:flags.1?true alt:string stickerset:InputStickerSet mask_coords:flags.0?MaskCoords = DocumentAttribute;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
maskflags.1?trueWhether this is a mask sticker
altstringAlternative emoji representation of sticker
stickersetInputStickerSetAssociated stickerset
mask_coordsflags.0?MaskCoordsMask coordinates (if this is a mask sticker, attached to a photo)
-

Type

-

DocumentAttribute

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/documentAttributeVideo.html b/data/corefork.telegram.org/constructor/documentAttributeVideo.html deleted file mode 100644 index 1a26cf9427..0000000000 --- a/data/corefork.telegram.org/constructor/documentAttributeVideo.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - documentAttributeVideo - - - - - - - - - - - - - -
- -
-
-
- -

documentAttributeVideo

- -

Defines a video

-

- -
-
documentAttributeVideo#ef02ce6 flags:# round_message:flags.0?true supports_streaming:flags.1?true duration:int w:int h:int = DocumentAttribute;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
round_messageflags.0?trueWhether this is a round video
supports_streamingflags.1?trueWhether the video supports streaming
durationintDuration in seconds
wintVideo width
hintVideo height
-

Type

-

DocumentAttribute

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/documentEmpty.html b/data/corefork.telegram.org/constructor/documentEmpty.html deleted file mode 100644 index d4f3c52898..0000000000 --- a/data/corefork.telegram.org/constructor/documentEmpty.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - documentEmpty - - - - - - - - - - - - - -
- -
-
-
- -

documentEmpty

- -

Empty constructor, document doesn't exist.

-

- -
-
documentEmpty#36f8c871 id:long = Document;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idlongDocument ID or 0
-

Type

-

Document

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/draftMessage.html b/data/corefork.telegram.org/constructor/draftMessage.html deleted file mode 100644 index 732eb65acb..0000000000 --- a/data/corefork.telegram.org/constructor/draftMessage.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - draftMessage - - - - - - - - - - - - - -
- -
-
-
- -

draftMessage

- -

Represents a message draft.

-

- -
-
draftMessage#fd8e711f flags:# no_webpage:flags.1?true reply_to_msg_id:flags.0?int message:string entities:flags.3?Vector<MessageEntity> date:int = DraftMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.1?trueWhether no webpage preview will be generated
reply_to_msg_idflags.0?intThe message this message will reply to
messagestringThe draft
entitiesflags.3?Vector<MessageEntity>Message entities for styled text.
dateintDate of last update of the draft.
-

Type

-

DraftMessage

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

-

Message drafts

-

How to handle message drafts

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/draftMessageEmpty.html b/data/corefork.telegram.org/constructor/draftMessageEmpty.html deleted file mode 100644 index e1a32aa67f..0000000000 --- a/data/corefork.telegram.org/constructor/draftMessageEmpty.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - draftMessageEmpty - - - - - - - - - - - - - -
- -
-
-
- -

draftMessageEmpty

- -

Empty draft

-

- -
-
draftMessageEmpty#1b0c841a flags:# date:flags.0?int = DraftMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
dateflags.0?intWhen was the draft last updated
-

Type

-

DraftMessage

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/emojiKeyword.html b/data/corefork.telegram.org/constructor/emojiKeyword.html deleted file mode 100644 index d1d008db2b..0000000000 --- a/data/corefork.telegram.org/constructor/emojiKeyword.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - emojiKeyword - - - - - - - - - - - - - -
- -
-
-
- -

emojiKeyword

- -

Emoji keyword

-

- -
-
emojiKeyword#d5b3b9f9 keyword:string emoticons:Vector<string> = EmojiKeyword;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
keywordstringKeyword
emoticonsVector<string>Emojis associated to keyword
-

Type

-

EmojiKeyword

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/emojiKeywordDeleted.html b/data/corefork.telegram.org/constructor/emojiKeywordDeleted.html deleted file mode 100644 index 410880ae9d..0000000000 --- a/data/corefork.telegram.org/constructor/emojiKeywordDeleted.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - emojiKeywordDeleted - - - - - - - - - - - - - -
- -
-
-
- -

emojiKeywordDeleted

- -

Deleted emoji keyword

-

- -
-
emojiKeywordDeleted#236df622 keyword:string emoticons:Vector<string> = EmojiKeyword;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
keywordstringKeyword
emoticonsVector<string>Emojis that were associated to keyword
-

Type

-

EmojiKeyword

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/emojiKeywordsDifference.html b/data/corefork.telegram.org/constructor/emojiKeywordsDifference.html deleted file mode 100644 index 7929b73cd8..0000000000 --- a/data/corefork.telegram.org/constructor/emojiKeywordsDifference.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - emojiKeywordsDifference - - - - - - - - - - - - - -
- -
-
-
- -

emojiKeywordsDifference

- -

Changes to emoji keywords

-

- -
-
emojiKeywordsDifference#5cc761bd lang_code:string from_version:int version:int keywords:Vector<EmojiKeyword> = EmojiKeywordsDifference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
lang_codestringLanguage code for keywords
from_versionintPrevious emoji keyword list version
versionintCurrent version of emoji keyword list
keywordsVector<EmojiKeyword>Emojis associated to keywords
-

Type

-

EmojiKeywordsDifference

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/emojiLanguage.html b/data/corefork.telegram.org/constructor/emojiLanguage.html deleted file mode 100644 index 21453e74f1..0000000000 --- a/data/corefork.telegram.org/constructor/emojiLanguage.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - emojiLanguage - - - - - - - - - - - - - -
- -
-
-
- -

emojiLanguage

- -

Emoji language

-

- -
-
emojiLanguage#b3fb5361 lang_code:string = EmojiLanguage;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
lang_codestringLanguage code
-

Type

-

EmojiLanguage

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/emojiURL.html b/data/corefork.telegram.org/constructor/emojiURL.html deleted file mode 100644 index 0ad49ad698..0000000000 --- a/data/corefork.telegram.org/constructor/emojiURL.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - emojiURL - - - - - - - - - - - - - -
- -
-
-
- -

emojiURL

- -

An HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation

-

- -
-
emojiURL#a575739d url:string = EmojiURL;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
urlstringAn HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation
-

Type

-

EmojiURL

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/encryptedChat.html b/data/corefork.telegram.org/constructor/encryptedChat.html deleted file mode 100644 index 51d0d8cf66..0000000000 --- a/data/corefork.telegram.org/constructor/encryptedChat.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - encryptedChat - - - - - - - - - - - - - -
- -
-
-
- -

encryptedChat

- -

Encrypted chat

-

- -
-
encryptedChat#61f0d4c7 id:int access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long = EncryptedChat;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idintChat ID
access_hashlongCheck sum dependant on the user ID
dateintDate chat was created
admin_idlongChat creator ID
participant_idlongID of the second chat participant
g_a_or_bbytesB = g ^ b mod p, if the currently authorized user is the chat's creator,
or A = g ^ a mod p otherwise
See Wikipedia for more info
key_fingerprintlong64-bit fingerprint of received key
-

Type

-

EncryptedChat

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/encryptedChatDiscarded.html b/data/corefork.telegram.org/constructor/encryptedChatDiscarded.html deleted file mode 100644 index 291feef357..0000000000 --- a/data/corefork.telegram.org/constructor/encryptedChatDiscarded.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - encryptedChatDiscarded - - - - - - - - - - - - - -
- -
-
-
- -

encryptedChatDiscarded

- -

Discarded or deleted chat.

-

- -
-
encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
history_deletedflags.0?trueWhether both users of this secret chat should also remove all of its messages
idintChat ID
-

Type

-

EncryptedChat

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/encryptedChatEmpty.html b/data/corefork.telegram.org/constructor/encryptedChatEmpty.html deleted file mode 100644 index 7d792d3e28..0000000000 --- a/data/corefork.telegram.org/constructor/encryptedChatEmpty.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - encryptedChatEmpty - - - - - - - - - - - - - -
- -
-
-
- -

encryptedChatEmpty

- -

Empty constructor.

-

- -
-
encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idintChat ID
-

Type

-

EncryptedChat

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/encryptedChatRequested.html b/data/corefork.telegram.org/constructor/encryptedChatRequested.html deleted file mode 100644 index b87dc93bec..0000000000 --- a/data/corefork.telegram.org/constructor/encryptedChatRequested.html +++ /dev/null @@ -1,185 +0,0 @@ - - - - - encryptedChatRequested - - - - - - - - - - - - - -
- -
-
-
- -

encryptedChatRequested

- -

Request to create an encrypted chat.

-

- -
-
encryptedChatRequested#48f1d94c flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:long participant_id:long g_a:bytes = EncryptedChat;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.0?intPeer folder ID, for more info click here
idintChat ID
access_hashlongCheck sum depending on user ID
dateintChat creation date
admin_idlongChat creator ID
participant_idlongID of second chat participant
g_abytesA = g ^ a mod p, see Wikipedia
-

Type

-

EncryptedChat

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/encryptedChatWaiting.html b/data/corefork.telegram.org/constructor/encryptedChatWaiting.html deleted file mode 100644 index 6bcd487b67..0000000000 --- a/data/corefork.telegram.org/constructor/encryptedChatWaiting.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - encryptedChatWaiting - - - - - - - - - - - - - -
- -
-
-
- -

encryptedChatWaiting

- -

Chat waiting for approval of second participant.

-

- -
-
encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idintChat ID
access_hashlongChecking sum depending on user ID
dateintDate of chat creation
admin_idlongChat creator ID
participant_idlongID of second chat participant
-

Type

-

EncryptedChat

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/encryptedFile.html b/data/corefork.telegram.org/constructor/encryptedFile.html deleted file mode 100644 index 352f911bfc..0000000000 --- a/data/corefork.telegram.org/constructor/encryptedFile.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - encryptedFile - - - - - - - - - - - - - -
- -
-
-
- -

encryptedFile

- -

Encrypted file.

-

- -
-
encryptedFile#4a70994c id:long access_hash:long size:int dc_id:int key_fingerprint:int = EncryptedFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongFile ID
access_hashlongChecking sum depending on user ID
sizeintFile size in bytes
dc_idintNumber of data centre
key_fingerprintint32-bit fingerprint of key used for file encryption
-

Type

-

EncryptedFile

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/encryptedFileEmpty.html b/data/corefork.telegram.org/constructor/encryptedFileEmpty.html deleted file mode 100644 index 4834a1157a..0000000000 --- a/data/corefork.telegram.org/constructor/encryptedFileEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - encryptedFileEmpty - - - - - - - - - - - - - -
- -
-
-
- -

encryptedFileEmpty

- -

Empty constructor, unexisitng file.

-

- -
-
encryptedFileEmpty#c21f497e = EncryptedFile;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

EncryptedFile

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/encryptedMessage.html b/data/corefork.telegram.org/constructor/encryptedMessage.html deleted file mode 100644 index eac98e7e74..0000000000 --- a/data/corefork.telegram.org/constructor/encryptedMessage.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - encryptedMessage - - - - - - - - - - - - - -
- -
-
-
- -

encryptedMessage

- -

Encrypted message.

-

- -
-
encryptedMessage#ed18c118 random_id:long chat_id:int date:int bytes:bytes file:EncryptedFile = EncryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
random_idlongRandom message ID, assigned by the author of message
chat_idintID of encrypted chat
dateintDate of sending
bytesbytesTL-serialising of DecryptedMessage type, encrypted with the key creatied at stage of chat initialization
fileEncryptedFileAttached encrypted file
-

Type

-

EncryptedMessage

-

Related pages

-

DecryptedMessage

-

Object describes the contents of an encrypted message.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/encryptedMessageService.html b/data/corefork.telegram.org/constructor/encryptedMessageService.html deleted file mode 100644 index e604c3def0..0000000000 --- a/data/corefork.telegram.org/constructor/encryptedMessageService.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - encryptedMessageService - - - - - - - - - - - - - -
- -
-
-
- -

encryptedMessageService

- -

Encrypted service message

-

- -
-
encryptedMessageService#23734b06 random_id:long chat_id:int date:int bytes:bytes = EncryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
random_idlongRandom message ID, assigned by the author of message
chat_idintID of encrypted chat
dateintDate of sending
bytesbytesTL-serialising of DecryptedMessage type, encrypted with the key creatied at stage of chat initialization
-

Type

-

EncryptedMessage

-

Related pages

-

DecryptedMessage

-

Object describes the contents of an encrypted message.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/error.html b/data/corefork.telegram.org/constructor/error.html deleted file mode 100644 index e3ac922a12..0000000000 --- a/data/corefork.telegram.org/constructor/error.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - error - - - - - - - - - - - - - -
- -
-
-
- -

error

- -

Error.

-

- -
-
error#c4b9f9bb code:int text:string = Error;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
codeintError code
textstringMessage
-

Type

-

Error

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/exportedMessageLink.html b/data/corefork.telegram.org/constructor/exportedMessageLink.html deleted file mode 100644 index 74592cf97e..0000000000 --- a/data/corefork.telegram.org/constructor/exportedMessageLink.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - exportedMessageLink - - - - - - - - - - - - - -
- -
-
-
- -

exportedMessageLink

- -

Link to a message in a supergroup/channel

-

- -
-
exportedMessageLink#5dab1af4 link:string html:string = ExportedMessageLink;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
linkstringURL
htmlstringEmbed code
-

Type

-

ExportedMessageLink

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/fileHash.html b/data/corefork.telegram.org/constructor/fileHash.html deleted file mode 100644 index 40d8f4e2f9..0000000000 --- a/data/corefork.telegram.org/constructor/fileHash.html +++ /dev/null @@ -1,171 +0,0 @@ - - - - - FileHash - - - - - - - - - - - - - -
- -
-
-
- -

FileHash

- -

SHA256 Hash of an uploaded file, to be checked for validity after download

-

- -
-
fileHash#6242c773 offset:int limit:int hash:bytes = FileHash;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset from where to start computing SHA-256 hash
limitintLength
hashbytesSHA-256 Hash of file chunk, to be checked for validity after download
-

Type

-

FileHash

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/fileLocationUnavailable.html b/data/corefork.telegram.org/constructor/fileLocationUnavailable.html deleted file mode 100644 index 7ac9543c2b..0000000000 --- a/data/corefork.telegram.org/constructor/fileLocationUnavailable.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - fileLocationUnavailable - - - - - - - - - - - - - -
- -
-
-
- -

fileLocationUnavailable

- -

File is currently unavailable.

-

- -
-
Constructor schema is available as of layer 98. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
volume_idlongServer volume
local_idintFile ID
secretlongChecksum to access the file
-

Type

-

FileLocation

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/folder.html b/data/corefork.telegram.org/constructor/folder.html deleted file mode 100644 index 9a0e6de0d1..0000000000 --- a/data/corefork.telegram.org/constructor/folder.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - folder - - - - - - - - - - - - - -
- -
-
-
- -

folder

- -

Folder

-

- -
-
folder#ff544e65 flags:# autofill_new_broadcasts:flags.0?true autofill_public_groups:flags.1?true autofill_new_correspondents:flags.2?true id:int title:string photo:flags.3?ChatPhoto = Folder;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
autofill_new_broadcastsflags.0?trueAutomatically add new channels to this folder
autofill_public_groupsflags.1?trueAutomatically add joined new public supergroups to this folder
autofill_new_correspondentsflags.2?trueAutomatically add new private chats to this folder
idintFolder ID
titlestringFolder title
photoflags.3?ChatPhotoFolder picture
-

Type

-

Folder

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/folderPeer.html b/data/corefork.telegram.org/constructor/folderPeer.html deleted file mode 100644 index 4396478ce4..0000000000 --- a/data/corefork.telegram.org/constructor/folderPeer.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - folderPeer - - - - - - - - - - - - - -
- -
-
-
- -

folderPeer

- -

Peer in a folder

-

- -
-
folderPeer#e9baa668 peer:Peer folder_id:int = FolderPeer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerFolder peer info
folder_idintPeer folder ID, for more info click here
-

Type

-

FolderPeer

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/game.html b/data/corefork.telegram.org/constructor/game.html deleted file mode 100644 index 78261a30e4..0000000000 --- a/data/corefork.telegram.org/constructor/game.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - game - - - - - - - - - - - - - -
- -
-
-
- -

game

- -

Indicates an already sent game

-

- -
-
game#bdf9653b flags:# id:long access_hash:long short_name:string title:string description:string photo:Photo document:flags.0?Document = Game;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idlongID of the game
access_hashlongAccess hash of the game
short_namestringShort name for the game
titlestringTitle of the game
descriptionstringGame description
photoPhotoGame preview
documentflags.0?DocumentOptional attached document
-

Type

-

Game

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/geoPoint.html b/data/corefork.telegram.org/constructor/geoPoint.html deleted file mode 100644 index d29e902da2..0000000000 --- a/data/corefork.telegram.org/constructor/geoPoint.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - geoPoint - - - - - - - - - - - - - -
- -
-
-
- -

geoPoint

- -

GeoPoint.

-

- -
-
geoPoint#b2a2f663 flags:# long:double lat:double access_hash:long accuracy_radius:flags.0?int = GeoPoint;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
longdoubleLongtitude
latdoubleLatitude
access_hashlongAccess hash
accuracy_radiusflags.0?intThe estimated horizontal accuracy of the location, in meters; as defined by the sender.
-

Type

-

GeoPoint

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/geoPointEmpty.html b/data/corefork.telegram.org/constructor/geoPointEmpty.html deleted file mode 100644 index c55eb338d1..0000000000 --- a/data/corefork.telegram.org/constructor/geoPointEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - geoPointEmpty - - - - - - - - - - - - - -
- -
-
-
- -

geoPointEmpty

- -

Empty constructor.

-

- -
-
geoPointEmpty#1117dd5f = GeoPoint;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

GeoPoint

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/globalPrivacySettings.html b/data/corefork.telegram.org/constructor/globalPrivacySettings.html deleted file mode 100644 index f231f75747..0000000000 --- a/data/corefork.telegram.org/constructor/globalPrivacySettings.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - globalPrivacySettings - - - - - - - - - - - - - -
- -
-
-
- -

globalPrivacySettings

- -

Global privacy settings

-

- -
-
globalPrivacySettings#bea2f424 flags:# archive_and_mute_new_noncontact_peers:flags.0?Bool = GlobalPrivacySettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
archive_and_mute_new_noncontact_peersflags.0?BoolWhether to archive and mute new chats from non-contacts
-

Type

-

GlobalPrivacySettings

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/groupCall.html b/data/corefork.telegram.org/constructor/groupCall.html deleted file mode 100644 index dda6ec54d4..0000000000 --- a/data/corefork.telegram.org/constructor/groupCall.html +++ /dev/null @@ -1,230 +0,0 @@ - - - - - groupCall - - - - - - - - - - - - - -
- -
-
-
- -

groupCall

- -

Info about a group call or livestream

-

- -
-
groupCall#d597650c flags:# join_muted:flags.1?true can_change_join_muted:flags.2?true join_date_asc:flags.6?true schedule_start_subscribed:flags.8?true can_start_video:flags.9?true record_video_active:flags.11?true id:long access_hash:long participants_count:int title:flags.3?string stream_dc_id:flags.4?int record_start_date:flags.5?int schedule_date:flags.7?int unmuted_video_count:flags.10?int unmuted_video_limit:int version:int = GroupCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
join_mutedflags.1?trueWhether the user should be muted upon joining the call
can_change_join_mutedflags.2?trueWhether the current user can change the value of the join_muted flag using phone.toggleGroupCallSettings
join_date_ascflags.6?trueSpecifies the ordering to use when locally sorting by date and displaying in the UI group call participants.
schedule_start_subscribedflags.8?trueWhether we subscribed to the scheduled call
can_start_videoflags.9?trueWhether you can start streaming video into the call
record_video_activeflags.11?trueWhether the group call is currently being recorded
idlongGroup call ID
access_hashlongGroup call access hash
participants_countintParticipant count
titleflags.3?stringGroup call title
stream_dc_idflags.4?intDC ID to be used for livestream chunks
record_start_dateflags.5?intWhen was the recording started
schedule_dateflags.7?intWhen is the call scheduled to start
unmuted_video_countflags.10?intNumber of people currently streaming video into the call
unmuted_video_limitintMaximum number of people allowed to stream video into the call
versionintVersion
-

Type

-

GroupCall

-

Related pages

-

phone.toggleGroupCallSettings

-

Change group call settings

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/groupCallDiscarded.html b/data/corefork.telegram.org/constructor/groupCallDiscarded.html deleted file mode 100644 index fe5ec97959..0000000000 --- a/data/corefork.telegram.org/constructor/groupCallDiscarded.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - groupCallDiscarded - - - - - - - - - - - - - -
- -
-
-
- -

groupCallDiscarded

- -

An ended group call

-

- -
-
groupCallDiscarded#7780bcb4 id:long access_hash:long duration:int = GroupCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongGroup call ID
access_hashlongGroup call access hash
durationintGroup call duration
-

Type

-

GroupCall

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/groupCallParticipant.html b/data/corefork.telegram.org/constructor/groupCallParticipant.html deleted file mode 100644 index 322fcde6e8..0000000000 --- a/data/corefork.telegram.org/constructor/groupCallParticipant.html +++ /dev/null @@ -1,247 +0,0 @@ - - - - - groupCallParticipant - - - - - - - - - - - - - -
- -
-
-
- -

groupCallParticipant

- -

Info about a group call participant

-

- -
-
groupCallParticipant#eba636fe flags:# muted:flags.0?true left:flags.1?true can_self_unmute:flags.2?true just_joined:flags.4?true versioned:flags.5?true min:flags.8?true muted_by_you:flags.9?true volume_by_admin:flags.10?true self:flags.12?true video_joined:flags.15?true peer:Peer date:int active_date:flags.3?int source:int volume:flags.7?int about:flags.11?string raise_hand_rating:flags.13?long video:flags.6?GroupCallParticipantVideo presentation:flags.14?GroupCallParticipantVideo = GroupCallParticipant;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
mutedflags.0?trueWhether the participant is muted
leftflags.1?trueWhether the participant has left
can_self_unmuteflags.2?trueWhether the participant can unmute themselves
just_joinedflags.4?trueWhether the participant has just joined
versionedflags.5?trueIf set, and updateGroupCallParticipants.version < locally stored call.version, info about this participant should be ignored. If (...), and updateGroupCallParticipants.version > call.version+1, the participant list should be refetched using phone.getGroupParticipants.
minflags.8?trueIf not set, the volume and muted_by_you fields can be safely used to overwrite locally cached information; otherwise, volume will contain valid information only if volume_by_admin is set both in the cache and in the received constructor.
muted_by_youflags.9?trueWhether this participant was muted by the current user
volume_by_adminflags.10?trueWhether our volume can only changed by an admin
selfflags.12?trueWhether this participant is the current user
video_joinedflags.15?trueWhether this participant is currently broadcasting video
peerPeerPeer information
dateintWhen did this participant join the group call
active_dateflags.3?intWhen was this participant last active in the group call
sourceintSource ID
volumeflags.7?intVolume, if not set the volume is set to 100%.
aboutflags.11?stringInfo about this participant
raise_hand_ratingflags.13?longSpecifies the UI visualization order of peers with raised hands: peers with a higher rating should be showed first in the list.
videoflags.6?GroupCallParticipantVideoInfo about the video stream the participant is currently broadcasting
presentationflags.14?GroupCallParticipantVideoInfo about the screen sharing stream the participant is currently broadcasting
-

Type

-

GroupCallParticipant

-

Related pages

-

updateGroupCallParticipants

-

The participant list of a certain group call has changed

-

phone.getGroupParticipants

-

Get group call participants

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/groupCallParticipantVideo.html b/data/corefork.telegram.org/constructor/groupCallParticipantVideo.html deleted file mode 100644 index 50f7c9cba5..0000000000 --- a/data/corefork.telegram.org/constructor/groupCallParticipantVideo.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - groupCallParticipantVideo - - - - - - - - - - - - - -
- -
-
-
- -

groupCallParticipantVideo

- -

Info about a video stream

-

- -
-
groupCallParticipantVideo#67753ac8 flags:# paused:flags.0?true endpoint:string source_groups:Vector<GroupCallParticipantVideoSourceGroup> audio_source:flags.1?int = GroupCallParticipantVideo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
pausedflags.0?trueWhether the stream is currently paused
endpointstringEndpoint
source_groupsVector<GroupCallParticipantVideoSourceGroup>Source groups
audio_sourceflags.1?intAudio source ID
-

Type

-

GroupCallParticipantVideo

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/groupCallParticipantVideoSourceGroup.html b/data/corefork.telegram.org/constructor/groupCallParticipantVideoSourceGroup.html deleted file mode 100644 index 0bdce90ba2..0000000000 --- a/data/corefork.telegram.org/constructor/groupCallParticipantVideoSourceGroup.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - groupCallParticipantVideoSourceGroup - - - - - - - - - - - - - -
- -
-
-
- -

groupCallParticipantVideoSourceGroup

- -

Describes a group of video synchronization source identifiers

-

- -
-
groupCallParticipantVideoSourceGroup#dcb118b7 semantics:string sources:Vector<int> = GroupCallParticipantVideoSourceGroup;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
semanticsstringSDP semantics
sourcesVector<int>Source IDs
-

Type

-

GroupCallParticipantVideoSourceGroup

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/help.appUpdate b/data/corefork.telegram.org/constructor/help.appUpdate deleted file mode 100644 index 2715bcde28..0000000000 --- a/data/corefork.telegram.org/constructor/help.appUpdate +++ /dev/null @@ -1,190 +0,0 @@ - - - - - help.appUpdate - - - - - - - - - - - - - -
- -
-
-
- -

help.appUpdate

- -

An update is available for the application.

-

- -
-
help.appUpdate#ccbbce30 flags:# can_not_skip:flags.0?true id:int version:string text:string entities:Vector<MessageEntity> document:flags.1?Document url:flags.2?string sticker:flags.3?Document = help.AppUpdate;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
can_not_skipflags.0?trueUnskippable, the new info must be shown to the user (with a popup or something else)
idintUpdate ID
versionstringNew version name
textstringText description of the update
entitiesVector<MessageEntity>Message entities for styled text
documentflags.1?DocumentApplication binary
urlflags.2?stringApplication download URL
stickerflags.3?DocumentAssociated sticker
-

Type

-

help.AppUpdate

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/help.countriesList b/data/corefork.telegram.org/constructor/help.countriesList deleted file mode 100644 index 24b6a0db08..0000000000 --- a/data/corefork.telegram.org/constructor/help.countriesList +++ /dev/null @@ -1,155 +0,0 @@ - - - - - help.countriesList - - - - - - - - - - - - - -
- -
-
-
- -

help.countriesList

- -

Name, ISO code, localized name and phone codes/patterns of all available countries

-

- -
-
help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countriesVector<help.Country>Name, ISO code, localized name and phone codes/patterns of all available countries
hashintHash for pagination, for more info click here
-

Type

-

help.CountriesList

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/help.countriesListNotModified b/data/corefork.telegram.org/constructor/help.countriesListNotModified deleted file mode 100644 index 9ef15126cb..0000000000 --- a/data/corefork.telegram.org/constructor/help.countriesListNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - help.countriesListNotModified - - - - - - - - - - - - - -
- -
-
-
- -

help.countriesListNotModified

- -

The country list has not changed

-

- -
-
help.countriesListNotModified#93cc1f32 = help.CountriesList;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

help.CountriesList

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/help.country b/data/corefork.telegram.org/constructor/help.country deleted file mode 100644 index e45e5841b3..0000000000 --- a/data/corefork.telegram.org/constructor/help.country +++ /dev/null @@ -1,172 +0,0 @@ - - - - - help.country - - - - - - - - - - - - - -
- -
-
-
- -

help.country

- -

Name, ISO code, localized name and phone codes/patterns of a specific country

-

- -
-
help.country#c3878e23 flags:# hidden:flags.0?true iso2:string default_name:string name:flags.1?string country_codes:Vector<help.CountryCode> = help.Country;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
hiddenflags.0?trueWhether this country should not be shown in the list
iso2stringISO code of country
default_namestringName of the country in the country's language
nameflags.1?stringName of the country in the user's language, if different from the original name
country_codesVector<help.CountryCode>Phone codes/patterns
-

Type

-

help.Country

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/help.countryCode b/data/corefork.telegram.org/constructor/help.countryCode deleted file mode 100644 index a6df889bf1..0000000000 --- a/data/corefork.telegram.org/constructor/help.countryCode +++ /dev/null @@ -1,162 +0,0 @@ - - - - - help.countryCode - - - - - - - - - - - - - -
- -
-
-
- -

help.countryCode

- -

Country code and phone number pattern of a specific country

-

- -
-
help.countryCode#4203c5ef flags:# country_code:string prefixes:flags.0?Vector<string> patterns:flags.1?Vector<string> = help.CountryCode;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
country_codestringISO country code
prefixesflags.0?Vector<string>Possible phone prefixes
patternsflags.1?Vector<string>Phone patterns: for example, XXX XXX XXX
-

Type

-

help.CountryCode

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/help.deepLinkInfo b/data/corefork.telegram.org/constructor/help.deepLinkInfo deleted file mode 100644 index 79652ae768..0000000000 --- a/data/corefork.telegram.org/constructor/help.deepLinkInfo +++ /dev/null @@ -1,165 +0,0 @@ - - - - - help.deepLinkInfo - - - - - - - - - - - - - -
- -
-
-
- -

help.deepLinkInfo

- -

Deep linking info

-

- -
-
help.deepLinkInfo#6a4ee832 flags:# update_app:flags.0?true message:string entities:flags.1?Vector<MessageEntity> = help.DeepLinkInfo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
update_appflags.0?trueAn update of the app is required to parse this link
messagestringMessage to show to the user
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
-

Type

-

help.DeepLinkInfo

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/help.deepLinkInfoEmpty b/data/corefork.telegram.org/constructor/help.deepLinkInfoEmpty deleted file mode 100644 index 95f2835a74..0000000000 --- a/data/corefork.telegram.org/constructor/help.deepLinkInfoEmpty +++ /dev/null @@ -1,132 +0,0 @@ - - - - - help.deepLinkInfoEmpty - - - - - - - - - - - - - -
- -
-
-
- -

help.deepLinkInfoEmpty

- -

Deep link info empty

-

- -
-
help.deepLinkInfoEmpty#66afa166 = help.DeepLinkInfo;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

help.DeepLinkInfo

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/help.inviteText b/data/corefork.telegram.org/constructor/help.inviteText deleted file mode 100644 index b7a4785f61..0000000000 --- a/data/corefork.telegram.org/constructor/help.inviteText +++ /dev/null @@ -1,147 +0,0 @@ - - - - - help.inviteText - - - - - - - - - - - - - -
- -
-
-
- -

help.inviteText

- -

Text of a text message with an invitation to install Telegram.

-

- -
-
help.inviteText#18cb9f78 message:string = help.InviteText;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
messagestringText of the message
-

Type

-

help.InviteText

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/help.noAppUpdate b/data/corefork.telegram.org/constructor/help.noAppUpdate deleted file mode 100644 index f723c30917..0000000000 --- a/data/corefork.telegram.org/constructor/help.noAppUpdate +++ /dev/null @@ -1,132 +0,0 @@ - - - - - help.noAppUpdate - - - - - - - - - - - - - -
- -
-
-
- -

help.noAppUpdate

- -

No updates are available for the application.

-

- -
-
help.noAppUpdate#c45a6536 = help.AppUpdate;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

help.AppUpdate

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/help.passportConfig b/data/corefork.telegram.org/constructor/help.passportConfig deleted file mode 100644 index 4a9329b2d5..0000000000 --- a/data/corefork.telegram.org/constructor/help.passportConfig +++ /dev/null @@ -1,156 +0,0 @@ - - - - - help.passportConfig - - - - - - - - - - - - - -
- -
-
-
- -

help.passportConfig

- -

Telegram passport configuration

-

- -
-
help.passportConfig#a098d6af hash:int countries_langs:DataJSON = help.PassportConfig;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashintHash for pagination, for more info click here
countries_langsDataJSONLocalization
-

Type

-

help.PassportConfig

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/help.passportConfigNotModified b/data/corefork.telegram.org/constructor/help.passportConfigNotModified deleted file mode 100644 index c11bbac714..0000000000 --- a/data/corefork.telegram.org/constructor/help.passportConfigNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - help.passportConfigNotModified - - - - - - - - - - - - - -
- -
-
-
- -

help.passportConfigNotModified

- -

Password configuration not modified

-

- -
-
help.passportConfigNotModified#bfb9f457 = help.PassportConfig;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

help.PassportConfig

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/help.promoData b/data/corefork.telegram.org/constructor/help.promoData deleted file mode 100644 index 6e48817d29..0000000000 --- a/data/corefork.telegram.org/constructor/help.promoData +++ /dev/null @@ -1,182 +0,0 @@ - - - - - help.promoData - - - - - - - - - - - - - -
- -
-
-
- -

help.promoData

- -

MTProxy/Public Service Announcement information

-

- -
-
help.promoData#8c39793f flags:# proxy:flags.0?true expires:int peer:Peer chats:Vector<Chat> users:Vector<User> psa_type:flags.1?string psa_message:flags.2?string = help.PromoData;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
proxyflags.0?trueMTProxy-related channel
expiresintExpiry of PSA/MTProxy info
peerPeerMTProxy/PSA peer
chatsVector<Chat>Chat info
usersVector<User>User info
psa_typeflags.1?stringPSA type
psa_messageflags.2?stringPSA message
-

Type

-

help.PromoData

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/help.promoDataEmpty b/data/corefork.telegram.org/constructor/help.promoDataEmpty deleted file mode 100644 index b8353b9b47..0000000000 --- a/data/corefork.telegram.org/constructor/help.promoDataEmpty +++ /dev/null @@ -1,147 +0,0 @@ - - - - - help.promoDataEmpty - - - - - - - - - - - - - -
- -
-
-
- -

help.promoDataEmpty

- -

No PSA/MTProxy info is available

-

- -
-
help.promoDataEmpty#98f6ac75 expires:int = help.PromoData;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
expiresintRe-fetch PSA/MTProxy info after the specified number of seconds
-

Type

-

help.PromoData

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/help.recentMeUrls b/data/corefork.telegram.org/constructor/help.recentMeUrls deleted file mode 100644 index 2b6aa06ca9..0000000000 --- a/data/corefork.telegram.org/constructor/help.recentMeUrls +++ /dev/null @@ -1,157 +0,0 @@ - - - - - help.recentMeUrls - - - - - - - - - - - - - -
- -
-
-
- -

help.recentMeUrls

- -

Recent t.me URLs

-

- -
-
help.recentMeUrls#e0310d7 urls:Vector<RecentMeUrl> chats:Vector<Chat> users:Vector<User> = help.RecentMeUrls;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlsVector<RecentMeUrl>URLs
chatsVector<Chat>Chats
usersVector<User>Users
-

Type

-

help.RecentMeUrls

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/help.support b/data/corefork.telegram.org/constructor/help.support deleted file mode 100644 index 67280957a2..0000000000 --- a/data/corefork.telegram.org/constructor/help.support +++ /dev/null @@ -1,152 +0,0 @@ - - - - - help.support - - - - - - - - - - - - - -
- -
-
-
- -

help.support

- -

Info on support user.

-

- -
-
help.support#17c6b5f6 phone_number:string user:User = help.Support;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number
userUserUser
-

Type

-

help.Support

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/help.supportName b/data/corefork.telegram.org/constructor/help.supportName deleted file mode 100644 index f593373bad..0000000000 --- a/data/corefork.telegram.org/constructor/help.supportName +++ /dev/null @@ -1,147 +0,0 @@ - - - - - help.supportName - - - - - - - - - - - - - -
- -
-
-
- -

help.supportName

- -

Localized name for telegram support

-

- -
-
help.supportName#8c05f1c9 name:string = help.SupportName;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
namestringLocalized name
-

Type

-

help.SupportName

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/help.termsOfService b/data/corefork.telegram.org/constructor/help.termsOfService deleted file mode 100644 index 50d6a751fa..0000000000 --- a/data/corefork.telegram.org/constructor/help.termsOfService +++ /dev/null @@ -1,175 +0,0 @@ - - - - - help.termsOfService - - - - - - - - - - - - - -
- -
-
-
- -

help.termsOfService

- -

Info about the latest telegram Terms Of Service

-

- -
-
help.termsOfService#780a0310 flags:# popup:flags.0?true id:DataJSON text:string entities:Vector<MessageEntity> min_age_confirm:flags.1?int = help.TermsOfService;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
popupflags.0?trueWhether a prompt must be showed to the user, in order to accept the new terms.
idDataJSONID of the new terms
textstringText of the new terms
entitiesVector<MessageEntity>Message entities for styled text
min_age_confirmflags.1?intMinimum age required to sign up to telegram, the user must confirm that they is older than the minimum age.
-

Type

-

help.TermsOfService

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/help.termsOfServiceUpdate b/data/corefork.telegram.org/constructor/help.termsOfServiceUpdate deleted file mode 100644 index 66383b5fca..0000000000 --- a/data/corefork.telegram.org/constructor/help.termsOfServiceUpdate +++ /dev/null @@ -1,157 +0,0 @@ - - - - - help.termsOfServiceUpdate - - - - - - - - - - - - - -
- -
-
-
- -

help.termsOfServiceUpdate

- -

Info about an update of telegram's terms of service. If the terms of service are declined, then the account.deleteAccount method should be called with the reason "Decline ToS update"

-

- -
-
help.termsOfServiceUpdate#28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
expiresintNew TOS updates will have to be queried using help.getTermsOfServiceUpdate in expires seconds
terms_of_servicehelp.TermsOfServiceNew terms of service
-

Type

-

help.TermsOfServiceUpdate

-

Related pages

-

help.getTermsOfServiceUpdate

-

Look for updates of telegram's terms of service

-

account.deleteAccount

-

Delete the user's account from the telegram servers. Can be used, for example, to delete the account of a user that provided the login code, but forgot the 2FA password and no recovery method is configured.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/help.termsOfServiceUpdateEmpty b/data/corefork.telegram.org/constructor/help.termsOfServiceUpdateEmpty deleted file mode 100644 index d23471419c..0000000000 --- a/data/corefork.telegram.org/constructor/help.termsOfServiceUpdateEmpty +++ /dev/null @@ -1,150 +0,0 @@ - - - - - help.termsOfServiceUpdateEmpty - - - - - - - - - - - - - -
- -
-
-
- -

help.termsOfServiceUpdateEmpty

- -

No changes were made to telegram's terms of service

-

- -
-
help.termsOfServiceUpdateEmpty#e3309f7f expires:int = help.TermsOfServiceUpdate;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
expiresintNew TOS updates will have to be queried using help.getTermsOfServiceUpdate in expires seconds
-

Type

-

help.TermsOfServiceUpdate

-

Related pages

-

help.getTermsOfServiceUpdate

-

Look for updates of telegram's terms of service

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/help.userInfo b/data/corefork.telegram.org/constructor/help.userInfo deleted file mode 100644 index c6a92bd89f..0000000000 --- a/data/corefork.telegram.org/constructor/help.userInfo +++ /dev/null @@ -1,165 +0,0 @@ - - - - - help.userInfo - - - - - - - - - - - - - -
- -
-
-
- -

help.userInfo

- -

Internal use

-

- -
-
help.userInfo#1eb3758 message:string entities:Vector<MessageEntity> author:string date:int = help.UserInfo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messagestringInfo
entitiesVector<MessageEntity>Message entities for styled text
authorstringAuthor
dateintDate
-

Type

-

help.UserInfo

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/help.userInfoEmpty b/data/corefork.telegram.org/constructor/help.userInfoEmpty deleted file mode 100644 index c0328c4fa8..0000000000 --- a/data/corefork.telegram.org/constructor/help.userInfoEmpty +++ /dev/null @@ -1,132 +0,0 @@ - - - - - help.userInfoEmpty - - - - - - - - - - - - - -
- -
-
-
- -

help.userInfoEmpty

- -

Internal use

-

- -
-
help.userInfoEmpty#f3ae2eed = help.UserInfo;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

help.UserInfo

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/highScore.html b/data/corefork.telegram.org/constructor/highScore.html deleted file mode 100644 index 6647340eb4..0000000000 --- a/data/corefork.telegram.org/constructor/highScore.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - highScore - - - - - - - - - - - - - -
- -
-
-
- -

highScore

- -

Game highscore

-

- -
-
highScore#73a379eb pos:int user_id:long score:int = HighScore;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
posintPosition in highscore list
user_idlongUser ID
scoreintScore
-

Type

-

HighScore

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/importedContact.html b/data/corefork.telegram.org/constructor/importedContact.html deleted file mode 100644 index 0ca8b92a1a..0000000000 --- a/data/corefork.telegram.org/constructor/importedContact.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - importedContact - - - - - - - - - - - - - -
- -
-
-
- -

importedContact

- -

Successfully imported contact.

-

- -
-
importedContact#c13e3c50 user_id:long client_id:long = ImportedContact;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser identifier
client_idlongThe contact's client identifier (passed to one of the InputContact constructors)
-

Type

-

ImportedContact

-

Related pages

-

InputContact

-

Object defines a contact from the user's phonebook.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inlineBotSwitchPM.html b/data/corefork.telegram.org/constructor/inlineBotSwitchPM.html deleted file mode 100644 index 18c7907e2c..0000000000 --- a/data/corefork.telegram.org/constructor/inlineBotSwitchPM.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inlineBotSwitchPM - - - - - - - - - - - - - -
- -
-
-
- -

inlineBotSwitchPM

- -

The bot requested the user to message him in private

-

- -
-
inlineBotSwitchPM#3c20629f text:string start_param:string = InlineBotSwitchPM;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textstringText for the button that switches the user to a private chat with the bot and sends the bot a start message with the parameter start_parameter (can be empty)
start_paramstringThe parameter for the /start parameter
-

Type

-

InlineBotSwitchPM

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html deleted file mode 100644 index 002a226f60..0000000000 --- a/data/corefork.telegram.org/constructor/inlineQueryPeerTypeBroadcast.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - inlineQueryPeerTypeBroadcast - - - - - - - - - - - - - -
- -
-
-
- -

inlineQueryPeerTypeBroadcast

- -

The inline query was sent in a channel

-

- -
-
inlineQueryPeerTypeBroadcast#6334ee9a = InlineQueryPeerType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InlineQueryPeerType

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html deleted file mode 100644 index 3f6e63246f..0000000000 --- a/data/corefork.telegram.org/constructor/inlineQueryPeerTypeMegagroup.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - inlineQueryPeerTypeMegagroup - - - - - - - - - - - - - -
- -
-
-
- -

inlineQueryPeerTypeMegagroup

- -

The inline query was sent in a supergroup

-

- -
-
inlineQueryPeerTypeMegagroup#5ec4be43 = InlineQueryPeerType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InlineQueryPeerType

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inlineQueryPeerTypePM.html b/data/corefork.telegram.org/constructor/inlineQueryPeerTypePM.html deleted file mode 100644 index 5ff1371c8a..0000000000 --- a/data/corefork.telegram.org/constructor/inlineQueryPeerTypePM.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inlineQueryPeerTypePM - - - - - - - - - - - - - -
- -
-
-
- -

inlineQueryPeerTypePM

- -

The inline query was sent in a private chat

-

- -
-
inlineQueryPeerTypePM#833c0fac = InlineQueryPeerType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InlineQueryPeerType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inlineQueryPeerTypeSameBotPM.html b/data/corefork.telegram.org/constructor/inlineQueryPeerTypeSameBotPM.html deleted file mode 100644 index 967c2351eb..0000000000 --- a/data/corefork.telegram.org/constructor/inlineQueryPeerTypeSameBotPM.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inlineQueryPeerTypeSameBotPM - - - - - - - - - - - - - -
- -
-
-
- -

inlineQueryPeerTypeSameBotPM

- -

The inline query was sent in a private chat with the bot itself

-

- -
-
inlineQueryPeerTypeSameBotPM#3081ed9d = InlineQueryPeerType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InlineQueryPeerType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputAppEvent.html b/data/corefork.telegram.org/constructor/inputAppEvent.html deleted file mode 100644 index 17f2ab5451..0000000000 --- a/data/corefork.telegram.org/constructor/inputAppEvent.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputAppEvent - - - - - - - - - - - - - -
- -
-
-
- -

inputAppEvent

- -

Event that occured in the application.

-

- -
-
inputAppEvent#1d1b1245 time:double type:string peer:long data:JSONValue = InputAppEvent;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
timedoubleClient's exact timestamp for the event
typestringType of event
peerlongArbitrary numeric value for more convenient selection of certain event types, or events referring to a certain object
dataJSONValueDetails of the event
-

Type

-

InputAppEvent

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputBotInlineMessageGame.html b/data/corefork.telegram.org/constructor/inputBotInlineMessageGame.html deleted file mode 100644 index 551ba71d02..0000000000 --- a/data/corefork.telegram.org/constructor/inputBotInlineMessageGame.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputBotInlineMessageGame - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageGame

- -

A game

-

- -
-
inputBotInlineMessageGame#4b425864 flags:# reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

InputBotInlineMessage

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputBotInlineMessageID.html b/data/corefork.telegram.org/constructor/inputBotInlineMessageID.html deleted file mode 100644 index 2078c42e9c..0000000000 --- a/data/corefork.telegram.org/constructor/inputBotInlineMessageID.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - inputBotInlineMessageID - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageID

- -

Represents a sent inline message from the perspective of a bot (legacy constructor)

-

- -
-
inputBotInlineMessageID#890c3d89 dc_id:int id:long access_hash:long = InputBotInlineMessageID;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
dc_idintDC ID to use when working with this inline message
idlongID of message, contains both the (32-bit, legacy) owner ID and the message ID, used only for Bot API backwards compatibility with 32-bit user ID.
access_hashlongAccess hash of message
-

Type

-

InputBotInlineMessageID

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputBotInlineMessageID64.html b/data/corefork.telegram.org/constructor/inputBotInlineMessageID64.html deleted file mode 100644 index 366ce8e894..0000000000 --- a/data/corefork.telegram.org/constructor/inputBotInlineMessageID64.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputBotInlineMessageID64 - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageID64

- -

Represents a sent inline message from the perspective of a bot

-

- -
-
inputBotInlineMessageID64#b6d915d7 dc_id:int owner_id:long id:int access_hash:long = InputBotInlineMessageID;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
dc_idintDC ID to use when working with this inline message
owner_idlongID of the owner of this message
idintID of message
access_hashlongAccess hash of message
-

Type

-

InputBotInlineMessageID

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaAuto.html b/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaAuto.html deleted file mode 100644 index 42c7179e3b..0000000000 --- a/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaAuto.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - inputBotInlineMessageMediaAuto - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageMediaAuto

- -

A media

-

- -
-
inputBotInlineMessageMediaAuto#3380c786 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
messagestringCaption
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

InputBotInlineMessage

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaContact.html b/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaContact.html deleted file mode 100644 index fcc605e329..0000000000 --- a/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaContact.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - inputBotInlineMessageMediaContact - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageMediaContact

- -

A contact

-

- -
-
inputBotInlineMessageMediaContact#a6edbffd flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
phone_numberstringPhone number
first_namestringFirst name
last_namestringLast name
vcardstringVCard info
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

InputBotInlineMessage

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaGeo.html b/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaGeo.html deleted file mode 100644 index 371e94d53f..0000000000 --- a/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaGeo.html +++ /dev/null @@ -1,175 +0,0 @@ - - - - - inputBotInlineMessageMediaGeo - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageMediaGeo

- -

Geolocation

-

- -
-
inputBotInlineMessageMediaGeo#96929a85 flags:# geo_point:InputGeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
geo_pointInputGeoPointGeolocation
headingflags.0?intFor live locations, a direction in which the location moves, in degrees; 1-360
periodflags.1?intValidity period
proximity_notification_radiusflags.3?intFor live locations, a maximum distance to another chat member for proximity alerts, in meters (0-100000)
reply_markupflags.2?ReplyMarkupReply markup for bot/inline keyboards
-

Type

-

InputBotInlineMessage

-

Related pages

-

Live geolocation

-

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaInvoice.html b/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaInvoice.html deleted file mode 100644 index 36acf83cd6..0000000000 --- a/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaInvoice.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - inputBotInlineMessageMediaInvoice - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageMediaInvoice

- -

An invoice

-

- -
-
inputBotInlineMessageMediaInvoice#d7e78225 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
titlestringProduct name, 1-32 characters
descriptionstringProduct description, 1-255 characters
photoflags.0?InputWebDocumentInvoice photo
invoiceInvoiceThe invoice
payloadbytesBot-defined invoice payload, 1-128 bytes. This will not be displayed to the user, use for your internal processes.
providerstringPayments provider token, obtained via Botfather
provider_dataDataJSONA JSON-serialized object for data about the invoice, which will be shared with the payment provider. A detailed description of the required fields should be provided by the payment provider.
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

InputBotInlineMessage

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaVenue.html b/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaVenue.html deleted file mode 100644 index bc2feed70c..0000000000 --- a/data/corefork.telegram.org/constructor/inputBotInlineMessageMediaVenue.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - inputBotInlineMessageMediaVenue - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageMediaVenue

- -

Venue

-

- -
-
inputBotInlineMessageMediaVenue#417bbf11 flags:# geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
geo_pointInputGeoPointGeolocation
titlestringVenue name
addressstringAddress
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
venue_typestringVenue type in the provider's database
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

InputBotInlineMessage

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputBotInlineMessageText.html b/data/corefork.telegram.org/constructor/inputBotInlineMessageText.html deleted file mode 100644 index 516fa59a87..0000000000 --- a/data/corefork.telegram.org/constructor/inputBotInlineMessageText.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - inputBotInlineMessageText - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineMessageText

- -

Simple text message

-

- -
-
inputBotInlineMessageText#3dcd7a87 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.0?trueDisable webpage preview
messagestringMessage
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
reply_markupflags.2?ReplyMarkupInline keyboard
-

Type

-

InputBotInlineMessage

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputBotInlineResult.html b/data/corefork.telegram.org/constructor/inputBotInlineResult.html deleted file mode 100644 index cd53bf6a76..0000000000 --- a/data/corefork.telegram.org/constructor/inputBotInlineResult.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - inputBotInlineResult - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineResult

- -

An inline bot result

-

- -
-
inputBotInlineResult#88bf9319 flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?InputWebDocument content:flags.5?InputWebDocument send_message:InputBotInlineMessage = InputBotInlineResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idstringID of result
typestringResult type (see bot API docs)
titleflags.1?stringResult title
descriptionflags.2?stringResult description
urlflags.3?stringURL of result
thumbflags.4?InputWebDocumentThumbnail for result
contentflags.5?InputWebDocumentResult contents
send_messageInputBotInlineMessageMessage to send when the result is selected
-

Type

-

InputBotInlineResult

-

Related pages

-

Telegram Bot API

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputBotInlineResultDocument.html b/data/corefork.telegram.org/constructor/inputBotInlineResultDocument.html deleted file mode 100644 index b438e6a473..0000000000 --- a/data/corefork.telegram.org/constructor/inputBotInlineResultDocument.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - inputBotInlineResultDocument - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineResultDocument

- -

Document (media of any type except for photos)

-

- -
-
inputBotInlineResultDocument#fff8fdc4 flags:# id:string type:string title:flags.1?string description:flags.2?string document:InputDocument send_message:InputBotInlineMessage = InputBotInlineResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idstringResult ID
typestringResult type (see bot API docs)
titleflags.1?stringResult title
descriptionflags.2?stringResult description
documentInputDocumentDocument to send
send_messageInputBotInlineMessageMessage to send when the result is selected
-

Type

-

InputBotInlineResult

-

Related pages

-

Telegram Bot API

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputBotInlineResultGame.html b/data/corefork.telegram.org/constructor/inputBotInlineResultGame.html deleted file mode 100644 index 5bc5fa498e..0000000000 --- a/data/corefork.telegram.org/constructor/inputBotInlineResultGame.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - inputBotInlineResultGame - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineResultGame

- -

Game

-

- -
-
inputBotInlineResultGame#4fa417f2 id:string short_name:string send_message:InputBotInlineMessage = InputBotInlineResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idstringResult ID
short_namestringGame short name
send_messageInputBotInlineMessageMessage to send when the result is selected
-

Type

-

InputBotInlineResult

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputBotInlineResultPhoto.html b/data/corefork.telegram.org/constructor/inputBotInlineResultPhoto.html deleted file mode 100644 index 37918f7619..0000000000 --- a/data/corefork.telegram.org/constructor/inputBotInlineResultPhoto.html +++ /dev/null @@ -1,164 +0,0 @@ - - - - - inputBotInlineResultPhoto - - - - - - - - - - - - - -
- -
-
-
- -

inputBotInlineResultPhoto

- -

Photo

-

- -
-
inputBotInlineResultPhoto#a8d864a7 id:string type:string photo:InputPhoto send_message:InputBotInlineMessage = InputBotInlineResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idstringResult ID
typestringResult type (see bot API docs)
photoInputPhotoPhoto to send
send_messageInputBotInlineMessageMessage to send when the result is selected
-

Type

-

InputBotInlineResult

-

Related pages

-

Telegram Bot API

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputChannel.html b/data/corefork.telegram.org/constructor/inputChannel.html deleted file mode 100644 index c00f8a6ef9..0000000000 --- a/data/corefork.telegram.org/constructor/inputChannel.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputChannel - - - - - - - - - - - - - -
- -
-
-
- -

inputChannel

- -

Represents a channel

-

- -
-
inputChannel#f35aec28 channel_id:long access_hash:long = InputChannel;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idlongChannel ID
access_hashlongAccess hash taken from the channel constructor
-

Type

-

InputChannel

-

Related pages

-

channel

-

Channel/supergroup info

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputChannelEmpty.html b/data/corefork.telegram.org/constructor/inputChannelEmpty.html deleted file mode 100644 index 742f924b98..0000000000 --- a/data/corefork.telegram.org/constructor/inputChannelEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputChannelEmpty - - - - - - - - - - - - - -
- -
-
-
- -

inputChannelEmpty

- -

Represents the absence of a channel

-

- -
-
inputChannelEmpty#ee8c1e86 = InputChannel;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputChannel

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputChannelFromMessage.html b/data/corefork.telegram.org/constructor/inputChannelFromMessage.html deleted file mode 100644 index 659b02a3ee..0000000000 --- a/data/corefork.telegram.org/constructor/inputChannelFromMessage.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - inputChannelFromMessage - - - - - - - - - - - - - -
- -
-
-
- -

inputChannelFromMessage

- -

Defines a min channel that was seen in a certain message of a certain chat.

-

- -
-
inputChannelFromMessage#5b934f9d peer:InputPeer msg_id:int channel_id:long = InputChannel;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat where the channel was seen
msg_idintThe message ID in the chat where the channel was seen
channel_idlongThe channel ID
-

Type

-

InputChannel

-

Related pages

-

Min constructors

-

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputChatPhotoEmpty.html b/data/corefork.telegram.org/constructor/inputChatPhotoEmpty.html deleted file mode 100644 index b4373a221f..0000000000 --- a/data/corefork.telegram.org/constructor/inputChatPhotoEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputChatPhotoEmpty - - - - - - - - - - - - - -
- -
-
-
- -

inputChatPhotoEmpty

- -

Empty constructor, remove group photo.

-

- -
-
inputChatPhotoEmpty#1ca48f57 = InputChatPhoto;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputChatPhoto

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputChatUploadedPhoto.html b/data/corefork.telegram.org/constructor/inputChatUploadedPhoto.html deleted file mode 100644 index 48e5520c95..0000000000 --- a/data/corefork.telegram.org/constructor/inputChatUploadedPhoto.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - inputChatUploadedPhoto - - - - - - - - - - - - - -
- -
-
-
- -

inputChatUploadedPhoto

- -

New photo to be set as group profile photo.

-

- -
-
inputChatUploadedPhoto#c642724e flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = InputChatPhoto;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
fileflags.0?InputFileFile saved in parts using the method upload.saveFilePart
videoflags.1?InputFileSquare video for animated profile picture
video_start_tsflags.2?doubleTimestamp that should be shown as static preview to the user (seconds)
-

Type

-

InputChatPhoto

-

Related pages

-

upload.saveFilePart

-

Saves a part of file for futher sending to one of the methods.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputCheckPasswordEmpty.html b/data/corefork.telegram.org/constructor/inputCheckPasswordEmpty.html deleted file mode 100644 index 46be073bd2..0000000000 --- a/data/corefork.telegram.org/constructor/inputCheckPasswordEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputCheckPasswordEmpty - - - - - - - - - - - - - -
- -
-
-
- -

inputCheckPasswordEmpty

- -

There is no password

-

- -
-
inputCheckPasswordEmpty#9880f658 = InputCheckPasswordSRP;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputCheckPasswordSRP

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputCheckPasswordSRP.html b/data/corefork.telegram.org/constructor/inputCheckPasswordSRP.html deleted file mode 100644 index 90d67dd6f3..0000000000 --- a/data/corefork.telegram.org/constructor/inputCheckPasswordSRP.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - inputCheckPasswordSRP - - - - - - - - - - - - - -
- -
-
-
- -

inputCheckPasswordSRP

- -

Constructor for checking the validity of a 2FA SRP password (see SRP)

-

- -
-
inputCheckPasswordSRP#d27ff082 srp_id:long A:bytes M1:bytes = InputCheckPasswordSRP;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
srp_idlongSRP ID
AbytesA parameter (see SRP)
M1bytesM1 parameter (see SRP)
-

Type

-

InputCheckPasswordSRP

-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputClientProxy.html b/data/corefork.telegram.org/constructor/inputClientProxy.html deleted file mode 100644 index 4b95f6dd7c..0000000000 --- a/data/corefork.telegram.org/constructor/inputClientProxy.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - inputClientProxy - - - - - - - - - - - - - -
- -
-
-
- -

inputClientProxy

- -

Info about an MTProxy used to connect.

-

- -
-
inputClientProxy#75588b3f address:string port:int = InputClientProxy;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
addressstringProxy address
portintProxy port
-

Type

-

InputClientProxy

-

Related pages

-

MTProto transports

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputDialogPeer.html b/data/corefork.telegram.org/constructor/inputDialogPeer.html deleted file mode 100644 index cfba495765..0000000000 --- a/data/corefork.telegram.org/constructor/inputDialogPeer.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputDialogPeer - - - - - - - - - - - - - -
- -
-
-
- -

inputDialogPeer

- -

A peer

-

- -
-
inputDialogPeer#fcaafeb7 peer:InputPeer = InputDialogPeer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
-

Type

-

InputDialogPeer

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputDialogPeerFolder.html b/data/corefork.telegram.org/constructor/inputDialogPeerFolder.html deleted file mode 100644 index ddf849e1c9..0000000000 --- a/data/corefork.telegram.org/constructor/inputDialogPeerFolder.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - inputDialogPeerFolder - - - - - - - - - - - - - -
- -
-
-
- -

inputDialogPeerFolder

- -

All peers in a peer folder

-

- -
-
inputDialogPeerFolder#64600527 folder_id:int = InputDialogPeer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
folder_idintPeer folder ID, for more info click here
-

Type

-

InputDialogPeer

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputDocument.html b/data/corefork.telegram.org/constructor/inputDocument.html deleted file mode 100644 index 4409ad314f..0000000000 --- a/data/corefork.telegram.org/constructor/inputDocument.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputDocument - - - - - - - - - - - - - -
- -
-
-
- -

inputDocument

- -

Defines a video for subsequent interaction.

-

- -
-
inputDocument#1abfb575 id:long access_hash:long file_reference:bytes = InputDocument;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongDocument ID
access_hashlongaccess_hash parameter from the document constructor
file_referencebytesFile reference
-

Type

-

InputDocument

-

Related pages

-

document

-

Document

-

File references

-

How to handle file references.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputDocumentEmpty.html b/data/corefork.telegram.org/constructor/inputDocumentEmpty.html deleted file mode 100644 index cbbc9d14ff..0000000000 --- a/data/corefork.telegram.org/constructor/inputDocumentEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputDocumentEmpty - - - - - - - - - - - - - -
- -
-
-
- -

inputDocumentEmpty

- -

Empty constructor.

-

- -
-
inputDocumentEmpty#72f0eaae = InputDocument;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputDocument

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputDocumentFileLocation.html b/data/corefork.telegram.org/constructor/inputDocumentFileLocation.html deleted file mode 100644 index 0f8478a7cb..0000000000 --- a/data/corefork.telegram.org/constructor/inputDocumentFileLocation.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - inputDocumentFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputDocumentFileLocation

- -

Document location (video, voice, audio, basically every type except photo)

-

- -
-
inputDocumentFileLocation#bad07584 id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongDocument ID
access_hashlongaccess_hash parameter from the document constructor
file_referencebytesFile reference
thumb_sizestringThumbnail size to download the thumbnail
-

Type

-

InputFileLocation

-

Related pages

-

document

-

Document

-

File references

-

How to handle file references.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputEncryptedChat.html b/data/corefork.telegram.org/constructor/inputEncryptedChat.html deleted file mode 100644 index b00b9a492f..0000000000 --- a/data/corefork.telegram.org/constructor/inputEncryptedChat.html +++ /dev/null @@ -1,159 +0,0 @@ - - - - - inputEncryptedChat - - - - - - - - - - - - - -
- -
-
-
- -

inputEncryptedChat

- -

Creates an encrypted chat.

-

- -
-
inputEncryptedChat#f141b5e1 chat_id:int access_hash:long = InputEncryptedChat;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idintChat ID
access_hashlongChecking sum from constructor encryptedChat, encryptedChatWaiting or encryptedChatRequested
-

Type

-

InputEncryptedChat

-

Related pages

-

encryptedChat

-

Encrypted chat

-

encryptedChatWaiting

-

Chat waiting for approval of second participant.

-

encryptedChatRequested

-

Request to create an encrypted chat.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputEncryptedFileBigUploaded.html b/data/corefork.telegram.org/constructor/inputEncryptedFileBigUploaded.html deleted file mode 100644 index 3a4b8d542f..0000000000 --- a/data/corefork.telegram.org/constructor/inputEncryptedFileBigUploaded.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - inputEncryptedFileBigUploaded - - - - - - - - - - - - - -
- -
-
-
- -

inputEncryptedFileBigUploaded

- -

Assigns a new big encrypted file (over 10Mb in size), saved in parts using the method upload.saveBigFilePart.

-

- -
-
inputEncryptedFileBigUploaded#2dc173c8 id:long parts:int key_fingerprint:int = InputEncryptedFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongRandom file id, created by the client
partsintNumber of saved parts
key_fingerprintint32-bit imprint of the key used to encrypt the file
-

Type

-

InputEncryptedFile

-

Related pages

-

upload.saveBigFilePart

-

Saves a part of a large file (over 10Mb in size) to be later passed to one of the methods.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputEncryptedFileEmpty.html b/data/corefork.telegram.org/constructor/inputEncryptedFileEmpty.html deleted file mode 100644 index 4de53fc688..0000000000 --- a/data/corefork.telegram.org/constructor/inputEncryptedFileEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputEncryptedFileEmpty - - - - - - - - - - - - - -
- -
-
-
- -

inputEncryptedFileEmpty

- -

Empty constructor.

-

- -
-
inputEncryptedFileEmpty#1837c364 = InputEncryptedFile;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputEncryptedFile

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputEncryptedFileLocation.html b/data/corefork.telegram.org/constructor/inputEncryptedFileLocation.html deleted file mode 100644 index e67381d504..0000000000 --- a/data/corefork.telegram.org/constructor/inputEncryptedFileLocation.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputEncryptedFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputEncryptedFileLocation

- -

Location of encrypted secret chat file.

-

- -
-
inputEncryptedFileLocation#f5235d55 id:long access_hash:long = InputFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongFile ID, id parameter value from encryptedFile
access_hashlongChecksum, access_hash parameter value from encryptedFile
-

Type

-

InputFileLocation

-

Related pages

-

encryptedFile

-

Encrypted file.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputEncryptedFileUploaded.html b/data/corefork.telegram.org/constructor/inputEncryptedFileUploaded.html deleted file mode 100644 index 46bda50159..0000000000 --- a/data/corefork.telegram.org/constructor/inputEncryptedFileUploaded.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputEncryptedFileUploaded - - - - - - - - - - - - - -
- -
-
-
- -

inputEncryptedFileUploaded

- -

Sets new encrypted file saved by parts using upload.saveFilePart method.

-

- -
-
inputEncryptedFileUploaded#64bd0306 id:long parts:int md5_checksum:string key_fingerprint:int = InputEncryptedFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongRandom file ID created by clien
partsintNumber of saved parts
md5_checksumstringIn case md5-HASH of the (already encrypted) file was transmitted, file content will be checked prior to use
key_fingerprintint32-bit fingerprint of the key used to encrypt a file
-

Type

-

InputEncryptedFile

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputFileBig.html b/data/corefork.telegram.org/constructor/inputFileBig.html deleted file mode 100644 index 5d35533c17..0000000000 --- a/data/corefork.telegram.org/constructor/inputFileBig.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - inputFileBig - - - - - - - - - - - - - -
- -
-
-
- -

inputFileBig

- -

Assigns a big file (over 10Mb in size), saved in part using the method upload.saveBigFilePart.

-

- -
-
inputFileBig#fa4f0bb5 id:long parts:int name:string = InputFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongRandom file id, created by the client
partsintNumber of parts saved
namestringFull file name
-

Type

-

InputFile

-

Related pages

-

upload.saveBigFilePart

-

Saves a part of a large file (over 10Mb in size) to be later passed to one of the methods.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputFileLocation.html b/data/corefork.telegram.org/constructor/inputFileLocation.html deleted file mode 100644 index 05f68762fc..0000000000 --- a/data/corefork.telegram.org/constructor/inputFileLocation.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - inputFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputFileLocation

- -

DEPRECATED location of a photo

-

- -
-
inputFileLocation#dfdaabe1 volume_id:long local_id:int secret:long file_reference:bytes = InputFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
volume_idlongServer volume
local_idintFile identifier
secretlongCheck sum to access the file
file_referencebytesFile reference
-

Type

-

InputFileLocation

-

Related pages

-

File references

-

How to handle file references.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputFolderPeer.html b/data/corefork.telegram.org/constructor/inputFolderPeer.html deleted file mode 100644 index 9a06fbf36e..0000000000 --- a/data/corefork.telegram.org/constructor/inputFolderPeer.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputFolderPeer - - - - - - - - - - - - - -
- -
-
-
- -

inputFolderPeer

- -

Peer in a folder

-

- -
-
inputFolderPeer#fbd2c296 peer:InputPeer folder_id:int = InputFolderPeer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
folder_idintPeer folder ID, for more info click here
-

Type

-

InputFolderPeer

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputGameID.html b/data/corefork.telegram.org/constructor/inputGameID.html deleted file mode 100644 index a66904aded..0000000000 --- a/data/corefork.telegram.org/constructor/inputGameID.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputGameID - - - - - - - - - - - - - -
- -
-
-
- -

inputGameID

- -

Indicates an already sent game

-

- -
-
inputGameID#32c3e77 id:long access_hash:long = InputGame;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlonggame ID from Game constructor
access_hashlongaccess hash from Game constructor
-

Type

-

InputGame

-

Related pages

-

Game

-

Indicates an already sent game

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputGameShortName.html b/data/corefork.telegram.org/constructor/inputGameShortName.html deleted file mode 100644 index 7f0566d85e..0000000000 --- a/data/corefork.telegram.org/constructor/inputGameShortName.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputGameShortName - - - - - - - - - - - - - -
- -
-
-
- -

inputGameShortName

- -

Game by short name

-

- -
-
inputGameShortName#c331e80a bot_id:InputUser short_name:string = InputGame;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
bot_idInputUserThe bot that provides the game
short_namestringThe game's short name
-

Type

-

InputGame

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputGeoPointEmpty.html b/data/corefork.telegram.org/constructor/inputGeoPointEmpty.html deleted file mode 100644 index 141cc1ea2e..0000000000 --- a/data/corefork.telegram.org/constructor/inputGeoPointEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputGeoPointEmpty - - - - - - - - - - - - - -
- -
-
-
- -

inputGeoPointEmpty

- -

Empty GeoPoint constructor.

-

- -
-
inputGeoPointEmpty#e4c123d6 = InputGeoPoint;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputGeoPoint

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputGroupCallStream.html b/data/corefork.telegram.org/constructor/inputGroupCallStream.html deleted file mode 100644 index 927e335d4b..0000000000 --- a/data/corefork.telegram.org/constructor/inputGroupCallStream.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - inputGroupCallStream - - - - - - - - - - - - - -
- -
-
-
- -

inputGroupCallStream

- -

Chunk of a livestream

-

- -
-
inputGroupCallStream#598a92a flags:# call:InputGroupCall time_ms:long scale:int video_channel:flags.0?int video_quality:flags.0?int = InputFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
callInputGroupCallLivestream info
time_mslongTimestamp in milliseconds
scaleintSpecifies the duration of the video segment to fetch in milliseconds, by bitshifting 1000 to the right scale times: duration_ms := 1000 >> scale
video_channelflags.0?intSelected video channel
video_qualityflags.0?intSelected video quality (0 = lowest, 1 = medium, 2 = best)
-

Type

-

InputFileLocation

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputKeyboardButtonUrlAuth.html b/data/corefork.telegram.org/constructor/inputKeyboardButtonUrlAuth.html deleted file mode 100644 index 86a540f219..0000000000 --- a/data/corefork.telegram.org/constructor/inputKeyboardButtonUrlAuth.html +++ /dev/null @@ -1,176 +0,0 @@ - - - - - inputKeyboardButtonUrlAuth - - - - - - - - - - - - - -
- -
-
-
- -

inputKeyboardButtonUrlAuth

- -

Button to request a user to authorize via URL using Seamless Telegram Login.

-

- -
-
inputKeyboardButtonUrlAuth#d02e7fd4 flags:# request_write_access:flags.0?true text:string fwd_text:flags.1?string url:string bot:InputUser = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
request_write_accessflags.0?trueSet this flag to request the permission for your bot to send messages to the user.
textstringButton text
fwd_textflags.1?stringNew text of the button in forwarded messages.
urlstringAn HTTP URL to be opened with user authorization data added to the query string when the button is pressed. If the user refuses to provide authorization data, the original URL without information about the user will be opened. The data added is the same as described in Receiving authorization data.
NOTE: You must always check the hash of the received data to verify the authentication and the integrity of the data as described in Checking authorization.
botInputUserUsername of a bot, which will be used for user authorization. See Setting up a bot for more details. If not specified, the current bot's username will be assumed. The url's domain must be the same as the domain linked with the bot. See Linking your domain to the bot for more details.
-

Type

-

KeyboardButton

-

Related pages

-

Telegram Login Widget

-

messages.acceptUrlAuth

-

Use this to accept a Seamless Telegram Login authorization request, for more info click here »

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMediaContact.html b/data/corefork.telegram.org/constructor/inputMediaContact.html deleted file mode 100644 index 25589fc4a9..0000000000 --- a/data/corefork.telegram.org/constructor/inputMediaContact.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputMediaContact - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaContact

- -

Phonebook contact

-

- -
-
inputMediaContact#f8ab7dfb phone_number:string first_name:string last_name:string vcard:string = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number
first_namestringContact's first name
last_namestringContact's last name
vcardstringContact vcard
-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMediaDice.html b/data/corefork.telegram.org/constructor/inputMediaDice.html deleted file mode 100644 index 37ba2659f4..0000000000 --- a/data/corefork.telegram.org/constructor/inputMediaDice.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - inputMediaDice - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaDice

- -

Send a dice-based animated sticker

-

- -
-
inputMediaDice#e66fbf7b emoticon:string = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
emoticonstringThe emoji, for now 🏀, 🎲 and 🎯 are supported
-

Type

-

InputMedia

-

Related pages

-

Dice

-

Telegram supports sending animated dice emojis.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMediaDocument.html b/data/corefork.telegram.org/constructor/inputMediaDocument.html deleted file mode 100644 index 45d2da48dd..0000000000 --- a/data/corefork.telegram.org/constructor/inputMediaDocument.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputMediaDocument - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaDocument

- -

Forwarded document

-

- -
-
inputMediaDocument#33473058 flags:# id:InputDocument ttl_seconds:flags.0?int query:flags.1?string = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idInputDocumentThe document to be forwarded.
ttl_secondsflags.0?intTime to live of self-destructing document
queryflags.1?stringText query or emoji that was used by the user to find this sticker or GIF: used to improve search result relevance.
-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMediaDocumentExternal.html b/data/corefork.telegram.org/constructor/inputMediaDocumentExternal.html deleted file mode 100644 index 32dce8255a..0000000000 --- a/data/corefork.telegram.org/constructor/inputMediaDocumentExternal.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - inputMediaDocumentExternal - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaDocumentExternal

- -

Document that will be downloaded by the telegram servers

-

- -
-
inputMediaDocumentExternal#fb52dc99 flags:# url:string ttl_seconds:flags.0?int = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
urlstringURL of the document
ttl_secondsflags.0?intSelf-destruct time to live of document
-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMediaEmpty.html b/data/corefork.telegram.org/constructor/inputMediaEmpty.html deleted file mode 100644 index 918d31a688..0000000000 --- a/data/corefork.telegram.org/constructor/inputMediaEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMediaEmpty - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaEmpty

- -

Empty media content of a message.

-

- -
-
inputMediaEmpty#9664f57f = InputMedia;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMediaGame.html b/data/corefork.telegram.org/constructor/inputMediaGame.html deleted file mode 100644 index 460603eefd..0000000000 --- a/data/corefork.telegram.org/constructor/inputMediaGame.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputMediaGame - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaGame

- -

A game

-

- -
-
inputMediaGame#d33f43f3 id:InputGame = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idInputGameThe game to forward
-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMediaGeoLive.html b/data/corefork.telegram.org/constructor/inputMediaGeoLive.html deleted file mode 100644 index d3eea8ada5..0000000000 --- a/data/corefork.telegram.org/constructor/inputMediaGeoLive.html +++ /dev/null @@ -1,175 +0,0 @@ - - - - - inputMediaGeoLive - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaGeoLive

- -

Live geolocation

-

- -
-
inputMediaGeoLive#971fa843 flags:# stopped:flags.0?true geo_point:InputGeoPoint heading:flags.2?int period:flags.1?int proximity_notification_radius:flags.3?int = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
stoppedflags.0?trueWhether sending of the geolocation was stopped
geo_pointInputGeoPointCurrent geolocation
headingflags.2?intFor live locations, a direction in which the location moves, in degrees; 1-360.
periodflags.1?intValidity period of the current location
proximity_notification_radiusflags.3?intFor live locations, a maximum distance to another chat member for proximity alerts, in meters (0-100000)
-

Type

-

InputMedia

-

Related pages

-

Live geolocation

-

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMediaGeoPoint.html b/data/corefork.telegram.org/constructor/inputMediaGeoPoint.html deleted file mode 100644 index a2462be5c9..0000000000 --- a/data/corefork.telegram.org/constructor/inputMediaGeoPoint.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputMediaGeoPoint - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaGeoPoint

- -

Map.

-

- -
-
inputMediaGeoPoint#f9c44144 geo_point:InputGeoPoint = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
geo_pointInputGeoPointGeoPoint
-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMediaInvoice.html b/data/corefork.telegram.org/constructor/inputMediaInvoice.html deleted file mode 100644 index 970538f03e..0000000000 --- a/data/corefork.telegram.org/constructor/inputMediaInvoice.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - inputMediaInvoice - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaInvoice

- -

Generated invoice of a bot payment

-

- -
-
inputMediaInvoice#d9799874 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON start_param:flags.1?string = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
titlestringProduct name, 1-32 characters
descriptionstringProduct description, 1-255 characters
photoflags.0?InputWebDocumentURL of the product photo for the invoice. Can be a photo of the goods or a marketing image for a service. People like it better when they see what they are paying for.
invoiceInvoiceThe actual invoice
payloadbytesBot-defined invoice payload, 1-128 bytes. This will not be displayed to the user, use for your internal processes.
providerstringPayments provider token, obtained via Botfather
provider_dataDataJSONJSON-encoded data about the invoice, which will be shared with the payment provider. A detailed description of required fields should be provided by the payment provider.
start_paramflags.1?stringStart parameter
-

Type

-

InputMedia

-

Related pages

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMediaPhoto.html b/data/corefork.telegram.org/constructor/inputMediaPhoto.html deleted file mode 100644 index 2ee06a9ef7..0000000000 --- a/data/corefork.telegram.org/constructor/inputMediaPhoto.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - inputMediaPhoto - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaPhoto

- -

Forwarded photo

-

- -
-
inputMediaPhoto#b3ba0635 flags:# id:InputPhoto ttl_seconds:flags.0?int = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idInputPhotoPhoto to be forwarded
ttl_secondsflags.0?intTime to live in seconds of self-destructing photo
-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMediaPhotoExternal.html b/data/corefork.telegram.org/constructor/inputMediaPhotoExternal.html deleted file mode 100644 index fa7dd4a1f3..0000000000 --- a/data/corefork.telegram.org/constructor/inputMediaPhotoExternal.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - inputMediaPhotoExternal - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaPhotoExternal

- -

New photo that will be uploaded by the server using the specified URL

-

- -
-
inputMediaPhotoExternal#e5bbfe1a flags:# url:string ttl_seconds:flags.0?int = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
urlstringURL of the photo
ttl_secondsflags.0?intSelf-destruct time to live of photo
-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMediaPoll.html b/data/corefork.telegram.org/constructor/inputMediaPoll.html deleted file mode 100644 index 6c82d9a811..0000000000 --- a/data/corefork.telegram.org/constructor/inputMediaPoll.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - inputMediaPoll - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaPoll

- -

A poll

-

- -
-
inputMediaPoll#f94e5f1 flags:# poll:Poll correct_answers:flags.0?Vector<bytes> solution:flags.1?string solution_entities:flags.1?Vector<MessageEntity> = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
pollPollThe poll to send
correct_answersflags.0?Vector<bytes>Correct answer IDs (for quiz polls)
solutionflags.1?stringExplanation of quiz solution
solution_entitiesflags.1?Vector<MessageEntity>Message entities for styled text
-

Type

-

InputMedia

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMediaUploadedPhoto.html b/data/corefork.telegram.org/constructor/inputMediaUploadedPhoto.html deleted file mode 100644 index ab7fbcd6a2..0000000000 --- a/data/corefork.telegram.org/constructor/inputMediaUploadedPhoto.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - inputMediaUploadedPhoto - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaUploadedPhoto

- -

Photo

-

- -
-
inputMediaUploadedPhoto#1e287d04 flags:# file:InputFile stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
fileInputFileThe uploaded file
stickersflags.0?Vector<InputDocument>Attached mask stickers
ttl_secondsflags.1?intTime to live in seconds of self-destructing photo
-

Type

-

InputMedia

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMediaVenue.html b/data/corefork.telegram.org/constructor/inputMediaVenue.html deleted file mode 100644 index 6c66c3d5a2..0000000000 --- a/data/corefork.telegram.org/constructor/inputMediaVenue.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - inputMediaVenue - - - - - - - - - - - - - -
- -
-
-
- -

inputMediaVenue

- -

Can be used to send a venue geolocation.

-

- -
-
inputMediaVenue#c13d1c11 geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string = InputMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
geo_pointInputGeoPointGeolocation
titlestringVenue name
addressstringPhysical address of the venue
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
venue_typestringVenue type in the provider's database
-

Type

-

InputMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMessageCallbackQuery.html b/data/corefork.telegram.org/constructor/inputMessageCallbackQuery.html deleted file mode 100644 index 4fbb609555..0000000000 --- a/data/corefork.telegram.org/constructor/inputMessageCallbackQuery.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputMessageCallbackQuery - - - - - - - - - - - - - -
- -
-
-
- -

inputMessageCallbackQuery

- -

Used by bots for fetching information about the message that originated a callback query

-

- -
-
inputMessageCallbackQuery#acfa1a7e id:int query_id:long = InputMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idintMessage ID
query_idlongCallback query ID
-

Type

-

InputMessage

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMessageEntityMentionName.html b/data/corefork.telegram.org/constructor/inputMessageEntityMentionName.html deleted file mode 100644 index c5d8251b7b..0000000000 --- a/data/corefork.telegram.org/constructor/inputMessageEntityMentionName.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputMessageEntityMentionName - - - - - - - - - - - - - -
- -
-
-
- -

inputMessageEntityMentionName

- -

Message entity that can be used to create a user user mention: received mentions use the messageEntityMentionName constructor, instead.

-

- -
-
inputMessageEntityMentionName#208e68c9 offset:int length:int user_id:InputUser = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
user_idInputUserIdentifier of the user that was mentioned
-

Type

-

MessageEntity

-

Related pages

-

Mentions

-

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

-

messageEntityMentionName

-

Message entity representing a user mention: for creating a mention use inputMessageEntityMentionName.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMessageID.html b/data/corefork.telegram.org/constructor/inputMessageID.html deleted file mode 100644 index 666cb9f8b9..0000000000 --- a/data/corefork.telegram.org/constructor/inputMessageID.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputMessageID - - - - - - - - - - - - - -
- -
-
-
- -

inputMessageID

- -

Message by ID

-

- -
-
inputMessageID#a676a322 id:int = InputMessage;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idintMessage ID
-

Type

-

InputMessage

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMessagePinned.html b/data/corefork.telegram.org/constructor/inputMessagePinned.html deleted file mode 100644 index b8d8362c5b..0000000000 --- a/data/corefork.telegram.org/constructor/inputMessagePinned.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagePinned - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagePinned

- -

Pinned message

-

- -
-
inputMessagePinned#86872538 = InputMessage;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputMessage

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMessageReplyTo.html b/data/corefork.telegram.org/constructor/inputMessageReplyTo.html deleted file mode 100644 index 1d84516e76..0000000000 --- a/data/corefork.telegram.org/constructor/inputMessageReplyTo.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputMessageReplyTo - - - - - - - - - - - - - -
- -
-
-
- -

inputMessageReplyTo

- -

Message to which the specified message replies to

-

- -
-
inputMessageReplyTo#bad88395 id:int = InputMessage;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idintID of the message that replies to the message we need
-

Type

-

InputMessage

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterChatPhotos.html b/data/corefork.telegram.org/constructor/inputMessagesFilterChatPhotos.html deleted file mode 100644 index bdf9e1b9fa..0000000000 --- a/data/corefork.telegram.org/constructor/inputMessagesFilterChatPhotos.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterChatPhotos - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterChatPhotos

- -

Return only chat photo changes

-

- -
-
inputMessagesFilterChatPhotos#3a20ecb8 = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterContacts.html b/data/corefork.telegram.org/constructor/inputMessagesFilterContacts.html deleted file mode 100644 index dbf1f16b2a..0000000000 --- a/data/corefork.telegram.org/constructor/inputMessagesFilterContacts.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterContacts - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterContacts

- -

Return only messages containing contacts

-

- -
-
inputMessagesFilterContacts#e062db83 = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterDocument.html b/data/corefork.telegram.org/constructor/inputMessagesFilterDocument.html deleted file mode 100644 index 69a1f91cf4..0000000000 --- a/data/corefork.telegram.org/constructor/inputMessagesFilterDocument.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterDocument - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterDocument

- -

Filter for messages containing documents.

-

- -
-
inputMessagesFilterDocument#9eddf188 = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterEmpty.html b/data/corefork.telegram.org/constructor/inputMessagesFilterEmpty.html deleted file mode 100644 index e91b728f51..0000000000 --- a/data/corefork.telegram.org/constructor/inputMessagesFilterEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterEmpty - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterEmpty

- -

Filter is absent.

-

- -
-
inputMessagesFilterEmpty#57e2f66c = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterGeo.html b/data/corefork.telegram.org/constructor/inputMessagesFilterGeo.html deleted file mode 100644 index ee9cf05586..0000000000 --- a/data/corefork.telegram.org/constructor/inputMessagesFilterGeo.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterGeo - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterGeo

- -

Return only messages containing geolocations

-

- -
-
inputMessagesFilterGeo#e7026d0d = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterGif.html b/data/corefork.telegram.org/constructor/inputMessagesFilterGif.html deleted file mode 100644 index d30ea1e4e8..0000000000 --- a/data/corefork.telegram.org/constructor/inputMessagesFilterGif.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterGif - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterGif

- -

Return only messages containing gifs

-

- -
-
inputMessagesFilterGif#ffc86587 = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterMusic.html b/data/corefork.telegram.org/constructor/inputMessagesFilterMusic.html deleted file mode 100644 index 0c5058b919..0000000000 --- a/data/corefork.telegram.org/constructor/inputMessagesFilterMusic.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterMusic - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterMusic

- -

Return only messages containing audio files

-

- -
-
inputMessagesFilterMusic#3751b49e = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterPhoneCalls.html b/data/corefork.telegram.org/constructor/inputMessagesFilterPhoneCalls.html deleted file mode 100644 index 0955269829..0000000000 --- a/data/corefork.telegram.org/constructor/inputMessagesFilterPhoneCalls.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputMessagesFilterPhoneCalls - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterPhoneCalls

- -

Return only phone calls

-

- -
-
inputMessagesFilterPhoneCalls#80c99768 flags:# missed:flags.0?true = MessagesFilter;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
missedflags.0?trueReturn only missed phone calls
-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterPhotoVideo.html b/data/corefork.telegram.org/constructor/inputMessagesFilterPhotoVideo.html deleted file mode 100644 index 9f5c5f4d19..0000000000 --- a/data/corefork.telegram.org/constructor/inputMessagesFilterPhotoVideo.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterPhotoVideo - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterPhotoVideo

- -

Filter for messages containing photos or videos.

-

- -
-
inputMessagesFilterPhotoVideo#56e9f0e4 = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterPhotos.html b/data/corefork.telegram.org/constructor/inputMessagesFilterPhotos.html deleted file mode 100644 index 7f41b10eeb..0000000000 --- a/data/corefork.telegram.org/constructor/inputMessagesFilterPhotos.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterPhotos - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterPhotos

- -

Filter for messages containing photos.

-

- -
-
inputMessagesFilterPhotos#9609a51c = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterPinned.html b/data/corefork.telegram.org/constructor/inputMessagesFilterPinned.html deleted file mode 100644 index e1f1f90ac1..0000000000 --- a/data/corefork.telegram.org/constructor/inputMessagesFilterPinned.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterPinned - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterPinned

- -

Fetch only pinned messages

-

- -
-
inputMessagesFilterPinned#1bb00451 = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterRoundVideo.html b/data/corefork.telegram.org/constructor/inputMessagesFilterRoundVideo.html deleted file mode 100644 index ebaf642993..0000000000 --- a/data/corefork.telegram.org/constructor/inputMessagesFilterRoundVideo.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterRoundVideo - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterRoundVideo

- -

Return only round videos

-

- -
-
inputMessagesFilterRoundVideo#b549da53 = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterRoundVoice.html b/data/corefork.telegram.org/constructor/inputMessagesFilterRoundVoice.html deleted file mode 100644 index 794645d122..0000000000 --- a/data/corefork.telegram.org/constructor/inputMessagesFilterRoundVoice.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterRoundVoice - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterRoundVoice

- -

Return only round videos and voice notes

-

- -
-
inputMessagesFilterRoundVoice#7a7c17a4 = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterUrl.html b/data/corefork.telegram.org/constructor/inputMessagesFilterUrl.html deleted file mode 100644 index b04d1288e3..0000000000 --- a/data/corefork.telegram.org/constructor/inputMessagesFilterUrl.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterUrl - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterUrl

- -

Return only messages containing URLs

-

- -
-
inputMessagesFilterUrl#7ef0dd87 = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterVideo.html b/data/corefork.telegram.org/constructor/inputMessagesFilterVideo.html deleted file mode 100644 index d944d2d9ce..0000000000 --- a/data/corefork.telegram.org/constructor/inputMessagesFilterVideo.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterVideo - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterVideo

- -

Filter for messages containing videos.

-

- -
-
inputMessagesFilterVideo#9fc00e65 = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputMessagesFilterVoice.html b/data/corefork.telegram.org/constructor/inputMessagesFilterVoice.html deleted file mode 100644 index 0422aac5ee..0000000000 --- a/data/corefork.telegram.org/constructor/inputMessagesFilterVoice.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputMessagesFilterVoice - - - - - - - - - - - - - -
- -
-
-
- -

inputMessagesFilterVoice

- -

Return only messages containing voice notes

-

- -
-
inputMessagesFilterVoice#50f5c392 = MessagesFilter;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessagesFilter

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputNotifyBroadcasts.html b/data/corefork.telegram.org/constructor/inputNotifyBroadcasts.html deleted file mode 100644 index a5f8770927..0000000000 --- a/data/corefork.telegram.org/constructor/inputNotifyBroadcasts.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - inputNotifyBroadcasts - - - - - - - - - - - - - -
- -
-
-
- -

inputNotifyBroadcasts

- -

All channels

-

- -
-
inputNotifyBroadcasts#b1db7c7e = InputNotifyPeer;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputNotifyPeer

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputNotifyChats.html b/data/corefork.telegram.org/constructor/inputNotifyChats.html deleted file mode 100644 index e7c11ab713..0000000000 --- a/data/corefork.telegram.org/constructor/inputNotifyChats.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputNotifyChats - - - - - - - - - - - - - -
- -
-
-
- -

inputNotifyChats

- -

Notifications generated by all groups.

-

- -
-
inputNotifyChats#4a95e84e = InputNotifyPeer;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputNotifyPeer

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputNotifyPeer.html b/data/corefork.telegram.org/constructor/inputNotifyPeer.html deleted file mode 100644 index 1f83010fe4..0000000000 --- a/data/corefork.telegram.org/constructor/inputNotifyPeer.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputNotifyPeer - - - - - - - - - - - - - -
- -
-
-
- -

inputNotifyPeer

- -

Notifications generated by a certain user or group.

-

- -
-
inputNotifyPeer#b8bc5b0c peer:InputPeer = InputNotifyPeer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerUser or group
-

Type

-

InputNotifyPeer

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputNotifyUsers.html b/data/corefork.telegram.org/constructor/inputNotifyUsers.html deleted file mode 100644 index 73c3c39e44..0000000000 --- a/data/corefork.telegram.org/constructor/inputNotifyUsers.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputNotifyUsers - - - - - - - - - - - - - -
- -
-
-
- -

inputNotifyUsers

- -

Notifications generated by all users.

-

- -
-
inputNotifyUsers#193b4417 = InputNotifyPeer;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputNotifyPeer

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPaymentCredentials.html b/data/corefork.telegram.org/constructor/inputPaymentCredentials.html deleted file mode 100644 index 13f88ad98d..0000000000 --- a/data/corefork.telegram.org/constructor/inputPaymentCredentials.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - inputPaymentCredentials - - - - - - - - - - - - - -
- -
-
-
- -

inputPaymentCredentials

- -

Payment credentials

-

- -
-
inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
saveflags.0?trueSave payment credential for future use
dataDataJSONPayment credentials
-

Type

-

InputPaymentCredentials

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPaymentCredentialsApplePay.html b/data/corefork.telegram.org/constructor/inputPaymentCredentialsApplePay.html deleted file mode 100644 index de3536bac0..0000000000 --- a/data/corefork.telegram.org/constructor/inputPaymentCredentialsApplePay.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputPaymentCredentialsApplePay - - - - - - - - - - - - - -
- -
-
-
- -

inputPaymentCredentialsApplePay

- -

Apple pay payment credentials

-

- -
-
inputPaymentCredentialsApplePay#aa1c39f payment_data:DataJSON = InputPaymentCredentials;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
payment_dataDataJSONPayment data
-

Type

-

InputPaymentCredentials

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPaymentCredentialsGooglePay.html b/data/corefork.telegram.org/constructor/inputPaymentCredentialsGooglePay.html deleted file mode 100644 index a405e02a13..0000000000 --- a/data/corefork.telegram.org/constructor/inputPaymentCredentialsGooglePay.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputPaymentCredentialsGooglePay - - - - - - - - - - - - - -
- -
-
-
- -

inputPaymentCredentialsGooglePay

- -

Google Pay payment credentials

-

- -
-
inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
payment_tokenDataJSONPayment token
-

Type

-

InputPaymentCredentials

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPaymentCredentialsSaved.html b/data/corefork.telegram.org/constructor/inputPaymentCredentialsSaved.html deleted file mode 100644 index 29c658c1fa..0000000000 --- a/data/corefork.telegram.org/constructor/inputPaymentCredentialsSaved.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputPaymentCredentialsSaved - - - - - - - - - - - - - -
- -
-
-
- -

inputPaymentCredentialsSaved

- -

Saved payment credentials

-

- -
-
inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idstringCredential ID
tmp_passwordbytesTemporary password
-

Type

-

InputPaymentCredentials

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPeerChannel.html b/data/corefork.telegram.org/constructor/inputPeerChannel.html deleted file mode 100644 index 8a3fb52e57..0000000000 --- a/data/corefork.telegram.org/constructor/inputPeerChannel.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputPeerChannel - - - - - - - - - - - - - -
- -
-
-
- -

inputPeerChannel

- -

Defines a channel for further interaction.

-

- -
-
inputPeerChannel#27bcbbfc channel_id:long access_hash:long = InputPeer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idlongChannel identifier
access_hashlongaccess_hash value from the channel constructor
-

Type

-

InputPeer

-

Related pages

-

channel

-

Channel/supergroup info

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPeerChannelFromMessage.html b/data/corefork.telegram.org/constructor/inputPeerChannelFromMessage.html deleted file mode 100644 index 9eba91f8fe..0000000000 --- a/data/corefork.telegram.org/constructor/inputPeerChannelFromMessage.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - inputPeerChannelFromMessage - - - - - - - - - - - - - -
- -
-
-
- -

inputPeerChannelFromMessage

- -

Defines a min channel that was seen in a certain message of a certain chat.

-

- -
-
inputPeerChannelFromMessage#bd2a0840 peer:InputPeer msg_id:int channel_id:long = InputPeer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat where the channel's message was seen
msg_idintThe message ID
channel_idlongThe identifier of the channel that was seen
-

Type

-

InputPeer

-

Related pages

-

Min constructors

-

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPeerChat.html b/data/corefork.telegram.org/constructor/inputPeerChat.html deleted file mode 100644 index 10f8531507..0000000000 --- a/data/corefork.telegram.org/constructor/inputPeerChat.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputPeerChat - - - - - - - - - - - - - -
- -
-
-
- -

inputPeerChat

- -

Defines a chat for further interaction.

-

- -
-
inputPeerChat#35a95cb9 chat_id:long = InputPeer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongChat idientifier
-

Type

-

InputPeer

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPeerNotifySettings.html b/data/corefork.telegram.org/constructor/inputPeerNotifySettings.html deleted file mode 100644 index 6edc1051ca..0000000000 --- a/data/corefork.telegram.org/constructor/inputPeerNotifySettings.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - inputPeerNotifySettings - - - - - - - - - - - - - -
- -
-
-
- -

inputPeerNotifySettings

- -

Notification settings.

-

- -
-
inputPeerNotifySettings#9c3d198e flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = InputPeerNotifySettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
show_previewsflags.0?BoolIf the text of the message shall be displayed in notification
silentflags.1?BoolPeer was muted?
mute_untilflags.2?intDate until which all notifications shall be switched off
soundflags.3?stringName of an audio file for notification
-

Type

-

InputPeerNotifySettings

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPeerPhotoFileLocation.html b/data/corefork.telegram.org/constructor/inputPeerPhotoFileLocation.html deleted file mode 100644 index 84c94acc52..0000000000 --- a/data/corefork.telegram.org/constructor/inputPeerPhotoFileLocation.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputPeerPhotoFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputPeerPhotoFileLocation

- -

Location of profile photo of channel/group/supergroup/user

-

- -
-
inputPeerPhotoFileLocation#37257e99 flags:# big:flags.0?true peer:InputPeer photo_id:long = InputFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
bigflags.0?trueWhether to download the high-quality version of the picture
peerInputPeerThe peer whose profile picture should be downloaded
photo_idlongPhoto ID
-

Type

-

InputFileLocation

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPeerSelf.html b/data/corefork.telegram.org/constructor/inputPeerSelf.html deleted file mode 100644 index 415b6c27fc..0000000000 --- a/data/corefork.telegram.org/constructor/inputPeerSelf.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPeerSelf - - - - - - - - - - - - - -
- -
-
-
- -

inputPeerSelf

- -

Defines the current user.

-

- -
-
inputPeerSelf#7da07ec9 = InputPeer;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPeer

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPeerUser.html b/data/corefork.telegram.org/constructor/inputPeerUser.html deleted file mode 100644 index 9cb02e4c7e..0000000000 --- a/data/corefork.telegram.org/constructor/inputPeerUser.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputPeerUser - - - - - - - - - - - - - -
- -
-
-
- -

inputPeerUser

- -

Defines a user for further interaction.

-

- -
-
inputPeerUser#dde8a54c user_id:long access_hash:long = InputPeer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser identifier
access_hashlongaccess_hash value from the user constructor
-

Type

-

InputPeer

-

Related pages

-

user

-

Indicates info about a certain user

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPeerUserFromMessage.html b/data/corefork.telegram.org/constructor/inputPeerUserFromMessage.html deleted file mode 100644 index cd52c2388b..0000000000 --- a/data/corefork.telegram.org/constructor/inputPeerUserFromMessage.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - inputPeerUserFromMessage - - - - - - - - - - - - - -
- -
-
-
- -

inputPeerUserFromMessage

- -

Defines a min user that was seen in a certain message of a certain chat.

-

- -
-
inputPeerUserFromMessage#a87b0a1c peer:InputPeer msg_id:int user_id:long = InputPeer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat where the user was seen
msg_idintThe message ID
user_idlongThe identifier of the user that was seen
-

Type

-

InputPeer

-

Related pages

-

Min constructors

-

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPhoneCall.html b/data/corefork.telegram.org/constructor/inputPhoneCall.html deleted file mode 100644 index 52b31957be..0000000000 --- a/data/corefork.telegram.org/constructor/inputPhoneCall.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputPhoneCall - - - - - - - - - - - - - -
- -
-
-
- -

inputPhoneCall

- -

Phone call

-

- -
-
inputPhoneCall#1e36fded id:long access_hash:long = InputPhoneCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongCall ID
access_hashlongAccess hash
-

Type

-

InputPhoneCall

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPhoneContact.html b/data/corefork.telegram.org/constructor/inputPhoneContact.html deleted file mode 100644 index 613f8b08eb..0000000000 --- a/data/corefork.telegram.org/constructor/inputPhoneContact.html +++ /dev/null @@ -1,166 +0,0 @@ - - - - - inputPhoneContact - - - - - - - - - - - - - -
- -
-
-
- -

inputPhoneContact

- -

Phone contact. The client_id is just an arbitrary contact ID: it should be set, for example, to an incremental number when using contacts.importContacts, in order to retry importing only the contacts that weren't imported successfully.

-

- -
-
inputPhoneContact#f392b7f4 client_id:long phone:string first_name:string last_name:string = InputContact;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
client_idlongUser identifier on the client
phonestringPhone number
first_namestringContact's first name
last_namestringContact's last name
-

Type

-

InputContact

-

Related pages

-

contacts.importContacts

-

Imports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.

-

Use contacts.addContact to add Telegram contacts without actually using their phone number.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPhoto.html b/data/corefork.telegram.org/constructor/inputPhoto.html deleted file mode 100644 index 5a480f1afb..0000000000 --- a/data/corefork.telegram.org/constructor/inputPhoto.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputPhoto - - - - - - - - - - - - - -
- -
-
-
- -

inputPhoto

- -

Defines a photo for further interaction.

-

- -
-
inputPhoto#3bb3b94a id:long access_hash:long file_reference:bytes = InputPhoto;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongPhoto identifier
access_hashlongaccess_hash value from the photo constructor
file_referencebytesFile reference
-

Type

-

InputPhoto

-

Related pages

-

photo

-

Photo

-

File references

-

How to handle file references.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPhotoEmpty.html b/data/corefork.telegram.org/constructor/inputPhotoEmpty.html deleted file mode 100644 index 4a91cf3c0b..0000000000 --- a/data/corefork.telegram.org/constructor/inputPhotoEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPhotoEmpty - - - - - - - - - - - - - -
- -
-
-
- -

inputPhotoEmpty

- -

Empty constructor.

-

- -
-
inputPhotoEmpty#1cd7bf0d = InputPhoto;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPhoto

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPhotoFileLocation.html b/data/corefork.telegram.org/constructor/inputPhotoFileLocation.html deleted file mode 100644 index 65d40b144d..0000000000 --- a/data/corefork.telegram.org/constructor/inputPhotoFileLocation.html +++ /dev/null @@ -1,171 +0,0 @@ - - - - - inputPhotoFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputPhotoFileLocation

- -

Use this object to download a photo with upload.getFile method

-

- -
-
inputPhotoFileLocation#40181ffe id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongPhoto ID, obtained from the photo object
access_hashlongPhoto's access hash, obtained from the photo object
file_referencebytesFile reference
thumb_sizestringThe PhotoSize to download: must be set to the type field of the desired PhotoSize object of the photo
-

Type

-

InputFileLocation

-

Related pages

-

photo

-

Photo

-

File references

-

How to handle file references.

-

PhotoSize

-

Location of a certain size of a picture

-

upload.getFile

-

Returns content of a whole file or its part.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPrivacyKeyAddedByPhone.html b/data/corefork.telegram.org/constructor/inputPrivacyKeyAddedByPhone.html deleted file mode 100644 index 70ea4bbca8..0000000000 --- a/data/corefork.telegram.org/constructor/inputPrivacyKeyAddedByPhone.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyAddedByPhone - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyKeyAddedByPhone

- -

Whether people can add you to their contact list by your phone number

-

- -
-
inputPrivacyKeyAddedByPhone#d1219bdd = InputPrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPrivacyKeyChatInvite.html b/data/corefork.telegram.org/constructor/inputPrivacyKeyChatInvite.html deleted file mode 100644 index 0e985a5633..0000000000 --- a/data/corefork.telegram.org/constructor/inputPrivacyKeyChatInvite.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyKeyChatInvite

- -

Whether the user can be invited to chats

-

- -
-
inputPrivacyKeyChatInvite#bdfb0426 = InputPrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPrivacyKeyForwards.html b/data/corefork.telegram.org/constructor/inputPrivacyKeyForwards.html deleted file mode 100644 index 9f3b752d18..0000000000 --- a/data/corefork.telegram.org/constructor/inputPrivacyKeyForwards.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyForwards - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyKeyForwards

- -

Whether messages forwarded from this user will be anonymous

-

- -
-
inputPrivacyKeyForwards#a4dd4c08 = InputPrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneCall.html b/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneCall.html deleted file mode 100644 index 9404441eb9..0000000000 --- a/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneCall.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyPhoneCall - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyKeyPhoneCall

- -

Whether the user will accept phone calls

-

- -
-
inputPrivacyKeyPhoneCall#fabadc5f = InputPrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneNumber.html b/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneNumber.html deleted file mode 100644 index 00388195d7..0000000000 --- a/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneNumber.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyPhoneNumber - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyKeyPhoneNumber

- -

Whether people will be able to see the user's phone number

-

- -
-
inputPrivacyKeyPhoneNumber#352dafa = InputPrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneP2P.html b/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneP2P.html deleted file mode 100644 index 409f271092..0000000000 --- a/data/corefork.telegram.org/constructor/inputPrivacyKeyPhoneP2P.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyPhoneP2P - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyKeyPhoneP2P

- -

Whether the user allows P2P communication during VoIP calls

-

- -
-
inputPrivacyKeyPhoneP2P#db9e70d2 = InputPrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPrivacyKeyProfilePhoto.html b/data/corefork.telegram.org/constructor/inputPrivacyKeyProfilePhoto.html deleted file mode 100644 index 311029f190..0000000000 --- a/data/corefork.telegram.org/constructor/inputPrivacyKeyProfilePhoto.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyKeyProfilePhoto - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyKeyProfilePhoto

- -

Whether people will be able to see the user's profile picture

-

- -
-
inputPrivacyKeyProfilePhoto#5719bacc = InputPrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPrivacyValueAllowChatParticipants.html b/data/corefork.telegram.org/constructor/inputPrivacyValueAllowChatParticipants.html deleted file mode 100644 index 1a5c21e0af..0000000000 --- a/data/corefork.telegram.org/constructor/inputPrivacyValueAllowChatParticipants.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputPrivacyValueAllowChatParticipants - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyValueAllowChatParticipants

- -

Allow only participants of certain chats

-

- -
-
inputPrivacyValueAllowChatParticipants#840649cf chats:Vector<long> = InputPrivacyRule;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chatsVector<long>Allowed chat IDs
-

Type

-

InputPrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPrivacyValueAllowContacts.html b/data/corefork.telegram.org/constructor/inputPrivacyValueAllowContacts.html deleted file mode 100644 index b632a48fff..0000000000 --- a/data/corefork.telegram.org/constructor/inputPrivacyValueAllowContacts.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyValueAllowContacts - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyValueAllowContacts

- -

Allow only contacts

-

- -
-
inputPrivacyValueAllowContacts#d09e07b = InputPrivacyRule;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPrivacyValueAllowUsers.html b/data/corefork.telegram.org/constructor/inputPrivacyValueAllowUsers.html deleted file mode 100644 index 0d082ca8f2..0000000000 --- a/data/corefork.telegram.org/constructor/inputPrivacyValueAllowUsers.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputPrivacyValueAllowUsers - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyValueAllowUsers

- -

Allow only certain users

-

- -
-
inputPrivacyValueAllowUsers#131cc67f users:Vector<InputUser> = InputPrivacyRule;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
usersVector<InputUser>Allowed users
-

Type

-

InputPrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPrivacyValueDisallowAll.html b/data/corefork.telegram.org/constructor/inputPrivacyValueDisallowAll.html deleted file mode 100644 index 75eecb889b..0000000000 --- a/data/corefork.telegram.org/constructor/inputPrivacyValueDisallowAll.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputPrivacyValueDisallowAll - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyValueDisallowAll

- -

Disallow all

-

- -
-
inputPrivacyValueDisallowAll#d66b66c9 = InputPrivacyRule;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputPrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPrivacyValueDisallowChatParticipants.html b/data/corefork.telegram.org/constructor/inputPrivacyValueDisallowChatParticipants.html deleted file mode 100644 index 443a79fd4b..0000000000 --- a/data/corefork.telegram.org/constructor/inputPrivacyValueDisallowChatParticipants.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputPrivacyValueDisallowChatParticipants - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyValueDisallowChatParticipants

- -

Disallow only participants of certain chats

-

- -
-
inputPrivacyValueDisallowChatParticipants#e94f0f86 chats:Vector<long> = InputPrivacyRule;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chatsVector<long>Disallowed chat IDs
-

Type

-

InputPrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputPrivacyValueDisallowUsers.html b/data/corefork.telegram.org/constructor/inputPrivacyValueDisallowUsers.html deleted file mode 100644 index 9438f2f5a0..0000000000 --- a/data/corefork.telegram.org/constructor/inputPrivacyValueDisallowUsers.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputPrivacyValueDisallowUsers - - - - - - - - - - - - - -
- -
-
-
- -

inputPrivacyValueDisallowUsers

- -

Disallow only certain users

-

- -
-
inputPrivacyValueDisallowUsers#90110467 users:Vector<InputUser> = InputPrivacyRule;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
usersVector<InputUser>Users to disallow
-

Type

-

InputPrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputReportReasonChildAbuse.html b/data/corefork.telegram.org/constructor/inputReportReasonChildAbuse.html deleted file mode 100644 index b126b58db1..0000000000 --- a/data/corefork.telegram.org/constructor/inputReportReasonChildAbuse.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputReportReasonChildAbuse - - - - - - - - - - - - - -
- -
-
-
- -

inputReportReasonChildAbuse

- -

Report for child abuse

-

- -
-
inputReportReasonChildAbuse#adf44ee3 = ReportReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ReportReason

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputReportReasonCopyright.html b/data/corefork.telegram.org/constructor/inputReportReasonCopyright.html deleted file mode 100644 index c20e0561a8..0000000000 --- a/data/corefork.telegram.org/constructor/inputReportReasonCopyright.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputReportReasonCopyright - - - - - - - - - - - - - -
- -
-
-
- -

inputReportReasonCopyright

- -

Report for copyrighted content

-

- -
-
inputReportReasonCopyright#9b89f93a = ReportReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ReportReason

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputReportReasonFake.html b/data/corefork.telegram.org/constructor/inputReportReasonFake.html deleted file mode 100644 index f7e03e9a66..0000000000 --- a/data/corefork.telegram.org/constructor/inputReportReasonFake.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputReportReasonFake - - - - - - - - - - - - - -
- -
-
-
- -

inputReportReasonFake

- -

Report for impersonation

-

- -
-
inputReportReasonFake#f5ddd6e7 = ReportReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ReportReason

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputReportReasonGeoIrrelevant.html b/data/corefork.telegram.org/constructor/inputReportReasonGeoIrrelevant.html deleted file mode 100644 index f5af496bd7..0000000000 --- a/data/corefork.telegram.org/constructor/inputReportReasonGeoIrrelevant.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputReportReasonGeoIrrelevant - - - - - - - - - - - - - -
- -
-
-
- -

inputReportReasonGeoIrrelevant

- -

Report an irrelevant geogroup

-

- -
-
inputReportReasonGeoIrrelevant#dbd4feed = ReportReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ReportReason

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputReportReasonOther.html b/data/corefork.telegram.org/constructor/inputReportReasonOther.html deleted file mode 100644 index 01594f8960..0000000000 --- a/data/corefork.telegram.org/constructor/inputReportReasonOther.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputReportReasonOther - - - - - - - - - - - - - -
- -
-
-
- -

inputReportReasonOther

- -

Other

-

- -
-
inputReportReasonOther#c1e4a2b1 = ReportReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ReportReason

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputReportReasonPornography.html b/data/corefork.telegram.org/constructor/inputReportReasonPornography.html deleted file mode 100644 index 33335cbfc7..0000000000 --- a/data/corefork.telegram.org/constructor/inputReportReasonPornography.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputReportReasonPornography - - - - - - - - - - - - - -
- -
-
-
- -

inputReportReasonPornography

- -

Report for pornography

-

- -
-
inputReportReasonPornography#2e59d922 = ReportReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ReportReason

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputReportReasonSpam.html b/data/corefork.telegram.org/constructor/inputReportReasonSpam.html deleted file mode 100644 index 140262fd97..0000000000 --- a/data/corefork.telegram.org/constructor/inputReportReasonSpam.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputReportReasonSpam - - - - - - - - - - - - - -
- -
-
-
- -

inputReportReasonSpam

- -

Report for spam

-

- -
-
inputReportReasonSpam#58dbcab8 = ReportReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ReportReason

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputReportReasonViolence.html b/data/corefork.telegram.org/constructor/inputReportReasonViolence.html deleted file mode 100644 index e62ed115bd..0000000000 --- a/data/corefork.telegram.org/constructor/inputReportReasonViolence.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputReportReasonViolence - - - - - - - - - - - - - -
- -
-
-
- -

inputReportReasonViolence

- -

Report for violence

-

- -
-
inputReportReasonViolence#1e22c78d = ReportReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

ReportReason

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputSecureFile.html b/data/corefork.telegram.org/constructor/inputSecureFile.html deleted file mode 100644 index a38b4ba663..0000000000 --- a/data/corefork.telegram.org/constructor/inputSecureFile.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputSecureFile - - - - - - - - - - - - - -
- -
-
-
- -

inputSecureFile

- -

Preuploaded passport file, for more info see the passport docs »

-

- -
-
inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongSecure file ID
access_hashlongSecure file access hash
-

Type

-

InputSecureFile

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputSecureFileLocation.html b/data/corefork.telegram.org/constructor/inputSecureFileLocation.html deleted file mode 100644 index a5ecfa55dd..0000000000 --- a/data/corefork.telegram.org/constructor/inputSecureFileLocation.html +++ /dev/null @@ -1,156 +0,0 @@ - - - - - inputSecureFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputSecureFileLocation

- -

Location of encrypted telegram passport file.

-

- -
-
inputSecureFileLocation#cbc7ee28 id:long access_hash:long = InputFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongFile ID, id parameter value from secureFile
access_hashlongChecksum, access_hash parameter value from secureFile
-

Type

-

InputFileLocation

-

Related pages

-

secureFile

-

Secure passport file, for more info see the passport docs »

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputSecureFileUploaded.html b/data/corefork.telegram.org/constructor/inputSecureFileUploaded.html deleted file mode 100644 index 4a826cc8f5..0000000000 --- a/data/corefork.telegram.org/constructor/inputSecureFileUploaded.html +++ /dev/null @@ -1,169 +0,0 @@ - - - - - inputSecureFileUploaded - - - - - - - - - - - - - -
- -
-
-
- -

inputSecureFileUploaded

- -

Uploaded secure file, for more info see the passport docs »

-

- -
-
inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongSecure file ID
partsintSecure file part count
md5_checksumstringMD5 hash of encrypted uploaded file, to be checked server-side
file_hashbytesFile hash
secretbytesSecret
-

Type

-

InputSecureFile

-

Related pages

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputSecureValue.html b/data/corefork.telegram.org/constructor/inputSecureValue.html deleted file mode 100644 index a832a2041d..0000000000 --- a/data/corefork.telegram.org/constructor/inputSecureValue.html +++ /dev/null @@ -1,190 +0,0 @@ - - - - - inputSecureValue - - - - - - - - - - - - - -
- -
-
-
- -

inputSecureValue

- -

Secure value, for more info see the passport docs »

-

- -
-
inputSecureValue#db21d0a7 flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?InputSecureFile reverse_side:flags.2?InputSecureFile selfie:flags.3?InputSecureFile translation:flags.6?Vector<InputSecureFile> files:flags.4?Vector<InputSecureFile> plain_data:flags.5?SecurePlainData = InputSecureValue;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
typeSecureValueTypeSecure passport value type
dataflags.0?SecureDataEncrypted Telegram Passport element data
front_sideflags.1?InputSecureFileEncrypted passport file with the front side of the document
reverse_sideflags.2?InputSecureFileEncrypted passport file with the reverse side of the document
selfieflags.3?InputSecureFileEncrypted passport file with a selfie of the user holding the document
translationflags.6?Vector<InputSecureFile>Array of encrypted passport files with translated versions of the provided documents
filesflags.4?Vector<InputSecureFile>Array of encrypted passport files with photos the of the documents
plain_dataflags.5?SecurePlainDataPlaintext verified passport data
-

Type

-

InputSecureValue

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputSingleMedia.html b/data/corefork.telegram.org/constructor/inputSingleMedia.html deleted file mode 100644 index 7bf34b9665..0000000000 --- a/data/corefork.telegram.org/constructor/inputSingleMedia.html +++ /dev/null @@ -1,174 +0,0 @@ - - - - - inputSingleMedia - - - - - - - - - - - - - -
- -
-
-
- -

inputSingleMedia

- -

A single media in an album or grouped media sent with messages.sendMultiMedia.

-

- -
-
inputSingleMedia#1cc6e91f flags:# media:InputMedia random_id:long message:string entities:flags.0?Vector<MessageEntity> = InputSingleMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
mediaInputMediaThe media
random_idlongUnique client media ID required to prevent message resending
messagestringA caption for the media
entitiesflags.0?Vector<MessageEntity>Message entities for styled text
-

Type

-

InputSingleMedia

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

-

messages.sendMultiMedia

-

Send an album or grouped media

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputStickerSetAnimatedEmoji.html b/data/corefork.telegram.org/constructor/inputStickerSetAnimatedEmoji.html deleted file mode 100644 index b76583615d..0000000000 --- a/data/corefork.telegram.org/constructor/inputStickerSetAnimatedEmoji.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputStickerSetAnimatedEmoji - - - - - - - - - - - - - -
- -
-
-
- -

inputStickerSetAnimatedEmoji

- -

Animated emojis stickerset

-

- -
-
inputStickerSetAnimatedEmoji#28703c8 = InputStickerSet;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputStickerSet

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputStickerSetAnimatedEmojiAnimations.html b/data/corefork.telegram.org/constructor/inputStickerSetAnimatedEmojiAnimations.html deleted file mode 100644 index 753c4001d4..0000000000 --- a/data/corefork.telegram.org/constructor/inputStickerSetAnimatedEmojiAnimations.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputStickerSetAnimatedEmojiAnimations - - - - - - - - - - - - - -
- -
-
-
- -

inputStickerSetAnimatedEmojiAnimations

- -

Animated emoji reaction stickerset (contains animations to play when a user clicks on a given animated emoji)

-

- -
-
inputStickerSetAnimatedEmojiAnimations#cde3739 = InputStickerSet;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputStickerSet

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputStickerSetDice.html b/data/corefork.telegram.org/constructor/inputStickerSetDice.html deleted file mode 100644 index fe2c781bc2..0000000000 --- a/data/corefork.telegram.org/constructor/inputStickerSetDice.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - inputStickerSetDice - - - - - - - - - - - - - -
- -
-
-
- -

inputStickerSetDice

- -

Used for fetching animated dice stickers

-

- -
-
inputStickerSetDice#e67f520e emoticon:string = InputStickerSet;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
emoticonstringThe emoji, for now 🏀, 🎲 and 🎯 are supported
-

Type

-

InputStickerSet

-

Related pages

-

Dice

-

Telegram supports sending animated dice emojis.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputStickerSetEmpty.html b/data/corefork.telegram.org/constructor/inputStickerSetEmpty.html deleted file mode 100644 index 82d1dd0ecc..0000000000 --- a/data/corefork.telegram.org/constructor/inputStickerSetEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputStickerSetEmpty - - - - - - - - - - - - - -
- -
-
-
- -

inputStickerSetEmpty

- -

Empty constructor

-

- -
-
inputStickerSetEmpty#ffb62b95 = InputStickerSet;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputStickerSet

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputStickerSetID.html b/data/corefork.telegram.org/constructor/inputStickerSetID.html deleted file mode 100644 index 37fb99132e..0000000000 --- a/data/corefork.telegram.org/constructor/inputStickerSetID.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputStickerSetID - - - - - - - - - - - - - -
- -
-
-
- -

inputStickerSetID

- -

Stickerset by ID

-

- -
-
inputStickerSetID#9de7a269 id:long access_hash:long = InputStickerSet;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongID
access_hashlongAccess hash
-

Type

-

InputStickerSet

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputStickerSetItem.html b/data/corefork.telegram.org/constructor/inputStickerSetItem.html deleted file mode 100644 index d4e4336fd3..0000000000 --- a/data/corefork.telegram.org/constructor/inputStickerSetItem.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - inputStickerSetItem - - - - - - - - - - - - - -
- -
-
-
- -

inputStickerSetItem

- -

Sticker in a stickerset

-

- -
-
inputStickerSetItem#ffa0a496 flags:# document:InputDocument emoji:string mask_coords:flags.0?MaskCoords = InputStickerSetItem;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
documentInputDocumentThe sticker
emojistringAssociated emoji
mask_coordsflags.0?MaskCoordsCoordinates for mask sticker
-

Type

-

InputStickerSetItem

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputStickerSetShortName.html b/data/corefork.telegram.org/constructor/inputStickerSetShortName.html deleted file mode 100644 index 540847fb14..0000000000 --- a/data/corefork.telegram.org/constructor/inputStickerSetShortName.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputStickerSetShortName - - - - - - - - - - - - - -
- -
-
-
- -

inputStickerSetShortName

- -

Stickerset by short name, from tg://addstickers?set=short_name

-

- -
-
inputStickerSetShortName#861cc8a0 short_name:string = InputStickerSet;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
short_namestringFrom tg://addstickers?set=short_name
-

Type

-

InputStickerSet

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputStickeredMediaDocument.html b/data/corefork.telegram.org/constructor/inputStickeredMediaDocument.html deleted file mode 100644 index 1b5d5702de..0000000000 --- a/data/corefork.telegram.org/constructor/inputStickeredMediaDocument.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputStickeredMediaDocument - - - - - - - - - - - - - -
- -
-
-
- -

inputStickeredMediaDocument

- -

A document with stickers attached

-

- -
-
inputStickeredMediaDocument#438865b id:InputDocument = InputStickeredMedia;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idInputDocumentThe document
-

Type

-

InputStickeredMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputStickeredMediaPhoto.html b/data/corefork.telegram.org/constructor/inputStickeredMediaPhoto.html deleted file mode 100644 index e8617172b0..0000000000 --- a/data/corefork.telegram.org/constructor/inputStickeredMediaPhoto.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputStickeredMediaPhoto - - - - - - - - - - - - - -
- -
-
-
- -

inputStickeredMediaPhoto

- -

A photo with stickers attached

-

- -
-
inputStickeredMediaPhoto#4a992157 id:InputPhoto = InputStickeredMedia;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idInputPhotoThe photo
-

Type

-

InputStickeredMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputTakeoutFileLocation.html b/data/corefork.telegram.org/constructor/inputTakeoutFileLocation.html deleted file mode 100644 index f38e149159..0000000000 --- a/data/corefork.telegram.org/constructor/inputTakeoutFileLocation.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputTakeoutFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputTakeoutFileLocation

- -

Empty constructor for takeout

-

- -
-
inputTakeoutFileLocation#29be5899 = InputFileLocation;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputFileLocation

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputTheme.html b/data/corefork.telegram.org/constructor/inputTheme.html deleted file mode 100644 index d97903df3b..0000000000 --- a/data/corefork.telegram.org/constructor/inputTheme.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputTheme - - - - - - - - - - - - - -
- -
-
-
- -

inputTheme

- -

Theme

-

- -
-
inputTheme#3c5693e9 id:long access_hash:long = InputTheme;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongID
access_hashlongAccess hash
-

Type

-

InputTheme

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputThemeSettings.html b/data/corefork.telegram.org/constructor/inputThemeSettings.html deleted file mode 100644 index cd22e8dc95..0000000000 --- a/data/corefork.telegram.org/constructor/inputThemeSettings.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - inputThemeSettings - - - - - - - - - - - - - -
- -
-
-
- -

inputThemeSettings

- -

Theme settings

-

- -
-
inputThemeSettings#8fde504f flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int outbox_accent_color:flags.3?int message_colors:flags.0?Vector<int> wallpaper:flags.1?InputWallPaper wallpaper_settings:flags.1?WallPaperSettings = InputThemeSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
message_colors_animatedflags.2?trueIf set, the freeform gradient fill needs to be animated on every sent message
base_themeBaseThemeDefault theme on which this theme is based
accent_colorintAccent color, ARGB format
outbox_accent_colorflags.3?intAccent color of outgoing messages in ARGB format
message_colorsflags.0?Vector<int>The fill to be used as a background for outgoing messages, in RGB24 format.
If just one or two equal colors are provided, describes a solid fill of a background.
If two different colors are provided, describes the top and bottom colors of a 0-degree gradient.
If three or four colors are provided, describes a freeform gradient fill of a background.
wallpaperflags.1?InputWallPaperWallpaper
wallpaper_settingsflags.1?WallPaperSettingsWallpaper settings
-

Type

-

InputThemeSettings

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputThemeSlug.html b/data/corefork.telegram.org/constructor/inputThemeSlug.html deleted file mode 100644 index 9b84dbdd37..0000000000 --- a/data/corefork.telegram.org/constructor/inputThemeSlug.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputThemeSlug - - - - - - - - - - - - - -
- -
-
-
- -

inputThemeSlug

- -

Theme by theme ID

-

- -
-
inputThemeSlug#f5890df1 slug:string = InputTheme;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
slugstringUnique theme ID
-

Type

-

InputTheme

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputUser.html b/data/corefork.telegram.org/constructor/inputUser.html deleted file mode 100644 index 52a3e6c9ba..0000000000 --- a/data/corefork.telegram.org/constructor/inputUser.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - inputUser - - - - - - - - - - - - - -
- -
-
-
- -

inputUser

- -

Defines a user for further interaction.

-

- -
-
inputUser#f21158c6 user_id:long access_hash:long = InputUser;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser identifier
access_hashlongaccess_hash value from the user constructor
-

Type

-

InputUser

-

Related pages

-

user

-

Indicates info about a certain user

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputUserEmpty.html b/data/corefork.telegram.org/constructor/inputUserEmpty.html deleted file mode 100644 index 5bd866e5b4..0000000000 --- a/data/corefork.telegram.org/constructor/inputUserEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputUserEmpty - - - - - - - - - - - - - -
- -
-
-
- -

inputUserEmpty

- -

Empty constructor, does not define a user.

-

- -
-
inputUserEmpty#b98886cf = InputUser;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputUser

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputUserFromMessage.html b/data/corefork.telegram.org/constructor/inputUserFromMessage.html deleted file mode 100644 index 28882e2c34..0000000000 --- a/data/corefork.telegram.org/constructor/inputUserFromMessage.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - inputUserFromMessage - - - - - - - - - - - - - -
- -
-
-
- -

inputUserFromMessage

- -

Defines a min user that was seen in a certain message of a certain chat.

-

- -
-
inputUserFromMessage#1da448e2 peer:InputPeer msg_id:int user_id:long = InputUser;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat where the user was seen
msg_idintThe message ID
user_idlongThe identifier of the user that was seen
-

Type

-

InputUser

-

Related pages

-

Min constructors

-

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputUserSelf.html b/data/corefork.telegram.org/constructor/inputUserSelf.html deleted file mode 100644 index 3721eaf005..0000000000 --- a/data/corefork.telegram.org/constructor/inputUserSelf.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - inputUserSelf - - - - - - - - - - - - - -
- -
-
-
- -

inputUserSelf

- -

Defines the current user.

-

- -
-
inputUserSelf#f7c1b13f = InputUser;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

InputUser

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputWallPaper.html b/data/corefork.telegram.org/constructor/inputWallPaper.html deleted file mode 100644 index b5c11735fc..0000000000 --- a/data/corefork.telegram.org/constructor/inputWallPaper.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputWallPaper - - - - - - - - - - - - - -
- -
-
-
- -

inputWallPaper

- -

Wallpaper

-

- -
-
inputWallPaper#e630b979 id:long access_hash:long = InputWallPaper;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongWallpaper ID
access_hashlongAccess hash
-

Type

-

InputWallPaper

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputWallPaperNoFile.html b/data/corefork.telegram.org/constructor/inputWallPaperNoFile.html deleted file mode 100644 index 58f4506331..0000000000 --- a/data/corefork.telegram.org/constructor/inputWallPaperNoFile.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - inputWallPaperNoFile - - - - - - - - - - - - - -
- -
-
-
- -

inputWallPaperNoFile

- -

Wallpaper with no file access hash, used for example when deleting (unsave=true) wallpapers using account.saveWallPaper, specifying just the wallpaper ID.

-

- -
-
inputWallPaperNoFile#967a462e id:long = InputWallPaper;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idlongWallpaper ID
-

Type

-

InputWallPaper

-

Related pages

-

account.saveWallPaper

-

Install/uninstall wallpaper

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputWallPaperSlug.html b/data/corefork.telegram.org/constructor/inputWallPaperSlug.html deleted file mode 100644 index ae84e0781e..0000000000 --- a/data/corefork.telegram.org/constructor/inputWallPaperSlug.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - inputWallPaperSlug - - - - - - - - - - - - - -
- -
-
-
- -

inputWallPaperSlug

- -

Wallpaper by slug (a unique ID)

-

- -
-
inputWallPaperSlug#72091c80 slug:string = InputWallPaper;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
slugstringUnique wallpaper ID
-

Type

-

InputWallPaper

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputWebDocument.html b/data/corefork.telegram.org/constructor/inputWebDocument.html deleted file mode 100644 index 9f11dfe696..0000000000 --- a/data/corefork.telegram.org/constructor/inputWebDocument.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - inputWebDocument - - - - - - - - - - - - - -
- -
-
-
- -

inputWebDocument

- -

The document

-

- -
-
inputWebDocument#9bed434d url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = InputWebDocument;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringRemote document URL to be downloaded using the appropriate method
sizeintRemote file size
mime_typestringMime type
attributesVector<DocumentAttribute>Attributes for media types
-

Type

-

InputWebDocument

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputWebFileGeoPointLocation.html b/data/corefork.telegram.org/constructor/inputWebFileGeoPointLocation.html deleted file mode 100644 index 5c0b3c43d7..0000000000 --- a/data/corefork.telegram.org/constructor/inputWebFileGeoPointLocation.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - inputWebFileGeoPointLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputWebFileGeoPointLocation

- -

Geolocation

-

- -
-
inputWebFileGeoPointLocation#9f2221c9 geo_point:InputGeoPoint access_hash:long w:int h:int zoom:int scale:int = InputWebFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
geo_pointInputGeoPointGeolocation
access_hashlongAccess hash
wintMap width in pixels before applying scale; 16-1024
hintMap height in pixels before applying scale; 16-1024
zoomintMap zoom level; 13-20
scaleintMap scale; 1-3
-

Type

-

InputWebFileLocation

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/inputWebFileLocation.html b/data/corefork.telegram.org/constructor/inputWebFileLocation.html deleted file mode 100644 index 1f1004a1b0..0000000000 --- a/data/corefork.telegram.org/constructor/inputWebFileLocation.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - inputWebFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

inputWebFileLocation

- -

Location of a remote HTTP(s) file

-

- -
-
inputWebFileLocation#c239d686 url:string access_hash:long = InputWebFileLocation;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringHTTP URL of file
access_hashlongAccess hash
-

Type

-

InputWebFileLocation

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/invoice.html b/data/corefork.telegram.org/constructor/invoice.html deleted file mode 100644 index 6d281ac028..0000000000 --- a/data/corefork.telegram.org/constructor/invoice.html +++ /dev/null @@ -1,209 +0,0 @@ - - - - - invoice - - - - - - - - - - - - - -
- -
-
-
- -

invoice

- -

Invoice

-

- -
-
invoice#cd886e0 flags:# test:flags.0?true name_requested:flags.1?true phone_requested:flags.2?true email_requested:flags.3?true shipping_address_requested:flags.4?true flexible:flags.5?true phone_to_provider:flags.6?true email_to_provider:flags.7?true currency:string prices:Vector<LabeledPrice> max_tip_amount:flags.8?long suggested_tip_amounts:flags.8?Vector<long> = Invoice;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
testflags.0?trueTest invoice
name_requestedflags.1?trueSet this flag if you require the user's full name to complete the order
phone_requestedflags.2?trueSet this flag if you require the user's phone number to complete the order
email_requestedflags.3?trueSet this flag if you require the user's email address to complete the order
shipping_address_requestedflags.4?trueSet this flag if you require the user's shipping address to complete the order
flexibleflags.5?trueSet this flag if the final price depends on the shipping method
phone_to_providerflags.6?trueSet this flag if user's phone number should be sent to provider
email_to_providerflags.7?trueSet this flag if user's email address should be sent to provider
currencystringThree-letter ISO 4217 currency code
pricesVector<LabeledPrice>Price breakdown, a list of components (e.g. product price, tax, discount, delivery cost, delivery tax, bonus, etc.)
max_tip_amountflags.8?longThe maximum accepted amount for tips in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
suggested_tip_amountsflags.8?Vector<long>A vector of suggested amounts of tips in the smallest units of the currency (integer, not float/double). At most 4 suggested tip amounts can be specified. The suggested tip amounts must be positive, passed in a strictly increased order and must not exceed max_tip_amount.
-

Type

-

Invoice

-

Related pages

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/jsonArray.html b/data/corefork.telegram.org/constructor/jsonArray.html deleted file mode 100644 index 702dcb47c3..0000000000 --- a/data/corefork.telegram.org/constructor/jsonArray.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - jsonArray - - - - - - - - - - - - - -
- -
-
-
- -

jsonArray

- -

JSON array

-

- -
-
jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
valueVector<JSONValue>JSON values
-

Type

-

JSONValue

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/jsonBool.html b/data/corefork.telegram.org/constructor/jsonBool.html deleted file mode 100644 index 9983c0cf8c..0000000000 --- a/data/corefork.telegram.org/constructor/jsonBool.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - jsonBool - - - - - - - - - - - - - -
- -
-
-
- -

jsonBool

- -

JSON boolean value

-

- -
-
jsonBool#c7345e6a value:Bool = JSONValue;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
valueBoolValue
-

Type

-

JSONValue

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/jsonNull.html b/data/corefork.telegram.org/constructor/jsonNull.html deleted file mode 100644 index a8821a8d0a..0000000000 --- a/data/corefork.telegram.org/constructor/jsonNull.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - jsonNull - - - - - - - - - - - - - -
- -
-
-
- -

jsonNull

- -

null JSON value

-

- -
-
jsonNull#3f6d7b68 = JSONValue;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

JSONValue

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/jsonNumber.html b/data/corefork.telegram.org/constructor/jsonNumber.html deleted file mode 100644 index 7e1fe480e7..0000000000 --- a/data/corefork.telegram.org/constructor/jsonNumber.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - jsonNumber - - - - - - - - - - - - - -
- -
-
-
- -

jsonNumber

- -

JSON numeric value

-

- -
-
jsonNumber#2be0dfa4 value:double = JSONValue;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
valuedoubleValue
-

Type

-

JSONValue

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/jsonObject.html b/data/corefork.telegram.org/constructor/jsonObject.html deleted file mode 100644 index 25f7ad3b9c..0000000000 --- a/data/corefork.telegram.org/constructor/jsonObject.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - jsonObject - - - - - - - - - - - - - -
- -
-
-
- -

jsonObject

- -

JSON object value

-

- -
-
jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
valueVector<JSONObjectValue>Values
-

Type

-

JSONValue

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/jsonObjectValue.html b/data/corefork.telegram.org/constructor/jsonObjectValue.html deleted file mode 100644 index e62ffbd968..0000000000 --- a/data/corefork.telegram.org/constructor/jsonObjectValue.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - jsonObjectValue - - - - - - - - - - - - - -
- -
-
-
- -

jsonObjectValue

- -

JSON key: value pair

-

- -
-
jsonObjectValue#c0de1bd9 key:string value:JSONValue = JSONObjectValue;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
keystringKey
valueJSONValueValue
-

Type

-

JSONObjectValue

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/jsonString.html b/data/corefork.telegram.org/constructor/jsonString.html deleted file mode 100644 index 681a9efc1b..0000000000 --- a/data/corefork.telegram.org/constructor/jsonString.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - jsonString - - - - - - - - - - - - - -
- -
-
-
- -

jsonString

- -

JSON string

-

- -
-
jsonString#b71e767a value:string = JSONValue;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
valuestringValue
-

Type

-

JSONValue

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/keyboardButton.html b/data/corefork.telegram.org/constructor/keyboardButton.html deleted file mode 100644 index e1742a0a4b..0000000000 --- a/data/corefork.telegram.org/constructor/keyboardButton.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - keyboardButton - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButton

- -

Bot keyboard button

-

- -
-
keyboardButton#a2fa4880 text:string = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textstringButton text
-

Type

-

KeyboardButton

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/keyboardButtonBuy.html b/data/corefork.telegram.org/constructor/keyboardButtonBuy.html deleted file mode 100644 index 8a1a66c14c..0000000000 --- a/data/corefork.telegram.org/constructor/keyboardButtonBuy.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - keyboardButtonBuy - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonBuy

- -

Button to buy a product

-

- -
-
keyboardButtonBuy#afd93fbb text:string = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textstringButton text
-

Type

-

KeyboardButton

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/keyboardButtonCallback.html b/data/corefork.telegram.org/constructor/keyboardButtonCallback.html deleted file mode 100644 index 74f6e5662e..0000000000 --- a/data/corefork.telegram.org/constructor/keyboardButtonCallback.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - keyboardButtonCallback - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonCallback

- -

Callback button

-

- -
-
keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
requires_passwordflags.0?trueWhether the user should verify his identity by entering his 2FA SRP parameters to the messages.getBotCallbackAnswer method. NOTE: telegram and the bot WILL NOT have access to the plaintext password, thanks to SRP. This button is mainly used by the official @botfather bot, for verifying the user's identity before transferring ownership of a bot to another user.
textstringButton text
databytesCallback data
-

Type

-

KeyboardButton

-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

-

messages.getBotCallbackAnswer

-

Press an inline callback button and get a callback answer from the bot

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/keyboardButtonGame.html b/data/corefork.telegram.org/constructor/keyboardButtonGame.html deleted file mode 100644 index a4f4acda0f..0000000000 --- a/data/corefork.telegram.org/constructor/keyboardButtonGame.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - keyboardButtonGame - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonGame

- -

Button to start a game

-

- -
-
keyboardButtonGame#50f41ccf text:string = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textstringButton text
-

Type

-

KeyboardButton

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/keyboardButtonRequestGeoLocation.html b/data/corefork.telegram.org/constructor/keyboardButtonRequestGeoLocation.html deleted file mode 100644 index 8edba698d1..0000000000 --- a/data/corefork.telegram.org/constructor/keyboardButtonRequestGeoLocation.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - keyboardButtonRequestGeoLocation - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonRequestGeoLocation

- -

Button to request a user's geolocation

-

- -
-
keyboardButtonRequestGeoLocation#fc796b3f text:string = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textstringButton text
-

Type

-

KeyboardButton

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/keyboardButtonRequestPhone.html b/data/corefork.telegram.org/constructor/keyboardButtonRequestPhone.html deleted file mode 100644 index f797aae1dd..0000000000 --- a/data/corefork.telegram.org/constructor/keyboardButtonRequestPhone.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - keyboardButtonRequestPhone - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonRequestPhone

- -

Button to request a user's phone number

-

- -
-
keyboardButtonRequestPhone#b16a6c29 text:string = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textstringButton text
-

Type

-

KeyboardButton

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/keyboardButtonRequestPoll.html b/data/corefork.telegram.org/constructor/keyboardButtonRequestPoll.html deleted file mode 100644 index 71ebc90ff9..0000000000 --- a/data/corefork.telegram.org/constructor/keyboardButtonRequestPoll.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - keyboardButtonRequestPoll - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonRequestPoll

- -

A button that allows the user to create and send a poll when pressed; available only in private

-

- -
-
keyboardButtonRequestPoll#bbc7515d flags:# quiz:flags.0?Bool text:string = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
quizflags.0?BoolIf set, only quiz polls can be sent
textstringButton text
-

Type

-

KeyboardButton

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/keyboardButtonRow.html b/data/corefork.telegram.org/constructor/keyboardButtonRow.html deleted file mode 100644 index fd97bf5fdc..0000000000 --- a/data/corefork.telegram.org/constructor/keyboardButtonRow.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - keyboardButtonRow - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonRow

- -

Inline keyboard row

-

- -
-
keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
buttonsVector<KeyboardButton>Bot or inline keyboard buttons
-

Type

-

KeyboardButtonRow

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/keyboardButtonSwitchInline.html b/data/corefork.telegram.org/constructor/keyboardButtonSwitchInline.html deleted file mode 100644 index d2b8b24171..0000000000 --- a/data/corefork.telegram.org/constructor/keyboardButtonSwitchInline.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - keyboardButtonSwitchInline - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonSwitchInline

- -

Button to force a user to switch to inline mode Pressing the button will prompt the user to select one of their chats, open that chat and insert the bot‘s username and the specified inline query in the input field.

-

- -
-
keyboardButtonSwitchInline#568a748 flags:# same_peer:flags.0?true text:string query:string = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
same_peerflags.0?trueIf set, pressing the button will insert the bot‘s username and the specified inline query in the current chat's input field.
textstringButton label
querystringThe inline query to use
-

Type

-

KeyboardButton

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/keyboardButtonUrl.html b/data/corefork.telegram.org/constructor/keyboardButtonUrl.html deleted file mode 100644 index e67747a45b..0000000000 --- a/data/corefork.telegram.org/constructor/keyboardButtonUrl.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - keyboardButtonUrl - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonUrl

- -

URL button

-

- -
-
keyboardButtonUrl#258aff05 text:string url:string = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textstringButton label
urlstringURL
-

Type

-

KeyboardButton

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/keyboardButtonUrlAuth.html b/data/corefork.telegram.org/constructor/keyboardButtonUrlAuth.html deleted file mode 100644 index 489f3ac924..0000000000 --- a/data/corefork.telegram.org/constructor/keyboardButtonUrlAuth.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - keyboardButtonUrlAuth - - - - - - - - - - - - - -
- -
-
-
- -

keyboardButtonUrlAuth

- -

Button to request a user to authorize via URL using Seamless Telegram Login. When the user clicks on such a button, messages.requestUrlAuth should be called, providing the button_id and the ID of the container message. The returned urlAuthResultRequest object will contain more details about the authorization request (request_write_access if the bot would like to send messages to the user along with the username of the bot which will be used for user authorization). Finally, the user can choose to call messages.acceptUrlAuth to get a urlAuthResultAccepted with the URL to open instead of the url of this constructor, or a urlAuthResultDefault, in which case the url of this constructor must be opened, instead. If the user refuses the authorization request but still wants to open the link, the url of this constructor must be used.

-

- -
-
keyboardButtonUrlAuth#10b78d29 flags:# text:string fwd_text:flags.0?string url:string button_id:int = KeyboardButton;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
textstringButton label
fwd_textflags.0?stringNew text of the button in forwarded messages.
urlstringAn HTTP URL to be opened with user authorization data added to the query string when the button is pressed. If the user refuses to provide authorization data, the original URL without information about the user will be opened. The data added is the same as described in Receiving authorization data.

NOTE: Services must always check the hash of the received data to verify the authentication and the integrity of the data as described in Checking authorization.
button_idintID of the button to pass to messages.requestUrlAuth
-

Type

-

KeyboardButton

-

Related pages

-

Telegram Login Widget

-

messages.requestUrlAuth

-

Get more info about a Seamless Telegram Login authorization request, for more info click here »

-

urlAuthResultRequest

-

Details about the authorization request, for more info click here »

-

messages.acceptUrlAuth

-

Use this to accept a Seamless Telegram Login authorization request, for more info click here »

-

urlAuthResultAccepted

-

Details about an accepted authorization request, for more info click here »

-

urlAuthResultDefault

-

Details about an accepted authorization request, for more info click here »

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/labeledPrice.html b/data/corefork.telegram.org/constructor/labeledPrice.html deleted file mode 100644 index 07ffaa7f98..0000000000 --- a/data/corefork.telegram.org/constructor/labeledPrice.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - labeledPrice - - - - - - - - - - - - - -
- -
-
-
- -

labeledPrice

- -

This object represents a portion of the price for goods or services.

-

- -
-
labeledPrice#cb296bf8 label:string amount:long = LabeledPrice;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
labelstringPortion label
amountlongPrice of the product in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
-

Type

-

LabeledPrice

-

Related pages

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/langPackDifference.html b/data/corefork.telegram.org/constructor/langPackDifference.html deleted file mode 100644 index c49ff851ab..0000000000 --- a/data/corefork.telegram.org/constructor/langPackDifference.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - langPackDifference - - - - - - - - - - - - - -
- -
-
-
- -

langPackDifference

- -

Changes to the app's localization pack

-

- -
-
langPackDifference#f385c1f6 lang_code:string from_version:int version:int strings:Vector<LangPackString> = LangPackDifference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
lang_codestringLanguage code
from_versionintPrevious version number
versionintNew version number
stringsVector<LangPackString>Localized strings
-

Type

-

LangPackDifference

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/langPackLanguage.html b/data/corefork.telegram.org/constructor/langPackLanguage.html deleted file mode 100644 index 4494b0d4a7..0000000000 --- a/data/corefork.telegram.org/constructor/langPackLanguage.html +++ /dev/null @@ -1,202 +0,0 @@ - - - - - langPackLanguage - - - - - - - - - - - - - -
- -
-
-
- -

langPackLanguage

- -

Identifies a localization pack

-

- -
-
langPackLanguage#eeca5ce3 flags:# official:flags.0?true rtl:flags.2?true beta:flags.3?true name:string native_name:string lang_code:string base_lang_code:flags.1?string plural_code:string strings_count:int translated_count:int translations_url:string = LangPackLanguage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
officialflags.0?trueWhether the language pack is official
rtlflags.2?trueIs this a localization pack for an RTL language
betaflags.3?trueIs this a beta localization pack?
namestringLanguage name
native_namestringLanguage name in the language itself
lang_codestringLanguage code (pack identifier)
base_lang_codeflags.1?stringIdentifier of a base language pack; may be empty. If a string is missed in the language pack, then it should be fetched from base language pack. Unsupported in custom language packs
plural_codestringA language code to be used to apply plural forms. See https://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html for more info
strings_countintTotal number of non-deleted strings from the language pack
translated_countintTotal number of translated strings from the language pack
translations_urlstringLink to language translation interface; empty for custom local language packs
-

Type

-

LangPackLanguage

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/langPackString.html b/data/corefork.telegram.org/constructor/langPackString.html deleted file mode 100644 index bb9565cd62..0000000000 --- a/data/corefork.telegram.org/constructor/langPackString.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - langPackString - - - - - - - - - - - - - -
- -
-
-
- -

langPackString

- -

Translated localization string

-

- -
-
langPackString#cad181f6 key:string value:string = LangPackString;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
keystringLanguage key
valuestringValue
-

Type

-

LangPackString

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/langPackStringDeleted.html b/data/corefork.telegram.org/constructor/langPackStringDeleted.html deleted file mode 100644 index 0f81d26630..0000000000 --- a/data/corefork.telegram.org/constructor/langPackStringDeleted.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - langPackStringDeleted - - - - - - - - - - - - - -
- -
-
-
- -

langPackStringDeleted

- -

Deleted localization string

-

- -
-
langPackStringDeleted#2979eeb2 key:string = LangPackString;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
keystringLocalization key
-

Type

-

LangPackString

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/langPackStringPluralized.html b/data/corefork.telegram.org/constructor/langPackStringPluralized.html deleted file mode 100644 index 2329e515ad..0000000000 --- a/data/corefork.telegram.org/constructor/langPackStringPluralized.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - langPackStringPluralized - - - - - - - - - - - - - -
- -
-
-
- -

langPackStringPluralized

- -

A language pack string which has different forms based on the number of some object it mentions. See https://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html for more info

-

- -
-
langPackStringPluralized#6c47ac9f flags:# key:string zero_value:flags.0?string one_value:flags.1?string two_value:flags.2?string few_value:flags.3?string many_value:flags.4?string other_value:string = LangPackString;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
keystringLocalization key
zero_valueflags.0?stringValue for zero objects
one_valueflags.1?stringValue for one object
two_valueflags.2?stringValue for two objects
few_valueflags.3?stringValue for a few objects
many_valueflags.4?stringValue for many objects
other_valuestringDefault value
-

Type

-

LangPackString

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/maskCoords.html b/data/corefork.telegram.org/constructor/maskCoords.html deleted file mode 100644 index c654ae73cc..0000000000 --- a/data/corefork.telegram.org/constructor/maskCoords.html +++ /dev/null @@ -1,169 +0,0 @@ - - - - - maskCoords - - - - - - - - - - - - - -
- -
-
-
- -

maskCoords

- -

Position on a photo where a mask should be placed

-

The n position indicates where the mask should be placed:

-
    -
  • 0 => Relative to the forehead
  • -
  • 1 => Relative to the eyes
  • -
  • 2 => Relative to the mouth
  • -
  • 3 => Relative to the chin
  • -
-

- -
-
maskCoords#aed6dbb2 n:int x:double y:double zoom:double = MaskCoords;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
nintPart of the face, relative to which the mask should be placed
xdoubleShift by X-axis measured in widths of the mask scaled to the face size, from left to right. (For example, -1.0 will place the mask just to the left of the default mask position)
ydoubleShift by Y-axis measured in widths of the mask scaled to the face size, from left to right. (For example, -1.0 will place the mask just to the left of the default mask position)
zoomdoubleMask scaling coefficient. (For example, 2.0 means a doubled size)
-

Type

-

MaskCoords

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/message.html b/data/corefork.telegram.org/constructor/message.html deleted file mode 100644 index 331b732222..0000000000 --- a/data/corefork.telegram.org/constructor/message.html +++ /dev/null @@ -1,302 +0,0 @@ - - - - - message - - - - - - - - - - - - - -
- -
-
-
- -

message

- -

A message

-

- -
-
message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true noforwards:flags.26?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
outflags.1?trueIs this an outgoing message
mentionedflags.4?trueWhether we were mentioned in this message
media_unreadflags.5?trueWhether there are unread media attachments in this message
silentflags.13?trueWhether this is a silent message (no notification triggered)
postflags.14?trueWhether this is a channel post
from_scheduledflags.18?trueWhether this is a scheduled message
legacyflags.19?trueThis is a legacy message: it has to be refetched with the new layer
edit_hideflags.21?trueWhether the message should be shown as not modified to the user, even if an edit date is present
pinnedflags.24?trueWhether this message is pinned
idintID of the message
from_idflags.8?PeerID of the sender of the message
peer_idPeerPeer ID, the chat where this message was sent
fwd_fromflags.2?MessageFwdHeaderInfo about forwarded messages
via_bot_idflags.11?longID of the inline bot that generated the message
reply_toflags.3?MessageReplyHeaderReply information
dateintDate of the message
messagestringThe message
mediaflags.9?MessageMediaMedia attachment
reply_markupflags.6?ReplyMarkupReply markup (bot/inline keyboards)
entitiesflags.7?Vector<MessageEntity>Message entities for styled text
viewsflags.10?intView count for channel posts
forwardsflags.10?intForward counter
repliesflags.23?MessageRepliesInfo about post comments (for channels) or message replies (for groups)
edit_dateflags.15?intLast edit date of this message
post_authorflags.16?stringName of the author of this message for channel posts (with signatures enabled)
grouped_idflags.17?longMultiple media messages sent using messages.sendMultiMedia with the same grouped ID indicate an album or media group
restriction_reasonflags.22?Vector<RestrictionReason>Contains the reason why access to this message must be restricted.
ttl_periodflags.25?intTime To Live of the message, once message.date+message.ttl_period === time(), the message will be deleted on the server, and must be deleted locally as well.
-

Type

-

Message

-

Related pages

-

Mentions

-

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

-

Scheduled messages

-

Telegram allows scheduling messages

-

Pinned messages

-

Telegram allows pinning multiple messages on top of a specific chat.

-

Styled text with message entities

-

How to create styled text with message entities

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

-

messages.sendMultiMedia

-

Send an album or grouped media

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionBotAllowed.html b/data/corefork.telegram.org/constructor/messageActionBotAllowed.html deleted file mode 100644 index 06aa62be81..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionBotAllowed.html +++ /dev/null @@ -1,149 +0,0 @@ - - - - - messageActionBotAllowed - - - - - - - - - - - - - -
- -
-
-
- -

messageActionBotAllowed

- -

The domain name of the website on which the user has logged in. More about Telegram Login »

-

- -
-
messageActionBotAllowed#abe9affe domain:string = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
domainstringThe domain name of the website on which the user has logged in.
-

Type

-

MessageAction

-

Related pages

-

Telegram Login Widget

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionChannelCreate.html b/data/corefork.telegram.org/constructor/messageActionChannelCreate.html deleted file mode 100644 index f5ceaffea0..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionChannelCreate.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionChannelCreate - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChannelCreate

- -

The channel was created

-

- -
-
messageActionChannelCreate#95d2ac92 title:string = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
titlestringOriginal channel/supergroup title
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionChannelMigrateFrom.html b/data/corefork.telegram.org/constructor/messageActionChannelMigrateFrom.html deleted file mode 100644 index 961ae445ce..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionChannelMigrateFrom.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messageActionChannelMigrateFrom - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChannelMigrateFrom

- -

Indicates the channel was migrated from the specified chat

-

- -
-
messageActionChannelMigrateFrom#ea3948e9 title:string chat_id:long = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
titlestringThe old chat tite
chat_idlongThe old chat ID
-

Type

-

MessageAction

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionChatAddUser.html b/data/corefork.telegram.org/constructor/messageActionChatAddUser.html deleted file mode 100644 index ac02c388e8..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionChatAddUser.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionChatAddUser - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChatAddUser

- -

New member in the group

-

- -
-
messageActionChatAddUser#15cefd00 users:Vector<long> = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
usersVector<long>Users that were invited to the chat
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionChatCreate.html b/data/corefork.telegram.org/constructor/messageActionChatCreate.html deleted file mode 100644 index 46d18cb90c..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionChatCreate.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageActionChatCreate - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChatCreate

- -

Group created

-

- -
-
messageActionChatCreate#bd47cbad title:string users:Vector<long> = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
titlestringGroup name
usersVector<long>List of group members
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionChatDeletePhoto.html b/data/corefork.telegram.org/constructor/messageActionChatDeletePhoto.html deleted file mode 100644 index 818e2340d4..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionChatDeletePhoto.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messageActionChatDeletePhoto - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChatDeletePhoto

- -

Group profile photo removed.

-

- -
-
messageActionChatDeletePhoto#95e3fbef = MessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionChatDeleteUser.html b/data/corefork.telegram.org/constructor/messageActionChatDeleteUser.html deleted file mode 100644 index 3e90c8dec4..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionChatDeleteUser.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionChatDeleteUser - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChatDeleteUser

- -

User left the group.

-

- -
-
messageActionChatDeleteUser#a43f30cc user_id:long = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongLeaving user ID
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionChatEditPhoto.html b/data/corefork.telegram.org/constructor/messageActionChatEditPhoto.html deleted file mode 100644 index 67c53a98f2..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionChatEditPhoto.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionChatEditPhoto - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChatEditPhoto

- -

Group profile changed

-

- -
-
messageActionChatEditPhoto#7fcb13a8 photo:Photo = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
photoPhotoNew group pofile photo
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionChatEditTitle.html b/data/corefork.telegram.org/constructor/messageActionChatEditTitle.html deleted file mode 100644 index c8b7ed31ae..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionChatEditTitle.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionChatEditTitle - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChatEditTitle

- -

Group name changed.

-

- -
-
messageActionChatEditTitle#b5a1ce5a title:string = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
titlestringNew group name
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionChatJoinedByLink.html b/data/corefork.telegram.org/constructor/messageActionChatJoinedByLink.html deleted file mode 100644 index 6d3f148e39..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionChatJoinedByLink.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionChatJoinedByLink - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChatJoinedByLink

- -

A user joined the chat via an invite link

-

- -
-
messageActionChatJoinedByLink#31224c3 inviter_id:long = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
inviter_idlongID of the user that created the invite link
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionChatMigrateTo.html b/data/corefork.telegram.org/constructor/messageActionChatMigrateTo.html deleted file mode 100644 index 921aa02468..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionChatMigrateTo.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - messageActionChatMigrateTo - - - - - - - - - - - - - -
- -
-
-
- -

messageActionChatMigrateTo

- -

Indicates the chat was migrated to the specified supergroup

-

- -
-
messageActionChatMigrateTo#e1037f92 channel_id:long = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
channel_idlongThe supergroup it was migrated to
-

Type

-

MessageAction

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionContactSignUp.html b/data/corefork.telegram.org/constructor/messageActionContactSignUp.html deleted file mode 100644 index cda339b4aa..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionContactSignUp.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messageActionContactSignUp - - - - - - - - - - - - - -
- -
-
-
- -

messageActionContactSignUp

- -

A contact just signed up to telegram

-

- -
-
messageActionContactSignUp#f3f25f76 = MessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionCustomAction.html b/data/corefork.telegram.org/constructor/messageActionCustomAction.html deleted file mode 100644 index 0c1573d518..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionCustomAction.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionCustomAction - - - - - - - - - - - - - -
- -
-
-
- -

messageActionCustomAction

- -

Custom action (most likely not supported by the current layer, an upgrade might be needed)

-

- -
-
messageActionCustomAction#fae69f56 message:string = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
messagestringAction message
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionEmpty.html b/data/corefork.telegram.org/constructor/messageActionEmpty.html deleted file mode 100644 index 7dab04fcba..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messageActionEmpty - - - - - - - - - - - - - -
- -
-
-
- -

messageActionEmpty

- -

Empty constructor.

-

- -
-
messageActionEmpty#b6aef7b0 = MessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionGeoProximityReached.html b/data/corefork.telegram.org/constructor/messageActionGeoProximityReached.html deleted file mode 100644 index c16450e5aa..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionGeoProximityReached.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - messageActionGeoProximityReached - - - - - - - - - - - - - -
- -
-
-
- -

messageActionGeoProximityReached

- -

A user of the chat is now in proximity of another user

-

- -
-
messageActionGeoProximityReached#98e0d697 from_id:Peer to_id:Peer distance:int = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
from_idPeerThe user or chat that is now in proximity of to_id
to_idPeerThe user or chat that subscribed to live geolocation proximity alerts
distanceintDistance, in meters (0-100000)
-

Type

-

MessageAction

-

Related pages

-

Live geolocation

-

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionGroupCall.html b/data/corefork.telegram.org/constructor/messageActionGroupCall.html deleted file mode 100644 index fa523596db..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionGroupCall.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messageActionGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

messageActionGroupCall

- -

The group call has ended

-

- -
-
messageActionGroupCall#7a0d7f42 flags:# call:InputGroupCall duration:flags.0?int = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
callInputGroupCallGroup call
durationflags.0?intGroup call duration
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionGroupCallScheduled.html b/data/corefork.telegram.org/constructor/messageActionGroupCallScheduled.html deleted file mode 100644 index 76ec4dc754..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionGroupCallScheduled.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageActionGroupCallScheduled - - - - - - - - - - - - - -
- -
-
-
- -

messageActionGroupCallScheduled

- -

A group call was scheduled

-

- -
-
messageActionGroupCallScheduled#b3a07661 call:InputGroupCall schedule_date:int = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallThe group call
schedule_dateintWhen is this group call scheduled to start
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionHistoryClear.html b/data/corefork.telegram.org/constructor/messageActionHistoryClear.html deleted file mode 100644 index e047a56f0e..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionHistoryClear.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messageActionHistoryClear - - - - - - - - - - - - - -
- -
-
-
- -

messageActionHistoryClear

- -

Chat history was cleared

-

- -
-
messageActionHistoryClear#9fbab604 = MessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionInviteToGroupCall.html b/data/corefork.telegram.org/constructor/messageActionInviteToGroupCall.html deleted file mode 100644 index a0cfa41cc8..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionInviteToGroupCall.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageActionInviteToGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

messageActionInviteToGroupCall

- -

A set of users was invited to the group call

-

- -
-
messageActionInviteToGroupCall#502f92f7 call:InputGroupCall users:Vector<long> = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallThe group call
usersVector<long>The invited users
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionPaymentSentMe.html b/data/corefork.telegram.org/constructor/messageActionPaymentSentMe.html deleted file mode 100644 index 0cca1826b7..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionPaymentSentMe.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - messageActionPaymentSentMe - - - - - - - - - - - - - -
- -
-
-
- -

messageActionPaymentSentMe

- -

A user just sent a payment to me (a bot)

-

- -
-
messageActionPaymentSentMe#8f31b327 flags:# currency:string total_amount:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string charge:PaymentCharge = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
currencystringThree-letter ISO 4217 currency code
total_amountlongPrice of the product in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
payloadbytesBot specified invoice payload
infoflags.0?PaymentRequestedInfoOrder info provided by the user
shipping_option_idflags.1?stringIdentifier of the shipping option chosen by the user
chargePaymentChargeProvider payment identifier
-

Type

-

MessageAction

-

Related pages

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionPhoneCall.html b/data/corefork.telegram.org/constructor/messageActionPhoneCall.html deleted file mode 100644 index 3203aab777..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionPhoneCall.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - messageActionPhoneCall - - - - - - - - - - - - - -
- -
-
-
- -

messageActionPhoneCall

- -

A phone call

-

- -
-
messageActionPhoneCall#80e11a7f flags:# video:flags.2?true call_id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.2?trueIs this a video call?
call_idlongCall ID
reasonflags.0?PhoneCallDiscardReasonIf the call has ended, the reason why it ended
durationflags.1?intDuration of the call in seconds
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionPinMessage.html b/data/corefork.telegram.org/constructor/messageActionPinMessage.html deleted file mode 100644 index 64def5498e..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionPinMessage.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messageActionPinMessage - - - - - - - - - - - - - -
- -
-
-
- -

messageActionPinMessage

- -

A message was pinned

-

- -
-
messageActionPinMessage#94bd38ed = MessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionScreenshotTaken.html b/data/corefork.telegram.org/constructor/messageActionScreenshotTaken.html deleted file mode 100644 index ae99e3e399..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionScreenshotTaken.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messageActionScreenshotTaken - - - - - - - - - - - - - -
- -
-
-
- -

messageActionScreenshotTaken

- -

A screenshot of the chat was taken

-

- -
-
messageActionScreenshotTaken#4792929b = MessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionSecureValuesSent.html b/data/corefork.telegram.org/constructor/messageActionSecureValuesSent.html deleted file mode 100644 index 097c9f4ec9..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionSecureValuesSent.html +++ /dev/null @@ -1,149 +0,0 @@ - - - - - messageActionSecureValuesSent - - - - - - - - - - - - - -
- -
-
-
- -

messageActionSecureValuesSent

- -

Request for secure telegram passport values was sent

-

- -
-
messageActionSecureValuesSent#d95c6154 types:Vector<SecureValueType> = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
typesVector<SecureValueType>Secure value types
-

Type

-

MessageAction

-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionSecureValuesSentMe.html b/data/corefork.telegram.org/constructor/messageActionSecureValuesSentMe.html deleted file mode 100644 index b84439a97b..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionSecureValuesSentMe.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - messageActionSecureValuesSentMe - - - - - - - - - - - - - -
- -
-
-
- -

messageActionSecureValuesSentMe

- -

Secure telegram passport values were received

-

- -
-
messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
valuesVector<SecureValue>Vector with information about documents and other Telegram Passport elements that were shared with the bot
credentialsSecureCredentialsEncryptedEncrypted credentials required to decrypt the data
-

Type

-

MessageAction

-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionSetChatTheme.html b/data/corefork.telegram.org/constructor/messageActionSetChatTheme.html deleted file mode 100644 index 39aacb79eb..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionSetChatTheme.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionSetChatTheme - - - - - - - - - - - - - -
- -
-
-
- -

messageActionSetChatTheme

- -

The chat theme was changed

-

- -
-
messageActionSetChatTheme#aa786345 emoticon:string = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
emoticonstringThe emoji that identifies a chat theme
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageActionSetMessagesTTL.html b/data/corefork.telegram.org/constructor/messageActionSetMessagesTTL.html deleted file mode 100644 index 7a6c669d2e..0000000000 --- a/data/corefork.telegram.org/constructor/messageActionSetMessagesTTL.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageActionSetMessagesTTL - - - - - - - - - - - - - -
- -
-
-
- -

messageActionSetMessagesTTL

- -

The Time-To-Live of messages in this chat was changed.

-

- -
-
messageActionSetMessagesTTL#aa1afbfd period:int = MessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
periodintNew Time-To-Live
-

Type

-

MessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageEmpty.html b/data/corefork.telegram.org/constructor/messageEmpty.html deleted file mode 100644 index d87c6ce43f..0000000000 --- a/data/corefork.telegram.org/constructor/messageEmpty.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messageEmpty - - - - - - - - - - - - - -
- -
-
-
- -

messageEmpty

- -

Empty constructor, non-existent message.

-

- -
-
messageEmpty#90a6ca84 flags:# id:int peer_id:flags.0?Peer = Message;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idintMessage identifier
peer_idflags.0?PeerPeer ID, the chat where this message was sent
-

Type

-

Message

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageEntityBankCard.html b/data/corefork.telegram.org/constructor/messageEntityBankCard.html deleted file mode 100644 index 914bde398a..0000000000 --- a/data/corefork.telegram.org/constructor/messageEntityBankCard.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityBankCard - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityBankCard

- -

Indicates a credit card number

-

- -
-
messageEntityBankCard#761e6af4 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageEntityBlockquote.html b/data/corefork.telegram.org/constructor/messageEntityBlockquote.html deleted file mode 100644 index 86d649fff8..0000000000 --- a/data/corefork.telegram.org/constructor/messageEntityBlockquote.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityBlockquote - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityBlockquote

- -

Message entity representing a block quote.

-

- -
-
messageEntityBlockquote#20df5d0 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageEntityBold.html b/data/corefork.telegram.org/constructor/messageEntityBold.html deleted file mode 100644 index 6c1877581e..0000000000 --- a/data/corefork.telegram.org/constructor/messageEntityBold.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityBold - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityBold

- -

Message entity representing bold text.

-

- -
-
messageEntityBold#bd610bc9 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageEntityBotCommand.html b/data/corefork.telegram.org/constructor/messageEntityBotCommand.html deleted file mode 100644 index cf73fc1ad1..0000000000 --- a/data/corefork.telegram.org/constructor/messageEntityBotCommand.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityBotCommand - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityBotCommand

- -

Message entity representing a bot /command

-

- -
-
messageEntityBotCommand#6cef8ac7 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageEntityCashtag.html b/data/corefork.telegram.org/constructor/messageEntityCashtag.html deleted file mode 100644 index 2268d9dc38..0000000000 --- a/data/corefork.telegram.org/constructor/messageEntityCashtag.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityCashtag - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityCashtag

- -

Message entity representing a $cashtag.

-

- -
-
messageEntityCashtag#4c4e743f offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageEntityCode.html b/data/corefork.telegram.org/constructor/messageEntityCode.html deleted file mode 100644 index ffcad5d772..0000000000 --- a/data/corefork.telegram.org/constructor/messageEntityCode.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityCode - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityCode

- -

Message entity representing a codeblock.

-

- -
-
messageEntityCode#28a20571 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageEntityEmail.html b/data/corefork.telegram.org/constructor/messageEntityEmail.html deleted file mode 100644 index c28beb0044..0000000000 --- a/data/corefork.telegram.org/constructor/messageEntityEmail.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityEmail - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityEmail

- -

Message entity representing an email@example.com.

-

- -
-
messageEntityEmail#64e475c2 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageEntityHashtag.html b/data/corefork.telegram.org/constructor/messageEntityHashtag.html deleted file mode 100644 index d0ef4472e6..0000000000 --- a/data/corefork.telegram.org/constructor/messageEntityHashtag.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityHashtag - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityHashtag

- -

#hashtag message entity

-

- -
-
messageEntityHashtag#6f635b0d offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageEntityItalic.html b/data/corefork.telegram.org/constructor/messageEntityItalic.html deleted file mode 100644 index 5e2c73c231..0000000000 --- a/data/corefork.telegram.org/constructor/messageEntityItalic.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityItalic - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityItalic

- -

Message entity representing italic text.

-

- -
-
messageEntityItalic#826f8b60 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageEntityMention.html b/data/corefork.telegram.org/constructor/messageEntityMention.html deleted file mode 100644 index e3eb6f19e7..0000000000 --- a/data/corefork.telegram.org/constructor/messageEntityMention.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messageEntityMention - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityMention

- -

Message entity mentioning the current user

-

- -
-
messageEntityMention#fa04579d offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

-

Related pages

-

Mentions

-

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageEntityMentionName.html b/data/corefork.telegram.org/constructor/messageEntityMentionName.html deleted file mode 100644 index 06cad5ac24..0000000000 --- a/data/corefork.telegram.org/constructor/messageEntityMentionName.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messageEntityMentionName - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityMentionName

- -

Message entity representing a user mention: for creating a mention use inputMessageEntityMentionName.

-

- -
-
messageEntityMentionName#dc7b1140 offset:int length:int user_id:long = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
user_idlongIdentifier of the user that was mentioned
-

Type

-

MessageEntity

-

Related pages

-

Mentions

-

Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.

-

inputMessageEntityMentionName

-

Message entity that can be used to create a user user mention: received mentions use the messageEntityMentionName constructor, instead.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageEntityPhone.html b/data/corefork.telegram.org/constructor/messageEntityPhone.html deleted file mode 100644 index 8fc4ddfcea..0000000000 --- a/data/corefork.telegram.org/constructor/messageEntityPhone.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityPhone - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityPhone

- -

Message entity representing a phone number.

-

- -
-
messageEntityPhone#9b69e34b offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageEntityPre.html b/data/corefork.telegram.org/constructor/messageEntityPre.html deleted file mode 100644 index a499b2d85d..0000000000 --- a/data/corefork.telegram.org/constructor/messageEntityPre.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messageEntityPre - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityPre

- -

Message entity representing a preformatted codeblock, allowing the user to specify a programming language for the codeblock.

-

- -
-
messageEntityPre#73924be0 offset:int length:int language:string = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
languagestringProgramming language of the code
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageEntityStrike.html b/data/corefork.telegram.org/constructor/messageEntityStrike.html deleted file mode 100644 index f7f89848fa..0000000000 --- a/data/corefork.telegram.org/constructor/messageEntityStrike.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityStrike - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityStrike

- -

Message entity representing strikethrough text.

-

- -
-
messageEntityStrike#bf0693d4 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageEntityTextUrl.html b/data/corefork.telegram.org/constructor/messageEntityTextUrl.html deleted file mode 100644 index c6e2fc7574..0000000000 --- a/data/corefork.telegram.org/constructor/messageEntityTextUrl.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - messageEntityTextUrl - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityTextUrl

- -

Message entity representing a text url: for in-text urls like https://google.com use messageEntityUrl.

-

- -
-
messageEntityTextUrl#76a6d327 offset:int length:int url:string = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
urlstringThe actual URL
-

Type

-

MessageEntity

-

Related pages

-

messageEntityUrl

-

Message entity representing an in-text url: https://google.com; for text urls, use messageEntityTextUrl.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageEntityUnderline.html b/data/corefork.telegram.org/constructor/messageEntityUnderline.html deleted file mode 100644 index 526e632345..0000000000 --- a/data/corefork.telegram.org/constructor/messageEntityUnderline.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityUnderline - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityUnderline

- -

Message entity representing underlined text.

-

- -
-
messageEntityUnderline#9c4e7e8b offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageEntityUnknown.html b/data/corefork.telegram.org/constructor/messageEntityUnknown.html deleted file mode 100644 index 5879a5db0d..0000000000 --- a/data/corefork.telegram.org/constructor/messageEntityUnknown.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageEntityUnknown - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityUnknown

- -

Unknown message entity

-

- -
-
messageEntityUnknown#bb92ba95 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageEntityUrl.html b/data/corefork.telegram.org/constructor/messageEntityUrl.html deleted file mode 100644 index 07c55efafe..0000000000 --- a/data/corefork.telegram.org/constructor/messageEntityUrl.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messageEntityUrl - - - - - - - - - - - - - -
- -
-
-
- -

messageEntityUrl

- -

Message entity representing an in-text url: https://google.com; for text urls, use messageEntityTextUrl.

-

- -
-
messageEntityUrl#6ed02538 offset:int length:int = MessageEntity;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset of message entity within message (in UTF-8 codepoints)
lengthintLength of message entity within message (in UTF-8 codepoints)
-

Type

-

MessageEntity

-

Related pages

-

messageEntityTextUrl

-

Message entity representing a text url: for in-text urls like https://google.com use messageEntityUrl.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageFwdHeader.html b/data/corefork.telegram.org/constructor/messageFwdHeader.html deleted file mode 100644 index 8b0d97fd7a..0000000000 --- a/data/corefork.telegram.org/constructor/messageFwdHeader.html +++ /dev/null @@ -1,195 +0,0 @@ - - - - - messageFwdHeader - - - - - - - - - - - - - -
- -
-
-
- -

messageFwdHeader

- -

Info about a forwarded message

-

- -
-
messageFwdHeader#5f777dce flags:# imported:flags.7?true from_id:flags.0?Peer from_name:flags.5?string date:int channel_post:flags.2?int post_author:flags.3?string saved_from_peer:flags.4?Peer saved_from_msg_id:flags.4?int psa_type:flags.6?string = MessageFwdHeader;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
importedflags.7?trueWhether this message was imported from a foreign chat service, click here for more info »
from_idflags.0?PeerThe ID of the user that originally sent the message
from_nameflags.5?stringThe name of the user that originally sent the message
dateintWhen was the message originally sent
channel_postflags.2?intID of the channel message that was forwarded
post_authorflags.3?stringFor channels and if signatures are enabled, author of the channel message
saved_from_peerflags.4?PeerOnly for messages forwarded to the current user (inputPeerSelf), full info about the user/channel that originally sent the message
saved_from_msg_idflags.4?intOnly for messages forwarded to the current user (inputPeerSelf), ID of the message that was forwarded from the original user/channel
psa_typeflags.6?stringPSA type
-

Type

-

MessageFwdHeader

-

Related pages

-

Imported messages

-

Telegram allows importing messages and media from foreign chat apps.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageInteractionCounters.html b/data/corefork.telegram.org/constructor/messageInteractionCounters.html deleted file mode 100644 index da2962d675..0000000000 --- a/data/corefork.telegram.org/constructor/messageInteractionCounters.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messageInteractionCounters - - - - - - - - - - - - - -
- -
-
-
- -

messageInteractionCounters

- -

Message interaction counters

-

- -
-
messageInteractionCounters#ad4fc9bd msg_id:int views:int forwards:int = MessageInteractionCounters;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
msg_idintMessage ID
viewsintViews
forwardsintNumber of times this message was forwarded
-

Type

-

MessageInteractionCounters

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageMediaAudio.html b/data/corefork.telegram.org/constructor/messageMediaAudio.html deleted file mode 100644 index ba89f2824e..0000000000 --- a/data/corefork.telegram.org/constructor/messageMediaAudio.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageMediaAudio - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaAudio

- -

Attached audio file.

-

- -
-
Constructor schema is available as of layer 46. Switch »

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
audioAudioAudi file
-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageMediaContact.html b/data/corefork.telegram.org/constructor/messageMediaContact.html deleted file mode 100644 index a91a3ceee1..0000000000 --- a/data/corefork.telegram.org/constructor/messageMediaContact.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - messageMediaContact - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaContact

- -

Attached contact.

-

- -
-
messageMediaContact#70322949 phone_number:string first_name:string last_name:string vcard:string user_id:long = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number
first_namestringContact's first name
last_namestringContact's last name
vcardstringVCARD of contact
user_idlongUser identifier or 0, if the user with the given phone number is not registered
-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageMediaDice.html b/data/corefork.telegram.org/constructor/messageMediaDice.html deleted file mode 100644 index 5bad20ec57..0000000000 --- a/data/corefork.telegram.org/constructor/messageMediaDice.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messageMediaDice - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaDice

- -

Dice-based animated sticker

-

- -
-
messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
valueintDice value
emoticonstringThe emoji, for now 🏀, 🎲 and 🎯 are supported
-

Type

-

MessageMedia

-

Related pages

-

Dice

-

Telegram supports sending animated dice emojis.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageMediaDocument.html b/data/corefork.telegram.org/constructor/messageMediaDocument.html deleted file mode 100644 index 01ecee2aa2..0000000000 --- a/data/corefork.telegram.org/constructor/messageMediaDocument.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messageMediaDocument - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaDocument

- -

Document (video, audio, voice, sticker, any media type except photo)

-

- -
-
messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
documentflags.0?DocumentAttached document
ttl_secondsflags.2?intTime to live of self-destructing document
-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageMediaEmpty.html b/data/corefork.telegram.org/constructor/messageMediaEmpty.html deleted file mode 100644 index 825f7c898f..0000000000 --- a/data/corefork.telegram.org/constructor/messageMediaEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messageMediaEmpty - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaEmpty

- -

Empty constructor.

-

- -
-
messageMediaEmpty#3ded6320 = MessageMedia;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageMediaGame.html b/data/corefork.telegram.org/constructor/messageMediaGame.html deleted file mode 100644 index 7637a83654..0000000000 --- a/data/corefork.telegram.org/constructor/messageMediaGame.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageMediaGame - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaGame

- -

Telegram game

-

- -
-
messageMediaGame#fdb19008 game:Game = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
gameGameGame
-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageMediaGeo.html b/data/corefork.telegram.org/constructor/messageMediaGeo.html deleted file mode 100644 index a3fe98b26a..0000000000 --- a/data/corefork.telegram.org/constructor/messageMediaGeo.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageMediaGeo - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaGeo

- -

Attached map.

-

- -
-
messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
geoGeoPointGeoPoint
-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageMediaGeoLive.html b/data/corefork.telegram.org/constructor/messageMediaGeoLive.html deleted file mode 100644 index b38c803403..0000000000 --- a/data/corefork.telegram.org/constructor/messageMediaGeoLive.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - messageMediaGeoLive - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaGeoLive

- -

Indicates a live geolocation

-

- -
-
messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
geoGeoPointGeolocation
headingflags.0?intFor live locations, a direction in which the location moves, in degrees; 1-360
periodintValidity period of provided geolocation
proximity_notification_radiusflags.1?intFor live locations, a maximum distance to another chat member for proximity alerts, in meters (0-100000).
-

Type

-

MessageMedia

-

Related pages

-

Live geolocation

-

Telegram allows sending the live geolocation of a user in a chat, optionally setting a proximity alert.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageMediaPhoto.html b/data/corefork.telegram.org/constructor/messageMediaPhoto.html deleted file mode 100644 index f98e27d627..0000000000 --- a/data/corefork.telegram.org/constructor/messageMediaPhoto.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messageMediaPhoto - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaPhoto

- -

Attached photo.

-

- -
-
messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
photoflags.0?PhotoPhoto
ttl_secondsflags.2?intTime to live in seconds of self-destructing photo
-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageMediaPoll.html b/data/corefork.telegram.org/constructor/messageMediaPoll.html deleted file mode 100644 index 91e275cc9b..0000000000 --- a/data/corefork.telegram.org/constructor/messageMediaPoll.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageMediaPoll - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaPoll

- -

Poll

-

- -
-
messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
pollPollThe poll
resultsPollResultsThe results of the poll
-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageMediaUnsupported.html b/data/corefork.telegram.org/constructor/messageMediaUnsupported.html deleted file mode 100644 index 8d665aed5f..0000000000 --- a/data/corefork.telegram.org/constructor/messageMediaUnsupported.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messageMediaUnsupported - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaUnsupported

- -

Current version of the client does not support this media type.

-

- -
-
messageMediaUnsupported#9f84f49e = MessageMedia;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageMediaVenue.html b/data/corefork.telegram.org/constructor/messageMediaVenue.html deleted file mode 100644 index 5ced6077f3..0000000000 --- a/data/corefork.telegram.org/constructor/messageMediaVenue.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messageMediaVenue - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaVenue

- -

Venue

-

- -
-
messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
geoGeoPointGeolocation of venue
titlestringVenue name
addressstringAddress
providerstringVenue provider: currently only "foursquare" needs to be supported
venue_idstringVenue ID in the provider's database
venue_typestringVenue type in the provider's database
-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageMediaWebPage.html b/data/corefork.telegram.org/constructor/messageMediaWebPage.html deleted file mode 100644 index 353a0bc05e..0000000000 --- a/data/corefork.telegram.org/constructor/messageMediaWebPage.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messageMediaWebPage - - - - - - - - - - - - - -
- -
-
-
- -

messageMediaWebPage

- -

Preview of webpage

-

- -
-
messageMediaWebPage#a32dd600 webpage:WebPage = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
webpageWebPageWebpage preview
-

Type

-

MessageMedia

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageRange.html b/data/corefork.telegram.org/constructor/messageRange.html deleted file mode 100644 index 8d32188cfb..0000000000 --- a/data/corefork.telegram.org/constructor/messageRange.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messageRange - - - - - - - - - - - - - -
- -
-
-
- -

messageRange

- -

Indicates a range of chat messages

-

- -
-
messageRange#ae30253 min_id:int max_id:int = MessageRange;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
min_idintStart of range (message ID)
max_idintEnd of range (message ID)
-

Type

-

MessageRange

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageReplies.html b/data/corefork.telegram.org/constructor/messageReplies.html deleted file mode 100644 index 71c951fd01..0000000000 --- a/data/corefork.telegram.org/constructor/messageReplies.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - messageReplies - - - - - - - - - - - - - -
- -
-
-
- -

messageReplies

- -

Info about the comment section of a channel post, or a simple message thread

-

- -
-
messageReplies#83d60fc2 flags:# comments:flags.0?true replies:int replies_pts:int recent_repliers:flags.1?Vector<Peer> channel_id:flags.0?long max_id:flags.2?int read_max_id:flags.3?int = MessageReplies;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
commentsflags.0?trueWhether this constructor contains information about the comment section of a channel post, or a simple message thread
repliesintContains the total number of replies in this thread or comment section.
replies_ptsintPTS of the message that started this thread.
recent_repliersflags.1?Vector<Peer>For channel post comments, contains information about the last few comment posters for a specific thread, to show a small list of commenter profile pictures in client previews.
channel_idflags.0?longFor channel post comments, contains the ID of the associated discussion supergroup
max_idflags.2?intID of the latest message in this thread or comment section.
read_max_idflags.3?intContains the ID of the latest read message in this thread or comment section.
-

Type

-

MessageReplies

-

Related pages

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Discussion groups

-

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageReplyHeader.html b/data/corefork.telegram.org/constructor/messageReplyHeader.html deleted file mode 100644 index 79c9f6f03c..0000000000 --- a/data/corefork.telegram.org/constructor/messageReplyHeader.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - messageReplyHeader - - - - - - - - - - - - - -
- -
-
-
- -

messageReplyHeader

- -

Message replies and thread information

-

- -
-
messageReplyHeader#a6d57763 flags:# reply_to_msg_id:int reply_to_peer_id:flags.0?Peer reply_to_top_id:flags.1?int = MessageReplyHeader;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
reply_to_msg_idintID of message to which this message is replying
reply_to_peer_idflags.0?PeerFor replies sent in channel discussion threads of which the current user is not a member, the discussion group ID
reply_to_top_idflags.1?intID of the message that started this message thread
-

Type

-

MessageReplyHeader

-

Related pages

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageService.html b/data/corefork.telegram.org/constructor/messageService.html deleted file mode 100644 index 6f2806c28b..0000000000 --- a/data/corefork.telegram.org/constructor/messageService.html +++ /dev/null @@ -1,212 +0,0 @@ - - - - - messageService - - - - - - - - - - - - - -
- -
-
-
- -

messageService

- -

Indicates a service message

-

- -
-
messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
outflags.1?trueWhether the message is outgoing
mentionedflags.4?trueWhether we were mentioned in the message
media_unreadflags.5?trueWhether the message contains unread media
silentflags.13?trueWhether the message is silent
postflags.14?trueWhether it's a channel post
legacyflags.19?trueThis is a legacy message: it has to be refetched with the new layer
idintMessage ID
from_idflags.8?PeerID of the sender of this message
peer_idPeerSender of service message
reply_toflags.3?MessageReplyHeaderReply (thread) information
dateintMessage date
actionMessageActionEvent connected with the service message
ttl_periodflags.25?intTime To Live of the message, once message.date+message.ttl_period === time(), the message will be deleted on the server, and must be deleted locally as well.
-

Type

-

Message

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageUserVote.html b/data/corefork.telegram.org/constructor/messageUserVote.html deleted file mode 100644 index 2503208604..0000000000 --- a/data/corefork.telegram.org/constructor/messageUserVote.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messageUserVote - - - - - - - - - - - - - -
- -
-
-
- -

messageUserVote

- -

How a user voted in a poll

-

- -
-
messageUserVote#34d247b4 user_id:long option:bytes date:int = MessageUserVote;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser ID
optionbytesThe option chosen by the user
dateintWhen did the user cast the vote
-

Type

-

MessageUserVote

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageUserVoteInputOption.html b/data/corefork.telegram.org/constructor/messageUserVoteInputOption.html deleted file mode 100644 index 31cdc681e3..0000000000 --- a/data/corefork.telegram.org/constructor/messageUserVoteInputOption.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messageUserVoteInputOption - - - - - - - - - - - - - -
- -
-
-
- -

messageUserVoteInputOption

- -

How a user voted in a poll (reduced constructor, returned if an option was provided to messages.getPollVotes)

-

- -
-
messageUserVoteInputOption#3ca5b0ec user_id:long date:int = MessageUserVote;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongThe user that voted for the queried option
dateintWhen did the user cast the vote
-

Type

-

MessageUserVote

-

Related pages

-

messages.getPollVotes

-

Get poll results for non-anonymous polls

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageUserVoteMultiple.html b/data/corefork.telegram.org/constructor/messageUserVoteMultiple.html deleted file mode 100644 index e3e352fa86..0000000000 --- a/data/corefork.telegram.org/constructor/messageUserVoteMultiple.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messageUserVoteMultiple - - - - - - - - - - - - - -
- -
-
-
- -

messageUserVoteMultiple

- -

How a user voted in a multiple-choice poll

-

- -
-
messageUserVoteMultiple#8a65e557 user_id:long options:Vector<bytes> date:int = MessageUserVote;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser ID
optionsVector<bytes>Options chosen by the user
dateintWhen did the user cast their votes
-

Type

-

MessageUserVote

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messageViews.html b/data/corefork.telegram.org/constructor/messageViews.html deleted file mode 100644 index c41a0b1221..0000000000 --- a/data/corefork.telegram.org/constructor/messageViews.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - messageViews - - - - - - - - - - - - - -
- -
-
-
- -

messageViews

- -

View, forward counter + info about replies of a specific message

-

- -
-
messageViews#455b853d flags:# views:flags.0?int forwards:flags.1?int replies:flags.2?MessageReplies = MessageViews;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
viewsflags.0?intViewcount of message
forwardsflags.1?intForward count of message
repliesflags.2?MessageRepliesReply and thread information of message
-

Type

-

MessageViews

-

Related pages

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.affectedFoundMessages b/data/corefork.telegram.org/constructor/messages.affectedFoundMessages deleted file mode 100644 index 19287535b3..0000000000 --- a/data/corefork.telegram.org/constructor/messages.affectedFoundMessages +++ /dev/null @@ -1,165 +0,0 @@ - - - - - messages.affectedFoundMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.affectedFoundMessages

- -

Messages found and affected by changes

-

- -
-
messages.affectedFoundMessages#ef8d3e6c pts:int pts_count:int offset:int messages:Vector<int> = messages.AffectedFoundMessages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
ptsintEvent count after generation
pts_countintNumber of events that were generated
offsetintIf bigger than zero, the request must be repeated to remove more messages
messagesVector<int>Affected message IDs
-

Type

-

messages.AffectedFoundMessages

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.affectedHistory b/data/corefork.telegram.org/constructor/messages.affectedHistory deleted file mode 100644 index ba05fdf2ee..0000000000 --- a/data/corefork.telegram.org/constructor/messages.affectedHistory +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messages.affectedHistory - - - - - - - - - - - - - -
- -
-
-
- -

messages.affectedHistory

- -

Affected part of communication history with the user or in a chat.

-

- -
-
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
ptsintNumber of events occured in a text box
pts_countintNumber of affected events
offsetintIf a parameter contains positive value, it is necessary to repeat the method call using the given value; during the proceeding of all the history the value itself shall gradually decrease
-

Type

-

messages.AffectedHistory

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.affectedMessages b/data/corefork.telegram.org/constructor/messages.affectedMessages deleted file mode 100644 index f1faed05e9..0000000000 --- a/data/corefork.telegram.org/constructor/messages.affectedMessages +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.affectedMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.affectedMessages

- -

Events affected by operation

-

- -
-
messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

messages.AffectedMessages

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.allStickers b/data/corefork.telegram.org/constructor/messages.allStickers deleted file mode 100644 index d8b853e370..0000000000 --- a/data/corefork.telegram.org/constructor/messages.allStickers +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.allStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.allStickers

- -

Info about all installed stickers

-

- -
-
messages.allStickers#cdbbcebb hash:long sets:Vector<StickerSet> = messages.AllStickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
setsVector<StickerSet>All stickersets
-

Type

-

messages.AllStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.allStickersNotModified b/data/corefork.telegram.org/constructor/messages.allStickersNotModified deleted file mode 100644 index 52ba76473e..0000000000 --- a/data/corefork.telegram.org/constructor/messages.allStickersNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messages.allStickersNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.allStickersNotModified

- -

Info about all installed stickers hasn't changed

-

- -
-
messages.allStickersNotModified#e86602c3 = messages.AllStickers;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

messages.AllStickers

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.archivedStickers b/data/corefork.telegram.org/constructor/messages.archivedStickers deleted file mode 100644 index 7ec2321537..0000000000 --- a/data/corefork.telegram.org/constructor/messages.archivedStickers +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messages.archivedStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.archivedStickers

- -

Archived stickersets

-

- -
-
messages.archivedStickers#4fcba9c8 count:int sets:Vector<StickerSetCovered> = messages.ArchivedStickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countintNumber of archived stickers
setsVector<StickerSetCovered>Archived stickersets
-

Type

-

messages.ArchivedStickers

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.botCallbackAnswer b/data/corefork.telegram.org/constructor/messages.botCallbackAnswer deleted file mode 100644 index f266d3a5e9..0000000000 --- a/data/corefork.telegram.org/constructor/messages.botCallbackAnswer +++ /dev/null @@ -1,177 +0,0 @@ - - - - - messages.botCallbackAnswer - - - - - - - - - - - - - -
- -
-
-
- -

messages.botCallbackAnswer

- -

Callback answer sent by the bot in response to a button press

-

- -
-
messages.botCallbackAnswer#36585ea4 flags:# alert:flags.1?true has_url:flags.3?true native_ui:flags.4?true message:flags.0?string url:flags.2?string cache_time:int = messages.BotCallbackAnswer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
alertflags.1?trueWhether an alert should be shown to the user instead of a toast notification
has_urlflags.3?trueWhether an URL is present
native_uiflags.4?trueWhether to show games in WebView or in native UI.
messageflags.0?stringAlert to show
urlflags.2?stringURL to open
cache_timeintFor how long should this answer be cached
-

Type

-

messages.BotCallbackAnswer

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.botResults b/data/corefork.telegram.org/constructor/messages.botResults deleted file mode 100644 index cbbe818eff..0000000000 --- a/data/corefork.telegram.org/constructor/messages.botResults +++ /dev/null @@ -1,182 +0,0 @@ - - - - - messages.botResults - - - - - - - - - - - - - -
- -
-
-
- -

messages.botResults

- -

Result of a query to an inline bot

-

- -
-
messages.botResults#947ca848 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
galleryflags.0?trueWhether the result is a picture gallery
query_idlongQuery ID
next_offsetflags.1?stringThe next offset to use when navigating through results
switch_pmflags.2?InlineBotSwitchPMWhether the bot requested the user to message him in private
resultsVector<BotInlineResult>The results
cache_timeintCaching validity of the results
usersVector<User>Users mentioned in the results
-

Type

-

messages.BotResults

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.channelMessages b/data/corefork.telegram.org/constructor/messages.channelMessages deleted file mode 100644 index c031610de3..0000000000 --- a/data/corefork.telegram.org/constructor/messages.channelMessages +++ /dev/null @@ -1,185 +0,0 @@ - - - - - messages.channelMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.channelMessages

- -

Channel messages

-

- -
-
messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
inexactflags.1?trueIf set, returned results may be inexact
ptsintEvent count after generation
countintTotal number of results were found server-side (may not be all included here)
offset_id_offsetflags.2?intIndicates the absolute position of messages[0] within the total result set with count count.
This is useful, for example, if the result was fetched using offset_id, and we need to display a progress/total counter (like photo 134 of 200, for all media in a chat, we could simply use photo ${offset_id_offset} of ${count}.
messagesVector<Message>Found messages
chatsVector<Chat>Chats
usersVector<User>Users
-

Type

-

messages.Messages

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.chatAdminsWithInvites b/data/corefork.telegram.org/constructor/messages.chatAdminsWithInvites deleted file mode 100644 index 7e80374bc2..0000000000 --- a/data/corefork.telegram.org/constructor/messages.chatAdminsWithInvites +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messages.chatAdminsWithInvites - - - - - - - - - - - - - -
- -
-
-
- -

messages.chatAdminsWithInvites

- -

Info about chat invites generated by admins.

-

- -
-
messages.chatAdminsWithInvites#b69b72d7 admins:Vector<ChatAdminWithInvites> users:Vector<User> = messages.ChatAdminsWithInvites;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
adminsVector<ChatAdminWithInvites>Info about chat invites generated by admins.
usersVector<User>Mentioned users
-

Type

-

messages.ChatAdminsWithInvites

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.chatFull b/data/corefork.telegram.org/constructor/messages.chatFull deleted file mode 100644 index 70cd2cfb86..0000000000 --- a/data/corefork.telegram.org/constructor/messages.chatFull +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messages.chatFull - - - - - - - - - - - - - -
- -
-
-
- -

messages.chatFull

- -

Extended info on chat and auxiliary data.

-

- -
-
messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.ChatFull;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
full_chatChatFullExtended info on a chat
chatsVector<Chat>List containing basic info on chat
usersVector<User>List of users mentioned above
-

Type

-

messages.ChatFull

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.chatInviteImporters b/data/corefork.telegram.org/constructor/messages.chatInviteImporters deleted file mode 100644 index 3a5bdb51ec..0000000000 --- a/data/corefork.telegram.org/constructor/messages.chatInviteImporters +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messages.chatInviteImporters - - - - - - - - - - - - - -
- -
-
-
- -

messages.chatInviteImporters

- -

Info about the users that joined the chat using a specific chat invite

-

- -
-
messages.chatInviteImporters#81b6b00a count:int importers:Vector<ChatInviteImporter> users:Vector<User> = messages.ChatInviteImporters;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countintNumber of users that joined
importersVector<ChatInviteImporter>The users that joined
usersVector<User>The users that joined
-

Type

-

messages.ChatInviteImporters

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.chats b/data/corefork.telegram.org/constructor/messages.chats deleted file mode 100644 index 713b13682c..0000000000 --- a/data/corefork.telegram.org/constructor/messages.chats +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messages.chats - - - - - - - - - - - - - -
- -
-
-
- -

messages.chats

- -

List of chats with auxiliary data.

-

- -
-
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chatsVector<Chat>List of chats
-

Type

-

messages.Chats

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.chatsSlice b/data/corefork.telegram.org/constructor/messages.chatsSlice deleted file mode 100644 index fb80703c33..0000000000 --- a/data/corefork.telegram.org/constructor/messages.chatsSlice +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.chatsSlice - - - - - - - - - - - - - -
- -
-
-
- -

messages.chatsSlice

- -

Partial list of chats, more would have to be fetched with pagination

-

- -
-
messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countintTotal number of results that were found server-side (not all are included in chats)
chatsVector<Chat>Chats
-

Type

-

messages.Chats

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.checkedHistoryImportPeer b/data/corefork.telegram.org/constructor/messages.checkedHistoryImportPeer deleted file mode 100644 index 912aba22cf..0000000000 --- a/data/corefork.telegram.org/constructor/messages.checkedHistoryImportPeer +++ /dev/null @@ -1,150 +0,0 @@ - - - - - messages.checkedHistoryImportPeer - - - - - - - - - - - - - -
- -
-
-
- -

messages.checkedHistoryImportPeer

- -

Contains a confirmation text to be shown to the user, upon importing chat history, click here for more info ».

-

- -
-
messages.checkedHistoryImportPeer#a24de717 confirm_text:string = messages.CheckedHistoryImportPeer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
confirm_textstringA confirmation text to be shown to the user, upon importing chat history ».
-

Type

-

messages.CheckedHistoryImportPeer

-

Related pages

-

Imported messages

-

Telegram allows importing messages and media from foreign chat apps.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.dhConfig b/data/corefork.telegram.org/constructor/messages.dhConfig deleted file mode 100644 index a65a71a79e..0000000000 --- a/data/corefork.telegram.org/constructor/messages.dhConfig +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.dhConfig - - - - - - - - - - - - - -
- -
-
-
- -

messages.dhConfig

- -

New set of configuring parameters.

-

- -
-
messages.dhConfig#2c221edd g:int p:bytes version:int random:bytes = messages.DhConfig;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
gintNew value prime, see Wikipedia
pbytesNew value primitive root, see Wikipedia
versionintVestion of set of parameters
randombytesRandom sequence of bytes of assigned length
-

Type

-

messages.DhConfig

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.dhConfigNotModified b/data/corefork.telegram.org/constructor/messages.dhConfigNotModified deleted file mode 100644 index d4de496a96..0000000000 --- a/data/corefork.telegram.org/constructor/messages.dhConfigNotModified +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messages.dhConfigNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.dhConfigNotModified

- -

Configuring parameters did not change.

-

- -
-
messages.dhConfigNotModified#c0e24635 random:bytes = messages.DhConfig;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
randombytesRandom sequence of bytes of assigned length
-

Type

-

messages.DhConfig

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.dialogs b/data/corefork.telegram.org/constructor/messages.dialogs deleted file mode 100644 index dcfec69e11..0000000000 --- a/data/corefork.telegram.org/constructor/messages.dialogs +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.dialogs - - - - - - - - - - - - - -
- -
-
-
- -

messages.dialogs

- -

Full list of chats with messages and auxiliary data.

-

- -
-
messages.dialogs#15ba6c40 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
dialogsVector<Dialog>List of chats
messagesVector<Message>List of last messages from each chat
chatsVector<Chat>List of groups mentioned in the chats
usersVector<User>List of users mentioned in messages and groups
-

Type

-

messages.Dialogs

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.dialogsNotModified b/data/corefork.telegram.org/constructor/messages.dialogsNotModified deleted file mode 100644 index 9feccc222e..0000000000 --- a/data/corefork.telegram.org/constructor/messages.dialogsNotModified +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messages.dialogsNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.dialogsNotModified

- -

Dialogs haven't changed

-

- -
-
messages.dialogsNotModified#f0e3e596 count:int = messages.Dialogs;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
countintNumber of dialogs found server-side by the query
-

Type

-

messages.Dialogs

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.dialogsSlice b/data/corefork.telegram.org/constructor/messages.dialogsSlice deleted file mode 100644 index 3c719af2f0..0000000000 --- a/data/corefork.telegram.org/constructor/messages.dialogsSlice +++ /dev/null @@ -1,167 +0,0 @@ - - - - - messages.dialogsSlice - - - - - - - - - - - - - -
- -
-
-
- -

messages.dialogsSlice

- -

Incomplete list of dialogs with messages and auxiliary data.

-

- -
-
messages.dialogsSlice#71e094f3 count:int dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countintTotal number of dialogs
dialogsVector<Dialog>List of dialogs
messagesVector<Message>List of last messages from dialogs
chatsVector<Chat>List of chats mentioned in dialogs
usersVector<User>List of users mentioned in messages and chats
-

Type

-

messages.Dialogs

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.discussionMessage b/data/corefork.telegram.org/constructor/messages.discussionMessage deleted file mode 100644 index f3aa7a299f..0000000000 --- a/data/corefork.telegram.org/constructor/messages.discussionMessage +++ /dev/null @@ -1,185 +0,0 @@ - - - - - messages.discussionMessage - - - - - - - - - - - - - -
- -
-
-
- -

messages.discussionMessage

- -

Information about a message thread

-

- -
-
messages.discussionMessage#a6341782 flags:# messages:Vector<Message> max_id:flags.0?int read_inbox_max_id:flags.1?int read_outbox_max_id:flags.2?int unread_count:int chats:Vector<Chat> users:Vector<User> = messages.DiscussionMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
messagesVector<Message>Discussion messages
max_idflags.0?intMessage ID of latest reply in this thread
read_inbox_max_idflags.1?intMessage ID of latest read incoming message in this thread
read_outbox_max_idflags.2?intMessage ID of latest read outgoing message in this thread
unread_countintNumber of unread messages
chatsVector<Chat>Chats mentioned in constructor
usersVector<User>Users mentioned in constructor
-

Type

-

messages.DiscussionMessage

-

Related pages

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.exportedChatInvite b/data/corefork.telegram.org/constructor/messages.exportedChatInvite deleted file mode 100644 index 375b0f07c1..0000000000 --- a/data/corefork.telegram.org/constructor/messages.exportedChatInvite +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messages.exportedChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

messages.exportedChatInvite

- -

Info about a chat invite

-

- -
-
messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
inviteExportedChatInviteInfo about the chat invite
usersVector<User>Mentioned users
-

Type

-

messages.ExportedChatInvite

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.exportedChatInviteReplaced b/data/corefork.telegram.org/constructor/messages.exportedChatInviteReplaced deleted file mode 100644 index 7c961dd6c2..0000000000 --- a/data/corefork.telegram.org/constructor/messages.exportedChatInviteReplaced +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messages.exportedChatInviteReplaced - - - - - - - - - - - - - -
- -
-
-
- -

messages.exportedChatInviteReplaced

- -

The specified chat invite was replaced with another one

-

- -
-
messages.exportedChatInviteReplaced#222600ef invite:ExportedChatInvite new_invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
inviteExportedChatInviteThe replaced chat invite
new_inviteExportedChatInviteThe invite that replaces the previous invite
usersVector<User>Mentioned users
-

Type

-

messages.ExportedChatInvite

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.favedStickers b/data/corefork.telegram.org/constructor/messages.favedStickers deleted file mode 100644 index c52cace772..0000000000 --- a/data/corefork.telegram.org/constructor/messages.favedStickers +++ /dev/null @@ -1,160 +0,0 @@ - - - - - messages.favedStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.favedStickers

- -

Favorited stickers

-

- -
-
messages.favedStickers#2cb51097 hash:long packs:Vector<StickerPack> stickers:Vector<Document> = messages.FavedStickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
packsVector<StickerPack>Emojis associated to stickers
stickersVector<Document>Favorited stickers
-

Type

-

messages.FavedStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.favedStickersNotModified b/data/corefork.telegram.org/constructor/messages.favedStickersNotModified deleted file mode 100644 index 1acc65d0ab..0000000000 --- a/data/corefork.telegram.org/constructor/messages.favedStickersNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messages.favedStickersNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.favedStickersNotModified

- -

No new favorited stickers were found

-

- -
-
messages.favedStickersNotModified#9e8fa6d3 = messages.FavedStickers;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

messages.FavedStickers

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.featuredStickers b/data/corefork.telegram.org/constructor/messages.featuredStickers deleted file mode 100644 index 45f6cbadc7..0000000000 --- a/data/corefork.telegram.org/constructor/messages.featuredStickers +++ /dev/null @@ -1,165 +0,0 @@ - - - - - messages.featuredStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.featuredStickers

- -

Featured stickersets

-

- -
-
messages.featuredStickers#84c02310 hash:long count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
countintTotal number of featured stickers
setsVector<StickerSetCovered>Featured stickersets
unreadVector<long>IDs of new featured stickersets
-

Type

-

messages.FeaturedStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.featuredStickersNotModified b/data/corefork.telegram.org/constructor/messages.featuredStickersNotModified deleted file mode 100644 index 464ad274fb..0000000000 --- a/data/corefork.telegram.org/constructor/messages.featuredStickersNotModified +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messages.featuredStickersNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.featuredStickersNotModified

- -

Featured stickers haven't changed

-

- -
-
messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
countintTotal number of featured stickers
-

Type

-

messages.FeaturedStickers

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.foundStickerSets b/data/corefork.telegram.org/constructor/messages.foundStickerSets deleted file mode 100644 index 1142cefe10..0000000000 --- a/data/corefork.telegram.org/constructor/messages.foundStickerSets +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.foundStickerSets - - - - - - - - - - - - - -
- -
-
-
- -

messages.foundStickerSets

- -

Found stickersets

-

- -
-
messages.foundStickerSets#8af09dd2 hash:long sets:Vector<StickerSetCovered> = messages.FoundStickerSets;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
setsVector<StickerSetCovered>Found stickersets
-

Type

-

messages.FoundStickerSets

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.foundStickerSetsNotModified b/data/corefork.telegram.org/constructor/messages.foundStickerSetsNotModified deleted file mode 100644 index 1a502cb48b..0000000000 --- a/data/corefork.telegram.org/constructor/messages.foundStickerSetsNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messages.foundStickerSetsNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.foundStickerSetsNotModified

- -

No further results were found

-

- -
-
messages.foundStickerSetsNotModified#d54b65d = messages.FoundStickerSets;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

messages.FoundStickerSets

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.highScores b/data/corefork.telegram.org/constructor/messages.highScores deleted file mode 100644 index da9b83ec90..0000000000 --- a/data/corefork.telegram.org/constructor/messages.highScores +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messages.highScores - - - - - - - - - - - - - -
- -
-
-
- -

messages.highScores

- -

Highscores in a game

-

- -
-
messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
scoresVector<HighScore>Highscores
usersVector<User>Users, associated to the highscores
-

Type

-

messages.HighScores

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.historyImport b/data/corefork.telegram.org/constructor/messages.historyImport deleted file mode 100644 index 9a72e4a67c..0000000000 --- a/data/corefork.telegram.org/constructor/messages.historyImport +++ /dev/null @@ -1,150 +0,0 @@ - - - - - messages.historyImport - - - - - - - - - - - - - -
- -
-
-
- -

messages.historyImport

- -

ID of a specific chat import session, click here for more info ».

-

- -
-
messages.historyImport#1662af0b id:long = messages.HistoryImport;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idlongHistory import ID
-

Type

-

messages.HistoryImport

-

Related pages

-

Imported messages

-

Telegram allows importing messages and media from foreign chat apps.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.historyImportParsed b/data/corefork.telegram.org/constructor/messages.historyImportParsed deleted file mode 100644 index a77632bb59..0000000000 --- a/data/corefork.telegram.org/constructor/messages.historyImportParsed +++ /dev/null @@ -1,166 +0,0 @@ - - - - - messages.historyImportParsed - - - - - - - - - - - - - -
- -
-
-
- -

messages.historyImportParsed

- -

Contains information about a chat export file generated by a foreign chat app, click here for more info.
-If neither the pm or group flags are set, the specified chat export was generated from a chat of unknown type.

-

- -
-
messages.historyImportParsed#5e0fb7b9 flags:# pm:flags.0?true group:flags.1?true title:flags.2?string = messages.HistoryImportParsed;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
pmflags.0?trueThe chat export file was generated from a private chat.
groupflags.1?trueThe chat export file was generated from a group chat.
titleflags.2?stringTitle of the chat.
-

Type

-

messages.HistoryImportParsed

-

Related pages

-

Imported messages

-

Telegram allows importing messages and media from foreign chat apps.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.messageEditData b/data/corefork.telegram.org/constructor/messages.messageEditData deleted file mode 100644 index b00c20fc82..0000000000 --- a/data/corefork.telegram.org/constructor/messages.messageEditData +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messages.messageEditData - - - - - - - - - - - - - -
- -
-
-
- -

messages.messageEditData

- -

Message edit data for media

-

- -
-
messages.messageEditData#26b5dde6 flags:# caption:flags.0?true = messages.MessageEditData;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
captionflags.0?trueMedia caption, if the specified media's caption can be edited
-

Type

-

messages.MessageEditData

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.messageViews b/data/corefork.telegram.org/constructor/messages.messageViews deleted file mode 100644 index 748c8c45ff..0000000000 --- a/data/corefork.telegram.org/constructor/messages.messageViews +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messages.messageViews - - - - - - - - - - - - - -
- -
-
-
- -

messages.messageViews

- -

View, forward counter + info about replies

-

- -
-
messages.messageViews#b6c4f543 views:Vector<MessageViews> chats:Vector<Chat> users:Vector<User> = messages.MessageViews;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
viewsVector<MessageViews>View, forward counter + info about replies
chatsVector<Chat>Chats mentioned in constructor
usersVector<User>Users mentioned in constructor
-

Type

-

messages.MessageViews

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.messages b/data/corefork.telegram.org/constructor/messages.messages deleted file mode 100644 index a47e40b872..0000000000 --- a/data/corefork.telegram.org/constructor/messages.messages +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messages.messages - - - - - - - - - - - - - -
- -
-
-
- -

messages.messages

- -

Full list of messages with auxilary data.

-

- -
-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messagesVector<Message>List of messages
chatsVector<Chat>List of chats mentioned in dialogs
usersVector<User>List of users mentioned in messages and chats
-

Type

-

messages.Messages

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.messagesNotModified b/data/corefork.telegram.org/constructor/messages.messagesNotModified deleted file mode 100644 index 45593813ba..0000000000 --- a/data/corefork.telegram.org/constructor/messages.messagesNotModified +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messages.messagesNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.messagesNotModified

- -

No new messages matching the query were found

-

- -
-
messages.messagesNotModified#74535f21 count:int = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
countintNumber of results found server-side by the given query
-

Type

-

messages.Messages

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.messagesSlice b/data/corefork.telegram.org/constructor/messages.messagesSlice deleted file mode 100644 index 671a158ea9..0000000000 --- a/data/corefork.telegram.org/constructor/messages.messagesSlice +++ /dev/null @@ -1,185 +0,0 @@ - - - - - messages.messagesSlice - - - - - - - - - - - - - -
- -
-
-
- -

messages.messagesSlice

- -

Incomplete list of messages and auxiliary data.

-

- -
-
messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
inexactflags.1?trueIf set, indicates that the results may be inexact
countintTotal number of messages in the list
next_rateflags.0?intRate to use in the offset_rate parameter in the next call to messages.searchGlobal
offset_id_offsetflags.2?intIndicates the absolute position of messages[0] within the total result set with count count.
This is useful, for example, if the result was fetched using offset_id, and we need to display a progress/total counter (like photo 134 of 200, for all media in a chat, we could simply use photo ${offset_id_offset} of ${count}.
messagesVector<Message>List of messages
chatsVector<Chat>List of chats mentioned in messages
usersVector<User>List of users mentioned in messages and chats
-

Type

-

messages.Messages

-

Related pages

-

messages.searchGlobal

-

Search for messages and peers globally

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.peerDialogs b/data/corefork.telegram.org/constructor/messages.peerDialogs deleted file mode 100644 index 0fcf070955..0000000000 --- a/data/corefork.telegram.org/constructor/messages.peerDialogs +++ /dev/null @@ -1,170 +0,0 @@ - - - - - messages.peerDialogs - - - - - - - - - - - - - -
- -
-
-
- -

messages.peerDialogs

- -

Dialog info of multiple peers

-

- -
-
messages.peerDialogs#3371c354 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> state:updates.State = messages.PeerDialogs;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
dialogsVector<Dialog>Dialog info
messagesVector<Message>Messages mentioned in dialog info
chatsVector<Chat>Chats
usersVector<User>Users
stateupdates.StateCurrent update state of dialog
-

Type

-

messages.PeerDialogs

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.recentStickers b/data/corefork.telegram.org/constructor/messages.recentStickers deleted file mode 100644 index b1f08bb9a8..0000000000 --- a/data/corefork.telegram.org/constructor/messages.recentStickers +++ /dev/null @@ -1,165 +0,0 @@ - - - - - messages.recentStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.recentStickers

- -

Recently used stickers

-

- -
-
messages.recentStickers#88d37c56 hash:long packs:Vector<StickerPack> stickers:Vector<Document> dates:Vector<int> = messages.RecentStickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
packsVector<StickerPack>Emojis associated to stickers
stickersVector<Document>Recent stickers
datesVector<int>When was each sticker last used
-

Type

-

messages.RecentStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.recentStickersNotModified b/data/corefork.telegram.org/constructor/messages.recentStickersNotModified deleted file mode 100644 index 4f0f177cb4..0000000000 --- a/data/corefork.telegram.org/constructor/messages.recentStickersNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messages.recentStickersNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.recentStickersNotModified

- -

No new recent sticker was found

-

- -
-
messages.recentStickersNotModified#b17f890 = messages.RecentStickers;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

messages.RecentStickers

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.savedGifs b/data/corefork.telegram.org/constructor/messages.savedGifs deleted file mode 100644 index 9d3af5fe6d..0000000000 --- a/data/corefork.telegram.org/constructor/messages.savedGifs +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.savedGifs - - - - - - - - - - - - - -
- -
-
-
- -

messages.savedGifs

- -

Saved gifs

-

- -
-
messages.savedGifs#84a02a0d hash:long gifs:Vector<Document> = messages.SavedGifs;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
gifsVector<Document>List of saved gifs
-

Type

-

messages.SavedGifs

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.savedGifsNotModified b/data/corefork.telegram.org/constructor/messages.savedGifsNotModified deleted file mode 100644 index 58885927ab..0000000000 --- a/data/corefork.telegram.org/constructor/messages.savedGifsNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messages.savedGifsNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.savedGifsNotModified

- -

No new saved gifs were found

-

- -
-
messages.savedGifsNotModified#e8025ca2 = messages.SavedGifs;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

messages.SavedGifs

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.searchCounter b/data/corefork.telegram.org/constructor/messages.searchCounter deleted file mode 100644 index 62a83df808..0000000000 --- a/data/corefork.telegram.org/constructor/messages.searchCounter +++ /dev/null @@ -1,165 +0,0 @@ - - - - - messages.searchCounter - - - - - - - - - - - - - -
- -
-
-
- -

messages.searchCounter

- -

Indicates how many results would be found by a messages.search call with the same parameters

-

- -
-
messages.searchCounter#e844ebff flags:# inexact:flags.1?true filter:MessagesFilter count:int = messages.SearchCounter;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
inexactflags.1?trueIf set, the results may be inexact
filterMessagesFilterProvided message filter
countintNumber of results that were found server-side
-

Type

-

messages.SearchCounter

-

Related pages

-

messages.search

-

Gets back found messages

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.sentEncryptedFile b/data/corefork.telegram.org/constructor/messages.sentEncryptedFile deleted file mode 100644 index d13e7666d7..0000000000 --- a/data/corefork.telegram.org/constructor/messages.sentEncryptedFile +++ /dev/null @@ -1,152 +0,0 @@ - - - - - messages.sentEncryptedFile - - - - - - - - - - - - - -
- -
-
-
- -

messages.sentEncryptedFile

- -

Message with a file enclosure sent to a protected chat

-

- -
-
messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
dateintSending date
fileEncryptedFileAttached file
-

Type

-

messages.SentEncryptedMessage

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.sentEncryptedMessage b/data/corefork.telegram.org/constructor/messages.sentEncryptedMessage deleted file mode 100644 index 45aa9070c8..0000000000 --- a/data/corefork.telegram.org/constructor/messages.sentEncryptedMessage +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messages.sentEncryptedMessage - - - - - - - - - - - - - -
- -
-
-
- -

messages.sentEncryptedMessage

- -

Message without file attachemts sent to an encrypted file.

-

- -
-
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
dateintDate of sending
-

Type

-

messages.SentEncryptedMessage

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.sentMessageLink b/data/corefork.telegram.org/constructor/messages.sentMessageLink deleted file mode 100644 index 746af76cc9..0000000000 --- a/data/corefork.telegram.org/constructor/messages.sentMessageLink +++ /dev/null @@ -1,167 +0,0 @@ - - - - - messages.sentMessageLink - - - - - - - - - - - - - -
- -
-
-
- -

messages.sentMessageLink

- -

Info on successfully sent message and on changes links.

-

- -
-
Constructor schema is available as of layer 24. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idintMessage ID
dateintDate of sending
ptsintNew value of pts parameter of a current state
seqintNew value of seq parameter of a current state
linksVector<contacts.Link>List of changes links
-

Type

-

messages.SentMessage

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.sponsoredMessages b/data/corefork.telegram.org/constructor/messages.sponsoredMessages deleted file mode 100644 index 5e2795349e..0000000000 --- a/data/corefork.telegram.org/constructor/messages.sponsoredMessages +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messages.sponsoredMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.sponsoredMessages

- -

A set of sponsored messages associated to a channel

-

- -
-
messages.sponsoredMessages#65a4c7d5 messages:Vector<SponsoredMessage> chats:Vector<Chat> users:Vector<User> = messages.SponsoredMessages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messagesVector<SponsoredMessage>Sponsored messages
chatsVector<Chat>Chats mentioned in the sponsored messages
usersVector<User>Users mentioned in the sponsored messages
-

Type

-

messages.SponsoredMessages

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.statedMessagesLinks b/data/corefork.telegram.org/constructor/messages.statedMessagesLinks deleted file mode 100644 index c208a82233..0000000000 --- a/data/corefork.telegram.org/constructor/messages.statedMessagesLinks +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.statedMessagesLinks - - - - - - - - - - - - - -
- -
-
-
- -

messages.statedMessagesLinks

- -

Message with auxiliary data, state data and the list of changed links.

-

- -
-
Constructor schema is available as of layer 24. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messagesVector<Message>List of messages
chatsVector<Chat>List of cats mentioned in messages
usersVector<User>List of users mentioned in messages and cahts
linksVector<contacts.Link>List of changed links
ptsintNumber of event occurred in a text box
seqintNumber of sent updates
-

Type

-

messages.StatedMessages

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.stickerSet b/data/corefork.telegram.org/constructor/messages.stickerSet deleted file mode 100644 index c2a9db0ff5..0000000000 --- a/data/corefork.telegram.org/constructor/messages.stickerSet +++ /dev/null @@ -1,157 +0,0 @@ - - - - - messages.stickerSet - - - - - - - - - - - - - -
- -
-
-
- -

messages.stickerSet

- -

Stickerset and stickers inside it

-

- -
-
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
setStickerSetThe stickerset
packsVector<StickerPack>Emoji info for stickers
documentsVector<Document>Stickers in stickerset
-

Type

-

messages.StickerSet

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.stickerSetInstallResultArchive b/data/corefork.telegram.org/constructor/messages.stickerSetInstallResultArchive deleted file mode 100644 index 23323c9671..0000000000 --- a/data/corefork.telegram.org/constructor/messages.stickerSetInstallResultArchive +++ /dev/null @@ -1,147 +0,0 @@ - - - - - messages.stickerSetInstallResultArchive - - - - - - - - - - - - - -
- -
-
-
- -

messages.stickerSetInstallResultArchive

- -

The stickerset was installed, but since there are too many stickersets some were archived

-

- -
-
messages.stickerSetInstallResultArchive#35e410a8 sets:Vector<StickerSetCovered> = messages.StickerSetInstallResult;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
setsVector<StickerSetCovered>Archived stickersets
-

Type

-

messages.StickerSetInstallResult

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.stickerSetInstallResultSuccess b/data/corefork.telegram.org/constructor/messages.stickerSetInstallResultSuccess deleted file mode 100644 index 4cc5bbbc08..0000000000 --- a/data/corefork.telegram.org/constructor/messages.stickerSetInstallResultSuccess +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messages.stickerSetInstallResultSuccess - - - - - - - - - - - - - -
- -
-
-
- -

messages.stickerSetInstallResultSuccess

- -

The stickerset was installed successfully

-

- -
-
messages.stickerSetInstallResultSuccess#38641628 = messages.StickerSetInstallResult;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

messages.StickerSetInstallResult

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.stickers b/data/corefork.telegram.org/constructor/messages.stickers deleted file mode 100644 index d7bdf66de5..0000000000 --- a/data/corefork.telegram.org/constructor/messages.stickers +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.stickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.stickers

- -

Found stickers

-

- -
-
messages.stickers#30a6ec7e hash:long stickers:Vector<Document> = messages.Stickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
stickersVector<Document>Stickers
-

Type

-

messages.Stickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.stickersNotModified b/data/corefork.telegram.org/constructor/messages.stickersNotModified deleted file mode 100644 index 83fd74a70b..0000000000 --- a/data/corefork.telegram.org/constructor/messages.stickersNotModified +++ /dev/null @@ -1,132 +0,0 @@ - - - - - messages.stickersNotModified - - - - - - - - - - - - - -
- -
-
-
- -

messages.stickersNotModified

- -

No new stickers were found for the given query

-

- -
-
messages.stickersNotModified#f1749a22 = messages.Stickers;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

messages.Stickers

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/messages.votesList b/data/corefork.telegram.org/constructor/messages.votesList deleted file mode 100644 index 938c8150ff..0000000000 --- a/data/corefork.telegram.org/constructor/messages.votesList +++ /dev/null @@ -1,170 +0,0 @@ - - - - - messages.votesList - - - - - - - - - - - - - -
- -
-
-
- -

messages.votesList

- -

How users voted in a poll

-

- -
-
messages.votesList#823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
countintTotal number of votes for all options (or only for the chosen option, if provided to messages.getPollVotes)
votesVector<MessageUserVote>Vote info for each user
usersVector<User>Info about users that voted in the poll
next_offsetflags.0?stringOffset to use with the next messages.getPollVotes request, empty string if no more results are available.
-

Type

-

messages.VotesList

-

Related pages

-

messages.getPollVotes

-

Get poll results for non-anonymous polls

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/nearestDc.html b/data/corefork.telegram.org/constructor/nearestDc.html deleted file mode 100644 index a18b53856a..0000000000 --- a/data/corefork.telegram.org/constructor/nearestDc.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - nearestDc - - - - - - - - - - - - - -
- -
-
-
- -

nearestDc

- -

Nearest data centre, according to geo-ip.

-

- -
-
nearestDc#8e1a1775 country:string this_dc:int nearest_dc:int = NearestDc;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countrystringCountry code determined by geo-ip
this_dcintNumber of current data centre
nearest_dcintNumber of nearest data centre
-

Type

-

NearestDc

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/notifyBroadcasts.html b/data/corefork.telegram.org/constructor/notifyBroadcasts.html deleted file mode 100644 index 2da9d0db04..0000000000 --- a/data/corefork.telegram.org/constructor/notifyBroadcasts.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - notifyBroadcasts - - - - - - - - - - - - - -
- -
-
-
- -

notifyBroadcasts

- -

Channel notification settings

-

- -
-
notifyBroadcasts#d612e8ef = NotifyPeer;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

NotifyPeer

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/notifyChats.html b/data/corefork.telegram.org/constructor/notifyChats.html deleted file mode 100644 index 783873a464..0000000000 --- a/data/corefork.telegram.org/constructor/notifyChats.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - notifyChats - - - - - - - - - - - - - -
- -
-
-
- -

notifyChats

- -

Notifications generated by all groups.

-

- -
-
notifyChats#c007cec3 = NotifyPeer;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

NotifyPeer

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/notifyPeer.html b/data/corefork.telegram.org/constructor/notifyPeer.html deleted file mode 100644 index 076a5bc749..0000000000 --- a/data/corefork.telegram.org/constructor/notifyPeer.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - notifyPeer - - - - - - - - - - - - - -
- -
-
-
- -

notifyPeer

- -

Notifications generated by a certain user or group.

-

- -
-
notifyPeer#9fd40bd8 peer:Peer = NotifyPeer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerPeeruser or group
-

Type

-

NotifyPeer

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/notifyUsers.html b/data/corefork.telegram.org/constructor/notifyUsers.html deleted file mode 100644 index 14fc4f6b2e..0000000000 --- a/data/corefork.telegram.org/constructor/notifyUsers.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - notifyUsers - - - - - - - - - - - - - -
- -
-
-
- -

notifyUsers

- -

Notifications generated by all users.

-

- -
-
notifyUsers#b4c83b4c = NotifyPeer;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

NotifyPeer

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/null.html b/data/corefork.telegram.org/constructor/null.html deleted file mode 100644 index 28355899f9..0000000000 --- a/data/corefork.telegram.org/constructor/null.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - null - - - - - - - - - - - - - -
- -
-
-
- -

null

- -

Corresponds to an arbitrary empty object.

-

- -
-
null#56730bcc = Null;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Null

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/page.html b/data/corefork.telegram.org/constructor/page.html deleted file mode 100644 index bbbea09703..0000000000 --- a/data/corefork.telegram.org/constructor/page.html +++ /dev/null @@ -1,190 +0,0 @@ - - - - - page - - - - - - - - - - - - - -
- -
-
-
- -

page

- -

Instant view page

-

- -
-
page#98657f0d flags:# part:flags.0?true rtl:flags.1?true v2:flags.2?true url:string blocks:Vector<PageBlock> photos:Vector<Photo> documents:Vector<Document> views:flags.3?int = Page;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
partflags.0?trueIndicates that not full page preview is available to the client and it will need to fetch full Instant View from the server using messages.getWebPagePreview.
rtlflags.1?trueWhether the page contains RTL text
v2flags.2?trueWhether this is an IV v2 page
urlstringOriginal page HTTP URL
blocksVector<PageBlock>Page elements (like with HTML elements, only as TL constructors)
photosVector<Photo>Photos in page
documentsVector<Document>Media in page
viewsflags.3?intViewcount
-

Type

-

Page

-

Related pages

-

messages.getWebPagePreview

-

Get preview of webpage

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockAnchor.html b/data/corefork.telegram.org/constructor/pageBlockAnchor.html deleted file mode 100644 index 7cc55160f8..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockAnchor.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockAnchor - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockAnchor

- -

Link to section within the page itself (like <a href="#target">anchor</a>)

-

- -
-
pageBlockAnchor#ce0d37b0 name:string = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
namestringName of target section
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockAudio.html b/data/corefork.telegram.org/constructor/pageBlockAudio.html deleted file mode 100644 index b6572ee95f..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockAudio.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - pageBlockAudio - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockAudio

- -

Audio

-

- -
-
pageBlockAudio#804361ea audio_id:long caption:PageCaption = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
audio_idlongAudio ID (to be fetched from the container page constructor
captionPageCaptionAudio caption
-

Type

-

PageBlock

-

Related pages

-

page

-

Instant view page

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockAuthorDate.html b/data/corefork.telegram.org/constructor/pageBlockAuthorDate.html deleted file mode 100644 index 7131a22305..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockAuthorDate.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageBlockAuthorDate - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockAuthorDate

- -

Author and date of creation of article

-

- -
-
pageBlockAuthorDate#baafe5e0 author:RichText published_date:int = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
authorRichTextAuthor name
published_dateintDate of pubblication
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockBlockquote.html b/data/corefork.telegram.org/constructor/pageBlockBlockquote.html deleted file mode 100644 index f3c5e0099c..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockBlockquote.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageBlockBlockquote - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockBlockquote

- -

Quote (equivalent to the HTML <blockquote>)

-

- -
-
pageBlockBlockquote#263d7c26 text:RichText caption:RichText = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextQuote contents
captionRichTextCaption
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockChannel.html b/data/corefork.telegram.org/constructor/pageBlockChannel.html deleted file mode 100644 index 254f451aed..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockChannel.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockChannel - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockChannel

- -

Reference to a telegram channel

-

- -
-
pageBlockChannel#ef1751b5 channel:Chat = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
channelChatThe channel/supergroup/chat
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockCollage.html b/data/corefork.telegram.org/constructor/pageBlockCollage.html deleted file mode 100644 index 29e943edb0..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockCollage.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageBlockCollage - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockCollage

- -

Collage of media

-

- -
-
pageBlockCollage#65a0fa4d items:Vector<PageBlock> caption:PageCaption = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
itemsVector<PageBlock>Media elements
captionPageCaptionCaption
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockCover.html b/data/corefork.telegram.org/constructor/pageBlockCover.html deleted file mode 100644 index 983e32e908..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockCover.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockCover - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockCover

- -

A page cover

-

- -
-
pageBlockCover#39f23300 cover:PageBlock = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
coverPageBlockCover
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockDetails.html b/data/corefork.telegram.org/constructor/pageBlockDetails.html deleted file mode 100644 index 06abaa77d7..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockDetails.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - pageBlockDetails - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockDetails

- -

A collapsible details block

-

- -
-
pageBlockDetails#76768bed flags:# open:flags.0?true blocks:Vector<PageBlock> title:RichText = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
openflags.0?trueWhether the block is open by default
blocksVector<PageBlock>Block contents
titleRichTextAlways visible heading for the block
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockDivider.html b/data/corefork.telegram.org/constructor/pageBlockDivider.html deleted file mode 100644 index 15f4efb3bb..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockDivider.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - pageBlockDivider - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockDivider

- -

An empty block separating a page

-

- -
-
pageBlockDivider#db20b188 = PageBlock;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockEmbed.html b/data/corefork.telegram.org/constructor/pageBlockEmbed.html deleted file mode 100644 index 77373b597e..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockEmbed.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - pageBlockEmbed - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockEmbed

- -

An embedded webpage

-

- -
-
pageBlockEmbed#a8718dc5 flags:# full_width:flags.0?true allow_scrolling:flags.3?true url:flags.1?string html:flags.2?string poster_photo_id:flags.4?long w:flags.5?int h:flags.5?int caption:PageCaption = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
full_widthflags.0?trueWhether the block should be full width
allow_scrollingflags.3?trueWhether scrolling should be allowed
urlflags.1?stringWeb page URL, if available
htmlflags.2?stringHTML-markup of the embedded page
poster_photo_idflags.4?longPoster photo, if available
wflags.5?intBlock width, if known
hflags.5?intBlock height, if known
captionPageCaptionCaption
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockEmbedPost.html b/data/corefork.telegram.org/constructor/pageBlockEmbedPost.html deleted file mode 100644 index 73eccb443e..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockEmbedPost.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - pageBlockEmbedPost - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockEmbedPost

- -

An embedded post

-

- -
-
pageBlockEmbedPost#f259a80b url:string webpage_id:long author_photo_id:long author:string date:int blocks:Vector<PageBlock> caption:PageCaption = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringWeb page URL
webpage_idlongID of generated webpage preview
author_photo_idlongID of the author's photo
authorstringAuthor name
dateintCreation date
blocksVector<PageBlock>Post contents
captionPageCaptionCaption
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockFooter.html b/data/corefork.telegram.org/constructor/pageBlockFooter.html deleted file mode 100644 index c2e9d41638..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockFooter.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockFooter - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockFooter

- -

Page footer

-

- -
-
pageBlockFooter#48870999 text:RichText = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextContents
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockHeader.html b/data/corefork.telegram.org/constructor/pageBlockHeader.html deleted file mode 100644 index 943c8f2496..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockHeader.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockHeader - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockHeader

- -

Page header

-

- -
-
pageBlockHeader#bfd064ec text:RichText = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextContents
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockKicker.html b/data/corefork.telegram.org/constructor/pageBlockKicker.html deleted file mode 100644 index e627f93058..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockKicker.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockKicker - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockKicker

- -

Kicker

-

- -
-
pageBlockKicker#1e148390 text:RichText = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextContents
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockList.html b/data/corefork.telegram.org/constructor/pageBlockList.html deleted file mode 100644 index 3f0d4dcb92..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockList.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockList - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockList

- -

Unordered list of IV blocks

-

- -
-
pageBlockList#e4e88011 items:Vector<PageListItem> = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
itemsVector<PageListItem>List of blocks in an IV page
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockMap.html b/data/corefork.telegram.org/constructor/pageBlockMap.html deleted file mode 100644 index a513f5b8b7..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockMap.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - pageBlockMap - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockMap

- -

A map

-

- -
-
pageBlockMap#a44f3ef6 geo:GeoPoint zoom:int w:int h:int caption:PageCaption = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
geoGeoPointLocation of the map center
zoomintMap zoom level; 13-20
wintMap width in pixels before applying scale; 16-102
hintMap height in pixels before applying scale; 16-1024
captionPageCaptionCaption
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockOrderedList.html b/data/corefork.telegram.org/constructor/pageBlockOrderedList.html deleted file mode 100644 index 8cb418baa8..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockOrderedList.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockOrderedList - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockOrderedList

- -

Ordered list of IV blocks

-

- -
-
pageBlockOrderedList#9a8ae1e1 items:Vector<PageListOrderedItem> = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
itemsVector<PageListOrderedItem>List items
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockParagraph.html b/data/corefork.telegram.org/constructor/pageBlockParagraph.html deleted file mode 100644 index eaadc3a72b..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockParagraph.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockParagraph - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockParagraph

- -

A paragraph

-

- -
-
pageBlockParagraph#467a0766 text:RichText = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockPhoto.html b/data/corefork.telegram.org/constructor/pageBlockPhoto.html deleted file mode 100644 index 39a3e42f5b..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockPhoto.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - pageBlockPhoto - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockPhoto

- -

A photo

-

- -
-
pageBlockPhoto#1759c560 flags:# photo_id:long caption:PageCaption url:flags.0?string webpage_id:flags.0?long = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
photo_idlongPhoto ID
captionPageCaptionCaption
urlflags.0?stringHTTP URL of page the photo leads to when clicked
webpage_idflags.0?longID of preview of the page the photo leads to when clicked
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockPreformatted.html b/data/corefork.telegram.org/constructor/pageBlockPreformatted.html deleted file mode 100644 index 4809f766ac..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockPreformatted.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageBlockPreformatted - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockPreformatted

- -

Preformatted (<pre> text)

-

- -
-
pageBlockPreformatted#c070d93e text:RichText language:string = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
languagestringProgramming language of preformatted text
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockPullquote.html b/data/corefork.telegram.org/constructor/pageBlockPullquote.html deleted file mode 100644 index c7946b400f..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockPullquote.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageBlockPullquote - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockPullquote

- -

Pullquote

-

- -
-
pageBlockPullquote#4f4456d3 text:RichText caption:RichText = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
captionRichTextCaption
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockRelatedArticles.html b/data/corefork.telegram.org/constructor/pageBlockRelatedArticles.html deleted file mode 100644 index 8d8029034a..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockRelatedArticles.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageBlockRelatedArticles - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockRelatedArticles

- -

Related articles

-

- -
-
pageBlockRelatedArticles#16115a96 title:RichText articles:Vector<PageRelatedArticle> = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
titleRichTextTitle
articlesVector<PageRelatedArticle>Related articles
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockSlideshow.html b/data/corefork.telegram.org/constructor/pageBlockSlideshow.html deleted file mode 100644 index d41d05aa8e..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockSlideshow.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageBlockSlideshow - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockSlideshow

- -

Slideshow

-

- -
-
pageBlockSlideshow#31f9590 items:Vector<PageBlock> caption:PageCaption = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
itemsVector<PageBlock>Slideshow items
captionPageCaptionCaption
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockSubheader.html b/data/corefork.telegram.org/constructor/pageBlockSubheader.html deleted file mode 100644 index d70da378ca..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockSubheader.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockSubheader - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockSubheader

- -

Subheader

-

- -
-
pageBlockSubheader#f12bb6e1 text:RichText = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextSubheader
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockSubtitle.html b/data/corefork.telegram.org/constructor/pageBlockSubtitle.html deleted file mode 100644 index 1703f14668..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockSubtitle.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockSubtitle - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockSubtitle

- -

Subtitle

-

- -
-
pageBlockSubtitle#8ffa9a1f text:RichText = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockTable.html b/data/corefork.telegram.org/constructor/pageBlockTable.html deleted file mode 100644 index 993ab02c01..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockTable.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - pageBlockTable - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockTable

- -

Table

-

- -
-
pageBlockTable#bf4dea82 flags:# bordered:flags.0?true striped:flags.1?true title:RichText rows:Vector<PageTableRow> = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
borderedflags.0?trueDoes the table have a visible border?
stripedflags.1?trueIs the table striped?
titleRichTextTitle
rowsVector<PageTableRow>Table rows
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockTitle.html b/data/corefork.telegram.org/constructor/pageBlockTitle.html deleted file mode 100644 index 2cbb2947ac..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockTitle.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageBlockTitle - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockTitle

- -

Title

-

- -
-
pageBlockTitle#70abc3fd text:RichText = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextTitle
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockUnsupported.html b/data/corefork.telegram.org/constructor/pageBlockUnsupported.html deleted file mode 100644 index 425888b6fb..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockUnsupported.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - pageBlockUnsupported - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockUnsupported

- -

Unsupported IV element

-

- -
-
pageBlockUnsupported#13567e8a = PageBlock;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageBlockVideo.html b/data/corefork.telegram.org/constructor/pageBlockVideo.html deleted file mode 100644 index 76866e4114..0000000000 --- a/data/corefork.telegram.org/constructor/pageBlockVideo.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - pageBlockVideo - - - - - - - - - - - - - -
- -
-
-
- -

pageBlockVideo

- -

Video

-

- -
-
pageBlockVideo#7c8fe7b6 flags:# autoplay:flags.0?true loop:flags.1?true video_id:long caption:PageCaption = PageBlock;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
autoplayflags.0?trueWhether the video is set to autoplay
loopflags.1?trueWhether the video is set to loop
video_idlongVideo ID
captionPageCaptionCaption
-

Type

-

PageBlock

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageCaption.html b/data/corefork.telegram.org/constructor/pageCaption.html deleted file mode 100644 index 27b69f5d73..0000000000 --- a/data/corefork.telegram.org/constructor/pageCaption.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageCaption - - - - - - - - - - - - - -
- -
-
-
- -

pageCaption

- -

Page caption

-

- -
-
pageCaption#6f747657 text:RichText credit:RichText = PageCaption;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextCaption
creditRichTextCredits
-

Type

-

PageCaption

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageListItemBlocks.html b/data/corefork.telegram.org/constructor/pageListItemBlocks.html deleted file mode 100644 index e41ea54f61..0000000000 --- a/data/corefork.telegram.org/constructor/pageListItemBlocks.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageListItemBlocks - - - - - - - - - - - - - -
- -
-
-
- -

pageListItemBlocks

- -

List item

-

- -
-
pageListItemBlocks#25e073fc blocks:Vector<PageBlock> = PageListItem;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
blocksVector<PageBlock>Blocks
-

Type

-

PageListItem

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageListItemText.html b/data/corefork.telegram.org/constructor/pageListItemText.html deleted file mode 100644 index 13b18fb180..0000000000 --- a/data/corefork.telegram.org/constructor/pageListItemText.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageListItemText - - - - - - - - - - - - - -
- -
-
-
- -

pageListItemText

- -

List item

-

- -
-
pageListItemText#b92fb6cd text:RichText = PageListItem;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
-

Type

-

PageListItem

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageListOrderedItemBlocks.html b/data/corefork.telegram.org/constructor/pageListOrderedItemBlocks.html deleted file mode 100644 index e406d5e978..0000000000 --- a/data/corefork.telegram.org/constructor/pageListOrderedItemBlocks.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageListOrderedItemBlocks - - - - - - - - - - - - - -
- -
-
-
- -

pageListOrderedItemBlocks

- -

Ordered list of IV blocks

-

- -
-
pageListOrderedItemBlocks#98dd8936 num:string blocks:Vector<PageBlock> = PageListOrderedItem;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
numstringNumber of element within ordered list
blocksVector<PageBlock>Item contents
-

Type

-

PageListOrderedItem

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageListOrderedItemText.html b/data/corefork.telegram.org/constructor/pageListOrderedItemText.html deleted file mode 100644 index 8b80ea1684..0000000000 --- a/data/corefork.telegram.org/constructor/pageListOrderedItemText.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - pageListOrderedItemText - - - - - - - - - - - - - -
- -
-
-
- -

pageListOrderedItemText

- -

Ordered list of text items

-

- -
-
pageListOrderedItemText#5e068047 num:string text:RichText = PageListOrderedItem;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
numstringNumber of element within ordered list
textRichTextText
-

Type

-

PageListOrderedItem

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageRelatedArticle.html b/data/corefork.telegram.org/constructor/pageRelatedArticle.html deleted file mode 100644 index 9249dbd9fb..0000000000 --- a/data/corefork.telegram.org/constructor/pageRelatedArticle.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - pageRelatedArticle - - - - - - - - - - - - - -
- -
-
-
- -

pageRelatedArticle

- -

Related article

-

- -
-
pageRelatedArticle#b390dc08 flags:# url:string webpage_id:long title:flags.0?string description:flags.1?string photo_id:flags.2?long author:flags.3?string published_date:flags.4?int = PageRelatedArticle;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
urlstringURL of article
webpage_idlongWebpage ID of generated IV preview
titleflags.0?stringTitle
descriptionflags.1?stringDescription
photo_idflags.2?longID of preview photo
authorflags.3?stringAuthor name
published_dateflags.4?intDate of pubblication
-

Type

-

PageRelatedArticle

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageTableCell.html b/data/corefork.telegram.org/constructor/pageTableCell.html deleted file mode 100644 index 43f3ec6665..0000000000 --- a/data/corefork.telegram.org/constructor/pageTableCell.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - pageTableCell - - - - - - - - - - - - - -
- -
-
-
- -

pageTableCell

- -

Table cell

-

- -
-
pageTableCell#34566b6a flags:# header:flags.0?true align_center:flags.3?true align_right:flags.4?true valign_middle:flags.5?true valign_bottom:flags.6?true text:flags.7?RichText colspan:flags.1?int rowspan:flags.2?int = PageTableCell;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
headerflags.0?trueIs this element part of the column header
align_centerflags.3?trueHorizontally centered block
align_rightflags.4?trueRight-aligned block
valign_middleflags.5?trueVertically centered block
valign_bottomflags.6?trueBlock vertically-alligned to the bottom
textflags.7?RichTextContent
colspanflags.1?intFor how many columns should this cell extend
rowspanflags.2?intFor how many rows should this cell extend
-

Type

-

PageTableCell

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pageTableRow.html b/data/corefork.telegram.org/constructor/pageTableRow.html deleted file mode 100644 index 4b355b868f..0000000000 --- a/data/corefork.telegram.org/constructor/pageTableRow.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - pageTableRow - - - - - - - - - - - - - -
- -
-
-
- -

pageTableRow

- -

Table row

-

- -
-
pageTableRow#e0c0c5e5 cells:Vector<PageTableCell> = PageTableRow;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
cellsVector<PageTableCell>Table cells
-

Type

-

PageTableRow

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow.html b/data/corefork.telegram.org/constructor/passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow.html deleted file mode 100644 index 1566989611..0000000000 --- a/data/corefork.telegram.org/constructor/passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow - - - - - - - - - - - - - -
- -
-
-
- -

passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow

- -

This key derivation algorithm defines that SRP 2FA login must be used

-

- -
-
passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow#3a912d4a salt1:bytes salt2:bytes g:int p:bytes = PasswordKdfAlgo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
salt1bytesOne of two salts used by the derivation function (see SRP 2FA login)
salt2bytesOne of two salts used by the derivation function (see SRP 2FA login)
gintBase (see SRP 2FA login)
pbytes2048-bit modulus (see SRP 2FA login)
-

Type

-

PasswordKdfAlgo

-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/passwordKdfAlgoUnknown.html b/data/corefork.telegram.org/constructor/passwordKdfAlgoUnknown.html deleted file mode 100644 index a7ec6d2712..0000000000 --- a/data/corefork.telegram.org/constructor/passwordKdfAlgoUnknown.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - passwordKdfAlgoUnknown - - - - - - - - - - - - - -
- -
-
-
- -

passwordKdfAlgoUnknown

- -

Unknown KDF (most likely, the client is outdated and does not support the specified KDF algorithm)

-

- -
-
passwordKdfAlgoUnknown#d45ab096 = PasswordKdfAlgo;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PasswordKdfAlgo

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/paymentCharge.html b/data/corefork.telegram.org/constructor/paymentCharge.html deleted file mode 100644 index 64c0b6057a..0000000000 --- a/data/corefork.telegram.org/constructor/paymentCharge.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - paymentCharge - - - - - - - - - - - - - -
- -
-
-
- -

paymentCharge

- -

Payment identifier

-

- -
-
paymentCharge#ea02c27e id:string provider_charge_id:string = PaymentCharge;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idstringTelegram payment identifier
provider_charge_idstringProvider payment identifier
-

Type

-

PaymentCharge

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/paymentRequestedInfo.html b/data/corefork.telegram.org/constructor/paymentRequestedInfo.html deleted file mode 100644 index 5c98faa7b3..0000000000 --- a/data/corefork.telegram.org/constructor/paymentRequestedInfo.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - paymentRequestedInfo - - - - - - - - - - - - - -
- -
-
-
- -

paymentRequestedInfo

- -

Order info provided by the user

-

- -
-
paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
nameflags.0?stringUser's full name
phoneflags.1?stringUser's phone number
emailflags.2?stringUser's email address
shipping_addressflags.3?PostAddressUser's shipping address
-

Type

-

PaymentRequestedInfo

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/payments.ValidatedRequestedInfo b/data/corefork.telegram.org/constructor/payments.ValidatedRequestedInfo deleted file mode 100644 index 336c06a7c2..0000000000 --- a/data/corefork.telegram.org/constructor/payments.ValidatedRequestedInfo +++ /dev/null @@ -1,145 +0,0 @@ - - - - - payments.ValidatedRequestedInfo - - - - - - - - - - - - - -
- -
-
-
- -

payments.ValidatedRequestedInfo

- -

Validated user-provided info

-

{schema}

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idflags.0?stringID
shipping_optionsflags.1?Vector<ShippingOption>Shipping options
-

Type

-

payments.ValidatedRequestedInfo

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/payments.bankCardData b/data/corefork.telegram.org/constructor/payments.bankCardData deleted file mode 100644 index dc91c2fcda..0000000000 --- a/data/corefork.telegram.org/constructor/payments.bankCardData +++ /dev/null @@ -1,152 +0,0 @@ - - - - - payments.bankCardData - - - - - - - - - - - - - -
- -
-
-
- -

payments.bankCardData

- -

Credit card info, provided by the card's bank(s)

-

- -
-
payments.bankCardData#3e24e573 title:string open_urls:Vector<BankCardOpenUrl> = payments.BankCardData;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
titlestringCredit card title
open_urlsVector<BankCardOpenUrl>Info URL(s) provided by the card's bank(s)
-

Type

-

payments.BankCardData

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/payments.paymentReceipt b/data/corefork.telegram.org/constructor/payments.paymentReceipt deleted file mode 100644 index 0e0d2f829e..0000000000 --- a/data/corefork.telegram.org/constructor/payments.paymentReceipt +++ /dev/null @@ -1,219 +0,0 @@ - - - - - payments.paymentReceipt - - - - - - - - - - - - - -
- -
-
-
- -

payments.paymentReceipt

- -

Receipt

-

- -
-
payments.paymentReceipt#70c4fe03 flags:# date:int bot_id:long provider_id:long title:string description:string photo:flags.2?WebDocument invoice:Invoice info:flags.0?PaymentRequestedInfo shipping:flags.1?ShippingOption tip_amount:flags.3?long currency:string total_amount:long credentials_title:string users:Vector<User> = payments.PaymentReceipt;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
dateintDate of generation
bot_idlongBot ID
provider_idlongProvider ID
titlestringTitle
descriptionstringDescription
photoflags.2?WebDocumentPhoto
invoiceInvoiceInvoice
infoflags.0?PaymentRequestedInfoInfo
shippingflags.1?ShippingOptionSelected shipping option
tip_amountflags.3?longTipped amount
currencystringThree-letter ISO 4217 currency code
total_amountlongTotal amount in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
credentials_titlestringPayment credential name
usersVector<User>Users
-

Type

-

payments.PaymentReceipt

-

Related pages

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/payments.paymentResult b/data/corefork.telegram.org/constructor/payments.paymentResult deleted file mode 100644 index 3a0a424570..0000000000 --- a/data/corefork.telegram.org/constructor/payments.paymentResult +++ /dev/null @@ -1,147 +0,0 @@ - - - - - payments.paymentResult - - - - - - - - - - - - - -
- -
-
-
- -

payments.paymentResult

- -

Payment result

-

- -
-
payments.paymentResult#4e5f810d updates:Updates = payments.PaymentResult;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
updatesUpdatesInfo about the payment
-

Type

-

payments.PaymentResult

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/payments.paymentVerificationNeeded b/data/corefork.telegram.org/constructor/payments.paymentVerificationNeeded deleted file mode 100644 index f2484250ec..0000000000 --- a/data/corefork.telegram.org/constructor/payments.paymentVerificationNeeded +++ /dev/null @@ -1,147 +0,0 @@ - - - - - payments.paymentVerificationNeeded - - - - - - - - - - - - - -
- -
-
-
- -

payments.paymentVerificationNeeded

- -

Payment was not successful, additional verification is needed

-

- -
-
payments.paymentVerificationNeeded#d8411139 url:string = payments.PaymentResult;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
urlstringURL for additional payment credentials verification
-

Type

-

payments.PaymentResult

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/payments.savedInfo b/data/corefork.telegram.org/constructor/payments.savedInfo deleted file mode 100644 index d7114a303e..0000000000 --- a/data/corefork.telegram.org/constructor/payments.savedInfo +++ /dev/null @@ -1,157 +0,0 @@ - - - - - payments.savedInfo - - - - - - - - - - - - - -
- -
-
-
- -

payments.savedInfo

- -

Saved server-side order information

-

- -
-
payments.savedInfo#fb8fe43c flags:# has_saved_credentials:flags.1?true saved_info:flags.0?PaymentRequestedInfo = payments.SavedInfo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
has_saved_credentialsflags.1?trueWhether the user has some saved payment credentials
saved_infoflags.0?PaymentRequestedInfoSaved server-side order information
-

Type

-

payments.SavedInfo

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/peerBlocked.html b/data/corefork.telegram.org/constructor/peerBlocked.html deleted file mode 100644 index b651ad965a..0000000000 --- a/data/corefork.telegram.org/constructor/peerBlocked.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - peerBlocked - - - - - - - - - - - - - -
- -
-
-
- -

peerBlocked

- -

Information about a blocked peer

-

- -
-
peerBlocked#e8fd8014 peer_id:Peer date:int = PeerBlocked;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peer_idPeerPeer ID
dateintWhen was the peer blocked
-

Type

-

PeerBlocked

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/peerChannel.html b/data/corefork.telegram.org/constructor/peerChannel.html deleted file mode 100644 index 3f7fb607ca..0000000000 --- a/data/corefork.telegram.org/constructor/peerChannel.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - peerChannel - - - - - - - - - - - - - -
- -
-
-
- -

peerChannel

- -

Channel/supergroup

-

- -
-
peerChannel#a2a5371e channel_id:long = Peer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
channel_idlongChannel ID
-

Type

-

Peer

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/peerChat.html b/data/corefork.telegram.org/constructor/peerChat.html deleted file mode 100644 index db09775785..0000000000 --- a/data/corefork.telegram.org/constructor/peerChat.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - peerChat - - - - - - - - - - - - - -
- -
-
-
- -

peerChat

- -

Group.

-

- -
-
peerChat#36c6019a chat_id:long = Peer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongGroup identifier
-

Type

-

Peer

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/peerLocated.html b/data/corefork.telegram.org/constructor/peerLocated.html deleted file mode 100644 index 7662f27e85..0000000000 --- a/data/corefork.telegram.org/constructor/peerLocated.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - peerLocated - - - - - - - - - - - - - -
- -
-
-
- -

peerLocated

- -

Peer geolocated nearby

-

- -
-
peerLocated#ca461b5d peer:Peer expires:int distance:int = PeerLocated;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerPeer
expiresintValidity period of current data
distanceintDistance from the peer in meters
-

Type

-

PeerLocated

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/peerNotifySettings.html b/data/corefork.telegram.org/constructor/peerNotifySettings.html deleted file mode 100644 index 0f493a6e9c..0000000000 --- a/data/corefork.telegram.org/constructor/peerNotifySettings.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - peerNotifySettings - - - - - - - - - - - - - -
- -
-
-
- -

peerNotifySettings

- -

Notification settings.

-

- -
-
peerNotifySettings#af509d20 flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = PeerNotifySettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
show_previewsflags.0?BoolDisplay text in notifications
silentflags.1?BoolMute peer?
mute_untilflags.2?intMute all notifications until this date
soundflags.3?stringAudio file name for notifications
-

Type

-

PeerNotifySettings

-

Event flags (events_mask)

- - - - - - - - - - - - - -
0x00000001Profile photo update notification
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/peerSelfLocated.html b/data/corefork.telegram.org/constructor/peerSelfLocated.html deleted file mode 100644 index ea0b0b7e47..0000000000 --- a/data/corefork.telegram.org/constructor/peerSelfLocated.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - peerSelfLocated - - - - - - - - - - - - - -
- -
-
-
- -

peerSelfLocated

- -

Current peer

-

- -
-
peerSelfLocated#f8ec284b expires:int = PeerLocated;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
expiresintExpiry of geolocation info for current peer
-

Type

-

PeerLocated

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/peerSettings.html b/data/corefork.telegram.org/constructor/peerSettings.html deleted file mode 100644 index 8aefb75aa2..0000000000 --- a/data/corefork.telegram.org/constructor/peerSettings.html +++ /dev/null @@ -1,197 +0,0 @@ - - - - - peerSettings - - - - - - - - - - - - - -
- -
-
-
- -

peerSettings

- -

Peer settings

-

- -
-
peerSettings#733f2961 flags:# report_spam:flags.0?true add_contact:flags.1?true block_contact:flags.2?true share_contact:flags.3?true need_contacts_exception:flags.4?true report_geo:flags.5?true autoarchived:flags.7?true invite_members:flags.8?true geo_distance:flags.6?int = PeerSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
report_spamflags.0?trueWhether we can still report the user for spam
add_contactflags.1?trueWhether we can add the user as contact
block_contactflags.2?trueWhether we can block the user
share_contactflags.3?trueWhether we can share the user's contact
need_contacts_exceptionflags.4?trueWhether a special exception for contacts is needed
report_geoflags.5?trueWhether we can report a geogroup is irrelevant for this location
autoarchivedflags.7?trueWhether this peer was automatically archived according to privacy settings
invite_membersflags.8?trueWhether we can invite members to a group or channel
geo_distanceflags.6?intDistance in meters between us and this peer
-

Type

-

PeerSettings

-

Related pages

-

globalPrivacySettings

-

Global privacy settings

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/peerUser.html b/data/corefork.telegram.org/constructor/peerUser.html deleted file mode 100644 index 2949ab048b..0000000000 --- a/data/corefork.telegram.org/constructor/peerUser.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - peerUser - - - - - - - - - - - - - -
- -
-
-
- -

peerUser

- -

Chat partner

-

- -
-
peerUser#59511722 user_id:long = Peer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser identifier
-

Type

-

Peer

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/phone.joinAsPeers b/data/corefork.telegram.org/constructor/phone.joinAsPeers deleted file mode 100644 index 5be76f3c0d..0000000000 --- a/data/corefork.telegram.org/constructor/phone.joinAsPeers +++ /dev/null @@ -1,157 +0,0 @@ - - - - - phone.joinAsPeers - - - - - - - - - - - - - -
- -
-
-
- -

phone.joinAsPeers

- -

A list of peers that can be used to join a group call, presenting yourself as a specific user/channel.

-

- -
-
phone.joinAsPeers#afe5623f peers:Vector<Peer> chats:Vector<Chat> users:Vector<User> = phone.JoinAsPeers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peersVector<Peer>Peers
chatsVector<Chat>Chats mentioned in the peers vector
usersVector<User>Users mentioned in the peers vector
-

Type

-

phone.JoinAsPeers

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/phone.phoneCall b/data/corefork.telegram.org/constructor/phone.phoneCall deleted file mode 100644 index b1a50fa604..0000000000 --- a/data/corefork.telegram.org/constructor/phone.phoneCall +++ /dev/null @@ -1,152 +0,0 @@ - - - - - phone.phoneCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.phoneCall

- -

A VoIP phone call

-

- -
-
phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_callPhoneCallThe VoIP phone call
usersVector<User>VoIP phone call participants
-

Type

-

phone.PhoneCall

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/phoneCall.html b/data/corefork.telegram.org/constructor/phoneCall.html deleted file mode 100644 index 38e480d525..0000000000 --- a/data/corefork.telegram.org/constructor/phoneCall.html +++ /dev/null @@ -1,209 +0,0 @@ - - - - - phoneCall - - - - - - - - - - - - - -
- -
-
-
- -

phoneCall

- -

Phone call

-

- -
-
phoneCall#967f7c67 flags:# p2p_allowed:flags.5?true video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long protocol:PhoneCallProtocol connections:Vector<PhoneConnection> start_date:int = PhoneCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
p2p_allowedflags.5?trueWhether P2P connection to the other peer is allowed
videoflags.6?trueWhether this is a video call
idlongCall ID
access_hashlongAccess hash
dateintDate of creation of the call
admin_idlongUser ID of the creator of the call
participant_idlongUser ID of the other participant in the call
g_a_or_bbytesParameter for key exchange
key_fingerprintlongKey fingerprint
protocolPhoneCallProtocolCall protocol info to be passed to libtgvoip
connectionsVector<PhoneConnection>List of endpoints the user can connect to to exchange call data
start_dateintWhen was the call actually started
-

Type

-

PhoneCall

-

Related pages

-

End-to-End Encrypted Voice Calls

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/phoneCallDiscardReasonBusy.html b/data/corefork.telegram.org/constructor/phoneCallDiscardReasonBusy.html deleted file mode 100644 index a4b592ece4..0000000000 --- a/data/corefork.telegram.org/constructor/phoneCallDiscardReasonBusy.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - phoneCallDiscardReasonBusy - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallDiscardReasonBusy

- -

The phone call was discared because the user is busy in another call

-

- -
-
phoneCallDiscardReasonBusy#faf7e8c9 = PhoneCallDiscardReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PhoneCallDiscardReason

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/phoneCallDiscardReasonDisconnect.html b/data/corefork.telegram.org/constructor/phoneCallDiscardReasonDisconnect.html deleted file mode 100644 index fc5fcb3112..0000000000 --- a/data/corefork.telegram.org/constructor/phoneCallDiscardReasonDisconnect.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - phoneCallDiscardReasonDisconnect - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallDiscardReasonDisconnect

- -

The phone call was disconnected

-

- -
-
phoneCallDiscardReasonDisconnect#e095c1a0 = PhoneCallDiscardReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PhoneCallDiscardReason

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/phoneCallDiscardReasonHangup.html b/data/corefork.telegram.org/constructor/phoneCallDiscardReasonHangup.html deleted file mode 100644 index b6b35dbf01..0000000000 --- a/data/corefork.telegram.org/constructor/phoneCallDiscardReasonHangup.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - phoneCallDiscardReasonHangup - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallDiscardReasonHangup

- -

The phone call was ended normally

-

- -
-
phoneCallDiscardReasonHangup#57adc690 = PhoneCallDiscardReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PhoneCallDiscardReason

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/phoneCallDiscardReasonMissed.html b/data/corefork.telegram.org/constructor/phoneCallDiscardReasonMissed.html deleted file mode 100644 index 19f7140d8b..0000000000 --- a/data/corefork.telegram.org/constructor/phoneCallDiscardReasonMissed.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - phoneCallDiscardReasonMissed - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallDiscardReasonMissed

- -

The phone call was missed

-

- -
-
phoneCallDiscardReasonMissed#85e42301 = PhoneCallDiscardReason;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PhoneCallDiscardReason

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/phoneCallDiscarded.html b/data/corefork.telegram.org/constructor/phoneCallDiscarded.html deleted file mode 100644 index 34919b1f3b..0000000000 --- a/data/corefork.telegram.org/constructor/phoneCallDiscarded.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - phoneCallDiscarded - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallDiscarded

- -

Indicates a discarded phone call

-

- -
-
phoneCallDiscarded#50ca4de1 flags:# need_rating:flags.2?true need_debug:flags.3?true video:flags.6?true id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = PhoneCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
need_ratingflags.2?trueWhether the server required the user to rate the call
need_debugflags.3?trueWhether the server required the client to send the libtgvoip call debug data
videoflags.6?trueWhether the call was a video call
idlongCall ID
reasonflags.0?PhoneCallDiscardReasonWhy was the phone call discarded
durationflags.1?intDuration of the phone call in seconds
-

Type

-

PhoneCall

-

Related pages

-

phone.setCallRating

-

Rate a call

-

phone.saveCallDebug

-

Send phone call debug data to server

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/phoneCallEmpty.html b/data/corefork.telegram.org/constructor/phoneCallEmpty.html deleted file mode 100644 index eff5589451..0000000000 --- a/data/corefork.telegram.org/constructor/phoneCallEmpty.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - phoneCallEmpty - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallEmpty

- -

Empty constructor

-

- -
-
phoneCallEmpty#5366c915 id:long = PhoneCall;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idlongCall ID
-

Type

-

PhoneCall

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/phoneCallProtocol.html b/data/corefork.telegram.org/constructor/phoneCallProtocol.html deleted file mode 100644 index 2a4d2a9ac5..0000000000 --- a/data/corefork.telegram.org/constructor/phoneCallProtocol.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - phoneCallProtocol - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallProtocol

- -

Protocol info for libtgvoip

-

- -
-
phoneCallProtocol#fc878fc8 flags:# udp_p2p:flags.0?true udp_reflector:flags.1?true min_layer:int max_layer:int library_versions:Vector<string> = PhoneCallProtocol;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
udp_p2pflags.0?trueWhether to allow P2P connection to the other participant
udp_reflectorflags.1?trueWhether to allow connection to the other participants through the reflector servers
min_layerintMinimum layer for remote libtgvoip
max_layerintMaximum layer for remote libtgvoip
library_versionsVector<string>When using phone.requestCall and phone.acceptCall, specify all library versions supported by the client.
The server will merge and choose the best library version supported by both peers, returning only the best value in the result of the callee's phone.acceptCall and in the phoneCallAccepted update received by the caller.
-

Type

-

PhoneCallProtocol

-

Related pages

-

phone.requestCall

-

Start a telegram phone call

-

phone.acceptCall

-

Accept incoming call

-

phoneCallAccepted

-

An accepted phone call

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/phoneCallRequested.html b/data/corefork.telegram.org/constructor/phoneCallRequested.html deleted file mode 100644 index 33f1b7bc6a..0000000000 --- a/data/corefork.telegram.org/constructor/phoneCallRequested.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - phoneCallRequested - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallRequested

- -

Requested phone call

-

- -
-
phoneCallRequested#14b0ed0c flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_hash:bytes protocol:PhoneCallProtocol = PhoneCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.6?trueWhether this is a video call
idlongPhone call ID
access_hashlongAccess hash
dateintWhen was the phone call created
admin_idlongID of the creator of the phone call
participant_idlongID of the other participant of the phone call
g_a_hashbytesParameter for key exchange
protocolPhoneCallProtocolCall protocol info to be passed to libtgvoip
-

Type

-

PhoneCall

-

Related pages

-

End-to-End Encrypted Voice Calls

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/phoneCallWaiting.html b/data/corefork.telegram.org/constructor/phoneCallWaiting.html deleted file mode 100644 index f9e98e2186..0000000000 --- a/data/corefork.telegram.org/constructor/phoneCallWaiting.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - phoneCallWaiting - - - - - - - - - - - - - -
- -
-
-
- -

phoneCallWaiting

- -

Incoming phone call

-

- -
-
phoneCallWaiting#c5226f17 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long protocol:PhoneCallProtocol receive_date:flags.0?int = PhoneCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.6?trueIs this a video call
idlongCall ID
access_hashlongAccess hash
dateintDate
admin_idlongAdmin ID
participant_idlongParticipant ID
protocolPhoneCallProtocolPhone call protocol info
receive_dateflags.0?intWhen was the phone call received
-

Type

-

PhoneCall

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/phoneConnection.html b/data/corefork.telegram.org/constructor/phoneConnection.html deleted file mode 100644 index eb6b41d7b7..0000000000 --- a/data/corefork.telegram.org/constructor/phoneConnection.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - phoneConnection - - - - - - - - - - - - - -
- -
-
-
- -

phoneConnection

- -

Identifies an endpoint that can be used to connect to the other user in a phone call

-

- -
-
phoneConnection#9d4c17c0 id:long ip:string ipv6:string port:int peer_tag:bytes = PhoneConnection;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongEndpoint ID
ipstringIP address of endpoint
ipv6stringIPv6 address of endpoint
portintPort ID
peer_tagbytesOur peer tag
-

Type

-

PhoneConnection

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/phoneConnectionWebrtc.html b/data/corefork.telegram.org/constructor/phoneConnectionWebrtc.html deleted file mode 100644 index 9a37308a68..0000000000 --- a/data/corefork.telegram.org/constructor/phoneConnectionWebrtc.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - phoneConnectionWebrtc - - - - - - - - - - - - - -
- -
-
-
- -

phoneConnectionWebrtc

- -

WebRTC connection parameters

-

- -
-
phoneConnectionWebrtc#635fe375 flags:# turn:flags.0?true stun:flags.1?true id:long ip:string ipv6:string port:int username:string password:string = PhoneConnection;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
turnflags.0?trueWhether this is a TURN endpoint
stunflags.1?trueWhether this is a STUN endpoint
idlongEndpoint ID
ipstringIP address
ipv6stringIPv6 address
portintPort
usernamestringUsername
passwordstringPassword
-

Type

-

PhoneConnection

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/photo.html b/data/corefork.telegram.org/constructor/photo.html deleted file mode 100644 index b84bea84af..0000000000 --- a/data/corefork.telegram.org/constructor/photo.html +++ /dev/null @@ -1,192 +0,0 @@ - - - - - photo - - - - - - - - - - - - - -
- -
-
-
- -

photo

- -

Photo

-

- -
-
photo#fb197a65 flags:# has_stickers:flags.0?true id:long access_hash:long file_reference:bytes date:int sizes:Vector<PhotoSize> video_sizes:flags.1?Vector<VideoSize> dc_id:int = Photo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
has_stickersflags.0?trueWhether the photo has mask stickers attached to it
idlongID
access_hashlongAccess hash
file_referencebytesfile reference
dateintDate of upload
sizesVector<PhotoSize>Available sizes for download
video_sizesflags.1?Vector<VideoSize>For animated profiles, the MPEG4 videos
dc_idintDC ID to use for download
-

Type

-

Photo

-

Related pages

-

File references

-

How to handle file references.

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/photoCachedSize.html b/data/corefork.telegram.org/constructor/photoCachedSize.html deleted file mode 100644 index 436d79349e..0000000000 --- a/data/corefork.telegram.org/constructor/photoCachedSize.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - photoCachedSize - - - - - - - - - - - - - -
- -
-
-
- -

photoCachedSize

- -

Description of an image and its content.

-

- -
-
photoCachedSize#21e1ad6 type:string w:int h:int bytes:bytes = PhotoSize;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typestringThumbnail type
wintImage width
hintImage height
bytesbytesBinary data, file content
-

Type

-

PhotoSize

-

Thumbnail type and its sizes

-

See here.

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/photoEmpty.html b/data/corefork.telegram.org/constructor/photoEmpty.html deleted file mode 100644 index d5df59c09b..0000000000 --- a/data/corefork.telegram.org/constructor/photoEmpty.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - photoEmpty - - - - - - - - - - - - - -
- -
-
-
- -

photoEmpty

- -

Empty constructor, non-existent photo

-

- -
-
photoEmpty#2331b22d id:long = Photo;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idlongPhoto identifier
-

Type

-

Photo

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/photoPathSize.html b/data/corefork.telegram.org/constructor/photoPathSize.html deleted file mode 100644 index 73f9d9cc68..0000000000 --- a/data/corefork.telegram.org/constructor/photoPathSize.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - photoPathSize - - - - - - - - - - - - - -
- -
-
-
- -

photoPathSize

- -

Messages with animated stickers can have a compressed svg (< 300 bytes) to show the outline of the sticker before fetching the actual lottie animation.

-

- -
-
photoPathSize#d8214d41 type:string bytes:bytes = PhotoSize;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typestringAlways j
bytesbytesCompressed SVG path payload, see here for decompression instructions
-

Type

-

PhotoSize

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/photoSize.html b/data/corefork.telegram.org/constructor/photoSize.html deleted file mode 100644 index 18bf11aba2..0000000000 --- a/data/corefork.telegram.org/constructor/photoSize.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - photoSize - - - - - - - - - - - - - -
- -
-
-
- -

photoSize

- -

Image description.

-

- -
-
photoSize#75c78e60 type:string w:int h:int size:int = PhotoSize;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typestringThumbnail type
wintImage width
hintImage height
sizeintFile size
-

Type

-

PhotoSize

-

Thumbnail type and its sizes

-

See here.

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/photoSizeEmpty.html b/data/corefork.telegram.org/constructor/photoSizeEmpty.html deleted file mode 100644 index f8102cb86a..0000000000 --- a/data/corefork.telegram.org/constructor/photoSizeEmpty.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - photoSizeEmpty - - - - - - - - - - - - - -
- -
-
-
- -

photoSizeEmpty

- -

Empty constructor. Image with this thumbnail is unavailable.

-

- -
-
photoSizeEmpty#e17e23c type:string = PhotoSize;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
typestringThumbnail type (see. photoSize)
-

Type

-

PhotoSize

-

Related pages

-

photoSize

-

Image description.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/photoStrippedSize.html b/data/corefork.telegram.org/constructor/photoStrippedSize.html deleted file mode 100644 index 5c40402e20..0000000000 --- a/data/corefork.telegram.org/constructor/photoStrippedSize.html +++ /dev/null @@ -1,159 +0,0 @@ - - - - - photoStrippedSize - - - - - - - - - - - - - -
- -
-
-
- -

photoStrippedSize

- -

A low-resolution compressed JPG payload

-

- -
-
photoStrippedSize#e0b0bc2e type:string bytes:bytes = PhotoSize;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typestringThumbnail type
bytesbytesThumbnail data, see here for more info on decompression »
-

Type

-

PhotoSize

-

Thumbnail type and its sizes

-

See the photoSize constructor.

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

-

photoSize

-

Image description.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/photos.photo b/data/corefork.telegram.org/constructor/photos.photo deleted file mode 100644 index 0b88304c96..0000000000 --- a/data/corefork.telegram.org/constructor/photos.photo +++ /dev/null @@ -1,152 +0,0 @@ - - - - - photos.photo - - - - - - - - - - - - - -
- -
-
-
- -

photos.photo

- -

Photo with auxiliary data.

-

- -
-
photos.photo#20212ca8 photo:Photo users:Vector<User> = photos.Photo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
photoPhotoPhoto
usersVector<User>Users
-

Type

-

photos.Photo

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/photos.photos b/data/corefork.telegram.org/constructor/photos.photos deleted file mode 100644 index 585f5427b0..0000000000 --- a/data/corefork.telegram.org/constructor/photos.photos +++ /dev/null @@ -1,152 +0,0 @@ - - - - - photos.photos - - - - - - - - - - - - - -
- -
-
-
- -

photos.photos

- -

Full list of photos with auxiliary data.

-

- -
-
photos.photos#8dca6aa5 photos:Vector<Photo> users:Vector<User> = photos.Photos;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
photosVector<Photo>List of photos
usersVector<User>List of mentioned users
-

Type

-

photos.Photos

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/photos.photosSlice b/data/corefork.telegram.org/constructor/photos.photosSlice deleted file mode 100644 index 2f6b3552ab..0000000000 --- a/data/corefork.telegram.org/constructor/photos.photosSlice +++ /dev/null @@ -1,157 +0,0 @@ - - - - - photos.photosSlice - - - - - - - - - - - - - -
- -
-
-
- -

photos.photosSlice

- -

Incomplete list of photos with auxiliary data.

-

- -
-
photos.photosSlice#15051f54 count:int photos:Vector<Photo> users:Vector<User> = photos.Photos;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
countintTotal number of photos
photosVector<Photo>List of photos
usersVector<User>List of mentioned users
-

Type

-

photos.Photos

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/poll.html b/data/corefork.telegram.org/constructor/poll.html deleted file mode 100644 index 1e5e25a94c..0000000000 --- a/data/corefork.telegram.org/constructor/poll.html +++ /dev/null @@ -1,195 +0,0 @@ - - - - - poll - - - - - - - - - - - - - -
- -
-
-
- -

poll

- -

Poll

-

- -
-
poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongID of the poll
flags#Flags, see TL conditional fields
closedflags.0?trueWhether the poll is closed and doesn't accept any more answers
public_votersflags.1?trueWhether cast votes are publicly visible to all users (non-anonymous poll)
multiple_choiceflags.2?trueWhether multiple options can be chosen as answer
quizflags.3?trueWhether this is a quiz (with wrong and correct answers, results shown in the return type)
questionstringThe question of the poll
answersVector<PollAnswer>The possible answers, vote using messages.sendVote.
close_periodflags.4?intAmount of time in seconds the poll will be active after creation, 5-600. Can't be used together with close_date.
close_dateflags.5?intPoint in time (Unix timestamp) when the poll will be automatically closed. Must be at least 5 and no more than 600 seconds in the future; can't be used together with close_period.
-

Type

-

Poll

-

Related pages

-

messages.sendVote

-

Vote in a poll

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pollAnswer.html b/data/corefork.telegram.org/constructor/pollAnswer.html deleted file mode 100644 index ba9e996dee..0000000000 --- a/data/corefork.telegram.org/constructor/pollAnswer.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - pollAnswer - - - - - - - - - - - - - -
- -
-
-
- -

pollAnswer

- -

A possible answer of a poll

-

- -
-
pollAnswer#6ca9c2e9 text:string option:bytes = PollAnswer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textstringTextual representation of the answer
optionbytesThe param that has to be passed to messages.sendVote.
-

Type

-

PollAnswer

-

Related pages

-

messages.sendVote

-

Vote in a poll

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pollAnswerVoters.html b/data/corefork.telegram.org/constructor/pollAnswerVoters.html deleted file mode 100644 index 3697908d6d..0000000000 --- a/data/corefork.telegram.org/constructor/pollAnswerVoters.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - pollAnswerVoters - - - - - - - - - - - - - -
- -
-
-
- -

pollAnswerVoters

- -

A poll answer, and how users voted on it

-

- -
-
pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
chosenflags.0?trueWhether we have chosen this answer
correctflags.1?trueFor quizes, whether the option we have chosen is correct
optionbytesThe param that has to be passed to messages.sendVote.
votersintHow many users voted for this option
-

Type

-

PollAnswerVoters

-

Related pages

-

messages.sendVote

-

Vote in a poll

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/pollResults.html b/data/corefork.telegram.org/constructor/pollResults.html deleted file mode 100644 index 864f573504..0000000000 --- a/data/corefork.telegram.org/constructor/pollResults.html +++ /dev/null @@ -1,184 +0,0 @@ - - - - - pollResults - - - - - - - - - - - - - -
- -
-
-
- -

pollResults

- -

Results of poll

-

- -
-
pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
minflags.0?trueSimilar to min objects, used for poll constructors that are the same for all users so they don't have option chosen by the current user (you can use messages.getPollResults to get the full poll results).
resultsflags.1?Vector<PollAnswerVoters>Poll results
total_votersflags.2?intTotal number of people that voted in the poll
recent_votersflags.3?Vector<long>IDs of the last users that recently voted in the poll
solutionflags.4?stringExplanation of quiz solution
solution_entitiesflags.4?Vector<MessageEntity>Message entities for styled text in quiz solution
-

Type

-

PollResults

-

Related pages

-

Min constructors

-

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

-

messages.getPollResults

-

Get poll results

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/popularContact.html b/data/corefork.telegram.org/constructor/popularContact.html deleted file mode 100644 index 47fd738c06..0000000000 --- a/data/corefork.telegram.org/constructor/popularContact.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - popularContact - - - - - - - - - - - - - -
- -
-
-
- -

popularContact

- -

Popular contact

-

- -
-
popularContact#5ce14175 client_id:long importers:int = PopularContact;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
client_idlongContact identifier
importersintHow many people imported this contact
-

Type

-

PopularContact

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/postAddress.html b/data/corefork.telegram.org/constructor/postAddress.html deleted file mode 100644 index 70d1b184e1..0000000000 --- a/data/corefork.telegram.org/constructor/postAddress.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - postAddress - - - - - - - - - - - - - -
- -
-
-
- -

postAddress

- -

Shipping address

-

- -
-
postAddress#1e8caaeb street_line1:string street_line2:string city:string state:string country_iso2:string post_code:string = PostAddress;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
street_line1stringFirst line for the address
street_line2stringSecond line for the address
citystringCity
statestringState, if applicable (empty otherwise)
country_iso2stringISO 3166-1 alpha-2 country code
post_codestringAddress post code
-

Type

-

PostAddress

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/privacyKeyAddedByPhone.html b/data/corefork.telegram.org/constructor/privacyKeyAddedByPhone.html deleted file mode 100644 index d31dedf597..0000000000 --- a/data/corefork.telegram.org/constructor/privacyKeyAddedByPhone.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyAddedByPhone - - - - - - - - - - - - - -
- -
-
-
- -

privacyKeyAddedByPhone

- -

Whether people can add you to their contact list by your phone number

-

- -
-
privacyKeyAddedByPhone#42ffd42b = PrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/privacyKeyChatInvite.html b/data/corefork.telegram.org/constructor/privacyKeyChatInvite.html deleted file mode 100644 index 247e538472..0000000000 --- a/data/corefork.telegram.org/constructor/privacyKeyChatInvite.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

privacyKeyChatInvite

- -

Whether the user can be invited to chats

-

- -
-
privacyKeyChatInvite#500e6dfa = PrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/privacyKeyForwards.html b/data/corefork.telegram.org/constructor/privacyKeyForwards.html deleted file mode 100644 index 9fb7cbe059..0000000000 --- a/data/corefork.telegram.org/constructor/privacyKeyForwards.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyForwards - - - - - - - - - - - - - -
- -
-
-
- -

privacyKeyForwards

- -

Whether messages forwarded from the user will be anonymously forwarded

-

- -
-
privacyKeyForwards#69ec56a3 = PrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/privacyKeyPhoneCall.html b/data/corefork.telegram.org/constructor/privacyKeyPhoneCall.html deleted file mode 100644 index a53b266a6e..0000000000 --- a/data/corefork.telegram.org/constructor/privacyKeyPhoneCall.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyPhoneCall - - - - - - - - - - - - - -
- -
-
-
- -

privacyKeyPhoneCall

- -

Whether the user accepts phone calls

-

- -
-
privacyKeyPhoneCall#3d662b7b = PrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/privacyKeyPhoneNumber.html b/data/corefork.telegram.org/constructor/privacyKeyPhoneNumber.html deleted file mode 100644 index c0f636ba59..0000000000 --- a/data/corefork.telegram.org/constructor/privacyKeyPhoneNumber.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyPhoneNumber - - - - - - - - - - - - - -
- -
-
-
- -

privacyKeyPhoneNumber

- -

Whether the user allows us to see his phone number

-

- -
-
privacyKeyPhoneNumber#d19ae46d = PrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/privacyKeyPhoneP2P.html b/data/corefork.telegram.org/constructor/privacyKeyPhoneP2P.html deleted file mode 100644 index 55b85a87bb..0000000000 --- a/data/corefork.telegram.org/constructor/privacyKeyPhoneP2P.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyPhoneP2P - - - - - - - - - - - - - -
- -
-
-
- -

privacyKeyPhoneP2P

- -

Whether P2P connections in phone calls are allowed

-

- -
-
privacyKeyPhoneP2P#39491cc8 = PrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/privacyKeyProfilePhoto.html b/data/corefork.telegram.org/constructor/privacyKeyProfilePhoto.html deleted file mode 100644 index a498fa2134..0000000000 --- a/data/corefork.telegram.org/constructor/privacyKeyProfilePhoto.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyProfilePhoto - - - - - - - - - - - - - -
- -
-
-
- -

privacyKeyProfilePhoto

- -

Whether the profile picture of the user is visible

-

- -
-
privacyKeyProfilePhoto#96151fed = PrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/privacyKeyStatusTimestamp.html b/data/corefork.telegram.org/constructor/privacyKeyStatusTimestamp.html deleted file mode 100644 index 0bcf4a792e..0000000000 --- a/data/corefork.telegram.org/constructor/privacyKeyStatusTimestamp.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyKeyStatusTimestamp - - - - - - - - - - - - - -
- -
-
-
- -

privacyKeyStatusTimestamp

- -

Whether we can see the last online timestamp

-

- -
-
privacyKeyStatusTimestamp#bc2eab30 = PrivacyKey;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyKey

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/privacyValueAllowAll.html b/data/corefork.telegram.org/constructor/privacyValueAllowAll.html deleted file mode 100644 index 67e9bd3414..0000000000 --- a/data/corefork.telegram.org/constructor/privacyValueAllowAll.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyValueAllowAll - - - - - - - - - - - - - -
- -
-
-
- -

privacyValueAllowAll

- -

Allow all users

-

- -
-
privacyValueAllowAll#65427b82 = PrivacyRule;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/privacyValueAllowChatParticipants.html b/data/corefork.telegram.org/constructor/privacyValueAllowChatParticipants.html deleted file mode 100644 index 8ff574448b..0000000000 --- a/data/corefork.telegram.org/constructor/privacyValueAllowChatParticipants.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - privacyValueAllowChatParticipants - - - - - - - - - - - - - -
- -
-
-
- -

privacyValueAllowChatParticipants

- -

Allow all participants of certain chats

-

- -
-
privacyValueAllowChatParticipants#6b134e8e chats:Vector<long> = PrivacyRule;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chatsVector<long>Allowed chats
-

Type

-

PrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/privacyValueAllowContacts.html b/data/corefork.telegram.org/constructor/privacyValueAllowContacts.html deleted file mode 100644 index d64d7084c8..0000000000 --- a/data/corefork.telegram.org/constructor/privacyValueAllowContacts.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyValueAllowContacts - - - - - - - - - - - - - -
- -
-
-
- -

privacyValueAllowContacts

- -

Allow all contacts

-

- -
-
privacyValueAllowContacts#fffe1bac = PrivacyRule;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/privacyValueAllowUsers.html b/data/corefork.telegram.org/constructor/privacyValueAllowUsers.html deleted file mode 100644 index 55bd805ab9..0000000000 --- a/data/corefork.telegram.org/constructor/privacyValueAllowUsers.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - privacyValueAllowUsers - - - - - - - - - - - - - -
- -
-
-
- -

privacyValueAllowUsers

- -

Allow only certain users

-

- -
-
privacyValueAllowUsers#b8905fb2 users:Vector<long> = PrivacyRule;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
usersVector<long>Allowed users
-

Type

-

PrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/privacyValueDisallowAll.html b/data/corefork.telegram.org/constructor/privacyValueDisallowAll.html deleted file mode 100644 index bee1a2ea69..0000000000 --- a/data/corefork.telegram.org/constructor/privacyValueDisallowAll.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyValueDisallowAll - - - - - - - - - - - - - -
- -
-
-
- -

privacyValueDisallowAll

- -

Disallow all users

-

- -
-
privacyValueDisallowAll#8b73e763 = PrivacyRule;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/privacyValueDisallowChatParticipants.html b/data/corefork.telegram.org/constructor/privacyValueDisallowChatParticipants.html deleted file mode 100644 index e45fb602a5..0000000000 --- a/data/corefork.telegram.org/constructor/privacyValueDisallowChatParticipants.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - privacyValueDisallowChatParticipants - - - - - - - - - - - - - -
- -
-
-
- -

privacyValueDisallowChatParticipants

- -

Disallow only participants of certain chats

-

- -
-
privacyValueDisallowChatParticipants#41c87565 chats:Vector<long> = PrivacyRule;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chatsVector<long>Disallowed chats
-

Type

-

PrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/privacyValueDisallowContacts.html b/data/corefork.telegram.org/constructor/privacyValueDisallowContacts.html deleted file mode 100644 index 95639061bd..0000000000 --- a/data/corefork.telegram.org/constructor/privacyValueDisallowContacts.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - privacyValueDisallowContacts - - - - - - - - - - - - - -
- -
-
-
- -

privacyValueDisallowContacts

- -

Disallow only contacts

-

- -
-
privacyValueDisallowContacts#f888fa1a = PrivacyRule;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

PrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/privacyValueDisallowUsers.html b/data/corefork.telegram.org/constructor/privacyValueDisallowUsers.html deleted file mode 100644 index f64c8ac358..0000000000 --- a/data/corefork.telegram.org/constructor/privacyValueDisallowUsers.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - privacyValueDisallowUsers - - - - - - - - - - - - - -
- -
-
-
- -

privacyValueDisallowUsers

- -

Disallow only certain users

-

- -
-
privacyValueDisallowUsers#e4621141 users:Vector<long> = PrivacyRule;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
usersVector<long>Disallowed users
-

Type

-

PrivacyRule

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/receivedNotifyMessage.html b/data/corefork.telegram.org/constructor/receivedNotifyMessage.html deleted file mode 100644 index 68095b89bd..0000000000 --- a/data/corefork.telegram.org/constructor/receivedNotifyMessage.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - receivedNotifyMessage - - - - - - - - - - - - - -
- -
-
-
- -

receivedNotifyMessage

- -

Message ID, for which PUSH-notifications were cancelled.

-

- -
-
receivedNotifyMessage#a384b779 id:int flags:int = ReceivedNotifyMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idintMessage ID, for which PUSH-notifications were canceled
flagsintReserved for future use
-

Type

-

ReceivedNotifyMessage

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/recentMeUrlChat.html b/data/corefork.telegram.org/constructor/recentMeUrlChat.html deleted file mode 100644 index 18047862b6..0000000000 --- a/data/corefork.telegram.org/constructor/recentMeUrlChat.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - recentMeUrlChat - - - - - - - - - - - - - -
- -
-
-
- -

recentMeUrlChat

- -

Recent t.me link to a chat

-

- -
-
recentMeUrlChat#b2da71d2 url:string chat_id:long = RecentMeUrl;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringt.me URL
chat_idlongChat ID
-

Type

-

RecentMeUrl

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/recentMeUrlChatInvite.html b/data/corefork.telegram.org/constructor/recentMeUrlChatInvite.html deleted file mode 100644 index e0fcf1d789..0000000000 --- a/data/corefork.telegram.org/constructor/recentMeUrlChatInvite.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - recentMeUrlChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

recentMeUrlChatInvite

- -

Recent t.me invite link to a chat

-

- -
-
recentMeUrlChatInvite#eb49081d url:string chat_invite:ChatInvite = RecentMeUrl;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringt.me URL
chat_inviteChatInviteChat invitation
-

Type

-

RecentMeUrl

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/recentMeUrlStickerSet.html b/data/corefork.telegram.org/constructor/recentMeUrlStickerSet.html deleted file mode 100644 index 428d65c56f..0000000000 --- a/data/corefork.telegram.org/constructor/recentMeUrlStickerSet.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - recentMeUrlStickerSet - - - - - - - - - - - - - -
- -
-
-
- -

recentMeUrlStickerSet

- -

Recent t.me stickerset installation URL

-

- -
-
recentMeUrlStickerSet#bc0a57dc url:string set:StickerSetCovered = RecentMeUrl;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringt.me URL
setStickerSetCoveredStickerset
-

Type

-

RecentMeUrl

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/recentMeUrlUnknown.html b/data/corefork.telegram.org/constructor/recentMeUrlUnknown.html deleted file mode 100644 index 673e3ed8e4..0000000000 --- a/data/corefork.telegram.org/constructor/recentMeUrlUnknown.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - recentMeUrlUnknown - - - - - - - - - - - - - -
- -
-
-
- -

recentMeUrlUnknown

- -

Unknown t.me url

-

- -
-
recentMeUrlUnknown#46e1d13d url:string = RecentMeUrl;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
urlstringURL
-

Type

-

RecentMeUrl

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/recentMeUrlUser.html b/data/corefork.telegram.org/constructor/recentMeUrlUser.html deleted file mode 100644 index ef98bce39b..0000000000 --- a/data/corefork.telegram.org/constructor/recentMeUrlUser.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - recentMeUrlUser - - - - - - - - - - - - - -
- -
-
-
- -

recentMeUrlUser

- -

Recent t.me link to a user

-

- -
-
recentMeUrlUser#b92c09e2 url:string user_id:long = RecentMeUrl;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringURL
user_idlongUser ID
-

Type

-

RecentMeUrl

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/replyInlineMarkup.html b/data/corefork.telegram.org/constructor/replyInlineMarkup.html deleted file mode 100644 index 7fb2c68458..0000000000 --- a/data/corefork.telegram.org/constructor/replyInlineMarkup.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - replyInlineMarkup - - - - - - - - - - - - - -
- -
-
-
- -

replyInlineMarkup

- -

Bot or inline keyboard

-

- -
-
replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
rowsVector<KeyboardButtonRow>Bot or inline keyboard rows
-

Type

-

ReplyMarkup

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/replyKeyboardForceReply.html b/data/corefork.telegram.org/constructor/replyKeyboardForceReply.html deleted file mode 100644 index 2889af6458..0000000000 --- a/data/corefork.telegram.org/constructor/replyKeyboardForceReply.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - replyKeyboardForceReply - - - - - - - - - - - - - -
- -
-
-
- -

replyKeyboardForceReply

- -

Force the user to send a reply

-

- -
-
replyKeyboardForceReply#86b40b08 flags:# single_use:flags.1?true selective:flags.2?true placeholder:flags.3?string = ReplyMarkup;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
single_useflags.1?trueRequests clients to hide the keyboard as soon as it's been used. The keyboard will still be available, but clients will automatically display the usual letter-keyboard in the chat – the user can press a special button in the input field to see the custom keyboard again.
selectiveflags.2?trueUse this parameter if you want to show the keyboard to specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.
Example: A user requests to change the bot‘s language, bot replies to the request with a keyboard to select the new language. Other users in the group don’t see the keyboard.
placeholderflags.3?stringThe placeholder to be shown in the input field when the keyboard is active; 1-64 characters.
-

Type

-

ReplyMarkup

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/replyKeyboardHide.html b/data/corefork.telegram.org/constructor/replyKeyboardHide.html deleted file mode 100644 index cd43360855..0000000000 --- a/data/corefork.telegram.org/constructor/replyKeyboardHide.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - replyKeyboardHide - - - - - - - - - - - - - -
- -
-
-
- -

replyKeyboardHide

- -

Hide sent bot keyboard

-

- -
-
replyKeyboardHide#a03e5b85 flags:# selective:flags.2?true = ReplyMarkup;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
selectiveflags.2?trueUse this flag if you want to remove the keyboard for specific users only. Targets: 1) users that are @mentioned in the text of the Message object; 2) if the bot's message is a reply (has reply_to_message_id), sender of the original message.

Example: A user votes in a poll, bot returns confirmation message in reply to the vote and removes the keyboard for that user, while still showing the keyboard with poll options to users who haven't voted yet
-

Type

-

ReplyMarkup

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/restrictionReason.html b/data/corefork.telegram.org/constructor/restrictionReason.html deleted file mode 100644 index 499bc1b6c1..0000000000 --- a/data/corefork.telegram.org/constructor/restrictionReason.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - - restrictionReason - - - - - - - - - - - - - -
- -
-
-
- -

restrictionReason

- -

Restriction reason.

-

Contains the reason why access to a certain object must be restricted. Clients are supposed to deny access to the channel if the platform field is equal to all or to the current platform (ios, android, wp, etc.). Platforms can be concatenated (ios-android, ios-wp), unknown platforms are to be ignored. The text is the error message that should be shown to the user.

-

- -
-
restrictionReason#d072acb4 platform:string reason:string text:string = RestrictionReason;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
platformstringPlatform identifier (ios, android, wp, all, etc.), can be concatenated with a dash as separator (android-ios, ios-wp, etc)
reasonstringRestriction reason (porno, terms, etc.)
textstringError message to be shown to the user
-

Type

-

RestrictionReason

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/savedPhoneContact.html b/data/corefork.telegram.org/constructor/savedPhoneContact.html deleted file mode 100644 index c8af629587..0000000000 --- a/data/corefork.telegram.org/constructor/savedPhoneContact.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - savedPhoneContact - - - - - - - - - - - - - -
- -
-
-
- -

savedPhoneContact

- -

Saved contact

-

- -
-
savedPhoneContact#1142bd56 phone:string first_name:string last_name:string date:int = SavedContact;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phonestringPhone number
first_namestringFirst name
last_namestringLast name
dateintDate added
-

Type

-

SavedContact

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureCredentialsEncrypted.html b/data/corefork.telegram.org/constructor/secureCredentialsEncrypted.html deleted file mode 100644 index 5e1b6bc939..0000000000 --- a/data/corefork.telegram.org/constructor/secureCredentialsEncrypted.html +++ /dev/null @@ -1,159 +0,0 @@ - - - - - secureCredentialsEncrypted - - - - - - - - - - - - - -
- -
-
-
- -

secureCredentialsEncrypted

- -

Encrypted credentials required to decrypt telegram passport data.

-

- -
-
secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
databytesEncrypted JSON-serialized data with unique user's payload, data hashes and secrets required for EncryptedPassportElement decryption and authentication, as described in decrypting data »
hashbytesData hash for data authentication as described in decrypting data »
secretbytesSecret, encrypted with the bot's public RSA key, required for data decryption as described in decrypting data »
-

Type

-

SecureCredentialsEncrypted

-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureData.html b/data/corefork.telegram.org/constructor/secureData.html deleted file mode 100644 index 5b643b2390..0000000000 --- a/data/corefork.telegram.org/constructor/secureData.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - secureData - - - - - - - - - - - - - -
- -
-
-
- -

secureData

- -

Secure passport data, for more info see the passport docs »

-

- -
-
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
databytesData
data_hashbytesData hash
secretbytesSecret
-

Type

-

SecureData

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureFile.html b/data/corefork.telegram.org/constructor/secureFile.html deleted file mode 100644 index 1302ab99e3..0000000000 --- a/data/corefork.telegram.org/constructor/secureFile.html +++ /dev/null @@ -1,180 +0,0 @@ - - - - - secureFile - - - - - - - - - - - - - -
- -
-
-
- -

secureFile

- -

Secure passport file, for more info see the passport docs »

-

- -
-
secureFile#e0277a62 id:long access_hash:long size:int dc_id:int date:int file_hash:bytes secret:bytes = SecureFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongID
access_hashlongAccess hash
sizeintFile size
dc_idintDC ID
dateintDate of upload
file_hashbytesFile hash
secretbytesSecret
-

Type

-

SecureFile

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureFileEmpty.html b/data/corefork.telegram.org/constructor/secureFileEmpty.html deleted file mode 100644 index 8657cb5833..0000000000 --- a/data/corefork.telegram.org/constructor/secureFileEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureFileEmpty - - - - - - - - - - - - - -
- -
-
-
- -

secureFileEmpty

- -

Empty constructor

-

- -
-
secureFileEmpty#64199744 = SecureFile;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureFile

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/securePasswordKdfAlgoPBKDF2HMACSHA512iter100000.html b/data/corefork.telegram.org/constructor/securePasswordKdfAlgoPBKDF2HMACSHA512iter100000.html deleted file mode 100644 index a927830dfb..0000000000 --- a/data/corefork.telegram.org/constructor/securePasswordKdfAlgoPBKDF2HMACSHA512iter100000.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - securePasswordKdfAlgoPBKDF2HMACSHA512iter100000 - - - - - - - - - - - - - -
- -
-
-
- -

securePasswordKdfAlgoPBKDF2HMACSHA512iter100000

- -

PBKDF2 with SHA512 and 100000 iterations KDF algo

-

- -
-
securePasswordKdfAlgoPBKDF2HMACSHA512iter100000#bbf2dda0 salt:bytes = SecurePasswordKdfAlgo;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
saltbytesSalt
-

Type

-

SecurePasswordKdfAlgo

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/securePasswordKdfAlgoSHA512.html b/data/corefork.telegram.org/constructor/securePasswordKdfAlgoSHA512.html deleted file mode 100644 index c646f8fb0c..0000000000 --- a/data/corefork.telegram.org/constructor/securePasswordKdfAlgoSHA512.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - securePasswordKdfAlgoSHA512 - - - - - - - - - - - - - -
- -
-
-
- -

securePasswordKdfAlgoSHA512

- -

SHA512 KDF algo

-

- -
-
securePasswordKdfAlgoSHA512#86471d92 salt:bytes = SecurePasswordKdfAlgo;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
saltbytesSalt
-

Type

-

SecurePasswordKdfAlgo

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/securePasswordKdfAlgoUnknown.html b/data/corefork.telegram.org/constructor/securePasswordKdfAlgoUnknown.html deleted file mode 100644 index b537d628d7..0000000000 --- a/data/corefork.telegram.org/constructor/securePasswordKdfAlgoUnknown.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - securePasswordKdfAlgoUnknown - - - - - - - - - - - - - -
- -
-
-
- -

securePasswordKdfAlgoUnknown

- -

Unknown KDF algo (most likely the client has to be updated)

-

- -
-
securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecurePasswordKdfAlgo

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/securePlainEmail.html b/data/corefork.telegram.org/constructor/securePlainEmail.html deleted file mode 100644 index 783b0b73b8..0000000000 --- a/data/corefork.telegram.org/constructor/securePlainEmail.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - securePlainEmail - - - - - - - - - - - - - -
- -
-
-
- -

securePlainEmail

- -

Email address to use in telegram passport: it must be verified, first ».

-

- -
-
securePlainEmail#21ec5a5f email:string = SecurePlainData;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
emailstringEmail address
-

Type

-

SecurePlainData

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/securePlainPhone.html b/data/corefork.telegram.org/constructor/securePlainPhone.html deleted file mode 100644 index 6cc2093640..0000000000 --- a/data/corefork.telegram.org/constructor/securePlainPhone.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - securePlainPhone - - - - - - - - - - - - - -
- -
-
-
- -

securePlainPhone

- -

Phone number to use in telegram passport: it must be verified, first ».

-

- -
-
securePlainPhone#7d6099dd phone:string = SecurePlainData;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
phonestringPhone number
-

Type

-

SecurePlainData

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureRequiredType.html b/data/corefork.telegram.org/constructor/secureRequiredType.html deleted file mode 100644 index 3d9a50327e..0000000000 --- a/data/corefork.telegram.org/constructor/secureRequiredType.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - secureRequiredType - - - - - - - - - - - - - -
- -
-
-
- -

secureRequiredType

- -

Required type

-

- -
-
secureRequiredType#829d99da flags:# native_names:flags.0?true selfie_required:flags.1?true translation_required:flags.2?true type:SecureValueType = SecureRequiredType;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
native_namesflags.0?trueNative names
selfie_requiredflags.1?trueIs a selfie required
translation_requiredflags.2?trueIs a translation required
typeSecureValueTypeSecure value type
-

Type

-

SecureRequiredType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureRequiredTypeOneOf.html b/data/corefork.telegram.org/constructor/secureRequiredTypeOneOf.html deleted file mode 100644 index 278b8a0451..0000000000 --- a/data/corefork.telegram.org/constructor/secureRequiredTypeOneOf.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - secureRequiredTypeOneOf - - - - - - - - - - - - - -
- -
-
-
- -

secureRequiredTypeOneOf

- -

One of

-

- -
-
secureRequiredTypeOneOf#27477b4 types:Vector<SecureRequiredType> = SecureRequiredType;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
typesVector<SecureRequiredType>Secure required value types
-

Type

-

SecureRequiredType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureSecretSettings.html b/data/corefork.telegram.org/constructor/secureSecretSettings.html deleted file mode 100644 index 7f0a5ef253..0000000000 --- a/data/corefork.telegram.org/constructor/secureSecretSettings.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - secureSecretSettings - - - - - - - - - - - - - -
- -
-
-
- -

secureSecretSettings

- -

Secure settings

-

- -
-
secureSecretSettings#1527bcac secure_algo:SecurePasswordKdfAlgo secure_secret:bytes secure_secret_id:long = SecureSecretSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
secure_algoSecurePasswordKdfAlgoSecure KDF algo
secure_secretbytesSecure secret
secure_secret_idlongSecret ID
-

Type

-

SecureSecretSettings

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValue.html b/data/corefork.telegram.org/constructor/secureValue.html deleted file mode 100644 index 24dbd1116d..0000000000 --- a/data/corefork.telegram.org/constructor/secureValue.html +++ /dev/null @@ -1,194 +0,0 @@ - - - - - secureValue - - - - - - - - - - - - - -
- -
-
-
- -

secureValue

- -

Secure value

-

- -
-
secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
typeSecureValueTypeSecure passport value type
dataflags.0?SecureDataEncrypted Telegram Passport element data
front_sideflags.1?SecureFileEncrypted passport file with the front side of the document
reverse_sideflags.2?SecureFileEncrypted passport file with the reverse side of the document
selfieflags.3?SecureFileEncrypted passport file with a selfie of the user holding the document
translationflags.6?Vector<SecureFile>Array of encrypted passport files with translated versions of the provided documents
filesflags.4?Vector<SecureFile>Array of encrypted passport files with photos the of the documents
plain_dataflags.5?SecurePlainDataPlaintext verified passport data
hashbytesData hash
-

Type

-

SecureValue

-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValueError.html b/data/corefork.telegram.org/constructor/secureValueError.html deleted file mode 100644 index 44b52763c3..0000000000 --- a/data/corefork.telegram.org/constructor/secureValueError.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - secureValueError - - - - - - - - - - - - - -
- -
-
-
- -

secureValueError

- -

Secure value error

-

- -
-
secureValueError#869d758f type:SecureValueType hash:bytes text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeType of element which has the issue
hashbytesHash
textstringError message
-

Type

-

SecureValueError

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValueErrorData.html b/data/corefork.telegram.org/constructor/secureValueErrorData.html deleted file mode 100644 index 82dc22a92b..0000000000 --- a/data/corefork.telegram.org/constructor/secureValueErrorData.html +++ /dev/null @@ -1,175 +0,0 @@ - - - - - secureValueErrorData - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorData

- -

Represents an issue in one of the data fields that was provided by the user. The error is considered resolved when the field's value changes.

-

- -
-
secureValueErrorData#e8a40bd9 type:SecureValueType data_hash:bytes field:string text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeThe section of the user's Telegram Passport which has the error, one of secureValueTypePersonalDetails, secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport, secureValueTypeAddress
data_hashbytesData hash
fieldstringName of the data field which has the error
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypePersonalDetails

-

Personal details

-

secureValueTypePassport

-

Passport

-

secureValueTypeDriverLicense

-

Driver's license

-

secureValueTypeIdentityCard

-

Identity card

-

secureValueTypeInternalPassport

-

Internal passport

-

secureValueTypeAddress

-

Address

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValueErrorFile.html b/data/corefork.telegram.org/constructor/secureValueErrorFile.html deleted file mode 100644 index 1c0f9a9da1..0000000000 --- a/data/corefork.telegram.org/constructor/secureValueErrorFile.html +++ /dev/null @@ -1,168 +0,0 @@ - - - - - secureValueErrorFile - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorFile

- -

Represents an issue with a document scan. The error is considered resolved when the file with the document scan changes.

-

- -
-
secureValueErrorFile#7a700873 type:SecureValueType file_hash:bytes text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeOne of secureValueTypeUtilityBill, secureValueTypeBankStatement, secureValueTypeRentalAgreement, secureValueTypePassportRegistration, secureValueTypeTemporaryRegistration
file_hashbytesFile hash
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypeUtilityBill

-

Utility bill

-

secureValueTypeBankStatement

-

Bank statement

-

secureValueTypeRentalAgreement

-

Rental agreement

-

secureValueTypePassportRegistration

-

Internal registration passport

-

secureValueTypeTemporaryRegistration

-

Temporary registration

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValueErrorFiles.html b/data/corefork.telegram.org/constructor/secureValueErrorFiles.html deleted file mode 100644 index 35affb61d8..0000000000 --- a/data/corefork.telegram.org/constructor/secureValueErrorFiles.html +++ /dev/null @@ -1,168 +0,0 @@ - - - - - secureValueErrorFiles - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorFiles

- -

Represents an issue with a list of scans. The error is considered resolved when the list of files containing the scans changes.

-

- -
-
secureValueErrorFiles#666220e9 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeOne of secureValueTypeUtilityBill, secureValueTypeBankStatement, secureValueTypeRentalAgreement, secureValueTypePassportRegistration, secureValueTypeTemporaryRegistration
file_hashVector<bytes>File hash
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypeUtilityBill

-

Utility bill

-

secureValueTypeBankStatement

-

Bank statement

-

secureValueTypeRentalAgreement

-

Rental agreement

-

secureValueTypePassportRegistration

-

Internal registration passport

-

secureValueTypeTemporaryRegistration

-

Temporary registration

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValueErrorFrontSide.html b/data/corefork.telegram.org/constructor/secureValueErrorFrontSide.html deleted file mode 100644 index 207c1238cc..0000000000 --- a/data/corefork.telegram.org/constructor/secureValueErrorFrontSide.html +++ /dev/null @@ -1,166 +0,0 @@ - - - - - secureValueErrorFrontSide - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorFrontSide

- -

Represents an issue with the front side of a document. The error is considered resolved when the file with the front side of the document changes.

-

- -
-
secureValueErrorFrontSide#be3dfa type:SecureValueType file_hash:bytes text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeOne of secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport
file_hashbytesFile hash
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypePassport

-

Passport

-

secureValueTypeDriverLicense

-

Driver's license

-

secureValueTypeIdentityCard

-

Identity card

-

secureValueTypeInternalPassport

-

Internal passport

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValueErrorReverseSide.html b/data/corefork.telegram.org/constructor/secureValueErrorReverseSide.html deleted file mode 100644 index 1ad1c10cfd..0000000000 --- a/data/corefork.telegram.org/constructor/secureValueErrorReverseSide.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - secureValueErrorReverseSide - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorReverseSide

- -

Represents an issue with the reverse side of a document. The error is considered resolved when the file with reverse side of the document changes.

-

- -
-
secureValueErrorReverseSide#868a2aa5 type:SecureValueType file_hash:bytes text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeOne of secureValueTypeDriverLicense, secureValueTypeIdentityCard
file_hashbytesFile hash
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypeDriverLicense

-

Driver's license

-

secureValueTypeIdentityCard

-

Identity card

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValueErrorSelfie.html b/data/corefork.telegram.org/constructor/secureValueErrorSelfie.html deleted file mode 100644 index b31e2c2a13..0000000000 --- a/data/corefork.telegram.org/constructor/secureValueErrorSelfie.html +++ /dev/null @@ -1,166 +0,0 @@ - - - - - secureValueErrorSelfie - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorSelfie

- -

Represents an issue with the selfie with a document. The error is considered resolved when the file with the selfie changes.

-

- -
-
secureValueErrorSelfie#e537ced6 type:SecureValueType file_hash:bytes text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeOne of secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport
file_hashbytesFile hash
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypePassport

-

Passport

-

secureValueTypeDriverLicense

-

Driver's license

-

secureValueTypeIdentityCard

-

Identity card

-

secureValueTypeInternalPassport

-

Internal passport

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValueErrorTranslationFile.html b/data/corefork.telegram.org/constructor/secureValueErrorTranslationFile.html deleted file mode 100644 index 822a4db7cc..0000000000 --- a/data/corefork.telegram.org/constructor/secureValueErrorTranslationFile.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - secureValueErrorTranslationFile - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorTranslationFile

- -

Represents an issue with one of the files that constitute the translation of a document. The error is considered resolved when the file changes.

-

- -
-
secureValueErrorTranslationFile#a1144770 type:SecureValueType file_hash:bytes text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeOne of secureValueTypePersonalDetails, secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport, secureValueTypeUtilityBill, secureValueTypeBankStatement, secureValueTypeRentalAgreement, secureValueTypePassportRegistration, secureValueTypeTemporaryRegistration
file_hashbytesFile hash
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypePersonalDetails

-

Personal details

-

secureValueTypePassport

-

Passport

-

secureValueTypeDriverLicense

-

Driver's license

-

secureValueTypeIdentityCard

-

Identity card

-

secureValueTypeInternalPassport

-

Internal passport

-

secureValueTypeUtilityBill

-

Utility bill

-

secureValueTypeBankStatement

-

Bank statement

-

secureValueTypeRentalAgreement

-

Rental agreement

-

secureValueTypePassportRegistration

-

Internal registration passport

-

secureValueTypeTemporaryRegistration

-

Temporary registration

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValueErrorTranslationFiles.html b/data/corefork.telegram.org/constructor/secureValueErrorTranslationFiles.html deleted file mode 100644 index 0798c94b0a..0000000000 --- a/data/corefork.telegram.org/constructor/secureValueErrorTranslationFiles.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - secureValueErrorTranslationFiles - - - - - - - - - - - - - -
- -
-
-
- -

secureValueErrorTranslationFiles

- -

Represents an issue with the translated version of a document. The error is considered resolved when a file with the document translation changes.

-

- -
-
secureValueErrorTranslationFiles#34636dd8 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeOne of secureValueTypePersonalDetails, secureValueTypePassport, secureValueTypeDriverLicense, secureValueTypeIdentityCard, secureValueTypeInternalPassport, secureValueTypeUtilityBill, secureValueTypeBankStatement, secureValueTypeRentalAgreement, secureValueTypePassportRegistration, secureValueTypeTemporaryRegistration
file_hashVector<bytes>Hash
textstringError message
-

Type

-

SecureValueError

-

Related pages

-

secureValueTypePersonalDetails

-

Personal details

-

secureValueTypePassport

-

Passport

-

secureValueTypeDriverLicense

-

Driver's license

-

secureValueTypeIdentityCard

-

Identity card

-

secureValueTypeInternalPassport

-

Internal passport

-

secureValueTypeUtilityBill

-

Utility bill

-

secureValueTypeBankStatement

-

Bank statement

-

secureValueTypeRentalAgreement

-

Rental agreement

-

secureValueTypePassportRegistration

-

Internal registration passport

-

secureValueTypeTemporaryRegistration

-

Temporary registration

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValueHash.html b/data/corefork.telegram.org/constructor/secureValueHash.html deleted file mode 100644 index a17a415b6d..0000000000 --- a/data/corefork.telegram.org/constructor/secureValueHash.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - secureValueHash - - - - - - - - - - - - - -
- -
-
-
- -

secureValueHash

- -

Secure value hash

-

- -
-
secureValueHash#ed1ecdb0 type:SecureValueType hash:bytes = SecureValueHash;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeSecure value type
hashbytesHash
-

Type

-

SecureValueHash

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValueTypeAddress.html b/data/corefork.telegram.org/constructor/secureValueTypeAddress.html deleted file mode 100644 index 1c1497b354..0000000000 --- a/data/corefork.telegram.org/constructor/secureValueTypeAddress.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeAddress - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypeAddress

- -

Address

-

- -
-
secureValueTypeAddress#cbe31e26 = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValueTypeBankStatement.html b/data/corefork.telegram.org/constructor/secureValueTypeBankStatement.html deleted file mode 100644 index 3bece8b5f6..0000000000 --- a/data/corefork.telegram.org/constructor/secureValueTypeBankStatement.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeBankStatement - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypeBankStatement

- -

Bank statement

-

- -
-
secureValueTypeBankStatement#89137c0d = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValueTypeDriverLicense.html b/data/corefork.telegram.org/constructor/secureValueTypeDriverLicense.html deleted file mode 100644 index babcab882e..0000000000 --- a/data/corefork.telegram.org/constructor/secureValueTypeDriverLicense.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeDriverLicense - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypeDriverLicense

- -

Driver's license

-

- -
-
secureValueTypeDriverLicense#6e425c4 = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValueTypeEmail.html b/data/corefork.telegram.org/constructor/secureValueTypeEmail.html deleted file mode 100644 index aa7c0e0f68..0000000000 --- a/data/corefork.telegram.org/constructor/secureValueTypeEmail.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeEmail - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypeEmail

- -

Email

-

- -
-
secureValueTypeEmail#8e3ca7ee = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValueTypeIdentityCard.html b/data/corefork.telegram.org/constructor/secureValueTypeIdentityCard.html deleted file mode 100644 index 15a907e957..0000000000 --- a/data/corefork.telegram.org/constructor/secureValueTypeIdentityCard.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeIdentityCard - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypeIdentityCard

- -

Identity card

-

- -
-
secureValueTypeIdentityCard#a0d0744b = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValueTypeInternalPassport.html b/data/corefork.telegram.org/constructor/secureValueTypeInternalPassport.html deleted file mode 100644 index 4fda53c4ca..0000000000 --- a/data/corefork.telegram.org/constructor/secureValueTypeInternalPassport.html +++ /dev/null @@ -1,134 +0,0 @@ - - - - - secureValueTypeInternalPassport - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypeInternalPassport

- -

Internal passport

-

- -
-
secureValueTypeInternalPassport#99a48f23 = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValueTypePassport.html b/data/corefork.telegram.org/constructor/secureValueTypePassport.html deleted file mode 100644 index dc61d341fe..0000000000 --- a/data/corefork.telegram.org/constructor/secureValueTypePassport.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypePassport - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypePassport

- -

Passport

-

- -
-
secureValueTypePassport#3dac6a00 = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValueTypePassportRegistration.html b/data/corefork.telegram.org/constructor/secureValueTypePassportRegistration.html deleted file mode 100644 index b70c4991b7..0000000000 --- a/data/corefork.telegram.org/constructor/secureValueTypePassportRegistration.html +++ /dev/null @@ -1,134 +0,0 @@ - - - - - secureValueTypePassportRegistration - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypePassportRegistration

- -

Internal registration passport

-

- -
-
secureValueTypePassportRegistration#99e3806a = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValueTypePersonalDetails.html b/data/corefork.telegram.org/constructor/secureValueTypePersonalDetails.html deleted file mode 100644 index 022f29e3e5..0000000000 --- a/data/corefork.telegram.org/constructor/secureValueTypePersonalDetails.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypePersonalDetails - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypePersonalDetails

- -

Personal details

-

- -
-
secureValueTypePersonalDetails#9d2a81e3 = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValueTypePhone.html b/data/corefork.telegram.org/constructor/secureValueTypePhone.html deleted file mode 100644 index ebfb3c2217..0000000000 --- a/data/corefork.telegram.org/constructor/secureValueTypePhone.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypePhone - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypePhone

- -

Phone

-

- -
-
secureValueTypePhone#b320aadb = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValueTypeRentalAgreement.html b/data/corefork.telegram.org/constructor/secureValueTypeRentalAgreement.html deleted file mode 100644 index dd9f2e1c44..0000000000 --- a/data/corefork.telegram.org/constructor/secureValueTypeRentalAgreement.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeRentalAgreement - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypeRentalAgreement

- -

Rental agreement

-

- -
-
secureValueTypeRentalAgreement#8b883488 = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValueTypeTemporaryRegistration.html b/data/corefork.telegram.org/constructor/secureValueTypeTemporaryRegistration.html deleted file mode 100644 index e5ed262ca8..0000000000 --- a/data/corefork.telegram.org/constructor/secureValueTypeTemporaryRegistration.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeTemporaryRegistration - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypeTemporaryRegistration

- -

Temporary registration

-

- -
-
secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/secureValueTypeUtilityBill.html b/data/corefork.telegram.org/constructor/secureValueTypeUtilityBill.html deleted file mode 100644 index 964f3b3a37..0000000000 --- a/data/corefork.telegram.org/constructor/secureValueTypeUtilityBill.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - secureValueTypeUtilityBill - - - - - - - - - - - - - -
- -
-
-
- -

secureValueTypeUtilityBill

- -

Utility bill

-

- -
-
secureValueTypeUtilityBill#fc36954e = SecureValueType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SecureValueType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/sendMessageCancelAction.html b/data/corefork.telegram.org/constructor/sendMessageCancelAction.html deleted file mode 100644 index 17171db354..0000000000 --- a/data/corefork.telegram.org/constructor/sendMessageCancelAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageCancelAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageCancelAction

- -

Invalidate all previous action updates. E.g. when user deletes entered text or aborts a video upload.

-

- -
-
sendMessageCancelAction#fd5ec8f5 = SendMessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/sendMessageChooseContactAction.html b/data/corefork.telegram.org/constructor/sendMessageChooseContactAction.html deleted file mode 100644 index e29bfd2720..0000000000 --- a/data/corefork.telegram.org/constructor/sendMessageChooseContactAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageChooseContactAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageChooseContactAction

- -

User is selecting a contact to share.

-

- -
-
sendMessageChooseContactAction#628cbc6f = SendMessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/sendMessageChooseStickerAction.html b/data/corefork.telegram.org/constructor/sendMessageChooseStickerAction.html deleted file mode 100644 index 2969cfefe6..0000000000 --- a/data/corefork.telegram.org/constructor/sendMessageChooseStickerAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageChooseStickerAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageChooseStickerAction

- -

User is choosing a sticker

-

- -
-
sendMessageChooseStickerAction#b05ac6b1 = SendMessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/sendMessageEmojiInteraction.html b/data/corefork.telegram.org/constructor/sendMessageEmojiInteraction.html deleted file mode 100644 index 6dfe2b367b..0000000000 --- a/data/corefork.telegram.org/constructor/sendMessageEmojiInteraction.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - sendMessageEmojiInteraction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageEmojiInteraction

- -

User has clicked on an animated emoji triggering a reaction, click here for more info ».

-

- -
-
sendMessageEmojiInteraction#25972bcb emoticon:string msg_id:int interaction:DataJSON = SendMessageAction;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
emoticonstringEmoji
msg_idintMessage ID of the animated emoji that was clicked
interactionDataJSONA JSON object with interaction info, click here for more info »
-

Type

-

SendMessageAction

-

Related pages

-

Animated Emojis

-

Graphical telegram clients should transform emojis into their respective animated version.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/sendMessageGamePlayAction.html b/data/corefork.telegram.org/constructor/sendMessageGamePlayAction.html deleted file mode 100644 index e820fa3e6e..0000000000 --- a/data/corefork.telegram.org/constructor/sendMessageGamePlayAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageGamePlayAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageGamePlayAction

- -

User is playing a game

-

- -
-
sendMessageGamePlayAction#dd6a8f48 = SendMessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/sendMessageGeoLocationAction.html b/data/corefork.telegram.org/constructor/sendMessageGeoLocationAction.html deleted file mode 100644 index d6efa14105..0000000000 --- a/data/corefork.telegram.org/constructor/sendMessageGeoLocationAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageGeoLocationAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageGeoLocationAction

- -

User is selecting a location to share.

-

- -
-
sendMessageGeoLocationAction#176f8ba1 = SendMessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/sendMessageHistoryImportAction.html b/data/corefork.telegram.org/constructor/sendMessageHistoryImportAction.html deleted file mode 100644 index 83eb70c50c..0000000000 --- a/data/corefork.telegram.org/constructor/sendMessageHistoryImportAction.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - sendMessageHistoryImportAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageHistoryImportAction

- -

Chat history is being imported

-

- -
-
sendMessageHistoryImportAction#dbda9246 progress:int = SendMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
progressintProgress percentage
-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/sendMessageRecordAudioAction.html b/data/corefork.telegram.org/constructor/sendMessageRecordAudioAction.html deleted file mode 100644 index 8f796a7471..0000000000 --- a/data/corefork.telegram.org/constructor/sendMessageRecordAudioAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageRecordAudioAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageRecordAudioAction

- -

User is recording a voice message.

-

- -
-
sendMessageRecordAudioAction#d52f73f7 = SendMessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/sendMessageRecordRoundAction.html b/data/corefork.telegram.org/constructor/sendMessageRecordRoundAction.html deleted file mode 100644 index a6914fe032..0000000000 --- a/data/corefork.telegram.org/constructor/sendMessageRecordRoundAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageRecordRoundAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageRecordRoundAction

- -

User is recording a round video to share

-

- -
-
sendMessageRecordRoundAction#88f27fbc = SendMessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/sendMessageRecordVideoAction.html b/data/corefork.telegram.org/constructor/sendMessageRecordVideoAction.html deleted file mode 100644 index 86bad15042..0000000000 --- a/data/corefork.telegram.org/constructor/sendMessageRecordVideoAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageRecordVideoAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageRecordVideoAction

- -

User is recording a video.

-

- -
-
sendMessageRecordVideoAction#a187d66f = SendMessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/sendMessageTypingAction.html b/data/corefork.telegram.org/constructor/sendMessageTypingAction.html deleted file mode 100644 index 2e46d0b5e6..0000000000 --- a/data/corefork.telegram.org/constructor/sendMessageTypingAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - sendMessageTypingAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageTypingAction

- -

User is typing.

-

- -
-
sendMessageTypingAction#16bf744e = SendMessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/sendMessageUploadAudioAction.html b/data/corefork.telegram.org/constructor/sendMessageUploadAudioAction.html deleted file mode 100644 index 98b2747efa..0000000000 --- a/data/corefork.telegram.org/constructor/sendMessageUploadAudioAction.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - sendMessageUploadAudioAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageUploadAudioAction

- -

User is uploading a voice message.

-

- -
-
sendMessageUploadAudioAction#f351d7ab progress:int = SendMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
progressintProgress percentage
-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/sendMessageUploadDocumentAction.html b/data/corefork.telegram.org/constructor/sendMessageUploadDocumentAction.html deleted file mode 100644 index 6513fe68d5..0000000000 --- a/data/corefork.telegram.org/constructor/sendMessageUploadDocumentAction.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - sendMessageUploadDocumentAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageUploadDocumentAction

- -

User is uploading a file.

-

- -
-
sendMessageUploadDocumentAction#aa0cd9e4 progress:int = SendMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
progressintProgress percentage
-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/sendMessageUploadPhotoAction.html b/data/corefork.telegram.org/constructor/sendMessageUploadPhotoAction.html deleted file mode 100644 index 1c29e77e74..0000000000 --- a/data/corefork.telegram.org/constructor/sendMessageUploadPhotoAction.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - sendMessageUploadPhotoAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageUploadPhotoAction

- -

User is uploading a photo.

-

- -
-
sendMessageUploadPhotoAction#d1d34a26 progress:int = SendMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
progressintProgress percentage
-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/sendMessageUploadRoundAction.html b/data/corefork.telegram.org/constructor/sendMessageUploadRoundAction.html deleted file mode 100644 index 18d5bb1f5f..0000000000 --- a/data/corefork.telegram.org/constructor/sendMessageUploadRoundAction.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - sendMessageUploadRoundAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageUploadRoundAction

- -

User is uploading a round video

-

- -
-
sendMessageUploadRoundAction#243e1c66 progress:int = SendMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
progressintProgress percentage
-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/sendMessageUploadVideoAction.html b/data/corefork.telegram.org/constructor/sendMessageUploadVideoAction.html deleted file mode 100644 index 880e64b6a8..0000000000 --- a/data/corefork.telegram.org/constructor/sendMessageUploadVideoAction.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - sendMessageUploadVideoAction - - - - - - - - - - - - - -
- -
-
-
- -

sendMessageUploadVideoAction

- -

User is uploading a video.

-

- -
-
sendMessageUploadVideoAction#e9763aec progress:int = SendMessageAction;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
progressintProgress percentage
-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/shippingOption.html b/data/corefork.telegram.org/constructor/shippingOption.html deleted file mode 100644 index 18541f89dd..0000000000 --- a/data/corefork.telegram.org/constructor/shippingOption.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - shippingOption - - - - - - - - - - - - - -
- -
-
-
- -

shippingOption

- -

Shipping option

-

- -
-
shippingOption#b6213cdf id:string title:string prices:Vector<LabeledPrice> = ShippingOption;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idstringOption ID
titlestringTitle
pricesVector<LabeledPrice>List of price portions
-

Type

-

ShippingOption

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/speakingInGroupCallAction.html b/data/corefork.telegram.org/constructor/speakingInGroupCallAction.html deleted file mode 100644 index 933ff45492..0000000000 --- a/data/corefork.telegram.org/constructor/speakingInGroupCallAction.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - speakingInGroupCallAction - - - - - - - - - - - - - -
- -
-
-
- -

speakingInGroupCallAction

- -

User is currently speaking in the group call

-

- -
-
speakingInGroupCallAction#d92c2285 = SendMessageAction;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

SendMessageAction

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/sponsoredMessage.html b/data/corefork.telegram.org/constructor/sponsoredMessage.html deleted file mode 100644 index 9e656a9d24..0000000000 --- a/data/corefork.telegram.org/constructor/sponsoredMessage.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - sponsoredMessage - - - - - - - - - - - - - -
- -
-
-
- -

sponsoredMessage

- -

A sponsored message.

-

- -
-
sponsoredMessage#2a3c381f flags:# random_id:bytes from_id:Peer start_param:flags.0?string message:string entities:flags.1?Vector<MessageEntity> = SponsoredMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
random_idbytesMessage ID
from_idPeerID of the sender of the message
start_paramflags.0?stringParameter for the bot start message if the sponsored chat is a chat with a bot.
messagestringSponsored message
entitiesflags.1?Vector<MessageEntity>Message entities for styled text
-

Type

-

SponsoredMessage

-

Related pages

-

Sponsored messages

-

How to implement sponsored messages

-

Styled text with message entities

-

How to create styled text with message entities

-
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/stats.broadcastStats b/data/corefork.telegram.org/constructor/stats.broadcastStats deleted file mode 100644 index d5081ab39b..0000000000 --- a/data/corefork.telegram.org/constructor/stats.broadcastStats +++ /dev/null @@ -1,220 +0,0 @@ - - - - - stats.broadcastStats - - - - - - - - - - - - - -
- -
-
-
- -

stats.broadcastStats

- -

Channel statistics.

-

- -
-
stats.broadcastStats#bdf78394 period:StatsDateRangeDays followers:StatsAbsValueAndPrev views_per_post:StatsAbsValueAndPrev shares_per_post:StatsAbsValueAndPrev enabled_notifications:StatsPercentValue growth_graph:StatsGraph followers_graph:StatsGraph mute_graph:StatsGraph top_hours_graph:StatsGraph interactions_graph:StatsGraph iv_interactions_graph:StatsGraph views_by_source_graph:StatsGraph new_followers_by_source_graph:StatsGraph languages_graph:StatsGraph recent_message_interactions:Vector<MessageInteractionCounters> = stats.BroadcastStats;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
periodStatsDateRangeDaysPeriod in consideration
followersStatsAbsValueAndPrevFollower count change for period in consideration
views_per_postStatsAbsValueAndPrevtotal_viewcount/postcount, for posts posted during the period in consideration (views_per_post).
Note that in this case, current refers to the period in consideration (min_date till max_date), and prev refers to the previous period ((min_date - (max_date - min_date)) till min_date).
shares_per_postStatsAbsValueAndPrevtotal_viewcount/postcount, for posts posted during the period in consideration (views_per_post).
Note that in this case, current refers to the period in consideration (min_date till max_date), and prev refers to the previous period ((min_date - (max_date - min_date)) till min_date)
enabled_notificationsStatsPercentValuePercentage of subscribers with enabled notifications
growth_graphStatsGraphChannel growth graph (absolute subscriber count)
followers_graphStatsGraphFollowers growth graph (relative subscriber count)
mute_graphStatsGraphMuted users graph (relative)
top_hours_graphStatsGraphViews per hour graph (absolute)
interactions_graphStatsGraphInteractions graph (absolute)
iv_interactions_graphStatsGraphIV interactions graph (absolute)
views_by_source_graphStatsGraphViews by source graph (absolute)
new_followers_by_source_graphStatsGraphNew followers by source graph (absolute)
languages_graphStatsGraphSubscriber language graph (piechart)
recent_message_interactionsVector<MessageInteractionCounters>Recent message interactions
-

Type

-

stats.BroadcastStats

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/stats.megagroupStats b/data/corefork.telegram.org/constructor/stats.megagroupStats deleted file mode 100644 index 720b6257e2..0000000000 --- a/data/corefork.telegram.org/constructor/stats.megagroupStats +++ /dev/null @@ -1,230 +0,0 @@ - - - - - stats.megagroupStats - - - - - - - - - - - - - -
- -
-
-
- -

stats.megagroupStats

- -

Supergroup statistics

-

- -
-
stats.megagroupStats#ef7ff916 period:StatsDateRangeDays members:StatsAbsValueAndPrev messages:StatsAbsValueAndPrev viewers:StatsAbsValueAndPrev posters:StatsAbsValueAndPrev growth_graph:StatsGraph members_graph:StatsGraph new_members_by_source_graph:StatsGraph languages_graph:StatsGraph messages_graph:StatsGraph actions_graph:StatsGraph top_hours_graph:StatsGraph weekdays_graph:StatsGraph top_posters:Vector<StatsGroupTopPoster> top_admins:Vector<StatsGroupTopAdmin> top_inviters:Vector<StatsGroupTopInviter> users:Vector<User> = stats.MegagroupStats;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
periodStatsDateRangeDaysPeriod in consideration
membersStatsAbsValueAndPrevMember count change for period in consideration
messagesStatsAbsValueAndPrevMessage number change for period in consideration
viewersStatsAbsValueAndPrevNumber of users that viewed messages, for range in consideration
postersStatsAbsValueAndPrevNumber of users that posted messages, for range in consideration
growth_graphStatsGraphSupergroup growth graph (absolute subscriber count)
members_graphStatsGraphMembers growth (relative subscriber count)
new_members_by_source_graphStatsGraphNew members by source graph
languages_graphStatsGraphSubscriber language graph (piechart)
messages_graphStatsGraphMessage activity graph (stacked bar graph, message type)
actions_graphStatsGraphGroup activity graph (deleted, modified messages, blocked users)
top_hours_graphStatsGraphActivity per hour graph (absolute)
weekdays_graphStatsGraphActivity per day of week graph (absolute)
top_postersVector<StatsGroupTopPoster>Info about most active group members
top_adminsVector<StatsGroupTopAdmin>Info about most active group admins
top_invitersVector<StatsGroupTopInviter>Info about most active group inviters
usersVector<User>Info about users mentioned in statistics
-

Type

-

stats.MegagroupStats

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/statsAbsValueAndPrev.html b/data/corefork.telegram.org/constructor/statsAbsValueAndPrev.html deleted file mode 100644 index b71377bfbf..0000000000 --- a/data/corefork.telegram.org/constructor/statsAbsValueAndPrev.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - statsAbsValueAndPrev - - - - - - - - - - - - - -
- -
-
-
- -

statsAbsValueAndPrev

- -

Statistics value couple; initial and final value for period of time currently in consideration

-

- -
-
statsAbsValueAndPrev#cb43acde current:double previous:double = StatsAbsValueAndPrev;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
currentdoubleCurrent value
previousdoublePrevious value
-

Type

-

StatsAbsValueAndPrev

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/statsDateRangeDays.html b/data/corefork.telegram.org/constructor/statsDateRangeDays.html deleted file mode 100644 index 485b02b819..0000000000 --- a/data/corefork.telegram.org/constructor/statsDateRangeDays.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - statsDateRangeDays - - - - - - - - - - - - - -
- -
-
-
- -

statsDateRangeDays

- -

Channel statistics date range

-

- -
-
statsDateRangeDays#b637edaf min_date:int max_date:int = StatsDateRangeDays;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
min_dateintInitial date
max_dateintFinal date
-

Type

-

StatsDateRangeDays

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/statsGraph.html b/data/corefork.telegram.org/constructor/statsGraph.html deleted file mode 100644 index 0f6f4b80d3..0000000000 --- a/data/corefork.telegram.org/constructor/statsGraph.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - statsGraph - - - - - - - - - - - - - -
- -
-
-
- -

statsGraph

- -

Channel statistics graph

-

- -
-
statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
jsonDataJSONStatistics data
zoom_tokenflags.0?stringZoom token
-

Type

-

StatsGraph

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/statsGraphAsync.html b/data/corefork.telegram.org/constructor/statsGraphAsync.html deleted file mode 100644 index 5d0a05aeaf..0000000000 --- a/data/corefork.telegram.org/constructor/statsGraphAsync.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - statsGraphAsync - - - - - - - - - - - - - -
- -
-
-
- -

statsGraphAsync

- -

This channel statistics graph must be generated asynchronously using stats.loadAsyncGraph to reduce server load

-

- -
-
statsGraphAsync#4a27eb2d token:string = StatsGraph;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
tokenstringToken to use for fetching the async graph
-

Type

-

StatsGraph

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

-

stats.loadAsyncGraph

-

Load channel statistics graph asynchronously

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/statsGroupTopAdmin.html b/data/corefork.telegram.org/constructor/statsGroupTopAdmin.html deleted file mode 100644 index e98646e03a..0000000000 --- a/data/corefork.telegram.org/constructor/statsGroupTopAdmin.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - statsGroupTopAdmin - - - - - - - - - - - - - -
- -
-
-
- -

statsGroupTopAdmin

- -

Information about an active admin in a supergroup

-

- -
-
statsGroupTopAdmin#d7584c87 user_id:long deleted:int kicked:int banned:int = StatsGroupTopAdmin;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser ID
deletedintNumber of deleted messages for statistics period in consideration
kickedintNumber of kicked users for statistics period in consideration
bannedintNumber of banned users for statistics period in consideration
-

Type

-

StatsGroupTopAdmin

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/statsGroupTopInviter.html b/data/corefork.telegram.org/constructor/statsGroupTopInviter.html deleted file mode 100644 index c0c12e7cef..0000000000 --- a/data/corefork.telegram.org/constructor/statsGroupTopInviter.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - statsGroupTopInviter - - - - - - - - - - - - - -
- -
-
-
- -

statsGroupTopInviter

- -

Information about an active supergroup inviter

-

- -
-
statsGroupTopInviter#535f779d user_id:long invitations:int = StatsGroupTopInviter;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser ID
invitationsintNumber of invitations for statistics period in consideration
-

Type

-

StatsGroupTopInviter

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/statsGroupTopPoster.html b/data/corefork.telegram.org/constructor/statsGroupTopPoster.html deleted file mode 100644 index 567c733fa0..0000000000 --- a/data/corefork.telegram.org/constructor/statsGroupTopPoster.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - statsGroupTopPoster - - - - - - - - - - - - - -
- -
-
-
- -

statsGroupTopPoster

- -

Information about an active user in a supergroup

-

- -
-
statsGroupTopPoster#9d04af9b user_id:long messages:int avg_chars:int = StatsGroupTopPoster;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser ID
messagesintNumber of messages for statistics period in consideration
avg_charsintAverage number of characters per message
-

Type

-

StatsGroupTopPoster

-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/statsURL.html b/data/corefork.telegram.org/constructor/statsURL.html deleted file mode 100644 index 64b4f7ed17..0000000000 --- a/data/corefork.telegram.org/constructor/statsURL.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - statsURL - - - - - - - - - - - - - -
- -
-
-
- -

statsURL

- -

URL with chat statistics

-

- -
-
statsURL#47a971e0 url:string = StatsURL;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
urlstringChat statistics
-

Type

-

StatsURL

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/stickerPack.html b/data/corefork.telegram.org/constructor/stickerPack.html deleted file mode 100644 index 80c9e0e579..0000000000 --- a/data/corefork.telegram.org/constructor/stickerPack.html +++ /dev/null @@ -1,156 +0,0 @@ - - - - - stickerPack - - - - - - - - - - - - - -
- -
-
-
- -

stickerPack

- -

A stickerpack is a group of stickers associated to the same emoji.
-It is not a sticker pack the way it is usually intended, you may be looking for a StickerSet.

-

- -
-
stickerPack#12b299d4 emoticon:string documents:Vector<long> = StickerPack;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
emoticonstringEmoji
documentsVector<long>Stickers
-

Type

-

StickerPack

-

Related pages

-

StickerSet

-

Represents a stickerset (stickerpack)

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/stickerSet.html b/data/corefork.telegram.org/constructor/stickerSet.html deleted file mode 100644 index 261c0749d3..0000000000 --- a/data/corefork.telegram.org/constructor/stickerSet.html +++ /dev/null @@ -1,217 +0,0 @@ - - - - - stickerSet - - - - - - - - - - - - - -
- -
-
-
- -

stickerSet

- -

Represents a stickerset (stickerpack)

-

- -
-
stickerSet#d7df217a flags:# archived:flags.1?true official:flags.2?true masks:flags.3?true animated:flags.5?true videos:flags.6?true installed_date:flags.0?int id:long access_hash:long title:string short_name:string thumbs:flags.4?Vector<PhotoSize> thumb_dc_id:flags.4?int thumb_version:flags.4?int count:int hash:int = StickerSet;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
archivedflags.1?trueWhether this stickerset was archived (due to too many saved stickers in the current account)
officialflags.2?trueIs this stickerset official
masksflags.3?trueIs this a mask stickerset
animatedflags.5?trueIs this an animated stickerpack
installed_dateflags.0?intWhen was this stickerset installed
idlongID of the stickerset
access_hashlongAccess hash of stickerset
titlestringTitle of stickerset
short_namestringShort name of stickerset to use in tg://addstickers?set=short_name
thumbsflags.4?Vector<PhotoSize>Stickerset thumbnail
thumb_dc_idflags.4?intDC ID of thumbnail
thumb_versionflags.4?intThumbnail version
countintNumber of stickers in pack
hashintHash
-

Type

-

StickerSet

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/stickerSetCovered.html b/data/corefork.telegram.org/constructor/stickerSetCovered.html deleted file mode 100644 index a8cc981d37..0000000000 --- a/data/corefork.telegram.org/constructor/stickerSetCovered.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - stickerSetCovered - - - - - - - - - - - - - -
- -
-
-
- -

stickerSetCovered

- -

Stickerset, with a specific sticker as preview

-

- -
-
stickerSetCovered#6410a5d2 set:StickerSet cover:Document = StickerSetCovered;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
setStickerSetStickerset
coverDocumentPreview
-

Type

-

StickerSetCovered

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/stickerSetMultiCovered.html b/data/corefork.telegram.org/constructor/stickerSetMultiCovered.html deleted file mode 100644 index 7a36c76919..0000000000 --- a/data/corefork.telegram.org/constructor/stickerSetMultiCovered.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - stickerSetMultiCovered - - - - - - - - - - - - - -
- -
-
-
- -

stickerSetMultiCovered

- -

Stickerset, with a specific stickers as preview

-

- -
-
stickerSetMultiCovered#3407e51b set:StickerSet covers:Vector<Document> = StickerSetCovered;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
setStickerSetStickerset
coversVector<Document>Preview stickers
-

Type

-

StickerSetCovered

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/stickers.suggestedShortName b/data/corefork.telegram.org/constructor/stickers.suggestedShortName deleted file mode 100644 index 31dac0cbb5..0000000000 --- a/data/corefork.telegram.org/constructor/stickers.suggestedShortName +++ /dev/null @@ -1,147 +0,0 @@ - - - - - stickers.suggestedShortName - - - - - - - - - - - - - -
- -
-
-
- -

stickers.suggestedShortName

- -

A suggested short name for a stickerpack

-

- -
-
stickers.suggestedShortName#85fea03f short_name:string = stickers.SuggestedShortName;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
short_namestringSuggested short name
-

Type

-

stickers.SuggestedShortName

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/storage.fileGif b/data/corefork.telegram.org/constructor/storage.fileGif deleted file mode 100644 index 6d20e196e6..0000000000 --- a/data/corefork.telegram.org/constructor/storage.fileGif +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.fileGif - - - - - - - - - - - - - -
- -
-
-
- -

storage.fileGif

- -

GIF image. MIME type: image/gif.

-

- -
-
storage.fileGif#cae1aadf = storage.FileType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

storage.FileType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/storage.fileJpeg b/data/corefork.telegram.org/constructor/storage.fileJpeg deleted file mode 100644 index 4f962ec872..0000000000 --- a/data/corefork.telegram.org/constructor/storage.fileJpeg +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.fileJpeg - - - - - - - - - - - - - -
- -
-
-
- -

storage.fileJpeg

- -

JPEG image. MIME type: image/jpeg.

-

- -
-
storage.fileJpeg#7efe0e = storage.FileType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

storage.FileType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/storage.fileMov b/data/corefork.telegram.org/constructor/storage.fileMov deleted file mode 100644 index 4ca319cb5b..0000000000 --- a/data/corefork.telegram.org/constructor/storage.fileMov +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.fileMov - - - - - - - - - - - - - -
- -
-
-
- -

storage.fileMov

- -

Quicktime video. MIME type: video/quicktime.

-

- -
-
storage.fileMov#4b09ebbc = storage.FileType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

storage.FileType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/storage.fileMp3 b/data/corefork.telegram.org/constructor/storage.fileMp3 deleted file mode 100644 index f139d32d29..0000000000 --- a/data/corefork.telegram.org/constructor/storage.fileMp3 +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.fileMp3 - - - - - - - - - - - - - -
- -
-
-
- -

storage.fileMp3

- -

Mp3 audio. MIME type: audio/mpeg.

-

- -
-
storage.fileMp3#528a0677 = storage.FileType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

storage.FileType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/storage.fileMp4 b/data/corefork.telegram.org/constructor/storage.fileMp4 deleted file mode 100644 index 71bc10738e..0000000000 --- a/data/corefork.telegram.org/constructor/storage.fileMp4 +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.fileMp4 - - - - - - - - - - - - - -
- -
-
-
- -

storage.fileMp4

- -

MPEG-4 video. MIME type: video/mp4.

-

- -
-
storage.fileMp4#b3cea0e4 = storage.FileType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

storage.FileType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/storage.filePartial b/data/corefork.telegram.org/constructor/storage.filePartial deleted file mode 100644 index cedfaf3186..0000000000 --- a/data/corefork.telegram.org/constructor/storage.filePartial +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.filePartial - - - - - - - - - - - - - -
- -
-
-
- -

storage.filePartial

- -

Part of a bigger file.

-

- -
-
storage.filePartial#40bc6f52 = storage.FileType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

storage.FileType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/storage.filePdf b/data/corefork.telegram.org/constructor/storage.filePdf deleted file mode 100644 index 5269693e55..0000000000 --- a/data/corefork.telegram.org/constructor/storage.filePdf +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.filePdf - - - - - - - - - - - - - -
- -
-
-
- -

storage.filePdf

- -

PDF document image. MIME type: application/pdf.

-

- -
-
storage.filePdf#ae1e508d = storage.FileType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

storage.FileType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/storage.filePng b/data/corefork.telegram.org/constructor/storage.filePng deleted file mode 100644 index d65ba5ce8d..0000000000 --- a/data/corefork.telegram.org/constructor/storage.filePng +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.filePng - - - - - - - - - - - - - -
- -
-
-
- -

storage.filePng

- -

PNG image. MIME type: image/png.

-

- -
-
storage.filePng#a4f63c0 = storage.FileType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

storage.FileType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/storage.fileUnknown b/data/corefork.telegram.org/constructor/storage.fileUnknown deleted file mode 100644 index cbbb38079c..0000000000 --- a/data/corefork.telegram.org/constructor/storage.fileUnknown +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.fileUnknown - - - - - - - - - - - - - -
- -
-
-
- -

storage.fileUnknown

- -

Unknown type.

-

- -
-
storage.fileUnknown#aa963b05 = storage.FileType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

storage.FileType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/storage.fileWebp b/data/corefork.telegram.org/constructor/storage.fileWebp deleted file mode 100644 index 3b5b0bb760..0000000000 --- a/data/corefork.telegram.org/constructor/storage.fileWebp +++ /dev/null @@ -1,132 +0,0 @@ - - - - - storage.fileWebp - - - - - - - - - - - - - -
- -
-
-
- -

storage.fileWebp

- -

WEBP image. MIME type: image/webp.

-

- -
-
storage.fileWebp#1081464c = storage.FileType;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

storage.FileType

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/textAnchor.html b/data/corefork.telegram.org/constructor/textAnchor.html deleted file mode 100644 index eb6e51014c..0000000000 --- a/data/corefork.telegram.org/constructor/textAnchor.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - textAnchor - - - - - - - - - - - - - -
- -
-
-
- -

textAnchor

- -

Text linking to another section of the page

-

- -
-
textAnchor#35553762 text:RichText name:string = RichText;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
namestringSection name
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/textBold.html b/data/corefork.telegram.org/constructor/textBold.html deleted file mode 100644 index 12d8027dfe..0000000000 --- a/data/corefork.telegram.org/constructor/textBold.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textBold - - - - - - - - - - - - - -
- -
-
-
- -

textBold

- -

Bold text

-

- -
-
textBold#6724abc4 text:RichText = RichText;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/textConcat.html b/data/corefork.telegram.org/constructor/textConcat.html deleted file mode 100644 index f6b5255cfd..0000000000 --- a/data/corefork.telegram.org/constructor/textConcat.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textConcat - - - - - - - - - - - - - -
- -
-
-
- -

textConcat

- -

Concatenation of rich texts

-

- -
-
textConcat#7e6260d7 texts:Vector<RichText> = RichText;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textsVector<RichText>Concatenated rich texts
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/textEmail.html b/data/corefork.telegram.org/constructor/textEmail.html deleted file mode 100644 index 870871a47a..0000000000 --- a/data/corefork.telegram.org/constructor/textEmail.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - textEmail - - - - - - - - - - - - - -
- -
-
-
- -

textEmail

- -

Rich text email link

-

- -
-
textEmail#de5a0dd6 text:RichText email:string = RichText;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextLink text
emailstringEmail address
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/textEmpty.html b/data/corefork.telegram.org/constructor/textEmpty.html deleted file mode 100644 index 85c83a202b..0000000000 --- a/data/corefork.telegram.org/constructor/textEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - textEmpty - - - - - - - - - - - - - -
- -
-
-
- -

textEmpty

- -

Empty rich text element

-

- -
-
textEmpty#dc3d824f = RichText;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/textFixed.html b/data/corefork.telegram.org/constructor/textFixed.html deleted file mode 100644 index 0a28768955..0000000000 --- a/data/corefork.telegram.org/constructor/textFixed.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textFixed - - - - - - - - - - - - - -
- -
-
-
- -

textFixed

- -

fixed-width rich text

-

- -
-
textFixed#6c3f19b9 text:RichText = RichText;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/textImage.html b/data/corefork.telegram.org/constructor/textImage.html deleted file mode 100644 index 7e1832cd9d..0000000000 --- a/data/corefork.telegram.org/constructor/textImage.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - textImage - - - - - - - - - - - - - -
- -
-
-
- -

textImage

- -

Inline image

-

- -
-
textImage#81ccf4f document_id:long w:int h:int = RichText;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
document_idlongDocument ID
wintWidth
hintHeight
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/textItalic.html b/data/corefork.telegram.org/constructor/textItalic.html deleted file mode 100644 index af65d3fa3f..0000000000 --- a/data/corefork.telegram.org/constructor/textItalic.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textItalic - - - - - - - - - - - - - -
- -
-
-
- -

textItalic

- -

Italic text

-

- -
-
textItalic#d912a59c text:RichText = RichText;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/textMarked.html b/data/corefork.telegram.org/constructor/textMarked.html deleted file mode 100644 index 37c23b17de..0000000000 --- a/data/corefork.telegram.org/constructor/textMarked.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textMarked - - - - - - - - - - - - - -
- -
-
-
- -

textMarked

- -

Highlighted text

-

- -
-
textMarked#34b8621 text:RichText = RichText;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/textPhone.html b/data/corefork.telegram.org/constructor/textPhone.html deleted file mode 100644 index 34ae633585..0000000000 --- a/data/corefork.telegram.org/constructor/textPhone.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - textPhone - - - - - - - - - - - - - -
- -
-
-
- -

textPhone

- -

Rich text linked to a phone number

-

- -
-
textPhone#1ccb966a text:RichText phone:string = RichText;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
phonestringPhone number
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/textPlain.html b/data/corefork.telegram.org/constructor/textPlain.html deleted file mode 100644 index c19e8c0749..0000000000 --- a/data/corefork.telegram.org/constructor/textPlain.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textPlain - - - - - - - - - - - - - -
- -
-
-
- -

textPlain

- -

Plain text

-

- -
-
textPlain#744694e0 text:string = RichText;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textstringText
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/textStrike.html b/data/corefork.telegram.org/constructor/textStrike.html deleted file mode 100644 index efc97596bb..0000000000 --- a/data/corefork.telegram.org/constructor/textStrike.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textStrike - - - - - - - - - - - - - -
- -
-
-
- -

textStrike

- -

Strikethrough text

-

- -
-
textStrike#9bf8bb95 text:RichText = RichText;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/textSubscript.html b/data/corefork.telegram.org/constructor/textSubscript.html deleted file mode 100644 index 57b371b799..0000000000 --- a/data/corefork.telegram.org/constructor/textSubscript.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textSubscript - - - - - - - - - - - - - -
- -
-
-
- -

textSubscript

- -

Subscript text

-

- -
-
textSubscript#ed6a8504 text:RichText = RichText;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/textSuperscript.html b/data/corefork.telegram.org/constructor/textSuperscript.html deleted file mode 100644 index 57d81c0db4..0000000000 --- a/data/corefork.telegram.org/constructor/textSuperscript.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textSuperscript - - - - - - - - - - - - - -
- -
-
-
- -

textSuperscript

- -

Superscript text

-

- -
-
textSuperscript#c7fb5e01 text:RichText = RichText;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/textUnderline.html b/data/corefork.telegram.org/constructor/textUnderline.html deleted file mode 100644 index ced69f125c..0000000000 --- a/data/corefork.telegram.org/constructor/textUnderline.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - textUnderline - - - - - - - - - - - - - -
- -
-
-
- -

textUnderline

- -

Underlined text

-

- -
-
textUnderline#c12622c4 text:RichText = RichText;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/textUrl.html b/data/corefork.telegram.org/constructor/textUrl.html deleted file mode 100644 index 61a5ad185f..0000000000 --- a/data/corefork.telegram.org/constructor/textUrl.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - textUrl - - - - - - - - - - - - - -
- -
-
-
- -

textUrl

- -

Link

-

- -
-
textUrl#3c2884c1 text:RichText url:string webpage_id:long = RichText;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
textRichTextText of link
urlstringWebpage HTTP URL
webpage_idlongIf a preview was already generated for the page, the page ID
-

Type

-

RichText

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/theme.html b/data/corefork.telegram.org/constructor/theme.html deleted file mode 100644 index cf39643f87..0000000000 --- a/data/corefork.telegram.org/constructor/theme.html +++ /dev/null @@ -1,197 +0,0 @@ - - - - - theme - - - - - - - - - - - - - -
- -
-
-
- -

theme

- -

Theme

-

- -
-
theme#e802b8dc flags:# creator:flags.0?true default:flags.1?true for_chat:flags.5?true id:long access_hash:long slug:string title:string document:flags.2?Document settings:flags.3?ThemeSettings installs_count:flags.4?int = Theme;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
creatorflags.0?trueWhether the current user is the creator of this theme
defaultflags.1?trueWhether this is the default theme
for_chatflags.5?trueWhether this theme is meant to be used as a chat theme
idlongTheme ID
access_hashlongTheme access hash
slugstringUnique theme ID
titlestringTheme name
documentflags.2?DocumentTheme
settingsflags.3?ThemeSettingsTheme settings
installs_countflags.4?intInstallation count
-

Type

-

Theme

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/topPeer.html b/data/corefork.telegram.org/constructor/topPeer.html deleted file mode 100644 index aae8b55857..0000000000 --- a/data/corefork.telegram.org/constructor/topPeer.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - topPeer - - - - - - - - - - - - - -
- -
-
-
- -

topPeer

- -

Top peer

-

- -
-
topPeer#edcdc05b peer:Peer rating:double = TopPeer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerPeer
ratingdoubleRating as computed in top peer rating »
-

Type

-

TopPeer

-

Related pages

-

Top peer rating

-

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/topPeerCategoryBotsInline.html b/data/corefork.telegram.org/constructor/topPeerCategoryBotsInline.html deleted file mode 100644 index 88a29e8c29..0000000000 --- a/data/corefork.telegram.org/constructor/topPeerCategoryBotsInline.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryBotsInline - - - - - - - - - - - - - -
- -
-
-
- -

topPeerCategoryBotsInline

- -

Most used inline bots

-

- -
-
topPeerCategoryBotsInline#148677e2 = TopPeerCategory;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

TopPeerCategory

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/topPeerCategoryBotsPM.html b/data/corefork.telegram.org/constructor/topPeerCategoryBotsPM.html deleted file mode 100644 index 7555aa5b7b..0000000000 --- a/data/corefork.telegram.org/constructor/topPeerCategoryBotsPM.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryBotsPM - - - - - - - - - - - - - -
- -
-
-
- -

topPeerCategoryBotsPM

- -

Most used bots

-

- -
-
topPeerCategoryBotsPM#ab661b5b = TopPeerCategory;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

TopPeerCategory

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/topPeerCategoryChannels.html b/data/corefork.telegram.org/constructor/topPeerCategoryChannels.html deleted file mode 100644 index 6e95852db4..0000000000 --- a/data/corefork.telegram.org/constructor/topPeerCategoryChannels.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryChannels - - - - - - - - - - - - - -
- -
-
-
- -

topPeerCategoryChannels

- -

Most frequently visited channels

-

- -
-
topPeerCategoryChannels#161d9628 = TopPeerCategory;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

TopPeerCategory

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/topPeerCategoryCorrespondents.html b/data/corefork.telegram.org/constructor/topPeerCategoryCorrespondents.html deleted file mode 100644 index 8d8c2a2863..0000000000 --- a/data/corefork.telegram.org/constructor/topPeerCategoryCorrespondents.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryCorrespondents - - - - - - - - - - - - - -
- -
-
-
- -

topPeerCategoryCorrespondents

- -

Users we've chatted most frequently with

-

- -
-
topPeerCategoryCorrespondents#637b7ed = TopPeerCategory;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

TopPeerCategory

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/topPeerCategoryForwardChats.html b/data/corefork.telegram.org/constructor/topPeerCategoryForwardChats.html deleted file mode 100644 index 27ccb1b3b0..0000000000 --- a/data/corefork.telegram.org/constructor/topPeerCategoryForwardChats.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryForwardChats - - - - - - - - - - - - - -
- -
-
-
- -

topPeerCategoryForwardChats

- -

Chats to which the users often forwards messages to

-

- -
-
topPeerCategoryForwardChats#fbeec0f0 = TopPeerCategory;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

TopPeerCategory

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/topPeerCategoryForwardUsers.html b/data/corefork.telegram.org/constructor/topPeerCategoryForwardUsers.html deleted file mode 100644 index 28f0729f2f..0000000000 --- a/data/corefork.telegram.org/constructor/topPeerCategoryForwardUsers.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryForwardUsers - - - - - - - - - - - - - -
- -
-
-
- -

topPeerCategoryForwardUsers

- -

Users to which the users often forwards messages to

-

- -
-
topPeerCategoryForwardUsers#a8406ca9 = TopPeerCategory;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

TopPeerCategory

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/topPeerCategoryGroups.html b/data/corefork.telegram.org/constructor/topPeerCategoryGroups.html deleted file mode 100644 index ec756ecbb1..0000000000 --- a/data/corefork.telegram.org/constructor/topPeerCategoryGroups.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryGroups - - - - - - - - - - - - - -
- -
-
-
- -

topPeerCategoryGroups

- -

Often-opened groups and supergroups

-

- -
-
topPeerCategoryGroups#bd17a14a = TopPeerCategory;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

TopPeerCategory

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/topPeerCategoryPeers.html b/data/corefork.telegram.org/constructor/topPeerCategoryPeers.html deleted file mode 100644 index 2116bc8758..0000000000 --- a/data/corefork.telegram.org/constructor/topPeerCategoryPeers.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - topPeerCategoryPeers - - - - - - - - - - - - - -
- -
-
-
- -

topPeerCategoryPeers

- -

Top peer category

-

- -
-
topPeerCategoryPeers#fb834291 category:TopPeerCategory count:int peers:Vector<TopPeer> = TopPeerCategoryPeers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
categoryTopPeerCategoryTop peer category of peers
countintCount of peers
peersVector<TopPeer>Peers
-

Type

-

TopPeerCategoryPeers

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/topPeerCategoryPhoneCalls.html b/data/corefork.telegram.org/constructor/topPeerCategoryPhoneCalls.html deleted file mode 100644 index 85a5d09006..0000000000 --- a/data/corefork.telegram.org/constructor/topPeerCategoryPhoneCalls.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - topPeerCategoryPhoneCalls - - - - - - - - - - - - - -
- -
-
-
- -

topPeerCategoryPhoneCalls

- -

Most frequently called users

-

- -
-
topPeerCategoryPhoneCalls#1e76a78c = TopPeerCategory;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

TopPeerCategory

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/true.html b/data/corefork.telegram.org/constructor/true.html deleted file mode 100644 index 401f973fb1..0000000000 --- a/data/corefork.telegram.org/constructor/true.html +++ /dev/null @@ -1,134 +0,0 @@ - - - - - true - - - - - - - - - - - - - -
- -
-
-
- -

true

- -

See predefined identifiers.

-

- -
-
true#3fedd339 = True;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

True

-

Related pages

-

TL-formal

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateBotCallbackQuery.html b/data/corefork.telegram.org/constructor/updateBotCallbackQuery.html deleted file mode 100644 index 99bf31279c..0000000000 --- a/data/corefork.telegram.org/constructor/updateBotCallbackQuery.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - updateBotCallbackQuery - - - - - - - - - - - - - -
- -
-
-
- -

updateBotCallbackQuery

- -

A callback button was pressed, and the button data was sent to the bot that created the button

-

- -
-
updateBotCallbackQuery#b9cfc48d flags:# query_id:long user_id:long peer:Peer msg_id:int chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
query_idlongQuery ID
user_idlongID of the user that pressed the button
peerPeerChat where the inline keyboard was sent
msg_idintMessage ID
chat_instancelongGlobal identifier, uniquely corresponding to the chat to which the message with the callback button was sent. Useful for high scores in games.
dataflags.0?bytesCallback data
game_short_nameflags.1?stringShort name of a Game to be returned, serves as the unique identifier for the game
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateBotCommands.html b/data/corefork.telegram.org/constructor/updateBotCommands.html deleted file mode 100644 index 8b1023926a..0000000000 --- a/data/corefork.telegram.org/constructor/updateBotCommands.html +++ /dev/null @@ -1,159 +0,0 @@ - - - - - updateBotCommands - - - - - - - - - - - - - -
- -
-
-
- -

updateBotCommands

- -

The command set of a certain bot in a certain chat has changed.

-

- -
-
updateBotCommands#4d712f2e peer:Peer bot_id:long commands:Vector<BotCommand> = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerThe affected chat
bot_idlongID of the bot that changed its command set
commandsVector<BotCommand>New bot commands
-

Type

-

Update

-

Related pages

-

Telegram Bot API

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateBotInlineQuery.html b/data/corefork.telegram.org/constructor/updateBotInlineQuery.html deleted file mode 100644 index c22796dec6..0000000000 --- a/data/corefork.telegram.org/constructor/updateBotInlineQuery.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - updateBotInlineQuery - - - - - - - - - - - - - -
- -
-
-
- -

updateBotInlineQuery

- -

An incoming inline query

-

- -
-
updateBotInlineQuery#496f379c flags:# query_id:long user_id:long query:string geo:flags.0?GeoPoint peer_type:flags.1?InlineQueryPeerType offset:string = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
query_idlongQuery ID
user_idlongUser that sent the query
querystringText of query
geoflags.0?GeoPointAttached geolocation
peer_typeflags.1?InlineQueryPeerTypeType of the chat from which the inline query was sent.
offsetstringOffset to navigate through results
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateBotInlineSend.html b/data/corefork.telegram.org/constructor/updateBotInlineSend.html deleted file mode 100644 index 24453e582b..0000000000 --- a/data/corefork.telegram.org/constructor/updateBotInlineSend.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - updateBotInlineSend - - - - - - - - - - - - - -
- -
-
-
- -

updateBotInlineSend

- -

The result of an inline query that was chosen by a user and sent to their chat partner. Please see our documentation on the feedback collecting for details on how to enable these updates for your bot.

-

- -
-
updateBotInlineSend#12f12a07 flags:# user_id:long query:string geo:flags.0?GeoPoint id:string msg_id:flags.1?InputBotInlineMessageID = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
user_idlongThe user that chose the result
querystringThe query that was used to obtain the result
geoflags.0?GeoPointOptional. Sender location, only for bots that require user location
idstringThe unique identifier for the result that was chosen
msg_idflags.1?InputBotInlineMessageIDIdentifier of the sent inline message. Available only if there is an inline keyboard attached to the message. Will be also received in callback queries and can be used to edit the message.
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateBotPrecheckoutQuery.html b/data/corefork.telegram.org/constructor/updateBotPrecheckoutQuery.html deleted file mode 100644 index e31f377500..0000000000 --- a/data/corefork.telegram.org/constructor/updateBotPrecheckoutQuery.html +++ /dev/null @@ -1,184 +0,0 @@ - - - - - updateBotPrecheckoutQuery - - - - - - - - - - - - - -
- -
-
-
- -

updateBotPrecheckoutQuery

- -

This object contains information about an incoming pre-checkout query.

-

- -
-
updateBotPrecheckoutQuery#8caa9a96 flags:# query_id:long user_id:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string currency:string total_amount:long = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
query_idlongUnique query identifier
user_idlongUser who sent the query
payloadbytesBot specified invoice payload
infoflags.0?PaymentRequestedInfoOrder info provided by the user
shipping_option_idflags.1?stringIdentifier of the shipping option chosen by the user
currencystringThree-letter ISO 4217 currency code
total_amountlongTotal amount in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
-

Type

-

Update

-

Related pages

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateBotStopped.html b/data/corefork.telegram.org/constructor/updateBotStopped.html deleted file mode 100644 index 5385713051..0000000000 --- a/data/corefork.telegram.org/constructor/updateBotStopped.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - updateBotStopped - - - - - - - - - - - - - -
- -
-
-
- -

updateBotStopped

- -

A bot was stopped or re-started.

-

- -
-
updateBotStopped#c4870a49 user_id:long date:int stopped:Bool qts:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongThe bot ID
dateintWhen did this action occur
stoppedBoolWhether the bot was stopped or started
qtsintNew qts value, see updates » for more info.
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateBotWebhookJSON.html b/data/corefork.telegram.org/constructor/updateBotWebhookJSON.html deleted file mode 100644 index dd2feedf53..0000000000 --- a/data/corefork.telegram.org/constructor/updateBotWebhookJSON.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateBotWebhookJSON - - - - - - - - - - - - - -
- -
-
-
- -

updateBotWebhookJSON

- -

A new incoming event; for bots only

-

- -
-
updateBotWebhookJSON#8317c0c3 data:DataJSON = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
dataDataJSONThe event
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateBotWebhookJSONQuery.html b/data/corefork.telegram.org/constructor/updateBotWebhookJSONQuery.html deleted file mode 100644 index 02145f548a..0000000000 --- a/data/corefork.telegram.org/constructor/updateBotWebhookJSONQuery.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateBotWebhookJSONQuery - - - - - - - - - - - - - -
- -
-
-
- -

updateBotWebhookJSONQuery

- -

A new incoming query; for bots only

-

- -
-
updateBotWebhookJSONQuery#9b9240a6 query_id:long data:DataJSON timeout:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
query_idlongQuery identifier
dataDataJSONQuery data
timeoutintQuery timeout
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateChannel.html b/data/corefork.telegram.org/constructor/updateChannel.html deleted file mode 100644 index d0dc034fba..0000000000 --- a/data/corefork.telegram.org/constructor/updateChannel.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateChannel - - - - - - - - - - - - - -
- -
-
-
- -

updateChannel

- -

A new channel is available

-

- -
-
updateChannel#635b4c09 channel_id:long = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
channel_idlongChannel ID
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateChannelAvailableMessages.html b/data/corefork.telegram.org/constructor/updateChannelAvailableMessages.html deleted file mode 100644 index fa52c5e555..0000000000 --- a/data/corefork.telegram.org/constructor/updateChannelAvailableMessages.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - updateChannelAvailableMessages - - - - - - - - - - - - - -
- -
-
-
- -

updateChannelAvailableMessages

- -

The history of a channel/supergroup was hidden.

-

- -
-
updateChannelAvailableMessages#b23fc698 channel_id:long available_min_id:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idlongChannel/supergroup ID
available_min_idintIdentifier of a maximum unavailable message in a channel due to hidden history.
-

Type

-

Update

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateChannelMessageForwards.html b/data/corefork.telegram.org/constructor/updateChannelMessageForwards.html deleted file mode 100644 index 4a55198265..0000000000 --- a/data/corefork.telegram.org/constructor/updateChannelMessageForwards.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateChannelMessageForwards - - - - - - - - - - - - - -
- -
-
-
- -

updateChannelMessageForwards

- -

The forward counter of a message in a channel has changed

-

- -
-
updateChannelMessageForwards#d29a27f4 channel_id:long id:int forwards:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idlongChannel ID
idintID of the message
forwardsintNew forward counter
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateChannelMessageViews.html b/data/corefork.telegram.org/constructor/updateChannelMessageViews.html deleted file mode 100644 index fbf2f7e872..0000000000 --- a/data/corefork.telegram.org/constructor/updateChannelMessageViews.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateChannelMessageViews - - - - - - - - - - - - - -
- -
-
-
- -

updateChannelMessageViews

- -

The view counter of a message in a channel has changed

-

- -
-
updateChannelMessageViews#f226ac08 channel_id:long id:int views:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idlongChannel ID
idintID of the message
viewsintNew view counter
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateChannelParticipant.html b/data/corefork.telegram.org/constructor/updateChannelParticipant.html deleted file mode 100644 index 6fcd8fba6a..0000000000 --- a/data/corefork.telegram.org/constructor/updateChannelParticipant.html +++ /dev/null @@ -1,192 +0,0 @@ - - - - - updateChannelParticipant - - - - - - - - - - - - - -
- -
-
-
- -

updateChannelParticipant

- -

A participant has left, joined, was banned or admined in a channel or supergroup.

-

- -
-
updateChannelParticipant#985d3abb flags:# channel_id:long date:int actor_id:long user_id:long prev_participant:flags.0?ChannelParticipant new_participant:flags.1?ChannelParticipant invite:flags.2?ExportedChatInvite qts:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
channel_idlongChannel ID
dateintDate of the event
actor_idlongUser that triggered the change (inviter, admin that kicked the user, or the even the user_id itself)
user_idlongUser that was affected by the change
prev_participantflags.0?ChannelParticipantPrevious participant status
new_participantflags.1?ChannelParticipantNew participant status
inviteflags.2?ExportedChatInviteChat invite used to join the channel/supergroup
qtsintNew qts value, see updates » for more info.
-

Type

-

Update

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateChannelReadMessagesContents.html b/data/corefork.telegram.org/constructor/updateChannelReadMessagesContents.html deleted file mode 100644 index 0bdf8cb8c2..0000000000 --- a/data/corefork.telegram.org/constructor/updateChannelReadMessagesContents.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - updateChannelReadMessagesContents - - - - - - - - - - - - - -
- -
-
-
- -

updateChannelReadMessagesContents

- -

The specified channel/supergroup messages were read

-

- -
-
updateChannelReadMessagesContents#44bdd535 channel_id:long messages:Vector<int> = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idlongChannel/supergroup ID
messagesVector<int>IDs of messages that were read
-

Type

-

Update

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateChannelTooLong.html b/data/corefork.telegram.org/constructor/updateChannelTooLong.html deleted file mode 100644 index 2b68b20de0..0000000000 --- a/data/corefork.telegram.org/constructor/updateChannelTooLong.html +++ /dev/null @@ -1,161 +0,0 @@ - - - - - updateChannelTooLong - - - - - - - - - - - - - -
- -
-
-
- -

updateChannelTooLong

- -

There are new updates in the specified channel, the client must fetch them.
-If the difference is too long or if the channel isn't currently in the states, start fetching from the specified pts.

-

- -
-
updateChannelTooLong#108d941f flags:# channel_id:long pts:flags.0?int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
channel_idlongThe channel
ptsflags.0?intThe PTS.
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateChannelUserTyping.html b/data/corefork.telegram.org/constructor/updateChannelUserTyping.html deleted file mode 100644 index 9d3e0d204a..0000000000 --- a/data/corefork.telegram.org/constructor/updateChannelUserTyping.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - updateChannelUserTyping - - - - - - - - - - - - - -
- -
-
-
- -

updateChannelUserTyping

- -

A user is typing in a supergroup, channel or message thread

-

- -
-
updateChannelUserTyping#8c88c923 flags:# channel_id:long top_msg_id:flags.0?int from_id:Peer action:SendMessageAction = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
channel_idlongChannel ID
top_msg_idflags.0?intThread ID
from_idPeerThe peer that is typing
actionSendMessageActionWhether the user is typing, sending a media or doing something else
-

Type

-

Update

-

Related pages

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateChannelWebPage.html b/data/corefork.telegram.org/constructor/updateChannelWebPage.html deleted file mode 100644 index f34e9f7dab..0000000000 --- a/data/corefork.telegram.org/constructor/updateChannelWebPage.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - updateChannelWebPage - - - - - - - - - - - - - -
- -
-
-
- -

updateChannelWebPage

- -

A webpage preview of a link in a channel/supergroup message was generated

-

- -
-
updateChannelWebPage#2f2ba99f channel_id:long webpage:WebPage pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idlongChannel/supergroup ID
webpageWebPageGenerated webpage preview
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateChat.html b/data/corefork.telegram.org/constructor/updateChat.html deleted file mode 100644 index b06c3897a7..0000000000 --- a/data/corefork.telegram.org/constructor/updateChat.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateChat - - - - - - - - - - - - - -
- -
-
-
- -

updateChat

- -

A new chat is available

-

- -
-
updateChat#f89a6a4e chat_id:long = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongChat ID
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateChatDefaultBannedRights.html b/data/corefork.telegram.org/constructor/updateChatDefaultBannedRights.html deleted file mode 100644 index b35b71873f..0000000000 --- a/data/corefork.telegram.org/constructor/updateChatDefaultBannedRights.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - updateChatDefaultBannedRights - - - - - - - - - - - - - -
- -
-
-
- -

updateChatDefaultBannedRights

- -

Default banned rights in a normal chat were updated

-

- -
-
updateChatDefaultBannedRights#54c01850 peer:Peer default_banned_rights:ChatBannedRights version:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerThe chat
default_banned_rightsChatBannedRightsNew default banned rights
versionintVersion
-

Type

-

Update

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateChatParticipant.html b/data/corefork.telegram.org/constructor/updateChatParticipant.html deleted file mode 100644 index d5e350aa31..0000000000 --- a/data/corefork.telegram.org/constructor/updateChatParticipant.html +++ /dev/null @@ -1,192 +0,0 @@ - - - - - updateChatParticipant - - - - - - - - - - - - - -
- -
-
-
- -

updateChatParticipant

- -

A user has joined or left a specific chat

-

- -
-
updateChatParticipant#d087663a flags:# chat_id:long date:int actor_id:long user_id:long prev_participant:flags.0?ChatParticipant new_participant:flags.1?ChatParticipant invite:flags.2?ExportedChatInvite qts:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
chat_idlongChat ID
dateintWhen did this event occur
actor_idlongUser that triggered the change (inviter, admin that kicked the user, or the even the user_id itself)
user_idlongUser that was affected by the change
prev_participantflags.0?ChatParticipantPrevious participant info (empty if this participant just joined)
new_participantflags.1?ChatParticipantNew participant info (empty if this participant just left)
inviteflags.2?ExportedChatInviteThe invite that was used to join the group
qtsintNew qts value, see updates » for more info.
-

Type

-

Update

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateChatParticipantAdd.html b/data/corefork.telegram.org/constructor/updateChatParticipantAdd.html deleted file mode 100644 index 101e416071..0000000000 --- a/data/corefork.telegram.org/constructor/updateChatParticipantAdd.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - updateChatParticipantAdd - - - - - - - - - - - - - -
- -
-
-
- -

updateChatParticipantAdd

- -

New group member.

-

- -
-
updateChatParticipantAdd#3dda5451 chat_id:long user_id:long inviter_id:long date:int version:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongGroup ID
user_idlongID of the new member
inviter_idlongID of the user, who added member to the group
dateintWhen was the participant added
versionintChat version number
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateChatParticipantAdmin.html b/data/corefork.telegram.org/constructor/updateChatParticipantAdmin.html deleted file mode 100644 index 28bd60ad40..0000000000 --- a/data/corefork.telegram.org/constructor/updateChatParticipantAdmin.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - updateChatParticipantAdmin - - - - - - - - - - - - - -
- -
-
-
- -

updateChatParticipantAdmin

- -

Admin permissions of a user in a legacy group were changed

-

- -
-
updateChatParticipantAdmin#d7ca61a2 chat_id:long user_id:long is_admin:Bool version:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongChat ID
user_idlongID of the (de)admined user
is_adminBoolWhether the user was rendered admin
versionintUsed in basic groups to reorder updates and make sure that all of them was received.
-

Type

-

Update

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateChatParticipants.html b/data/corefork.telegram.org/constructor/updateChatParticipants.html deleted file mode 100644 index 77e959f561..0000000000 --- a/data/corefork.telegram.org/constructor/updateChatParticipants.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateChatParticipants - - - - - - - - - - - - - -
- -
-
-
- -

updateChatParticipants

- -

Composition of chat participants changed.

-

- -
-
updateChatParticipants#7761198 participants:ChatParticipants = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
participantsChatParticipantsUpdated chat participants
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateChatUserTyping.html b/data/corefork.telegram.org/constructor/updateChatUserTyping.html deleted file mode 100644 index 221951c518..0000000000 --- a/data/corefork.telegram.org/constructor/updateChatUserTyping.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - updateChatUserTyping - - - - - - - - - - - - - -
- -
-
-
- -

updateChatUserTyping

- -

The user is preparing a message in a group; typing, recording, uploading, etc. This update is valid for 6 seconds. If no repeated update received after 6 seconds, it should be considered that the user stopped doing whatever he's been doing.

-

- -
-
updateChatUserTyping#83487af0 chat_id:long from_id:Peer action:SendMessageAction = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongGroup id
from_idPeerPeer that started typing (can be the chat itself, in case of anonymous admins).
actionSendMessageActionType of action
Parameter added in Layer 17.
-

Type

-

Update

-

Related pages

-

Layers

-

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateConfig.html b/data/corefork.telegram.org/constructor/updateConfig.html deleted file mode 100644 index d5d414be9c..0000000000 --- a/data/corefork.telegram.org/constructor/updateConfig.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - updateConfig - - - - - - - - - - - - - -
- -
-
-
- -

updateConfig

- -

The server-side configuration has changed; the client should re-fetch the config using help.getConfig

-

- -
-
updateConfig#a229dd06 = Update;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Update

-

Related pages

-

help.getConfig

-

Returns current configuration, including data center configuration.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateContactsReset.html b/data/corefork.telegram.org/constructor/updateContactsReset.html deleted file mode 100644 index 38c655f8d4..0000000000 --- a/data/corefork.telegram.org/constructor/updateContactsReset.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - updateContactsReset - - - - - - - - - - - - - -
- -
-
-
- -

updateContactsReset

- -

All contacts were deleted

-

- -
-
updateContactsReset#7084a7be = Update;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateDcOptions.html b/data/corefork.telegram.org/constructor/updateDcOptions.html deleted file mode 100644 index 2deded5beb..0000000000 --- a/data/corefork.telegram.org/constructor/updateDcOptions.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateDcOptions - - - - - - - - - - - - - -
- -
-
-
- -

updateDcOptions

- -

Changes in the data center configuration options.

-

- -
-
updateDcOptions#8e5e9873 dc_options:Vector<DcOption> = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
dc_optionsVector<DcOption>New connection options
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateDeleteChannelMessages.html b/data/corefork.telegram.org/constructor/updateDeleteChannelMessages.html deleted file mode 100644 index 99b2c39fbb..0000000000 --- a/data/corefork.telegram.org/constructor/updateDeleteChannelMessages.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - updateDeleteChannelMessages - - - - - - - - - - - - - -
- -
-
-
- -

updateDeleteChannelMessages

- -

Some messages in a supergroup/channel were deleted

-

- -
-
updateDeleteChannelMessages#c32d5b12 channel_id:long messages:Vector<int> pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idlongChannel ID
messagesVector<int>IDs of messages that were deleted
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateDeleteMessages.html b/data/corefork.telegram.org/constructor/updateDeleteMessages.html deleted file mode 100644 index dc60c375cb..0000000000 --- a/data/corefork.telegram.org/constructor/updateDeleteMessages.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - updateDeleteMessages - - - - - - - - - - - - - -
- -
-
-
- -

updateDeleteMessages

- -

Messages were deleted.

-

- -
-
updateDeleteMessages#a20db0e5 messages:Vector<int> pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messagesVector<int>List of identifiers of deleted messages
ptsintNew quality of actions in a message box
pts_countintNumber of generated events
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateDialogFilter.html b/data/corefork.telegram.org/constructor/updateDialogFilter.html deleted file mode 100644 index 2731c3ce3b..0000000000 --- a/data/corefork.telegram.org/constructor/updateDialogFilter.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - updateDialogFilter - - - - - - - - - - - - - -
- -
-
-
- -

updateDialogFilter

- -

A new folder was added

-

- -
-
updateDialogFilter#26ffde7d flags:# id:int filter:flags.0?DialogFilter = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idintFolder ID
filterflags.0?DialogFilterFolder info
-

Type

-

Update

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateDialogFilterOrder.html b/data/corefork.telegram.org/constructor/updateDialogFilterOrder.html deleted file mode 100644 index 8728715ab0..0000000000 --- a/data/corefork.telegram.org/constructor/updateDialogFilterOrder.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - updateDialogFilterOrder - - - - - - - - - - - - - -
- -
-
-
- -

updateDialogFilterOrder

- -

New folder order

-

- -
-
updateDialogFilterOrder#a5d72105 order:Vector<int> = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
orderVector<int>Ordered folder IDs
-

Type

-

Update

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateDialogFilters.html b/data/corefork.telegram.org/constructor/updateDialogFilters.html deleted file mode 100644 index 0be8003fbf..0000000000 --- a/data/corefork.telegram.org/constructor/updateDialogFilters.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - updateDialogFilters - - - - - - - - - - - - - -
- -
-
-
- -

updateDialogFilters

- -

Clients should update folder info

-

- -
-
updateDialogFilters#3504914f = Update;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Update

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateDialogPinned.html b/data/corefork.telegram.org/constructor/updateDialogPinned.html deleted file mode 100644 index 843896dfd9..0000000000 --- a/data/corefork.telegram.org/constructor/updateDialogPinned.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - updateDialogPinned - - - - - - - - - - - - - -
- -
-
-
- -

updateDialogPinned

- -

A dialog was pinned/unpinned

-

- -
-
updateDialogPinned#6e6fe51c flags:# pinned:flags.0?true folder_id:flags.1?int peer:DialogPeer = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.0?trueWhether the dialog was pinned
folder_idflags.1?intPeer folder ID, for more info click here
peerDialogPeerThe dialog
-

Type

-

Update

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateDialogUnreadMark.html b/data/corefork.telegram.org/constructor/updateDialogUnreadMark.html deleted file mode 100644 index 22000cf2ac..0000000000 --- a/data/corefork.telegram.org/constructor/updateDialogUnreadMark.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateDialogUnreadMark - - - - - - - - - - - - - -
- -
-
-
- -

updateDialogUnreadMark

- -

The manual unread mark of a chat was changed

-

- -
-
updateDialogUnreadMark#e16459c3 flags:# unread:flags.0?true peer:DialogPeer = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
unreadflags.0?trueWas the chat marked or unmarked as read
peerDialogPeerThe dialog
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateDraftMessage.html b/data/corefork.telegram.org/constructor/updateDraftMessage.html deleted file mode 100644 index 9610f47e00..0000000000 --- a/data/corefork.telegram.org/constructor/updateDraftMessage.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - updateDraftMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateDraftMessage

- -

Notifies a change of a message draft.

-

- -
-
updateDraftMessage#ee2bb969 peer:Peer draft:DraftMessage = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerThe peer to which the draft is associated
draftDraftMessageThe draft
-

Type

-

Update

-

Related pages

-

Message drafts

-

How to handle message drafts

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateEditChannelMessage.html b/data/corefork.telegram.org/constructor/updateEditChannelMessage.html deleted file mode 100644 index 6132316bea..0000000000 --- a/data/corefork.telegram.org/constructor/updateEditChannelMessage.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - updateEditChannelMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateEditChannelMessage

- -

A message was edited in a channel/supergroup

-

- -
-
updateEditChannelMessage#1b3f4df7 message:Message pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageThe new message
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateEditMessage.html b/data/corefork.telegram.org/constructor/updateEditMessage.html deleted file mode 100644 index 14b412e1bc..0000000000 --- a/data/corefork.telegram.org/constructor/updateEditMessage.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - updateEditMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateEditMessage

- -

A message was edited

-

- -
-
updateEditMessage#e40370a3 message:Message pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageThe new edited message
ptsintPTS
pts_countintPTS count
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateEncryptedChatTyping.html b/data/corefork.telegram.org/constructor/updateEncryptedChatTyping.html deleted file mode 100644 index d8176f8591..0000000000 --- a/data/corefork.telegram.org/constructor/updateEncryptedChatTyping.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateEncryptedChatTyping - - - - - - - - - - - - - -
- -
-
-
- -

updateEncryptedChatTyping

- -

Interlocutor is typing a message in an encrypted chat. Update period is 6 second. If upon this time there is no repeated update, it shall be considered that the interlocutor stopped typing.

-

- -
-
updateEncryptedChatTyping#1710f156 chat_id:int = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chat_idintChat ID
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateEncryptedMessagesRead.html b/data/corefork.telegram.org/constructor/updateEncryptedMessagesRead.html deleted file mode 100644 index 1ba6bb6c94..0000000000 --- a/data/corefork.telegram.org/constructor/updateEncryptedMessagesRead.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateEncryptedMessagesRead - - - - - - - - - - - - - -
- -
-
-
- -

updateEncryptedMessagesRead

- -

Communication history in an encrypted chat was marked as read.

-

- -
-
updateEncryptedMessagesRead#38fe25b7 chat_id:int max_date:int date:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idintChat ID
max_dateintMaximum value of data for read messages
dateintTime when messages were read
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateEncryption.html b/data/corefork.telegram.org/constructor/updateEncryption.html deleted file mode 100644 index db8f4479c4..0000000000 --- a/data/corefork.telegram.org/constructor/updateEncryption.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updateEncryption - - - - - - - - - - - - - -
- -
-
-
- -

updateEncryption

- -

Change of state in an encrypted chat.

-

- -
-
updateEncryption#b4a2e88d chat:EncryptedChat date:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chatEncryptedChatEncrypted chat
dateintDate of change
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateFavedStickers.html b/data/corefork.telegram.org/constructor/updateFavedStickers.html deleted file mode 100644 index 4e72a2287c..0000000000 --- a/data/corefork.telegram.org/constructor/updateFavedStickers.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - updateFavedStickers - - - - - - - - - - - - - -
- -
-
-
- -

updateFavedStickers

- -

The list of favorited stickers was changed, the client should call messages.getFavedStickers to refetch the new list

-

- -
-
updateFavedStickers#e511996d = Update;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Update

-

Related pages

-

messages.getFavedStickers

-

Get faved stickers

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateFolderPeers.html b/data/corefork.telegram.org/constructor/updateFolderPeers.html deleted file mode 100644 index 43bcabc7f8..0000000000 --- a/data/corefork.telegram.org/constructor/updateFolderPeers.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - updateFolderPeers - - - - - - - - - - - - - -
- -
-
-
- -

updateFolderPeers

- -

The peer list of a peer folder was updated

-

- -
-
updateFolderPeers#19360dc0 folder_peers:Vector<FolderPeer> pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
folder_peersVector<FolderPeer>New peer list
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateGeoLiveViewed.html b/data/corefork.telegram.org/constructor/updateGeoLiveViewed.html deleted file mode 100644 index f2359dea84..0000000000 --- a/data/corefork.telegram.org/constructor/updateGeoLiveViewed.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updateGeoLiveViewed - - - - - - - - - - - - - -
- -
-
-
- -

updateGeoLiveViewed

- -

Live geoposition message was viewed

-

- -
-
updateGeoLiveViewed#871fb939 peer:Peer msg_id:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerThe user that viewed the live geoposition
msg_idintMessage ID of geoposition message
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateGroupCall.html b/data/corefork.telegram.org/constructor/updateGroupCall.html deleted file mode 100644 index 778494b8d2..0000000000 --- a/data/corefork.telegram.org/constructor/updateGroupCall.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - updateGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

updateGroupCall

- -

A new groupcall was started

-

- -
-
updateGroupCall#14b24500 chat_id:long call:GroupCall = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongThe channel/supergroup where this group call or livestream takes place
callGroupCallInfo about the group call or livestream
-

Type

-

Update

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateGroupCallConnection.html b/data/corefork.telegram.org/constructor/updateGroupCallConnection.html deleted file mode 100644 index 6e3d4ad6da..0000000000 --- a/data/corefork.telegram.org/constructor/updateGroupCallConnection.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateGroupCallConnection - - - - - - - - - - - - - -
- -
-
-
- -

updateGroupCallConnection

- -

New WebRTC parameters

-

- -
-
updateGroupCallConnection#b783982 flags:# presentation:flags.0?true params:DataJSON = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
presentationflags.0?trueAre these parameters related to the screen capture session currently in progress?
paramsDataJSONWebRTC parameters
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateGroupCallParticipants.html b/data/corefork.telegram.org/constructor/updateGroupCallParticipants.html deleted file mode 100644 index 5a52b59053..0000000000 --- a/data/corefork.telegram.org/constructor/updateGroupCallParticipants.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateGroupCallParticipants - - - - - - - - - - - - - -
- -
-
-
- -

updateGroupCallParticipants

- -

The participant list of a certain group call has changed

-

- -
-
updateGroupCallParticipants#f2ebdb4e call:InputGroupCall participants:Vector<GroupCallParticipant> version:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallGroup call
participantsVector<GroupCallParticipant>New participant list
versionintVersion
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateInlineBotCallbackQuery.html b/data/corefork.telegram.org/constructor/updateInlineBotCallbackQuery.html deleted file mode 100644 index deee1553a1..0000000000 --- a/data/corefork.telegram.org/constructor/updateInlineBotCallbackQuery.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - updateInlineBotCallbackQuery - - - - - - - - - - - - - -
- -
-
-
- -

updateInlineBotCallbackQuery

- -

This notification is received by bots when a button is pressed

-

- -
-
updateInlineBotCallbackQuery#691e9052 flags:# query_id:long user_id:long msg_id:InputBotInlineMessageID chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
query_idlongQuery ID
user_idlongID of the user that pressed the button
msg_idInputBotInlineMessageIDID of the inline message with the button
chat_instancelongGlobal identifier, uniquely corresponding to the chat to which the message with the callback button was sent. Useful for high scores in games.
dataflags.0?bytesData associated with the callback button. Be aware that a bad client can send arbitrary data in this field.
game_short_nameflags.1?stringShort name of a Game to be returned, serves as the unique identifier for the game
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateLangPack.html b/data/corefork.telegram.org/constructor/updateLangPack.html deleted file mode 100644 index 830bee4103..0000000000 --- a/data/corefork.telegram.org/constructor/updateLangPack.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateLangPack - - - - - - - - - - - - - -
- -
-
-
- -

updateLangPack

- -

Language pack updated

-

- -
-
updateLangPack#56022f4d difference:LangPackDifference = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
differenceLangPackDifferenceChanged strings
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateLangPackTooLong.html b/data/corefork.telegram.org/constructor/updateLangPackTooLong.html deleted file mode 100644 index 63a13653ba..0000000000 --- a/data/corefork.telegram.org/constructor/updateLangPackTooLong.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - updateLangPackTooLong - - - - - - - - - - - - - -
- -
-
-
- -

updateLangPackTooLong

- -

A language pack has changed, the client should manually fetch the changed strings using langpack.getDifference

-

- -
-
updateLangPackTooLong#46560264 lang_code:string = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
lang_codestringLanguage code
-

Type

-

Update

-

Related pages

-

langpack.getDifference

-

Get new strings in languagepack

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateLoginToken.html b/data/corefork.telegram.org/constructor/updateLoginToken.html deleted file mode 100644 index b49cabf6c4..0000000000 --- a/data/corefork.telegram.org/constructor/updateLoginToken.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - updateLoginToken - - - - - - - - - - - - - -
- -
-
-
- -

updateLoginToken

- -

A login token (for login via QR code) was accepted.

-

- -
-
updateLoginToken#564fe691 = Update;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateMessageID.html b/data/corefork.telegram.org/constructor/updateMessageID.html deleted file mode 100644 index f5539d8dc5..0000000000 --- a/data/corefork.telegram.org/constructor/updateMessageID.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - updateMessageID - - - - - - - - - - - - - -
- -
-
-
- -

updateMessageID

- -

Sent message with random_id client identifier was assigned an identifier.

-

- -
-
updateMessageID#4e90bfd6 id:int random_id:long = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idintid identifier of a respective Message
random_idlongPreviuosly transferred client random_id identifier
-

Type

-

Update

-

Related pages

-

Message

-

Object describing a message.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateMessagePoll.html b/data/corefork.telegram.org/constructor/updateMessagePoll.html deleted file mode 100644 index 00db776cef..0000000000 --- a/data/corefork.telegram.org/constructor/updateMessagePoll.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - updateMessagePoll - - - - - - - - - - - - - -
- -
-
-
- -

updateMessagePoll

- -

The results of a poll have changed

-

- -
-
updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
poll_idlongPoll ID
pollflags.0?PollIf the server knows the client hasn't cached this poll yet, the poll itself
resultsPollResultsNew poll results
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateMessagePollVote.html b/data/corefork.telegram.org/constructor/updateMessagePollVote.html deleted file mode 100644 index d7a61893e9..0000000000 --- a/data/corefork.telegram.org/constructor/updateMessagePollVote.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - updateMessagePollVote - - - - - - - - - - - - - -
- -
-
-
- -

updateMessagePollVote

- -

A specific user has voted in a poll

-

- -
-
updateMessagePollVote#106395c9 poll_id:long user_id:long options:Vector<bytes> qts:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
poll_idlongPoll ID
user_idlongUser ID
optionsVector<bytes>Chosen option(s)
qtsintNew qts value, see updates » for more info.
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateNewChannelMessage.html b/data/corefork.telegram.org/constructor/updateNewChannelMessage.html deleted file mode 100644 index db343c1263..0000000000 --- a/data/corefork.telegram.org/constructor/updateNewChannelMessage.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - updateNewChannelMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateNewChannelMessage

- -

A new message was sent in a channel/supergroup

-

- -
-
updateNewChannelMessage#62ba04d9 message:Message pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageNew message
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateNewEncryptedMessage.html b/data/corefork.telegram.org/constructor/updateNewEncryptedMessage.html deleted file mode 100644 index d4303376c9..0000000000 --- a/data/corefork.telegram.org/constructor/updateNewEncryptedMessage.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - updateNewEncryptedMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateNewEncryptedMessage

- -

New encrypted message.

-

- -
-
updateNewEncryptedMessage#12bcbd9a message:EncryptedMessage qts:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messageEncryptedMessageMessage
qtsintNew qts value, see updates » for more info.
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateNewMessage.html b/data/corefork.telegram.org/constructor/updateNewMessage.html deleted file mode 100644 index 0a1dd082dc..0000000000 --- a/data/corefork.telegram.org/constructor/updateNewMessage.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateNewMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateNewMessage

- -

New message in a private chat or in a legacy group.

-

- -
-
updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageMessage
ptsintNew quantity of actions in a message box
pts_countintNumber of generated events
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateNewScheduledMessage.html b/data/corefork.telegram.org/constructor/updateNewScheduledMessage.html deleted file mode 100644 index f161aaa12c..0000000000 --- a/data/corefork.telegram.org/constructor/updateNewScheduledMessage.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - updateNewScheduledMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateNewScheduledMessage

- -

A message was added to the schedule queue of a chat

-

- -
-
updateNewScheduledMessage#39a51dfb message:Message = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
messageMessageMessage
-

Type

-

Update

-

Related pages

-

Scheduled messages

-

Telegram allows scheduling messages

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateNewStickerSet.html b/data/corefork.telegram.org/constructor/updateNewStickerSet.html deleted file mode 100644 index a17c049c9e..0000000000 --- a/data/corefork.telegram.org/constructor/updateNewStickerSet.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateNewStickerSet - - - - - - - - - - - - - -
- -
-
-
- -

updateNewStickerSet

- -

A new stickerset was installed

-

- -
-
updateNewStickerSet#688a30aa stickerset:messages.StickerSet = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
stickersetmessages.StickerSetThe installed stickerset
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateNotifySettings.html b/data/corefork.telegram.org/constructor/updateNotifySettings.html deleted file mode 100644 index d80e2000c5..0000000000 --- a/data/corefork.telegram.org/constructor/updateNotifySettings.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updateNotifySettings - - - - - - - - - - - - - -
- -
-
-
- -

updateNotifySettings

- -

Changes in notification settings.

-

- -
-
updateNotifySettings#bec268ef peer:NotifyPeer notify_settings:PeerNotifySettings = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerNotifyPeerNofication source
notify_settingsPeerNotifySettingsNew notification settings
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updatePeerBlocked.html b/data/corefork.telegram.org/constructor/updatePeerBlocked.html deleted file mode 100644 index c0ffb13fe6..0000000000 --- a/data/corefork.telegram.org/constructor/updatePeerBlocked.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updatePeerBlocked - - - - - - - - - - - - - -
- -
-
-
- -

updatePeerBlocked

- -

A peer was blocked

-

- -
-
updatePeerBlocked#246a4b22 peer_id:Peer blocked:Bool = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peer_idPeerThe blocked peer
blockedBoolWhether the peer was blocked or unblocked
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updatePeerHistoryTTL.html b/data/corefork.telegram.org/constructor/updatePeerHistoryTTL.html deleted file mode 100644 index 779eac479d..0000000000 --- a/data/corefork.telegram.org/constructor/updatePeerHistoryTTL.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updatePeerHistoryTTL - - - - - - - - - - - - - -
- -
-
-
- -

updatePeerHistoryTTL

- -

The Time-To-Live for messages sent by the current user in a specific chat has changed

-

- -
-
updatePeerHistoryTTL#bb9bb9a5 flags:# peer:Peer ttl_period:flags.0?int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
peerPeerThe chat
ttl_periodflags.0?intThe new Time-To-Live
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updatePeerLocated.html b/data/corefork.telegram.org/constructor/updatePeerLocated.html deleted file mode 100644 index 14731546dd..0000000000 --- a/data/corefork.telegram.org/constructor/updatePeerLocated.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updatePeerLocated - - - - - - - - - - - - - -
- -
-
-
- -

updatePeerLocated

- -

List of peers near you was updated

-

- -
-
updatePeerLocated#b4afcfb0 peers:Vector<PeerLocated> = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peersVector<PeerLocated>Geolocated peer list update
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updatePeerSettings.html b/data/corefork.telegram.org/constructor/updatePeerSettings.html deleted file mode 100644 index 2b2b5c30ba..0000000000 --- a/data/corefork.telegram.org/constructor/updatePeerSettings.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updatePeerSettings - - - - - - - - - - - - - -
- -
-
-
- -

updatePeerSettings

- -

Settings of a certain peer have changed

-

- -
-
updatePeerSettings#6a7e7366 peer:Peer settings:PeerSettings = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerThe peer
settingsPeerSettingsAssociated peer settings
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updatePhoneCall.html b/data/corefork.telegram.org/constructor/updatePhoneCall.html deleted file mode 100644 index 350529c8fd..0000000000 --- a/data/corefork.telegram.org/constructor/updatePhoneCall.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updatePhoneCall - - - - - - - - - - - - - -
- -
-
-
- -

updatePhoneCall

- -

An incoming phone call

-

- -
-
updatePhoneCall#ab0f6b1e phone_call:PhoneCall = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
phone_callPhoneCallPhone call
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updatePhoneCallSignalingData.html b/data/corefork.telegram.org/constructor/updatePhoneCallSignalingData.html deleted file mode 100644 index 805bfbdbc0..0000000000 --- a/data/corefork.telegram.org/constructor/updatePhoneCallSignalingData.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updatePhoneCallSignalingData - - - - - - - - - - - - - -
- -
-
-
- -

updatePhoneCallSignalingData

- -

Incoming phone call signaling payload

-

- -
-
updatePhoneCallSignalingData#2661bf09 phone_call_id:long data:bytes = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_call_idlongPhone call ID
databytesSignaling payload
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updatePinnedDialogs.html b/data/corefork.telegram.org/constructor/updatePinnedDialogs.html deleted file mode 100644 index 6beddb77b0..0000000000 --- a/data/corefork.telegram.org/constructor/updatePinnedDialogs.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - updatePinnedDialogs - - - - - - - - - - - - - -
- -
-
-
- -

updatePinnedDialogs

- -

Pinned dialogs were updated

-

- -
-
updatePinnedDialogs#fa0f3ca2 flags:# folder_id:flags.1?int order:flags.0?Vector<DialogPeer> = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.1?intPeer folder ID, for more info click here
orderflags.0?Vector<DialogPeer>New order of pinned dialogs
-

Type

-

Update

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updatePinnedMessages.html b/data/corefork.telegram.org/constructor/updatePinnedMessages.html deleted file mode 100644 index 0b7c6e4213..0000000000 --- a/data/corefork.telegram.org/constructor/updatePinnedMessages.html +++ /dev/null @@ -1,175 +0,0 @@ - - - - - updatePinnedMessages - - - - - - - - - - - - - -
- -
-
-
- -

updatePinnedMessages

- -

Some messages were pinned in a chat

-

- -
-
updatePinnedMessages#ed85eab5 flags:# pinned:flags.0?true peer:Peer messages:Vector<int> pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.0?trueWhether the messages were pinned or unpinned
peerPeerPeer
messagesVector<int>Message IDs
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updatePrivacy.html b/data/corefork.telegram.org/constructor/updatePrivacy.html deleted file mode 100644 index c175fdad10..0000000000 --- a/data/corefork.telegram.org/constructor/updatePrivacy.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updatePrivacy - - - - - - - - - - - - - -
- -
-
-
- -

updatePrivacy

- -

Privacy rules were changed

-

- -
-
updatePrivacy#ee3b272a key:PrivacyKey rules:Vector<PrivacyRule> = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
keyPrivacyKeyPeers to which the privacy rules apply
rulesVector<PrivacyRule>New privacy rules
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updatePtsChanged.html b/data/corefork.telegram.org/constructor/updatePtsChanged.html deleted file mode 100644 index ddcfefadc1..0000000000 --- a/data/corefork.telegram.org/constructor/updatePtsChanged.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - updatePtsChanged - - - - - - - - - - - - - -
- -
-
-
- -

updatePtsChanged

- -

Common message box sequence PTS has changed, state has to be refetched using updates.getState

-

- -
-
updatePtsChanged#3354678f = Update;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateReadChannelDiscussionInbox.html b/data/corefork.telegram.org/constructor/updateReadChannelDiscussionInbox.html deleted file mode 100644 index a779431407..0000000000 --- a/data/corefork.telegram.org/constructor/updateReadChannelDiscussionInbox.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - updateReadChannelDiscussionInbox - - - - - - - - - - - - - -
- -
-
-
- -

updateReadChannelDiscussionInbox

- -

Incoming comments in a discussion thread were marked as read

-

- -
-
updateReadChannelDiscussionInbox#d6b19546 flags:# channel_id:long top_msg_id:int read_max_id:int broadcast_id:flags.0?long broadcast_post:flags.0?int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
channel_idlongDiscussion group ID
top_msg_idintID of the group message that started the thread (message in linked discussion group)
read_max_idintMessage ID of latest read incoming message for this thread
broadcast_idflags.0?longIf set, contains the ID of the channel that contains the post that started the comment thread in the discussion group (channel_id)
broadcast_postflags.0?intIf set, contains the ID of the channel post that started the the comment thread
-

Type

-

Update

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateReadChannelDiscussionOutbox.html b/data/corefork.telegram.org/constructor/updateReadChannelDiscussionOutbox.html deleted file mode 100644 index a051872c73..0000000000 --- a/data/corefork.telegram.org/constructor/updateReadChannelDiscussionOutbox.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - updateReadChannelDiscussionOutbox - - - - - - - - - - - - - -
- -
-
-
- -

updateReadChannelDiscussionOutbox

- -

Outgoing comments in a discussion thread were marked as read

-

- -
-
updateReadChannelDiscussionOutbox#695c9e7c channel_id:long top_msg_id:int read_max_id:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idlongSupergroup ID
top_msg_idintID of the group message that started the thread
read_max_idintMessage ID of latest read outgoing message for this thread
-

Type

-

Update

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateReadChannelInbox.html b/data/corefork.telegram.org/constructor/updateReadChannelInbox.html deleted file mode 100644 index 613c39ba31..0000000000 --- a/data/corefork.telegram.org/constructor/updateReadChannelInbox.html +++ /dev/null @@ -1,179 +0,0 @@ - - - - - updateReadChannelInbox - - - - - - - - - - - - - -
- -
-
-
- -

updateReadChannelInbox

- -

Incoming messages in a channel/supergroup were read

-

- -
-
updateReadChannelInbox#922e6e10 flags:# folder_id:flags.0?int channel_id:long max_id:int still_unread_count:int pts:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.0?intPeer folder ID, for more info click here
channel_idlongChannel/supergroup ID
max_idintPosition up to which all incoming messages are read.
still_unread_countintCount of messages weren't read yet
ptsintEvent count after generation
-

Type

-

Update

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateReadChannelOutbox.html b/data/corefork.telegram.org/constructor/updateReadChannelOutbox.html deleted file mode 100644 index 9a6e4d0bd7..0000000000 --- a/data/corefork.telegram.org/constructor/updateReadChannelOutbox.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - updateReadChannelOutbox - - - - - - - - - - - - - -
- -
-
-
- -

updateReadChannelOutbox

- -

Outgoing messages in a channel/supergroup were read

-

- -
-
updateReadChannelOutbox#b75f99a9 channel_id:long max_id:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channel_idlongChannel/supergroup ID
max_idintPosition up to which all outgoing messages are read.
-

Type

-

Update

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateReadFeaturedStickers.html b/data/corefork.telegram.org/constructor/updateReadFeaturedStickers.html deleted file mode 100644 index 77f6b67910..0000000000 --- a/data/corefork.telegram.org/constructor/updateReadFeaturedStickers.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - updateReadFeaturedStickers - - - - - - - - - - - - - -
- -
-
-
- -

updateReadFeaturedStickers

- -

Some featured stickers were marked as read

-

- -
-
updateReadFeaturedStickers#571d2742 = Update;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateReadHistoryInbox.html b/data/corefork.telegram.org/constructor/updateReadHistoryInbox.html deleted file mode 100644 index 8e39d08257..0000000000 --- a/data/corefork.telegram.org/constructor/updateReadHistoryInbox.html +++ /dev/null @@ -1,182 +0,0 @@ - - - - - updateReadHistoryInbox - - - - - - - - - - - - - -
- -
-
-
- -

updateReadHistoryInbox

- -

Incoming messages were read

-

- -
-
updateReadHistoryInbox#9c974fdf flags:# folder_id:flags.0?int peer:Peer max_id:int still_unread_count:int pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.0?intPeer folder ID, for more info click here
peerPeerPeer
max_idintMaximum ID of messages read
still_unread_countintNumber of messages that are still unread
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateReadHistoryOutbox.html b/data/corefork.telegram.org/constructor/updateReadHistoryOutbox.html deleted file mode 100644 index 20dc91ac61..0000000000 --- a/data/corefork.telegram.org/constructor/updateReadHistoryOutbox.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - updateReadHistoryOutbox - - - - - - - - - - - - - -
- -
-
-
- -

updateReadHistoryOutbox

- -

Outgoing messages were read

-

- -
-
updateReadHistoryOutbox#2f2f21bf peer:Peer max_id:int pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerPeerPeer
max_idintMaximum ID of read outgoing messages
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateReadMessagesContents.html b/data/corefork.telegram.org/constructor/updateReadMessagesContents.html deleted file mode 100644 index bd073bc108..0000000000 --- a/data/corefork.telegram.org/constructor/updateReadMessagesContents.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - updateReadMessagesContents - - - - - - - - - - - - - -
- -
-
-
- -

updateReadMessagesContents

- -

Contents of messages in the common message box were read

-

- -
-
updateReadMessagesContents#68c13933 messages:Vector<int> pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
messagesVector<int>IDs of read messages
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateRecentStickers.html b/data/corefork.telegram.org/constructor/updateRecentStickers.html deleted file mode 100644 index 8b02b85917..0000000000 --- a/data/corefork.telegram.org/constructor/updateRecentStickers.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - updateRecentStickers - - - - - - - - - - - - - -
- -
-
-
- -

updateRecentStickers

- -

The recent sticker list was updated

-

- -
-
updateRecentStickers#9a422c20 = Update;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateSavedGifs.html b/data/corefork.telegram.org/constructor/updateSavedGifs.html deleted file mode 100644 index 98f285dce1..0000000000 --- a/data/corefork.telegram.org/constructor/updateSavedGifs.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - updateSavedGifs - - - - - - - - - - - - - -
- -
-
-
- -

updateSavedGifs

- -

The saved gif list has changed, the client should refetch it using messages.getSavedGifs

-

- -
-
updateSavedGifs#9375341e = Update;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateServiceNotification.html b/data/corefork.telegram.org/constructor/updateServiceNotification.html deleted file mode 100644 index 7f6bf82f9a..0000000000 --- a/data/corefork.telegram.org/constructor/updateServiceNotification.html +++ /dev/null @@ -1,183 +0,0 @@ - - - - - updateServiceNotification - - - - - - - - - - - - - -
- -
-
-
- -

updateServiceNotification

- -

A service message for the user.

-

The app must show the message to the user upon receiving this update. In case the popup parameter was passed, the text message must be displayed in a popup alert immediately upon receipt. It is recommended to handle the text as you would an ordinary message in terms of highlighting links, etc. The message must also be stored locally as part of the message history with the user id 777000 (Telegram Notifications).

-

- -
-
updateServiceNotification#ebe46819 flags:# popup:flags.0?true inbox_date:flags.1?int type:string message:string media:MessageMedia entities:Vector<MessageEntity> = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
popupflags.0?true(boolTrue) if the message must be displayed in a popup.
inbox_dateflags.1?intWhen was the notification received
The message must also be stored locally as part of the message history with the user id 777000 (Telegram Notifications).
typestringString, identical in format and contents to the type field in API errors. Describes type of service message. It is acceptable to ignore repeated messages of the same type within a short period of time (15 minutes).
messagestringMessage text
mediaMessageMediaMedia content (optional)
entitiesVector<MessageEntity>Message entities for styled text
-

Type

-

Update

-

Related pages

-

Error handling

-

How to handle API return errors correctly.

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateShort.html b/data/corefork.telegram.org/constructor/updateShort.html deleted file mode 100644 index bae66247d3..0000000000 --- a/data/corefork.telegram.org/constructor/updateShort.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updateShort - - - - - - - - - - - - - -
- -
-
-
- -

updateShort

- -

Shortened constructor containing info on one update not requiring auxiliary data

-

- -
-
updateShort#78d4dec1 update:Update date:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
updateUpdateUpdate
dateintDate of event
-

Type

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateShortChatMessage.html b/data/corefork.telegram.org/constructor/updateShortChatMessage.html deleted file mode 100644 index d61e3319fc..0000000000 --- a/data/corefork.telegram.org/constructor/updateShortChatMessage.html +++ /dev/null @@ -1,232 +0,0 @@ - - - - - updateShortChatMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateShortChatMessage

- -

Shortened constructor containing info on one new incoming text message from a chat

-

- -
-
updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
outflags.1?trueWhether the message is outgoing
mentionedflags.4?trueWhether we were mentioned in this message
media_unreadflags.5?trueWhether the message contains some unread mentions
silentflags.13?trueIf true, the message is a silent message, no notifications should be triggered
idintID of the message
from_idlongID of the sender of the message
chat_idlongID of the chat where the message was sent
messagestringMessage
ptsintPTS
pts_countintPTS count
dateintdate
fwd_fromflags.2?MessageFwdHeaderInfo about a forwarded message
via_bot_idflags.11?longInfo about the inline bot used to generate this message
reply_toflags.3?MessageReplyHeaderReply (thread) information
entitiesflags.7?Vector<MessageEntity>Entities for styled text
ttl_periodflags.25?intTime To Live of the message, once updateShortChatMessage.date+updateShortChatMessage.ttl_period === time(), the message will be deleted on the server, and must be deleted locally as well.
-

Type

-

Updates

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateShortMessage.html b/data/corefork.telegram.org/constructor/updateShortMessage.html deleted file mode 100644 index 084b21894a..0000000000 --- a/data/corefork.telegram.org/constructor/updateShortMessage.html +++ /dev/null @@ -1,229 +0,0 @@ - - - - - updateShortMessage - - - - - - - - - - - - - -
- -
-
-
- -

updateShortMessage

- -

Info about a message sent to (received from) another user

-

- -
-
updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
outflags.1?trueWhether the message is outgoing
mentionedflags.4?trueWhether we were mentioned in the message
media_unreadflags.5?trueWhether there are some unread mentions in this message
silentflags.13?trueIf true, the message is a silent message, no notifications should be triggered
idintThe message ID
user_idlongThe ID of the sender (if outgoing will be the ID of the destination) of the message
messagestringThe message
ptsintPTS
pts_countintPTS count
dateintdate
fwd_fromflags.2?MessageFwdHeaderInfo about a forwarded message
via_bot_idflags.11?longInfo about the inline bot used to generate this message
reply_toflags.3?MessageReplyHeaderReply and thread information
entitiesflags.7?Vector<MessageEntity>Entities for styled text
ttl_periodflags.25?intTime To Live of the message, once message.date+message.ttl_period === time(), the message will be deleted on the server, and must be deleted locally as well.
-

Type

-

Updates

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateStickerSets.html b/data/corefork.telegram.org/constructor/updateStickerSets.html deleted file mode 100644 index fdd12b6646..0000000000 --- a/data/corefork.telegram.org/constructor/updateStickerSets.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - updateStickerSets - - - - - - - - - - - - - -
- -
-
-
- -

updateStickerSets

- -

Installed stickersets have changed, the client should refetch them using messages.getAllStickers

-

- -
-
updateStickerSets#43ae3dec = Update;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateStickerSetsOrder.html b/data/corefork.telegram.org/constructor/updateStickerSetsOrder.html deleted file mode 100644 index 3a1c66e63c..0000000000 --- a/data/corefork.telegram.org/constructor/updateStickerSetsOrder.html +++ /dev/null @@ -1,157 +0,0 @@ - - - - - updateStickerSetsOrder - - - - - - - - - - - - - -
- -
-
-
- -

updateStickerSetsOrder

- -

The order of stickersets was changed

-

- -
-
updateStickerSetsOrder#bb2d201 flags:# masks:flags.0?true order:Vector<long> = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
masksflags.0?trueWhether the updated stickers are mask stickers
orderVector<long>New sticker order by sticker ID
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateTheme.html b/data/corefork.telegram.org/constructor/updateTheme.html deleted file mode 100644 index 8e429292ce..0000000000 --- a/data/corefork.telegram.org/constructor/updateTheme.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - updateTheme - - - - - - - - - - - - - -
- -
-
-
- -

updateTheme

- -

A cloud theme was updated

-

- -
-
updateTheme#8216fba3 theme:Theme = Update;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
themeThemeTheme
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateUserBlocked.html b/data/corefork.telegram.org/constructor/updateUserBlocked.html deleted file mode 100644 index 614b658a70..0000000000 --- a/data/corefork.telegram.org/constructor/updateUserBlocked.html +++ /dev/null @@ -1,159 +0,0 @@ - - - - - updateUserBlocked - - - - - - - - - - - - - -
- -
-
-
- -

updateUserBlocked

- -

User was added to the blacklist (method contacts.block) or removed from the blacklist (method contacts.unblock).

-

- -
-
Constructor schema is available as of layer 119. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idintUser id
blockedBool(boolTrue) if the the user is blocked
-

Type

-

Update

-

Related pages

-

boolTrue

-

The constructor can be interpreted as a booleantrue value.

-

contacts.block

-

Adds the user to the blacklist.

-

contacts.unblock

-

Deletes the user from the blacklist.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateUserName.html b/data/corefork.telegram.org/constructor/updateUserName.html deleted file mode 100644 index 69fa4a0d4f..0000000000 --- a/data/corefork.telegram.org/constructor/updateUserName.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - updateUserName - - - - - - - - - - - - - -
- -
-
-
- -

updateUserName

- -

Changes the user's first name, last name and username.

-

- -
-
updateUserName#c3f202e0 user_id:long first_name:string last_name:string username:string = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser identifier
first_namestringNew first name. Corresponds to the new value of real_first_name field of the userFull constructor.
last_namestringNew last name. Corresponds to the new value of real_last_name field of the userFull constructor.
usernamestringNew username.
Parameter added in Layer 18.
-

Type

-

Update

-

Related pages

-

userFull

-

Extended user info

-

Layers

-

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateUserPhone.html b/data/corefork.telegram.org/constructor/updateUserPhone.html deleted file mode 100644 index c932ca7892..0000000000 --- a/data/corefork.telegram.org/constructor/updateUserPhone.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updateUserPhone - - - - - - - - - - - - - -
- -
-
-
- -

updateUserPhone

- -

A user's phone number was changed

-

- -
-
updateUserPhone#5492a13 user_id:long phone:string = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser ID
phonestringNew phone number
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateUserPhoto.html b/data/corefork.telegram.org/constructor/updateUserPhoto.html deleted file mode 100644 index ec6b532dd7..0000000000 --- a/data/corefork.telegram.org/constructor/updateUserPhoto.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - updateUserPhoto - - - - - - - - - - - - - -
- -
-
-
- -

updateUserPhoto

- -

Change of contact's profile photo.

-

- -
-
updateUserPhoto#f227868c user_id:long date:int photo:UserProfilePhoto previous:Bool = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser identifier
dateintDate of photo update.
photoUserProfilePhotoNew profile photo
previousBool(boolTrue), if one of the previously used photos is set a profile photo.
-

Type

-

Update

-

Related pages

-

boolTrue

-

The constructor can be interpreted as a booleantrue value.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateUserStatus.html b/data/corefork.telegram.org/constructor/updateUserStatus.html deleted file mode 100644 index e466d3621e..0000000000 --- a/data/corefork.telegram.org/constructor/updateUserStatus.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updateUserStatus - - - - - - - - - - - - - -
- -
-
-
- -

updateUserStatus

- -

Contact status update.

-

- -
-
updateUserStatus#e5bdf8de user_id:long status:UserStatus = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser identifier
statusUserStatusNew status
-

Type

-

Update

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateUserTyping.html b/data/corefork.telegram.org/constructor/updateUserTyping.html deleted file mode 100644 index c29fcc2d4d..0000000000 --- a/data/corefork.telegram.org/constructor/updateUserTyping.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - updateUserTyping - - - - - - - - - - - - - -
- -
-
-
- -

updateUserTyping

- -

The user is preparing a message; typing, recording, uploading, etc. This update is valid for 6 seconds. If no repeated update received after 6 seconds, it should be considered that the user stopped doing whatever he's been doing.

-

- -
-
updateUserTyping#c01e857f user_id:long action:SendMessageAction = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idlongUser id
actionSendMessageActionAction type
Param added in Layer 17.
-

Type

-

Update

-

Related pages

-

Layers

-

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updateWebPage.html b/data/corefork.telegram.org/constructor/updateWebPage.html deleted file mode 100644 index 03167f9324..0000000000 --- a/data/corefork.telegram.org/constructor/updateWebPage.html +++ /dev/null @@ -1,160 +0,0 @@ - - - - - updateWebPage - - - - - - - - - - - - - -
- -
-
-
- -

updateWebPage

- -

An instant view webpage preview was generated

-

- -
-
updateWebPage#7f891213 webpage:WebPage pts:int pts_count:int = Update;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
webpageWebPageWebpage preview
ptsintEvent count after generation
pts_countintNumber of events that were generated
-

Type

-

Update

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updates.channelDifference b/data/corefork.telegram.org/constructor/updates.channelDifference deleted file mode 100644 index 2e76d2eeae..0000000000 --- a/data/corefork.telegram.org/constructor/updates.channelDifference +++ /dev/null @@ -1,185 +0,0 @@ - - - - - updates.channelDifference - - - - - - - - - - - - - -
- -
-
-
- -

updates.channelDifference

- -

The new updates

-

- -
-
updates.channelDifference#2064674e flags:# final:flags.0?true pts:int timeout:flags.1?int new_messages:Vector<Message> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
finalflags.0?trueWhether there are more updates to be fetched using getDifference, starting from the provided pts
ptsintThe PTS from which to start getting updates the next time
timeoutflags.1?intClients are supposed to refetch the channel difference after timeout seconds have elapsed
new_messagesVector<Message>New messages
other_updatesVector<Update>Other updates
chatsVector<Chat>Chats
usersVector<User>Users
-

Type

-

updates.ChannelDifference

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updates.channelDifferenceEmpty b/data/corefork.telegram.org/constructor/updates.channelDifferenceEmpty deleted file mode 100644 index 9ec9f55d68..0000000000 --- a/data/corefork.telegram.org/constructor/updates.channelDifferenceEmpty +++ /dev/null @@ -1,165 +0,0 @@ - - - - - updates.channelDifferenceEmpty - - - - - - - - - - - - - -
- -
-
-
- -

updates.channelDifferenceEmpty

- -

There are no new updates

-

- -
-
updates.channelDifferenceEmpty#3e11affb flags:# final:flags.0?true pts:int timeout:flags.1?int = updates.ChannelDifference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
finalflags.0?trueWhether there are more updates that must be fetched (always false)
ptsintThe latest PTS
timeoutflags.1?intClients are supposed to refetch the channel difference after timeout seconds have elapsed
-

Type

-

updates.ChannelDifference

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updates.channelDifferenceTooLong b/data/corefork.telegram.org/constructor/updates.channelDifferenceTooLong deleted file mode 100644 index 2ce9bc4947..0000000000 --- a/data/corefork.telegram.org/constructor/updates.channelDifferenceTooLong +++ /dev/null @@ -1,190 +0,0 @@ - - - - - updates.channelDifferenceTooLong - - - - - - - - - - - - - -
- -
-
-
- -

updates.channelDifferenceTooLong

- -

The provided pts + limit < remote pts. Simply, there are too many updates to be fetched (more than limit), the client has to resolve the update gap in one of the following ways:

-
    -
  1. Delete all known messages in the chat, begin from scratch by refetching all messages manually with getHistory. It is easy to implement, but suddenly disappearing messages looks awful for the user.
  2. -
  3. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to getHistory. It looks much smoothly for the user, they will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of getHistory and getMessages must be used to update state of deleted and edited messages left in the memory.
  4. -
  5. Save all messages loaded in the memory and stored in the database without saving that some messages form continuous ranges. Messages in the database will be excluded from results of getChatHistory and searchChatMessages after application restart and will be available only through getMessage. Every message should still be checked using getHistory. It has more disadvantages over 2) than advantages.
  6. -
  7. Save all messages with saving all data about continuous message ranges. Messages from the database may be used as results of getChatHistory and (if implemented continuous ranges support for searching shared media) searchChatMessages. The messages should still be lazily checked using getHistory, but they are still available offline. It is the best way for gaps support, but it is pretty hard to implement correctly. It should be also noted that some messages like live location messages shouldn't be deleted.
  8. -
-

- -
-
updates.channelDifferenceTooLong#a4bcc6fe flags:# final:flags.0?true timeout:flags.1?int dialog:Dialog messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
finalflags.0?trueWhether there are more updates that must be fetched (always false)
timeoutflags.1?intClients are supposed to refetch the channel difference after timeout seconds have elapsed
dialogDialogDialog containing the latest PTS that can be used to reset the channel state
messagesVector<Message>The latest messages
chatsVector<Chat>Chats from messages
usersVector<User>Users from messages
-

Type

-

updates.ChannelDifference

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

messages.getHistory

-

Gets back the conversation history with one interlocutor / within a chat

-

messages.getMessages

-

Returns the list of messages by their IDs.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updates.difference b/data/corefork.telegram.org/constructor/updates.difference deleted file mode 100644 index 7b05d7b1a2..0000000000 --- a/data/corefork.telegram.org/constructor/updates.difference +++ /dev/null @@ -1,172 +0,0 @@ - - - - - updates.difference - - - - - - - - - - - - - -
- -
-
-
- -

updates.difference

- -

Full list of occurred events.

-

- -
-
updates.difference#f49ca0 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> state:updates.State = updates.Difference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
new_messagesVector<Message>List of new messages
new_encrypted_messagesVector<EncryptedMessage>List of new encrypted secret chat messages
other_updatesVector<Update>List of updates
chatsVector<Chat>List of chats mentioned in events
usersVector<User>List of users mentioned in events
stateupdates.StateCurrent state
-

Type

-

updates.Difference

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updates.differenceEmpty b/data/corefork.telegram.org/constructor/updates.differenceEmpty deleted file mode 100644 index 710786ec21..0000000000 --- a/data/corefork.telegram.org/constructor/updates.differenceEmpty +++ /dev/null @@ -1,152 +0,0 @@ - - - - - updates.differenceEmpty - - - - - - - - - - - - - -
- -
-
-
- -

updates.differenceEmpty

- -

No events.

-

- -
-
updates.differenceEmpty#5d75a138 date:int seq:int = updates.Difference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
dateintCurrent date
seqintNumber of sent updates
-

Type

-

updates.Difference

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updates.differenceSlice b/data/corefork.telegram.org/constructor/updates.differenceSlice deleted file mode 100644 index 9d44f3114b..0000000000 --- a/data/corefork.telegram.org/constructor/updates.differenceSlice +++ /dev/null @@ -1,175 +0,0 @@ - - - - - updates.differenceSlice - - - - - - - - - - - - - -
- -
-
-
- -

updates.differenceSlice

- -

Incomplete list of occurred events.

-

- -
-
updates.differenceSlice#a8fb1981 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> intermediate_state:updates.State = updates.Difference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
new_messagesVector<Message>List of new messgaes
new_encrypted_messagesVector<EncryptedMessage>New messages from the encrypted event sequence
other_updatesVector<Update>List of updates
chatsVector<Chat>List of chats mentioned in events
usersVector<User>List of users mentioned in events
intermediate_stateupdates.StateIntermediary state
-

Type

-

updates.Difference

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updates.differenceTooLong b/data/corefork.telegram.org/constructor/updates.differenceTooLong deleted file mode 100644 index df49d349bb..0000000000 --- a/data/corefork.telegram.org/constructor/updates.differenceTooLong +++ /dev/null @@ -1,150 +0,0 @@ - - - - - updates.differenceTooLong - - - - - - - - - - - - - -
- -
-
-
- -

updates.differenceTooLong

- -

The difference is too long, and the specified state must be used to refetch updates.

-

- -
-
updates.differenceTooLong#4afe8f6d pts:int = updates.Difference;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
ptsintThe new state to use.
-

Type

-

updates.Difference

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updates.html b/data/corefork.telegram.org/constructor/updates.html deleted file mode 100644 index 8f32e83775..0000000000 --- a/data/corefork.telegram.org/constructor/updates.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Updates - - - - - - - - - - - - - -
- -
-
-
- -

Updates

- -

Full constructor of updates

-

- -
-
updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
updatesVector<Update>List of updates
usersVector<User>List of users mentioned in updates
chatsVector<Chat>List of chats mentioned in updates
dateintCurrent date
seqintTotal number of sent updates
-

Type

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updatesCombined.html b/data/corefork.telegram.org/constructor/updatesCombined.html deleted file mode 100644 index fd9c54186a..0000000000 --- a/data/corefork.telegram.org/constructor/updatesCombined.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - updatesCombined - - - - - - - - - - - - - -
- -
-
-
- -

updatesCombined

- -

Constructor for a group of updates.

-

- -
-
updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
updatesVector<Update>List of updates
usersVector<User>List of users mentioned in updates
chatsVector<Chat>List of chats mentioned in updates
dateintCurrent date
seq_startintValue seq for the earliest update in a group
seqintValue seq for the latest update in a group
-

Type

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/updatesTooLong.html b/data/corefork.telegram.org/constructor/updatesTooLong.html deleted file mode 100644 index 656800da3d..0000000000 --- a/data/corefork.telegram.org/constructor/updatesTooLong.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - updatesTooLong - - - - - - - - - - - - - -
- -
-
-
- -

updatesTooLong

- -

Too many updates, it is necessary to execute updates.getDifference.

-

- -
-
updatesTooLong#e317af7e = Updates;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Updates

-

Related pages

-

updates.getDifference

-

Get new updates.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/upload.cdnFile b/data/corefork.telegram.org/constructor/upload.cdnFile deleted file mode 100644 index f490620ccb..0000000000 --- a/data/corefork.telegram.org/constructor/upload.cdnFile +++ /dev/null @@ -1,149 +0,0 @@ - - - - - upload.cdnFile - - - - - - - - - - - - - -
- -
-
-
- -

upload.cdnFile

- -

Represent a chunk of a CDN file.

-

- -
-
upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
bytesbytesThe data
-

Type

-

upload.CdnFile

-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/upload.cdnFileReuploadNeeded b/data/corefork.telegram.org/constructor/upload.cdnFileReuploadNeeded deleted file mode 100644 index 226a04ab94..0000000000 --- a/data/corefork.telegram.org/constructor/upload.cdnFileReuploadNeeded +++ /dev/null @@ -1,149 +0,0 @@ - - - - - upload.cdnFileReuploadNeeded - - - - - - - - - - - - - -
- -
-
-
- -

upload.cdnFileReuploadNeeded

- -

The file was cleared from the temporary RAM cache of the CDN and has to be reuploaded.

-

- -
-
upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
request_tokenbytesRequest token (see CDN)
-

Type

-

upload.CdnFile

-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/upload.file b/data/corefork.telegram.org/constructor/upload.file deleted file mode 100644 index 7c4d276484..0000000000 --- a/data/corefork.telegram.org/constructor/upload.file +++ /dev/null @@ -1,157 +0,0 @@ - - - - - upload.file - - - - - - - - - - - - - -
- -
-
-
- -

upload.file

- -

File content.

-

- -
-
upload.file#96a18d5 type:storage.FileType mtime:int bytes:bytes = upload.File;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typestorage.FileTypeFile type
mtimeintModification type
bytesbytesBinary data, file content
-

Type

-

upload.File

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/upload.fileCdnRedirect b/data/corefork.telegram.org/constructor/upload.fileCdnRedirect deleted file mode 100644 index d815cbc650..0000000000 --- a/data/corefork.telegram.org/constructor/upload.fileCdnRedirect +++ /dev/null @@ -1,169 +0,0 @@ - - - - - upload.fileCdnRedirect - - - - - - - - - - - - - -
- -
-
-
- -

upload.fileCdnRedirect

- -

The file must be downloaded from a CDN DC.

-

- -
-
upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
dc_idintCDN DC ID
file_tokenbytesFile token (see CDN files)
encryption_keybytesEncryption key (see CDN files)
encryption_ivbytesEncryption IV (see CDN files)
file_hashesVector<FileHash>File hashes (see CDN files)
-

Type

-

upload.File

-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/upload.webFile b/data/corefork.telegram.org/constructor/upload.webFile deleted file mode 100644 index 1f8e91216a..0000000000 --- a/data/corefork.telegram.org/constructor/upload.webFile +++ /dev/null @@ -1,170 +0,0 @@ - - - - - upload.webFile - - - - - - - - - - - - - -
- -
-
-
- -

upload.webFile

- -

Represents a chunk of an HTTP webfile downloaded through telegram's secure MTProto servers

-

- -
-
upload.webFile#21e753bc size:int mime_type:string file_type:storage.FileType mtime:int bytes:bytes = upload.WebFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
sizeintFile size
mime_typestringMime type
file_typestorage.FileTypeFile type
mtimeintModified time
bytesbytesData
-

Type

-

upload.WebFile

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/urlAuthResultAccepted.html b/data/corefork.telegram.org/constructor/urlAuthResultAccepted.html deleted file mode 100644 index 3550841877..0000000000 --- a/data/corefork.telegram.org/constructor/urlAuthResultAccepted.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - urlAuthResultAccepted - - - - - - - - - - - - - -
- -
-
-
- -

urlAuthResultAccepted

- -

Details about an accepted authorization request, for more info click here »

-

- -
-
urlAuthResultAccepted#8f8c0e4e url:string = UrlAuthResult;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
urlstringThe URL name of the website on which the user has logged in.
-

Type

-

UrlAuthResult

-

Related pages

-

Seamless Telegram Login

-

Handle Seamless Telegram Login URL authorization requests.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/urlAuthResultDefault.html b/data/corefork.telegram.org/constructor/urlAuthResultDefault.html deleted file mode 100644 index 96a567cd78..0000000000 --- a/data/corefork.telegram.org/constructor/urlAuthResultDefault.html +++ /dev/null @@ -1,135 +0,0 @@ - - - - - urlAuthResultDefault - - - - - - - - - - - - - -
- -
-
-
- -

urlAuthResultDefault

- -

Details about an accepted authorization request, for more info click here »

-

- -
-
urlAuthResultDefault#a9d6db1f = UrlAuthResult;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

UrlAuthResult

-

Related pages

-

Seamless Telegram Login

-

Handle Seamless Telegram Login URL authorization requests.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/urlAuthResultRequest.html b/data/corefork.telegram.org/constructor/urlAuthResultRequest.html deleted file mode 100644 index 0cb43ed8e9..0000000000 --- a/data/corefork.telegram.org/constructor/urlAuthResultRequest.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - urlAuthResultRequest - - - - - - - - - - - - - -
- -
-
-
- -

urlAuthResultRequest

- -

Details about the authorization request, for more info click here »

-

- -
-
urlAuthResultRequest#92d33a0e flags:# request_write_access:flags.0?true bot:User domain:string = UrlAuthResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
request_write_accessflags.0?trueWhether the bot would like to send messages to the user
botUserUsername of a bot, which will be used for user authorization. If not specified, the current bot's username will be assumed. The url's domain must be the same as the domain linked with the bot. See Linking your domain to the bot for more details.
domainstringThe domain name of the website on which the user will log in.
-

Type

-

UrlAuthResult

-

Related pages

-

Seamless Telegram Login

-

Handle Seamless Telegram Login URL authorization requests.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/user.html b/data/corefork.telegram.org/constructor/user.html deleted file mode 100644 index 55b01c34a4..0000000000 --- a/data/corefork.telegram.org/constructor/user.html +++ /dev/null @@ -1,287 +0,0 @@ - - - - - user - - - - - - - - - - - - - -
- -
-
-
- -

user

- -

Indicates info about a certain user

-

- -
-
user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
selfflags.10?trueWhether this user indicates the currently logged in user
contactflags.11?trueWhether this user is a contact
mutual_contactflags.12?trueWhether this user is a mutual contact
deletedflags.13?trueWhether the account of this user was deleted
botflags.14?trueIs this user a bot?
bot_chat_historyflags.15?trueCan the bot see all messages in groups?
bot_nochatsflags.16?trueCan the bot be added to groups?
verifiedflags.17?trueWhether this user is verified
restrictedflags.18?trueAccess to this user must be restricted for the reason specified in restriction_reason
minflags.20?trueSee min
bot_inline_geoflags.21?trueWhether the bot can request our geolocation in inline mode
supportflags.23?trueWhether this is an official support user
scamflags.24?trueThis may be a scam user
apply_min_photoflags.25?trueIf set, the profile picture for this user should be refetched
fakeflags.26?trueIf set, this user was reported by many users as a fake or scam user: be careful when interacting with them.
idlongID of the user
access_hashflags.0?longAccess hash of the user
first_nameflags.1?stringFirst name
last_nameflags.2?stringLast name
usernameflags.3?stringUsername
phoneflags.4?stringPhone number
photoflags.5?UserProfilePhotoProfile picture of user
statusflags.6?UserStatusOnline status of user
bot_info_versionflags.14?intVersion of the bot_info field in userFull, incremented every time it changes
restriction_reasonflags.18?Vector<RestrictionReason>Contains the reason why access to this user must be restricted.
bot_inline_placeholderflags.19?stringInline placeholder for this inline bot
lang_codeflags.22?stringLanguage code of the user
-

Type

-

User

-

Related pages

-

Min constructors

-

In some situations user and channel constructors have reduced set of fields present (although id is always there) and min flag set.

-

userFull

-

Extended user info

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/userEmpty.html b/data/corefork.telegram.org/constructor/userEmpty.html deleted file mode 100644 index 6fb5fe236e..0000000000 --- a/data/corefork.telegram.org/constructor/userEmpty.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - userEmpty - - - - - - - - - - - - - -
- -
-
-
- -

userEmpty

- -

Empty constructor, non-existent user.

-

- -
-
userEmpty#d3bc4b7a id:long = User;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idlongUser identifier or 0
-

Type

-

User

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/userFull.html b/data/corefork.telegram.org/constructor/userFull.html deleted file mode 100644 index d030d3d747..0000000000 --- a/data/corefork.telegram.org/constructor/userFull.html +++ /dev/null @@ -1,239 +0,0 @@ - - - - - userFull - - - - - - - - - - - - - -
- -
-
-
- -

userFull

- -

Extended user info

-

- -
-
userFull#d697ff05 flags:# blocked:flags.0?true phone_calls_available:flags.4?true phone_calls_private:flags.5?true can_pin_message:flags.7?true has_scheduled:flags.12?true video_calls_available:flags.13?true user:User about:flags.1?string settings:PeerSettings profile_photo:flags.2?Photo notify_settings:PeerNotifySettings bot_info:flags.3?BotInfo pinned_msg_id:flags.6?int common_chats_count:int folder_id:flags.11?int ttl_period:flags.14?int theme_emoticon:flags.15?string = UserFull;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
blockedflags.0?trueWhether you have blocked this user
phone_calls_availableflags.4?trueWhether this user can make VoIP calls
phone_calls_privateflags.5?trueWhether this user's privacy settings allow you to call him
can_pin_messageflags.7?trueWhether you can pin messages in the chat with this user, you can do this only for a chat with yourself
has_scheduledflags.12?trueWhether scheduled messages are available
video_calls_availableflags.13?trueWhether the user can receive video calls
userUserRemaining user info
aboutflags.1?stringBio of the user
settingsPeerSettingsPeer settings
profile_photoflags.2?PhotoProfile photo
notify_settingsPeerNotifySettingsNotification settings
bot_infoflags.3?BotInfoFor bots, info about the bot (bot commands, etc)
pinned_msg_idflags.6?intMessage ID of the last pinned message
common_chats_countintChats in common with this user
folder_idflags.11?intPeer folder ID, for more info click here
ttl_periodflags.14?intTime To Live of all messages in this chat; once a message is this many seconds old, it must be deleted.
theme_emoticonflags.15?stringEmoji associated with chat theme
-

Type

-

UserFull

-

Related pages

-

Scheduled messages

-

Telegram allows scheduling messages

-

Pinned messages

-

Telegram allows pinning multiple messages on top of a specific chat.

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/userProfilePhoto.html b/data/corefork.telegram.org/constructor/userProfilePhoto.html deleted file mode 100644 index b418d1d1cb..0000000000 --- a/data/corefork.telegram.org/constructor/userProfilePhoto.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - userProfilePhoto - - - - - - - - - - - - - -
- -
-
-
- -

userProfilePhoto

- -

User profile photo.

-

- -
-
userProfilePhoto#82d1f706 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = UserProfilePhoto;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
has_videoflags.0?trueWhether an animated profile picture is available for this user
photo_idlongIdentifier of the respective photo
Parameter added in Layer 2
stripped_thumbflags.1?bytesStripped thumbnail
dc_idintDC ID where the photo is stored
-

Type

-

UserProfilePhoto

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

-

Layers

-

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/userProfilePhotoEmpty.html b/data/corefork.telegram.org/constructor/userProfilePhotoEmpty.html deleted file mode 100644 index 36eeaada3b..0000000000 --- a/data/corefork.telegram.org/constructor/userProfilePhotoEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - userProfilePhotoEmpty - - - - - - - - - - - - - -
- -
-
-
- -

userProfilePhotoEmpty

- -

Profile photo has not been set, or was hidden.

-

- -
-
userProfilePhotoEmpty#4f11bae1 = UserProfilePhoto;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

UserProfilePhoto

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/userStatusEmpty.html b/data/corefork.telegram.org/constructor/userStatusEmpty.html deleted file mode 100644 index 5e1d38b5f4..0000000000 --- a/data/corefork.telegram.org/constructor/userStatusEmpty.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - userStatusEmpty - - - - - - - - - - - - - -
- -
-
-
- -

userStatusEmpty

- -

User status has not been set yet.

-

- -
-
userStatusEmpty#9d05049 = UserStatus;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

UserStatus

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/userStatusLastMonth.html b/data/corefork.telegram.org/constructor/userStatusLastMonth.html deleted file mode 100644 index 9b1f8a434d..0000000000 --- a/data/corefork.telegram.org/constructor/userStatusLastMonth.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - userStatusLastMonth - - - - - - - - - - - - - -
- -
-
-
- -

userStatusLastMonth

- -

Online status: last seen last month

-

- -
-
userStatusLastMonth#77ebc742 = UserStatus;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

UserStatus

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/userStatusLastWeek.html b/data/corefork.telegram.org/constructor/userStatusLastWeek.html deleted file mode 100644 index 278022a112..0000000000 --- a/data/corefork.telegram.org/constructor/userStatusLastWeek.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - userStatusLastWeek - - - - - - - - - - - - - -
- -
-
-
- -

userStatusLastWeek

- -

Online status: last seen last week

-

- -
-
userStatusLastWeek#7bf09fc = UserStatus;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

UserStatus

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/userStatusOffline.html b/data/corefork.telegram.org/constructor/userStatusOffline.html deleted file mode 100644 index cc15570b31..0000000000 --- a/data/corefork.telegram.org/constructor/userStatusOffline.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - userStatusOffline - - - - - - - - - - - - - -
- -
-
-
- -

userStatusOffline

- -

The user's offline status.

-

- -
-
userStatusOffline#8c703f was_online:int = UserStatus;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
was_onlineintTime the user was last seen online
-

Type

-

UserStatus

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/userStatusOnline.html b/data/corefork.telegram.org/constructor/userStatusOnline.html deleted file mode 100644 index 9c3c922969..0000000000 --- a/data/corefork.telegram.org/constructor/userStatusOnline.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - userStatusOnline - - - - - - - - - - - - - -
- -
-
-
- -

userStatusOnline

- -

Online status of the user.

-

- -
-
userStatusOnline#edb93949 expires:int = UserStatus;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
expiresintTime to expiration of the current online status
-

Type

-

UserStatus

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/userStatusRecently.html b/data/corefork.telegram.org/constructor/userStatusRecently.html deleted file mode 100644 index 628144c4fe..0000000000 --- a/data/corefork.telegram.org/constructor/userStatusRecently.html +++ /dev/null @@ -1,132 +0,0 @@ - - - - - userStatusRecently - - - - - - - - - - - - - -
- -
-
-
- -

userStatusRecently

- -

Online status: last seen recently

-

- -
-
userStatusRecently#e26f42f1 = UserStatus;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

UserStatus

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/vector.html b/data/corefork.telegram.org/constructor/vector.html deleted file mode 100644 index 650b72e963..0000000000 --- a/data/corefork.telegram.org/constructor/vector.html +++ /dev/null @@ -1,134 +0,0 @@ - - - - - vector - - - - - - - - - - - - - -
- -
-
-
- -

vector

- -

A universal vector constructor.

-

- -
-
vector#1cb5c415 {t:Type} # [ t ] = Vector t;

-

Parameters

-

This constructor does not require any parameters.

-

Type

-

Vector t

-

Params additional

-

For serialization write the constructor id 0x1cb5c415:int, then the number of vector elements - #:int, then, one after another, the # of the elements of the type t, that was implicitly passed to the constructor.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/videoSize.html b/data/corefork.telegram.org/constructor/videoSize.html deleted file mode 100644 index f7bd4f2c80..0000000000 --- a/data/corefork.telegram.org/constructor/videoSize.html +++ /dev/null @@ -1,175 +0,0 @@ - - - - - videoSize - - - - - - - - - - - - - -
- -
-
-
- -

videoSize

- -

Animated profile picture in MPEG4 format

-

- -
-
videoSize#de33b094 flags:# type:string w:int h:int size:int video_start_ts:flags.0?double = VideoSize;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
typestringu for animated profile pictures, and v for trimmed and downscaled video previews
wintVideo width
hintVideo height
sizeintFile size
video_start_tsflags.0?doubleTimestamp that should be shown as static preview to the user (seconds)
-

Type

-

VideoSize

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/wallPaper.html b/data/corefork.telegram.org/constructor/wallPaper.html deleted file mode 100644 index cce1877da9..0000000000 --- a/data/corefork.telegram.org/constructor/wallPaper.html +++ /dev/null @@ -1,192 +0,0 @@ - - - - - wallPaper - - - - - - - - - - - - - -
- -
-
-
- -

wallPaper

- -

Wallpaper settings.

-

- -
-
wallPaper#a437c3ed id:long flags:# creator:flags.0?true default:flags.1?true pattern:flags.3?true dark:flags.4?true access_hash:long slug:string document:Document settings:flags.2?WallPaperSettings = WallPaper;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongIdentifier
flags#Flags, see TL conditional fields
creatorflags.0?trueCreator of the wallpaper
defaultflags.1?trueWhether this is the default wallpaper
patternflags.3?truePattern
darkflags.4?trueDark mode
access_hashlongAccess hash
slugstringUnique wallpaper ID
documentDocumentThe actual wallpaper
settingsflags.2?WallPaperSettingsWallpaper settings
-

Type

-

WallPaper

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/wallPaperNoFile.html b/data/corefork.telegram.org/constructor/wallPaperNoFile.html deleted file mode 100644 index a4aad193a5..0000000000 --- a/data/corefork.telegram.org/constructor/wallPaperNoFile.html +++ /dev/null @@ -1,171 +0,0 @@ - - - - - wallPaperNoFile - - - - - - - - - - - - - -
- -
-
-
- -

wallPaperNoFile

- -

Wallpaper with no file access hash, used for example when deleting (unsave=true) wallpapers using account.saveWallPaper, specifying just the wallpaper ID.
-Also used for some default wallpapers which contain only colours.

-

- -
-
wallPaperNoFile#e0804116 id:long flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongWallpaper ID
flags#Flags, see TL conditional fields
defaultflags.1?trueWhether this is the default wallpaper
darkflags.4?trueDark mode
settingsflags.2?WallPaperSettingsWallpaper settings
-

Type

-

WallPaper

-

Related pages

-

account.saveWallPaper

-

Install/uninstall wallpaper

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/wallPaperSettings.html b/data/corefork.telegram.org/constructor/wallPaperSettings.html deleted file mode 100644 index 9f4ab4e1d6..0000000000 --- a/data/corefork.telegram.org/constructor/wallPaperSettings.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - wallPaperSettings - - - - - - - - - - - - - -
- -
-
-
- -

wallPaperSettings

- -

Wallpaper settings

-

- -
-
wallPaperSettings#1dc1bca4 flags:# blur:flags.1?true motion:flags.2?true background_color:flags.0?int second_background_color:flags.4?int third_background_color:flags.5?int fourth_background_color:flags.6?int intensity:flags.3?int rotation:flags.4?int = WallPaperSettings;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
blurflags.1?trueIf set, the wallpaper must be downscaled to fit in 450x450 square and then box-blurred with radius 12
motionflags.2?trueIf set, the background needs to be slightly moved when device is rotated
background_colorflags.0?intIf set, a PNG pattern is to be combined with the color chosen by the user: the main color of the background in RGB24 format
second_background_colorflags.4?intIf set, a PNG pattern is to be combined with the first and second background colors (RGB24 format) in a top-bottom gradient
third_background_colorflags.5?intIf set, a PNG pattern is to be combined with the first, second and third background colors (RGB24 format) in a freeform gradient
fourth_background_colorflags.6?intIf set, a PNG pattern is to be combined with the first, second, third and fourth background colors (RGB24 format) in a freeform gradient
intensityflags.3?intIntensity of the pattern when it is shown above the main background color, 0-100
rotationflags.4?intClockwise rotation angle of the gradient, in degrees; 0-359. Should be always divisible by 45
-

Type

-

WallPaperSettings

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/wallPaperSolid.html b/data/corefork.telegram.org/constructor/wallPaperSolid.html deleted file mode 100644 index f3be02a641..0000000000 --- a/data/corefork.telegram.org/constructor/wallPaperSolid.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - wallPaperSolid - - - - - - - - - - - - - -
- -
-
-
- -

wallPaperSolid

- -

One-color background wallpaper (no image).

-

- -
-
Constructor schema is available as of layer 93. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idintIdentifier
titlestringName
bg_colorintBackground color (RGB)
colorintBasic background color (RGB)
-

Type

-

WallPaper

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/webAuthorization.html b/data/corefork.telegram.org/constructor/webAuthorization.html deleted file mode 100644 index cdf661cd35..0000000000 --- a/data/corefork.telegram.org/constructor/webAuthorization.html +++ /dev/null @@ -1,189 +0,0 @@ - - - - - webAuthorization - - - - - - - - - - - - - -
- -
-
-
- -

webAuthorization

- -

Represents a bot logged in using the Telegram login widget

-

- -
-
webAuthorization#a6f8f452 hash:long bot_id:long domain:string browser:string platform:string date_created:int date_active:int ip:string region:string = WebAuthorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashlongAuthorization hash
bot_idlongBot ID
domainstringThe domain name of the website on which the user has logged in.
browserstringBrowser user-agent
platformstringPlatform
date_createdintWhen was the web session created
date_activeintWhen was the web session last active
ipstringIP address
regionstringRegion, determined from IP address
-

Type

-

WebAuthorization

-

Related pages

-

Telegram Login Widget

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/webDocument.html b/data/corefork.telegram.org/constructor/webDocument.html deleted file mode 100644 index 016d00a38a..0000000000 --- a/data/corefork.telegram.org/constructor/webDocument.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - webDocument - - - - - - - - - - - - - -
- -
-
-
- -

webDocument

- -

Remote document

-

- -
-
webDocument#1c570ed1 url:string access_hash:long size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringDocument URL
access_hashlongAccess hash
sizeintFile size
mime_typestringMIME type
attributesVector<DocumentAttribute>Attributes for media types
-

Type

-

WebDocument

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/webDocumentNoProxy.html b/data/corefork.telegram.org/constructor/webDocumentNoProxy.html deleted file mode 100644 index cef96456d0..0000000000 --- a/data/corefork.telegram.org/constructor/webDocumentNoProxy.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - webDocumentNoProxy - - - - - - - - - - - - - -
- -
-
-
- -

webDocumentNoProxy

- -

Remote document that can be downloaded without proxying through telegram

-

- -
-
webDocumentNoProxy#f9c8bcc6 url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringDocument URL
sizeintFile size
mime_typestringMIME type
attributesVector<DocumentAttribute>Attributes for media types
-

Type

-

WebDocument

-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/webPage.html b/data/corefork.telegram.org/constructor/webPage.html deleted file mode 100644 index 55803a11f9..0000000000 --- a/data/corefork.telegram.org/constructor/webPage.html +++ /dev/null @@ -1,240 +0,0 @@ - - - - - webPage - - - - - - - - - - - - - -
- -
-
-
- -

webPage

- -

Webpage preview

-

- -
-
webPage#e89c45b2 flags:# id:long url:string display_url:string hash:int type:flags.0?string site_name:flags.1?string title:flags.2?string description:flags.3?string photo:flags.4?Photo embed_url:flags.5?string embed_type:flags.5?string embed_width:flags.6?int embed_height:flags.6?int duration:flags.7?int author:flags.8?string document:flags.9?Document cached_page:flags.10?Page attributes:flags.12?Vector<WebPageAttribute> = WebPage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idlongPreview ID
urlstringURL of previewed webpage
display_urlstringWebpage URL to be displayed to the user
hashintHash for pagination, for more info click here
typeflags.0?stringType of the web page. Can be: article, photo, audio, video, document, profile, app, or something else
site_nameflags.1?stringShort name of the site (e.g., Google Docs, App Store)
titleflags.2?stringTitle of the content
descriptionflags.3?stringContent description
photoflags.4?PhotoImage representing the content
embed_urlflags.5?stringURL to show in the embedded preview
embed_typeflags.5?stringMIME type of the embedded preview, (e.g., text/html or video/mp4)
embed_widthflags.6?intWidth of the embedded preview
embed_heightflags.6?intHeight of the embedded preview
durationflags.7?intDuration of the content, in seconds
authorflags.8?stringAuthor of the content
documentflags.9?DocumentPreview of the content as a media file
cached_pageflags.10?PagePage contents in instant view format
attributesflags.12?Vector<WebPageAttribute>Webpage attributes
-

Type

-

WebPage

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/webPageEmpty.html b/data/corefork.telegram.org/constructor/webPageEmpty.html deleted file mode 100644 index 64964739ba..0000000000 --- a/data/corefork.telegram.org/constructor/webPageEmpty.html +++ /dev/null @@ -1,147 +0,0 @@ - - - - - webPageEmpty - - - - - - - - - - - - - -
- -
-
-
- -

webPageEmpty

- -

No preview is available for the webpage

-

- -
-
webPageEmpty#eb1477e8 id:long = WebPage;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idlongPreview ID
-

Type

-

WebPage

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/webPageNotModified.html b/data/corefork.telegram.org/constructor/webPageNotModified.html deleted file mode 100644 index 6f9d87861e..0000000000 --- a/data/corefork.telegram.org/constructor/webPageNotModified.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - webPageNotModified - - - - - - - - - - - - - -
- -
-
-
- -

webPageNotModified

- -

The preview of the webpage hasn't changed

-

- -
-
webPageNotModified#7311ca11 flags:# cached_page_views:flags.0?int = WebPage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
cached_page_viewsflags.0?intPage view count
-

Type

-

WebPage

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/constructor/webPagePending.html b/data/corefork.telegram.org/constructor/webPagePending.html deleted file mode 100644 index bb394c3c99..0000000000 --- a/data/corefork.telegram.org/constructor/webPagePending.html +++ /dev/null @@ -1,152 +0,0 @@ - - - - - webPagePending - - - - - - - - - - - - - -
- -
-
-
- -

webPagePending

- -

A preview of the webpage is currently being generated

-

- -
-
webPagePending#c586da1c id:long date:int = WebPage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongID of preview
dateintWhen was the processing started
-

Type

-

WebPage

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/css/core-widgets.css b/data/corefork.telegram.org/css/core-widgets.css deleted file mode 100644 index 6b86cfbf74..0000000000 --- a/data/corefork.telegram.org/css/core-widgets.css +++ /dev/null @@ -1,105 +0,0 @@ -.widget-accent-colors { - display: flex; - flex-wrap: nowrap; - justify-content: space-between; - max-width: 480px; - margin: 3px 0 0; -} -.widget-accent-colors .widget-accent-color-item { - position: relative; - flex-basis: 42px; - font-weight: normal; - text-align: center; - cursor: pointer; -} -.widget-accent-color-item input.radio { - position: absolute; - left: -5000px; -} -.widget-accent-color-item input.radio + .widget-color-circle:after { - position: absolute; - left: 0; - display: inline-block; - content: ''; - width: 100%; - height: 100%; - border-radius: 50%; - vertical-align: top; - background: url('data:image/svg+xml,%3Csvg height="15" viewBox="0 0 18 15" width="18" xmlns="http://www.w3.org/2000/svg"%3E%3Cg fill="%23fff" fill-rule="evenodd"%3E%3Crect height="8" rx="1.472727" transform="matrix(.70710678 -.70710678 .70710678 .70710678 -5.753048 6.110913)" width="3" x="3" y="6"/%3E%3Crect height="3" rx="1.472727" transform="matrix(.70710678 -.70710678 .70710678 .70710678 -2.081475 9.974874)" width="16" x="3" y="6"/%3E%3C/g%3E%3C/svg%3E') no-repeat center 11px; - transition: transform 0.12s linear; - transform: scale3d(0, 0, 1); -} -.widget-accent-color-item input.radio + .widget-color-circle.bordered, -.widget-accent-color-item input.radio:checked + .widget-color-circle-custom.bordered { - box-shadow: inset 0 0 0 1px #eaeaea; -} -.widget-accent-color-item input.radio + .widget-color-circle-custom.bordered { - border: none; -} -.widget-accent-color-item input.radio + .widget-color-circle.light:after { - background-image: url('data:image/svg+xml,%3Csvg height="15" viewBox="0 0 18 15" width="18" xmlns="http://www.w3.org/2000/svg"%3E%3Cg fill="%2315202b" fill-rule="evenodd"%3E%3Crect height="8" rx="1.472727" transform="matrix(.70710678 -.70710678 .70710678 .70710678 -5.753048 6.110913)" width="3" x="3" y="6"/%3E%3Crect height="3" rx="1.472727" transform="matrix(.70710678 -.70710678 .70710678 .70710678 -2.081475 9.974874)" width="16" x="3" y="6"/%3E%3C/g%3E%3C/svg%3E'); -} -.widget-accent-color-item input.radio:checked + .widget-color-circle:after { - transform: scale3d(1, 1, 1); -} -.widget-color-circle { - position: relative; - display: inline-block; - vertical-align: top; - width: 36px; - height: 36px; - border-radius: 50%; - background-color: #319BE6; - transition: background-color 0.12s ease, box-shadow 0.12s ease; -} -.widget-color-circle-custom { - background-color: #F5F5F5; - color: #F5F5F5; -} -.widget-accent-color-item input.radio + .widget-color-circle-custom:before { - position: absolute; - left: 0; - display: inline-block; - content: ''; - width: 100%; - height: 100%; - vertical-align: top; - background: url('data:image/svg+xml,%3Csvg height="14" viewBox="0 0 15 14" width="15" xmlns="http://www.w3.org/2000/svg"%3E%3Cpath d="m3.9468491 8.55631162c-1.3103539 0-2.36810946 1.04207749-2.36810946 2.33300928 0 1.0187474-.91566899 1.5553396-1.57873964 1.5553396.72622023.9487571 1.96553085 1.5553395 3.15747928 1.5553395 1.7445073 0 3.15747928-1.3920289 3.15747928-3.1106791 0-1.29093179-1.05775556-2.33300928-2.36810946-2.33300928zm10.8222602-7.28676572-1.0577555-1.04207749c-.3078543-.30329121-.8051572-.30329121-1.1130115 0l-7.07275356 6.96792112 2.170767 2.13859186 7.07275356-6.96792112c.3078543-.30329121.3078543-.79322316 0-1.09651437z" fill="%23bdbdbd"/%3E%3C/svg%3E') no-repeat center; - transition: opacity 0.12s ease; -} -.widget-color-label { - font-size: 12px; - line-height: 14px; - margin-top: 8px; - color: #333; -} -.widget-color-label-custom { - transition: opacity 0.12s ease; - position: absolute; - width: 100%; -} -.widget-accent-color-field-item { - transition: all .2s ease; - opacity: 0; -} -.widget-accent-color-field-item input.widget-accent-color-field { - font-size: 12px !important; - line-height: 14px !important; - text-transform: uppercase; - position: relative; - text-align: center; - margin-top: 3px !important; - padding: 5px 0 !important; - color: #222 !important; - width: 52px !important; -} -.widget-accent-color-item input.radio:checked ~ .widget-accent-color-field-item { - opacity: 1; -} -.widget-accent-color-item input.radio:checked ~ .widget-color-circle-custom { - background-color: currentColor !important; -} -.widget-accent-color-item input.radio:checked + .widget-color-circle-custom:before, -.widget-accent-color-item input.radio:checked ~ .widget-color-label-custom { - opacity: 0; -} diff --git a/data/corefork.telegram.org/getProxyConfig.html b/data/corefork.telegram.org/getProxyConfig.html deleted file mode 100644 index 7238f2dd28..0000000000 --- a/data/corefork.telegram.org/getProxyConfig.html +++ /dev/null @@ -1,24 +0,0 @@ -# force_probability 10 10 -default 2; -proxy_for 1 149.154.X.X:8888; -proxy_for -1 149.154.X.X:8888; -proxy_for 2 149.154.X.X:8888; -proxy_for -2 149.154.X.X:8888; -proxy_for 3 149.154.X.X:8888; -proxy_for -3 149.154.X.X:8888; -proxy_for 4 91.108.X.X:8888; -proxy_for 4 91.108.X.X:8888; -proxy_for 4 91.108.X.X:8888; -proxy_for 4 91.108.X.X:8888; -proxy_for 4 91.108.X.X:8888; -proxy_for 4 91.108.X.X:8888; -proxy_for 4 91.108.X.X:8888; -proxy_for 4 91.108.X.X:8888; -proxy_for 4 91.108.X.X:8888; -proxy_for 4 91.108.X.X:8888; -proxy_for -4 149.154.X.X:8888; -proxy_for -4 149.154.X.X:8888; -proxy_for 5 91.108.X.X:8888; -proxy_for 5 91.108.X.X:8888; -proxy_for -5 91.108.X.X:8888; -proxy_for -5 91.108.X.X:8888; diff --git a/data/corefork.telegram.org/import-stickers.html b/data/corefork.telegram.org/import-stickers.html deleted file mode 100644 index 0daae5650c..0000000000 --- a/data/corefork.telegram.org/import-stickers.html +++ /dev/null @@ -1,159 +0,0 @@ - - - - - Importing Stickers to Telegram - - - - - - - - - - - - - -
- -
-
-
-
-

Importing Stickers to Telegram

- -

The easiest way to create stickers on Telegram is to simply upload them using the @stickers bot. This bot can help you upload new stickers, create sticker packs and get usage stats for your stickers and packs.

-

Telegram also offers a platform for developers of apps that help users make their own stickers. For example, apps that allow people to upload pictures of themselves and turn them into stickers.

-

Who is this for?

-

USE this:

-
    -
  • To help people make their own unique custom stickers.
  • -
  • To help people migrate their unique custom stickers they created from another platform.
  • -
-

DON'T use this:

- -

In short, if a set of stickers is already available on Telegram – there's no need to import it!

-

Sticker Importing Apps

-

As of version 7.8, Telegram apps support a simple API for importing stickers.

-
- -
- -
-

WARNING: Each time a user imports stickers, a new sticker pack is created on Telegram. Do not use the importing feature to share stickers you made with other users. If you want to share your stickers, simply upload them using @stickers and share the link of your pack. For example, here's a link to install some Duck Stickers.

-
-

Importing SDKs

-

We have created libraries and sample apps for iOS and Android which you can use to implement importing stickers to Telegram from your app.

-

Sticker Formats

-

Telegram apps support two sticker types. Regardless of the type, each sticker must be associated with at least one emoji that expresses the emotion corresponding to the sticker.

-

Animated Stickers

-

Must be in TGS format, created using the Bodymovin-TG plugin for Adobe After Effects.

-
-

Note: Animated .WEBP is NOT currently supported, only static .WEBP is supported for static stickers. Animated stickers must be in .TGS format. You can also import .WEBM video stickers.

-
-

Max. size: 64 KB
Dimensions: 512x512 px
FPS: 30-60 FPS
Max. duration: 3 seconds

-
-

For full technical details on Telegram animated stickers, see this page.

-
-

Video Stickers

-

Must be in WEBM format with VP9 and alpha channel encoding (transparency is a temporary requirement).

-

Max. size: 256 KB
Max. dimensions: 512x512 px, at least one side of the image must be 512px.
FPS: 30
Max. duration: 3 seconds

-

Static Stickers

-

Must be in PNG or WEBP format with a transparent layer. All static stickers should use white stroke and shadow, exactly like in this example: StickerExample.psd

-

Max. size: 512 KB
Max. dimensions: 512x512 px, at least one side of the image must be 512px.

-
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/js/core-widgets.js b/data/corefork.telegram.org/js/core-widgets.js deleted file mode 100644 index 67bf4c7d05..0000000000 --- a/data/corefork.telegram.org/js/core-widgets.js +++ /dev/null @@ -1,279 +0,0 @@ -function fixColor(color) { - color = color.toUpperCase(); - if (color.length == 1 || color.length == 2) { - color = color + color + color; - } else if (color.length > 3 && color.length < 6) { - color = color.substr(0, 3); - } else if (color.length > 6) { - color = color.substr(0, 6); - } - return color; -} - -function isColorLight(color, k) { - var hsl = rgb2hsl(color); - if (typeof k === 'undefined') k = 0.8; - if (k > 0) return (hsl.l > k); - return (hsl.l < (1 + k)); -} - -function rgb2hsl(rgb) { - rgb = fixColor(rgb); - if (rgb.length == 3) { - rgb = rgb[0] + rgb[0] + rgb[1] + rgb[1] + rgb[2] + rgb[2]; - } - var r = parseInt(rgb.substr(0, 2), 16); - var g = parseInt(rgb.substr(2, 2), 16); - var b = parseInt(rgb.substr(4, 2), 16); - r /= 255; g /= 255; b /= 255; - var max = Math.max(r, g, b), - min = Math.min(r, g, b); - var h, s, l = (max + min) / 2; - if (max == min) { - h = s = 0; // achromatic - } else { - var d = max - min; - s = l > 0.5 ? d / (2 - max - min) : d / (max + min); - switch (max) { - case r: h = (g - b) / d + (g < b ? 6 : 0); break; - case g: h = (b - r) / d + 2; break; - case b: h = (r - g) / d + 4; break; - } - h /= 6; - } - return {h: h, s: s, l: l}; -} - -var PostWidget = { - options: {}, - init: function(options) { - var form = $('#post_widget_config').get(0); - if (!form) return; - PostWidget.options = options || {}; - $('.form-telegram input.form-control[type="text"]').on('change blur', function() { - PostWidget.update(); - }); - $('.form-telegram input.radio, .form-telegram input.checkbox').on('change', function() { - var is_dark = (this.getAttribute('name') == 'dark'); - PostWidget.update(is_dark); - }); - $('.widget-accent-color-item input.radio').on('change', function() { - if (this.value == 'custom') { - $('.widget-accent-color-field').select(); - } - PostWidget.update(); - }); - $('.widget-accent-color-field').on('input', function() { - var val = this.value; - this.value = val.toUpperCase().replace(/[^0-9A-F]+/g, ''); - var color = fixColor(this.value); - $('.widget-color-circle-custom').css('color', color ? '#' + color : '').toggleClass('light', isColorLight(color)).toggleClass('bordered', isColorLight(color, 0.95)); - }); - $('.widget-accent-color-field').on('focus', function() { - $('.widget-accent-color-item .radio[value="custom"]').prop('checked', true); - PostWidget.update(); - }); - PostWidget.update(); - initRipple(); - }, - update: function(toggle_dark) { - var options = PostWidget.options || {}; - var form = $('#post_widget_config').get(0); - if (!form) return; - var tfi = $('#post_link').parents('.textfield-item'); - var post_link = $('#post_link').val() || options.default_link, - match; - if (match = post_link.match(/^(?:(?:https?):\/\/)?(?:t\.me|telegram\.me|telegram\.dog)\/([a-zA-Z0-9_]+\/\d+)(?:\?(.*))?$/i)) { - var post_id = match[1], suffix = match[2] || ''; - var querystring = suffix.split('#')[0]; - var str_values = querystring.split('&'); - var query = {}; - for (var i = 0; i < str_values.length; i++) { - var key_value = str_values[i].split('='); - var key = decodeURIComponent(key_value[0]); - var value = key_value.length > 1 ? decodeURIComponent(key_value[1]) : null; - query[key] = value; - } - var single = typeof query.single !== 'undefined'; - var comment_id = parseInt(query.comment); - } else { - tfi.addClass('is-invalid'); - $('#post_link_error').html(options.link_error); - $('#post_link').one('input', function() { - tfi.removeClass('is-invalid'); - }); - return; - } - tfi.removeClass('is-invalid'); - var width = form.width.value; - if (!width) width = '100%'; - var author_photo = form.author_photo.value; - var dark = form.dark.checked; - var dark_colors = {}; - $('.widget-accent-color-item[data-color]').each(function() { - var color = $(this).attr('data-color'); - var dark_color = $(this).attr('data-dark-color'); - var bg_color = $(this).attr(dark ? 'data-dark-color' : 'data-bg-color'); - var text = $(this).attr(dark ? 'data-dark-text' : 'data-text'); - var cur_color = dark && dark_color ? dark_color : color; - dark_colors[color] = dark_color; - $('.widget-color-circle', this).css('backgroundColor', '#' + bg_color).toggleClass('light', isColorLight(cur_color)).toggleClass('bordered', isColorLight(cur_color, 0.95)); - if (text) { - $('.widget-color-label', this).text(text); - } - }); - var color = form.color.value; - var dark_color = ''; - var customcolor = form.customcolor.value; - if (color == 'default') { - color = ''; - dark_color = ''; - } else if (color == 'custom') { - color = fixColor(customcolor); - if (color != customcolor) { - form.customcolor.value = color; - $('.widget-color-circle-custom').css('color', color ? '#' + color : '').toggleClass('light', isColorLight(color)).toggleClass('bordered', isColorLight(color, 0.95)); - } - dark_color = color; - } else { - dark_color = dark_colors[color] || color; - } - if (!color) { - color = ''; - dark_color = ''; - $('.widget-accent-color-item .radio[value="default"]').prop('checked', true); - var custom_default = form.customcolor.defaultValue; - form.customcolor.value = custom_default; - $('.widget-color-circle-custom').css('color', custom_default ? '#' + custom_default : '').toggleClass('light', isColorLight(custom_default)).toggleClass('bordered', isColorLight(custom_default, 0.95)); - } - var code = ''; - $('#embed_code').val(code); - $('#embed_code').height(0); - $('#embed_code').height($('#embed_code').get(0).scrollHeight); - if (PostWidget.lastCode != code) { - PostWidget.lastCode = code; - $('#widget_container').toggleClass('dark', !!dark); - if (toggle_dark) { - var frame = $('#widget_container iframe').get(0); - Telegram.setWidgetOptions({dark: dark}, frame); - } else { - $('#widget_container').html(code); - } - } - } -}; - -var DiscussionWidget = { - options: {}, - init: function(options) { - var form = $('#discussion_widget_config').get(0); - if (!form) return; - DiscussionWidget.options = options || {}; - $('.form-telegram input.form-control[type="text"]').on('change blur', function() { - DiscussionWidget.update(); - }); - $('.form-telegram input.checkbox').on('change', function() { - var is_dark = (this.getAttribute('name') == 'dark'); - DiscussionWidget.update(is_dark); - }); - $('.widget-accent-color-item input.radio').on('change', function() { - if (this.value == 'custom') { - $('.widget-accent-color-field').select(); - } - DiscussionWidget.update(); - }); - $('.widget-accent-color-field').on('input', function() { - var val = this.value; - this.value = val.toUpperCase().replace(/[^0-9A-F]+/g, ''); - var color = fixColor(this.value); - $('.widget-color-circle-custom').css('color', color ? '#' + color : '').toggleClass('light', isColorLight(color)).toggleClass('bordered', isColorLight(color, 0.95)); - }); - $('.widget-accent-color-field').on('focus', function() { - $('.widget-accent-color-item .radio[value="custom"]').prop('checked', true); - DiscussionWidget.update(); - }); - DiscussionWidget.update(); - initRipple(); - }, - update: function(toggle_dark) { - var options = DiscussionWidget.options || {}; - var form = $('#discussion_widget_config').get(0); - if (!form) return; - var tfi = $('#post_link').parents('.textfield-item'); - var post_link = $('#post_link').val() || options.default_link, - match; - var post_full_id = '', post_id = 0; - if (match = post_link.match(/^(?:(?:https?):\/\/)?(?:t\.me|telegram\.me|telegram\.dog)\/([a-zA-Z0-9_]+(\/\d+)?)/i)) { - post_full_id = match[1]; - post_id = match[2] || 0; - } else { - tfi.addClass('is-invalid'); - $('#post_link_error').html(options.link_error); - $('#post_link').one('input', function() { - tfi.removeClass('is-invalid'); - }); - return; - } - $('.canonical-helper', form).toggleClass('hide', !!post_id); - tfi.removeClass('is-invalid'); - var limit = parseInt(form.comments_limit.value) || 5; - var real_limit = Math.max(3, Math.min(50, limit)); - form.comments_limit.value = real_limit; - var height = parseInt(form.height.value) || 0; - var real_height = height > 0 ? Math.max(300, height) : 0; - form.height.value = real_height || ''; - var dark = form.dark.checked; - var dark_colors = {}; - $('.widget-accent-color-item[data-color]').each(function() { - var color = $(this).attr('data-color'); - var dark_color = $(this).attr('data-dark-color'); - var bg_color = $(this).attr(dark ? 'data-dark-color' : 'data-bg-color'); - var text = $(this).attr(dark ? 'data-dark-text' : 'data-text'); - var cur_color = dark && dark_color ? dark_color : color; - dark_colors[color] = dark_color; - $('.widget-color-circle', this).css('backgroundColor', '#' + bg_color).toggleClass('light', isColorLight(cur_color)).toggleClass('bordered', isColorLight(cur_color, 0.95)); - if (text) { - $('.widget-color-label', this).text(text); - } - }); - var color = form.color.value; - var dark_color = ''; - var customcolor = form.customcolor.value; - if (color == 'default') { - color = ''; - dark_color = ''; - } else if (color == 'custom') { - color = fixColor(customcolor); - if (color != customcolor) { - form.customcolor.value = color; - $('.widget-color-circle-custom').css('color', color ? '#' + color : '').toggleClass('light', isColorLight(color)).toggleClass('bordered', isColorLight(color, 0.95)); - } - dark_color = color; - } else { - dark_color = dark_colors[color] || color; - } - if (!color) { - color = ''; - dark_color = ''; - $('.widget-accent-color-item .radio[value="default"]').prop('checked', true); - var custom_default = form.customcolor.defaultValue; - form.customcolor.value = custom_default; - $('.widget-color-circle-custom').css('color', custom_default ? '#' + custom_default : '').toggleClass('light', isColorLight(custom_default)).toggleClass('bordered', isColorLight(custom_default, 0.95)); - } - var colorful = form.colorful.checked; - var code = ''; - $('#embed_code').val(code); - $('#embed_code').height(0); - $('#embed_code').height($('#embed_code').get(0).scrollHeight); - if (DiscussionWidget.lastCode != code) { - DiscussionWidget.lastCode = code; - $('#widget_container').toggleClass('dark', !!dark); - if (toggle_dark) { - var frame = $('#widget_container iframe').get(0); - Telegram.setWidgetOptions({dark: dark}, frame); - } else { - $('#widget_container').html(code); - } - } - } -}; diff --git a/data/corefork.telegram.org/method/account.acceptAuthorization b/data/corefork.telegram.org/method/account.acceptAuthorization deleted file mode 100644 index 3292165b02..0000000000 --- a/data/corefork.telegram.org/method/account.acceptAuthorization +++ /dev/null @@ -1,170 +0,0 @@ - - - - - account.acceptAuthorization - - - - - - - - - - - - - -
- -
-
-
- -

account.acceptAuthorization

- -

Sends a Telegram Passport authorization form, effectively sharing data with the service

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.acceptAuthorization#f3ed4c73 bot_id:long scope:string public_key:string value_hashes:Vector<SecureValueHash> credentials:SecureCredentialsEncrypted = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
bot_idlongBot ID
scopestringTelegram Passport element types requested by the service
public_keystringService's public key
value_hashesVector<SecureValueHash>Types of values sent and their hashes
credentialsSecureCredentialsEncryptedEncrypted values
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.cancelPasswordEmail b/data/corefork.telegram.org/method/account.cancelPasswordEmail deleted file mode 100644 index 3a22a5529e..0000000000 --- a/data/corefork.telegram.org/method/account.cancelPasswordEmail +++ /dev/null @@ -1,138 +0,0 @@ - - - - - account.cancelPasswordEmail - - - - - - - - - - - - - -
- -
-
-
- -

account.cancelPasswordEmail

- -

Cancel the code that was sent to verify an email to use as 2FA recovery method.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.cancelPasswordEmail#c1cbd5b6 = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Bool

-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.changePhone b/data/corefork.telegram.org/method/account.changePhone deleted file mode 100644 index ed818379f5..0000000000 --- a/data/corefork.telegram.org/method/account.changePhone +++ /dev/null @@ -1,190 +0,0 @@ - - - - - account.changePhone - - - - - - - - - - - - - -
- -
-
-
- -

account.changePhone

- -

Change the phone number of the current account

-

- -
-
userEmpty#d3bc4b7a id:long = User;
-user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
----functions---
-account.changePhone#70c32edb phone_number:string phone_code_hash:string phone_code:string = User;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringNew phone number
phone_code_hashstringPhone code hash received when calling account.sendChangePhoneCode
phone_codestringPhone code received when calling account.sendChangePhoneCode
-

Result

-

User

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PHONE_CODE_EMPTYphone_code is missing.
400PHONE_NUMBER_INVALIDThe phone number is invalid.
400PHONE_NUMBER_OCCUPIEDThe phone number is already in use.
-

Related pages

-

account.sendChangePhoneCode

-

Verify a new phone number to associate to the current account

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.checkUsername b/data/corefork.telegram.org/method/account.checkUsername deleted file mode 100644 index b05b04315b..0000000000 --- a/data/corefork.telegram.org/method/account.checkUsername +++ /dev/null @@ -1,167 +0,0 @@ - - - - - account.checkUsername - - - - - - - - - - - - - -
- -
-
-
- -

account.checkUsername

- -

Validates a username and checks availability.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.checkUsername#2714d86c username:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
usernamestringusername
Accepted characters: A-z (case-insensitive), 0-9 and underscores.
Length: 5-32 characters.
-

Result

-

Return Bool result on whether the passed username can be used.

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400USERNAME_INVALIDUnacceptable username.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.confirmPasswordEmail b/data/corefork.telegram.org/method/account.confirmPasswordEmail deleted file mode 100644 index f960fb7b81..0000000000 --- a/data/corefork.telegram.org/method/account.confirmPasswordEmail +++ /dev/null @@ -1,175 +0,0 @@ - - - - - account.confirmPasswordEmail - - - - - - - - - - - - - -
- -
-
-
- -

account.confirmPasswordEmail

- -

Verify an email to use as 2FA recovery method.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.confirmPasswordEmail#8fdf1920 code:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
codestringThe phone code that was received after setting a recovery email
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CODE_INVALIDCode invalid.
400EMAIL_HASH_EXPIREDEmail hash expired.
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.confirmPhone b/data/corefork.telegram.org/method/account.confirmPhone deleted file mode 100644 index 7f8e380ef1..0000000000 --- a/data/corefork.telegram.org/method/account.confirmPhone +++ /dev/null @@ -1,180 +0,0 @@ - - - - - account.confirmPhone - - - - - - - - - - - - - -
- -
-
-
- -

account.confirmPhone

- -

Confirm a phone number to cancel account deletion, for more info click here »

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.confirmPhone#5f2178c3 phone_code_hash:string phone_code:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_code_hashstringPhone code hash, for more info click here »
phone_codestringSMS code, for more info click here »
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CODE_HASH_INVALIDCode hash invalid.
400PHONE_CODE_EMPTYphone_code is missing.
-

Related pages

-

Account deletion

-

How to reset an account if the 2FA password was forgotten.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.createTheme b/data/corefork.telegram.org/method/account.createTheme deleted file mode 100644 index 33ba13c727..0000000000 --- a/data/corefork.telegram.org/method/account.createTheme +++ /dev/null @@ -1,186 +0,0 @@ - - - - - account.createTheme - - - - - - - - - - - - - -
- -
-
-
- -

account.createTheme

- -

Create a theme

-

- -
-
theme#e802b8dc flags:# creator:flags.0?true default:flags.1?true for_chat:flags.5?true id:long access_hash:long slug:string title:string document:flags.2?Document settings:flags.3?ThemeSettings installs_count:flags.4?int = Theme;
----functions---
-account.createTheme#8432c21f flags:# slug:string title:string document:flags.2?InputDocument settings:flags.3?InputThemeSettings = Theme;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
slugstringUnique theme ID
titlestringTheme name
documentflags.2?InputDocumentTheme file
settingsflags.3?InputThemeSettingsTheme settings
-

Result

-

Theme

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400THEME_MIME_INVALIDThe theme's MIME type is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.declinePasswordReset b/data/corefork.telegram.org/method/account.declinePasswordReset deleted file mode 100644 index e1ca2b8585..0000000000 --- a/data/corefork.telegram.org/method/account.declinePasswordReset +++ /dev/null @@ -1,155 +0,0 @@ - - - - - account.declinePasswordReset - - - - - - - - - - - - - -
- -
-
-
- -

account.declinePasswordReset

- -

Abort a pending 2FA password reset, see here for more info »

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.declinePasswordReset#4c9409f6 = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400RESET_REQUEST_MISSINGNo password reset is in progress.
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.deleteAccount b/data/corefork.telegram.org/method/account.deleteAccount deleted file mode 100644 index 56a03c27d6..0000000000 --- a/data/corefork.telegram.org/method/account.deleteAccount +++ /dev/null @@ -1,170 +0,0 @@ - - - - - account.deleteAccount - - - - - - - - - - - - - -
- -
-
-
- -

account.deleteAccount

- -

Delete the user's account from the telegram servers. Can be used, for example, to delete the account of a user that provided the login code, but forgot the 2FA password and no recovery method is configured.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.deleteAccount#418d4e0b reason:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
reasonstringWhy is the account being deleted, can be empty
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
4202FA_CONFIRM_WAIT_XSince this account is active and protected by a 2FA password, we will delete it in 1 week for security purposes. You can cancel this process at any time, you'll be able to reset your account in X seconds.
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.deleteSecureValue b/data/corefork.telegram.org/method/account.deleteSecureValue deleted file mode 100644 index a5920c95bc..0000000000 --- a/data/corefork.telegram.org/method/account.deleteSecureValue +++ /dev/null @@ -1,153 +0,0 @@ - - - - - account.deleteSecureValue - - - - - - - - - - - - - -
- -
-
-
- -

account.deleteSecureValue

- -

Delete stored Telegram Passport documents, for more info see the passport docs »

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.deleteSecureValue#b880bc4b types:Vector<SecureValueType> = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
typesVector<SecureValueType>Document types to delete
-

Result

-

Bool

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.finishTakeoutSession b/data/corefork.telegram.org/method/account.finishTakeoutSession deleted file mode 100644 index 5910bb8533..0000000000 --- a/data/corefork.telegram.org/method/account.finishTakeoutSession +++ /dev/null @@ -1,172 +0,0 @@ - - - - - account.finishTakeoutSession - - - - - - - - - - - - - -
- -
-
-
- -

account.finishTakeoutSession

- -

Finish account takeout session

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.finishTakeoutSession#1d2652ee flags:# success:flags.0?true = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
successflags.0?trueData exported successfully
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
403TAKEOUT_REQUIREDA takeout session has to be initialized, first.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.getAccountTTL b/data/corefork.telegram.org/method/account.getAccountTTL deleted file mode 100644 index b105c50706..0000000000 --- a/data/corefork.telegram.org/method/account.getAccountTTL +++ /dev/null @@ -1,134 +0,0 @@ - - - - - account.getAccountTTL - - - - - - - - - - - - - -
- -
-
-
- -

account.getAccountTTL

- -

Get days to live of account

-

- -
-
accountDaysTTL#b8d0afdf days:int = AccountDaysTTL;
----functions---
-account.getAccountTTL#8fc711d = AccountDaysTTL;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

AccountDaysTTL

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.getAllSecureValues b/data/corefork.telegram.org/method/account.getAllSecureValues deleted file mode 100644 index d763ca4826..0000000000 --- a/data/corefork.telegram.org/method/account.getAllSecureValues +++ /dev/null @@ -1,136 +0,0 @@ - - - - - account.getAllSecureValues - - - - - - - - - - - - - -
- -
-
-
- -

account.getAllSecureValues

- -

Get all saved Telegram Passport documents, for more info see the passport docs »

-

- -
-
---functions---
-account.getAllSecureValues#b288bc7d = Vector<SecureValue>;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Vector<SecureValue>

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.getAuthorizationForm b/data/corefork.telegram.org/method/account.getAuthorizationForm deleted file mode 100644 index 55e4233610..0000000000 --- a/data/corefork.telegram.org/method/account.getAuthorizationForm +++ /dev/null @@ -1,176 +0,0 @@ - - - - - account.getAuthorizationForm - - - - - - - - - - - - - -
- -
-
-
- -

account.getAuthorizationForm

- -

Returns a Telegram Passport authorization form for sharing data with a service

-

- -
-
account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;
----functions---
-account.getAuthorizationForm#a929597a bot_id:long scope:string public_key:string = account.AuthorizationForm;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
bot_idlongUser identifier of the service's bot
scopestringTelegram Passport element types requested by the service
public_keystringService's public key
-

Result

-

account.AuthorizationForm

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PUBLIC_KEY_REQUIREDA public key is required.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.getAuthorizations b/data/corefork.telegram.org/method/account.getAuthorizations deleted file mode 100644 index da22572747..0000000000 --- a/data/corefork.telegram.org/method/account.getAuthorizations +++ /dev/null @@ -1,134 +0,0 @@ - - - - - account.getAuthorizations - - - - - - - - - - - - - -
- -
-
-
- -

account.getAuthorizations

- -

Get logged-in sessions

-

- -
-
account.authorizations#1250abde authorizations:Vector<Authorization> = account.Authorizations;
----functions---
-account.getAuthorizations#e320c158 = account.Authorizations;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

account.Authorizations

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.getAutoDownloadSettings b/data/corefork.telegram.org/method/account.getAutoDownloadSettings deleted file mode 100644 index 7828dde479..0000000000 --- a/data/corefork.telegram.org/method/account.getAutoDownloadSettings +++ /dev/null @@ -1,134 +0,0 @@ - - - - - account.getAutoDownloadSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.getAutoDownloadSettings

- -

Get media autodownload settings

-

- -
-
account.autoDownloadSettings#63cacf26 low:AutoDownloadSettings medium:AutoDownloadSettings high:AutoDownloadSettings = account.AutoDownloadSettings;
----functions---
-account.getAutoDownloadSettings#56da0b3f = account.AutoDownloadSettings;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

account.AutoDownloadSettings

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.getContactSignUpNotification b/data/corefork.telegram.org/method/account.getContactSignUpNotification deleted file mode 100644 index c75becf1c5..0000000000 --- a/data/corefork.telegram.org/method/account.getContactSignUpNotification +++ /dev/null @@ -1,135 +0,0 @@ - - - - - account.getContactSignUpNotification - - - - - - - - - - - - - -
- -
-
-
- -

account.getContactSignUpNotification

- -

Whether the user will receive notifications when contacts sign up

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.getContactSignUpNotification#9f07c728 = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.getGlobalPrivacySettings b/data/corefork.telegram.org/method/account.getGlobalPrivacySettings deleted file mode 100644 index ba741dd533..0000000000 --- a/data/corefork.telegram.org/method/account.getGlobalPrivacySettings +++ /dev/null @@ -1,134 +0,0 @@ - - - - - account.getGlobalPrivacySettings - - - - - - - - - - - - - -
- -
-
-
- -

account.getGlobalPrivacySettings

- -

Get global privacy settings

-

- -
-
globalPrivacySettings#bea2f424 flags:# archive_and_mute_new_noncontact_peers:flags.0?Bool = GlobalPrivacySettings;
----functions---
-account.getGlobalPrivacySettings#eb2b4cf6 = GlobalPrivacySettings;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

GlobalPrivacySettings

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.getMultiWallPapers b/data/corefork.telegram.org/method/account.getMultiWallPapers deleted file mode 100644 index 9ca2cc83f0..0000000000 --- a/data/corefork.telegram.org/method/account.getMultiWallPapers +++ /dev/null @@ -1,148 +0,0 @@ - - - - - account.getMultiWallPapers - - - - - - - - - - - - - -
- -
-
-
- -

account.getMultiWallPapers

- -

Get info about multiple wallpapers

-

- -
-
---functions---
-account.getMultiWallPapers#65ad71dc wallpapers:Vector<InputWallPaper> = Vector<WallPaper>;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
wallpapersVector<InputWallPaper>Wallpapers to fetch info about
-

Result

-

Vector<WallPaper>

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.getNotifyExceptions b/data/corefork.telegram.org/method/account.getNotifyExceptions deleted file mode 100644 index 96b8cf3aa6..0000000000 --- a/data/corefork.telegram.org/method/account.getNotifyExceptions +++ /dev/null @@ -1,165 +0,0 @@ - - - - - account.getNotifyExceptions - - - - - - - - - - - - - -
- -
-
-
- -

account.getNotifyExceptions

- -

Returns list of chats with non-default notification settings

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-account.getNotifyExceptions#53577479 flags:# compare_sound:flags.1?true peer:flags.0?InputNotifyPeer = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
compare_soundflags.1?trueIf true, chats with non-default sound will also be returned
peerflags.0?InputNotifyPeerIf specified, only chats of the specified category will be returned
-

Result

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.getNotifySettings b/data/corefork.telegram.org/method/account.getNotifySettings deleted file mode 100644 index 55ca584191..0000000000 --- a/data/corefork.telegram.org/method/account.getNotifySettings +++ /dev/null @@ -1,166 +0,0 @@ - - - - - account.getNotifySettings - - - - - - - - - - - - - -
- -
-
-
- -

account.getNotifySettings

- -

Gets current notification settings for a given user/group, from all users/all groups.

-

- -
-
peerNotifySettings#af509d20 flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = PeerNotifySettings;
----functions---
-account.getNotifySettings#12b3ad31 peer:InputNotifyPeer = PeerNotifySettings;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputNotifyPeerNotification source
-

Result

-

Returns a PeerNotifySettings object containing current notification settings.

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.getPassword b/data/corefork.telegram.org/method/account.getPassword deleted file mode 100644 index ba8a9fd2e7..0000000000 --- a/data/corefork.telegram.org/method/account.getPassword +++ /dev/null @@ -1,134 +0,0 @@ - - - - - account.getPassword - - - - - - - - - - - - - -
- -
-
-
- -

account.getPassword

- -

Obtain configuration for two-factor authorization with password

-

- -
-
account.password#185b184f flags:# has_recovery:flags.0?true has_secure_values:flags.1?true has_password:flags.2?true current_algo:flags.2?PasswordKdfAlgo srp_B:flags.2?bytes srp_id:flags.2?long hint:flags.3?string email_unconfirmed_pattern:flags.4?string new_algo:PasswordKdfAlgo new_secure_algo:SecurePasswordKdfAlgo secure_random:bytes pending_reset_date:flags.5?int = account.Password;
----functions---
-account.getPassword#548a30f5 = account.Password;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

account.Password

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.getPasswordSettings b/data/corefork.telegram.org/method/account.getPasswordSettings deleted file mode 100644 index 4420ff1f14..0000000000 --- a/data/corefork.telegram.org/method/account.getPasswordSettings +++ /dev/null @@ -1,170 +0,0 @@ - - - - - account.getPasswordSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.getPasswordSettings

- -

Get private info associated to the password info (recovery email, telegram passport info & so on)

-

- -
-
account.passwordSettings#9a5c33e5 flags:# email:flags.0?string secure_settings:flags.1?SecureSecretSettings = account.PasswordSettings;
----functions---
-account.getPasswordSettings#9cd4eaf9 password:InputCheckPasswordSRP = account.PasswordSettings;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
passwordInputCheckPasswordSRPThe password (see SRP)
-

Result

-

account.PasswordSettings

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PASSWORD_HASH_INVALIDThe provided password hash is invalid.
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.getPrivacy b/data/corefork.telegram.org/method/account.getPrivacy deleted file mode 100644 index 65b6b9292c..0000000000 --- a/data/corefork.telegram.org/method/account.getPrivacy +++ /dev/null @@ -1,166 +0,0 @@ - - - - - account.getPrivacy - - - - - - - - - - - - - -
- -
-
-
- -

account.getPrivacy

- -

Get privacy settings of current account

-

- -
-
account.privacyRules#50a04e45 rules:Vector<PrivacyRule> chats:Vector<Chat> users:Vector<User> = account.PrivacyRules;
----functions---
-account.getPrivacy#dadbc950 key:InputPrivacyKey = account.PrivacyRules;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
keyInputPrivacyKeyPeer category whose privacy settings should be fetched
-

Result

-

account.PrivacyRules

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PRIVACY_KEY_INVALIDThe privacy key is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.getSecureValue b/data/corefork.telegram.org/method/account.getSecureValue deleted file mode 100644 index edab1df248..0000000000 --- a/data/corefork.telegram.org/method/account.getSecureValue +++ /dev/null @@ -1,151 +0,0 @@ - - - - - account.getSecureValue - - - - - - - - - - - - - -
- -
-
-
- -

account.getSecureValue

- -

Get saved Telegram Passport document, for more info see the passport docs »

-

- -
-
---functions---
-account.getSecureValue#73665bc2 types:Vector<SecureValueType> = Vector<SecureValue>;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
typesVector<SecureValueType>Requested value types
-

Result

-

Vector<SecureValue>

-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.getTheme b/data/corefork.telegram.org/method/account.getTheme deleted file mode 100644 index 7eb0b294da..0000000000 --- a/data/corefork.telegram.org/method/account.getTheme +++ /dev/null @@ -1,181 +0,0 @@ - - - - - account.getTheme - - - - - - - - - - - - - -
- -
-
-
- -

account.getTheme

- -

Get theme information

-

- -
-
theme#e802b8dc flags:# creator:flags.0?true default:flags.1?true for_chat:flags.5?true id:long access_hash:long slug:string title:string document:flags.2?Document settings:flags.3?ThemeSettings installs_count:flags.4?int = Theme;
----functions---
-account.getTheme#8d9d742b format:string theme:InputTheme document_id:long = Theme;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
formatstringTheme format, a string that identifies the theming engines supported by the client
themeInputThemeTheme
document_idlongDocument ID
-

Result

-

Theme

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400THEME_FORMAT_INVALIDInvalid theme format provided.
400THEME_INVALIDInvalid theme provided.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.getThemes b/data/corefork.telegram.org/method/account.getThemes deleted file mode 100644 index 1032acae44..0000000000 --- a/data/corefork.telegram.org/method/account.getThemes +++ /dev/null @@ -1,158 +0,0 @@ - - - - - account.getThemes - - - - - - - - - - - - - -
- -
-
-
- -

account.getThemes

- -

Get installed themes

-

- -
-
account.themesNotModified#f41eb622 = account.Themes;
-account.themes#9a3d8c6d hash:long themes:Vector<Theme> = account.Themes;
----functions---
-account.getThemes#7206e458 format:string hash:long = account.Themes;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
formatstringTheme format, a string that identifies the theming engines supported by the client
hashlongHash for pagination, for more info click here
-

Result

-

account.Themes

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.getTmpPassword b/data/corefork.telegram.org/method/account.getTmpPassword deleted file mode 100644 index 959f95052c..0000000000 --- a/data/corefork.telegram.org/method/account.getTmpPassword +++ /dev/null @@ -1,176 +0,0 @@ - - - - - account.getTmpPassword - - - - - - - - - - - - - -
- -
-
-
- -

account.getTmpPassword

- -

Get temporary payment password

-

- -
-
account.tmpPassword#db64fd34 tmp_password:bytes valid_until:int = account.TmpPassword;
----functions---
-account.getTmpPassword#449e0b51 password:InputCheckPasswordSRP period:int = account.TmpPassword;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
passwordInputCheckPasswordSRPSRP password parameters
periodintTime during which the temporary password will be valid, in seconds; should be between 60 and 86400
-

Result

-

account.TmpPassword

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PASSWORD_HASH_INVALIDThe provided password hash is invalid.
400TMP_PASSWORD_DISABLEDThe temporary password is disabled.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.getWallPaper b/data/corefork.telegram.org/method/account.getWallPaper deleted file mode 100644 index d09ea6d53b..0000000000 --- a/data/corefork.telegram.org/method/account.getWallPaper +++ /dev/null @@ -1,167 +0,0 @@ - - - - - account.getWallPaper - - - - - - - - - - - - - -
- -
-
-
- -

account.getWallPaper

- -

Get info about a certain wallpaper

-

- -
-
wallPaper#a437c3ed id:long flags:# creator:flags.0?true default:flags.1?true pattern:flags.3?true dark:flags.4?true access_hash:long slug:string document:Document settings:flags.2?WallPaperSettings = WallPaper;
-wallPaperNoFile#e0804116 id:long flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;
----functions---
-account.getWallPaper#fc8ddbea wallpaper:InputWallPaper = WallPaper;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
wallpaperInputWallPaperThe wallpaper to get info about
-

Result

-

WallPaper

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400WALLPAPER_INVALIDThe specified wallpaper is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.getWallPapers b/data/corefork.telegram.org/method/account.getWallPapers deleted file mode 100644 index 11acd2d24a..0000000000 --- a/data/corefork.telegram.org/method/account.getWallPapers +++ /dev/null @@ -1,153 +0,0 @@ - - - - - account.getWallPapers - - - - - - - - - - - - - -
- -
-
-
- -

account.getWallPapers

- -

Returns a list of available wallpapers.

-

- -
-
account.wallPapersNotModified#1c199183 = account.WallPapers;
-account.wallPapers#cdc3858c hash:long wallpapers:Vector<WallPaper> = account.WallPapers;
----functions---
-account.getWallPapers#7967d36 hash:long = account.WallPapers;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
-

Result

-

Vector<WallPaper>

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.getWebAuthorizations b/data/corefork.telegram.org/method/account.getWebAuthorizations deleted file mode 100644 index 839d82e415..0000000000 --- a/data/corefork.telegram.org/method/account.getWebAuthorizations +++ /dev/null @@ -1,136 +0,0 @@ - - - - - account.getWebAuthorizations - - - - - - - - - - - - - -
- -
-
-
- -

account.getWebAuthorizations

- -

Get web login widget authorizations

-

- -
-
account.webAuthorizations#ed56c9fc authorizations:Vector<WebAuthorization> users:Vector<User> = account.WebAuthorizations;
----functions---
-account.getWebAuthorizations#182e6d6f = account.WebAuthorizations;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

account.WebAuthorizations

-

Related pages

-

Telegram Login Widget

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.initTakeoutSession b/data/corefork.telegram.org/method/account.initTakeoutSession deleted file mode 100644 index d97072f320..0000000000 --- a/data/corefork.telegram.org/method/account.initTakeoutSession +++ /dev/null @@ -1,204 +0,0 @@ - - - - - account.initTakeoutSession - - - - - - - - - - - - - -
- -
-
-
- -

account.initTakeoutSession

- -

Initialize account takeout session

-

- -
-
account.takeout#4dba4501 id:long = account.Takeout;
----functions---
-account.initTakeoutSession#f05b4804 flags:# contacts:flags.0?true message_users:flags.1?true message_chats:flags.2?true message_megagroups:flags.3?true message_channels:flags.4?true files:flags.5?true file_max_size:flags.5?int = account.Takeout;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
contactsflags.0?trueWhether to export contacts
message_usersflags.1?trueWhether to export messages in private chats
message_chatsflags.2?trueWhether to export messages in legacy groups
message_megagroupsflags.3?trueWhether to export messages in supergroups
message_channelsflags.4?trueWhether to export messages in channels
filesflags.5?trueWhether to export files
file_max_sizeflags.5?intMaximum size of files to export
-

Result

-

account.Takeout

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
420TAKEOUT_INIT_DELAY_XWait X seconds before initing takeout.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.installTheme b/data/corefork.telegram.org/method/account.installTheme deleted file mode 100644 index 115dddc218..0000000000 --- a/data/corefork.telegram.org/method/account.installTheme +++ /dev/null @@ -1,165 +0,0 @@ - - - - - account.installTheme - - - - - - - - - - - - - -
- -
-
-
- -

account.installTheme

- -

Install a theme

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.installTheme#7ae43737 flags:# dark:flags.0?true format:flags.1?string theme:flags.1?InputTheme = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
darkflags.0?trueWhether to install the dark version
formatflags.1?stringTheme format, a string that identifies the theming engines supported by the client
themeflags.1?InputThemeTheme to install
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.installWallPaper b/data/corefork.telegram.org/method/account.installWallPaper deleted file mode 100644 index 7298bc5a0b..0000000000 --- a/data/corefork.telegram.org/method/account.installWallPaper +++ /dev/null @@ -1,172 +0,0 @@ - - - - - account.installWallPaper - - - - - - - - - - - - - -
- -
-
-
- -

account.installWallPaper

- -

Install wallpaper

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.installWallPaper#feed5769 wallpaper:InputWallPaper settings:WallPaperSettings = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
wallpaperInputWallPaperWallpaper to install
settingsWallPaperSettingsWallpaper settings
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400WALLPAPER_INVALIDThe specified wallpaper is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.registerDevice b/data/corefork.telegram.org/method/account.registerDevice deleted file mode 100644 index a097a0036e..0000000000 --- a/data/corefork.telegram.org/method/account.registerDevice +++ /dev/null @@ -1,217 +0,0 @@ - - - - - account.registerDevice - - - - - - - - - - - - - -
- -
-
-
- -

account.registerDevice

- -

Register device to receive PUSH notifications

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.registerDevice#ec86017a flags:# no_muted:flags.0?true token_type:int token:string app_sandbox:Bool secret:bytes other_uids:Vector<long> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
no_mutedflags.0?trueAvoid receiving (silent and invisible background) notifications. Useful to save battery.
token_typeintDevice 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
tokenstringDevice token
app_sandboxBoolIf (boolTrue) is transmitted, a sandbox-certificate will be used during transmission.
secretbytesFor FCM and APNS VoIP, optional encryption key used to encrypt push notifications
other_uidsVector<long>List of user identifiers of other users currently using the client
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400TOKEN_INVALIDThe provided token is invalid.
400WEBPUSH_AUTH_INVALIDThe specified web push authentication secret is invalid.
400WEBPUSH_KEY_INVALIDThe specified web push elliptic curve Diffie-Hellman public key is invalid.
400WEBPUSH_TOKEN_INVALIDThe 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.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.reportPeer b/data/corefork.telegram.org/method/account.reportPeer deleted file mode 100644 index 0b1608397e..0000000000 --- a/data/corefork.telegram.org/method/account.reportPeer +++ /dev/null @@ -1,182 +0,0 @@ - - - - - account.reportPeer - - - - - - - - - - - - - -
- -
-
-
- -

account.reportPeer

- -

Report a peer for violation of telegram's Terms of Service

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.reportPeer#c5ba3d86 peer:InputPeer reason:ReportReason message:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe peer to report
reasonReportReasonThe reason why this peer is being reported
messagestringComment for report moderation
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.reportProfilePhoto b/data/corefork.telegram.org/method/account.reportProfilePhoto deleted file mode 100644 index d3d2fc589a..0000000000 --- a/data/corefork.telegram.org/method/account.reportProfilePhoto +++ /dev/null @@ -1,165 +0,0 @@ - - - - - account.reportProfilePhoto - - - - - - - - - - - - - -
- -
-
-
- -

account.reportProfilePhoto

- -

Report a profile photo of a dialog

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.reportProfilePhoto#fa8cc6f5 peer:InputPeer photo_id:InputPhoto reason:ReportReason message:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe dialog
photo_idInputPhotoDialog photo ID
reasonReportReasonReport reason
messagestringComment for report moderation
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.resetAuthorization b/data/corefork.telegram.org/method/account.resetAuthorization deleted file mode 100644 index 482cdec4e1..0000000000 --- a/data/corefork.telegram.org/method/account.resetAuthorization +++ /dev/null @@ -1,175 +0,0 @@ - - - - - account.resetAuthorization - - - - - - - - - - - - - -
- -
-
-
- -

account.resetAuthorization

- -

Log out an active authorized session by its hash

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.resetAuthorization#df77f3bc hash:long = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashlongSession hash
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
406FRESH_RESET_AUTHORISATION_FORBIDDENYou can't logout other sessions if less than 24 hours have passed since you logged on the current session.
400HASH_INVALIDThe provided hash is invalid.
-

Related pages

-

User Authorization

-

How to register a user's phone to start using the API.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.resetNotifySettings b/data/corefork.telegram.org/method/account.resetNotifySettings deleted file mode 100644 index a0b6c04bf2..0000000000 --- a/data/corefork.telegram.org/method/account.resetNotifySettings +++ /dev/null @@ -1,135 +0,0 @@ - - - - - account.resetNotifySettings - - - - - - - - - - - - - -
- -
-
-
- -

account.resetNotifySettings

- -

Resets all notification settings from users and groups.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.resetNotifySettings#db7e1747 = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.resetPassword b/data/corefork.telegram.org/method/account.resetPassword deleted file mode 100644 index 357c4dfee7..0000000000 --- a/data/corefork.telegram.org/method/account.resetPassword +++ /dev/null @@ -1,139 +0,0 @@ - - - - - account.resetPassword - - - - - - - - - - - - - -
- -
-
-
- -

account.resetPassword

- -

Initiate a 2FA password reset: can only be used if the user is already logged-in, see here for more info »

-

- -
-
account.resetPasswordFailedWait#e3779861 retry_date:int = account.ResetPasswordResult;
-account.resetPasswordRequestedWait#e9effc7d until_date:int = account.ResetPasswordResult;
-account.resetPasswordOk#e926d63e = account.ResetPasswordResult;
----functions---
-account.resetPassword#9308ce1b = account.ResetPasswordResult;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

account.ResetPasswordResult

-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.resetWallPapers b/data/corefork.telegram.org/method/account.resetWallPapers deleted file mode 100644 index c0ec14aa15..0000000000 --- a/data/corefork.telegram.org/method/account.resetWallPapers +++ /dev/null @@ -1,135 +0,0 @@ - - - - - account.resetWallPapers - - - - - - - - - - - - - -
- -
-
-
- -

account.resetWallPapers

- -

Delete installed wallpapers

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.resetWallPapers#bb3b9804 = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.resetWebAuthorization b/data/corefork.telegram.org/method/account.resetWebAuthorization deleted file mode 100644 index a86255ffb7..0000000000 --- a/data/corefork.telegram.org/method/account.resetWebAuthorization +++ /dev/null @@ -1,171 +0,0 @@ - - - - - account.resetWebAuthorization - - - - - - - - - - - - - -
- -
-
-
- -

account.resetWebAuthorization

- -

Log out an active web telegram login session

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.resetWebAuthorization#2d01b9ef hash:long = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashlongSession hash
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400HASH_INVALIDThe provided hash is invalid.
-

Related pages

-

webAuthorization

-

Represents a bot logged in using the Telegram login widget

-

Telegram Login Widget

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.resetWebAuthorizations b/data/corefork.telegram.org/method/account.resetWebAuthorizations deleted file mode 100644 index 771b11ffbd..0000000000 --- a/data/corefork.telegram.org/method/account.resetWebAuthorizations +++ /dev/null @@ -1,137 +0,0 @@ - - - - - account.resetWebAuthorizations - - - - - - - - - - - - - -
- -
-
-
- -

account.resetWebAuthorizations

- -

Reset all active web telegram login sessions

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.resetWebAuthorizations#682d2594 = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Bool

-

Related pages

-

Telegram Login Widget

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.saveAutoDownloadSettings b/data/corefork.telegram.org/method/account.saveAutoDownloadSettings deleted file mode 100644 index c75385db1d..0000000000 --- a/data/corefork.telegram.org/method/account.saveAutoDownloadSettings +++ /dev/null @@ -1,165 +0,0 @@ - - - - - account.saveAutoDownloadSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.saveAutoDownloadSettings

- -

Change media autodownload settings

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.saveAutoDownloadSettings#76f36233 flags:# low:flags.0?true high:flags.1?true settings:AutoDownloadSettings = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
lowflags.0?trueWhether to save settings in the low data usage preset
highflags.1?trueWhether to save settings in the high data usage preset
settingsAutoDownloadSettingsMedia autodownload settings
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.saveSecureValue b/data/corefork.telegram.org/method/account.saveSecureValue deleted file mode 100644 index 1ff2c7aab7..0000000000 --- a/data/corefork.telegram.org/method/account.saveSecureValue +++ /dev/null @@ -1,174 +0,0 @@ - - - - - account.saveSecureValue - - - - - - - - - - - - - -
- -
-
-
- -

account.saveSecureValue

- -

Securely save Telegram Passport document, for more info see the passport docs »

-

- -
-
secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;
----functions---
-account.saveSecureValue#899fe31d value:InputSecureValue secure_secret_id:long = SecureValue;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
valueInputSecureValueSecure value, for more info see the passport docs »
secure_secret_idlongPassport secret hash, for more info see the passport docs »
-

Result

-

SecureValue

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PASSWORD_REQUIREDA 2FA password must be configured to use Telegram Passport.
-

Related pages

-

Telegram Passport Encryption Details

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.saveTheme b/data/corefork.telegram.org/method/account.saveTheme deleted file mode 100644 index f08fb3dca8..0000000000 --- a/data/corefork.telegram.org/method/account.saveTheme +++ /dev/null @@ -1,155 +0,0 @@ - - - - - account.saveTheme - - - - - - - - - - - - - -
- -
-
-
- -

account.saveTheme

- -

Save a theme

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.saveTheme#f257106c theme:InputTheme unsave:Bool = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
themeInputThemeTheme to save
unsaveBoolUnsave
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.saveWallPaper b/data/corefork.telegram.org/method/account.saveWallPaper deleted file mode 100644 index b963d5b9b3..0000000000 --- a/data/corefork.telegram.org/method/account.saveWallPaper +++ /dev/null @@ -1,177 +0,0 @@ - - - - - account.saveWallPaper - - - - - - - - - - - - - -
- -
-
-
- -

account.saveWallPaper

- -

Install/uninstall wallpaper

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.saveWallPaper#6c5a5b37 wallpaper:InputWallPaper unsave:Bool settings:WallPaperSettings = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
wallpaperInputWallPaperWallpaper to save
unsaveBoolUninstall wallpaper?
settingsWallPaperSettingsWallpaper settings
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400WALLPAPER_INVALIDThe specified wallpaper is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.sendChangePhoneCode b/data/corefork.telegram.org/method/account.sendChangePhoneCode deleted file mode 100644 index c54ab9b563..0000000000 --- a/data/corefork.telegram.org/method/account.sendChangePhoneCode +++ /dev/null @@ -1,186 +0,0 @@ - - - - - account.sendChangePhoneCode - - - - - - - - - - - - - -
- -
-
-
- -

account.sendChangePhoneCode

- -

Verify a new phone number to associate to the current account

-

- -
-
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
----functions---
-account.sendChangePhoneCode#82574ae5 phone_number:string settings:CodeSettings = auth.SentCode;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringNew phone number
settingsCodeSettingsPhone code settings
-

Result

-

auth.SentCode

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
406FRESH_CHANGE_PHONE_FORBIDDENYou can't change phone number right after logging in, please wait at least 24 hours.
400PHONE_NUMBER_BANNEDThe provided phone number is banned from telegram.
400PHONE_NUMBER_INVALIDThe phone number is invalid.
400PHONE_NUMBER_OCCUPIEDThe phone number is already in use.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.sendConfirmPhoneCode b/data/corefork.telegram.org/method/account.sendConfirmPhoneCode deleted file mode 100644 index 30be036b63..0000000000 --- a/data/corefork.telegram.org/method/account.sendConfirmPhoneCode +++ /dev/null @@ -1,174 +0,0 @@ - - - - - account.sendConfirmPhoneCode - - - - - - - - - - - - - -
- -
-
-
- -

account.sendConfirmPhoneCode

- -

Send confirmation code to cancel account deletion, for more info click here »

-

- -
-
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
----functions---
-account.sendConfirmPhoneCode#1b3faa88 hash:string settings:CodeSettings = auth.SentCode;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
hashstringThe hash from the service notification, for more info click here »
settingsCodeSettingsPhone code settings
-

Result

-

auth.SentCode

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400HASH_INVALIDThe provided hash is invalid.
-

Related pages

-

Account deletion

-

How to reset an account if the 2FA password was forgotten.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.sendVerifyEmailCode b/data/corefork.telegram.org/method/account.sendVerifyEmailCode deleted file mode 100644 index ecf1047fd3..0000000000 --- a/data/corefork.telegram.org/method/account.sendVerifyEmailCode +++ /dev/null @@ -1,168 +0,0 @@ - - - - - account.sendVerifyEmailCode - - - - - - - - - - - - - -
- -
-
-
- -

account.sendVerifyEmailCode

- -

Send the verification email code for telegram passport.

-

- -
-
account.sentEmailCode#811f854f email_pattern:string length:int = account.SentEmailCode;
----functions---
-account.sendVerifyEmailCode#7011509f email:string = account.SentEmailCode;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
emailstringThe email where to send the code
-

Result

-

account.SentEmailCode

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400EMAIL_INVALIDThe specified email is invalid.
-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.sendVerifyPhoneCode b/data/corefork.telegram.org/method/account.sendVerifyPhoneCode deleted file mode 100644 index 2715cf9415..0000000000 --- a/data/corefork.telegram.org/method/account.sendVerifyPhoneCode +++ /dev/null @@ -1,173 +0,0 @@ - - - - - account.sendVerifyPhoneCode - - - - - - - - - - - - - -
- -
-
-
- -

account.sendVerifyPhoneCode

- -

Send the verification phone code for telegram passport.

-

- -
-
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
----functions---
-account.sendVerifyPhoneCode#a5a356f9 phone_number:string settings:CodeSettings = auth.SentCode;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringThe phone number to verify
settingsCodeSettingsPhone code settings
-

Result

-

auth.SentCode

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PHONE_NUMBER_INVALIDThe phone number is invalid.
-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.setAccountTTL b/data/corefork.telegram.org/method/account.setAccountTTL deleted file mode 100644 index e44535d1d1..0000000000 --- a/data/corefork.telegram.org/method/account.setAccountTTL +++ /dev/null @@ -1,167 +0,0 @@ - - - - - account.setAccountTTL - - - - - - - - - - - - - -
- -
-
-
- -

account.setAccountTTL

- -

Set account self-destruction period

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.setAccountTTL#2442485e ttl:AccountDaysTTL = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
ttlAccountDaysTTLTime to live in days
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400TTL_DAYS_INVALIDThe provided TTL is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.setContactSignUpNotification b/data/corefork.telegram.org/method/account.setContactSignUpNotification deleted file mode 100644 index 4e689a9599..0000000000 --- a/data/corefork.telegram.org/method/account.setContactSignUpNotification +++ /dev/null @@ -1,150 +0,0 @@ - - - - - account.setContactSignUpNotification - - - - - - - - - - - - - -
- -
-
-
- -

account.setContactSignUpNotification

- -

Toggle contact sign up notifications

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.setContactSignUpNotification#cff43f61 silent:Bool = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
silentBoolWhether to disable contact sign up notifications
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.setContentSettings b/data/corefork.telegram.org/method/account.setContentSettings deleted file mode 100644 index 89ff7b5ee6..0000000000 --- a/data/corefork.telegram.org/method/account.setContentSettings +++ /dev/null @@ -1,172 +0,0 @@ - - - - - account.setContentSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.setContentSettings

- -

Set sensitive content settings (for viewing or hiding NSFW content)

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.setContentSettings#b574b16b flags:# sensitive_enabled:flags.0?true = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
sensitive_enabledflags.0?trueEnable NSFW content
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
403SENSITIVE_CHANGE_FORBIDDENYou can't change your sensitive content settings.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.setGlobalPrivacySettings b/data/corefork.telegram.org/method/account.setGlobalPrivacySettings deleted file mode 100644 index 01a004581b..0000000000 --- a/data/corefork.telegram.org/method/account.setGlobalPrivacySettings +++ /dev/null @@ -1,166 +0,0 @@ - - - - - account.setGlobalPrivacySettings - - - - - - - - - - - - - -
- -
-
-
- -

account.setGlobalPrivacySettings

- -

Set global privacy settings

-

- -
-
globalPrivacySettings#bea2f424 flags:# archive_and_mute_new_noncontact_peers:flags.0?Bool = GlobalPrivacySettings;
----functions---
-account.setGlobalPrivacySettings#1edaaac2 settings:GlobalPrivacySettings = GlobalPrivacySettings;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
settingsGlobalPrivacySettingsGlobal privacy settings
-

Result

-

GlobalPrivacySettings

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400AUTOARCHIVE_NOT_AVAILABLEThe autoarchive setting is not available at this time: please check the value of the autoarchive_setting_available field in client config » before calling this method.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.setPrivacy b/data/corefork.telegram.org/method/account.setPrivacy deleted file mode 100644 index 6f4e1e8093..0000000000 --- a/data/corefork.telegram.org/method/account.setPrivacy +++ /dev/null @@ -1,181 +0,0 @@ - - - - - account.setPrivacy - - - - - - - - - - - - - -
- -
-
-
- -

account.setPrivacy

- -

Change privacy settings of current account

-

- -
-
account.privacyRules#50a04e45 rules:Vector<PrivacyRule> chats:Vector<Chat> users:Vector<User> = account.PrivacyRules;
----functions---
-account.setPrivacy#c9f81ce8 key:InputPrivacyKey rules:Vector<InputPrivacyRule> = account.PrivacyRules;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
keyInputPrivacyKeyPeers to which the privacy rules apply
rulesVector<InputPrivacyRule>New privacy rules
-

Result

-

account.PrivacyRules

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PRIVACY_KEY_INVALIDThe privacy key is invalid.
400PRIVACY_TOO_LONGToo many privacy rules were specified, the current limit is 1000.
400PRIVACY_VALUE_INVALIDThe specified privacy rule combination is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.unregisterDevice b/data/corefork.telegram.org/method/account.unregisterDevice deleted file mode 100644 index 7e28dbe92e..0000000000 --- a/data/corefork.telegram.org/method/account.unregisterDevice +++ /dev/null @@ -1,180 +0,0 @@ - - - - - account.unregisterDevice - - - - - - - - - - - - - -
- -
-
-
- -

account.unregisterDevice

- -

Deletes a device by its token, stops sending PUSH-notifications to it.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.unregisterDevice#6a0d3206 token_type:int token:string other_uids:Vector<long> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
token_typeintDevice 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
tokenstringDevice token
other_uidsVector<long>List of user identifiers of other users currently using the client
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400TOKEN_INVALIDThe provided token is invalid.
-

Related pages

-

Handling PUSH-notifications

-

How to subscribe to and handle PUSH notifications

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.updateDeviceLocked b/data/corefork.telegram.org/method/account.updateDeviceLocked deleted file mode 100644 index 21437ff9d6..0000000000 --- a/data/corefork.telegram.org/method/account.updateDeviceLocked +++ /dev/null @@ -1,153 +0,0 @@ - - - - - account.updateDeviceLocked - - - - - - - - - - - - - -
- -
-
-
- -

account.updateDeviceLocked

- -

When client-side passcode lock feature is enabled, will not show message texts in incoming PUSH notifications.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.updateDeviceLocked#38df3532 period:int = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
periodintInactivity period after which to start hiding message texts in PUSH notifications.
-

Result

-

Bool

-

Related pages

-

Handling PUSH-notifications

-

How to subscribe to and handle PUSH notifications

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.updateNotifySettings b/data/corefork.telegram.org/method/account.updateNotifySettings deleted file mode 100644 index d460a3f380..0000000000 --- a/data/corefork.telegram.org/method/account.updateNotifySettings +++ /dev/null @@ -1,192 +0,0 @@ - - - - - account.updateNotifySettings - - - - - - - - - - - - - -
- -
-
-
- -

account.updateNotifySettings

- -

Edits notification settings from a given user/group, from all users/all groups.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.updateNotifySettings#84be5b93 peer:InputNotifyPeer settings:InputPeerNotifySettings = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputNotifyPeerNotification source
settingsInputPeerNotifySettingsNotification settings
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400SETTINGS_INVALIDInvalid settings were provided.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.updatePasswordSettings b/data/corefork.telegram.org/method/account.updatePasswordSettings deleted file mode 100644 index 3c9ee4f64e..0000000000 --- a/data/corefork.telegram.org/method/account.updatePasswordSettings +++ /dev/null @@ -1,207 +0,0 @@ - - - - - account.updatePasswordSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.updatePasswordSettings

- -

Set a new 2FA password

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.updatePasswordSettings#a59b102f password:InputCheckPasswordSRP new_settings:account.PasswordInputSettings = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
passwordInputCheckPasswordSRPThe old password (see SRP)
new_settingsaccount.PasswordInputSettingsThe new password (see SRP)
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400EMAIL_UNCONFIRMEDEmail unconfirmed.
400EMAIL_UNCONFIRMED_XThe provided email isn't confirmed, X is the length of the verification code that was just sent to the email: use account.verifyEmail to enter the received verification code and enable the recovery email.
400NEW_SALT_INVALIDThe new salt is invalid.
400NEW_SETTINGS_INVALIDThe new password settings are invalid.
400PASSWORD_HASH_INVALIDThe old password hash is invalid.
400SRP_ID_INVALIDInvalid SRP ID provided.
400SRP_PASSWORD_CHANGEDPassword has changed.
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

-

account.verifyEmail

-

Verify an email address for telegram passport.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.updateProfile b/data/corefork.telegram.org/method/account.updateProfile deleted file mode 100644 index f350d7ccde..0000000000 --- a/data/corefork.telegram.org/method/account.updateProfile +++ /dev/null @@ -1,187 +0,0 @@ - - - - - account.updateProfile - - - - - - - - - - - - - -
- -
-
-
- -

account.updateProfile

- -

Updates user profile.

-

- -
-
userEmpty#d3bc4b7a id:long = User;
-user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
----functions---
-account.updateProfile#78515775 flags:# first_name:flags.0?string last_name:flags.1?string about:flags.2?string = User;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
first_nameflags.0?stringNew user first name
last_nameflags.1?stringNew user last name
aboutflags.2?stringNew bio
-

Result

-

Returns User object containing the updated current user profile.

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400ABOUT_TOO_LONGAbout string too long.
400FIRSTNAME_INVALIDThe first name is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.updateTheme b/data/corefork.telegram.org/method/account.updateTheme deleted file mode 100644 index 27af44124b..0000000000 --- a/data/corefork.telegram.org/method/account.updateTheme +++ /dev/null @@ -1,196 +0,0 @@ - - - - - account.updateTheme - - - - - - - - - - - - - -
- -
-
-
- -

account.updateTheme

- -

Update theme

-

- -
-
theme#e802b8dc flags:# creator:flags.0?true default:flags.1?true for_chat:flags.5?true id:long access_hash:long slug:string title:string document:flags.2?Document settings:flags.3?ThemeSettings installs_count:flags.4?int = Theme;
----functions---
-account.updateTheme#5cb367d5 flags:# format:string theme:InputTheme slug:flags.0?string title:flags.1?string document:flags.2?InputDocument settings:flags.3?InputThemeSettings = Theme;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
formatstringTheme format, a string that identifies the theming engines supported by the client
themeInputThemeTheme to update
slugflags.0?stringUnique theme ID
titleflags.1?stringTheme name
documentflags.2?InputDocumentTheme file
settingsflags.3?InputThemeSettingsTheme settings
-

Result

-

Theme

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400THEME_INVALIDInvalid theme provided.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.updateUsername b/data/corefork.telegram.org/method/account.updateUsername deleted file mode 100644 index 9013c5807a..0000000000 --- a/data/corefork.telegram.org/method/account.updateUsername +++ /dev/null @@ -1,182 +0,0 @@ - - - - - account.updateUsername - - - - - - - - - - - - - -
- -
-
-
- -

account.updateUsername

- -

Changes username for the current user.

-

- -
-
userEmpty#d3bc4b7a id:long = User;
-user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
----functions---
-account.updateUsername#3e0bdd7c username:string = User;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
usernamestringusername or empty string if username is to be removed
Accepted characters: a-z (case-insensitive), 0-9 and underscores.
Length: 5-32 characters.
-

Result

-

Returns updated information on the user in a User type object.

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400USERNAME_INVALIDUnacceptable username.
400USERNAME_NOT_MODIFIEDUsername is not different from the current username.
400USERNAME_OCCUPIEDUsername is taken.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.uploadTheme b/data/corefork.telegram.org/method/account.uploadTheme deleted file mode 100644 index 7de5f38b14..0000000000 --- a/data/corefork.telegram.org/method/account.uploadTheme +++ /dev/null @@ -1,190 +0,0 @@ - - - - - account.uploadTheme - - - - - - - - - - - - - -
- -
-
-
- -

account.uploadTheme

- -

Upload theme

-

- -
-
documentEmpty#36f8c871 id:long = Document;
-document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
----functions---
-account.uploadTheme#1c3db333 flags:# file:InputFile thumb:flags.0?InputFile file_name:string mime_type:string = Document;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
fileInputFileTheme file uploaded as described in files »
thumbflags.0?InputFileThumbnail
file_namestringFile name
mime_typestringMIME type, must be application/x-tgtheme-{format}, where format depends on the client
-

Result

-

Document

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400THEME_FILE_INVALIDInvalid theme file provided.
-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.uploadWallPaper b/data/corefork.telegram.org/method/account.uploadWallPaper deleted file mode 100644 index 9e01adabc8..0000000000 --- a/data/corefork.telegram.org/method/account.uploadWallPaper +++ /dev/null @@ -1,182 +0,0 @@ - - - - - account.uploadWallPaper - - - - - - - - - - - - - -
- -
-
-
- -

account.uploadWallPaper

- -

Create and upload a new wallpaper

-

- -
-
wallPaper#a437c3ed id:long flags:# creator:flags.0?true default:flags.1?true pattern:flags.3?true dark:flags.4?true access_hash:long slug:string document:Document settings:flags.2?WallPaperSettings = WallPaper;
-wallPaperNoFile#e0804116 id:long flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;
----functions---
-account.uploadWallPaper#dd853661 file:InputFile mime_type:string settings:WallPaperSettings = WallPaper;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
fileInputFileThe JPG/PNG wallpaper
mime_typestringMIME type of uploaded wallpaper
settingsWallPaperSettingsWallpaper settings
-

Result

-

WallPaper

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400WALLPAPER_FILE_INVALIDThe specified wallpaper file is invalid.
400WALLPAPER_MIME_INVALIDThe specified wallpaper MIME type is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.verifyEmail b/data/corefork.telegram.org/method/account.verifyEmail deleted file mode 100644 index 6c1a301b8b..0000000000 --- a/data/corefork.telegram.org/method/account.verifyEmail +++ /dev/null @@ -1,179 +0,0 @@ - - - - - account.verifyEmail - - - - - - - - - - - - - -
- -
-
-
- -

account.verifyEmail

- -

Verify an email address for telegram passport.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.verifyEmail#ecba39db email:string code:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
emailstringThe email to verify
codestringThe verification code that was received
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400EMAIL_INVALIDThe specified email is invalid.
400EMAIL_VERIFY_EXPIREDThe verification email has expired.
-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/account.verifyPhone b/data/corefork.telegram.org/method/account.verifyPhone deleted file mode 100644 index 523b1609c0..0000000000 --- a/data/corefork.telegram.org/method/account.verifyPhone +++ /dev/null @@ -1,191 +0,0 @@ - - - - - account.verifyPhone - - - - - - - - - - - - - -
- -
-
-
- -

account.verifyPhone

- -

Verify a phone number for telegram passport.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-account.verifyPhone#4dd3a7f6 phone_number:string phone_code_hash:string phone_code:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number
phone_code_hashstringPhone code hash received from the call to account.sendVerifyPhoneCode
phone_codestringCode received after the call to account.sendVerifyPhoneCode
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PHONE_CODE_EMPTYphone_code is missing.
400PHONE_CODE_EXPIREDThe phone code you provided has expired, this may happen if it was sent to any chat on telegram (if the code is sent through a telegram chat (not the official account) to avoid it append or prepend to the code some chars).
400PHONE_NUMBER_INVALIDThe phone number is invalid.
-

Related pages

-

account.sendVerifyPhoneCode

-

Send the verification phone code for telegram passport.

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/auth.acceptLoginToken b/data/corefork.telegram.org/method/auth.acceptLoginToken deleted file mode 100644 index 4e79b36bc1..0000000000 --- a/data/corefork.telegram.org/method/auth.acceptLoginToken +++ /dev/null @@ -1,171 +0,0 @@ - - - - - auth.acceptLoginToken - - - - - - - - - - - - - -
- -
-
-
- -

auth.acceptLoginToken

- -

Accept QR code login token, logging in the app that generated it.

-

Returns info about the new session.

-

For more info, see login via QR code.

-

- -
-
authorization#ad01d61d flags:# current:flags.0?true official_app:flags.1?true password_pending:flags.2?true encrypted_requests_disabled:flags.3?true call_requests_disabled:flags.4?true hash:long device_model:string platform:string system_version:string api_id:int app_name:string app_version:string date_created:int date_active:int ip:string country:string region:string = Authorization;
----functions---
-auth.acceptLoginToken#e894ad4d token:bytes = Authorization;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
tokenbytesLogin token embedded in QR code, for more info, see login via QR code.
-

Result

-

Authorization

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400AUTH_TOKEN_INVALIDXThe specified auth token is invalid.
-

Related pages

-

Login via QR code

-

QR code login flow

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/auth.bindTempAuthKey b/data/corefork.telegram.org/method/auth.bindTempAuthKey deleted file mode 100644 index a789a81182..0000000000 --- a/data/corefork.telegram.org/method/auth.bindTempAuthKey +++ /dev/null @@ -1,252 +0,0 @@ - - - - - auth.bindTempAuthKey - - - - - - - - - - - - - -
- -
-
-
- -

auth.bindTempAuthKey

- -

Binds a temporary authorization key temp_auth_key_id to the permanent authorization key perm_auth_key_id. Each permanent key may only be bound to one temporary key at a time, binding a new temporary key overwrites the previous one.

-

For more information, see Perfect Forward Secrecy.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-auth.bindTempAuthKey#cdd42a05 perm_auth_key_id:long nonce:long expires_at:int encrypted_message:bytes = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
perm_auth_key_idlongPermanent auth_key_id to bind to
noncelongRandom long from Binding message contents
expires_atintUnix timestamp to invalidate temporary key, see Binding message contents
encrypted_messagebytesSee Generating encrypted_message
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400ENCRYPTED_MESSAGE_INVALIDEncrypted message is incorrect.
400TEMP_AUTH_KEY_ALREADY_BOUNDThe passed temporary key is already bound to another perm_auth_key_id.
400TEMP_AUTH_KEY_EMPTYThe request was not performed with a temporary authorization key.
-

Generating encrypted_message

-

The client begins by creating a special binding message:

-

Binding message contents

-
bind_auth_key_inner#75a3f765 nonce:long temp_auth_key_id:long perm_auth_key_id:long temp_session_id:long expires_at:int = BindAuthKeyInner;
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
noncelongRandom long
temp_auth_key_idlongTemporary auth_key_id
perm_auth_key_idlongPermanent auth_key_id to bind to
temp_session_idlongSession id, which will be used to invoke auth.bindTempAuthKey method
expires_atintUnix timestamp to invalidate temporary key
-

Encrypting the binding message

-

This binding message is encrypted in the usual way, but with MTProto v1 using the perm_auth_key. In other words, one has to prepend random:int128 (it replaces the customary session_id:long and salt:long that are irrelevant in this case), then append the same msg_id that will be used for the request, a seqno equal to zero, and the correct msg_len (40 bytes in this case); after that, one computes the msg_key:int128 as SHA1 of the resulting string, appends padding necessary for a 16-byte alignment, encrypts the resulting string using the key derived from perm_auth_key and msg_key, and prepends perm_auth_key_id and msg_key to the encrypted data as usual.

-

Binding

-

Once encrypted_message is ready, an auth.bindTempAuthKey request is sent to the server using temp_auth_key and temp_session_id. Don't forget to rewrite client info using initConnection when the binding is completed.

-

Bots can use this method

-

Related pages

-

Perfect Forward Secrecy

-

Binding temporary authorization key to permanent ones.

-

long

-

A basic bare type, elements of which correspond to two-element sequences, representing 64-bit signed numbers (little-endian).

-

More on basic types »

-

int

-

A basic bare type, the values of which correspond to single-element sequences, i.e. numbers from -2^31 to 2^31-1 which in this case represent themselves.

-

More on basic types »

-

Mobile Protocol: Detailed Description

-

Calling API Methods

-

Additional options for calling methods.

-

initConnection

-

Initialize connection

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/auth.cancelCode b/data/corefork.telegram.org/method/auth.cancelCode deleted file mode 100644 index af9053c9d7..0000000000 --- a/data/corefork.telegram.org/method/auth.cancelCode +++ /dev/null @@ -1,180 +0,0 @@ - - - - - auth.cancelCode - - - - - - - - - - - - - -
- -
-
-
- -

auth.cancelCode

- -

Cancel the login verification code

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-auth.cancelCode#1f040578 phone_number:string phone_code_hash:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number
phone_code_hashstringPhone code hash from auth.sendCode
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PHONE_CODE_EXPIREDThe phone code you provided has expired, this may happen if it was sent to any chat on telegram (if the code is sent through a telegram chat (not the official account) to avoid it append or prepend to the code some chars).
400PHONE_NUMBER_INVALIDThe phone number is invalid.
-

Related pages

-

auth.sendCode

-

Send the verification code for login

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/auth.checkPassword b/data/corefork.telegram.org/method/auth.checkPassword deleted file mode 100644 index 930a4f083a..0000000000 --- a/data/corefork.telegram.org/method/auth.checkPassword +++ /dev/null @@ -1,180 +0,0 @@ - - - - - auth.checkPassword - - - - - - - - - - - - - -
- -
-
-
- -

auth.checkPassword

- -

Try logging to an account protected by a 2FA password.

-

- -
-
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
-auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
----functions---
-auth.checkPassword#d18b4d16 password:InputCheckPasswordSRP = auth.Authorization;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
passwordInputCheckPasswordSRPThe account's password (see SRP)
-

Result

-

auth.Authorization

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PASSWORD_HASH_INVALIDThe provided password isn't valid.
400SRP_ID_INVALIDInvalid SRP ID provided.
400SRP_PASSWORD_CHANGEDPassword has changed.
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/auth.checkRecoveryPassword b/data/corefork.telegram.org/method/auth.checkRecoveryPassword deleted file mode 100644 index c47c7a3a0a..0000000000 --- a/data/corefork.telegram.org/method/auth.checkRecoveryPassword +++ /dev/null @@ -1,174 +0,0 @@ - - - - - auth.checkRecoveryPassword - - - - - - - - - - - - - -
- -
-
-
- -

auth.checkRecoveryPassword

- -

Check if the 2FA recovery code sent using auth.requestPasswordRecovery is valid, before passing it to auth.recoverPassword.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-auth.checkRecoveryPassword#d36bf79 code:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
codestringCode received via email
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PASSWORD_RECOVERY_EXPIREDThe recovery code has expired.
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

-

auth.requestPasswordRecovery

-

Request recovery code of a 2FA password, only for accounts with a recovery email configured.

-

auth.recoverPassword

-

Reset the 2FA password using the recovery code sent using auth.requestPasswordRecovery.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/auth.dropTempAuthKeys b/data/corefork.telegram.org/method/auth.dropTempAuthKeys deleted file mode 100644 index c9823e69fc..0000000000 --- a/data/corefork.telegram.org/method/auth.dropTempAuthKeys +++ /dev/null @@ -1,151 +0,0 @@ - - - - - auth.dropTempAuthKeys - - - - - - - - - - - - - -
- -
-
-
- -

auth.dropTempAuthKeys

- -

Delete all temporary authorization keys except for the ones specified

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-auth.dropTempAuthKeys#8e48a188 except_auth_keys:Vector<long> = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
except_auth_keysVector<long>The auth keys that shouldn't be dropped.
-

Result

-

Bool

-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/auth.exportAuthorization b/data/corefork.telegram.org/method/auth.exportAuthorization deleted file mode 100644 index 19cb7c8ea9..0000000000 --- a/data/corefork.telegram.org/method/auth.exportAuthorization +++ /dev/null @@ -1,167 +0,0 @@ - - - - - auth.exportAuthorization - - - - - - - - - - - - - -
- -
-
-
- -

auth.exportAuthorization

- -

Returns data for copying authorization to another data-centre.

-

- -
-
auth.exportedAuthorization#b434e2b8 id:long bytes:bytes = auth.ExportedAuthorization;
----functions---
-auth.exportAuthorization#e5bfffcd dc_id:int = auth.ExportedAuthorization;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
dc_idintNumber of a target data-centre
-

Result

-

auth.ExportedAuthorization

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400DC_ID_INVALIDThe provided DC ID is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/auth.exportLoginToken b/data/corefork.telegram.org/method/auth.exportLoginToken deleted file mode 100644 index 8a2d4932e9..0000000000 --- a/data/corefork.telegram.org/method/auth.exportLoginToken +++ /dev/null @@ -1,183 +0,0 @@ - - - - - auth.exportLoginToken - - - - - - - - - - - - - -
- -
-
-
- -

auth.exportLoginToken

- -

Generate a login token, for login via QR code.
-The generated login token should be encoded using base64url, then shown as a tg://login?token=base64encodedtoken URL in the QR code.

-

For more info, see login via QR code.

-

- -
-
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
-auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;
-auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;
----functions---
-auth.exportLoginToken#b7e085fe api_id:int api_hash:string except_ids:Vector<long> = auth.LoginToken;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
api_idintApplication identifier (see. App configuration)
api_hashstringApplication identifier hash (see. App configuration)
except_idsVector<long>List of already logged-in user IDs, to prevent logging in twice with the same user
-

Result

-

auth.LoginToken

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400API_ID_INVALIDAPI ID invalid.
-

Related pages

-

Login via QR code

-

QR code login flow

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/auth.importAuthorization b/data/corefork.telegram.org/method/auth.importAuthorization deleted file mode 100644 index 176ce4aa92..0000000000 --- a/data/corefork.telegram.org/method/auth.importAuthorization +++ /dev/null @@ -1,178 +0,0 @@ - - - - - auth.importAuthorization - - - - - - - - - - - - - -
- -
-
-
- -

auth.importAuthorization

- -

Logs in a user using a key transmitted from his native data-centre.

-

- -
-
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
-auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
----functions---
-auth.importAuthorization#a57a7dad id:long bytes:bytes = auth.Authorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idlongUser ID
bytesbytesAuthorization key
-

Result

-

auth.Authorization

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400AUTH_BYTES_INVALIDThe provided authorization is invalid.
400USER_ID_INVALIDThe provided user ID is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/auth.importBotAuthorization b/data/corefork.telegram.org/method/auth.importBotAuthorization deleted file mode 100644 index 48e130192e..0000000000 --- a/data/corefork.telegram.org/method/auth.importBotAuthorization +++ /dev/null @@ -1,205 +0,0 @@ - - - - - auth.importBotAuthorization - - - - - - - - - - - - - -
- -
-
-
- -

auth.importBotAuthorization

- -

Login as a bot

-

- -
-
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
-auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
----functions---
-auth.importBotAuthorization#67a3ff2c flags:int api_id:int api_hash:string bot_auth_token:string = auth.Authorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flagsintReserved for future use
api_idintApplication identifier (see. App configuration)
api_hashstringApplication identifier hash (see. App configuration)
bot_auth_tokenstringBot token (see bots)
-

Result

-

Returns an auth.Authorization object with information on the new authorization.

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400ACCESS_TOKEN_EXPIREDBot token expired.
400ACCESS_TOKEN_INVALIDThe provided token is not valid.
400API_ID_INVALIDThe api_id/api_hash combination is invalid.
400API_ID_PUBLISHED_FLOODThis API id was published somewhere, you can't use it now.
401AUTH_KEY_INVALIDAuth key invalid.
-

Bots can use this method

-

Related pages

-

Bots: An introduction for developers

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/auth.importLoginToken b/data/corefork.telegram.org/method/auth.importLoginToken deleted file mode 100644 index b1b82453c1..0000000000 --- a/data/corefork.telegram.org/method/auth.importLoginToken +++ /dev/null @@ -1,187 +0,0 @@ - - - - - auth.importLoginToken - - - - - - - - - - - - - -
- -
-
-
- -

auth.importLoginToken

- -

Login using a redirected login token, generated in case of DC mismatch during QR code login.

-

For more info, see login via QR code.

-

- -
-
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
-auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;
-auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;
----functions---
-auth.importLoginToken#95ac5ce4 token:bytes = auth.LoginToken;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
tokenbytesLogin token
-

Result

-

auth.LoginToken

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400AUTH_TOKEN_ALREADY_ACCEPTEDThe specified auth token was already accepted.
400AUTH_TOKEN_EXPIREDThe authorization token has expired.
400AUTH_TOKEN_INVALIDThe specified auth token is invalid.
400AUTH_TOKEN_INVALIDXThe specified auth token is invalid.
-

Related pages

-

Login via QR code

-

QR code login flow

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/auth.logOut b/data/corefork.telegram.org/method/auth.logOut deleted file mode 100644 index 25d8faa316..0000000000 --- a/data/corefork.telegram.org/method/auth.logOut +++ /dev/null @@ -1,140 +0,0 @@ - - - - - auth.logOut - - - - - - - - - - - - - -
- -
-
-
- -

auth.logOut

- -

Logs out the user.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-auth.logOut#5717da40 = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Bool

-

Query example

-
(auth.logOut )
-=
-(boolTrue)
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/auth.recoverPassword b/data/corefork.telegram.org/method/auth.recoverPassword deleted file mode 100644 index 67a4398875..0000000000 --- a/data/corefork.telegram.org/method/auth.recoverPassword +++ /dev/null @@ -1,187 +0,0 @@ - - - - - auth.recoverPassword - - - - - - - - - - - - - -
- -
-
-
- -

auth.recoverPassword

- -

Reset the 2FA password using the recovery code sent using auth.requestPasswordRecovery.

-

- -
-
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
-auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
----functions---
-auth.recoverPassword#37096c70 flags:# code:string new_settings:flags.0?account.PasswordInputSettings = auth.Authorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
codestringCode received via email
new_settingsflags.0?account.PasswordInputSettingsNew password
-

Result

-

auth.Authorization

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CODE_EMPTYThe provided code is empty.
400NEW_SETTINGS_INVALIDThe new settings are invalid.
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

-

auth.requestPasswordRecovery

-

Request recovery code of a 2FA password, only for accounts with a recovery email configured.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/auth.requestPasswordRecovery b/data/corefork.telegram.org/method/auth.requestPasswordRecovery deleted file mode 100644 index 1ba3f369ea..0000000000 --- a/data/corefork.telegram.org/method/auth.requestPasswordRecovery +++ /dev/null @@ -1,159 +0,0 @@ - - - - - auth.requestPasswordRecovery - - - - - - - - - - - - - -
- -
-
-
- -

auth.requestPasswordRecovery

- -

Request recovery code of a 2FA password, only for accounts with a recovery email configured.

-

- -
-
auth.passwordRecovery#137948a5 email_pattern:string = auth.PasswordRecovery;
----functions---
-auth.requestPasswordRecovery#d897bc66 = auth.PasswordRecovery;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

auth.PasswordRecovery

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PASSWORD_EMPTYThe provided password is empty.
400PASSWORD_RECOVERY_NANo email was set, can't recover password via email.
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/auth.resendCode b/data/corefork.telegram.org/method/auth.resendCode deleted file mode 100644 index 7cba74b9fa..0000000000 --- a/data/corefork.telegram.org/method/auth.resendCode +++ /dev/null @@ -1,191 +0,0 @@ - - - - - auth.resendCode - - - - - - - - - - - - - -
- -
-
-
- -

auth.resendCode

- -

Resend the login code via another medium, the phone code type is determined by the return value of the previous auth.sendCode/auth.resendCode: see login for more info.

-

- -
-
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
----functions---
-auth.resendCode#3ef1a9bf phone_number:string phone_code_hash:string = auth.SentCode;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringThe phone number
phone_code_hashstringThe phone code hash obtained from auth.sendCode
-

Result

-

auth.SentCode

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PHONE_CODE_EXPIREDThe phone code you provided has expired, this may happen if it was sent to any chat on telegram (if the code is sent through a telegram chat (not the official account) to avoid it append or prepend to the code some chars).
400PHONE_CODE_HASH_EMPTYphone_code_hash is missing.
400PHONE_NUMBER_INVALIDThe phone number is invalid.
406SEND_CODE_UNAVAILABLEReturned when all available options for this type of number were already used (e.g. flash-call, then SMS, then this error might be returned to trigger a second resend).
-

Related pages

-

auth.sendCode

-

Send the verification code for login

-

User Authorization

-

How to register a user's phone to start using the API.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/auth.resetAuthorizations b/data/corefork.telegram.org/method/auth.resetAuthorizations deleted file mode 100644 index 8928be563e..0000000000 --- a/data/corefork.telegram.org/method/auth.resetAuthorizations +++ /dev/null @@ -1,156 +0,0 @@ - - - - - auth.resetAuthorizations - - - - - - - - - - - - - -
- -
-
-
- -

auth.resetAuthorizations

- -

Terminates all user's authorized sessions except for the current one.

-

After calling this method it is necessary to reregister the current device using the method account.registerDevice

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-auth.resetAuthorizations#9fab0d1a = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
406FRESH_RESET_AUTHORISATION_FORBIDDENYou can't logout other sessions if less than 24 hours have passed since you logged on the current session.
-

Related pages

-

account.registerDevice

-

Register device to receive PUSH notifications

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/auth.sendCall b/data/corefork.telegram.org/method/auth.sendCall deleted file mode 100644 index ffc1255c55..0000000000 --- a/data/corefork.telegram.org/method/auth.sendCall +++ /dev/null @@ -1,175 +0,0 @@ - - - - - auth.sendCall - - - - - - - - - - - - - -
- -
-
-
- -

auth.sendCall

- -

Makes a voice call to the passed phone number. A robot will repeat the confirmation code from a previously sent SMS message.

-

{schema}

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number in the international format
phone_code_hashstringSMS-message ID
-

Result

-

Bool

-

Query example

-
(auth.sendCall "79991234567" "2dc02d2cda9e615c84")
-=
-(boolTrue)
-
-03c51564 3939370b 33323139 37363534 63643212 32643230 39616463 35313665 00343863 64e1a61b
-=
-997275b5
-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PHONE_NUMBER_INVALIDInvalid phone number
400PHONE_CODE_HASH_EMPTYphone_code_hash was not sent
400PHONE_CODE_EXPIREDSMS expired
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/auth.sendInvites b/data/corefork.telegram.org/method/auth.sendInvites deleted file mode 100644 index 10a3136919..0000000000 --- a/data/corefork.telegram.org/method/auth.sendInvites +++ /dev/null @@ -1,157 +0,0 @@ - - - - - auth.sendInvites - - - - - - - - - - - - - -
- -
-
-
- -

auth.sendInvites

- -

Saves information that the current user sent SMS-messages with invitations to its unregistered contacts.

-

{schema}

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numbersVector<string>List of phone numbers of message recipients in the international format
messagestringMessage text
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_EMPTYThe provided message is empty
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/auth.sendSms b/data/corefork.telegram.org/method/auth.sendSms deleted file mode 100644 index 1d5b0a244c..0000000000 --- a/data/corefork.telegram.org/method/auth.sendSms +++ /dev/null @@ -1,167 +0,0 @@ - - - - - auth.sendSms - - - - - - - - - - - - - -
- -
-
-
- -

auth.sendSms

- -

Forces sending an SMS message to the specified phone number. Use this method if auth.sentAppCode was returned as a response to auth.sendCode, but the user can't reach the device with Telegram.

-

{schema}

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number in international format
phone_code_hashstringSMS-message ID
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PHONE_NUMBER_INVALIDInvalid phone number
400PHONE_CODE_HASH_EMPTYphone_code_hash was not sent
400PHONE_CODE_EXPIREDSMS expired
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/auth.signIn b/data/corefork.telegram.org/method/auth.signIn deleted file mode 100644 index c234fdb24d..0000000000 --- a/data/corefork.telegram.org/method/auth.signIn +++ /dev/null @@ -1,219 +0,0 @@ - - - - - auth.signIn - - - - - - - - - - - - - -
- -
-
-
- -

auth.signIn

- -

Signs in a user with a validated phone number.

-

- -
-
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
-auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
----functions---
-auth.signIn#bcd51581 phone_number:string phone_code_hash:string phone_code:string = auth.Authorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number in the international format
phone_code_hashstringSMS-message ID, obtained from auth.sendCode
phone_codestringValid numerical code from the SMS-message
-

Result

-

Returns an auth.Authorization object with information on the new authorization.

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PHONE_CODE_EMPTYphone_code from the SMS is empty.
400PHONE_CODE_EXPIREDSMS expired.
400PHONE_CODE_INVALIDInvalid SMS code was sent.
400PHONE_NUMBER_INVALIDInvalid phone number.
400PHONE_NUMBER_UNOCCUPIEDThe code is valid but no user with the given number is registered.
-

Query example

-
(auth.signIn "79991234567" "2dc02d2cda9e615c84" "44444")
-=
-(auth.authorization
-  expires:1403938438
-  user:(userSelf
-    id:603177
-    first_name:"John"
-    last_name:"Doe"
-    phone:"79991234567"
-    photo:(userProfilePhotoEmpty)
-    status:(userStatusEmpty)
-    inactive:(boolTrue)
-  )
-)
-
-bcd51581 3939370b 33323139 37363534 63643212 32643230 39616463 35313665 00343863 34343405 00003434 45ca2b3b
-=
-f6b673a4 53ae6686 720535ec 00093429 686f4a04 0000006e 656f4403 3939370b 33323139 37363534 4f11bae1 09d05049 997275b5 d8487410
-

Related pages

-

auth.sendCode

-

Send the verification code for login

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/auth.signUp b/data/corefork.telegram.org/method/auth.signUp deleted file mode 100644 index c567279d0e..0000000000 --- a/data/corefork.telegram.org/method/auth.signUp +++ /dev/null @@ -1,236 +0,0 @@ - - - - - auth.signUp - - - - - - - - - - - - - -
- -
-
-
- -

auth.signUp

- -

Registers a validated phone number in the system.

-

- -
-
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
-auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
----functions---
-auth.signUp#80eee427 phone_number:string phone_code_hash:string first_name:string last_name:string = auth.Authorization;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
phone_numberstringPhone number in the international format
phone_code_hashstringSMS-message ID
first_namestringNew user first name
last_namestringNew user last name
-

Result

-

Returns an auth.Authorization object with information about the new authorization.

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400FIRSTNAME_INVALIDInvalid first name.
400LASTNAME_INVALIDInvalid last name.
400PHONE_CODE_EMPTYphone_code from a SMS is empty.
400PHONE_CODE_EXPIREDSMS expired.
400PHONE_CODE_INVALIDInvalid SMS code was sent.
400PHONE_NUMBER_FLOODYou asked for the code too many times.
400PHONE_NUMBER_INVALIDInvalid phone number.
400PHONE_NUMBER_OCCUPIEDThe phone number is already in use.
-

Query example

-
(auth.signUp "79991234567" "2dc02d2cda9e615c84" "44444" "John" "Doe")
-=
-(auth.authorization
-  expires:1403938438
-  user:(userSelf
-    id:603177
-    first_name:"John"
-    last_name:"Doe"
-    phone:"79991234567"
-    photo:(userProfilePhotoEmpty)
-    status:(userStatusEmpty)
-    inactive:(boolTrue)
-  )
-)
-
-1b067634 3939370b 33323139 37363534 63643212 32643230 39616463 35313665 00343863 34343405 00003434 686f4a04 0000006e 656f4403 c18027ca
-=
-f6b673a4 53ae6686 720535ec 00093429 686f4a04 0000006e 656f4403 3939370b 33323139 37363534 4f11bae1 09d05049 997275b5 d8487410
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/bots.answerWebhookJSONQuery b/data/corefork.telegram.org/method/bots.answerWebhookJSONQuery deleted file mode 100644 index 3bd2015143..0000000000 --- a/data/corefork.telegram.org/method/bots.answerWebhookJSONQuery +++ /dev/null @@ -1,178 +0,0 @@ - - - - - bots.answerWebhookJSONQuery - - - - - - - - - - - - - -
- -
-
-
- -

bots.answerWebhookJSONQuery

- -

Answers a custom query; for bots only

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-bots.answerWebhookJSONQuery#e6213f4d query_id:long data:DataJSON = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
query_idlongIdentifier of a custom query
dataDataJSONJSON-serialized answer to the query
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400QUERY_ID_INVALIDThe query ID is invalid.
400USER_BOT_INVALIDThis method can only be called by a bot.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/bots.getBotCommands b/data/corefork.telegram.org/method/bots.getBotCommands deleted file mode 100644 index 06c4c9a99a..0000000000 --- a/data/corefork.telegram.org/method/bots.getBotCommands +++ /dev/null @@ -1,154 +0,0 @@ - - - - - bots.getBotCommands - - - - - - - - - - - - - -
- -
-
-
- -

bots.getBotCommands

- -

Obtain a list of bot commands for the specified bot scope and language code

-

- -
-
---functions---
-bots.getBotCommands#e34c0dd6 scope:BotCommandScope lang_code:string = Vector<BotCommand>;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
scopeBotCommandScopeCommand scope
lang_codestringLanguage code
-

Result

-

Vector<BotCommand>

-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/bots.resetBotCommands b/data/corefork.telegram.org/method/bots.resetBotCommands deleted file mode 100644 index 3de04b1565..0000000000 --- a/data/corefork.telegram.org/method/bots.resetBotCommands +++ /dev/null @@ -1,156 +0,0 @@ - - - - - bots.resetBotCommands - - - - - - - - - - - - - -
- -
-
-
- -

bots.resetBotCommands

- -

Clear bot commands for the specified bot scope and language code

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-bots.resetBotCommands#3d8de0f9 scope:BotCommandScope lang_code:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
scopeBotCommandScopeCommand scope
lang_codestringLanguage code
-

Result

-

Bool

-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/bots.sendCustomRequest b/data/corefork.telegram.org/method/bots.sendCustomRequest deleted file mode 100644 index cc53669b6e..0000000000 --- a/data/corefork.telegram.org/method/bots.sendCustomRequest +++ /dev/null @@ -1,177 +0,0 @@ - - - - - bots.sendCustomRequest - - - - - - - - - - - - - -
- -
-
-
- -

bots.sendCustomRequest

- -

Sends a custom request; for bots only

-

- -
-
dataJSON#7d748d04 data:string = DataJSON;
----functions---
-bots.sendCustomRequest#aa2769ed custom_method:string params:DataJSON = DataJSON;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
custom_methodstringThe method name
paramsDataJSONJSON-serialized method parameters
-

Result

-

DataJSON

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400METHOD_INVALIDThe specified method is invalid.
400USER_BOT_INVALIDThis method can only be called by a bot.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/bots.setBotCommands b/data/corefork.telegram.org/method/bots.setBotCommands deleted file mode 100644 index 39c184fa21..0000000000 --- a/data/corefork.telegram.org/method/bots.setBotCommands +++ /dev/null @@ -1,188 +0,0 @@ - - - - - bots.setBotCommands - - - - - - - - - - - - - -
- -
-
-
- -

bots.setBotCommands

- -

Set bot command list

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-bots.setBotCommands#517165a scope:BotCommandScope lang_code:string commands:Vector<BotCommand> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
scopeBotCommandScopeCommand scope
lang_codestringLanguage code
commandsVector<BotCommand>Bot commands
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOT_COMMAND_DESCRIPTION_INVALIDThe specified command description is invalid.
400BOT_COMMAND_INVALIDThe specified command is invalid.
400LANG_CODE_INVALIDThe specified language code is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.checkUsername b/data/corefork.telegram.org/method/channels.checkUsername deleted file mode 100644 index fb42c0bf50..0000000000 --- a/data/corefork.telegram.org/method/channels.checkUsername +++ /dev/null @@ -1,190 +0,0 @@ - - - - - channels.checkUsername - - - - - - - - - - - - - -
- -
-
-
- -

channels.checkUsername

- -

Check if a username is free and can be assigned to a channel/supergroup

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-channels.checkUsername#10e6bd2c channel:InputChannel username:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelThe channel/supergroup that will assigned the specified username
usernamestringThe username to check
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNELS_ADMIN_PUBLIC_TOO_MUCHYou're admin of too many public channels, make some channels private to change the username of this channel.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400USERNAME_INVALIDThe provided username is not valid.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.convertToGigagroup b/data/corefork.telegram.org/method/channels.convertToGigagroup deleted file mode 100644 index fc70a6340a..0000000000 --- a/data/corefork.telegram.org/method/channels.convertToGigagroup +++ /dev/null @@ -1,177 +0,0 @@ - - - - - channels.convertToGigagroup - - - - - - - - - - - - - -
- -
-
-
- -

channels.convertToGigagroup

- -

Convert a supergroup to a gigagroup, when requested by channel suggestions.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.convertToGigagroup#b290c69 channel:InputChannel = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelThe supergroup to convert
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PARTICIPANTS_TOO_FEWNot enough participants.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

Client configuration

-

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.createChannel b/data/corefork.telegram.org/method/channels.createChannel deleted file mode 100644 index e41f146338..0000000000 --- a/data/corefork.telegram.org/method/channels.createChannel +++ /dev/null @@ -1,232 +0,0 @@ - - - - - channels.createChannel - - - - - - - - - - - - - -
- -
-
-
- -

channels.createChannel

- -

Create a supergroup/channel.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.createChannel#3d5fb10f flags:# broadcast:flags.0?true megagroup:flags.1?true for_import:flags.3?true title:string about:string geo_point:flags.2?InputGeoPoint address:flags.2?string = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
broadcastflags.0?trueWhether to create a channel
megagroupflags.1?trueWhether to create a supergroup
for_importflags.3?trueWhether the supergroup is being created to import messages from a foreign chat service using messages.initHistoryImport
titlestringChannel title
aboutstringChannel description
geo_pointflags.2?InputGeoPointGeogroup location
addressflags.2?stringGeogroup address
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNELS_ADMIN_LOCATED_TOO_MUCHThe user has reached the limit of public geogroups.
400CHANNELS_TOO_MUCHYou have joined too many channels/supergroups.
400CHAT_ABOUT_TOO_LONGChat about too long.
400CHAT_TITLE_EMPTYNo chat title provided.
403USER_RESTRICTEDYou're spamreported, you can't create channels or chats.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

messages.initHistoryImport

-

Import chat history from a foreign chat app into a specific Telegram chat, click here for more info about imported chats ».

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.deleteChannel b/data/corefork.telegram.org/method/channels.deleteChannel deleted file mode 100644 index 1dc39c76aa..0000000000 --- a/data/corefork.telegram.org/method/channels.deleteChannel +++ /dev/null @@ -1,200 +0,0 @@ - - - - - channels.deleteChannel - - - - - - - - - - - - - -
- -
-
-
- -

channels.deleteChannel

- -

Delete a channel/supergroup

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.deleteChannel#c0111fe3 channel:InputChannel = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel/supergroup to delete
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHANNEL_TOO_LARGEChannel is too large to be deleted; this error is issued when trying to delete channels with more than 1000 members (subject to change).
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.deleteHistory b/data/corefork.telegram.org/method/channels.deleteHistory deleted file mode 100644 index fa320faece..0000000000 --- a/data/corefork.telegram.org/method/channels.deleteHistory +++ /dev/null @@ -1,180 +0,0 @@ - - - - - channels.deleteHistory - - - - - - - - - - - - - -
- -
-
-
- -

channels.deleteHistory

- -

Delete the history of a supergroup

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-channels.deleteHistory#af369d42 channel:InputChannel max_id:int = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelSupergroup whose history must be deleted
max_idintID of message up to which the history must be deleted
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.deleteMessages b/data/corefork.telegram.org/method/channels.deleteMessages deleted file mode 100644 index 4c649693f1..0000000000 --- a/data/corefork.telegram.org/method/channels.deleteMessages +++ /dev/null @@ -1,190 +0,0 @@ - - - - - channels.deleteMessages - - - - - - - - - - - - - -
- -
-
-
- -

channels.deleteMessages

- -

Delete messages in a channel/supergroup

-

- -
-
messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;
----functions---
-channels.deleteMessages#84c1fd4e channel:InputChannel id:Vector<int> = messages.AffectedMessages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel/supergroup
idVector<int>IDs of messages to delete
-

Result

-

messages.AffectedMessages

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
403MESSAGE_DELETE_FORBIDDENYou can't delete one of the messages you tried to delete, most likely because it is a service message.
400MSG_ID_INVALIDInvalid message ID provided.
-

Bots can use this method

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.deleteUserHistory b/data/corefork.telegram.org/method/channels.deleteUserHistory deleted file mode 100644 index 44a6375f2f..0000000000 --- a/data/corefork.telegram.org/method/channels.deleteUserHistory +++ /dev/null @@ -1,199 +0,0 @@ - - - - - channels.deleteUserHistory - - - - - - - - - - - - - -
- -
-
-
- -

channels.deleteUserHistory

- -

Delete all messages sent by a certain user in a supergroup

-

- -
-
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
----functions---
-channels.deleteUserHistory#d10dd71b channel:InputChannel user_id:InputUser = messages.AffectedHistory;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelSupergroup
user_idInputUserUser whose messages should be deleted
-

Result

-

messages.AffectedHistory

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400MSG_ID_INVALIDInvalid message ID provided.
400USER_ID_INVALIDThe provided user ID is invalid.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.editAdmin b/data/corefork.telegram.org/method/channels.editAdmin deleted file mode 100644 index 11a2bcbe1f..0000000000 --- a/data/corefork.telegram.org/method/channels.editAdmin +++ /dev/null @@ -1,301 +0,0 @@ - - - - - channels.editAdmin - - - - - - - - - - - - - -
- -
-
-
- -

channels.editAdmin

- -

Modify the admin rights of a user in a supergroup/channel.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.editAdmin#d33c8902 channel:InputChannel user_id:InputUser admin_rights:ChatAdminRights rank:string = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelThe supergroup/channel.
user_idInputUserThe ID of the user whose admin rights should be modified
admin_rightsChatAdminRightsThe admin rights
rankstringIndicates the role (rank) of the admin in the group: just an arbitrary string
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400ADMINS_TOO_MUCHThere are too many admins.
400ADMIN_RANK_EMOJI_NOT_ALLOWEDAn admin rank cannot contain emojis.
400ADMIN_RANK_INVALIDThe specified admin rank is invalid.
400BOTS_TOO_MUCHThere are too many bots in this chat/channel.
400BOT_CHANNELS_NABots can't edit admin privileges.
400BOT_GROUPS_BLOCKEDThis bot can't be added to groups.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
403CHAT_ADMIN_INVITE_REQUIREDYou do not have the rights to do this.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
406FRESH_CHANGE_ADMINS_FORBIDDENYou were just elected admin, you can't add or modify other admins yet.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400PEER_ID_INVALIDThe provided peer id is invalid.
403RIGHT_FORBIDDENYour admin rights do not allow you to do this.
400USERS_TOO_MUCHThe maximum number of users has been exceeded (to create a chat, for example).
400USER_BLOCKEDUser blocked.
403USER_CHANNELS_TOO_MUCHOne of the users you tried to add is already in too many channels/supergroups.
400USER_CREATORYou can't leave this channel, because you're its creator.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_NOT_MUTUAL_CONTACTThe provided user is not a mutual contact.
403USER_PRIVACY_RESTRICTEDThe user's privacy settings do not allow you to do this.
403USER_RESTRICTEDYou're spamreported, you can't create channels or chats.
-

Bots can use this method

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.editBanned b/data/corefork.telegram.org/method/channels.editBanned deleted file mode 100644 index 60ddcdcbda..0000000000 --- a/data/corefork.telegram.org/method/channels.editBanned +++ /dev/null @@ -1,241 +0,0 @@ - - - - - channels.editBanned - - - - - - - - - - - - - -
- -
-
-
- -

channels.editBanned

- -

Ban/unban/kick a user in a supergroup/channel.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.editBanned#96e6cd81 channel:InputChannel participant:InputPeer banned_rights:ChatBannedRights = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelThe supergroup/channel.
participantInputPeerParticipant to ban
banned_rightsChatBannedRightsThe banned rights
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_ADD_INVALIDInternal error.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400PARTICIPANT_ID_INVALIDThe specified participant ID is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PINNED_DIALOGS_TOO_MUCHToo many pinned dialogs.
400USER_ADMIN_INVALIDYou're not an admin.
400USER_ID_INVALIDThe provided user ID is invalid.
-

Bots can use this method

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.editCreator b/data/corefork.telegram.org/method/channels.editCreator deleted file mode 100644 index 9d7761ba52..0000000000 --- a/data/corefork.telegram.org/method/channels.editCreator +++ /dev/null @@ -1,225 +0,0 @@ - - - - - channels.editCreator - - - - - - - - - - - - - -
- -
-
-
- -

channels.editCreator

- -

Transfer channel ownership

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.editCreator#8f38cd1f channel:InputChannel user_id:InputUser password:InputCheckPasswordSRP = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel
user_idInputUserNew channel owner
passwordInputCheckPasswordSRP2FA password of account
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400PASSWORD_HASH_INVALIDThe provided password hash is invalid.
400PASSWORD_MISSINGYou must enable 2FA in order to transfer ownership of a channel.
400PASSWORD_TOO_FRESH_XThe password was modified less than 24 hours ago, try again in X seconds.
400SESSION_TOO_FRESH_XThis session was created less than 24 hours ago, try again in X seconds.
400SRP_ID_INVALIDInvalid SRP ID provided.
400USER_ID_INVALIDThe provided user ID is invalid.
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.editLocation b/data/corefork.telegram.org/method/channels.editLocation deleted file mode 100644 index 71a74976a1..0000000000 --- a/data/corefork.telegram.org/method/channels.editLocation +++ /dev/null @@ -1,180 +0,0 @@ - - - - - channels.editLocation - - - - - - - - - - - - - -
- -
-
-
- -

channels.editLocation

- -

Edit location of geogroup

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-channels.editLocation#58e63f6d channel:InputChannel geo_point:InputGeoPoint address:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelGeogroup
geo_pointInputGeoPointNew geolocation
addressstringAddress string
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400MEGAGROUP_REQUIREDYou can only use this method on a supergroup.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.editPhoto b/data/corefork.telegram.org/method/channels.editPhoto deleted file mode 100644 index cc022e8bcf..0000000000 --- a/data/corefork.telegram.org/method/channels.editPhoto +++ /dev/null @@ -1,221 +0,0 @@ - - - - - channels.editPhoto - - - - - - - - - - - - - -
- -
-
-
- -

channels.editPhoto

- -

Change the photo of a channel/supergroup

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.editPhoto#f12e57c9 channel:InputChannel photo:InputChatPhoto = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel/supergroup whose photo should be edited
photoInputChatPhotoNew photo
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400FILE_REFERENCE_INVALIDThe specified file reference is invalid.
400PHOTO_CROP_SIZE_SMALLPhoto is too small.
400PHOTO_EXT_INVALIDThe extension of the photo is invalid.
400PHOTO_INVALIDPhoto invalid.
-

Bots can use this method

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.editTitle b/data/corefork.telegram.org/method/channels.editTitle deleted file mode 100644 index b06962f7d2..0000000000 --- a/data/corefork.telegram.org/method/channels.editTitle +++ /dev/null @@ -1,206 +0,0 @@ - - - - - channels.editTitle - - - - - - - - - - - - - -
- -
-
-
- -

channels.editTitle

- -

Edit the name of a channel/supergroup

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.editTitle#566decd0 channel:InputChannel title:string = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel/supergroup
titlestringNew name
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400CHAT_TITLE_EMPTYNo chat title provided.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
-

Bots can use this method

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.exportMessageLink b/data/corefork.telegram.org/method/channels.exportMessageLink deleted file mode 100644 index b9d9c2ab2f..0000000000 --- a/data/corefork.telegram.org/method/channels.exportMessageLink +++ /dev/null @@ -1,204 +0,0 @@ - - - - - channels.exportMessageLink - - - - - - - - - - - - - -
- -
-
-
- -

channels.exportMessageLink

- -

Get link and embed info of a message in a channel/supergroup

-

- -
-
exportedMessageLink#5dab1af4 link:string html:string = ExportedMessageLink;
----functions---
-channels.exportMessageLink#e63fadeb flags:# grouped:flags.0?true thread:flags.1?true channel:InputChannel id:int = ExportedMessageLink;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
groupedflags.0?trueWhether to include other grouped media (for albums)
threadflags.1?trueWhether to also include a thread ID, if available, inside of the link
channelInputChannelChannel
idintMessage ID
-

Result

-

ExportedMessageLink

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.getAdminLog b/data/corefork.telegram.org/method/channels.getAdminLog deleted file mode 100644 index 4a7aebbde4..0000000000 --- a/data/corefork.telegram.org/method/channels.getAdminLog +++ /dev/null @@ -1,226 +0,0 @@ - - - - - channels.getAdminLog - - - - - - - - - - - - - -
- -
-
-
- -

channels.getAdminLog

- -

Get the admin log of a channel/supergroup

-

- -
-
channels.adminLogResults#ed8af74d events:Vector<ChannelAdminLogEvent> chats:Vector<Chat> users:Vector<User> = channels.AdminLogResults;
----functions---
-channels.getAdminLog#33ddf480 flags:# channel:InputChannel q:string events_filter:flags.0?ChannelAdminLogEventsFilter admins:flags.1?Vector<InputUser> max_id:long min_id:long limit:int = channels.AdminLogResults;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
channelInputChannelChannel
qstringSearch query, can be empty
events_filterflags.0?ChannelAdminLogEventsFilterEvent filter
adminsflags.1?Vector<InputUser>Only show events from these admins
max_idlongMaximum ID of message to return (see pagination)
min_idlongMinimum ID of message to return (see pagination)
limitintMaximum number of results to return, see pagination
-

Result

-

channels.AdminLogResults

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400MSG_ID_INVALIDInvalid message ID provided.
-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.getAdminedPublicChannels b/data/corefork.telegram.org/method/channels.getAdminedPublicChannels deleted file mode 100644 index a6755b7726..0000000000 --- a/data/corefork.telegram.org/method/channels.getAdminedPublicChannels +++ /dev/null @@ -1,191 +0,0 @@ - - - - - channels.getAdminedPublicChannels - - - - - - - - - - - - - -
- -
-
-
- -

channels.getAdminedPublicChannels

- -

Get channels/supergroups/geogroups we're admin in. Usually called when the user exceeds the limit for owned public channels/supergroups/geogroups, and the user is given the choice to remove one of his channels/supergroups/geogroups.

-

- -
-
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
-messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
----functions---
-channels.getAdminedPublicChannels#f8b036af flags:# by_location:flags.0?true check_limit:flags.1?true = messages.Chats;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
by_locationflags.0?trueGet geogroups
check_limitflags.1?trueIf set and the user has reached the limit of owned public channels/supergroups/geogroups, instead of returning the channel list one of the specified errors will be returned.
Useful to check if a new public channel can indeed be created, even before asking the user to enter a channel username to use in channels.checkUsername/channels.updateUsername.
-

Result

-

messages.Chats

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNELS_ADMIN_LOCATED_TOO_MUCHReturned if both the check_limit and the by_location flags are set and the user has reached the limit of public geogroups.
400CHANNELS_ADMIN_PUBLIC_TOO_MUCHReturned if the check_limit flag is set and the user has reached the limit of public channels/supergroups.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

channels.checkUsername

-

Check if a username is free and can be assigned to a channel/supergroup

-

channels.updateUsername

-

Change the username of a supergroup/channel

-

config

-

Current configuration

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.getChannels b/data/corefork.telegram.org/method/channels.getChannels deleted file mode 100644 index 457f66f200..0000000000 --- a/data/corefork.telegram.org/method/channels.getChannels +++ /dev/null @@ -1,181 +0,0 @@ - - - - - channels.getChannels - - - - - - - - - - - - - -
- -
-
-
- -

channels.getChannels

- -

Get info about channels/supergroups

-

- -
-
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
-messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
----functions---
-channels.getChannels#a7f6bbb id:Vector<InputChannel> = messages.Chats;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idVector<InputChannel>IDs of channels/supergroups to get info about
-

Result

-

messages.Chats

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
-

Bots can use this method

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.getFullChannel b/data/corefork.telegram.org/method/channels.getFullChannel deleted file mode 100644 index a707edf182..0000000000 --- a/data/corefork.telegram.org/method/channels.getFullChannel +++ /dev/null @@ -1,187 +0,0 @@ - - - - - channels.getFullChannel - - - - - - - - - - - - - -
- -
-
-
- -

channels.getFullChannel

- -

Get full info about a channel

-

- -
-
messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.ChatFull;
----functions---
-channels.getFullChannel#8736a09 channel:InputChannel = messages.ChatFull;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelThe channel to get info about
-

Result

-

messages.ChatFull

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
403CHANNEL_PUBLIC_GROUP_NAchannel/supergroup not available.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400MSG_ID_INVALIDInvalid message ID provided.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.getGroupsForDiscussion b/data/corefork.telegram.org/method/channels.getGroupsForDiscussion deleted file mode 100644 index 67d3a40964..0000000000 --- a/data/corefork.telegram.org/method/channels.getGroupsForDiscussion +++ /dev/null @@ -1,144 +0,0 @@ - - - - - channels.getGroupsForDiscussion - - - - - - - - - - - - - -
- -
-
-
- -

channels.getGroupsForDiscussion

- -

Get all groups that can be used as discussion groups.

-

Returned legacy group chats must be first upgraded to supergroups before they can be set as a discussion group.
-To set a returned supergroup as a discussion group, access to its old messages must be enabled using channels.togglePreHistoryHidden, first.

-

- -
-
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
-messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
----functions---
-channels.getGroupsForDiscussion#f5dad378 = messages.Chats;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

messages.Chats

-

Related pages

-

Discussion groups

-

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

channels.togglePreHistoryHidden

-

Hide/unhide message history for new channel/supergroup users

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.getInactiveChannels b/data/corefork.telegram.org/method/channels.getInactiveChannels deleted file mode 100644 index 8081ac4ec7..0000000000 --- a/data/corefork.telegram.org/method/channels.getInactiveChannels +++ /dev/null @@ -1,134 +0,0 @@ - - - - - channels.getInactiveChannels - - - - - - - - - - - - - -
- -
-
-
- -

channels.getInactiveChannels

- -

Get inactive channels and supergroups

-

- -
-
messages.inactiveChats#a927fec5 dates:Vector<int> chats:Vector<Chat> users:Vector<User> = messages.InactiveChats;
----functions---
-channels.getInactiveChannels#11e831ee = messages.InactiveChats;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

messages.InactiveChats

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.getLeftChannels b/data/corefork.telegram.org/method/channels.getLeftChannels deleted file mode 100644 index 22d7ffcc64..0000000000 --- a/data/corefork.telegram.org/method/channels.getLeftChannels +++ /dev/null @@ -1,172 +0,0 @@ - - - - - channels.getLeftChannels - - - - - - - - - - - - - -
- -
-
-
- -

channels.getLeftChannels

- -

Get a list of channels/supergroups we left

-

- -
-
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
-messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
----functions---
-channels.getLeftChannels#8341ecc0 offset:int = messages.Chats;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset for pagination
-

Result

-

messages.Chats

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
403TAKEOUT_REQUIREDA takeout session has to be initialized, first.
-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.getMessages b/data/corefork.telegram.org/method/channels.getMessages deleted file mode 100644 index f2b72040d4..0000000000 --- a/data/corefork.telegram.org/method/channels.getMessages +++ /dev/null @@ -1,193 +0,0 @@ - - - - - channels.getMessages - - - - - - - - - - - - - -
- -
-
-
- -

channels.getMessages

- -

Get channel/supergroup messages

-

- -
-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
----functions---
-channels.getMessages#ad8c9a23 channel:InputChannel id:Vector<InputMessage> = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel/supergroup
idVector<InputMessage>IDs of messages to get
-

Result

-

messages.Messages

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MESSAGE_IDS_EMPTYNo message ids were provided.
400MSG_ID_INVALIDInvalid message ID provided.
-

Bots can use this method

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.getParticipant b/data/corefork.telegram.org/method/channels.getParticipant deleted file mode 100644 index 663c5275b8..0000000000 --- a/data/corefork.telegram.org/method/channels.getParticipant +++ /dev/null @@ -1,205 +0,0 @@ - - - - - channels.getParticipant - - - - - - - - - - - - - -
- -
-
-
- -

channels.getParticipant

- -

Get info about a channel/supergroup participant

-

- -
-
channels.channelParticipant#dfb80317 participant:ChannelParticipant chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipant;
----functions---
-channels.getParticipant#a0ab6cc6 channel:InputChannel participant:InputPeer = channels.ChannelParticipant;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel/supergroup
participantInputPeerParticipant to get info about
-

Result

-

channels.ChannelParticipant

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400MSG_ID_INVALIDInvalid message ID provided.
400PARTICIPANT_ID_INVALIDThe specified participant ID is invalid.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_NOT_PARTICIPANTYou're not a member of this supergroup/channel.
-

Bots can use this method

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.getParticipants b/data/corefork.telegram.org/method/channels.getParticipants deleted file mode 100644 index fa2b18a0ba..0000000000 --- a/data/corefork.telegram.org/method/channels.getParticipants +++ /dev/null @@ -1,203 +0,0 @@ - - - - - channels.getParticipants - - - - - - - - - - - - - -
- -
-
-
- -

channels.getParticipants

- -

Get the participants of a supergroup/channel

-

- -
-
channels.channelParticipants#9ab0feaf count:int participants:Vector<ChannelParticipant> chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipants;
-channels.channelParticipantsNotModified#f0173fe9 = channels.ChannelParticipants;
----functions---
-channels.getParticipants#77ced9d0 channel:InputChannel filter:ChannelParticipantsFilter offset:int limit:int hash:long = channels.ChannelParticipants;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel
filterChannelParticipantsFilterWhich participant types to fetch
offsetintOffset
limitintLimit
hashlongHash
-

Result

-

channels.ChannelParticipants

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
-

Bots can use this method

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.getSponsoredMessages b/data/corefork.telegram.org/method/channels.getSponsoredMessages deleted file mode 100644 index ffa01a9eaa..0000000000 --- a/data/corefork.telegram.org/method/channels.getSponsoredMessages +++ /dev/null @@ -1,154 +0,0 @@ - - - - - channels.getSponsoredMessages - - - - - - - - - - - - - -
- -
-
-
- -

channels.getSponsoredMessages

- -

Get a list of sponsored messages

-

- -
-
messages.sponsoredMessages#65a4c7d5 messages:Vector<SponsoredMessage> chats:Vector<Chat> users:Vector<User> = messages.SponsoredMessages;
----functions---
-channels.getSponsoredMessages#ec210fbf channel:InputChannel = messages.SponsoredMessages;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelPeer
-

Result

-

messages.SponsoredMessages

-
-

Related pages

-

Sponsored messages

-

How to implement sponsored messages

-
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.inviteToChannel b/data/corefork.telegram.org/method/channels.inviteToChannel deleted file mode 100644 index 06ae4321ef..0000000000 --- a/data/corefork.telegram.org/method/channels.inviteToChannel +++ /dev/null @@ -1,262 +0,0 @@ - - - - - channels.inviteToChannel - - - - - - - - - - - - - -
- -
-
-
- -

channels.inviteToChannel

- -

Invite users to a channel/supergroup

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.inviteToChannel#199f3a6c channel:InputChannel users:Vector<InputUser> = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel/supergroup
usersVector<InputUser>Users to invite
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOTS_TOO_MUCHThere are too many bots in this chat/channel.
400BOT_GROUPS_BLOCKEDThis bot can't be added to groups.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_INVALIDInvalid chat.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400USERS_TOO_MUCHThe maximum number of users has been exceeded (to create a chat, for example).
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400USER_BLOCKEDUser blocked.
400USER_BOTBots can only be admins in channels.
403USER_CHANNELS_TOO_MUCHOne of the users you tried to add is already in too many channels/supergroups.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_KICKEDThis user was kicked from this supergroup/channel.
400USER_NOT_MUTUAL_CONTACTThe provided user is not a mutual contact.
403USER_PRIVACY_RESTRICTEDThe user's privacy settings do not allow you to do this.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.joinChannel b/data/corefork.telegram.org/method/channels.joinChannel deleted file mode 100644 index 4566580034..0000000000 --- a/data/corefork.telegram.org/method/channels.joinChannel +++ /dev/null @@ -1,227 +0,0 @@ - - - - - channels.joinChannel - - - - - - - - - - - - - -
- -
-
-
- -

channels.joinChannel

- -

Join a channel/supergroup

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.joinChannel#24b524c5 channel:InputChannel = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel/supergroup to join
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNELS_TOO_MUCHYou have joined too many channels/supergroups.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_INVALIDInvalid chat.
400INVITE_HASH_EMPTYThe invite hash is empty.
400INVITE_HASH_EXPIREDThe invite link has expired.
400INVITE_HASH_INVALIDThe invite hash is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USERS_TOO_MUCHThe maximum number of users has been exceeded (to create a chat, for example).
400USER_ALREADY_PARTICIPANTThe user is already in the group.
400USER_CHANNELS_TOO_MUCHOne of the users you tried to add is already in too many channels/supergroups.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.leaveChannel b/data/corefork.telegram.org/method/channels.leaveChannel deleted file mode 100644 index c2626690ee..0000000000 --- a/data/corefork.telegram.org/method/channels.leaveChannel +++ /dev/null @@ -1,201 +0,0 @@ - - - - - channels.leaveChannel - - - - - - - - - - - - - -
- -
-
-
- -

channels.leaveChannel

- -

Leave a channel/supergroup

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.leaveChannel#f836aa95 channel:InputChannel = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel/supergroup to leave
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
403CHANNEL_PUBLIC_GROUP_NAchannel/supergroup not available.
400MSG_ID_INVALIDInvalid message ID provided.
400USER_CREATORYou can't leave this channel, because you're its creator.
400USER_NOT_PARTICIPANTYou're not a member of this supergroup/channel.
-

Bots can use this method

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.readHistory b/data/corefork.telegram.org/method/channels.readHistory deleted file mode 100644 index 9554e8a3aa..0000000000 --- a/data/corefork.telegram.org/method/channels.readHistory +++ /dev/null @@ -1,185 +0,0 @@ - - - - - channels.readHistory - - - - - - - - - - - - - -
- -
-
-
- -

channels.readHistory

- -

Mark channel/supergroup history as read

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-channels.readHistory#cc104937 channel:InputChannel max_id:int = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel/supergroup
max_idintID of message up to which messages should be marked as read
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.readMessageContents b/data/corefork.telegram.org/method/channels.readMessageContents deleted file mode 100644 index d257d4b237..0000000000 --- a/data/corefork.telegram.org/method/channels.readMessageContents +++ /dev/null @@ -1,185 +0,0 @@ - - - - - channels.readMessageContents - - - - - - - - - - - - - -
- -
-
-
- -

channels.readMessageContents

- -

Mark channel/supergroup message contents as read

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-channels.readMessageContents#eab5dc38 channel:InputChannel id:Vector<int> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel/supergroup
idVector<int>IDs of messages whose contents should be marked as read
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.reportSpam b/data/corefork.telegram.org/method/channels.reportSpam deleted file mode 100644 index 2c406aaa3a..0000000000 --- a/data/corefork.telegram.org/method/channels.reportSpam +++ /dev/null @@ -1,192 +0,0 @@ - - - - - channels.reportSpam - - - - - - - - - - - - - -
- -
-
-
- -

channels.reportSpam

- -

Reports some messages from a user in a supergroup as spam; requires administrator rights in the supergroup

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-channels.reportSpam#fe087810 channel:InputChannel user_id:InputUser id:Vector<int> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelSupergroup
user_idInputUserID of the user that sent the spam messages
idVector<int>IDs of spam messages
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400USER_ID_INVALIDThe provided user ID is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.setDiscussionGroup b/data/corefork.telegram.org/method/channels.setDiscussionGroup deleted file mode 100644 index 04d1c6ca7d..0000000000 --- a/data/corefork.telegram.org/method/channels.setDiscussionGroup +++ /dev/null @@ -1,200 +0,0 @@ - - - - - channels.setDiscussionGroup - - - - - - - - - - - - - -
- -
-
-
- -

channels.setDiscussionGroup

- -

Associate a group to a channel as discussion group for that channel

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-channels.setDiscussionGroup#40582bb2 broadcast:InputChannel group:InputChannel = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
broadcastInputChannelChannel
groupInputChannelDiscussion group to associate to the channel
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BROADCAST_ID_INVALIDBroadcast ID invalid.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400LINK_NOT_MODIFIEDDiscussion link not modified.
400MEGAGROUP_ID_INVALIDInvalid supergroup ID.
400MEGAGROUP_PREHISTORY_HIDDENGroup with hidden history for new members can't be set as discussion groups.
-

Related pages

-

Discussion groups

-

Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.setStickers b/data/corefork.telegram.org/method/channels.setStickers deleted file mode 100644 index 43f48ae7a4..0000000000 --- a/data/corefork.telegram.org/method/channels.setStickers +++ /dev/null @@ -1,183 +0,0 @@ - - - - - channels.setStickers - - - - - - - - - - - - - -
- -
-
-
- -

channels.setStickers

- -

Associate a stickerset to the supergroup

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-channels.setStickers#ea8ca4f9 channel:InputChannel stickerset:InputStickerSet = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelSupergroup
stickersetInputStickerSetThe stickerset to associate
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400PARTICIPANTS_TOO_FEWNot enough participants.
406STICKERSET_OWNER_ANONYMOUSProvided stickerset can't be installed as group stickerset to prevent admin deanonymisation.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.toggleSignatures b/data/corefork.telegram.org/method/channels.toggleSignatures deleted file mode 100644 index f983d944f1..0000000000 --- a/data/corefork.telegram.org/method/channels.toggleSignatures +++ /dev/null @@ -1,187 +0,0 @@ - - - - - channels.toggleSignatures - - - - - - - - - - - - - -
- -
-
-
- -

channels.toggleSignatures

- -

Enable/disable message signatures in channels

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.toggleSignatures#1f69b606 channel:InputChannel enabled:Bool = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel
enabledBoolValue
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.toggleSlowMode b/data/corefork.telegram.org/method/channels.toggleSlowMode deleted file mode 100644 index d397c4208b..0000000000 --- a/data/corefork.telegram.org/method/channels.toggleSlowMode +++ /dev/null @@ -1,190 +0,0 @@ - - - - - channels.toggleSlowMode - - - - - - - - - - - - - -
- -
-
-
- -

channels.toggleSlowMode

- -

Toggle supergroup slow mode: if enabled, users will only be able to send one message every seconds seconds

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-channels.toggleSlowMode#edd49ef0 channel:InputChannel seconds:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelThe supergroup
secondsintUsers will only be able to send one message every seconds seconds, 0 to disable the limitation
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400SECONDS_INVALIDInvalid duration provided.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/channels.updateUsername b/data/corefork.telegram.org/method/channels.updateUsername deleted file mode 100644 index 8591f4b39f..0000000000 --- a/data/corefork.telegram.org/method/channels.updateUsername +++ /dev/null @@ -1,212 +0,0 @@ - - - - - channels.updateUsername - - - - - - - - - - - - - -
- -
-
-
- -

channels.updateUsername

- -

Change the username of a supergroup/channel

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-channels.updateUsername#3514b3de channel:InputChannel username:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
channelInputChannelChannel
usernamestringNew username
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNELS_ADMIN_PUBLIC_TOO_MUCHYou're admin of too many public channels, make some channels private to change the username of this channel.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400USERNAME_INVALIDThe provided username is not valid.
400USERNAME_NOT_MODIFIEDThe username was not modified.
400USERNAME_OCCUPIEDThe provided username is already occupied.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/contacts.acceptContact b/data/corefork.telegram.org/method/contacts.acceptContact deleted file mode 100644 index 5a367820ed..0000000000 --- a/data/corefork.telegram.org/method/contacts.acceptContact +++ /dev/null @@ -1,190 +0,0 @@ - - - - - contacts.acceptContact - - - - - - - - - - - - - -
- -
-
-
- -

contacts.acceptContact

- -

If the peer settings of a new user allow us to add him as contact, add that user as contact

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-contacts.acceptContact#f831a20f id:InputUser = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idInputUserThe user to add as contact
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CONTACT_ADD_MISSINGContact to add is missing.
400CONTACT_ID_INVALIDThe provided contact ID is invalid.
400CONTACT_REQ_MISSINGMissing contact request.
400MSG_ID_INVALIDInvalid message ID provided.
-

Related pages

-

peerSettings

-

Peer settings

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/contacts.addContact b/data/corefork.telegram.org/method/contacts.addContact deleted file mode 100644 index 5257951565..0000000000 --- a/data/corefork.telegram.org/method/contacts.addContact +++ /dev/null @@ -1,217 +0,0 @@ - - - - - contacts.addContact - - - - - - - - - - - - - -
- -
-
-
- -

contacts.addContact

- -

Add an existing telegram user as contact.

-

Use contacts.importContacts to add contacts by phone number, without knowing their Telegram ID.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-contacts.addContact#e8f463d0 flags:# add_phone_privacy_exception:flags.0?true id:InputUser first_name:string last_name:string phone:string = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
add_phone_privacy_exceptionflags.0?trueAllow the other user to see our phone number?
idInputUserTelegram ID of the other user
first_namestringFirst name
last_namestringLast name
phonestringUser's phone number
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CONTACT_ID_INVALIDThe provided contact ID is invalid.
400CONTACT_NAME_EMPTYContact name empty.
400MSG_ID_INVALIDInvalid message ID provided.
-

Related pages

-

contacts.importContacts

-

Imports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.

-

Use contacts.addContact to add Telegram contacts without actually using their phone number.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/contacts.block b/data/corefork.telegram.org/method/contacts.block deleted file mode 100644 index f7c46ebea8..0000000000 --- a/data/corefork.telegram.org/method/contacts.block +++ /dev/null @@ -1,182 +0,0 @@ - - - - - contacts.block - - - - - - - - - - - - - -
- -
-
-
- -

contacts.block

- -

Adds the user to the blacklist.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-contacts.block#68cc1411 id:InputPeer = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idInputPeerUser ID
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CONTACT_ID_INVALIDThe provided contact ID is invalid.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/contacts.blockFromReplies b/data/corefork.telegram.org/method/contacts.blockFromReplies deleted file mode 100644 index d77150aa47..0000000000 --- a/data/corefork.telegram.org/method/contacts.blockFromReplies +++ /dev/null @@ -1,178 +0,0 @@ - - - - - contacts.blockFromReplies - - - - - - - - - - - - - -
- -
-
-
- -

contacts.blockFromReplies

- -

Stop getting notifications about thread replies of a certain user in @replies

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-contacts.blockFromReplies#29a8962c flags:# delete_message:flags.0?true delete_history:flags.1?true report_spam:flags.2?true msg_id:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
delete_messageflags.0?trueWhether to delete the specified message as well
delete_historyflags.1?trueWhether to delete all @replies messages from this user as well
report_spamflags.2?trueWhether to also report this user for spam
msg_idintID of the message in the @replies chat
-

Result

-

Updates

-

Related pages

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/contacts.deleteByPhones b/data/corefork.telegram.org/method/contacts.deleteByPhones deleted file mode 100644 index 682d4a2139..0000000000 --- a/data/corefork.telegram.org/method/contacts.deleteByPhones +++ /dev/null @@ -1,150 +0,0 @@ - - - - - contacts.deleteByPhones - - - - - - - - - - - - - -
- -
-
-
- -

contacts.deleteByPhones

- -

Delete contacts by phone number

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-contacts.deleteByPhones#1013fd9e phones:Vector<string> = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
phonesVector<string>Phone numbers
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/contacts.deleteContacts b/data/corefork.telegram.org/method/contacts.deleteContacts deleted file mode 100644 index 95a779560a..0000000000 --- a/data/corefork.telegram.org/method/contacts.deleteContacts +++ /dev/null @@ -1,155 +0,0 @@ - - - - - contacts.deleteContacts - - - - - - - - - - - - - -
- -
-
-
- -

contacts.deleteContacts

- -

Deletes several contacts from the list.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-contacts.deleteContacts#96a0e00 id:Vector<InputUser> = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idVector<InputUser>User ID list
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/contacts.getBlocked b/data/corefork.telegram.org/method/contacts.getBlocked deleted file mode 100644 index 963d06f964..0000000000 --- a/data/corefork.telegram.org/method/contacts.getBlocked +++ /dev/null @@ -1,155 +0,0 @@ - - - - - contacts.getBlocked - - - - - - - - - - - - - -
- -
-
-
- -

contacts.getBlocked

- -

Returns the list of blocked users.

-

- -
-
contacts.blocked#ade1591 blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
-contacts.blockedSlice#e1664194 count:int blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
----functions---
-contacts.getBlocked#f57c350f offset:int limit:int = contacts.Blocked;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintThe number of list elements to be skipped
limitintThe number of list elements to be returned
-

Result

-

contacts.Blocked

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/contacts.getContactIDs b/data/corefork.telegram.org/method/contacts.getContactIDs deleted file mode 100644 index 6df017f54d..0000000000 --- a/data/corefork.telegram.org/method/contacts.getContactIDs +++ /dev/null @@ -1,151 +0,0 @@ - - - - - contacts.getContactIDs - - - - - - - - - - - - - -
- -
-
-
- -

contacts.getContactIDs

- -

Get contact by telegram IDs

-

- -
-
---functions---
-contacts.getContactIDs#7adc669d hash:long = Vector<int>;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
-

Result

-

Vector<int>

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/contacts.getContacts b/data/corefork.telegram.org/method/contacts.getContacts deleted file mode 100644 index b9b60ddbac..0000000000 --- a/data/corefork.telegram.org/method/contacts.getContacts +++ /dev/null @@ -1,155 +0,0 @@ - - - - - contacts.getContacts - - - - - - - - - - - - - -
- -
-
-
- -

contacts.getContacts

- -

Returns the current user's contact list.

-

- -
-
contacts.contactsNotModified#b74ba9d2 = contacts.Contacts;
-contacts.contacts#eae87e42 contacts:Vector<Contact> saved_count:int users:Vector<User> = contacts.Contacts;
----functions---
-contacts.getContacts#5dd69e12 hash:long = contacts.Contacts;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashlongIf there already is a full contact list on the client, a hash of a the list of contact IDs in ascending order may be passed in this parameter. If the contact set was not changed, (contacts.contactsNotModified) will be returned.
-

Result

-

contacts.Contacts

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

-

contacts.contactsNotModified

-

Contact list on the server is the same as the list on the client.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/contacts.getLocated b/data/corefork.telegram.org/method/contacts.getLocated deleted file mode 100644 index 5eb2049697..0000000000 --- a/data/corefork.telegram.org/method/contacts.getLocated +++ /dev/null @@ -1,197 +0,0 @@ - - - - - contacts.getLocated - - - - - - - - - - - - - -
- -
-
-
- -

contacts.getLocated

- -

Get contacts near you

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-contacts.getLocated#d348bc44 flags:# background:flags.1?true geo_point:InputGeoPoint self_expires:flags.0?int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
backgroundflags.1?trueWhile the geolocation of the current user is public, clients should update it in the background every half-an-hour or so, while setting this flag.
Do this only if the new location is more than 1 KM away from the previous one, or if the previous location is unknown.
geo_pointInputGeoPointGeolocation
self_expiresflags.0?intIf set, the geolocation of the current user will be public for the specified number of seconds; pass 0x7fffffff to disable expiry, 0 to make the current geolocation private; if the flag isn't set, no changes will be applied.
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400GEO_POINT_INVALIDInvalid geoposition provided.
406USERPIC_PRIVACY_REQUIREDYou need to disable privacy settings for your profile picture in order to make your geolocation public.
406USERPIC_UPLOAD_REQUIREDYou must have a profile picture to publish your geolocation.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/contacts.getSaved b/data/corefork.telegram.org/method/contacts.getSaved deleted file mode 100644 index 93039e8a55..0000000000 --- a/data/corefork.telegram.org/method/contacts.getSaved +++ /dev/null @@ -1,150 +0,0 @@ - - - - - contacts.getSaved - - - - - - - - - - - - - -
- -
-
-
- -

contacts.getSaved

- -

Get all contacts

-

- -
-
---functions---
-contacts.getSaved#82f1e39f = Vector<SavedContact>;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Vector<SavedContact>

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
403TAKEOUT_REQUIREDA takeout session has to be initialized, first.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/contacts.getStatuses b/data/corefork.telegram.org/method/contacts.getStatuses deleted file mode 100644 index b1eed5005d..0000000000 --- a/data/corefork.telegram.org/method/contacts.getStatuses +++ /dev/null @@ -1,133 +0,0 @@ - - - - - contacts.getStatuses - - - - - - - - - - - - - -
- -
-
-
- -

contacts.getStatuses

- -

Returns the list of contact statuses.

-

- -
-
---functions---
-contacts.getStatuses#c4a353ee = Vector<ContactStatus>;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Vector<ContactStatus>

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/contacts.getTopPeers b/data/corefork.telegram.org/method/contacts.getTopPeers deleted file mode 100644 index 2221fbccec..0000000000 --- a/data/corefork.telegram.org/method/contacts.getTopPeers +++ /dev/null @@ -1,226 +0,0 @@ - - - - - contacts.getTopPeers - - - - - - - - - - - - - -
- -
-
-
- -

contacts.getTopPeers

- -

Get most used peers

-

- -
-
contacts.topPeersNotModified#de266ef5 = contacts.TopPeers;
-contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;
-contacts.topPeersDisabled#b52c939d = contacts.TopPeers;
----functions---
-contacts.getTopPeers#973478b6 flags:# correspondents:flags.0?true bots_pm:flags.1?true bots_inline:flags.2?true phone_calls:flags.3?true forward_users:flags.4?true forward_chats:flags.5?true groups:flags.10?true channels:flags.15?true offset:int limit:int hash:long = contacts.TopPeers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
correspondentsflags.0?trueUsers we've chatted most frequently with
bots_pmflags.1?trueMost used bots
bots_inlineflags.2?trueMost used inline bots
phone_callsflags.3?trueMost frequently called users
forward_usersflags.4?trueUsers to which the users often forwards messages to
forward_chatsflags.5?trueChats to which the users often forwards messages to
groupsflags.10?trueOften-opened groups and supergroups
channelsflags.15?trueMost frequently visited channels
offsetintOffset for pagination
limitintMaximum number of results to return, see pagination
hashlongHash for pagination, for more info click here
-

Result

-

contacts.TopPeers

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400TYPES_EMPTYNo top peer type was provided.
-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/contacts.importContacts b/data/corefork.telegram.org/method/contacts.importContacts deleted file mode 100644 index 6907adf945..0000000000 --- a/data/corefork.telegram.org/method/contacts.importContacts +++ /dev/null @@ -1,154 +0,0 @@ - - - - - contacts.importContacts - - - - - - - - - - - - - -
- -
-
-
- -

contacts.importContacts

- -

Imports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.

-

Use contacts.addContact to add Telegram contacts without actually using their phone number.

-

- -
-
contacts.importedContacts#77d01c3b imported:Vector<ImportedContact> popular_invites:Vector<PopularContact> retry_contacts:Vector<long> users:Vector<User> = contacts.ImportedContacts;
----functions---
-contacts.importContacts#2c800be5 contacts:Vector<InputContact> = contacts.ImportedContacts;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
contactsVector<InputContact>List of contacts to import
-

Result

-

contacts.ImportedContacts

-

Related pages

-

contacts.addContact

-

Add an existing telegram user as contact.

-

Use contacts.importContacts to add contacts by phone number, without knowing their Telegram ID.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/contacts.resetSaved b/data/corefork.telegram.org/method/contacts.resetSaved deleted file mode 100644 index b006ae0f8f..0000000000 --- a/data/corefork.telegram.org/method/contacts.resetSaved +++ /dev/null @@ -1,135 +0,0 @@ - - - - - contacts.resetSaved - - - - - - - - - - - - - -
- -
-
-
- -

contacts.resetSaved

- -

Delete saved contacts

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-contacts.resetSaved#879537f1 = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/contacts.resetTopPeerRating b/data/corefork.telegram.org/method/contacts.resetTopPeerRating deleted file mode 100644 index 2b87a73c6f..0000000000 --- a/data/corefork.telegram.org/method/contacts.resetTopPeerRating +++ /dev/null @@ -1,175 +0,0 @@ - - - - - contacts.resetTopPeerRating - - - - - - - - - - - - - -
- -
-
-
- -

contacts.resetTopPeerRating

- -

Reset rating of top peer

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-contacts.resetTopPeerRating#1ae373ac category:TopPeerCategory peer:InputPeer = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
categoryTopPeerCategoryTop peer category
peerInputPeerPeer whose rating should be reset
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

Top peer rating

-

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/contacts.search b/data/corefork.telegram.org/method/contacts.search deleted file mode 100644 index 373bb2952a..0000000000 --- a/data/corefork.telegram.org/method/contacts.search +++ /dev/null @@ -1,178 +0,0 @@ - - - - - contacts.search - - - - - - - - - - - - - -
- -
-
-
- -

contacts.search

- -

Returns users found by username substring.

-

- -
-
contacts.found#b3134d9d my_results:Vector<Peer> results:Vector<Peer> chats:Vector<Chat> users:Vector<User> = contacts.Found;
----functions---
-contacts.search#11f812d8 q:string limit:int = contacts.Found;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
qstringTarget substring
limitintMaximum number of users to be returned
-

Result

-

contacts.Found

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400QUERY_TOO_SHORTThe query string is too short.
400SEARCH_QUERY_EMPTYThe search query is empty.
-

Notes

-

This method will exclude the current user's contacts from the search results. It is assumed that searches among the user's contacts can be handled locally by the client.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/contacts.toggleTopPeers b/data/corefork.telegram.org/method/contacts.toggleTopPeers deleted file mode 100644 index ddc92a0947..0000000000 --- a/data/corefork.telegram.org/method/contacts.toggleTopPeers +++ /dev/null @@ -1,153 +0,0 @@ - - - - - contacts.toggleTopPeers - - - - - - - - - - - - - -
- -
-
-
- -

contacts.toggleTopPeers

- -

Enable/disable top peers

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-contacts.toggleTopPeers#8514bdda enabled:Bool = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
enabledBoolEnable/disable
-

Result

-

Bool

-

Related pages

-

Top peer rating

-

If enabled, the rating of top peers indicates the relevance of a frequently used peer in a certain category (frequently messaged users, frequently used bots, inline bots, frequently visited channels and so on).

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/contacts.unblock b/data/corefork.telegram.org/method/contacts.unblock deleted file mode 100644 index 64ac7eaba6..0000000000 --- a/data/corefork.telegram.org/method/contacts.unblock +++ /dev/null @@ -1,182 +0,0 @@ - - - - - contacts.unblock - - - - - - - - - - - - - -
- -
-
-
- -

contacts.unblock

- -

Deletes the user from the blacklist.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-contacts.unblock#bea65d50 id:InputPeer = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idInputPeerUser ID
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CONTACT_ID_INVALIDThe provided contact ID is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/folders.deleteFolder b/data/corefork.telegram.org/method/folders.deleteFolder deleted file mode 100644 index d9e13c95b7..0000000000 --- a/data/corefork.telegram.org/method/folders.deleteFolder +++ /dev/null @@ -1,175 +0,0 @@ - - - - - folders.deleteFolder - - - - - - - - - - - - - -
- -
-
-
- -

folders.deleteFolder

- -

Delete a peer folder

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-folders.deleteFolder#1c295881 folder_id:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
folder_idintPeer folder ID, for more info click here
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400FOLDER_ID_EMPTYAn empty folder ID was specified.
-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/folders.editPeerFolders b/data/corefork.telegram.org/method/folders.editPeerFolders deleted file mode 100644 index f5937fd1c0..0000000000 --- a/data/corefork.telegram.org/method/folders.editPeerFolders +++ /dev/null @@ -1,175 +0,0 @@ - - - - - folders.editPeerFolders - - - - - - - - - - - - - -
- -
-
-
- -

folders.editPeerFolders

- -

Edit peers in peer folder

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-folders.editPeerFolders#6847d0ab folder_peers:Vector<InputFolderPeer> = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
folder_peersVector<InputFolderPeer>New peer list
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400FOLDER_ID_INVALIDInvalid folder ID.
-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/help.acceptTermsOfService b/data/corefork.telegram.org/method/help.acceptTermsOfService deleted file mode 100644 index 9b0ab51586..0000000000 --- a/data/corefork.telegram.org/method/help.acceptTermsOfService +++ /dev/null @@ -1,150 +0,0 @@ - - - - - help.acceptTermsOfService - - - - - - - - - - - - - -
- -
-
-
- -

help.acceptTermsOfService

- -

Accept the new terms of service

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-help.acceptTermsOfService#ee72f79a id:DataJSON = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idDataJSONID of terms of service
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/help.dismissSuggestion b/data/corefork.telegram.org/method/help.dismissSuggestion deleted file mode 100644 index c296e6b4df..0000000000 --- a/data/corefork.telegram.org/method/help.dismissSuggestion +++ /dev/null @@ -1,160 +0,0 @@ - - - - - help.dismissSuggestion - - - - - - - - - - - - - -
- -
-
-
- -

help.dismissSuggestion

- -

Dismiss a suggestion, see here for more info ».

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-help.dismissSuggestion#f50dbaa1 peer:InputPeer suggestion:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerIn the case of pending suggestions in channels, the channel ID.
suggestionstringSuggestion, see here for more info ».
-

Result

-

Bool

-

Related pages

-

channelFull

-

Full info about a channel/supergroup

-

Client configuration

-

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/help.editUserInfo b/data/corefork.telegram.org/method/help.editUserInfo deleted file mode 100644 index 8ef8ba531e..0000000000 --- a/data/corefork.telegram.org/method/help.editUserInfo +++ /dev/null @@ -1,180 +0,0 @@ - - - - - help.editUserInfo - - - - - - - - - - - - - -
- -
-
-
- -

help.editUserInfo

- -

Internal use

-

- -
-
help.userInfoEmpty#f3ae2eed = help.UserInfo;
-help.userInfo#1eb3758 message:string entities:Vector<MessageEntity> author:string date:int = help.UserInfo;
----functions---
-help.editUserInfo#66b91b70 user_id:InputUser message:string entities:Vector<MessageEntity> = help.UserInfo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idInputUserUser
messagestringMessage
entitiesVector<MessageEntity>Message entities for styled text
-

Result

-

help.UserInfo

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400USER_INVALIDInvalid user provided.
-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/help.getAppChangelog b/data/corefork.telegram.org/method/help.getAppChangelog deleted file mode 100644 index 9cd2a3167e..0000000000 --- a/data/corefork.telegram.org/method/help.getAppChangelog +++ /dev/null @@ -1,162 +0,0 @@ - - - - - help.getAppChangelog - - - - - - - - - - - - - -
- -
-
-
- -

help.getAppChangelog

- -

Get changelog of current app.
-Typically, an updates constructor will be returned, containing one or more updateServiceNotification updates with app-specific changelogs.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-help.getAppChangelog#9010ef6f prev_app_version:string = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
prev_app_versionstringPrevious app version
-

Result

-

Updates

-

Related pages

-

Updates

-

Full constructor of updates

-

updateServiceNotification

-

A service message for the user.

-

The app must show the message to the user upon receiving this update. In case the popup parameter was passed, the text message must be displayed in a popup alert immediately upon receipt. It is recommended to handle the text as you would an ordinary message in terms of highlighting links, etc. The message must also be stored locally as part of the message history with the user id 777000 (Telegram Notifications).

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/help.getAppConfig b/data/corefork.telegram.org/method/help.getAppConfig deleted file mode 100644 index 46b7268f49..0000000000 --- a/data/corefork.telegram.org/method/help.getAppConfig +++ /dev/null @@ -1,142 +0,0 @@ - - - - - help.getAppConfig - - - - - - - - - - - - - -
- -
-
-
- -

help.getAppConfig

- -

Get app-specific configuration, see client configuration for more info on the result.

-

- -
-
jsonNull#3f6d7b68 = JSONValue;
-jsonBool#c7345e6a value:Bool = JSONValue;
-jsonNumber#2be0dfa4 value:double = JSONValue;
-jsonString#b71e767a value:string = JSONValue;
-jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;
-jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;
----functions---
-help.getAppConfig#98914110 = JSONValue;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

JSONValue, see client configuration for more info on the result

-

Related pages

-

Client configuration

-

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/help.getAppUpdate b/data/corefork.telegram.org/method/help.getAppUpdate deleted file mode 100644 index bc6bab8e7a..0000000000 --- a/data/corefork.telegram.org/method/help.getAppUpdate +++ /dev/null @@ -1,150 +0,0 @@ - - - - - help.getAppUpdate - - - - - - - - - - - - - -
- -
-
-
- -

help.getAppUpdate

- -

Returns information on update availability for the current application.

-

- -
-
help.appUpdate#ccbbce30 flags:# can_not_skip:flags.0?true id:int version:string text:string entities:Vector<MessageEntity> document:flags.1?Document url:flags.2?string sticker:flags.3?Document = help.AppUpdate;
-help.noAppUpdate#c45a6536 = help.AppUpdate;
----functions---
-help.getAppUpdate#522d5a7d source:string = help.AppUpdate;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
sourcestringSource
-

Result

-

help.AppUpdate

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/help.getCdnConfig b/data/corefork.telegram.org/method/help.getCdnConfig deleted file mode 100644 index f6639f7f18..0000000000 --- a/data/corefork.telegram.org/method/help.getCdnConfig +++ /dev/null @@ -1,154 +0,0 @@ - - - - - help.getCdnConfig - - - - - - - - - - - - - -
- -
-
-
- -

help.getCdnConfig

- -

Get configuration for CDN file downloads.

-

- -
-
cdnConfig#5725e40a public_keys:Vector<CdnPublicKey> = CdnConfig;
----functions---
-help.getCdnConfig#52029342 = CdnConfig;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

CdnConfig

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
-

Bots can use this method

-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/help.getConfig b/data/corefork.telegram.org/method/help.getConfig deleted file mode 100644 index 7c87b42057..0000000000 --- a/data/corefork.telegram.org/method/help.getConfig +++ /dev/null @@ -1,192 +0,0 @@ - - - - - help.getConfig - - - - - - - - - - - - - -
- -
-
-
- -

help.getConfig

- -

Returns current configuration, including data center configuration.

-

- -
-
config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;
----functions---
-help.getConfig#c4f9186b = Config;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Config

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CONNECTION_API_ID_INVALIDThe provided API id is invalid.
400CONNECTION_APP_VERSION_EMPTYApp version is empty.
400CONNECTION_LAYER_INVALIDLayer invalid.
400CONNECTION_NOT_INITEDConnection not initialized.
400DATA_INVALIDEncrypted data invalid.
400INPUT_LAYER_INVALIDThe provided layer is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400USERNAME_INVALIDThe provided username is not valid.
403USER_PRIVACY_RESTRICTEDThe user's privacy settings do not allow you to do this.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/help.getCountriesList b/data/corefork.telegram.org/method/help.getCountriesList deleted file mode 100644 index ec87ab6a22..0000000000 --- a/data/corefork.telegram.org/method/help.getCountriesList +++ /dev/null @@ -1,158 +0,0 @@ - - - - - help.getCountriesList - - - - - - - - - - - - - -
- -
-
-
- -

help.getCountriesList

- -

Get name, ISO code, localized name and phone codes/patterns of all available countries

-

- -
-
help.countriesListNotModified#93cc1f32 = help.CountriesList;
-help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;
----functions---
-help.getCountriesList#735787a8 lang_code:string hash:int = help.CountriesList;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
lang_codestringLanguage code of the current user
hashintHash for pagination, for more info click here
-

Result

-

help.CountriesList

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/help.getDeepLinkInfo b/data/corefork.telegram.org/method/help.getDeepLinkInfo deleted file mode 100644 index 476faf413d..0000000000 --- a/data/corefork.telegram.org/method/help.getDeepLinkInfo +++ /dev/null @@ -1,150 +0,0 @@ - - - - - help.getDeepLinkInfo - - - - - - - - - - - - - -
- -
-
-
- -

help.getDeepLinkInfo

- -

Get info about a t.me link

-

- -
-
help.deepLinkInfoEmpty#66afa166 = help.DeepLinkInfo;
-help.deepLinkInfo#6a4ee832 flags:# update_app:flags.0?true message:string entities:flags.1?Vector<MessageEntity> = help.DeepLinkInfo;
----functions---
-help.getDeepLinkInfo#3fedc75f path:string = help.DeepLinkInfo;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
pathstringPath in t.me/path
-

Result

-

help.DeepLinkInfo

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/help.getInviteText b/data/corefork.telegram.org/method/help.getInviteText deleted file mode 100644 index 9ecd60da01..0000000000 --- a/data/corefork.telegram.org/method/help.getInviteText +++ /dev/null @@ -1,134 +0,0 @@ - - - - - help.getInviteText - - - - - - - - - - - - - -
- -
-
-
- -

help.getInviteText

- -

Returns localized text of a text message with an invitation.

-

- -
-
help.inviteText#18cb9f78 message:string = help.InviteText;
----functions---
-help.getInviteText#4d392343 = help.InviteText;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

help.InviteText

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/help.getNearestDc b/data/corefork.telegram.org/method/help.getNearestDc deleted file mode 100644 index ae2f6bbeb8..0000000000 --- a/data/corefork.telegram.org/method/help.getNearestDc +++ /dev/null @@ -1,134 +0,0 @@ - - - - - help.getNearestDc - - - - - - - - - - - - - -
- -
-
-
- -

help.getNearestDc

- -

Returns info on data centre nearest to the user.

-

- -
-
nearestDc#8e1a1775 country:string this_dc:int nearest_dc:int = NearestDc;
----functions---
-help.getNearestDc#1fb33026 = NearestDc;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

NearestDc

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/help.getPassportConfig b/data/corefork.telegram.org/method/help.getPassportConfig deleted file mode 100644 index eeaac41eca..0000000000 --- a/data/corefork.telegram.org/method/help.getPassportConfig +++ /dev/null @@ -1,154 +0,0 @@ - - - - - help.getPassportConfig - - - - - - - - - - - - - -
- -
-
-
- -

help.getPassportConfig

- -

Get passport configuration

-

- -
-
help.passportConfigNotModified#bfb9f457 = help.PassportConfig;
-help.passportConfig#a098d6af hash:int countries_langs:DataJSON = help.PassportConfig;
----functions---
-help.getPassportConfig#c661ad08 hash:int = help.PassportConfig;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashintHash for pagination, for more info click here
-

Result

-

help.PassportConfig

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/help.getPromoData b/data/corefork.telegram.org/method/help.getPromoData deleted file mode 100644 index 3778e05b26..0000000000 --- a/data/corefork.telegram.org/method/help.getPromoData +++ /dev/null @@ -1,135 +0,0 @@ - - - - - help.getPromoData - - - - - - - - - - - - - -
- -
-
-
- -

help.getPromoData

- -

Get MTProxy/Public Service Announcement information

-

- -
-
help.promoDataEmpty#98f6ac75 expires:int = help.PromoData;
-help.promoData#8c39793f flags:# proxy:flags.0?true expires:int peer:Peer chats:Vector<Chat> users:Vector<User> psa_type:flags.1?string psa_message:flags.2?string = help.PromoData;
----functions---
-help.getPromoData#c0977421 = help.PromoData;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

help.PromoData

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/help.getProxyData b/data/corefork.telegram.org/method/help.getProxyData deleted file mode 100644 index e0d15403e4..0000000000 --- a/data/corefork.telegram.org/method/help.getProxyData +++ /dev/null @@ -1,132 +0,0 @@ - - - - - help.getProxyData - - - - - - - - - - - - - -
- -
-
-
- -

help.getProxyData

- -

Get promotion info of the currently-used MTProxy

-

- -
-
 Method schema is available as of layer 113. Switch »

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

help.ProxyData

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/help.getRecentMeUrls b/data/corefork.telegram.org/method/help.getRecentMeUrls deleted file mode 100644 index 9695382b88..0000000000 --- a/data/corefork.telegram.org/method/help.getRecentMeUrls +++ /dev/null @@ -1,149 +0,0 @@ - - - - - help.getRecentMeUrls - - - - - - - - - - - - - -
- -
-
-
- -

help.getRecentMeUrls

- -

Get recently used t.me links

-

- -
-
help.recentMeUrls#e0310d7 urls:Vector<RecentMeUrl> chats:Vector<Chat> users:Vector<User> = help.RecentMeUrls;
----functions---
-help.getRecentMeUrls#3dc0f114 referer:string = help.RecentMeUrls;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
refererstringReferer
-

Result

-

help.RecentMeUrls

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/help.getSupport b/data/corefork.telegram.org/method/help.getSupport deleted file mode 100644 index 2ac1c12f5f..0000000000 --- a/data/corefork.telegram.org/method/help.getSupport +++ /dev/null @@ -1,134 +0,0 @@ - - - - - help.getSupport - - - - - - - - - - - - - -
- -
-
-
- -

help.getSupport

- -

Returns the support user for the 'ask a question' feature.

-

- -
-
help.support#17c6b5f6 phone_number:string user:User = help.Support;
----functions---
-help.getSupport#9cdf08cd = help.Support;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

help.Support

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/help.getSupportName b/data/corefork.telegram.org/method/help.getSupportName deleted file mode 100644 index d7140fa7a1..0000000000 --- a/data/corefork.telegram.org/method/help.getSupportName +++ /dev/null @@ -1,151 +0,0 @@ - - - - - help.getSupportName - - - - - - - - - - - - - -
- -
-
-
- -

help.getSupportName

- -

Get localized name of the telegram support user

-

- -
-
help.supportName#8c05f1c9 name:string = help.SupportName;
----functions---
-help.getSupportName#d360e72c = help.SupportName;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

help.SupportName

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
403USER_INVALIDInvalid user provided.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/help.getTermsOfServiceUpdate b/data/corefork.telegram.org/method/help.getTermsOfServiceUpdate deleted file mode 100644 index cac127278c..0000000000 --- a/data/corefork.telegram.org/method/help.getTermsOfServiceUpdate +++ /dev/null @@ -1,135 +0,0 @@ - - - - - help.getTermsOfServiceUpdate - - - - - - - - - - - - - -
- -
-
-
- -

help.getTermsOfServiceUpdate

- -

Look for updates of telegram's terms of service

-

- -
-
help.termsOfServiceUpdateEmpty#e3309f7f expires:int = help.TermsOfServiceUpdate;
-help.termsOfServiceUpdate#28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate;
----functions---
-help.getTermsOfServiceUpdate#2ca51fd1 = help.TermsOfServiceUpdate;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

help.TermsOfServiceUpdate

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/help.getUserInfo b/data/corefork.telegram.org/method/help.getUserInfo deleted file mode 100644 index e9362f066e..0000000000 --- a/data/corefork.telegram.org/method/help.getUserInfo +++ /dev/null @@ -1,167 +0,0 @@ - - - - - help.getUserInfo - - - - - - - - - - - - - -
- -
-
-
- -

help.getUserInfo

- -

Internal use

-

- -
-
help.userInfoEmpty#f3ae2eed = help.UserInfo;
-help.userInfo#1eb3758 message:string entities:Vector<MessageEntity> author:string date:int = help.UserInfo;
----functions---
-help.getUserInfo#38a08d3 user_id:InputUser = help.UserInfo;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
user_idInputUserUser ID
-

Result

-

help.UserInfo

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
403USER_INVALIDInvalid user provided.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/help.hidePromoData b/data/corefork.telegram.org/method/help.hidePromoData deleted file mode 100644 index a0004ea8a6..0000000000 --- a/data/corefork.telegram.org/method/help.hidePromoData +++ /dev/null @@ -1,150 +0,0 @@ - - - - - help.hidePromoData - - - - - - - - - - - - - -
- -
-
-
- -

help.hidePromoData

- -

Hide MTProxy/Public Service Announcement information

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-help.hidePromoData#1e251c95 peer:InputPeer = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer to hide
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/help.saveAppLog b/data/corefork.telegram.org/method/help.saveAppLog deleted file mode 100644 index d6ef89fd0c..0000000000 --- a/data/corefork.telegram.org/method/help.saveAppLog +++ /dev/null @@ -1,150 +0,0 @@ - - - - - help.saveAppLog - - - - - - - - - - - - - -
- -
-
-
- -

help.saveAppLog

- -

Saves logs of application on the server.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-help.saveAppLog#6f02f748 events:Vector<InputAppEvent> = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
eventsVector<InputAppEvent>List of input events
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/help.setBotUpdatesStatus b/data/corefork.telegram.org/method/help.setBotUpdatesStatus deleted file mode 100644 index cfab355bfd..0000000000 --- a/data/corefork.telegram.org/method/help.setBotUpdatesStatus +++ /dev/null @@ -1,156 +0,0 @@ - - - - - help.setBotUpdatesStatus - - - - - - - - - - - - - -
- -
-
-
- -

help.setBotUpdatesStatus

- -

Informs the server about the number of pending bot updates if they haven't been processed for a long time; for bots only

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-help.setBotUpdatesStatus#ec22cfcd pending_updates_count:int message:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
pending_updates_countintNumber of pending updates
messagestringError message, if present
-

Result

-

Bool

-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/initConnection.html b/data/corefork.telegram.org/method/initConnection.html deleted file mode 100644 index 4281c86836..0000000000 --- a/data/corefork.telegram.org/method/initConnection.html +++ /dev/null @@ -1,216 +0,0 @@ - - - - - initConnection - - - - - - - - - - - - - -
- -
-
-
- -

initConnection

- -

Initialize connection

-

- -
-
---functions---
-initConnection#c1cd5ea9 {X:Type} flags:# api_id:int device_model:string system_version:string app_version:string system_lang_code:string lang_pack:string lang_code:string proxy:flags.0?InputClientProxy params:flags.1?JSONValue query:!X = X;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
api_idintApplication identifier (see. App configuration)
device_modelstringDevice model
system_versionstringOperation system version
app_versionstringApplication version
system_lang_codestringCode for the language used on the device's OS, ISO 639-1 standard
lang_packstringLanguage pack to use
lang_codestringCode for the language used on the client, ISO 639-1 standard
proxyflags.0?InputClientProxyInfo about an MTProto proxy
paramsflags.1?JSONValueAdditional initConnection parameters.
For now, only the tz_offset field is supported, for specifying timezone offset in seconds.
query!XThe query itself
-

Result

-

X

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400CONNECTION_LAYER_INVALIDLayer invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/invokeAfterMsg.html b/data/corefork.telegram.org/method/invokeAfterMsg.html deleted file mode 100644 index c3f1686c62..0000000000 --- a/data/corefork.telegram.org/method/invokeAfterMsg.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - invokeAfterMsg - - - - - - - - - - - - - -
- -
-
-
- -

invokeAfterMsg

- -

Invokes a query after successfull completion of one of the previous queries.

-

- -
-
---functions---
-invokeAfterMsg#cb9f372d {X:Type} msg_id:long query:!X = X;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
msg_idlongMessage identifier on which a current query depends
query!XThe query itself
-

Result

-

X

-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/invokeAfterMsgs.html b/data/corefork.telegram.org/method/invokeAfterMsgs.html deleted file mode 100644 index ebf51352b2..0000000000 --- a/data/corefork.telegram.org/method/invokeAfterMsgs.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - invokeAfterMsgs - - - - - - - - - - - - - -
- -
-
-
- -

invokeAfterMsgs

- -

Invokes a query after a successfull completion of previous queries

-

- -
-
---functions---
-invokeAfterMsgs#3dc4b4f0 {X:Type} msg_ids:Vector<long> query:!X = X;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
msg_idsVector<long>List of messages on which a current query depends
query!XThe query itself
-

Result

-

X

-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/invokeWithLayer.html b/data/corefork.telegram.org/method/invokeWithLayer.html deleted file mode 100644 index 77ccb817e0..0000000000 --- a/data/corefork.telegram.org/method/invokeWithLayer.html +++ /dev/null @@ -1,204 +0,0 @@ - - - - - invokeWithLayer - - - - - - - - - - - - - -
- -
-
-
- -

invokeWithLayer

- -

Invoke the specified query using the specified API layer

-

- -
-
---functions---
-invokeWithLayer#da9b0d0d {X:Type} layer:int query:!X = X;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
layerintThe layer to use
query!XThe query
-

Result

-

X

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400AUTH_BYTES_INVALIDThe provided authorization is invalid.
400CDN_METHOD_INVALIDYou can't call this method in a CDN DC.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400CONNECTION_API_ID_INVALIDThe provided API id is invalid.
400CONNECTION_NOT_INITEDConnection not initialized.
400INPUT_LAYER_INVALIDThe provided layer is invalid.
400INVITE_HASH_EXPIREDThe invite link has expired.
-

Bots can use this method

-

Related pages

-

Calling API Methods

-

Additional options for calling methods.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/invokeWithMessagesRange.html b/data/corefork.telegram.org/method/invokeWithMessagesRange.html deleted file mode 100644 index 2569e77e92..0000000000 --- a/data/corefork.telegram.org/method/invokeWithMessagesRange.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - invokeWithMessagesRange - - - - - - - - - - - - - -
- -
-
-
- -

invokeWithMessagesRange

- -

Invoke with the given message range

-

- -
-
---functions---
-invokeWithMessagesRange#365275f2 {X:Type} range:MessageRange query:!X = X;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
rangeMessageRangeMessage range
query!XQuery
-

Result

-

X

-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/invokeWithTakeout.html b/data/corefork.telegram.org/method/invokeWithTakeout.html deleted file mode 100644 index b8f607b777..0000000000 --- a/data/corefork.telegram.org/method/invokeWithTakeout.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - invokeWithTakeout - - - - - - - - - - - - - -
- -
-
-
- -

invokeWithTakeout

- -

Invoke a method within a takeout session

-

- -
-
---functions---
-invokeWithTakeout#aca9fd2e {X:Type} takeout_id:long query:!X = X;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
takeout_idlongTakeout session ID
query!XQuery
-

Result

-

X

-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/invokeWithoutUpdates.html b/data/corefork.telegram.org/method/invokeWithoutUpdates.html deleted file mode 100644 index 7ff250afcc..0000000000 --- a/data/corefork.telegram.org/method/invokeWithoutUpdates.html +++ /dev/null @@ -1,154 +0,0 @@ - - - - - invokeWithoutUpdates - - - - - - - - - - - - - -
- -
-
-
- -

invokeWithoutUpdates

- -

Invoke a request without subscribing the used connection for updates (this is enabled by default for file queries).

-

- -
-
---functions---
-invokeWithoutUpdates#bf9459b7 {X:Type} query:!X = X;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
query!XThe query
-

Result

-

X

-

Bots can use this method

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/langpack.getDifference b/data/corefork.telegram.org/method/langpack.getDifference deleted file mode 100644 index 9c1256b662..0000000000 --- a/data/corefork.telegram.org/method/langpack.getDifference +++ /dev/null @@ -1,176 +0,0 @@ - - - - - langpack.getDifference - - - - - - - - - - - - - -
- -
-
-
- -

langpack.getDifference

- -

Get new strings in languagepack

-

- -
-
langPackDifference#f385c1f6 lang_code:string from_version:int version:int strings:Vector<LangPackString> = LangPackDifference;
----functions---
-langpack.getDifference#cd984aa5 lang_pack:string lang_code:string from_version:int = LangPackDifference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
lang_packstringLanguage pack
lang_codestringLanguage code
from_versionintPrevious localization pack version
-

Result

-

LangPackDifference

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400LANG_PACK_INVALIDThe provided language pack is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/langpack.getLanguage b/data/corefork.telegram.org/method/langpack.getLanguage deleted file mode 100644 index 2e135d4952..0000000000 --- a/data/corefork.telegram.org/method/langpack.getLanguage +++ /dev/null @@ -1,154 +0,0 @@ - - - - - langpack.getLanguage - - - - - - - - - - - - - -
- -
-
-
- -

langpack.getLanguage

- -

Get information about a language in a localization pack

-

- -
-
langPackLanguage#eeca5ce3 flags:# official:flags.0?true rtl:flags.2?true beta:flags.3?true name:string native_name:string lang_code:string base_lang_code:flags.1?string plural_code:string strings_count:int translated_count:int translations_url:string = LangPackLanguage;
----functions---
-langpack.getLanguage#6a596502 lang_pack:string lang_code:string = LangPackLanguage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
lang_packstringLanguage pack name
lang_codestringLanguage code
-

Result

-

LangPackLanguage

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/langpack.getLanguages b/data/corefork.telegram.org/method/langpack.getLanguages deleted file mode 100644 index 5269447176..0000000000 --- a/data/corefork.telegram.org/method/langpack.getLanguages +++ /dev/null @@ -1,165 +0,0 @@ - - - - - langpack.getLanguages - - - - - - - - - - - - - -
- -
-
-
- -

langpack.getLanguages

- -

Get information about all languages in a localization pack

-

- -
-
---functions---
-langpack.getLanguages#42c6978f lang_pack:string = Vector<LangPackLanguage>;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
lang_packstringLanguage pack
-

Result

-

Vector<LangPackLanguage>

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400LANG_PACK_INVALIDThe provided language pack is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.acceptEncryption b/data/corefork.telegram.org/method/messages.acceptEncryption deleted file mode 100644 index 70b1fcda96..0000000000 --- a/data/corefork.telegram.org/method/messages.acceptEncryption +++ /dev/null @@ -1,190 +0,0 @@ - - - - - messages.acceptEncryption - - - - - - - - - - - - - -
- -
-
-
- -

messages.acceptEncryption

- -

Confirms creation of a secret chat

-

- -
-
encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;
-encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;
-encryptedChatRequested#48f1d94c flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:long participant_id:long g_a:bytes = EncryptedChat;
-encryptedChat#61f0d4c7 id:int access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long = EncryptedChat;
-encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;
----functions---
-messages.acceptEncryption#3dbc0415 peer:InputEncryptedChat g_b:bytes key_fingerprint:long = EncryptedChat;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputEncryptedChatSecret chat ID
g_bbytesB = g ^ b mod p, see Wikipedia
key_fingerprintlong64-bit fingerprint of the received key
-

Result

-

EncryptedChat

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400ENCRYPTION_ALREADY_ACCEPTEDSecret chat already accepted.
400ENCRYPTION_ALREADY_DECLINEDThe secret chat was already declined.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.addChatUser b/data/corefork.telegram.org/method/messages.addChatUser deleted file mode 100644 index 35d82ebb3a..0000000000 --- a/data/corefork.telegram.org/method/messages.addChatUser +++ /dev/null @@ -1,237 +0,0 @@ - - - - - messages.addChatUser - - - - - - - - - - - - - -
- -
-
-
- -

messages.addChatUser

- -

Adds a user to a chat and sends a service message on it.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.addChatUser#f24753e3 chat_id:long user_id:InputUser fwd_limit:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongChat ID
user_idInputUserUser ID to be added
fwd_limitintNumber of last messages to be forwarded
-

Result

-

messages.StatedMessage

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USERS_TOO_MUCHThe maximum number of users has been exceeded (to create a chat, for example).
400USER_ALREADY_PARTICIPANTThe user is already in the group.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_IS_BLOCKEDYou were blocked by this user.
403USER_NOT_MUTUAL_CONTACTThe provided user is not a mutual contact.
403USER_PRIVACY_RESTRICTEDThe user's privacy settings do not allow you to do this.
400YOU_BLOCKED_USERYou blocked this user.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.checkChatInvite b/data/corefork.telegram.org/method/messages.checkChatInvite deleted file mode 100644 index d7d56fbb8b..0000000000 --- a/data/corefork.telegram.org/method/messages.checkChatInvite +++ /dev/null @@ -1,178 +0,0 @@ - - - - - messages.checkChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

messages.checkChatInvite

- -

Check the validity of a chat invite link and get basic info about it

-

- -
-
chatInviteAlready#5a686d7c chat:Chat = ChatInvite;
-chatInvite#dfc2f58e flags:# channel:flags.0?true broadcast:flags.1?true public:flags.2?true megagroup:flags.3?true title:string photo:Photo participants_count:int participants:flags.4?Vector<User> = ChatInvite;
-chatInvitePeek#61695cb0 chat:Chat expires:int = ChatInvite;
----functions---
-messages.checkChatInvite#3eadb1bb hash:string = ChatInvite;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashstringInvite hash in t.me/joinchat/hash
-

Result

-

ChatInvite

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400INVITE_HASH_EMPTYThe invite hash is empty.
400INVITE_HASH_EXPIREDThe invite link has expired.
400INVITE_HASH_INVALIDThe invite hash is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.checkHistoryImportPeer b/data/corefork.telegram.org/method/messages.checkHistoryImportPeer deleted file mode 100644 index 8b850af35c..0000000000 --- a/data/corefork.telegram.org/method/messages.checkHistoryImportPeer +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.checkHistoryImportPeer - - - - - - - - - - - - - -
- -
-
-
- -

messages.checkHistoryImportPeer

- -

Check whether chat history exported from another chat app can be imported into a specific Telegram chat, click here for more info ».

-

If the check succeeds, and no RPC errors are returned, a messages.CheckedHistoryImportPeer constructor will be returned, with a confirmation text to be shown to the user, before actually initializing the import.

-

- -
-
messages.checkedHistoryImportPeer#a24de717 confirm_text:string = messages.CheckedHistoryImportPeer;
----functions---
-messages.checkHistoryImportPeer#5dc60f03 peer:InputPeer = messages.CheckedHistoryImportPeer;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat where we want to import history ».
-

Result

-

messages.CheckedHistoryImportPeer

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400USER_NOT_MUTUAL_CONTACTThe provided user is not a mutual contact.
-

Related pages

-

Imported messages

-

Telegram allows importing messages and media from foreign chat apps.

-

messages.CheckedHistoryImportPeer

-

Contains a confirmation text to be shown to the user, upon importing chat history, click here for more info ».

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.clearAllDrafts b/data/corefork.telegram.org/method/messages.clearAllDrafts deleted file mode 100644 index e9fc0b2ddf..0000000000 --- a/data/corefork.telegram.org/method/messages.clearAllDrafts +++ /dev/null @@ -1,138 +0,0 @@ - - - - - messages.clearAllDrafts - - - - - - - - - - - - - -
- -
-
-
- -

messages.clearAllDrafts

- -

Clear all drafts.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.clearAllDrafts#7e58ee9c = Bool;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Bool

-

Related pages

-

Message drafts

-

How to handle message drafts

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.clearRecentStickers b/data/corefork.telegram.org/method/messages.clearRecentStickers deleted file mode 100644 index 3eded15e17..0000000000 --- a/data/corefork.telegram.org/method/messages.clearRecentStickers +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.clearRecentStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.clearRecentStickers

- -

Clear recent stickers

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.clearRecentStickers#8999602d flags:# attached:flags.0?true = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
attachedflags.0?trueSet this flag to clear the list of stickers recently attached to photo or video files
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.createChat b/data/corefork.telegram.org/method/messages.createChat deleted file mode 100644 index 0831942e44..0000000000 --- a/data/corefork.telegram.org/method/messages.createChat +++ /dev/null @@ -1,197 +0,0 @@ - - - - - messages.createChat - - - - - - - - - - - - - -
- -
-
-
- -

messages.createChat

- -

Creates a new chat.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.createChat#9cb126e users:Vector<InputUser> title:string = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
usersVector<InputUser>List of user IDs to be invited
titlestringChat name
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_INVALIDInvalid chat.
400CHAT_TITLE_EMPTYNo chat title provided.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400USERS_TOO_FEWNot enough users (to create a chat, for example).
403USER_RESTRICTEDYou're spamreported, you can't create channels or chats.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.deleteChat b/data/corefork.telegram.org/method/messages.deleteChat deleted file mode 100644 index fe1fdc9a2b..0000000000 --- a/data/corefork.telegram.org/method/messages.deleteChat +++ /dev/null @@ -1,170 +0,0 @@ - - - - - messages.deleteChat - - - - - - - - - - - - - -
- -
-
-
- -

messages.deleteChat

- -

Delete a chat

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.deleteChat#5bd0ee50 chat_id:long = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongChat ID
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.deleteExportedChatInvite b/data/corefork.telegram.org/method/messages.deleteExportedChatInvite deleted file mode 100644 index 8c8f45c96e..0000000000 --- a/data/corefork.telegram.org/method/messages.deleteExportedChatInvite +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.deleteExportedChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

messages.deleteExportedChatInvite

- -

Delete a chat invite

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.deleteExportedChatInvite#d464a42b peer:InputPeer link:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
linkstringInvite link
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.deleteHistory b/data/corefork.telegram.org/method/messages.deleteHistory deleted file mode 100644 index 22c7cd9710..0000000000 --- a/data/corefork.telegram.org/method/messages.deleteHistory +++ /dev/null @@ -1,206 +0,0 @@ - - - - - messages.deleteHistory - - - - - - - - - - - - - -
- -
-
-
- -

messages.deleteHistory

- -

Deletes communication history.

-

- -
-
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
----functions---
-messages.deleteHistory#1c015b09 flags:# just_clear:flags.0?true revoke:flags.1?true peer:InputPeer max_id:int = messages.AffectedHistory;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
just_clearflags.0?trueJust clear history for the current user, without actually removing messages for every chat user
revokeflags.1?trueWhether to delete the message history for all chat participants
peerInputPeerUser or chat, communication history of which will be deleted
max_idintMaximum ID of message to delete
-

Result

-

messages.AffectedHistory

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.deleteMessages b/data/corefork.telegram.org/method/messages.deleteMessages deleted file mode 100644 index d9c36ddbe9..0000000000 --- a/data/corefork.telegram.org/method/messages.deleteMessages +++ /dev/null @@ -1,177 +0,0 @@ - - - - - messages.deleteMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.deleteMessages

- -

Deletes messages by their identifiers.

-

- -
-
messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;
----functions---
-messages.deleteMessages#e58e95d2 flags:# revoke:flags.0?true id:Vector<int> = messages.AffectedMessages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
revokeflags.0?trueWhether to delete messages for all participants of the chat
idVector<int>Message ID list
-

Result

-

The method returns the list of successfully deleted messages in Vector<int>.

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
403MESSAGE_DELETE_FORBIDDENYou can't delete one of the messages you tried to delete, most likely because it is a service message.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.deletePhoneCallHistory b/data/corefork.telegram.org/method/messages.deletePhoneCallHistory deleted file mode 100644 index 388a0c15fd..0000000000 --- a/data/corefork.telegram.org/method/messages.deletePhoneCallHistory +++ /dev/null @@ -1,154 +0,0 @@ - - - - - messages.deletePhoneCallHistory - - - - - - - - - - - - - -
- -
-
-
- -

messages.deletePhoneCallHistory

- -

Delete the entire phone call history.

-

- -
-
messages.affectedFoundMessages#ef8d3e6c pts:int pts_count:int offset:int messages:Vector<int> = messages.AffectedFoundMessages;
----functions---
-messages.deletePhoneCallHistory#f9cbe409 flags:# revoke:flags.0?true = messages.AffectedFoundMessages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
revokeflags.0?trueWhether to remove phone call history for participants as well
-

Result

-

messages.AffectedFoundMessages

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.deleteScheduledMessages b/data/corefork.telegram.org/method/messages.deleteScheduledMessages deleted file mode 100644 index e705cb8b5b..0000000000 --- a/data/corefork.telegram.org/method/messages.deleteScheduledMessages +++ /dev/null @@ -1,160 +0,0 @@ - - - - - messages.deleteScheduledMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.deleteScheduledMessages

- -

Delete scheduled messages

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.deleteScheduledMessages#59ae2b16 peer:InputPeer id:Vector<int> = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
idVector<int>Scheduled message IDs
-

Result

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.discardEncryption b/data/corefork.telegram.org/method/messages.discardEncryption deleted file mode 100644 index 4d75229eca..0000000000 --- a/data/corefork.telegram.org/method/messages.discardEncryption +++ /dev/null @@ -1,187 +0,0 @@ - - - - - messages.discardEncryption - - - - - - - - - - - - - -
- -
-
-
- -

messages.discardEncryption

- -

Cancels a request for creation and/or delete info on secret chat.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.discardEncryption#f393aea0 flags:# delete_history:flags.0?true chat_id:int = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
delete_historyflags.0?trueWhether to delete the entire chat history for the other user as well
chat_idintSecret chat ID
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ID_EMPTYThe provided chat ID is empty.
400ENCRYPTION_ALREADY_DECLINEDThe secret chat was already declined.
400ENCRYPTION_ID_INVALIDThe provided secret chat ID is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.editChatAbout b/data/corefork.telegram.org/method/messages.editChatAbout deleted file mode 100644 index f0d32fc285..0000000000 --- a/data/corefork.telegram.org/method/messages.editChatAbout +++ /dev/null @@ -1,216 +0,0 @@ - - - - - messages.editChatAbout - - - - - - - - - - - - - -
- -
-
-
- -

messages.editChatAbout

- -

Edit the description of a group/supergroup/channel.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.editChatAbout#def60797 peer:InputPeer about:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe group/supergroup/channel.
aboutstringThe new description
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ABOUT_NOT_MODIFIEDAbout text has not changed.
400CHAT_ABOUT_TOO_LONGChat about too long.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Bots can use this method

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.editChatAdmin b/data/corefork.telegram.org/method/messages.editChatAdmin deleted file mode 100644 index b29e0f56e5..0000000000 --- a/data/corefork.telegram.org/method/messages.editChatAdmin +++ /dev/null @@ -1,195 +0,0 @@ - - - - - messages.editChatAdmin - - - - - - - - - - - - - -
- -
-
-
- -

messages.editChatAdmin

- -

Make a user admin in a legacy group.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.editChatAdmin#a85bd1c2 chat_id:long user_id:InputUser is_admin:Bool = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongThe ID of the group
user_idInputUserThe user to make admin
is_adminBoolWhether to make him admin
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USER_ID_INVALIDThe provided user ID is invalid.
400USER_NOT_PARTICIPANTYou're not a member of this supergroup/channel.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.editChatDefaultBannedRights b/data/corefork.telegram.org/method/messages.editChatDefaultBannedRights deleted file mode 100644 index 2a489559d3..0000000000 --- a/data/corefork.telegram.org/method/messages.editChatDefaultBannedRights +++ /dev/null @@ -1,206 +0,0 @@ - - - - - messages.editChatDefaultBannedRights - - - - - - - - - - - - - -
- -
-
-
- -

messages.editChatDefaultBannedRights

- -

Edit the default banned rights of a channel/supergroup/group.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.editChatDefaultBannedRights#a5866b41 peer:InputPeer banned_rights:ChatBannedRights = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe peer
banned_rightsChatBannedRightsThe new global rights
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BANNED_RIGHTS_INVALIDYou provided some invalid flags in the banned rights.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400PEER_ID_INVALIDThe provided peer id is invalid.
400UNTIL_DATE_INVALIDInvalid until date provided.
-

Bots can use this method

-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.editChatPhoto b/data/corefork.telegram.org/method/messages.editChatPhoto deleted file mode 100644 index e167aab352..0000000000 --- a/data/corefork.telegram.org/method/messages.editChatPhoto +++ /dev/null @@ -1,203 +0,0 @@ - - - - - messages.editChatPhoto - - - - - - - - - - - - - -
- -
-
-
- -

messages.editChatPhoto

- -

Changes chat photo and sends a service message on it

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.editChatPhoto#35ddd674 chat_id:long photo:InputChatPhoto = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongChat ID
photoInputChatPhotoPhoto to be set
-

Result

-

Returns a messages.StatedMessage object containing a service message sent during an action.

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PHOTO_CROP_SIZE_SMALLPhoto is too small.
400PHOTO_EXT_INVALIDThe extension of the photo is invalid.
400PHOTO_INVALIDPhoto invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.editChatTitle b/data/corefork.telegram.org/method/messages.editChatTitle deleted file mode 100644 index dca4360b94..0000000000 --- a/data/corefork.telegram.org/method/messages.editChatTitle +++ /dev/null @@ -1,193 +0,0 @@ - - - - - messages.editChatTitle - - - - - - - - - - - - - -
- -
-
-
- -

messages.editChatTitle

- -

Chanages chat name and sends a service message on it.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.editChatTitle#73783ffd chat_id:long title:string = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongChat ID
titlestringNew chat name, different from the old one
-

Result

-

Returns a messages.StatedMessage object containing a service message sent during an action.

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400CHAT_TITLE_EMPTYNo chat title provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.editExportedChatInvite b/data/corefork.telegram.org/method/messages.editExportedChatInvite deleted file mode 100644 index 1c5a721dae..0000000000 --- a/data/corefork.telegram.org/method/messages.editExportedChatInvite +++ /dev/null @@ -1,193 +0,0 @@ - - - - - messages.editExportedChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

messages.editExportedChatInvite

- -

Edit an exported chat invite

-

- -
-
messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
-messages.exportedChatInviteReplaced#222600ef invite:ExportedChatInvite new_invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
----functions---
-messages.editExportedChatInvite#2e4ffbe flags:# revoked:flags.2?true peer:InputPeer link:string expire_date:flags.0?int usage_limit:flags.1?int = messages.ExportedChatInvite;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
revokedflags.2?trueWhether to revoke the chat invite
peerInputPeerChat
linkstringInvite link
expire_dateflags.0?intNew expiration date
usage_limitflags.1?intMaximum number of users that can join using this link
-

Result

-

messages.ExportedChatInvite

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.editInlineBotMessage b/data/corefork.telegram.org/method/messages.editInlineBotMessage deleted file mode 100644 index 0dd5b17581..0000000000 --- a/data/corefork.telegram.org/method/messages.editInlineBotMessage +++ /dev/null @@ -1,206 +0,0 @@ - - - - - messages.editInlineBotMessage - - - - - - - - - - - - - -
- -
-
-
- -

messages.editInlineBotMessage

- -

Edit an inline bot message

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.editInlineBotMessage#83557dba flags:# no_webpage:flags.1?true id:InputBotInlineMessageID message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.1?trueDisable webpage preview
idInputBotInlineMessageIDSent inline message ID
messageflags.11?stringMessage
mediaflags.14?InputMediaMedia
reply_markupflags.2?ReplyMarkupReply markup for inline keyboards
entitiesflags.3?Vector<MessageEntity>Message entities for styled text
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MESSAGE_NOT_MODIFIEDThe message text has not changed.
-

Bots can use this method

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.exportChatInvite b/data/corefork.telegram.org/method/messages.exportChatInvite deleted file mode 100644 index 082ede6097..0000000000 --- a/data/corefork.telegram.org/method/messages.exportChatInvite +++ /dev/null @@ -1,217 +0,0 @@ - - - - - messages.exportChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

messages.exportChatInvite

- -

Export an invite link for a chat

-

- -
-
chatInviteExported#b18105e8 flags:# revoked:flags.0?true permanent:flags.5?true link:string admin_id:long date:int start_date:flags.4?int expire_date:flags.1?int usage_limit:flags.2?int usage:flags.3?int = ExportedChatInvite;
----functions---
-messages.exportChatInvite#14b9bcd7 flags:# legacy_revoke_permanent:flags.2?true peer:InputPeer expire_date:flags.0?int usage_limit:flags.1?int = ExportedChatInvite;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
legacy_revoke_permanentflags.2?trueLegacy flag, reproducing legacy behavior of this method: if set, revokes all previous links before creating a new one. Kept for bot API BC, should not be used by modern clients.
peerInputPeerChat
expire_dateflags.0?intExpiration date
usage_limitflags.1?intMaximum number of users that can join using this link
-

Result

-

ExportedChatInvite

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400EXPIRE_DATE_INVALIDThe specified expiration date is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USAGE_LIMIT_INVALIDThe specified usage limit is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.faveSticker b/data/corefork.telegram.org/method/messages.faveSticker deleted file mode 100644 index 926e021c72..0000000000 --- a/data/corefork.telegram.org/method/messages.faveSticker +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.faveSticker - - - - - - - - - - - - - -
- -
-
-
- -

messages.faveSticker

- -

Mark a sticker as favorite

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.faveSticker#b9ffc55b id:InputDocument unfave:Bool = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idInputDocumentSticker to mark as favorite
unfaveBoolUnfavorite
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400STICKER_ID_INVALIDThe provided sticker ID is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.forwardMessage b/data/corefork.telegram.org/method/messages.forwardMessage deleted file mode 100644 index 22d984f418..0000000000 --- a/data/corefork.telegram.org/method/messages.forwardMessage +++ /dev/null @@ -1,177 +0,0 @@ - - - - - messages.forwardMessage - - - - - - - - - - - - - -
- -
-
-
- -

messages.forwardMessage

- -

Forwards single messages.

-

{schema}

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerUser or chat where a message will be forwarded
idintForwarded message ID
random_idlongUnique client message ID required to prevent message resending
-

Result

-

messages.StatedMessage

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid
400MESSAGE_ID_INVALIDThe provided message id is invalid
400PEER_ID_INVALIDThe provided peer id is invalid
400YOU_BLOCKED_USERYou blocked this user
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.forwardMessages b/data/corefork.telegram.org/method/messages.forwardMessages deleted file mode 100644 index 6f68e774c6..0000000000 --- a/data/corefork.telegram.org/method/messages.forwardMessages +++ /dev/null @@ -1,363 +0,0 @@ - - - - - messages.forwardMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.forwardMessages

- -

Forwards messages by their IDs.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.forwardMessages#d9fee60e flags:# silent:flags.5?true background:flags.6?true with_my_score:flags.8?true drop_author:flags.11?true drop_media_captions:flags.12?true from_peer:InputPeer id:Vector<int> random_id:Vector<long> to_peer:InputPeer schedule_date:flags.10?int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.5?trueWhether to send messages silently (no notification will be triggered on the destination clients)
backgroundflags.6?trueWhether to send the message in background
with_my_scoreflags.8?trueWhen forwarding games, whether to include your score in the game
drop_authorflags.11?trueWhether to forward messages without quoting the original author
drop_media_captionsflags.12?trueWhether to strip captions from media
from_peerInputPeerSource of messages
idVector<int>IDs of messages
random_idVector<long>Random ID to prevent resending of messages
to_peerInputPeerDestination peer
schedule_dateflags.10?intScheduled message date for scheduled messages
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BROADCAST_PUBLIC_VOTERS_FORBIDDENYou can't forward polls with public voters.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_RESTRICTEDYou can't send messages in this chat, you were restricted.
403CHAT_SEND_GAME_FORBIDDENYou can't send a game to this chat.
403CHAT_SEND_GIFS_FORBIDDENYou can't send gifs in this chat.
403CHAT_SEND_MEDIA_FORBIDDENYou can't send media in this chat.
403CHAT_SEND_POLL_FORBIDDENYou can't send polls in this chat.
403CHAT_SEND_STICKERS_FORBIDDENYou can't send stickers in this chat.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400GROUPED_MEDIA_INVALIDInvalid grouped media.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MEDIA_EMPTYThe provided media object is invalid.
400MESSAGE_IDS_EMPTYNo message ids were provided.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
420P0NY_FLOODWAIT 
400PEER_ID_INVALIDThe provided peer id is invalid.
400RANDOM_ID_INVALIDA provided random ID is invalid.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
400SLOWMODE_MULTI_MSGS_DISABLEDSlowmode is enabled, you cannot forward multiple messages to this group.
420SLOWMODE_WAIT_XSlowmode is enabled in this chat: you must wait for the specified number of seconds before sending another message to the chat.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400USER_IS_BLOCKEDYou were blocked by this user.
400USER_IS_BOTBots can't send messages to other bots.
400YOU_BLOCKED_USERYou blocked this user.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getAdminsWithInvites b/data/corefork.telegram.org/method/messages.getAdminsWithInvites deleted file mode 100644 index 0eabd250d0..0000000000 --- a/data/corefork.telegram.org/method/messages.getAdminsWithInvites +++ /dev/null @@ -1,149 +0,0 @@ - - - - - messages.getAdminsWithInvites - - - - - - - - - - - - - -
- -
-
-
- -

messages.getAdminsWithInvites

- -

Get info about chat invites generated by admins.

-

- -
-
messages.chatAdminsWithInvites#b69b72d7 admins:Vector<ChatAdminWithInvites> users:Vector<User> = messages.ChatAdminsWithInvites;
----functions---
-messages.getAdminsWithInvites#3920e6ef peer:InputPeer = messages.ChatAdminsWithInvites;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerChat
-

Result

-

messages.ChatAdminsWithInvites

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getAllChats b/data/corefork.telegram.org/method/messages.getAllChats deleted file mode 100644 index f3d5c3ff9e..0000000000 --- a/data/corefork.telegram.org/method/messages.getAllChats +++ /dev/null @@ -1,150 +0,0 @@ - - - - - messages.getAllChats - - - - - - - - - - - - - -
- -
-
-
- -

messages.getAllChats

- -

Get all chats, channels and supergroups

-

- -
-
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
-messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
----functions---
-messages.getAllChats#875f74be except_ids:Vector<long> = messages.Chats;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
except_idsVector<long>Except these chats/channels/supergroups
-

Result

-

messages.Chats

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getAllDrafts b/data/corefork.telegram.org/method/messages.getAllDrafts deleted file mode 100644 index a3ab074305..0000000000 --- a/data/corefork.telegram.org/method/messages.getAllDrafts +++ /dev/null @@ -1,143 +0,0 @@ - - - - - messages.getAllDrafts - - - - - - - - - - - - - -
- -
-
-
- -

messages.getAllDrafts

- -

Save get all message drafts.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.getAllDrafts#6a3f8d65 = Updates;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Updates, contains all the latest updateDraftMessage updates related to all chats with drafts.

-

Related pages

-

Message drafts

-

How to handle message drafts

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getAllStickers b/data/corefork.telegram.org/method/messages.getAllStickers deleted file mode 100644 index c177e06a2b..0000000000 --- a/data/corefork.telegram.org/method/messages.getAllStickers +++ /dev/null @@ -1,153 +0,0 @@ - - - - - messages.getAllStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.getAllStickers

- -

Get all installed stickers

-

- -
-
messages.allStickersNotModified#e86602c3 = messages.AllStickers;
-messages.allStickers#cdbbcebb hash:long sets:Vector<StickerSet> = messages.AllStickers;
----functions---
-messages.getAllStickers#b8a0a1a8 hash:long = messages.AllStickers;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
-

Result

-

messages.AllStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getArchivedStickers b/data/corefork.telegram.org/method/messages.getArchivedStickers deleted file mode 100644 index caf1de733c..0000000000 --- a/data/corefork.telegram.org/method/messages.getArchivedStickers +++ /dev/null @@ -1,167 +0,0 @@ - - - - - messages.getArchivedStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.getArchivedStickers

- -

Get all archived stickers

-

- -
-
messages.archivedStickers#4fcba9c8 count:int sets:Vector<StickerSetCovered> = messages.ArchivedStickers;
----functions---
-messages.getArchivedStickers#57f17692 flags:# masks:flags.0?true offset_id:long limit:int = messages.ArchivedStickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
masksflags.0?trueGet mask stickers
offset_idlongOffsets for pagination, for more info click here
limitintMaximum number of results to return, see pagination
-

Result

-

messages.ArchivedStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getBotCallbackAnswer b/data/corefork.telegram.org/method/messages.getBotCallbackAnswer deleted file mode 100644 index 1a5c7def17..0000000000 --- a/data/corefork.telegram.org/method/messages.getBotCallbackAnswer +++ /dev/null @@ -1,226 +0,0 @@ - - - - - messages.getBotCallbackAnswer - - - - - - - - - - - - - -
- -
-
-
- -

messages.getBotCallbackAnswer

- -

Press an inline callback button and get a callback answer from the bot

-

- -
-
messages.botCallbackAnswer#36585ea4 flags:# alert:flags.1?true has_url:flags.3?true native_ui:flags.4?true message:flags.0?string url:flags.2?string cache_time:int = messages.BotCallbackAnswer;
----functions---
-messages.getBotCallbackAnswer#9342ca07 flags:# game:flags.1?true peer:InputPeer msg_id:int data:flags.0?bytes password:flags.2?InputCheckPasswordSRP = messages.BotCallbackAnswer;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
gameflags.1?trueWhether this is a "play game" button
peerInputPeerWhere was the inline keyboard sent
msg_idintID of the Message with the inline keyboard
dataflags.0?bytesCallback data
passwordflags.2?InputCheckPasswordSRPFor buttons requiring you to verify your identity with your 2FA password, the SRP payload generated using SRP.
-

Result

-

messages.BotCallbackAnswer

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOT_RESPONSE_TIMEOUTA timeout occurred while fetching data from the bot.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400DATA_INVALIDEncrypted data invalid.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
-503TimeoutTimeout while fetching data.
-

Related pages

-

keyboardButtonCallback

-

Callback button

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getChatInviteImporters b/data/corefork.telegram.org/method/messages.getChatInviteImporters deleted file mode 100644 index adeb48c928..0000000000 --- a/data/corefork.telegram.org/method/messages.getChatInviteImporters +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.getChatInviteImporters - - - - - - - - - - - - - -
- -
-
-
- -

messages.getChatInviteImporters

- -

Get info about the users that joined the chat using a specific chat invite

-

- -
-
messages.chatInviteImporters#81b6b00a count:int importers:Vector<ChatInviteImporter> users:Vector<User> = messages.ChatInviteImporters;
----functions---
-messages.getChatInviteImporters#26fb7289 peer:InputPeer link:string offset_date:int offset_user:InputUser limit:int = messages.ChatInviteImporters;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerChat
linkstringInvite link
offset_dateintOffsets for pagination, for more info click here
offset_userInputUserUser ID for pagination
limitintMaximum number of results to return, see pagination
-

Result

-

messages.ChatInviteImporters

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getChats b/data/corefork.telegram.org/method/messages.getChats deleted file mode 100644 index a0133d55a0..0000000000 --- a/data/corefork.telegram.org/method/messages.getChats +++ /dev/null @@ -1,173 +0,0 @@ - - - - - messages.getChats - - - - - - - - - - - - - -
- -
-
-
- -

messages.getChats

- -

Returns chat basic info on their IDs.

-

- -
-
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
-messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
----functions---
-messages.getChats#49e9528f id:Vector<long> = messages.Chats;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idVector<long>List of chat IDs
-

Result

-

messages.Chats

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getCommonChats b/data/corefork.telegram.org/method/messages.getCommonChats deleted file mode 100644 index c46e887e46..0000000000 --- a/data/corefork.telegram.org/method/messages.getCommonChats +++ /dev/null @@ -1,185 +0,0 @@ - - - - - messages.getCommonChats - - - - - - - - - - - - - -
- -
-
-
- -

messages.getCommonChats

- -

Get chats in common with a user

-

- -
-
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
-messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
----functions---
-messages.getCommonChats#e40ca104 user_id:InputUser max_id:long limit:int = messages.Chats;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idInputUserUser ID
max_idlongMaximum ID of chat to return (see pagination)
limitintMaximum number of results to return, see pagination
-

Result

-

messages.Chats

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MSG_ID_INVALIDInvalid message ID provided.
400USER_ID_INVALIDThe provided user ID is invalid.
-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getDhConfig b/data/corefork.telegram.org/method/messages.getDhConfig deleted file mode 100644 index 616eaccf05..0000000000 --- a/data/corefork.telegram.org/method/messages.getDhConfig +++ /dev/null @@ -1,175 +0,0 @@ - - - - - messages.getDhConfig - - - - - - - - - - - - - -
- -
-
-
- -

messages.getDhConfig

- -

Returns configuration parameters for Diffie-Hellman key generation. Can also return a random sequence of bytes of required length.

-

- -
-
messages.dhConfigNotModified#c0e24635 random:bytes = messages.DhConfig;
-messages.dhConfig#2c221edd g:int p:bytes version:int random:bytes = messages.DhConfig;
----functions---
-messages.getDhConfig#26cf8950 version:int random_length:int = messages.DhConfig;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
versionintValue of the version parameter from messages.dhConfig, avialable at the client
random_lengthintLength of the required random sequence
-

Result

-

messages.DhConfig

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400RANDOM_LENGTH_INVALIDRandom length invalid.
-

Related pages

-

messages.dhConfig

-

New set of configuring parameters.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getDialogFilters b/data/corefork.telegram.org/method/messages.getDialogFilters deleted file mode 100644 index c596eb405c..0000000000 --- a/data/corefork.telegram.org/method/messages.getDialogFilters +++ /dev/null @@ -1,136 +0,0 @@ - - - - - messages.getDialogFilters - - - - - - - - - - - - - -
- -
-
-
- -

messages.getDialogFilters

- -

Get folders

-

- -
-
---functions---
-messages.getDialogFilters#f19ed96d = Vector<DialogFilter>;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Vector<DialogFilter>

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getDialogUnreadMarks b/data/corefork.telegram.org/method/messages.getDialogUnreadMarks deleted file mode 100644 index 6600db9d67..0000000000 --- a/data/corefork.telegram.org/method/messages.getDialogUnreadMarks +++ /dev/null @@ -1,133 +0,0 @@ - - - - - messages.getDialogUnreadMarks - - - - - - - - - - - - - -
- -
-
-
- -

messages.getDialogUnreadMarks

- -

Get dialogs manually marked as unread

-

- -
-
---functions---
-messages.getDialogUnreadMarks#22e24e22 = Vector<DialogPeer>;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Vector<DialogPeer>

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getDialogs b/data/corefork.telegram.org/method/messages.getDialogs deleted file mode 100644 index 3602c618b1..0000000000 --- a/data/corefork.telegram.org/method/messages.getDialogs +++ /dev/null @@ -1,213 +0,0 @@ - - - - - messages.getDialogs - - - - - - - - - - - - - -
- -
-
-
- -

messages.getDialogs

- -

Returns the current user dialog list.

-

- -
-
messages.dialogs#15ba6c40 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;
-messages.dialogsSlice#71e094f3 count:int dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;
-messages.dialogsNotModified#f0e3e596 count:int = messages.Dialogs;
----functions---
-messages.getDialogs#a0f4cb4f flags:# exclude_pinned:flags.0?true folder_id:flags.1?int offset_date:int offset_id:int offset_peer:InputPeer limit:int hash:long = messages.Dialogs;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
exclude_pinnedflags.0?trueExclude pinned dialogs
folder_idflags.1?intPeer folder ID, for more info click here
offset_dateintOffsets for pagination, for more info click here
offset_idintOffsets for pagination, for more info click here
offset_peerInputPeerOffset peer for pagination
limitintNumber of list elements to be returned
hashlongHash for pagination, for more info click here
-

Result

-

messages.Dialogs

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400FOLDER_ID_INVALIDInvalid folder ID.
400OFFSET_PEER_ID_INVALIDThe provided offset peer is invalid.
-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getDocumentByHash b/data/corefork.telegram.org/method/messages.getDocumentByHash deleted file mode 100644 index ddd2aa79b5..0000000000 --- a/data/corefork.telegram.org/method/messages.getDocumentByHash +++ /dev/null @@ -1,178 +0,0 @@ - - - - - messages.getDocumentByHash - - - - - - - - - - - - - -
- -
-
-
- -

messages.getDocumentByHash

- -

Get a document by its SHA256 hash, mainly used for gifs

-

- -
-
documentEmpty#36f8c871 id:long = Document;
-document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
----functions---
-messages.getDocumentByHash#338e2464 sha256:bytes size:int mime_type:string = Document;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
sha256bytesSHA256 of file
sizeintSize of the file in bytes
mime_typestringMime type
-

Result

-

Document

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400SHA256_HASH_INVALIDThe provided SHA256 hash is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getEmojiKeywords b/data/corefork.telegram.org/method/messages.getEmojiKeywords deleted file mode 100644 index 0f0f0abc28..0000000000 --- a/data/corefork.telegram.org/method/messages.getEmojiKeywords +++ /dev/null @@ -1,149 +0,0 @@ - - - - - messages.getEmojiKeywords - - - - - - - - - - - - - -
- -
-
-
- -

messages.getEmojiKeywords

- -

Get localized emoji keywords

-

- -
-
emojiKeywordsDifference#5cc761bd lang_code:string from_version:int version:int keywords:Vector<EmojiKeyword> = EmojiKeywordsDifference;
----functions---
-messages.getEmojiKeywords#35a0e062 lang_code:string = EmojiKeywordsDifference;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
lang_codestringLanguage code
-

Result

-

EmojiKeywordsDifference

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getEmojiKeywordsDifference b/data/corefork.telegram.org/method/messages.getEmojiKeywordsDifference deleted file mode 100644 index 9691cd452d..0000000000 --- a/data/corefork.telegram.org/method/messages.getEmojiKeywordsDifference +++ /dev/null @@ -1,154 +0,0 @@ - - - - - messages.getEmojiKeywordsDifference - - - - - - - - - - - - - -
- -
-
-
- -

messages.getEmojiKeywordsDifference

- -

Get changed emoji keywords

-

- -
-
emojiKeywordsDifference#5cc761bd lang_code:string from_version:int version:int keywords:Vector<EmojiKeyword> = EmojiKeywordsDifference;
----functions---
-messages.getEmojiKeywordsDifference#1508b6af lang_code:string from_version:int = EmojiKeywordsDifference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
lang_codestringLanguage code
from_versionintPrevious emoji keyword localization version
-

Result

-

EmojiKeywordsDifference

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getEmojiKeywordsLanguages b/data/corefork.telegram.org/method/messages.getEmojiKeywordsLanguages deleted file mode 100644 index 149e643b64..0000000000 --- a/data/corefork.telegram.org/method/messages.getEmojiKeywordsLanguages +++ /dev/null @@ -1,148 +0,0 @@ - - - - - messages.getEmojiKeywordsLanguages - - - - - - - - - - - - - -
- -
-
-
- -

messages.getEmojiKeywordsLanguages

- -

Get info about an emoji keyword localization

-

- -
-
---functions---
-messages.getEmojiKeywordsLanguages#4e9963b2 lang_codes:Vector<string> = Vector<EmojiLanguage>;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
lang_codesVector<string>Language codes
-

Result

-

Vector<EmojiLanguage>

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getEmojiURL b/data/corefork.telegram.org/method/messages.getEmojiURL deleted file mode 100644 index dde7230fec..0000000000 --- a/data/corefork.telegram.org/method/messages.getEmojiURL +++ /dev/null @@ -1,149 +0,0 @@ - - - - - messages.getEmojiURL - - - - - - - - - - - - - -
- -
-
-
- -

messages.getEmojiURL

- -

Returns an HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation

-

- -
-
emojiURL#a575739d url:string = EmojiURL;
----functions---
-messages.getEmojiURL#d5b10c26 lang_code:string = EmojiURL;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
lang_codestringLanguage code for which the emoji replacements will be suggested
-

Result

-

EmojiURL

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getExportedChatInvite b/data/corefork.telegram.org/method/messages.getExportedChatInvite deleted file mode 100644 index e05f2dd67f..0000000000 --- a/data/corefork.telegram.org/method/messages.getExportedChatInvite +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.getExportedChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

messages.getExportedChatInvite

- -

Get info about a chat invite

-

- -
-
messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
-messages.exportedChatInviteReplaced#222600ef invite:ExportedChatInvite new_invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
----functions---
-messages.getExportedChatInvite#73746f5c peer:InputPeer link:string = messages.ExportedChatInvite;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerChat
linkstringInvite link
-

Result

-

messages.ExportedChatInvite

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getExportedChatInvites b/data/corefork.telegram.org/method/messages.getExportedChatInvites deleted file mode 100644 index 3fd02c9507..0000000000 --- a/data/corefork.telegram.org/method/messages.getExportedChatInvites +++ /dev/null @@ -1,182 +0,0 @@ - - - - - messages.getExportedChatInvites - - - - - - - - - - - - - -
- -
-
-
- -

messages.getExportedChatInvites

- -

Get info about the chat invites of a specific chat

-

- -
-
messages.exportedChatInvites#bdc62dcc count:int invites:Vector<ExportedChatInvite> users:Vector<User> = messages.ExportedChatInvites;
----functions---
-messages.getExportedChatInvites#a2b5a3f6 flags:# revoked:flags.3?true peer:InputPeer admin_id:InputUser offset_date:flags.2?int offset_link:flags.2?string limit:int = messages.ExportedChatInvites;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
revokedflags.3?trueWhether to fetch revoked chat invites
peerInputPeerChat
admin_idInputUserWhether to only fetch chat invites from this admin
offset_dateflags.2?intOffsets for pagination, for more info click here
offset_linkflags.2?stringOffsets for pagination, for more info click here
limitintMaximum number of results to return, see pagination
-

Result

-

messages.ExportedChatInvites

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getFavedStickers b/data/corefork.telegram.org/method/messages.getFavedStickers deleted file mode 100644 index 266ebdff82..0000000000 --- a/data/corefork.telegram.org/method/messages.getFavedStickers +++ /dev/null @@ -1,153 +0,0 @@ - - - - - messages.getFavedStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.getFavedStickers

- -

Get faved stickers

-

- -
-
messages.favedStickersNotModified#9e8fa6d3 = messages.FavedStickers;
-messages.favedStickers#2cb51097 hash:long packs:Vector<StickerPack> stickers:Vector<Document> = messages.FavedStickers;
----functions---
-messages.getFavedStickers#4f1aaa9 hash:long = messages.FavedStickers;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
-

Result

-

messages.FavedStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getFeaturedStickers b/data/corefork.telegram.org/method/messages.getFeaturedStickers deleted file mode 100644 index 24bc4fea95..0000000000 --- a/data/corefork.telegram.org/method/messages.getFeaturedStickers +++ /dev/null @@ -1,153 +0,0 @@ - - - - - messages.getFeaturedStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.getFeaturedStickers

- -

Get featured stickers

-

- -
-
messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;
-messages.featuredStickers#84c02310 hash:long count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;
----functions---
-messages.getFeaturedStickers#64780b14 hash:long = messages.FeaturedStickers;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
-

Result

-

messages.FeaturedStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getFullChat b/data/corefork.telegram.org/method/messages.getFullChat deleted file mode 100644 index 0014643c2d..0000000000 --- a/data/corefork.telegram.org/method/messages.getFullChat +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.getFullChat - - - - - - - - - - - - - -
- -
-
-
- -

messages.getFullChat

- -

Returns full chat info according to its ID.

-

- -
-
messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.ChatFull;
----functions---
-messages.getFullChat#aeb00b34 chat_id:long = messages.ChatFull;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongChat ID
-

Result

-

messages.ChatFull

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getGameHighScores b/data/corefork.telegram.org/method/messages.getGameHighScores deleted file mode 100644 index 60f5c81337..0000000000 --- a/data/corefork.telegram.org/method/messages.getGameHighScores +++ /dev/null @@ -1,187 +0,0 @@ - - - - - messages.getGameHighScores - - - - - - - - - - - - - -
- -
-
-
- -

messages.getGameHighScores

- -

Get highscores of a game

-

- -
-
messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;
----functions---
-messages.getGameHighScores#e822649d peer:InputPeer id:int user_id:InputUser = messages.HighScores;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerWhere was the game sent
idintID of message with game media attachment
user_idInputUserGet high scores made by a certain user
-

Result

-

messages.HighScores

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USER_BOT_REQUIREDThis method can only be called by a bot.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getInlineBotResults b/data/corefork.telegram.org/method/messages.getInlineBotResults deleted file mode 100644 index fc885247ca..0000000000 --- a/data/corefork.telegram.org/method/messages.getInlineBotResults +++ /dev/null @@ -1,226 +0,0 @@ - - - - - messages.getInlineBotResults - - - - - - - - - - - - - -
- -
-
-
- -

messages.getInlineBotResults

- -

Query an inline bot

-

- -
-
messages.botResults#947ca848 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;
----functions---
-messages.getInlineBotResults#514e999d flags:# bot:InputUser peer:InputPeer geo_point:flags.0?InputGeoPoint query:string offset:string = messages.BotResults;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
botInputUserThe bot to query
peerInputPeerThe currently opened chat
geo_pointflags.0?InputGeoPointThe geolocation, if requested
querystringThe query
offsetstringThe offset within the results, will be passed directly as-is to the bot.
-

Result

-

messages.BotResults

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOT_INLINE_DISABLEDThis bot can't be used in inline mode.
400BOT_INVALIDThis is not a valid bot.
400BOT_RESPONSE_TIMEOUTA timeout occurred while fetching data from the bot.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
-503TimeoutTimeout while fetching data.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getInlineGameHighScores b/data/corefork.telegram.org/method/messages.getInlineGameHighScores deleted file mode 100644 index b27ae767a8..0000000000 --- a/data/corefork.telegram.org/method/messages.getInlineGameHighScores +++ /dev/null @@ -1,177 +0,0 @@ - - - - - messages.getInlineGameHighScores - - - - - - - - - - - - - -
- -
-
-
- -

messages.getInlineGameHighScores

- -

Get highscores of a game sent using an inline bot

-

- -
-
messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;
----functions---
-messages.getInlineGameHighScores#f635e1b id:InputBotInlineMessageID user_id:InputUser = messages.HighScores;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idInputBotInlineMessageIDID of inline message
user_idInputUserGet high scores of a certain user
-

Result

-

messages.HighScores

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400USER_BOT_REQUIREDThis method can only be called by a bot.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getMaskStickers b/data/corefork.telegram.org/method/messages.getMaskStickers deleted file mode 100644 index cf3a249b4d..0000000000 --- a/data/corefork.telegram.org/method/messages.getMaskStickers +++ /dev/null @@ -1,153 +0,0 @@ - - - - - messages.getMaskStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.getMaskStickers

- -

Get installed mask stickers

-

- -
-
messages.allStickersNotModified#e86602c3 = messages.AllStickers;
-messages.allStickers#cdbbcebb hash:long sets:Vector<StickerSet> = messages.AllStickers;
----functions---
-messages.getMaskStickers#640f82b8 hash:long = messages.AllStickers;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
-

Result

-

messages.AllStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getMessageEditData b/data/corefork.telegram.org/method/messages.getMessageEditData deleted file mode 100644 index fd034fcd9d..0000000000 --- a/data/corefork.telegram.org/method/messages.getMessageEditData +++ /dev/null @@ -1,186 +0,0 @@ - - - - - messages.getMessageEditData - - - - - - - - - - - - - -
- -
-
-
- -

messages.getMessageEditData

- -

Find out if a media message's caption can be edited

-

- -
-
messages.messageEditData#26b5dde6 flags:# caption:flags.0?true = messages.MessageEditData;
----functions---
-messages.getMessageEditData#fda68d36 peer:InputPeer id:int = messages.MessageEditData;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer where the media was sent
idintID of message
-

Result

-

messages.MessageEditData

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
403MESSAGE_AUTHOR_REQUIREDMessage author required.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getMessageReactionsList b/data/corefork.telegram.org/method/messages.getMessageReactionsList deleted file mode 100644 index 7865c1eac2..0000000000 --- a/data/corefork.telegram.org/method/messages.getMessageReactionsList +++ /dev/null @@ -1,178 +0,0 @@ - - - - - messages.getMessageReactionsList - - - - - - - - - - - - - -
- -
-
-
- -

messages.getMessageReactionsList

- -

Get full message reaction list

-

- -
-
 Method schema is available as of layer 136. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerPeer
idintMessage ID
reactionflags.0?stringGet only reactions of this type (UTF8 emoji)
offsetflags.1?stringOffset (typically taken from the next_offset field of the returned MessageReactionsList)
limitintMaximum number of results to return, see pagination
-

Result

-

MessageReactionsList

-

Bots can use this method

-

Related pages

-

MessageReactionsList

-

List of message reactions

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getMessageReadParticipants b/data/corefork.telegram.org/method/messages.getMessageReadParticipants deleted file mode 100644 index fc3d628c93..0000000000 --- a/data/corefork.telegram.org/method/messages.getMessageReadParticipants +++ /dev/null @@ -1,173 +0,0 @@ - - - - - messages.getMessageReadParticipants - - - - - - - - - - - - - -
- -
-
-
- -

messages.getMessageReadParticipants

- -

Get which users read a specific message: only available for groups and supergroups with less than chat_read_mark_size_threshold members, read receipts will be stored for chat_read_mark_expire_period seconds after the message was sent, see client configuration for more info ».

-

- -
-
---functions---
-messages.getMessageReadParticipants#2c6f97b7 peer:InputPeer msg_id:int = Vector<long>;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerDialog
msg_idintMessage ID
-

Result

-

Vector<long>

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_TOO_BIGThis method is not available for groups with more than chat_read_mark_size_threshold members, see client configuration ».
-

Related pages

-

Client configuration

-

The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getMessages b/data/corefork.telegram.org/method/messages.getMessages deleted file mode 100644 index 89be9a90ec..0000000000 --- a/data/corefork.telegram.org/method/messages.getMessages +++ /dev/null @@ -1,153 +0,0 @@ - - - - - messages.getMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.getMessages

- -

Returns the list of messages by their IDs.

-

- -
-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
----functions---
-messages.getMessages#63c66506 id:Vector<InputMessage> = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idVector<InputMessage>Message ID list
-

Result

-

messages.Messages

-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getMessagesReactions b/data/corefork.telegram.org/method/messages.getMessagesReactions deleted file mode 100644 index 796e9c3703..0000000000 --- a/data/corefork.telegram.org/method/messages.getMessagesReactions +++ /dev/null @@ -1,153 +0,0 @@ - - - - - messages.getMessagesReactions - - - - - - - - - - - - - -
- -
-
-
- -

messages.getMessagesReactions

- -

Get message reactions

-

- -
-
 Method schema is available as of layer 136. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
idVector<int>Message IDs
-

Result

-

Updates

-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getMessagesViews b/data/corefork.telegram.org/method/messages.getMessagesViews deleted file mode 100644 index 1a4ab38a02..0000000000 --- a/data/corefork.telegram.org/method/messages.getMessagesViews +++ /dev/null @@ -1,199 +0,0 @@ - - - - - messages.getMessagesViews - - - - - - - - - - - - - -
- -
-
-
- -

messages.getMessagesViews

- -

Get and increase the view counter of a message sent or forwarded from a channel

-

- -
-
messages.messageViews#b6c4f543 views:Vector<MessageViews> chats:Vector<Chat> users:Vector<User> = messages.MessageViews;
----functions---
-messages.getMessagesViews#5784d3e1 peer:InputPeer id:Vector<int> increment:Bool = messages.MessageViews;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer where the message was found
idVector<int>ID of message
incrementBoolWhether to mark the message as viewed and increment the view counter
-

Result

-

Vector<int>

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getOldFeaturedStickers b/data/corefork.telegram.org/method/messages.getOldFeaturedStickers deleted file mode 100644 index 2cd5175023..0000000000 --- a/data/corefork.telegram.org/method/messages.getOldFeaturedStickers +++ /dev/null @@ -1,163 +0,0 @@ - - - - - messages.getOldFeaturedStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.getOldFeaturedStickers

- -

Method for fetching previously featured stickers

-

- -
-
messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;
-messages.featuredStickers#84c02310 hash:long count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;
----functions---
-messages.getOldFeaturedStickers#7ed094a1 offset:int limit:int hash:long = messages.FeaturedStickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
offsetintOffset
limitintMaximum number of results to return, see pagination
hashlongHash for pagination, for more info click here
-

Result

-

messages.FeaturedStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getOnlines b/data/corefork.telegram.org/method/messages.getOnlines deleted file mode 100644 index c66a640ec2..0000000000 --- a/data/corefork.telegram.org/method/messages.getOnlines +++ /dev/null @@ -1,171 +0,0 @@ - - - - - messages.getOnlines - - - - - - - - - - - - - -
- -
-
-
- -

messages.getOnlines

- -

Get count of online users in a chat

-

- -
-
chatOnlines#f041e250 onlines:int = ChatOnlines;
----functions---
-messages.getOnlines#6e2be050 peer:InputPeer = ChatOnlines;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat
-

Result

-

ChatOnlines

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getPeerDialogs b/data/corefork.telegram.org/method/messages.getPeerDialogs deleted file mode 100644 index 2fb117751c..0000000000 --- a/data/corefork.telegram.org/method/messages.getPeerDialogs +++ /dev/null @@ -1,181 +0,0 @@ - - - - - messages.getPeerDialogs - - - - - - - - - - - - - -
- -
-
-
- -

messages.getPeerDialogs

- -

Get dialog info of specified peers

-

- -
-
messages.peerDialogs#3371c354 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> state:updates.State = messages.PeerDialogs;
----functions---
-messages.getPeerDialogs#e470bcfd peers:Vector<InputDialogPeer> = messages.PeerDialogs;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peersVector<InputDialogPeer>Peers
-

Result

-

messages.PeerDialogs

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getPeerSettings b/data/corefork.telegram.org/method/messages.getPeerSettings deleted file mode 100644 index a56e903992..0000000000 --- a/data/corefork.telegram.org/method/messages.getPeerSettings +++ /dev/null @@ -1,171 +0,0 @@ - - - - - messages.getPeerSettings - - - - - - - - - - - - - -
- -
-
-
- -

messages.getPeerSettings

- -

Get peer settings

-

- -
-
peerSettings#733f2961 flags:# report_spam:flags.0?true add_contact:flags.1?true block_contact:flags.2?true share_contact:flags.3?true need_contacts_exception:flags.4?true report_geo:flags.5?true autoarchived:flags.7?true invite_members:flags.8?true geo_distance:flags.6?int = PeerSettings;
----functions---
-messages.getPeerSettings#3672e09c peer:InputPeer = PeerSettings;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe peer
-

Result

-

PeerSettings

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getPinnedDialogs b/data/corefork.telegram.org/method/messages.getPinnedDialogs deleted file mode 100644 index 7078cfb778..0000000000 --- a/data/corefork.telegram.org/method/messages.getPinnedDialogs +++ /dev/null @@ -1,169 +0,0 @@ - - - - - messages.getPinnedDialogs - - - - - - - - - - - - - -
- -
-
-
- -

messages.getPinnedDialogs

- -

Get pinned dialogs

-

- -
-
messages.peerDialogs#3371c354 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> state:updates.State = messages.PeerDialogs;
----functions---
-messages.getPinnedDialogs#d6b94df2 folder_id:int = messages.PeerDialogs;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
folder_idintPeer folder ID, for more info click here
-

Result

-

messages.PeerDialogs

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400FOLDER_ID_INVALIDInvalid folder ID.
-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getPollResults b/data/corefork.telegram.org/method/messages.getPollResults deleted file mode 100644 index a4b3d7f31d..0000000000 --- a/data/corefork.telegram.org/method/messages.getPollResults +++ /dev/null @@ -1,177 +0,0 @@ - - - - - messages.getPollResults - - - - - - - - - - - - - -
- -
-
-
- -

messages.getPollResults

- -

Get poll results

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.getPollResults#73bb643b peer:InputPeer msg_id:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer where the poll was found
msg_idintMessage ID of poll message
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getRecentLocations b/data/corefork.telegram.org/method/messages.getRecentLocations deleted file mode 100644 index 4c10ba0336..0000000000 --- a/data/corefork.telegram.org/method/messages.getRecentLocations +++ /dev/null @@ -1,165 +0,0 @@ - - - - - messages.getRecentLocations - - - - - - - - - - - - - -
- -
-
-
- -

messages.getRecentLocations

- -

Get live location history of a certain user

-

- -
-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
----functions---
-messages.getRecentLocations#702a40e0 peer:InputPeer limit:int hash:long = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerUser
limitintMaximum number of results to return, see pagination
hashlongHash for pagination, for more info click here
-

Result

-

messages.Messages

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getRecentStickers b/data/corefork.telegram.org/method/messages.getRecentStickers deleted file mode 100644 index 07a32d074b..0000000000 --- a/data/corefork.telegram.org/method/messages.getRecentStickers +++ /dev/null @@ -1,163 +0,0 @@ - - - - - messages.getRecentStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.getRecentStickers

- -

Get recent stickers

-

- -
-
messages.recentStickersNotModified#b17f890 = messages.RecentStickers;
-messages.recentStickers#88d37c56 hash:long packs:Vector<StickerPack> stickers:Vector<Document> dates:Vector<int> = messages.RecentStickers;
----functions---
-messages.getRecentStickers#9da9403b flags:# attached:flags.0?true hash:long = messages.RecentStickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
attachedflags.0?trueGet stickers recently attached to photo or video files
hashlongHash for pagination, for more info click here
-

Result

-

messages.RecentStickers

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getReplies b/data/corefork.telegram.org/method/messages.getReplies deleted file mode 100644 index 120bb97404..0000000000 --- a/data/corefork.telegram.org/method/messages.getReplies +++ /dev/null @@ -1,217 +0,0 @@ - - - - - messages.getReplies - - - - - - - - - - - - - -
- -
-
-
- -

messages.getReplies

- -

Get messages in a reply thread

-

- -
-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
----functions---
-messages.getReplies#22ddd30c peer:InputPeer msg_id:int offset_id:int offset_date:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
msg_idintMessage ID
offset_idintOffsets for pagination, for more info click here
offset_dateintOffsets for pagination, for more info click here
add_offsetintOffsets for pagination, for more info click here
limitintMaximum number of results to return, see pagination
max_idintIf a positive value was transferred, the method will return only messages with ID smaller than max_id
min_idintIf a positive value was transferred, the method will return only messages with ID bigger than min_id
hashlongHash for pagination, for more info click here
-

Result

-

messages.Messages

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getSavedGifs b/data/corefork.telegram.org/method/messages.getSavedGifs deleted file mode 100644 index 7de5e9faf6..0000000000 --- a/data/corefork.telegram.org/method/messages.getSavedGifs +++ /dev/null @@ -1,153 +0,0 @@ - - - - - messages.getSavedGifs - - - - - - - - - - - - - -
- -
-
-
- -

messages.getSavedGifs

- -

Get saved GIFs

-

- -
-
messages.savedGifsNotModified#e8025ca2 = messages.SavedGifs;
-messages.savedGifs#84a02a0d hash:long gifs:Vector<Document> = messages.SavedGifs;
----functions---
-messages.getSavedGifs#5cf09635 hash:long = messages.SavedGifs;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashlongHash for pagination, for more info click here
-

Result

-

messages.SavedGifs

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getScheduledHistory b/data/corefork.telegram.org/method/messages.getScheduledHistory deleted file mode 100644 index 602a0db6a5..0000000000 --- a/data/corefork.telegram.org/method/messages.getScheduledHistory +++ /dev/null @@ -1,182 +0,0 @@ - - - - - messages.getScheduledHistory - - - - - - - - - - - - - -
- -
-
-
- -

messages.getScheduledHistory

- -

Get scheduled messages

-

- -
-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
----functions---
-messages.getScheduledHistory#f516760b peer:InputPeer hash:long = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
hashlongHash for pagination, for more info click here
-

Result

-

messages.Messages

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getScheduledMessages b/data/corefork.telegram.org/method/messages.getScheduledMessages deleted file mode 100644 index c09be1a4ed..0000000000 --- a/data/corefork.telegram.org/method/messages.getScheduledMessages +++ /dev/null @@ -1,179 +0,0 @@ - - - - - messages.getScheduledMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.getScheduledMessages

- -

Get scheduled messages

-

- -
-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
----functions---
-messages.getScheduledMessages#bdbb0464 peer:InputPeer id:Vector<int> = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
idVector<int>IDs of scheduled messages
-

Result

-

messages.Messages

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getSearchCounters b/data/corefork.telegram.org/method/messages.getSearchCounters deleted file mode 100644 index db2aba4779..0000000000 --- a/data/corefork.telegram.org/method/messages.getSearchCounters +++ /dev/null @@ -1,173 +0,0 @@ - - - - - messages.getSearchCounters - - - - - - - - - - - - - -
- -
-
-
- -

messages.getSearchCounters

- -

Get the number of results that would be found by a messages.search call with the same parameters

-

- -
-
---functions---
-messages.getSearchCounters#732eef00 peer:InputPeer filters:Vector<MessagesFilter> = Vector<messages.SearchCounter>;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer where to search
filtersVector<MessagesFilter>Search filters
-

Result

-

Vector<messages.SearchCounter>

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

messages.search

-

Gets back found messages

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getSplitRanges b/data/corefork.telegram.org/method/messages.getSplitRanges deleted file mode 100644 index d685239dbc..0000000000 --- a/data/corefork.telegram.org/method/messages.getSplitRanges +++ /dev/null @@ -1,133 +0,0 @@ - - - - - messages.getSplitRanges - - - - - - - - - - - - - -
- -
-
-
- -

messages.getSplitRanges

- -

Get message ranges for saving the user's chat history

-

- -
-
---functions---
-messages.getSplitRanges#1cff7e08 = Vector<MessageRange>;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Vector<MessageRange>

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getStickerSet b/data/corefork.telegram.org/method/messages.getStickerSet deleted file mode 100644 index e9b99a47f2..0000000000 --- a/data/corefork.telegram.org/method/messages.getStickerSet +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.getStickerSet - - - - - - - - - - - - - -
- -
-
-
- -

messages.getStickerSet

- -

Get info about a stickerset

-

- -
-
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
----functions---
-messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
stickersetInputStickerSetStickerset
-

Result

-

messages.StickerSet

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400EMOTICON_STICKERPACK_MISSING 
400STICKERSET_INVALIDThe provided sticker set is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getStickers b/data/corefork.telegram.org/method/messages.getStickers deleted file mode 100644 index 9c8918bb06..0000000000 --- a/data/corefork.telegram.org/method/messages.getStickers +++ /dev/null @@ -1,175 +0,0 @@ - - - - - messages.getStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.getStickers

- -

Get stickers by emoji

-

- -
-
messages.stickersNotModified#f1749a22 = messages.Stickers;
-messages.stickers#30a6ec7e hash:long stickers:Vector<Document> = messages.Stickers;
----functions---
-messages.getStickers#d5a5d3a1 emoticon:string hash:long = messages.Stickers;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
emoticonstringThe emoji
hashlongHash for pagination, for more info click here
-

Result

-

messages.Stickers

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400EMOTICON_EMPTYThe emoji is empty.
-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getSuggestedDialogFilters b/data/corefork.telegram.org/method/messages.getSuggestedDialogFilters deleted file mode 100644 index 155c653d41..0000000000 --- a/data/corefork.telegram.org/method/messages.getSuggestedDialogFilters +++ /dev/null @@ -1,136 +0,0 @@ - - - - - messages.getSuggestedDialogFilters - - - - - - - - - - - - - -
- -
-
-
- -

messages.getSuggestedDialogFilters

- -

Get suggested folders

-

- -
-
---functions---
-messages.getSuggestedDialogFilters#a29cd42c = Vector<DialogFilterSuggested>;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

Vector<DialogFilterSuggested>

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getUnreadMentions b/data/corefork.telegram.org/method/messages.getUnreadMentions deleted file mode 100644 index b68ef6e471..0000000000 --- a/data/corefork.telegram.org/method/messages.getUnreadMentions +++ /dev/null @@ -1,212 +0,0 @@ - - - - - messages.getUnreadMentions - - - - - - - - - - - - - -
- -
-
-
- -

messages.getUnreadMentions

- -

Get unread messages where we were mentioned

-

- -
-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
----functions---
-messages.getUnreadMentions#46578472 peer:InputPeer offset_id:int add_offset:int limit:int max_id:int min_id:int = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer where to look for mentions
offset_idintOffsets for pagination, for more info click here
add_offsetintOffsets for pagination, for more info click here
limitintMaximum number of results to return, see pagination
max_idintMaximum message ID to return, see pagination
min_idintMinimum message ID to return, see pagination
-

Result

-

messages.Messages

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getWebPage b/data/corefork.telegram.org/method/messages.getWebPage deleted file mode 100644 index 35ea89af78..0000000000 --- a/data/corefork.telegram.org/method/messages.getWebPage +++ /dev/null @@ -1,177 +0,0 @@ - - - - - messages.getWebPage - - - - - - - - - - - - - -
- -
-
-
- -

messages.getWebPage

- -

Get instant view page

-

- -
-
webPageEmpty#eb1477e8 id:long = WebPage;
-webPagePending#c586da1c id:long date:int = WebPage;
-webPage#e89c45b2 flags:# id:long url:string display_url:string hash:int type:flags.0?string site_name:flags.1?string title:flags.2?string description:flags.3?string photo:flags.4?Photo embed_url:flags.5?string embed_type:flags.5?string embed_width:flags.6?int embed_height:flags.6?int duration:flags.7?int author:flags.8?string document:flags.9?Document cached_page:flags.10?Page attributes:flags.12?Vector<WebPageAttribute> = WebPage;
-webPageNotModified#7311ca11 flags:# cached_page_views:flags.0?int = WebPage;
----functions---
-messages.getWebPage#32ca8f91 url:string hash:int = WebPage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
urlstringURL of IV page to fetch
hashintHash for pagination, for more info click here
-

Result

-

WebPage

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400WC_CONVERT_URL_INVALIDWC convert URL invalid.
-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.getWebPagePreview b/data/corefork.telegram.org/method/messages.getWebPagePreview deleted file mode 100644 index e5860c23e9..0000000000 --- a/data/corefork.telegram.org/method/messages.getWebPagePreview +++ /dev/null @@ -1,191 +0,0 @@ - - - - - messages.getWebPagePreview - - - - - - - - - - - - - -
- -
-
-
- -

messages.getWebPagePreview

- -

Get preview of webpage

-

- -
-
messageMediaEmpty#3ded6320 = MessageMedia;
-messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;
-messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;
-messageMediaContact#70322949 phone_number:string first_name:string last_name:string vcard:string user_id:long = MessageMedia;
-messageMediaUnsupported#9f84f49e = MessageMedia;
-messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;
-messageMediaWebPage#a32dd600 webpage:WebPage = MessageMedia;
-messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;
-messageMediaGame#fdb19008 game:Game = MessageMedia;
-messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
-messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;
-messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
-messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;
----functions---
-messages.getWebPagePreview#8b68b0cc flags:# message:string entities:flags.3?Vector<MessageEntity> = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
messagestringMessage from which to extract the preview
entitiesflags.3?Vector<MessageEntity>Message entities for styled text
-

Result

-

MessageMedia

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_EMPTYThe provided message is empty.
-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.hidePeerSettingsBar b/data/corefork.telegram.org/method/messages.hidePeerSettingsBar deleted file mode 100644 index 9503e8e70d..0000000000 --- a/data/corefork.telegram.org/method/messages.hidePeerSettingsBar +++ /dev/null @@ -1,153 +0,0 @@ - - - - - messages.hidePeerSettingsBar - - - - - - - - - - - - - -
- -
-
-
- -

messages.hidePeerSettingsBar

- -

Should be called after the user hides the report spam/add as contact bar of a new chat, effectively prevents the user from executing the actions specified in the peer's settings.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.hidePeerSettingsBar#4facb138 peer:InputPeer = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
-

Result

-

Bool

-

Related pages

-

peerSettings

-

Peer settings

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.importChatInvite b/data/corefork.telegram.org/method/messages.importChatInvite deleted file mode 100644 index 34ba8bc87f..0000000000 --- a/data/corefork.telegram.org/method/messages.importChatInvite +++ /dev/null @@ -1,227 +0,0 @@ - - - - - messages.importChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

messages.importChatInvite

- -

Import a chat invite and join a private chat/supergroup/channel

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.importChatInvite#6c50051c hash:string = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
hashstringhash from t.me/joinchat/hash
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNELS_TOO_MUCHYou have joined too many channels/supergroups.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_INVALIDInvalid chat.
400INVITE_HASH_EMPTYThe invite hash is empty.
400INVITE_HASH_EXPIREDThe invite link has expired.
400INVITE_HASH_INVALIDThe invite hash is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USERS_TOO_MUCHThe maximum number of users has been exceeded (to create a chat, for example).
400USER_ALREADY_PARTICIPANTThe user is already in the group.
400USER_CHANNELS_TOO_MUCHOne of the users you tried to add is already in too many channels/supergroups.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.installStickerSet b/data/corefork.telegram.org/method/messages.installStickerSet deleted file mode 100644 index b4ebbd9baf..0000000000 --- a/data/corefork.telegram.org/method/messages.installStickerSet +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.installStickerSet - - - - - - - - - - - - - -
- -
-
-
- -

messages.installStickerSet

- -

Install a stickerset

-

- -
-
messages.stickerSetInstallResultSuccess#38641628 = messages.StickerSetInstallResult;
-messages.stickerSetInstallResultArchive#35e410a8 sets:Vector<StickerSetCovered> = messages.StickerSetInstallResult;
----functions---
-messages.installStickerSet#c78fe460 stickerset:InputStickerSet archived:Bool = messages.StickerSetInstallResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
stickersetInputStickerSetStickerset to install
archivedBoolWhether to archive stickerset
-

Result

-

messages.StickerSetInstallResult

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400STICKERSET_INVALIDThe provided sticker set is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.markDialogUnread b/data/corefork.telegram.org/method/messages.markDialogUnread deleted file mode 100644 index 1bda8ae4a8..0000000000 --- a/data/corefork.telegram.org/method/messages.markDialogUnread +++ /dev/null @@ -1,160 +0,0 @@ - - - - - messages.markDialogUnread - - - - - - - - - - - - - -
- -
-
-
- -

messages.markDialogUnread

- -

Manually mark dialog as unread

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.markDialogUnread#c286d98f flags:# unread:flags.0?true peer:InputDialogPeer = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
unreadflags.0?trueMark as unread/read
peerInputDialogPeerDialog
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.migrateChat b/data/corefork.telegram.org/method/messages.migrateChat deleted file mode 100644 index a83baced49..0000000000 --- a/data/corefork.telegram.org/method/messages.migrateChat +++ /dev/null @@ -1,190 +0,0 @@ - - - - - messages.migrateChat - - - - - - - - - - - - - -
- -
-
-
- -

messages.migrateChat

- -

Turn a legacy group into a supergroup

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.migrateChat#a2875319 chat_id:long = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
chat_idlongLegacy group to migrate
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNELS_TOO_MUCHYou have joined too many channels/supergroups.
403CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.readDiscussion b/data/corefork.telegram.org/method/messages.readDiscussion deleted file mode 100644 index 294e434025..0000000000 --- a/data/corefork.telegram.org/method/messages.readDiscussion +++ /dev/null @@ -1,180 +0,0 @@ - - - - - messages.readDiscussion - - - - - - - - - - - - - -
- -
-
-
- -

messages.readDiscussion

- -

Mark a thread as read

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.readDiscussion#f731a9f4 peer:InputPeer msg_id:int read_max_id:int = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerGroup ID
msg_idintID of message that started the thread
read_max_idintID up to which thread messages were read
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.readEncryptedHistory b/data/corefork.telegram.org/method/messages.readEncryptedHistory deleted file mode 100644 index f87d1f060f..0000000000 --- a/data/corefork.telegram.org/method/messages.readEncryptedHistory +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.readEncryptedHistory - - - - - - - - - - - - - -
- -
-
-
- -

messages.readEncryptedHistory

- -

Marks message history within a secret chat as read.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.readEncryptedHistory#7f4b690a peer:InputEncryptedChat max_date:int = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputEncryptedChatSecret chat ID
max_dateintMaximum date value for received messages in history
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400MSG_WAIT_FAILEDA waiting call returned an error.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.readFeaturedStickers b/data/corefork.telegram.org/method/messages.readFeaturedStickers deleted file mode 100644 index 8a4bee52ca..0000000000 --- a/data/corefork.telegram.org/method/messages.readFeaturedStickers +++ /dev/null @@ -1,150 +0,0 @@ - - - - - messages.readFeaturedStickers - - - - - - - - - - - - - -
- -
-
-
- -

messages.readFeaturedStickers

- -

Mark new featured stickers as read

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.readFeaturedStickers#5b118126 id:Vector<long> = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idVector<long>IDs of stickersets to mark as read
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.readHistory b/data/corefork.telegram.org/method/messages.readHistory deleted file mode 100644 index a8d5c4bef1..0000000000 --- a/data/corefork.telegram.org/method/messages.readHistory +++ /dev/null @@ -1,186 +0,0 @@ - - - - - messages.readHistory - - - - - - - - - - - - - -
- -
-
-
- -

messages.readHistory

- -

Marks message history as read.

-

- -
-
messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;
----functions---
-messages.readHistory#e306d3a peer:InputPeer max_id:int = messages.AffectedMessages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerTarget user or group
max_idintIf a positive value is passed, only messages with identifiers less or equal than the given one will be read
-

Result

-

messages.AffectedHistory

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.readMentions b/data/corefork.telegram.org/method/messages.readMentions deleted file mode 100644 index d1f2520fd3..0000000000 --- a/data/corefork.telegram.org/method/messages.readMentions +++ /dev/null @@ -1,181 +0,0 @@ - - - - - messages.readMentions - - - - - - - - - - - - - -
- -
-
-
- -

messages.readMentions

- -

Mark mentions as read

-

- -
-
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
----functions---
-messages.readMentions#f0189d3 peer:InputPeer = messages.AffectedHistory;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerDialog
-

Result

-

messages.AffectedHistory

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.readMessageContents b/data/corefork.telegram.org/method/messages.readMessageContents deleted file mode 100644 index 5e935c4684..0000000000 --- a/data/corefork.telegram.org/method/messages.readMessageContents +++ /dev/null @@ -1,149 +0,0 @@ - - - - - messages.readMessageContents - - - - - - - - - - - - - -
- -
-
-
- -

messages.readMessageContents

- -

Notifies the sender about the recipient having listened a voice message or watched a video.

-

- -
-
messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;
----functions---
-messages.readMessageContents#36a73f77 id:Vector<int> = messages.AffectedMessages;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idVector<int>Message ID list
-

Result

-

Returns a list of listened\watched messages as Vector<int>.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.receivedMessages b/data/corefork.telegram.org/method/messages.receivedMessages deleted file mode 100644 index 8a5a2d137f..0000000000 --- a/data/corefork.telegram.org/method/messages.receivedMessages +++ /dev/null @@ -1,148 +0,0 @@ - - - - - messages.receivedMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.receivedMessages

- -

Confirms receipt of messages by a client, cancels PUSH-notification sending.

-

- -
-
---functions---
-messages.receivedMessages#5a954c0 max_id:int = Vector<ReceivedNotifyMessage>;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
max_idintMaximum message ID available in a client.
-

Result

-

The method returns the list of message IDs, for which PUSH-notifications were cancelled.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.receivedQueue b/data/corefork.telegram.org/method/messages.receivedQueue deleted file mode 100644 index 2736a80725..0000000000 --- a/data/corefork.telegram.org/method/messages.receivedQueue +++ /dev/null @@ -1,170 +0,0 @@ - - - - - messages.receivedQueue - - - - - - - - - - - - - -
- -
-
-
- -

messages.receivedQueue

- -

Confirms receipt of messages in a secret chat by client, cancels push notifications.

-

- -
-
---functions---
-messages.receivedQueue#55a5bb66 max_qts:int = Vector<long>;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
max_qtsintMaximum qts value available at the client
-

Result

-

Method returns a list of random_ids of messages for which push notifications were cancelled in Vector<long>.

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MAX_QTS_INVALIDThe specified max_qts is invalid.
400MSG_WAIT_FAILEDA waiting call returned an error.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.reorderPinnedDialogs b/data/corefork.telegram.org/method/messages.reorderPinnedDialogs deleted file mode 100644 index 5845312c2e..0000000000 --- a/data/corefork.telegram.org/method/messages.reorderPinnedDialogs +++ /dev/null @@ -1,185 +0,0 @@ - - - - - messages.reorderPinnedDialogs - - - - - - - - - - - - - -
- -
-
-
- -

messages.reorderPinnedDialogs

- -

Reorder pinned dialogs

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.reorderPinnedDialogs#3b1adf37 flags:# force:flags.0?true folder_id:int order:Vector<InputDialogPeer> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
forceflags.0?trueIf set, dialogs pinned server-side but not present in the order field will be unpinned.
folder_idintPeer folder ID, for more info click here
orderVector<InputDialogPeer>New dialog order
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.reorderStickerSets b/data/corefork.telegram.org/method/messages.reorderStickerSets deleted file mode 100644 index 7f80b04b5d..0000000000 --- a/data/corefork.telegram.org/method/messages.reorderStickerSets +++ /dev/null @@ -1,160 +0,0 @@ - - - - - messages.reorderStickerSets - - - - - - - - - - - - - -
- -
-
-
- -

messages.reorderStickerSets

- -

Reorder installed stickersets

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.reorderStickerSets#78337739 flags:# masks:flags.0?true order:Vector<long> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
masksflags.0?trueReorder mask stickersets
orderVector<long>New stickerset order by stickerset IDs
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.report b/data/corefork.telegram.org/method/messages.report deleted file mode 100644 index 36b6213ce0..0000000000 --- a/data/corefork.telegram.org/method/messages.report +++ /dev/null @@ -1,187 +0,0 @@ - - - - - messages.report - - - - - - - - - - - - - -
- -
-
-
- -

messages.report

- -

Report a message in a chat for violation of telegram's Terms of Service

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.report#8953ab4e peer:InputPeer id:Vector<int> reason:ReportReason message:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
idVector<int>IDs of messages to report
reasonReportReasonWhy are these messages being reported
messagestringComment for report moderation
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.reportSpam b/data/corefork.telegram.org/method/messages.reportSpam deleted file mode 100644 index 24f4af3571..0000000000 --- a/data/corefork.telegram.org/method/messages.reportSpam +++ /dev/null @@ -1,180 +0,0 @@ - - - - - messages.reportSpam - - - - - - - - - - - - - -
- -
-
-
- -

messages.reportSpam

- -

Report a new incoming chat for spam, if the peer settings of the chat allow us to do that

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.reportSpam#cf1592db peer:InputPeer = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer to report
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

peerSettings

-

Peer settings

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.requestUrlAuth b/data/corefork.telegram.org/method/messages.requestUrlAuth deleted file mode 100644 index a3a893318a..0000000000 --- a/data/corefork.telegram.org/method/messages.requestUrlAuth +++ /dev/null @@ -1,174 +0,0 @@ - - - - - messages.requestUrlAuth - - - - - - - - - - - - - -
- -
-
-
- -

messages.requestUrlAuth

- -

Get more info about a Seamless Telegram Login authorization request, for more info click here »

-

- -
-
urlAuthResultRequest#92d33a0e flags:# request_write_access:flags.0?true bot:User domain:string = UrlAuthResult;
-urlAuthResultAccepted#8f8c0e4e url:string = UrlAuthResult;
-urlAuthResultDefault#a9d6db1f = UrlAuthResult;
----functions---
-messages.requestUrlAuth#198fb446 flags:# peer:flags.1?InputPeer msg_id:flags.1?int button_id:flags.1?int url:flags.2?string = UrlAuthResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
peerflags.1?InputPeerPeer where the message is located
msg_idflags.1?intThe message
button_idflags.1?intThe ID of the button with the authorization request
urlflags.2?stringURL used for link URL authorization, click here for more info »
-

Result

-

UrlAuthResult

-

Related pages

-

Seamless Telegram Login

-

Handle Seamless Telegram Login URL authorization requests.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.saveDraft b/data/corefork.telegram.org/method/messages.saveDraft deleted file mode 100644 index 7d2f47f3f9..0000000000 --- a/data/corefork.telegram.org/method/messages.saveDraft +++ /dev/null @@ -1,202 +0,0 @@ - - - - - messages.saveDraft - - - - - - - - - - - - - -
- -
-
-
- -

messages.saveDraft

- -

Save a message draft associated to a chat.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.saveDraft#bc39e14b flags:# no_webpage:flags.1?true reply_to_msg_id:flags.0?int peer:InputPeer message:string entities:flags.3?Vector<MessageEntity> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.1?trueDisable generation of the webpage preview
reply_to_msg_idflags.0?intMessage ID the message should reply to
peerInputPeerDestination of the message that should be sent
messagestringThe draft
entitiesflags.3?Vector<MessageEntity>Message entities for styled text
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

-

Message drafts

-

How to handle message drafts

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.saveGif b/data/corefork.telegram.org/method/messages.saveGif deleted file mode 100644 index a4abe9140b..0000000000 --- a/data/corefork.telegram.org/method/messages.saveGif +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.saveGif - - - - - - - - - - - - - -
- -
-
-
- -

messages.saveGif

- -

Add GIF to saved gifs list

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.saveGif#327a30cb id:InputDocument unsave:Bool = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idInputDocumentGIF to save
unsaveBoolWhether to remove GIF from saved gifs list
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400GIF_ID_INVALIDThe provided GIF ID is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.saveRecentSticker b/data/corefork.telegram.org/method/messages.saveRecentSticker deleted file mode 100644 index 7dc1e7a739..0000000000 --- a/data/corefork.telegram.org/method/messages.saveRecentSticker +++ /dev/null @@ -1,182 +0,0 @@ - - - - - messages.saveRecentSticker - - - - - - - - - - - - - -
- -
-
-
- -

messages.saveRecentSticker

- -

Add/remove sticker from recent stickers list

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.saveRecentSticker#392718f8 flags:# attached:flags.0?true id:InputDocument unsave:Bool = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
attachedflags.0?trueWhether to add/remove stickers recently attached to photo or video files
idInputDocumentSticker
unsaveBoolWhether to save or unsave the sticker
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400STICKER_ID_INVALIDThe provided sticker ID is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.search b/data/corefork.telegram.org/method/messages.search deleted file mode 100644 index 007c86b21f..0000000000 --- a/data/corefork.telegram.org/method/messages.search +++ /dev/null @@ -1,291 +0,0 @@ - - - - - messages.search - - - - - - - - - - - - - -
- -
-
-
- -

messages.search

- -

Gets back found messages

-

- -
-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
----functions---
-messages.search#a0fda762 flags:# peer:InputPeer q:string from_id:flags.0?InputPeer top_msg_id:flags.1?int filter:MessagesFilter min_date:int max_date:int offset_id:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerUser or chat, histories with which are searched, or (inputPeerEmpty) constructor for global search
qstringText search request
from_idflags.0?InputPeerOnly return messages sent by the specified user ID
top_msg_idflags.1?intThread ID
filterMessagesFilterFilter to return only specified message types
min_dateintIf a positive value was transferred, only messages with a sending date bigger than the transferred one will be returned
max_dateintIf a positive value was transferred, only messages with a sending date smaller than the transferred one will be returned
offset_idintOnly return messages starting from the specified message ID
add_offsetintAdditional offset
limitintNumber of results to return
max_idintMaximum message ID to return
min_idintMinimum message ID to return
hashlongHash
-

Result

-

messages.Messages

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400FROM_PEER_INVALIDThe specified from_id is invalid.
400INPUT_FILTER_INVALIDThe specified filter is invalid.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PEER_ID_NOT_SUPPORTEDThe provided peer ID is not supported.
400SEARCH_QUERY_EMPTYThe search query is empty.
400USER_ID_INVALIDThe provided user ID is invalid.
-

Related pages

-

inputPeerEmpty

-

An empty constructor, no user or chat is defined.

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.searchGifs b/data/corefork.telegram.org/method/messages.searchGifs deleted file mode 100644 index ece679afc7..0000000000 --- a/data/corefork.telegram.org/method/messages.searchGifs +++ /dev/null @@ -1,177 +0,0 @@ - - - - - messages.searchGifs - - - - - - - - - - - - - -
- -
-
-
- -

messages.searchGifs

- -

Search for GIFs

-

- -
-
 Method schema is available as of layer 114. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
qstringText query
offsetintOffset for pagination »
-

Result

-

messages.FoundGifs

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400METHOD_INVALIDThe specified method is invalid.
400SEARCH_QUERY_EMPTYThe search query is empty.
-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.searchGlobal b/data/corefork.telegram.org/method/messages.searchGlobal deleted file mode 100644 index dee64135da..0000000000 --- a/data/corefork.telegram.org/method/messages.searchGlobal +++ /dev/null @@ -1,226 +0,0 @@ - - - - - messages.searchGlobal - - - - - - - - - - - - - -
- -
-
-
- -

messages.searchGlobal

- -

Search for messages and peers globally

-

- -
-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
----functions---
-messages.searchGlobal#4bc6589a flags:# folder_id:flags.0?int q:string filter:MessagesFilter min_date:int max_date:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
folder_idflags.0?intPeer folder ID, for more info click here
qstringQuery
filterMessagesFilterGlobal search filter
min_dateintIf a positive value was specified, the method will return only messages with date bigger than min_date
max_dateintIf a positive value was transferred, the method will return only messages with date smaller than max_date
offset_rateintInitially 0, then set to the next_rate parameter of messages.messagesSlice
offset_peerInputPeerOffsets for pagination, for more info click here
offset_idintOffsets for pagination, for more info click here
limitintOffsets for pagination, for more info click here
-

Result

-

messages.Messages

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400FOLDER_ID_INVALIDInvalid folder ID.
400SEARCH_QUERY_EMPTYThe search query is empty.
-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

-

messages.messagesSlice

-

Incomplete list of messages and auxiliary data.

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.searchStickerSets b/data/corefork.telegram.org/method/messages.searchStickerSets deleted file mode 100644 index 8afd50498e..0000000000 --- a/data/corefork.telegram.org/method/messages.searchStickerSets +++ /dev/null @@ -1,168 +0,0 @@ - - - - - messages.searchStickerSets - - - - - - - - - - - - - -
- -
-
-
- -

messages.searchStickerSets

- -

Search for stickersets

-

- -
-
messages.foundStickerSetsNotModified#d54b65d = messages.FoundStickerSets;
-messages.foundStickerSets#8af09dd2 hash:long sets:Vector<StickerSetCovered> = messages.FoundStickerSets;
----functions---
-messages.searchStickerSets#35705b8a flags:# exclude_featured:flags.0?true q:string hash:long = messages.FoundStickerSets;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
exclude_featuredflags.0?trueExclude featured stickersets from results
qstringQuery string
hashlongHash for pagination, for more info click here
-

Result

-

messages.FoundStickerSets

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.sendBroadcast b/data/corefork.telegram.org/method/messages.sendBroadcast deleted file mode 100644 index 0f24999788..0000000000 --- a/data/corefork.telegram.org/method/messages.sendBroadcast +++ /dev/null @@ -1,145 +0,0 @@ - - - - - messages.sendBroadcast - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendBroadcast

- -

Sends multiple messages to contacts.

-

{schema}

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
contactsVector<InputUser>List of user ID to whom a message will be sent
messagestringMessage text
mediaInputMediaMessage media-contents
-

Result

-

messages.StatedMessages

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.sendEncrypted b/data/corefork.telegram.org/method/messages.sendEncrypted deleted file mode 100644 index 1be3fbfa2e..0000000000 --- a/data/corefork.telegram.org/method/messages.sendEncrypted +++ /dev/null @@ -1,210 +0,0 @@ - - - - - messages.sendEncrypted - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendEncrypted

- -

Sends a text message to a secret chat.

-

- -
-
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;
-messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;
----functions---
-messages.sendEncrypted#44fa7a15 flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.0?trueSend encrypted message without a notification
peerInputEncryptedChatSecret chat ID
random_idlongUnique client message ID, necessary to avoid message resending
databytesTL-serialization of DecryptedMessage type, encrypted with a key that was created during chat initialization
-

Result

-

messages.SentEncryptedMessage

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
400DATA_INVALIDEncrypted data invalid.
400ENCRYPTION_DECLINEDThe secret chat was declined.
400MSG_WAIT_FAILEDA waiting call returned an error.
403USER_IS_BLOCKEDYou were blocked by this user.
-

Related pages

-

DecryptedMessage

-

Object describes the contents of an encrypted message.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.sendEncryptedFile b/data/corefork.telegram.org/method/messages.sendEncryptedFile deleted file mode 100644 index a2c3797ca4..0000000000 --- a/data/corefork.telegram.org/method/messages.sendEncryptedFile +++ /dev/null @@ -1,215 +0,0 @@ - - - - - messages.sendEncryptedFile - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendEncryptedFile

- -

Sends a message with a file attachment to a secret chat

-

- -
-
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;
-messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;
----functions---
-messages.sendEncryptedFile#5559481d flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes file:InputEncryptedFile = messages.SentEncryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.0?trueWhether to send the file without triggering a notification
peerInputEncryptedChatSecret chat ID
random_idlongUnique client message ID necessary to prevent message resending
databytesTL-serialization of DecryptedMessage type, encrypted with a key generated during chat initialization
fileInputEncryptedFileFile attachment for the secret chat
-

Result

-

messages.SentEncryptedMessage

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400DATA_TOO_LONGData too long.
400ENCRYPTION_DECLINEDThe secret chat was declined.
400FILE_EMTPYAn empty file was provided.
400MD5_CHECKSUM_INVALIDThe MD5 checksums do not match.
400MSG_WAIT_FAILEDA waiting call returned an error.
-

Related pages

-

DecryptedMessage

-

Object describes the contents of an encrypted message.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.sendEncryptedService b/data/corefork.telegram.org/method/messages.sendEncryptedService deleted file mode 100644 index aba6a47d0c..0000000000 --- a/data/corefork.telegram.org/method/messages.sendEncryptedService +++ /dev/null @@ -1,205 +0,0 @@ - - - - - messages.sendEncryptedService - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendEncryptedService

- -

Sends a service message to a secret chat.

-

- -
-
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;
-messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;
----functions---
-messages.sendEncryptedService#32d439a4 peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputEncryptedChatSecret chat ID
random_idlongUnique client message ID required to prevent message resending
databytesTL-serialization of DecryptedMessage type, encrypted with a key generated during chat initialization
-

Result

-

messages.SentEncryptedMessage

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400DATA_INVALIDEncrypted data invalid.
400ENCRYPTION_DECLINEDThe secret chat was declined.
400ENCRYPTION_ID_INVALIDThe provided secret chat ID is invalid.
400MSG_WAIT_FAILEDA waiting call returned an error.
403USER_DELETEDYou can't send this secret message because the other participant deleted their account.
403USER_IS_BLOCKEDYou were blocked by this user.
-

Related pages

-

DecryptedMessage

-

Object describes the contents of an encrypted message.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.sendInlineBotResult b/data/corefork.telegram.org/method/messages.sendInlineBotResult deleted file mode 100644 index 992f798eb6..0000000000 --- a/data/corefork.telegram.org/method/messages.sendInlineBotResult +++ /dev/null @@ -1,344 +0,0 @@ - - - - - messages.sendInlineBotResult - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendInlineBotResult

- -

Send a result obtained using messages.getInlineBotResults.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.sendInlineBotResult#220815b0 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true hide_via:flags.11?true peer:InputPeer reply_to_msg_id:flags.0?int random_id:long query_id:long id:string schedule_date:flags.10?int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.5?trueWhether to send the message silently (no notification will be triggered on the other client)
backgroundflags.6?trueWhether to send the message in background
clear_draftflags.7?trueWhether to clear the draft
hide_viaflags.11?trueWhether to hide the via @botname in the resulting message (only for bot usernames encountered in the config)
peerInputPeerDestination
reply_to_msg_idflags.0?intID of the message this message should reply to
random_idlongRandom ID to avoid resending the same query
query_idlongQuery ID from messages.getInlineBotResults
idstringResult ID from messages.getInlineBotResults
schedule_dateflags.10?intScheduled message date for scheduled messages
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_RESTRICTEDYou can't send messages in this chat, you were restricted.
403CHAT_SEND_GAME_FORBIDDENYou can't send a game to this chat.
403CHAT_SEND_GIFS_FORBIDDENYou can't send gifs in this chat.
403CHAT_SEND_INLINE_FORBIDDENYou can't send inline messages in this group.
403CHAT_SEND_MEDIA_FORBIDDENYou can't send media in this chat.
403CHAT_SEND_STICKERS_FORBIDDENYou can't send stickers in this chat.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400INLINE_RESULT_EXPIREDThe inline query expired.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MEDIA_EMPTYThe provided media object is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400QUERY_ID_EMPTYThe query ID is empty.
400RESULT_ID_EMPTYResult ID empty.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
420SLOWMODE_WAIT_XSlowmode is enabled in this chat: you must wait for the specified number of seconds before sending another message to the chat.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400WEBPAGE_CURL_FAILEDFailure while fetching the webpage with cURL.
400WEBPAGE_MEDIA_EMPTYWebpage media empty.
400YOU_BLOCKED_USERYou blocked this user.
-

Related pages

-

Message drafts

-

How to handle message drafts

-

config

-

Current configuration

-

messages.getInlineBotResults

-

Query an inline bot

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.sendMedia b/data/corefork.telegram.org/method/messages.sendMedia deleted file mode 100644 index 051920c59e..0000000000 --- a/data/corefork.telegram.org/method/messages.sendMedia +++ /dev/null @@ -1,518 +0,0 @@ - - - - - messages.sendMedia - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendMedia

- -

Send a media

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.5?trueSend message silently (no notification should be triggered)
backgroundflags.6?trueSend message in background
clear_draftflags.7?trueClear the draft
peerInputPeerDestination
reply_to_msg_idflags.0?intMessage ID to which this message should reply to
mediaInputMediaAttached media
messagestringCaption
random_idlongRandom ID to avoid resending the same message
reply_markupflags.2?ReplyMarkupReply markup for bot keyboards
entitiesflags.3?Vector<MessageEntity>Message entities for styled text
schedule_dateflags.10?intScheduled message date for scheduled messages
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOT_PAYMENTS_DISABLEDPlease enable bot payments in botfather before calling this method.
400BOT_POLLS_DISABLED 
400BROADCAST_PUBLIC_VOTERS_FORBIDDENYou can't forward polls with public voters.
400BUTTON_DATA_INVALIDThe data of one or more of the buttons you provided is invalid.
400BUTTON_TYPE_INVALIDThe type of one or more of the buttons you provided is invalid.
400BUTTON_URL_INVALIDButton URL invalid.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_RESTRICTEDYou can't send messages in this chat, you were restricted.
403CHAT_SEND_GIFS_FORBIDDENYou can't send gifs in this chat.
403CHAT_SEND_MEDIA_FORBIDDENYou can't send media in this chat.
403CHAT_SEND_POLL_FORBIDDENYou can't send polls in this chat.
403CHAT_SEND_STICKERS_FORBIDDENYou can't send stickers in this chat.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400CURRENCY_TOTAL_AMOUNT_INVALIDThe total amount of all prices is invalid.
400EMOTICON_INVALIDThe specified emoji is invalid.
400EXTERNAL_URL_INVALIDExternal URL invalid.
400FILE_PARTS_INVALIDThe number of file parts is invalid.
400FILE_PART_LENGTH_INVALIDThe length of a file part is invalid.
400FILE_REFERENCE_EMPTYAn empty file reference was specified.
400FILE_REFERENCE_EXPIREDFile reference expired, it must be refetched as described in https://core.telegram.org/api/file_reference.
400GAME_BOT_INVALIDBots can't send another bot's game.
400IMAGE_PROCESS_FAILEDFailure while processing image.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MD5_CHECKSUM_INVALIDThe MD5 checksums do not match.
400MEDIA_CAPTION_TOO_LONGThe caption is too long.
400MEDIA_EMPTYThe provided media object is invalid.
400MEDIA_INVALIDMedia invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PAYMENT_PROVIDER_INVALIDThe specified payment provider is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PHOTO_EXT_INVALIDThe extension of the photo is invalid.
400PHOTO_INVALID_DIMENSIONSThe photo dimensions are invalid.
400PHOTO_SAVE_FILE_INVALIDInternal issues, try again later.
400POLL_ANSWERS_INVALIDInvalid poll answers were provided.
400POLL_ANSWER_INVALIDOne of the poll answers is not acceptable.
400POLL_OPTION_DUPLICATEDuplicate poll options provided.
400POLL_OPTION_INVALIDInvalid poll option provided.
400POLL_QUESTION_INVALIDOne of the poll questions is not acceptable.
400QUIZ_CORRECT_ANSWERS_EMPTYNo correct quiz answer was specified.
400QUIZ_CORRECT_ANSWERS_TOO_MUCHYou specified too many correct answers in a quiz, quizes can only have one right answer!
400QUIZ_CORRECT_ANSWER_INVALIDAn invalid value was provided to the correct_answers field.
400QUIZ_MULTIPLE_INVALIDQuizes can't have the multiple_choice flag set!
400REPLY_MARKUP_BUY_EMPTYReply markup for buy button empty.
400REPLY_MARKUP_INVALIDThe provided reply markup is invalid.
400SCHEDULE_BOT_NOT_ALLOWEDBots cannot schedule messages.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
420SLOWMODE_WAIT_XSlowmode is enabled in this chat: you must wait for the specified number of seconds before sending another message to the chat.
400TTL_MEDIA_INVALIDInvalid media Time To Live was provided.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400USER_IS_BLOCKEDYou were blocked by this user.
400USER_IS_BOTBots can't send messages to other bots.
400VIDEO_CONTENT_TYPE_INVALIDThe video's content type is invalid.
400WEBPAGE_CURL_FAILEDFailure while fetching the webpage with cURL.
400WEBPAGE_MEDIA_EMPTYWebpage media empty.
400YOU_BLOCKED_USERYou blocked this user.
-

Bots can use this method

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

-

Scheduled messages

-

Telegram allows scheduling messages

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.sendMessage b/data/corefork.telegram.org/method/messages.sendMessage deleted file mode 100644 index b0a3538b5e..0000000000 --- a/data/corefork.telegram.org/method/messages.sendMessage +++ /dev/null @@ -1,398 +0,0 @@ - - - - - messages.sendMessage - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendMessage

- -

Sends a message to a chat

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.sendMessage#520c3870 flags:# no_webpage:flags.1?true silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
no_webpageflags.1?trueSet this flag to disable generation of the webpage preview
silentflags.5?trueSend this message silently (no notifications for the receivers)
backgroundflags.6?trueSend this message as background message
clear_draftflags.7?trueClear the draft field
peerInputPeerThe destination where the message will be sent
reply_to_msg_idflags.0?intThe message ID to which this message will reply to
messagestringThe message
random_idlongUnique client message ID required to prevent message resending
reply_markupflags.2?ReplyMarkupReply markup for sending bot buttons
entitiesflags.3?Vector<MessageEntity>Message entities for sending styled text
schedule_dateflags.10?intScheduled message date for scheduled messages
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400BOT_DOMAIN_INVALIDBot domain invalid.
400BOT_INVALIDThis is not a valid bot.
400BUTTON_DATA_INVALIDThe data of one or more of the buttons you provided is invalid.
400BUTTON_TYPE_INVALIDThe type of one or more of the buttons you provided is invalid.
400BUTTON_URL_INVALIDButton URL invalid.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
400CHAT_RESTRICTEDYou can't send messages in this chat, you were restricted.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400ENCRYPTION_DECLINEDThe secret chat was declined.
400ENTITIES_TOO_LONGYou provided too many styled message entities.
400ENTITY_MENTION_USER_INVALIDYou mentioned an invalid user.
400FROM_MESSAGE_BOT_DISABLEDBots can't use fromMessage min constructors.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MESSAGE_EMPTYThe provided message is empty.
400MESSAGE_TOO_LONGThe provided message is too long.
400MSG_ID_INVALIDProvided reply_to_msg_id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PINNED_DIALOGS_TOO_MUCHToo many pinned dialogs.
400POLL_OPTION_INVALIDInvalid poll option provided.
400REPLY_MARKUP_INVALIDThe provided reply markup is invalid.
400REPLY_MARKUP_TOO_LONGThe specified reply_markup is too long.
400SCHEDULE_BOT_NOT_ALLOWEDBots cannot schedule messages.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_STATUS_PRIVATECan't schedule until user is online, if the user's last seen timestamp is hidden by their privacy settings.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
420SLOWMODE_WAIT_XSlowmode is enabled in this chat: you must wait for the specified number of seconds before sending another message to the chat.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400USER_IS_BLOCKEDYou were blocked by this user.
400USER_IS_BOTBots can't send messages to other bots.
400YOU_BLOCKED_USERYou blocked this user.
-

Bots can use this method

-

Related pages

-

Styled text with message entities

-

How to create styled text with message entities

-

Scheduled messages

-

Telegram allows scheduling messages

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.sendMultiMedia b/data/corefork.telegram.org/method/messages.sendMultiMedia deleted file mode 100644 index c5fab9b6ea..0000000000 --- a/data/corefork.telegram.org/method/messages.sendMultiMedia +++ /dev/null @@ -1,263 +0,0 @@ - - - - - messages.sendMultiMedia - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendMultiMedia

- -

Send an album or grouped media

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.sendMultiMedia#cc0110cb flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int multi_media:Vector<InputSingleMedia> schedule_date:flags.10?int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.5?trueWhether to send the album silently (no notification triggered)
backgroundflags.6?trueSend in background?
clear_draftflags.7?trueWhether to clear drafts
peerInputPeerThe destination chat
reply_to_msg_idflags.0?intThe message to reply to
multi_mediaVector<InputSingleMedia>The medias to send
schedule_dateflags.10?intScheduled message date for scheduled messages
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400MEDIA_CAPTION_TOO_LONGThe caption is too long.
400MEDIA_EMPTYThe provided media object is invalid.
400MEDIA_INVALIDMedia invalid.
400MULTI_MEDIA_TOO_LONGToo many media files for album.
400PEER_ID_INVALIDThe provided peer id is invalid.
400RANDOM_ID_EMPTYRandom ID empty.
400SCHEDULE_DATE_TOO_LATEYou can't schedule a message this far in the future.
400SCHEDULE_TOO_MUCHThere are too many scheduled messages.
420SLOWMODE_WAIT_XSlowmode is enabled in this chat: wait X seconds before sending another message to this chat.
-

Bots can use this method

-

Related pages

-

Message drafts

-

How to handle message drafts

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.sendReaction b/data/corefork.telegram.org/method/messages.sendReaction deleted file mode 100644 index 5e50671580..0000000000 --- a/data/corefork.telegram.org/method/messages.sendReaction +++ /dev/null @@ -1,185 +0,0 @@ - - - - - messages.sendReaction - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendReaction

- -

Send reaction to message

-

- -
-
 Method schema is available as of layer 136. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerPeer
msg_idintMessage ID to react to
reactionflags.0?stringReaction (a UTF8 emoji)
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400REACTION_EMPTYEmpty reaction provided.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.sendScheduledMessages b/data/corefork.telegram.org/method/messages.sendScheduledMessages deleted file mode 100644 index f29f504d77..0000000000 --- a/data/corefork.telegram.org/method/messages.sendScheduledMessages +++ /dev/null @@ -1,182 +0,0 @@ - - - - - messages.sendScheduledMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendScheduledMessages

- -

Send scheduled messages right away

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.sendScheduledMessages#bd38850a peer:InputPeer id:Vector<int> = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPeer
idVector<int>Scheduled message IDs
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.sendScreenshotNotification b/data/corefork.telegram.org/method/messages.sendScreenshotNotification deleted file mode 100644 index fb009b5bfa..0000000000 --- a/data/corefork.telegram.org/method/messages.sendScreenshotNotification +++ /dev/null @@ -1,187 +0,0 @@ - - - - - messages.sendScreenshotNotification - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendScreenshotNotification

- -

Notify the other user in a private chat that a screenshot of the chat was taken

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.sendScreenshotNotification#c97df020 peer:InputPeer reply_to_msg_id:int random_id:long = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerOther user
reply_to_msg_idintID of message that was screenshotted, can be 0
random_idlongRandom ID to avoid message resending
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400PEER_ID_INVALIDThe provided peer id is invalid.
400YOU_BLOCKED_USERYou blocked this user.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.sendVote b/data/corefork.telegram.org/method/messages.sendVote deleted file mode 100644 index d1ae30b45a..0000000000 --- a/data/corefork.telegram.org/method/messages.sendVote +++ /dev/null @@ -1,220 +0,0 @@ - - - - - messages.sendVote - - - - - - - - - - - - - -
- -
-
-
- -

messages.sendVote

- -

Vote in a poll

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.sendVote#10ea6184 peer:InputPeer msg_id:int options:Vector<bytes> = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat where the poll was sent
msg_idintThe message ID of the poll
optionsVector<bytes>The options that were chosen
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400MESSAGE_POLL_CLOSEDPoll closed.
400OPTIONS_TOO_MUCHToo many options provided.
400OPTION_INVALIDInvalid option selected.
400PEER_ID_INVALIDThe provided peer id is invalid.
400REVOTE_NOT_ALLOWEDYou cannot change your vote.
-

Related pages

-

poll

-

Poll

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.setBotPrecheckoutResults b/data/corefork.telegram.org/method/messages.setBotPrecheckoutResults deleted file mode 100644 index 8f5fef059e..0000000000 --- a/data/corefork.telegram.org/method/messages.setBotPrecheckoutResults +++ /dev/null @@ -1,188 +0,0 @@ - - - - - messages.setBotPrecheckoutResults - - - - - - - - - - - - - -
- -
-
-
- -

messages.setBotPrecheckoutResults

- -

Once the user has confirmed their payment and shipping details, the bot receives an updateBotPrecheckoutQuery update.
-Use this method to respond to such pre-checkout queries.
-Note: Telegram must receive an answer within 10 seconds after the pre-checkout query was sent.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.setBotPrecheckoutResults#9c2dd95 flags:# success:flags.1?true query_id:long error:flags.0?string = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
successflags.1?trueSet this flag if everything is alright (goods are available, etc.) and the bot is ready to proceed with the order, otherwise do not set it, and set the error field, instead
query_idlongUnique identifier for the query to be answered
errorflags.0?stringRequired if the success isn't set. Error message in human readable form that explains the reason for failure to proceed with the checkout (e.g. "Sorry, somebody just bought the last of our amazing black T-shirts while you were busy filling out your payment details. Please choose a different color or garment!"). Telegram will display this message to the user.
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400ERROR_TEXT_EMPTYThe provided error message is empty.
-

Bots can use this method

-

Related pages

-

updateBotPrecheckoutQuery

-

This object contains information about an incoming pre-checkout query.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.setBotShippingResults b/data/corefork.telegram.org/method/messages.setBotShippingResults deleted file mode 100644 index ba98b839e6..0000000000 --- a/data/corefork.telegram.org/method/messages.setBotShippingResults +++ /dev/null @@ -1,186 +0,0 @@ - - - - - messages.setBotShippingResults - - - - - - - - - - - - - -
- -
-
-
- -

messages.setBotShippingResults

- -

If you sent an invoice requesting a shipping address and the parameter is_flexible was specified, the bot will receive an updateBotShippingQuery update. Use this method to reply to shipping queries.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.setBotShippingResults#e5f672fa flags:# query_id:long error:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
query_idlongUnique identifier for the query to be answered
errorflags.0?stringError message in human readable form that explains why it is impossible to complete the order (e.g. "Sorry, delivery to your desired address is unavailable'). Telegram will display this message to the user.
shipping_optionsflags.1?Vector<ShippingOption>A vector of available shipping options.
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400QUERY_ID_INVALIDThe query ID is invalid.
-

Bots can use this method

-

Related pages

-

updateBotShippingQuery

-

This object contains information about an incoming shipping query.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.setChatTheme b/data/corefork.telegram.org/method/messages.setChatTheme deleted file mode 100644 index 4c3b6c91fe..0000000000 --- a/data/corefork.telegram.org/method/messages.setChatTheme +++ /dev/null @@ -1,185 +0,0 @@ - - - - - messages.setChatTheme - - - - - - - - - - - - - -
- -
-
-
- -

messages.setChatTheme

- -

Change the chat theme of a certain chat

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.setChatTheme#e63be13f peer:InputPeer emoticon:string = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerPrivate chat where to change theme
emoticonstringEmoji, identifying a specific chat theme; a list of chat themes can be fetched using account.getChatThemes
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400EMOJI_INVALIDThe specified theme emoji is valid.
400EMOJI_NOT_MODIFIEDThe theme wasn't changed.
-

Related pages

-

account.getChatThemes

-

Get all available chat themes

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.setEncryptedTyping b/data/corefork.telegram.org/method/messages.setEncryptedTyping deleted file mode 100644 index 67060e3eec..0000000000 --- a/data/corefork.telegram.org/method/messages.setEncryptedTyping +++ /dev/null @@ -1,177 +0,0 @@ - - - - - messages.setEncryptedTyping - - - - - - - - - - - - - -
- -
-
-
- -

messages.setEncryptedTyping

- -

Send typing event by the current user to a secret chat.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.setEncryptedTyping#791451ed peer:InputEncryptedChat typing:Bool = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputEncryptedChatSecret chat ID
typingBoolTyping.
Possible values:
(boolTrue), if the user started typing and more than 5 seconds have passed since the last request
(boolFalse), if the user stopped typing
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ID_INVALIDThe provided chat id is invalid.
-

Related pages

-

boolTrue

-

The constructor can be interpreted as a booleantrue value.

-

boolFalse

-

Constructor may be interpreted as a booleanfalse value.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.setGameScore b/data/corefork.telegram.org/method/messages.setGameScore deleted file mode 100644 index 70d4aea20e..0000000000 --- a/data/corefork.telegram.org/method/messages.setGameScore +++ /dev/null @@ -1,218 +0,0 @@ - - - - - messages.setGameScore - - - - - - - - - - - - - -
- -
-
-
- -

messages.setGameScore

- -

Use this method to set the score of the specified user in a game sent as a normal message (bots only).

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.setGameScore#8ef8ecc0 flags:# edit_message:flags.0?true force:flags.1?true peer:InputPeer id:int user_id:InputUser score:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
edit_messageflags.0?trueSet this flag if the game message should be automatically edited to include the current scoreboard
forceflags.1?trueSet this flag if the high score is allowed to decrease. This can be useful when fixing mistakes or banning cheaters
peerInputPeerUnique identifier of target chat
idintIdentifier of the sent message
user_idInputUserUser identifier
scoreintNew score
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOT_SCORE_NOT_MODIFIEDThe score wasn't modified.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USER_BOT_REQUIREDThis method can only be called by a bot.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.setHistoryTTL b/data/corefork.telegram.org/method/messages.setHistoryTTL deleted file mode 100644 index 031dc2bad1..0000000000 --- a/data/corefork.telegram.org/method/messages.setHistoryTTL +++ /dev/null @@ -1,182 +0,0 @@ - - - - - messages.setHistoryTTL - - - - - - - - - - - - - -
- -
-
-
- -

messages.setHistoryTTL

- -

Set maximum Time-To-Live of all messages in the specified chat

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.setHistoryTTL#b80e5fe4 peer:InputPeer period:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe dialog
periodintAutomatically delete all messages sent in the chat after this many seconds
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
400TTL_PERIOD_INVALIDThe specified TTL period is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.setInlineBotResults b/data/corefork.telegram.org/method/messages.setInlineBotResults deleted file mode 100644 index be9d09aa86..0000000000 --- a/data/corefork.telegram.org/method/messages.setInlineBotResults +++ /dev/null @@ -1,358 +0,0 @@ - - - - - messages.setInlineBotResults - - - - - - - - - - - - - -
- -
-
-
- -

messages.setInlineBotResults

- -

Answer an inline query, for bots only

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.setInlineBotResults#eb5ea206 flags:# gallery:flags.0?true private:flags.1?true query_id:long results:Vector<InputBotInlineResult> cache_time:int next_offset:flags.2?string switch_pm:flags.3?InlineBotSwitchPM = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
galleryflags.0?trueSet this flag if the results are composed of media files
privateflags.1?trueSet this flag if results may be cached on the server side only for the user that sent the query. By default, results may be returned to any user who sends the same query
query_idlongUnique identifier for the answered query
resultsVector<InputBotInlineResult>Vector of results for the inline query
cache_timeintThe maximum amount of time in seconds that the result of the inline query may be cached on the server. Defaults to 300.
next_offsetflags.2?stringPass the offset that a client should send in the next query with the same text to receive more results. Pass an empty string if there are no more results or if you don‘t support pagination. Offset length can’t exceed 64 bytes.
switch_pmflags.3?InlineBotSwitchPMIf passed, clients will display a button with specified text that switches the user to a private chat with the bot and sends the bot a start message with a certain parameter.
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400ARTICLE_TITLE_EMPTYThe title of the article is empty.
400AUDIO_CONTENT_URL_EMPTYThe remote URL specified in the content field is empty.
400AUDIO_TITLE_EMPTYAn empty audio title was provided.
400BUTTON_DATA_INVALIDThe data of one or more of the buttons you provided is invalid.
400BUTTON_TYPE_INVALIDThe type of one or more of the buttons you provided is invalid.
400BUTTON_URL_INVALIDButton URL invalid.
400DOCUMENT_INVALIDThe specified document is invalid.
400FILE_CONTENT_TYPE_INVALIDFile content-type is invalid.
400FILE_TITLE_EMPTYAn empty file title was specified.
400GIF_CONTENT_TYPE_INVALIDGIF content-type invalid.
400MESSAGE_EMPTYThe provided message is empty.
400MESSAGE_TOO_LONGThe provided message is too long.
400NEXT_OFFSET_INVALIDThe specified offset is longer than 64 bytes.
400PHOTO_CONTENT_TYPE_INVALIDPhoto mime-type invalid.
400PHOTO_CONTENT_URL_EMPTYPhoto URL invalid.
400PHOTO_INVALIDPhoto invalid.
400PHOTO_THUMB_URL_EMPTYPhoto thumbnail URL is empty.
400QUERY_ID_INVALIDThe query ID is invalid.
400REPLY_MARKUP_INVALIDThe provided reply markup is invalid.
400RESULTS_TOO_MUCHToo many results were provided.
400RESULT_ID_DUPLICATEYou provided a duplicate result ID.
400RESULT_TYPE_INVALIDResult type invalid.
400SEND_MESSAGE_MEDIA_INVALIDInvalid media provided.
400SEND_MESSAGE_TYPE_INVALIDThe message type is invalid.
400START_PARAM_INVALIDStart parameter invalid.
400STICKER_DOCUMENT_INVALIDThe specified sticker document is invalid.
403USER_BOT_INVALIDThis method can only be called by a bot.
400VIDEO_TITLE_EMPTYThe specified video title is empty.
400WEBDOCUMENT_INVALIDInvalid webdocument URL provided.
400WEBDOCUMENT_MIME_INVALIDInvalid webdocument mime type provided.
400WEBDOCUMENT_SIZE_TOO_BIGWebdocument is too big!
400WEBDOCUMENT_URL_INVALIDThe specified webdocument URL is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.setInlineGameScore b/data/corefork.telegram.org/method/messages.setInlineGameScore deleted file mode 100644 index 05ad9684a9..0000000000 --- a/data/corefork.telegram.org/method/messages.setInlineGameScore +++ /dev/null @@ -1,198 +0,0 @@ - - - - - messages.setInlineGameScore - - - - - - - - - - - - - -
- -
-
-
- -

messages.setInlineGameScore

- -

Use this method to set the score of the specified user in a game sent as an inline message (bots only).

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.setInlineGameScore#15ad9f64 flags:# edit_message:flags.0?true force:flags.1?true id:InputBotInlineMessageID user_id:InputUser score:int = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
edit_messageflags.0?trueSet this flag if the game message should be automatically edited to include the current scoreboard
forceflags.1?trueSet this flag if the high score is allowed to decrease. This can be useful when fixing mistakes or banning cheaters
idInputBotInlineMessageIDID of the inline message
user_idInputUserUser identifier
scoreintNew score
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400USER_BOT_REQUIREDThis method can only be called by a bot.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.setTyping b/data/corefork.telegram.org/method/messages.setTyping deleted file mode 100644 index 2a5aae903f..0000000000 --- a/data/corefork.telegram.org/method/messages.setTyping +++ /dev/null @@ -1,240 +0,0 @@ - - - - - messages.setTyping - - - - - - - - - - - - - -
- -
-
-
- -

messages.setTyping

- -

Sends a current user typing event (see SendMessageAction for all event types) to a conversation partner or group.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.setTyping#58943ee2 flags:# peer:InputPeer top_msg_id:flags.0?int action:SendMessageAction = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerTarget user or group
top_msg_idflags.0?intThread ID
actionSendMessageActionType of action
Parameter added in Layer 17.
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_ID_INVALIDThe provided chat id is invalid.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400USER_IS_BLOCKEDYou were blocked by this user.
400USER_IS_BOTBots can't send messages to other bots.
-

Bots can use this method

-

Related pages

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

-

Layers

-

Below you will find information on schema changes. For more details on the use of layers, see Invoking API methods.

-

SendMessageAction

-

User actions. Use this to provide users with detailed info about their chat partners' actions: typing or sending attachments of all kinds.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.startBot b/data/corefork.telegram.org/method/messages.startBot deleted file mode 100644 index 34755a31fd..0000000000 --- a/data/corefork.telegram.org/method/messages.startBot +++ /dev/null @@ -1,224 +0,0 @@ - - - - - messages.startBot - - - - - - - - - - - - - -
- -
-
-
- -

messages.startBot

- -

Start a conversation with a bot using a deep linking parameter

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.startBot#e6df7378 bot:InputUser peer:InputPeer random_id:long start_param:string = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
botInputUserThe bot
peerInputPeerThe chat where to start the bot, can be the bot's private chat or a group
random_idlongRandom ID to avoid resending the same message
start_paramstringDeep linking parameter
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOT_INVALIDThis is not a valid bot.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400START_PARAM_EMPTYThe start parameter is empty.
400START_PARAM_INVALIDStart parameter invalid.
400START_PARAM_TOO_LONGStart parameter is too long.
-

Related pages

-

Bots: An introduction for developers

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.startHistoryImport b/data/corefork.telegram.org/method/messages.startHistoryImport deleted file mode 100644 index 70e055e9e6..0000000000 --- a/data/corefork.telegram.org/method/messages.startHistoryImport +++ /dev/null @@ -1,180 +0,0 @@ - - - - - messages.startHistoryImport - - - - - - - - - - - - - -
- -
-
-
- -

messages.startHistoryImport

- -

Complete the history import process, importing all messages into the chat.
-To be called only after initializing the import with messages.initHistoryImport and uploading all files using messages.uploadImportedMedia.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.startHistoryImport#b43df344 peer:InputPeer import_id:long = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe Telegram chat where the messages should be imported, click here for more info »
import_idlongIdentifier of a history import session, returned by messages.initHistoryImport.
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400IMPORT_ID_INVALIDThe specified import ID is invalid.
-

Related pages

-

Imported messages

-

Telegram allows importing messages and media from foreign chat apps.

-

messages.initHistoryImport

-

Import chat history from a foreign chat app into a specific Telegram chat, click here for more info about imported chats ».

-

messages.uploadImportedMedia

-

Upload a media file associated with an imported chat, click here for more info ».

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.toggleDialogPin b/data/corefork.telegram.org/method/messages.toggleDialogPin deleted file mode 100644 index 0baf9c522d..0000000000 --- a/data/corefork.telegram.org/method/messages.toggleDialogPin +++ /dev/null @@ -1,187 +0,0 @@ - - - - - messages.toggleDialogPin - - - - - - - - - - - - - -
- -
-
-
- -

messages.toggleDialogPin

- -

Pin/unpin a dialog

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.toggleDialogPin#a731e257 flags:# pinned:flags.0?true peer:InputDialogPeer = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
pinnedflags.0?trueWhether to pin or unpin the dialog
peerInputDialogPeerThe dialog to pin
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PINNED_DIALOGS_TOO_MUCHToo many pinned dialogs.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.toggleStickerSets b/data/corefork.telegram.org/method/messages.toggleStickerSets deleted file mode 100644 index be2fac4409..0000000000 --- a/data/corefork.telegram.org/method/messages.toggleStickerSets +++ /dev/null @@ -1,170 +0,0 @@ - - - - - messages.toggleStickerSets - - - - - - - - - - - - - -
- -
-
-
- -

messages.toggleStickerSets

- -

Apply changes to multiple stickersets

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.toggleStickerSets#b5052fea flags:# uninstall:flags.0?true archive:flags.1?true unarchive:flags.2?true stickersets:Vector<InputStickerSet> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
uninstallflags.0?trueUninstall the specified stickersets
archiveflags.1?trueArchive the specified stickersets
unarchiveflags.2?trueUnarchive the specified stickersets
stickersetsVector<InputStickerSet>Stickersets to act upon
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.uninstallStickerSet b/data/corefork.telegram.org/method/messages.uninstallStickerSet deleted file mode 100644 index 9223939b97..0000000000 --- a/data/corefork.telegram.org/method/messages.uninstallStickerSet +++ /dev/null @@ -1,167 +0,0 @@ - - - - - messages.uninstallStickerSet - - - - - - - - - - - - - -
- -
-
-
- -

messages.uninstallStickerSet

- -

Uninstall a stickerset

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.uninstallStickerSet#f96e55de stickerset:InputStickerSet = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
stickersetInputStickerSetThe stickerset to uninstall
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400STICKERSET_INVALIDThe provided sticker set is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.unpinAllMessages b/data/corefork.telegram.org/method/messages.unpinAllMessages deleted file mode 100644 index a12ac989d5..0000000000 --- a/data/corefork.telegram.org/method/messages.unpinAllMessages +++ /dev/null @@ -1,153 +0,0 @@ - - - - - messages.unpinAllMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.unpinAllMessages

- -

Unpin all pinned messages

-

- -
-
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
----functions---
-messages.unpinAllMessages#f025bc8b peer:InputPeer = messages.AffectedHistory;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerChat where to unpin
-

Result

-

messages.AffectedHistory

-

Bots can use this method

-

Related pages

-

Pinned messages

-

Telegram allows pinning multiple messages on top of a specific chat.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.updateDialogFilter b/data/corefork.telegram.org/method/messages.updateDialogFilter deleted file mode 100644 index 170206ff38..0000000000 --- a/data/corefork.telegram.org/method/messages.updateDialogFilter +++ /dev/null @@ -1,190 +0,0 @@ - - - - - messages.updateDialogFilter - - - - - - - - - - - - - -
- -
-
-
- -

messages.updateDialogFilter

- -

Update folder

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.updateDialogFilter#1ad4a04a flags:# id:int filter:flags.0?DialogFilter = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
idintFolder ID
filterflags.0?DialogFilterFolder info
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400FILTER_ID_INVALIDThe specified filter ID is invalid.
400FILTER_INCLUDE_EMPTYThe include_peers vector of the filter is empty.
400FILTER_TITLE_EMPTYThe title field of the filter is empty.
-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.updateDialogFiltersOrder b/data/corefork.telegram.org/method/messages.updateDialogFiltersOrder deleted file mode 100644 index ce13528998..0000000000 --- a/data/corefork.telegram.org/method/messages.updateDialogFiltersOrder +++ /dev/null @@ -1,153 +0,0 @@ - - - - - messages.updateDialogFiltersOrder - - - - - - - - - - - - - -
- -
-
-
- -

messages.updateDialogFiltersOrder

- -

Reorder folders

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-messages.updateDialogFiltersOrder#c563c1e4 order:Vector<int> = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
orderVector<int>New folder order
-

Result

-

Bool

-

Related pages

-

Folders

-

Telegram allows placing chats into folders, based on their type, mute status, or other custom criteria, thanks to folder blacklists and whitelists.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.updatePinnedMessage b/data/corefork.telegram.org/method/messages.updatePinnedMessage deleted file mode 100644 index 0d4e9b1805..0000000000 --- a/data/corefork.telegram.org/method/messages.updatePinnedMessage +++ /dev/null @@ -1,238 +0,0 @@ - - - - - messages.updatePinnedMessage - - - - - - - - - - - - - -
- -
-
-
- -

messages.updatePinnedMessage

- -

Pin a message

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-messages.updatePinnedMessage#d2aaf7ec flags:# silent:flags.0?true unpin:flags.1?true pm_oneside:flags.2?true peer:InputPeer id:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
silentflags.0?truePin the message silently, without triggering a notification
unpinflags.1?trueWhether the message should unpinned or pinned
pm_onesideflags.2?trueWhether the message should only be pinned on the local side of a one-to-one chat
peerInputPeerThe peer where to pin the message
idintThe message to pin or unpin
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOT_ONESIDE_NOT_AVAILBots can't pin messages in PM just for themselves.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_NOT_MODIFIEDThe pinned message wasn't modified.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400MESSAGE_ID_INVALIDThe provided message id is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PIN_RESTRICTEDYou can't pin messages.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.uploadEncryptedFile b/data/corefork.telegram.org/method/messages.uploadEncryptedFile deleted file mode 100644 index 8fb678854c..0000000000 --- a/data/corefork.telegram.org/method/messages.uploadEncryptedFile +++ /dev/null @@ -1,155 +0,0 @@ - - - - - messages.uploadEncryptedFile - - - - - - - - - - - - - -
- -
-
-
- -

messages.uploadEncryptedFile

- -

Upload encrypted file and associate it to a secret chat

-

- -
-
encryptedFileEmpty#c21f497e = EncryptedFile;
-encryptedFile#4a70994c id:long access_hash:long size:int dc_id:int key_fingerprint:int = EncryptedFile;
----functions---
-messages.uploadEncryptedFile#5057c497 peer:InputEncryptedChat file:InputEncryptedFile = EncryptedFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputEncryptedChatThe secret chat to associate the file to
fileInputEncryptedFileThe file
-

Result

-

EncryptedFile

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.uploadImportedMedia b/data/corefork.telegram.org/method/messages.uploadImportedMedia deleted file mode 100644 index 57c70d33b0..0000000000 --- a/data/corefork.telegram.org/method/messages.uploadImportedMedia +++ /dev/null @@ -1,181 +0,0 @@ - - - - - messages.uploadImportedMedia - - - - - - - - - - - - - -
- -
-
-
- -

messages.uploadImportedMedia

- -

Upload a media file associated with an imported chat, click here for more info ».

-

- -
-
messageMediaEmpty#3ded6320 = MessageMedia;
-messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;
-messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;
-messageMediaContact#70322949 phone_number:string first_name:string last_name:string vcard:string user_id:long = MessageMedia;
-messageMediaUnsupported#9f84f49e = MessageMedia;
-messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;
-messageMediaWebPage#a32dd600 webpage:WebPage = MessageMedia;
-messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;
-messageMediaGame#fdb19008 game:Game = MessageMedia;
-messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
-messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;
-messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
-messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;
----functions---
-messages.uploadImportedMedia#2a862092 peer:InputPeer import_id:long file_name:string media:InputMedia = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe Telegram chat where the media will be imported
import_idlongIdentifier of a history import session, returned by messages.initHistoryImport
file_namestringFile name
mediaInputMediaMedia metadata
-

Result

-

MessageMedia

-

Related pages

-

Imported messages

-

Telegram allows importing messages and media from foreign chat apps.

-

messages.initHistoryImport

-

Import chat history from a foreign chat app into a specific Telegram chat, click here for more info about imported chats ».

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/messages.uploadMedia b/data/corefork.telegram.org/method/messages.uploadMedia deleted file mode 100644 index 8aef22faf3..0000000000 --- a/data/corefork.telegram.org/method/messages.uploadMedia +++ /dev/null @@ -1,264 +0,0 @@ - - - - - messages.uploadMedia - - - - - - - - - - - - - -
- -
-
-
- -

messages.uploadMedia

- -

Upload a file and associate it to a chat (without actually sending it to the chat)

-

- -
-
messageMediaEmpty#3ded6320 = MessageMedia;
-messageMediaPhoto#695150d7 flags:# photo:flags.0?Photo ttl_seconds:flags.2?int = MessageMedia;
-messageMediaGeo#56e0d474 geo:GeoPoint = MessageMedia;
-messageMediaContact#70322949 phone_number:string first_name:string last_name:string vcard:string user_id:long = MessageMedia;
-messageMediaUnsupported#9f84f49e = MessageMedia;
-messageMediaDocument#9cb070d7 flags:# document:flags.0?Document ttl_seconds:flags.2?int = MessageMedia;
-messageMediaWebPage#a32dd600 webpage:WebPage = MessageMedia;
-messageMediaVenue#2ec0533f geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string = MessageMedia;
-messageMediaGame#fdb19008 game:Game = MessageMedia;
-messageMediaInvoice#84551347 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument receipt_msg_id:flags.2?int currency:string total_amount:long start_param:string = MessageMedia;
-messageMediaGeoLive#b940c666 flags:# geo:GeoPoint heading:flags.0?int period:int proximity_notification_radius:flags.1?int = MessageMedia;
-messageMediaPoll#4bd6e798 poll:Poll results:PollResults = MessageMedia;
-messageMediaDice#3f7ee58b value:int emoticon:string = MessageMedia;
----functions---
-messages.uploadMedia#519bc2b1 peer:InputPeer media:InputMedia = MessageMedia;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe chat, can be an inputPeerEmpty for bots
mediaInputMediaFile uploaded in chunks as described in files »
-

Result

-

MessageMedia

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOT_MISSINGThis method can only be run by a bot.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400CHAT_RESTRICTEDYou can't send messages in this chat, you were restricted.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400FILE_PARTS_INVALIDThe number of file parts is invalid.
400IMAGE_PROCESS_FAILEDFailure while processing image.
400INPUT_USER_DEACTIVATEDThe specified user was deleted.
400MEDIA_INVALIDMedia invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400PEER_ID_INVALIDThe provided peer id is invalid.
400PHOTO_EXT_INVALIDThe extension of the photo is invalid.
400PHOTO_INVALID_DIMENSIONSThe photo dimensions are invalid.
400PHOTO_SAVE_FILE_INVALIDInternal issues, try again later.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
400WEBPAGE_CURL_FAILEDFailure while fetching the webpage with cURL.
-

Bots can use this method

-

Related pages

-

inputPeerEmpty

-

An empty constructor, no user or chat is defined.

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/payments.getBankCardData b/data/corefork.telegram.org/method/payments.getBankCardData deleted file mode 100644 index 6f494d15c1..0000000000 --- a/data/corefork.telegram.org/method/payments.getBankCardData +++ /dev/null @@ -1,166 +0,0 @@ - - - - - payments.getBankCardData - - - - - - - - - - - - - -
- -
-
-
- -

payments.getBankCardData

- -

Get info about a credit card

-

- -
-
payments.bankCardData#3e24e573 title:string open_urls:Vector<BankCardOpenUrl> = payments.BankCardData;
----functions---
-payments.getBankCardData#2e79d779 number:string = payments.BankCardData;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
numberstringCredit card number
-

Result

-

payments.BankCardData

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400BANK_CARD_NUMBER_INVALIDThe specified card number is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/payments.getPaymentForm b/data/corefork.telegram.org/method/payments.getPaymentForm deleted file mode 100644 index 99b4cb6720..0000000000 --- a/data/corefork.telegram.org/method/payments.getPaymentForm +++ /dev/null @@ -1,181 +0,0 @@ - - - - - payments.getPaymentForm - - - - - - - - - - - - - -
- -
-
-
- -

payments.getPaymentForm

- -

Get a payment form

-

- -
-
payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
----functions---
-payments.getPaymentForm#8a333c8d flags:# peer:InputPeer msg_id:int theme_params:flags.0?DataJSON = payments.PaymentForm;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerThe peer where the payment form was sent
msg_idintMessage ID of payment form
theme_paramsflags.0?DataJSONA JSON object with the following keys, containing color theme information (integers, RGB24) to pass to the payment provider, to apply in eventual verification pages:
bg_color - Background color
text_color - Text color
hint_color - Hint text color
link_color - Link color
button_color - Button color
button_text_color - Button text color
-

Result

-

payments.PaymentForm

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/payments.getSavedInfo b/data/corefork.telegram.org/method/payments.getSavedInfo deleted file mode 100644 index 7c2ada5984..0000000000 --- a/data/corefork.telegram.org/method/payments.getSavedInfo +++ /dev/null @@ -1,134 +0,0 @@ - - - - - payments.getSavedInfo - - - - - - - - - - - - - -
- -
-
-
- -

payments.getSavedInfo

- -

Get saved payment information

-

- -
-
payments.savedInfo#fb8fe43c flags:# has_saved_credentials:flags.1?true saved_info:flags.0?PaymentRequestedInfo = payments.SavedInfo;
----functions---
-payments.getSavedInfo#227d824b = payments.SavedInfo;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

payments.SavedInfo

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/payments.sendPaymentForm b/data/corefork.telegram.org/method/payments.sendPaymentForm deleted file mode 100644 index 614b2050f1..0000000000 --- a/data/corefork.telegram.org/method/payments.sendPaymentForm +++ /dev/null @@ -1,206 +0,0 @@ - - - - - payments.sendPaymentForm - - - - - - - - - - - - - -
- -
-
-
- -

payments.sendPaymentForm

- -

Send compiled payment form

-

- -
-
payments.paymentResult#4e5f810d updates:Updates = payments.PaymentResult;
-payments.paymentVerificationNeeded#d8411139 url:string = payments.PaymentResult;
----functions---
-payments.sendPaymentForm#30c3bc9d flags:# form_id:long peer:InputPeer msg_id:int requested_info_id:flags.0?string shipping_option_id:flags.1?string credentials:InputPaymentCredentials tip_amount:flags.2?long = payments.PaymentResult;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
form_idlongForm ID
peerInputPeerThe peer where the payment form was sent
msg_idintMessage ID of form
requested_info_idflags.0?stringID of saved and validated order info
shipping_option_idflags.1?stringChosen shipping option ID
credentialsInputPaymentCredentialsPayment credentials
tip_amountflags.2?longTip, in the smallest units of the currency (integer, not float/double). For example, for a price of US$ 1.45 pass amount = 145. See the exp parameter in currencies.json, it shows the number of digits past the decimal point for each currency (2 for the majority of currencies).
-

Result

-

payments.PaymentResult

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
-

Related pages

-

payments.ValidatedRequestedInfo

-

Validated user-provided info

-

Bot Payments API

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/payments.validateRequestedInfo b/data/corefork.telegram.org/method/payments.validateRequestedInfo deleted file mode 100644 index 32e10cbe5e..0000000000 --- a/data/corefork.telegram.org/method/payments.validateRequestedInfo +++ /dev/null @@ -1,186 +0,0 @@ - - - - - payments.validateRequestedInfo - - - - - - - - - - - - - -
- -
-
-
- -

payments.validateRequestedInfo

- -

Submit requested order information for validation

-

- -
-
payments.validatedRequestedInfo#d1451883 flags:# id:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = payments.ValidatedRequestedInfo;
----functions---
-payments.validateRequestedInfo#db103170 flags:# save:flags.0?true peer:InputPeer msg_id:int info:PaymentRequestedInfo = payments.ValidatedRequestedInfo;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
saveflags.0?trueSave order information to re-use it for future orders
peerInputPeerPeer where the payment form was sent
msg_idintMessage ID of payment form
infoPaymentRequestedInfoRequested order information
-

Result

-

payments.ValidatedRequestedInfo

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400MESSAGE_ID_INVALIDThe provided message id is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.acceptCall b/data/corefork.telegram.org/method/phone.acceptCall deleted file mode 100644 index eb14374915..0000000000 --- a/data/corefork.telegram.org/method/phone.acceptCall +++ /dev/null @@ -1,193 +0,0 @@ - - - - - phone.acceptCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.acceptCall

- -

Accept incoming call

-

- -
-
phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;
----functions---
-phone.acceptCall#3bd2b4a0 peer:InputPhoneCall g_b:bytes protocol:PhoneCallProtocol = phone.PhoneCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPhoneCallThe call to accept
g_bbytesParameter for E2E encryption key exchange »
protocolPhoneCallProtocolPhone call settings
-

Result

-

phone.PhoneCall

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CALL_ALREADY_ACCEPTEDThe call was already accepted.
400CALL_ALREADY_DECLINEDThe call was already declined.
400CALL_PEER_INVALIDThe provided call peer object is invalid.
400CALL_PROTOCOL_FLAGS_INVALIDCall protocol flags invalid.
-

Related pages

-

End-to-End Encrypted Voice Calls

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.checkGroupCall b/data/corefork.telegram.org/method/phone.checkGroupCall deleted file mode 100644 index f722d0ea93..0000000000 --- a/data/corefork.telegram.org/method/phone.checkGroupCall +++ /dev/null @@ -1,154 +0,0 @@ - - - - - phone.checkGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.checkGroupCall

- -

Check whether the group call Server Forwarding Unit is currently receiving the streams with the specified WebRTC source IDs

-

- -
-
---functions---
-phone.checkGroupCall#b59cf977 call:InputGroupCall sources:Vector<int> = Vector<int>;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallGroup call
sourcesVector<int>Source IDs
-

Result

-

Vector<int>

-

Returns an intersection of the source IDs specified in sources, and the source IDs currently being forwarded by the SFU.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.confirmCall b/data/corefork.telegram.org/method/phone.confirmCall deleted file mode 100644 index 8ef0127681..0000000000 --- a/data/corefork.telegram.org/method/phone.confirmCall +++ /dev/null @@ -1,188 +0,0 @@ - - - - - phone.confirmCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.confirmCall

- -

Complete phone call E2E encryption key exchange »

-

- -
-
phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;
----functions---
-phone.confirmCall#2efe1722 peer:InputPhoneCall g_a:bytes key_fingerprint:long protocol:PhoneCallProtocol = phone.PhoneCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPhoneCallThe phone call
g_abytesParameter for E2E encryption key exchange »
key_fingerprintlongKey fingerprint
protocolPhoneCallProtocolPhone call settings
-

Result

-

phone.PhoneCall

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CALL_ALREADY_DECLINEDThe call was already declined.
400CALL_PEER_INVALIDThe provided call peer object is invalid.
-

Related pages

-

End-to-End Encrypted Voice Calls

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.createGroupCall b/data/corefork.telegram.org/method/phone.createGroupCall deleted file mode 100644 index 73b61a74d2..0000000000 --- a/data/corefork.telegram.org/method/phone.createGroupCall +++ /dev/null @@ -1,200 +0,0 @@ - - - - - phone.createGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.createGroupCall

- -

Create a group call or livestream

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.createGroupCall#48cdc6d8 flags:# peer:InputPeer random_id:int title:flags.0?string schedule_date:flags.1?int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
peerInputPeerAssociate the group call or livestream to the provided group/supergroup/channel
random_idintUnique client message ID required to prevent creation of duplicate group calls
titleflags.0?stringCall title
schedule_dateflags.1?intFor scheduled group call or livestreams, the absolute date when the group call will start
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400SCHEDULE_DATE_INVALIDInvalid schedule date provided.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.discardCall b/data/corefork.telegram.org/method/phone.discardCall deleted file mode 100644 index 464b9ef2a7..0000000000 --- a/data/corefork.telegram.org/method/phone.discardCall +++ /dev/null @@ -1,202 +0,0 @@ - - - - - phone.discardCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.discardCall

- -

Refuse or end running call

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.discardCall#b2cbc1c0 flags:# video:flags.0?true peer:InputPhoneCall duration:int reason:PhoneCallDiscardReason connection_id:long = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.0?trueWhether this is a video call
peerInputPhoneCallThe phone call
durationintCall duration
reasonPhoneCallDiscardReasonWhy was the call discarded
connection_idlongPreferred libtgvoip relay ID
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CALL_ALREADY_ACCEPTEDThe call was already accepted.
400CALL_PEER_INVALIDThe provided call peer object is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.discardGroupCall b/data/corefork.telegram.org/method/phone.discardGroupCall deleted file mode 100644 index 41c1bfda46..0000000000 --- a/data/corefork.telegram.org/method/phone.discardGroupCall +++ /dev/null @@ -1,155 +0,0 @@ - - - - - phone.discardGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.discardGroupCall

- -

Terminate a group call

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.discardGroupCall#7a777135 call:InputGroupCall = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallThe group call to terminate
-

Result

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.editGroupCallMember b/data/corefork.telegram.org/method/phone.editGroupCallMember deleted file mode 100644 index 81305b2262..0000000000 --- a/data/corefork.telegram.org/method/phone.editGroupCallMember +++ /dev/null @@ -1,167 +0,0 @@ - - - - - phone.editGroupCallMember - - - - - - - - - - - - - -
- -
-
-
- -

phone.editGroupCallMember

- -

Edit information about a given group call participant

-

- -
-
 Method schema is available as of layer 123. Switch »

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - -
flags#Flags, see TL conditional fields
mutedflags.0?trueWhether to mute or unmute the user
callInputGroupCallGroup call
user_idInputUserThe user in question
-

Result

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.editGroupCallTitle b/data/corefork.telegram.org/method/phone.editGroupCallTitle deleted file mode 100644 index 3f222bf22e..0000000000 --- a/data/corefork.telegram.org/method/phone.editGroupCallTitle +++ /dev/null @@ -1,160 +0,0 @@ - - - - - phone.editGroupCallTitle - - - - - - - - - - - - - -
- -
-
-
- -

phone.editGroupCallTitle

- -

Edit the title of a group call or livestream

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.editGroupCallTitle#1ca6ac0a call:InputGroupCall title:string = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallGroup call
titlestringNew title
-

Result

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.exportGroupCallInvite b/data/corefork.telegram.org/method/phone.exportGroupCallInvite deleted file mode 100644 index 513c754b13..0000000000 --- a/data/corefork.telegram.org/method/phone.exportGroupCallInvite +++ /dev/null @@ -1,159 +0,0 @@ - - - - - phone.exportGroupCallInvite - - - - - - - - - - - - - -
- -
-
-
- -

phone.exportGroupCallInvite

- -

Get an invite link for a group call or livestream

-

- -
-
phone.exportedGroupCallInvite#204bd158 link:string = phone.ExportedGroupCallInvite;
----functions---
-phone.exportGroupCallInvite#e6aa647f flags:# can_self_unmute:flags.0?true call:InputGroupCall = phone.ExportedGroupCallInvite;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
can_self_unmuteflags.0?trueFor livestreams, if set, users that join using this link will be able to speak without explicitly requesting permission by (for example by raising their hand).
callInputGroupCallThe group call
-

Result

-

phone.ExportedGroupCallInvite

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.getCallConfig b/data/corefork.telegram.org/method/phone.getCallConfig deleted file mode 100644 index 37d57e09ce..0000000000 --- a/data/corefork.telegram.org/method/phone.getCallConfig +++ /dev/null @@ -1,134 +0,0 @@ - - - - - phone.getCallConfig - - - - - - - - - - - - - -
- -
-
-
- -

phone.getCallConfig

- -

Get phone call configuration to be passed to libtgvoip's shared config

-

- -
-
dataJSON#7d748d04 data:string = DataJSON;
----functions---
-phone.getCallConfig#55451fa9 = DataJSON;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

DataJSON

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.getGroupCall b/data/corefork.telegram.org/method/phone.getGroupCall deleted file mode 100644 index 240595798d..0000000000 --- a/data/corefork.telegram.org/method/phone.getGroupCall +++ /dev/null @@ -1,157 +0,0 @@ - - - - - phone.getGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.getGroupCall

- -

Get info about a group call

-

- -
-
phone.groupCall#9e727aad call:GroupCall participants:Vector<GroupCallParticipant> participants_next_offset:string chats:Vector<Chat> users:Vector<User> = phone.GroupCall;
----functions---
-phone.getGroupCall#41845db call:InputGroupCall limit:int = phone.GroupCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallThe group call
limitintMaximum number of results to return, see pagination
-

Result

-

phone.GroupCall

-

Related pages

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.getGroupCallJoinAs b/data/corefork.telegram.org/method/phone.getGroupCallJoinAs deleted file mode 100644 index 0d97c2a619..0000000000 --- a/data/corefork.telegram.org/method/phone.getGroupCallJoinAs +++ /dev/null @@ -1,149 +0,0 @@ - - - - - phone.getGroupCallJoinAs - - - - - - - - - - - - - -
- -
-
-
- -

phone.getGroupCallJoinAs

- -

Get a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.

-

- -
-
phone.joinAsPeers#afe5623f peers:Vector<Peer> chats:Vector<Chat> users:Vector<User> = phone.JoinAsPeers;
----functions---
-phone.getGroupCallJoinAs#ef7c213a peer:InputPeer = phone.JoinAsPeers;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerThe dialog whose group call or livestream we're trying to join
-

Result

-

phone.JoinAsPeers

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.getGroupParticipants b/data/corefork.telegram.org/method/phone.getGroupParticipants deleted file mode 100644 index 9a991fee32..0000000000 --- a/data/corefork.telegram.org/method/phone.getGroupParticipants +++ /dev/null @@ -1,174 +0,0 @@ - - - - - phone.getGroupParticipants - - - - - - - - - - - - - -
- -
-
-
- -

phone.getGroupParticipants

- -

Get group call participants

-

- -
-
phone.groupParticipants#f47751b6 count:int participants:Vector<GroupCallParticipant> next_offset:string chats:Vector<Chat> users:Vector<User> version:int = phone.GroupParticipants;
----functions---
-phone.getGroupParticipants#c558d8ab call:InputGroupCall ids:Vector<InputPeer> sources:Vector<int> offset:string limit:int = phone.GroupParticipants;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallGroup call
idsVector<InputPeer>If specified, will fetch group participant info about the specified peers
sourcesVector<int>If specified, will fetch group participant info about the specified WebRTC source IDs
offsetstringOffset for results, taken from the next_offset field of phone.groupParticipants, initially an empty string.
Note: if no more results are available, the method call will return an empty next_offset; thus, avoid providing the next_offset returned in phone.groupParticipants if it is empty, to avoid an infinite loop.
limitintMaximum number of results to return, see pagination
-

Result

-

phone.GroupParticipants

-

Related pages

-

phone.groupParticipants

-

Info about the participants of a group call or livestream

-

Pagination in the API

-

How to fetch results from large lists of objects.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.inviteToGroupCall b/data/corefork.telegram.org/method/phone.inviteToGroupCall deleted file mode 100644 index 9e0fc8a6ba..0000000000 --- a/data/corefork.telegram.org/method/phone.inviteToGroupCall +++ /dev/null @@ -1,177 +0,0 @@ - - - - - phone.inviteToGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.inviteToGroupCall

- -

Invite a set of users to a group call.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.inviteToGroupCall#7b393160 call:InputGroupCall users:Vector<InputUser> = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallThe group call
usersVector<InputUser>The users to invite.
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
403GROUPCALL_FORBIDDENThe group call has already ended.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.joinGroupCall b/data/corefork.telegram.org/method/phone.joinGroupCall deleted file mode 100644 index d7dcf44f82..0000000000 --- a/data/corefork.telegram.org/method/phone.joinGroupCall +++ /dev/null @@ -1,202 +0,0 @@ - - - - - phone.joinGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.joinGroupCall

- -

Join a group call

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.joinGroupCall#b132ff7b flags:# muted:flags.0?true video_stopped:flags.2?true call:InputGroupCall join_as:InputPeer invite_hash:flags.1?string params:DataJSON = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
mutedflags.0?trueIf set, the user will be muted by default upon joining.
video_stoppedflags.2?trueIf set, the user's video will be disabled by default upon joining.
callInputGroupCallThe group call
join_asInputPeerJoin the group call, presenting yourself as the specified user/channel
invite_hashflags.1?stringThe invitation hash from the invite link: https://t.me/username?voicechat=hash
paramsDataJSONWebRTC parameters
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400GROUPCALL_SSRC_DUPLICATE_MUCHThe app needs to retry joining the group call with a new SSRC value.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.joinGroupCallPresentation b/data/corefork.telegram.org/method/phone.joinGroupCallPresentation deleted file mode 100644 index 58926e206d..0000000000 --- a/data/corefork.telegram.org/method/phone.joinGroupCallPresentation +++ /dev/null @@ -1,180 +0,0 @@ - - - - - phone.joinGroupCallPresentation - - - - - - - - - - - - - -
- -
-
-
- -

phone.joinGroupCallPresentation

- -

Start screen sharing in a call

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.joinGroupCallPresentation#cbea6bc4 call:InputGroupCall params:DataJSON = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallThe group call
paramsDataJSONWebRTC parameters
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
403PARTICIPANT_JOIN_MISSINGTrying to enable a presentation, when the user hasn't joined the Video Chat with phone.joinGroupCall.
-

Related pages

-

phone.joinGroupCall

-

Join a group call

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.leaveGroupCall b/data/corefork.telegram.org/method/phone.leaveGroupCall deleted file mode 100644 index a9a3edefa4..0000000000 --- a/data/corefork.telegram.org/method/phone.leaveGroupCall +++ /dev/null @@ -1,160 +0,0 @@ - - - - - phone.leaveGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.leaveGroupCall

- -

Leave a group call

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.leaveGroupCall#500377f9 call:InputGroupCall source:int = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallThe group call
sourceintYour source ID
-

Result

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.leaveGroupCallPresentation b/data/corefork.telegram.org/method/phone.leaveGroupCallPresentation deleted file mode 100644 index 6b692cdd00..0000000000 --- a/data/corefork.telegram.org/method/phone.leaveGroupCallPresentation +++ /dev/null @@ -1,155 +0,0 @@ - - - - - phone.leaveGroupCallPresentation - - - - - - - - - - - - - -
- -
-
-
- -

phone.leaveGroupCallPresentation

- -

Stop screen sharing in a group call

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.leaveGroupCallPresentation#1c50d144 call:InputGroupCall = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallThe group call
-

Result

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.receivedCall b/data/corefork.telegram.org/method/phone.receivedCall deleted file mode 100644 index 77b53b2a5c..0000000000 --- a/data/corefork.telegram.org/method/phone.receivedCall +++ /dev/null @@ -1,172 +0,0 @@ - - - - - phone.receivedCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.receivedCall

- -

Optional: notify the server that the user is currently busy in a call: this will automatically refuse all incoming phone calls until the current phone call is ended.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-phone.receivedCall#17d54f61 peer:InputPhoneCall = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPhoneCallThe phone call we're currently in
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CALL_ALREADY_DECLINEDThe call was already declined.
400CALL_PEER_INVALIDThe provided call peer object is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.requestCall b/data/corefork.telegram.org/method/phone.requestCall deleted file mode 100644 index 12aefa7e57..0000000000 --- a/data/corefork.telegram.org/method/phone.requestCall +++ /dev/null @@ -1,213 +0,0 @@ - - - - - phone.requestCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.requestCall

- -

Start a telegram phone call

-

- -
-
phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;
----functions---
-phone.requestCall#42ff96ed flags:# video:flags.0?true user_id:InputUser random_id:int g_a_hash:bytes protocol:PhoneCallProtocol = phone.PhoneCall;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
videoflags.0?trueWhether to start a video call
user_idInputUserDestination of the phone call
random_idintRandom ID to avoid resending the same object
g_a_hashbytesParameter for E2E encryption key exchange »
protocolPhoneCallProtocolPhone call settings
-

Result

-

phone.PhoneCall

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CALL_PROTOCOL_FLAGS_INVALIDCall protocol flags invalid.
400PARTICIPANT_VERSION_OUTDATEDThe other participant does not use an up to date telegram client with support for calls.
400USER_ID_INVALIDThe provided user ID is invalid.
403USER_IS_BLOCKEDYou were blocked by this user.
403USER_PRIVACY_RESTRICTEDThe user's privacy settings do not allow you to do this.
-

Related pages

-

End-to-End Encrypted Voice Calls

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.saveCallDebug b/data/corefork.telegram.org/method/phone.saveCallDebug deleted file mode 100644 index 8c95c4f3bf..0000000000 --- a/data/corefork.telegram.org/method/phone.saveCallDebug +++ /dev/null @@ -1,177 +0,0 @@ - - - - - phone.saveCallDebug - - - - - - - - - - - - - -
- -
-
-
- -

phone.saveCallDebug

- -

Send phone call debug data to server

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-phone.saveCallDebug#277add7e peer:InputPhoneCall debug:DataJSON = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPhoneCallPhone call
debugDataJSONDebug statistics obtained from libtgvoip
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CALL_PEER_INVALIDThe provided call peer object is invalid.
400DATA_JSON_INVALIDThe provided JSON data is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.sendSignalingData b/data/corefork.telegram.org/method/phone.sendSignalingData deleted file mode 100644 index a9fd06a944..0000000000 --- a/data/corefork.telegram.org/method/phone.sendSignalingData +++ /dev/null @@ -1,155 +0,0 @@ - - - - - phone.sendSignalingData - - - - - - - - - - - - - -
- -
-
-
- -

phone.sendSignalingData

- -

Send VoIP signaling data

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-phone.sendSignalingData#ff7a9383 peer:InputPhoneCall data:bytes = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPhoneCallPhone call
databytesSignaling payload
-

Result

-

Bool

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.setCallRating b/data/corefork.telegram.org/method/phone.setCallRating deleted file mode 100644 index 585fc6d11c..0000000000 --- a/data/corefork.telegram.org/method/phone.setCallRating +++ /dev/null @@ -1,192 +0,0 @@ - - - - - phone.setCallRating - - - - - - - - - - - - - -
- -
-
-
- -

phone.setCallRating

- -

Rate a call

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.setCallRating#59ead627 flags:# user_initiative:flags.0?true peer:InputPhoneCall rating:int comment:string = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
user_initiativeflags.0?trueWhether the user decided on their own initiative to rate the call
peerInputPhoneCallThe call to rate
ratingintRating in 1-5 stars
commentstringAn additional comment
-

Result

-

Updates with info about the rating message sent to the official VoIP bot

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400CALL_PEER_INVALIDThe provided call peer object is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.startScheduledGroupCall b/data/corefork.telegram.org/method/phone.startScheduledGroupCall deleted file mode 100644 index d6e3e00378..0000000000 --- a/data/corefork.telegram.org/method/phone.startScheduledGroupCall +++ /dev/null @@ -1,155 +0,0 @@ - - - - - phone.startScheduledGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.startScheduledGroupCall

- -

Start a scheduled group call.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.startScheduledGroupCall#5680e342 call:InputGroupCall = Updates;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallThe scheduled group call
-

Result

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.toggleGroupCallRecord b/data/corefork.telegram.org/method/phone.toggleGroupCallRecord deleted file mode 100644 index 563a8ebac4..0000000000 --- a/data/corefork.telegram.org/method/phone.toggleGroupCallRecord +++ /dev/null @@ -1,180 +0,0 @@ - - - - - phone.toggleGroupCallRecord - - - - - - - - - - - - - -
- -
-
-
- -

phone.toggleGroupCallRecord

- -

Start or stop recording a group call: the recorded audio and video streams will be automatically sent to Saved messages (the chat with ourselves).

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.toggleGroupCallRecord#f128c708 flags:# start:flags.0?true video:flags.2?true call:InputGroupCall title:flags.1?string video_portrait:flags.2?Bool = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
startflags.0?trueWhether to start or stop recording
videoflags.2?trueWhether to also record video streams
callInputGroupCallThe group call or livestream
titleflags.1?stringRecording title
video_portraitflags.2?BoolIf video stream recording is enabled, whether to record in portrait or landscape mode
-

Result

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.toggleGroupCallSettings b/data/corefork.telegram.org/method/phone.toggleGroupCallSettings deleted file mode 100644 index 2c2b18c908..0000000000 --- a/data/corefork.telegram.org/method/phone.toggleGroupCallSettings +++ /dev/null @@ -1,187 +0,0 @@ - - - - - phone.toggleGroupCallSettings - - - - - - - - - - - - - -
- -
-
-
- -

phone.toggleGroupCallSettings

- -

Change group call settings

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.toggleGroupCallSettings#74bbb43d flags:# reset_invite_hash:flags.1?true call:InputGroupCall join_muted:flags.0?Bool = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
reset_invite_hashflags.1?trueInvalidate existing invite links
callInputGroupCallGroup call
join_mutedflags.0?BoolWhether all users will bthat join this group calle muted by default upon joining the group call
-

Result

-

Updates

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400GROUPCALL_NOT_MODIFIEDGroup call settings weren't modified.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/phone.toggleGroupCallStartSubscription b/data/corefork.telegram.org/method/phone.toggleGroupCallStartSubscription deleted file mode 100644 index a0b3a23233..0000000000 --- a/data/corefork.telegram.org/method/phone.toggleGroupCallStartSubscription +++ /dev/null @@ -1,160 +0,0 @@ - - - - - phone.toggleGroupCallStartSubscription - - - - - - - - - - - - - -
- -
-
-
- -

phone.toggleGroupCallStartSubscription

- -

Subscribe or unsubscribe to a scheduled group call

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
----functions---
-phone.toggleGroupCallStartSubscription#219c34e6 call:InputGroupCall subscribed:Bool = Updates;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
callInputGroupCallScheduled group call
subscribedBoolEnable or disable subscription
-

Result

-

Updates

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/photos.deletePhotos b/data/corefork.telegram.org/method/photos.deletePhotos deleted file mode 100644 index 99961ac6fa..0000000000 --- a/data/corefork.telegram.org/method/photos.deletePhotos +++ /dev/null @@ -1,148 +0,0 @@ - - - - - photos.deletePhotos - - - - - - - - - - - - - -
- -
-
-
- -

photos.deletePhotos

- -

Deletes profile photos.

-

- -
-
---functions---
-photos.deletePhotos#87cf7f2f id:Vector<InputPhoto> = Vector<long>;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idVector<InputPhoto>Input photos to delete
-

Result

-

Method returns a list of successfully deleted photos in Vector<long>

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/photos.getUserPhotos b/data/corefork.telegram.org/method/photos.getUserPhotos deleted file mode 100644 index eae12568a6..0000000000 --- a/data/corefork.telegram.org/method/photos.getUserPhotos +++ /dev/null @@ -1,193 +0,0 @@ - - - - - photos.getUserPhotos - - - - - - - - - - - - - -
- -
-
-
- -

photos.getUserPhotos

- -

Returns the list of user photos.

-

- -
-
photos.photos#8dca6aa5 photos:Vector<Photo> users:Vector<User> = photos.Photos;
-photos.photosSlice#15051f54 count:int photos:Vector<Photo> users:Vector<User> = photos.Photos;
----functions---
-photos.getUserPhotos#91cd32a8 user_id:InputUser offset:int max_id:long limit:int = photos.Photos;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
user_idInputUserUser ID
offsetintNumber of list elements to be skipped
max_idlongIf a positive value was transferred, the method will return only photos with IDs less than the set one
limitintNumber of list elements to be returned
-

Result

-

photos.Photos

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400MAX_ID_INVALIDThe provided max ID is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400USER_ID_INVALIDThe provided user ID is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/photos.updateProfilePhoto b/data/corefork.telegram.org/method/photos.updateProfilePhoto deleted file mode 100644 index 9b73d695c0..0000000000 --- a/data/corefork.telegram.org/method/photos.updateProfilePhoto +++ /dev/null @@ -1,196 +0,0 @@ - - - - - photos.updateProfilePhoto - - - - - - - - - - - - - -
- -
-
-
- -

photos.updateProfilePhoto

- -

Installs a previously uploaded photo as a profile photo.

-

- -
-
photos.photo#20212ca8 photo:Photo users:Vector<User> = photos.Photo;
----functions---
-photos.updateProfilePhoto#72d4742c id:InputPhoto = photos.Photo;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idInputPhotoInput photo
-

Result

-

UserProfilePhoto

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400ALBUM_PHOTOS_TOO_MANYToo many.
400FILE_PARTS_INVALIDThe number of file parts is invalid.
400IMAGE_PROCESS_FAILEDFailure while processing image.
400LOCATION_INVALIDThe provided location is invalid.
400PHOTO_CROP_SIZE_SMALLPhoto is too small.
400PHOTO_EXT_INVALIDThe extension of the photo is invalid.
400PHOTO_ID_INVALIDPhoto ID invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/stats.getBroadcastStats b/data/corefork.telegram.org/method/stats.getBroadcastStats deleted file mode 100644 index 857fd492b4..0000000000 --- a/data/corefork.telegram.org/method/stats.getBroadcastStats +++ /dev/null @@ -1,194 +0,0 @@ - - - - - stats.getBroadcastStats - - - - - - - - - - - - - -
- -
-
-
- -

stats.getBroadcastStats

- -

Get channel statistics

-

- -
-
stats.broadcastStats#bdf78394 period:StatsDateRangeDays followers:StatsAbsValueAndPrev views_per_post:StatsAbsValueAndPrev shares_per_post:StatsAbsValueAndPrev enabled_notifications:StatsPercentValue growth_graph:StatsGraph followers_graph:StatsGraph mute_graph:StatsGraph top_hours_graph:StatsGraph interactions_graph:StatsGraph iv_interactions_graph:StatsGraph views_by_source_graph:StatsGraph new_followers_by_source_graph:StatsGraph languages_graph:StatsGraph recent_message_interactions:Vector<MessageInteractionCounters> = stats.BroadcastStats;
----functions---
-stats.getBroadcastStats#ab42441a flags:# dark:flags.0?true channel:InputChannel = stats.BroadcastStats;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
darkflags.0?trueWhether to enable dark theme for graph colors
channelInputChannelThe channel
-

Result

-

stats.BroadcastStats

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BROADCAST_REQUIREDThis method can only be called on a channel, please use stats.getMegagroupStats for supergroups.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
-

Related pages

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/stats.getMegagroupStats b/data/corefork.telegram.org/method/stats.getMegagroupStats deleted file mode 100644 index c3950a3133..0000000000 --- a/data/corefork.telegram.org/method/stats.getMegagroupStats +++ /dev/null @@ -1,191 +0,0 @@ - - - - - stats.getMegagroupStats - - - - - - - - - - - - - -
- -
-
-
- -

stats.getMegagroupStats

- -

Get supergroup statistics

-

- -
-
stats.megagroupStats#ef7ff916 period:StatsDateRangeDays members:StatsAbsValueAndPrev messages:StatsAbsValueAndPrev viewers:StatsAbsValueAndPrev posters:StatsAbsValueAndPrev growth_graph:StatsGraph members_graph:StatsGraph new_members_by_source_graph:StatsGraph languages_graph:StatsGraph messages_graph:StatsGraph actions_graph:StatsGraph top_hours_graph:StatsGraph weekdays_graph:StatsGraph top_posters:Vector<StatsGroupTopPoster> top_admins:Vector<StatsGroupTopAdmin> top_inviters:Vector<StatsGroupTopInviter> users:Vector<User> = stats.MegagroupStats;
----functions---
-stats.getMegagroupStats#dcdf8607 flags:# dark:flags.0?true channel:InputChannel = stats.MegagroupStats;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
darkflags.0?trueWhether to enable dark theme for graph colors
channelInputChannelSupergroup ID
-

Result

-

stats.MegagroupStats

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHAT_ADMIN_REQUIREDYou must be an admin in this chat to do this.
400MEGAGROUP_REQUIREDYou can only use this method on a supergroup.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/stats.loadAsyncGraph b/data/corefork.telegram.org/method/stats.loadAsyncGraph deleted file mode 100644 index ada1f63dff..0000000000 --- a/data/corefork.telegram.org/method/stats.loadAsyncGraph +++ /dev/null @@ -1,193 +0,0 @@ - - - - - stats.loadAsyncGraph - - - - - - - - - - - - - -
- -
-
-
- -

stats.loadAsyncGraph

- -

Load channel statistics graph asynchronously

-

- -
-
statsGraphAsync#4a27eb2d token:string = StatsGraph;
-statsGraphError#bedc9822 error:string = StatsGraph;
-statsGraph#8ea464b6 flags:# json:DataJSON zoom_token:flags.0?string = StatsGraph;
----functions---
-stats.loadAsyncGraph#621d5fa0 flags:# token:string x:flags.0?long = StatsGraph;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
tokenstringGraph token from statsGraphAsync constructor
xflags.0?longZoom value, if required
-

Result

-

StatsGraph

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400GRAPH_EXPIRED_RELOADThis graph has expired, please obtain a new graph token.
400GRAPH_INVALID_RELOADInvalid graph token provided, please reload the stats and provide the updated token.
400GRAPH_OUTDATED_RELOADThe graph is outdated, please get a new async token using stats.getBroadcastStats.
-

Related pages

-

statsGraphAsync

-

This channel statistics graph must be generated asynchronously using stats.loadAsyncGraph to reduce server load

-

Channel statistics

-

Telegram offers detailed channel statistics for channels and supergroups.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/stickers.changeStickerPosition b/data/corefork.telegram.org/method/stickers.changeStickerPosition deleted file mode 100644 index 99a87299b7..0000000000 --- a/data/corefork.telegram.org/method/stickers.changeStickerPosition +++ /dev/null @@ -1,177 +0,0 @@ - - - - - stickers.changeStickerPosition - - - - - - - - - - - - - -
- -
-
-
- -

stickers.changeStickerPosition

- -

Changes the absolute position of a sticker in the set to which it belongs; for bots only. The sticker set must have been created by the bot

-

- -
-
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
----functions---
-stickers.changeStickerPosition#ffb6d4ca sticker:InputDocument position:int = messages.StickerSet;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
stickerInputDocumentThe sticker
positionintThe new position of the sticker, zero-based
-

Result

-

messages.StickerSet

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOT_MISSINGThis method can only be run by a bot.
400STICKER_INVALIDThe provided sticker is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/stickers.checkShortName b/data/corefork.telegram.org/method/stickers.checkShortName deleted file mode 100644 index 3ae709b85b..0000000000 --- a/data/corefork.telegram.org/method/stickers.checkShortName +++ /dev/null @@ -1,172 +0,0 @@ - - - - - stickers.checkShortName - - - - - - - - - - - - - -
- -
-
-
- -

stickers.checkShortName

- -

Check whether the given short name is available

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-stickers.checkShortName#284b3639 short_name:string = Bool;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
short_namestringShort name
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400SHORT_NAME_INVALIDThe specified short name is invalid.
400SHORT_NAME_OCCUPIEDThe specified short name is already in use.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/stickers.createStickerSet b/data/corefork.telegram.org/method/stickers.createStickerSet deleted file mode 100644 index 271d8c019d..0000000000 --- a/data/corefork.telegram.org/method/stickers.createStickerSet +++ /dev/null @@ -1,282 +0,0 @@ - - - - - stickers.createStickerSet - - - - - - - - - - - - - -
- -
-
-
- -

stickers.createStickerSet

- -

Create a stickerset, bots only.

-

- -
-
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
----functions---
-stickers.createStickerSet#9021ab67 flags:# masks:flags.0?true animated:flags.1?true videos:flags.4?true user_id:InputUser title:string short_name:string thumb:flags.2?InputDocument stickers:Vector<InputStickerSetItem> software:flags.3?string = messages.StickerSet;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
masksflags.0?trueWhether this is a mask stickerset
animatedflags.1?trueWhether this is an animated stickerset
user_idInputUserStickerset owner
titlestringStickerset name, 1-64 chars
short_namestringSticker set name. Can contain only English letters, digits and underscores. Must end with "by" ( is case insensitive); 1-64 characters
thumbflags.2?InputDocumentThumbnail
stickersVector<InputStickerSetItem>Stickers
softwareflags.3?stringUsed when importing stickers using the sticker import SDKs, specifies the name of the software that created the stickers
-

Result

-

messages.StickerSet

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOT_MISSINGThis method can only be run by a bot.
400PACK_SHORT_NAME_INVALIDShort pack name invalid.
400PACK_SHORT_NAME_OCCUPIEDA stickerpack with this name already exists.
400PACK_TITLE_INVALIDThe stickerpack title is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
400SHORTNAME_OCCUPY_FAILEDAn internal error occurred.
400STICKERS_EMPTYNo sticker provided.
400STICKER_EMOJI_INVALIDSticker emoji invalid.
400STICKER_FILE_INVALIDSticker file invalid.
400STICKER_PNG_DIMENSIONSSticker png dimensions invalid.
400STICKER_PNG_NOPNGOne of the specified stickers is not a valid PNG file.
400STICKER_TGS_NODOCIncorrect document type for sticker.
400STICKER_TGS_NOTGSInvalid TGS sticker provided.
400STICKER_THUMB_PNG_NOPNGIncorrect stickerset thumb file provided, PNG / WEBP expected.
400STICKER_THUMB_TGS_NOTGSIncorrect stickerset TGS thumb file provided.
400USER_ID_INVALIDThe provided user ID is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/stickers.removeStickerFromSet b/data/corefork.telegram.org/method/stickers.removeStickerFromSet deleted file mode 100644 index 523b9a42b3..0000000000 --- a/data/corefork.telegram.org/method/stickers.removeStickerFromSet +++ /dev/null @@ -1,172 +0,0 @@ - - - - - stickers.removeStickerFromSet - - - - - - - - - - - - - -
- -
-
-
- -

stickers.removeStickerFromSet

- -

Remove a sticker from the set where it belongs, bots only. The sticker set must have been created by the bot.

-

- -
-
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
----functions---
-stickers.removeStickerFromSet#f7760f51 sticker:InputDocument = messages.StickerSet;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
stickerInputDocumentThe sticker to remove
-

Result

-

messages.StickerSet

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400BOT_MISSINGThis method can only be run by a bot.
400STICKER_INVALIDThe provided sticker is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/stickers.setStickerSetThumb b/data/corefork.telegram.org/method/stickers.setStickerSetThumb deleted file mode 100644 index 4a6a1e745d..0000000000 --- a/data/corefork.telegram.org/method/stickers.setStickerSetThumb +++ /dev/null @@ -1,182 +0,0 @@ - - - - - stickers.setStickerSetThumb - - - - - - - - - - - - - -
- -
-
-
- -

stickers.setStickerSetThumb

- -

Set stickerset thumbnail

-

- -
-
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
----functions---
-stickers.setStickerSetThumb#9a364e30 stickerset:InputStickerSet thumb:InputDocument = messages.StickerSet;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
stickersetInputStickerSetStickerset
thumbInputDocumentThumbnail
-

Result

-

messages.StickerSet

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400STICKERSET_INVALIDThe provided sticker set is invalid.
400STICKER_THUMB_PNG_NOPNGIncorrect stickerset thumb file provided, PNG / WEBP expected.
400STICKER_THUMB_TGS_NOTGSIncorrect stickerset TGS thumb file provided.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/stickers.suggestShortName b/data/corefork.telegram.org/method/stickers.suggestShortName deleted file mode 100644 index 1ce2b43bb5..0000000000 --- a/data/corefork.telegram.org/method/stickers.suggestShortName +++ /dev/null @@ -1,166 +0,0 @@ - - - - - stickers.suggestShortName - - - - - - - - - - - - - -
- -
-
-
- -

stickers.suggestShortName

- -

Suggests a short name for a given stickerpack name

-

- -
-
stickers.suggestedShortName#85fea03f short_name:string = stickers.SuggestedShortName;
----functions---
-stickers.suggestShortName#4dafc503 title:string = stickers.SuggestedShortName;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
titlestringSticker pack name
-

Result

-

stickers.SuggestedShortName

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400TITLE_INVALIDThe specified stickerpack title is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/updates.getChannelDifference b/data/corefork.telegram.org/method/updates.getChannelDifference deleted file mode 100644 index 3965b855fd..0000000000 --- a/data/corefork.telegram.org/method/updates.getChannelDifference +++ /dev/null @@ -1,247 +0,0 @@ - - - - - updates.getChannelDifference - - - - - - - - - - - - - -
- -
-
-
- -

updates.getChannelDifference

- -

Returns the difference between the current state of updates of a certain channel and transmitted.

-

- -
-
updates.channelDifferenceEmpty#3e11affb flags:# final:flags.0?true pts:int timeout:flags.1?int = updates.ChannelDifference;
-updates.channelDifferenceTooLong#a4bcc6fe flags:# final:flags.0?true timeout:flags.1?int dialog:Dialog messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
-updates.channelDifference#2064674e flags:# final:flags.0?true pts:int timeout:flags.1?int new_messages:Vector<Message> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
----functions---
-updates.getChannelDifference#3173d78 flags:# force:flags.0?true channel:InputChannel filter:ChannelMessagesFilter pts:int limit:int = updates.ChannelDifference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
forceflags.0?trueSet to true to skip some possibly unneeded updates and reduce server-side load
channelInputChannelThe channel
filterChannelMessagesFilterMesssage filter
ptsintPersistent timestamp (see updates)
limitintHow many updates to fetch, max 100000
Ordinary (non-bot) users are supposed to pass 10-100
-

Result

-

updates.ChannelDifference

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
403CHANNEL_PUBLIC_GROUP_NAchannel/supergroup not available.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400FROM_MESSAGE_BOT_DISABLEDBots can't use fromMessage min constructors.
400MSG_ID_INVALIDInvalid message ID provided.
400PERSISTENT_TIMESTAMP_EMPTYPersistent timestamp empty.
400PERSISTENT_TIMESTAMP_INVALIDPersistent timestamp invalid.
400PINNED_DIALOGS_TOO_MUCHToo many pinned dialogs.
400RANGES_INVALIDInvalid range provided.
400USER_BANNED_IN_CHANNELYou're banned from sending messages in supergroups/channels.
-

Bots can use this method

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/updates.getDifference b/data/corefork.telegram.org/method/updates.getDifference deleted file mode 100644 index d9553f4f9b..0000000000 --- a/data/corefork.telegram.org/method/updates.getDifference +++ /dev/null @@ -1,225 +0,0 @@ - - - - - updates.getDifference - - - - - - - - - - - - - -
- -
-
-
- -

updates.getDifference

- -

Get new updates.

-

- -
-
updates.differenceEmpty#5d75a138 date:int seq:int = updates.Difference;
-updates.difference#f49ca0 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> state:updates.State = updates.Difference;
-updates.differenceSlice#a8fb1981 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> intermediate_state:updates.State = updates.Difference;
-updates.differenceTooLong#4afe8f6d pts:int = updates.Difference;
----functions---
-updates.getDifference#25939651 flags:# pts:int pts_total_limit:flags.0?int date:int qts:int = updates.Difference;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
ptsintPTS, see updates.
pts_total_limitflags.0?intFor fast updating: if provided and pts + pts_total_limit < remote pts, updates.differenceTooLong will be returned.
Simply tells the server to not return the difference if it is bigger than pts_total_limit
If the remote pts is too big (> ~4000000), this field will default to 1000000
dateintdate, see updates.
qtsintQTS, see updates.
-

Result

-

updates.Difference

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400CDN_METHOD_INVALIDYou can't call this method in a CDN DC.
403CHAT_WRITE_FORBIDDENYou can't write in this chat.
400DATE_EMPTYDate empty.
400MSG_ID_INVALIDInvalid message ID provided.
400PERSISTENT_TIMESTAMP_EMPTYPersistent timestamp empty.
400PERSISTENT_TIMESTAMP_INVALIDPersistent timestamp invalid.
-

Bots can use this method

-

Related pages

-

Working with Updates

-

How to subscribe to updates and handle them properly.

-

updates.differenceTooLong

-

The difference is too long, and the specified state must be used to refetch updates.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/updates.getState b/data/corefork.telegram.org/method/updates.getState deleted file mode 100644 index 4eaaedd8b4..0000000000 --- a/data/corefork.telegram.org/method/updates.getState +++ /dev/null @@ -1,135 +0,0 @@ - - - - - updates.getState - - - - - - - - - - - - - -
- -
-
-
- -

updates.getState

- -

Returns a current state of updates.

-

- -
-
updates.state#a56c2a3e pts:int qts:int date:int seq:int unread_count:int = updates.State;
----functions---
-updates.getState#edd4882a = updates.State;

-

Parameters

-

This constructor does not require any parameters.

-

Result

-

updates.State

-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/upload.getCdnFile b/data/corefork.telegram.org/method/upload.getCdnFile deleted file mode 100644 index 470e12c4d2..0000000000 --- a/data/corefork.telegram.org/method/upload.getCdnFile +++ /dev/null @@ -1,162 +0,0 @@ - - - - - upload.getCdnFile - - - - - - - - - - - - - -
- -
-
-
- -

upload.getCdnFile

- -

Download a CDN file.

-

- -
-
upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;
-upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;
----functions---
-upload.getCdnFile#2000bcc3 file_token:bytes offset:int limit:int = upload.CdnFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
file_tokenbytesFile token
offsetintOffset of chunk to download
limitintLength of chunk to download
-

Result

-

upload.CdnFile

-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/upload.getCdnFileHashes b/data/corefork.telegram.org/method/upload.getCdnFileHashes deleted file mode 100644 index 408e57e5bb..0000000000 --- a/data/corefork.telegram.org/method/upload.getCdnFileHashes +++ /dev/null @@ -1,178 +0,0 @@ - - - - - upload.getCdnFileHashes - - - - - - - - - - - - - -
- -
-
-
- -

upload.getCdnFileHashes

- -

Get SHA256 hashes for verifying downloaded CDN files

-

- -
-
---functions---
-upload.getCdnFileHashes#4da54231 file_token:bytes offset:int = Vector<FileHash>;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
file_tokenbytesFile
offsetintOffset from which to start getting hashes
-

Result

-

Vector<FileHash>

-

Possible errors

- - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400CDN_METHOD_INVALIDYou can't call this method in a CDN DC.
400RSA_DECRYPT_FAILEDInternal RSA decryption failed.
-

Bots can use this method

-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/upload.getFile b/data/corefork.telegram.org/method/upload.getFile deleted file mode 100644 index 5101e074b6..0000000000 --- a/data/corefork.telegram.org/method/upload.getFile +++ /dev/null @@ -1,252 +0,0 @@ - - - - - upload.getFile - - - - - - - - - - - - - -
- -
-
-
- -

upload.getFile

- -

Returns content of a whole file or its part.

-

- -
-
upload.file#96a18d5 type:storage.FileType mtime:int bytes:bytes = upload.File;
-upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;
----functions---
-upload.getFile#b15a9afc flags:# precise:flags.0?true cdn_supported:flags.1?true location:InputFileLocation offset:int limit:int = upload.File;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
preciseflags.0?trueDisable some checks on limit and offset values, useful for example to stream videos by keyframes
cdn_supportedflags.1?trueWhether the current client supports CDN downloads
locationInputFileLocationFile location
offsetintNumber of bytes to be skipped
limitintNumber of bytes to be returned
-

Result

-

upload.File

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
406FILEREF_UPGRADE_NEEDEDThe client has to be updated in order to support file references.
400FILE_ID_INVALIDThe provided file id is invalid.
400FILE_REFERENCE_*The file reference expired, it must be refreshed.
400FILE_REFERENCE_EXPIREDFile reference expired, it must be refetched as described in https://core.telegram.org/api/file_reference.
400LIMIT_INVALIDThe provided limit is invalid.
400LOCATION_INVALIDThe provided location is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
400OFFSET_INVALIDThe provided offset is invalid.
400PEER_ID_INVALIDThe provided peer id is invalid.
-

Bots can use this method

-

Related pages

-

Encrypted CDNs for Speed and Security

-

File references

-

How to handle file references.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/upload.getFileHashes b/data/corefork.telegram.org/method/upload.getFileHashes deleted file mode 100644 index 71aff6ea27..0000000000 --- a/data/corefork.telegram.org/method/upload.getFileHashes +++ /dev/null @@ -1,171 +0,0 @@ - - - - - upload.getFileHashes - - - - - - - - - - - - - -
- -
-
-
- -

upload.getFileHashes

- -

Get SHA256 hashes for verifying downloaded files

-

- -
-
---functions---
-upload.getFileHashes#c7025931 location:InputFileLocation offset:int = Vector<FileHash>;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
locationInputFileLocationFile
offsetintOffset from which to get file hashes
-

Result

-

Vector<FileHash>

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400LOCATION_INVALIDThe provided location is invalid.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/upload.getWebFile b/data/corefork.telegram.org/method/upload.getWebFile deleted file mode 100644 index 59010601f6..0000000000 --- a/data/corefork.telegram.org/method/upload.getWebFile +++ /dev/null @@ -1,176 +0,0 @@ - - - - - upload.getWebfile - - - - - - - - - - - - - -
- -
-
-
- -

upload.getWebfile

- -

Returns content of an HTTP file or a part, by proxying the request through telegram.

-

- -
-
upload.webFile#21e753bc size:int mime_type:string file_type:storage.FileType mtime:int bytes:bytes = upload.WebFile;
----functions---
-upload.getWebFile#24e6818d location:InputWebFileLocation offset:int limit:int = upload.WebFile;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
locationInputWebFileLocationThe file to download
offsetintNumber of bytes to be skipped
limitintNumber of bytes to be returned
-

Result

-

upload.WebFile

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400LOCATION_INVALIDThe provided location is invalid.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/upload.reuploadCdnFile b/data/corefork.telegram.org/method/upload.reuploadCdnFile deleted file mode 100644 index 64c75bb3ac..0000000000 --- a/data/corefork.telegram.org/method/upload.reuploadCdnFile +++ /dev/null @@ -1,173 +0,0 @@ - - - - - upload.reuploadCdnFile - - - - - - - - - - - - - -
- -
-
-
- -

upload.reuploadCdnFile

- -

Request a reupload of a certain file to a CDN DC.

-

- -
-
---functions---
-upload.reuploadCdnFile#9b2754a8 file_token:bytes request_token:bytes = Vector<FileHash>;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
file_tokenbytesFile token
request_tokenbytesRequest token
-

Result

-

Vector<FileHash>

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400RSA_DECRYPT_FAILEDInternal RSA decryption failed.
-

Bots can use this method

-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/upload.saveBigFilePart b/data/corefork.telegram.org/method/upload.saveBigFilePart deleted file mode 100644 index 707d7f45f1..0000000000 --- a/data/corefork.telegram.org/method/upload.saveBigFilePart +++ /dev/null @@ -1,208 +0,0 @@ - - - - - upload.saveBigFilePart - - - - - - - - - - - - - -
- -
-
-
- -

upload.saveBigFilePart

- -

Saves a part of a large file (over 10Mb in size) to be later passed to one of the methods.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-upload.saveBigFilePart#de7b673d file_id:long file_part:int file_total_parts:int bytes:bytes = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
file_idlongRandom file id, created by the client
file_partintPart sequence number
file_total_partsintTotal number of parts
bytesbytesBinary data, part contents
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
400FILE_PARTS_INVALIDThe number of file parts is invalid.
400FILE_PART_EMPTYThe provided file part is empty.
400FILE_PART_INVALIDThe file part number is invalid.
400FILE_PART_SIZE_CHANGEDProvided file part size has changed.
400FILE_PART_SIZE_INVALIDThe provided file part size is invalid.
400FILE_PART_TOO_BIGThe uploaded file part is too big.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/users.getUsers b/data/corefork.telegram.org/method/users.getUsers deleted file mode 100644 index c56bdf0e42..0000000000 --- a/data/corefork.telegram.org/method/users.getUsers +++ /dev/null @@ -1,191 +0,0 @@ - - - - - users.getUsers - - - - - - - - - - - - - -
- -
-
-
- -

users.getUsers

- -

Returns basic user info according to their identifiers.

-

- -
-
---functions---
-users.getUsers#d91a548 id:Vector<InputUser> = Vector<User>;

-

Parameters

- - - - - - - - - - - - - - - -
NameTypeDescription
idVector<InputUser>List of user identifiers
-

Result

-

Vector<User>

-

Possible errors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
CodeTypeDescription
401AUTH_KEY_PERM_EMPTYThe temporary auth key must be binded to the permanent auth key to use these methods.
400CHANNEL_INVALIDThe provided channel is invalid.
400CHANNEL_PRIVATEYou haven't joined this channel/supergroup.
400CONNECTION_NOT_INITEDConnection not initialized.
400INPUT_LAYER_INVALIDThe provided layer is invalid.
400MSG_ID_INVALIDInvalid message ID provided.
-

Bots can use this method

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/method/users.setSecureValueErrors b/data/corefork.telegram.org/method/users.setSecureValueErrors deleted file mode 100644 index 32088573f1..0000000000 --- a/data/corefork.telegram.org/method/users.setSecureValueErrors +++ /dev/null @@ -1,176 +0,0 @@ - - - - - users.setSecureValueErrors - - - - - - - - - - - - - -
- -
-
-
- -

users.setSecureValueErrors

- -

Notify the user that the sent passport data contains some errors The user will not be able to re-submit their Passport data to you until the errors are fixed (the contents of the field for which you returned the error must change).

-

Use this if the data submitted by the user doesn't satisfy the standards your service requires for any reason. For example, if a birthday date seems invalid, a submitted document is blurry, a scan shows evidence of tampering, etc. Supply some details in the error message to make sure the user knows how to correct the issues.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
----functions---
-users.setSecureValueErrors#90c894b5 id:InputUser errors:Vector<SecureValueError> = Bool;

-

Parameters

- - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
idInputUserThe user
errorsVector<SecureValueError>Errors
-

Result

-

Bool

-

Possible errors

- - - - - - - - - - - - - - - -
CodeTypeDescription
400USER_ID_INVALIDThe provided user ID is invalid.
-

Bots can use this method

-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/mtproto.html b/data/corefork.telegram.org/mtproto.html deleted file mode 100644 index 430aa6a267..0000000000 --- a/data/corefork.telegram.org/mtproto.html +++ /dev/null @@ -1,260 +0,0 @@ - - - - - MTProto Mobile Protocol - - - - - - - - - - - - - -
- -
-
-
-
-

MTProto Mobile Protocol

- -
- -
-

Please feel free to check out our FAQ for the Technically Inclined. -Client developers are required to comply with the Security Guidelines.

-
-

Related articles

-

-
-

This page deals with the basic layer of MTProto encryption used for Cloud chats (server-client encryption). See also:

- -

General Description

-

The protocol is designed for access to a server API from applications running on mobile devices. It must be emphasized that a web browser is not such an application.

-

The protocol is subdivided into three virtually independent components:

-
    -
  • High-level component (API query language): defines the method whereby API queries and responses are converted to binary messages.
  • -
  • Cryptographic (authorization) layer: defines the method by which messages are encrypted prior to being transmitted through the transport protocol.
  • -
  • Transport component: defines the method for the client and the server to transmit messages over some other existing network protocol (such as HTTP, HTTPS, WS (plain websockets), WSS (websockets over HTTPS), TCP, UDP).
  • -
- -
-

As of version 4.6, major Telegram clients are using MTProto 2.0, described in this article. -MTProto v1.0 (described here for reference) is deprecated and is currently being phased out.

-
-

Brief Component Summary

-

High-Level Component (RPC Query Language/API)

-

From the standpoint of the high-level component, the client and the server exchange messages inside a session. The session is attached to the client device (the application, to be more exact) rather than a specific websocket/http/https/tcp connection. In addition, each session is attached to a user key ID by which authorization is actually accomplished.

-

Several connections to a server may be open; messages may be sent in either direction through any of the connections (a response to a query is not necessarily returned through the same connection that carried the original query, although most often, that is the case; however, in no case can a message be returned through a connection belonging to a different session). When the UDP protocol is used, a response might be returned by a different IP address than the one to which the query had been sent.

-

There are several types of messages:

-
    -
  • RPC calls (client to server): calls to API methods
  • -
  • RPC responses (server to client): results of RPC calls
  • -
  • Message received acknowledgment (or rather, notification of status of a set of messages)
  • -
  • Message status query
  • -
  • Multipart message or container (a container that holds several messages; needed to send several RPC calls at once over an HTTP connection, for example; also, a container may support gzip).
  • -
-

From the standpoint of lower level protocols, a message is a binary data stream aligned along a 4 or 16-byte boundary. The first several fields in the message are fixed and are used by the cryptographic/authorization system.

-

Each message, either individual or inside a container, consists of a message identifier (64 bits, see below), a message sequence number within a session (32 bits), the length (of the message body in bytes; 32 bits), and a body (any size which is a multiple of 4 bytes). In addition, when a container or a single message is sent, an internal header is added at the top (see below), then the entire message is encrypted, and an external header is placed at the top of the message (a 64-bit key identifier and a 128-bit message key).

-

A message body normally consists of a 32-bit message type followed by type-dependent parameters. In particular, each RPC function has a corresponding message type. For more detail, see Binary Data Serialization, Mobile Protocol: Service Messages.

-

All numbers are written as little endian. However, very large numbers (2048-bit) used in RSA and DH are written in the big endian format because that is how the OpenSSL library does it.

-

Authorization and Encryption

-

Prior to a message (or a multipart message) being transmitted over a network using a transport protocol, it is encrypted in a certain way, and an external header is added at the top of the message which is: a 64-bit key identifier (that uniquely identifies an authorization key for the server as well as the user) and a 128-bit message key. A user key together with the message key defines an actual 256-bit key which is what encrypts the message using AES-256 encryption. Note that the initial part of the message to be encrypted contains variable data (session, message ID, sequence number, server salt) that obviously influences the message key (and thus the AES key and iv). The message key is defined as the 128 middle bits of the SHA256 of the message body (including session, message ID, etc.), including the padding bytes, prepended by 32 bytes taken from the authorization key. Multipart messages are encrypted as a single message.

-
-

For a technical specification, see Mobile Protocol: Detailed Description

-
-

The first thing a client application must do is create an authorization key which is normally generated when it is first run and almost never changes.

-

The protocol’s principal drawback is that an intruder passively intercepting messages and then somehow appropriating the authorization key (for example, by stealing a device) will be able to decrypt all the intercepted messages post factum. This probably is not too much of a problem (by stealing a device, one could also gain access to all the information cached on the device without decrypting anything); however, the following steps could be taken to overcome this weakness:

-
    -
  • Session keys generated using the Diffie-Hellman protocol and used in conjunction with the authorization and the message keys to select AES parameters. To create these, the first thing a client must do after creating a new session is send a special RPC query to the server (“generate session key”) to which the server will respond, whereupon all subsequent messages within the session are encrypted using the session key as well.
  • -
  • Protecting the key stored on the client device with a (text) password; this password is never stored in memory and is entered by a user when starting the application or more frequently (depending on application settings).
  • -
  • Data stored (cached) on the user device can also be protected by encryption using an authorization key which, in turn, is to be password-protected. Then, a password will be required to gain access even to that data.
  • -
-

Time Synchronization

-

If client time diverges widely from server time, a server may start ignoring client messages, or vice versa, because of an invalid message identifier (which is closely related to creation time). Under these circumstances, the server will send the client a special message containing the correct time and a certain 128-bit salt (either explicitly provided by the client in a special RPC synchronization request or equal to the key of the latest message received from the client during the current session). This message could be the first one in a container that includes other messages (if the time discrepancy is significant but does not as yet result in the client’s messages being ignored).

-

Having received such a message or a container holding it, the client first performs a time synchronization (in effect, simply storing the difference between the server’s time and its own to be able to compute the “correct” time in the future) and then verifies that the message identifiers for correctness.

-

Where a correction has been neglected, the client will have to generate a new session to assure the monotonicity of message identifiers.

-

MTProto transport

-

Before being sent using the selected transport protocol, the payload has to be wrapped in a secondary protocol header, defined by the appropriate MTProto transport protocol.

- -

The server recognizes these different protocols (and distinguishes them from HTTP, too) by the header. -Additionally, the following transport features can be used:

- -

Example implementations for these protocols can be seen in tdlib and MadelineProto.

-

Transport

-

Enables the delivery of encrypted containers together with the external header (hereinafter, Payload) from client to server and back. -Multiple transport protocols are defined:

- -

(We shall examine only the first five types.)

-

Recap

-

To recap, using the ISO/OSI stack as comparison:

-
- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/mtproto/TL-abstract-types.html b/data/corefork.telegram.org/mtproto/TL-abstract-types.html deleted file mode 100644 index f23f8d5c88..0000000000 --- a/data/corefork.telegram.org/mtproto/TL-abstract-types.html +++ /dev/null @@ -1,202 +0,0 @@ - - - - - Binary serialization and abstract TL types - - - - - - - - - - - - - -
- -
-
-
- -

Binary serialization and abstract TL types

- -

TL Language defines abstract data types in the spirit of a general theory of types (more accurately, Martin-Löf’s theories of dependent intuitionistic types) without specifying the values of these types should be represented in memory, when saved to disk, or transmitted over a network. In contrast, the article on binary serialization discusses the problem of effective serialization of values of abstract types. To this end, the concept of a concrete or serialized type has been defined as the sets of serializations of all possible values of the corresponding abstract type. In this case, the serializations take values in the set A of words in the alphabet A*, which consists of 2^32 characters -- 32-bit integers.

-

In order to use a TL schema (e.g. “program”) in the TL language to describe the serialization of values of abstract types, we should explain how the concrete type [T] (subset [T] of A^) is associated with the abstract type T (defined in TL), and how the values of the abstract type T correspond to the values of the concrete type [T] (i.e. the elements of [T]*).

-

Serialization is the process of constructing an element of [T] based on a value of the abstract type T. The reverse process is deserialization.

-

Values of the abstract type T may be represented in a different way. Typically, some sort of trees or graphs are used in memory or, if desired, a set of nodes may be used, each of which contains a certain tag (“node type”) and several pointers to other nodes and/or values of built-in primitive types such as int. However, for general discussions it is useful to write the values of abstract type T as a string, more specifically, an S-expression. Recall that an S-expression is either an atom (the value of a primitive type, for example, an integer or a string constant in quotation marks; or an identifier that corresponds to a built-in or defined function) or a space-delimited list of S-expressions ending in parentheses. In our case, we use S-expressions, the first element of which is a combinator identifier, while the remaining elements (the number of which depends on the combinator’s arity) are S-expressions representing elements of the chosen combinator’s fields (or parameters). Moreover, the type of the arguments’ S-expressions and the type of the S-expressions of the result (e.g. the associated expression) must match.

-

For example, for the schema

-
pair x:int y:int = Pair;
-pnil = PairList;
-pcons hd:Pair tl:PairList = PairList;
-

the following are examples of the abstract type PairList, written as S-expressions:

-
(pnil)
-(pcons (pair 2 3) (pcons (pair 9 4) (pnil)))
-

We usually write E : T (read "E of type T”) when we want to say that E is a value of type T. We assume there is a built-in type Type whose values are types. Thus, writing T : Type means that T is a type.

-

For example, we can write:

-
PairList : Type;
-(pcons (pair 2 3) (pcons (pair 9 4) (pnil))) : PairList;
-

Converting an abstract value to a serialized value, generally speaking, is straightforward (and, if desired, can be defined by induction):

-
    -
  • -

    It is the serialization of values n of the primitive type int (as a single-symbol word in the alphabet A)

    -
  • -
  • -

    The serialization of a string constant (a value of the primitive type string) is a sequence of the 32-bit numbers defined in Binary serialization.

    -
  • -
  • -

    The serialization of the S-expression (C E1 ... Er) : T, where C is a combinator with arity r with argument types T1, ..., Tr and result type T (e.g. C : T1->T2->...->Tr->T) is the concatenation of the combinator number C (a 32-bit number that unambiguously identifies the combinator, usually equal to the CRC-32 of the string of its TL description) and the serializations of the values E1 of type T1, E2 of type T2, ..., Er of type Tr.

    -
  • -
-

If we use [T] to denote the concrete type corresponding to the abstract T, and [E] to denote an element of [T] corresponding to the value E of type T, then the last rule may be written as:

-
    -
  • [T] is the combination, for each constructor of type C T1->T2->...->Tr->T (i.e. that returns a value of type T), of direct products {C} x [T1] x [T2] x ... x [Tr], where {C} is a single-element set consisting of the combinator number C. Because {C}<>{C'} when C<>C’, this defines a mutually single-valued mapping of the values of the abstract type T (written using S-expressions) to the set [T].
  • -
-

Values of the built-in clothed types Int and String and serialized as if they were defined using int x:int = Int; and string s:string = String;, i.e. the serialization of integer constant or a string is preceded by number of the int or string combinator (constructor). In S-expressions, this may be written as (int 5) or (string "Test").

-

However, what has been described above does not account for certain subtleties, such as the existence of naked types, or the difference between functions (active combinators whose application may be reduced, e.g. calculated) and constructors (passive combinators for which there are not and cannot be reduction rules). Furthermore, we have not explained how to handle polymorphic types and optional combinator parameters. We will attempt to explain this now.

-

Constants, surface values, and functional values

-

By dividing combinators into constructors and functions, we can introduce the following classes of expressions (values) of the abstract type T:

-
    -
  • -

    Constant expressions: for the types int and string, these are all integer/string constants; for T, these are all expressions like (C E1 ... Er) : T, where the combinator C : T1->T2->...->Tr->T is a constructor, and Ei : Ti is constant expressions of types Ti. In other words, a constant expression is an S-expression consisting of only constructors and constant of primitive types.

    -
  • -
  • -

    Surface expressions are expressions that outwardly contain a functional combinator whose arguments, however, are constant expressions of the appropriate types. In other words, the functional combinator is resolved only at the outer level. (This is not entirely true; see the full explanation below).

    -
  • -
  • -

    Functional expressions: These are expressions that may contain any combinators or constants at all levels.

    -
  • -
-

In practice, we most frequently need constant values (for storage and passing any data structures, in particular, responses to RPC queries) and surface expressions (for example, as RPC queries: then the functional combinator of the outer level is the name of the RPC function that we want to call, while its parameters are the arguments, which are constant values, for invoking the function). In some cases, arbitrary functional expressions are helpful (for example, it we want to remotely transmit the result of one RPC query to a different RPC query).

-

We will use c(T) to denote a subtype of the abstract type T, whose values are constant expressions of type T. Clearly, c(T) possesses approximately the same constructors as T itself (with the types of all arguments Ti replaced by c(Ti), but it does not have functional combinators.

-

Analogously, we will use f(T) to denote a subtype of T, whose values are surface expressions of type T. Clearly, the combinators of f(T) are essentially functional combinators of type T, but c() applies to the types of these combinators’ arguments: The combinator A : T1->...->Tr->T turns into A' : c(T1)->...->c(Tr)->f(T). (See the clarification of this rule below.)

-

Thus, we have defined two “functionals” c : Type -> Type and f : Type -> Type, such that forall T : Type, c(T) :- T and forall T : Type, f(T) :- T (writing T :- T' means that T is contained in T', or that T is a subtype of T').

-

We will assume that c and f are idempotent.

-

Naked types

-

From the perspective of abstract type theory, naked types (in contrast to built-in primitive types like int and string are unnecessary. However, they are extremely useful in practice.

-

Therefore, TL introduces the (partially defined) idempotent unary operator %, which turns a standard functional (e.g. an expression of type ...->Type or simply Type) into a different standard functional of the same type. If T is a type, then from an abstract theoretical point of view, %T is equivalent to c(T). In other words, the values of %T are the constant values of T. If T is a k-arity standard expression, then T : S1 -> ... -> Sk -> Type, where each Si=Type or #, then by definition %T is a k-arity standard expression with the same arity, which is defined by the equation (%T) a1 ... ak = % (T a1 ... ak).

-

When a constant value of type %T is serialized, it is first serialized as a value of type T (assuming that T is not already a naked type itself). Then the first character of the serialization is discarded (e.g. the name of the enclosing combinator). Therefore, %T is a only a valid type expression if there is not more than one constructor for %T. The expression %T, where T : S1 -> ... -> Sk -> Type, is valid, if for any choice of parameters a1 : S1, ... , ak : Sk, the type T a1 ... ak does not have more than one constructor. Using % in other instances is incorrect.

-

If for every value of the parameters a1 : S1, ..., ak : Sk, there is exactly one constructor C for T a1 ... ak, then TL allows writing C a1 ... ak instead of %T a1 ... ak or %(T a1 .. ak). In other words, in certain situations the identifier C is a synonym for %T. This is only allowed in the context of a type (when specifying the type of a combinator’s field or result).

-

Moreover, it is assumed that %Int = int and %String = string.

-

! modifier

-

In TL, the idempotent operator ! can modify any type, actually making surface values be allowed when its constant values are serialized. However, if T is a standard function like S1->..->Sr->Type, then !T is defined using the equation (!T) a1 ... ar = !(T a1 ... ar), for any a1:S1, ..., ar:Sr.

-

The ! operator is only allowed in a definition of the types of fields of functional combinators. It is usually used as a type prefix, for example:

-
set_timeout {X:Type} timeout:int f:!X = X;
-

In this case, the set_timeout “wrapper” is defined. It takes two explicit parameters: the integer timeout and a surface expression of type X. X : Type is itself an implicit parameter (it is not explicitly stated, rather it is inferred from the values of the other parameters and their types). A similar kind of wrapper may be helpful for modifying the action of RPC queries (which are surface expressions of various types). For example, suppose we have the function

-
factorial n:int = int;
-

then we can wrap the RPC query (factorial 100) as follows: (set_timeout 200 (factorial 100)). This expression is still a surface value of type int, which means it can be passed as an RPC query.

-

A consecutive pair of two computations is another example:

-
pair {X Y : Type} x:X y:Y = Pair X Y;  // constructor
-seq_pair {X Y : Type} x:!X y:!Y = Pair X Y; // functional wrapper for sequential computation
-par_pair {X Y : Type} x:!X y:!Y = Pair X Y; // functional wrapper for parallel computation
-

Now the RPC query (seq_pair (factorial 2) (factorial 3)) : Pair int int first calculates factorial 2, then factorial 3, and returns the pair (pair 2 6). In this case, the sequence of operations isn’t important, because they do not have side effects. It would have been just as well to use (par_pair (factorial 2) (factorial 3)). However, this is not always the case.

-

We can also define an analogy to a “comma” operation:

-
comma {X Y : Type} x:!X y:!Y = Y;
-

For example, this operation could first calculate x, then forget the result, calculate y, and return y.

-

Note that the semantics of the seq_pair, par_pair and comma wrappers are indeed defined where they are implemented (like the semantics of all other functional combinators), not by their TL declaration.

-

In principle, polymorphic wrappers like set_timeout can also be applied, for example, to “annotate” a RPC response’s constant values. For example, the server might return a response to a query together with the time it was calculated. However, a value of type !X must be constant, because that is what is expected as the enclosing expression’s value. In other words, set_timeout 239 E is a constant/surface value of type X if and only if E is such itself.

-

$ modifier

-

The idempotent modifier $ permits the use of arbitrary functional values of an appropriate type in contexts where only constants or surface values are usually allowed. It recursively transforms all combinators for all of the types involved, canceling the action of % and affixing $ to the parameter types and result of all combinators ($ is also added to the front of the transformed combinators). Moreover, built-in types are also transformed (in the final stage): $int = Int and $string = String.

-

This may be useful to create an RPC query that performs a “deep computation” of the expression passed to it:

-
compute {X:Type} expr:$X = X;
-

For example, now we can transmit the following as an RPC query:

-
(compute ($factorial ($factorial (int 3)))) : int
-

(Note that the three has become clothed; the combinator $factorial has type $int -> $int).

-

This is very powerful tool. It does not have to be implemented in very simple versions of TL. $ is not encountered in currently used TL schemas.

-

More on modifiers

-

In fact, at least in terms of its application to serialization, the TL language by default implies the c() modifier around all combinators’ parameter types and results, while ! and $ cancel it (more accurately, ! only cancels, and in some sense $ reverses the meaning). This is why there is no explicit c() modifier in TL and why it is assumed that all functions only accept constant values and return constant results, unless otherwise specified.

-

You may think that some functional combinators may have a type such as partial_factorial n:int = $int; and that the RPC query (partial_factorial 3) might then unexpectedly return ($product (int 3) ($product (int 2) ($product (int 1) (int 1)))) : $int ...

-

It is probably more correct to think about the ! modifier as follows. All types initially include only constant values (and only constructors). The ! modifier makes a new type (it’s twin) out of each type. This new type has no inherent constructors. Functional combinators differ from constructors in that ! is implicitly added in front of their result’s type. After this, the (local or remote) process of calculating the expression can be represented using the polymorphic function eval : !X -> X.

-

Optional combinator parameters and their values

-

See Optional combinator parameters and their values.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/mtproto/TL-combinators.html b/data/corefork.telegram.org/mtproto/TL-combinators.html deleted file mode 100644 index 4d6c7dc85c..0000000000 --- a/data/corefork.telegram.org/mtproto/TL-combinators.html +++ /dev/null @@ -1,251 +0,0 @@ - - - - - Formal description of TL combinators - - - - - - - - - - - - - -
- -
-
-
- -

Formal description of TL combinators

- -

Formal declaration of TL combinators

-

Main article: Formal description of TL. See also TL Language.

-

Combinators in TL are declared as follows:

-
-

combinator-decl ::= full-combinator-id { opt-args } { args } = result-type ;
-full-combinator-id ::= lc-ident-full | _
-combinator-id ::= lc-ident-ns | _
-opt-args ::= { var-ident { var-ident } : [excl-mark] type-expr }
-args ::= var-ident-opt : [ conditional-arg-def ] [ ! ] type-term
-args ::= [ var-ident-opt : ] [ multiplicity *] [ { args } ]
-args ::= ( var-ident-opt { var-ident-opt } : [!] type-term )
-args ::= [ ! ] type-term
-multiplicity ::= nat-term
-var-ident-opt ::= var-ident | _
-conditional-arg-def ::= var-ident [ . nat-const ] ?
-result-type ::= boxed-type-ident { subexpr }
-result-type ::= boxed-type-ident < subexpr { , subexpr } >

-
-

We shall clarify what all this means.

-
    -
  • -

    A combinator identifier is either an identifier starting with a lowercase Latin letter (lc-ident), or a namespace identifier (also lc-ident) followed by a period and another lc-ident. Therefore, cons and lists.get are valid combinator identifiers.

    -
  • -
  • -

    A combinator has a name, also known as a number (not to be confused with the designation) -- a 32-bit number that unambiguously determines it. It is either calculated automatically (see below) or it is explicitly assigned in the declaration. To do this, a hash mark (#) and exactly 8 hexadecimal digits -- the combinator’s name -- are added to the identifier of the combinator being defined.

    -
  • -
  • -

    A combinator’s declaration begins with its identifier, to which its name (separated by a hash mark) may have been added.

    -
  • -
  • -

    After the combinator identifier comes the main part of the declaration, which consists of declarations of fields (or variables), including an indication of their types.

    -
  • -
  • -

    First come declarations of optional fields (of which there may be several or none at all). Then there are the declarations of the required fields (there may not be any of these either).

    -
  • -
  • -

    Any identifier that begins with an uppercase or lowercase letter and which does not contain references to a namespace can be a field (variable) identifier. Using uc-ident for identifiers of variable types and lc-indent for other variables is good practice.

    -
  • -
  • -

    Next a combinator declaration contains the equals sign (=) and the result type (it may be composite or appearing for the first time). The result type may be polymorphic and/or dependent; any fields of the defined constructor’s fields of type Type or # may be returned (as subexpressions).

    -
  • -
  • -

    A combinator declaration is terminated with a semicolon.

    -
  • -
-

In what follows, a constructor’s fields, variables, and arguments mean the same thing.

-

Optional field declarations

-
    -
  • -

    These have the form { field_1 ... field_k : type-expr }, where field_i is a variable (field) identifier that is unique within the scope of the combinator declaration, and type-expr is a type shared by all of the fields.

    -
  • -
  • -

    If k>1, this entry is functionally equivalent to { field_1 : type-expr } ... { field_k : type-expr }.

    -
  • -
  • -

    All optional fields must be explicitly named (using _ instead of field_i is not allowed).

    -
  • -
  • -

    Moreover, at present the names of all optional fields must share the combinator’s result type (possibly more than once) and themselves be of type # (i,e., nat) or Type. Therefore, if the exact result type is known, it is possible to determine the values of all of the combinator’s implicit parameters (possibly obtaining a contradiction of the form 2=3 in doing so, which means that the combinator is not allowed in the context).

    -
  • -
-

Required field declarations

-
    -
  • -

    These may have the form ( field_1 ... field_k : type-expr ), similar to an optional field declaration, but with parentheses. This entry is equivalent to ( field_1 : type-expr ) ... ( field_k : type-expr ), where the fields are defined one at a time.

    -
  • -
  • -

    The underscore sign (_) can be used as names of one or more fields (field_i), indicating that the field is anonymous (the exact name is unimportant).

    -
  • -
  • -

    One field may be declared without outer parentheses, like this: field_id : type-expr. Here, however, if type-expr is a complex type, parentheses may be necessary around type-expr (this is reflected in BNF).

    -
  • -
  • -

    Furthermore, one anonymous field may be declared using a type-expr entry, functionally equivalent to _ : type-expr.

    -
  • -
  • -

    Required field declarations follow one after another, separated by spaces (by any number of whitespace symbols, to be more precise).

    -
  • -
  • -

    The declared field’s type (type-expr) may use the declared combinator’s previously defined variables (fields) as subexpressions (i.e. parameter values). For example:

    -

    nil {X:Type} = List X; -cons {X:Type} hd:X tl:(list X) = List X; -typed_list (X:Type) (l : list X) = TypedList;

    -
  • -
-

Repetitions

-
    -
  • -

    These may only exist among required parameters. They have the form [ field-id : ] [ multiplicity * ] [ args ], where args has the same format as the combinator’s declaration of (several) required fields, except that all of the enclosing combinator’s previously declared fields may be used in the argument types.

    -
  • -
  • -

    The name of a field of an enclosing combinator that receives a repetition as a value may be specified (field-id), or bypassed, which is equivalent to using the underscore sign as a field-id.

    -
  • -
  • -

    The multiplicity field is an expression of the type # (nat), which can be a real constant, the name of a preceding field of type #, or an expression in the form ( c + v ), where c is a real constant and v is the name of a field of type #. The sense of the multiplicity field is to provide the length of the (repetition) vector, each element of which consists of values of the types enumerated in args.

    -
  • -
  • -

    The multiplicity field may be bypassed. In this case, the last preceding parameter of type # from the enclosing combinator is used (it must be).

    -
  • -
  • -

    Functionally, the repetition field-id : multiplicity * [ args ] is equivalent to the declaration of the single field ( field-id : %Tuple %AuxType multiplicity ), where aux_type is an auxiliary type with a new name defined as aux_type *args* = AuxType. If any of the enclosing type’s fields are used within args, they are added to the auxiliary constructor aux_type and to its AuxType result type as the first (optional) parameters.

    -
  • -
  • -

    If args consists of one anonymous field of type some-type, then some-type can be used directly instead of %AuxType.

    -
  • -
  • -

    If during implementation the repetitions are rewritten as indicated above, it is logical to use instead of aux_type and AuxType, some identifiers that contain the name of the outer combinator being defined and the repetition’s index number inside its definition.

    -
  • -
-

Example:

-
matrix {m n : #} a : m* [ n* [ double ] ] = Matrix m n;
-

is functionally equivalent to

-
aux_type {n : #} (_ : %Tuple double n) = AuxType n;
-matrix {m : #} {n : #} (a : %Tuple %(AuxType n) m) = Matrix m n;
-

Moreover, the built-in types Tuple and Vector could be defined as:

-
tnil {X : Type} = Tuple X 0;
-tcons {X : Type} {n : #} hd:X tl:%(Tuple X n) = Tuple X (S n);
-vector {X : Type} (n : #) (v : %(Tuple X n)) = Vector X;
-

Actually, the following equivalent entry is considered the definition of Vector (i.e. it is specifically this entry that is used to compute the name of the vector constructor and its partial applications):

-
vector {t : Type} # [ t ] = Vector t;
-

If we expand it using Tuple, we obtain the previous definition exactly.

-

Conditional fields

-

The construction

-
-

args ::= var-ident-opt : [ conditional-arg-def ] [ ! ] type-term
-conditional-arg-def ::= var-ident [ . nat-const ] ?

-
-

permits assigning fields which are only present if the value of a preceding mandatory or optional field of type # is not null (or if its chosen bit is not zero if the special binary bit-selection operator . is applied). -Example:

-
-

user {fields:#} id:int first_name:(fields.0?string) last_name:(fields.1?string) friends:(fields.2?%(Vector int)) = User fields;
-get_users req_fields:# ids:%(Vector int) = Vector %(User req_fields)

-
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/mtproto/TL-dependent.html b/data/corefork.telegram.org/mtproto/TL-dependent.html deleted file mode 100644 index bb1c22e608..0000000000 --- a/data/corefork.telegram.org/mtproto/TL-dependent.html +++ /dev/null @@ -1,236 +0,0 @@ - - - - - TL-dependent - - - - - - - - - - - - - -
- -
-
-
- -

TL-dependent

- -

Main article: TL Language.

-

In certain cases, types may depend not only on other types (polymorphism), but also on the parameters of another type (dependent types). The TL language provides very limited support for this functionality: dependence is only allowed on a natural parameter whose type is designated using # (alias nat, but this is private -- TL doesn’t currently support this synonym). Values of type # are serialized as 32-bit signed numbers from 0 to 2^31-1.

-

Example: integer tuples (vectors)

-

Suppose we want to use induction to define the types “one integer”, “two integers”, and “three integers”. We could try to define them as follows:

-
empty = Empty;
-single x:int = Single;
-pair x:int y:int = Pair;
-triple x:int y:int z:int = Triple;
-quadruple x:int y:int z:int t:int = Quadruple;
-...
-

or as:

-
empty = Empty;
-single x:int empty = Single;
-pair x:int y:single = Pair;
-triple x:int yz:pair = Triple;
-quadruple x:int yzt:triple = Quadruple;
-

or as:

-
tnil = Tuple0;
-tcons0 hd:int tl:Tuple0 = Tuple1;
-tcons1 hd:int tl:Tuple1 = Tuple2;
-tcons2 hd:int tl:Tuple2 = Tuple3;
-...
-tcons_n hd:int tl:Tuple_n = Tuple_(n+1)
-

The first two variations lead to the same serialization. For example, (2 3 9):%triple and (2 (3 9)):%triple serialize as three 32-bit numbers: 2 3 9. The last variation better emphasizes the inductive version of the definition, but it uses boxed types. This is good from a theoretical perspective, but it leads to “superfluous” constructor names in serialization.

-

Therefore, we will write %Type-Ident to indicate the bare type that corresponds to the boxed type Type-Ident with a single constructor. If this constructor is named constructor, then according to the definition %Type-Ident = %constructor. Now we can write our definition like this:

-
tnil = Tuple0;
-tcons_n hd:int tl:%Tuple_n = Tuple_(n+1)
-

If we now abstract n out of the name of the type name and make it like a parameter for a polymorphic (dependent, to be more exact) type, then something like the following can be written in a suitable functional language:

-
NewType Tuple (n : #) :=
-| tnil = Tuple 0
-| tcons n:# hd:int tl:%(Tuple n) = Tuple (S n)
-EndType;
-

In the TL language, it looks like this:

-
tnil = Tuple 0;
-tcons {n:#} hd:int tl:%(Tuple n) = Tuple (S n);
-

The function S : # -> # and the constant O : # (it is 0) are the function for the next natural number (S n = n + 1) and the constant null. Therefore, the type # (alias nat) behaves as if it were defined in TL using the constructors

-
O = nat;
-S nat = nat;
-

or, using syntax more typical of other functional languages,

-
NewType nat :=
-| O
-| S nat
-EndType;
-

Types of all defined combinators:

-
O : #
-S : # -> #
-Tuple : # -> Type
-tnil : Tuple 0
-tcons : forall n : #, int -> Tuple n -> Tuple (S n)
-

or

-
Tuple : forall n : #, Type;
-tcons : forall n : #, forall hd : int, forall tl : Tuple n, Tuple (S n)
-

Note that in this case the constructor tnil does not depend on the parameter n, while tcons does.

-

In an analogous manner, it is possible to define a complete binary tree of height h with strings in the leaf nodes:

-
tleaf value:string = BinTree 0;
-tnode {h:#} left:(BinTree h) right:(BinTree h) = BinTree (S h);
-

Or a random tree whose leaf nodes are all a distance of h from the root and whose nodes are all labeled with integers:

-
hleaf value:int = Tree 0;
-hnode {n:#} left:(Tree n) next:(Tree (S n)) = Tree (S n)
-hnil {n:#} = Tree (S n)
-

Another version:

-
hleaf' value:int = Tree' 0;
-hnode' {n:#} children:(list (Tree' n)) = Tree' (S n)
-

Polymorphic dependent types

-

Let us try to define a type Tuple X n whose values are n-tuples of type X values. In this way, Tuple will be simultaneously polymorphic and dependent:

-
Tuple : Type -> # -> Type;
-

In the familiar syntax of functional languages:

-
NewType Tuple {X : Type} {n : #} :=
-| vnil : Tuple X 0
-| vcons {n:#} hd:X tl:%(Tuple X n) : Tuple X (S n)
-EndType
-

or, in TL syntax,

-
vnil {X:Type} = Tuple X 0;
-vcons {X:Type} {n:#} tl:(%Tuple X n) = Tuple X S n
-

In the end we obtain terms for the following types:

-
vnil : forall X : Type, Tuple X 0
-vcons : forall X : Type, forall n : #, X -> Tuple X n -> Tuple X (S n)
-

or

-
vnil : forall X : Type, Tuple X 0
-vcons : forall X : Type, forall n : #, forall hd : X, forall tl : Tuple X n, Tuple X (S n)
-

Dependent sums

-

The Tuple we just defined differs from the built-in Vector type. Specifically, the Vector type formally depends on a single argument (a type), but our Tuple depends on two (a type and a number):

-
Tuple : Type -> # -> Type;
-Vector : Type -> Type;
-

The built-in Vector could be defined in terms of our Tuple using “summing across all n : #":

-
vector {X:Type} n:# v:(%Tuple X n) = Vector X;
-

Nevertheless, our Tuple has its advantages. For example, we can define data types such as:

-
matrix_10x10 a:(%Tuple (%Tuple double 10) 10) = Matrix_10x10;
-

In any event, remember that during calculation of the matrix_10x10 combinator’s number, all parentheses must be removed and the CRC32 of the string matrix_10x10 a:%Tuple %Tuple double 10 10 = Matrix_10x10 must be computed.

-

Moreover, we can define arbitrarily-sized matrices:

-
matrix {X:Type} m:# n:# a:(%Tuple (%Tuple X m) n) = Matrix X;
-

In this case using vector would result in storing the length of a row (m) in each row, e.g. n times.

-

Note that the serializations of values of type %Tuple X n and vector X (also known as %vector X and %Vector X) nearly match when n > 0: in both cases we obtain a single 32-bit number (equal to n-1 or n depending on the version) followed by the serializations of n objects of type X. (This is slightly untrue: values of type %Tuple X n can only be serialized if n is a constant or value known from one of the preceding fields of the enclosing entry; but then this n won’t be serialized explicitly anywhere).

-

Special syntax for repetitions

-

In view of the importance of the construction presented above, it is built into the TL language in the following manner. A substructure in the form of [ array-field-name ":" ] [ nat-ident "" ] "[" field-descr ... "]” may be used in the declaration of any combinator, where nat-ident* is the name of any previously encountered field of type # (if it is not explicitly indicated, the most recent is used). In abstract, this substructure is equivalent to:

-
aux_type *field-descr* ... = AuxType;
-*current_constructor* ... [ *array-field-name* ":" ] (%Tuple aux_type *nat-ident*)
-

For example, 10x10 matrices, vectors, and arbitrary matrices may be defined in the following way:

-
matrix {X:Type} m:# n:# a:n*[ m*[ X ] ] = Matrix X;
-matrix_10x10 a:10*[ 10*[ double ]] = Matrix_10x10;
-vector {X:Type} # [ X ] = Vector X;
-

We have already encountered the last version as a “definition” of the “built-in type” Vector.

-

Of course, several fields, as complex as desired, may be within the repeating part. Furthermore, besides using n as a repeat counter, one may use expressions of the form (n+const) and (const+n), where const is a small nonnegative constant, which are shorthand for S (S ( ... (S n) ... )):

-
repeat_np1 n:# a:(S n)*[ key:string value:string ] = Dictionary;
-

To calculate the CRC32 these expressions are converted to expressions of the form (const+X) without internal spaces. Additionally, the * in this case is not set off by spaces on the left and right.

-

Serialization of dependent types

-

Serialization of dependent types and polymorphic types is not a fundamental challenge: we have combinators with non-zero arity with Type values. For example, the type Tuple double 10 : Type serializes to 'Tuple' '%double' 10. Note that at present in practice there is virtually no need to serialize types, whether dependent or not.

-

Optional combinator parameters in TL

-

Optional combinator parameters in TL must possess the following properties:

-
    -
  • -

    Optional parameters must be precisely ythe combinator’s first several arguments;

    -
  • -
  • -

    The value of any optional parameter must be entirely determined by the combinator’s result type.

    -
  • -
-

For example, in cons {X:Type} hd:X tl:(list X) = list X the parameter X may be made optional, because it is located at the very beginning of the argument list and is unambiguously determined by the list X result type. Similarly, in tcons {X:Type} {n:#} hd:X tl:(%Tuple X n) = Tuple X (S n) the values of X and n are completely determined based on the Tuple X (S n) result type, therefore they made be made optional parameters.

-

It usually makes sense to move all of a constructor’s arguments satisfying the second condition to the beginning of the list, arrange them in the order they appear in the result type’s parameters, and make them optional. Given such an approach, the full version of a constructor is rarely needed -- only when we want to transmit the value of the polymorphic or dependent type as a value of type Object. In all other cases, the type of the expected value from the context is already known, which means that all optional parameters can be recovered during decomposition.

-

See also Optional combinator parameters and their values.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/mtproto/TL-formal.html b/data/corefork.telegram.org/mtproto/TL-formal.html deleted file mode 100644 index 1bccc7538d..0000000000 --- a/data/corefork.telegram.org/mtproto/TL-formal.html +++ /dev/null @@ -1,319 +0,0 @@ - - - - - TL-formal - - - - - - - - - - - - - -
- -
-
-
- -

TL-formal

- -

See also TL Language. -For the syntax of declaring combinators, see in article Formal declaration of TL combinators. -For the syntax of patterns, see in article Formal declaration of TL patterns.

-

Tokens

-

Comments are the same as in C/C++. They are removed by a lexical parser (for example, being replaced by a single space). Whitespace separates tokens. Except for string constants, tokens cannot contain spaces.

-

Character classes:

-
-

lc-letter ::= a | b | ... | z
-uc-letter ::= A | B | ... | Z
-digit ::= 0 | 1 | ... | 9
-hex-digit ::= digit | a | b | c | d | e | f
-underscore ::= _
-letter ::= lc-letter | uc-letter
-ident-char ::= letter | digit | underscore

-
-

Simple identifiers and keywords:

-
-

lc-ident ::= lc-letter { ident-char }
-uc-ident ::= uc-letter { ident-char }
-namespace-ident ::= lc-ident
-lc-ident-ns ::= [ namespace-ident . ] lc-ident
-uc-ident-ns ::= [ namespace-ident . ] uc-ident
-lc-ident-full ::= lc-ident-ns [ # hex-digit *8 ]

-
-

Tokens:

-
-

underscore ::= _
-colon ::= :
-semicolon ::= ;
-open-par ::= (
-close-par ::= )
-open-bracket ::= [
-close-bracket ::= ]
-open-brace ::= {
-close-brace ::= }
-triple-minus ::= ---
-nat-const ::= digit { digit }
-lc-ident-full
-lc-ident
-uc-ident-ns
-equals ::= =
-hash ::= #
-question-mark ::= ?
-percent ::= %
-plus ::= +
-langle ::= <
-rangle ::= >
-comma ::= ,
-dot ::= .
-asterisk ::= *
-excl-mark ::= !
-Final-kw ::= Final
-New-kw ::= New
-Empty-kw ::= Empty

-
-

Final is a reserved keyword, e.g. a special token. Words like Type are not keywords, rather they are identifiers with preset values.

-

Tokens consisting of one or more constant symbols shall be hereafter denoted using terms in quotation marks (for example, --- replaces triple-minus).

-

Syntax

-

General syntax of a TL program

-

Syntactically, a TL program consists of a stream of tokens (separated by spaces, which are ignored at this stage). General program structure:

-
-

TL-program ::= constr-declarations { --- functions --- fun-declarations | --- types --- constr-declarations }

-
-

Here the constructor- and function declarations are nearly identical in their syntax (they are both combinators):

-
-

constr-declarations ::= { declaration }
-fun-declarations ::= { declaration }

-
-

There are various declarations:

-
-

declaration ::= combinator-decl | partial-app-decl | final-decl

-
-

Before explaining how declarations of combinators, partial applications, and type finalization are given, we will introduce additional syntactical categories:

-

Syntactical categories and constructions

-

The concept of an expression (expr) is important. There are type expressions (type-expr) and numeric expressions (nat-expr). However, they are defined the same way. Their correctness as type- or numeric expressions is checked when the type of the analyzed expression is checked.

-
-

type-expr ::= expr
-nat-expr ::= expr
-expr ::= { subexpr }
-subexpr ::= term | nat-const + subexpr | subexpr + nat-const
-term ::= ( expr ) | type-ident | var-ident | nat-const | % term | type-ident < expr { , expr } >
-type-ident ::= boxed-type-ident | lc-ident-ns | #
-boxed-type-ident ::= uc-ident-ns
-var-ident ::= lc-ident | uc-ident
-type-term ::= term
-nat-term ::= term

-
-

Note that writing E = E_1 E_2 ... E_n in the expression for expr means applying the function E_1 to the argument E_2, applying the result to E_3, etc. Specifically, E_1 E_2 E_3 = (E_1 E_2) E_3. A solitary # is included in type-ident, because it is actually the identifier for a built-in type (# alias nat).

-

The expression E<E_1,...,E_n> is syntactic sugar for (E (E_1) ... (E_n)), i.e. both expressions are transformed into the same internal representation.

-

Combinator declarations

-
-

combinator-decl ::= full-combinator-id { opt-args } { args } = result-type ;
-full-combinator-id ::= lc-ident-full | _
-combinator-id ::= lc-ident-ns | _
-opt-args ::= { var-ident { var-ident } : [excl-mark] type-expr }
-args ::= var-ident-opt : [ conditional-def ] [ ! ] type-term
-args ::= [ var-ident-opt : ] [ multiplicity *] [ { args } ]
-args ::= ( var-ident-opt { var-ident-opt } : [!] type-term )
-args ::= [ ! ] type-term
-multiplicity ::= nat-term
-var-ident-opt ::= var-ident | _
-conditional-def ::= var-ident [ . nat-const ] ?
-result-type ::= boxed-type-ident { subexpr }
-result-type ::= boxed-type-ident < subexpr { , subexpr } >

-
-

See Formal declaration of TL combinators for a description of what exactly this means. Here we will only note that when declaring the type of a combinator’s next argument, only the names of previously arranged (more to the left) arguments of the same combinator may be used as variables, but when declaring the result type you can use all of its parameters (of type Type and #).

-

Note that the names of combinators declared in this way may be used in TL itself only as the corresponding bare types. The only combinators that appear in declarations are built-in: O : # and S : # -> #.

-

There are also “pseudo-declarations” that are allowed only to declare built-in types (such as int ? = Int;):

-
-

builtin-combinator-decl ::= full-combinator-id ? = boxed-type-ident ;

-
-

Partial applications (patterns)

-
-

partial-app-decl ::= partial-type-app-decl | partial-comb-app-decl
-partial-type-app-decl ::= boxed-type-ident subexpr { subexpr } ; | boxed-type-ident < expr { , expr } > ;
-partial-comb-app-decl ::= combinator-id subexpr { subexpr } ;

-
-

See Formal declaration of TL patterns.

-

Type finalization

-
-

final-decl ::= New boxed-type-ident ; | Final boxed-type-ident ; | Empty boxed-type-ident ;

-
-

This type of declaration means that there must not be any constructor for the indicated type: before the declaration for New and after the declaration for Final. The keyword Empty enables both effects.

-

Predefined identifiers

-

Nearly all predefined identifiers may be given using the following schema (usually located in common.tl):

-
-

/////
-//
-// Common Types
-//
-/////

-

// Built-in types
-int ? = Int;
-long ? = Long;
-double ? = Double;
-string ? = String;

-

// Boolean emulation
-boolFalse = Bool;
-boolTrue = Bool;

-

// Boolean for diagonal queries
-boolStat statTrue:int statFalse:int statUnknown:int = BoolStat;

-

// Vector
-vector {t:Type} # [t] = Vector t;
-tuple {t:Type} {n:#} [t] = Tuple t n;
-vectorTotal {t:Type} total_count:int vector:%(Vector t) = VectorTotal t;

-

/////
-//
-// Result- (Maybe-) types
-//
-/////

-

resultFalse {t:Type} = Maybe t;
-resultTrue {t:Type} result:t = Maybe t;

-

pair {X:Type} {Y:Type} a:X b:Y = Pair X Y;
-map {X:Type} {Y:Type} key:X value:Y = Map X Y;

-

Empty False;
-true = True;

-

unit = Unit;

-
-
    -
  • -

    Predefined identifier Type: This type signifies the type of all types. It is usually used to specify the types of optional parameters in the constructors of polymorphic types. If strongly desired, it can be used in its own right, but this is very rarely needed in practice.

    -
  • -
  • -

    Identifier #: This type is used to specify a special type of nonnegative integers in the range from 0 to 2^31-1; its main purpose is the same as that of Type. There are two built-in constructors: O : # and S : # -> # (“null” and “next number”, respectively), which work as if # was defined using the schema

    -
  • -
-
-

O = #;
-S # = #;

-
-
    -
  • -

    Identifier Tuple: Type -> # -> Type denotes a set of the specified number of values of the indicated type. In other words, Tuple X n means “a set of n values of type X".

    -
  • -
  • -

    The typeBool, with two constructors boolTrue and boolFalse, is used to transmit Boolean values.

    -
  • -
  • -

    The constructor-less type False may be used instead of undeclared or invalid types in the construction of a TL schema, because any attempt to (de)serialize a value of type False will produce an error. Usage Example:

    -
  • -
-
-

user {flags:#} id:flags.0?string first_name:flags.1?string last_name:flags.2?string reserved3:flags.3?False reserved4:flags.4?False = User flags;
-user_present {flags:#} info:%(User flags) = UserInfo flags;
-user_absent {flags:#} = UserInfo flags;
-getUser flags:# id:int = !UserInfo flags;

-
-

In the future, bits 3 and 4 in the flags field may be used to transmit new fields after changing the names and types of the reserved3 and reserved4 fields. This will change the user constructor’s number, but this isn’t too important, since the User flags type is only used as a bare type. Transmitting bits 3 or 4 in the flags field in a getUser query before these fields have actually been defined will lead to an error in the (de)serialization of the request.

-
    -
  • The type True with a single null constructor true plays a role similar to the void type in C/C++. It is especially useful as a bare type %True, alias true, because its serialization has zero length. For example, the first_name:flags.1?string constructor used above is in fact shorthand for (the as-yet unsupported) alternative-type general constructor first_name:(flags.1?string:true).
  • -
-

When directly used in a conditional field it may simply indicate the presence (absence) of a certain parameter with void type. -If the conditional field exists, the associated parameter will not be populated; the conditional field simply exists and the existance value can be used to perform certain operations, example:

-
user {flags:#} id:flags.0?string first_name:flags.1?string last_name:flags.2?string bot:flags.3?true reserved4:flags.4?False = User flags;
-

If bit 3 of the flags parameter isn't set, the user is a normal user. -If bit 3 of the flags parameter is set, this indicates that the specified user is a bot: however, during deserialization, the bot parameter must not be assigned any value, since true is actually a void type.

-
    -
  • The typeUnit with a single null constructor Unit is similar to the previous type.
  • -
-

ANTLR definition

-

An ANLTR definition of TL grammar can be found here ».

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/mtproto/TL-optargs.html b/data/corefork.telegram.org/mtproto/TL-optargs.html deleted file mode 100644 index 8aa55122a6..0000000000 --- a/data/corefork.telegram.org/mtproto/TL-optargs.html +++ /dev/null @@ -1,151 +0,0 @@ - - - - - Optional combinator parameters and their values - - - - - - - - - - - - - -
- -
-
-
- -

Optional combinator parameters and their values

- -

TL Language makes it possible to declare a combinator’s first few parameters optional. Subsequently, they are almost never required to be explicitly stated. This is directly related to another important property of TL: polymorphism.

-

All optional parameters are typically required to be part of the result type (at least once).

-

A (sub)expression may be serialized/deserialized in one of two ways:

-
    -
  • -

    The result type is known (for example, we’re parsing the response to a previously sent RPC query and therefore know the value of some type is expected). In this case, the result type may be used to determine the values of the combinator’s implicit parameters.

    -
  • -
  • -

    The result type is not known. It is determined as a result of (de)serialization (for example, we are serializing an RPC query). In this case, it is necessary to explicitly specify (and serialize) all of the combinator’s optional parameters by using the full version of the combinator.

    -
  • -
-

We will assume that the functional combinator only differs from the constructor in that before its result type the ! modifier is implicitly added, and the (remote or local) computation of a functional expression may be presented as the execution of some polymorphic function eval : !X -> X.

-

Moreover, the unknown result type is obviously usually (but not always) bound to the serialization of an expression whose type has been modified by !.

-

We can formulate the following rules. Let there be some constructor

-
C {a1:T1} ... {am:Tm} b1:U1 ... bn:Un = T;
-

Some of its arguments or its result may be marked with the ! modifier (We consider a functional combinator to be a constructor whose result type has been modified by an implicit !).

-

The following conditions must hold:

-
    -
  • -

    Each type T1, ..., Tm, U1, ..., Un, and T may depend on parameters of type Type or #, which have been declared to the left of the use of the given type.

    -
  • -
  • -

    The types of implicit parameters T1, ..., Tm may not be modified by !.

    -
  • -
  • -

    Only implicit parameters of type Type or # are allowed. In other words, Ti is either a Type or a #. (Unlike the previous rule, this rule may be relaxed in the future.)

    -
  • -
  • -

    Each implicit parameter a1, ..., am must be used at least once -- either within one of the Ui types that have a !, or in the result type T, if it does not have an explicit or implicit !.

    -
  • -
  • -

    If an implicit parameter ai is not used in the result type, or if the result type has a !, then its first (leftmost) usage must be within a type Uj that is modified by !.

    -
  • -
-

The idea is this: we assume that during (de)serialization of a value of a type modified by ! that we do not know this type in advance and we will find out what it is only based on the result of the (de)serialization; Conversely, we assume that during (de)serialization of a value of a type that is not modified by ! that we know this type in advance. In this case, complying with the rules stated above lets us always compute the values of all implicit parameters -- either from the (previously known) result type or from the type of one of the bj:!Uj parameters (which was obtained during the serialization process).

-

In fact, ! denotes the direction in which type information is flowing. By default, the result type is the source of information about types (and their parameters), while argument types are the recipients of that information. The use of ! reverses the direction of information flow, making the result type the recipient and the argument type the source of type information.

-

See also Binary serialization and abstract TL types and Polymorphism in TL.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/mtproto/TL-patterns.html b/data/corefork.telegram.org/mtproto/TL-patterns.html deleted file mode 100644 index a3ef5eb43e..0000000000 --- a/data/corefork.telegram.org/mtproto/TL-patterns.html +++ /dev/null @@ -1,129 +0,0 @@ - - - - - TL-patterns - - - - - - - - - - - - - -
- -
-
-
- -

TL-patterns

- -
-

partial-app-decl ::= partial-type-app-decl | partial-comb-app-decl
-partial-type-app-decl ::= boxed-type-ident subexpr { subexpr } ; | boxed-type-ident < expr { , expr } > ;
-partial-comb-app-decl ::= combinator-id subexpr { subexpr } ;

-
-

According to the original design, templates must be used to replace concrete values in the first few or all of the optional arguments of a constructor or polymorphic type. For example, if Tuple int 10 is used frequently, you can declare a template for it, which will cause the appropriate constructors to be generated automatically. When using such a constructor there may be nowhere to pass an int type or the tuple size 10. Similarly, it was originally planned to declared templates for Vector int, Vector string, etc. in order to generate constructors for each vector type being used type. These constructors would make it possible during deserialization to determine what kind of array is being transmitted.

-

Templates are not used now. Instead, the same universal constructors (for example, vector {t:Type} [t] = Vector t) are used with the values of the optional parameters being inferred from the type of the result (if we already know from the schema that in this location there must be a Vector int during deserialization, we understand that we will see the universal vector constructor in which t is equal to int).

-

This approach is better in that it is not necessary to define Vector SomeType templates in advance for all possible types in order to generate their own constructors for each of these cases. Nevertheless, there is a drawback. If someone wants to transmit the serialization of a value of the clothed type Vector int as a serialization of a value of type Object, a problem arises during serialization: after seeing the universal vector constructor and then reading the vector length, we cannot determine what type of values should be expected next.

-

In theory, this problem can be solved by using the full form of the constructor (@vector) corresponding to vector (it is automatically defined and is different in that all of the optional parameters become required), or by defining

-
-

object X:Type X = TypedObject

-
-

and passing the object type explicitly. Type serialization is required in both cases.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/mtproto/TL-polymorph.html b/data/corefork.telegram.org/mtproto/TL-polymorph.html deleted file mode 100644 index 658321fb15..0000000000 --- a/data/corefork.telegram.org/mtproto/TL-polymorph.html +++ /dev/null @@ -1,170 +0,0 @@ - - - - - Polymorphism in TL - - - - - - - - - - - - - -
- -
-
-
- -

Polymorphism in TL

- -

It should be noted that in the TL schema of the overwhelming majority of API calls the use of polymorphic types is restricted to the Vector type. Nevertheless, having a view of the big picture is still helpful.

-

Ordinary inductive types

-

For example, let us consider the IntList, which is defined as follows:

-
int_cons hd:int tl:IntList = IntList;
-int_nil = IntList;
-

The “int_cons” and “int_nil” constructors as well as the “IntList” type itself are expressions of the following types (writing A : X means that A is an expression of type X):

-
IntList : Type;
-int_cons : int -> IntList -> IntList;
-int_nil : IntList;
-

The keyword Type is used to denote the type of all types. Note that Type is not Object (Object is the type of all terms). -Here is alternative syntax that could be used in some other functional programming language (but not in TL):

-
NewType IntList :=
-| int_cons hd:int tl:IntList
-| int_nil
-EndType
-

Polymorphic type

-

TL supports the following version (curly brackets indicate optional fields, see below):

-
cons {X:Type} hd:X tl:(List X) = List X;
-nil {X:Type} = List X
-

Here is an alternative formulation in other functional languages with dependent types:

-
NewType List {X:Type} :=
-| cons {X:Type} hd:X tl:(List X)
-| nil {X:Type}
-EndType
-

In any event, these variations are equivalent to one another from the point of view of the formal theory of types and lead to the definition of the following terms:

-
List : Type -> Type;
-cons : forall (X:Type), X -> List X -> List X;
-nil : forall (X:Type), X -> List X;
-

In each case, remember that writing “A -> B” is shorthand for “forall (x : A), B” for any variable x not entering into A and B. For example, the “cons” type could be written as follows:

-
cons : forall (X:Type), forall (hd : X), forall (tl : List X), List X
-

or more compactly:

-
cons : forall (X : Type) (hd : X) (tl : List X), List X
-

See Calculus of constructions. Examples of functional languages with dependent types, which support similar constructions are Coq and Agda.

-

In this case, the entry after a universal quantifier proves to be more content-related than that after an arrow, because the name of a variable bound by the quantifier is used to transmit the name of the corresponding field in the constructor, even if this variable is not used anywhere as it pertains to the expression under the quantifier. Structurally, all of these entries of the “cons” type are equivalent.

-

Serialization of types (values of type Type)

-

As we can see, to serialize a value of type List X, which has been obtained by applying the combinator “cons X:Type hd:X tl:(List X) = List X”, we need to:

-
    -
  1. serialize the name of the “cons” combinator into a 32-bit number;
  2. -
  3. serialize X (as a type, i.e. as a value of type Type) if X is a required parameter;
  4. -
  5. serialize the head of the list (hd) as a value of type X;
  6. -
  7. serialize the tail of the list as a value of the polymorphic type List X.
  8. -
-

In the first step, the natural question is which string exactly will be used to calculate the CRC32. It is proposed to take "cons X:Type hd:X tl:List X = List X” without the terminating semicolon and without any parentheses (closed type expressions are unambiguously reconstructed based on their construction’s prefix).

-

In the last step, we recursively resolve the very same problem of serializing a value of type List X; we will consider it resolved based on the assumption of induction in the construction of the value being serialized. We will similarly consider the third step understandable (induction in the construction of the value being serialized).

-

We still need to describe how to transmit (serialize) types, e.g. values of type Type. Types in TL schemas currently appear only as constructors’ optional parameters and are therefore never serialized explicitly. Rather, their values are inferred from the previously known type of the value being serialized.

-

For completeness we will describe how it would be possible to serialize types (values of type Type). However, keep in mind that for now this information is not useful. See Type serialization.

-

Optional arguments in polymorphic constructors

-

It was stated above that any subset of (the first few) parameters of any constructor can be identified as optional (by enclosing their declarations in curly brackets), but this is not actually entirely accurate. First, these optional parameters can only be of type Type or # (natural numbers). Second, optional parameters must share the return value’s type, otherwise their value cannot be determined.

-

Note that @'''constr-id''' means the constructor’s “full form” (in which all optional parameters become required), while '''constr-id'’ denotes its abbreviated form (without the optional arguments). If there are no optional arguments, then these two forms are the same. Constructors’ full forms are never used at present.

-

Bare polymorphic types

-

There is a small problem: if we want to serialize the value of the bare type ‘%pair string int’ or ‘%pair string Y’ (which in TL is usually denoted simply as “pair”, though the form “%Pair” is preferable), we cannot simultaneously use both the full constructor @pair and the partial pair, because the constructor’s name will not be serialized. Therefore, we must differentiate the bare types %@pair (type X, type Y, value x:X, and value y:Y are serialized) and %pair (only x:X and y:Y are serialized; types X and Y are known from the context). In practice, we nearly almost always need the bare type %pair, and this is precisely what “pair” means in the type’s context in TL. Therefore,

-
record name:string map:(List (pair int string)) = Record;
-

will be serialized approximately like we want it to be (the serialization of list elements will consist of the serialization of int and the serialization of string, without any additional headers, types, or combinator names). -Incidentally, when calculating the “record” combinator’s name 'record' in the example given above, the CRC32 of record name:string map:List pair int string = Record will be computed.

-

Also note that a more precise description of this type would be

-
record name:string map:(List %(Pair int string)) = Record
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/mtproto/TL-tl.html b/data/corefork.telegram.org/mtproto/TL-tl.html deleted file mode 100644 index 6eb37b1df6..0000000000 --- a/data/corefork.telegram.org/mtproto/TL-tl.html +++ /dev/null @@ -1,308 +0,0 @@ - - - - - TL schema for serialization of TL schemas - - - - - - - - - - - - - -
- -
-
-
- -

TL schema for serialization of TL schemas

- -

If necessary, a TL schema can be serialized in binary form. Here, this serialization format is defined by a TL schema (usually stored in the file tl.tl). This can be useful, for example, to make it possible to write a parser one time for converting a TL schema from text form (stored in the file something.tl) to binary form (stored in the file something.tlo). All other programs (for example, auto-generators of TL-(de)serializers for various programming languages) only need to know how to read .tlo files, which only requires generating an automatic deserializer according to the schema presented below.

-

First, a fragment of the file common.tl with certain required built-in types:

-
/////
-//
-// Common Types (source file common.tl, only necessary definitions included)
-//
-/////
-
-// Built-in types
-int ? = Int;
-long ? = Long;
-double ? = Double;
-string ? = String;
-
-// Boolean emulation
-boolFalse = Bool;
-boolTrue = Bool;
-
-// Vector
-vector {t:Type} # [t] = Vector t;
-tuple {t:Type} {n:#} [t] = Tuple t n;
-vectorTotal {t:Type} total_count:int vector:%(Vector t) = VectorTotal t;
-
-Empty False;
-true = True;
-

Next, properly, comes tl.tl itself. Note that the declaration for a fairly complex data type required only twenty lines in TL. This demonstrates the expressiveness and compactness of the TL language.

-
/////
-//
-// Serialized binary TL-schema in TL format, source file tl.tl
-//
-/////
-tls.schema_v2 version:int date:int types_num:# types:types_num*[tls.Type] 
-
-    constructor_num:# constructors:constructor_num*[tls.Combinator] 
-    functions_num:# functions:functions_num*[tls.Combinator] = tls.Schema;
-tls.type name:int id:string constructors_num:int flags:int arity:int params_type:long = tls.Type;
-
-tls.combinator name:int id:string type_name:int left:tls.CombinatorLeft right:tls.CombinatorRight = tls.Combinator;
-tls.combinatorLeftBuiltin = tls.CombinatorLeft;
-tls.combinatorLeft args_num:# args:args_num*[tls.Arg] = tls.CombinatorLeft;
-tls.combinatorRight value:tls.TypeExpr = tls.CombinatorRight;
-
-tls.arg id:string flags:# var_num:flags.1?int exist_var_num:flags.2?int exist_var_bit:flags.2?int type:tls.TypeExpr = tls.Arg;
-
-tls.exprType _:tls.TypeExpr = tls.Expr;
-
-tls.exprNat _:tls.NatExpr = tls.Expr;
-tls.natConst value:int = tls.NatExpr;
-
-tls.natVar dif:int var_num:int = tls.NatExpr;
-tls.typeVar var_num:int flags:int = tls.TypeExpr;
-
-tls.array multiplicity:tls.NatExpr args_num:# args:args_num*[tls.Arg] = tls.TypeExpr;
-tls.typeExpr name:int flags:int children_num:# children:children_num*[tls.Expr] = tls.TypeExpr;
-

Remarks

-

Schema serialization (version 2) always begins with the index number of the tls.schema_v2 constructor for tls.Schema. -Because the CRC32 of the string

-
tls.schema_v2 version:int date:int types_num:# types:types_num*[ tls.Type ] constructor_num:# constructors:constructor_num*[ tls.Combinator ] functions_num:# functions:functions_num*[ tls.Combinator ] = tls.Schema
-

is 0x3a2f9be2, this constant is in fact the magic number for tlo files in the current version’s format. -If the format is extended in the future (for example, if TL’s additional features are supported), then a tls.schema_v3 constructor with a different number will appear.

-

Example

-

If one adds declarations for the used built-in types (like int ? = Int;) from the file common.tl before tl.tl and serialize the resulting schema, the following binary data is obtained (tl.tlo):

-
-

0000: 3a2f9be2 00000000 51fec698 00000015 12eb4386 70659eff 00002301 00000000
-0020: 00000000 00000000 00000000 00000000 12eb4386 250be282 6f6f4204 0000006c
-0040: 00000002 02000010 00000000 00000000 00000000 12eb4386 2210c154 756f4406
-0060: 00656c62 00000001 02000000 00000000 00000000 00000000 12eb4386 00000000
-0080: 6c614605 00006573 00000000 00000401 00000000 00000000 00000000 12eb4386
-00a0: a8509bda 746e4903 00000001 02000001 00000000 00000000 00000000 12eb4386
-00c0: 22076cba 6e6f4c04 00000067 00000001 02000001 00000000 00000000 00000000
-00e0: 12eb4386 b5286e24 72745306 00676e69 00000001 02000001 00000000 00000000
-0100: 00000000 12eb4386 3fedd339 75725404 00000065 00000001 02000000 00000000
-0120: 00000000 00000000 12eb4386 9770768a 70755405 0000656c 00000001 02000000
-0140: 00000002 00000002 00000000 12eb4386 2cecf817 70795404 00000065 00000000
-0160: 00000000 00000000 00000000 00000000 12eb4386 1cb5c415 63655606 00726f74
-0180: 00000001 02000008 00000001 00000000 00000000 12eb4386 10133f47 6365560b
-01a0: 54726f74 6c61746f 00000001 02000000 00000001 00000000 00000000 12eb4386
-01c0: 29dfe61b 736c7407 6772412e 00000001 02000000 00000000 00000000 00000000
-01e0: 12eb4386 5c0a1ed5 736c740e 6d6f432e 616e6962 00726f74 00000001 02000000
-0200: 00000000 00000000 00000000 12eb4386 8133d9ba 736c7412 6d6f432e 616e6962
-0220: 4c726f74 00746665 00000002 02000010 00000000 00000000 00000000 12eb4386
-0240: 2c064372 736c7413 6d6f432e 616e6962 52726f74 74686769 00000001 02000000
-0260: 00000000 00000000 00000000 12eb4386 307d41a0 736c7408 7078452e 00000072
-0280: 00000002 02000010 00000000 00000000 00000000 12eb4386 c2635441 736c740b
-02a0: 74614e2e 72707845 00000002 02000010 00000000 00000000 00000000 12eb4386
-02c0: 3a2f9be2 736c740a 6863532e 00616d65 00000001 02000000 00000000 00000000
-02e0: 00000000 12eb4386 12eb4386 736c7408 7079542e 00000065 00000001 02000000
-0300: 00000000 00000000 00000000 12eb4386 193fd378 736c740c 7079542e 70784565
-0320: 00000072 00000003 02000010 00000000 00000000 00000000 00000018 5c0a1ed5
-0340: bc799737 6f6f6209 6c61466c 00006573 250be282 4c12c6d9 00000000 2c064372
-0360: c1863d08 250be282 00000000 00000000 5c0a1ed5 997275b5 6f6f6208 7572546c
-0380: 00000065 250be282 4c12c6d9 00000000 2c064372 c1863d08 250be282 00000000
-03a0: 00000000 5c0a1ed5 2210c154 756f6406 00656c62 2210c154 cd211f63 2c064372
-03c0: c1863d08 2210c154 00000000 00000000 5c0a1ed5 a8509bda 746e6903 a8509bda
-03e0: cd211f63 2c064372 c1863d08 a8509bda 00000000 00000000 5c0a1ed5 22076cba
-0400: 6e6f6c04 00000067 22076cba cd211f63 2c064372 c1863d08 22076cba 00000000
-0420: 00000000 5c0a1ed5 b5286e24 72747306 00676e69 b5286e24 cd211f63 2c064372
-0440: c1863d08 b5286e24 00000000 00000000 5c0a1ed5 3fedd339 75727404 00000065
-0460: 3fedd339 4c12c6d9 00000000 2c064372 c1863d08 3fedd339 00000000 00000000
-0480: 5c0a1ed5 9770768a 70757405 0000656c 9770768a 4c12c6d9 00000003 29dfe61b
-04a0: 00007401 00020005 00000000 c1863d08 2cecf817 00000000 00000000 29dfe61b
-04c0: 00006e01 00020005 00000001 c1863d08 70659eff 00000000 00000000 29dfe61b
-04e0: 00000000 00000000 d9fb20de 4e8a14f0 00000000 00000001 00000001 29dfe61b
-0500: 00000000 00000000 0142ceae 00000000 00000000 2c064372 c1863d08 9770768a
-0520: 00000000 00000002 ecc9da78 0142ceae 00000000 00000000 dcb49bd8 4e8a14f0
-0540: 00000000 00000001 5c0a1ed5 1cb5c415 63657606 00726f74 1cb5c415 4c12c6d9
-0560: 00000003 29dfe61b 00007401 00020005 00000000 c1863d08 2cecf817 00000000
-0580: 00000000 29dfe61b 00000000 00000004 00000001 c1863d08 70659eff 00000000
-05a0: 00000000 29dfe61b 00000000 00000000 d9fb20de 4e8a14f0 00000000 00000001
-05c0: 00000001 29dfe61b 00000000 00000000 0142ceae 00000000 00000000 2c064372
-05e0: c1863d08 1cb5c415 00000000 00000001 ecc9da78 0142ceae 00000000 00000000
-0600: 5c0a1ed5 10133f47 6365760b 54726f74 6c61746f 10133f47 4c12c6d9 00000003
-0620: 29dfe61b 00007401 00020005 00000000 c1863d08 2cecf817 00000000 00000000
-0640: 29dfe61b 746f740b 635f6c61 746e756f 00000000 c1863d08 a8509bda 00000001
-0660: 00000000 29dfe61b 63657606 00726f74 00000000 c1863d08 1cb5c415 00000001
-0680: 00000001 ecc9da78 0142ceae 00000000 00000000 2c064372 c1863d08 10133f47
-06a0: 00000000 00000001 ecc9da78 0142ceae 00000000 00000000 5c0a1ed5 29dfe61b
-06c0: 736c7407 6772612e 29dfe61b 4c12c6d9 00000006 29dfe61b 00646902 00000000
-06e0: c1863d08 b5286e24 00000001 00000000 29dfe61b 616c6605 00007367 00000004
-0700: 00000000 c1863d08 70659eff 00000000 00000000 29dfe61b 72617607 6d756e5f
-0720: 00000002 00000000 00000001 c1863d08 a8509bda 00000001 00000000 29dfe61b
-0740: 6978650d 765f7473 6e5f7261 00006d75 00000002 00000000 00000002 c1863d08
-0760: a8509bda 00000001 00000000 29dfe61b 6978650d 765f7473 625f7261 00007469
-0780: 00000002 00000000 00000002 c1863d08 a8509bda 00000001 00000000 29dfe61b
-07a0: 70797404 00000065 00000000 c1863d08 193fd378 00000000 00000000 2c064372
-07c0: c1863d08 29dfe61b 00000000 00000000 5c0a1ed5 5c0a1ed5 736c740e 6d6f632e
-07e0: 616e6962 00726f74 5c0a1ed5 4c12c6d9 00000005 29dfe61b 6d616e04 00000065
-0800: 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b 00646902 00000000
-0820: c1863d08 b5286e24 00000001 00000000 29dfe61b 70797409 616e5f65 0000656d
-0840: 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b 66656c04 00000074
-0860: 00000000 c1863d08 8133d9ba 00000000 00000000 29dfe61b 67697205 00007468
-0880: 00000000 c1863d08 2c064372 00000000 00000000 2c064372 c1863d08 5c0a1ed5
-08a0: 00000000 00000000 5c0a1ed5 cd211f63 736c7419 6d6f632e 616e6962 4c726f74
-08c0: 42746665 746c6975 00006e69 8133d9ba 4c12c6d9 00000000 2c064372 c1863d08
-08e0: 8133d9ba 00000000 00000000 5c0a1ed5 4c12c6d9 736c7412 6d6f632e 616e6962
-0900: 4c726f74 00746665 8133d9ba 4c12c6d9 00000002 29dfe61b 67726108 756e5f73
-0920: 0000006d 00000004 00000000 c1863d08 70659eff 00000000 00000000 29dfe61b
-0940: 67726104 00000073 00000000 d9fb20de 4e8a14f0 00000000 00000000 00000001
-0960: 29dfe61b 00000000 00000000 c1863d08 29dfe61b 00000000 00000000 2c064372
-0980: c1863d08 8133d9ba 00000000 00000000 5c0a1ed5 2c064372 736c7413 6d6f632e
-09a0: 616e6962 52726f74 74686769 2c064372 4c12c6d9 00000001 29dfe61b 6c617605
-09c0: 00006575 00000000 c1863d08 193fd378 00000000 00000000 2c064372 c1863d08
-09e0: 2c064372 00000000 00000000 5c0a1ed5 ecc9da78 736c740c 7078652e 70795472
-0a00: 00000065 307d41a0 4c12c6d9 00000001 29dfe61b 00000000 00000000 c1863d08
-0a20: 193fd378 00000000 00000000 2c064372 c1863d08 307d41a0 00000000 00000000
-0a40: 5c0a1ed5 dcb49bd8 736c740b 7078652e 74614e72 307d41a0 4c12c6d9 00000001
-0a60: 29dfe61b 00000000 00000000 c1863d08 c2635441 00000000 00000000 2c064372
-0a80: c1863d08 307d41a0 00000000 00000000 5c0a1ed5 8ce940b1 736c740c 74616e2e
-0aa0: 736e6f43 00000074 c2635441 4c12c6d9 00000001 29dfe61b 6c617605 00006575
-0ac0: 00000000 c1863d08 a8509bda 00000001 00000000 2c064372 c1863d08 c2635441
-0ae0: 00000000 00000000 5c0a1ed5 4e8a14f0 736c740a 74616e2e 00726156 c2635441
-0b00: 4c12c6d9 00000002 29dfe61b 66696403 00000000 c1863d08 a8509bda 00000001
-0b20: 00000000 29dfe61b 72617607 6d756e5f 00000000 c1863d08 a8509bda 00000001
-0b40: 00000000 2c064372 c1863d08 c2635441 00000000 00000000 5c0a1ed5 3a2f9be2
-0b60: 736c740d 6863732e 5f616d65 00003276 3a2f9be2 4c12c6d9 00000008 29dfe61b
-0b80: 72657607 6e6f6973 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b
-0ba0: 74616404 00000065 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b
-0bc0: 70797409 6e5f7365 00006d75 00000004 00000000 c1863d08 70659eff 00000000
-0be0: 00000000 29dfe61b 70797405 00007365 00000000 d9fb20de 4e8a14f0 00000000
-0c00: 00000000 00000001 29dfe61b 00000000 00000000 c1863d08 12eb4386 00000000
-0c20: 00000000 29dfe61b 6e6f630f 75727473 726f7463 6d756e5f 00000004 00000001
-0c40: c1863d08 70659eff 00000000 00000000 29dfe61b 6e6f630c 75727473 726f7463
-0c60: 00000073 00000000 d9fb20de 4e8a14f0 00000000 00000001 00000001 29dfe61b
-0c80: 00000000 00000000 c1863d08 5c0a1ed5 00000000 00000000 29dfe61b 6e75660d
-0ca0: 6f697463 6e5f736e 00006d75 00000004 00000002 c1863d08 70659eff 00000000
-0cc0: 00000000 29dfe61b 6e756609 6f697463 0000736e 00000000 d9fb20de 4e8a14f0
-0ce0: 00000000 00000002 00000001 29dfe61b 00000000 00000000 c1863d08 5c0a1ed5
-0d00: 00000000 00000000 2c064372 c1863d08 3a2f9be2 00000000 00000000 5c0a1ed5
-0d20: 12eb4386 736c7408 7079742e 00000065 12eb4386 4c12c6d9 00000006 29dfe61b
-0d40: 6d616e04 00000065 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b
-0d60: 00646902 00000000 c1863d08 b5286e24 00000001 00000000 29dfe61b 6e6f6310
-0d80: 75727473 726f7463 756e5f73 0000006d 00000000 c1863d08 a8509bda 00000001
-0da0: 00000000 29dfe61b 616c6605 00007367 00000000 c1863d08 a8509bda 00000001
-0dc0: 00000000 29dfe61b 69726105 00007974 00000000 c1863d08 a8509bda 00000001
-0de0: 00000000 29dfe61b 7261700b 5f736d61 65707974 00000000 c1863d08 22076cba
-0e00: 00000001 00000000 2c064372 c1863d08 12eb4386 00000000 00000000 5c0a1ed5
-0e20: 0142ceae 736c740b 7079742e 72615665 193fd378 4c12c6d9 00000002 29dfe61b
-0e40: 72617607 6d756e5f 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b
-0e60: 616c6605 00007367 00000000 c1863d08 a8509bda 00000001 00000000 2c064372
-0e80: c1863d08 193fd378 00000000 00000000 5c0a1ed5 d9fb20de 736c7409 7272612e
-0ea0: 00007961 193fd378 4c12c6d9 00000003 29dfe61b 6c756d0c 6c706974 74696369
-0ec0: 00000079 00000000 c1863d08 c2635441 00000000 00000000 29dfe61b 67726108
-0ee0: 756e5f73 0000006d 00000004 00000000 c1863d08 70659eff 00000000 00000000
-0f00: 29dfe61b 67726104 00000073 00000000 d9fb20de 4e8a14f0 00000000 00000000
-0f20: 00000001 29dfe61b 00000000 00000000 c1863d08 29dfe61b 00000000 00000000
-0f40: 2c064372 c1863d08 193fd378 00000000 00000000 5c0a1ed5 c1863d08 736c740c
-0f60: 7079742e 70784565 00000072 193fd378 4c12c6d9 00000004 29dfe61b 6d616e04
-0f80: 00000065 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b 616c6605
-0fa0: 00007367 00000000 c1863d08 a8509bda 00000001 00000000 29dfe61b 6968630c
-0fc0: 6572646c 756e5f6e 0000006d 00000004 00000000 c1863d08 70659eff 00000000
-0fe0: 00000000 29dfe61b 69686308 6572646c 0000006e 00000000 d9fb20de 4e8a14f0
-1000: 00000000 00000000 00000001 29dfe61b 00000000 00000000 c1863d08 307d41a0
-1020: 00000000 00000000 2c064372 c1863d08 193fd378 00000000 00000000 00000000

-
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/mtproto/TL-types.html b/data/corefork.telegram.org/mtproto/TL-types.html deleted file mode 100644 index 28c1e276c4..0000000000 --- a/data/corefork.telegram.org/mtproto/TL-types.html +++ /dev/null @@ -1,124 +0,0 @@ - - - - - Type serialization - - - - - - - - - - - - - -
- -
-
-
- -

Type serialization

- -

See Polymorphism in TL and TL Language.

-

It remains to describe how types, e.g. values of type Type, are transmitted (serialized). In general, there is nothing unexpected going on here: we have type constructors of various arities (for example, List is an arity-1 constructor, but IntList is a 0-arity constructor); and if we know that a 32-bit “name” is assigned to each type constructor, there are no further questions -- values of type Type are serialized exactly like values of any other recursive type with a defined set of constructors of differing arity.

-

How can a 32-bit “name” be assigned to a type (a type constructor, to be more exact) such as List or IntList? -It is proposed to use the sum of the names of all of its constructors, plus the CRC32 of the string with the designation of the type's name and all of its parameters such as “IntList = Type” or “List X:Type = Type”. This way, the List constructor’s “name” is the sum of the CRC32s of the three strings "List X:Type = Type", "cons X:Type hd:X tl:List X = List X", and "nil X:Type = List X". -For “bare” types (which, formally speaking, are subtypes of the corresponding “boxed” type), the situation is somewhat more complicated; the logical negation of the corresponding constructor’s name is used. For built-in bareand boxed types (for example, int and Int), a pseudo-declaration is used (for example, int ? = Int").

-
    -
  • This description is somewhat outdated and may be updated in the future. Specifically, how to treat the ! modifier has not been explained.*
  • -
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/mtproto/TL.html b/data/corefork.telegram.org/mtproto/TL.html deleted file mode 100644 index e89117151f..0000000000 --- a/data/corefork.telegram.org/mtproto/TL.html +++ /dev/null @@ -1,210 +0,0 @@ - - - - - TL Language - - - - - - - - - - - - - -
- -
-
-
- -

TL Language

- -

TL (Type Language) serves to describe the used system of types, constructors, and existing functions. In fact, the combinator description format presented in Binary Data Serialization is used.

-

See also:

- -

Advanced topics:

- -

Overview

-

A TL program usually consists of two sections separated by keyword ---functions---. The first section consists of declarations of built-in types and aggregate types (i.e. their constructors). The second section consists of the declared functions, i.e. functional combinators.

-

Actually, both the first and second sections consist of combinator declarations, each of which ends with a semicolon. However, the first section contains only constructors, while the second section only involves functions. Each combinator is declared using a “combinator declaration” in the format explained above. However, the combinator number and field names may be explicitly assigned.

-

If additional type declarations are required after functions have been declared, the keyword (section divider) ---types--- is used. Furthermore, a functional combinator may be declared in the type section if its result type begins with an exclamation point (in fact, when the function section is interpreted, this exclamation point is added automatically).

-

To explicitly define 32-bit names of combinators, a hash mark (#) is added immediately after the combinator’s name, followed by 8 hexadecimal digits.

-

Namespaces

-

Composite constructions like <namespace_identifier>.<constructor_identifier> and <namespace_identifier>.<Type_identifier> can be used as constructor- or type identifiers. The portion of the identifier to the left of the period is called the namespace. Moreover, the rule about a first uppercase letter in type identifiers and lowercase letter in constructor identifiers applies to the part of the construction after the period. For example, auth.Message would be a type, while auth.std_message would be a constructor.

-

Namespaces do not require a special declaration.

-

Comments

-

Comments are the same as in C++.

-

Example

-
// built-in types
-int#a8509bda ? = Int;
-long ? = Long;
-double ? = Double;
-string ? = String;
-null = Null;
-
-vector {t:Type} # [ t ] = Vector t;
-coupleInt {alpha:Type} int alpha = CoupleInt<alpha>;
-coupleStr {gamma:Type} string gamma = CoupleStr gamma;  
-/* The name of the type variable is irrelevant: "gamma" could be replaced with "alpha"; 
-   However, the combinator number will depend on the specific choice. */
-
-intHash {alpha:Type} vector<coupleInt<alpha>> = IntHash<alpha>;
-strHash {alpha:Type} (vector (coupleStr alpha)) = StrHash alpha;
-intSortedHash {alpha:Type} intHash<alpha> = IntSortedHash<alpha>;
-strSortedHash {alpha:Type} (strHash alpha) = StrSortedHash alpha;
-
-// custom types
-pair x:Object y:Object = Pair;
-triple x:Object y:Object z:Object = Triple;
-
-user#d23c81a3 id:int first_name:string last_name:string = User;
-no_user#c67599d1 id:int = User;
-group id:int title:string last_name:string = Group;
-no_group = Group;
-
----functions---
-
-// Maybe some built-in arithmetic functions; inverse quotes make "identifiers" out of arbitrary non-alphanumeric strings
-`+` Int Int = Int;
-`-` Int Int = Int;
-`+` Double Double = Double;
-// ...
-
-// API functions (aka RPC functions)
-getUser#b0f732d5 int = User;
-getUsers#2d84d5f5 (Vector int) = Vector User;
-

In this case, the user constructor has been explicitly assigned a number (0xd23c81a3); In fact, this was not necessary, since this value is the CRC32 of the string "user id:int first_name:string last_name:string = User", which would have been used by default.

-

Special constructors are not required for Vector int, Vector User, Vector Object, etc. -- the same universal constructor can be used everywhere:

-
vector#1cb5c415 {t:Type} # [ t ] = Vector t;
-

Note that when the getUsers (Vector int) = Vector User; constructor number is calculated, the CRC32 of the string "getUsers Vector int = Vector User” is computed (from which all parentheses have been removed).

-

Notation T0<T1,T2,...,Tn> is syntactic sugar for (T0 (T1) (T2) ... (Tn)). For example, Vector<User> and (Vector User) are entirely interchangeable.

-

Example of an RPC query

-

Suppose we want to call getUsers([2,3,4]). This query will be serialized into a sequence of 32-bit integers as follows:

-
0x2d84d5f5 0x1cb5c415 0x3 0x2 0x3 0x4
-

Please note that TL serialization yields sequences of 32-bit integers. When it has to be embedded into a byte stream, for example a network packet, each 32-bit integer is represented by four bytes in little-endian order. In this way the above query corresponds to the following byte stream:

-
F5 D5 84 2D 15 C4 B5 1C 03 00 00 00 02 00 00 00 03 00 00 00 04 00 00 00
-

The response might look something like this:

-
0x1cb5c415 0x3 0xd23c81a3 0x2 0x74655005 0x00007265 0x72615006 0x72656b 0xc67599d1 0x3 0xd23c81a3 0x4 0x686f4a04 0x6e 0x656f4403
-

This roughly corresponds to

-
[{"id":2,"first_name":"Peter", "last_name":"Parker"},{},{"id":4,"first_name":"John","last_name":"Doe"}]
-

Note that in both cases the same universal constructor vector#1cb5c415 is used: in the request to serialize the value of type Vector int, and in the serialization of the value of type Vector User in the response. There is no ambiguity because in both cases the type of the value being (de)serialized is known before its (de)serialization begins. For example, after receiving the query, the server sees that the first part is 0x2d84d5f5, which corresponds to the combinator getUsers#2d84d5f5 (Vector int) = Vector User. Thus, it is understood that what follows will be a value of type Vector int. After receiving the response to this query, the client knows that it must receive a value of type Vector User and it deserializes the response accordingly.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/mtproto/description.html b/data/corefork.telegram.org/mtproto/description.html deleted file mode 100644 index f1fffd7c32..0000000000 --- a/data/corefork.telegram.org/mtproto/description.html +++ /dev/null @@ -1,238 +0,0 @@ - - - - - Mobile Protocol: Detailed Description - - - - - - - - - - - - - -
- -
-
-
- -

Mobile Protocol: Detailed Description

- -
- -
-

As of version 4.6, major Telegram clients are using MTProto 2.0. -MTProto v.1.0 is deprecated and is currently being phased out.

-
-

This article describes the basic layer of the MTProto protocol version 2.0 (Cloud chats, server-client encryption). The principal differences from version 1.0 (described here for reference) are as follows:

-
    -
  • SHA-256 is used instead of SHA-1;
  • -
  • Padding bytes are involved in the computation of msg_key;
  • -
  • msg_key depends not only on the message to be encrypted, but on a portion of auth_key as well;
  • -
  • 12..1024 padding bytes are used instead of 0..15 padding bytes in v.1.0.
  • -
-

See also: MTProto 2.0: Secret Chats, end-to-end encryption

-

Protocol description

-

Before a message (or a multipart message) is transmitted over a network using a transport protocol, it is encrypted in a certain way, and an external header is added at the top of the message that consists of a 64-bit key identifier auth_key_id (that uniquely identifies an authorization key for the server as well as the user) and a 128-bit message key msg_key.

-

The authorization key auth_key combined with the message key msg_key define an actual 256-bit key aes_key and a 256-bit initialization vector aes_iv, which are used to encrypt the message using AES-256 encryption in infinite garble extension (IGE) mode. Note that the initial part of the message to be encrypted contains variable data (session, message ID, sequence number, server salt) that obviously influences the message key (and thus the AES key and iv). In MTProto 2.0, the message key is defined as the 128 middle bits of the SHA-256 of the message body (including session, message ID, padding, etc.) prepended by 32 bytes taken from the authorization key. In the older MTProto 1.0, the message key was computed as the lower 128 bits of SHA-1 of the message body, excluding the padding bytes.

-

Multipart messages are encrypted as a single message.

- -
-

Got questions about this setup? — Check out the Advanced FAQ!

-
-
Note 1
-

Each plaintext message to be encrypted in MTProto always contains the following data to be checked upon decryption in order to make the system robust against known problems with the components:

-
    -
  • server salt (64-Bit)
  • -
  • session id
  • -
  • message sequence number
  • -
  • message length
  • -
  • time
  • -
-
Note 2
-

Telegram's End-to-end encrypted Secret Chats are using an additional layer of encryption on top of the described above. See Secret Chats, End-to-End encryption for details.

-

Terminology

-

Authorization Key (auth_key)

-

A 2048-bit key shared by the client device and the server, created upon user registration directly on the client device by exchanging Diffie-Hellman keys, and never transmitted over a network. Each authorization key is user-specific. There is nothing that prevents a user from having several keys (that correspond to “permanent sessions” on different devices), and some of these may be locked forever in the event the device is lost. See also Creating an Authorization Key.

-

Server Key

-

A 2048-bit RSA key used by the server digitally to sign its own messages while registration is underway and the authorization key is being generated. The application has a built-in public server key which can be used to verify a signature but cannot be used to sign messages. A private server key is stored on the server and changed very infrequently.

-

Key Identifier (auth_key_id)

-

The 64 lower-order bits of the SHA1 hash of the authorization key are used to indicate which particular key was used to encrypt a message. Keys must be uniquely defined by the 64 lower-order bits of their SHA1, and in the event of a collision, an authorization key is regenerated. A zero key identifier means that encryption is not used which is permissible for a limited set of message types used during registration to generate an authorization key in a Diffie-Hellman exchange. For MTProto 2.0, SHA1 is still used here, because auth_key_id should identify the authorization key used independently of the protocol version.

-

Session

-

A (random) 64-bit number generated by the client to distinguish between individual sessions (for example, between different instances of the application, created with the same authorization key). The session in conjunction with the key identifier corresponds to an application instance. The server can maintain session state. Under no circumstances can a message meant for one session be sent into a different session. The server may unilaterally forget any client sessions; clients should be able to handle this.

-

Server Salt

-

A (random) 64-bit number changed every 30 minutes (separately for each session) at the request of the server. All subsequent messages must contain the new salt (although, messages with the old salt are still accepted for a further 1800 seconds). Required to protect against replay attacks and certain tricks associated with adjusting the client clock to a moment in the distant future.

-

Message Identifier (msg_id)

-

A (time-dependent) 64-bit number used uniquely to identify a message within a session. Client message identifiers are divisible by 4, server message identifiers modulo 4 yield 1 if the message is a response to a client message, and 3 otherwise. Client message identifiers must increase monotonically (within a single session), the same as server message identifiers, and must approximately equal unixtime*2^32. This way, a message identifier points to the approximate moment in time the message was created. A message is rejected over 300 seconds after it is created or 30 seconds before it is created (this is needed to protect from replay attacks). In this situation, it must be re-sent with a different identifier (or placed in a container with a higher identifier). The identifier of a message container must be strictly greater than those of its nested messages.

-

Important: to counter replay-attacks the lower 32 bits of msg_id passed by the client must not be empty and must present a fractional part of the time point when the message was created.

-

Content-related Message

-

A message requiring an explicit acknowledgment. These include all the user and many service messages, virtually all with the exception of containers and acknowledgments.

-

Message Sequence Number (msg_seqno)

-

A 32-bit number equal to twice the number of “content-related” messages (those requiring acknowledgment, and in particular those that are not containers) created by the sender prior to this message and subsequently incremented by one if the current message is a content-related message. A container is always generated after its entire contents; therefore, its sequence number is greater than or equal to the sequence numbers of the messages contained in it.

-

Message Key (msg_key)

-

In MTProto 2.0, the middle 128 bits of the SHA-256 hash of the message to be encrypted (including the internal header and the padding bytes for MTProto 2.0), prepended by a 32-byte fragment of the authorization key.

-

In MTProto 1.0, message key was defined differently, as the lower 128 bits of the SHA-1 hash of the message to be encrypted, with padding bytes excluded from the computation of the hash. Authorization key was not involved in this computation.

-

Internal (cryptographic) Header

-

A header (16 bytes) added before a message or a container before it is all encrypted together. Consists of the server salt (64 bits) and the session (64 bits).

-

External (cryptographic) Header

-

A header (24 bytes) added before an encrypted message or a container. Consists of the key identifier auth_key_id (64 bits) and the message key msg_key (128 bits).

-

Payload

-

External header + encrypted message or container.

-

Defining AES Key and Initialization Vector

-

The 2048-bit authorization key (auth_key) and the 128-bit message key (msg_key) are used to compute a 256-bit AES key (aes_key) and a 256-bit initialization vector (aes_iv) which are subsequently used to encrypt the part of the message to be encrypted (i. e. everything with the exception of the external header that is added later) with AES-256 in infinite garble extension (IGE) mode.

-

For MTProto 2.0, the algorithm for computing aes_key and aes_iv from auth_key and msg_key is as follows.

-
    -
  • msg_key_large = SHA256 (substr (auth_key, 88+x, 32) + plaintext + random_padding);
  • -
  • msg_key = substr (msg_key_large, 8, 16);
  • -
  • sha256_a = SHA256 (msg_key + substr (auth_key, x, 36));
  • -
  • sha256_b = SHA256 (substr (auth_key, 40+x, 36) + msg_key);
  • -
  • aes_key = substr (sha256_a, 0, 8) + substr (sha256_b, 8, 16) + substr (sha256_a, 24, 8);
  • -
  • aes_iv = substr (sha256_b, 0, 8) + substr (sha256_a, 8, 16) + substr (sha256_b, 24, 8);
  • -
-

where x = 0 for messages from client to server and x = 8 for those from server to client.

-

For the obsolete MTProto 1.0, msg_key, aes_key, and aes_iv were computed differently (see this document for reference).

-

The lower-order 1024 bits of auth_key are not involved in the computation. They may (together with the remaining bits or separately) be used on the client device to encrypt the local copy of the data received from the server. The 512 lower-order bits of auth_key are not stored on the server; therefore, if the client device uses them to encrypt local data and the user loses the key or the password, data decryption of local data is impossible (even if data from the server could be obtained).

-

In MTProto 1.0, when AES was used to encrypt a block of data of a length not divisible by 16 bytes, the data was padded with 0 to 15 random padding bytes random_padding to a length divisible by 16 bytes prior to encryption. In MTProto 2.0, this padding is taken into account when computing msg_key. Note that MTProto 2.0 requires from 12 to 1024 bytes of padding, still subject to the condition that the resulting message length be divisible by 16 bytes.

-

Using MTProto 2.0 instead of MTProto 1.0

-

A client may either use only MTProto 2.0 or only MTProto 1.0 in the same TCP connection. The server detects the protocol used by the first message received from the client, and then uses the same encryption for its messages, and expects the client to use the same encryption henceforth. We recommend using MTProto 2.0; MTProto 1.0 is deprecated and supported for backward compatibility only.

-

Important Checks

-

When an encrypted message is received, it must be checked that msg_key is in fact equal to the 128 middle bits of the SHA-256 of the decrypted data with a 32-byte fragment of auth_key prepended to it, and that msg_id has even parity for messages from client to server, and odd parity for messages from server to client.

-

In addition, the identifiers (msg_id) of the last N messages received from the other side must be stored, and if a message comes in with msg_id lower than all or equal to any of the stored values, the message is to be ignored. Otherwise, the new message msg_id is added to the set, and, if the number of stored msg_id values is greater than N, the oldest (i. e. the lowest) is forgotten.

-

On top of this, msg_id values that belong over 30 seconds in the future or over 300 seconds in the past are to be ignored. This is especially important for the server. The client would also find this useful (to protect from a replay attack), but only if it is certain of its time (for example, if its time has been synchronized with that of the server).

-

Certain client-to-server service messages containing data sent by the client to the server (for example, msg_id of a recent client query) may, nonetheless, be processed on the client even if the time appears to be “incorrect”. This is especially true of messages to change server_salt and notifications of invalid client time. See Mobile Protocol: Service Messages.

-

Storing an Authorization Key on a Client Device

-

It may be suggested to users concerned with security that they password protect the authorization key in approximately the same way as in ssh. This can be accomplished by prepending the value of cryptographic hash function, such as SHA-256, of the key to the front of the key, following which the entire string is encrypted using AES in CBC mode and a key equal to the user’s (text) password. When the user inputs the password, the stored protected password is decrypted and verified by checking the SHA-256 value. From the user’s standpoint, this is practically the same as using an application or a website password.

-

Unencrypted Messages

-

Special plain-text messages may be used to create an authorization key as well as to perform a time synchronization. They begin with auth_key_id = 0 (64 bits) which means that there is no auth_key. This is followed directly by the message body in serialized format without internal or external headers. A message identifier (64 bits) and body length in bytes (32 bytes) are added before the message body.

-

Only a very limited number of messages of special types can be transmitted as plain text.

-

Schematic Presentation of Messages

-

Encrypted Message

- - - - -
auth_key_id
int64
msg_key
int128
encrypted_data
bytes
-

Encrypted Message: encrypted_data

-

Contains the cypher text for the following data:

- - - - - - - - -
salt
int64
session_id
int64
message_id
int64
seq_no
int32
message_data_length
int32
message_data
bytes
padding12..1024
bytes
-

Unencrypted Message

- - - - - -
auth_key_id = 0
int64
message_id
int64
message_data_length
int32
message_data
bytes
-

MTProto 2.0 uses 12..1024 padding bytes, instead of the 0..15 used in MTProto 1.0

-

Creating an Authorization Key

-

An authorization key is normally created once for every user during the application installation process immediately prior to registration. Registration itself, in actuality, occurs after the authorization key is created. However, a user may be prompted to complete the registration form while the authorization key is being generated in the background. Intervals between user key strokes may be used as a source of entropy in the generation of high-quality random numbers required for the creation of an authorization key.

-

See Creating an Authorization Key.

-

During the creation of the authorization key, the client obtains its server salt (to be used with the new key for all communication in the near future). The client then creates an encrypted session using the newly generated key, and subsequent communication occurs within that session (including the transmission of the user's registration information and phone number validation) unless the client creates a new session. The client is free to create new or additional sessions at any time by choosing a new random session_id.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/mtproto/description_v1.html b/data/corefork.telegram.org/mtproto/description_v1.html deleted file mode 100644 index be348fa35a..0000000000 --- a/data/corefork.telegram.org/mtproto/description_v1.html +++ /dev/null @@ -1,205 +0,0 @@ - - - - - Mobile Protocol: Detailed Description (v.1.0, DEPRECATED) - - - - - - - - - - - - - -
- -
-
-
- -

Mobile Protocol: Detailed Description (v.1.0, DEPRECATED)

- -
-

This document describes MTProto v.1.0, its status is DEPRECATED. -For information on encryption used in up-to-date Telegram clients, kindly see this document.

-
-

Prior to a message (or a multipart message) being transmitted over a network using a transport protocol, it is encrypted in a certain way, and an external header is added at the top of the message which is: a 64-bit key identifier (that uniquely identifies an authorization key for the server as well as the user) and a 128-bit message key.

-

A user key together with the message key define an actual 256-bit key and a 256-bit initialization vector, which is what encrypts the message using AES-256 encryption with infinite garble extension (IGE). Note that the initial part of the message to be encrypted contains variable data (session, message ID, sequence number, server salt) that obviously influences the message key (and thus the AES key and iv). The message key is defined as the 128 lower-order bits of the SHA1 of the message body (including session, message ID, etc.) Multipart messages are encrypted as a single message.

- -

Terminology

-

Authorization Key

-

a 2048-bit key shared by the client device and the server, created upon user registration directly on the client device be exchanging Diffie-Hellman keys, and never transmitted over a network. Each authorization key is user-specific. There is nothing that prevents a user from having several keys (that correspond to “permanent sessions” on different devices), and some of these may be locked forever in the event the device is lost. See also Creating an Authorization Key.

-

Server Key

-

a 2048-bit RSA key used by the server digitally to sign its own messages while registration is underway and the authorization key is being generated. The application has a built-in public server key which can be used to verify a signature but cannot be used to sign messages. A private server key is stored on the server and changed very infrequently.

-

Key Identifier

-

The 64 lower-order bits of the SHA1 hash of the authorization key are used to indicate which particular key was used to encrypt a message. Keys must be uniquely defined by the 64 lower-order bits of their SHA1, and in the event of a collision, an authorization key is regenerated. A zero key identifier means that encryption is not used which is permissible for a limited set of message types used during registration to generate an authorization key based on a Diffie-Hellman exchange.

-

Session

-

a (random) 64-bit number generated by the client to distinguish between individual sessions (for example, between different instances of the application, created with the same authorization key). The session in conjunction with the key identifier corresponds to an application instance. The server can maintain session state. Under no circumstances can a message meant for one session be sent into a different session. The server may unilaterally forget any client sessions; clients should be able to handle this.

-

Server Salt

-

a (random) 64-bit number periodically (say, every 24 hours) changed (separately for each session) at the request of the server. All subsequent messages must contain the new salt (although, messages with the old salt are still accepted for a further 300 seconds). Required to protect against replay attacks and certain tricks associated with adjusting the client clock to a moment in the distant future.

-

Message Identifier (msg_id)

-

a (time-dependent) 64-bit number used uniquely to identify a message within a session. Client message identifiers are divisible by 4, server message identifiers modulo 4 yield 1 if the message is a response to a client message, and 3 otherwise. Client message identifiers must increase monotonically (within a single session), the same as server message identifiers, and must approximately equal unixtime*2^32. This way, a message identifier points to the approximate moment in time the message was created. A message is rejected over 300 seconds after it is created or 30 seconds before it is created (this is needed to protect from replay attacks). In this situation, it must be re-sent with a different identifier (or placed in a container with a higher identifier). The identifier of a message container must be strictly greater than those of its nested messages.

-

Important: to counter replay-attacks the lower 32 bits of msg_id passed by the client must not be empty and must present a fractional part of the time point when the message was created. At some point in the nearest future the server will start ignoring messages, in which the lower 32 bits of msg_id contain too many zeroes.

-

Content-related Message

-

A message requiring an explicit acknowledgment. These include all the user and many service messages, virtually all with the exception of containers and acknowledgments.

-

Message Sequence Number (msg_seqno)

-

a 32-bit number equal to twice the number of “content-related” messages (those requiring acknowledgment, and in particular those that are not containers) created by the sender prior to this message and subsequently incremented by one if the current message is a content-related message. A container is always generated after its entire contents; therefore, its sequence number is greater than or equal to the sequence numbers of the messages contained in it.

-

Message Key

-

The lower-order 128 bits of the SHA1 hash of the part of the message to be encrypted (including the internal header and excluding the alignment bytes).

-

Internal (cryptographic) Header

-

A header (16 bytes) added before a message or a container before it is all encrypted together. Consists of the server salt (64 bits) and the session (64 bits).

-

External (cryptographic) Header

-

A header (24 bytes) added before an encrypted message or a container. Consists of a key identifier (64 bits) and a message key (128 bits).

-

Payload

-

External header + encrypted message or container.

-

Defining AES Key and Initialization Vector

-

The 2048-bit authorization key (auth_key) and the 128-bit message key (msg_key) are used to compute a 256-bit AES key (aes_key) and a 256-bit initialization vector (aes_iv) which are subsequently used to encrypt the part of the message to be encrypted (i. e. everything with the exception of the external header which is added later) with AES-256 in infinite garble extension (IGE) mode.

-

The algorithm for computing aes_key and aes_iv from auth_key and msg_key is as follows:

-
    -
  • msg_key = substr (SHA1 (plaintext), 4, 16);
  • -
  • sha1_a = SHA1 (msg_key + substr (auth_key, x, 32));
  • -
  • sha1_b = SHA1 (substr (auth_key, 32+x, 16) + msg_key + substr (auth_key, 48+x, 16));
  • -
  • sha1_с = SHA1 (substr (auth_key, 64+x, 32) + msg_key);
  • -
  • sha1_d = SHA1 (msg_key + substr (auth_key, 96+x, 32));
  • -
  • aes_key = substr (sha1_a, 0, 8) + substr (sha1_b, 8, 12) + substr (sha1_c, 4, 12);
  • -
  • aes_iv = substr (sha1_a, 8, 12) + substr (sha1_b, 0, 8) + substr (sha1_c, 16, 4) + substr (sha1_d, 0, 8);
  • -
-

where x = 0 for messages from client to server and x = 8 for those from server to client.

-

The lower-order 1024 bits of auth_key are not involved in the computation. They may (together with the remaining bits or separately) be used on the client device to encrypt the local copy of the data received from the server. The 512 lower-order bits of auth_key are not stored on the server; therefore, if the client device uses them to encrypt local data and the user loses the key or the password, data decryption of local data is impossible (even if data from the server could be obtained).

-

When AES is used to encrypt a block of data of a length not divisible by 16 bytes, the data is padded with random bytes to the smallest length divisible by 16 bytes immediately prior to being encrypted.

-

Important Tests

-

When an encrypted message is received, it must be checked that msg_key is in fact equal to the 128 lower-order bits of the SHA1 hash of the previously encrypted portion, and that msg_id has even parity for messages from client to server, and odd parity for messages from server to client.

-

In addition, the identifiers (msg_id) of the last N messages received from the other side must be stored, and if a message comes in with msg_id lower than all or equal to any of the stored values, the message is to be ignored. Otherwise, the new message msg_id is added to the set, and, if the number of stored msg_id values is greater than N, the oldest (i. e. the lowest) is forgotten.

-

In addition, msg_id values that belong over 30 seconds in the future or over 300 seconds in the past are to be ignored. This is especially important for the server. The client would also find this useful (to protect from a replay attack), but only if it is certain of its time (for example, if its time has been synchronized with that of the server).

-

Certain client-to-server service messages containing data sent by the client to the server (for example, msg_id of a recent client query) may, nonetheless, be processed on the client even if the time appears to be “incorrect”. This is especially true of messages to change server_salt and notifications of invalid client time. See Mobile Protocol: Service Messages.

-

Storing an Authorization Key on a Client Device

-

It may be suggested to users concerned with security that they password protect the authorization key in approximately the same way as in ssh. This is accomplished by adding the SHA1 of the key to the front of the key, following which the entire string is encrypted using AES in CBC mode and a key equal to the user’s (text) password. When the user inputs the password, the stored protected password is decrypted and verified by being compared with SHA1. From the user’s standpoint, this is practically the same as using an application or a website password.

-

Unencrypted Messages

-

Special plain-text messages may be used to create an authorization key as well as to perform a time synchronization. They begin with auth_key_id = 0 (64 bits) which means that there is no auth_key. This is followed directly by the message body in serialized format without internal or external headers. A message identifier (64 bits) and body length in bytes (32 bytes) are added before the message body.

-

Only a very limited number of messages of special types can be transmitted as plain text.

-

Schematic Presentation of Messages

-

Encrypted Message

- - - - -
auth_key_id
int64
msg_key
int128
encrypted_data
bytes
-

Encrypted Message: encrypted_data

-

Contains the cypher text for the following data:

- - - - - - - - -
salt
int64
session_id
int64
message_id
int64
seq_no
int32
message_data_length
int32
message_data
bytes
padding 0..15
bytes
-

Unencrypted Message

- - - - - -
auth_key_id = 0
int64
message_id
int64
message_data_length
int32
message_data
bytes
-

Creating an Authorization Key

-

An authorization key is normally created once for every user during the application installation process immediately prior to registration. Registration itself, in actuality, occurs after the authorization key is created. However, a user may be prompted to complete the registration form while the authorization key is being generated in the background. Intervals between user key strokes may be used as a source of entropy in the generation of high-quality random numbers required for the creation of an authorization key.

-

See Creating an Authorization Key.

-

During the creation of the authorization key, the client obtains its server salt (to be used with the new key for all communication in the near future). The client then creates an encrypted session using the newly generated key, and subsequent communication occurs within that session (including the transmission of the user's registration information and phone number validation) unless the client creates a new session. The client is free to create new or additional sessions at any time by choosing a new random session_id.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/mtproto/mtproto-transports.html b/data/corefork.telegram.org/mtproto/mtproto-transports.html deleted file mode 100644 index 88d72e683a..0000000000 --- a/data/corefork.telegram.org/mtproto/mtproto-transports.html +++ /dev/null @@ -1,281 +0,0 @@ - - - - - MTProto transports - - - - - - - - - - - - - -
- -
-
-
- -

MTProto transports

- -
- -

Here's a list of MTProto transport protocols (see the ISO/OSI recap for a full explanation):

- -

The server recognizes these different protocols (and distinguishes them from HTTP, too) by the header.
Additionally, the following transport features can be used:

- -

Example implementations for these protocols can be seen in tdlib and MadelineProto.

-

Abridged

-

The lightest protocol available.

-
    -
  • Overhead: Very small
  • -
  • Minimum envelope length: 1 byte
  • -
  • Maximum envelope length: 4 bytes
  • -
-

Payload structure:

-
+-+----...----+
-|l|  payload  |
-+-+----...----+
-OR
-
-+-+---+----...----+
-|h|len|  payload  +
-+-+---+----...----+
-

Before sending anything into the underlying socket (see transports), the client must first send 0xef as the first byte (the server will not send 0xef as the first byte in the first reply).
Then, payloads are wrapped in the following envelope:

-
    -
  • Length: payload length, divided by four, and encoded as a single byte, only if the resulting packet length is a value between 0x01..0x7e.
  • -
  • Payload: the MTProto payload
  • -
-

If the packet length divided by four is bigger than or equal to 127 (>= 0x7f), the following envelope must be used, instead:

-
    -
  • Header: A single byte of value 0x7f
  • -
  • Length: payload length, divided by four, and encoded as 3 length bytes (little endian)
  • -
  • Payload: the MTProto payload
  • -
-

Intermediate

-

In case 4-byte data alignment is needed, an intermediate version of the original protocol may be used.

-
    -
  • Overhead: small
  • -
  • Minimum envelope length: 4 bytes
  • -
  • Maximum envelope length: 4 bytes
  • -
-

Payload structure:

-
+----+----...----+
-+len.+  payload  +
-+----+----...----+
-

Before sending anything into the underlying socket (see transports), the client must first send 0xeeeeeeee as the first int (four bytes, the server will not send 0xeeeeeeee as the first int in the first reply).
Then, payloads are wrapped in the following envelope:

-
    -
  • Length: payload length encoded as 4 length bytes (little endian)
  • -
  • Payload: the MTProto payload
  • -
-

Padded intermediate

-

Padded version of the intermediate protocol, to use with obfuscation enabled to bypass ISP blocks.

-
    -
  • Overhead: small-medium
  • -
  • Minimum envelope length: random
  • -
  • Maximum envelope length: random
  • -
-

Before sending anything into the underlying socket (see transports), the client must first send 0xdddddddd as the first int (four bytes, the server will not send 0xdddddddd as the first int in the first reply).
Then, payloads are wrapped in the following envelope:

-
+----+----...----+----...----+
-|tlen|  payload  |  padding  |
-+----+----...----+----...----+
-

Envelope description:

-
    -
  • Total length: payload+padding length encoded as 4 length bytes (little endian)
  • -
  • Payload: the MTProto payload
  • -
  • Padding: A random padding string of length 0-15
  • -
-

Full

-

The basic MTProto transport protocol

-
    -
  • Overhead: medium
  • -
  • Minimum envelope length: 12 bytes (length+seqno+crc)
  • -
  • Maximum envelope length: 12 bytes (length+seqno+crc)
  • -
-

Payload structure:

-
+----+----+----...----+----+
-|len.|seq.|  payload  |crc.|
-+----+----+----...----+----+
-

Envelope description:

-
    -
  • Length: length+seqno+payload+crc length encoded as 4 length bytes (little endian, the length of the length field must be included, too)
  • -
  • Seqno: the TCP sequence number for this TCP connection (different from the MTProto sequence number): the first packet sent is numbered 0, the next one 1, etc.
  • -
  • payload: MTProto payload
  • -
  • crc: 4 CRC32 bytes computed using length, sequence number, and payload together.
  • -
-

Transport features

-

Additionally, the following transport features can be used:

-

Quick ack

-

These MTProto transport protocols have support for quick acknowledgment.
In this case, the client sets the highest-order length bit in the query packet, and the server responds with a special 4 bytes as a separate packet.
They are the 32 higher-order bits of SHA256 of the encrypted portion of the packet prepended by 32 bytes from the authorization key (the same hash as computed for verifying the message key), with the most significant bit set to make clear that this is not the length of a regular server response packet; if the abridged version is used, bswap is applied to these four bytes.

-

Transport errors

-

In the event of a transport error (missing auth key, transport flood, etc.), the server may send a packet with a signed little-endian number of 4 bytes, whose absolute value contains the error code (the error itself is actually negative).

-

For example, error Code 403 corresponds to situations where the corresponding HTTP error would have been returned by the HTTP protocol.

-

Error 404 (auth key not found) is returned when the specified auth key ID cannot be found by the DC.

-

Error 429 (transport flood) is returned when too many transport connections are established to the same IP in a too short lapse of time, or if any of the container/service message limits are reached.

-

Error 444 (invalid DC) is returned while creating an auth key, connecting to an MTProxy or in other contexts if an invalid DC ID is specified.

-

Transport obfuscation

-

Transport obfuscation is required to use the websocket transports.

-

Transport obfuscation to prevent ISP blocks is implemented using the following protocol, situated under the MTProto transport in the ISO/OSI stack, see the recap; this means that the payload is first wrapped in the MTProto transport envelope (all transports are supported), and then obfuscated:

-

Prior to establishing the connection (and eventually sending the protocol header of a specific MTProto transport), a 64-byte (512-bit) random initialization payload is generated.
During the generation process, special care must be taken in order to avoid a situation where that the first int (first four bytes) of the random string are equal to one of the known protocol identifiers (see above).
In particular, the first four bytes must not be equal to 0xdddddddd (padded intermediate), 0xeeeeeeee (intermediate), POST, GET, HEAD, or any of the HTTP methods that are accepted by the MTProto servers.
The first byte must also not be equal to 0xef (abridged).
Bytes 4-8 must also not be equal to 0x00000000, since that would indicate use of the full transport with the initial TCP sequence number (0).

-

The protocol identifier, if present, must be inserted in the initialization payload at byte offset 56: if its length is less than 4, it must be padded using the protocol identifier itself, to make its length 4 (0xef => 0xefefefef): the standalone protocol identifier must be not be sent aftwerwards.

-

This protocol is also (but not exclusively) used when connecting to MTProxies: only in this case, the DC ID in a specially encoded form must also be inserted in the initialization payload at offset 60.
The encoding simply consist of the DC ID in two-byte signed little-endian form; 10000 has to be added to the DC ID to connect to the test servers; it has to be made negative if the DC we're connecting to is a media (not CDN) DC.

-

Next, a secondary initialization payload is generated by reversing the primary initialization payload.

-

Two keys are extracted from both initialization payloads, using bytes at offsets 8-40: the key extracted from the primary payload is used as encryption key, the key extracted from the secondary payload is used as decryption key.

-

Two IVs are extracted from both initialization payloads, using bytes at offsets 40-56: the IV extracted from the primary payload is used as encryption IV, the IV extracted from the secondary payload is used as decryption IV.

-

Only if using MTProxy, the secret is used to provide connection with the MTProxy server.
The secret is a 16-byte string, usually distributed in its hexadecimal form along with the MTProxy host and port.

-

Often, a 17-byte version of the secret can be found: this simply indicates that the client should use a specific MTProto transport (based on the first byte, usually it's 0xdd, to indicate that the padded intermediate protocol should be used 0xdddddddd; however, clients should default to the padded intermediate transport whenever an additional byte in the secret is encountered).

-

The extracted encryption and decryption keys must be concatenated with the secret (the first byte of which should be ignored if it's the 17-byte version), and the SHA256 hash of such string should be used as encryption/decryption key.

-

The obtained encryption and decryption key/IV pairs must then be used with AES-256-CTR to encrypt and decrypt all outgoing and incoming payloads.

-

The first thing that must be encrypted using the encryption key is the initialization payload itself.
Then bytes 56-64 of the encrypted initialization payload are substituted in the original initialization payload: this is the part that contains the constant MTProto transport protocol identifier and the DC ID (only for MTProxies).

-

The final initialization payload must then be sent in the socket as first 64 bytes after the TCP handshake.

-

Example pseudocode for the generation of an MTProxy connection payload (media DC 4) using the obfuscated padded intermediate transport.
Warning: do not use the specified proxy secret in any MTProxy exposed on the internet.

-
protocol := 0xdddddddd
-dc := 0xfcff
-
-while 1:
-    init := (56 random bytes) + protocol + dc + (2 random bytes)
-
-    if init[0] == 0xef:
-      continue
-
-    first_int := substr(init, 0, 4)
-    if first_int == 0x44414548 || first_int == 0x54534f50 || first_int == 0x20544547 || first_int == 0x4954504f || first_int == 0x02010316 || first_int == 0xdddddddd || first_int == 0xeeeeeeee:
-      continue
-
-    second_int := substr(init, 0, 4)
-    if second_int == 0x00000000:
-      continue
-
-    break
-
-initRev := strrev(init)
-
-encryptKey := substr(init, 8, 32)
-encryptIV := substr(init, 40, 16)
-
-decryptKey := substr(initRev, 8, 32)
-decryptIV := substr(initRev, 40, 16)
-
-secret := substr(0xdd99999999999999999999999999999999, 1, 16)
-
-encryptKey = SHA256(encryptKey + secret)
-decryptKey = SHA256(decryptKey + secret)
-
-encryptedInit := CTR(encryptKey, encryptIV, init)
-
-finalInit := substr(init, 0, 56) + substr(encryptedInit, 56, 8)
-
-write(finalInit)
-
- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/mtproto/samples-auth_key.html b/data/corefork.telegram.org/mtproto/samples-auth_key.html deleted file mode 100644 index 54ce6ab2ee..0000000000 --- a/data/corefork.telegram.org/mtproto/samples-auth_key.html +++ /dev/null @@ -1,748 +0,0 @@ - - - - - samples-auth_key - - - - - - - - - - - - - -
- -
-
-
- -

samples-auth_key

- -

In the examples below, the transport headers are omitted:

-
-

For example, for an abridged version of the transport the client sends 0xef as the first byte (important: only prior to the very first data packet), then packet length is encoded by a single byte (0x01-0x7e = data length divided by 4; or 0x7f followed by 3 bytes (little endian) divided by 4) followed by the data themselves. In this case, server responses have the same form (although the server does not send 0xefas the first byte).

-
-

Detailed documentation on creating authorization keys is available here ».

-

1. Request for (p,q) Authorization

-
req_pq#60469778 nonce:int128 = ResPQ
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851e57ac42770964aExact unixtime * 2^32
message_length16, 420Message body length
%(req_pq)20, 460469778req_pq constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCRandom number
-

The header is 20 bytes long, the message body is 20 bytes long, and the entire message is 40 bytes in length.

-
0000 | 00 00 00 00 00 00 00 00 4A 96 70 27 C4 7A E5 51
-0010 | 14 00 00 00 78 97 46 60 3E 05 49 82 8C CA 27 E9
-0020 | 66 B3 01 A4 8F EC E2 FC
-

2. A response from the server has been received with the following content:

-
0000 | 00 00 00 00 00 00 00 00 01 C8 83 1E C9 7A E5 51
-0010 | 40 00 00 00 63 24 16 05 3E 05 49 82 8C CA 27 E9
-0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
-0030 | 77 BA 4A A5 73 90 73 30 08 17 ED 48 94 1A 08 F9
-0040 | 81 00 00 00 15 C4 B5 1C 01 00 00 00 21 6B E8 6C
-0050 | 02 2B B4 C3
-
Response decomposition using the following formula:
-
resPQ#05162463 nonce:int128 server_nonce:int128 pq:string server_public_key_fingerprints:Vector long = ResPQ 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851E57AC91E83C801Server message ID
message_length16, 464Message body length
%(resPQ)20, 405162463resPQ constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce40, 16A5CF4D33F4A11EA877BA4AA573907330Server-generated random number
pq56, 1217ED48941A08F981Single-byte prefix denoting length, an 8-byte string, and three bytes of padding
%(Vector long)68, 41cb5c415Vector long constructor number from TL schema
count72, 41Number of elements in key fingerprint list
fingerprints[]76, 8c3b42b026ce86b2164 lower-order bits of SHA1 (server_public_key)
-

The server_public_key public key has been selected whose fingerprint corresponds to the only one received from the server: c3b42b026ce86b21.

-

3. Pq = 17ED48941A08F981 decomposed into 2 prime cofactors:

-
p = 494C553B
-q = 53911073
-

4. encrypted_data Generation

-
p_q_inner_data#83c95aec pq:string p:string q:string nonce:int128 server_nonce:int128 new_nonce:int256 = P_Q_inner_data
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterOffset, Length in bytesValueDescription
%(p_q_inner_data)0, 483c95aecp_q_inner_data constructor number from TL schema
pq4, 1217ED48941A08F981Single-byte prefix denoting length, 8-byte string, and three bytes of padding
p16, 8494C553BFirst prime cofactor: single-byte prefix denoting length, 4-byte string, and three bytes of padding
q24, 853911073Second prime cofactor: single-byte prefix denoting length, 4-byte string, and three bytes of padding
nonce32, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce48, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
new_nonce64, 32311C85DB234AA2640AFC4A76A735CF5B 1F0FD68BD17FA181E1229AD867CC024DClient-generated random number
-

The serialization of P_Q_inner_data produces some string data. This is followed by encrypted_data:

-
SHA1 (data) = DB761C27718A2305044F71F2AD951629D78B2449
-RSA (data_with_hash, server_public_key) = 7BB0100A523161904D9C69FA04BC60DECFC5DD74B99995C768EB60D8716E2109BAF2D4601DAB6B09610DC11067BB89021E09471FCFA52DBD0F23204AD8CA8B012BF40A112F44695AB6C266955386114EF5211E6372227ADBD34995D3E0E5FF02EC63A43F9926878962F7C570E6A6E78BF8366AF917A5272675C46064BE62E3E202EFA8B1ADFB1C32A898C2987BE27B5F31D57C9BB963ABCB734B16F652CEDB4293CBB7C878A3A3FFAC9DBEA9DF7C67BC9E9508E111C78FC46E057F5C65ADE381D91FEE430A6B576A99BDF8551FDB1BE2B57069B1A45730618F27427E8A04720B4971EF4A9215983D68F2830C3EAA6E40385562F970D38A05C9F1246DC33438E6
-

The length of the final string was 256 bytes.

-
Request to Start Diffie-Hellman Key Exchange
-
req_DH_params#d712e4be nonce:int128 server_nonce:int128 p:string q:string public_key_fingerprint:long encrypted_data:string = Server_DH_Params
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851e57ac917717a27Exact unixtime * 2^32
message_length16, 4320Message body length
%(req_DH_params)20, 4d712e4bereq_DH_params constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce40, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
p56, 8494C553BFirst prime cofactor: single-byte prefix denoting length, 4-byte string, and three bytes of padding
q64, 853911073Second prime cofactor: single-byte prefix denoting length, 4-byte string, and three bytes of padding
public_key_fingerprint72, 8c3b42b026ce86b21Fingerprint of public key used
encrypted_data80, 260See aboveSee “Generation of encrypted_data"
-
0000 | 00 00 00 00 00 00 00 00 27 7A 71 17 C9 7A E5 51
-0010 | 40 01 00 00 BE E4 12 D7 3E 05 49 82 8C CA 27 E9
-0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
-0030 | 77 BA 4A A5 73 90 73 30 04 49 4C 55 3B 00 00 00
-0040 | 04 53 91 10 73 00 00 00 21 6B E8 6C 02 2B B4 C3
-0050 | FE 00 01 00 7B B0 10 0A 52 31 61 90 4D 9C 69 FA
-0060 | 04 BC 60 DE CF C5 DD 74 B9 99 95 C7 68 EB 60 D8
-0070 | 71 6E 21 09 BA F2 D4 60 1D AB 6B 09 61 0D C1 10
-0080 | 67 BB 89 02 1E 09 47 1F CF A5 2D BD 0F 23 20 4A
-0090 | D8 CA 8B 01 2B F4 0A 11 2F 44 69 5A B6 C2 66 95
-00A0 | 53 86 11 4E F5 21 1E 63 72 22 7A DB D3 49 95 D3
-00B0 | E0 E5 FF 02 EC 63 A4 3F 99 26 87 89 62 F7 C5 70
-00C0 | E6 A6 E7 8B F8 36 6A F9 17 A5 27 26 75 C4 60 64
-00D0 | BE 62 E3 E2 02 EF A8 B1 AD FB 1C 32 A8 98 C2 98
-00E0 | 7B E2 7B 5F 31 D5 7C 9B B9 63 AB CB 73 4B 16 F6
-00F0 | 52 CE DB 42 93 CB B7 C8 78 A3 A3 FF AC 9D BE A9
-0100 | DF 7C 67 BC 9E 95 08 E1 11 C7 8F C4 6E 05 7F 5C
-0110 | 65 AD E3 81 D9 1F EE 43 0A 6B 57 6A 99 BD F8 55
-0120 | 1F DB 1B E2 B5 70 69 B1 A4 57 30 61 8F 27 42 7E
-0130 | 8A 04 72 0B 49 71 EF 4A 92 15 98 3D 68 F2 83 0C
-0140 | 3E AA 6E 40 38 55 62 F9 70 D3 8A 05 C9 F1 24 6D
-0150 | C3 34 38 E6
-

5. A response from the server has been received with the following content:

-
0000 | 00 00 00 00 00 00 00 00 01 54 43 36 CB 7A E5 51
-0010 | 78 02 00 00 5C 07 E8 D0 3E 05 49 82 8C CA 27 E9
-0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
-0030 | 77 BA 4A A5 73 90 73 30 FE 50 02 00 28 A9 2F E2
-0040 | 01 73 B3 47 A8 BB 32 4B 5F AB 26 67 C9 A8 BB CE
-0050 | 64 68 D5 B5 09 A4 CB DD C1 86 24 0A C9 12 CF 70
-0060 | 06 AF 89 26 DE 60 6A 2E 74 C0 49 3C AA 57 74 1E
-0070 | 6C 82 45 1F 54 D3 E0 68 F5 CC C4 9B 44 44 12 4B
-0080 | 96 66 FF B4 05 AA B5 64 A3 D0 1E 67 F6 E9 12 86
-0090 | 7C 8D 20 D9 88 27 07 DC 33 0B 17 B4 E0 DD 57 CB
-00A0 | 53 BF AA FA 9E F5 BE 76 AE 6C 1B 9B 6C 51 E2 D6
-00B0 | 50 2A 47 C8 83 09 5C 46 C8 1E 3B E2 5F 62 42 7B
-00C0 | 58 54 88 BB 3B F2 39 21 3B F4 8E B8 FE 34 C9 A0
-00D0 | 26 CC 84 13 93 40 43 97 4D B0 35 56 63 30 38 39
-00E0 | 2C EC B5 1F 94 82 4E 14 0B 98 63 77 30 A4 BE 79
-00F0 | A8 F9 DA FA 39 BA E8 1E 10 95 84 9E A4 C8 34 67
-0100 | C9 2A 3A 17 D9 97 81 7C 8A 7A C6 1C 3F F4 14 DA
-0110 | 37 B7 D6 6E 94 9C 0A EC 85 8F 04 82 24 21 0F CC
-0120 | 61 F1 1C 3A 91 0B 43 1C CB D1 04 CC CC 8D C6 D2
-0130 | 9D 4A 5D 13 3B E6 39 A4 C3 2B BF F1 53 E6 3A CA
-0140 | 3A C5 2F 2E 47 09 B8 AE 01 84 4B 14 2C 1E E8 9D
-0150 | 07 5D 64 F6 9A 39 9F EB 04 E6 56 FE 36 75 A6 F8
-0160 | F4 12 07 8F 3D 0B 58 DA 15 31 1C 1A 9F 8E 53 B3
-0170 | CD 6B B5 57 2C 29 49 04 B7 26 D0 BE 33 7E 2E 21
-0180 | 97 7D A2 6D D6 E3 32 70 25 1C 2C A2 9D FC C7 02
-0190 | 27 F0 75 5F 84 CF DA 9A C4 B8 DD 5F 84 F1 D1 EB
-01A0 | 36 BA 45 CD DC 70 44 4D 8C 21 3E 4B D8 F6 3B 8A
-01B0 | B9 5A 2D 0B 41 80 DC 91 28 3D C0 63 AC FB 92 D6
-01C0 | A4 E4 07 CD E7 C8 C6 96 89 F7 7A 00 74 41 D4 A6
-01D0 | A8 38 4B 66 65 02 D9 B7 7F C6 8B 5B 43 CC 60 7E
-01E0 | 60 A1 46 22 3E 11 0F CB 43 BC 3C 94 2E F9 81 93
-01F0 | 0C DC 4A 1D 31 0C 0B 64 D5 E5 5D 30 8D 86 32 51
-0200 | AB 90 50 2C 3E 46 CC 59 9E 88 6A 92 7C DA 96 3B
-0210 | 9E B1 6C E6 26 03 B6 85 29 EE 98 F9 F5 20 64 19
-0220 | E0 3F B4 58 EC 4B D9 45 4A A8 F6 BA 77 75 73 CC
-0230 | 54 B3 28 89 5B 1D F2 5E AD 9F B4 CD 51 98 EE 02
-0240 | 2B 2B 81 F3 88 D2 81 D5 E5 BC 58 01 07 CA 01 A5
-0250 | 06 65 C3 2B 55 27 15 F3 35 FD 76 26 4F AD 00 DD
-0260 | D5 AE 45 B9 48 32 AC 79 CE 7C 51 1D 19 4B C4 2B
-0270 | 70 EF A8 50 BB 15 C2 01 2C 52 15 CA BF E9 7C E6
-0280 | 6B 8D 87 34 D0 EE 75 9A 63 8A F0 13
-
Response decomposition using the following formula:
-
server_DH_params_fail#79cb045d nonce:int128 server_nonce:int128 new_nonce_hash:int128 = Server_DH_Params;
-server_DH_params_ok#d0e8075c nonce:int128 server_nonce:int128 encrypted_answer:string = Server_DH_Params;
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851E57ACB36435401Exact unixtime * 2^32
message_length16, 4632Message body length
%(server_DH_params_ok)20, 4d0e8075cserver_DH_params_ok constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce40, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
encrypted_answer56, 596See belowSee “Decomposition of encrypted_answer"
-
Conversion of encrypted_answer into answer:
-
encrypted_answer = 28A92FE20173B347A8BB324B5FAB2667C9A8BBCE6468D5B509A4CBDDC186240AC912CF7006AF8926DE606A2E74C0493CAA57741E6C82451F54D3E068F5CCC49B4444124B9666FFB405AAB564A3D01E67F6E912867C8D20D9882707DC330B17B4E0DD57CB53BFAAFA9EF5BE76AE6C1B9B6C51E2D6502A47C883095C46C81E3BE25F62427B585488BB3BF239213BF48EB8FE34C9A026CC8413934043974DB03556633038392CECB51F94824E140B98637730A4BE79A8F9DAFA39BAE81E1095849EA4C83467C92A3A17D997817C8A7AC61C3FF414DA37B7D66E949C0AEC858F048224210FCC61F11C3A910B431CCBD104CCCC8DC6D29D4A5D133BE639A4C32BBFF153E63ACA3AC52F2E4709B8AE01844B142C1EE89D075D64F69A399FEB04E656FE3675A6F8F412078F3D0B58DA15311C1A9F8E53B3CD6BB5572C294904B726D0BE337E2E21977DA26DD6E33270251C2CA29DFCC70227F0755F84CFDA9AC4B8DD5F84F1D1EB36BA45CDDC70444D8C213E4BD8F63B8AB95A2D0B4180DC91283DC063ACFB92D6A4E407CDE7C8C69689F77A007441D4A6A8384B666502D9B77FC68B5B43CC607E60A146223E110FCB43BC3C942EF981930CDC4A1D310C0B64D5E55D308D863251AB90502C3E46CC599E886A927CDA963B9EB16CE62603B68529EE98F9F5206419E03FB458EC4BD9454AA8F6BA777573CC54B328895B1DF25EAD9FB4CD5198EE022B2B81F388D281D5E5BC580107CA01A50665C32B552715F335FD76264FAD00DDD5AE45B94832AC79CE7C511D194BC42B70EFA850BB15C2012C5215CABFE97CE66B8D8734D0EE759A638AF013
-tmp_aes_key = F011280887C7BB01DF0FC4E17830E0B91FBB8BE4B2267CB985AE25F33B527253
-tmp_aes_iv = 3212D579EE35452ED23E0D0C92841AA7D31B2E9BDEF2151E80D15860311C85DB
-answer = BA0D89B53E0549828CCA27E966B301A48FECE2FCA5CF4D33F4A11EA877BA4AA57390733002000000FE000100C71CAEB9C6B1C9048E6C522F70F13F73980D40238E3E21C14934D037563D930F48198A0AA7C14058229493D22530F4DBFA336F6E0AC925139543AED44CCE7C3720FD51F69458705AC68CD4FE6B6B13ABDC9746512969328454F18FAF8C595F642477FE96BB2A941D5BCD1D4AC8CC49880708FA9B378E3C4F3A9060BEE67CF9A4A4A695811051907E162753B56B0F6B410DBA74D8A84B2A14B3144E0EF1284754FD17ED950D5965B4B9DD46582DB1178D169C6BC465B0D6FF9CA3928FEF5B9AE4E418FC15E83EBEA0F87FA9FF5EED70050DED2849F47BF959D956850CE929851F0D8115F635B105EE2E4E15D04B2454BF6F4FADF034B10403119CD8E3B92FCC5BFE000100262AABA621CC4DF587DC94CF8252258C0B9337DFB47545A49CDD5C9B8EAE7236C6CADC40B24E88590F1CC2CC762EBF1CF11DCC0B393CAAD6CEE4EE5848001C73ACBB1D127E4CB93072AA3D1C8151B6FB6AA6124B7CD782EAF981BDCFCE9D7A00E423BD9D194E8AF78EF6501F415522E44522281C79D906DDB79C72E9C63D83FB2A940FF779DFB5F2FD786FB4AD71C9F08CF48758E534E9815F634F1E3A80A5E1C2AF210C5AB762755AD4B2126DFA61A77FA9DA967D65DFD0AFB5CDF26C4D4E1A88B180F4E0D0B45BA1484F95CB2712B50BF3F5968D9D55C99C0FB9FB67BFF56D7D4481B634514FBA3488C4CDA2FC0659990E8E868B28632875A9AA703BCDCE8FCB7AE551
-
Server_DH_inner_data decomposition using the following formula:
-
server_DH_inner_data#b5890dba nonce:int128 server_nonce:int128 g:int dh_prime:string g_a:string server_time:int = Server_DH_inner_data;
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterOffset, Length in bytesValueDescription
%(server_DH_inner_data)0, 4b5890dbaserver_DH_inner_data constructor number from TL schema
nonce4, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce20, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
g36, 42Value received from server in Step 2
dh_prime40, 260C71CAEB9C6B1C9048E6C522F70F13F73 980D40238E3E21C14934D037563D930F 48198A0AA7C14058229493D22530F4DB FA336F6E0AC925139543AED44CCE7C37 20FD51F69458705AC68CD4FE6B6B13AB DC9746512969328454F18FAF8C595F64 2477FE96BB2A941D5BCD1D4AC8CC4988 0708FA9B378E3C4F3A9060BEE67CF9A4 A4A695811051907E162753B56B0F6B41 0DBA74D8A84B2A14B3144E0EF1284754 FD17ED950D5965B4B9DD46582DB1178D 169C6BC465B0D6FF9CA3928FEF5B9AE4 E418FC15E83EBEA0F87FA9FF5EED7005 0DED2849F47BF959D956850CE929851F 0D8115F635B105EE2E4E15D04B2454BF 6F4FADF034B10403119CD8E3B92FCC5B
g_a300, 260262AABA621CC4DF587DC94CF8252258C 0B9337DFB47545A49CDD5C9B8EAE7236 C6CADC40B24E88590F1CC2CC762EBF1C F11DCC0B393CAAD6CEE4EE5848001C73 ACBB1D127E4CB93072AA3D1C8151B6FB 6AA6124B7CD782EAF981BDCFCE9D7A00 E423BD9D194E8AF78EF6501F415522E4 4522281C79D906DDB79C72E9C63D83FB 2A940FF779DFB5F2FD786FB4AD71C9F0 8CF48758E534E9815F634F1E3A80A5E1 C2AF210C5AB762755AD4B2126DFA61A7 7FA9DA967D65DFD0AFB5CDF26C4D4E1A 88B180F4E0D0B45BA1484F95CB2712B5 0BF3F5968D9D55C99C0FB9FB67BFF56D 7D4481B634514FBA3488C4CDA2FC0659 990E8E868B28632875A9AA703BCDCE8F
server_time560, 41373993675Server time
-

6. Random number b is computed:

-
b = 6F620AFA575C9233EB4C014110A7BCAF49464F798A18A0981FEA1E05E8DA67D9681E0FD6DF0EDF0272AE3492451A84502F2EFC0DA18741A5FB80BD82296919A70FAA6D07CBBBCA2037EA7D3E327B61D585ED3373EE0553A91CBD29B01FA9A89D479CA53D57BDE3A76FBD922A923A0A38B922C1D0701F53FF52D7EA9217080163A64901E766EB6A0F20BC391B64B9D1DD2CD13A7D0C946A3A7DF8CEC9E2236446F646C42CFE2B60A2A8D776E56C8D7519B08B88ED0970E10D12A8C9E355D765F2B7BBB7B4CA9360083435523CB0D57D2B106FD14F94B4EEE79D8AC131CA56AD389C84FE279716F8124A543337FB9EA3D988EC5FA63D90A4BA3970E7A39E5C0DE5
-
Generation of encrypted_data
-
client_DH_inner_data#6643b654 nonce:int128 server_nonce:int128 retry_id:long g_b:string = Client_DH_Inner_Data
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterOffset, Length in bytesValueDescription
%(client_DH_inner_data)0, 46643b654client_DH_inner_data constructor number from TL schema
nonce4, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce20, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
retry_id36, 80First attempt
g_b44, 26073700E7BFC7AEEC828EB8E0DCC04D09A 0DD56A1B4B35F72F0B55FCE7DB7EBB72 D7C33C5D4AA59E1C74D09B01AE536B31 8CFED436AFDB15FE9EB4C70D7F0CB14E 46DBBDE9053A64304361EB358A9BB32E 9D5C2843FE87248B89C3F066A7D5876D 61657ACC52B0D81CD683B2A0FA93E8AD AB20377877F3BC3369BBF57B10F5B589 E65A9C27490F30A0C70FFCFD3453F5B3 79C1B9727A573CFFDCA8D23C721B135B 92E529B1CDD2F7ABD4F34DAC4BE1EEAF 60993DDE8ED45890E4F47C26F2C0B2E0 37BB502739C8824F2A99E2B1E7E41658 3417CC79A8807A4BDAC6A5E9805D4F61 86C37D66F6988C9F9C752896F3D34D25 529263FAF2670A09B2A59CE35264511Fg^b mod dh_prime
-

The serialization of Client_DH_Inner_Data produces some string data. This is followed by encrypted_data:

-
data_with_hash := SHA1(data) + data + (0-15 random bytes); such that the length be divisible by 16;
-AES256_ige_encrypt (data_with_hash, tmp_aes_key, tmp_aes_iv) = 928A4957D0463B525C1CC48AABAA030A256BE5C746792C84CA4C5A0DF60AC799048D98A38A8480EDCF082214DFC79DCB9EE34E206513E2B3BC1504CFE6C9ADA46BF9A03CA74F192EAF8C278454ADABC795A566615462D31817382984039505F71CB33A41E2527A4B1AC05107872FED8E3ABCEE1518AE965B0ED3AED7F67479155BDA8E4C286B64CDF123EC748CF289B1DB02D1907B562DF462D8582BA6F0A3022DC2D3504D69D1BA48B677E3A830BFAFD67584C8AA24E1344A8904E305F9587C92EF964F0083F50F61EAB4A393EAA33C9270294AEDC7732891D4EA1599F52311D74469D2112F4EDF3F342E93C8E87E812DC3989BAECFE6740A46077524C75093F5A5405736DE8937BB6E42C9A0DCF22CA53227D462BCCC2CFE94B6FE86AB7FBFA395021F66661AF7C0024CA2986CA03F3476905407D1EA9C010B763258DB1AA2CC7826D91334EFC1FDC665B67FE45ED0
-

The length of the final string was 336 bytes.

-
Request
-
set_client_DH_params#f5045f1f nonce:int128 server_nonce:int128 encrypted_data:string = Set_client_DH_params_answer;
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterOffset, Length in bytesValueDescription
auth_key_id0, 80Since message is in plain text
message_id8, 851e57acd2aa32c6dExact unixtime * 2^32
message_length16, 4376Message body length
%(set_client_DH_params)20, 4f5045f1fset_client_DH_params constructor number from TL schema
nonce24, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce40, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
encrypted_data56, 340See aboveSee “Generation of encrypted_data"
-
0000 | 00 00 00 00 00 00 00 00 6D 2C A3 2A CD 7A E5 51
-0010 | 78 01 00 00 1F 5F 04 F5 3E 05 49 82 8C CA 27 E9
-0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
-0030 | 77 BA 4A A5 73 90 73 30 FE 50 01 00 92 8A 49 57
-0040 | D0 46 3B 52 5C 1C C4 8A AB AA 03 0A 25 6B E5 C7
-0050 | 46 79 2C 84 CA 4C 5A 0D F6 0A C7 99 04 8D 98 A3
-0060 | 8A 84 80 ED CF 08 22 14 DF C7 9D CB 9E E3 4E 20
-0070 | 65 13 E2 B3 BC 15 04 CF E6 C9 AD A4 6B F9 A0 3C
-0080 | A7 4F 19 2E AF 8C 27 84 54 AD AB C7 95 A5 66 61
-0090 | 54 62 D3 18 17 38 29 84 03 95 05 F7 1C B3 3A 41
-00A0 | E2 52 7A 4B 1A C0 51 07 87 2F ED 8E 3A BC EE 15
-00B0 | 18 AE 96 5B 0E D3 AE D7 F6 74 79 15 5B DA 8E 4C
-00C0 | 28 6B 64 CD F1 23 EC 74 8C F2 89 B1 DB 02 D1 90
-00D0 | 7B 56 2D F4 62 D8 58 2B A6 F0 A3 02 2D C2 D3 50
-00E0 | 4D 69 D1 BA 48 B6 77 E3 A8 30 BF AF D6 75 84 C8
-00F0 | AA 24 E1 34 4A 89 04 E3 05 F9 58 7C 92 EF 96 4F
-0100 | 00 83 F5 0F 61 EA B4 A3 93 EA A3 3C 92 70 29 4A
-0110 | ED C7 73 28 91 D4 EA 15 99 F5 23 11 D7 44 69 D2
-0120 | 11 2F 4E DF 3F 34 2E 93 C8 E8 7E 81 2D C3 98 9B
-0130 | AE CF E6 74 0A 46 07 75 24 C7 50 93 F5 A5 40 57
-0140 | 36 DE 89 37 BB 6E 42 C9 A0 DC F2 2C A5 32 27 D4
-0150 | 62 BC CC 2C FE 94 B6 FE 86 AB 7F BF A3 95 02 1F
-0160 | 66 66 1A F7 C0 02 4C A2 98 6C A0 3F 34 76 90 54
-0170 | 07 D1 EA 9C 01 0B 76 32 58 DB 1A A2 CC 78 26 D9
-0180 | 13 34 EF C1 FD C6 65 B6 7F E4 5E D0
-

7. Computing auth_key using formula g^{ab} mod dh_prime:

-
auth_key = AB96E207C631300986F30EF97DF55E179E63C112675F0CE502EE76D74BBEE6CBD1E95772818881E9F2FF54BD52C258787474F6A7BEA61EABE49D1D01D55F64FC07BC31685716EC8FB46FEACF9502E42CFD6B9F45A08E90AA5C2B5933AC767CBE1CD50D8E64F89727CA4A1A5D32C0DB80A9FCDBDDD4F8D5A1E774198F1A4299F927C484FEEC395F29647E43C3243986F93609E23538C21871DF50E00070B3B6A8FA9BC15628E8B43FF977409A61CEEC5A21CF7DFB5A4CC28F5257BC30CD8F2FB92FBF21E28924065F50E0BBD5E11A420300E2C136B80E9826C6C5609B5371B7850AA628323B6422F3A94F6DFDE4C3DC1EA60F7E11EE63122B3F39CBD1A8430157
-

8. The server verifies that auth_key_hash is unique.

-

The key is unique.

-

9. A response from the server has been received with the following content:

-
0000 | 00 00 00 00 00 00 00 00 01 30 AA C5 CE 7A E5 51
-0010 | 34 00 00 00 34 F7 CB 3B 3E 05 49 82 8C CA 27 E9
-0020 | 66 B3 01 A4 8F EC E2 FC A5 CF 4D 33 F4 A1 1E A8
-0030 | 77 BA 4A A5 73 90 73 30 CC EB C0 21 72 66 E1 ED
-0040 | EC 7F B0 A0 EE D6 C2 20
-

Set_client_DH_params_answer decomposition using the following formula:

-
dh_gen_ok#3bcbf734 nonce:int128 server_nonce:int128 new_nonce_hash1:int128 = Set_client_DH_params_answer;
-dh_gen_retry#46dc1fb9 nonce:int128 server_nonce:int128 new_nonce_hash2:int128 = Set_client_DH_params_answer;
-dh_gen_fail#a69dae02 nonce:int128 server_nonce:int128 new_nonce_hash3:int128 = Set_client_DH_params_answer;
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParameterOffset, Length in bytesValueDescription
%(dh_gen_ok)0, 43bcbf734dh_gen_ok constructor number from TL schema
nonce4, 163E0549828CCA27E966B301A48FECE2FCValue generated by client in Step 1
server_nonce20, 16A5CF4D33F4A11EA877BA4AA573907330Value received from server in Step 2
new_nonce_hash136, 16CCEBC0217266E1EDEC7FB0A0EED6C220
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/mtproto/security_guidelines.html b/data/corefork.telegram.org/mtproto/security_guidelines.html deleted file mode 100644 index a4627d6170..0000000000 --- a/data/corefork.telegram.org/mtproto/security_guidelines.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - Security Guidelines for Client Developers - - - - - - - - - - - - - -
- -
-
-
- -

Security Guidelines for Client Developers

- -
- -

See also:

-

- -

While MTProto is designed to be a reasonably fast and secure protocol, its advantages can be easily negated by careless implementation. We collected some security guidelines for client software developers on this page. All Telegram clients are required to comply.

-
-

Note that as of version 4.6, major Telegram clients are using MTProto 2.0. -MTProto v.1.0 is deprecated and is currently being phased out.

-
-

Diffie-Hellman key exchange

-

We use DH key exchange in two cases:

- -

In both cases, there are some verifications to be done whenever DH is used:

-

Validation of DH parameters

-

Client is expected to check whether p = dh_prime is a safe 2048-bit prime (meaning that both p and (p-1)/2 are prime, and that 2^2047 < p < 2^2048), and that g generates a cyclic subgroup of prime order (p-1)/2, i.e. is a quadratic residue mod p. Since g is always equal to 2, 3, 4, 5, 6 or 7, this is easily done using quadratic reciprocity law, yielding a simple condition on p mod 4g -- namely, p mod 8 = 7 for g = 2; p mod 3 = 2 for g = 3; no extra condition for g = 4; p mod 5 = 1 or 4 for g = 5; p mod 24 = 19 or 23 for g = 6; and p mod 7 = 3, 5 or 6 for g = 7. After g and p have been checked by the client, it makes sense to cache the result, so as not to repeat lengthy computations in future.

-

If the verification takes too long (which is the case for older mobile devices), one might initially run only 15 Miller--Rabin iterations (use parameter 30 in Java) for verifying primeness of p and (p - 1)/2 with error probability not exceeding one billionth, and do more iterations in the background later.

-

Another way to optimize this is to embed into the client application code a small table with some known "good" couples (g,p) (or just known safe primes p, since the condition on g is easily verified during execution), checked during code generation phase, so as to avoid doing such verification during runtime altogether. The server rarely changes these values, thus one usually needs to put the current value of server's dh_prime into such a table. For example, the current value of dh_prime equals (in big-endian byte order)

-
C7 1C AE B9 C6 B1 C9 04 8E 6C 52 2F 70 F1 3F 73 98 0D 40 23 8E 3E 21 C1 49 34 D0 37 56 3D 93 0F 48 19 8A 0A A7 C1 40 58 22 94 93 D2 25 30 F4 DB FA 33 6F 6E 0A C9 25 13 95 43 AE D4 4C CE 7C 37 20 FD 51 F6 94 58 70 5A C6 8C D4 FE 6B 6B 13 AB DC 97 46 51 29 69 32 84 54 F1 8F AF 8C 59 5F 64 24 77 FE 96 BB 2A 94 1D 5B CD 1D 4A C8 CC 49 88 07 08 FA 9B 37 8E 3C 4F 3A 90 60 BE E6 7C F9 A4 A4 A6 95 81 10 51 90 7E 16 27 53 B5 6B 0F 6B 41 0D BA 74 D8 A8 4B 2A 14 B3 14 4E 0E F1 28 47 54 FD 17 ED 95 0D 59 65 B4 B9 DD 46 58 2D B1 17 8D 16 9C 6B C4 65 B0 D6 FF 9C A3 92 8F EF 5B 9A E4 E4 18 FC 15 E8 3E BE A0 F8 7F A9 FF 5E ED 70 05 0D ED 28 49 F4 7B F9 59 D9 56 85 0C E9 29 85 1F 0D 81 15 F6 35 B1 05 EE 2E 4E 15 D0 4B 24 54 BF 6F 4F AD F0 34 B1 04 03 11 9C D8 E3 B9 2F CC 5B
-

g_a and g_b validation

-

Apart from the conditions on the Diffie-Hellman prime dh_prime and generator g, both sides are to check that g, g_a and g_b are greater than 1 and less than dh_prime - 1. We recommend checking that g_a and g_b are between 2^{2048-64} and dh_prime - 2^{2048-64} as well.

-

Checking SHA1 hash values during key generation

-

Once the client receives a server_DH_params_ok answer in step 5) of the Authorization Key generation protocol and decrypts it obtaining answer_with_hash, it MUST check that

-
answer_with_hash := SHA1(answer) + answer + (0-15 random bytes)
-

In other words, the first 20 bytes of answer_with_hash must be equal to SHA1 of the remainder of the decrypted message without the padding random bytes.

-

Checking nonce, server_nonce and new_nonce fields

-

When the client receives and/or decrypts server messages during creation of Authorization Key, and these messages contain some nonce fields already known to the client from messages previously obtained during the same run of the protocol, the client is to check that these fields indeed contain the values previosly known.

-

Using secure pseudorandom number generator to create DH secret parameters a and b

-

Client must use a cryptographically secure PRNG to generate secret exponents a or b for DH key exchange. For secret chats, the client might request some entropy (random bytes) from the server while invoking messages.getDhConfig and feed these random bytes into its PRNG (for example, by PRNG_seed if OpenSSL library is used), but never using these "random" bytes by themselves or replacing by them the local PRNG seed. One should mix bytes received from server into local PRNG seed.

-

MTProto Encrypted Messages

-

Some important checks are to be done while sending and especially receiving encrypted MTProto messages.

-

Checking SHA256 hash value of msg_key

-

msg_key is used not only to compute the AES key and IV to decrypt the received message. After decryption, the client MUST check that msg_key is indeed equal to SHA256 of the plaintext obtained as the result of decryption (including the final 12...1024 padding bytes), prepended with 32 bytes taken from the auth_key, as explained in MTProto 2.0 Description.

-

If an error is encountered before this check could be performed, the client must perform the msg_key check anyway before returning any result. Note that the response to any error encountered before the msg_key check must be the same as the response to a failed msg_key check.

-

Checking message length

-

The client must check that the length of the message or container obtained from the decrypted message (computed from its length field) does not exceed the total size of the plaintext, and that the difference (i.e. the length of the random padding) lies in the range from 12 to 1024 bytes.

-

The length should be always divisible by 4 and non-negative. On no account the client is to access data past the end of the decryption buffer containing the plaintext message.

-

Checking session_id

-

The client is to check that the session_id field in the decrypted message indeed equals to that of an active session created by the client.

-

Checking msg_id

-

The client must check that msg_id has even parity for messages from client to server, and odd parity for messages from server to client.

-

In addition, the identifiers (msg_id) of the last N messages received from the other side must be stored, and if a message comes in with an msg_id lower than all or equal to any of the stored values, that message is to be ignored. Otherwise, the new message msg_id is added to the set, and, if the number of stored msg_id values is greater than N, the oldest (i. e. the lowest) is discarded.

-

In addition, msg_id values that belong over 30 seconds in the future or over 300 seconds in the past are to be ignored (recall that msg_id approximately equals unixtime * 2^32). This is especially important for the server. The client would also find this useful (to protect from a replay attack), but only if it is certain of its time (for example, if its time has been synchronized with that of the server).

-

Certain client-to-server service messages containing data sent by the client to the server (for example, msg_id of a recent client query) may, nonetheless, be processed on the client even if the time appears to be “incorrect”. This is especially true of messages to change server_salt and notifications about invalid time on the client. See Mobile Protocol: Service Messages.

-

Behavior in case of mismatch

-

If one of the checks listed above fails, the client is to completely discard the message obtained from server. We also recommend closing and reestablishing the TCP connection to the server, then retrying the operation or the whole key generation protocol.

-

No information from incorrect messages can be used. Even if the application throws an exception and dies, this is much better than continuing with invalid data.

-

Notice that invalid messages will infrequently appear during normal work even if no malicious tampering is being done. This is due to network transmission errors. We recommend ignoring the invalid message and closing the TCP connection, then creating a new TCP connection to the server and retrying the original query.

-
-

The previous version of security recommendations relevant for MTProto 1.0 clients is available here.

-
- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/mtproto/security_guidelines_v1.html b/data/corefork.telegram.org/mtproto/security_guidelines_v1.html deleted file mode 100644 index 7240af0216..0000000000 --- a/data/corefork.telegram.org/mtproto/security_guidelines_v1.html +++ /dev/null @@ -1,175 +0,0 @@ - - - - - Security Guidelines for Client Developers (v.1.0, DEPRECATED) - - - - - - - - - - - - - -
- -
-
-
- -

Security Guidelines for Client Developers (v.1.0, DEPRECATED)

- -
- -
-

This document describes security recommendations for clients using MTProto 1.0, its status is DEPRECATED. -For up-to-date security recommendations, kindly see this document.

-
-

See also:

-

- -

While MTProto is designed to be a reasonably fast and secure protocol, its advantages can be easily negated by careless implementation. We collected some security guidelines for client software developers on this page. All Telegram clients are required to comply with these.

-

Diffie--Hellman key exchange

-

We use DH key exchange in two cases:

- -

In both cases, there are some verifications to be done whenever DH is used:

-

Validation of DH parameters

-

Client is expected to check whether p = dh_prime is a safe 2048-bit prime (meaning that both p and (p-1)/2 are prime, and that 2^2047 < p < 2^2048), and that g generates a cyclic subgroup of prime order (p-1)/2, i.e. is a quadratic residue mod p. Since g is always equal to 2, 3, 4, 5, 6 or 7, this is easily done using quadratic reciprocity law, yielding a simple condition on p mod 4g -- namely, p mod 8 = 7 for g = 2; p mod 3 = 2 for g = 3; no extra condition for g = 4; p mod 5 = 1 or 4 for g = 5; p mod 24 = 19 or 23 for g = 6; and p mod 7 = 3, 5 or 6 for g = 7. After g and p have been checked by the client, it makes sense to cache the result, so as not to repeat lengthy computations in future.

-

If the verification takes too long (which is the case for older mobile devices), one might initially run only 15 Miller--Rabin iterations (use parameter 30 in Java) for verifying primeness of p and (p - 1)/2 with error probability not exceeding one billionth, and do more iterations in the background later.

-

Another way to optimize this is to embed into the client application code a small table with some known "good" couples (g,p) (or just known safe primes p, since the condition on g is easily verified during execution), checked during code generation phase, so as to avoid doing such verification during runtime altogether. The server rarely changes these values, thus one usually needs to put the current value of server's dh_prime into such a table. For example, the current value of dh_prime equals (in big-endian byte order)

-
C7 1C AE B9 C6 B1 C9 04 8E 6C 52 2F 70 F1 3F 73 98 0D 40 23 8E 3E 21 C1 49 34 D0 37 56 3D 93 0F 48 19 8A 0A A7 C1 40 58 22 94 93 D2 25 30 F4 DB FA 33 6F 6E 0A C9 25 13 95 43 AE D4 4C CE 7C 37 20 FD 51 F6 94 58 70 5A C6 8C D4 FE 6B 6B 13 AB DC 97 46 51 29 69 32 84 54 F1 8F AF 8C 59 5F 64 24 77 FE 96 BB 2A 94 1D 5B CD 1D 4A C8 CC 49 88 07 08 FA 9B 37 8E 3C 4F 3A 90 60 BE E6 7C F9 A4 A4 A6 95 81 10 51 90 7E 16 27 53 B5 6B 0F 6B 41 0D BA 74 D8 A8 4B 2A 14 B3 14 4E 0E F1 28 47 54 FD 17 ED 95 0D 59 65 B4 B9 DD 46 58 2D B1 17 8D 16 9C 6B C4 65 B0 D6 FF 9C A3 92 8F EF 5B 9A E4 E4 18 FC 15 E8 3E BE A0 F8 7F A9 FF 5E ED 70 05 0D ED 28 49 F4 7B F9 59 D9 56 85 0C E9 29 85 1F 0D 81 15 F6 35 B1 05 EE 2E 4E 15 D0 4B 24 54 BF 6F 4F AD F0 34 B1 04 03 11 9C D8 E3 B9 2F CC 5B
-

g_a and g_b validation

-

Apart from the conditions on the Diffie-Hellman prime dh_prime and generator g, both sides are to check that g, g_a and g_b are greater than 1 and less than dh_prime - 1. We recommend checking that g_a and g_b are between 2^{2048-64} and dh_prime - 2^{2048-64} as well.

-

Checking SHA1 hash values

-

Once the client receives a server_DH_params_ok answer in step 5) of the Authorization Key generation protocol and decrypts it obtaining answer_with_hash, it MUST check that

-
answer_with_hash := SHA1(answer) + answer + (0-15 random bytes)
-

In other words, the first 20 bytes of answer_with_hash must be equal to SHA1 of the remainder of the decrypted message without the padding random bytes.

-

Checking nonce, server_nonce and new_nonce fields

-

When the client receives and/or decrypts server messages during creation of Authorization Key, and these messages contain some nonce fields already known to the client from messages previously obtained during the same run of the protocol, the client is to check that these fields indeed contain the values previosly known.

-

Using secure pseudorandom number generator to create DH secret parameters a and b

-

Client must use a cryptographically secure PRNG to generate secret exponents a or b for DH key exchange. For secret chats, the client might request some entropy (random bytes) from the server while invoking messages.getDhConfig and feed these random bytes into its PRNG (for example, by PRNG_seed if OpenSSL library is used), but never using these "random" bytes by themselves or replacing by them the local PRNG seed. One should mix bytes received from server into local PRNG seed.

-

MTProto Encrypted Messages

-

Some important checks are to be done while sending and especially receiving encrypted MTProto messages.

-

Checking SHA1 hash value of msg_key

-

msg_key is used not only to compute the AES key and IV to decrypt the received message. After decryption, the client MUST check that msg_key is indeed equal to SHA1 of the plaintext obtained as the result of decryption (without the final padding bytes).

-

If an error is encountered before this check could be performed, the client must perform the msg-key check anyway before returning any result. Note that the response to any error encountered before the msg_key check must be the same as the response to a failed msg_key check.

-

Checking message length

-

The client is to check that the length of the message or container obtained from the decrypted message (computed from its length field) does not exceed the total size of the plaintext, and that the difference is not more than 15 bytes. Apart from this, knowing the total length is important for the previous verification.

-

The length should be always divisible by 4 and non-negative. On no account the client is to access data past the end of the decryption buffer containing the plaintext message.

-

Checking session_id

-

The client is to check that the session_id field in the decrypted message indeed equals to that of an active session created by the client.

-

Checking msg_id

-

The client must check that msg_id has even parity for messages from client to server, and odd parity for messages from server to client.

-

In addition, the identifiers (msg_id) of the last N messages received from the other side must be stored, and if a message comes in with an msg_id lower than all or equal to any of the stored values, that message is to be ignored. Otherwise, the new message msg_id is added to the set, and, if the number of stored msg_id values is greater than N, the oldest (i. e. the lowest) is discarded.

-

In addition, msg_id values that belong over 30 seconds in the future or over 300 seconds in the past are to be ignored (recall that msg_id approximately equals unixtime * 2^32). This is especially important for the server. The client would also find this useful (to protect from a replay attack), but only if it is certain of its time (for example, if its time has been synchronized with that of the server).

-

Certain client-to-server service messages containing data sent by the client to the server (for example, msg_id of a recent client query) may, nonetheless, be processed on the client even if the time appears to be “incorrect”. This is especially true of messages to change server_salt and notifications about invalid time on the client. See Mobile Protocol: Service Messages.

-

Behavior in case of mismatch

-

If one of the checks listed above fails, the client is to completely discard the message obtained from server. We also recommend closing and reestablishing the TCP connection to the server, then retrying the operation or the whole key generation protocol.

-

No information from incorrect messages can be used. Even if the application throws an exception and dies, this is much better than continuing with invalid data.

-

Notice that invalid messages will infrequently appear during normal work even if no malicious tampering is being done. This is due to network transmission errors. We recommend ignoring the invalid message and closing the TCP connection, then creating a new TCP connection to the server and retrying the original query.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/mtproto/serialize.html b/data/corefork.telegram.org/mtproto/serialize.html deleted file mode 100644 index e2028a2386..0000000000 --- a/data/corefork.telegram.org/mtproto/serialize.html +++ /dev/null @@ -1,240 +0,0 @@ - - - - - Binary Data Serialization - - - - - - - - - - - - - -
- -
-
-
- -

Binary Data Serialization

- -

MTProto operation requires that elementary and composite data types as well as queries to which such data types are passed as arguments or by which they are returned, be transmitted in binary format (i. e. serialized) . -The TL language is used to describe the data types to be serialized.

-

General Definitions

-

For our purposes, we can identify a type with the set of its (serialized) values understood as strings (finite sequences) of 32-bit numbers (transmitted in little endian order).

-

Therefore:

-
    -
  • Alphabet (A), in this case, is a set of 32-bit numbers (normally, signed, i. e. between -2^31 and 2^31 - 1).
  • -
  • Value, in this case, is the same as a string in Alphabet A, i. e. a finite (possibly, empty) sequence of 32-bit numbers. The set of all such sequences is designated as A*.
  • -
  • Type, for our purposes, is the same as the set of legal values of a type, i. e. some set T which is a subset of A* and is a prefix code (i. e. no element of T may be a prefix for any other element). Therefore, any sequence from A* can contain no more than one prefix that is a member of T.
  • -
  • Value of Type T is any sequence (value) which is a member of T as a subset of A*.
  • -
  • Compatible Types are the types T and T’ not intersecting as subsets of A*, such that the union of T and T' is a prefix code.
  • -
  • Coordinated System of Types is a finite or infinite set of types T_1, ..., T_n, ..., such that any two types from this set are compatible.
  • -
  • Data Type is the same as type in the sense of the definition above.
  • -
  • Functional Type is a type describing a function; it is not a type in the sense of the definition above. Initially, we ignore the existence of functional types and describe only the data types; however, in reality, functional types will later be implemented in some extension of this system using the so-called temporary combinators.
  • -
-

Combinators, Constructors, Composite Data Types

-
    -
  • -

    Combinator is a function that takes arguments of certain types and returns a value of some other type. We normally look at combinators whose argument and result types are data types (rather than functional types).

    -
  • -
  • -

    Arity (of combinator) is a non-negative integer, the number of combinator arguments.

    -
  • -
  • -

    Combinator identifier is an identifier beginning with a lowercase Roman letter that uniquely identifies a combinator.

    -
  • -
  • -

    Combinator number or combinator name is a 32-bit number (i.e., an element of A) that uniquely identifies a combinator. Most often, it is CRC32 of the string containing the combinator description without the final semicolon, and with one space between contiguous lexemes. This always falls in the range from 0x01000000 to 0xffffff00. The highest 256 values are reserved for the so-called temporal-logic combinators used to transmit functions. We frequently denote as combinator the combinator name with single quotes: ‘combinator’.

    -
  • -
  • -

    Combinator description is a string of format combinator_name type_arg_1 ... type_arg_N = type_res; where N stands for the arity of the combinator, type_arg_i is the type of the i-th argument (or rather, a string with the combinator name), and type_res is the combinator value type.

    -
  • -
  • -

    Constructor is a combinator that cannot be computed (reduced). This is used to represent composite data types. For example, combinator ‘int_tree’ with description int_tree IntTree int IntTree = IntTree, alongside combinator empty_tree = IntTree, may be used to define a composite data type called “IntTree” that takes on values in the form of binary trees with integers as nodes.

    -
  • -
  • -

    Function (functional combinator) is a combinator which may be computed (reduced) on condition that the requisite number of arguments of requisite types are provided. The result of the computation is an expression consisting of constructors and base type values only.

    -
  • -
  • -

    Normal form is an expression consisting only of constructors and base type values; that which is normally the result of computing a function.

    -
  • -
  • -

    Type identifier is an identifier that normally starts with a capital letter in Roman script and uniquely identifies the type.

    -
  • -
  • -

    Type number or type name is a 32-bit number that uniquely identifies a type; it normally is the sum of the CRC32 values of the descriptions of the type constructors.

    -
  • -
  • -

    Description of (composite) Type T is a collection of the descriptions of all constructors that take on Type T values. This is normally written as text with each string containing the description of a single constructor. Here is a description of Type ‘IntTree’, for example:

    -

    int_tree IntTree int IntTree = IntTree; -empty_tree = IntTree;

    -
  • -
  • -

    Polymorphic type is a type whose description contains parameters (type variables) in lieu of actual types; approximately, what would be a template in C++. Here is a description of Type List alpha where List is a polymorphic type of arity 1 (i. e., dependent on a single argument), and alpha is a type variable which appears as the constructor’s optional parameter (in curly braces):

    -

    cons {alpha:Type} alpha (List alpha) = List alpha; -nil {alpha:Type} = List alpha;

    -
  • -
  • -

    Value of (composite) Type T is any sequence from A* in the format constr_num arg1 ... argN, where constr_num is the index number of some Constructor C which takes on values of Type T, and arg_i is a value of Type T_i which is the type of the i-th argument to Constructor C. For example, let Combinator int_tree have the index number 17, whereas Combinator empty_tree has the index number 239. Then, the value of Type IntTree is, for example, 17 17 239 1 239 2 239 which is more conveniently written as 'int_tree' 'int_tree' 'empty_tree' 1 'empty_tree' 2 ‘empty_tree’. From the standpoint of a high-level language, this is int_tree (int_tree (empty_tree) 1 (empty_tree)) 2 (empty_tree): IntTree.

    -
  • -
  • -

    Schema is a collection of all the (composite) data type descriptions. This is used to define some agreed-to system of types.

    -
  • -
-

Boxed and Bare Types

-
    -
  • Boxed type is a type any value of which starts with the constructor number. Since every constructor has a uniquely determined value type, the first number in any boxed type value uniquely defines its type. This guarantees that the various boxed types in totality make up a coordinated system of types. A boxed type identifier is always capitalized.
  • -
  • Bare type is a type whose values do not contain a constructor number, which is implied instead. A bare type identifier always coincides with the name of the implied constructor (and therefore, begins with a lowercase letter) which may be padded at the front by the percentage sign (%). In addition, if X is a boxed type with no more than a single constructor, then %X refers to the corresponding bare type. The values of a bare type are identical with the set of number sequences obtained by dropping the first number (i. e., the external constructor index number) from the set of values of the corresponding boxed type (which is the result type of the selected constructor), starting with the selected constructor index number. For example, 3 4 is a value of the int_couple bare type, defined using int_couple int int = IntCouple. The corresponding boxed type is IntCouple; if 404 is the constructor index number for int_couple, then 404 3 4 is the value for the IntCouple boxed type which corresponds to the value of the bare type int_couple (also known as %int_couple and %IntCouple; the latter form is conceptually preferable but longer).
  • -
-

Conceptually, only boxed types should be used everywhere. However, for speed and compactness, bare types have to be used (for instance, an array of 10,000 bare int values is 40,000 bytes long, whereas boxed Int values take up twice as much space; therefore, when transmitting a large array of integer identifiers, say, it is more efficient to use the Vector int type rather than Vector Int). In addition, all base types (int, long, double, string) are bare.

-

If a boxed type is polymorphic of type arity r, this is also true of any derived bare type. In other words, if one were to define intCouple {alpha:Type} int alpha = IntCouple alpha, then, thereafter, intCouple as an identifier would also be a polymorphic type of arity 1 in combinator (and consequently, in constructor and type) descriptions. The notations intCouple X, %(IntCouple X), and %IntCouple X are equivalent.

-

Base Types

-

Base types exist both as bare (int, long, double, string) and as boxed (Int, Long, Double, String) versions. Their constructor identifiers coincide with the names of the relevant bare types. Their pseudodescriptions have the following appearance:

-
int ? = Int;
-long ? = Long;
-double ? = Double;
-string ? = String;
-

Consequently, the int constructor index number, for example, is the CRC32 of the string "int ? = Int".

-

The values of bare type int are exactly all the single-element sequences, i. e. numbers between -2^31 and 2^31-1 represent themselves in this case. Values of type long are two-element sequences that are 64-bit signed numbers (little endian again). Values of type double, again, are two-element sequences containing 64-bit real numbers in a standard double format. And finally, the values of type string look differently depending on the length L of the string being serialized:

-
    -
  • If L <= 253, the serialization contains one byte with the value of L, then L bytes of the string followed by 0 to 3 characters containing 0, such that the overall length of the value be divisible by 4, whereupon all of this is interpreted as a sequence of int(L/4)+1 32-bit numbers.
  • -
  • If L >= 254, the serialization contains byte 254, followed by 3 bytes with the string length L, followed by L bytes of the string, further followed by 0 to 3 null padding bytes.
  • -
-

Object Pseudotype

-

The Object pseudotype is a “type” which can take on values that belong to any boxed type in the schema. This helps quickly define such types as list of random items without using polymorphic types. It is best not to abuse this capability since it results in the use of dynamic typing. Nonetheless, it is hard to imagine the data structures that we know from PHP and JSON without using the Object pseudotype.

-

It is recommended to use TypedObject instead whenever possible:

-
object X:Type value:X = TypedObject;
-

Built-In Composite Types: Vectors and Associative Arrays

-

The Vector t polymorphic pseudotype is a “type” whose value is a sequence of values of any type t, either boxed or bare.

-
vector {t:Type} # [ t ] = Vector t;
-

Serialization always uses the same constructor “vector” (const 0x1cb5c415 = crc32("vector t:Type # [ t ] = Vector t”) that is not dependent on the specific value of the variable of type t. The value of the Vector t type is the index number of the relevant constructor number followed by N, the number of elements in the vector, and then by N values of type t. The value of the optional parameter t is not involved in the serialization since it is derived from the result type (always known prior to deserialization).

-

Polymorphic pseudotypes IntHash t and StrHash t are associative arrays mapping integer and string keys to values of type t. They are, in fact, vectors containing bare 2-tuples (int, t) or (string, t):

-
coupleInt {t:Type} int t = CoupleInt t;
-intHash {t:Type} (vector %(CoupleInt t)) = IntHash t;
-coupleStr {t:Type} string t = CoupleStr t;
-strHash {t:Type} (vector %(CoupleStr t)) = StrHash t;
-

The percentage sign, in this case, means that a bare type that corresponds to the boxed type in parentheses is taken; the boxed type in question must have no more than a single constructor, whatever the values of the parameters.

-

The keys may be sorted or be in some other order (as in PHP arrays). For associative arrays with sorted keys, the IntSortedHash or StrSortedHash alias is used:

-
intSortedHash {t:Type} (intHash t) = IntSortedHash t;
-strSortedHash {t:Type} (strHash t) = StrSortedHash t;
-

Polymorphic Type Constructors

-

The constructor of a polymorphic type does not depend on the specific types to which the polymorphic type is applied. When it is computed, optional parameters (normally containing type variables and placed in curly braces) cease to be optional (the curly braces are removed), and, in addition to that, all parenthesis are also removed. Therefore,

-
vector {t:Type} # [ t ] = Vector t;
-

corresponds to the constructor number crc32("vector t:Type # [ t ] = Vector t") = 0x1cb5c415. During (de)serialization, the specific values of the optional variable t are derived from the result type (i. e. the object being serialized or deserialized) that is always known, and are never serialized explicitly.

-

Previously, it had to be known which specific variable types each polymorphic type will apply to. To accomplish this, the type system used strings of the form

-
polymorphic_type_name type_1 ... type_N;
-

For example,

-
Vector int;
-Vector string;
-Vector Object;
-

Now they are ignored.

-

See also polymorphism in TL.

-

In this case, the Object pseudotype permits using Vector Object to store lists of anything (the values of any boxed types). Since bare types are efficient when short, in practice it is unlikely that cases more complex than the ones cited above will be required.

-

Field Names

-

Let us say that we need to represent users as triplets containing one integer (user ID) and two strings (first and last names). The requisite data structure is the triplet int, string, string which may be declared as follows:

-
user int string string = User;
-

On the other hand, a group may be described by a similar triplet consisting of a group ID, its name, and description:

-
group int string string = Group;
-

For the difference between User and Group to be clear, it is convenient to assign names to some or all of the fields:

-
user id:int first_name:string last_name:string = User;
-group id:int title:string description:string = Group;
-

If the User type needs to be extended at a later time by having records with some additional field added to it, it could be accomplished as follows:

-
userv2 id:int unread_messages:int first_name:string last_name:string in_groups:vector int = User;
-

Aside from other things, this approach helps define correct mappings between fields that belong to different constructors of the same type, convert between them as well as convert type values into an associative array with string keys (field names, if defined, are natural choices for such keys).

-

TL Language

-

See TL Language

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/mtproto/service_messages.html b/data/corefork.telegram.org/mtproto/service_messages.html deleted file mode 100644 index 7ef9827419..0000000000 --- a/data/corefork.telegram.org/mtproto/service_messages.html +++ /dev/null @@ -1,195 +0,0 @@ - - - - - Service Messages - - - - - - - - - - - - - -
- -
-
-
- -

Service Messages

- -

Response to an RPC query

-

A response to an RPC query is normally wrapped as follows:

-
rpc_result#f35c6d01 req_msg_id:long result:Object = RpcResult;
-

Here req_msg_id is the identifier of the message sent by the other party and containing an RPC query. This way, the recipient knows that the result is a response to the specific RPC query in question. -At the same time, this response serves as acknowledgment of the other party’s receipt of the req_msg_id message.

-

Note that the response to an RPC query must also be acknowledged. Most frequently, this coincides with the transmission of the next message (which may have a container attached to it carrying a service message with the acknowledgment).

-

RPC Error

-

The result field returned in response to any RPC query may also contain an error message in the following format:

-
rpc_error#2144ca19 error_code:int error_message:string = RpcError;
-

Cancellation of an RPC Query

-

In certain situations, the client does not want to receive a response to an already transmitted RPC query, for example because the response turns out to be long and the client has decided to do without it because of insufficient link capacity. Simply interrupting the TCP connection will not have any effect because the server would re-send the missing response at the first opportunity. Therefore, the client needs a way to cancel receipt of the RPC response message, actually acknowledging its receipt prior to it being in fact received, which will settle the server down and prevent it from re-sending the response. However, the client does not know the RPC response’s msg_id prior to receiving the response; the only thing it knows is the req_msg_id. i. e. the msg_id of the relevant RPC query. Therefore, a special query is used:

-
rpc_drop_answer#58e4a740 req_msg_id:long = RpcDropAnswer;
-

The response to this query returns as one of the following messages wrapped in rpc_result and requiring an acknowledgment:

-
rpc_answer_unknown#5e2ad36e = RpcDropAnswer;
-rpc_answer_dropped_running#cd78e586 = RpcDropAnswer;
-rpc_answer_dropped#a43ad8b7 msg_id:long seq_no:int bytes:int = RpcDropAnswer;
-

The first version of the response is used if the server remembers nothing of the incoming req_msg_id (if it has already been responded to, for example). The second version is used if the response was canceled while the RPC query was being processed (where the RPC query itself was still fully processed); in this case, the same rpc_answer_dropped_running is also returned in response to the original query, and both of these responses require an acknowledgment from the client. The final version means that the RPC response was removed from the server’s outgoing queue, and its msg_id, seq_no, and length in bytes are transmitted to the client.

-

Note that rpc_answer_dropped_running and rpc_answer_dropped serve as acknowledgments of the server’s receipt of the original query (the same one, the response to which we wish to forget). In addition, same as for any RPC queries, any response to rpc_drop_answer is an acknowledgment for rpc_drop_answer itself.

-

As an alternative to using rpc_drop_answer, a new session may be created after the connection is reset and the old session is removed through destroy_session.

-

Messages associated with querying, changing, and receiving the status of other messages

-

See Mobile Protocol: Service Messages about Messages

-

Request for several future salts

-

The client may at any time request from the server several (between 1 and 64) future server salts together with their validity periods. Having stored them in persistent memory, the client may use them to send messages in the future even if it changes sessions (a server salt is attached to the authorization key rather than being session-specific).

-
get_future_salts#b921bd04 num:int = FutureSalts;
-future_salt#0949d9dc valid_since:int valid_until:int salt:long = FutureSalt;
-future_salts#ae500895 req_msg_id:long now:int salts:vector<future_salt> = FutureSalts;
-

The client must check to see that the response’s req_msg_id in fact coincides with msg_id of the query for get_future_salts. The server returns a maximum of num future server salts (may return fewer). The response serves as the acknowledgment of the query and does not require an acknowledgment itself.

-

Ping Messages (PING/PONG)

-
ping#7abe77ec ping_id:long = Pong;
-

A response is usually returned to the same connection:

-
pong#347773c5 msg_id:long ping_id:long = Pong;
-

These messages do not require acknowledgments. A pong is transmitted only in response to a ping while a ping can be initiated by either side.

-

Deferred Connection Closure + PING

-
ping_delay_disconnect#f3427b8c ping_id:long disconnect_delay:int = Pong;
-

Works like ping. In addition, after this is received, the server starts a timer which will close the current connection disconnect_delay seconds later unless it receives a new message of the same type which automatically resets all previous timers. If the client sends these pings once every 60 seconds, for example, it may set disconnect_delay equal to 75 seconds.

-

Request to Destroy Session

-

Used by the client to notify the server that it may forget the data from a different session belonging to the same user (i. e. with the same auth_key_id). The result of this being applied to the current session is undefined.

-
destroy_session#e7512126 session_id:long = DestroySessionRes;
-destroy_session_ok#e22045fc session_id:long = DestroySessionRes;
-destroy_session_none#62d350c9 session_id:long = DestroySessionRes;
-

New Session Creation Notification

-

The server notifies the client that a new session (from the server’s standpoint) had to be created to handle a client message. If, after this, the server receives a message with an even smaller msg_id within the same session, a similar notification will be generated for this msg_id as well. No such notifications are generated for high msg_id values.

-
new_session_created#9ec20908 first_msg_id:long unique_id:long server_salt:long = NewSession
-

The unique_id parameter is generated by the server every time a session is (re-)created.

-

This notification must be acknowledged by the client. It is necessary, for instance, for the client to understand that there is, in fact, a “gap” in the stream of long poll notifications received from the server (the user may have failed to receive notifications during some period of time).

-

Notice that the server may unilaterally destroy (close) any existing client sessions with all pending messages and notifications, without sending any notifications. This happens, for example, if the session is inactive for a long time, and the server runs out of memory. If the client at some point decides to send new messages to the server using the old session, already forgotten by the server, such a "new session created" notification will be generated. The client is expected to handle such situations gracefully.

-

Containers

-

Containers are messages containing several other messages. Used for the ability to transmit several RPC queries and/or service messages at the same time, using HTTP or even TCP or UDP protocol. A container may only be accepted or rejected by the other party as a whole.

-

Simple Container

-

A simple container carries several messages as follows:

-
msg_container#73f1f8dc messages:vector message = MessageContainer;
-

Here message refers to any message together with its length and msg_id:

-
message msg_id:long seqno:int bytes:int body:Object = Message;
-

bytes is the number of bytes in the body serialization. -All messages in a container must have msg_id lower than that of the container itself. A container does not require an acknowledgment and may not carry other simple containers. When messages are re-sent, they may be combined into a container in a different manner or sent individually.

-

MTProto container payloads have a limit of 2^15 bytes or 1020 messages, whichever limit is reached first.
-Clients should group acknowledgments, state requests and message resend requests into three separate msgs_ack, msgs_state_req, msg_resend_req service messages with at most 8192 IDs each; these three messages (+http_wait) will not be included in the 1020 message limit.

-

Empty containers are also allowed. They are used by the server, for example, to respond to an HTTP request when the timeout specified in http_wait expires, and there are no messages to transmit.

-

Example implementation.

-

Message Copies

-

In some situations, an old message with a msg_id that is no longer valid needs to be re-sent. Then, it is wrapped in a copy container:

-
msg_copy#e06046b2 orig_message:Message = MessageCopy;
-

Once received, the message is processed as if the wrapper were not there. However, if it is known for certain that the message orig_message.msg_id was received, then the new message is not processed (while at the same time, it and orig_message.msg_id are acknowledged). The value of orig_message.msg_id must be lower than the container’s msg_id.

-

This is not used at this time, because an old message can be wrapped in a simple container with the same result.

-

Packed Object

-

Used to replace any other object (or rather, a serialization thereof) with its archived (gzipped) representation:

-
gzip_packed#3072cfa1 packed_data:string = Object;
-

At the present time, it is supported in the body of an RPC response (i.e., as result in rpc_result) and generated by the server for a limited number of high-level queries. In addition, it may be used to transmit non-service messages (i. e. RPC queries) from client to server.

-

HTTP Wait/Long Poll

-

The following special service query not requiring an acknowledgement (which must be transmitted only through an HTTP connection) is used to enable the server to send messages in the future to the client using HTTP protocol:

-
http_wait#9299359f max_delay:int wait_after:int max_wait:int = HttpWait;
-

When such a message (or a container carrying such a message) is received, the server either waits max_delay milliseconds, whereupon it forwards all the messages that it is holding on to the client if there is at least one message queued in session (if needed, by placing them into a container to which acknowledgments may also be added); or else waits no more than max_wait milliseconds until such a message is available. If a message never appears, an empty container is transmitted.

-

The max_delay parameter denotes the maximum number of milliseconds that has elapsed between the first message for this session and the transmission of an HTTP response. The wait_after parameter works as follows: after the receipt of the latest message for a particular session, the server waits another wait_after milliseconds in case there are more messages. If there are no additional messages, the result is transmitted (a container with all the messages). If more messages appear, the wait_after timer is reset.

-

At the same time, the max_delay parameter has higher priority than wait_after, and max_wait has higher priority than max_delay.

-

This message does not require a response or an acknowledgement. If the container transmitted over HTTP carries several such messages, the behavior is undefined (in fact, the latest parameter will be used).

-

If no http_wait is present in container, default values max_delay=0 (milliseconds), wait_after=0 (milliseconds), and max_wait=25000 (milliseconds) are used.

-

If the client’s ping of the server takes a long time, it may make sense to set max_delay to a value that is comparable in magnitude to ping time.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/mtproto/service_messages_about_messages.html b/data/corefork.telegram.org/mtproto/service_messages_about_messages.html deleted file mode 100644 index d271a6e13d..0000000000 --- a/data/corefork.telegram.org/mtproto/service_messages_about_messages.html +++ /dev/null @@ -1,185 +0,0 @@ - - - - - Service Messages about Messages - - - - - - - - - - - - - -
- -
-
-
- -

Service Messages about Messages

- -

Acknowledgment of Receipt

-

Receipt of virtually all messages (with the exception of some purely service ones as well as the plain-text messages used in the protocol for creating an authorization key) must be acknowledged. -This requires the use of the following service message (not requiring an acknowledgment):

-
msgs_ack#62d6b459 msg_ids:Vector<long> = MsgsAck;
-

A server usually acknowledges the receipt of a message from a client (normally, an RPC query) using an RPC response. If a response is a long time coming, a server may first send a receipt acknowledgment, and somewhat later, the RPC response itself.

-

A client normally acknowledges the receipt of a message from a server (usually, an RPC response) by adding an acknowledgment to the next RPC query if it is not transmitted too late (if it is generated, say, 60-120 seconds following the receipt of a message from the server). However, if for a long period of time there is no reason to send messages to the server or if there is a large number of unacknowledged messages from the server (say, over 16), the client transmits a stand-alone acknowledgment.

-

Max 8192 IDs are allowed per constructor.

-

Notice of Ignored Error Message

-

In certain cases, a server may notify a client that its incoming message was ignored for whatever reason. Note that such a notification cannot be generated unless a message is correctly decoded by the server.

-
bad_msg_notification#a7eff811 bad_msg_id:long bad_msg_seqno:int error_code:int = BadMsgNotification;
-bad_server_salt#edab447b bad_msg_id:long bad_msg_seqno:int error_code:int new_server_salt:long = BadMsgNotification;
-

Here, error_code can also take on the following values:

-
    -
  • 16: msg_id too low (most likely, client time is wrong; it would be worthwhile to synchronize it using msg_id notifications and re-send the original message with the “correct” msg_id or wrap it in a container with a new msg_id if the original message had waited too long on the client to be transmitted)
  • -
  • 17: msg_id too high (similar to the previous case, the client time has to be synchronized, and the message re-sent with the correct msg_id)
  • -
  • 18: incorrect two lower order msg_id bits (the server expects client message msg_id to be divisible by 4)
  • -
  • 19: container msg_id is the same as msg_id of a previously received message (this must never happen)
  • -
  • 20: message too old, and it cannot be verified whether the server has received a message with this msg_id or not
  • -
  • 32: msg_seqno too low (the server has already received a message with a lower msg_id but with either a higher or an equal and odd seqno)
  • -
  • 33: msg_seqno too high (similarly, there is a message with a higher msg_id but with either a lower or an equal and odd seqno)
  • -
  • 34: an even msg_seqno expected (irrelevant message), but odd received
  • -
  • 35: odd msg_seqno expected (relevant message), but even received
  • -
  • 48: incorrect server salt (in this case, the bad_server_salt response is received with the correct salt, and the message is to be re-sent with it)
  • -
  • 64: invalid container.
  • -
-

The intention is that error_code values are grouped (error_code >> 4): for example, the codes 0x40 - 0x4f correspond to errors in container decomposition.

-

Notifications of an ignored message do not require acknowledgment (i.e., are irrelevant).

-

Important: if server_salt has changed on the server or if client time is incorrect, any query will result in a notification in the above format. The client must check that it has, in fact, recently sent a message with the specified msg_id, and if that is the case, update its time correction value (the difference between the client’s and the server’s clocks) and the server salt based on msg_id and the server_salt notification, so as to use these to (re)send future messages. In the meantime, the original message (the one that caused the error message to be returned) must also be re-sent with a better msg_id and/or server_salt.

-

In addition, the client can update the server_salt value used to send messages to the server, based on the values of RPC responses or containers carrying an RPC response, provided that this RPC response is actually a match for the query sent recently. (If there is doubt, it is best not to update since there is risk of a replay attack).

-

Request for Message Status Information

-

If either party has not received information on the status of its outgoing messages for a while, it may explicitly request it from the other party:

-
msgs_state_req#da69fb52 msg_ids:Vector long = MsgsStateReq;
-

Max 8192 IDs are allowed per constructor.

-

The response to the query contains the following information:

-

Informational Message regarding Status of Messages

-
msgs_state_info#04deb57d req_msg_id:long info:string = MsgsStateInfo;
-

Here, info is a string that contains exactly one byte of message status for each message from the incoming msg_ids list:

-
    -
  • 1 = nothing is known about the message (msg_id too low, the other party may have forgotten it)
  • -
  • 2 = message not received (msg_id falls within the range of stored identifiers; however, the other party has certainly not received a message like that)
  • -
  • 3 = message not received (msg_id too high; however, the other party has certainly not received it yet)
  • -
  • 4 = message received (note that this response is also at the same time a receipt acknowledgment)
  • -
  • +8 = message already acknowledged
  • -
  • +16 = message not requiring acknowledgment
  • -
  • +32 = RPC query contained in message being processed or processing already complete
  • -
  • +64 = content-related response to message already generated
  • -
  • +128 = other party knows for a fact that message is already received
  • -
-

This response does not require an acknowledgment. It is an acknowledgment of the relevant msgs_state_req, in and of itself.

-

Note that if it turns out suddenly that the other party is missing a message that appears to have been sent to it, the message must not be re-sent on its own with the same msg_id. Instead, it can be either wrapped in a container, or the status of the message can be checked using msgs_state_req and if the message wasn't received, then it must be re-sent with a new msg_id.

-

Voluntary Communication of Status of Messages

-

Either party may voluntarily inform the other party of the status of the messages transmitted by the other party.

-
msgs_all_info#8cc0d131 msg_ids:Vector long info:string = MsgsAllInfo
-

All message codes known to this party are enumerated, with the exception of those for which the +128 and the +16 flags are set. However, if the +32 flag is set but not +64, then the message status will still be communicated.

-

This message does not require an acknowledgment.

-

Extended Voluntary Communication of Status of One Message

-

Normally used by the server to respond to the receipt of a duplicate msg_id, especially if a response to the message has already been generated and the response is large. If the response is small, the server may re-send the answer itself instead. This message can also be used as a notification instead of resending a large message.

-
msg_detailed_info#276d3ec6 msg_id:long answer_msg_id:long bytes:int status:int = MsgDetailedInfo;
-msg_new_detailed_info#809db6df answer_msg_id:long bytes:int status:int = MsgDetailedInfo;
-

The second version is used to notify of messages that were created on the server not in response to an RPC query (such as notifications of new messages) and were transmitted to the client some time ago, but not acknowledged.

-

Currently, status is always zero. This may change in future.

-

This message does not require an acknowledgment.

-

Explicit Request to Re-Send Messages

-
msg_resend_req#7d861a08 msg_ids:Vector long = MsgResendReq;
-

The remote party immediately responds by re-sending the requested messages, normally using the same connection that was used to transmit the query. If at least one message with requested msg_id does not exist or has already been forgotten, or has been sent by the requesting party (known from parity), MsgsStateInfo is returned for all messages requested as if the MsgResendReq query had been a MsgsStateReq query as well.
-Max 8192 IDs are allowed per constructor.

-

Explicit Request to Re-Send Answers

-
msg_resend_ans_req#8610baeb msg_ids:Vector long = MsgResendReq;
-

The remote party immediately responds by re-sending answers to the requested messages, normally using the same connection that was used to transmit the query. MsgsStateInfo is returned for all messages requested as if the MsgResendReq query had been a MsgsStateReq query as well.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/mtproto_v1.html b/data/corefork.telegram.org/mtproto_v1.html deleted file mode 100644 index d35544a3e8..0000000000 --- a/data/corefork.telegram.org/mtproto_v1.html +++ /dev/null @@ -1,229 +0,0 @@ - - - - - MTProto Mobile Protocol v.1.0 (DEPRECATED) - - - - - - - - - - - - - -
- -
-
-
-
-

MTProto Mobile Protocol v.1.0 (DEPRECATED)

- -
-

This document describes MTProto v1.0, its status is DEPRECATED.
For information on encryption used in up-to-date Telegram clients, kindly see this document.

-
-

Related articles

-

-
-

This page deals with the basic layer of MTProto encryption used for Cloud chats (server-client encryption). See also:

- -

General Description

-

The protocol is designed for access to a server API from applications running on mobile devices. It must be emphasized that a web browser is not such an application.

-

The protocol is subdivided into three virtually independent components:

-
    -
  • High-level component (API query language): defines the method whereby API queries and responses are converted to binary messages.
  • -
  • Cryptographic (authorization) layer: defines the method by which messages are encrypted prior to being transmitted through the transport protocol.
  • -
  • Transport component: defines the method for the client and the server to transmit messages over some other existing network protocol (such as, http, https, tcp, udp).
  • -
- - -
-

Got questions about this setup? — Check out the Advanced FAQ!

-
-
Note 1
-

Each plaintext message to be encrypted in MTProto always contains the following data to be checked upon decryption in order to make the system robust against known problems with the components:

-
    -
  • server salt (64-Bit)
  • -
  • session id
  • -
  • message sequence number
  • -
  • message length
  • -
  • time
  • -
-
Note 2
-

See additional comments on our use of IGE, SHA-1 and message authentication.

-
Note 3
-

Telegram's End-to-end encrypted Secret Chats are using an additional layer of encryption on top of the described above. See Secret Chats, End-to-End encryption for details.

-

Brief Component Summary

-

High-Level Component (RPC Query Language/API)

-

From the standpoint of the high-level component, the client and the server exchange messages inside a session. The session is attached to the client device (the application, to be more exact) rather than a specific http/https/tcp connection. In addition, each session is attached to a user key ID by which authorization is actually accomplished.

-

Several connections to a server may be open; messages may be sent in either direction through any of the connections (a response to a query is not necessarily returned through the same connection that carried the original query, although most often, that is the case; however, in no case can a message be returned through a connection belonging to a different session). When the UDP protocol is used, a response might be returned by a different IP address than the one to which the query had been sent.

-

There are several types of messages:

-
    -
  • RPC calls (client to server): calls to API methods
  • -
  • RPC responses (server to client): results of RPC calls
  • -
  • Message received acknowledgment (or rather, notification of status of a set of messages)
  • -
  • Message status query
  • -
  • Multipart message or container (a container that holds several messages; needed to send several RPC calls at once over an HTTP connection, for example; also, a container may support gzip).
  • -
-

From the standpoint of lower level protocols, a message is a binary data stream aligned along a 4 or 16-byte boundary. The first several fields in the message are fixed and are used by the cryptographic/authorization system.

-

Each message, either individual or inside a container, consists of a message identifier (64 bits, see below), a message sequence number within a session (32 bits), the length (of the message body in bytes; 32 bits), and a body (any size which is a multiple of 4 bytes). In addition, when a container or a single message is sent, an internal header is added at the top (see below), then the entire message is encrypted, and an external header is placed at the top of the message (a 64-bit key identifier and a 128-bit message key).

-

A message body normally consists of a 32-bit message type followed by type-dependent parameters. In particular, each RPC function has a corresponding message type. For more detail, see Binary Data Serialization, Mobile Protocol: Service Messages.

-

All numbers are written as little endian. However, very large numbers (2048-bit) used in RSA and DH are written in the big endian format because that is what the OpenSSL library does.

-

Authorization and Encryption

-

Prior to a message (or a multipart message) being transmitted over a network using a transport protocol, it is encrypted in a certain way, and an external header is added at the top of the message which is: a 64-bit key identifier (that uniquely identifies an authorization key for the server as well as the user) and a 128-bit message key. A user key together with the message key defines an actual 256-bit key which is what encrypts the message using AES-256 encryption. Note that the initial part of the message to be encrypted contains variable data (session, message ID, sequence number, server salt) that obviously influences the message key (and thus the AES key and iv). The message key is defined as the 128 lower-order bits of the SHA1 of the message body (including session, message ID, etc.). Multipart messages are encrypted as a single message.

-

For a technical specification, see Mobile Protocol: Detailed Description
The first thing a client application must do is create an authorization key which is normally generated when it is first run and almost never changes.

-

The protocol’s principal drawback is that an intruder passively intercepting messages and then somehow appropriating the authorization key (for example, by stealing a device) will be able to decrypt all the intercepted messages post factum. This probably is not too much of a problem (by stealing a device, one could also gain access to all the information cached on the device without decrypting anything); however, the following steps could be taken to overcome this weakness:

-
    -
  • Session keys generated using the Diffie-Hellman protocol and used in conjunction with the authorization and the message keys to select AES parameters. To create these, the first thing a client must do after creating a new session is send a special RPC query to the server (“generate session key”) to which the server will respond, whereupon all subsequent messages within the session are encrypted using the session key as well.
  • -
  • Protecting the key stored on the client device with a (text) password; this password is never stored in memory and is entered by a user when starting the application or more frequently (depending on application settings).
  • -
  • Data stored (cached) on the user device can also be protected by encryption using an authorization key which, in turn, is to be password-protected. Then, a password will be required to gain access even to those data.
  • -
-

Time Synchronization

-

If client time diverges widely from server time, a server may start ignoring client messages, or vice versa, because of an invalid message identifier (which is closely related to creation time). Under these circumstances, the server will send the client a special message containing the correct time and a certain 128-bit salt (either explicitly provided by the client in a special RPC synchronization request or equal to the key of the latest message received from the client during the current session). This message could be the first one in a container that includes other messages (if the time discrepancy is significant but does not as yet result in the client’s messages being ignored).

-

Having received such a message or a container holding it, the client first performs a time synchronization (in effect, simply storing the difference between the server’s time and its own to be able to compute the “correct” time in the future) and then verifies that the message identifiers for correctness.

-

Where a correction has been neglected, the client will have to generate a new session to assure the monotonicity of message identifiers.

-

Transport

-

Enables the delivery of encrypted containers together with the external header (hereinafter, Payload) from client to server and back. There are three types of transport:

-
    -
  • HTTP
  • -
  • TCP
  • -
  • UDP
  • -
-

We shall examine the first two types.

-

HTTP Transport

-

Implemented over HTTP/1.1 (with keepalive) running over the traditional TCP Port 80. HTTPS is not used; the above encryption method is used instead.

-

An HTTP connection is attached to a session (or rather, to session + key identifier) specified in the most recent user query received; normally, the session is the same in all queries, but crafty HTTP proxies may corrupt that. A server may not return a message into an HTTP connection unless it belongs to the same session, and unless it is the server’s turn (an HTTP request had been received from the client to which a response has not been sent yet).

-

The overall arrangement is as follows. The client opens one or more keepalive HTTP connections to the server. If one or more messages need to be sent, they are made into a payload which is followed by a POST request to the URL/api to which the payload is transmitted as data. In addition, Content-Length, Keepalive, and Host are valid HTTP headers.

-

Having received the query, the server may either wait a little while (if the query requires a response following a short timeout) or immediately return a dummy response (only acknowledging the receipt of the container). In any case, the response may contain any number of messages. The server may at the same time send out any other messages it might be holding for the session.

-

In addition, there exists a special long poll RPC query (valid for HTTP connections only) which transmits maximum timeout T. If the server has messages for the session, they are returned immediately; otherwise, a wait state is entered until such time as the server has a message for the client or T seconds have elapsed. If no events occur in the span of T seconds, a dummy response is returned (special message).

-

If a server needs to send a message to a client, it checks for an HTTP connection that belongs to the required session and is in the “answering an HTTP request” state (including long poll) whereupon the message is added to the response container for the connection and sent to the user. In a typical case, there is some additional wait time (50 milliseconds) against the eventuality that the server will soon have more messages for the session.

-

If no suitable HTTP connection is available, the messages are placed in the current session’s send queue. However, they find their way there anyway until receipt is explicitly or indirectly confirmed by the client. For the HTTP protocol, sending the next query into the same HTTP connection is regarded as an implicit acknowledgment (not any more, the HTTP protocol also requires that explicit acknowledgments be sent); in other cases, the client must return an explicit acknowledgment within a reasonable time (it can be added to a container for the following request).

-

Important: if the acknowledgment fails to arrive on time, the message can be resent (possibly, in a different container). The parties must autonomously be ready for this and must store the identifiers of the most recent messages received (and ignore such duplicates rather than repeat actions). In order not to have the identifiers stored forever, there exist special garbage collection messages that take advantage of message identifier monotonicity.

-

If the send queue overflows or if messages stay in the queue for over 10 minutes, the server forgets them (or sends them to swap, no genius required). This may happen even faster, if the server is running out of buffer space (for example, because of serious network issues resulting in a large number of connections becoming severed).

-

TCP Transport

-

This is very similar to the HTTP transport. May also be implemented over Port 80 (to penetrate all firewalls) and even use the same server IP addresses. In this situation, the server understands whether HTTP or TCP protocol must be used for the connection, based on the first four incoming bytes (for HTTP, it is POST).

-

When a TCP connection is created, it is assigned to the session (and the authorization key) transmitted in the first user message, and subsequently used exclusively for this session (multiplexing arrangements are not allowed).

-

If a payload (packet) needs to be transmitted from server to client or from client to server, it is encapsulated as follows: 4 length bytes are added at the front (to include the length, the sequence number, and CRC32; always divisible by 4) and 4 bytes with the packet sequence number within this TCP connection (the first packet sent is numbered 0, the next one 1, etc.), and 4 CRC32 bytes at the end (length, sequence number, and payload together).

-

There is an abridged version of the same protocol: if the client sends 0xef as the first byte (important: only prior to the very first data packet), then packet length is encoded by a single byte (0x01..0x7e = data length divided by 4; or 0x7f followed by 3 length bytes (little endian) divided by 4) followed by the data themselves (sequence number and CRC32 not added). In this case, server responses look the same (the server does not send 0xefas the first byte).

-

In case 4-byte data alignment is needed, an intermediate version of the original protocol may be used: if the client sends 0xeeeeeeee as the first int (four bytes), then packet length is encoded always by four bytes as in the original version, but the sequence number and CRC32 are omitted, thus decreasing total packet size by 8 bytes.

-

The full, the intermediate and the abridged versions of the protocol have support for quick acknowledgment. In this case, the client sets the highest-order length bit in the query packet, and the server responds with a special 4 bytes as a separate packet. They are the 32 higher-order SHA1 bits of the encrypted portion of the packet with the most significant bit set to make clear that this is not the length of a regular server response packet; if the abridged version is used, bswap is applied to these four bytes.

-

There are no implicit acknowledgments for the TCP transport: all messages must be acknowledged explicitly. Most frequently, acknowledgments are placed in a container with the next query or response if it is transmitted in short order. For example, this is almost always the case for client messages containing RPC queries: the acknowledgment normally arrives with the RPC response.

-

In the event of an error, the server may send a packet whose payload consists of 4 bytes as the error code. For example, Error Code 403 corresponds to situations where the corresponding HTTP error would have been returned by the HTTP protocol.

-
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/passport.html b/data/corefork.telegram.org/passport.html deleted file mode 100644 index ffcc341cc7..0000000000 --- a/data/corefork.telegram.org/passport.html +++ /dev/null @@ -1,690 +0,0 @@ - - - - - Telegram Passport Manual - - - - - - - - - - - - - -
- -
-
-
-
-

Telegram Passport Manual

- -
- -

Telegram Passport is a unified authorization method for services that require personal identification. Users can upload their documents once, then instantly share their data with services that require real-world ID (finance, ICOs, etc.). Telegram doesn't have access to the users' personal information thanks to end-to-end encryption.

-

Overview

-

From the perspective of a service that requires real-world ID, the process looks like this:

-
    -
  • A user presses "Log in with Telegram" on your website or in your app.
  • -
  • You request the data you need.
  • -
  • The user accepts your privacy policy and agrees to share their data.
  • -
  • The user's Telegram app downloads and decrypts the data you requested from the end-to-end encrypted storage on Telegram.
  • -
  • If some of the data you requested is missing, the user can add it to their Telegram Passport at this point.
  • -
  • The user's app encrypts the data with your public key and sends it to you.
  • -
  • You decrypt the data, check it for errors and re-request any missing or invalid information.
  • -
  • You sign the user up for your service. Tada!
  • -
-

Check out this example to see Telegram Passport in action.

-
-

To learn more about Telegram Passport from the perspective of a user, please see this blog post and the technical MTProto documentation. -See this page if you're interested in encryption algorithms used on Telegram's side.

-
-

Recent changes

-

August 25, 2018

-

Telegram Passport 1.1 (blog post)

-
    -
  • Added support for requesting several documents of one type. See the new objects PassportScope, PassportScopeElement, PassportScopeElementOneOfSeveral and PassportScopeElementOne.
  • -
  • Added support for middle names.
  • -
  • Added support for requesting certified English translations for documents (see Fields; new field translation also added to the SecureValue object). Note: Please only request translations after you have received a valid document that requires one.
  • -
  • Added support for requesting names in the language of the user's country of residence (if other than English). New fields first_name_native, last_name_native and middle_name_native added to the PersonalDetails object.
  • -
  • Replaced the payload parameter with the new parameter nonce, which serves the same function, to make the purpose more obvious (see Request Parameters and the Credentials object).
  • -
  • Updated the example page to support the new functionality.
  • -
-

Setting Up Telegram Passport

-

To integrate Telegram Passport into your login or verification flow, you need a working Telegram bot (see this page for information on how to get one).

-

To request data from Telegram Passport users, your bot will need to generate a pair of encryption keys.

-

Generating a private key

-

First, use a console to generate a private key:

-
openssl genrsa 2048 > private.key
-

WARNING: Keep your private key SECRET!

-

Generating your public key

-

Then use the console to print the corresponding public key:

-
openssl rsa -in private.key -pubout
-

Use the /setpublickey command with @BotFather to connect this public key with your bot.

-

Privacy Policy

-

Add a link to your Privacy Policy by using the /setprivacypolicy command. Users will see this link when offered to authorize you to access their data.

-

Requesting Information

-

SDK

-

To request information stored in a Telegram Passport, use one of these SDKs:

- -

Request Parameters

-

Use the following parameters to request information with the SDK:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ParametersTypeRequired
bot_idIntegerYes
scopePassportScopeYes
public_keyStringYes
nonceStringYes
-

PassportScope

-

This object represents the data to be requested.

- - - - - - - - - - - - - - - - - - -
FieldTypeDescription
dataArray of PassportScopeElementList of requested elements, each type may be used only once in the entire array of PassportScopeElement objects
vIntegerScope version, must be 1
-

PassportScopeElement

-

This object represents a requested element, should be one of:

- -

PassportScopeElementOneOfSeveral

-

This object represents several elements one of which must be provided.

- - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
one_ofArray of PassportScopeElementOneList of elements one of which must be provided; must contain either several of “passport”, “driver_license”, “identity_card”, “internal_passport” or several of “utility_bill”, “bank_statement”, “rental_agreement”, “passport_registration”, “temporary_registration”
selfieBooleanOptional. Use this parameter if you want to request a selfie with the document from this list that the user chooses to upload.
translationBooleanOptional. Use this parameter if you want to request a translation of the document from this list that the user chooses to upload. Note: We suggest to only request translations after you have received a valid document that requires one.
-

PassportScopeElementOne

-

This object represents one particular element that must be provided. If no options are needed, String can be used instead of this object to specify the type of the element.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
typeStringElement type. One of "personal_details", "passport", "driver_license", "identity_card", "internal_passport", "address", "utility_bill", "bank_statement", "rental_agreement", "passport_registration", "temporary_registration", "phone_number", "email"
selfieBooleanOptional. Use this parameter if you want to request a selfie with the document as well. Available for "passport", "driver_license", "identity_card" and "internal_passport"
translationBooleanOptional. Use this parameter if you want to request a translation of the document as well. Available for "passport", "driver_license", "identity_card", "internal_passport", "utility_bill", "bank_statement", "rental_agreement", "passport_registration" and "temporary_registration". Note: We suggest to only request translations after you have received a valid document that requires one.
native_namesBooleanOptional. Use this parameter to request the first, last and middle name of the user in the language of the user's country of residence. Available for "personal_details"
-

You can also use the special type "id_document" as an alias for one of "passport", "driver_license", "identity_card" and the special type "address_document" as an alias for one of "utility_bill", "bank_statement", "rental_agreement". -So {"type":"id_document",selfie:true} is equal to {"one_of":["passport","driver_license","identity_card"],selfie:true}.

-

Fields

-

Your bot can request personal details, one or several types of identity document, residential address, one or several types of proof of address document, a phone number, or an email address. You can also request optional selfies with the document and certified English translations of the document. -This is just a list of data types that can be requested, and the encrypted objects that will contain such data.

-
-

Note: We suggest to only request English translations after you have received a valid document that requires one.

-
-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameKeyTypeDescription
personal_detailsdataPersonalDetailsPersonal Details
passportdataIdDocumentDataPassport
front_sidePassportFile
selfieOptional. PassportFile
translationOptional. Array of PassportFile
internal_passportdataIdDocumentDataInternal Passport
front_sidePassportFile
selfieOptional. PassportFile
translationOptional. Array of PassportFile
driver_licensedataIdDocumentDataDriver License
front_sidePassportFile
reverse_sidePassportFile
selfieOptional. PassportFile
translationOptional. Array of PassportFile
identity_carddataIdDocumentDataIdentity Card
front_sidePassportFile
reverse_sidePassportFile
selfieOptional. PassportFile
translationOptional. Array of PassportFile
addressdataResidentialAddressAddress
utility_billfilesArray of PassportFileUtility Bill
translationOptional. Array of PassportFile
bank_statementfilesArray of PassportFileBank Statement
translationOptional. Array of PassportFile
rental_agreementfilesArray of PassportFileRental Agreement
translationOptional. Array of PassportFile
passport_registrationfilesArray of PassportFileRegistration Page in the Internal Passport
translationOptional. Array of PassportFile
temporary_registrationfilesArray of PassportFileTemporary Registration
translationOptional. Array of PassportFile
phone_numberStringPhone number
emailStringEmail
-

PersonalDetails

-

This object represents personal details.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
first_nameStringFirst Name
last_nameStringLast Name
middle_nameStringOptional. Middle Name
birth_dateStringDate of birth in DD.MM.YYYY format
genderStringGender, male or female
country_codeStringCitizenship (ISO 3166-1 alpha-2 country code)
residence_country_codeStringCountry of residence (ISO 3166-1 alpha-2 country code)
first_name_nativeStringFirst Name in the language of the user's country of residence
last_name_nativeStringLast Name in the language of the user's country of residence
middle_name_nativeStringOptional. Middle Name in the language of the user's country of residence
-

ResidentialAddress

-

This object represents a residential address.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
street_line1StringFirst line for the address
street_line2StringOptional. Second line for the address
cityStringCity
stateStringOptional. State
country_codeStringISO 3166-1 alpha-2 country code
post_codeStringAddress post code
-

IdDocumentData

-

This object represents the data of an identity document.

- - - - - - - - - - - - - - - - - - -
FieldTypeDescription
document_noStringDocument number
expiry_dateStringOptional. Date of expiry, in DD.MM.YYYY format
-

PassportFile

-

This object represents a PassportFile related to a document. The file is up to 10MB in size and in the .jpg format.

-

Receiving information

-

When the user confirms your request by pressing the 'Authorize' button, the Bot API sends an Update with the field passport_data to the bot that contains encrypted Telegram Passport data.

-
-

Note that all base64-encoded fields should be decoded before use.

-
-

Decrypting data

-

To decrypt the received data, first, decrypt the credentials contained in EncryptedCredentials.

-
    -
  1. -

    Decrypt the credentials secret ( secret field in EncryptedCredentials) using your private key (set OAEP padding option, e.g. OPENSSL_PKCS1_OAEP_PADDING in PHP)

    -
  2. -
  3. -

    Use this secret and the credentials hash ( hash field in EncryptedCredentials) to calculate credentials_key and credentials_iv as described below:

    -
     credentials_secret_hash = SHA512( credentials_secret + credentials_hash )
    - credentials_key = slice( credentials_secret_hash, 0, 32 )
    - credentials_iv = slice( credentials_secret_hash, 32, 16 )
    -
  4. -
  5. -

    Decrypt the credentials data ( data field in EncryptedCredentials) by AES256-CBC using these credentials_key and credentials_iv. IMPORTANT: At this step, make sure that the credentials hash is equal to SHA256( credentials_data )

    -
  6. -
  7. -

    Credentials data is padded with 32 to 255 random padding bytes to make its length divisible by 16 bytes. The first byte contains the length of this padding (including this byte). Remove the padding to get the data.

    -
  8. -
-
-

Note that all hashes represent as raw binary data, not hexits

-
-

Credentials

-

Credentials is a JSON-serialized object.

- - - - - - - - - - - - - - - - - - -
FieldTypeDescription
secure_dataSecureDataCredentials for encrypted data
nonceStringBot-specified nonce
-

IMPORTANT: Make sure that the nonce is the same as was passed in the request.

-

SecureData

-

This object represents the credentials required to decrypt encrypted data. All fields are optional and depend on fields that were requested.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
personal_detailsSecureValueOptional. Credentials for encrypted personal details
passportSecureValueOptional. Credentials for encrypted passport
internal_passportSecureValueOptional. Credentials for encrypted internal passport
driver_licenseSecureValueOptional. Credentials for encrypted driver license
identity_cardSecureValueOptional. Credentials for encrypted ID card
addressSecureValueOptional. Credentials for encrypted residential address
utility_billSecureValueOptional. Credentials for encrypted utility bill
bank_statementSecureValueOptional. Credentials for encrypted bank statement
rental_agreementSecureValueOptional. Credentials for encrypted rental agreement
passport_registrationSecureValueOptional. Credentials for encrypted registration from internal passport
temporary_registrationSecureValueOptional. Credentials for encrypted temporary registration
-

SecureValue

-

This object represents the credentials required to decrypt encrypted values. All fields are optional and depend on the type of fields that were requested.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
dataDataCredentialsOptional. Credentials for encrypted Telegram Passport data. Available for "personal_details", "passport", "driver_license", "identity_card", "internal_passport" and "address" types.
front_sideFileCredentialsOptional. Credentials for an encrypted document's front side. Available for "passport", "driver_license", "identity_card" and "internal_passport".
reverse_sideFileCredentialsOptional. Credentials for an encrypted document's reverse side. Available for "driver_license" and "identity_card".
selfieFileCredentialsOptional. Credentials for an encrypted selfie of the user with a document. Available for "passport", "driver_license", "identity_card" and "internal_passport".
translationArray of FileCredentialsOptional. Credentials for an encrypted translation of the document. Available for "passport", "driver_license", "identity_card", "internal_passport", "utility_bill", "bank_statement", "rental_agreement", "passport_registration" and "temporary_registration".
filesArray of FileCredentialsOptional. Credentials for encrypted files. Available for "utility_bill", "bank_statement", "rental_agreement", "passport_registration" and "temporary_registration" types.
-

DataCredentials

-

These credentials can be used to decrypt encrypted data from the data field in EncryptedPassportElement.

- - - - - - - - - - - - - - - - - - -
FieldTypeDescription
data_hashStringChecksum of encrypted data
secretStringSecret of encrypted data
-
    -
  1. -

    To decrypt data, use the corresponding secret and data_hash from DataCredentials as described below:

    -
     data_secret_hash = SHA512( data_secret + data_hash )
    - data_key = slice( data_secret_hash, 0, 32 )
    - data_iv = slice( data_secret_hash, 32, 16 )
    -
  2. -
  3. -

    Use AES256-CBC with this data_key and data_iv to decrypt the data (the data field in EncryptedPassportElement). IMPORTANT: At this step, make sure that data_hash from the credentials is equal to SHA256( data ).

    -
  4. -
  5. -

    The data is padded with 32 to 255 random padding bytes to make its length divisible by 16 bytes. The first byte contains the length of the padding (including this byte). Remove padding to get the data.

    -
  6. -
  7. -

    The data is a JSON-serialized object of one of the following types: PersonalDetails, IdDocumentData, ResidentialAddress, depending on type.

    -
  8. -
-

FileCredentials

-

These credentials can be used to decrypt encrypted files from the front_side, reverse_side, selfie, files and translation fields in EncryptedPassportElement.

- - - - - - - - - - - - - - - - - - -
FieldTypeDescription
file_hashStringChecksum of encrypted file
secretStringSecret of encrypted file
-
    -
  1. -

    To decrypt the file, use the corresponding secret and file_hash from FileCredentials as described below:

    -
     file_secret_hash = SHA512( file_secret + file_hash )
    - file_key = slice( file_secret_hash, 0, 32 )
    - file_iv = slice( file_secret_hash, 32, 16 )
    -
  2. -
  3. -

    Download the encrypted file using the getFile method.

    -
  4. -
  5. -

    Use AES256-CBC with this file_key and file_iv to decrypt the content of the file. IMPORTANT: At this step, make sure that file_hash from the credentials is equal to SHA256( file_content ).

    -
  6. -
  7. -

    The content of the file is padded with 32 to 255 random padding bytes to make its length divisible by 16 bytes. The first byte contains the length of the padding (including that byte). Remove padding to get the file content.

    -
  8. -
-

Fixing errors

-

If the data you received contains errors, the bot can use the setPassportDataErrors method to inform the user and request information again. The user will not be able to resend the data, until all errors are fixed.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/passport/encryption.html b/data/corefork.telegram.org/passport/encryption.html deleted file mode 100644 index 8aed498b38..0000000000 --- a/data/corefork.telegram.org/passport/encryption.html +++ /dev/null @@ -1,606 +0,0 @@ - - - - - Telegram Passport Encryption Details - - - - - - - - - - - - - -
- -
-
-
- -

Telegram Passport Encryption Details

- -
- -

Telegram Passport data is stored encrypted End-to-End which means that the Telegram server does not have access to the data and only functions as a storage for encrypted data it can't decipher. Encryption and decryption are handled exclusively by the Telegram clients, which are open source.

-

Overview

-

To encrypt each particular element of Telegram Passport, the client generates a random secret. The secret is a 32-byte number with the modulo 255 sum of bytes equal to 239. This secret is in turn encrypted with the passport_secret that is generated when the user creates their Telegram Passport. passport_secret is encrypted with the user's password and is stored encrypted in the Telegram Cloud.

-

Passport Secret

-

The passport secret is one of the secret parameters used to encrypt the data uploaded by the user to the Telegram Cloud.

-

When first setting up Telegram Passport it must be created, encrypted and uploaded as described in Passport Secret Encryption.

-

When using Telegram Passport normally, it must be downloaded and decrypted for use as described in Passport Secret Decryption.

-

The passport secret must also be downloaded, re-encrypted and re-uploaded as described in Passport Secret Encryption if a new, more secure encryption algorithm is defined in a newer version of Telegram or the 2FA password is updated.

-

Passport Secret Encryption

-

First of all, server-side passport parameters are fetched, schema:

-
account.password#185b184f flags:# has_recovery:flags.0?true has_secure_values:flags.1?true has_password:flags.2?true current_algo:flags.2?PasswordKdfAlgo srp_B:flags.2?bytes srp_id:flags.2?long hint:flags.3?string email_unconfirmed_pattern:flags.4?string new_algo:PasswordKdfAlgo new_secure_algo:SecurePasswordKdfAlgo secure_random:bytes pending_reset_date:flags.5?int = account.Password;
-
-securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;
-securePasswordKdfAlgoPBKDF2HMACSHA512iter100000#bbf2dda0 salt:bytes = SecurePasswordKdfAlgo;
-securePasswordKdfAlgoSHA512#86471d92 salt:bytes = SecurePasswordKdfAlgo;
-
-
----functions---
-
-account.getPassword#548a30f5 = account.Password;
-

When Telegram Passport is first used, the client generates a passport_secret (a 32-byte number with the modulo 255 sum of bytes equal to 239), using a part of server-generated random secure_random from account.password as an additional source of entropy for OpenSSL (when re-encrypting the passport_secret with a more secure algorithm or after a 2FA password change, the previous passport_secret is used, instead). -Then passport_secret is then encrypted using the user's password and hashed using the schema and parameters specified in the new_algo field of account.password.

-

The server should always return a securePasswordKdfAlgoPBKDF2HMACSHA512iter100000 constructor in the new_algo field. -If securePasswordKdfAlgoUnknown is returned, the remotely stored secret is encrypted using a new algorithm, not supported by the current client: the user should update their app.

-

The other constructors may be used only when decrypting old passport parameters generated by a legacy client; in this case, the passport secret should be re-encrypted and updated using new_algo.

- -

Subsequently, the client receives the encrypted passport_secret from the server and decrypts it after the user enters their password ».

-

In case the password is changed or a more secure algorithm is introduced in an update of the API, the client re-encrypts the passport_secret using the new password. -If the password is disabled, all Telegram Passport data is lost.

-

Passport Secret Decryption

-

Schema:

-
securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;
-securePasswordKdfAlgoPBKDF2HMACSHA512iter100000#bbf2dda0 salt:bytes = SecurePasswordKdfAlgo;
-securePasswordKdfAlgoSHA512#86471d92 salt:bytes = SecurePasswordKdfAlgo;
-
-secureSecretSettings#1527bcac secure_algo:SecurePasswordKdfAlgo secure_secret:bytes secure_secret_id:long = SecureSecretSettings;
-
-account.passwordSettings#9a5c33e5 flags:# email:flags.0?string secure_settings:flags.1?SecureSecretSettings = account.PasswordSettings;
-
----functions---
-
-account.getPasswordSettings#9cd4eaf9 password:InputCheckPasswordSRP = account.PasswordSettings;
-

The client requests the user's 2FA password and generates the SRP paramaters to be passed to account.getPasswordSettings.

-

If the password is correct, an account.passwordSettings constructor with secureSecretSettings is returned.

-

encrypted_passport_secret, passport_secret_fingerprint parameters are extracted from the secureSecretSettings constructor:

-
encrypted_passport_secret = secureSecretSettings.secure_secret
-passport_secret_fingerprint = secureSecretSettings.secure_id
-

The combined passport_secret_salt is extracted from the SecurePasswordKdfAlgo.

-
passport_secret_salt = SecurePasswordKdfAlgo.salt
-

Similar to passport secret encryption, the following process is used to decrypt and verify the encrypted_passport_secret:

-
    -
  • -

    The user's 2FA plaintext password is hashed using the specified algorithm.

    - -
  • -
  • -

    The secret_key and iv parameters are extracted from the generated password_hash

    -
    secret_key = slice( password_hash, 0, 32 )
    -iv = slice( password_hash, 32, 16 )
    -
  • -
  • -

    The encrypted_passport_secret is decrypted using AES256-CBC with the key secret_key and iv:

    -
    passport_secret = AES256_CBC_DEC(encrypted_passport_secret, secret_key, iv)
    -
  • -
  • -

    The passport_secret is verified by generating and checking the fingerprint:

    -
    my_passport_secret_fingerprint = long( slice( SHA256( passport_secret ), 0, 8 ) )
    -

    The client must verify that passport_secret_fingerprint is indeed equal to my_passport_secret_fingerprint.

    -
  • -
-

The passport_secret can now be used to decrypt encrypted passport data stored on telegram servers:

-

Data and File Encryption

-

Encryption

-

To encrypt Telegram Passport data, the client generates a data_secret (a 32-byte number with the modulo 255 sum of bytes equal to 239). The the data is encrypted according to the following scheme:

- -

Packing

-
SecureData
-
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;
-
    -
  • data is an encrypted and padded (see Encryption) JSON-serialized object of one of the following types: PersonalDetails, IdDocumentData, ResidentialAddress, depending on the chosen type. -Data must be in JSON format and not TL, as it has to be passed directly to the service using E2E encryption, without the bot API middleman to convert TL objects.
  • -
  • data_hash is the data_hash
  • -
  • secret is the encrypted_data_secret
  • -
-

Data is an encrypted and padded JSON-serialized object of one of the specified JSON types, depending on the chosen type.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Chosen typeJSON object
secureValueTypePersonalDetailsPersonalDetails
secureValueTypePassportIdDocumentData
secureValueTypeDriverLicenseIdDocumentData
secureValueTypeIdentityCardIdDocumentData
secureValueTypeInternalPassportIdDocumentData
secureValueTypeAddressResidentialAddress
-
InputSecureFile
-
inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;
-inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;
-
----functions---
-
-upload.saveFilePart#b304a621 file_id:long file_part:int bytes:bytes = Bool;
-

Files (JPG format, max. 10MB) are encrypted and padded (see Encryption), and then uploaded chunk by chunk as described in files », except that instead of generating an inputFile, an inputSecureFile should be generated, instead.

-
    -
  • As for secret chat files, the md5_checksum is to be set to the MD5 hash of the encrypted file, for a server-side integrity check.
  • -
  • The file_hash field should be set to the data_hash of the data.
  • -
  • The secret field is the encrypted_data_secret.
  • -
-
SecurePlainData
-
securePlainPhone#7d6099dd phone:string = SecurePlainData;
-securePlainEmail#21ec5a5f email:string = SecurePlainData;
-
----functions---
-
-account.sendVerifyPhoneCode#a5a356f9 phone_number:string settings:CodeSettings = auth.SentCode;
-account.verifyPhone#4dd3a7f6 phone_number:string phone_code_hash:string phone_code:string = Bool;
-account.sendVerifyEmailCode#7011509f email:string = account.SentEmailCode;
-account.verifyEmail#ecba39db email:string code:string = Bool;
-
-auth.resendCode#3ef1a9bf phone_number:string phone_code_hash:string = auth.SentCode;
-auth.cancelCode#1f040578 phone_number:string phone_code_hash:string = Bool;
-

The email/phone is passed in plaintext using the respective SecurePlainData constructor. -To verify a phone number or email and use it in Telegram Passport, use the appropriate methods:

- -

The flow is similar to the one used for logging in:

-
    -
  • Send email/phone code using the appropriate account.sendVerify*Code method
  • -
  • Pass the received code to the appropriate account.verify* method
  • -
  • Only for phone code verification, you can also resend/cancel the phone code using auth.resendCode/auth.cancelCode, as for logging in.
  • -
-

For more info, see the authorization docs.

-

When to use each constructor.

-
inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;
-inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;
-
-secureValueTypePersonalDetails#9d2a81e3 = SecureValueType;
-secureValueTypePassport#3dac6a00 = SecureValueType;
-secureValueTypeDriverLicense#6e425c4 = SecureValueType;
-secureValueTypeIdentityCard#a0d0744b = SecureValueType;
-secureValueTypeInternalPassport#99a48f23 = SecureValueType;
-secureValueTypeAddress#cbe31e26 = SecureValueType;
-secureValueTypeUtilityBill#fc36954e = SecureValueType;
-secureValueTypeBankStatement#89137c0d = SecureValueType;
-secureValueTypeRentalAgreement#8b883488 = SecureValueType;
-secureValueTypePassportRegistration#99e3806a = SecureValueType;
-secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;
-secureValueTypePhone#b320aadb = SecureValueType;
-secureValueTypeEmail#8e3ca7ee = SecureValueType;
-
-securePlainPhone#7d6099dd phone:string = SecurePlainData;
-securePlainEmail#21ec5a5f email:string = SecurePlainData;
-
-secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;
-
-inputSecureValue#db21d0a7 flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?InputSecureFile reverse_side:flags.2?InputSecureFile selfie:flags.3?InputSecureFile translation:flags.6?Vector<InputSecureFile> files:flags.4?Vector<InputSecureFile> plain_data:flags.5?SecurePlainData = InputSecureValue;
-

The schema for the inputSecureValue constructor defines the constructor to use for each field.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
typeSecureValueTypeSecure passport value type
dataflags.0?SecureDataEncrypted Telegram Passport element data
front_sideflags.1?InputSecureFileEncrypted passport file with the front side of the document
reverse_sideflags.2?InputSecureFileEncrypted passport file with the reverse side of the document
selfieflags.3?InputSecureFileEncrypted passport file with a selfie of the user holding the document
translationflags.6?Vector<InputSecureFile>Array of encrypted passport files with translated versions of the provided documents
filesflags.4?Vector<InputSecureFile>Array of encrypted passport files with photos the of the documents
plain_dataflags.5?SecurePlainDataPlaintext verified passport data
-

Here's a list of possible SecureValueTypes, and the parameters that can be set/requested when using each type.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TypeAllowed fields
secureValueTypeEmailplain_data
secureValueTypePhoneplain_data
secureValueTypePersonalDetailsdata
secureValueTypePassportdata, front_side, selfie, translation
secureValueTypeDriverLicensedata, front_side, reverse_side, selfie, translation
secureValueTypeIdentityCarddata, front_side, reverse_side, selfie, translation
secureValueTypeInternalPassportdata, front_side, selfie, translation
secureValueTypeAddressdata
secureValueTypeUtilityBillfiles, translation
secureValueTypeBankStatementfiles, translation
secureValueTypeRentalAgreementfiles, translation
secureValueTypePassportRegistrationfiles, translation
secureValueTypeTemporaryRegistrationfiles, translation
-

Fetching and deleting stored passport data

-
---functions---
-
-account.getAllSecureValues#b288bc7d = Vector<SecureValue>;
-account.getSecureValue#73665bc2 types:Vector<SecureValueType> = Vector<SecureValue>;
-account.deleteSecureValue#b880bc4b types:Vector<SecureValueType> = Bool;
-

The above methods can be used to fetch or remove encrypted Telegram Passport files stored in the Telegram Cloud by document type.

-

Passport Credentials

-

When a service requests data, it passes a nonce to the client. The nonce is a cryptographically secure unique identifier which allows the service to identify a request when receiving data as well as confirm the integrity of the data. The Telegram server doesn't have access to this nonce.

-

Once the user authorizes the Telegram Passport data transfer, the client forms the credentials (Credentials JSON object). Credentials contain the data_hash and data_secret from each element of Telegram Passport to which the user has allowed access. In addition to this, the credentials will always contain the nonce that the client received from the service at the initiation of the request.

-

Credentials are then passed to the service through the Bot API in encrypted form. To encrypt the credentials, the client generates a credentials_secret (a 32-byte number with the modulo 255 sum of bytes equal to 239). Then the credentials are encrypted according to the following scheme:

-
    -
  • -

    Credentials are padded to a length which is divisible by 16 bytes. To achieve this, 32 to 255 bytes are added at the beginning, where the first byte always holds the number of added bytes and the rest are random.

    -
  • -
  • -

    A hash of the padded credentials credentials_hash is calculated:

    -
    credentials_hash = SHA256( credentials )
    -
  • -
  • -

    The encryption key credentials_key is calculated:

    -
    credentials_secret_hash = SHA512( credentials_secret + credentials_hash )
    -credentials_key = slice( credentials_secret_hash, 0, 32 )
    -iv = slice( credentials_secret_hash, 32, 16 )
    -
  • -
  • -

    Credentials are encrypted using AES256-CBC with the key credentials_key and iv.

    -
    encrypted_credentials = AES256-CBC-ENC(credentials, credentials_key, iv)
    -
  • -
  • -

    credentials_secret is encrypted with the public RSA-key of the service with OPENSSL_PKCS1_OAEP_PADDING.

    -
    encrypted_credentials_secret = RSA-ENC(credentials_secret, key, OPENSSL_PKCS1_OAEP_PADDING)
    -
  • -
  • -

    The encrypted credentials are passed to the service via the MTProto API together with the encrypred credentials_secret and credentials_hash. Along with the credentials, the service receives from the Telegram Cloud the data it requested in encrypted form. See Submitting the Passport Form and PassportData:

    -
    secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;
    -
  • -
  • -

    data is the encrypted_credentials

    -
  • -
  • -

    hash is the credentials_hash

    -
  • -
  • -

    secret is the encrypted_credentials_secret

    -
  • -
-

Then the service decrypts the data as described here.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/passport/example.html b/data/corefork.telegram.org/passport/example.html deleted file mode 100644 index fbfa48d49e..0000000000 --- a/data/corefork.telegram.org/passport/example.html +++ /dev/null @@ -1,585 +0,0 @@ - - - - - Example - - - - - - - - - - - - - - - -
- -
-
-
-
-

Example

- -

If you'd like to test Telegram Passport, use this page to request data. If you'd like to check out a real-life implementation, please see this blog post for examples of services that have integrated Telegram Passport.

-

Request Telegram Passport Data

-

-

-
-
-
- - -
-
-
-
- -
- -
- -
-
- -
-
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- - -
-
-
-
- -
- -
- -
- -
-
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- -
-
- - -
-
-
-
- -
- -
- -
-
- -
-
- -
-
- - -
-
-
- -

-
-
-

Note that the passport demo bot will only store data for 1 hour and then discard it. After logging in here, you can use the logout button on this page to reset your session.

-
- -
- -
-
- -
- - - - - - - - - diff --git a/data/corefork.telegram.org/passport/sdk-android.html b/data/corefork.telegram.org/passport/sdk-android.html deleted file mode 100644 index 9784921198..0000000000 --- a/data/corefork.telegram.org/passport/sdk-android.html +++ /dev/null @@ -1,180 +0,0 @@ - - - - - Android SDK - - - - - - - - - - - - - -
- -
-
-
- -

Android SDK

- -
- -

The Android SDK helps you easily integrate Telegram Passport requests into your Android-based apps. Check out our GitHub repository to see samples using this SDK.

-

Installation

-

Installing from Maven

-

Telegram Passport SDK is available from the Maven repository. -Add this line to the dependencies section in your build.gradle:

-
compile 'org.telegram:passport:1.1'
-

and sync your project.

-

Adding as a module

-

Download the library, unzip it and copy the library project to the root of your project directory (the one with settings.gradle and gradle.properties). Then, make the following changes to your Gradle scripts.

-

In settings.gradle, add ':telegrampassport' to includes:

-
include ':app', ':telegrampassport'
-

In the build.gradle file for your app, add this line to the dependencies section:

-
compile ':telegrampassport'
-

and sync your project.

-

Usage

-

Adding the button

-

The SDK provides the "Log in with Telegram" button which we recommend using for a consistent user experience across different apps. You can either add it from your Java code:

-
TelegramLoginButton telegramButton;
-// ...
-telegramButton=new TelegramLoginButton(this);
-// Optionally you can change the roundness of the button corners
-// to better fit your design.
-telegramButton.setCornerRoundness(1f);
-viewGroupOfSomeSort.addView(telegramButton, ViewGroup.LayoutParams.WRAP_CONTENT, ViewGroup.LayoutParams.WRAP_CONTENT);
-

Or from XML:

-
 <org.telegram.passport.TelegramLoginButton
-             android:layout_width="wrap_content"
-             android:layout_height="wrap_content"
-             app:cornerRoundness="0.5"/>
-

Requesting authorization

-

The button doesn't do anything by itself; you need to set an OnClickListener on it to start the authorization flow (replace the comments with actual parameters):

-
private static final int TG_PASSPORT_RESULT=352; // this can be any integer less than 0xFFFF
-// ...
-telegramButton.setOnClickListener(new View.OnClickListener(){
-@Override
-public void onClick(View view){
-    TelegramPassport.AuthRequest req=new TelegramPassport.AuthRequest();
-    req.botID=/* your bot ID here */;
-    req.publicKey=/* your bot public key here */;
-    req.nonce=/* a unique nonce to pass to the bot server */;
-    // Request either a passport or an ID card with selfie, a driver license, personal details with
-    // name as it appears in the documents, address with any address document, and a phone number.
-    // You could also pass a raw JSON object here if that's what works better for you
-    // (for example, if you already get it from your server in the correct format).
-    req.scope=new PassportScope(
-        new PassportScopeElementOneOfSeveral(PassportScope.PASSPORT, PassportScope.IDENTITY_CARD).withSelfie(),
-        new PassportScopeElementOne(PassportScope.PERSONAL_DETAILS).withNativeNames(),
-        PassportScope.DRIVER_LICENSE,
-        PassportScope.ADDRESS,
-        PassportScope.ADDRESS_DOCUMENT,
-        PassportScope.PHONE_NUMBER
-    );
-    TelegramPassport.request(MyActivity.this, req, TG_PASSPORT_RESULT);
-}});
-

If you need more control over the process, the TelegramPassport class contains several more methods:

-
    -
  • getAuthIntent(AuthParams) returns an Intent for you to use in startActivityForResult if you need to do that in some special way. Be sure to check that an app is present that can handle this intent before starting it by using PackageManager or intent.resolveActivity.
  • -
  • showAppInstallAlert(Activity) shows an alert that the user needs to install Telegram in order to continue. This is intended to be used together with the previous method for the cases when the app isn't installed.
  • -
-

Handling the result

-

The result is delivered via the onActivityResult method in your activity with the request code you passed to TelegramPassport.request. Currently, the only meaningful parameter is resultCode, which is RESULT_OK if the authorization was successful and RESULT_CANCELED otherwise.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/passport/sdk-ios-mac.html b/data/corefork.telegram.org/passport/sdk-ios-mac.html deleted file mode 100644 index ce9fca8125..0000000000 --- a/data/corefork.telegram.org/passport/sdk-ios-mac.html +++ /dev/null @@ -1,246 +0,0 @@ - - - - - iOS & macOS SDK - - - - - - - - - - - - - -
- -
-
-
- -

iOS & macOS SDK

- -
- -

TGPassportKit helps you easily integrate Telegram Passport requests into your iOS & macOS apps. Check out our GitHub repository to see samples using this SDK.

-

Installation

-

Installing using Cocoapods

-

To install TGPassportKit via Cocoapods add the following to your Podfile:

-
target 'MyApp' do
-  pod 'TGPassportKit' 
-end
-

then run pod install in your project root directory.

-

Installing using Carthage

-

Add the following line to your Cartfile:

-
github "telegrammessenger/TGPassportKit"
-

then run carthage update, and you will get the latest version of TGPassportKit in your Carthage folder.

-

Project Setup

-

Configure Your Info.plist

-

Configure your Info.plist by right-clicking it in Project Navigator, choosing Open As > Source Code and adding this snippet: -Replace {bot_id} with your value

-
<key>CFBundleURLTypes</key>
-<array>
-  <dict>
-  <key>CFBundleURLSchemes</key>
-  <array>
-    <string>tgbot{bot_id}</string>
-  </array>
-  </dict>
-</array>
-<key>LSApplicationQueriesSchemes</key>
-<array>
-  <string>tg</string>
-</array>
-

Connect AppDelegate methods

-

Add this code to your UIApplicationDelegate implementation

-
#import <TGPassportKit/TGPAppDelegate.h>
-
-- (BOOL)application:(UIApplication *)application
-            openURL:(NSURL *)url
-            options:(NSDictionary<UIApplicationOpenURLOptionsKey, id> *)options {
-    BOOL handledByPassportKit = [[TGPAppDelegate sharedDelegate] application:application
-                                                                     openURL:url
-                                                                     options:options];
-
-    return YES;
-}
-

If you support iOS 9 and below, also add this method:

-
- (BOOL)application:(UIApplication *)application 
-            openURL:(NSURL *)url 
-  sourceApplication:(nullable NSString *)sourceApplication 
-         annotation:(id)annotation {
-    BOOL handledByPassportKit = [[TGPAppDelegate sharedDelegate] application:application
-                                                                     openURL:url
-                                                           sourceApplication:sourceApplication
-                                                                  annotation:annotation];
-
-    return YES;
-}
-

Usage

-

Add Telegram Passport Button

-

To add the Telegram Passport button, add the following code to your view controller: -Replace {bot_id}, {bot_public_key} and {request_nonce} with your values

-
#import <TGPassportKit/TGPButton.h>
-
-@interface ViewController <TGPButtonDelegate>
-
-@end
-
-@implementation ViewController
-
-- (void)viewDidLoad {
-  [super viewDidLoad];
-
-  TGPButton *button = [[TGPButton alloc] init];
-  button.botConfig = [[TGPBotConfig alloc] initWithBotId:{bot_id} 
-                                               publicKey:@"{bot_public_key}"];
-  button.scope = [[TGPScope alloc] initWithJSONString:@"{\"data\":[\"id_document\",\"address_document\",\"phone_number\"],\"v\":1}"];
-// You can also construct a scope using provided data type classes like this: 
-// button.scope = [[TGPScope alloc] initWithTypes:@[[[TGPPersonalDetails alloc] init], [[TGPIdentityDocument alloc] initWithType:TGPIdentityDocumentTypePassport selfie:true translation:true]]];
-  button.nonce = @"{request_nonce}";
-  button.delegate = self;
-  [self.view addSubview:button];
-}
-
-- (void)passportButton:(TGPButton *)passportButton 
- didCompleteWithResult:(TGPRequestResult)result 
-                 error:(NSError *)error {
-    switch (result) {
-        case TGPRequestResultSucceed:
-            NSLog(@"Succeed");
-            break;
-
-        case TGPRequestResultCancelled:
-            NSLog(@"Cancelled");
-            break;
-
-        default:
-            NSLog(@"Failed");
-            break;
-    }
-}
-
-@end
-

...or Implement Your Own Behavior

-

If you want to design a custom UI and behavior, you can invoke a Passport request like this: -Replace {bot_id}, {bot_public_key} and {request_nonce} with your values

-
#import <TGPassportKit/TGPRequest.h>
-
-- (void)performPassportRequest 
-{
-    TGPBotConfig *botConfig = [[TGPBotConfig alloc] initWithBotId:{bot_id} 
-                                                        publicKey:@"{bot_public_key}"];
-    TGPRequest *request = [[TGPRequest alloc] initWithBotConfig:botConfig];
-    [request performWithScope:[[TGPScope alloc] initWithJSONString:@"{\"data\":[\"id_document\",\"phone_number\"],\"v\":1}"] 
-                      payload:@"{request_nonce}" 
-            completionHandler:^(TGPRequestResult result, NSError * _Nullable error) {
-        switch (result) {
-            case TGPRequestResultSucceed:
-                NSLog(@"Succeed");
-                break;
-
-            case TGPRequestResultCancelled:
-                NSLog(@"Cancelled");
-                break;
-
-            default:
-                NSLog(@"Failed");
-                break;
-        }
-    }];
-}
- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/passport/sdk-javascript.html b/data/corefork.telegram.org/passport/sdk-javascript.html deleted file mode 100644 index 4a9ea10099..0000000000 --- a/data/corefork.telegram.org/passport/sdk-javascript.html +++ /dev/null @@ -1,258 +0,0 @@ - - - - - Javascript SDK - - - - - - - - - - - - - -
- -
-
-
- -

Javascript SDK

- -
- -

The Javascript SDK helps you easily integrate Telegram Passport requests into your website. Check out our GitHub repository to see samples using this SDK.

-

Installation

-

Download and include the Javascript SDK in the head section of your page:

-
<script src="telegram-passport.js"></script>
-

Usage

-

Simply call Telegram.Passport.createAuthButton to create the default Telegram Passport button:

-
<div id="telegram_passport_auth"></div>
-<script>
-  Telegram.Passport.createAuthButton('telegram_passport_auth', {
-    bot_id:       123456, // place id of your bot here
-    scope:        {data: [{type: 'id_document', selfie: true}, 'address_document', 'phone_number', 'email'], v: 1},
-    public_key:   '-----BEGIN PUBLIC KEY----- ...', // place public key of your bot here
-    nonce:        'ab2df83746a87d2f3bd6...', // place nonce here
-    callback_url: 'https://example.com/callback/' // place callback url here
-  });
-</script>
-
-

Note that if you use a Content-Security-Policy (CSP) header with the frame-src/child-src directive you should allow tg: source to prevent errors in some browsers (e.g. Firefox)

-
-

createAuthButton

- - - - - - - - - - - - - - - - - - - - - - - -
ParametersTypeRequired
elementString or DOMNodeYes
auth_paramsAuthParameters or FunctionYes
optionsAuthButtonOptionsOptional
-

AuthParameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
bot_idIntegerUnique identifier for the bot
scopePassportScopeA JSON-serialized object describing the data you want to request
public_keyStringPublic key of your bot
nonceStringBot-specified nonce
callback_urlStringOptional. URL to which the user will be redirected.
-

AuthButtonOptions

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
FieldTypeDescription
textStringOptional. Text on the button. Defaults to "Log In With Telegram".
radiusIntegerOptional. Radius of the button and tooltip in px. Defaults to 23.
tooltip_textStringOptional. Text on the tooltip. Defaults to "Please install Telegram to use this option.".
tooltip_positionStringOptional. Tooltip position. One of "top", "bottom", "left", "right". Defaults to "bottom".
tooltip_forceBooleanOptional. Always show a tooltip. Defaults to false.
-

You can also create your custom button. Do not forget about the tooltip. You should add an onclick listener to the button which calls the Telegram.Passport.auth(auth_params, tooltip_toggle); method:

-
<button id="telegram_passport_auth">Log In With Telegram</button>
-<script>
-  var auth_button = document.getElementById('telegram_passport_auth');
-  var auth_params = {
-    bot_id:        XXXXXX, // place id of your bot here
-    scope:         {data: [{type: 'id_document', selfie: true}, 'address_document', 'phone_number', 'email'], v: 1},
-    public_key:    '-----BEGIN PUBLIC KEY----- ...', // place public key of your bot here
-    nonce:         'ab2df83746a87d2f3bd6...', // place nonce here
-    callback_url:  'https://example.com/callback/' // place callback url here
-  };
-  auth_button.addEventListener('click', function() {
-    Telegram.Passport.auth(auth_params, function(show) {
-      if (show) {
-        // some code to show tooltip
-      } else {
-        // some code to hide tooltip
-      }
-    });
-  }, false);
-</script>
-

Receiving information

-

When the user confirms your request by pressing the 'Authorize' button, it will be redirected to the URL specified in the callback_url with the parameter tg_passport=success and the Bot API will send the bot an Update with the field passport_data which contains encrypted Telegram Passport data.

-

If the user cancels your request, it will be redirected to the URL specified in the callback_url with the parameter tg_passport=cancel.

-

If an error occurs during the request, the user will be redirected to the URL specified in the callback_url with the parameter tg_passport=error. The parameter error will contain one of the following values: BOT_INVALID, PUBLIC_KEY_REQUIRED, PUBLIC_KEY_INVALID, SCOPE_EMPTY, NONCE_EMPTY.

- -
- -
-
- -
- - - - - - - - diff --git a/data/corefork.telegram.org/schema/end-to-end-json.html b/data/corefork.telegram.org/schema/end-to-end-json.html deleted file mode 100644 index 6c3b4f2cbe..0000000000 --- a/data/corefork.telegram.org/schema/end-to-end-json.html +++ /dev/null @@ -1 +0,0 @@ -{"constructors":[{"id":"528568095","predicate":"decryptedMessage","params":[{"name":"random_id","type":"long"},{"name":"random_bytes","type":"bytes"},{"name":"message","type":"string"},{"name":"media","type":"DecryptedMessageMedia"}],"type":"DecryptedMessage","layer":8},{"id":"541931640","predicate":"decryptedMessage","params":[{"name":"random_id","type":"long"},{"name":"ttl","type":"int"},{"name":"message","type":"string"},{"name":"media","type":"DecryptedMessageMedia"}],"type":"DecryptedMessage","layer":17},{"id":"917541342","predicate":"decryptedMessage","params":[{"name":"flags","type":"#"},{"name":"random_id","type":"long"},{"name":"ttl","type":"int"},{"name":"message","type":"string"},{"name":"media","type":"flags.9?DecryptedMessageMedia"},{"name":"entities","type":"flags.7?Vector"},{"name":"via_bot_name","type":"flags.11?string"},{"name":"reply_to_random_id","type":"flags.3?long"}],"type":"DecryptedMessage","layer":45},{"id":"-1848883596","predicate":"decryptedMessage","params":[{"name":"flags","type":"#"},{"name":"random_id","type":"long"},{"name":"ttl","type":"int"},{"name":"message","type":"string"},{"name":"media","type":"flags.9?DecryptedMessageMedia"},{"name":"entities","type":"flags.7?Vector"},{"name":"via_bot_name","type":"flags.11?string"},{"name":"reply_to_random_id","type":"flags.3?long"},{"name":"grouped_id","type":"flags.17?long"}],"type":"DecryptedMessage","layer":73},{"id":"-1438109059","predicate":"decryptedMessageService","params":[{"name":"random_id","type":"long"},{"name":"random_bytes","type":"bytes"},{"name":"action","type":"DecryptedMessageAction"}],"type":"DecryptedMessage","layer":8},{"id":"1930838368","predicate":"decryptedMessageService","params":[{"name":"random_id","type":"long"},{"name":"action","type":"DecryptedMessageAction"}],"type":"DecryptedMessage","layer":17},{"id":"144661578","predicate":"decryptedMessageMediaEmpty","params":[],"type":"DecryptedMessageMedia","layer":8},{"id":"846826124","predicate":"decryptedMessageMediaPhoto","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":8},{"id":"-235238024","predicate":"decryptedMessageMediaPhoto","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"},{"name":"caption","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"1290694387","predicate":"decryptedMessageMediaVideo","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"duration","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":8},{"id":"1380598109","predicate":"decryptedMessageMediaVideo","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"duration","type":"int"},{"name":"mime_type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":17},{"id":"-1760785394","predicate":"decryptedMessageMediaVideo","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"duration","type":"int"},{"name":"mime_type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"},{"name":"caption","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"893913689","predicate":"decryptedMessageMediaGeoPoint","params":[{"name":"lat","type":"double"},{"name":"long","type":"double"}],"type":"DecryptedMessageMedia","layer":8},{"id":"1485441687","predicate":"decryptedMessageMediaContact","params":[{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"user_id","type":"int"}],"type":"DecryptedMessageMedia","layer":8},{"id":"-1586283796","predicate":"decryptedMessageActionSetMessageTTL","params":[{"name":"ttl_seconds","type":"int"}],"type":"DecryptedMessageAction","layer":8},{"id":"-1332395189","predicate":"decryptedMessageMediaDocument","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"file_name","type":"string"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":8},{"id":"2063502050","predicate":"decryptedMessageMediaDocument","params":[{"name":"thumb","type":"bytes"},{"name":"thumb_w","type":"int"},{"name":"thumb_h","type":"int"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"},{"name":"attributes","type":"Vector"},{"name":"caption","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"1619031439","predicate":"decryptedMessageMediaAudio","params":[{"name":"duration","type":"int"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":8},{"id":"1474341323","predicate":"decryptedMessageMediaAudio","params":[{"name":"duration","type":"int"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"key","type":"bytes"},{"name":"iv","type":"bytes"}],"type":"DecryptedMessageMedia","layer":17},{"id":"206520510","predicate":"decryptedMessageActionReadMessages","params":[{"name":"random_ids","type":"Vector"}],"type":"DecryptedMessageAction","layer":8},{"id":"1700872964","predicate":"decryptedMessageActionDeleteMessages","params":[{"name":"random_ids","type":"Vector"}],"type":"DecryptedMessageAction","layer":8},{"id":"-1967000459","predicate":"decryptedMessageActionScreenshotMessages","params":[{"name":"random_ids","type":"Vector"}],"type":"DecryptedMessageAction","layer":8},{"id":"1729750108","predicate":"decryptedMessageActionFlushHistory","params":[],"type":"DecryptedMessageAction","layer":8},{"id":"467867529","predicate":"decryptedMessageLayer","params":[{"name":"random_bytes","type":"bytes"},{"name":"layer","type":"int"},{"name":"in_seq_no","type":"int"},{"name":"out_seq_no","type":"int"},{"name":"message","type":"DecryptedMessage"}],"type":"DecryptedMessageLayer","layer":17},{"id":"381645902","predicate":"sendMessageTypingAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-44119819","predicate":"sendMessageCancelAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-1584933265","predicate":"sendMessageRecordVideoAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-1845219337","predicate":"sendMessageUploadVideoAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-718310409","predicate":"sendMessageRecordAudioAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-424899985","predicate":"sendMessageUploadAudioAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-1727382502","predicate":"sendMessageUploadPhotoAction","params":[],"type":"SendMessageAction","layer":17},{"id":"-1884362354","predicate":"sendMessageUploadDocumentAction","params":[],"type":"SendMessageAction","layer":17},{"id":"393186209","predicate":"sendMessageGeoLocationAction","params":[],"type":"SendMessageAction","layer":17},{"id":"1653390447","predicate":"sendMessageChooseContactAction","params":[],"type":"SendMessageAction","layer":17},{"id":"1360072880","predicate":"decryptedMessageActionResend","params":[{"name":"start_seq_no","type":"int"},{"name":"end_seq_no","type":"int"}],"type":"DecryptedMessageAction","layer":17},{"id":"-217806717","predicate":"decryptedMessageActionNotifyLayer","params":[{"name":"layer","type":"int"}],"type":"DecryptedMessageAction","layer":17},{"id":"-860719551","predicate":"decryptedMessageActionTyping","params":[{"name":"action","type":"SendMessageAction"}],"type":"DecryptedMessageAction","layer":17},{"id":"-204906213","predicate":"decryptedMessageActionRequestKey","params":[{"name":"exchange_id","type":"long"},{"name":"g_a","type":"bytes"}],"type":"DecryptedMessageAction","layer":20},{"id":"1877046107","predicate":"decryptedMessageActionAcceptKey","params":[{"name":"exchange_id","type":"long"},{"name":"g_b","type":"bytes"},{"name":"key_fingerprint","type":"long"}],"type":"DecryptedMessageAction","layer":20},{"id":"-586814357","predicate":"decryptedMessageActionAbortKey","params":[{"name":"exchange_id","type":"long"}],"type":"DecryptedMessageAction","layer":20},{"id":"-332526693","predicate":"decryptedMessageActionCommitKey","params":[{"name":"exchange_id","type":"long"},{"name":"key_fingerprint","type":"long"}],"type":"DecryptedMessageAction","layer":20},{"id":"-1473258141","predicate":"decryptedMessageActionNoop","params":[],"type":"DecryptedMessageAction","layer":20},{"id":"1815593308","predicate":"documentAttributeImageSize","params":[{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute","layer":23},{"id":"297109817","predicate":"documentAttributeAnimated","params":[],"type":"DocumentAttribute","layer":23},{"id":"-83208409","predicate":"documentAttributeSticker","params":[],"type":"DocumentAttribute","layer":23},{"id":"978674434","predicate":"documentAttributeSticker","params":[{"name":"alt","type":"string"},{"name":"stickerset","type":"InputStickerSet"}],"type":"DocumentAttribute","layer":45},{"id":"1494273227","predicate":"documentAttributeVideo","params":[{"name":"duration","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute","layer":23},{"id":"250621158","predicate":"documentAttributeVideo","params":[{"name":"flags","type":"#"},{"name":"duration","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute","layer":66},{"id":"85215461","predicate":"documentAttributeAudio","params":[{"name":"duration","type":"int"}],"type":"DocumentAttribute","layer":23},{"id":"-556656416","predicate":"documentAttributeAudio","params":[{"name":"duration","type":"int"},{"name":"title","type":"string"},{"name":"performer","type":"string"}],"type":"DocumentAttribute","layer":45},{"id":"-1739392570","predicate":"documentAttributeAudio","params":[{"name":"flags","type":"#"},{"name":"duration","type":"int"},{"name":"title","type":"flags.0?string"},{"name":"performer","type":"flags.1?string"},{"name":"waveform","type":"flags.2?bytes"}],"type":"DocumentAttribute","layer":46},{"id":"358154344","predicate":"documentAttributeFilename","params":[{"name":"file_name","type":"string"}],"type":"DocumentAttribute","layer":23},{"id":"236446268","predicate":"photoSizeEmpty","params":[{"name":"type","type":"string"}],"type":"PhotoSize","layer":23},{"id":"2009052699","predicate":"photoSize","params":[{"name":"type","type":"string"},{"name":"location","type":"FileLocation"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"}],"type":"PhotoSize","layer":23},{"id":"-374917894","predicate":"photoCachedSize","params":[{"name":"type","type":"string"},{"name":"location","type":"FileLocation"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"bytes","type":"bytes"}],"type":"PhotoSize","layer":23},{"id":"2086234950","predicate":"fileLocationUnavailable","params":[{"name":"volume_id","type":"long"},{"name":"local_id","type":"int"},{"name":"secret","type":"long"}],"type":"FileLocation","layer":23},{"id":"1406570614","predicate":"fileLocation","params":[{"name":"dc_id","type":"int"},{"name":"volume_id","type":"long"},{"name":"local_id","type":"int"},{"name":"secret","type":"long"}],"type":"FileLocation","layer":23},{"id":"-90853155","predicate":"decryptedMessageMediaExternalDocument","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"thumb","type":"PhotoSize"},{"name":"dc_id","type":"int"},{"name":"attributes","type":"Vector"}],"type":"DecryptedMessageMedia","layer":23},{"id":"-1148011883","predicate":"messageEntityUnknown","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"-100378723","predicate":"messageEntityMention","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1868782349","predicate":"messageEntityHashtag","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1827637959","predicate":"messageEntityBotCommand","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1859134776","predicate":"messageEntityUrl","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1692693954","predicate":"messageEntityEmail","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"-1117713463","predicate":"messageEntityBold","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"-2106619040","predicate":"messageEntityItalic","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"681706865","predicate":"messageEntityCode","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity","layer":45},{"id":"1938967520","predicate":"messageEntityPre","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"language","type":"string"}],"type":"MessageEntity","layer":45},{"id":"1990644519","predicate":"messageEntityTextUrl","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"url","type":"string"}],"type":"MessageEntity","layer":45},{"id":"-2044933984","predicate":"inputStickerSetShortName","params":[{"name":"short_name","type":"string"}],"type":"InputStickerSet","layer":45},{"id":"-4838507","predicate":"inputStickerSetEmpty","params":[],"type":"InputStickerSet","layer":45},{"id":"-1978796689","predicate":"decryptedMessageMediaVenue","params":[{"name":"lat","type":"double"},{"name":"long","type":"double"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"-452652584","predicate":"decryptedMessageMediaWebPage","params":[{"name":"url","type":"string"}],"type":"DecryptedMessageMedia","layer":45},{"id":"-1997373508","predicate":"sendMessageRecordRoundAction","params":[],"type":"SendMessageAction","layer":66},{"id":"-1150187996","predicate":"sendMessageUploadRoundAction","params":[],"type":"SendMessageAction","layer":66}],"methods":[]} \ No newline at end of file diff --git a/data/corefork.telegram.org/schema/end-to-end.html b/data/corefork.telegram.org/schema/end-to-end.html deleted file mode 100644 index ddaa977025..0000000000 --- a/data/corefork.telegram.org/schema/end-to-end.html +++ /dev/null @@ -1,225 +0,0 @@ - - - - - Current end-to-end TL-schema - - - - - - - - - - - - - -
- -
-
-
- -

Current end-to-end TL-schema

- -
-

Below you will find the current end-to-end TL-schema. More details on TL »

-
-

See also:
-End-to-end encryption in MTProto, Secret Chats
-Detailed schema in JSON

-
- -
-
===8===
-decryptedMessage#1f814f1f random_id:long random_bytes:bytes message:string media:DecryptedMessageMedia = DecryptedMessage;
-decryptedMessageService#aa48327d random_id:long random_bytes:bytes action:DecryptedMessageAction = DecryptedMessage;
-decryptedMessageMediaEmpty#89f5c4a = DecryptedMessageMedia;
-decryptedMessageMediaPhoto#32798a8c thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageMediaVideo#4cee6ef3 thumb:bytes thumb_w:int thumb_h:int duration:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageMediaGeoPoint#35480a59 lat:double long:double = DecryptedMessageMedia;
-decryptedMessageMediaContact#588a0a97 phone_number:string first_name:string last_name:string user_id:int = DecryptedMessageMedia;
-decryptedMessageActionSetMessageTTL#a1733aec ttl_seconds:int = DecryptedMessageAction;
-decryptedMessageMediaDocument#b095434b thumb:bytes thumb_w:int thumb_h:int file_name:string mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageMediaAudio#6080758f duration:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageActionReadMessages#c4f40be random_ids:Vector<long> = DecryptedMessageAction;
-decryptedMessageActionDeleteMessages#65614304 random_ids:Vector<long> = DecryptedMessageAction;
-decryptedMessageActionScreenshotMessages#8ac1f475 random_ids:Vector<long> = DecryptedMessageAction;
-decryptedMessageActionFlushHistory#6719e45c = DecryptedMessageAction;
-
-===17===
-decryptedMessage#204d3878 random_id:long ttl:int message:string media:DecryptedMessageMedia = DecryptedMessage;
-decryptedMessageService#73164160 random_id:long action:DecryptedMessageAction = DecryptedMessage;
-decryptedMessageMediaVideo#524a415d thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageMediaAudio#57e0a9cb duration:int mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageLayer#1be31789 random_bytes:bytes layer:int in_seq_no:int out_seq_no:int message:DecryptedMessage = DecryptedMessageLayer;
-sendMessageTypingAction#16bf744e = SendMessageAction;
-sendMessageCancelAction#fd5ec8f5 = SendMessageAction;
-sendMessageRecordVideoAction#a187d66f = SendMessageAction;
-sendMessageUploadVideoAction#92042ff7 = SendMessageAction;
-sendMessageRecordAudioAction#d52f73f7 = SendMessageAction;
-sendMessageUploadAudioAction#e6ac8a6f = SendMessageAction;
-sendMessageUploadPhotoAction#990a3c1a = SendMessageAction;
-sendMessageUploadDocumentAction#8faee98e = SendMessageAction;
-sendMessageGeoLocationAction#176f8ba1 = SendMessageAction;
-sendMessageChooseContactAction#628cbc6f = SendMessageAction;
-decryptedMessageActionResend#511110b0 start_seq_no:int end_seq_no:int = DecryptedMessageAction;
-decryptedMessageActionNotifyLayer#f3048883 layer:int = DecryptedMessageAction;
-decryptedMessageActionTyping#ccb27641 action:SendMessageAction = DecryptedMessageAction;
-
-===20===
-decryptedMessageActionRequestKey#f3c9611b exchange_id:long g_a:bytes = DecryptedMessageAction;
-decryptedMessageActionAcceptKey#6fe1735b exchange_id:long g_b:bytes key_fingerprint:long = DecryptedMessageAction;
-decryptedMessageActionAbortKey#dd05ec6b exchange_id:long = DecryptedMessageAction;
-decryptedMessageActionCommitKey#ec2e0b9b exchange_id:long key_fingerprint:long = DecryptedMessageAction;
-decryptedMessageActionNoop#a82fdd63 = DecryptedMessageAction;
-
-===23===
-documentAttributeImageSize#6c37c15c w:int h:int = DocumentAttribute;
-documentAttributeAnimated#11b58939 = DocumentAttribute;
-documentAttributeSticker#fb0a5727 = DocumentAttribute;
-documentAttributeVideo#5910cccb duration:int w:int h:int = DocumentAttribute;
-documentAttributeAudio#51448e5 duration:int = DocumentAttribute;
-documentAttributeFilename#15590068 file_name:string = DocumentAttribute;
-photoSizeEmpty#e17e23c type:string = PhotoSize;
-photoSize#77bfb61b type:string location:FileLocation w:int h:int size:int = PhotoSize;
-photoCachedSize#e9a734fa type:string location:FileLocation w:int h:int bytes:bytes = PhotoSize;
-fileLocationUnavailable#7c596b46 volume_id:long local_id:int secret:long = FileLocation;
-fileLocation#53d69076 dc_id:int volume_id:long local_id:int secret:long = FileLocation;
-decryptedMessageMediaExternalDocument#fa95b0dd id:long access_hash:long date:int mime_type:string size:int thumb:PhotoSize dc_id:int attributes:Vector<DocumentAttribute> = DecryptedMessageMedia;
-
-===45===
-decryptedMessage#36b091de flags:# random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long = DecryptedMessage;
-decryptedMessageMediaPhoto#f1fa8d78 thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;
-decryptedMessageMediaVideo#970c8c0e thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;
-decryptedMessageMediaDocument#7afe8ae2 thumb:bytes thumb_w:int thumb_h:int mime_type:string size:int key:bytes iv:bytes attributes:Vector<DocumentAttribute> caption:string = DecryptedMessageMedia;
-documentAttributeSticker#3a556302 alt:string stickerset:InputStickerSet = DocumentAttribute;
-documentAttributeAudio#ded218e0 duration:int title:string performer:string = DocumentAttribute;
-messageEntityUnknown#bb92ba95 offset:int length:int = MessageEntity;
-messageEntityMention#fa04579d offset:int length:int = MessageEntity;
-messageEntityHashtag#6f635b0d offset:int length:int = MessageEntity;
-messageEntityBotCommand#6cef8ac7 offset:int length:int = MessageEntity;
-messageEntityUrl#6ed02538 offset:int length:int = MessageEntity;
-messageEntityEmail#64e475c2 offset:int length:int = MessageEntity;
-messageEntityBold#bd610bc9 offset:int length:int = MessageEntity;
-messageEntityItalic#826f8b60 offset:int length:int = MessageEntity;
-messageEntityCode#28a20571 offset:int length:int = MessageEntity;
-messageEntityPre#73924be0 offset:int length:int language:string = MessageEntity;
-messageEntityTextUrl#76a6d327 offset:int length:int url:string = MessageEntity;
-inputStickerSetShortName#861cc8a0 short_name:string = InputStickerSet;
-inputStickerSetEmpty#ffb62b95 = InputStickerSet;
-decryptedMessageMediaVenue#8a0df56f lat:double long:double title:string address:string provider:string venue_id:string = DecryptedMessageMedia;
-decryptedMessageMediaWebPage#e50511d8 url:string = DecryptedMessageMedia;
-
-===46===
-documentAttributeAudio#9852f9c6 flags:# voice:flags.10?true duration:int title:flags.0?string performer:flags.1?string waveform:flags.2?bytes = DocumentAttribute;
-
-===66===
-documentAttributeVideo#ef02ce6 flags:# round_message:flags.0?true duration:int w:int h:int = DocumentAttribute;
-sendMessageRecordRoundAction#88f27fbc = SendMessageAction;
-sendMessageUploadRoundAction#bb718624 = SendMessageAction;
-
-===73===
-decryptedMessage#91cc4674 flags:# no_webpage:flags.1?true silent:flags.5?true random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long grouped_id:flags.17?long = DecryptedMessage;
-
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/schema/json.html b/data/corefork.telegram.org/schema/json.html deleted file mode 100644 index a6e0156ccf..0000000000 --- a/data/corefork.telegram.org/schema/json.html +++ /dev/null @@ -1 +0,0 @@ -{"constructors":[{"id":"-1132882121","predicate":"boolFalse","params":[],"type":"Bool"},{"id":"-1720552011","predicate":"boolTrue","params":[],"type":"Bool"},{"id":"1072550713","predicate":"true","params":[],"type":"True"},{"id":"481674261","predicate":"vector","params":[],"type":"Vector t"},{"id":"-994444869","predicate":"error","params":[{"name":"code","type":"int"},{"name":"text","type":"string"}],"type":"Error"},{"id":"1450380236","predicate":"null","params":[],"type":"Null"},{"id":"2134579434","predicate":"inputPeerEmpty","params":[],"type":"InputPeer"},{"id":"2107670217","predicate":"inputPeerSelf","params":[],"type":"InputPeer"},{"id":"900291769","predicate":"inputPeerChat","params":[{"name":"chat_id","type":"long"}],"type":"InputPeer"},{"id":"-1182234929","predicate":"inputUserEmpty","params":[],"type":"InputUser"},{"id":"-138301121","predicate":"inputUserSelf","params":[],"type":"InputUser"},{"id":"-208488460","predicate":"inputPhoneContact","params":[{"name":"client_id","type":"long"},{"name":"phone","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"}],"type":"InputContact"},{"id":"-181407105","predicate":"inputFile","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"name","type":"string"},{"name":"md5_checksum","type":"string"}],"type":"InputFile"},{"id":"-1771768449","predicate":"inputMediaEmpty","params":[],"type":"InputMedia"},{"id":"505969924","predicate":"inputMediaUploadedPhoto","params":[{"name":"flags","type":"#"},{"name":"file","type":"InputFile"},{"name":"stickers","type":"flags.0?Vector"},{"name":"ttl_seconds","type":"flags.1?int"}],"type":"InputMedia"},{"id":"-1279654347","predicate":"inputMediaPhoto","params":[{"name":"flags","type":"#"},{"name":"id","type":"InputPhoto"},{"name":"ttl_seconds","type":"flags.0?int"}],"type":"InputMedia"},{"id":"-104578748","predicate":"inputMediaGeoPoint","params":[{"name":"geo_point","type":"InputGeoPoint"}],"type":"InputMedia"},{"id":"-122978821","predicate":"inputMediaContact","params":[{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"vcard","type":"string"}],"type":"InputMedia"},{"id":"480546647","predicate":"inputChatPhotoEmpty","params":[],"type":"InputChatPhoto"},{"id":"-968723890","predicate":"inputChatUploadedPhoto","params":[{"name":"flags","type":"#"},{"name":"file","type":"flags.0?InputFile"},{"name":"video","type":"flags.1?InputFile"},{"name":"video_start_ts","type":"flags.2?double"}],"type":"InputChatPhoto"},{"id":"-1991004873","predicate":"inputChatPhoto","params":[{"name":"id","type":"InputPhoto"}],"type":"InputChatPhoto"},{"id":"-457104426","predicate":"inputGeoPointEmpty","params":[],"type":"InputGeoPoint"},{"id":"1210199983","predicate":"inputGeoPoint","params":[{"name":"flags","type":"#"},{"name":"lat","type":"double"},{"name":"long","type":"double"},{"name":"accuracy_radius","type":"flags.0?int"}],"type":"InputGeoPoint"},{"id":"483901197","predicate":"inputPhotoEmpty","params":[],"type":"InputPhoto"},{"id":"1001634122","predicate":"inputPhoto","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"}],"type":"InputPhoto"},{"id":"-539317279","predicate":"inputFileLocation","params":[{"name":"volume_id","type":"long"},{"name":"local_id","type":"int"},{"name":"secret","type":"long"},{"name":"file_reference","type":"bytes"}],"type":"InputFileLocation"},{"id":"1498486562","predicate":"peerUser","params":[{"name":"user_id","type":"long"}],"type":"Peer"},{"id":"918946202","predicate":"peerChat","params":[{"name":"chat_id","type":"long"}],"type":"Peer"},{"id":"-1432995067","predicate":"storage.fileUnknown","params":[],"type":"storage.FileType"},{"id":"1086091090","predicate":"storage.filePartial","params":[],"type":"storage.FileType"},{"id":"8322574","predicate":"storage.fileJpeg","params":[],"type":"storage.FileType"},{"id":"-891180321","predicate":"storage.fileGif","params":[],"type":"storage.FileType"},{"id":"172975040","predicate":"storage.filePng","params":[],"type":"storage.FileType"},{"id":"-1373745011","predicate":"storage.filePdf","params":[],"type":"storage.FileType"},{"id":"1384777335","predicate":"storage.fileMp3","params":[],"type":"storage.FileType"},{"id":"1258941372","predicate":"storage.fileMov","params":[],"type":"storage.FileType"},{"id":"-1278304028","predicate":"storage.fileMp4","params":[],"type":"storage.FileType"},{"id":"276907596","predicate":"storage.fileWebp","params":[],"type":"storage.FileType"},{"id":"-742634630","predicate":"userEmpty","params":[{"name":"id","type":"long"}],"type":"User"},{"id":"1326562017","predicate":"userProfilePhotoEmpty","params":[],"type":"UserProfilePhoto"},{"id":"-2100168954","predicate":"userProfilePhoto","params":[{"name":"flags","type":"#"},{"name":"has_video","type":"flags.0?true"},{"name":"photo_id","type":"long"},{"name":"stripped_thumb","type":"flags.1?bytes"},{"name":"dc_id","type":"int"}],"type":"UserProfilePhoto"},{"id":"164646985","predicate":"userStatusEmpty","params":[],"type":"UserStatus"},{"id":"-306628279","predicate":"userStatusOnline","params":[{"name":"expires","type":"int"}],"type":"UserStatus"},{"id":"9203775","predicate":"userStatusOffline","params":[{"name":"was_online","type":"int"}],"type":"UserStatus"},{"id":"693512293","predicate":"chatEmpty","params":[{"name":"id","type":"long"}],"type":"Chat"},{"id":"1103884886","predicate":"chat","params":[{"name":"flags","type":"#"},{"name":"creator","type":"flags.0?true"},{"name":"kicked","type":"flags.1?true"},{"name":"left","type":"flags.2?true"},{"name":"deactivated","type":"flags.5?true"},{"name":"call_active","type":"flags.23?true"},{"name":"call_not_empty","type":"flags.24?true"},{"name":"noforwards","type":"flags.25?true"},{"name":"id","type":"long"},{"name":"title","type":"string"},{"name":"photo","type":"ChatPhoto"},{"name":"participants_count","type":"int"},{"name":"date","type":"int"},{"name":"version","type":"int"},{"name":"migrated_to","type":"flags.6?InputChannel"},{"name":"admin_rights","type":"flags.14?ChatAdminRights"},{"name":"default_banned_rights","type":"flags.18?ChatBannedRights"}],"type":"Chat"},{"id":"1704108455","predicate":"chatForbidden","params":[{"name":"id","type":"long"},{"name":"title","type":"string"}],"type":"Chat"},{"id":"1304281241","predicate":"chatFull","params":[{"name":"flags","type":"#"},{"name":"can_set_username","type":"flags.7?true"},{"name":"has_scheduled","type":"flags.8?true"},{"name":"id","type":"long"},{"name":"about","type":"string"},{"name":"participants","type":"ChatParticipants"},{"name":"chat_photo","type":"flags.2?Photo"},{"name":"notify_settings","type":"PeerNotifySettings"},{"name":"exported_invite","type":"flags.13?ExportedChatInvite"},{"name":"bot_info","type":"flags.3?Vector"},{"name":"pinned_msg_id","type":"flags.6?int"},{"name":"folder_id","type":"flags.11?int"},{"name":"call","type":"flags.12?InputGroupCall"},{"name":"ttl_period","type":"flags.14?int"},{"name":"groupcall_default_join_as","type":"flags.15?Peer"},{"name":"theme_emoticon","type":"flags.16?string"}],"type":"ChatFull"},{"id":"-1070776313","predicate":"chatParticipant","params":[{"name":"user_id","type":"long"},{"name":"inviter_id","type":"long"},{"name":"date","type":"int"}],"type":"ChatParticipant"},{"id":"-2023500831","predicate":"chatParticipantsForbidden","params":[{"name":"flags","type":"#"},{"name":"chat_id","type":"long"},{"name":"self_participant","type":"flags.0?ChatParticipant"}],"type":"ChatParticipants"},{"id":"1018991608","predicate":"chatParticipants","params":[{"name":"chat_id","type":"long"},{"name":"participants","type":"Vector"},{"name":"version","type":"int"}],"type":"ChatParticipants"},{"id":"935395612","predicate":"chatPhotoEmpty","params":[],"type":"ChatPhoto"},{"id":"476978193","predicate":"chatPhoto","params":[{"name":"flags","type":"#"},{"name":"has_video","type":"flags.0?true"},{"name":"photo_id","type":"long"},{"name":"stripped_thumb","type":"flags.1?bytes"},{"name":"dc_id","type":"int"}],"type":"ChatPhoto"},{"id":"-1868117372","predicate":"messageEmpty","params":[{"name":"flags","type":"#"},{"name":"id","type":"int"},{"name":"peer_id","type":"flags.0?Peer"}],"type":"Message"},{"id":"-2049520670","predicate":"message","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"mentioned","type":"flags.4?true"},{"name":"media_unread","type":"flags.5?true"},{"name":"silent","type":"flags.13?true"},{"name":"post","type":"flags.14?true"},{"name":"from_scheduled","type":"flags.18?true"},{"name":"legacy","type":"flags.19?true"},{"name":"edit_hide","type":"flags.21?true"},{"name":"pinned","type":"flags.24?true"},{"name":"noforwards","type":"flags.26?true"},{"name":"id","type":"int"},{"name":"from_id","type":"flags.8?Peer"},{"name":"peer_id","type":"Peer"},{"name":"fwd_from","type":"flags.2?MessageFwdHeader"},{"name":"via_bot_id","type":"flags.11?long"},{"name":"reply_to","type":"flags.3?MessageReplyHeader"},{"name":"date","type":"int"},{"name":"message","type":"string"},{"name":"media","type":"flags.9?MessageMedia"},{"name":"reply_markup","type":"flags.6?ReplyMarkup"},{"name":"entities","type":"flags.7?Vector"},{"name":"views","type":"flags.10?int"},{"name":"forwards","type":"flags.10?int"},{"name":"replies","type":"flags.23?MessageReplies"},{"name":"edit_date","type":"flags.15?int"},{"name":"post_author","type":"flags.16?string"},{"name":"grouped_id","type":"flags.17?long"},{"name":"restriction_reason","type":"flags.22?Vector"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Message"},{"id":"721967202","predicate":"messageService","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"mentioned","type":"flags.4?true"},{"name":"media_unread","type":"flags.5?true"},{"name":"silent","type":"flags.13?true"},{"name":"post","type":"flags.14?true"},{"name":"legacy","type":"flags.19?true"},{"name":"id","type":"int"},{"name":"from_id","type":"flags.8?Peer"},{"name":"peer_id","type":"Peer"},{"name":"reply_to","type":"flags.3?MessageReplyHeader"},{"name":"date","type":"int"},{"name":"action","type":"MessageAction"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Message"},{"id":"1038967584","predicate":"messageMediaEmpty","params":[],"type":"MessageMedia"},{"id":"1766936791","predicate":"messageMediaPhoto","params":[{"name":"flags","type":"#"},{"name":"photo","type":"flags.0?Photo"},{"name":"ttl_seconds","type":"flags.2?int"}],"type":"MessageMedia"},{"id":"1457575028","predicate":"messageMediaGeo","params":[{"name":"geo","type":"GeoPoint"}],"type":"MessageMedia"},{"id":"1882335561","predicate":"messageMediaContact","params":[{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"vcard","type":"string"},{"name":"user_id","type":"long"}],"type":"MessageMedia"},{"id":"-1618676578","predicate":"messageMediaUnsupported","params":[],"type":"MessageMedia"},{"id":"-1230047312","predicate":"messageActionEmpty","params":[],"type":"MessageAction"},{"id":"-1119368275","predicate":"messageActionChatCreate","params":[{"name":"title","type":"string"},{"name":"users","type":"Vector"}],"type":"MessageAction"},{"id":"-1247687078","predicate":"messageActionChatEditTitle","params":[{"name":"title","type":"string"}],"type":"MessageAction"},{"id":"2144015272","predicate":"messageActionChatEditPhoto","params":[{"name":"photo","type":"Photo"}],"type":"MessageAction"},{"id":"-1780220945","predicate":"messageActionChatDeletePhoto","params":[],"type":"MessageAction"},{"id":"365886720","predicate":"messageActionChatAddUser","params":[{"name":"users","type":"Vector"}],"type":"MessageAction"},{"id":"-1539362612","predicate":"messageActionChatDeleteUser","params":[{"name":"user_id","type":"long"}],"type":"MessageAction"},{"id":"739712882","predicate":"dialog","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.2?true"},{"name":"unread_mark","type":"flags.3?true"},{"name":"peer","type":"Peer"},{"name":"top_message","type":"int"},{"name":"read_inbox_max_id","type":"int"},{"name":"read_outbox_max_id","type":"int"},{"name":"unread_count","type":"int"},{"name":"unread_mentions_count","type":"int"},{"name":"notify_settings","type":"PeerNotifySettings"},{"name":"pts","type":"flags.0?int"},{"name":"draft","type":"flags.1?DraftMessage"},{"name":"folder_id","type":"flags.4?int"}],"type":"Dialog"},{"id":"590459437","predicate":"photoEmpty","params":[{"name":"id","type":"long"}],"type":"Photo"},{"id":"-82216347","predicate":"photo","params":[{"name":"flags","type":"#"},{"name":"has_stickers","type":"flags.0?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"date","type":"int"},{"name":"sizes","type":"Vector"},{"name":"video_sizes","type":"flags.1?Vector"},{"name":"dc_id","type":"int"}],"type":"Photo"},{"id":"236446268","predicate":"photoSizeEmpty","params":[{"name":"type","type":"string"}],"type":"PhotoSize"},{"id":"1976012384","predicate":"photoSize","params":[{"name":"type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"}],"type":"PhotoSize"},{"id":"35527382","predicate":"photoCachedSize","params":[{"name":"type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"bytes","type":"bytes"}],"type":"PhotoSize"},{"id":"286776671","predicate":"geoPointEmpty","params":[],"type":"GeoPoint"},{"id":"-1297942941","predicate":"geoPoint","params":[{"name":"flags","type":"#"},{"name":"long","type":"double"},{"name":"lat","type":"double"},{"name":"access_hash","type":"long"},{"name":"accuracy_radius","type":"flags.0?int"}],"type":"GeoPoint"},{"id":"1577067778","predicate":"auth.sentCode","params":[{"name":"flags","type":"#"},{"name":"type","type":"auth.SentCodeType"},{"name":"phone_code_hash","type":"string"},{"name":"next_type","type":"flags.1?auth.CodeType"},{"name":"timeout","type":"flags.2?int"}],"type":"auth.SentCode"},{"id":"-855308010","predicate":"auth.authorization","params":[{"name":"flags","type":"#"},{"name":"tmp_sessions","type":"flags.0?int"},{"name":"user","type":"User"}],"type":"auth.Authorization"},{"id":"-1271602504","predicate":"auth.exportedAuthorization","params":[{"name":"id","type":"long"},{"name":"bytes","type":"bytes"}],"type":"auth.ExportedAuthorization"},{"id":"-1195615476","predicate":"inputNotifyPeer","params":[{"name":"peer","type":"InputPeer"}],"type":"InputNotifyPeer"},{"id":"423314455","predicate":"inputNotifyUsers","params":[],"type":"InputNotifyPeer"},{"id":"1251338318","predicate":"inputNotifyChats","params":[],"type":"InputNotifyPeer"},{"id":"-1673717362","predicate":"inputPeerNotifySettings","params":[{"name":"flags","type":"#"},{"name":"show_previews","type":"flags.0?Bool"},{"name":"silent","type":"flags.1?Bool"},{"name":"mute_until","type":"flags.2?int"},{"name":"sound","type":"flags.3?string"}],"type":"InputPeerNotifySettings"},{"id":"-1353671392","predicate":"peerNotifySettings","params":[{"name":"flags","type":"#"},{"name":"show_previews","type":"flags.0?Bool"},{"name":"silent","type":"flags.1?Bool"},{"name":"mute_until","type":"flags.2?int"},{"name":"sound","type":"flags.3?string"}],"type":"PeerNotifySettings"},{"id":"1933519201","predicate":"peerSettings","params":[{"name":"flags","type":"#"},{"name":"report_spam","type":"flags.0?true"},{"name":"add_contact","type":"flags.1?true"},{"name":"block_contact","type":"flags.2?true"},{"name":"share_contact","type":"flags.3?true"},{"name":"need_contacts_exception","type":"flags.4?true"},{"name":"report_geo","type":"flags.5?true"},{"name":"autoarchived","type":"flags.7?true"},{"name":"invite_members","type":"flags.8?true"},{"name":"geo_distance","type":"flags.6?int"}],"type":"PeerSettings"},{"id":"-1539849235","predicate":"wallPaper","params":[{"name":"id","type":"long"},{"name":"flags","type":"#"},{"name":"creator","type":"flags.0?true"},{"name":"default","type":"flags.1?true"},{"name":"pattern","type":"flags.3?true"},{"name":"dark","type":"flags.4?true"},{"name":"access_hash","type":"long"},{"name":"slug","type":"string"},{"name":"document","type":"Document"},{"name":"settings","type":"flags.2?WallPaperSettings"}],"type":"WallPaper"},{"id":"1490799288","predicate":"inputReportReasonSpam","params":[],"type":"ReportReason"},{"id":"505595789","predicate":"inputReportReasonViolence","params":[],"type":"ReportReason"},{"id":"777640226","predicate":"inputReportReasonPornography","params":[],"type":"ReportReason"},{"id":"-1376497949","predicate":"inputReportReasonChildAbuse","params":[],"type":"ReportReason"},{"id":"-1041980751","predicate":"inputReportReasonOther","params":[],"type":"ReportReason"},{"id":"-694681851","predicate":"userFull","params":[{"name":"flags","type":"#"},{"name":"blocked","type":"flags.0?true"},{"name":"phone_calls_available","type":"flags.4?true"},{"name":"phone_calls_private","type":"flags.5?true"},{"name":"can_pin_message","type":"flags.7?true"},{"name":"has_scheduled","type":"flags.12?true"},{"name":"video_calls_available","type":"flags.13?true"},{"name":"user","type":"User"},{"name":"about","type":"flags.1?string"},{"name":"settings","type":"PeerSettings"},{"name":"profile_photo","type":"flags.2?Photo"},{"name":"notify_settings","type":"PeerNotifySettings"},{"name":"bot_info","type":"flags.3?BotInfo"},{"name":"pinned_msg_id","type":"flags.6?int"},{"name":"common_chats_count","type":"int"},{"name":"folder_id","type":"flags.11?int"},{"name":"ttl_period","type":"flags.14?int"},{"name":"theme_emoticon","type":"flags.15?string"}],"type":"UserFull"},{"id":"341499403","predicate":"contact","params":[{"name":"user_id","type":"long"},{"name":"mutual","type":"Bool"}],"type":"Contact"},{"id":"-1052885936","predicate":"importedContact","params":[{"name":"user_id","type":"long"},{"name":"client_id","type":"long"}],"type":"ImportedContact"},{"id":"383348795","predicate":"contactStatus","params":[{"name":"user_id","type":"long"},{"name":"status","type":"UserStatus"}],"type":"ContactStatus"},{"id":"-1219778094","predicate":"contacts.contactsNotModified","params":[],"type":"contacts.Contacts"},{"id":"-353862078","predicate":"contacts.contacts","params":[{"name":"contacts","type":"Vector"},{"name":"saved_count","type":"int"},{"name":"users","type":"Vector"}],"type":"contacts.Contacts"},{"id":"2010127419","predicate":"contacts.importedContacts","params":[{"name":"imported","type":"Vector"},{"name":"popular_invites","type":"Vector"},{"name":"retry_contacts","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.ImportedContacts"},{"id":"182326673","predicate":"contacts.blocked","params":[{"name":"blocked","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.Blocked"},{"id":"-513392236","predicate":"contacts.blockedSlice","params":[{"name":"count","type":"int"},{"name":"blocked","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.Blocked"},{"id":"364538944","predicate":"messages.dialogs","params":[{"name":"dialogs","type":"Vector"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Dialogs"},{"id":"1910543603","predicate":"messages.dialogsSlice","params":[{"name":"count","type":"int"},{"name":"dialogs","type":"Vector"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Dialogs"},{"id":"-1938715001","predicate":"messages.messages","params":[{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Messages"},{"id":"978610270","predicate":"messages.messagesSlice","params":[{"name":"flags","type":"#"},{"name":"inexact","type":"flags.1?true"},{"name":"count","type":"int"},{"name":"next_rate","type":"flags.0?int"},{"name":"offset_id_offset","type":"flags.2?int"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Messages"},{"id":"1694474197","predicate":"messages.chats","params":[{"name":"chats","type":"Vector"}],"type":"messages.Chats"},{"id":"-438840932","predicate":"messages.chatFull","params":[{"name":"full_chat","type":"ChatFull"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.ChatFull"},{"id":"-1269012015","predicate":"messages.affectedHistory","params":[{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"offset","type":"int"}],"type":"messages.AffectedHistory"},{"id":"1474492012","predicate":"inputMessagesFilterEmpty","params":[],"type":"MessagesFilter"},{"id":"-1777752804","predicate":"inputMessagesFilterPhotos","params":[],"type":"MessagesFilter"},{"id":"-1614803355","predicate":"inputMessagesFilterVideo","params":[],"type":"MessagesFilter"},{"id":"1458172132","predicate":"inputMessagesFilterPhotoVideo","params":[],"type":"MessagesFilter"},{"id":"-1629621880","predicate":"inputMessagesFilterDocument","params":[],"type":"MessagesFilter"},{"id":"2129714567","predicate":"inputMessagesFilterUrl","params":[],"type":"MessagesFilter"},{"id":"-3644025","predicate":"inputMessagesFilterGif","params":[],"type":"MessagesFilter"},{"id":"522914557","predicate":"updateNewMessage","params":[{"name":"message","type":"Message"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"1318109142","predicate":"updateMessageID","params":[{"name":"id","type":"int"},{"name":"random_id","type":"long"}],"type":"Update"},{"id":"-1576161051","predicate":"updateDeleteMessages","params":[{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1071741569","predicate":"updateUserTyping","params":[{"name":"user_id","type":"long"},{"name":"action","type":"SendMessageAction"}],"type":"Update"},{"id":"-2092401936","predicate":"updateChatUserTyping","params":[{"name":"chat_id","type":"long"},{"name":"from_id","type":"Peer"},{"name":"action","type":"SendMessageAction"}],"type":"Update"},{"id":"125178264","predicate":"updateChatParticipants","params":[{"name":"participants","type":"ChatParticipants"}],"type":"Update"},{"id":"-440534818","predicate":"updateUserStatus","params":[{"name":"user_id","type":"long"},{"name":"status","type":"UserStatus"}],"type":"Update"},{"id":"-1007549728","predicate":"updateUserName","params":[{"name":"user_id","type":"long"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"username","type":"string"}],"type":"Update"},{"id":"-232290676","predicate":"updateUserPhoto","params":[{"name":"user_id","type":"long"},{"name":"date","type":"int"},{"name":"photo","type":"UserProfilePhoto"},{"name":"previous","type":"Bool"}],"type":"Update"},{"id":"-1519637954","predicate":"updates.state","params":[{"name":"pts","type":"int"},{"name":"qts","type":"int"},{"name":"date","type":"int"},{"name":"seq","type":"int"},{"name":"unread_count","type":"int"}],"type":"updates.State"},{"id":"1567990072","predicate":"updates.differenceEmpty","params":[{"name":"date","type":"int"},{"name":"seq","type":"int"}],"type":"updates.Difference"},{"id":"16030880","predicate":"updates.difference","params":[{"name":"new_messages","type":"Vector"},{"name":"new_encrypted_messages","type":"Vector"},{"name":"other_updates","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"state","type":"updates.State"}],"type":"updates.Difference"},{"id":"-1459938943","predicate":"updates.differenceSlice","params":[{"name":"new_messages","type":"Vector"},{"name":"new_encrypted_messages","type":"Vector"},{"name":"other_updates","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"intermediate_state","type":"updates.State"}],"type":"updates.Difference"},{"id":"-484987010","predicate":"updatesTooLong","params":[],"type":"Updates"},{"id":"826001400","predicate":"updateShortMessage","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"mentioned","type":"flags.4?true"},{"name":"media_unread","type":"flags.5?true"},{"name":"silent","type":"flags.13?true"},{"name":"id","type":"int"},{"name":"user_id","type":"long"},{"name":"message","type":"string"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"date","type":"int"},{"name":"fwd_from","type":"flags.2?MessageFwdHeader"},{"name":"via_bot_id","type":"flags.11?long"},{"name":"reply_to","type":"flags.3?MessageReplyHeader"},{"name":"entities","type":"flags.7?Vector"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Updates"},{"id":"1299050149","predicate":"updateShortChatMessage","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"mentioned","type":"flags.4?true"},{"name":"media_unread","type":"flags.5?true"},{"name":"silent","type":"flags.13?true"},{"name":"id","type":"int"},{"name":"from_id","type":"long"},{"name":"chat_id","type":"long"},{"name":"message","type":"string"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"date","type":"int"},{"name":"fwd_from","type":"flags.2?MessageFwdHeader"},{"name":"via_bot_id","type":"flags.11?long"},{"name":"reply_to","type":"flags.3?MessageReplyHeader"},{"name":"entities","type":"flags.7?Vector"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Updates"},{"id":"2027216577","predicate":"updateShort","params":[{"name":"update","type":"Update"},{"name":"date","type":"int"}],"type":"Updates"},{"id":"1918567619","predicate":"updatesCombined","params":[{"name":"updates","type":"Vector"},{"name":"users","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"date","type":"int"},{"name":"seq_start","type":"int"},{"name":"seq","type":"int"}],"type":"Updates"},{"id":"1957577280","predicate":"updates","params":[{"name":"updates","type":"Vector"},{"name":"users","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"date","type":"int"},{"name":"seq","type":"int"}],"type":"Updates"},{"id":"-1916114267","predicate":"photos.photos","params":[{"name":"photos","type":"Vector"},{"name":"users","type":"Vector"}],"type":"photos.Photos"},{"id":"352657236","predicate":"photos.photosSlice","params":[{"name":"count","type":"int"},{"name":"photos","type":"Vector"},{"name":"users","type":"Vector"}],"type":"photos.Photos"},{"id":"539045032","predicate":"photos.photo","params":[{"name":"photo","type":"Photo"},{"name":"users","type":"Vector"}],"type":"photos.Photo"},{"id":"157948117","predicate":"upload.file","params":[{"name":"type","type":"storage.FileType"},{"name":"mtime","type":"int"},{"name":"bytes","type":"bytes"}],"type":"upload.File"},{"id":"414687501","predicate":"dcOption","params":[{"name":"flags","type":"#"},{"name":"ipv6","type":"flags.0?true"},{"name":"media_only","type":"flags.1?true"},{"name":"tcpo_only","type":"flags.2?true"},{"name":"cdn","type":"flags.3?true"},{"name":"static","type":"flags.4?true"},{"name":"id","type":"int"},{"name":"ip_address","type":"string"},{"name":"port","type":"int"},{"name":"secret","type":"flags.10?bytes"}],"type":"DcOption"},{"id":"856375399","predicate":"config","params":[{"name":"flags","type":"#"},{"name":"phonecalls_enabled","type":"flags.1?true"},{"name":"default_p2p_contacts","type":"flags.3?true"},{"name":"preload_featured_stickers","type":"flags.4?true"},{"name":"ignore_phone_entities","type":"flags.5?true"},{"name":"revoke_pm_inbox","type":"flags.6?true"},{"name":"blocked_mode","type":"flags.8?true"},{"name":"pfs_enabled","type":"flags.13?true"},{"name":"date","type":"int"},{"name":"expires","type":"int"},{"name":"test_mode","type":"Bool"},{"name":"this_dc","type":"int"},{"name":"dc_options","type":"Vector"},{"name":"dc_txt_domain_name","type":"string"},{"name":"chat_size_max","type":"int"},{"name":"megagroup_size_max","type":"int"},{"name":"forwarded_count_max","type":"int"},{"name":"online_update_period_ms","type":"int"},{"name":"offline_blur_timeout_ms","type":"int"},{"name":"offline_idle_timeout_ms","type":"int"},{"name":"online_cloud_timeout_ms","type":"int"},{"name":"notify_cloud_delay_ms","type":"int"},{"name":"notify_default_delay_ms","type":"int"},{"name":"push_chat_period_ms","type":"int"},{"name":"push_chat_limit","type":"int"},{"name":"saved_gifs_limit","type":"int"},{"name":"edit_time_limit","type":"int"},{"name":"revoke_time_limit","type":"int"},{"name":"revoke_pm_time_limit","type":"int"},{"name":"rating_e_decay","type":"int"},{"name":"stickers_recent_limit","type":"int"},{"name":"stickers_faved_limit","type":"int"},{"name":"channels_read_media_period","type":"int"},{"name":"tmp_sessions","type":"flags.0?int"},{"name":"pinned_dialogs_count_max","type":"int"},{"name":"pinned_infolder_count_max","type":"int"},{"name":"call_receive_timeout_ms","type":"int"},{"name":"call_ring_timeout_ms","type":"int"},{"name":"call_connect_timeout_ms","type":"int"},{"name":"call_packet_timeout_ms","type":"int"},{"name":"me_url_prefix","type":"string"},{"name":"autoupdate_url_prefix","type":"flags.7?string"},{"name":"gif_search_username","type":"flags.9?string"},{"name":"venue_search_username","type":"flags.10?string"},{"name":"img_search_username","type":"flags.11?string"},{"name":"static_maps_provider","type":"flags.12?string"},{"name":"caption_length_max","type":"int"},{"name":"message_length_max","type":"int"},{"name":"webfile_dc_id","type":"int"},{"name":"suggested_lang_code","type":"flags.2?string"},{"name":"lang_pack_version","type":"flags.2?int"},{"name":"base_lang_pack_version","type":"flags.2?int"}],"type":"Config"},{"id":"-1910892683","predicate":"nearestDc","params":[{"name":"country","type":"string"},{"name":"this_dc","type":"int"},{"name":"nearest_dc","type":"int"}],"type":"NearestDc"},{"id":"-860107216","predicate":"help.appUpdate","params":[{"name":"flags","type":"#"},{"name":"can_not_skip","type":"flags.0?true"},{"name":"id","type":"int"},{"name":"version","type":"string"},{"name":"text","type":"string"},{"name":"entities","type":"Vector"},{"name":"document","type":"flags.1?Document"},{"name":"url","type":"flags.2?string"},{"name":"sticker","type":"flags.3?Document"}],"type":"help.AppUpdate"},{"id":"-1000708810","predicate":"help.noAppUpdate","params":[],"type":"help.AppUpdate"},{"id":"415997816","predicate":"help.inviteText","params":[{"name":"message","type":"string"}],"type":"help.InviteText"},{"id":"314359194","predicate":"updateNewEncryptedMessage","params":[{"name":"message","type":"EncryptedMessage"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"386986326","predicate":"updateEncryptedChatTyping","params":[{"name":"chat_id","type":"int"}],"type":"Update"},{"id":"-1264392051","predicate":"updateEncryption","params":[{"name":"chat","type":"EncryptedChat"},{"name":"date","type":"int"}],"type":"Update"},{"id":"956179895","predicate":"updateEncryptedMessagesRead","params":[{"name":"chat_id","type":"int"},{"name":"max_date","type":"int"},{"name":"date","type":"int"}],"type":"Update"},{"id":"-1417756512","predicate":"encryptedChatEmpty","params":[{"name":"id","type":"int"}],"type":"EncryptedChat"},{"id":"1722964307","predicate":"encryptedChatWaiting","params":[{"name":"id","type":"int"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"}],"type":"EncryptedChat"},{"id":"1223809356","predicate":"encryptedChatRequested","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.0?int"},{"name":"id","type":"int"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_a","type":"bytes"}],"type":"EncryptedChat"},{"id":"1643173063","predicate":"encryptedChat","params":[{"name":"id","type":"int"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_a_or_b","type":"bytes"},{"name":"key_fingerprint","type":"long"}],"type":"EncryptedChat"},{"id":"505183301","predicate":"encryptedChatDiscarded","params":[{"name":"flags","type":"#"},{"name":"history_deleted","type":"flags.0?true"},{"name":"id","type":"int"}],"type":"EncryptedChat"},{"id":"-247351839","predicate":"inputEncryptedChat","params":[{"name":"chat_id","type":"int"},{"name":"access_hash","type":"long"}],"type":"InputEncryptedChat"},{"id":"-1038136962","predicate":"encryptedFileEmpty","params":[],"type":"EncryptedFile"},{"id":"1248893260","predicate":"encryptedFile","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"size","type":"int"},{"name":"dc_id","type":"int"},{"name":"key_fingerprint","type":"int"}],"type":"EncryptedFile"},{"id":"406307684","predicate":"inputEncryptedFileEmpty","params":[],"type":"InputEncryptedFile"},{"id":"1690108678","predicate":"inputEncryptedFileUploaded","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"md5_checksum","type":"string"},{"name":"key_fingerprint","type":"int"}],"type":"InputEncryptedFile"},{"id":"1511503333","predicate":"inputEncryptedFile","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputEncryptedFile"},{"id":"-182231723","predicate":"inputEncryptedFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputFileLocation"},{"id":"-317144808","predicate":"encryptedMessage","params":[{"name":"random_id","type":"long"},{"name":"chat_id","type":"int"},{"name":"date","type":"int"},{"name":"bytes","type":"bytes"},{"name":"file","type":"EncryptedFile"}],"type":"EncryptedMessage"},{"id":"594758406","predicate":"encryptedMessageService","params":[{"name":"random_id","type":"long"},{"name":"chat_id","type":"int"},{"name":"date","type":"int"},{"name":"bytes","type":"bytes"}],"type":"EncryptedMessage"},{"id":"-1058912715","predicate":"messages.dhConfigNotModified","params":[{"name":"random","type":"bytes"}],"type":"messages.DhConfig"},{"id":"740433629","predicate":"messages.dhConfig","params":[{"name":"g","type":"int"},{"name":"p","type":"bytes"},{"name":"version","type":"int"},{"name":"random","type":"bytes"}],"type":"messages.DhConfig"},{"id":"1443858741","predicate":"messages.sentEncryptedMessage","params":[{"name":"date","type":"int"}],"type":"messages.SentEncryptedMessage"},{"id":"-1802240206","predicate":"messages.sentEncryptedFile","params":[{"name":"date","type":"int"},{"name":"file","type":"EncryptedFile"}],"type":"messages.SentEncryptedMessage"},{"id":"-95482955","predicate":"inputFileBig","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"name","type":"string"}],"type":"InputFile"},{"id":"767652808","predicate":"inputEncryptedFileBigUploaded","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"key_fingerprint","type":"int"}],"type":"InputEncryptedFile"},{"id":"1037718609","predicate":"updateChatParticipantAdd","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"long"},{"name":"inviter_id","type":"long"},{"name":"date","type":"int"},{"name":"version","type":"int"}],"type":"Update"},{"id":"-483443337","predicate":"updateChatParticipantDelete","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"long"},{"name":"version","type":"int"}],"type":"Update"},{"id":"-1906403213","predicate":"updateDcOptions","params":[{"name":"dc_options","type":"Vector"}],"type":"Update"},{"id":"1530447553","predicate":"inputMediaUploadedDocument","params":[{"name":"flags","type":"#"},{"name":"nosound_video","type":"flags.3?true"},{"name":"force_file","type":"flags.4?true"},{"name":"file","type":"InputFile"},{"name":"thumb","type":"flags.2?InputFile"},{"name":"mime_type","type":"string"},{"name":"attributes","type":"Vector"},{"name":"stickers","type":"flags.0?Vector"},{"name":"ttl_seconds","type":"flags.1?int"}],"type":"InputMedia"},{"id":"860303448","predicate":"inputMediaDocument","params":[{"name":"flags","type":"#"},{"name":"id","type":"InputDocument"},{"name":"ttl_seconds","type":"flags.0?int"},{"name":"query","type":"flags.1?string"}],"type":"InputMedia"},{"id":"-1666158377","predicate":"messageMediaDocument","params":[{"name":"flags","type":"#"},{"name":"document","type":"flags.0?Document"},{"name":"ttl_seconds","type":"flags.2?int"}],"type":"MessageMedia"},{"id":"1928391342","predicate":"inputDocumentEmpty","params":[],"type":"InputDocument"},{"id":"448771445","predicate":"inputDocument","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"}],"type":"InputDocument"},{"id":"-1160743548","predicate":"inputDocumentFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"thumb_size","type":"string"}],"type":"InputFileLocation"},{"id":"922273905","predicate":"documentEmpty","params":[{"name":"id","type":"long"}],"type":"Document"},{"id":"512177195","predicate":"document","params":[{"name":"flags","type":"#"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"date","type":"int"},{"name":"mime_type","type":"string"},{"name":"size","type":"int"},{"name":"thumbs","type":"flags.0?Vector"},{"name":"video_thumbs","type":"flags.1?Vector"},{"name":"dc_id","type":"int"},{"name":"attributes","type":"Vector"}],"type":"Document"},{"id":"398898678","predicate":"help.support","params":[{"name":"phone_number","type":"string"},{"name":"user","type":"User"}],"type":"help.Support"},{"id":"-1613493288","predicate":"notifyPeer","params":[{"name":"peer","type":"Peer"}],"type":"NotifyPeer"},{"id":"-1261946036","predicate":"notifyUsers","params":[],"type":"NotifyPeer"},{"id":"-1073230141","predicate":"notifyChats","params":[],"type":"NotifyPeer"},{"id":"-1094555409","predicate":"updateNotifySettings","params":[{"name":"peer","type":"NotifyPeer"},{"name":"notify_settings","type":"PeerNotifySettings"}],"type":"Update"},{"id":"381645902","predicate":"sendMessageTypingAction","params":[],"type":"SendMessageAction"},{"id":"-44119819","predicate":"sendMessageCancelAction","params":[],"type":"SendMessageAction"},{"id":"-1584933265","predicate":"sendMessageRecordVideoAction","params":[],"type":"SendMessageAction"},{"id":"-378127636","predicate":"sendMessageUploadVideoAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"-718310409","predicate":"sendMessageRecordAudioAction","params":[],"type":"SendMessageAction"},{"id":"-212740181","predicate":"sendMessageUploadAudioAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"-774682074","predicate":"sendMessageUploadPhotoAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"-1441998364","predicate":"sendMessageUploadDocumentAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"393186209","predicate":"sendMessageGeoLocationAction","params":[],"type":"SendMessageAction"},{"id":"1653390447","predicate":"sendMessageChooseContactAction","params":[],"type":"SendMessageAction"},{"id":"-1290580579","predicate":"contacts.found","params":[{"name":"my_results","type":"Vector"},{"name":"results","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.Found"},{"id":"-337352679","predicate":"updateServiceNotification","params":[{"name":"flags","type":"#"},{"name":"popup","type":"flags.0?true"},{"name":"inbox_date","type":"flags.1?int"},{"name":"type","type":"string"},{"name":"message","type":"string"},{"name":"media","type":"MessageMedia"},{"name":"entities","type":"Vector"}],"type":"Update"},{"id":"-496024847","predicate":"userStatusRecently","params":[],"type":"UserStatus"},{"id":"129960444","predicate":"userStatusLastWeek","params":[],"type":"UserStatus"},{"id":"2011940674","predicate":"userStatusLastMonth","params":[],"type":"UserStatus"},{"id":"-298113238","predicate":"updatePrivacy","params":[{"name":"key","type":"PrivacyKey"},{"name":"rules","type":"Vector"}],"type":"Update"},{"id":"1335282456","predicate":"inputPrivacyKeyStatusTimestamp","params":[],"type":"InputPrivacyKey"},{"id":"-1137792208","predicate":"privacyKeyStatusTimestamp","params":[],"type":"PrivacyKey"},{"id":"218751099","predicate":"inputPrivacyValueAllowContacts","params":[],"type":"InputPrivacyRule"},{"id":"407582158","predicate":"inputPrivacyValueAllowAll","params":[],"type":"InputPrivacyRule"},{"id":"320652927","predicate":"inputPrivacyValueAllowUsers","params":[{"name":"users","type":"Vector"}],"type":"InputPrivacyRule"},{"id":"195371015","predicate":"inputPrivacyValueDisallowContacts","params":[],"type":"InputPrivacyRule"},{"id":"-697604407","predicate":"inputPrivacyValueDisallowAll","params":[],"type":"InputPrivacyRule"},{"id":"-1877932953","predicate":"inputPrivacyValueDisallowUsers","params":[{"name":"users","type":"Vector"}],"type":"InputPrivacyRule"},{"id":"-123988","predicate":"privacyValueAllowContacts","params":[],"type":"PrivacyRule"},{"id":"1698855810","predicate":"privacyValueAllowAll","params":[],"type":"PrivacyRule"},{"id":"-1198497870","predicate":"privacyValueAllowUsers","params":[{"name":"users","type":"Vector"}],"type":"PrivacyRule"},{"id":"-125240806","predicate":"privacyValueDisallowContacts","params":[],"type":"PrivacyRule"},{"id":"-1955338397","predicate":"privacyValueDisallowAll","params":[],"type":"PrivacyRule"},{"id":"-463335103","predicate":"privacyValueDisallowUsers","params":[{"name":"users","type":"Vector"}],"type":"PrivacyRule"},{"id":"1352683077","predicate":"account.privacyRules","params":[{"name":"rules","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"account.PrivacyRules"},{"id":"-1194283041","predicate":"accountDaysTTL","params":[{"name":"days","type":"int"}],"type":"AccountDaysTTL"},{"id":"88680979","predicate":"updateUserPhone","params":[{"name":"user_id","type":"long"},{"name":"phone","type":"string"}],"type":"Update"},{"id":"1815593308","predicate":"documentAttributeImageSize","params":[{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute"},{"id":"297109817","predicate":"documentAttributeAnimated","params":[],"type":"DocumentAttribute"},{"id":"1662637586","predicate":"documentAttributeSticker","params":[{"name":"flags","type":"#"},{"name":"mask","type":"flags.1?true"},{"name":"alt","type":"string"},{"name":"stickerset","type":"InputStickerSet"},{"name":"mask_coords","type":"flags.0?MaskCoords"}],"type":"DocumentAttribute"},{"id":"250621158","predicate":"documentAttributeVideo","params":[{"name":"flags","type":"#"},{"name":"round_message","type":"flags.0?true"},{"name":"supports_streaming","type":"flags.1?true"},{"name":"duration","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"DocumentAttribute"},{"id":"-1739392570","predicate":"documentAttributeAudio","params":[{"name":"flags","type":"#"},{"name":"voice","type":"flags.10?true"},{"name":"duration","type":"int"},{"name":"title","type":"flags.0?string"},{"name":"performer","type":"flags.1?string"},{"name":"waveform","type":"flags.2?bytes"}],"type":"DocumentAttribute"},{"id":"358154344","predicate":"documentAttributeFilename","params":[{"name":"file_name","type":"string"}],"type":"DocumentAttribute"},{"id":"-244016606","predicate":"messages.stickersNotModified","params":[],"type":"messages.Stickers"},{"id":"816245886","predicate":"messages.stickers","params":[{"name":"hash","type":"long"},{"name":"stickers","type":"Vector"}],"type":"messages.Stickers"},{"id":"313694676","predicate":"stickerPack","params":[{"name":"emoticon","type":"string"},{"name":"documents","type":"Vector"}],"type":"StickerPack"},{"id":"-395967805","predicate":"messages.allStickersNotModified","params":[],"type":"messages.AllStickers"},{"id":"-843329861","predicate":"messages.allStickers","params":[{"name":"hash","type":"long"},{"name":"sets","type":"Vector"}],"type":"messages.AllStickers"},{"id":"-1667805217","predicate":"updateReadHistoryInbox","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.0?int"},{"name":"peer","type":"Peer"},{"name":"max_id","type":"int"},{"name":"still_unread_count","type":"int"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"791617983","predicate":"updateReadHistoryOutbox","params":[{"name":"peer","type":"Peer"},{"name":"max_id","type":"int"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-2066640507","predicate":"messages.affectedMessages","params":[{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"messages.AffectedMessages"},{"id":"2139689491","predicate":"updateWebPage","params":[{"name":"webpage","type":"WebPage"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-350980120","predicate":"webPageEmpty","params":[{"name":"id","type":"long"}],"type":"WebPage"},{"id":"-981018084","predicate":"webPagePending","params":[{"name":"id","type":"long"},{"name":"date","type":"int"}],"type":"WebPage"},{"id":"-392411726","predicate":"webPage","params":[{"name":"flags","type":"#"},{"name":"id","type":"long"},{"name":"url","type":"string"},{"name":"display_url","type":"string"},{"name":"hash","type":"int"},{"name":"type","type":"flags.0?string"},{"name":"site_name","type":"flags.1?string"},{"name":"title","type":"flags.2?string"},{"name":"description","type":"flags.3?string"},{"name":"photo","type":"flags.4?Photo"},{"name":"embed_url","type":"flags.5?string"},{"name":"embed_type","type":"flags.5?string"},{"name":"embed_width","type":"flags.6?int"},{"name":"embed_height","type":"flags.6?int"},{"name":"duration","type":"flags.7?int"},{"name":"author","type":"flags.8?string"},{"name":"document","type":"flags.9?Document"},{"name":"cached_page","type":"flags.10?Page"},{"name":"attributes","type":"flags.12?Vector"}],"type":"WebPage"},{"id":"-1557277184","predicate":"messageMediaWebPage","params":[{"name":"webpage","type":"WebPage"}],"type":"MessageMedia"},{"id":"-1392388579","predicate":"authorization","params":[{"name":"flags","type":"#"},{"name":"current","type":"flags.0?true"},{"name":"official_app","type":"flags.1?true"},{"name":"password_pending","type":"flags.2?true"},{"name":"encrypted_requests_disabled","type":"flags.3?true"},{"name":"call_requests_disabled","type":"flags.4?true"},{"name":"hash","type":"long"},{"name":"device_model","type":"string"},{"name":"platform","type":"string"},{"name":"system_version","type":"string"},{"name":"api_id","type":"int"},{"name":"app_name","type":"string"},{"name":"app_version","type":"string"},{"name":"date_created","type":"int"},{"name":"date_active","type":"int"},{"name":"ip","type":"string"},{"name":"country","type":"string"},{"name":"region","type":"string"}],"type":"Authorization"},{"id":"307276766","predicate":"account.authorizations","params":[{"name":"authorizations","type":"Vector"}],"type":"account.Authorizations"},{"id":"408623183","predicate":"account.password","params":[{"name":"flags","type":"#"},{"name":"has_recovery","type":"flags.0?true"},{"name":"has_secure_values","type":"flags.1?true"},{"name":"has_password","type":"flags.2?true"},{"name":"current_algo","type":"flags.2?PasswordKdfAlgo"},{"name":"srp_B","type":"flags.2?bytes"},{"name":"srp_id","type":"flags.2?long"},{"name":"hint","type":"flags.3?string"},{"name":"email_unconfirmed_pattern","type":"flags.4?string"},{"name":"new_algo","type":"PasswordKdfAlgo"},{"name":"new_secure_algo","type":"SecurePasswordKdfAlgo"},{"name":"secure_random","type":"bytes"},{"name":"pending_reset_date","type":"flags.5?int"}],"type":"account.Password"},{"id":"-1705233435","predicate":"account.passwordSettings","params":[{"name":"flags","type":"#"},{"name":"email","type":"flags.0?string"},{"name":"secure_settings","type":"flags.1?SecureSecretSettings"}],"type":"account.PasswordSettings"},{"id":"-1036572727","predicate":"account.passwordInputSettings","params":[{"name":"flags","type":"#"},{"name":"new_algo","type":"flags.0?PasswordKdfAlgo"},{"name":"new_password_hash","type":"flags.0?bytes"},{"name":"hint","type":"flags.0?string"},{"name":"email","type":"flags.1?string"},{"name":"new_secure_settings","type":"flags.2?SecureSecretSettings"}],"type":"account.PasswordInputSettings"},{"id":"326715557","predicate":"auth.passwordRecovery","params":[{"name":"email_pattern","type":"string"}],"type":"auth.PasswordRecovery"},{"id":"-1052959727","predicate":"inputMediaVenue","params":[{"name":"geo_point","type":"InputGeoPoint"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"},{"name":"venue_type","type":"string"}],"type":"InputMedia"},{"id":"784356159","predicate":"messageMediaVenue","params":[{"name":"geo","type":"GeoPoint"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"},{"name":"venue_type","type":"string"}],"type":"MessageMedia"},{"id":"-1551583367","predicate":"receivedNotifyMessage","params":[{"name":"id","type":"int"},{"name":"flags","type":"int"}],"type":"ReceivedNotifyMessage"},{"id":"-1316944408","predicate":"chatInviteExported","params":[{"name":"flags","type":"#"},{"name":"revoked","type":"flags.0?true"},{"name":"permanent","type":"flags.5?true"},{"name":"link","type":"string"},{"name":"admin_id","type":"long"},{"name":"date","type":"int"},{"name":"start_date","type":"flags.4?int"},{"name":"expire_date","type":"flags.1?int"},{"name":"usage_limit","type":"flags.2?int"},{"name":"usage","type":"flags.3?int"}],"type":"ExportedChatInvite"},{"id":"1516793212","predicate":"chatInviteAlready","params":[{"name":"chat","type":"Chat"}],"type":"ChatInvite"},{"id":"-540871282","predicate":"chatInvite","params":[{"name":"flags","type":"#"},{"name":"channel","type":"flags.0?true"},{"name":"broadcast","type":"flags.1?true"},{"name":"public","type":"flags.2?true"},{"name":"megagroup","type":"flags.3?true"},{"name":"title","type":"string"},{"name":"photo","type":"Photo"},{"name":"participants_count","type":"int"},{"name":"participants","type":"flags.4?Vector"}],"type":"ChatInvite"},{"id":"51520707","predicate":"messageActionChatJoinedByLink","params":[{"name":"inviter_id","type":"long"}],"type":"MessageAction"},{"id":"1757493555","predicate":"updateReadMessagesContents","params":[{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-4838507","predicate":"inputStickerSetEmpty","params":[],"type":"InputStickerSet"},{"id":"-1645763991","predicate":"inputStickerSetID","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputStickerSet"},{"id":"-2044933984","predicate":"inputStickerSetShortName","params":[{"name":"short_name","type":"string"}],"type":"InputStickerSet"},{"id":"-673242758","predicate":"stickerSet","params":[{"name":"flags","type":"#"},{"name":"archived","type":"flags.1?true"},{"name":"official","type":"flags.2?true"},{"name":"masks","type":"flags.3?true"},{"name":"animated","type":"flags.5?true"},{"name":"videos","type":"flags.6?true"},{"name":"installed_date","type":"flags.0?int"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"title","type":"string"},{"name":"short_name","type":"string"},{"name":"thumbs","type":"flags.4?Vector"},{"name":"thumb_dc_id","type":"flags.4?int"},{"name":"thumb_version","type":"flags.4?int"},{"name":"count","type":"int"},{"name":"hash","type":"int"}],"type":"StickerSet"},{"id":"-1240849242","predicate":"messages.stickerSet","params":[{"name":"set","type":"StickerSet"},{"name":"packs","type":"Vector"},{"name":"documents","type":"Vector"}],"type":"messages.StickerSet"},{"id":"1073147056","predicate":"user","params":[{"name":"flags","type":"#"},{"name":"self","type":"flags.10?true"},{"name":"contact","type":"flags.11?true"},{"name":"mutual_contact","type":"flags.12?true"},{"name":"deleted","type":"flags.13?true"},{"name":"bot","type":"flags.14?true"},{"name":"bot_chat_history","type":"flags.15?true"},{"name":"bot_nochats","type":"flags.16?true"},{"name":"verified","type":"flags.17?true"},{"name":"restricted","type":"flags.18?true"},{"name":"min","type":"flags.20?true"},{"name":"bot_inline_geo","type":"flags.21?true"},{"name":"support","type":"flags.23?true"},{"name":"scam","type":"flags.24?true"},{"name":"apply_min_photo","type":"flags.25?true"},{"name":"fake","type":"flags.26?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"flags.0?long"},{"name":"first_name","type":"flags.1?string"},{"name":"last_name","type":"flags.2?string"},{"name":"username","type":"flags.3?string"},{"name":"phone","type":"flags.4?string"},{"name":"photo","type":"flags.5?UserProfilePhoto"},{"name":"status","type":"flags.6?UserStatus"},{"name":"bot_info_version","type":"flags.14?int"},{"name":"restriction_reason","type":"flags.18?Vector"},{"name":"bot_inline_placeholder","type":"flags.19?string"},{"name":"lang_code","type":"flags.22?string"}],"type":"User"},{"id":"-1032140601","predicate":"botCommand","params":[{"name":"command","type":"string"},{"name":"description","type":"string"}],"type":"BotCommand"},{"id":"460632885","predicate":"botInfo","params":[{"name":"user_id","type":"long"},{"name":"description","type":"string"},{"name":"commands","type":"Vector"}],"type":"BotInfo"},{"id":"-1560655744","predicate":"keyboardButton","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"2002815875","predicate":"keyboardButtonRow","params":[{"name":"buttons","type":"Vector"}],"type":"KeyboardButtonRow"},{"id":"-1606526075","predicate":"replyKeyboardHide","params":[{"name":"flags","type":"#"},{"name":"selective","type":"flags.2?true"}],"type":"ReplyMarkup"},{"id":"-2035021048","predicate":"replyKeyboardForceReply","params":[{"name":"flags","type":"#"},{"name":"single_use","type":"flags.1?true"},{"name":"selective","type":"flags.2?true"},{"name":"placeholder","type":"flags.3?string"}],"type":"ReplyMarkup"},{"id":"-2049074735","predicate":"replyKeyboardMarkup","params":[{"name":"flags","type":"#"},{"name":"resize","type":"flags.0?true"},{"name":"single_use","type":"flags.1?true"},{"name":"selective","type":"flags.2?true"},{"name":"rows","type":"Vector"},{"name":"placeholder","type":"flags.3?string"}],"type":"ReplyMarkup"},{"id":"-571955892","predicate":"inputPeerUser","params":[{"name":"user_id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputPeer"},{"id":"-233744186","predicate":"inputUser","params":[{"name":"user_id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputUser"},{"id":"-1148011883","predicate":"messageEntityUnknown","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-100378723","predicate":"messageEntityMention","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1868782349","predicate":"messageEntityHashtag","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1827637959","predicate":"messageEntityBotCommand","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1859134776","predicate":"messageEntityUrl","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1692693954","predicate":"messageEntityEmail","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-1117713463","predicate":"messageEntityBold","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-2106619040","predicate":"messageEntityItalic","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"681706865","predicate":"messageEntityCode","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1938967520","predicate":"messageEntityPre","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"language","type":"string"}],"type":"MessageEntity"},{"id":"1990644519","predicate":"messageEntityTextUrl","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"url","type":"string"}],"type":"MessageEntity"},{"id":"-1877614335","predicate":"updateShortSentMessage","params":[{"name":"flags","type":"#"},{"name":"out","type":"flags.1?true"},{"name":"id","type":"int"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"date","type":"int"},{"name":"media","type":"flags.9?MessageMedia"},{"name":"entities","type":"flags.7?Vector"},{"name":"ttl_period","type":"flags.25?int"}],"type":"Updates"},{"id":"-292807034","predicate":"inputChannelEmpty","params":[],"type":"InputChannel"},{"id":"-212145112","predicate":"inputChannel","params":[{"name":"channel_id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputChannel"},{"id":"-1566230754","predicate":"peerChannel","params":[{"name":"channel_id","type":"long"}],"type":"Peer"},{"id":"666680316","predicate":"inputPeerChannel","params":[{"name":"channel_id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputPeer"},{"id":"-2107528095","predicate":"channel","params":[{"name":"flags","type":"#"},{"name":"creator","type":"flags.0?true"},{"name":"left","type":"flags.2?true"},{"name":"broadcast","type":"flags.5?true"},{"name":"verified","type":"flags.7?true"},{"name":"megagroup","type":"flags.8?true"},{"name":"restricted","type":"flags.9?true"},{"name":"signatures","type":"flags.11?true"},{"name":"min","type":"flags.12?true"},{"name":"scam","type":"flags.19?true"},{"name":"has_link","type":"flags.20?true"},{"name":"has_geo","type":"flags.21?true"},{"name":"slowmode_enabled","type":"flags.22?true"},{"name":"call_active","type":"flags.23?true"},{"name":"call_not_empty","type":"flags.24?true"},{"name":"fake","type":"flags.25?true"},{"name":"gigagroup","type":"flags.26?true"},{"name":"noforwards","type":"flags.27?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"flags.13?long"},{"name":"title","type":"string"},{"name":"username","type":"flags.6?string"},{"name":"photo","type":"ChatPhoto"},{"name":"date","type":"int"},{"name":"restriction_reason","type":"flags.9?Vector"},{"name":"admin_rights","type":"flags.14?ChatAdminRights"},{"name":"banned_rights","type":"flags.15?ChatBannedRights"},{"name":"default_banned_rights","type":"flags.18?ChatBannedRights"},{"name":"participants_count","type":"flags.17?int"}],"type":"Chat"},{"id":"399807445","predicate":"channelForbidden","params":[{"name":"flags","type":"#"},{"name":"broadcast","type":"flags.5?true"},{"name":"megagroup","type":"flags.8?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"title","type":"string"},{"name":"until_date","type":"flags.16?int"}],"type":"Chat"},{"id":"2131196633","predicate":"contacts.resolvedPeer","params":[{"name":"peer","type":"Peer"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.ResolvedPeer"},{"id":"-374179305","predicate":"channelFull","params":[{"name":"flags","type":"#"},{"name":"can_view_participants","type":"flags.3?true"},{"name":"can_set_username","type":"flags.6?true"},{"name":"can_set_stickers","type":"flags.7?true"},{"name":"hidden_prehistory","type":"flags.10?true"},{"name":"can_set_location","type":"flags.16?true"},{"name":"has_scheduled","type":"flags.19?true"},{"name":"can_view_stats","type":"flags.20?true"},{"name":"blocked","type":"flags.22?true"},{"name":"id","type":"long"},{"name":"about","type":"string"},{"name":"participants_count","type":"flags.0?int"},{"name":"admins_count","type":"flags.1?int"},{"name":"kicked_count","type":"flags.2?int"},{"name":"banned_count","type":"flags.2?int"},{"name":"online_count","type":"flags.13?int"},{"name":"read_inbox_max_id","type":"int"},{"name":"read_outbox_max_id","type":"int"},{"name":"unread_count","type":"int"},{"name":"chat_photo","type":"Photo"},{"name":"notify_settings","type":"PeerNotifySettings"},{"name":"exported_invite","type":"flags.23?ExportedChatInvite"},{"name":"bot_info","type":"Vector"},{"name":"migrated_from_chat_id","type":"flags.4?long"},{"name":"migrated_from_max_id","type":"flags.4?int"},{"name":"pinned_msg_id","type":"flags.5?int"},{"name":"stickerset","type":"flags.8?StickerSet"},{"name":"available_min_id","type":"flags.9?int"},{"name":"folder_id","type":"flags.11?int"},{"name":"linked_chat_id","type":"flags.14?long"},{"name":"location","type":"flags.15?ChannelLocation"},{"name":"slowmode_seconds","type":"flags.17?int"},{"name":"slowmode_next_send_date","type":"flags.18?int"},{"name":"stats_dc","type":"flags.12?int"},{"name":"pts","type":"int"},{"name":"call","type":"flags.21?InputGroupCall"},{"name":"ttl_period","type":"flags.24?int"},{"name":"pending_suggestions","type":"flags.25?Vector"},{"name":"groupcall_default_join_as","type":"flags.26?Peer"},{"name":"theme_emoticon","type":"flags.27?string"}],"type":"ChatFull"},{"id":"182649427","predicate":"messageRange","params":[{"name":"min_id","type":"int"},{"name":"max_id","type":"int"}],"type":"MessageRange"},{"id":"1682413576","predicate":"messages.channelMessages","params":[{"name":"flags","type":"#"},{"name":"inexact","type":"flags.1?true"},{"name":"pts","type":"int"},{"name":"count","type":"int"},{"name":"offset_id_offset","type":"flags.2?int"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.Messages"},{"id":"-1781355374","predicate":"messageActionChannelCreate","params":[{"name":"title","type":"string"}],"type":"MessageAction"},{"id":"277713951","predicate":"updateChannelTooLong","params":[{"name":"flags","type":"#"},{"name":"channel_id","type":"long"},{"name":"pts","type":"flags.0?int"}],"type":"Update"},{"id":"1666927625","predicate":"updateChannel","params":[{"name":"channel_id","type":"long"}],"type":"Update"},{"id":"1656358105","predicate":"updateNewChannelMessage","params":[{"name":"message","type":"Message"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1842450928","predicate":"updateReadChannelInbox","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.0?int"},{"name":"channel_id","type":"long"},{"name":"max_id","type":"int"},{"name":"still_unread_count","type":"int"},{"name":"pts","type":"int"}],"type":"Update"},{"id":"-1020437742","predicate":"updateDeleteChannelMessages","params":[{"name":"channel_id","type":"long"},{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-232346616","predicate":"updateChannelMessageViews","params":[{"name":"channel_id","type":"long"},{"name":"id","type":"int"},{"name":"views","type":"int"}],"type":"Update"},{"id":"1041346555","predicate":"updates.channelDifferenceEmpty","params":[{"name":"flags","type":"#"},{"name":"final","type":"flags.0?true"},{"name":"pts","type":"int"},{"name":"timeout","type":"flags.1?int"}],"type":"updates.ChannelDifference"},{"id":"-1531132162","predicate":"updates.channelDifferenceTooLong","params":[{"name":"flags","type":"#"},{"name":"final","type":"flags.0?true"},{"name":"timeout","type":"flags.1?int"},{"name":"dialog","type":"Dialog"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"updates.ChannelDifference"},{"id":"543450958","predicate":"updates.channelDifference","params":[{"name":"flags","type":"#"},{"name":"final","type":"flags.0?true"},{"name":"pts","type":"int"},{"name":"timeout","type":"flags.1?int"},{"name":"new_messages","type":"Vector"},{"name":"other_updates","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"updates.ChannelDifference"},{"id":"-1798033689","predicate":"channelMessagesFilterEmpty","params":[],"type":"ChannelMessagesFilter"},{"id":"-847783593","predicate":"channelMessagesFilter","params":[{"name":"flags","type":"#"},{"name":"exclude_new_messages","type":"flags.1?true"},{"name":"ranges","type":"Vector"}],"type":"ChannelMessagesFilter"},{"id":"-1072953408","predicate":"channelParticipant","params":[{"name":"user_id","type":"long"},{"name":"date","type":"int"}],"type":"ChannelParticipant"},{"id":"682146919","predicate":"channelParticipantSelf","params":[{"name":"user_id","type":"long"},{"name":"inviter_id","type":"long"},{"name":"date","type":"int"}],"type":"ChannelParticipant"},{"id":"803602899","predicate":"channelParticipantCreator","params":[{"name":"flags","type":"#"},{"name":"user_id","type":"long"},{"name":"admin_rights","type":"ChatAdminRights"},{"name":"rank","type":"flags.0?string"}],"type":"ChannelParticipant"},{"id":"-566281095","predicate":"channelParticipantsRecent","params":[],"type":"ChannelParticipantsFilter"},{"id":"-1268741783","predicate":"channelParticipantsAdmins","params":[],"type":"ChannelParticipantsFilter"},{"id":"-1548400251","predicate":"channelParticipantsKicked","params":[{"name":"q","type":"string"}],"type":"ChannelParticipantsFilter"},{"id":"-1699676497","predicate":"channels.channelParticipants","params":[{"name":"count","type":"int"},{"name":"participants","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"channels.ChannelParticipants"},{"id":"-541588713","predicate":"channels.channelParticipant","params":[{"name":"participant","type":"ChannelParticipant"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"channels.ChannelParticipant"},{"id":"-462696732","predicate":"chatParticipantCreator","params":[{"name":"user_id","type":"long"}],"type":"ChatParticipant"},{"id":"-1600962725","predicate":"chatParticipantAdmin","params":[{"name":"user_id","type":"long"},{"name":"inviter_id","type":"long"},{"name":"date","type":"int"}],"type":"ChatParticipant"},{"id":"-674602590","predicate":"updateChatParticipantAdmin","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"long"},{"name":"is_admin","type":"Bool"},{"name":"version","type":"int"}],"type":"Update"},{"id":"-519864430","predicate":"messageActionChatMigrateTo","params":[{"name":"channel_id","type":"long"}],"type":"MessageAction"},{"id":"-365344535","predicate":"messageActionChannelMigrateFrom","params":[{"name":"title","type":"string"},{"name":"chat_id","type":"long"}],"type":"MessageAction"},{"id":"-1328445861","predicate":"channelParticipantsBots","params":[],"type":"ChannelParticipantsFilter"},{"id":"2013922064","predicate":"help.termsOfService","params":[{"name":"flags","type":"#"},{"name":"popup","type":"flags.0?true"},{"name":"id","type":"DataJSON"},{"name":"text","type":"string"},{"name":"entities","type":"Vector"},{"name":"min_age_confirm","type":"flags.1?int"}],"type":"help.TermsOfService"},{"id":"1753886890","predicate":"updateNewStickerSet","params":[{"name":"stickerset","type":"messages.StickerSet"}],"type":"Update"},{"id":"196268545","predicate":"updateStickerSetsOrder","params":[{"name":"flags","type":"#"},{"name":"masks","type":"flags.0?true"},{"name":"order","type":"Vector"}],"type":"Update"},{"id":"1135492588","predicate":"updateStickerSets","params":[],"type":"Update"},{"id":"-402498398","predicate":"messages.savedGifsNotModified","params":[],"type":"messages.SavedGifs"},{"id":"-2069878259","predicate":"messages.savedGifs","params":[{"name":"hash","type":"long"},{"name":"gifs","type":"Vector"}],"type":"messages.SavedGifs"},{"id":"-1821035490","predicate":"updateSavedGifs","params":[],"type":"Update"},{"id":"864077702","predicate":"inputBotInlineMessageMediaAuto","params":[{"name":"flags","type":"#"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"1036876423","predicate":"inputBotInlineMessageText","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.0?true"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"-2000710887","predicate":"inputBotInlineResult","params":[{"name":"flags","type":"#"},{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"title","type":"flags.1?string"},{"name":"description","type":"flags.2?string"},{"name":"url","type":"flags.3?string"},{"name":"thumb","type":"flags.4?InputWebDocument"},{"name":"content","type":"flags.5?InputWebDocument"},{"name":"send_message","type":"InputBotInlineMessage"}],"type":"InputBotInlineResult"},{"id":"1984755728","predicate":"botInlineMessageMediaAuto","params":[{"name":"flags","type":"#"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"-1937807902","predicate":"botInlineMessageText","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.0?true"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"295067450","predicate":"botInlineResult","params":[{"name":"flags","type":"#"},{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"title","type":"flags.1?string"},{"name":"description","type":"flags.2?string"},{"name":"url","type":"flags.3?string"},{"name":"thumb","type":"flags.4?WebDocument"},{"name":"content","type":"flags.5?WebDocument"},{"name":"send_message","type":"BotInlineMessage"}],"type":"BotInlineResult"},{"id":"-1803769784","predicate":"messages.botResults","params":[{"name":"flags","type":"#"},{"name":"gallery","type":"flags.0?true"},{"name":"query_id","type":"long"},{"name":"next_offset","type":"flags.1?string"},{"name":"switch_pm","type":"flags.2?InlineBotSwitchPM"},{"name":"results","type":"Vector"},{"name":"cache_time","type":"int"},{"name":"users","type":"Vector"}],"type":"messages.BotResults"},{"id":"1232025500","predicate":"updateBotInlineQuery","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"query","type":"string"},{"name":"geo","type":"flags.0?GeoPoint"},{"name":"peer_type","type":"flags.1?InlineQueryPeerType"},{"name":"offset","type":"string"}],"type":"Update"},{"id":"317794823","predicate":"updateBotInlineSend","params":[{"name":"flags","type":"#"},{"name":"user_id","type":"long"},{"name":"query","type":"string"},{"name":"geo","type":"flags.0?GeoPoint"},{"name":"id","type":"string"},{"name":"msg_id","type":"flags.1?InputBotInlineMessageID"}],"type":"Update"},{"id":"1358283666","predicate":"inputMessagesFilterVoice","params":[],"type":"MessagesFilter"},{"id":"928101534","predicate":"inputMessagesFilterMusic","params":[],"type":"MessagesFilter"},{"id":"-1107622874","predicate":"inputPrivacyKeyChatInvite","params":[],"type":"InputPrivacyKey"},{"id":"1343122938","predicate":"privacyKeyChatInvite","params":[],"type":"PrivacyKey"},{"id":"1571494644","predicate":"exportedMessageLink","params":[{"name":"link","type":"string"},{"name":"html","type":"string"}],"type":"ExportedMessageLink"},{"id":"1601666510","predicate":"messageFwdHeader","params":[{"name":"flags","type":"#"},{"name":"imported","type":"flags.7?true"},{"name":"from_id","type":"flags.0?Peer"},{"name":"from_name","type":"flags.5?string"},{"name":"date","type":"int"},{"name":"channel_post","type":"flags.2?int"},{"name":"post_author","type":"flags.3?string"},{"name":"saved_from_peer","type":"flags.4?Peer"},{"name":"saved_from_msg_id","type":"flags.4?int"},{"name":"psa_type","type":"flags.6?string"}],"type":"MessageFwdHeader"},{"id":"457133559","predicate":"updateEditChannelMessage","params":[{"name":"message","type":"Message"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1799538451","predicate":"messageActionPinMessage","params":[],"type":"MessageAction"},{"id":"1923290508","predicate":"auth.codeTypeSms","params":[],"type":"auth.CodeType"},{"id":"1948046307","predicate":"auth.codeTypeCall","params":[],"type":"auth.CodeType"},{"id":"577556219","predicate":"auth.codeTypeFlashCall","params":[],"type":"auth.CodeType"},{"id":"1035688326","predicate":"auth.sentCodeTypeApp","params":[{"name":"length","type":"int"}],"type":"auth.SentCodeType"},{"id":"-1073693790","predicate":"auth.sentCodeTypeSms","params":[{"name":"length","type":"int"}],"type":"auth.SentCodeType"},{"id":"1398007207","predicate":"auth.sentCodeTypeCall","params":[{"name":"length","type":"int"}],"type":"auth.SentCodeType"},{"id":"-1425815847","predicate":"auth.sentCodeTypeFlashCall","params":[{"name":"pattern","type":"string"}],"type":"auth.SentCodeType"},{"id":"629866245","predicate":"keyboardButtonUrl","params":[{"name":"text","type":"string"},{"name":"url","type":"string"}],"type":"KeyboardButton"},{"id":"901503851","predicate":"keyboardButtonCallback","params":[{"name":"flags","type":"#"},{"name":"requires_password","type":"flags.0?true"},{"name":"text","type":"string"},{"name":"data","type":"bytes"}],"type":"KeyboardButton"},{"id":"-1318425559","predicate":"keyboardButtonRequestPhone","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"-59151553","predicate":"keyboardButtonRequestGeoLocation","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"90744648","predicate":"keyboardButtonSwitchInline","params":[{"name":"flags","type":"#"},{"name":"same_peer","type":"flags.0?true"},{"name":"text","type":"string"},{"name":"query","type":"string"}],"type":"KeyboardButton"},{"id":"1218642516","predicate":"replyInlineMarkup","params":[{"name":"rows","type":"Vector"}],"type":"ReplyMarkup"},{"id":"911761060","predicate":"messages.botCallbackAnswer","params":[{"name":"flags","type":"#"},{"name":"alert","type":"flags.1?true"},{"name":"has_url","type":"flags.3?true"},{"name":"native_ui","type":"flags.4?true"},{"name":"message","type":"flags.0?string"},{"name":"url","type":"flags.2?string"},{"name":"cache_time","type":"int"}],"type":"messages.BotCallbackAnswer"},{"id":"-1177566067","predicate":"updateBotCallbackQuery","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"peer","type":"Peer"},{"name":"msg_id","type":"int"},{"name":"chat_instance","type":"long"},{"name":"data","type":"flags.0?bytes"},{"name":"game_short_name","type":"flags.1?string"}],"type":"Update"},{"id":"649453030","predicate":"messages.messageEditData","params":[{"name":"flags","type":"#"},{"name":"caption","type":"flags.0?true"}],"type":"messages.MessageEditData"},{"id":"-469536605","predicate":"updateEditMessage","params":[{"name":"message","type":"Message"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1768777083","predicate":"inputBotInlineMessageMediaGeo","params":[{"name":"flags","type":"#"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"heading","type":"flags.0?int"},{"name":"period","type":"flags.1?int"},{"name":"proximity_notification_radius","type":"flags.3?int"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"1098628881","predicate":"inputBotInlineMessageMediaVenue","params":[{"name":"flags","type":"#"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"},{"name":"venue_type","type":"string"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"-1494368259","predicate":"inputBotInlineMessageMediaContact","params":[{"name":"flags","type":"#"},{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"vcard","type":"string"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"85477117","predicate":"botInlineMessageMediaGeo","params":[{"name":"flags","type":"#"},{"name":"geo","type":"GeoPoint"},{"name":"heading","type":"flags.0?int"},{"name":"period","type":"flags.1?int"},{"name":"proximity_notification_radius","type":"flags.3?int"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"-1970903652","predicate":"botInlineMessageMediaVenue","params":[{"name":"flags","type":"#"},{"name":"geo","type":"GeoPoint"},{"name":"title","type":"string"},{"name":"address","type":"string"},{"name":"provider","type":"string"},{"name":"venue_id","type":"string"},{"name":"venue_type","type":"string"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"416402882","predicate":"botInlineMessageMediaContact","params":[{"name":"flags","type":"#"},{"name":"phone_number","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"vcard","type":"string"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"-1462213465","predicate":"inputBotInlineResultPhoto","params":[{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"photo","type":"InputPhoto"},{"name":"send_message","type":"InputBotInlineMessage"}],"type":"InputBotInlineResult"},{"id":"-459324","predicate":"inputBotInlineResultDocument","params":[{"name":"flags","type":"#"},{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"title","type":"flags.1?string"},{"name":"description","type":"flags.2?string"},{"name":"document","type":"InputDocument"},{"name":"send_message","type":"InputBotInlineMessage"}],"type":"InputBotInlineResult"},{"id":"400266251","predicate":"botInlineMediaResult","params":[{"name":"flags","type":"#"},{"name":"id","type":"string"},{"name":"type","type":"string"},{"name":"photo","type":"flags.0?Photo"},{"name":"document","type":"flags.1?Document"},{"name":"title","type":"flags.2?string"},{"name":"description","type":"flags.3?string"},{"name":"send_message","type":"BotInlineMessage"}],"type":"BotInlineResult"},{"id":"-1995686519","predicate":"inputBotInlineMessageID","params":[{"name":"dc_id","type":"int"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputBotInlineMessageID"},{"id":"1763610706","predicate":"updateInlineBotCallbackQuery","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"msg_id","type":"InputBotInlineMessageID"},{"name":"chat_instance","type":"long"},{"name":"data","type":"flags.0?bytes"},{"name":"game_short_name","type":"flags.1?string"}],"type":"Update"},{"id":"1008755359","predicate":"inlineBotSwitchPM","params":[{"name":"text","type":"string"},{"name":"start_param","type":"string"}],"type":"InlineBotSwitchPM"},{"id":"863093588","predicate":"messages.peerDialogs","params":[{"name":"dialogs","type":"Vector"},{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"state","type":"updates.State"}],"type":"messages.PeerDialogs"},{"id":"-305282981","predicate":"topPeer","params":[{"name":"peer","type":"Peer"},{"name":"rating","type":"double"}],"type":"TopPeer"},{"id":"-1419371685","predicate":"topPeerCategoryBotsPM","params":[],"type":"TopPeerCategory"},{"id":"344356834","predicate":"topPeerCategoryBotsInline","params":[],"type":"TopPeerCategory"},{"id":"104314861","predicate":"topPeerCategoryCorrespondents","params":[],"type":"TopPeerCategory"},{"id":"-1122524854","predicate":"topPeerCategoryGroups","params":[],"type":"TopPeerCategory"},{"id":"371037736","predicate":"topPeerCategoryChannels","params":[],"type":"TopPeerCategory"},{"id":"-75283823","predicate":"topPeerCategoryPeers","params":[{"name":"category","type":"TopPeerCategory"},{"name":"count","type":"int"},{"name":"peers","type":"Vector"}],"type":"TopPeerCategoryPeers"},{"id":"-567906571","predicate":"contacts.topPeersNotModified","params":[],"type":"contacts.TopPeers"},{"id":"1891070632","predicate":"contacts.topPeers","params":[{"name":"categories","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"contacts.TopPeers"},{"id":"-595914432","predicate":"messageEntityMentionName","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"user_id","type":"long"}],"type":"MessageEntity"},{"id":"546203849","predicate":"inputMessageEntityMentionName","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"},{"name":"user_id","type":"InputUser"}],"type":"MessageEntity"},{"id":"975236280","predicate":"inputMessagesFilterChatPhotos","params":[],"type":"MessagesFilter"},{"id":"-1218471511","predicate":"updateReadChannelOutbox","params":[{"name":"channel_id","type":"long"},{"name":"max_id","type":"int"}],"type":"Update"},{"id":"-299124375","predicate":"updateDraftMessage","params":[{"name":"peer","type":"Peer"},{"name":"draft","type":"DraftMessage"}],"type":"Update"},{"id":"453805082","predicate":"draftMessageEmpty","params":[{"name":"flags","type":"#"},{"name":"date","type":"flags.0?int"}],"type":"DraftMessage"},{"id":"-40996577","predicate":"draftMessage","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"message","type":"string"},{"name":"entities","type":"flags.3?Vector"},{"name":"date","type":"int"}],"type":"DraftMessage"},{"id":"-1615153660","predicate":"messageActionHistoryClear","params":[],"type":"MessageAction"},{"id":"-958657434","predicate":"messages.featuredStickersNotModified","params":[{"name":"count","type":"int"}],"type":"messages.FeaturedStickers"},{"id":"-2067782896","predicate":"messages.featuredStickers","params":[{"name":"hash","type":"long"},{"name":"count","type":"int"},{"name":"sets","type":"Vector"},{"name":"unread","type":"Vector"}],"type":"messages.FeaturedStickers"},{"id":"1461528386","predicate":"updateReadFeaturedStickers","params":[],"type":"Update"},{"id":"186120336","predicate":"messages.recentStickersNotModified","params":[],"type":"messages.RecentStickers"},{"id":"-1999405994","predicate":"messages.recentStickers","params":[{"name":"hash","type":"long"},{"name":"packs","type":"Vector"},{"name":"stickers","type":"Vector"},{"name":"dates","type":"Vector"}],"type":"messages.RecentStickers"},{"id":"-1706939360","predicate":"updateRecentStickers","params":[],"type":"Update"},{"id":"1338747336","predicate":"messages.archivedStickers","params":[{"name":"count","type":"int"},{"name":"sets","type":"Vector"}],"type":"messages.ArchivedStickers"},{"id":"946083368","predicate":"messages.stickerSetInstallResultSuccess","params":[],"type":"messages.StickerSetInstallResult"},{"id":"904138920","predicate":"messages.stickerSetInstallResultArchive","params":[{"name":"sets","type":"Vector"}],"type":"messages.StickerSetInstallResult"},{"id":"1678812626","predicate":"stickerSetCovered","params":[{"name":"set","type":"StickerSet"},{"name":"cover","type":"Document"}],"type":"StickerSetCovered"},{"id":"-1574314746","predicate":"updateConfig","params":[],"type":"Update"},{"id":"861169551","predicate":"updatePtsChanged","params":[],"type":"Update"},{"id":"-440664550","predicate":"inputMediaPhotoExternal","params":[{"name":"flags","type":"#"},{"name":"url","type":"string"},{"name":"ttl_seconds","type":"flags.0?int"}],"type":"InputMedia"},{"id":"-78455655","predicate":"inputMediaDocumentExternal","params":[{"name":"flags","type":"#"},{"name":"url","type":"string"},{"name":"ttl_seconds","type":"flags.0?int"}],"type":"InputMedia"},{"id":"872932635","predicate":"stickerSetMultiCovered","params":[{"name":"set","type":"StickerSet"},{"name":"covers","type":"Vector"}],"type":"StickerSetCovered"},{"id":"-1361650766","predicate":"maskCoords","params":[{"name":"n","type":"int"},{"name":"x","type":"double"},{"name":"y","type":"double"},{"name":"zoom","type":"double"}],"type":"MaskCoords"},{"id":"-1744710921","predicate":"documentAttributeHasStickers","params":[],"type":"DocumentAttribute"},{"id":"1251549527","predicate":"inputStickeredMediaPhoto","params":[{"name":"id","type":"InputPhoto"}],"type":"InputStickeredMedia"},{"id":"70813275","predicate":"inputStickeredMediaDocument","params":[{"name":"id","type":"InputDocument"}],"type":"InputStickeredMedia"},{"id":"-1107729093","predicate":"game","params":[{"name":"flags","type":"#"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"short_name","type":"string"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"Photo"},{"name":"document","type":"flags.0?Document"}],"type":"Game"},{"id":"1336154098","predicate":"inputBotInlineResultGame","params":[{"name":"id","type":"string"},{"name":"short_name","type":"string"},{"name":"send_message","type":"InputBotInlineMessage"}],"type":"InputBotInlineResult"},{"id":"1262639204","predicate":"inputBotInlineMessageGame","params":[{"name":"flags","type":"#"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"-38694904","predicate":"messageMediaGame","params":[{"name":"game","type":"Game"}],"type":"MessageMedia"},{"id":"-750828557","predicate":"inputMediaGame","params":[{"name":"id","type":"InputGame"}],"type":"InputMedia"},{"id":"53231223","predicate":"inputGameID","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputGame"},{"id":"-1020139510","predicate":"inputGameShortName","params":[{"name":"bot_id","type":"InputUser"},{"name":"short_name","type":"string"}],"type":"InputGame"},{"id":"1358175439","predicate":"keyboardButtonGame","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"-1834538890","predicate":"messageActionGameScore","params":[{"name":"game_id","type":"long"},{"name":"score","type":"int"}],"type":"MessageAction"},{"id":"1940093419","predicate":"highScore","params":[{"name":"pos","type":"int"},{"name":"user_id","type":"long"},{"name":"score","type":"int"}],"type":"HighScore"},{"id":"-1707344487","predicate":"messages.highScores","params":[{"name":"scores","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.HighScores"},{"id":"1258196845","predicate":"updates.differenceTooLong","params":[{"name":"pts","type":"int"}],"type":"updates.Difference"},{"id":"791390623","predicate":"updateChannelWebPage","params":[{"name":"channel_id","type":"long"},{"name":"webpage","type":"WebPage"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"-1663561404","predicate":"messages.chatsSlice","params":[{"name":"count","type":"int"},{"name":"chats","type":"Vector"}],"type":"messages.Chats"},{"id":"-599948721","predicate":"textEmpty","params":[],"type":"RichText"},{"id":"1950782688","predicate":"textPlain","params":[{"name":"text","type":"string"}],"type":"RichText"},{"id":"1730456516","predicate":"textBold","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"-653089380","predicate":"textItalic","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"-1054465340","predicate":"textUnderline","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"-1678197867","predicate":"textStrike","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"1816074681","predicate":"textFixed","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"1009288385","predicate":"textUrl","params":[{"name":"text","type":"RichText"},{"name":"url","type":"string"},{"name":"webpage_id","type":"long"}],"type":"RichText"},{"id":"-564523562","predicate":"textEmail","params":[{"name":"text","type":"RichText"},{"name":"email","type":"string"}],"type":"RichText"},{"id":"2120376535","predicate":"textConcat","params":[{"name":"texts","type":"Vector"}],"type":"RichText"},{"id":"324435594","predicate":"pageBlockUnsupported","params":[],"type":"PageBlock"},{"id":"1890305021","predicate":"pageBlockTitle","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-1879401953","predicate":"pageBlockSubtitle","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-1162877472","predicate":"pageBlockAuthorDate","params":[{"name":"author","type":"RichText"},{"name":"published_date","type":"int"}],"type":"PageBlock"},{"id":"-1076861716","predicate":"pageBlockHeader","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-248793375","predicate":"pageBlockSubheader","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"1182402406","predicate":"pageBlockParagraph","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-1066346178","predicate":"pageBlockPreformatted","params":[{"name":"text","type":"RichText"},{"name":"language","type":"string"}],"type":"PageBlock"},{"id":"1216809369","predicate":"pageBlockFooter","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"-618614392","predicate":"pageBlockDivider","params":[],"type":"PageBlock"},{"id":"-837994576","predicate":"pageBlockAnchor","params":[{"name":"name","type":"string"}],"type":"PageBlock"},{"id":"-454524911","predicate":"pageBlockList","params":[{"name":"items","type":"Vector"}],"type":"PageBlock"},{"id":"641563686","predicate":"pageBlockBlockquote","params":[{"name":"text","type":"RichText"},{"name":"caption","type":"RichText"}],"type":"PageBlock"},{"id":"1329878739","predicate":"pageBlockPullquote","params":[{"name":"text","type":"RichText"},{"name":"caption","type":"RichText"}],"type":"PageBlock"},{"id":"391759200","predicate":"pageBlockPhoto","params":[{"name":"flags","type":"#"},{"name":"photo_id","type":"long"},{"name":"caption","type":"PageCaption"},{"name":"url","type":"flags.0?string"},{"name":"webpage_id","type":"flags.0?long"}],"type":"PageBlock"},{"id":"2089805750","predicate":"pageBlockVideo","params":[{"name":"flags","type":"#"},{"name":"autoplay","type":"flags.0?true"},{"name":"loop","type":"flags.1?true"},{"name":"video_id","type":"long"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"972174080","predicate":"pageBlockCover","params":[{"name":"cover","type":"PageBlock"}],"type":"PageBlock"},{"id":"-1468953147","predicate":"pageBlockEmbed","params":[{"name":"flags","type":"#"},{"name":"full_width","type":"flags.0?true"},{"name":"allow_scrolling","type":"flags.3?true"},{"name":"url","type":"flags.1?string"},{"name":"html","type":"flags.2?string"},{"name":"poster_photo_id","type":"flags.4?long"},{"name":"w","type":"flags.5?int"},{"name":"h","type":"flags.5?int"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"-229005301","predicate":"pageBlockEmbedPost","params":[{"name":"url","type":"string"},{"name":"webpage_id","type":"long"},{"name":"author_photo_id","type":"long"},{"name":"author","type":"string"},{"name":"date","type":"int"},{"name":"blocks","type":"Vector"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"1705048653","predicate":"pageBlockCollage","params":[{"name":"items","type":"Vector"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"52401552","predicate":"pageBlockSlideshow","params":[{"name":"items","type":"Vector"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"1930545681","predicate":"webPageNotModified","params":[{"name":"flags","type":"#"},{"name":"cached_page_views","type":"flags.0?int"}],"type":"WebPage"},{"id":"-88417185","predicate":"inputPrivacyKeyPhoneCall","params":[],"type":"InputPrivacyKey"},{"id":"1030105979","predicate":"privacyKeyPhoneCall","params":[],"type":"PrivacyKey"},{"id":"-580219064","predicate":"sendMessageGamePlayAction","params":[],"type":"SendMessageAction"},{"id":"-2048646399","predicate":"phoneCallDiscardReasonMissed","params":[],"type":"PhoneCallDiscardReason"},{"id":"-527056480","predicate":"phoneCallDiscardReasonDisconnect","params":[],"type":"PhoneCallDiscardReason"},{"id":"1471006352","predicate":"phoneCallDiscardReasonHangup","params":[],"type":"PhoneCallDiscardReason"},{"id":"-84416311","predicate":"phoneCallDiscardReasonBusy","params":[],"type":"PhoneCallDiscardReason"},{"id":"1852826908","predicate":"updateDialogPinned","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.0?true"},{"name":"folder_id","type":"flags.1?int"},{"name":"peer","type":"DialogPeer"}],"type":"Update"},{"id":"-99664734","predicate":"updatePinnedDialogs","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.1?int"},{"name":"order","type":"flags.0?Vector"}],"type":"Update"},{"id":"2104790276","predicate":"dataJSON","params":[{"name":"data","type":"string"}],"type":"DataJSON"},{"id":"-2095595325","predicate":"updateBotWebhookJSON","params":[{"name":"data","type":"DataJSON"}],"type":"Update"},{"id":"-1684914010","predicate":"updateBotWebhookJSONQuery","params":[{"name":"query_id","type":"long"},{"name":"data","type":"DataJSON"},{"name":"timeout","type":"int"}],"type":"Update"},{"id":"-886477832","predicate":"labeledPrice","params":[{"name":"label","type":"string"},{"name":"amount","type":"long"}],"type":"LabeledPrice"},{"id":"215516896","predicate":"invoice","params":[{"name":"flags","type":"#"},{"name":"test","type":"flags.0?true"},{"name":"name_requested","type":"flags.1?true"},{"name":"phone_requested","type":"flags.2?true"},{"name":"email_requested","type":"flags.3?true"},{"name":"shipping_address_requested","type":"flags.4?true"},{"name":"flexible","type":"flags.5?true"},{"name":"phone_to_provider","type":"flags.6?true"},{"name":"email_to_provider","type":"flags.7?true"},{"name":"currency","type":"string"},{"name":"prices","type":"Vector"},{"name":"max_tip_amount","type":"flags.8?long"},{"name":"suggested_tip_amounts","type":"flags.8?Vector"}],"type":"Invoice"},{"id":"-646342540","predicate":"inputMediaInvoice","params":[{"name":"flags","type":"#"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.0?InputWebDocument"},{"name":"invoice","type":"Invoice"},{"name":"payload","type":"bytes"},{"name":"provider","type":"string"},{"name":"provider_data","type":"DataJSON"},{"name":"start_param","type":"flags.1?string"}],"type":"InputMedia"},{"id":"-368917890","predicate":"paymentCharge","params":[{"name":"id","type":"string"},{"name":"provider_charge_id","type":"string"}],"type":"PaymentCharge"},{"id":"-1892568281","predicate":"messageActionPaymentSentMe","params":[{"name":"flags","type":"#"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"},{"name":"payload","type":"bytes"},{"name":"info","type":"flags.0?PaymentRequestedInfo"},{"name":"shipping_option_id","type":"flags.1?string"},{"name":"charge","type":"PaymentCharge"}],"type":"MessageAction"},{"id":"-2074799289","predicate":"messageMediaInvoice","params":[{"name":"flags","type":"#"},{"name":"shipping_address_requested","type":"flags.1?true"},{"name":"test","type":"flags.3?true"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.0?WebDocument"},{"name":"receipt_msg_id","type":"flags.2?int"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"},{"name":"start_param","type":"string"}],"type":"MessageMedia"},{"id":"512535275","predicate":"postAddress","params":[{"name":"street_line1","type":"string"},{"name":"street_line2","type":"string"},{"name":"city","type":"string"},{"name":"state","type":"string"},{"name":"country_iso2","type":"string"},{"name":"post_code","type":"string"}],"type":"PostAddress"},{"id":"-1868808300","predicate":"paymentRequestedInfo","params":[{"name":"flags","type":"#"},{"name":"name","type":"flags.0?string"},{"name":"phone","type":"flags.1?string"},{"name":"email","type":"flags.2?string"},{"name":"shipping_address","type":"flags.3?PostAddress"}],"type":"PaymentRequestedInfo"},{"id":"-1344716869","predicate":"keyboardButtonBuy","params":[{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"1080663248","predicate":"messageActionPaymentSent","params":[{"name":"currency","type":"string"},{"name":"total_amount","type":"long"}],"type":"MessageAction"},{"id":"-842892769","predicate":"paymentSavedCredentialsCard","params":[{"name":"id","type":"string"},{"name":"title","type":"string"}],"type":"PaymentSavedCredentials"},{"id":"475467473","predicate":"webDocument","params":[{"name":"url","type":"string"},{"name":"access_hash","type":"long"},{"name":"size","type":"int"},{"name":"mime_type","type":"string"},{"name":"attributes","type":"Vector"}],"type":"WebDocument"},{"id":"-1678949555","predicate":"inputWebDocument","params":[{"name":"url","type":"string"},{"name":"size","type":"int"},{"name":"mime_type","type":"string"},{"name":"attributes","type":"Vector"}],"type":"InputWebDocument"},{"id":"-1036396922","predicate":"inputWebFileLocation","params":[{"name":"url","type":"string"},{"name":"access_hash","type":"long"}],"type":"InputWebFileLocation"},{"id":"568808380","predicate":"upload.webFile","params":[{"name":"size","type":"int"},{"name":"mime_type","type":"string"},{"name":"file_type","type":"storage.FileType"},{"name":"mtime","type":"int"},{"name":"bytes","type":"bytes"}],"type":"upload.WebFile"},{"id":"378828315","predicate":"payments.paymentForm","params":[{"name":"flags","type":"#"},{"name":"can_save_credentials","type":"flags.2?true"},{"name":"password_missing","type":"flags.3?true"},{"name":"form_id","type":"long"},{"name":"bot_id","type":"long"},{"name":"invoice","type":"Invoice"},{"name":"provider_id","type":"long"},{"name":"url","type":"string"},{"name":"native_provider","type":"flags.4?string"},{"name":"native_params","type":"flags.4?DataJSON"},{"name":"saved_info","type":"flags.0?PaymentRequestedInfo"},{"name":"saved_credentials","type":"flags.1?PaymentSavedCredentials"},{"name":"users","type":"Vector"}],"type":"payments.PaymentForm"},{"id":"-784000893","predicate":"payments.validatedRequestedInfo","params":[{"name":"flags","type":"#"},{"name":"id","type":"flags.0?string"},{"name":"shipping_options","type":"flags.1?Vector"}],"type":"payments.ValidatedRequestedInfo"},{"id":"1314881805","predicate":"payments.paymentResult","params":[{"name":"updates","type":"Updates"}],"type":"payments.PaymentResult"},{"id":"1891958275","predicate":"payments.paymentReceipt","params":[{"name":"flags","type":"#"},{"name":"date","type":"int"},{"name":"bot_id","type":"long"},{"name":"provider_id","type":"long"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.2?WebDocument"},{"name":"invoice","type":"Invoice"},{"name":"info","type":"flags.0?PaymentRequestedInfo"},{"name":"shipping","type":"flags.1?ShippingOption"},{"name":"tip_amount","type":"flags.3?long"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"},{"name":"credentials_title","type":"string"},{"name":"users","type":"Vector"}],"type":"payments.PaymentReceipt"},{"id":"-74456004","predicate":"payments.savedInfo","params":[{"name":"flags","type":"#"},{"name":"has_saved_credentials","type":"flags.1?true"},{"name":"saved_info","type":"flags.0?PaymentRequestedInfo"}],"type":"payments.SavedInfo"},{"id":"-1056001329","predicate":"inputPaymentCredentialsSaved","params":[{"name":"id","type":"string"},{"name":"tmp_password","type":"bytes"}],"type":"InputPaymentCredentials"},{"id":"873977640","predicate":"inputPaymentCredentials","params":[{"name":"flags","type":"#"},{"name":"save","type":"flags.0?true"},{"name":"data","type":"DataJSON"}],"type":"InputPaymentCredentials"},{"id":"-614138572","predicate":"account.tmpPassword","params":[{"name":"tmp_password","type":"bytes"},{"name":"valid_until","type":"int"}],"type":"account.TmpPassword"},{"id":"-1239335713","predicate":"shippingOption","params":[{"name":"id","type":"string"},{"name":"title","type":"string"},{"name":"prices","type":"Vector"}],"type":"ShippingOption"},{"id":"-1246823043","predicate":"updateBotShippingQuery","params":[{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"payload","type":"bytes"},{"name":"shipping_address","type":"PostAddress"}],"type":"Update"},{"id":"-1934976362","predicate":"updateBotPrecheckoutQuery","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"user_id","type":"long"},{"name":"payload","type":"bytes"},{"name":"info","type":"flags.0?PaymentRequestedInfo"},{"name":"shipping_option_id","type":"flags.1?string"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"}],"type":"Update"},{"id":"-6249322","predicate":"inputStickerSetItem","params":[{"name":"flags","type":"#"},{"name":"document","type":"InputDocument"},{"name":"emoji","type":"string"},{"name":"mask_coords","type":"flags.0?MaskCoords"}],"type":"InputStickerSetItem"},{"id":"-1425052898","predicate":"updatePhoneCall","params":[{"name":"phone_call","type":"PhoneCall"}],"type":"Update"},{"id":"506920429","predicate":"inputPhoneCall","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputPhoneCall"},{"id":"1399245077","predicate":"phoneCallEmpty","params":[{"name":"id","type":"long"}],"type":"PhoneCall"},{"id":"-987599081","predicate":"phoneCallWaiting","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"protocol","type":"PhoneCallProtocol"},{"name":"receive_date","type":"flags.0?int"}],"type":"PhoneCall"},{"id":"347139340","predicate":"phoneCallRequested","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_a_hash","type":"bytes"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"PhoneCall"},{"id":"912311057","predicate":"phoneCallAccepted","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_b","type":"bytes"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"PhoneCall"},{"id":"-1770029977","predicate":"phoneCall","params":[{"name":"flags","type":"#"},{"name":"p2p_allowed","type":"flags.5?true"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"date","type":"int"},{"name":"admin_id","type":"long"},{"name":"participant_id","type":"long"},{"name":"g_a_or_b","type":"bytes"},{"name":"key_fingerprint","type":"long"},{"name":"protocol","type":"PhoneCallProtocol"},{"name":"connections","type":"Vector"},{"name":"start_date","type":"int"}],"type":"PhoneCall"},{"id":"1355435489","predicate":"phoneCallDiscarded","params":[{"name":"flags","type":"#"},{"name":"need_rating","type":"flags.2?true"},{"name":"need_debug","type":"flags.3?true"},{"name":"video","type":"flags.6?true"},{"name":"id","type":"long"},{"name":"reason","type":"flags.0?PhoneCallDiscardReason"},{"name":"duration","type":"flags.1?int"}],"type":"PhoneCall"},{"id":"-1655957568","predicate":"phoneConnection","params":[{"name":"id","type":"long"},{"name":"ip","type":"string"},{"name":"ipv6","type":"string"},{"name":"port","type":"int"},{"name":"peer_tag","type":"bytes"}],"type":"PhoneConnection"},{"id":"-58224696","predicate":"phoneCallProtocol","params":[{"name":"flags","type":"#"},{"name":"udp_p2p","type":"flags.0?true"},{"name":"udp_reflector","type":"flags.1?true"},{"name":"min_layer","type":"int"},{"name":"max_layer","type":"int"},{"name":"library_versions","type":"Vector"}],"type":"PhoneCallProtocol"},{"id":"-326966976","predicate":"phone.phoneCall","params":[{"name":"phone_call","type":"PhoneCall"},{"name":"users","type":"Vector"}],"type":"phone.PhoneCall"},{"id":"-2134272152","predicate":"inputMessagesFilterPhoneCalls","params":[{"name":"flags","type":"#"},{"name":"missed","type":"flags.0?true"}],"type":"MessagesFilter"},{"id":"-2132731265","predicate":"messageActionPhoneCall","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.2?true"},{"name":"call_id","type":"long"},{"name":"reason","type":"flags.0?PhoneCallDiscardReason"},{"name":"duration","type":"flags.1?int"}],"type":"MessageAction"},{"id":"2054952868","predicate":"inputMessagesFilterRoundVoice","params":[],"type":"MessagesFilter"},{"id":"-1253451181","predicate":"inputMessagesFilterRoundVideo","params":[],"type":"MessagesFilter"},{"id":"-1997373508","predicate":"sendMessageRecordRoundAction","params":[],"type":"SendMessageAction"},{"id":"608050278","predicate":"sendMessageUploadRoundAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"-242427324","predicate":"upload.fileCdnRedirect","params":[{"name":"dc_id","type":"int"},{"name":"file_token","type":"bytes"},{"name":"encryption_key","type":"bytes"},{"name":"encryption_iv","type":"bytes"},{"name":"file_hashes","type":"Vector"}],"type":"upload.File"},{"id":"-290921362","predicate":"upload.cdnFileReuploadNeeded","params":[{"name":"request_token","type":"bytes"}],"type":"upload.CdnFile"},{"id":"-1449145777","predicate":"upload.cdnFile","params":[{"name":"bytes","type":"bytes"}],"type":"upload.CdnFile"},{"id":"-914167110","predicate":"cdnPublicKey","params":[{"name":"dc_id","type":"int"},{"name":"public_key","type":"string"}],"type":"CdnPublicKey"},{"id":"1462101002","predicate":"cdnConfig","params":[{"name":"public_keys","type":"Vector"}],"type":"CdnConfig"},{"id":"-283684427","predicate":"pageBlockChannel","params":[{"name":"channel","type":"Chat"}],"type":"PageBlock"},{"id":"-892239370","predicate":"langPackString","params":[{"name":"key","type":"string"},{"name":"value","type":"string"}],"type":"LangPackString"},{"id":"1816636575","predicate":"langPackStringPluralized","params":[{"name":"flags","type":"#"},{"name":"key","type":"string"},{"name":"zero_value","type":"flags.0?string"},{"name":"one_value","type":"flags.1?string"},{"name":"two_value","type":"flags.2?string"},{"name":"few_value","type":"flags.3?string"},{"name":"many_value","type":"flags.4?string"},{"name":"other_value","type":"string"}],"type":"LangPackString"},{"id":"695856818","predicate":"langPackStringDeleted","params":[{"name":"key","type":"string"}],"type":"LangPackString"},{"id":"-209337866","predicate":"langPackDifference","params":[{"name":"lang_code","type":"string"},{"name":"from_version","type":"int"},{"name":"version","type":"int"},{"name":"strings","type":"Vector"}],"type":"LangPackDifference"},{"id":"-288727837","predicate":"langPackLanguage","params":[{"name":"flags","type":"#"},{"name":"official","type":"flags.0?true"},{"name":"rtl","type":"flags.2?true"},{"name":"beta","type":"flags.3?true"},{"name":"name","type":"string"},{"name":"native_name","type":"string"},{"name":"lang_code","type":"string"},{"name":"base_lang_code","type":"flags.1?string"},{"name":"plural_code","type":"string"},{"name":"strings_count","type":"int"},{"name":"translated_count","type":"int"},{"name":"translations_url","type":"string"}],"type":"LangPackLanguage"},{"id":"1180041828","predicate":"updateLangPackTooLong","params":[{"name":"lang_code","type":"string"}],"type":"Update"},{"id":"1442983757","predicate":"updateLangPack","params":[{"name":"difference","type":"LangPackDifference"}],"type":"Update"},{"id":"885242707","predicate":"channelParticipantAdmin","params":[{"name":"flags","type":"#"},{"name":"can_edit","type":"flags.0?true"},{"name":"self","type":"flags.1?true"},{"name":"user_id","type":"long"},{"name":"inviter_id","type":"flags.1?long"},{"name":"promoted_by","type":"long"},{"name":"date","type":"int"},{"name":"admin_rights","type":"ChatAdminRights"},{"name":"rank","type":"flags.2?string"}],"type":"ChannelParticipant"},{"id":"1844969806","predicate":"channelParticipantBanned","params":[{"name":"flags","type":"#"},{"name":"left","type":"flags.0?true"},{"name":"peer","type":"Peer"},{"name":"kicked_by","type":"long"},{"name":"date","type":"int"},{"name":"banned_rights","type":"ChatBannedRights"}],"type":"ChannelParticipant"},{"id":"338142689","predicate":"channelParticipantsBanned","params":[{"name":"q","type":"string"}],"type":"ChannelParticipantsFilter"},{"id":"106343499","predicate":"channelParticipantsSearch","params":[{"name":"q","type":"string"}],"type":"ChannelParticipantsFilter"},{"id":"-421545947","predicate":"channelAdminLogEventActionChangeTitle","params":[{"name":"prev_value","type":"string"},{"name":"new_value","type":"string"}],"type":"ChannelAdminLogEventAction"},{"id":"1427671598","predicate":"channelAdminLogEventActionChangeAbout","params":[{"name":"prev_value","type":"string"},{"name":"new_value","type":"string"}],"type":"ChannelAdminLogEventAction"},{"id":"1783299128","predicate":"channelAdminLogEventActionChangeUsername","params":[{"name":"prev_value","type":"string"},{"name":"new_value","type":"string"}],"type":"ChannelAdminLogEventAction"},{"id":"1129042607","predicate":"channelAdminLogEventActionChangePhoto","params":[{"name":"prev_photo","type":"Photo"},{"name":"new_photo","type":"Photo"}],"type":"ChannelAdminLogEventAction"},{"id":"460916654","predicate":"channelAdminLogEventActionToggleInvites","params":[{"name":"new_value","type":"Bool"}],"type":"ChannelAdminLogEventAction"},{"id":"648939889","predicate":"channelAdminLogEventActionToggleSignatures","params":[{"name":"new_value","type":"Bool"}],"type":"ChannelAdminLogEventAction"},{"id":"-370660328","predicate":"channelAdminLogEventActionUpdatePinned","params":[{"name":"message","type":"Message"}],"type":"ChannelAdminLogEventAction"},{"id":"1889215493","predicate":"channelAdminLogEventActionEditMessage","params":[{"name":"prev_message","type":"Message"},{"name":"new_message","type":"Message"}],"type":"ChannelAdminLogEventAction"},{"id":"1121994683","predicate":"channelAdminLogEventActionDeleteMessage","params":[{"name":"message","type":"Message"}],"type":"ChannelAdminLogEventAction"},{"id":"405815507","predicate":"channelAdminLogEventActionParticipantJoin","params":[],"type":"ChannelAdminLogEventAction"},{"id":"-124291086","predicate":"channelAdminLogEventActionParticipantLeave","params":[],"type":"ChannelAdminLogEventAction"},{"id":"-484690728","predicate":"channelAdminLogEventActionParticipantInvite","params":[{"name":"participant","type":"ChannelParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"-422036098","predicate":"channelAdminLogEventActionParticipantToggleBan","params":[{"name":"prev_participant","type":"ChannelParticipant"},{"name":"new_participant","type":"ChannelParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"-714643696","predicate":"channelAdminLogEventActionParticipantToggleAdmin","params":[{"name":"prev_participant","type":"ChannelParticipant"},{"name":"new_participant","type":"ChannelParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"531458253","predicate":"channelAdminLogEvent","params":[{"name":"id","type":"long"},{"name":"date","type":"int"},{"name":"user_id","type":"long"},{"name":"action","type":"ChannelAdminLogEventAction"}],"type":"ChannelAdminLogEvent"},{"id":"-309659827","predicate":"channels.adminLogResults","params":[{"name":"events","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"channels.AdminLogResults"},{"id":"-368018716","predicate":"channelAdminLogEventsFilter","params":[{"name":"flags","type":"#"},{"name":"join","type":"flags.0?true"},{"name":"leave","type":"flags.1?true"},{"name":"invite","type":"flags.2?true"},{"name":"ban","type":"flags.3?true"},{"name":"unban","type":"flags.4?true"},{"name":"kick","type":"flags.5?true"},{"name":"unkick","type":"flags.6?true"},{"name":"promote","type":"flags.7?true"},{"name":"demote","type":"flags.8?true"},{"name":"info","type":"flags.9?true"},{"name":"settings","type":"flags.10?true"},{"name":"pinned","type":"flags.11?true"},{"name":"edit","type":"flags.12?true"},{"name":"delete","type":"flags.13?true"},{"name":"group_call","type":"flags.14?true"},{"name":"invites","type":"flags.15?true"},{"name":"send","type":"flags.16?true"}],"type":"ChannelAdminLogEventsFilter"},{"id":"511092620","predicate":"topPeerCategoryPhoneCalls","params":[],"type":"TopPeerCategory"},{"id":"-2143067670","predicate":"pageBlockAudio","params":[{"name":"audio_id","type":"long"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"1558266229","predicate":"popularContact","params":[{"name":"client_id","type":"long"},{"name":"importers","type":"int"}],"type":"PopularContact"},{"id":"1200788123","predicate":"messageActionScreenshotTaken","params":[],"type":"MessageAction"},{"id":"-1634752813","predicate":"messages.favedStickersNotModified","params":[],"type":"messages.FavedStickers"},{"id":"750063767","predicate":"messages.favedStickers","params":[{"name":"hash","type":"long"},{"name":"packs","type":"Vector"},{"name":"stickers","type":"Vector"}],"type":"messages.FavedStickers"},{"id":"-451831443","predicate":"updateFavedStickers","params":[],"type":"Update"},{"id":"1153291573","predicate":"updateChannelReadMessagesContents","params":[{"name":"channel_id","type":"long"},{"name":"messages","type":"Vector"}],"type":"Update"},{"id":"-1040652646","predicate":"inputMessagesFilterMyMentions","params":[],"type":"MessagesFilter"},{"id":"1887741886","predicate":"updateContactsReset","params":[],"type":"Update"},{"id":"-1312568665","predicate":"channelAdminLogEventActionChangeStickerSet","params":[{"name":"prev_stickerset","type":"InputStickerSet"},{"name":"new_stickerset","type":"InputStickerSet"}],"type":"ChannelAdminLogEventAction"},{"id":"-85549226","predicate":"messageActionCustomAction","params":[{"name":"message","type":"string"}],"type":"MessageAction"},{"id":"178373535","predicate":"inputPaymentCredentialsApplePay","params":[{"name":"payment_data","type":"DataJSON"}],"type":"InputPaymentCredentials"},{"id":"-419271411","predicate":"inputMessagesFilterGeo","params":[],"type":"MessagesFilter"},{"id":"-530392189","predicate":"inputMessagesFilterContacts","params":[],"type":"MessagesFilter"},{"id":"-1304443240","predicate":"updateChannelAvailableMessages","params":[{"name":"channel_id","type":"long"},{"name":"available_min_id","type":"int"}],"type":"Update"},{"id":"1599903217","predicate":"channelAdminLogEventActionTogglePreHistoryHidden","params":[{"name":"new_value","type":"Bool"}],"type":"ChannelAdminLogEventAction"},{"id":"-1759532989","predicate":"inputMediaGeoLive","params":[{"name":"flags","type":"#"},{"name":"stopped","type":"flags.0?true"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"heading","type":"flags.2?int"},{"name":"period","type":"flags.1?int"},{"name":"proximity_notification_radius","type":"flags.3?int"}],"type":"InputMedia"},{"id":"-1186937242","predicate":"messageMediaGeoLive","params":[{"name":"flags","type":"#"},{"name":"geo","type":"GeoPoint"},{"name":"heading","type":"flags.0?int"},{"name":"period","type":"int"},{"name":"proximity_notification_radius","type":"flags.1?int"}],"type":"MessageMedia"},{"id":"1189204285","predicate":"recentMeUrlUnknown","params":[{"name":"url","type":"string"}],"type":"RecentMeUrl"},{"id":"-1188296222","predicate":"recentMeUrlUser","params":[{"name":"url","type":"string"},{"name":"user_id","type":"long"}],"type":"RecentMeUrl"},{"id":"-1294306862","predicate":"recentMeUrlChat","params":[{"name":"url","type":"string"},{"name":"chat_id","type":"long"}],"type":"RecentMeUrl"},{"id":"-347535331","predicate":"recentMeUrlChatInvite","params":[{"name":"url","type":"string"},{"name":"chat_invite","type":"ChatInvite"}],"type":"RecentMeUrl"},{"id":"-1140172836","predicate":"recentMeUrlStickerSet","params":[{"name":"url","type":"string"},{"name":"set","type":"StickerSetCovered"}],"type":"RecentMeUrl"},{"id":"235081943","predicate":"help.recentMeUrls","params":[{"name":"urls","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"help.RecentMeUrls"},{"id":"-266911767","predicate":"channels.channelParticipantsNotModified","params":[],"type":"channels.ChannelParticipants"},{"id":"1951620897","predicate":"messages.messagesNotModified","params":[{"name":"count","type":"int"}],"type":"messages.Messages"},{"id":"482797855","predicate":"inputSingleMedia","params":[{"name":"flags","type":"#"},{"name":"media","type":"InputMedia"},{"name":"random_id","type":"long"},{"name":"message","type":"string"},{"name":"entities","type":"flags.0?Vector"}],"type":"InputSingleMedia"},{"id":"-1493633966","predicate":"webAuthorization","params":[{"name":"hash","type":"long"},{"name":"bot_id","type":"long"},{"name":"domain","type":"string"},{"name":"browser","type":"string"},{"name":"platform","type":"string"},{"name":"date_created","type":"int"},{"name":"date_active","type":"int"},{"name":"ip","type":"string"},{"name":"region","type":"string"}],"type":"WebAuthorization"},{"id":"-313079300","predicate":"account.webAuthorizations","params":[{"name":"authorizations","type":"Vector"},{"name":"users","type":"Vector"}],"type":"account.WebAuthorizations"},{"id":"-1502174430","predicate":"inputMessageID","params":[{"name":"id","type":"int"}],"type":"InputMessage"},{"id":"-1160215659","predicate":"inputMessageReplyTo","params":[{"name":"id","type":"int"}],"type":"InputMessage"},{"id":"-2037963464","predicate":"inputMessagePinned","params":[],"type":"InputMessage"},{"id":"-1687559349","predicate":"messageEntityPhone","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1280209983","predicate":"messageEntityCashtag","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-1410748418","predicate":"messageActionBotAllowed","params":[{"name":"domain","type":"string"}],"type":"MessageAction"},{"id":"-55902537","predicate":"inputDialogPeer","params":[{"name":"peer","type":"InputPeer"}],"type":"InputDialogPeer"},{"id":"-445792507","predicate":"dialogPeer","params":[{"name":"peer","type":"Peer"}],"type":"DialogPeer"},{"id":"223655517","predicate":"messages.foundStickerSetsNotModified","params":[],"type":"messages.FoundStickerSets"},{"id":"-1963942446","predicate":"messages.foundStickerSets","params":[{"name":"hash","type":"long"},{"name":"sets","type":"Vector"}],"type":"messages.FoundStickerSets"},{"id":"1648543603","predicate":"fileHash","params":[{"name":"offset","type":"int"},{"name":"limit","type":"int"},{"name":"hash","type":"bytes"}],"type":"FileHash"},{"id":"-104284986","predicate":"webDocumentNoProxy","params":[{"name":"url","type":"string"},{"name":"size","type":"int"},{"name":"mime_type","type":"string"},{"name":"attributes","type":"Vector"}],"type":"WebDocument"},{"id":"1968737087","predicate":"inputClientProxy","params":[{"name":"address","type":"string"},{"name":"port","type":"int"}],"type":"InputClientProxy"},{"id":"-483352705","predicate":"help.termsOfServiceUpdateEmpty","params":[{"name":"expires","type":"int"}],"type":"help.TermsOfServiceUpdate"},{"id":"686618977","predicate":"help.termsOfServiceUpdate","params":[{"name":"expires","type":"int"},{"name":"terms_of_service","type":"help.TermsOfService"}],"type":"help.TermsOfServiceUpdate"},{"id":"859091184","predicate":"inputSecureFileUploaded","params":[{"name":"id","type":"long"},{"name":"parts","type":"int"},{"name":"md5_checksum","type":"string"},{"name":"file_hash","type":"bytes"},{"name":"secret","type":"bytes"}],"type":"InputSecureFile"},{"id":"1399317950","predicate":"inputSecureFile","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputSecureFile"},{"id":"-876089816","predicate":"inputSecureFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputFileLocation"},{"id":"1679398724","predicate":"secureFileEmpty","params":[],"type":"SecureFile"},{"id":"-534283678","predicate":"secureFile","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"size","type":"int"},{"name":"dc_id","type":"int"},{"name":"date","type":"int"},{"name":"file_hash","type":"bytes"},{"name":"secret","type":"bytes"}],"type":"SecureFile"},{"id":"-1964327229","predicate":"secureData","params":[{"name":"data","type":"bytes"},{"name":"data_hash","type":"bytes"},{"name":"secret","type":"bytes"}],"type":"SecureData"},{"id":"2103482845","predicate":"securePlainPhone","params":[{"name":"phone","type":"string"}],"type":"SecurePlainData"},{"id":"569137759","predicate":"securePlainEmail","params":[{"name":"email","type":"string"}],"type":"SecurePlainData"},{"id":"-1658158621","predicate":"secureValueTypePersonalDetails","params":[],"type":"SecureValueType"},{"id":"1034709504","predicate":"secureValueTypePassport","params":[],"type":"SecureValueType"},{"id":"115615172","predicate":"secureValueTypeDriverLicense","params":[],"type":"SecureValueType"},{"id":"-1596951477","predicate":"secureValueTypeIdentityCard","params":[],"type":"SecureValueType"},{"id":"-1717268701","predicate":"secureValueTypeInternalPassport","params":[],"type":"SecureValueType"},{"id":"-874308058","predicate":"secureValueTypeAddress","params":[],"type":"SecureValueType"},{"id":"-63531698","predicate":"secureValueTypeUtilityBill","params":[],"type":"SecureValueType"},{"id":"-1995211763","predicate":"secureValueTypeBankStatement","params":[],"type":"SecureValueType"},{"id":"-1954007928","predicate":"secureValueTypeRentalAgreement","params":[],"type":"SecureValueType"},{"id":"-1713143702","predicate":"secureValueTypePassportRegistration","params":[],"type":"SecureValueType"},{"id":"-368907213","predicate":"secureValueTypeTemporaryRegistration","params":[],"type":"SecureValueType"},{"id":"-1289704741","predicate":"secureValueTypePhone","params":[],"type":"SecureValueType"},{"id":"-1908627474","predicate":"secureValueTypeEmail","params":[],"type":"SecureValueType"},{"id":"411017418","predicate":"secureValue","params":[{"name":"flags","type":"#"},{"name":"type","type":"SecureValueType"},{"name":"data","type":"flags.0?SecureData"},{"name":"front_side","type":"flags.1?SecureFile"},{"name":"reverse_side","type":"flags.2?SecureFile"},{"name":"selfie","type":"flags.3?SecureFile"},{"name":"translation","type":"flags.6?Vector"},{"name":"files","type":"flags.4?Vector"},{"name":"plain_data","type":"flags.5?SecurePlainData"},{"name":"hash","type":"bytes"}],"type":"SecureValue"},{"id":"-618540889","predicate":"inputSecureValue","params":[{"name":"flags","type":"#"},{"name":"type","type":"SecureValueType"},{"name":"data","type":"flags.0?SecureData"},{"name":"front_side","type":"flags.1?InputSecureFile"},{"name":"reverse_side","type":"flags.2?InputSecureFile"},{"name":"selfie","type":"flags.3?InputSecureFile"},{"name":"translation","type":"flags.6?Vector"},{"name":"files","type":"flags.4?Vector"},{"name":"plain_data","type":"flags.5?SecurePlainData"}],"type":"InputSecureValue"},{"id":"-316748368","predicate":"secureValueHash","params":[{"name":"type","type":"SecureValueType"},{"name":"hash","type":"bytes"}],"type":"SecureValueHash"},{"id":"-391902247","predicate":"secureValueErrorData","params":[{"name":"type","type":"SecureValueType"},{"name":"data_hash","type":"bytes"},{"name":"field","type":"string"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"12467706","predicate":"secureValueErrorFrontSide","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"-2037765467","predicate":"secureValueErrorReverseSide","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"-449327402","predicate":"secureValueErrorSelfie","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"2054162547","predicate":"secureValueErrorFile","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"1717706985","predicate":"secureValueErrorFiles","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"Vector"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"871426631","predicate":"secureCredentialsEncrypted","params":[{"name":"data","type":"bytes"},{"name":"hash","type":"bytes"},{"name":"secret","type":"bytes"}],"type":"SecureCredentialsEncrypted"},{"id":"-1389486888","predicate":"account.authorizationForm","params":[{"name":"flags","type":"#"},{"name":"required_types","type":"Vector"},{"name":"values","type":"Vector"},{"name":"errors","type":"Vector"},{"name":"users","type":"Vector"},{"name":"privacy_policy_url","type":"flags.0?string"}],"type":"account.AuthorizationForm"},{"id":"-2128640689","predicate":"account.sentEmailCode","params":[{"name":"email_pattern","type":"string"},{"name":"length","type":"int"}],"type":"account.SentEmailCode"},{"id":"455635795","predicate":"messageActionSecureValuesSentMe","params":[{"name":"values","type":"Vector"},{"name":"credentials","type":"SecureCredentialsEncrypted"}],"type":"MessageAction"},{"id":"-648257196","predicate":"messageActionSecureValuesSent","params":[{"name":"types","type":"Vector"}],"type":"MessageAction"},{"id":"1722786150","predicate":"help.deepLinkInfoEmpty","params":[],"type":"help.DeepLinkInfo"},{"id":"1783556146","predicate":"help.deepLinkInfo","params":[{"name":"flags","type":"#"},{"name":"update_app","type":"flags.0?true"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"}],"type":"help.DeepLinkInfo"},{"id":"289586518","predicate":"savedPhoneContact","params":[{"name":"phone","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"date","type":"int"}],"type":"SavedContact"},{"id":"1304052993","predicate":"account.takeout","params":[{"name":"id","type":"long"}],"type":"account.Takeout"},{"id":"700340377","predicate":"inputTakeoutFileLocation","params":[],"type":"InputFileLocation"},{"id":"-513517117","predicate":"updateDialogUnreadMark","params":[{"name":"flags","type":"#"},{"name":"unread","type":"flags.0?true"},{"name":"peer","type":"DialogPeer"}],"type":"Update"},{"id":"-253500010","predicate":"messages.dialogsNotModified","params":[{"name":"count","type":"int"}],"type":"messages.Dialogs"},{"id":"-1625153079","predicate":"inputWebFileGeoPointLocation","params":[{"name":"geo_point","type":"InputGeoPoint"},{"name":"access_hash","type":"long"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"zoom","type":"int"},{"name":"scale","type":"int"}],"type":"InputWebFileLocation"},{"id":"-1255369827","predicate":"contacts.topPeersDisabled","params":[],"type":"contacts.TopPeers"},{"id":"-1685456582","predicate":"inputReportReasonCopyright","params":[],"type":"ReportReason"},{"id":"-732254058","predicate":"passwordKdfAlgoUnknown","params":[],"type":"PasswordKdfAlgo"},{"id":"4883767","predicate":"securePasswordKdfAlgoUnknown","params":[],"type":"SecurePasswordKdfAlgo"},{"id":"-1141711456","predicate":"securePasswordKdfAlgoPBKDF2HMACSHA512iter100000","params":[{"name":"salt","type":"bytes"}],"type":"SecurePasswordKdfAlgo"},{"id":"-2042159726","predicate":"securePasswordKdfAlgoSHA512","params":[{"name":"salt","type":"bytes"}],"type":"SecurePasswordKdfAlgo"},{"id":"354925740","predicate":"secureSecretSettings","params":[{"name":"secure_algo","type":"SecurePasswordKdfAlgo"},{"name":"secure_secret","type":"bytes"},{"name":"secure_secret_id","type":"long"}],"type":"SecureSecretSettings"},{"id":"982592842","predicate":"passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow","params":[{"name":"salt1","type":"bytes"},{"name":"salt2","type":"bytes"},{"name":"g","type":"int"},{"name":"p","type":"bytes"}],"type":"PasswordKdfAlgo"},{"id":"-1736378792","predicate":"inputCheckPasswordEmpty","params":[],"type":"InputCheckPasswordSRP"},{"id":"-763367294","predicate":"inputCheckPasswordSRP","params":[{"name":"srp_id","type":"long"},{"name":"A","type":"bytes"},{"name":"M1","type":"bytes"}],"type":"InputCheckPasswordSRP"},{"id":"-2036501105","predicate":"secureValueError","params":[{"name":"type","type":"SecureValueType"},{"name":"hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"-1592506512","predicate":"secureValueErrorTranslationFile","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"bytes"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"878931416","predicate":"secureValueErrorTranslationFiles","params":[{"name":"type","type":"SecureValueType"},{"name":"file_hash","type":"Vector"},{"name":"text","type":"string"}],"type":"SecureValueError"},{"id":"-2103600678","predicate":"secureRequiredType","params":[{"name":"flags","type":"#"},{"name":"native_names","type":"flags.0?true"},{"name":"selfie_required","type":"flags.1?true"},{"name":"translation_required","type":"flags.2?true"},{"name":"type","type":"SecureValueType"}],"type":"SecureRequiredType"},{"id":"41187252","predicate":"secureRequiredTypeOneOf","params":[{"name":"types","type":"Vector"}],"type":"SecureRequiredType"},{"id":"-1078332329","predicate":"help.passportConfigNotModified","params":[],"type":"help.PassportConfig"},{"id":"-1600596305","predicate":"help.passportConfig","params":[{"name":"hash","type":"int"},{"name":"countries_langs","type":"DataJSON"}],"type":"help.PassportConfig"},{"id":"488313413","predicate":"inputAppEvent","params":[{"name":"time","type":"double"},{"name":"type","type":"string"},{"name":"peer","type":"long"},{"name":"data","type":"JSONValue"}],"type":"InputAppEvent"},{"id":"-1059185703","predicate":"jsonObjectValue","params":[{"name":"key","type":"string"},{"name":"value","type":"JSONValue"}],"type":"JSONObjectValue"},{"id":"1064139624","predicate":"jsonNull","params":[],"type":"JSONValue"},{"id":"-952869270","predicate":"jsonBool","params":[{"name":"value","type":"Bool"}],"type":"JSONValue"},{"id":"736157604","predicate":"jsonNumber","params":[{"name":"value","type":"double"}],"type":"JSONValue"},{"id":"-1222740358","predicate":"jsonString","params":[{"name":"value","type":"string"}],"type":"JSONValue"},{"id":"-146520221","predicate":"jsonArray","params":[{"name":"value","type":"Vector"}],"type":"JSONValue"},{"id":"-1715350371","predicate":"jsonObject","params":[{"name":"value","type":"Vector"}],"type":"JSONValue"},{"id":"-1311015810","predicate":"inputNotifyBroadcasts","params":[],"type":"InputNotifyPeer"},{"id":"-703403793","predicate":"notifyBroadcasts","params":[],"type":"NotifyPeer"},{"id":"-311786236","predicate":"textSubscript","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"-939827711","predicate":"textSuperscript","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"55281185","predicate":"textMarked","params":[{"name":"text","type":"RichText"}],"type":"RichText"},{"id":"483104362","predicate":"textPhone","params":[{"name":"text","type":"RichText"},{"name":"phone","type":"string"}],"type":"RichText"},{"id":"136105807","predicate":"textImage","params":[{"name":"document_id","type":"long"},{"name":"w","type":"int"},{"name":"h","type":"int"}],"type":"RichText"},{"id":"504660880","predicate":"pageBlockKicker","params":[{"name":"text","type":"RichText"}],"type":"PageBlock"},{"id":"878078826","predicate":"pageTableCell","params":[{"name":"flags","type":"#"},{"name":"header","type":"flags.0?true"},{"name":"align_center","type":"flags.3?true"},{"name":"align_right","type":"flags.4?true"},{"name":"valign_middle","type":"flags.5?true"},{"name":"valign_bottom","type":"flags.6?true"},{"name":"text","type":"flags.7?RichText"},{"name":"colspan","type":"flags.1?int"},{"name":"rowspan","type":"flags.2?int"}],"type":"PageTableCell"},{"id":"-524237339","predicate":"pageTableRow","params":[{"name":"cells","type":"Vector"}],"type":"PageTableRow"},{"id":"-1085412734","predicate":"pageBlockTable","params":[{"name":"flags","type":"#"},{"name":"bordered","type":"flags.0?true"},{"name":"striped","type":"flags.1?true"},{"name":"title","type":"RichText"},{"name":"rows","type":"Vector"}],"type":"PageBlock"},{"id":"1869903447","predicate":"pageCaption","params":[{"name":"text","type":"RichText"},{"name":"credit","type":"RichText"}],"type":"PageCaption"},{"id":"-1188055347","predicate":"pageListItemText","params":[{"name":"text","type":"RichText"}],"type":"PageListItem"},{"id":"635466748","predicate":"pageListItemBlocks","params":[{"name":"blocks","type":"Vector"}],"type":"PageListItem"},{"id":"1577484359","predicate":"pageListOrderedItemText","params":[{"name":"num","type":"string"},{"name":"text","type":"RichText"}],"type":"PageListOrderedItem"},{"id":"-1730311882","predicate":"pageListOrderedItemBlocks","params":[{"name":"num","type":"string"},{"name":"blocks","type":"Vector"}],"type":"PageListOrderedItem"},{"id":"-1702174239","predicate":"pageBlockOrderedList","params":[{"name":"items","type":"Vector"}],"type":"PageBlock"},{"id":"1987480557","predicate":"pageBlockDetails","params":[{"name":"flags","type":"#"},{"name":"open","type":"flags.0?true"},{"name":"blocks","type":"Vector"},{"name":"title","type":"RichText"}],"type":"PageBlock"},{"id":"-1282352120","predicate":"pageRelatedArticle","params":[{"name":"flags","type":"#"},{"name":"url","type":"string"},{"name":"webpage_id","type":"long"},{"name":"title","type":"flags.0?string"},{"name":"description","type":"flags.1?string"},{"name":"photo_id","type":"flags.2?long"},{"name":"author","type":"flags.3?string"},{"name":"published_date","type":"flags.4?int"}],"type":"PageRelatedArticle"},{"id":"370236054","predicate":"pageBlockRelatedArticles","params":[{"name":"title","type":"RichText"},{"name":"articles","type":"Vector"}],"type":"PageBlock"},{"id":"-1538310410","predicate":"pageBlockMap","params":[{"name":"geo","type":"GeoPoint"},{"name":"zoom","type":"int"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"caption","type":"PageCaption"}],"type":"PageBlock"},{"id":"-1738178803","predicate":"page","params":[{"name":"flags","type":"#"},{"name":"part","type":"flags.0?true"},{"name":"rtl","type":"flags.1?true"},{"name":"v2","type":"flags.2?true"},{"name":"url","type":"string"},{"name":"blocks","type":"Vector"},{"name":"photos","type":"Vector"},{"name":"documents","type":"Vector"},{"name":"views","type":"flags.3?int"}],"type":"Page"},{"id":"-610373422","predicate":"inputPrivacyKeyPhoneP2P","params":[],"type":"InputPrivacyKey"},{"id":"961092808","predicate":"privacyKeyPhoneP2P","params":[],"type":"PrivacyKey"},{"id":"894777186","predicate":"textAnchor","params":[{"name":"text","type":"RichText"},{"name":"name","type":"string"}],"type":"RichText"},{"id":"-1945767479","predicate":"help.supportName","params":[{"name":"name","type":"string"}],"type":"help.SupportName"},{"id":"-206688531","predicate":"help.userInfoEmpty","params":[],"type":"help.UserInfo"},{"id":"32192344","predicate":"help.userInfo","params":[{"name":"message","type":"string"},{"name":"entities","type":"Vector"},{"name":"author","type":"string"},{"name":"date","type":"int"}],"type":"help.UserInfo"},{"id":"-202219658","predicate":"messageActionContactSignUp","params":[],"type":"MessageAction"},{"id":"-1398708869","predicate":"updateMessagePoll","params":[{"name":"flags","type":"#"},{"name":"poll_id","type":"long"},{"name":"poll","type":"flags.0?Poll"},{"name":"results","type":"PollResults"}],"type":"Update"},{"id":"1823064809","predicate":"pollAnswer","params":[{"name":"text","type":"string"},{"name":"option","type":"bytes"}],"type":"PollAnswer"},{"id":"-2032041631","predicate":"poll","params":[{"name":"id","type":"long"},{"name":"flags","type":"#"},{"name":"closed","type":"flags.0?true"},{"name":"public_voters","type":"flags.1?true"},{"name":"multiple_choice","type":"flags.2?true"},{"name":"quiz","type":"flags.3?true"},{"name":"question","type":"string"},{"name":"answers","type":"Vector"},{"name":"close_period","type":"flags.4?int"},{"name":"close_date","type":"flags.5?int"}],"type":"Poll"},{"id":"997055186","predicate":"pollAnswerVoters","params":[{"name":"flags","type":"#"},{"name":"chosen","type":"flags.0?true"},{"name":"correct","type":"flags.1?true"},{"name":"option","type":"bytes"},{"name":"voters","type":"int"}],"type":"PollAnswerVoters"},{"id":"-591909213","predicate":"pollResults","params":[{"name":"flags","type":"#"},{"name":"min","type":"flags.0?true"},{"name":"results","type":"flags.1?Vector"},{"name":"total_voters","type":"flags.2?int"},{"name":"recent_voters","type":"flags.3?Vector"},{"name":"solution","type":"flags.4?string"},{"name":"solution_entities","type":"flags.4?Vector"}],"type":"PollResults"},{"id":"261416433","predicate":"inputMediaPoll","params":[{"name":"flags","type":"#"},{"name":"poll","type":"Poll"},{"name":"correct_answers","type":"flags.0?Vector"},{"name":"solution","type":"flags.1?string"},{"name":"solution_entities","type":"flags.1?Vector"}],"type":"InputMedia"},{"id":"1272375192","predicate":"messageMediaPoll","params":[{"name":"poll","type":"Poll"},{"name":"results","type":"PollResults"}],"type":"MessageMedia"},{"id":"-264117680","predicate":"chatOnlines","params":[{"name":"onlines","type":"int"}],"type":"ChatOnlines"},{"id":"1202287072","predicate":"statsURL","params":[{"name":"url","type":"string"}],"type":"StatsURL"},{"id":"-525288402","predicate":"photoStrippedSize","params":[{"name":"type","type":"string"},{"name":"bytes","type":"bytes"}],"type":"PhotoSize"},{"id":"1605510357","predicate":"chatAdminRights","params":[{"name":"flags","type":"#"},{"name":"change_info","type":"flags.0?true"},{"name":"post_messages","type":"flags.1?true"},{"name":"edit_messages","type":"flags.2?true"},{"name":"delete_messages","type":"flags.3?true"},{"name":"ban_users","type":"flags.4?true"},{"name":"invite_users","type":"flags.5?true"},{"name":"pin_messages","type":"flags.7?true"},{"name":"add_admins","type":"flags.9?true"},{"name":"anonymous","type":"flags.10?true"},{"name":"manage_call","type":"flags.11?true"},{"name":"other","type":"flags.12?true"}],"type":"ChatAdminRights"},{"id":"-1626209256","predicate":"chatBannedRights","params":[{"name":"flags","type":"#"},{"name":"view_messages","type":"flags.0?true"},{"name":"send_messages","type":"flags.1?true"},{"name":"send_media","type":"flags.2?true"},{"name":"send_stickers","type":"flags.3?true"},{"name":"send_gifs","type":"flags.4?true"},{"name":"send_games","type":"flags.5?true"},{"name":"send_inline","type":"flags.6?true"},{"name":"embed_links","type":"flags.7?true"},{"name":"send_polls","type":"flags.8?true"},{"name":"change_info","type":"flags.10?true"},{"name":"invite_users","type":"flags.15?true"},{"name":"pin_messages","type":"flags.17?true"},{"name":"until_date","type":"int"}],"type":"ChatBannedRights"},{"id":"1421875280","predicate":"updateChatDefaultBannedRights","params":[{"name":"peer","type":"Peer"},{"name":"default_banned_rights","type":"ChatBannedRights"},{"name":"version","type":"int"}],"type":"Update"},{"id":"-433014407","predicate":"inputWallPaper","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputWallPaper"},{"id":"1913199744","predicate":"inputWallPaperSlug","params":[{"name":"slug","type":"string"}],"type":"InputWallPaper"},{"id":"-1150621555","predicate":"channelParticipantsContacts","params":[{"name":"q","type":"string"}],"type":"ChannelParticipantsFilter"},{"id":"771095562","predicate":"channelAdminLogEventActionDefaultBannedRights","params":[{"name":"prev_banned_rights","type":"ChatBannedRights"},{"name":"new_banned_rights","type":"ChatBannedRights"}],"type":"ChannelAdminLogEventAction"},{"id":"-1895328189","predicate":"channelAdminLogEventActionStopPoll","params":[{"name":"message","type":"Message"}],"type":"ChannelAdminLogEventAction"},{"id":"471437699","predicate":"account.wallPapersNotModified","params":[],"type":"account.WallPapers"},{"id":"-842824308","predicate":"account.wallPapers","params":[{"name":"hash","type":"long"},{"name":"wallpapers","type":"Vector"}],"type":"account.WallPapers"},{"id":"-557924733","predicate":"codeSettings","params":[{"name":"flags","type":"#"},{"name":"allow_flashcall","type":"flags.0?true"},{"name":"current_number","type":"flags.1?true"},{"name":"allow_app_hash","type":"flags.4?true"}],"type":"CodeSettings"},{"id":"499236004","predicate":"wallPaperSettings","params":[{"name":"flags","type":"#"},{"name":"blur","type":"flags.1?true"},{"name":"motion","type":"flags.2?true"},{"name":"background_color","type":"flags.0?int"},{"name":"second_background_color","type":"flags.4?int"},{"name":"third_background_color","type":"flags.5?int"},{"name":"fourth_background_color","type":"flags.6?int"},{"name":"intensity","type":"flags.3?int"},{"name":"rotation","type":"flags.4?int"}],"type":"WallPaperSettings"},{"id":"-532532493","predicate":"autoDownloadSettings","params":[{"name":"flags","type":"#"},{"name":"disabled","type":"flags.0?true"},{"name":"video_preload_large","type":"flags.1?true"},{"name":"audio_preload_next","type":"flags.2?true"},{"name":"phonecalls_less_data","type":"flags.3?true"},{"name":"photo_size_max","type":"int"},{"name":"video_size_max","type":"int"},{"name":"file_size_max","type":"int"},{"name":"video_upload_maxbitrate","type":"int"}],"type":"AutoDownloadSettings"},{"id":"1674235686","predicate":"account.autoDownloadSettings","params":[{"name":"low","type":"AutoDownloadSettings"},{"name":"medium","type":"AutoDownloadSettings"},{"name":"high","type":"AutoDownloadSettings"}],"type":"account.AutoDownloadSettings"},{"id":"-709641735","predicate":"emojiKeyword","params":[{"name":"keyword","type":"string"},{"name":"emoticons","type":"Vector"}],"type":"EmojiKeyword"},{"id":"594408994","predicate":"emojiKeywordDeleted","params":[{"name":"keyword","type":"string"},{"name":"emoticons","type":"Vector"}],"type":"EmojiKeyword"},{"id":"1556570557","predicate":"emojiKeywordsDifference","params":[{"name":"lang_code","type":"string"},{"name":"from_version","type":"int"},{"name":"version","type":"int"},{"name":"keywords","type":"Vector"}],"type":"EmojiKeywordsDifference"},{"id":"-1519029347","predicate":"emojiURL","params":[{"name":"url","type":"string"}],"type":"EmojiURL"},{"id":"-1275374751","predicate":"emojiLanguage","params":[{"name":"lang_code","type":"string"}],"type":"EmojiLanguage"},{"id":"-1529000952","predicate":"inputPrivacyKeyForwards","params":[],"type":"InputPrivacyKey"},{"id":"1777096355","predicate":"privacyKeyForwards","params":[],"type":"PrivacyKey"},{"id":"1461304012","predicate":"inputPrivacyKeyProfilePhoto","params":[],"type":"InputPrivacyKey"},{"id":"-1777000467","predicate":"privacyKeyProfilePhoto","params":[],"type":"PrivacyKey"},{"id":"1075322878","predicate":"inputPhotoFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"thumb_size","type":"string"}],"type":"InputFileLocation"},{"id":"-667654413","predicate":"inputPhotoLegacyFileLocation","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"file_reference","type":"bytes"},{"name":"volume_id","type":"long"},{"name":"local_id","type":"int"},{"name":"secret","type":"long"}],"type":"InputFileLocation"},{"id":"925204121","predicate":"inputPeerPhotoFileLocation","params":[{"name":"flags","type":"#"},{"name":"big","type":"flags.0?true"},{"name":"peer","type":"InputPeer"},{"name":"photo_id","type":"long"}],"type":"InputFileLocation"},{"id":"-1652231205","predicate":"inputStickerSetThumb","params":[{"name":"stickerset","type":"InputStickerSet"},{"name":"thumb_version","type":"int"}],"type":"InputFileLocation"},{"id":"-11252123","predicate":"folder","params":[{"name":"flags","type":"#"},{"name":"autofill_new_broadcasts","type":"flags.0?true"},{"name":"autofill_public_groups","type":"flags.1?true"},{"name":"autofill_new_correspondents","type":"flags.2?true"},{"name":"id","type":"int"},{"name":"title","type":"string"},{"name":"photo","type":"flags.3?ChatPhoto"}],"type":"Folder"},{"id":"1908216652","predicate":"dialogFolder","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.2?true"},{"name":"folder","type":"Folder"},{"name":"peer","type":"Peer"},{"name":"top_message","type":"int"},{"name":"unread_muted_peers_count","type":"int"},{"name":"unread_unmuted_peers_count","type":"int"},{"name":"unread_muted_messages_count","type":"int"},{"name":"unread_unmuted_messages_count","type":"int"}],"type":"Dialog"},{"id":"1684014375","predicate":"inputDialogPeerFolder","params":[{"name":"folder_id","type":"int"}],"type":"InputDialogPeer"},{"id":"1363483106","predicate":"dialogPeerFolder","params":[{"name":"folder_id","type":"int"}],"type":"DialogPeer"},{"id":"-70073706","predicate":"inputFolderPeer","params":[{"name":"peer","type":"InputPeer"},{"name":"folder_id","type":"int"}],"type":"InputFolderPeer"},{"id":"-373643672","predicate":"folderPeer","params":[{"name":"peer","type":"Peer"},{"name":"folder_id","type":"int"}],"type":"FolderPeer"},{"id":"422972864","predicate":"updateFolderPeers","params":[{"name":"folder_peers","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"497305826","predicate":"inputUserFromMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"user_id","type":"long"}],"type":"InputUser"},{"id":"1536380829","predicate":"inputChannelFromMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"channel_id","type":"long"}],"type":"InputChannel"},{"id":"-1468331492","predicate":"inputPeerUserFromMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"user_id","type":"long"}],"type":"InputPeer"},{"id":"-1121318848","predicate":"inputPeerChannelFromMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"channel_id","type":"long"}],"type":"InputPeer"},{"id":"55761658","predicate":"inputPrivacyKeyPhoneNumber","params":[],"type":"InputPrivacyKey"},{"id":"-778378131","predicate":"privacyKeyPhoneNumber","params":[],"type":"PrivacyKey"},{"id":"-1472172887","predicate":"topPeerCategoryForwardUsers","params":[],"type":"TopPeerCategory"},{"id":"-68239120","predicate":"topPeerCategoryForwardChats","params":[],"type":"TopPeerCategory"},{"id":"84703944","predicate":"channelAdminLogEventActionChangeLinkedChat","params":[{"name":"prev_value","type":"long"},{"name":"new_value","type":"long"}],"type":"ChannelAdminLogEventAction"},{"id":"-398136321","predicate":"messages.searchCounter","params":[{"name":"flags","type":"#"},{"name":"inexact","type":"flags.1?true"},{"name":"filter","type":"MessagesFilter"},{"name":"count","type":"int"}],"type":"messages.SearchCounter"},{"id":"280464681","predicate":"keyboardButtonUrlAuth","params":[{"name":"flags","type":"#"},{"name":"text","type":"string"},{"name":"fwd_text","type":"flags.0?string"},{"name":"url","type":"string"},{"name":"button_id","type":"int"}],"type":"KeyboardButton"},{"id":"-802258988","predicate":"inputKeyboardButtonUrlAuth","params":[{"name":"flags","type":"#"},{"name":"request_write_access","type":"flags.0?true"},{"name":"text","type":"string"},{"name":"fwd_text","type":"flags.1?string"},{"name":"url","type":"string"},{"name":"bot","type":"InputUser"}],"type":"KeyboardButton"},{"id":"-1831650802","predicate":"urlAuthResultRequest","params":[{"name":"flags","type":"#"},{"name":"request_write_access","type":"flags.0?true"},{"name":"bot","type":"User"},{"name":"domain","type":"string"}],"type":"UrlAuthResult"},{"id":"-1886646706","predicate":"urlAuthResultAccepted","params":[{"name":"url","type":"string"}],"type":"UrlAuthResult"},{"id":"-1445536993","predicate":"urlAuthResultDefault","params":[],"type":"UrlAuthResult"},{"id":"-2079962673","predicate":"inputPrivacyValueAllowChatParticipants","params":[{"name":"chats","type":"Vector"}],"type":"InputPrivacyRule"},{"id":"-380694650","predicate":"inputPrivacyValueDisallowChatParticipants","params":[{"name":"chats","type":"Vector"}],"type":"InputPrivacyRule"},{"id":"1796427406","predicate":"privacyValueAllowChatParticipants","params":[{"name":"chats","type":"Vector"}],"type":"PrivacyRule"},{"id":"1103656293","predicate":"privacyValueDisallowChatParticipants","params":[{"name":"chats","type":"Vector"}],"type":"PrivacyRule"},{"id":"-1672577397","predicate":"messageEntityUnderline","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-1090087980","predicate":"messageEntityStrike","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"34469328","predicate":"messageEntityBlockquote","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"1786671974","predicate":"updatePeerSettings","params":[{"name":"peer","type":"Peer"},{"name":"settings","type":"PeerSettings"}],"type":"Update"},{"id":"-1078612597","predicate":"channelLocationEmpty","params":[],"type":"ChannelLocation"},{"id":"547062491","predicate":"channelLocation","params":[{"name":"geo_point","type":"GeoPoint"},{"name":"address","type":"string"}],"type":"ChannelLocation"},{"id":"-901375139","predicate":"peerLocated","params":[{"name":"peer","type":"Peer"},{"name":"expires","type":"int"},{"name":"distance","type":"int"}],"type":"PeerLocated"},{"id":"-1263546448","predicate":"updatePeerLocated","params":[{"name":"peers","type":"Vector"}],"type":"Update"},{"id":"241923758","predicate":"channelAdminLogEventActionChangeLocation","params":[{"name":"prev_value","type":"ChannelLocation"},{"name":"new_value","type":"ChannelLocation"}],"type":"ChannelAdminLogEventAction"},{"id":"-606798099","predicate":"inputReportReasonGeoIrrelevant","params":[],"type":"ReportReason"},{"id":"1401984889","predicate":"channelAdminLogEventActionToggleSlowMode","params":[{"name":"prev_value","type":"int"},{"name":"new_value","type":"int"}],"type":"ChannelAdminLogEventAction"},{"id":"1148485274","predicate":"auth.authorizationSignUpRequired","params":[{"name":"flags","type":"#"},{"name":"terms_of_service","type":"flags.0?help.TermsOfService"}],"type":"auth.Authorization"},{"id":"-666824391","predicate":"payments.paymentVerificationNeeded","params":[{"name":"url","type":"string"}],"type":"payments.PaymentResult"},{"id":"42402760","predicate":"inputStickerSetAnimatedEmoji","params":[],"type":"InputStickerSet"},{"id":"967122427","predicate":"updateNewScheduledMessage","params":[{"name":"message","type":"Message"}],"type":"Update"},{"id":"-1870238482","predicate":"updateDeleteScheduledMessages","params":[{"name":"peer","type":"Peer"},{"name":"messages","type":"Vector"}],"type":"Update"},{"id":"-797791052","predicate":"restrictionReason","params":[{"name":"platform","type":"string"},{"name":"reason","type":"string"},{"name":"text","type":"string"}],"type":"RestrictionReason"},{"id":"1012306921","predicate":"inputTheme","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputTheme"},{"id":"-175567375","predicate":"inputThemeSlug","params":[{"name":"slug","type":"string"}],"type":"InputTheme"},{"id":"-402474788","predicate":"theme","params":[{"name":"flags","type":"#"},{"name":"creator","type":"flags.0?true"},{"name":"default","type":"flags.1?true"},{"name":"for_chat","type":"flags.5?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"slug","type":"string"},{"name":"title","type":"string"},{"name":"document","type":"flags.2?Document"},{"name":"settings","type":"flags.3?ThemeSettings"},{"name":"installs_count","type":"flags.4?int"}],"type":"Theme"},{"id":"-199313886","predicate":"account.themesNotModified","params":[],"type":"account.Themes"},{"id":"-1707242387","predicate":"account.themes","params":[{"name":"hash","type":"long"},{"name":"themes","type":"Vector"}],"type":"account.Themes"},{"id":"-2112423005","predicate":"updateTheme","params":[{"name":"theme","type":"Theme"}],"type":"Update"},{"id":"-786326563","predicate":"inputPrivacyKeyAddedByPhone","params":[],"type":"InputPrivacyKey"},{"id":"1124062251","predicate":"privacyKeyAddedByPhone","params":[],"type":"PrivacyKey"},{"id":"-2027964103","predicate":"updateGeoLiveViewed","params":[{"name":"peer","type":"Peer"},{"name":"msg_id","type":"int"}],"type":"Update"},{"id":"1448076945","predicate":"updateLoginToken","params":[],"type":"Update"},{"id":"1654593920","predicate":"auth.loginToken","params":[{"name":"expires","type":"int"},{"name":"token","type":"bytes"}],"type":"auth.LoginToken"},{"id":"110008598","predicate":"auth.loginTokenMigrateTo","params":[{"name":"dc_id","type":"int"},{"name":"token","type":"bytes"}],"type":"auth.LoginToken"},{"id":"957176926","predicate":"auth.loginTokenSuccess","params":[{"name":"authorization","type":"auth.Authorization"}],"type":"auth.LoginToken"},{"id":"1474462241","predicate":"account.contentSettings","params":[{"name":"flags","type":"#"},{"name":"sensitive_enabled","type":"flags.0?true"},{"name":"sensitive_can_change","type":"flags.1?true"}],"type":"account.ContentSettings"},{"id":"-1456996667","predicate":"messages.inactiveChats","params":[{"name":"dates","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.InactiveChats"},{"id":"-1012849566","predicate":"baseThemeClassic","params":[],"type":"BaseTheme"},{"id":"-69724536","predicate":"baseThemeDay","params":[],"type":"BaseTheme"},{"id":"-1212997976","predicate":"baseThemeNight","params":[],"type":"BaseTheme"},{"id":"1834973166","predicate":"baseThemeTinted","params":[],"type":"BaseTheme"},{"id":"1527845466","predicate":"baseThemeArctic","params":[],"type":"BaseTheme"},{"id":"-1770371538","predicate":"inputWallPaperNoFile","params":[{"name":"id","type":"long"}],"type":"InputWallPaper"},{"id":"-528465642","predicate":"wallPaperNoFile","params":[{"name":"id","type":"long"},{"name":"flags","type":"#"},{"name":"default","type":"flags.1?true"},{"name":"dark","type":"flags.4?true"},{"name":"settings","type":"flags.2?WallPaperSettings"}],"type":"WallPaper"},{"id":"-1881255857","predicate":"inputThemeSettings","params":[{"name":"flags","type":"#"},{"name":"message_colors_animated","type":"flags.2?true"},{"name":"base_theme","type":"BaseTheme"},{"name":"accent_color","type":"int"},{"name":"outbox_accent_color","type":"flags.3?int"},{"name":"message_colors","type":"flags.0?Vector"},{"name":"wallpaper","type":"flags.1?InputWallPaper"},{"name":"wallpaper_settings","type":"flags.1?WallPaperSettings"}],"type":"InputThemeSettings"},{"id":"-94849324","predicate":"themeSettings","params":[{"name":"flags","type":"#"},{"name":"message_colors_animated","type":"flags.2?true"},{"name":"base_theme","type":"BaseTheme"},{"name":"accent_color","type":"int"},{"name":"outbox_accent_color","type":"flags.3?int"},{"name":"message_colors","type":"flags.0?Vector"},{"name":"wallpaper","type":"flags.1?WallPaper"}],"type":"ThemeSettings"},{"id":"1421174295","predicate":"webPageAttributeTheme","params":[{"name":"flags","type":"#"},{"name":"documents","type":"flags.0?Vector"},{"name":"settings","type":"flags.1?ThemeSettings"}],"type":"WebPageAttribute"},{"id":"274961865","predicate":"updateMessagePollVote","params":[{"name":"poll_id","type":"long"},{"name":"user_id","type":"long"},{"name":"options","type":"Vector"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"886196148","predicate":"messageUserVote","params":[{"name":"user_id","type":"long"},{"name":"option","type":"bytes"},{"name":"date","type":"int"}],"type":"MessageUserVote"},{"id":"1017491692","predicate":"messageUserVoteInputOption","params":[{"name":"user_id","type":"long"},{"name":"date","type":"int"}],"type":"MessageUserVote"},{"id":"-1973033641","predicate":"messageUserVoteMultiple","params":[{"name":"user_id","type":"long"},{"name":"options","type":"Vector"},{"name":"date","type":"int"}],"type":"MessageUserVote"},{"id":"136574537","predicate":"messages.votesList","params":[{"name":"flags","type":"#"},{"name":"count","type":"int"},{"name":"votes","type":"Vector"},{"name":"users","type":"Vector"},{"name":"next_offset","type":"flags.0?string"}],"type":"messages.VotesList"},{"id":"-1144565411","predicate":"keyboardButtonRequestPoll","params":[{"name":"flags","type":"#"},{"name":"quiz","type":"flags.0?Bool"},{"name":"text","type":"string"}],"type":"KeyboardButton"},{"id":"1981704948","predicate":"messageEntityBankCard","params":[{"name":"offset","type":"int"},{"name":"length","type":"int"}],"type":"MessageEntity"},{"id":"-177732982","predicate":"bankCardOpenUrl","params":[{"name":"url","type":"string"},{"name":"name","type":"string"}],"type":"BankCardOpenUrl"},{"id":"1042605427","predicate":"payments.bankCardData","params":[{"name":"title","type":"string"},{"name":"open_urls","type":"Vector"}],"type":"payments.BankCardData"},{"id":"-118740917","predicate":"peerSelfLocated","params":[{"name":"expires","type":"int"}],"type":"PeerLocated"},{"id":"1949890536","predicate":"dialogFilter","params":[{"name":"flags","type":"#"},{"name":"contacts","type":"flags.0?true"},{"name":"non_contacts","type":"flags.1?true"},{"name":"groups","type":"flags.2?true"},{"name":"broadcasts","type":"flags.3?true"},{"name":"bots","type":"flags.4?true"},{"name":"exclude_muted","type":"flags.11?true"},{"name":"exclude_read","type":"flags.12?true"},{"name":"exclude_archived","type":"flags.13?true"},{"name":"id","type":"int"},{"name":"title","type":"string"},{"name":"emoticon","type":"flags.25?string"},{"name":"pinned_peers","type":"Vector"},{"name":"include_peers","type":"Vector"},{"name":"exclude_peers","type":"Vector"}],"type":"DialogFilter"},{"id":"2004110666","predicate":"dialogFilterSuggested","params":[{"name":"filter","type":"DialogFilter"},{"name":"description","type":"string"}],"type":"DialogFilterSuggested"},{"id":"654302845","predicate":"updateDialogFilter","params":[{"name":"flags","type":"#"},{"name":"id","type":"int"},{"name":"filter","type":"flags.0?DialogFilter"}],"type":"Update"},{"id":"-1512627963","predicate":"updateDialogFilterOrder","params":[{"name":"order","type":"Vector"}],"type":"Update"},{"id":"889491791","predicate":"updateDialogFilters","params":[],"type":"Update"},{"id":"-1237848657","predicate":"statsDateRangeDays","params":[{"name":"min_date","type":"int"},{"name":"max_date","type":"int"}],"type":"StatsDateRangeDays"},{"id":"-884757282","predicate":"statsAbsValueAndPrev","params":[{"name":"current","type":"double"},{"name":"previous","type":"double"}],"type":"StatsAbsValueAndPrev"},{"id":"-875679776","predicate":"statsPercentValue","params":[{"name":"part","type":"double"},{"name":"total","type":"double"}],"type":"StatsPercentValue"},{"id":"1244130093","predicate":"statsGraphAsync","params":[{"name":"token","type":"string"}],"type":"StatsGraph"},{"id":"-1092839390","predicate":"statsGraphError","params":[{"name":"error","type":"string"}],"type":"StatsGraph"},{"id":"-1901828938","predicate":"statsGraph","params":[{"name":"flags","type":"#"},{"name":"json","type":"DataJSON"},{"name":"zoom_token","type":"flags.0?string"}],"type":"StatsGraph"},{"id":"-1387279939","predicate":"messageInteractionCounters","params":[{"name":"msg_id","type":"int"},{"name":"views","type":"int"},{"name":"forwards","type":"int"}],"type":"MessageInteractionCounters"},{"id":"-1107852396","predicate":"stats.broadcastStats","params":[{"name":"period","type":"StatsDateRangeDays"},{"name":"followers","type":"StatsAbsValueAndPrev"},{"name":"views_per_post","type":"StatsAbsValueAndPrev"},{"name":"shares_per_post","type":"StatsAbsValueAndPrev"},{"name":"enabled_notifications","type":"StatsPercentValue"},{"name":"growth_graph","type":"StatsGraph"},{"name":"followers_graph","type":"StatsGraph"},{"name":"mute_graph","type":"StatsGraph"},{"name":"top_hours_graph","type":"StatsGraph"},{"name":"interactions_graph","type":"StatsGraph"},{"name":"iv_interactions_graph","type":"StatsGraph"},{"name":"views_by_source_graph","type":"StatsGraph"},{"name":"new_followers_by_source_graph","type":"StatsGraph"},{"name":"languages_graph","type":"StatsGraph"},{"name":"recent_message_interactions","type":"Vector"}],"type":"stats.BroadcastStats"},{"id":"-428884101","predicate":"inputMediaDice","params":[{"name":"emoticon","type":"string"}],"type":"InputMedia"},{"id":"1065280907","predicate":"messageMediaDice","params":[{"name":"value","type":"int"},{"name":"emoticon","type":"string"}],"type":"MessageMedia"},{"id":"-427863538","predicate":"inputStickerSetDice","params":[{"name":"emoticon","type":"string"}],"type":"InputStickerSet"},{"id":"-1728664459","predicate":"help.promoDataEmpty","params":[{"name":"expires","type":"int"}],"type":"help.PromoData"},{"id":"-1942390465","predicate":"help.promoData","params":[{"name":"flags","type":"#"},{"name":"proxy","type":"flags.0?true"},{"name":"expires","type":"int"},{"name":"peer","type":"Peer"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"psa_type","type":"flags.1?string"},{"name":"psa_message","type":"flags.2?string"}],"type":"help.PromoData"},{"id":"-567037804","predicate":"videoSize","params":[{"name":"flags","type":"#"},{"name":"type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"size","type":"int"},{"name":"video_start_ts","type":"flags.0?double"}],"type":"VideoSize"},{"id":"643940105","predicate":"updatePhoneCallSignalingData","params":[{"name":"phone_call_id","type":"long"},{"name":"data","type":"bytes"}],"type":"Update"},{"id":"1634294960","predicate":"chatInvitePeek","params":[{"name":"chat","type":"Chat"},{"name":"expires","type":"int"}],"type":"ChatInvite"},{"id":"-1660637285","predicate":"statsGroupTopPoster","params":[{"name":"user_id","type":"long"},{"name":"messages","type":"int"},{"name":"avg_chars","type":"int"}],"type":"StatsGroupTopPoster"},{"id":"-682079097","predicate":"statsGroupTopAdmin","params":[{"name":"user_id","type":"long"},{"name":"deleted","type":"int"},{"name":"kicked","type":"int"},{"name":"banned","type":"int"}],"type":"StatsGroupTopAdmin"},{"id":"1398765469","predicate":"statsGroupTopInviter","params":[{"name":"user_id","type":"long"},{"name":"invitations","type":"int"}],"type":"StatsGroupTopInviter"},{"id":"-276825834","predicate":"stats.megagroupStats","params":[{"name":"period","type":"StatsDateRangeDays"},{"name":"members","type":"StatsAbsValueAndPrev"},{"name":"messages","type":"StatsAbsValueAndPrev"},{"name":"viewers","type":"StatsAbsValueAndPrev"},{"name":"posters","type":"StatsAbsValueAndPrev"},{"name":"growth_graph","type":"StatsGraph"},{"name":"members_graph","type":"StatsGraph"},{"name":"new_members_by_source_graph","type":"StatsGraph"},{"name":"languages_graph","type":"StatsGraph"},{"name":"messages_graph","type":"StatsGraph"},{"name":"actions_graph","type":"StatsGraph"},{"name":"top_hours_graph","type":"StatsGraph"},{"name":"weekdays_graph","type":"StatsGraph"},{"name":"top_posters","type":"Vector"},{"name":"top_admins","type":"Vector"},{"name":"top_inviters","type":"Vector"},{"name":"users","type":"Vector"}],"type":"stats.MegagroupStats"},{"id":"-1096616924","predicate":"globalPrivacySettings","params":[{"name":"flags","type":"#"},{"name":"archive_and_mute_new_noncontact_peers","type":"flags.0?Bool"}],"type":"GlobalPrivacySettings"},{"id":"1667228533","predicate":"phoneConnectionWebrtc","params":[{"name":"flags","type":"#"},{"name":"turn","type":"flags.0?true"},{"name":"stun","type":"flags.1?true"},{"name":"id","type":"long"},{"name":"ip","type":"string"},{"name":"ipv6","type":"string"},{"name":"port","type":"int"},{"name":"username","type":"string"},{"name":"password","type":"string"}],"type":"PhoneConnection"},{"id":"1107543535","predicate":"help.countryCode","params":[{"name":"flags","type":"#"},{"name":"country_code","type":"string"},{"name":"prefixes","type":"flags.0?Vector"},{"name":"patterns","type":"flags.1?Vector"}],"type":"help.CountryCode"},{"id":"-1014526429","predicate":"help.country","params":[{"name":"flags","type":"#"},{"name":"hidden","type":"flags.0?true"},{"name":"iso2","type":"string"},{"name":"default_name","type":"string"},{"name":"name","type":"flags.1?string"},{"name":"country_codes","type":"Vector"}],"type":"help.Country"},{"id":"-1815339214","predicate":"help.countriesListNotModified","params":[],"type":"help.CountriesList"},{"id":"-2016381538","predicate":"help.countriesList","params":[{"name":"countries","type":"Vector"},{"name":"hash","type":"int"}],"type":"help.CountriesList"},{"id":"1163625789","predicate":"messageViews","params":[{"name":"flags","type":"#"},{"name":"views","type":"flags.0?int"},{"name":"forwards","type":"flags.1?int"},{"name":"replies","type":"flags.2?MessageReplies"}],"type":"MessageViews"},{"id":"-761649164","predicate":"updateChannelMessageForwards","params":[{"name":"channel_id","type":"long"},{"name":"id","type":"int"},{"name":"forwards","type":"int"}],"type":"Update"},{"id":"-96535659","predicate":"photoSizeProgressive","params":[{"name":"type","type":"string"},{"name":"w","type":"int"},{"name":"h","type":"int"},{"name":"sizes","type":"Vector"}],"type":"PhotoSize"},{"id":"-1228606141","predicate":"messages.messageViews","params":[{"name":"views","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.MessageViews"},{"id":"-693004986","predicate":"updateReadChannelDiscussionInbox","params":[{"name":"flags","type":"#"},{"name":"channel_id","type":"long"},{"name":"top_msg_id","type":"int"},{"name":"read_max_id","type":"int"},{"name":"broadcast_id","type":"flags.0?long"},{"name":"broadcast_post","type":"flags.0?int"}],"type":"Update"},{"id":"1767677564","predicate":"updateReadChannelDiscussionOutbox","params":[{"name":"channel_id","type":"long"},{"name":"top_msg_id","type":"int"},{"name":"read_max_id","type":"int"}],"type":"Update"},{"id":"-1506535550","predicate":"messages.discussionMessage","params":[{"name":"flags","type":"#"},{"name":"messages","type":"Vector"},{"name":"max_id","type":"flags.0?int"},{"name":"read_inbox_max_id","type":"flags.1?int"},{"name":"read_outbox_max_id","type":"flags.2?int"},{"name":"unread_count","type":"int"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.DiscussionMessage"},{"id":"-1495959709","predicate":"messageReplyHeader","params":[{"name":"flags","type":"#"},{"name":"reply_to_msg_id","type":"int"},{"name":"reply_to_peer_id","type":"flags.0?Peer"},{"name":"reply_to_top_id","type":"flags.1?int"}],"type":"MessageReplyHeader"},{"id":"-2083123262","predicate":"messageReplies","params":[{"name":"flags","type":"#"},{"name":"comments","type":"flags.0?true"},{"name":"replies","type":"int"},{"name":"replies_pts","type":"int"},{"name":"recent_repliers","type":"flags.1?Vector"},{"name":"channel_id","type":"flags.0?long"},{"name":"max_id","type":"flags.2?int"},{"name":"read_max_id","type":"flags.3?int"}],"type":"MessageReplies"},{"id":"610945826","predicate":"updatePeerBlocked","params":[{"name":"peer_id","type":"Peer"},{"name":"blocked","type":"Bool"}],"type":"Update"},{"id":"-386039788","predicate":"peerBlocked","params":[{"name":"peer_id","type":"Peer"},{"name":"date","type":"int"}],"type":"PeerBlocked"},{"id":"-1937192669","predicate":"updateChannelUserTyping","params":[{"name":"flags","type":"#"},{"name":"channel_id","type":"long"},{"name":"top_msg_id","type":"flags.0?int"},{"name":"from_id","type":"Peer"},{"name":"action","type":"SendMessageAction"}],"type":"Update"},{"id":"-1392895362","predicate":"inputMessageCallbackQuery","params":[{"name":"id","type":"int"},{"name":"query_id","type":"long"}],"type":"InputMessage"},{"id":"453242886","predicate":"channelParticipantLeft","params":[{"name":"peer","type":"Peer"}],"type":"ChannelParticipant"},{"id":"-531931925","predicate":"channelParticipantsMentions","params":[{"name":"flags","type":"#"},{"name":"q","type":"flags.0?string"},{"name":"top_msg_id","type":"flags.1?int"}],"type":"ChannelParticipantsFilter"},{"id":"-309990731","predicate":"updatePinnedMessages","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.0?true"},{"name":"peer","type":"Peer"},{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"1538885128","predicate":"updatePinnedChannelMessages","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.0?true"},{"name":"channel_id","type":"long"},{"name":"messages","type":"Vector"},{"name":"pts","type":"int"},{"name":"pts_count","type":"int"}],"type":"Update"},{"id":"464520273","predicate":"inputMessagesFilterPinned","params":[],"type":"MessagesFilter"},{"id":"-1986399595","predicate":"stats.messageStats","params":[{"name":"views_graph","type":"StatsGraph"}],"type":"stats.MessageStats"},{"id":"-1730095465","predicate":"messageActionGeoProximityReached","params":[{"name":"from_id","type":"Peer"},{"name":"to_id","type":"Peer"},{"name":"distance","type":"int"}],"type":"MessageAction"},{"id":"-668906175","predicate":"photoPathSize","params":[{"name":"type","type":"string"},{"name":"bytes","type":"bytes"}],"type":"PhotoSize"},{"id":"-651419003","predicate":"speakingInGroupCallAction","params":[],"type":"SendMessageAction"},{"id":"2004925620","predicate":"groupCallDiscarded","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"duration","type":"int"}],"type":"GroupCall"},{"id":"-711498484","predicate":"groupCall","params":[{"name":"flags","type":"#"},{"name":"join_muted","type":"flags.1?true"},{"name":"can_change_join_muted","type":"flags.2?true"},{"name":"join_date_asc","type":"flags.6?true"},{"name":"schedule_start_subscribed","type":"flags.8?true"},{"name":"can_start_video","type":"flags.9?true"},{"name":"record_video_active","type":"flags.11?true"},{"name":"id","type":"long"},{"name":"access_hash","type":"long"},{"name":"participants_count","type":"int"},{"name":"title","type":"flags.3?string"},{"name":"stream_dc_id","type":"flags.4?int"},{"name":"record_start_date","type":"flags.5?int"},{"name":"schedule_date","type":"flags.7?int"},{"name":"unmuted_video_count","type":"flags.10?int"},{"name":"unmuted_video_limit","type":"int"},{"name":"version","type":"int"}],"type":"GroupCall"},{"id":"-659913713","predicate":"inputGroupCall","params":[{"name":"id","type":"long"},{"name":"access_hash","type":"long"}],"type":"InputGroupCall"},{"id":"2047704898","predicate":"messageActionGroupCall","params":[{"name":"flags","type":"#"},{"name":"call","type":"InputGroupCall"},{"name":"duration","type":"flags.0?int"}],"type":"MessageAction"},{"id":"1345295095","predicate":"messageActionInviteToGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"users","type":"Vector"}],"type":"MessageAction"},{"id":"-341428482","predicate":"groupCallParticipant","params":[{"name":"flags","type":"#"},{"name":"muted","type":"flags.0?true"},{"name":"left","type":"flags.1?true"},{"name":"can_self_unmute","type":"flags.2?true"},{"name":"just_joined","type":"flags.4?true"},{"name":"versioned","type":"flags.5?true"},{"name":"min","type":"flags.8?true"},{"name":"muted_by_you","type":"flags.9?true"},{"name":"volume_by_admin","type":"flags.10?true"},{"name":"self","type":"flags.12?true"},{"name":"video_joined","type":"flags.15?true"},{"name":"peer","type":"Peer"},{"name":"date","type":"int"},{"name":"active_date","type":"flags.3?int"},{"name":"source","type":"int"},{"name":"volume","type":"flags.7?int"},{"name":"about","type":"flags.11?string"},{"name":"raise_hand_rating","type":"flags.13?long"},{"name":"video","type":"flags.6?GroupCallParticipantVideo"},{"name":"presentation","type":"flags.14?GroupCallParticipantVideo"}],"type":"GroupCallParticipant"},{"id":"-124097970","predicate":"updateChat","params":[{"name":"chat_id","type":"long"}],"type":"Update"},{"id":"-219423922","predicate":"updateGroupCallParticipants","params":[{"name":"call","type":"InputGroupCall"},{"name":"participants","type":"Vector"},{"name":"version","type":"int"}],"type":"Update"},{"id":"347227392","predicate":"updateGroupCall","params":[{"name":"chat_id","type":"long"},{"name":"call","type":"GroupCall"}],"type":"Update"},{"id":"-1636664659","predicate":"phone.groupCall","params":[{"name":"call","type":"GroupCall"},{"name":"participants","type":"Vector"},{"name":"participants_next_offset","type":"string"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"phone.GroupCall"},{"id":"-193506890","predicate":"phone.groupParticipants","params":[{"name":"count","type":"int"},{"name":"participants","type":"Vector"},{"name":"next_offset","type":"string"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"},{"name":"version","type":"int"}],"type":"phone.GroupParticipants"},{"id":"813821341","predicate":"inlineQueryPeerTypeSameBotPM","params":[],"type":"InlineQueryPeerType"},{"id":"-2093215828","predicate":"inlineQueryPeerTypePM","params":[],"type":"InlineQueryPeerType"},{"id":"-681130742","predicate":"inlineQueryPeerTypeChat","params":[],"type":"InlineQueryPeerType"},{"id":"1589952067","predicate":"inlineQueryPeerTypeMegagroup","params":[],"type":"InlineQueryPeerType"},{"id":"1664413338","predicate":"inlineQueryPeerTypeBroadcast","params":[],"type":"InlineQueryPeerType"},{"id":"589338437","predicate":"channelAdminLogEventActionStartGroupCall","params":[{"name":"call","type":"InputGroupCall"}],"type":"ChannelAdminLogEventAction"},{"id":"-610299584","predicate":"channelAdminLogEventActionDiscardGroupCall","params":[{"name":"call","type":"InputGroupCall"}],"type":"ChannelAdminLogEventAction"},{"id":"-115071790","predicate":"channelAdminLogEventActionParticipantMute","params":[{"name":"participant","type":"GroupCallParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"-431740480","predicate":"channelAdminLogEventActionParticipantUnmute","params":[{"name":"participant","type":"GroupCallParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"1456906823","predicate":"channelAdminLogEventActionToggleGroupCallSetting","params":[{"name":"join_muted","type":"Bool"}],"type":"ChannelAdminLogEventAction"},{"id":"-1966921727","predicate":"inputPaymentCredentialsGooglePay","params":[{"name":"payment_token","type":"DataJSON"}],"type":"InputPaymentCredentials"},{"id":"375566091","predicate":"messages.historyImport","params":[{"name":"id","type":"long"}],"type":"messages.HistoryImport"},{"id":"-606432698","predicate":"sendMessageHistoryImportAction","params":[{"name":"progress","type":"int"}],"type":"SendMessageAction"},{"id":"1578088377","predicate":"messages.historyImportParsed","params":[{"name":"flags","type":"#"},{"name":"pm","type":"flags.0?true"},{"name":"group","type":"flags.1?true"},{"name":"title","type":"flags.2?string"}],"type":"messages.HistoryImportParsed"},{"id":"-170010905","predicate":"inputReportReasonFake","params":[],"type":"ReportReason"},{"id":"-275956116","predicate":"messages.affectedFoundMessages","params":[{"name":"pts","type":"int"},{"name":"pts_count","type":"int"},{"name":"offset","type":"int"},{"name":"messages","type":"Vector"}],"type":"messages.AffectedFoundMessages"},{"id":"-1441072131","predicate":"messageActionSetMessagesTTL","params":[{"name":"period","type":"int"}],"type":"MessageAction"},{"id":"-1147422299","predicate":"updatePeerHistoryTTL","params":[{"name":"flags","type":"#"},{"name":"peer","type":"Peer"},{"name":"ttl_period","type":"flags.0?int"}],"type":"Update"},{"id":"-796432838","predicate":"updateChatParticipant","params":[{"name":"flags","type":"#"},{"name":"chat_id","type":"long"},{"name":"date","type":"int"},{"name":"actor_id","type":"long"},{"name":"user_id","type":"long"},{"name":"prev_participant","type":"flags.0?ChatParticipant"},{"name":"new_participant","type":"flags.1?ChatParticipant"},{"name":"invite","type":"flags.2?ExportedChatInvite"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"-1738720581","predicate":"updateChannelParticipant","params":[{"name":"flags","type":"#"},{"name":"channel_id","type":"long"},{"name":"date","type":"int"},{"name":"actor_id","type":"long"},{"name":"user_id","type":"long"},{"name":"prev_participant","type":"flags.0?ChannelParticipant"},{"name":"new_participant","type":"flags.1?ChannelParticipant"},{"name":"invite","type":"flags.2?ExportedChatInvite"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"-997782967","predicate":"updateBotStopped","params":[{"name":"user_id","type":"long"},{"name":"date","type":"int"},{"name":"stopped","type":"Bool"},{"name":"qts","type":"int"}],"type":"Update"},{"id":"190633460","predicate":"chatInviteImporter","params":[{"name":"user_id","type":"long"},{"name":"date","type":"int"}],"type":"ChatInviteImporter"},{"id":"-1111085620","predicate":"messages.exportedChatInvites","params":[{"name":"count","type":"int"},{"name":"invites","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.ExportedChatInvites"},{"id":"410107472","predicate":"messages.exportedChatInvite","params":[{"name":"invite","type":"ExportedChatInvite"},{"name":"users","type":"Vector"}],"type":"messages.ExportedChatInvite"},{"id":"572915951","predicate":"messages.exportedChatInviteReplaced","params":[{"name":"invite","type":"ExportedChatInvite"},{"name":"new_invite","type":"ExportedChatInvite"},{"name":"users","type":"Vector"}],"type":"messages.ExportedChatInvite"},{"id":"-2118733814","predicate":"messages.chatInviteImporters","params":[{"name":"count","type":"int"},{"name":"importers","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.ChatInviteImporters"},{"id":"-219353309","predicate":"chatAdminWithInvites","params":[{"name":"admin_id","type":"long"},{"name":"invites_count","type":"int"},{"name":"revoked_invites_count","type":"int"}],"type":"ChatAdminWithInvites"},{"id":"-1231326505","predicate":"messages.chatAdminsWithInvites","params":[{"name":"admins","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.ChatAdminsWithInvites"},{"id":"1557846647","predicate":"channelAdminLogEventActionParticipantJoinByInvite","params":[{"name":"invite","type":"ExportedChatInvite"}],"type":"ChannelAdminLogEventAction"},{"id":"1515256996","predicate":"channelAdminLogEventActionExportedInviteDelete","params":[{"name":"invite","type":"ExportedChatInvite"}],"type":"ChannelAdminLogEventAction"},{"id":"1091179342","predicate":"channelAdminLogEventActionExportedInviteRevoke","params":[{"name":"invite","type":"ExportedChatInvite"}],"type":"ChannelAdminLogEventAction"},{"id":"-384910503","predicate":"channelAdminLogEventActionExportedInviteEdit","params":[{"name":"prev_invite","type":"ExportedChatInvite"},{"name":"new_invite","type":"ExportedChatInvite"}],"type":"ChannelAdminLogEventAction"},{"id":"1048537159","predicate":"channelAdminLogEventActionParticipantVolume","params":[{"name":"participant","type":"GroupCallParticipant"}],"type":"ChannelAdminLogEventAction"},{"id":"1855199800","predicate":"channelAdminLogEventActionChangeHistoryTTL","params":[{"name":"prev_value","type":"int"},{"name":"new_value","type":"int"}],"type":"ChannelAdminLogEventAction"},{"id":"-1571952873","predicate":"messages.checkedHistoryImportPeer","params":[{"name":"confirm_text","type":"string"}],"type":"messages.CheckedHistoryImportPeer"},{"id":"93890858","predicate":"inputGroupCallStream","params":[{"name":"flags","type":"#"},{"name":"call","type":"InputGroupCall"},{"name":"time_ms","type":"long"},{"name":"scale","type":"int"},{"name":"video_channel","type":"flags.0?int"},{"name":"video_quality","type":"flags.0?int"}],"type":"InputFileLocation"},{"id":"-1343921601","predicate":"phone.joinAsPeers","params":[{"name":"peers","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"phone.JoinAsPeers"},{"id":"541839704","predicate":"phone.exportedGroupCallInvite","params":[{"name":"link","type":"string"}],"type":"phone.ExportedGroupCallInvite"},{"id":"-672693723","predicate":"inputBotInlineMessageMediaInvoice","params":[{"name":"flags","type":"#"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.0?InputWebDocument"},{"name":"invoice","type":"Invoice"},{"name":"payload","type":"bytes"},{"name":"provider","type":"string"},{"name":"provider_data","type":"DataJSON"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"InputBotInlineMessage"},{"id":"894081801","predicate":"botInlineMessageMediaInvoice","params":[{"name":"flags","type":"#"},{"name":"shipping_address_requested","type":"flags.1?true"},{"name":"test","type":"flags.3?true"},{"name":"title","type":"string"},{"name":"description","type":"string"},{"name":"photo","type":"flags.0?WebDocument"},{"name":"currency","type":"string"},{"name":"total_amount","type":"long"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"}],"type":"BotInlineMessage"},{"id":"-1281329567","predicate":"messageActionGroupCallScheduled","params":[{"name":"call","type":"InputGroupCall"},{"name":"schedule_date","type":"int"}],"type":"MessageAction"},{"id":"-592373577","predicate":"groupCallParticipantVideoSourceGroup","params":[{"name":"semantics","type":"string"},{"name":"sources","type":"Vector"}],"type":"GroupCallParticipantVideoSourceGroup"},{"id":"1735736008","predicate":"groupCallParticipantVideo","params":[{"name":"flags","type":"#"},{"name":"paused","type":"flags.0?true"},{"name":"endpoint","type":"string"},{"name":"source_groups","type":"Vector"},{"name":"audio_source","type":"flags.1?int"}],"type":"GroupCallParticipantVideo"},{"id":"192428418","predicate":"updateGroupCallConnection","params":[{"name":"flags","type":"#"},{"name":"presentation","type":"flags.0?true"},{"name":"params","type":"DataJSON"}],"type":"Update"},{"id":"-2046910401","predicate":"stickers.suggestedShortName","params":[{"name":"short_name","type":"string"}],"type":"stickers.SuggestedShortName"},{"id":"795652779","predicate":"botCommandScopeDefault","params":[],"type":"BotCommandScope"},{"id":"1011811544","predicate":"botCommandScopeUsers","params":[],"type":"BotCommandScope"},{"id":"1877059713","predicate":"botCommandScopeChats","params":[],"type":"BotCommandScope"},{"id":"-1180016534","predicate":"botCommandScopeChatAdmins","params":[],"type":"BotCommandScope"},{"id":"-610432643","predicate":"botCommandScopePeer","params":[{"name":"peer","type":"InputPeer"}],"type":"BotCommandScope"},{"id":"1071145937","predicate":"botCommandScopePeerAdmins","params":[{"name":"peer","type":"InputPeer"}],"type":"BotCommandScope"},{"id":"169026035","predicate":"botCommandScopePeerUser","params":[{"name":"peer","type":"InputPeer"},{"name":"user_id","type":"InputUser"}],"type":"BotCommandScope"},{"id":"-478701471","predicate":"account.resetPasswordFailedWait","params":[{"name":"retry_date","type":"int"}],"type":"account.ResetPasswordResult"},{"id":"-370148227","predicate":"account.resetPasswordRequestedWait","params":[{"name":"until_date","type":"int"}],"type":"account.ResetPasswordResult"},{"id":"-383330754","predicate":"account.resetPasswordOk","params":[],"type":"account.ResetPasswordResult"},{"id":"1299263278","predicate":"updateBotCommands","params":[{"name":"peer","type":"Peer"},{"name":"bot_id","type":"long"},{"name":"commands","type":"Vector"}],"type":"Update"},{"id":"-318022605","predicate":"chatTheme","params":[{"name":"emoticon","type":"string"},{"name":"theme","type":"Theme"},{"name":"dark_theme","type":"Theme"}],"type":"ChatTheme"},{"id":"-535699004","predicate":"account.chatThemesNotModified","params":[],"type":"account.ChatThemes"},{"id":"-28524867","predicate":"account.chatThemes","params":[{"name":"hash","type":"int"},{"name":"themes","type":"Vector"}],"type":"account.ChatThemes"},{"id":"-1434950843","predicate":"messageActionSetChatTheme","params":[{"name":"emoticon","type":"string"}],"type":"MessageAction"},{"id":"-1336228175","predicate":"sendMessageChooseStickerAction","params":[],"type":"SendMessageAction"},{"id":"708589599","predicate":"sponsoredMessage","params":[{"name":"flags","type":"#"},{"name":"random_id","type":"bytes"},{"name":"from_id","type":"Peer"},{"name":"start_param","type":"flags.0?string"},{"name":"message","type":"string"},{"name":"entities","type":"flags.1?Vector"}],"type":"SponsoredMessage"},{"id":"1705297877","predicate":"messages.sponsoredMessages","params":[{"name":"messages","type":"Vector"},{"name":"chats","type":"Vector"},{"name":"users","type":"Vector"}],"type":"messages.SponsoredMessages"},{"id":"215889721","predicate":"inputStickerSetAnimatedEmojiAnimations","params":[],"type":"InputStickerSet"},{"id":"630664139","predicate":"sendMessageEmojiInteraction","params":[{"name":"emoticon","type":"string"},{"name":"msg_id","type":"int"},{"name":"interaction","type":"DataJSON"}],"type":"SendMessageAction"},{"id":"-1234857938","predicate":"sendMessageEmojiInteractionSeen","params":[{"name":"emoticon","type":"string"}],"type":"SendMessageAction"},{"id":"-1227287081","predicate":"inputBotInlineMessageID64","params":[{"name":"dc_id","type":"int"},{"name":"owner_id","type":"long"},{"name":"id","type":"int"},{"name":"access_hash","type":"long"}],"type":"InputBotInlineMessageID"}],"methods":[{"id":"-878758099","method":"invokeAfterMsg","params":[{"name":"msg_id","type":"long"},{"name":"query","type":"!X"}],"type":"X"},{"id":"1036301552","method":"invokeAfterMsgs","params":[{"name":"msg_ids","type":"Vector"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-1502141361","method":"auth.sendCode","params":[{"name":"phone_number","type":"string"},{"name":"api_id","type":"int"},{"name":"api_hash","type":"string"},{"name":"settings","type":"CodeSettings"}],"type":"auth.SentCode"},{"id":"-2131827673","method":"auth.signUp","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"}],"type":"auth.Authorization"},{"id":"-1126886015","method":"auth.signIn","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"},{"name":"phone_code","type":"string"}],"type":"auth.Authorization"},{"id":"1461180992","method":"auth.logOut","params":[],"type":"Bool"},{"id":"-1616179942","method":"auth.resetAuthorizations","params":[],"type":"Bool"},{"id":"-440401971","method":"auth.exportAuthorization","params":[{"name":"dc_id","type":"int"}],"type":"auth.ExportedAuthorization"},{"id":"-1518699091","method":"auth.importAuthorization","params":[{"name":"id","type":"long"},{"name":"bytes","type":"bytes"}],"type":"auth.Authorization"},{"id":"-841733627","method":"auth.bindTempAuthKey","params":[{"name":"perm_auth_key_id","type":"long"},{"name":"nonce","type":"long"},{"name":"expires_at","type":"int"},{"name":"encrypted_message","type":"bytes"}],"type":"Bool"},{"id":"-326762118","method":"account.registerDevice","params":[{"name":"flags","type":"#"},{"name":"no_muted","type":"flags.0?true"},{"name":"token_type","type":"int"},{"name":"token","type":"string"},{"name":"app_sandbox","type":"Bool"},{"name":"secret","type":"bytes"},{"name":"other_uids","type":"Vector"}],"type":"Bool"},{"id":"1779249670","method":"account.unregisterDevice","params":[{"name":"token_type","type":"int"},{"name":"token","type":"string"},{"name":"other_uids","type":"Vector"}],"type":"Bool"},{"id":"-2067899501","method":"account.updateNotifySettings","params":[{"name":"peer","type":"InputNotifyPeer"},{"name":"settings","type":"InputPeerNotifySettings"}],"type":"Bool"},{"id":"313765169","method":"account.getNotifySettings","params":[{"name":"peer","type":"InputNotifyPeer"}],"type":"PeerNotifySettings"},{"id":"-612493497","method":"account.resetNotifySettings","params":[],"type":"Bool"},{"id":"2018596725","method":"account.updateProfile","params":[{"name":"flags","type":"#"},{"name":"first_name","type":"flags.0?string"},{"name":"last_name","type":"flags.1?string"},{"name":"about","type":"flags.2?string"}],"type":"User"},{"id":"1713919532","method":"account.updateStatus","params":[{"name":"offline","type":"Bool"}],"type":"Bool"},{"id":"127302966","method":"account.getWallPapers","params":[{"name":"hash","type":"long"}],"type":"account.WallPapers"},{"id":"-977650298","method":"account.reportPeer","params":[{"name":"peer","type":"InputPeer"},{"name":"reason","type":"ReportReason"},{"name":"message","type":"string"}],"type":"Bool"},{"id":"227648840","method":"users.getUsers","params":[{"name":"id","type":"Vector"}],"type":"Vector"},{"id":"-902781519","method":"users.getFullUser","params":[{"name":"id","type":"InputUser"}],"type":"UserFull"},{"id":"2061264541","method":"contacts.getContactIDs","params":[{"name":"hash","type":"long"}],"type":"Vector"},{"id":"-995929106","method":"contacts.getStatuses","params":[],"type":"Vector"},{"id":"1574346258","method":"contacts.getContacts","params":[{"name":"hash","type":"long"}],"type":"contacts.Contacts"},{"id":"746589157","method":"contacts.importContacts","params":[{"name":"contacts","type":"Vector"}],"type":"contacts.ImportedContacts"},{"id":"157945344","method":"contacts.deleteContacts","params":[{"name":"id","type":"Vector"}],"type":"Updates"},{"id":"269745566","method":"contacts.deleteByPhones","params":[{"name":"phones","type":"Vector"}],"type":"Bool"},{"id":"1758204945","method":"contacts.block","params":[{"name":"id","type":"InputPeer"}],"type":"Bool"},{"id":"-1096393392","method":"contacts.unblock","params":[{"name":"id","type":"InputPeer"}],"type":"Bool"},{"id":"-176409329","method":"contacts.getBlocked","params":[{"name":"offset","type":"int"},{"name":"limit","type":"int"}],"type":"contacts.Blocked"},{"id":"1673946374","method":"messages.getMessages","params":[{"name":"id","type":"Vector"}],"type":"messages.Messages"},{"id":"-1594569905","method":"messages.getDialogs","params":[{"name":"flags","type":"#"},{"name":"exclude_pinned","type":"flags.0?true"},{"name":"folder_id","type":"flags.1?int"},{"name":"offset_date","type":"int"},{"name":"offset_id","type":"int"},{"name":"offset_peer","type":"InputPeer"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Dialogs"},{"id":"1143203525","method":"messages.getHistory","params":[{"name":"peer","type":"InputPeer"},{"name":"offset_id","type":"int"},{"name":"offset_date","type":"int"},{"name":"add_offset","type":"int"},{"name":"limit","type":"int"},{"name":"max_id","type":"int"},{"name":"min_id","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"-1593989278","method":"messages.search","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"q","type":"string"},{"name":"from_id","type":"flags.0?InputPeer"},{"name":"top_msg_id","type":"flags.1?int"},{"name":"filter","type":"MessagesFilter"},{"name":"min_date","type":"int"},{"name":"max_date","type":"int"},{"name":"offset_id","type":"int"},{"name":"add_offset","type":"int"},{"name":"limit","type":"int"},{"name":"max_id","type":"int"},{"name":"min_id","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"238054714","method":"messages.readHistory","params":[{"name":"peer","type":"InputPeer"},{"name":"max_id","type":"int"}],"type":"messages.AffectedMessages"},{"id":"469850889","method":"messages.deleteHistory","params":[{"name":"flags","type":"#"},{"name":"just_clear","type":"flags.0?true"},{"name":"revoke","type":"flags.1?true"},{"name":"peer","type":"InputPeer"},{"name":"max_id","type":"int"}],"type":"messages.AffectedHistory"},{"id":"-443640366","method":"messages.deleteMessages","params":[{"name":"flags","type":"#"},{"name":"revoke","type":"flags.0?true"},{"name":"id","type":"Vector"}],"type":"messages.AffectedMessages"},{"id":"94983360","method":"messages.receivedMessages","params":[{"name":"max_id","type":"int"}],"type":"Vector"},{"id":"1486110434","method":"messages.setTyping","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"top_msg_id","type":"flags.0?int"},{"name":"action","type":"SendMessageAction"}],"type":"Bool"},{"id":"1376532592","method":"messages.sendMessage","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"clear_draft","type":"flags.7?true"},{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"message","type":"string"},{"name":"random_id","type":"long"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"},{"name":"entities","type":"flags.3?Vector"},{"name":"schedule_date","type":"flags.10?int"}],"type":"Updates"},{"id":"881978281","method":"messages.sendMedia","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"clear_draft","type":"flags.7?true"},{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"media","type":"InputMedia"},{"name":"message","type":"string"},{"name":"random_id","type":"long"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"},{"name":"entities","type":"flags.3?Vector"},{"name":"schedule_date","type":"flags.10?int"}],"type":"Updates"},{"id":"-637606386","method":"messages.forwardMessages","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"with_my_score","type":"flags.8?true"},{"name":"drop_author","type":"flags.11?true"},{"name":"drop_media_captions","type":"flags.12?true"},{"name":"from_peer","type":"InputPeer"},{"name":"id","type":"Vector"},{"name":"random_id","type":"Vector"},{"name":"to_peer","type":"InputPeer"},{"name":"schedule_date","type":"flags.10?int"}],"type":"Updates"},{"id":"-820669733","method":"messages.reportSpam","params":[{"name":"peer","type":"InputPeer"}],"type":"Bool"},{"id":"913498268","method":"messages.getPeerSettings","params":[{"name":"peer","type":"InputPeer"}],"type":"PeerSettings"},{"id":"-1991005362","method":"messages.report","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"},{"name":"reason","type":"ReportReason"},{"name":"message","type":"string"}],"type":"Bool"},{"id":"1240027791","method":"messages.getChats","params":[{"name":"id","type":"Vector"}],"type":"messages.Chats"},{"id":"-1364194508","method":"messages.getFullChat","params":[{"name":"chat_id","type":"long"}],"type":"messages.ChatFull"},{"id":"1937260541","method":"messages.editChatTitle","params":[{"name":"chat_id","type":"long"},{"name":"title","type":"string"}],"type":"Updates"},{"id":"903730804","method":"messages.editChatPhoto","params":[{"name":"chat_id","type":"long"},{"name":"photo","type":"InputChatPhoto"}],"type":"Updates"},{"id":"-230206493","method":"messages.addChatUser","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"InputUser"},{"name":"fwd_limit","type":"int"}],"type":"Updates"},{"id":"-1575461717","method":"messages.deleteChatUser","params":[{"name":"flags","type":"#"},{"name":"revoke_history","type":"flags.0?true"},{"name":"chat_id","type":"long"},{"name":"user_id","type":"InputUser"}],"type":"Updates"},{"id":"164303470","method":"messages.createChat","params":[{"name":"users","type":"Vector"},{"name":"title","type":"string"}],"type":"Updates"},{"id":"-304838614","method":"updates.getState","params":[],"type":"updates.State"},{"id":"630429265","method":"updates.getDifference","params":[{"name":"flags","type":"#"},{"name":"pts","type":"int"},{"name":"pts_total_limit","type":"flags.0?int"},{"name":"date","type":"int"},{"name":"qts","type":"int"}],"type":"updates.Difference"},{"id":"1926525996","method":"photos.updateProfilePhoto","params":[{"name":"id","type":"InputPhoto"}],"type":"photos.Photo"},{"id":"-1980559511","method":"photos.uploadProfilePhoto","params":[{"name":"flags","type":"#"},{"name":"file","type":"flags.0?InputFile"},{"name":"video","type":"flags.1?InputFile"},{"name":"video_start_ts","type":"flags.2?double"}],"type":"photos.Photo"},{"id":"-2016444625","method":"photos.deletePhotos","params":[{"name":"id","type":"Vector"}],"type":"Vector"},{"id":"-1291540959","method":"upload.saveFilePart","params":[{"name":"file_id","type":"long"},{"name":"file_part","type":"int"},{"name":"bytes","type":"bytes"}],"type":"Bool"},{"id":"-1319462148","method":"upload.getFile","params":[{"name":"flags","type":"#"},{"name":"precise","type":"flags.0?true"},{"name":"cdn_supported","type":"flags.1?true"},{"name":"location","type":"InputFileLocation"},{"name":"offset","type":"int"},{"name":"limit","type":"int"}],"type":"upload.File"},{"id":"-990308245","method":"help.getConfig","params":[],"type":"Config"},{"id":"531836966","method":"help.getNearestDc","params":[],"type":"NearestDc"},{"id":"1378703997","method":"help.getAppUpdate","params":[{"name":"source","type":"string"}],"type":"help.AppUpdate"},{"id":"1295590211","method":"help.getInviteText","params":[],"type":"help.InviteText"},{"id":"-1848823128","method":"photos.getUserPhotos","params":[{"name":"user_id","type":"InputUser"},{"name":"offset","type":"int"},{"name":"max_id","type":"long"},{"name":"limit","type":"int"}],"type":"photos.Photos"},{"id":"651135312","method":"messages.getDhConfig","params":[{"name":"version","type":"int"},{"name":"random_length","type":"int"}],"type":"messages.DhConfig"},{"id":"-162681021","method":"messages.requestEncryption","params":[{"name":"user_id","type":"InputUser"},{"name":"random_id","type":"int"},{"name":"g_a","type":"bytes"}],"type":"EncryptedChat"},{"id":"1035731989","method":"messages.acceptEncryption","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"g_b","type":"bytes"},{"name":"key_fingerprint","type":"long"}],"type":"EncryptedChat"},{"id":"-208425312","method":"messages.discardEncryption","params":[{"name":"flags","type":"#"},{"name":"delete_history","type":"flags.0?true"},{"name":"chat_id","type":"int"}],"type":"Bool"},{"id":"2031374829","method":"messages.setEncryptedTyping","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"typing","type":"Bool"}],"type":"Bool"},{"id":"2135648522","method":"messages.readEncryptedHistory","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"max_date","type":"int"}],"type":"Bool"},{"id":"1157265941","method":"messages.sendEncrypted","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.0?true"},{"name":"peer","type":"InputEncryptedChat"},{"name":"random_id","type":"long"},{"name":"data","type":"bytes"}],"type":"messages.SentEncryptedMessage"},{"id":"1431914525","method":"messages.sendEncryptedFile","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.0?true"},{"name":"peer","type":"InputEncryptedChat"},{"name":"random_id","type":"long"},{"name":"data","type":"bytes"},{"name":"file","type":"InputEncryptedFile"}],"type":"messages.SentEncryptedMessage"},{"id":"852769188","method":"messages.sendEncryptedService","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"random_id","type":"long"},{"name":"data","type":"bytes"}],"type":"messages.SentEncryptedMessage"},{"id":"1436924774","method":"messages.receivedQueue","params":[{"name":"max_qts","type":"int"}],"type":"Vector"},{"id":"1259113487","method":"messages.reportEncryptedSpam","params":[{"name":"peer","type":"InputEncryptedChat"}],"type":"Bool"},{"id":"-562337987","method":"upload.saveBigFilePart","params":[{"name":"file_id","type":"long"},{"name":"file_part","type":"int"},{"name":"file_total_parts","type":"int"},{"name":"bytes","type":"bytes"}],"type":"Bool"},{"id":"-1043505495","method":"initConnection","params":[{"name":"flags","type":"#"},{"name":"api_id","type":"int"},{"name":"device_model","type":"string"},{"name":"system_version","type":"string"},{"name":"app_version","type":"string"},{"name":"system_lang_code","type":"string"},{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"},{"name":"proxy","type":"flags.0?InputClientProxy"},{"name":"params","type":"flags.1?JSONValue"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-1663104819","method":"help.getSupport","params":[],"type":"help.Support"},{"id":"916930423","method":"messages.readMessageContents","params":[{"name":"id","type":"Vector"}],"type":"messages.AffectedMessages"},{"id":"655677548","method":"account.checkUsername","params":[{"name":"username","type":"string"}],"type":"Bool"},{"id":"1040964988","method":"account.updateUsername","params":[{"name":"username","type":"string"}],"type":"User"},{"id":"301470424","method":"contacts.search","params":[{"name":"q","type":"string"},{"name":"limit","type":"int"}],"type":"contacts.Found"},{"id":"-623130288","method":"account.getPrivacy","params":[{"name":"key","type":"InputPrivacyKey"}],"type":"account.PrivacyRules"},{"id":"-906486552","method":"account.setPrivacy","params":[{"name":"key","type":"InputPrivacyKey"},{"name":"rules","type":"Vector"}],"type":"account.PrivacyRules"},{"id":"1099779595","method":"account.deleteAccount","params":[{"name":"reason","type":"string"}],"type":"Bool"},{"id":"150761757","method":"account.getAccountTTL","params":[],"type":"AccountDaysTTL"},{"id":"608323678","method":"account.setAccountTTL","params":[{"name":"ttl","type":"AccountDaysTTL"}],"type":"Bool"},{"id":"-627372787","method":"invokeWithLayer","params":[{"name":"layer","type":"int"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-113456221","method":"contacts.resolveUsername","params":[{"name":"username","type":"string"}],"type":"contacts.ResolvedPeer"},{"id":"-2108208411","method":"account.sendChangePhoneCode","params":[{"name":"phone_number","type":"string"},{"name":"settings","type":"CodeSettings"}],"type":"auth.SentCode"},{"id":"1891839707","method":"account.changePhone","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"},{"name":"phone_code","type":"string"}],"type":"User"},{"id":"-710552671","method":"messages.getStickers","params":[{"name":"emoticon","type":"string"},{"name":"hash","type":"long"}],"type":"messages.Stickers"},{"id":"-1197432408","method":"messages.getAllStickers","params":[{"name":"hash","type":"long"}],"type":"messages.AllStickers"},{"id":"954152242","method":"account.updateDeviceLocked","params":[{"name":"period","type":"int"}],"type":"Bool"},{"id":"1738800940","method":"auth.importBotAuthorization","params":[{"name":"flags","type":"int"},{"name":"api_id","type":"int"},{"name":"api_hash","type":"string"},{"name":"bot_auth_token","type":"string"}],"type":"auth.Authorization"},{"id":"-1956073268","method":"messages.getWebPagePreview","params":[{"name":"flags","type":"#"},{"name":"message","type":"string"},{"name":"entities","type":"flags.3?Vector"}],"type":"MessageMedia"},{"id":"-484392616","method":"account.getAuthorizations","params":[],"type":"account.Authorizations"},{"id":"-545786948","method":"account.resetAuthorization","params":[{"name":"hash","type":"long"}],"type":"Bool"},{"id":"1418342645","method":"account.getPassword","params":[],"type":"account.Password"},{"id":"-1663767815","method":"account.getPasswordSettings","params":[{"name":"password","type":"InputCheckPasswordSRP"}],"type":"account.PasswordSettings"},{"id":"-1516564433","method":"account.updatePasswordSettings","params":[{"name":"password","type":"InputCheckPasswordSRP"},{"name":"new_settings","type":"account.PasswordInputSettings"}],"type":"Bool"},{"id":"-779399914","method":"auth.checkPassword","params":[{"name":"password","type":"InputCheckPasswordSRP"}],"type":"auth.Authorization"},{"id":"-661144474","method":"auth.requestPasswordRecovery","params":[],"type":"auth.PasswordRecovery"},{"id":"923364464","method":"auth.recoverPassword","params":[{"name":"flags","type":"#"},{"name":"code","type":"string"},{"name":"new_settings","type":"flags.0?account.PasswordInputSettings"}],"type":"auth.Authorization"},{"id":"-1080796745","method":"invokeWithoutUpdates","params":[{"name":"query","type":"!X"}],"type":"X"},{"id":"347716823","method":"messages.exportChatInvite","params":[{"name":"flags","type":"#"},{"name":"legacy_revoke_permanent","type":"flags.2?true"},{"name":"peer","type":"InputPeer"},{"name":"expire_date","type":"flags.0?int"},{"name":"usage_limit","type":"flags.1?int"}],"type":"ExportedChatInvite"},{"id":"1051570619","method":"messages.checkChatInvite","params":[{"name":"hash","type":"string"}],"type":"ChatInvite"},{"id":"1817183516","method":"messages.importChatInvite","params":[{"name":"hash","type":"string"}],"type":"Updates"},{"id":"639215886","method":"messages.getStickerSet","params":[{"name":"stickerset","type":"InputStickerSet"}],"type":"messages.StickerSet"},{"id":"-946871200","method":"messages.installStickerSet","params":[{"name":"stickerset","type":"InputStickerSet"},{"name":"archived","type":"Bool"}],"type":"messages.StickerSetInstallResult"},{"id":"-110209570","method":"messages.uninstallStickerSet","params":[{"name":"stickerset","type":"InputStickerSet"}],"type":"Bool"},{"id":"-421563528","method":"messages.startBot","params":[{"name":"bot","type":"InputUser"},{"name":"peer","type":"InputPeer"},{"name":"random_id","type":"long"},{"name":"start_param","type":"string"}],"type":"Updates"},{"id":"-1877938321","method":"help.getAppChangelog","params":[{"name":"prev_app_version","type":"string"}],"type":"Updates"},{"id":"1468322785","method":"messages.getMessagesViews","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"},{"name":"increment","type":"Bool"}],"type":"messages.MessageViews"},{"id":"-871347913","method":"channels.readHistory","params":[{"name":"channel","type":"InputChannel"},{"name":"max_id","type":"int"}],"type":"Bool"},{"id":"-2067661490","method":"channels.deleteMessages","params":[{"name":"channel","type":"InputChannel"},{"name":"id","type":"Vector"}],"type":"messages.AffectedMessages"},{"id":"-787622117","method":"channels.deleteUserHistory","params":[{"name":"channel","type":"InputChannel"},{"name":"user_id","type":"InputUser"}],"type":"messages.AffectedHistory"},{"id":"-32999408","method":"channels.reportSpam","params":[{"name":"channel","type":"InputChannel"},{"name":"user_id","type":"InputUser"},{"name":"id","type":"Vector"}],"type":"Bool"},{"id":"-1383294429","method":"channels.getMessages","params":[{"name":"channel","type":"InputChannel"},{"name":"id","type":"Vector"}],"type":"messages.Messages"},{"id":"2010044880","method":"channels.getParticipants","params":[{"name":"channel","type":"InputChannel"},{"name":"filter","type":"ChannelParticipantsFilter"},{"name":"offset","type":"int"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"channels.ChannelParticipants"},{"id":"-1599378234","method":"channels.getParticipant","params":[{"name":"channel","type":"InputChannel"},{"name":"participant","type":"InputPeer"}],"type":"channels.ChannelParticipant"},{"id":"176122811","method":"channels.getChannels","params":[{"name":"id","type":"Vector"}],"type":"messages.Chats"},{"id":"141781513","method":"channels.getFullChannel","params":[{"name":"channel","type":"InputChannel"}],"type":"messages.ChatFull"},{"id":"1029681423","method":"channels.createChannel","params":[{"name":"flags","type":"#"},{"name":"broadcast","type":"flags.0?true"},{"name":"megagroup","type":"flags.1?true"},{"name":"for_import","type":"flags.3?true"},{"name":"title","type":"string"},{"name":"about","type":"string"},{"name":"geo_point","type":"flags.2?InputGeoPoint"},{"name":"address","type":"flags.2?string"}],"type":"Updates"},{"id":"-751007486","method":"channels.editAdmin","params":[{"name":"channel","type":"InputChannel"},{"name":"user_id","type":"InputUser"},{"name":"admin_rights","type":"ChatAdminRights"},{"name":"rank","type":"string"}],"type":"Updates"},{"id":"1450044624","method":"channels.editTitle","params":[{"name":"channel","type":"InputChannel"},{"name":"title","type":"string"}],"type":"Updates"},{"id":"-248621111","method":"channels.editPhoto","params":[{"name":"channel","type":"InputChannel"},{"name":"photo","type":"InputChatPhoto"}],"type":"Updates"},{"id":"283557164","method":"channels.checkUsername","params":[{"name":"channel","type":"InputChannel"},{"name":"username","type":"string"}],"type":"Bool"},{"id":"890549214","method":"channels.updateUsername","params":[{"name":"channel","type":"InputChannel"},{"name":"username","type":"string"}],"type":"Bool"},{"id":"615851205","method":"channels.joinChannel","params":[{"name":"channel","type":"InputChannel"}],"type":"Updates"},{"id":"-130635115","method":"channels.leaveChannel","params":[{"name":"channel","type":"InputChannel"}],"type":"Updates"},{"id":"429865580","method":"channels.inviteToChannel","params":[{"name":"channel","type":"InputChannel"},{"name":"users","type":"Vector"}],"type":"Updates"},{"id":"-1072619549","method":"channels.deleteChannel","params":[{"name":"channel","type":"InputChannel"}],"type":"Updates"},{"id":"51854712","method":"updates.getChannelDifference","params":[{"name":"flags","type":"#"},{"name":"force","type":"flags.0?true"},{"name":"channel","type":"InputChannel"},{"name":"filter","type":"ChannelMessagesFilter"},{"name":"pts","type":"int"},{"name":"limit","type":"int"}],"type":"updates.ChannelDifference"},{"id":"-1470377534","method":"messages.editChatAdmin","params":[{"name":"chat_id","type":"long"},{"name":"user_id","type":"InputUser"},{"name":"is_admin","type":"Bool"}],"type":"Bool"},{"id":"-1568189671","method":"messages.migrateChat","params":[{"name":"chat_id","type":"long"}],"type":"Updates"},{"id":"1271290010","method":"messages.searchGlobal","params":[{"name":"flags","type":"#"},{"name":"folder_id","type":"flags.0?int"},{"name":"q","type":"string"},{"name":"filter","type":"MessagesFilter"},{"name":"min_date","type":"int"},{"name":"max_date","type":"int"},{"name":"offset_rate","type":"int"},{"name":"offset_peer","type":"InputPeer"},{"name":"offset_id","type":"int"},{"name":"limit","type":"int"}],"type":"messages.Messages"},{"id":"2016638777","method":"messages.reorderStickerSets","params":[{"name":"flags","type":"#"},{"name":"masks","type":"flags.0?true"},{"name":"order","type":"Vector"}],"type":"Bool"},{"id":"864953444","method":"messages.getDocumentByHash","params":[{"name":"sha256","type":"bytes"},{"name":"size","type":"int"},{"name":"mime_type","type":"string"}],"type":"Document"},{"id":"1559270965","method":"messages.getSavedGifs","params":[{"name":"hash","type":"long"}],"type":"messages.SavedGifs"},{"id":"846868683","method":"messages.saveGif","params":[{"name":"id","type":"InputDocument"},{"name":"unsave","type":"Bool"}],"type":"Bool"},{"id":"1364105629","method":"messages.getInlineBotResults","params":[{"name":"flags","type":"#"},{"name":"bot","type":"InputUser"},{"name":"peer","type":"InputPeer"},{"name":"geo_point","type":"flags.0?InputGeoPoint"},{"name":"query","type":"string"},{"name":"offset","type":"string"}],"type":"messages.BotResults"},{"id":"-346119674","method":"messages.setInlineBotResults","params":[{"name":"flags","type":"#"},{"name":"gallery","type":"flags.0?true"},{"name":"private","type":"flags.1?true"},{"name":"query_id","type":"long"},{"name":"results","type":"Vector"},{"name":"cache_time","type":"int"},{"name":"next_offset","type":"flags.2?string"},{"name":"switch_pm","type":"flags.3?InlineBotSwitchPM"}],"type":"Bool"},{"id":"570955184","method":"messages.sendInlineBotResult","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"clear_draft","type":"flags.7?true"},{"name":"hide_via","type":"flags.11?true"},{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"random_id","type":"long"},{"name":"query_id","type":"long"},{"name":"id","type":"string"},{"name":"schedule_date","type":"flags.10?int"}],"type":"Updates"},{"id":"-432034325","method":"channels.exportMessageLink","params":[{"name":"flags","type":"#"},{"name":"grouped","type":"flags.0?true"},{"name":"thread","type":"flags.1?true"},{"name":"channel","type":"InputChannel"},{"name":"id","type":"int"}],"type":"ExportedMessageLink"},{"id":"527021574","method":"channels.toggleSignatures","params":[{"name":"channel","type":"InputChannel"},{"name":"enabled","type":"Bool"}],"type":"Updates"},{"id":"1056025023","method":"auth.resendCode","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"}],"type":"auth.SentCode"},{"id":"520357240","method":"auth.cancelCode","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"}],"type":"Bool"},{"id":"-39416522","method":"messages.getMessageEditData","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"}],"type":"messages.MessageEditData"},{"id":"1224152952","method":"messages.editMessage","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"},{"name":"message","type":"flags.11?string"},{"name":"media","type":"flags.14?InputMedia"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"},{"name":"entities","type":"flags.3?Vector"},{"name":"schedule_date","type":"flags.15?int"}],"type":"Updates"},{"id":"-2091549254","method":"messages.editInlineBotMessage","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"id","type":"InputBotInlineMessageID"},{"name":"message","type":"flags.11?string"},{"name":"media","type":"flags.14?InputMedia"},{"name":"reply_markup","type":"flags.2?ReplyMarkup"},{"name":"entities","type":"flags.3?Vector"}],"type":"Bool"},{"id":"-1824339449","method":"messages.getBotCallbackAnswer","params":[{"name":"flags","type":"#"},{"name":"game","type":"flags.1?true"},{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"data","type":"flags.0?bytes"},{"name":"password","type":"flags.2?InputCheckPasswordSRP"}],"type":"messages.BotCallbackAnswer"},{"id":"-712043766","method":"messages.setBotCallbackAnswer","params":[{"name":"flags","type":"#"},{"name":"alert","type":"flags.1?true"},{"name":"query_id","type":"long"},{"name":"message","type":"flags.0?string"},{"name":"url","type":"flags.2?string"},{"name":"cache_time","type":"int"}],"type":"Bool"},{"id":"-1758168906","method":"contacts.getTopPeers","params":[{"name":"flags","type":"#"},{"name":"correspondents","type":"flags.0?true"},{"name":"bots_pm","type":"flags.1?true"},{"name":"bots_inline","type":"flags.2?true"},{"name":"phone_calls","type":"flags.3?true"},{"name":"forward_users","type":"flags.4?true"},{"name":"forward_chats","type":"flags.5?true"},{"name":"groups","type":"flags.10?true"},{"name":"channels","type":"flags.15?true"},{"name":"offset","type":"int"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"contacts.TopPeers"},{"id":"451113900","method":"contacts.resetTopPeerRating","params":[{"name":"category","type":"TopPeerCategory"},{"name":"peer","type":"InputPeer"}],"type":"Bool"},{"id":"-462373635","method":"messages.getPeerDialogs","params":[{"name":"peers","type":"Vector"}],"type":"messages.PeerDialogs"},{"id":"-1137057461","method":"messages.saveDraft","params":[{"name":"flags","type":"#"},{"name":"no_webpage","type":"flags.1?true"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"peer","type":"InputPeer"},{"name":"message","type":"string"},{"name":"entities","type":"flags.3?Vector"}],"type":"Bool"},{"id":"1782549861","method":"messages.getAllDrafts","params":[],"type":"Updates"},{"id":"1685588756","method":"messages.getFeaturedStickers","params":[{"name":"hash","type":"long"}],"type":"messages.FeaturedStickers"},{"id":"1527873830","method":"messages.readFeaturedStickers","params":[{"name":"id","type":"Vector"}],"type":"Bool"},{"id":"-1649852357","method":"messages.getRecentStickers","params":[{"name":"flags","type":"#"},{"name":"attached","type":"flags.0?true"},{"name":"hash","type":"long"}],"type":"messages.RecentStickers"},{"id":"958863608","method":"messages.saveRecentSticker","params":[{"name":"flags","type":"#"},{"name":"attached","type":"flags.0?true"},{"name":"id","type":"InputDocument"},{"name":"unsave","type":"Bool"}],"type":"Bool"},{"id":"-1986437075","method":"messages.clearRecentStickers","params":[{"name":"flags","type":"#"},{"name":"attached","type":"flags.0?true"}],"type":"Bool"},{"id":"1475442322","method":"messages.getArchivedStickers","params":[{"name":"flags","type":"#"},{"name":"masks","type":"flags.0?true"},{"name":"offset_id","type":"long"},{"name":"limit","type":"int"}],"type":"messages.ArchivedStickers"},{"id":"457157256","method":"account.sendConfirmPhoneCode","params":[{"name":"hash","type":"string"},{"name":"settings","type":"CodeSettings"}],"type":"auth.SentCode"},{"id":"1596029123","method":"account.confirmPhone","params":[{"name":"phone_code_hash","type":"string"},{"name":"phone_code","type":"string"}],"type":"Bool"},{"id":"-122669393","method":"channels.getAdminedPublicChannels","params":[{"name":"flags","type":"#"},{"name":"by_location","type":"flags.0?true"},{"name":"check_limit","type":"flags.1?true"}],"type":"messages.Chats"},{"id":"1678738104","method":"messages.getMaskStickers","params":[{"name":"hash","type":"long"}],"type":"messages.AllStickers"},{"id":"-866424884","method":"messages.getAttachedStickers","params":[{"name":"media","type":"InputStickeredMedia"}],"type":"Vector"},{"id":"-1907842680","method":"auth.dropTempAuthKeys","params":[{"name":"except_auth_keys","type":"Vector"}],"type":"Bool"},{"id":"-1896289088","method":"messages.setGameScore","params":[{"name":"flags","type":"#"},{"name":"edit_message","type":"flags.0?true"},{"name":"force","type":"flags.1?true"},{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"},{"name":"user_id","type":"InputUser"},{"name":"score","type":"int"}],"type":"Updates"},{"id":"363700068","method":"messages.setInlineGameScore","params":[{"name":"flags","type":"#"},{"name":"edit_message","type":"flags.0?true"},{"name":"force","type":"flags.1?true"},{"name":"id","type":"InputBotInlineMessageID"},{"name":"user_id","type":"InputUser"},{"name":"score","type":"int"}],"type":"Bool"},{"id":"-400399203","method":"messages.getGameHighScores","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"},{"name":"user_id","type":"InputUser"}],"type":"messages.HighScores"},{"id":"258170395","method":"messages.getInlineGameHighScores","params":[{"name":"id","type":"InputBotInlineMessageID"},{"name":"user_id","type":"InputUser"}],"type":"messages.HighScores"},{"id":"-468934396","method":"messages.getCommonChats","params":[{"name":"user_id","type":"InputUser"},{"name":"max_id","type":"long"},{"name":"limit","type":"int"}],"type":"messages.Chats"},{"id":"-2023787330","method":"messages.getAllChats","params":[{"name":"except_ids","type":"Vector"}],"type":"messages.Chats"},{"id":"-333262899","method":"help.setBotUpdatesStatus","params":[{"name":"pending_updates_count","type":"int"},{"name":"message","type":"string"}],"type":"Bool"},{"id":"852135825","method":"messages.getWebPage","params":[{"name":"url","type":"string"},{"name":"hash","type":"int"}],"type":"WebPage"},{"id":"-1489903017","method":"messages.toggleDialogPin","params":[{"name":"flags","type":"#"},{"name":"pinned","type":"flags.0?true"},{"name":"peer","type":"InputDialogPeer"}],"type":"Bool"},{"id":"991616823","method":"messages.reorderPinnedDialogs","params":[{"name":"flags","type":"#"},{"name":"force","type":"flags.0?true"},{"name":"folder_id","type":"int"},{"name":"order","type":"Vector"}],"type":"Bool"},{"id":"-692498958","method":"messages.getPinnedDialogs","params":[{"name":"folder_id","type":"int"}],"type":"messages.PeerDialogs"},{"id":"-1440257555","method":"bots.sendCustomRequest","params":[{"name":"custom_method","type":"string"},{"name":"params","type":"DataJSON"}],"type":"DataJSON"},{"id":"-434028723","method":"bots.answerWebhookJSONQuery","params":[{"name":"query_id","type":"long"},{"name":"data","type":"DataJSON"}],"type":"Bool"},{"id":"619086221","method":"upload.getWebFile","params":[{"name":"location","type":"InputWebFileLocation"},{"name":"offset","type":"int"},{"name":"limit","type":"int"}],"type":"upload.WebFile"},{"id":"-1976353651","method":"payments.getPaymentForm","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"theme_params","type":"flags.0?DataJSON"}],"type":"payments.PaymentForm"},{"id":"611897804","method":"payments.getPaymentReceipt","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"}],"type":"payments.PaymentReceipt"},{"id":"-619695760","method":"payments.validateRequestedInfo","params":[{"name":"flags","type":"#"},{"name":"save","type":"flags.0?true"},{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"info","type":"PaymentRequestedInfo"}],"type":"payments.ValidatedRequestedInfo"},{"id":"818134173","method":"payments.sendPaymentForm","params":[{"name":"flags","type":"#"},{"name":"form_id","type":"long"},{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"requested_info_id","type":"flags.0?string"},{"name":"shipping_option_id","type":"flags.1?string"},{"name":"credentials","type":"InputPaymentCredentials"},{"name":"tip_amount","type":"flags.2?long"}],"type":"payments.PaymentResult"},{"id":"1151208273","method":"account.getTmpPassword","params":[{"name":"password","type":"InputCheckPasswordSRP"},{"name":"period","type":"int"}],"type":"account.TmpPassword"},{"id":"578650699","method":"payments.getSavedInfo","params":[],"type":"payments.SavedInfo"},{"id":"-667062079","method":"payments.clearSavedInfo","params":[{"name":"flags","type":"#"},{"name":"credentials","type":"flags.0?true"},{"name":"info","type":"flags.1?true"}],"type":"Bool"},{"id":"-436833542","method":"messages.setBotShippingResults","params":[{"name":"flags","type":"#"},{"name":"query_id","type":"long"},{"name":"error","type":"flags.0?string"},{"name":"shipping_options","type":"flags.1?Vector"}],"type":"Bool"},{"id":"163765653","method":"messages.setBotPrecheckoutResults","params":[{"name":"flags","type":"#"},{"name":"success","type":"flags.1?true"},{"name":"query_id","type":"long"},{"name":"error","type":"flags.0?string"}],"type":"Bool"},{"id":"-1876841625","method":"stickers.createStickerSet","params":[{"name":"flags","type":"#"},{"name":"masks","type":"flags.0?true"},{"name":"animated","type":"flags.1?true"},{"name":"videos","type":"flags.4?true"},{"name":"user_id","type":"InputUser"},{"name":"title","type":"string"},{"name":"short_name","type":"string"},{"name":"thumb","type":"flags.2?InputDocument"},{"name":"stickers","type":"Vector"},{"name":"software","type":"flags.3?string"}],"type":"messages.StickerSet"},{"id":"-143257775","method":"stickers.removeStickerFromSet","params":[{"name":"sticker","type":"InputDocument"}],"type":"messages.StickerSet"},{"id":"-4795190","method":"stickers.changeStickerPosition","params":[{"name":"sticker","type":"InputDocument"},{"name":"position","type":"int"}],"type":"messages.StickerSet"},{"id":"-2041315650","method":"stickers.addStickerToSet","params":[{"name":"stickerset","type":"InputStickerSet"},{"name":"sticker","type":"InputStickerSetItem"}],"type":"messages.StickerSet"},{"id":"1369162417","method":"messages.uploadMedia","params":[{"name":"peer","type":"InputPeer"},{"name":"media","type":"InputMedia"}],"type":"MessageMedia"},{"id":"1430593449","method":"phone.getCallConfig","params":[],"type":"DataJSON"},{"id":"1124046573","method":"phone.requestCall","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.0?true"},{"name":"user_id","type":"InputUser"},{"name":"random_id","type":"int"},{"name":"g_a_hash","type":"bytes"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"phone.PhoneCall"},{"id":"1003664544","method":"phone.acceptCall","params":[{"name":"peer","type":"InputPhoneCall"},{"name":"g_b","type":"bytes"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"phone.PhoneCall"},{"id":"788404002","method":"phone.confirmCall","params":[{"name":"peer","type":"InputPhoneCall"},{"name":"g_a","type":"bytes"},{"name":"key_fingerprint","type":"long"},{"name":"protocol","type":"PhoneCallProtocol"}],"type":"phone.PhoneCall"},{"id":"399855457","method":"phone.receivedCall","params":[{"name":"peer","type":"InputPhoneCall"}],"type":"Bool"},{"id":"-1295269440","method":"phone.discardCall","params":[{"name":"flags","type":"#"},{"name":"video","type":"flags.0?true"},{"name":"peer","type":"InputPhoneCall"},{"name":"duration","type":"int"},{"name":"reason","type":"PhoneCallDiscardReason"},{"name":"connection_id","type":"long"}],"type":"Updates"},{"id":"1508562471","method":"phone.setCallRating","params":[{"name":"flags","type":"#"},{"name":"user_initiative","type":"flags.0?true"},{"name":"peer","type":"InputPhoneCall"},{"name":"rating","type":"int"},{"name":"comment","type":"string"}],"type":"Updates"},{"id":"662363518","method":"phone.saveCallDebug","params":[{"name":"peer","type":"InputPhoneCall"},{"name":"debug","type":"DataJSON"}],"type":"Bool"},{"id":"536919235","method":"upload.getCdnFile","params":[{"name":"file_token","type":"bytes"},{"name":"offset","type":"int"},{"name":"limit","type":"int"}],"type":"upload.CdnFile"},{"id":"-1691921240","method":"upload.reuploadCdnFile","params":[{"name":"file_token","type":"bytes"},{"name":"request_token","type":"bytes"}],"type":"Vector"},{"id":"1375900482","method":"help.getCdnConfig","params":[],"type":"CdnConfig"},{"id":"-219008246","method":"langpack.getLangPack","params":[{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"}],"type":"LangPackDifference"},{"id":"-269862909","method":"langpack.getStrings","params":[{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"},{"name":"keys","type":"Vector"}],"type":"Vector"},{"id":"-845657435","method":"langpack.getDifference","params":[{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"},{"name":"from_version","type":"int"}],"type":"LangPackDifference"},{"id":"1120311183","method":"langpack.getLanguages","params":[{"name":"lang_pack","type":"string"}],"type":"Vector"},{"id":"-1763259007","method":"channels.editBanned","params":[{"name":"channel","type":"InputChannel"},{"name":"participant","type":"InputPeer"},{"name":"banned_rights","type":"ChatBannedRights"}],"type":"Updates"},{"id":"870184064","method":"channels.getAdminLog","params":[{"name":"flags","type":"#"},{"name":"channel","type":"InputChannel"},{"name":"q","type":"string"},{"name":"events_filter","type":"flags.0?ChannelAdminLogEventsFilter"},{"name":"admins","type":"flags.1?Vector"},{"name":"max_id","type":"long"},{"name":"min_id","type":"long"},{"name":"limit","type":"int"}],"type":"channels.AdminLogResults"},{"id":"1302676017","method":"upload.getCdnFileHashes","params":[{"name":"file_token","type":"bytes"},{"name":"offset","type":"int"}],"type":"Vector"},{"id":"-914493408","method":"messages.sendScreenshotNotification","params":[{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"int"},{"name":"random_id","type":"long"}],"type":"Updates"},{"id":"-359881479","method":"channels.setStickers","params":[{"name":"channel","type":"InputChannel"},{"name":"stickerset","type":"InputStickerSet"}],"type":"Bool"},{"id":"82946729","method":"messages.getFavedStickers","params":[{"name":"hash","type":"long"}],"type":"messages.FavedStickers"},{"id":"-1174420133","method":"messages.faveSticker","params":[{"name":"id","type":"InputDocument"},{"name":"unfave","type":"Bool"}],"type":"Bool"},{"id":"-357180360","method":"channels.readMessageContents","params":[{"name":"channel","type":"InputChannel"},{"name":"id","type":"Vector"}],"type":"Bool"},{"id":"-2020263951","method":"contacts.resetSaved","params":[],"type":"Bool"},{"id":"1180140658","method":"messages.getUnreadMentions","params":[{"name":"peer","type":"InputPeer"},{"name":"offset_id","type":"int"},{"name":"add_offset","type":"int"},{"name":"limit","type":"int"},{"name":"max_id","type":"int"},{"name":"min_id","type":"int"}],"type":"messages.Messages"},{"id":"-1355375294","method":"channels.deleteHistory","params":[{"name":"channel","type":"InputChannel"},{"name":"max_id","type":"int"}],"type":"Bool"},{"id":"1036054804","method":"help.getRecentMeUrls","params":[{"name":"referer","type":"string"}],"type":"help.RecentMeUrls"},{"id":"-356796084","method":"channels.togglePreHistoryHidden","params":[{"name":"channel","type":"InputChannel"},{"name":"enabled","type":"Bool"}],"type":"Updates"},{"id":"251759059","method":"messages.readMentions","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.AffectedHistory"},{"id":"1881817312","method":"messages.getRecentLocations","params":[{"name":"peer","type":"InputPeer"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"-872345397","method":"messages.sendMultiMedia","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.5?true"},{"name":"background","type":"flags.6?true"},{"name":"clear_draft","type":"flags.7?true"},{"name":"peer","type":"InputPeer"},{"name":"reply_to_msg_id","type":"flags.0?int"},{"name":"multi_media","type":"Vector"},{"name":"schedule_date","type":"flags.10?int"}],"type":"Updates"},{"id":"1347929239","method":"messages.uploadEncryptedFile","params":[{"name":"peer","type":"InputEncryptedChat"},{"name":"file","type":"InputEncryptedFile"}],"type":"EncryptedFile"},{"id":"405695855","method":"account.getWebAuthorizations","params":[],"type":"account.WebAuthorizations"},{"id":"755087855","method":"account.resetWebAuthorization","params":[{"name":"hash","type":"long"}],"type":"Bool"},{"id":"1747789204","method":"account.resetWebAuthorizations","params":[],"type":"Bool"},{"id":"896555914","method":"messages.searchStickerSets","params":[{"name":"flags","type":"#"},{"name":"exclude_featured","type":"flags.0?true"},{"name":"q","type":"string"},{"name":"hash","type":"long"}],"type":"messages.FoundStickerSets"},{"id":"-956147407","method":"upload.getFileHashes","params":[{"name":"location","type":"InputFileLocation"},{"name":"offset","type":"int"}],"type":"Vector"},{"id":"749019089","method":"help.getTermsOfServiceUpdate","params":[],"type":"help.TermsOfServiceUpdate"},{"id":"-294455398","method":"help.acceptTermsOfService","params":[{"name":"id","type":"DataJSON"}],"type":"Bool"},{"id":"-1299661699","method":"account.getAllSecureValues","params":[],"type":"Vector"},{"id":"1936088002","method":"account.getSecureValue","params":[{"name":"types","type":"Vector"}],"type":"Vector"},{"id":"-1986010339","method":"account.saveSecureValue","params":[{"name":"value","type":"InputSecureValue"},{"name":"secure_secret_id","type":"long"}],"type":"SecureValue"},{"id":"-1199522741","method":"account.deleteSecureValue","params":[{"name":"types","type":"Vector"}],"type":"Bool"},{"id":"-1865902923","method":"users.setSecureValueErrors","params":[{"name":"id","type":"InputUser"},{"name":"errors","type":"Vector"}],"type":"Bool"},{"id":"-1456907910","method":"account.getAuthorizationForm","params":[{"name":"bot_id","type":"long"},{"name":"scope","type":"string"},{"name":"public_key","type":"string"}],"type":"account.AuthorizationForm"},{"id":"-202552205","method":"account.acceptAuthorization","params":[{"name":"bot_id","type":"long"},{"name":"scope","type":"string"},{"name":"public_key","type":"string"},{"name":"value_hashes","type":"Vector"},{"name":"credentials","type":"SecureCredentialsEncrypted"}],"type":"Bool"},{"id":"-1516022023","method":"account.sendVerifyPhoneCode","params":[{"name":"phone_number","type":"string"},{"name":"settings","type":"CodeSettings"}],"type":"auth.SentCode"},{"id":"1305716726","method":"account.verifyPhone","params":[{"name":"phone_number","type":"string"},{"name":"phone_code_hash","type":"string"},{"name":"phone_code","type":"string"}],"type":"Bool"},{"id":"1880182943","method":"account.sendVerifyEmailCode","params":[{"name":"email","type":"string"}],"type":"account.SentEmailCode"},{"id":"-323339813","method":"account.verifyEmail","params":[{"name":"email","type":"string"},{"name":"code","type":"string"}],"type":"Bool"},{"id":"1072547679","method":"help.getDeepLinkInfo","params":[{"name":"path","type":"string"}],"type":"help.DeepLinkInfo"},{"id":"-2098076769","method":"contacts.getSaved","params":[],"type":"Vector"},{"id":"-2092831552","method":"channels.getLeftChannels","params":[{"name":"offset","type":"int"}],"type":"messages.Chats"},{"id":"-262453244","method":"account.initTakeoutSession","params":[{"name":"flags","type":"#"},{"name":"contacts","type":"flags.0?true"},{"name":"message_users","type":"flags.1?true"},{"name":"message_chats","type":"flags.2?true"},{"name":"message_megagroups","type":"flags.3?true"},{"name":"message_channels","type":"flags.4?true"},{"name":"files","type":"flags.5?true"},{"name":"file_max_size","type":"flags.5?int"}],"type":"account.Takeout"},{"id":"489050862","method":"account.finishTakeoutSession","params":[{"name":"flags","type":"#"},{"name":"success","type":"flags.0?true"}],"type":"Bool"},{"id":"486505992","method":"messages.getSplitRanges","params":[],"type":"Vector"},{"id":"911373810","method":"invokeWithMessagesRange","params":[{"name":"range","type":"MessageRange"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-1398145746","method":"invokeWithTakeout","params":[{"name":"takeout_id","type":"long"},{"name":"query","type":"!X"}],"type":"X"},{"id":"-1031349873","method":"messages.markDialogUnread","params":[{"name":"flags","type":"#"},{"name":"unread","type":"flags.0?true"},{"name":"peer","type":"InputDialogPeer"}],"type":"Bool"},{"id":"585256482","method":"messages.getDialogUnreadMarks","params":[],"type":"Vector"},{"id":"-2062238246","method":"contacts.toggleTopPeers","params":[{"name":"enabled","type":"Bool"}],"type":"Bool"},{"id":"2119757468","method":"messages.clearAllDrafts","params":[],"type":"Bool"},{"id":"-1735311088","method":"help.getAppConfig","params":[],"type":"JSONValue"},{"id":"1862465352","method":"help.saveAppLog","params":[{"name":"events","type":"Vector"}],"type":"Bool"},{"id":"-966677240","method":"help.getPassportConfig","params":[{"name":"hash","type":"int"}],"type":"help.PassportConfig"},{"id":"1784243458","method":"langpack.getLanguage","params":[{"name":"lang_pack","type":"string"},{"name":"lang_code","type":"string"}],"type":"LangPackLanguage"},{"id":"-760547348","method":"messages.updatePinnedMessage","params":[{"name":"flags","type":"#"},{"name":"silent","type":"flags.0?true"},{"name":"unpin","type":"flags.1?true"},{"name":"pm_oneside","type":"flags.2?true"},{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"}],"type":"Updates"},{"id":"-1881204448","method":"account.confirmPasswordEmail","params":[{"name":"code","type":"string"}],"type":"Bool"},{"id":"2055154197","method":"account.resendPasswordEmail","params":[],"type":"Bool"},{"id":"-1043606090","method":"account.cancelPasswordEmail","params":[],"type":"Bool"},{"id":"-748624084","method":"help.getSupportName","params":[],"type":"help.SupportName"},{"id":"59377875","method":"help.getUserInfo","params":[{"name":"user_id","type":"InputUser"}],"type":"help.UserInfo"},{"id":"1723407216","method":"help.editUserInfo","params":[{"name":"user_id","type":"InputUser"},{"name":"message","type":"string"},{"name":"entities","type":"Vector"}],"type":"help.UserInfo"},{"id":"-1626880216","method":"account.getContactSignUpNotification","params":[],"type":"Bool"},{"id":"-806076575","method":"account.setContactSignUpNotification","params":[{"name":"silent","type":"Bool"}],"type":"Bool"},{"id":"1398240377","method":"account.getNotifyExceptions","params":[{"name":"flags","type":"#"},{"name":"compare_sound","type":"flags.1?true"},{"name":"peer","type":"flags.0?InputNotifyPeer"}],"type":"Updates"},{"id":"283795844","method":"messages.sendVote","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"options","type":"Vector"}],"type":"Updates"},{"id":"1941660731","method":"messages.getPollResults","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"}],"type":"Updates"},{"id":"1848369232","method":"messages.getOnlines","params":[{"name":"peer","type":"InputPeer"}],"type":"ChatOnlines"},{"id":"-554301545","method":"messages.editChatAbout","params":[{"name":"peer","type":"InputPeer"},{"name":"about","type":"string"}],"type":"Bool"},{"id":"-1517917375","method":"messages.editChatDefaultBannedRights","params":[{"name":"peer","type":"InputPeer"},{"name":"banned_rights","type":"ChatBannedRights"}],"type":"Updates"},{"id":"-57811990","method":"account.getWallPaper","params":[{"name":"wallpaper","type":"InputWallPaper"}],"type":"WallPaper"},{"id":"-578472351","method":"account.uploadWallPaper","params":[{"name":"file","type":"InputFile"},{"name":"mime_type","type":"string"},{"name":"settings","type":"WallPaperSettings"}],"type":"WallPaper"},{"id":"1817860919","method":"account.saveWallPaper","params":[{"name":"wallpaper","type":"InputWallPaper"},{"name":"unsave","type":"Bool"},{"name":"settings","type":"WallPaperSettings"}],"type":"Bool"},{"id":"-18000023","method":"account.installWallPaper","params":[{"name":"wallpaper","type":"InputWallPaper"},{"name":"settings","type":"WallPaperSettings"}],"type":"Bool"},{"id":"-1153722364","method":"account.resetWallPapers","params":[],"type":"Bool"},{"id":"1457130303","method":"account.getAutoDownloadSettings","params":[],"type":"account.AutoDownloadSettings"},{"id":"1995661875","method":"account.saveAutoDownloadSettings","params":[{"name":"flags","type":"#"},{"name":"low","type":"flags.0?true"},{"name":"high","type":"flags.1?true"},{"name":"settings","type":"AutoDownloadSettings"}],"type":"Bool"},{"id":"899735650","method":"messages.getEmojiKeywords","params":[{"name":"lang_code","type":"string"}],"type":"EmojiKeywordsDifference"},{"id":"352892591","method":"messages.getEmojiKeywordsDifference","params":[{"name":"lang_code","type":"string"},{"name":"from_version","type":"int"}],"type":"EmojiKeywordsDifference"},{"id":"1318675378","method":"messages.getEmojiKeywordsLanguages","params":[{"name":"lang_codes","type":"Vector"}],"type":"Vector"},{"id":"-709817306","method":"messages.getEmojiURL","params":[{"name":"lang_code","type":"string"}],"type":"EmojiURL"},{"id":"1749536939","method":"folders.editPeerFolders","params":[{"name":"folder_peers","type":"Vector"}],"type":"Updates"},{"id":"472471681","method":"folders.deleteFolder","params":[{"name":"folder_id","type":"int"}],"type":"Updates"},{"id":"1932455680","method":"messages.getSearchCounters","params":[{"name":"peer","type":"InputPeer"},{"name":"filters","type":"Vector"}],"type":"Vector"},{"id":"-170208392","method":"channels.getGroupsForDiscussion","params":[],"type":"messages.Chats"},{"id":"1079520178","method":"channels.setDiscussionGroup","params":[{"name":"broadcast","type":"InputChannel"},{"name":"group","type":"InputChannel"}],"type":"Bool"},{"id":"428848198","method":"messages.requestUrlAuth","params":[{"name":"flags","type":"#"},{"name":"peer","type":"flags.1?InputPeer"},{"name":"msg_id","type":"flags.1?int"},{"name":"button_id","type":"flags.1?int"},{"name":"url","type":"flags.2?string"}],"type":"UrlAuthResult"},{"id":"-1322487515","method":"messages.acceptUrlAuth","params":[{"name":"flags","type":"#"},{"name":"write_allowed","type":"flags.0?true"},{"name":"peer","type":"flags.1?InputPeer"},{"name":"msg_id","type":"flags.1?int"},{"name":"button_id","type":"flags.1?int"},{"name":"url","type":"flags.2?string"}],"type":"UrlAuthResult"},{"id":"1336717624","method":"messages.hidePeerSettingsBar","params":[{"name":"peer","type":"InputPeer"}],"type":"Bool"},{"id":"-386636848","method":"contacts.addContact","params":[{"name":"flags","type":"#"},{"name":"add_phone_privacy_exception","type":"flags.0?true"},{"name":"id","type":"InputUser"},{"name":"first_name","type":"string"},{"name":"last_name","type":"string"},{"name":"phone","type":"string"}],"type":"Updates"},{"id":"-130964977","method":"contacts.acceptContact","params":[{"name":"id","type":"InputUser"}],"type":"Updates"},{"id":"-1892102881","method":"channels.editCreator","params":[{"name":"channel","type":"InputChannel"},{"name":"user_id","type":"InputUser"},{"name":"password","type":"InputCheckPasswordSRP"}],"type":"Updates"},{"id":"-750207932","method":"contacts.getLocated","params":[{"name":"flags","type":"#"},{"name":"background","type":"flags.1?true"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"self_expires","type":"flags.0?int"}],"type":"Updates"},{"id":"1491484525","method":"channels.editLocation","params":[{"name":"channel","type":"InputChannel"},{"name":"geo_point","type":"InputGeoPoint"},{"name":"address","type":"string"}],"type":"Bool"},{"id":"-304832784","method":"channels.toggleSlowMode","params":[{"name":"channel","type":"InputChannel"},{"name":"seconds","type":"int"}],"type":"Updates"},{"id":"-183077365","method":"messages.getScheduledHistory","params":[{"name":"peer","type":"InputPeer"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"-1111817116","method":"messages.getScheduledMessages","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"}],"type":"messages.Messages"},{"id":"-1120369398","method":"messages.sendScheduledMessages","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"}],"type":"Updates"},{"id":"1504586518","method":"messages.deleteScheduledMessages","params":[{"name":"peer","type":"InputPeer"},{"name":"id","type":"Vector"}],"type":"Updates"},{"id":"473805619","method":"account.uploadTheme","params":[{"name":"flags","type":"#"},{"name":"file","type":"InputFile"},{"name":"thumb","type":"flags.0?InputFile"},{"name":"file_name","type":"string"},{"name":"mime_type","type":"string"}],"type":"Document"},{"id":"-2077048289","method":"account.createTheme","params":[{"name":"flags","type":"#"},{"name":"slug","type":"string"},{"name":"title","type":"string"},{"name":"document","type":"flags.2?InputDocument"},{"name":"settings","type":"flags.3?InputThemeSettings"}],"type":"Theme"},{"id":"1555261397","method":"account.updateTheme","params":[{"name":"flags","type":"#"},{"name":"format","type":"string"},{"name":"theme","type":"InputTheme"},{"name":"slug","type":"flags.0?string"},{"name":"title","type":"flags.1?string"},{"name":"document","type":"flags.2?InputDocument"},{"name":"settings","type":"flags.3?InputThemeSettings"}],"type":"Theme"},{"id":"-229175188","method":"account.saveTheme","params":[{"name":"theme","type":"InputTheme"},{"name":"unsave","type":"Bool"}],"type":"Bool"},{"id":"2061776695","method":"account.installTheme","params":[{"name":"flags","type":"#"},{"name":"dark","type":"flags.0?true"},{"name":"format","type":"flags.1?string"},{"name":"theme","type":"flags.1?InputTheme"}],"type":"Bool"},{"id":"-1919060949","method":"account.getTheme","params":[{"name":"format","type":"string"},{"name":"theme","type":"InputTheme"},{"name":"document_id","type":"long"}],"type":"Theme"},{"id":"1913054296","method":"account.getThemes","params":[{"name":"format","type":"string"},{"name":"hash","type":"long"}],"type":"account.Themes"},{"id":"-1210022402","method":"auth.exportLoginToken","params":[{"name":"api_id","type":"int"},{"name":"api_hash","type":"string"},{"name":"except_ids","type":"Vector"}],"type":"auth.LoginToken"},{"id":"-1783866140","method":"auth.importLoginToken","params":[{"name":"token","type":"bytes"}],"type":"auth.LoginToken"},{"id":"-392909491","method":"auth.acceptLoginToken","params":[{"name":"token","type":"bytes"}],"type":"Authorization"},{"id":"-1250643605","method":"account.setContentSettings","params":[{"name":"flags","type":"#"},{"name":"sensitive_enabled","type":"flags.0?true"}],"type":"Bool"},{"id":"-1952756306","method":"account.getContentSettings","params":[],"type":"account.ContentSettings"},{"id":"300429806","method":"channels.getInactiveChannels","params":[],"type":"messages.InactiveChats"},{"id":"1705865692","method":"account.getMultiWallPapers","params":[{"name":"wallpapers","type":"Vector"}],"type":"Vector"},{"id":"-1200736242","method":"messages.getPollVotes","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"id","type":"int"},{"name":"option","type":"flags.0?bytes"},{"name":"offset","type":"flags.1?string"},{"name":"limit","type":"int"}],"type":"messages.VotesList"},{"id":"-1257951254","method":"messages.toggleStickerSets","params":[{"name":"flags","type":"#"},{"name":"uninstall","type":"flags.0?true"},{"name":"archive","type":"flags.1?true"},{"name":"unarchive","type":"flags.2?true"},{"name":"stickersets","type":"Vector"}],"type":"Bool"},{"id":"779736953","method":"payments.getBankCardData","params":[{"name":"number","type":"string"}],"type":"payments.BankCardData"},{"id":"-241247891","method":"messages.getDialogFilters","params":[],"type":"Vector"},{"id":"-1566780372","method":"messages.getSuggestedDialogFilters","params":[],"type":"Vector"},{"id":"450142282","method":"messages.updateDialogFilter","params":[{"name":"flags","type":"#"},{"name":"id","type":"int"},{"name":"filter","type":"flags.0?DialogFilter"}],"type":"Bool"},{"id":"-983318044","method":"messages.updateDialogFiltersOrder","params":[{"name":"order","type":"Vector"}],"type":"Bool"},{"id":"-1421720550","method":"stats.getBroadcastStats","params":[{"name":"flags","type":"#"},{"name":"dark","type":"flags.0?true"},{"name":"channel","type":"InputChannel"}],"type":"stats.BroadcastStats"},{"id":"1646092192","method":"stats.loadAsyncGraph","params":[{"name":"flags","type":"#"},{"name":"token","type":"string"},{"name":"x","type":"flags.0?long"}],"type":"StatsGraph"},{"id":"-1707717072","method":"stickers.setStickerSetThumb","params":[{"name":"stickerset","type":"InputStickerSet"},{"name":"thumb","type":"InputDocument"}],"type":"messages.StickerSet"},{"id":"85399130","method":"bots.setBotCommands","params":[{"name":"scope","type":"BotCommandScope"},{"name":"lang_code","type":"string"},{"name":"commands","type":"Vector"}],"type":"Bool"},{"id":"2127598753","method":"messages.getOldFeaturedStickers","params":[{"name":"offset","type":"int"},{"name":"limit","type":"int"},{"name":"hash","type":"long"}],"type":"messages.FeaturedStickers"},{"id":"-1063816159","method":"help.getPromoData","params":[],"type":"help.PromoData"},{"id":"505748629","method":"help.hidePromoData","params":[{"name":"peer","type":"InputPeer"}],"type":"Bool"},{"id":"-8744061","method":"phone.sendSignalingData","params":[{"name":"peer","type":"InputPhoneCall"},{"name":"data","type":"bytes"}],"type":"Bool"},{"id":"-589330937","method":"stats.getMegagroupStats","params":[{"name":"flags","type":"#"},{"name":"dark","type":"flags.0?true"},{"name":"channel","type":"InputChannel"}],"type":"stats.MegagroupStats"},{"id":"-349483786","method":"account.getGlobalPrivacySettings","params":[],"type":"GlobalPrivacySettings"},{"id":"517647042","method":"account.setGlobalPrivacySettings","params":[{"name":"settings","type":"GlobalPrivacySettings"}],"type":"GlobalPrivacySettings"},{"id":"-183649631","method":"help.dismissSuggestion","params":[{"name":"peer","type":"InputPeer"},{"name":"suggestion","type":"string"}],"type":"Bool"},{"id":"1935116200","method":"help.getCountriesList","params":[{"name":"lang_code","type":"string"},{"name":"hash","type":"int"}],"type":"help.CountriesList"},{"id":"584962828","method":"messages.getReplies","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"offset_id","type":"int"},{"name":"offset_date","type":"int"},{"name":"add_offset","type":"int"},{"name":"limit","type":"int"},{"name":"max_id","type":"int"},{"name":"min_id","type":"int"},{"name":"hash","type":"long"}],"type":"messages.Messages"},{"id":"1147761405","method":"messages.getDiscussionMessage","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"}],"type":"messages.DiscussionMessage"},{"id":"-147740172","method":"messages.readDiscussion","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"},{"name":"read_max_id","type":"int"}],"type":"Bool"},{"id":"698914348","method":"contacts.blockFromReplies","params":[{"name":"flags","type":"#"},{"name":"delete_message","type":"flags.0?true"},{"name":"delete_history","type":"flags.1?true"},{"name":"report_spam","type":"flags.2?true"},{"name":"msg_id","type":"int"}],"type":"Updates"},{"id":"1445996571","method":"stats.getMessagePublicForwards","params":[{"name":"channel","type":"InputChannel"},{"name":"msg_id","type":"int"},{"name":"offset_rate","type":"int"},{"name":"offset_peer","type":"InputPeer"},{"name":"offset_id","type":"int"},{"name":"limit","type":"int"}],"type":"messages.Messages"},{"id":"-1226791947","method":"stats.getMessageStats","params":[{"name":"flags","type":"#"},{"name":"dark","type":"flags.0?true"},{"name":"channel","type":"InputChannel"},{"name":"msg_id","type":"int"}],"type":"stats.MessageStats"},{"id":"-265962357","method":"messages.unpinAllMessages","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.AffectedHistory"},{"id":"1221445336","method":"phone.createGroupCall","params":[{"name":"flags","type":"#"},{"name":"peer","type":"InputPeer"},{"name":"random_id","type":"int"},{"name":"title","type":"flags.0?string"},{"name":"schedule_date","type":"flags.1?int"}],"type":"Updates"},{"id":"-1322057861","method":"phone.joinGroupCall","params":[{"name":"flags","type":"#"},{"name":"muted","type":"flags.0?true"},{"name":"video_stopped","type":"flags.2?true"},{"name":"call","type":"InputGroupCall"},{"name":"join_as","type":"InputPeer"},{"name":"invite_hash","type":"flags.1?string"},{"name":"params","type":"DataJSON"}],"type":"Updates"},{"id":"1342404601","method":"phone.leaveGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"source","type":"int"}],"type":"Updates"},{"id":"2067345760","method":"phone.inviteToGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"users","type":"Vector"}],"type":"Updates"},{"id":"2054648117","method":"phone.discardGroupCall","params":[{"name":"call","type":"InputGroupCall"}],"type":"Updates"},{"id":"1958458429","method":"phone.toggleGroupCallSettings","params":[{"name":"flags","type":"#"},{"name":"reset_invite_hash","type":"flags.1?true"},{"name":"call","type":"InputGroupCall"},{"name":"join_muted","type":"flags.0?Bool"}],"type":"Updates"},{"id":"68699611","method":"phone.getGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"limit","type":"int"}],"type":"phone.GroupCall"},{"id":"-984033109","method":"phone.getGroupParticipants","params":[{"name":"call","type":"InputGroupCall"},{"name":"ids","type":"Vector"},{"name":"sources","type":"Vector"},{"name":"offset","type":"string"},{"name":"limit","type":"int"}],"type":"phone.GroupParticipants"},{"id":"-1248003721","method":"phone.checkGroupCall","params":[{"name":"call","type":"InputGroupCall"},{"name":"sources","type":"Vector"}],"type":"Vector"},{"id":"1540419152","method":"messages.deleteChat","params":[{"name":"chat_id","type":"long"}],"type":"Bool"},{"id":"-104078327","method":"messages.deletePhoneCallHistory","params":[{"name":"flags","type":"#"},{"name":"revoke","type":"flags.0?true"}],"type":"messages.AffectedFoundMessages"},{"id":"1140726259","method":"messages.checkHistoryImport","params":[{"name":"import_head","type":"string"}],"type":"messages.HistoryImportParsed"},{"id":"873008187","method":"messages.initHistoryImport","params":[{"name":"peer","type":"InputPeer"},{"name":"file","type":"InputFile"},{"name":"media_count","type":"int"}],"type":"messages.HistoryImport"},{"id":"713433234","method":"messages.uploadImportedMedia","params":[{"name":"peer","type":"InputPeer"},{"name":"import_id","type":"long"},{"name":"file_name","type":"string"},{"name":"media","type":"InputMedia"}],"type":"MessageMedia"},{"id":"-1271008444","method":"messages.startHistoryImport","params":[{"name":"peer","type":"InputPeer"},{"name":"import_id","type":"long"}],"type":"Bool"},{"id":"-1565154314","method":"messages.getExportedChatInvites","params":[{"name":"flags","type":"#"},{"name":"revoked","type":"flags.3?true"},{"name":"peer","type":"InputPeer"},{"name":"admin_id","type":"InputUser"},{"name":"offset_date","type":"flags.2?int"},{"name":"offset_link","type":"flags.2?string"},{"name":"limit","type":"int"}],"type":"messages.ExportedChatInvites"},{"id":"1937010524","method":"messages.getExportedChatInvite","params":[{"name":"peer","type":"InputPeer"},{"name":"link","type":"string"}],"type":"messages.ExportedChatInvite"},{"id":"48562110","method":"messages.editExportedChatInvite","params":[{"name":"flags","type":"#"},{"name":"revoked","type":"flags.2?true"},{"name":"peer","type":"InputPeer"},{"name":"link","type":"string"},{"name":"expire_date","type":"flags.0?int"},{"name":"usage_limit","type":"flags.1?int"}],"type":"messages.ExportedChatInvite"},{"id":"1452833749","method":"messages.deleteRevokedExportedChatInvites","params":[{"name":"peer","type":"InputPeer"},{"name":"admin_id","type":"InputUser"}],"type":"Bool"},{"id":"-731601877","method":"messages.deleteExportedChatInvite","params":[{"name":"peer","type":"InputPeer"},{"name":"link","type":"string"}],"type":"Bool"},{"id":"958457583","method":"messages.getAdminsWithInvites","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.ChatAdminsWithInvites"},{"id":"654013065","method":"messages.getChatInviteImporters","params":[{"name":"peer","type":"InputPeer"},{"name":"link","type":"string"},{"name":"offset_date","type":"int"},{"name":"offset_user","type":"InputUser"},{"name":"limit","type":"int"}],"type":"messages.ChatInviteImporters"},{"id":"-1207017500","method":"messages.setHistoryTTL","params":[{"name":"peer","type":"InputPeer"},{"name":"period","type":"int"}],"type":"Updates"},{"id":"-91437323","method":"account.reportProfilePhoto","params":[{"name":"peer","type":"InputPeer"},{"name":"photo_id","type":"InputPhoto"},{"name":"reason","type":"ReportReason"},{"name":"message","type":"string"}],"type":"Bool"},{"id":"187239529","method":"channels.convertToGigagroup","params":[{"name":"channel","type":"InputChannel"}],"type":"Updates"},{"id":"1573261059","method":"messages.checkHistoryImportPeer","params":[{"name":"peer","type":"InputPeer"}],"type":"messages.CheckedHistoryImportPeer"},{"id":"-248985848","method":"phone.toggleGroupCallRecord","params":[{"name":"flags","type":"#"},{"name":"start","type":"flags.0?true"},{"name":"video","type":"flags.2?true"},{"name":"call","type":"InputGroupCall"},{"name":"title","type":"flags.1?string"},{"name":"video_portrait","type":"flags.2?Bool"}],"type":"Updates"},{"id":"-1524155713","method":"phone.editGroupCallParticipant","params":[{"name":"flags","type":"#"},{"name":"call","type":"InputGroupCall"},{"name":"participant","type":"InputPeer"},{"name":"muted","type":"flags.0?Bool"},{"name":"volume","type":"flags.1?int"},{"name":"raise_hand","type":"flags.2?Bool"},{"name":"video_stopped","type":"flags.3?Bool"},{"name":"video_paused","type":"flags.4?Bool"},{"name":"presentation_paused","type":"flags.5?Bool"}],"type":"Updates"},{"id":"480685066","method":"phone.editGroupCallTitle","params":[{"name":"call","type":"InputGroupCall"},{"name":"title","type":"string"}],"type":"Updates"},{"id":"-277077702","method":"phone.getGroupCallJoinAs","params":[{"name":"peer","type":"InputPeer"}],"type":"phone.JoinAsPeers"},{"id":"-425040769","method":"phone.exportGroupCallInvite","params":[{"name":"flags","type":"#"},{"name":"can_self_unmute","type":"flags.0?true"},{"name":"call","type":"InputGroupCall"}],"type":"phone.ExportedGroupCallInvite"},{"id":"563885286","method":"phone.toggleGroupCallStartSubscription","params":[{"name":"call","type":"InputGroupCall"},{"name":"subscribed","type":"Bool"}],"type":"Updates"},{"id":"1451287362","method":"phone.startScheduledGroupCall","params":[{"name":"call","type":"InputGroupCall"}],"type":"Updates"},{"id":"1465786252","method":"phone.saveDefaultGroupCallJoinAs","params":[{"name":"peer","type":"InputPeer"},{"name":"join_as","type":"InputPeer"}],"type":"Bool"},{"id":"-873829436","method":"phone.joinGroupCallPresentation","params":[{"name":"call","type":"InputGroupCall"},{"name":"params","type":"DataJSON"}],"type":"Updates"},{"id":"475058500","method":"phone.leaveGroupCallPresentation","params":[{"name":"call","type":"InputGroupCall"}],"type":"Updates"},{"id":"676017721","method":"stickers.checkShortName","params":[{"name":"short_name","type":"string"}],"type":"Bool"},{"id":"1303364867","method":"stickers.suggestShortName","params":[{"name":"title","type":"string"}],"type":"stickers.SuggestedShortName"},{"id":"1032708345","method":"bots.resetBotCommands","params":[{"name":"scope","type":"BotCommandScope"},{"name":"lang_code","type":"string"}],"type":"Bool"},{"id":"-481554986","method":"bots.getBotCommands","params":[{"name":"scope","type":"BotCommandScope"},{"name":"lang_code","type":"string"}],"type":"Vector"},{"id":"-1828139493","method":"account.resetPassword","params":[],"type":"account.ResetPasswordResult"},{"id":"1284770294","method":"account.declinePasswordReset","params":[],"type":"Bool"},{"id":"221691769","method":"auth.checkRecoveryPassword","params":[{"name":"code","type":"string"}],"type":"Bool"},{"id":"-690545285","method":"account.getChatThemes","params":[{"name":"hash","type":"int"}],"type":"account.ChatThemes"},{"id":"-432283329","method":"messages.setChatTheme","params":[{"name":"peer","type":"InputPeer"},{"name":"emoticon","type":"string"}],"type":"Updates"},{"id":"-1095836780","method":"channels.viewSponsoredMessage","params":[{"name":"channel","type":"InputChannel"},{"name":"random_id","type":"bytes"}],"type":"Bool"},{"id":"-333377601","method":"channels.getSponsoredMessages","params":[{"name":"channel","type":"InputChannel"}],"type":"messages.SponsoredMessages"},{"id":"745510839","method":"messages.getMessageReadParticipants","params":[{"name":"peer","type":"InputPeer"},{"name":"msg_id","type":"int"}],"type":"Vector"}]} \ No newline at end of file diff --git a/data/corefork.telegram.org/schema/mtproto-json.html b/data/corefork.telegram.org/schema/mtproto-json.html deleted file mode 100644 index ceca9f3321..0000000000 --- a/data/corefork.telegram.org/schema/mtproto-json.html +++ /dev/null @@ -1 +0,0 @@ -{"constructors":[{"id":"481674261","predicate":"vector","params":[],"type":"Vector t"},{"id":"85337187","predicate":"resPQ","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"pq","type":"bytes"},{"name":"server_public_key_fingerprints","type":"Vector"}],"type":"ResPQ"},{"id":"-1443537003","predicate":"p_q_inner_data_dc","params":[{"name":"pq","type":"bytes"},{"name":"p","type":"bytes"},{"name":"q","type":"bytes"},{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"new_nonce","type":"int256"},{"name":"dc","type":"int"}],"type":"P_Q_inner_data"},{"id":"1459478408","predicate":"p_q_inner_data_temp_dc","params":[{"name":"pq","type":"bytes"},{"name":"p","type":"bytes"},{"name":"q","type":"bytes"},{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"new_nonce","type":"int256"},{"name":"dc","type":"int"},{"name":"expires_in","type":"int"}],"type":"P_Q_inner_data"},{"id":"-790100132","predicate":"server_DH_params_ok","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"encrypted_answer","type":"bytes"}],"type":"Server_DH_Params"},{"id":"-1249309254","predicate":"server_DH_inner_data","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"g","type":"int"},{"name":"dh_prime","type":"bytes"},{"name":"g_a","type":"bytes"},{"name":"server_time","type":"int"}],"type":"Server_DH_inner_data"},{"id":"1715713620","predicate":"client_DH_inner_data","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"retry_id","type":"long"},{"name":"g_b","type":"bytes"}],"type":"Client_DH_Inner_Data"},{"id":"1003222836","predicate":"dh_gen_ok","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"new_nonce_hash1","type":"int128"}],"type":"Set_client_DH_params_answer"},{"id":"1188831161","predicate":"dh_gen_retry","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"new_nonce_hash2","type":"int128"}],"type":"Set_client_DH_params_answer"},{"id":"-1499615742","predicate":"dh_gen_fail","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"new_nonce_hash3","type":"int128"}],"type":"Set_client_DH_params_answer"},{"id":"1973679973","predicate":"bind_auth_key_inner","params":[{"name":"nonce","type":"long"},{"name":"temp_auth_key_id","type":"long"},{"name":"perm_auth_key_id","type":"long"},{"name":"temp_session_id","type":"long"},{"name":"expires_at","type":"int"}],"type":"BindAuthKeyInner"},{"id":"-212046591","predicate":"rpc_result","params":[{"name":"req_msg_id","type":"long"},{"name":"result","type":"Object"}],"type":"RpcResult"},{"id":"558156313","predicate":"rpc_error","params":[{"name":"error_code","type":"int"},{"name":"error_message","type":"string"}],"type":"RpcError"},{"id":"1579864942","predicate":"rpc_answer_unknown","params":[],"type":"RpcDropAnswer"},{"id":"-847714938","predicate":"rpc_answer_dropped_running","params":[],"type":"RpcDropAnswer"},{"id":"-1539647305","predicate":"rpc_answer_dropped","params":[{"name":"msg_id","type":"long"},{"name":"seq_no","type":"int"},{"name":"bytes","type":"int"}],"type":"RpcDropAnswer"},{"id":"155834844","predicate":"future_salt","params":[{"name":"valid_since","type":"int"},{"name":"valid_until","type":"int"},{"name":"salt","type":"long"}],"type":"FutureSalt"},{"id":"-1370486635","predicate":"future_salts","params":[{"name":"req_msg_id","type":"long"},{"name":"now","type":"int"},{"name":"salts","type":"vector"}],"type":"FutureSalts"},{"id":"880243653","predicate":"pong","params":[{"name":"msg_id","type":"long"},{"name":"ping_id","type":"long"}],"type":"Pong"},{"id":"-501201412","predicate":"destroy_session_ok","params":[{"name":"session_id","type":"long"}],"type":"DestroySessionRes"},{"id":"1658015945","predicate":"destroy_session_none","params":[{"name":"session_id","type":"long"}],"type":"DestroySessionRes"},{"id":"-1631450872","predicate":"new_session_created","params":[{"name":"first_msg_id","type":"long"},{"name":"unique_id","type":"long"},{"name":"server_salt","type":"long"}],"type":"NewSession"},{"id":"1945237724","predicate":"msg_container","params":[{"name":"messages","type":"vector<%Message>"}],"type":"MessageContainer"},{"id":"1538843921","predicate":"message","params":[{"name":"msg_id","type":"long"},{"name":"seqno","type":"int"},{"name":"bytes","type":"int"},{"name":"body","type":"Object"}],"type":"Message"},{"id":"-530561358","predicate":"msg_copy","params":[{"name":"orig_message","type":"Message"}],"type":"MessageCopy"},{"id":"812830625","predicate":"gzip_packed","params":[{"name":"packed_data","type":"bytes"}],"type":"Object"},{"id":"1658238041","predicate":"msgs_ack","params":[{"name":"msg_ids","type":"Vector"}],"type":"MsgsAck"},{"id":"-1477445615","predicate":"bad_msg_notification","params":[{"name":"bad_msg_id","type":"long"},{"name":"bad_msg_seqno","type":"int"},{"name":"error_code","type":"int"}],"type":"BadMsgNotification"},{"id":"-307542917","predicate":"bad_server_salt","params":[{"name":"bad_msg_id","type":"long"},{"name":"bad_msg_seqno","type":"int"},{"name":"error_code","type":"int"},{"name":"new_server_salt","type":"long"}],"type":"BadMsgNotification"},{"id":"2105940488","predicate":"msg_resend_req","params":[{"name":"msg_ids","type":"Vector"}],"type":"MsgResendReq"},{"id":"-630588590","predicate":"msgs_state_req","params":[{"name":"msg_ids","type":"Vector"}],"type":"MsgsStateReq"},{"id":"81704317","predicate":"msgs_state_info","params":[{"name":"req_msg_id","type":"long"},{"name":"info","type":"bytes"}],"type":"MsgsStateInfo"},{"id":"-1933520591","predicate":"msgs_all_info","params":[{"name":"msg_ids","type":"Vector"},{"name":"info","type":"bytes"}],"type":"MsgsAllInfo"},{"id":"661470918","predicate":"msg_detailed_info","params":[{"name":"msg_id","type":"long"},{"name":"answer_msg_id","type":"long"},{"name":"bytes","type":"int"},{"name":"status","type":"int"}],"type":"MsgDetailedInfo"},{"id":"-2137147681","predicate":"msg_new_detailed_info","params":[{"name":"answer_msg_id","type":"long"},{"name":"bytes","type":"int"},{"name":"status","type":"int"}],"type":"MsgDetailedInfo"},{"id":"-161422892","predicate":"destroy_auth_key_ok","params":[],"type":"DestroyAuthKeyRes"},{"id":"178201177","predicate":"destroy_auth_key_none","params":[],"type":"DestroyAuthKeyRes"},{"id":"-368010477","predicate":"destroy_auth_key_fail","params":[],"type":"DestroyAuthKeyRes"}],"methods":[{"id":"-1099002127","method":"req_pq_multi","params":[{"name":"nonce","type":"int128"}],"type":"ResPQ"},{"id":"-686627650","method":"req_DH_params","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"p","type":"bytes"},{"name":"q","type":"bytes"},{"name":"public_key_fingerprint","type":"long"},{"name":"encrypted_data","type":"bytes"}],"type":"Server_DH_Params"},{"id":"-184262881","method":"set_client_DH_params","params":[{"name":"nonce","type":"int128"},{"name":"server_nonce","type":"int128"},{"name":"encrypted_data","type":"bytes"}],"type":"Set_client_DH_params_answer"},{"id":"1491380032","method":"rpc_drop_answer","params":[{"name":"req_msg_id","type":"long"}],"type":"RpcDropAnswer"},{"id":"-1188971260","method":"get_future_salts","params":[{"name":"num","type":"int"}],"type":"FutureSalts"},{"id":"2059302892","method":"ping","params":[{"name":"ping_id","type":"long"}],"type":"Pong"},{"id":"-213746804","method":"ping_delay_disconnect","params":[{"name":"ping_id","type":"long"},{"name":"disconnect_delay","type":"int"}],"type":"Pong"},{"id":"-414113498","method":"destroy_session","params":[{"name":"session_id","type":"long"}],"type":"DestroySessionRes"},{"id":"-1835453025","method":"http_wait","params":[{"name":"max_delay","type":"int"},{"name":"wait_after","type":"int"},{"name":"max_wait","type":"int"}],"type":"HttpWait"},{"id":"-784117408","method":"destroy_auth_key","params":[],"type":"DestroyAuthKeyRes"}]} \ No newline at end of file diff --git a/data/corefork.telegram.org/schema/mtproto.html b/data/corefork.telegram.org/schema/mtproto.html deleted file mode 100644 index 4da64ba771..0000000000 --- a/data/corefork.telegram.org/schema/mtproto.html +++ /dev/null @@ -1,204 +0,0 @@ - - - - - Current MTProto TL-schema - - - - - - - - - - - - - -
- -
-
-
- -

Current MTProto TL-schema

- -

Below you will find the current MTProto TL-schema. More details on TL »

-

See also the detailed schema in JSON »

-


-
int ? = Int;
-long ? = Long;
-double ? = Double;
-string ? = String;
-
-vector {t:Type} # [ t ] = Vector t;
-
-int128 4*[ int ] = Int128;
-int256 8*[ int ] = Int256;
-
-resPQ#05162463 nonce:int128 server_nonce:int128 pq:bytes server_public_key_fingerprints:Vector<long> = ResPQ;
-
-p_q_inner_data_dc#a9f55f95 pq:bytes p:bytes q:bytes nonce:int128 server_nonce:int128 new_nonce:int256 dc:int = P_Q_inner_data;
-p_q_inner_data_temp_dc#56fddf88 pq:bytes p:bytes q:bytes nonce:int128 server_nonce:int128 new_nonce:int256 dc:int expires_in:int = P_Q_inner_data;
-
-server_DH_params_ok#d0e8075c nonce:int128 server_nonce:int128 encrypted_answer:bytes = Server_DH_Params;
-
-server_DH_inner_data#b5890dba nonce:int128 server_nonce:int128 g:int dh_prime:bytes g_a:bytes server_time:int = Server_DH_inner_data;
-
-client_DH_inner_data#6643b654 nonce:int128 server_nonce:int128 retry_id:long g_b:bytes = Client_DH_Inner_Data;
-
-dh_gen_ok#3bcbf734 nonce:int128 server_nonce:int128 new_nonce_hash1:int128 = Set_client_DH_params_answer;
-dh_gen_retry#46dc1fb9 nonce:int128 server_nonce:int128 new_nonce_hash2:int128 = Set_client_DH_params_answer;
-dh_gen_fail#a69dae02 nonce:int128 server_nonce:int128 new_nonce_hash3:int128 = Set_client_DH_params_answer;
-
-bind_auth_key_inner#75a3f765 nonce:long temp_auth_key_id:long perm_auth_key_id:long temp_session_id:long expires_at:int = BindAuthKeyInner;
-
-rpc_result#f35c6d01 req_msg_id:long result:Object = RpcResult;
-rpc_error#2144ca19 error_code:int error_message:string = RpcError;
-
-rpc_answer_unknown#5e2ad36e = RpcDropAnswer;
-rpc_answer_dropped_running#cd78e586 = RpcDropAnswer;
-rpc_answer_dropped#a43ad8b7 msg_id:long seq_no:int bytes:int = RpcDropAnswer;
-
-future_salt#0949d9dc valid_since:int valid_until:int salt:long = FutureSalt;
-future_salts#ae500895 req_msg_id:long now:int salts:vector<future_salt> = FutureSalts;
-
-pong#347773c5 msg_id:long ping_id:long = Pong;
-
-destroy_session_ok#e22045fc session_id:long = DestroySessionRes;
-destroy_session_none#62d350c9 session_id:long = DestroySessionRes;
-
-new_session_created#9ec20908 first_msg_id:long unique_id:long server_salt:long = NewSession;
-
-msg_container#73f1f8dc messages:vector<%Message> = MessageContainer;
-message msg_id:long seqno:int bytes:int body:Object = Message;
-msg_copy#e06046b2 orig_message:Message = MessageCopy;
-
-gzip_packed#3072cfa1 packed_data:bytes = Object;
-
-msgs_ack#62d6b459 msg_ids:Vector<long> = MsgsAck;
-
-bad_msg_notification#a7eff811 bad_msg_id:long bad_msg_seqno:int error_code:int = BadMsgNotification;
-bad_server_salt#edab447b bad_msg_id:long bad_msg_seqno:int error_code:int new_server_salt:long = BadMsgNotification;
-
-msg_resend_req#7d861a08 msg_ids:Vector<long> = MsgResendReq;
-msgs_state_req#da69fb52 msg_ids:Vector<long> = MsgsStateReq;
-msgs_state_info#04deb57d req_msg_id:long info:bytes = MsgsStateInfo;
-msgs_all_info#8cc0d131 msg_ids:Vector<long> info:bytes = MsgsAllInfo;
-msg_detailed_info#276d3ec6 msg_id:long answer_msg_id:long bytes:int status:int = MsgDetailedInfo;
-msg_new_detailed_info#809db6df answer_msg_id:long bytes:int status:int = MsgDetailedInfo;
-
-destroy_auth_key_ok#f660e1d4 = DestroyAuthKeyRes;
-destroy_auth_key_none#0a9f2259 = DestroyAuthKeyRes;
-destroy_auth_key_fail#ea109b13 = DestroyAuthKeyRes;
-
----functions---
-
-req_pq_multi#be7e8ef1 nonce:int128 = ResPQ;
-
-req_DH_params#d712e4be nonce:int128 server_nonce:int128 p:bytes q:bytes public_key_fingerprint:long encrypted_data:bytes = Server_DH_Params;
-
-set_client_DH_params#f5045f1f nonce:int128 server_nonce:int128 encrypted_data:bytes = Set_client_DH_params_answer;
-
-rpc_drop_answer#58e4a740 req_msg_id:long = RpcDropAnswer;
-get_future_salts#b921bd04 num:int = FutureSalts;
-ping#7abe77ec ping_id:long = Pong;
-ping_delay_disconnect#f3427b8c ping_id:long disconnect_delay:int = Pong;
-destroy_session#e7512126 session_id:long = DestroySessionRes;
-
-http_wait#9299359f max_delay:int wait_after:int max_wait:int = HttpWait;
-
-destroy_auth_key#d1435160 = DestroyAuthKeyRes;
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/AccountDaysTTL.html b/data/corefork.telegram.org/type/AccountDaysTTL.html deleted file mode 100644 index 86dd14f653..0000000000 --- a/data/corefork.telegram.org/type/AccountDaysTTL.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - AccountDaysTTL - - - - - - - - - - - - - -
- -
-
-
- -

AccountDaysTTL

- -

Time-to-live of current account

-

- -
-
accountDaysTTL#b8d0afdf days:int = AccountDaysTTL;
-
----functions---
-
-account.getAccountTTL#8fc711d = AccountDaysTTL;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
accountDaysTTLTime to live in days of the current account
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getAccountTTLGet days to live of account
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/Audio.html b/data/corefork.telegram.org/type/Audio.html deleted file mode 100644 index 7a36aea12c..0000000000 --- a/data/corefork.telegram.org/type/Audio.html +++ /dev/null @@ -1,128 +0,0 @@ - - - - - Audio - - - - - - - - - - - - - -
- -
-
-
- -

Audio

- -

Audio file.

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/Authorization.html b/data/corefork.telegram.org/type/Authorization.html deleted file mode 100644 index dd13bba0a8..0000000000 --- a/data/corefork.telegram.org/type/Authorization.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Authorization - - - - - - - - - - - - - -
- -
-
-
- -

Authorization

- -

Represents a logged-in session

-

- -
-
authorization#ad01d61d flags:# current:flags.0?true official_app:flags.1?true password_pending:flags.2?true encrypted_requests_disabled:flags.3?true call_requests_disabled:flags.4?true hash:long device_model:string platform:string system_version:string api_id:int app_name:string app_version:string date_created:int date_active:int ip:string country:string region:string = Authorization;
-
----functions---
-
-auth.acceptLoginToken#e894ad4d token:bytes = Authorization;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
authorizationLogged-in session
-

Methods

- - - - - - - - - - - - - -
MethodDescription
auth.acceptLoginTokenLogin via QR code
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/AutoDownloadSettings.html b/data/corefork.telegram.org/type/AutoDownloadSettings.html deleted file mode 100644 index f5a0aa9ad8..0000000000 --- a/data/corefork.telegram.org/type/AutoDownloadSettings.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - AutoDownloadSettings - - - - - - - - - - - - - -
- -
-
-
- -

AutoDownloadSettings

- -

Media autodownload settings

-

- -
-
autoDownloadSettings#e04232f3 flags:# disabled:flags.0?true video_preload_large:flags.1?true audio_preload_next:flags.2?true phonecalls_less_data:flags.3?true photo_size_max:int video_size_max:int file_size_max:int video_upload_maxbitrate:int = AutoDownloadSettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
autoDownloadSettingsAutodownload settings
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/BankCardOpenUrl.html b/data/corefork.telegram.org/type/BankCardOpenUrl.html deleted file mode 100644 index dfad1a3f10..0000000000 --- a/data/corefork.telegram.org/type/BankCardOpenUrl.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - BankCardOpenUrl - - - - - - - - - - - - - -
- -
-
-
- -

BankCardOpenUrl

- -

Credit card info URL provided by the bank

-

- -
-
bankCardOpenUrl#f568028a url:string name:string = BankCardOpenUrl;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
bankCardOpenUrlCredit card info URL provided by the bank
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/BaseTheme.html b/data/corefork.telegram.org/type/BaseTheme.html deleted file mode 100644 index 5acb185325..0000000000 --- a/data/corefork.telegram.org/type/BaseTheme.html +++ /dev/null @@ -1,163 +0,0 @@ - - - - - BaseTheme - - - - - - - - - - - - - -
- -
-
-
- -

BaseTheme

- -

Basic theme settings

-

- -
-
baseThemeClassic#c3a12462 = BaseTheme;
-baseThemeDay#fbd81688 = BaseTheme;
-baseThemeNight#b7b31ea8 = BaseTheme;
-baseThemeTinted#6d5f77ee = BaseTheme;
-baseThemeArctic#5b11125a = BaseTheme;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
baseThemeClassicClassic theme
baseThemeDayDay theme
baseThemeNightNight theme
baseThemeTintedTinted theme
baseThemeArcticArctic theme
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/Bool.html b/data/corefork.telegram.org/type/Bool.html deleted file mode 100644 index defb5fde58..0000000000 --- a/data/corefork.telegram.org/type/Bool.html +++ /dev/null @@ -1,718 +0,0 @@ - - - - - Bool - - - - - - - - - - - - - -
- -
-
-
- -

Bool

- -

Boolean type.

-

- -
-
boolFalse#bc799737 = Bool;
-boolTrue#997275b5 = Bool;
-
----functions---
-
-auth.logOut#5717da40 = Bool;
-auth.resetAuthorizations#9fab0d1a = Bool;
-auth.bindTempAuthKey#cdd42a05 perm_auth_key_id:long nonce:long expires_at:int encrypted_message:bytes = Bool;
-auth.cancelCode#1f040578 phone_number:string phone_code_hash:string = Bool;
-auth.dropTempAuthKeys#8e48a188 except_auth_keys:Vector<long> = Bool;
-auth.checkRecoveryPassword#d36bf79 code:string = Bool;
-
-account.registerDevice#ec86017a flags:# no_muted:flags.0?true token_type:int token:string app_sandbox:Bool secret:bytes other_uids:Vector<long> = Bool;
-account.unregisterDevice#6a0d3206 token_type:int token:string other_uids:Vector<long> = Bool;
-account.updateNotifySettings#84be5b93 peer:InputNotifyPeer settings:InputPeerNotifySettings = Bool;
-account.resetNotifySettings#db7e1747 = Bool;
-account.updateStatus#6628562c offline:Bool = Bool;
-account.reportPeer#c5ba3d86 peer:InputPeer reason:ReportReason message:string = Bool;
-account.checkUsername#2714d86c username:string = Bool;
-account.deleteAccount#418d4e0b reason:string = Bool;
-account.setAccountTTL#2442485e ttl:AccountDaysTTL = Bool;
-account.updateDeviceLocked#38df3532 period:int = Bool;
-account.resetAuthorization#df77f3bc hash:long = Bool;
-account.updatePasswordSettings#a59b102f password:InputCheckPasswordSRP new_settings:account.PasswordInputSettings = Bool;
-account.confirmPhone#5f2178c3 phone_code_hash:string phone_code:string = Bool;
-account.resetWebAuthorization#2d01b9ef hash:long = Bool;
-account.resetWebAuthorizations#682d2594 = Bool;
-account.deleteSecureValue#b880bc4b types:Vector<SecureValueType> = Bool;
-account.acceptAuthorization#f3ed4c73 bot_id:long scope:string public_key:string value_hashes:Vector<SecureValueHash> credentials:SecureCredentialsEncrypted = Bool;
-account.verifyPhone#4dd3a7f6 phone_number:string phone_code_hash:string phone_code:string = Bool;
-account.verifyEmail#ecba39db email:string code:string = Bool;
-account.finishTakeoutSession#1d2652ee flags:# success:flags.0?true = Bool;
-account.confirmPasswordEmail#8fdf1920 code:string = Bool;
-account.resendPasswordEmail#7a7f2a15 = Bool;
-account.cancelPasswordEmail#c1cbd5b6 = Bool;
-account.getContactSignUpNotification#9f07c728 = Bool;
-account.setContactSignUpNotification#cff43f61 silent:Bool = Bool;
-account.saveWallPaper#6c5a5b37 wallpaper:InputWallPaper unsave:Bool settings:WallPaperSettings = Bool;
-account.installWallPaper#feed5769 wallpaper:InputWallPaper settings:WallPaperSettings = Bool;
-account.resetWallPapers#bb3b9804 = Bool;
-account.saveAutoDownloadSettings#76f36233 flags:# low:flags.0?true high:flags.1?true settings:AutoDownloadSettings = Bool;
-account.saveTheme#f257106c theme:InputTheme unsave:Bool = Bool;
-account.installTheme#7ae43737 flags:# dark:flags.0?true format:flags.1?string theme:flags.1?InputTheme = Bool;
-account.setContentSettings#b574b16b flags:# sensitive_enabled:flags.0?true = Bool;
-account.reportProfilePhoto#fa8cc6f5 peer:InputPeer photo_id:InputPhoto reason:ReportReason message:string = Bool;
-account.declinePasswordReset#4c9409f6 = Bool;
-
-contacts.deleteByPhones#1013fd9e phones:Vector<string> = Bool;
-contacts.block#68cc1411 id:InputPeer = Bool;
-contacts.unblock#bea65d50 id:InputPeer = Bool;
-contacts.resetTopPeerRating#1ae373ac category:TopPeerCategory peer:InputPeer = Bool;
-contacts.resetSaved#879537f1 = Bool;
-contacts.toggleTopPeers#8514bdda enabled:Bool = Bool;
-
-messages.setTyping#58943ee2 flags:# peer:InputPeer top_msg_id:flags.0?int action:SendMessageAction = Bool;
-messages.reportSpam#cf1592db peer:InputPeer = Bool;
-messages.report#8953ab4e peer:InputPeer id:Vector<int> reason:ReportReason message:string = Bool;
-messages.discardEncryption#f393aea0 flags:# delete_history:flags.0?true chat_id:int = Bool;
-messages.setEncryptedTyping#791451ed peer:InputEncryptedChat typing:Bool = Bool;
-messages.readEncryptedHistory#7f4b690a peer:InputEncryptedChat max_date:int = Bool;
-messages.reportEncryptedSpam#4b0c8c0f peer:InputEncryptedChat = Bool;
-messages.uninstallStickerSet#f96e55de stickerset:InputStickerSet = Bool;
-messages.editChatAdmin#a85bd1c2 chat_id:long user_id:InputUser is_admin:Bool = Bool;
-messages.reorderStickerSets#78337739 flags:# masks:flags.0?true order:Vector<long> = Bool;
-messages.saveGif#327a30cb id:InputDocument unsave:Bool = Bool;
-messages.setInlineBotResults#eb5ea206 flags:# gallery:flags.0?true private:flags.1?true query_id:long results:Vector<InputBotInlineResult> cache_time:int next_offset:flags.2?string switch_pm:flags.3?InlineBotSwitchPM = Bool;
-messages.editInlineBotMessage#83557dba flags:# no_webpage:flags.1?true id:InputBotInlineMessageID message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> = Bool;
-messages.setBotCallbackAnswer#d58f130a flags:# alert:flags.1?true query_id:long message:flags.0?string url:flags.2?string cache_time:int = Bool;
-messages.saveDraft#bc39e14b flags:# no_webpage:flags.1?true reply_to_msg_id:flags.0?int peer:InputPeer message:string entities:flags.3?Vector<MessageEntity> = Bool;
-messages.readFeaturedStickers#5b118126 id:Vector<long> = Bool;
-messages.saveRecentSticker#392718f8 flags:# attached:flags.0?true id:InputDocument unsave:Bool = Bool;
-messages.clearRecentStickers#8999602d flags:# attached:flags.0?true = Bool;
-messages.setInlineGameScore#15ad9f64 flags:# edit_message:flags.0?true force:flags.1?true id:InputBotInlineMessageID user_id:InputUser score:int = Bool;
-messages.toggleDialogPin#a731e257 flags:# pinned:flags.0?true peer:InputDialogPeer = Bool;
-messages.reorderPinnedDialogs#3b1adf37 flags:# force:flags.0?true folder_id:int order:Vector<InputDialogPeer> = Bool;
-messages.setBotShippingResults#e5f672fa flags:# query_id:long error:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = Bool;
-messages.setBotPrecheckoutResults#9c2dd95 flags:# success:flags.1?true query_id:long error:flags.0?string = Bool;
-messages.faveSticker#b9ffc55b id:InputDocument unfave:Bool = Bool;
-messages.markDialogUnread#c286d98f flags:# unread:flags.0?true peer:InputDialogPeer = Bool;
-messages.clearAllDrafts#7e58ee9c = Bool;
-messages.editChatAbout#def60797 peer:InputPeer about:string = Bool;
-messages.hidePeerSettingsBar#4facb138 peer:InputPeer = Bool;
-messages.toggleStickerSets#b5052fea flags:# uninstall:flags.0?true archive:flags.1?true unarchive:flags.2?true stickersets:Vector<InputStickerSet> = Bool;
-messages.updateDialogFilter#1ad4a04a flags:# id:int filter:flags.0?DialogFilter = Bool;
-messages.updateDialogFiltersOrder#c563c1e4 order:Vector<int> = Bool;
-messages.readDiscussion#f731a9f4 peer:InputPeer msg_id:int read_max_id:int = Bool;
-messages.deleteChat#5bd0ee50 chat_id:long = Bool;
-messages.startHistoryImport#b43df344 peer:InputPeer import_id:long = Bool;
-messages.deleteRevokedExportedChatInvites#56987bd5 peer:InputPeer admin_id:InputUser = Bool;
-messages.deleteExportedChatInvite#d464a42b peer:InputPeer link:string = Bool;
-
-upload.saveFilePart#b304a621 file_id:long file_part:int bytes:bytes = Bool;
-upload.saveBigFilePart#de7b673d file_id:long file_part:int file_total_parts:int bytes:bytes = Bool;
-
-channels.readHistory#cc104937 channel:InputChannel max_id:int = Bool;
-channels.reportSpam#fe087810 channel:InputChannel user_id:InputUser id:Vector<int> = Bool;
-channels.checkUsername#10e6bd2c channel:InputChannel username:string = Bool;
-channels.updateUsername#3514b3de channel:InputChannel username:string = Bool;
-channels.setStickers#ea8ca4f9 channel:InputChannel stickerset:InputStickerSet = Bool;
-channels.readMessageContents#eab5dc38 channel:InputChannel id:Vector<int> = Bool;
-channels.deleteHistory#af369d42 channel:InputChannel max_id:int = Bool;
-channels.setDiscussionGroup#40582bb2 broadcast:InputChannel group:InputChannel = Bool;
-channels.editLocation#58e63f6d channel:InputChannel geo_point:InputGeoPoint address:string = Bool;
-channels.viewSponsoredMessage#beaedb94 channel:InputChannel random_id:bytes = Bool;
-
-help.setBotUpdatesStatus#ec22cfcd pending_updates_count:int message:string = Bool;
-help.acceptTermsOfService#ee72f79a id:DataJSON = Bool;
-help.saveAppLog#6f02f748 events:Vector<InputAppEvent> = Bool;
-help.hidePromoData#1e251c95 peer:InputPeer = Bool;
-help.dismissSuggestion#f50dbaa1 peer:InputPeer suggestion:string = Bool;
-
-bots.answerWebhookJSONQuery#e6213f4d query_id:long data:DataJSON = Bool;
-bots.setBotCommands#517165a scope:BotCommandScope lang_code:string commands:Vector<BotCommand> = Bool;
-bots.resetBotCommands#3d8de0f9 scope:BotCommandScope lang_code:string = Bool;
-
-payments.clearSavedInfo#d83d70c1 flags:# credentials:flags.0?true info:flags.1?true = Bool;
-
-phone.receivedCall#17d54f61 peer:InputPhoneCall = Bool;
-phone.saveCallDebug#277add7e peer:InputPhoneCall debug:DataJSON = Bool;
-phone.sendSignalingData#ff7a9383 peer:InputPhoneCall data:bytes = Bool;
-phone.saveDefaultGroupCallJoinAs#575e1f8c peer:InputPeer join_as:InputPeer = Bool;
-
-users.setSecureValueErrors#90c894b5 id:InputUser errors:Vector<SecureValueError> = Bool;
-
-stickers.checkShortName#284b3639 short_name:string = Bool;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
boolFalseConstructor may be interpreted as a booleanfalse value.
boolTrueThe constructor can be interpreted as a booleantrue value.
-

Methods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
MethodDescription
auth.logOutLogs out the user.
auth.resetAuthorizationsTerminates all user's authorized sessions except for the current one.

After calling this method it is necessary to reregister the current device using the method account.registerDevice
auth.bindTempAuthKeyBinds a temporary authorization key temp_auth_key_id to the permanent authorization key perm_auth_key_id. Each permanent key may only be bound to one temporary key at a time, binding a new temporary key overwrites the previous one.

For more information, see Perfect Forward Secrecy.
account.registerDeviceRegister device to receive PUSH notifications
account.unregisterDeviceDeletes a device by its token, stops sending PUSH-notifications to it.
account.updateNotifySettingsEdits notification settings from a given user/group, from all users/all groups.
account.resetNotifySettingsResets all notification settings from users and groups.
account.updateStatusUpdates online user status.
account.reportPeerReport a peer for violation of telegram's Terms of Service
contacts.deleteByPhonesDelete contacts by phone number
contacts.blockAdds the user to the blacklist.
contacts.unblockDeletes the user from the blacklist.
messages.setTypingSends a current user typing event (see SendMessageAction for all event types) to a conversation partner or group.
messages.reportSpamReport a new incoming chat for spam, if the peer settings of the chat allow us to do that
messages.reportReport a message in a chat for violation of telegram's Terms of Service
upload.saveFilePartSaves a part of file for futher sending to one of the methods.
messages.discardEncryptionCancels a request for creation and/or delete info on secret chat.
messages.setEncryptedTypingSend typing event by the current user to a secret chat.
messages.readEncryptedHistoryMarks message history within a secret chat as read.
messages.reportEncryptedSpamReport a secret chat for spam
upload.saveBigFilePartSaves a part of a large file (over 10Mb in size) to be later passed to one of the methods.
account.checkUsernameValidates a username and checks availability.
account.deleteAccountDelete the user's account from the telegram servers. Can be used, for example, to delete the account of a user that provided the login code, but forgot the 2FA password and no recovery method is configured.
account.setAccountTTLSet account self-destruction period
account.updateDeviceLockedWhen client-side passcode lock feature is enabled, will not show message texts in incoming PUSH notifications.
account.resetAuthorizationLog out an active authorized session by it hash
account.updatePasswordSettingsSet a new 2FA password
messages.uninstallStickerSetUninstall a stickerset
channels.readHistoryMark channel/supergroup history as read
channels.reportSpamReports some messages from a user in a supergroup as spam; requires administrator rights in the supergroup
channels.checkUsernameCheck if a username is free and can be assigned to a channel/supergroup
channels.updateUsernameChange the username of a supergroup/channel
messages.editChatAdminMake a user admin in a legacy group.
messages.reorderStickerSetsReorder installed stickersets
messages.saveGifAdd GIF to saved gifs list
messages.setInlineBotResultsAnswer an inline query, for bots only
auth.cancelCodeCancel the login verification code
messages.editInlineBotMessageEdit an inline bot message
messages.setBotCallbackAnswerSet the callback answer to a user button press (bots only)
contacts.resetTopPeerRatingReset rating of top peer
messages.saveDraftSave a message draft associated to a chat.
messages.readFeaturedStickersMark new featured stickers as read
messages.saveRecentStickerAdd/remove sticker from recent stickers list
messages.clearRecentStickersClear recent stickers
account.confirmPhoneConfirm a phone number to cancel account deletion, for more info click here »
auth.dropTempAuthKeysDelete all temporary authorization keys except for the ones specified
messages.setInlineGameScoreUse this method to set the score of the specified user in a game sent as an inline message (bots only).
help.setBotUpdatesStatusInforms the server about the number of pending bot updates if they haven't been processed for a long time; for bots only
messages.toggleDialogPinPin/unpin a dialog
messages.reorderPinnedDialogsReorder pinned dialogs
bots.answerWebhookJSONQueryAnswers a custom query; for bots only
payments.clearSavedInfoClear saved payment information
messages.setBotShippingResultsIf you sent an invoice requesting a shipping address and the parameter is_flexible was specified, the bot will receive an updateBotShippingQuery update. Use this method to reply to shipping queries.
messages.setBotPrecheckoutResultsOnce the user has confirmed their payment and shipping details, the bot receives an updateBotPrecheckoutQuery update.
Use this method to respond to such pre-checkout queries.
Note: Telegram must receive an answer within 10 seconds after the pre-checkout query was sent.
phone.receivedCallOptional: notify the server that the user is currently busy in a call: this will automatically refuse all incoming phone calls until the current phone call is ended.
phone.saveCallDebugSend phone call debug data to server
channels.setStickersAssociate a stickerset to the supergroup
messages.faveStickerMark a sticker as favorite
channels.readMessageContentsMark channel/supergroup message contents as read
contacts.resetSavedDelete saved contacts
channels.deleteHistoryDelete the history of a supergroup
account.resetWebAuthorizationLog out an active web telegram login session
account.resetWebAuthorizationsReset all active web telegram login sessions
help.acceptTermsOfServiceAccept the new terms of service
account.deleteSecureValueDelete stored telegram passport value
users.setSecureValueErrorsSet secure passport value errors for a user
account.acceptAuthorizationSends a Telegram Passport authorization form, effectively sharing data with the service
account.verifyPhoneVerify a phone number for telegram passport.
account.verifyEmailVerify an email address for telegram passport.
account.finishTakeoutSessionFinish account takeout session
messages.markDialogUnreadManually mark dialog as unread
contacts.toggleTopPeersEnable/disable top peers
messages.clearAllDraftsClear all drafts.
help.saveAppLogSaves logs of application on the server.
account.confirmPasswordEmailVerify an email to use as 2FA recovery method.
account.resendPasswordEmailResend the code to verify an email to use as 2FA recovery method.
account.cancelPasswordEmailCancel the code that was sent to verify an email to use as 2FA recovery method.
account.getContactSignUpNotificationWhether the user will receive notifications when contacts sign up
account.setContactSignUpNotificationToggle contact sign up notifications
messages.editChatAboutEdit the description of a group/supergroup/channel.
account.saveWallPaperInstall/uninstall wallpaper
account.installWallPaperInstall wallpaper
account.resetWallPapersDelete installed wallpapers
account.saveAutoDownloadSettingsChange media autodownload settings
channels.setDiscussionGroupAssociate a group to a channel as discussion group for that channel
messages.hidePeerSettingsBarShould be called after the user hides the report spam/add as contact bar of a new chat, effectively prevents the user from executing the actions specified in the peer's settings.
channels.editLocationEdit location of geogroup
account.saveThemeSave a theme
account.installThemeInstall a theme
account.setContentSettingsSet sensitive content settings (for viewing or hiding NSFW content)
messages.toggleStickerSetsApply changes to multiple stickersets
messages.updateDialogFilterUpdate folder
messages.updateDialogFiltersOrderReorder folders
bots.setBotCommandsSet bot command list
help.hidePromoDataHide MTProxy/Public Service Announcement information
phone.sendSignalingDataSend VoIP signaling data
help.dismissSuggestionDismiss a suggestion
messages.readDiscussionMark a channel discussion as read
messages.deleteChatDelete a chat
messages.startHistoryImportComplete the history import process, importing all messages into the chat.
To be called only after initializing the import with messages.initHistoryImport and uploading all files using messages.uploadImportedMedia.
messages.deleteRevokedExportedChatInvitesDelete all revoked chat invites
messages.deleteExportedChatInviteDelete a chat invite
account.reportProfilePhotoReport a profile photo of a dialog
phone.saveDefaultGroupCallJoinAsSet the default peer that will be used to join a group call in a specific dialog.
stickers.checkShortNameCheck whether the given short name is available
bots.resetBotCommandsClear bot commands for the specified bot scope and language code
account.declinePasswordResetAbort a pending 2FA password reset
auth.checkRecoveryPasswordCheck if the recovery code sent using auth.requestPasswordRecovery is valid, before passing it to auth.recoverPassword.
channels.viewSponsoredMessageMark a specific sponsored message as read
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/BotCommand.html b/data/corefork.telegram.org/type/BotCommand.html deleted file mode 100644 index a72d6a6079..0000000000 --- a/data/corefork.telegram.org/type/BotCommand.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - BotCommand - - - - - - - - - - - - - -
- -
-
-
- -

BotCommand

- -

Describes a bot command that can be used in a chat

-

- -
-
botCommand#c27ac8c7 command:string description:string = BotCommand;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
botCommandDescribes a bot command that can be used in a chat
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/BotCommandScope.html b/data/corefork.telegram.org/type/BotCommandScope.html deleted file mode 100644 index b2127395a6..0000000000 --- a/data/corefork.telegram.org/type/BotCommandScope.html +++ /dev/null @@ -1,176 +0,0 @@ - - - - - BotCommandScope - - - - - - - - - - - - - -
- -
-
-
- -

BotCommandScope

- -

Represents a scope where the bot commands, specified using bots.setBotCommands will be valid.

-

- -
-
botCommandScopeDefault#2f6cb2ab = BotCommandScope;
-botCommandScopeUsers#3c4f04d8 = BotCommandScope;
-botCommandScopeChats#6fe1a881 = BotCommandScope;
-botCommandScopeChatAdmins#b9aa606a = BotCommandScope;
-botCommandScopePeer#db9d897d peer:InputPeer = BotCommandScope;
-botCommandScopePeerAdmins#3fd863d1 peer:InputPeer = BotCommandScope;
-botCommandScopePeerUser#a1321f3 peer:InputPeer user_id:InputUser = BotCommandScope;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
botCommandScopeDefaultThe commands will be valid in all chats
botCommandScopeUsersThe specified bot commands will only be valid in all private chats with users.
botCommandScopeChatsThe specified bot commands will be valid in all groups and supergroups
botCommandScopeChatAdminsThe specified bot commands will be valid only for chat administrators, in all groups and supergroups.
botCommandScopePeerThe specified bot commands will be valid only in a specific dialog
botCommandScopePeerAdminsThe specified bot commands will be valid for all admins of the specified group or supergroup.
botCommandScopePeerUserThe specified bot commands will be valid only for a specific user in the specified chat
-

Related pages

-

bots.setBotCommands

-

Set bot command list

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/BotInfo.html b/data/corefork.telegram.org/type/BotInfo.html deleted file mode 100644 index c5c28b73d6..0000000000 --- a/data/corefork.telegram.org/type/BotInfo.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - BotInfo - - - - - - - - - - - - - -
- -
-
-
- -

BotInfo

- -

Info about bots (available bot commands, etc)

-

- -
-
botInfo#1b74b335 user_id:long description:string commands:Vector<BotCommand> = BotInfo;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
botInfoInfo about bots (available bot commands, etc)
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/BotInlineMessage.html b/data/corefork.telegram.org/type/BotInlineMessage.html deleted file mode 100644 index 11de0a5422..0000000000 --- a/data/corefork.telegram.org/type/BotInlineMessage.html +++ /dev/null @@ -1,168 +0,0 @@ - - - - - BotInlineMessage - - - - - - - - - - - - - -
- -
-
-
- -

BotInlineMessage

- -

Inline message

-

- -
-
botInlineMessageMediaAuto#764cf810 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-botInlineMessageText#8c7f65e2 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-botInlineMessageMediaGeo#51846fd flags:# geo:GeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-botInlineMessageMediaVenue#8a86659c flags:# geo:GeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-botInlineMessageMediaContact#18d1cdc2 flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = BotInlineMessage;
-botInlineMessageMediaInvoice#354a9b09 flags:# shipping_address_requested:flags.1?true test:flags.3?true title:string description:string photo:flags.0?WebDocument currency:string total_amount:long reply_markup:flags.2?ReplyMarkup = BotInlineMessage;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
botInlineMessageMediaAutoSend whatever media is attached to the botInlineMediaResult
botInlineMessageTextSend a simple text message
botInlineMessageMediaGeoSend a geolocation
botInlineMessageMediaVenueSend a venue
botInlineMessageMediaContactSend a contact
botInlineMessageMediaInvoiceSend an invoice
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/BotInlineResult.html b/data/corefork.telegram.org/type/BotInlineResult.html deleted file mode 100644 index 3d88f40e0d..0000000000 --- a/data/corefork.telegram.org/type/BotInlineResult.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - BotInlineResult - - - - - - - - - - - - - -
- -
-
-
- -

BotInlineResult

- -

Results of an inline query

-

- -
-
botInlineResult#11965f3a flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?WebDocument content:flags.5?WebDocument send_message:BotInlineMessage = BotInlineResult;
-botInlineMediaResult#17db940b flags:# id:string type:string photo:flags.0?Photo document:flags.1?Document title:flags.2?string description:flags.3?string send_message:BotInlineMessage = BotInlineResult;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
botInlineResultGeneric result
botInlineMediaResultMedia result
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/CdnConfig.html b/data/corefork.telegram.org/type/CdnConfig.html deleted file mode 100644 index 4bec9e352c..0000000000 --- a/data/corefork.telegram.org/type/CdnConfig.html +++ /dev/null @@ -1,164 +0,0 @@ - - - - - CdnConfig - - - - - - - - - - - - - -
- -
-
-
- -

CdnConfig

- -

Configuration for CDN file downloads.

-

- -
-
cdnConfig#5725e40a public_keys:Vector<CdnPublicKey> = CdnConfig;
-
----functions---
-
-help.getCdnConfig#52029342 = CdnConfig;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
cdnConfigConfiguration for CDN file downloads.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getCdnConfigGet configuration for CDN file downloads.
-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/CdnPublicKey.html b/data/corefork.telegram.org/type/CdnPublicKey.html deleted file mode 100644 index 488f95b2a6..0000000000 --- a/data/corefork.telegram.org/type/CdnPublicKey.html +++ /dev/null @@ -1,145 +0,0 @@ - - - - - CdnPublicKey - - - - - - - - - - - - - -
- -
-
-
- -

CdnPublicKey

- -

Public key to use only during handshakes to CDN DCs.

-

- -
-
cdnPublicKey#c982eaba dc_id:int public_key:string = CdnPublicKey;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
cdnPublicKeyPublic key to use only during handshakes to CDN DCs.
-

Related pages

-

Encrypted CDNs for Speed and Security

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ChannelAdminLogEvent.html b/data/corefork.telegram.org/type/ChannelAdminLogEvent.html deleted file mode 100644 index b298a682d4..0000000000 --- a/data/corefork.telegram.org/type/ChannelAdminLogEvent.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - ChannelAdminLogEvent - - - - - - - - - - - - - -
- -
-
-
- -

ChannelAdminLogEvent

- -

An event in a channel admin log

-

- -
-
channelAdminLogEvent#1fad68cd id:long date:int user_id:long action:ChannelAdminLogEventAction = ChannelAdminLogEvent;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
channelAdminLogEventAdmin log event
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ChannelAdminLogEventAction.html b/data/corefork.telegram.org/type/ChannelAdminLogEventAction.html deleted file mode 100644 index 3376d17ab9..0000000000 --- a/data/corefork.telegram.org/type/ChannelAdminLogEventAction.html +++ /dev/null @@ -1,298 +0,0 @@ - - - - - ChannelAdminLogEventAction - - - - - - - - - - - - - -
- -
-
-
- -

ChannelAdminLogEventAction

- -

Channel admin log event

-

- -
-
channelAdminLogEventActionChangeTitle#e6dfb825 prev_value:string new_value:string = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeAbout#55188a2e prev_value:string new_value:string = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeUsername#6a4afc38 prev_value:string new_value:string = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangePhoto#434bd2af prev_photo:Photo new_photo:Photo = ChannelAdminLogEventAction;
-channelAdminLogEventActionToggleInvites#1b7907ae new_value:Bool = ChannelAdminLogEventAction;
-channelAdminLogEventActionToggleSignatures#26ae0971 new_value:Bool = ChannelAdminLogEventAction;
-channelAdminLogEventActionUpdatePinned#e9e82c18 message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionEditMessage#709b2405 prev_message:Message new_message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionDeleteMessage#42e047bb message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantJoin#183040d3 = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantLeave#f89777f2 = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantInvite#e31c34d8 participant:ChannelParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantToggleBan#e6d83d7e prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantToggleAdmin#d5676710 prev_participant:ChannelParticipant new_participant:ChannelParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeStickerSet#b1c3caa7 prev_stickerset:InputStickerSet new_stickerset:InputStickerSet = ChannelAdminLogEventAction;
-channelAdminLogEventActionTogglePreHistoryHidden#5f5c95f1 new_value:Bool = ChannelAdminLogEventAction;
-channelAdminLogEventActionDefaultBannedRights#2df5fc0a prev_banned_rights:ChatBannedRights new_banned_rights:ChatBannedRights = ChannelAdminLogEventAction;
-channelAdminLogEventActionStopPoll#8f079643 message:Message = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeLinkedChat#50c7ac8 prev_value:long new_value:long = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeLocation#e6b76ae prev_value:ChannelLocation new_value:ChannelLocation = ChannelAdminLogEventAction;
-channelAdminLogEventActionToggleSlowMode#53909779 prev_value:int new_value:int = ChannelAdminLogEventAction;
-channelAdminLogEventActionStartGroupCall#23209745 call:InputGroupCall = ChannelAdminLogEventAction;
-channelAdminLogEventActionDiscardGroupCall#db9f9140 call:InputGroupCall = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantMute#f92424d2 participant:GroupCallParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantUnmute#e64429c0 participant:GroupCallParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionToggleGroupCallSetting#56d6a247 join_muted:Bool = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantJoinByInvite#5cdada77 invite:ExportedChatInvite = ChannelAdminLogEventAction;
-channelAdminLogEventActionExportedInviteDelete#5a50fca4 invite:ExportedChatInvite = ChannelAdminLogEventAction;
-channelAdminLogEventActionExportedInviteRevoke#410a134e invite:ExportedChatInvite = ChannelAdminLogEventAction;
-channelAdminLogEventActionExportedInviteEdit#e90ebb59 prev_invite:ExportedChatInvite new_invite:ExportedChatInvite = ChannelAdminLogEventAction;
-channelAdminLogEventActionParticipantVolume#3e7f6847 participant:GroupCallParticipant = ChannelAdminLogEventAction;
-channelAdminLogEventActionChangeHistoryTTL#6e941a38 prev_value:int new_value:int = ChannelAdminLogEventAction;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
channelAdminLogEventActionChangeTitleChannel/supergroup title was changed
channelAdminLogEventActionChangeAboutThe description was changed
channelAdminLogEventActionChangeUsernameChannel/supergroup username was changed
channelAdminLogEventActionChangePhotoThe channel/supergroup's picture was changed
channelAdminLogEventActionToggleInvitesInvites were enabled/disabled
channelAdminLogEventActionToggleSignaturesChannel signatures were enabled/disabled
channelAdminLogEventActionUpdatePinnedA message was pinned
channelAdminLogEventActionEditMessageA message was edited
channelAdminLogEventActionDeleteMessageA message was deleted
channelAdminLogEventActionParticipantJoinA user has joined the group (in the case of big groups, info of the user that has joined isn't shown)
channelAdminLogEventActionParticipantLeaveA user left the channel/supergroup (in the case of big groups, info of the user that has joined isn't shown)
channelAdminLogEventActionParticipantInviteA user was invited to the group
channelAdminLogEventActionParticipantToggleBanThe banned rights of a user were changed
channelAdminLogEventActionParticipantToggleAdminThe admin rights of a user were changed
channelAdminLogEventActionChangeStickerSetThe supergroup's stickerset was changed
channelAdminLogEventActionTogglePreHistoryHiddenThe hidden prehistory setting was changed
channelAdminLogEventActionDefaultBannedRightsThe default banned rights were modified
channelAdminLogEventActionStopPollA poll was stopped
channelAdminLogEventActionChangeLinkedChatThe linked chat was changed
channelAdminLogEventActionChangeLocationThe geogroup location was changed
channelAdminLogEventActionToggleSlowModeSlow mode setting for supergroups was changed
channelAdminLogEventActionStartGroupCallA group call was started
channelAdminLogEventActionDiscardGroupCallA group call was terminated
channelAdminLogEventActionParticipantMuteA group call participant was muted
channelAdminLogEventActionParticipantUnmuteA group call participant was unmuted
channelAdminLogEventActionToggleGroupCallSettingGroup call settings were changed
channelAdminLogEventActionParticipantJoinByInviteA user joined the supergroup/channel using a specific invite link
channelAdminLogEventActionExportedInviteDeleteA chat invite was deleted
channelAdminLogEventActionExportedInviteRevokeA specific invite link was revoked
channelAdminLogEventActionExportedInviteEditA chat invite was edited
channelAdminLogEventActionParticipantVolumechannelAdminLogEvent.user_id has set the volume of participant.peer to participant.volume
channelAdminLogEventActionChangeHistoryTTLThe Time-To-Live of messages in this chat was changed
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ChannelAdminLogEventsFilter.html b/data/corefork.telegram.org/type/ChannelAdminLogEventsFilter.html deleted file mode 100644 index f32ee6ac3c..0000000000 --- a/data/corefork.telegram.org/type/ChannelAdminLogEventsFilter.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - ChannelAdminLogEventsFilter - - - - - - - - - - - - - -
- -
-
-
- -

ChannelAdminLogEventsFilter

- -

Filter for fetching events in the channel admin log

-

- -
-
channelAdminLogEventsFilter#ea107ae4 flags:# join:flags.0?true leave:flags.1?true invite:flags.2?true ban:flags.3?true unban:flags.4?true kick:flags.5?true unkick:flags.6?true promote:flags.7?true demote:flags.8?true info:flags.9?true settings:flags.10?true pinned:flags.11?true edit:flags.12?true delete:flags.13?true group_call:flags.14?true invites:flags.15?true send:flags.16?true = ChannelAdminLogEventsFilter;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
channelAdminLogEventsFilterFilter only certain admin log events
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ChannelLocation.html b/data/corefork.telegram.org/type/ChannelLocation.html deleted file mode 100644 index 22f5204f31..0000000000 --- a/data/corefork.telegram.org/type/ChannelLocation.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - ChannelLocation - - - - - - - - - - - - - -
- -
-
-
- -

ChannelLocation

- -

Geographical location of supergroup (geogroups)

-

- -
-
channelLocationEmpty#bfb5ad8b = ChannelLocation;
-channelLocation#209b82db geo_point:GeoPoint address:string = ChannelLocation;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
channelLocationEmptyNo location (normal supergroup)
channelLocationGeographical location of supergroup (geogroups)
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ChannelMessagesFilter.html b/data/corefork.telegram.org/type/ChannelMessagesFilter.html deleted file mode 100644 index 2929b021ba..0000000000 --- a/data/corefork.telegram.org/type/ChannelMessagesFilter.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - ChannelMessagesFilter - - - - - - - - - - - - - -
- -
-
-
- -

ChannelMessagesFilter

- -

Filter for fetching only certain types of channel messages

-

- -
-
channelMessagesFilterEmpty#94d42ee7 = ChannelMessagesFilter;
-channelMessagesFilter#cd77d957 flags:# exclude_new_messages:flags.1?true ranges:Vector<MessageRange> = ChannelMessagesFilter;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
channelMessagesFilterEmptyNo filter
channelMessagesFilterFilter for getting only certain types of channel messages
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ChannelParticipantsFilter.html b/data/corefork.telegram.org/type/ChannelParticipantsFilter.html deleted file mode 100644 index 057166248d..0000000000 --- a/data/corefork.telegram.org/type/ChannelParticipantsFilter.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - ChannelParticipantsFilter - - - - - - - - - - - - - -
- -
-
-
- -

ChannelParticipantsFilter

- -

Filter for fetching channel participants

-

- -
-
channelParticipantsRecent#de3f3c79 = ChannelParticipantsFilter;
-channelParticipantsAdmins#b4608969 = ChannelParticipantsFilter;
-channelParticipantsKicked#a3b54985 q:string = ChannelParticipantsFilter;
-channelParticipantsBots#b0d1865b = ChannelParticipantsFilter;
-channelParticipantsBanned#1427a5e1 q:string = ChannelParticipantsFilter;
-channelParticipantsSearch#656ac4b q:string = ChannelParticipantsFilter;
-channelParticipantsContacts#bb6ae88d q:string = ChannelParticipantsFilter;
-channelParticipantsMentions#e04b5ceb flags:# q:flags.0?string top_msg_id:flags.1?int = ChannelParticipantsFilter;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
channelParticipantsRecentFetch only recent participants
channelParticipantsAdminsFetch only admin participants
channelParticipantsKickedFetch only kicked participants
channelParticipantsBotsFetch only bot participants
channelParticipantsBannedFetch only banned participants
channelParticipantsSearchQuery participants by name
channelParticipantsContactsFetch only participants that are also contacts
channelParticipantsMentionsThis filter is used when looking for members to mention.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/Chat.html b/data/corefork.telegram.org/type/Chat.html deleted file mode 100644 index c926423622..0000000000 --- a/data/corefork.telegram.org/type/Chat.html +++ /dev/null @@ -1,163 +0,0 @@ - - - - - Chat - - - - - - - - - - - - - -
- -
-
-
- -

Chat

- -

Object defines a group.

-

- -
-
chatEmpty#29562865 id:long = Chat;
-chat#41cbf256 flags:# creator:flags.0?true kicked:flags.1?true left:flags.2?true deactivated:flags.5?true call_active:flags.23?true call_not_empty:flags.24?true noforwards:flags.25?true id:long title:string photo:ChatPhoto participants_count:int date:int version:int migrated_to:flags.6?InputChannel admin_rights:flags.14?ChatAdminRights default_banned_rights:flags.18?ChatBannedRights = Chat;
-chatForbidden#6592a1a7 id:long title:string = Chat;
-channel#8261ac61 flags:# creator:flags.0?true left:flags.2?true broadcast:flags.5?true verified:flags.7?true megagroup:flags.8?true restricted:flags.9?true signatures:flags.11?true min:flags.12?true scam:flags.19?true has_link:flags.20?true has_geo:flags.21?true slowmode_enabled:flags.22?true call_active:flags.23?true call_not_empty:flags.24?true fake:flags.25?true gigagroup:flags.26?true noforwards:flags.27?true id:long access_hash:flags.13?long title:string username:flags.6?string photo:ChatPhoto date:int restriction_reason:flags.9?Vector<RestrictionReason> admin_rights:flags.14?ChatAdminRights banned_rights:flags.15?ChatBannedRights default_banned_rights:flags.18?ChatBannedRights participants_count:flags.17?int = Chat;
-channelForbidden#17d493d5 flags:# broadcast:flags.5?true megagroup:flags.8?true id:long access_hash:long title:string until_date:flags.16?int = Chat;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
chatEmptyEmpty constructor, group doesn't exist
chatInfo about a group
chatForbiddenA group to which the user has no access. E.g., because the user was kicked from the group.
channelChannel/supergroup info
channelForbiddenIndicates a channel/supergroup we can't access because we were banned, or for some other reason.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ChatAdminWithInvites.html b/data/corefork.telegram.org/type/ChatAdminWithInvites.html deleted file mode 100644 index 062ff94569..0000000000 --- a/data/corefork.telegram.org/type/ChatAdminWithInvites.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - ChatAdminWithInvites - - - - - - - - - - - - - -
- -
-
-
- -

ChatAdminWithInvites

- -

Info about chat invites generated by admins.

-

- -
-
chatAdminWithInvites#f2ecef23 admin_id:long invites_count:int revoked_invites_count:int = ChatAdminWithInvites;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
chatAdminWithInvitesInfo about chat invites generated by admins.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ChatBannedRights.html b/data/corefork.telegram.org/type/ChatBannedRights.html deleted file mode 100644 index 712e2b9c0f..0000000000 --- a/data/corefork.telegram.org/type/ChatBannedRights.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - ChatBannedRights - - - - - - - - - - - - - -
- -
-
-
- -

ChatBannedRights

- -

Represents the rights of a normal user in a supergroup/channel/chat.

-

- -
-
chatBannedRights#9f120418 flags:# view_messages:flags.0?true send_messages:flags.1?true send_media:flags.2?true send_stickers:flags.3?true send_gifs:flags.4?true send_games:flags.5?true send_inline:flags.6?true embed_links:flags.7?true send_polls:flags.8?true change_info:flags.10?true invite_users:flags.15?true pin_messages:flags.17?true until_date:int = ChatBannedRights;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
chatBannedRightsRepresents the rights of a normal user in a supergroup/channel/chat. In this case, the flags are inverted: if set, a flag does not allow a user to do X.
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ChatFull.html b/data/corefork.telegram.org/type/ChatFull.html deleted file mode 100644 index 1f802af8a0..0000000000 --- a/data/corefork.telegram.org/type/ChatFull.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - ChatFull - - - - - - - - - - - - - -
- -
-
-
- -

ChatFull

- -

Object containing detailed group info

-

- -
-
chatFull#4dbdc099 flags:# can_set_username:flags.7?true has_scheduled:flags.8?true id:long about:string participants:ChatParticipants chat_photo:flags.2?Photo notify_settings:PeerNotifySettings exported_invite:flags.13?ExportedChatInvite bot_info:flags.3?Vector<BotInfo> pinned_msg_id:flags.6?int folder_id:flags.11?int call:flags.12?InputGroupCall ttl_period:flags.14?int groupcall_default_join_as:flags.15?Peer theme_emoticon:flags.16?string = ChatFull;
-channelFull#e9b27a17 flags:# can_view_participants:flags.3?true can_set_username:flags.6?true can_set_stickers:flags.7?true hidden_prehistory:flags.10?true can_set_location:flags.16?true has_scheduled:flags.19?true can_view_stats:flags.20?true blocked:flags.22?true id:long about:string participants_count:flags.0?int admins_count:flags.1?int kicked_count:flags.2?int banned_count:flags.2?int online_count:flags.13?int read_inbox_max_id:int read_outbox_max_id:int unread_count:int chat_photo:Photo notify_settings:PeerNotifySettings exported_invite:flags.23?ExportedChatInvite bot_info:Vector<BotInfo> migrated_from_chat_id:flags.4?long migrated_from_max_id:flags.4?int pinned_msg_id:flags.5?int stickerset:flags.8?StickerSet available_min_id:flags.9?int folder_id:flags.11?int linked_chat_id:flags.14?long location:flags.15?ChannelLocation slowmode_seconds:flags.17?int slowmode_next_send_date:flags.18?int stats_dc:flags.12?int pts:int call:flags.21?InputGroupCall ttl_period:flags.24?int pending_suggestions:flags.25?Vector<string> groupcall_default_join_as:flags.26?Peer theme_emoticon:flags.27?string = ChatFull;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
chatFullDetailed chat info
channelFullFull info about a channel/supergroup
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ChatInvite.html b/data/corefork.telegram.org/type/ChatInvite.html deleted file mode 100644 index 6951b3aa47..0000000000 --- a/data/corefork.telegram.org/type/ChatInvite.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - ChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

ChatInvite

- -

Chat invite

-

- -
-
chatInviteAlready#5a686d7c chat:Chat = ChatInvite;
-chatInvite#dfc2f58e flags:# channel:flags.0?true broadcast:flags.1?true public:flags.2?true megagroup:flags.3?true title:string photo:Photo participants_count:int participants:flags.4?Vector<User> = ChatInvite;
-chatInvitePeek#61695cb0 chat:Chat expires:int = ChatInvite;
-
----functions---
-
-messages.checkChatInvite#3eadb1bb hash:string = ChatInvite;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
chatInviteAlreadyThe user has already joined this chat
chatInviteChat invite info
chatInvitePeekA chat invitation that also allows peeking into the group to read messages without joining it.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.checkChatInviteCheck the validity of a chat invite link and get basic info about it
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ChatInviteImporter.html b/data/corefork.telegram.org/type/ChatInviteImporter.html deleted file mode 100644 index b6d549ef7d..0000000000 --- a/data/corefork.telegram.org/type/ChatInviteImporter.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - ChatInviteImporter - - - - - - - - - - - - - -
- -
-
-
- -

ChatInviteImporter

- -

When and which user joined the chat using a chat invite

-

- -
-
chatInviteImporter#b5cd5f4 user_id:long date:int = ChatInviteImporter;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
chatInviteImporterWhen and which user joined the chat using a chat invite
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ChatOnlines.html b/data/corefork.telegram.org/type/ChatOnlines.html deleted file mode 100644 index 9c03b6cc7a..0000000000 --- a/data/corefork.telegram.org/type/ChatOnlines.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - ChatOnlines - - - - - - - - - - - - - -
- -
-
-
- -

ChatOnlines

- -

Number of online users in a chat

-

- -
-
chatOnlines#f041e250 onlines:int = ChatOnlines;
-
----functions---
-
-messages.getOnlines#6e2be050 peer:InputPeer = ChatOnlines;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
chatOnlinesNumber of online users in a chat
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getOnlinesGet count of online users in a chat
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ChatParticipant.html b/data/corefork.telegram.org/type/ChatParticipant.html deleted file mode 100644 index ea08b14f56..0000000000 --- a/data/corefork.telegram.org/type/ChatParticipant.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - ChatParticipant - - - - - - - - - - - - - -
- -
-
-
- -

ChatParticipant

- -

Details of a group member.

-

- -
-
chatParticipant#c02d4007 user_id:long inviter_id:long date:int = ChatParticipant;
-chatParticipantCreator#e46bcee4 user_id:long = ChatParticipant;
-chatParticipantAdmin#a0933f5b user_id:long inviter_id:long date:int = ChatParticipant;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
chatParticipantGroup member.
chatParticipantCreatorRepresents the creator of the group
chatParticipantAdminChat admin
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ChatParticipants.html b/data/corefork.telegram.org/type/ChatParticipants.html deleted file mode 100644 index 10bfad2dd5..0000000000 --- a/data/corefork.telegram.org/type/ChatParticipants.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - ChatParticipants - - - - - - - - - - - - - -
- -
-
-
- -

ChatParticipants

- -

Object contains info on group members.

-

- -
-
chatParticipantsForbidden#8763d3e1 flags:# chat_id:long self_participant:flags.0?ChatParticipant = ChatParticipants;
-chatParticipants#3cbc93f8 chat_id:long participants:Vector<ChatParticipant> version:int = ChatParticipants;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
chatParticipantsForbiddenInfo on members is unavailable
chatParticipantsGroup members.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ChatPhoto.html b/data/corefork.telegram.org/type/ChatPhoto.html deleted file mode 100644 index 3e9772c633..0000000000 --- a/data/corefork.telegram.org/type/ChatPhoto.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - ChatPhoto - - - - - - - - - - - - - -
- -
-
-
- -

ChatPhoto

- -

Object defines a group profile photo.

-

- -
-
chatPhotoEmpty#37c1011c = ChatPhoto;
-chatPhoto#1c6e1c11 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = ChatPhoto;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
chatPhotoEmptyGroup photo is not set.
chatPhotoGroup profile photo.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ChatTheme.html b/data/corefork.telegram.org/type/ChatTheme.html deleted file mode 100644 index 9a83cb9e1e..0000000000 --- a/data/corefork.telegram.org/type/ChatTheme.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - ChatTheme - - - - - - - - - - - - - -
- -
-
-
- -

ChatTheme

- -

A chat theme

-

- -
-
chatTheme#ed0b5c33 emoticon:string theme:Theme dark_theme:Theme = ChatTheme;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
chatThemeA chat theme
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/CodeSettings.html b/data/corefork.telegram.org/type/CodeSettings.html deleted file mode 100644 index 11f87ca859..0000000000 --- a/data/corefork.telegram.org/type/CodeSettings.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - CodeSettings - - - - - - - - - - - - - -
- -
-
-
- -

CodeSettings

- -

Settings for the code type to send

-

- -
-
codeSettings#debebe83 flags:# allow_flashcall:flags.0?true current_number:flags.1?true allow_app_hash:flags.4?true = CodeSettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
codeSettingsSettings used by telegram servers for sending the confirm code.

Example implementations: telegram for android, tdlib.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/Config.html b/data/corefork.telegram.org/type/Config.html deleted file mode 100644 index 941000963d..0000000000 --- a/data/corefork.telegram.org/type/Config.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Config - - - - - - - - - - - - - -
- -
-
-
- -

Config

- -

Object contains info on API configuring parameters.

-

- -
-
config#330b4067 flags:# phonecalls_enabled:flags.1?true default_p2p_contacts:flags.3?true preload_featured_stickers:flags.4?true ignore_phone_entities:flags.5?true revoke_pm_inbox:flags.6?true blocked_mode:flags.8?true pfs_enabled:flags.13?true date:int expires:int test_mode:Bool this_dc:int dc_options:Vector<DcOption> dc_txt_domain_name:string chat_size_max:int megagroup_size_max:int forwarded_count_max:int online_update_period_ms:int offline_blur_timeout_ms:int offline_idle_timeout_ms:int online_cloud_timeout_ms:int notify_cloud_delay_ms:int notify_default_delay_ms:int push_chat_period_ms:int push_chat_limit:int saved_gifs_limit:int edit_time_limit:int revoke_time_limit:int revoke_pm_time_limit:int rating_e_decay:int stickers_recent_limit:int stickers_faved_limit:int channels_read_media_period:int tmp_sessions:flags.0?int pinned_dialogs_count_max:int pinned_infolder_count_max:int call_receive_timeout_ms:int call_ring_timeout_ms:int call_connect_timeout_ms:int call_packet_timeout_ms:int me_url_prefix:string autoupdate_url_prefix:flags.7?string gif_search_username:flags.9?string venue_search_username:flags.10?string img_search_username:flags.11?string static_maps_provider:flags.12?string caption_length_max:int message_length_max:int webfile_dc_id:int suggested_lang_code:flags.2?string lang_pack_version:flags.2?int base_lang_pack_version:flags.2?int = Config;
-
----functions---
-
-help.getConfig#c4f9186b = Config;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
configCurrent configuration
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getConfigReturns current configuration, icluding data center configuration.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/Contact.html b/data/corefork.telegram.org/type/Contact.html deleted file mode 100644 index bcb81df1db..0000000000 --- a/data/corefork.telegram.org/type/Contact.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - Contact - - - - - - - - - - - - - -
- -
-
-
- -

Contact

- -

A contact of the current user.

-

- -
-
contact#145ade0b user_id:long mutual:Bool = Contact;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
contactA contact of the current user that is registered in the system.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/DataJSON.html b/data/corefork.telegram.org/type/DataJSON.html deleted file mode 100644 index 51ebddaa15..0000000000 --- a/data/corefork.telegram.org/type/DataJSON.html +++ /dev/null @@ -1,168 +0,0 @@ - - - - - DataJSON - - - - - - - - - - - - - -
- -
-
-
- -

DataJSON

- -

Represent a JSON-encoded object

-

- -
-
dataJSON#7d748d04 data:string = DataJSON;
-
----functions---
-
-bots.sendCustomRequest#aa2769ed custom_method:string params:DataJSON = DataJSON;
-
-phone.getCallConfig#55451fa9 = DataJSON;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
dataJSONRepresents a json-encoded object
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
bots.sendCustomRequestSends a custom request; for bots only
phone.getCallConfigGet phone call configuration to be passed to libtgvoip's shared config
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/DcOption.html b/data/corefork.telegram.org/type/DcOption.html deleted file mode 100644 index 98f4f3f9f3..0000000000 --- a/data/corefork.telegram.org/type/DcOption.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - DcOption - - - - - - - - - - - - - -
- -
-
-
- -

DcOption

- -

Information for connection to data centre.

-

- -
-
dcOption#18b7a10d flags:# ipv6:flags.0?true media_only:flags.1?true tcpo_only:flags.2?true cdn:flags.3?true static:flags.4?true id:int ip_address:string port:int secret:flags.10?bytes = DcOption;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
dcOptionData centre
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/DecryptedDataBlock.html b/data/corefork.telegram.org/type/DecryptedDataBlock.html deleted file mode 100644 index 7e7670f0a1..0000000000 --- a/data/corefork.telegram.org/type/DecryptedDataBlock.html +++ /dev/null @@ -1,128 +0,0 @@ - - - - - DecryptedDataBlock - - - - - - - - - - - - - -
- -
-
-
- -

DecryptedDataBlock

- -

VoIP decrypted data block

-

- -
-
Type schema is not available in the selected layer.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/DecryptedMessage.html b/data/corefork.telegram.org/type/DecryptedMessage.html deleted file mode 100644 index 3d50a1bebe..0000000000 --- a/data/corefork.telegram.org/type/DecryptedMessage.html +++ /dev/null @@ -1,140 +0,0 @@ - - - - - DecryptedMessage - - - - - - - - - - - - - -
- -
-
-
- -

DecryptedMessage

- -

Object describes the contents of an encrypted message.

-

- -
-
===8===
-decryptedMessage#1f814f1f random_id:long random_bytes:bytes message:string media:DecryptedMessageMedia = DecryptedMessage;
-decryptedMessageService#aa48327d random_id:long random_bytes:bytes action:DecryptedMessageAction = DecryptedMessage;
-
-===17===
-decryptedMessage#204d3878 random_id:long ttl:int message:string media:DecryptedMessageMedia = DecryptedMessage;
-decryptedMessageService#73164160 random_id:long action:DecryptedMessageAction = DecryptedMessage;
-
-===45===
-decryptedMessage#36b091de flags:# random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long = DecryptedMessage;
-
-===73===
-decryptedMessage#91cc4674 flags:# no_webpage:flags.1?true silent:flags.5?true random_id:long ttl:int message:string media:flags.9?DecryptedMessageMedia entities:flags.7?Vector<MessageEntity> via_bot_name:flags.11?string reply_to_random_id:flags.3?long grouped_id:flags.17?long = DecryptedMessage;

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/DecryptedMessageAction.html b/data/corefork.telegram.org/type/DecryptedMessageAction.html deleted file mode 100644 index 5e07926032..0000000000 --- a/data/corefork.telegram.org/type/DecryptedMessageAction.html +++ /dev/null @@ -1,145 +0,0 @@ - - - - - DecryptedMessageAction - - - - - - - - - - - - - -
- -
-
-
- -

DecryptedMessageAction

- -

Object describes the action to which a service message is linked.

-

- -
-
===8===
-decryptedMessageActionSetMessageTTL#a1733aec ttl_seconds:int = DecryptedMessageAction;
-decryptedMessageActionReadMessages#c4f40be random_ids:Vector<long> = DecryptedMessageAction;
-decryptedMessageActionDeleteMessages#65614304 random_ids:Vector<long> = DecryptedMessageAction;
-decryptedMessageActionScreenshotMessages#8ac1f475 random_ids:Vector<long> = DecryptedMessageAction;
-decryptedMessageActionFlushHistory#6719e45c = DecryptedMessageAction;
-
-===17===
-decryptedMessageActionResend#511110b0 start_seq_no:int end_seq_no:int = DecryptedMessageAction;
-decryptedMessageActionNotifyLayer#f3048883 layer:int = DecryptedMessageAction;
-decryptedMessageActionTyping#ccb27641 action:SendMessageAction = DecryptedMessageAction;
-
-===20===
-decryptedMessageActionRequestKey#f3c9611b exchange_id:long g_a:bytes = DecryptedMessageAction;
-decryptedMessageActionAcceptKey#6fe1735b exchange_id:long g_b:bytes key_fingerprint:long = DecryptedMessageAction;
-decryptedMessageActionAbortKey#dd05ec6b exchange_id:long = DecryptedMessageAction;
-decryptedMessageActionCommitKey#ec2e0b9b exchange_id:long key_fingerprint:long = DecryptedMessageAction;
-decryptedMessageActionNoop#a82fdd63 = DecryptedMessageAction;

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/DecryptedMessageLayer.html b/data/corefork.telegram.org/type/DecryptedMessageLayer.html deleted file mode 100644 index bf1fba789f..0000000000 --- a/data/corefork.telegram.org/type/DecryptedMessageLayer.html +++ /dev/null @@ -1,129 +0,0 @@ - - - - - DecryptedMessageLayer - - - - - - - - - - - - - -
- -
-
-
- -

DecryptedMessageLayer

- -

Object describes encrypted message content in relation to the required layer.

-

- -
-
===17===
-decryptedMessageLayer#1be31789 random_bytes:bytes layer:int in_seq_no:int out_seq_no:int message:DecryptedMessage = DecryptedMessageLayer;

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/DecryptedMessageMedia.html b/data/corefork.telegram.org/type/DecryptedMessageMedia.html deleted file mode 100644 index 940459b943..0000000000 --- a/data/corefork.telegram.org/type/DecryptedMessageMedia.html +++ /dev/null @@ -1,149 +0,0 @@ - - - - - DecryptedMessageMedia - - - - - - - - - - - - - -
- -
-
-
- -

DecryptedMessageMedia

- -

Object describes media contents of an encrypted message.

-

- -
-
===8===
-decryptedMessageMediaEmpty#89f5c4a = DecryptedMessageMedia;
-decryptedMessageMediaPhoto#32798a8c thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageMediaVideo#4cee6ef3 thumb:bytes thumb_w:int thumb_h:int duration:int w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageMediaGeoPoint#35480a59 lat:double long:double = DecryptedMessageMedia;
-decryptedMessageMediaContact#588a0a97 phone_number:string first_name:string last_name:string user_id:int = DecryptedMessageMedia;
-decryptedMessageMediaDocument#b095434b thumb:bytes thumb_w:int thumb_h:int file_name:string mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageMediaAudio#6080758f duration:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-
-===17===
-decryptedMessageMediaVideo#524a415d thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes = DecryptedMessageMedia;
-decryptedMessageMediaAudio#57e0a9cb duration:int mime_type:string size:int key:bytes iv:bytes = DecryptedMessageMedia;
-
-===23===
-decryptedMessageMediaExternalDocument#fa95b0dd id:long access_hash:long date:int mime_type:string size:int thumb:PhotoSize dc_id:int attributes:Vector<DocumentAttribute> = DecryptedMessageMedia;
-
-===45===
-decryptedMessageMediaPhoto#f1fa8d78 thumb:bytes thumb_w:int thumb_h:int w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;
-decryptedMessageMediaVideo#970c8c0e thumb:bytes thumb_w:int thumb_h:int duration:int mime_type:string w:int h:int size:int key:bytes iv:bytes caption:string = DecryptedMessageMedia;
-decryptedMessageMediaDocument#7afe8ae2 thumb:bytes thumb_w:int thumb_h:int mime_type:string size:int key:bytes iv:bytes attributes:Vector<DocumentAttribute> caption:string = DecryptedMessageMedia;
-decryptedMessageMediaVenue#8a0df56f lat:double long:double title:string address:string provider:string venue_id:string = DecryptedMessageMedia;
-decryptedMessageMediaWebPage#e50511d8 url:string = DecryptedMessageMedia;

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/Dialog.html b/data/corefork.telegram.org/type/Dialog.html deleted file mode 100644 index a1f1205604..0000000000 --- a/data/corefork.telegram.org/type/Dialog.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - Dialog - - - - - - - - - - - - - -
- -
-
-
- -

Dialog

- -

Chat info.

-

- -
-
dialog#2c171f72 flags:# pinned:flags.2?true unread_mark:flags.3?true peer:Peer top_message:int read_inbox_max_id:int read_outbox_max_id:int unread_count:int unread_mentions_count:int notify_settings:PeerNotifySettings pts:flags.0?int draft:flags.1?DraftMessage folder_id:flags.4?int = Dialog;
-dialogFolder#71bd134c flags:# pinned:flags.2?true folder:Folder peer:Peer top_message:int unread_muted_peers_count:int unread_unmuted_peers_count:int unread_muted_messages_count:int unread_unmuted_messages_count:int = Dialog;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
dialogChat
dialogFolderDialog in folder
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/DialogFilter.html b/data/corefork.telegram.org/type/DialogFilter.html deleted file mode 100644 index 34c2d65658..0000000000 --- a/data/corefork.telegram.org/type/DialogFilter.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - DialogFilter - - - - - - - - - - - - - -
- -
-
-
- -

DialogFilter

- -

Dialog filter (folders)

-

- -
-
dialogFilter#7438f7e8 flags:# contacts:flags.0?true non_contacts:flags.1?true groups:flags.2?true broadcasts:flags.3?true bots:flags.4?true exclude_muted:flags.11?true exclude_read:flags.12?true exclude_archived:flags.13?true id:int title:string emoticon:flags.25?string pinned_peers:Vector<InputPeer> include_peers:Vector<InputPeer> exclude_peers:Vector<InputPeer> = DialogFilter;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
dialogFilterDialog filter (folder)
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/DialogFilterSuggested.html b/data/corefork.telegram.org/type/DialogFilterSuggested.html deleted file mode 100644 index 288e48c5dc..0000000000 --- a/data/corefork.telegram.org/type/DialogFilterSuggested.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - DialogFilterSuggested - - - - - - - - - - - - - -
- -
-
-
- -

DialogFilterSuggested

- -

Suggested dialog filters (folders)

-

- -
-
dialogFilterSuggested#77744d4a filter:DialogFilter description:string = DialogFilterSuggested;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
dialogFilterSuggestedSuggested folders
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/DialogPeer.html b/data/corefork.telegram.org/type/DialogPeer.html deleted file mode 100644 index f163582501..0000000000 --- a/data/corefork.telegram.org/type/DialogPeer.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - DialogPeer - - - - - - - - - - - - - -
- -
-
-
- -

DialogPeer

- -

Peer, or all peers in a folder

-

- -
-
dialogPeer#e56dbf05 peer:Peer = DialogPeer;
-dialogPeerFolder#514519e2 folder_id:int = DialogPeer;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
dialogPeerPeer
dialogPeerFolderFolder
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/DisabledFeature.html b/data/corefork.telegram.org/type/DisabledFeature.html deleted file mode 100644 index 858a75af5a..0000000000 --- a/data/corefork.telegram.org/type/DisabledFeature.html +++ /dev/null @@ -1,128 +0,0 @@ - - - - - DisabledFeature - - - - - - - - - - - - - -
- -
-
-
- -

DisabledFeature

- -

A disabled feature

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/Document.html b/data/corefork.telegram.org/type/Document.html deleted file mode 100644 index 09432150c9..0000000000 --- a/data/corefork.telegram.org/type/Document.html +++ /dev/null @@ -1,173 +0,0 @@ - - - - - Document - - - - - - - - - - - - - -
- -
-
-
- -

Document

- -

A document.

-

- -
-
documentEmpty#36f8c871 id:long = Document;
-document#1e87342b flags:# id:long access_hash:long file_reference:bytes date:int mime_type:string size:int thumbs:flags.0?Vector<PhotoSize> video_thumbs:flags.1?Vector<VideoSize> dc_id:int attributes:Vector<DocumentAttribute> = Document;
-
----functions---
-
-messages.getDocumentByHash#338e2464 sha256:bytes size:int mime_type:string = Document;
-
-account.uploadTheme#1c3db333 flags:# file:InputFile thumb:flags.0?InputFile file_name:string mime_type:string = Document;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
documentEmptyEmpty constructor, document doesn't exist.
documentDocument
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
messages.getDocumentByHashGet a document by its SHA256 hash, mainly used for gifs
account.uploadThemeUpload theme
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/DocumentAttribute.html b/data/corefork.telegram.org/type/DocumentAttribute.html deleted file mode 100644 index 10c48e6d24..0000000000 --- a/data/corefork.telegram.org/type/DocumentAttribute.html +++ /dev/null @@ -1,173 +0,0 @@ - - - - - DocumentAttribute - - - - - - - - - - - - - -
- -
-
-
- -

DocumentAttribute

- -

Various possible attributes of a document (used to define if it's a sticker, a GIF, a video, a mask sticker, an image, an audio, and so on)

-

- -
-
documentAttributeImageSize#6c37c15c w:int h:int = DocumentAttribute;
-documentAttributeAnimated#11b58939 = DocumentAttribute;
-documentAttributeSticker#6319d612 flags:# mask:flags.1?true alt:string stickerset:InputStickerSet mask_coords:flags.0?MaskCoords = DocumentAttribute;
-documentAttributeVideo#ef02ce6 flags:# round_message:flags.0?true supports_streaming:flags.1?true duration:int w:int h:int = DocumentAttribute;
-documentAttributeAudio#9852f9c6 flags:# voice:flags.10?true duration:int title:flags.0?string performer:flags.1?string waveform:flags.2?bytes = DocumentAttribute;
-documentAttributeFilename#15590068 file_name:string = DocumentAttribute;
-documentAttributeHasStickers#9801d2f7 = DocumentAttribute;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
documentAttributeImageSizeDefines the width and height of an image uploaded as document
documentAttributeAnimatedDefines an animated GIF
documentAttributeStickerDefines a sticker
documentAttributeVideoDefines a video
documentAttributeAudioRepresents an audio file
documentAttributeFilenameA simple document with a file name
documentAttributeHasStickersWhether the current document has stickers attached
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/DraftMessage.html b/data/corefork.telegram.org/type/DraftMessage.html deleted file mode 100644 index a03249d14a..0000000000 --- a/data/corefork.telegram.org/type/DraftMessage.html +++ /dev/null @@ -1,151 +0,0 @@ - - - - - DraftMessage - - - - - - - - - - - - - -
- -
-
-
- -

DraftMessage

- -

Represents a message draft.

-

- -
-
draftMessageEmpty#1b0c841a flags:# date:flags.0?int = DraftMessage;
-draftMessage#fd8e711f flags:# no_webpage:flags.1?true reply_to_msg_id:flags.0?int message:string entities:flags.3?Vector<MessageEntity> date:int = DraftMessage;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
draftMessageEmptyEmpty draft
draftMessageRepresents a message draft.
-

Related pages

-

Message drafts

-

How to handle message drafts

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/EmojiKeyword.html b/data/corefork.telegram.org/type/EmojiKeyword.html deleted file mode 100644 index ea3f4fc596..0000000000 --- a/data/corefork.telegram.org/type/EmojiKeyword.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - EmojiKeyword - - - - - - - - - - - - - -
- -
-
-
- -

EmojiKeyword

- -

Emoji keyword

-

- -
-
emojiKeyword#d5b3b9f9 keyword:string emoticons:Vector<string> = EmojiKeyword;
-emojiKeywordDeleted#236df622 keyword:string emoticons:Vector<string> = EmojiKeyword;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
emojiKeywordEmoji keyword
emojiKeywordDeletedDeleted emoji keyword
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/EmojiKeywordsDifference.html b/data/corefork.telegram.org/type/EmojiKeywordsDifference.html deleted file mode 100644 index 59fd088941..0000000000 --- a/data/corefork.telegram.org/type/EmojiKeywordsDifference.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - EmojiKeywordsDifference - - - - - - - - - - - - - -
- -
-
-
- -

EmojiKeywordsDifference

- -

New emoji keywords

-

- -
-
emojiKeywordsDifference#5cc761bd lang_code:string from_version:int version:int keywords:Vector<EmojiKeyword> = EmojiKeywordsDifference;
-
----functions---
-
-messages.getEmojiKeywords#35a0e062 lang_code:string = EmojiKeywordsDifference;
-messages.getEmojiKeywordsDifference#1508b6af lang_code:string from_version:int = EmojiKeywordsDifference;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
emojiKeywordsDifferenceChanges to emoji keywords
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
messages.getEmojiKeywordsGet localized emoji keywords
messages.getEmojiKeywordsDifferenceGet changed emoji keywords
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/EmojiLanguage.html b/data/corefork.telegram.org/type/EmojiLanguage.html deleted file mode 100644 index aa3735fc91..0000000000 --- a/data/corefork.telegram.org/type/EmojiLanguage.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - EmojiLanguage - - - - - - - - - - - - - -
- -
-
-
- -

EmojiLanguage

- -

Emoji language

-

- -
-
emojiLanguage#b3fb5361 lang_code:string = EmojiLanguage;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
emojiLanguageEmoji language
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/EmojiURL.html b/data/corefork.telegram.org/type/EmojiURL.html deleted file mode 100644 index 79df4831a7..0000000000 --- a/data/corefork.telegram.org/type/EmojiURL.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - EmojiURL - - - - - - - - - - - - - -
- -
-
-
- -

EmojiURL

- -

Emoji URL

-

- -
-
emojiURL#a575739d url:string = EmojiURL;
-
----functions---
-
-messages.getEmojiURL#d5b10c26 lang_code:string = EmojiURL;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
emojiURLAn HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getEmojiURLReturns an HTTP URL which can be used to automatically log in into translation platform and suggest new emoji replacements. The URL will be valid for 30 seconds after generation
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/EncryptedChat.html b/data/corefork.telegram.org/type/EncryptedChat.html deleted file mode 100644 index ddb3a6019a..0000000000 --- a/data/corefork.telegram.org/type/EncryptedChat.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - EncryptedChat - - - - - - - - - - - - - -
- -
-
-
- -

EncryptedChat

- -

Object contains info on an encrypted chat.

-

- -
-
encryptedChatEmpty#ab7ec0a0 id:int = EncryptedChat;
-encryptedChatWaiting#66b25953 id:int access_hash:long date:int admin_id:long participant_id:long = EncryptedChat;
-encryptedChatRequested#48f1d94c flags:# folder_id:flags.0?int id:int access_hash:long date:int admin_id:long participant_id:long g_a:bytes = EncryptedChat;
-encryptedChat#61f0d4c7 id:int access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long = EncryptedChat;
-encryptedChatDiscarded#1e1c7c45 flags:# history_deleted:flags.0?true id:int = EncryptedChat;
-
----functions---
-
-messages.requestEncryption#f64daf43 user_id:InputUser random_id:int g_a:bytes = EncryptedChat;
-messages.acceptEncryption#3dbc0415 peer:InputEncryptedChat g_b:bytes key_fingerprint:long = EncryptedChat;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
encryptedChatEmptyEmpty constructor.
encryptedChatWaitingChat waiting for approval of second participant.
encryptedChatRequestedRequest to create an encrypted chat.
encryptedChatEncrypted chat
encryptedChatDiscardedDiscarded or deleted chat.
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
messages.requestEncryptionSends a request to start a secret chat to the user.
messages.acceptEncryptionConfirms creation of a secret chat
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/EncryptedFile.html b/data/corefork.telegram.org/type/EncryptedFile.html deleted file mode 100644 index d4b5df4f0d..0000000000 --- a/data/corefork.telegram.org/type/EncryptedFile.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - EncryptedFile - - - - - - - - - - - - - -
- -
-
-
- -

EncryptedFile

- -

Seta an encrypted file.

-

- -
-
encryptedFileEmpty#c21f497e = EncryptedFile;
-encryptedFile#4a70994c id:long access_hash:long size:int dc_id:int key_fingerprint:int = EncryptedFile;
-
----functions---
-
-messages.uploadEncryptedFile#5057c497 peer:InputEncryptedChat file:InputEncryptedFile = EncryptedFile;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
encryptedFileEmptyEmpty constructor, unexisitng file.
encryptedFileEncrypted file.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.uploadEncryptedFileUpload encrypted file and associate it to a secret chat
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/EncryptedMessage.html b/data/corefork.telegram.org/type/EncryptedMessage.html deleted file mode 100644 index 03a74965d2..0000000000 --- a/data/corefork.telegram.org/type/EncryptedMessage.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - EncryptedMessage - - - - - - - - - - - - - -
- -
-
-
- -

EncryptedMessage

- -

Object contains encrypted message.

-

- -
-
encryptedMessage#ed18c118 random_id:long chat_id:int date:int bytes:bytes file:EncryptedFile = EncryptedMessage;
-encryptedMessageService#23734b06 random_id:long chat_id:int date:int bytes:bytes = EncryptedMessage;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
encryptedMessageEncrypted message.
encryptedMessageServiceEncrypted service message
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/Error.html b/data/corefork.telegram.org/type/Error.html deleted file mode 100644 index cb84f989f3..0000000000 --- a/data/corefork.telegram.org/type/Error.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - Error - - - - - - - - - - - - - -
- -
-
-
- -

Error

- -

An object containing a query error.

-

- -
-
error#c4b9f9bb code:int text:string = Error;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
errorError.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ExportedChatInvite.html b/data/corefork.telegram.org/type/ExportedChatInvite.html deleted file mode 100644 index 9d0e8ac4d3..0000000000 --- a/data/corefork.telegram.org/type/ExportedChatInvite.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - ExportedChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

ExportedChatInvite

- -

Exported chat invite

-

- -
-
chatInviteExported#b18105e8 flags:# revoked:flags.0?true permanent:flags.5?true link:string admin_id:long date:int start_date:flags.4?int expire_date:flags.1?int usage_limit:flags.2?int usage:flags.3?int = ExportedChatInvite;
-
----functions---
-
-messages.exportChatInvite#14b9bcd7 flags:# legacy_revoke_permanent:flags.2?true peer:InputPeer expire_date:flags.0?int usage_limit:flags.1?int = ExportedChatInvite;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
chatInviteExportedExported chat invite
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.exportChatInviteExport an invite link for a chat
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ExportedMessageLink.html b/data/corefork.telegram.org/type/ExportedMessageLink.html deleted file mode 100644 index 272196b5f7..0000000000 --- a/data/corefork.telegram.org/type/ExportedMessageLink.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - ExportedMessageLink - - - - - - - - - - - - - -
- -
-
-
- -

ExportedMessageLink

- -

HTTP link and embed info of channel message

-

- -
-
exportedMessageLink#5dab1af4 link:string html:string = ExportedMessageLink;
-
----functions---
-
-channels.exportMessageLink#e63fadeb flags:# grouped:flags.0?true thread:flags.1?true channel:InputChannel id:int = ExportedMessageLink;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
exportedMessageLinkLink to a message in a supergroup/channel
-

Methods

- - - - - - - - - - - - - -
MethodDescription
channels.exportMessageLinkGet link and embed info of a message in a channel/supergroup
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/FileLocation.html b/data/corefork.telegram.org/type/FileLocation.html deleted file mode 100644 index bfb7dcfc83..0000000000 --- a/data/corefork.telegram.org/type/FileLocation.html +++ /dev/null @@ -1,128 +0,0 @@ - - - - - FileLocation - - - - - - - - - - - - - -
- -
-
-
- -

FileLocation

- -

Indicates the location of a photo, will be deprecated soon

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/Folder.html b/data/corefork.telegram.org/type/Folder.html deleted file mode 100644 index 300e93a47d..0000000000 --- a/data/corefork.telegram.org/type/Folder.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - Folder - - - - - - - - - - - - - -
- -
-
-
- -

Folder

- -

A folder

-

- -
-
folder#ff544e65 flags:# autofill_new_broadcasts:flags.0?true autofill_public_groups:flags.1?true autofill_new_correspondents:flags.2?true id:int title:string photo:flags.3?ChatPhoto = Folder;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
folderFolder
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/FolderPeer.html b/data/corefork.telegram.org/type/FolderPeer.html deleted file mode 100644 index d56865f02e..0000000000 --- a/data/corefork.telegram.org/type/FolderPeer.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - FolderPeer - - - - - - - - - - - - - -
- -
-
-
- -

FolderPeer

- -

Peer associated to folder

-

- -
-
folderPeer#e9baa668 peer:Peer folder_id:int = FolderPeer;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
folderPeerPeer in a folder
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/Game.html b/data/corefork.telegram.org/type/Game.html deleted file mode 100644 index e9af2ecc96..0000000000 --- a/data/corefork.telegram.org/type/Game.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - Game - - - - - - - - - - - - - -
- -
-
-
- -

Game

- -

Indicates an already sent game

-

- -
-
game#bdf9653b flags:# id:long access_hash:long short_name:string title:string description:string photo:Photo document:flags.0?Document = Game;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
gameIndicates an already sent game
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/GeoPoint.html b/data/corefork.telegram.org/type/GeoPoint.html deleted file mode 100644 index f9faad1b7c..0000000000 --- a/data/corefork.telegram.org/type/GeoPoint.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - GeoPoint - - - - - - - - - - - - - -
- -
-
-
- -

GeoPoint

- -

Object defines a GeoPoint.

-

- -
-
geoPointEmpty#1117dd5f = GeoPoint;
-geoPoint#b2a2f663 flags:# long:double lat:double access_hash:long accuracy_radius:flags.0?int = GeoPoint;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
geoPointEmptyEmpty constructor.
geoPointGeoPoint.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/GlobalPrivacySettings.html b/data/corefork.telegram.org/type/GlobalPrivacySettings.html deleted file mode 100644 index 86dc69d324..0000000000 --- a/data/corefork.telegram.org/type/GlobalPrivacySettings.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - GlobalPrivacySettings - - - - - - - - - - - - - -
- -
-
-
- -

GlobalPrivacySettings

- -

Global privacy settings

-

- -
-
globalPrivacySettings#bea2f424 flags:# archive_and_mute_new_noncontact_peers:flags.0?Bool = GlobalPrivacySettings;
-
----functions---
-
-account.getGlobalPrivacySettings#eb2b4cf6 = GlobalPrivacySettings;
-account.setGlobalPrivacySettings#1edaaac2 settings:GlobalPrivacySettings = GlobalPrivacySettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
globalPrivacySettingsGlobal privacy settings
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
account.getGlobalPrivacySettingsSet global privacy settings
account.setGlobalPrivacySettingsSet global privacy settings
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/GroupCall.html b/data/corefork.telegram.org/type/GroupCall.html deleted file mode 100644 index 3e32dc360f..0000000000 --- a/data/corefork.telegram.org/type/GroupCall.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - GroupCall - - - - - - - - - - - - - -
- -
-
-
- -

GroupCall

- -

A group call

-

- -
-
groupCallDiscarded#7780bcb4 id:long access_hash:long duration:int = GroupCall;
-groupCall#d597650c flags:# join_muted:flags.1?true can_change_join_muted:flags.2?true join_date_asc:flags.6?true schedule_start_subscribed:flags.8?true can_start_video:flags.9?true record_video_active:flags.11?true id:long access_hash:long participants_count:int title:flags.3?string stream_dc_id:flags.4?int record_start_date:flags.5?int schedule_date:flags.7?int unmuted_video_count:flags.10?int unmuted_video_limit:int version:int = GroupCall;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
groupCallDiscardedAn ended group call
groupCallInfo about a group call or livestream
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/GroupCallParticipant.html b/data/corefork.telegram.org/type/GroupCallParticipant.html deleted file mode 100644 index c11fcc2220..0000000000 --- a/data/corefork.telegram.org/type/GroupCallParticipant.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - GroupCallParticipant - - - - - - - - - - - - - -
- -
-
-
- -

GroupCallParticipant

- -

Info about a group call participant

-

- -
-
groupCallParticipant#eba636fe flags:# muted:flags.0?true left:flags.1?true can_self_unmute:flags.2?true just_joined:flags.4?true versioned:flags.5?true min:flags.8?true muted_by_you:flags.9?true volume_by_admin:flags.10?true self:flags.12?true video_joined:flags.15?true peer:Peer date:int active_date:flags.3?int source:int volume:flags.7?int about:flags.11?string raise_hand_rating:flags.13?long video:flags.6?GroupCallParticipantVideo presentation:flags.14?GroupCallParticipantVideo = GroupCallParticipant;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
groupCallParticipantInfo about a group call participant
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/GroupCallParticipantVideo.html b/data/corefork.telegram.org/type/GroupCallParticipantVideo.html deleted file mode 100644 index 59373a6d01..0000000000 --- a/data/corefork.telegram.org/type/GroupCallParticipantVideo.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - GroupCallParticipantVideo - - - - - - - - - - - - - -
- -
-
-
- -

GroupCallParticipantVideo

- -

Info about a video stream

-

- -
-
groupCallParticipantVideo#67753ac8 flags:# paused:flags.0?true endpoint:string source_groups:Vector<GroupCallParticipantVideoSourceGroup> audio_source:flags.1?int = GroupCallParticipantVideo;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
groupCallParticipantVideoInfo about a video stream
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/GroupCallParticipantVideoSourceGroup.html b/data/corefork.telegram.org/type/GroupCallParticipantVideoSourceGroup.html deleted file mode 100644 index 236023d156..0000000000 --- a/data/corefork.telegram.org/type/GroupCallParticipantVideoSourceGroup.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - GroupCallParticipantVideoSourceGroup - - - - - - - - - - - - - -
- -
-
-
- -

GroupCallParticipantVideoSourceGroup

- -

Describes a group of video synchronization source identifiers

-

- -
-
groupCallParticipantVideoSourceGroup#dcb118b7 semantics:string sources:Vector<int> = GroupCallParticipantVideoSourceGroup;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
groupCallParticipantVideoSourceGroupDescribes a group of video synchronization source identifiers
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/HighScore.html b/data/corefork.telegram.org/type/HighScore.html deleted file mode 100644 index 014c1205b0..0000000000 --- a/data/corefork.telegram.org/type/HighScore.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - HighScore - - - - - - - - - - - - - -
- -
-
-
- -

HighScore

- -

Game high score

-

- -
-
highScore#73a379eb pos:int user_id:long score:int = HighScore;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
highScoreGame highscore
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ImportedContact.html b/data/corefork.telegram.org/type/ImportedContact.html deleted file mode 100644 index a5bf089395..0000000000 --- a/data/corefork.telegram.org/type/ImportedContact.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - ImportedContact - - - - - - - - - - - - - -
- -
-
-
- -

ImportedContact

- -

Object contains info on a successfully imported contact.

-

- -
-
importedContact#c13e3c50 user_id:long client_id:long = ImportedContact;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
importedContactSuccessfully imported contact.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InlineBotSwitchPM.html b/data/corefork.telegram.org/type/InlineBotSwitchPM.html deleted file mode 100644 index 24bc090b78..0000000000 --- a/data/corefork.telegram.org/type/InlineBotSwitchPM.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - InlineBotSwitchPM - - - - - - - - - - - - - -
- -
-
-
- -

InlineBotSwitchPM

- -

The bot requested the user to message him in private

-

- -
-
inlineBotSwitchPM#3c20629f text:string start_param:string = InlineBotSwitchPM;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inlineBotSwitchPMThe bot requested the user to message him in private
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InlineQueryPeerType.html b/data/corefork.telegram.org/type/InlineQueryPeerType.html deleted file mode 100644 index dbe096fb97..0000000000 --- a/data/corefork.telegram.org/type/InlineQueryPeerType.html +++ /dev/null @@ -1,163 +0,0 @@ - - - - - InlineQueryPeerType - - - - - - - - - - - - - -
- -
-
-
- -

InlineQueryPeerType

- -

Type of the chat from which the inline query was sent.

-

- -
-
inlineQueryPeerTypeSameBotPM#3081ed9d = InlineQueryPeerType;
-inlineQueryPeerTypePM#833c0fac = InlineQueryPeerType;
-inlineQueryPeerTypeChat#d766c50a = InlineQueryPeerType;
-inlineQueryPeerTypeMegagroup#5ec4be43 = InlineQueryPeerType;
-inlineQueryPeerTypeBroadcast#6334ee9a = InlineQueryPeerType;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inlineQueryPeerTypeSameBotPMThe inline query was sent in a private chat with the bot itself
inlineQueryPeerTypePMThe inline query was sent in a private chat
inlineQueryPeerTypeChatThe inline query was sent in a chat
inlineQueryPeerTypeMegagroupThe inline query was sent in a supergroup
inlineQueryPeerTypeBroadcastThe inline query was sent in a channel
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputAppEvent.html b/data/corefork.telegram.org/type/InputAppEvent.html deleted file mode 100644 index 72af0e2f82..0000000000 --- a/data/corefork.telegram.org/type/InputAppEvent.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - InputAppEvent - - - - - - - - - - - - - -
- -
-
-
- -

InputAppEvent

- -

Object contains info about an event that occured in the application.

-

- -
-
inputAppEvent#1d1b1245 time:double type:string peer:long data:JSONValue = InputAppEvent;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inputAppEventEvent that occured in the application.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputBotInlineMessage.html b/data/corefork.telegram.org/type/InputBotInlineMessage.html deleted file mode 100644 index 1bfacdd643..0000000000 --- a/data/corefork.telegram.org/type/InputBotInlineMessage.html +++ /dev/null @@ -1,173 +0,0 @@ - - - - - InputBotInlineMessage - - - - - - - - - - - - - -
- -
-
-
- -

InputBotInlineMessage

- -

Represents a sent inline message from the perspective of a bot

-

- -
-
inputBotInlineMessageMediaAuto#3380c786 flags:# message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageText#3dcd7a87 flags:# no_webpage:flags.0?true message:string entities:flags.1?Vector<MessageEntity> reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageMediaGeo#96929a85 flags:# geo_point:InputGeoPoint heading:flags.0?int period:flags.1?int proximity_notification_radius:flags.3?int reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageMediaVenue#417bbf11 flags:# geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageMediaContact#a6edbffd flags:# phone_number:string first_name:string last_name:string vcard:string reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageGame#4b425864 flags:# reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;
-inputBotInlineMessageMediaInvoice#d7e78225 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON reply_markup:flags.2?ReplyMarkup = InputBotInlineMessage;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputBotInlineMessageMediaAutoA media
inputBotInlineMessageTextSimple text message
inputBotInlineMessageMediaGeoGeolocation
inputBotInlineMessageMediaVenueVenue
inputBotInlineMessageMediaContactA contact
inputBotInlineMessageGameA game
inputBotInlineMessageMediaInvoiceAn invoice
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputBotInlineMessageID.html b/data/corefork.telegram.org/type/InputBotInlineMessageID.html deleted file mode 100644 index 2bfea62773..0000000000 --- a/data/corefork.telegram.org/type/InputBotInlineMessageID.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - InputBotInlineMessageID - - - - - - - - - - - - - -
- -
-
-
- -

InputBotInlineMessageID

- -

Represents a sent inline message from the perspective of a bot

-

- -
-
inputBotInlineMessageID#890c3d89 dc_id:int id:long access_hash:long = InputBotInlineMessageID;
-inputBotInlineMessageID64#b6d915d7 dc_id:int owner_id:long id:int access_hash:long = InputBotInlineMessageID;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
inputBotInlineMessageIDRepresents a sent inline message from the perspective of a bot
inputBotInlineMessageID64Represents a sent inline message from the perspective of a bot
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputBotInlineResult.html b/data/corefork.telegram.org/type/InputBotInlineResult.html deleted file mode 100644 index 0abf058c2b..0000000000 --- a/data/corefork.telegram.org/type/InputBotInlineResult.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - - InputBotInlineResult - - - - - - - - - - - - - -
- -
-
-
- -

InputBotInlineResult

- -

Inline bot result

-

- -
-
inputBotInlineResult#88bf9319 flags:# id:string type:string title:flags.1?string description:flags.2?string url:flags.3?string thumb:flags.4?InputWebDocument content:flags.5?InputWebDocument send_message:InputBotInlineMessage = InputBotInlineResult;
-inputBotInlineResultPhoto#a8d864a7 id:string type:string photo:InputPhoto send_message:InputBotInlineMessage = InputBotInlineResult;
-inputBotInlineResultDocument#fff8fdc4 flags:# id:string type:string title:flags.1?string description:flags.2?string document:InputDocument send_message:InputBotInlineMessage = InputBotInlineResult;
-inputBotInlineResultGame#4fa417f2 id:string short_name:string send_message:InputBotInlineMessage = InputBotInlineResult;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputBotInlineResultAn inline bot result
inputBotInlineResultPhotoPhoto
inputBotInlineResultDocumentDocument (media of any type except for photos)
inputBotInlineResultGameGame
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputChannel.html b/data/corefork.telegram.org/type/InputChannel.html deleted file mode 100644 index 68ed6460a5..0000000000 --- a/data/corefork.telegram.org/type/InputChannel.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - InputChannel - - - - - - - - - - - - - -
- -
-
-
- -

InputChannel

- -

Represents a channel

-

- -
-
inputChannelEmpty#ee8c1e86 = InputChannel;
-inputChannel#f35aec28 channel_id:long access_hash:long = InputChannel;
-inputChannelFromMessage#5b934f9d peer:InputPeer msg_id:int channel_id:long = InputChannel;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputChannelEmptyRepresents the absence of a channel
inputChannelRepresents a channel
inputChannelFromMessageDefines a min channel that was seen in a certain message of a certain chat.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputChatPhoto.html b/data/corefork.telegram.org/type/InputChatPhoto.html deleted file mode 100644 index 02b489957b..0000000000 --- a/data/corefork.telegram.org/type/InputChatPhoto.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - InputChatPhoto - - - - - - - - - - - - - -
- -
-
-
- -

InputChatPhoto

- -

Defines a new group profile photo.

-

- -
-
inputChatPhotoEmpty#1ca48f57 = InputChatPhoto;
-inputChatUploadedPhoto#c642724e flags:# file:flags.0?InputFile video:flags.1?InputFile video_start_ts:flags.2?double = InputChatPhoto;
-inputChatPhoto#8953ad37 id:InputPhoto = InputChatPhoto;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputChatPhotoEmptyEmpty constructor, remove group photo.
inputChatUploadedPhotoNew photo to be set as group profile photo.
inputChatPhotoExisting photo to be set as a chat profile photo.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputCheckPasswordSRP.html b/data/corefork.telegram.org/type/InputCheckPasswordSRP.html deleted file mode 100644 index 28b8dde02b..0000000000 --- a/data/corefork.telegram.org/type/InputCheckPasswordSRP.html +++ /dev/null @@ -1,151 +0,0 @@ - - - - - InputCheckPasswordSRP - - - - - - - - - - - - - -
- -
-
-
- -

InputCheckPasswordSRP

- -

Constructors for checking the validity of a 2FA SRP password

-

- -
-
inputCheckPasswordEmpty#9880f658 = InputCheckPasswordSRP;
-inputCheckPasswordSRP#d27ff082 srp_id:long A:bytes M1:bytes = InputCheckPasswordSRP;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
inputCheckPasswordEmptyThere is no password
inputCheckPasswordSRPConstructor for checking the validity of a 2FA SRP password (see SRP)
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputClientProxy.html b/data/corefork.telegram.org/type/InputClientProxy.html deleted file mode 100644 index b07397b52f..0000000000 --- a/data/corefork.telegram.org/type/InputClientProxy.html +++ /dev/null @@ -1,145 +0,0 @@ - - - - - InputClientProxy - - - - - - - - - - - - - -
- -
-
-
- -

InputClientProxy

- -

Info about an MTProxy used to connect.

-

- -
-
inputClientProxy#75588b3f address:string port:int = InputClientProxy;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inputClientProxyInfo about an MTProxy used to connect.
-

Related pages

-

MTProto transports

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputContact.html b/data/corefork.telegram.org/type/InputContact.html deleted file mode 100644 index c3d35ff1ec..0000000000 --- a/data/corefork.telegram.org/type/InputContact.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - InputContact - - - - - - - - - - - - - -
- -
-
-
- -

InputContact

- -

Object defines a contact from the user's phonebook.

-

- -
-
inputPhoneContact#f392b7f4 client_id:long phone:string first_name:string last_name:string = InputContact;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inputPhoneContactPhone contact. The client_id is just an arbitrary contact ID: it should be set, for example, to an incremental number when using contacts.importContacts, in order to retry importing only the contacts that weren't imported successfully.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputDialogPeer.html b/data/corefork.telegram.org/type/InputDialogPeer.html deleted file mode 100644 index 4b3414c813..0000000000 --- a/data/corefork.telegram.org/type/InputDialogPeer.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - InputDialogPeer - - - - - - - - - - - - - -
- -
-
-
- -

InputDialogPeer

- -

Peer, or all peers in a certain folder

-

- -
-
inputDialogPeer#fcaafeb7 peer:InputPeer = InputDialogPeer;
-inputDialogPeerFolder#64600527 folder_id:int = InputDialogPeer;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
inputDialogPeerA peer
inputDialogPeerFolderAll peers in a folder
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputDocument.html b/data/corefork.telegram.org/type/InputDocument.html deleted file mode 100644 index 87c57e6fb6..0000000000 --- a/data/corefork.telegram.org/type/InputDocument.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - InputDocument - - - - - - - - - - - - - -
- -
-
-
- -

InputDocument

- -

Defines a document for subsequent interaction.

-

- -
-
inputDocumentEmpty#72f0eaae = InputDocument;
-inputDocument#1abfb575 id:long access_hash:long file_reference:bytes = InputDocument;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
inputDocumentEmptyEmpty constructor.
inputDocumentDefines a video for subsequent interaction.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputEncryptedChat.html b/data/corefork.telegram.org/type/InputEncryptedChat.html deleted file mode 100644 index 7747bae015..0000000000 --- a/data/corefork.telegram.org/type/InputEncryptedChat.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - InputEncryptedChat - - - - - - - - - - - - - -
- -
-
-
- -

InputEncryptedChat

- -

Object sets an encrypted chat ID.

-

- -
-
inputEncryptedChat#f141b5e1 chat_id:int access_hash:long = InputEncryptedChat;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inputEncryptedChatCreates an encrypted chat.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputEncryptedFile.html b/data/corefork.telegram.org/type/InputEncryptedFile.html deleted file mode 100644 index 137e4fb619..0000000000 --- a/data/corefork.telegram.org/type/InputEncryptedFile.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - - InputEncryptedFile - - - - - - - - - - - - - -
- -
-
-
- -

InputEncryptedFile

- -

Object sets encrypted file for attachment

-

- -
-
inputEncryptedFileEmpty#1837c364 = InputEncryptedFile;
-inputEncryptedFileUploaded#64bd0306 id:long parts:int md5_checksum:string key_fingerprint:int = InputEncryptedFile;
-inputEncryptedFile#5a17b5e5 id:long access_hash:long = InputEncryptedFile;
-inputEncryptedFileBigUploaded#2dc173c8 id:long parts:int key_fingerprint:int = InputEncryptedFile;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputEncryptedFileEmptyEmpty constructor.
inputEncryptedFileUploadedSets new encrypted file saved by parts using upload.saveFilePart method.
inputEncryptedFileSets forwarded encrypted file for attachment.
inputEncryptedFileBigUploadedAssigns a new big encrypted file (over 10Mb in size), saved in parts using the method upload.saveBigFilePart.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputFile.html b/data/corefork.telegram.org/type/InputFile.html deleted file mode 100644 index a369f8717a..0000000000 --- a/data/corefork.telegram.org/type/InputFile.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - InputFile - - - - - - - - - - - - - -
- -
-
-
- -

InputFile

- -

Defines a file uploaded by the client.

-

- -
-
inputFile#f52ff27f id:long parts:int name:string md5_checksum:string = InputFile;
-inputFileBig#fa4f0bb5 id:long parts:int name:string = InputFile;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
inputFileDefines a file saved in parts using the method upload.saveFilePart.
inputFileBigAssigns a big file (over 10Mb in size), saved in part using the method upload.saveBigFilePart.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputFileLocation.html b/data/corefork.telegram.org/type/InputFileLocation.html deleted file mode 100644 index ef0e64b156..0000000000 --- a/data/corefork.telegram.org/type/InputFileLocation.html +++ /dev/null @@ -1,188 +0,0 @@ - - - - - InputFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

InputFileLocation

- -

Defines the location of a file for download.

-

- -
-
inputFileLocation#dfdaabe1 volume_id:long local_id:int secret:long file_reference:bytes = InputFileLocation;
-inputEncryptedFileLocation#f5235d55 id:long access_hash:long = InputFileLocation;
-inputDocumentFileLocation#bad07584 id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;
-inputSecureFileLocation#cbc7ee28 id:long access_hash:long = InputFileLocation;
-inputTakeoutFileLocation#29be5899 = InputFileLocation;
-inputPhotoFileLocation#40181ffe id:long access_hash:long file_reference:bytes thumb_size:string = InputFileLocation;
-inputPhotoLegacyFileLocation#d83466f3 id:long access_hash:long file_reference:bytes volume_id:long local_id:int secret:long = InputFileLocation;
-inputPeerPhotoFileLocation#37257e99 flags:# big:flags.0?true peer:InputPeer photo_id:long = InputFileLocation;
-inputStickerSetThumb#9d84f3db stickerset:InputStickerSet thumb_version:int = InputFileLocation;
-inputGroupCallStream#598a92a flags:# call:InputGroupCall time_ms:long scale:int video_channel:flags.0?int video_quality:flags.0?int = InputFileLocation;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputFileLocationDEPRECATED location of a photo
inputEncryptedFileLocationLocation of encrypted secret chat file.
inputDocumentFileLocationDocument location (video, voice, audio, basically every type except photo)
inputSecureFileLocationLocation of encrypted telegram passport file.
inputTakeoutFileLocationEmpty constructor for takeout
inputPhotoFileLocationUse this object to download a photo with upload.getFile method
inputPhotoLegacyFileLocationLegacy file location
inputPeerPhotoFileLocationLocation of profile photo of channel/group/supergroup/user
inputStickerSetThumbLocation of stickerset thumbnail (see files)
inputGroupCallStreamChunk of a livestream
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputFolderPeer.html b/data/corefork.telegram.org/type/InputFolderPeer.html deleted file mode 100644 index d4299bf5ec..0000000000 --- a/data/corefork.telegram.org/type/InputFolderPeer.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - InputFolderPeer - - - - - - - - - - - - - -
- -
-
-
- -

InputFolderPeer

- -

Peer in a folder

-

- -
-
inputFolderPeer#fbd2c296 peer:InputPeer folder_id:int = InputFolderPeer;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inputFolderPeerPeer in a folder
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputGame.html b/data/corefork.telegram.org/type/InputGame.html deleted file mode 100644 index f6c77c6835..0000000000 --- a/data/corefork.telegram.org/type/InputGame.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - InputGame - - - - - - - - - - - - - -
- -
-
-
- -

InputGame

- -

A game to send

-

- -
-
inputGameID#32c3e77 id:long access_hash:long = InputGame;
-inputGameShortName#c331e80a bot_id:InputUser short_name:string = InputGame;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
inputGameIDIndicates an already sent game
inputGameShortNameGame by short name
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputGroupCall.html b/data/corefork.telegram.org/type/InputGroupCall.html deleted file mode 100644 index c26f046f84..0000000000 --- a/data/corefork.telegram.org/type/InputGroupCall.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - InputGroupCall - - - - - - - - - - - - - -
- -
-
-
- -

InputGroupCall

- -

Indicates a group call

-

- -
-
inputGroupCall#d8aa840f id:long access_hash:long = InputGroupCall;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inputGroupCallPoints to a specific group call
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputMedia.html b/data/corefork.telegram.org/type/InputMedia.html deleted file mode 100644 index d60b085917..0000000000 --- a/data/corefork.telegram.org/type/InputMedia.html +++ /dev/null @@ -1,213 +0,0 @@ - - - - - InputMedia - - - - - - - - - - - - - -
- -
-
-
- -

InputMedia

- -

Defines media content of a message.

-

- -
-
inputMediaEmpty#9664f57f = InputMedia;
-inputMediaUploadedPhoto#1e287d04 flags:# file:InputFile stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
-inputMediaPhoto#b3ba0635 flags:# id:InputPhoto ttl_seconds:flags.0?int = InputMedia;
-inputMediaGeoPoint#f9c44144 geo_point:InputGeoPoint = InputMedia;
-inputMediaContact#f8ab7dfb phone_number:string first_name:string last_name:string vcard:string = InputMedia;
-inputMediaUploadedDocument#5b38c6c1 flags:# nosound_video:flags.3?true force_file:flags.4?true file:InputFile thumb:flags.2?InputFile mime_type:string attributes:Vector<DocumentAttribute> stickers:flags.0?Vector<InputDocument> ttl_seconds:flags.1?int = InputMedia;
-inputMediaDocument#33473058 flags:# id:InputDocument ttl_seconds:flags.0?int query:flags.1?string = InputMedia;
-inputMediaVenue#c13d1c11 geo_point:InputGeoPoint title:string address:string provider:string venue_id:string venue_type:string = InputMedia;
-inputMediaPhotoExternal#e5bbfe1a flags:# url:string ttl_seconds:flags.0?int = InputMedia;
-inputMediaDocumentExternal#fb52dc99 flags:# url:string ttl_seconds:flags.0?int = InputMedia;
-inputMediaGame#d33f43f3 id:InputGame = InputMedia;
-inputMediaInvoice#d9799874 flags:# title:string description:string photo:flags.0?InputWebDocument invoice:Invoice payload:bytes provider:string provider_data:DataJSON start_param:flags.1?string = InputMedia;
-inputMediaGeoLive#971fa843 flags:# stopped:flags.0?true geo_point:InputGeoPoint heading:flags.2?int period:flags.1?int proximity_notification_radius:flags.3?int = InputMedia;
-inputMediaPoll#f94e5f1 flags:# poll:Poll correct_answers:flags.0?Vector<bytes> solution:flags.1?string solution_entities:flags.1?Vector<MessageEntity> = InputMedia;
-inputMediaDice#e66fbf7b emoticon:string = InputMedia;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputMediaEmptyEmpty media content of a message.
inputMediaUploadedPhotoPhoto
inputMediaPhotoForwarded photo
inputMediaGeoPointMap.
inputMediaContactPhonebook contact
inputMediaUploadedDocumentNew document
inputMediaDocumentForwarded document
inputMediaVenueCan be used to send a venue geolocation.
inputMediaPhotoExternalNew photo that will be uploaded by the server using the specified URL
inputMediaDocumentExternalDocument that will be downloaded by the telegram servers
inputMediaGameA game
inputMediaInvoiceGenerated invoice of a bot payment
inputMediaGeoLiveLive geographical location
inputMediaPollA poll
inputMediaDiceSend a dice in the chat
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputMessage.html b/data/corefork.telegram.org/type/InputMessage.html deleted file mode 100644 index e437614a13..0000000000 --- a/data/corefork.telegram.org/type/InputMessage.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - - InputMessage - - - - - - - - - - - - - -
- -
-
-
- -

InputMessage

- -

A message

-

- -
-
inputMessageID#a676a322 id:int = InputMessage;
-inputMessageReplyTo#bad88395 id:int = InputMessage;
-inputMessagePinned#86872538 = InputMessage;
-inputMessageCallbackQuery#acfa1a7e id:int query_id:long = InputMessage;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputMessageIDMessage by ID
inputMessageReplyToMessage to which the specified message replies to
inputMessagePinnedPinned message
inputMessageCallbackQueryUsed by bots for fetching information about the message that originated a callback query
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputNotifyPeer.html b/data/corefork.telegram.org/type/InputNotifyPeer.html deleted file mode 100644 index b1c0917215..0000000000 --- a/data/corefork.telegram.org/type/InputNotifyPeer.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - - InputNotifyPeer - - - - - - - - - - - - - -
- -
-
-
- -

InputNotifyPeer

- -

Object defines the set of users and/or groups that generate notifications.

-

- -
-
inputNotifyPeer#b8bc5b0c peer:InputPeer = InputNotifyPeer;
-inputNotifyUsers#193b4417 = InputNotifyPeer;
-inputNotifyChats#4a95e84e = InputNotifyPeer;
-inputNotifyBroadcasts#b1db7c7e = InputNotifyPeer;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputNotifyPeerNotifications generated by a certain user or group.
inputNotifyUsersNotifications generated by all users.
inputNotifyChatsNotifications generated by all groups.
inputNotifyBroadcastsAll channels
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputPaymentCredentials.html b/data/corefork.telegram.org/type/InputPaymentCredentials.html deleted file mode 100644 index 165fcd84b6..0000000000 --- a/data/corefork.telegram.org/type/InputPaymentCredentials.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - - InputPaymentCredentials - - - - - - - - - - - - - -
- -
-
-
- -

InputPaymentCredentials

- -

Payment credentials

-

- -
-
inputPaymentCredentialsSaved#c10eb2cf id:string tmp_password:bytes = InputPaymentCredentials;
-inputPaymentCredentials#3417d728 flags:# save:flags.0?true data:DataJSON = InputPaymentCredentials;
-inputPaymentCredentialsApplePay#aa1c39f payment_data:DataJSON = InputPaymentCredentials;
-inputPaymentCredentialsGooglePay#8ac32801 payment_token:DataJSON = InputPaymentCredentials;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputPaymentCredentialsSavedSaved payment credentials
inputPaymentCredentialsPayment credentials
inputPaymentCredentialsApplePayApple pay payment credentials
inputPaymentCredentialsGooglePayGoogle Pay payment credentials
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputPeer.html b/data/corefork.telegram.org/type/InputPeer.html deleted file mode 100644 index b4d03a4a8d..0000000000 --- a/data/corefork.telegram.org/type/InputPeer.html +++ /dev/null @@ -1,173 +0,0 @@ - - - - - InputPeer - - - - - - - - - - - - - -
- -
-
-
- -

InputPeer

- -

Peer

-

- -
-
inputPeerEmpty#7f3b18ea = InputPeer;
-inputPeerSelf#7da07ec9 = InputPeer;
-inputPeerChat#35a95cb9 chat_id:long = InputPeer;
-inputPeerUser#dde8a54c user_id:long access_hash:long = InputPeer;
-inputPeerChannel#27bcbbfc channel_id:long access_hash:long = InputPeer;
-inputPeerUserFromMessage#a87b0a1c peer:InputPeer msg_id:int user_id:long = InputPeer;
-inputPeerChannelFromMessage#bd2a0840 peer:InputPeer msg_id:int channel_id:long = InputPeer;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputPeerEmptyAn empty constructor, no user or chat is defined.
inputPeerSelfDefines the current user.
inputPeerChatDefines a chat for further interaction.
inputPeerUserDefines a user for further interaction.
inputPeerChannelDefines a channel for further interaction.
inputPeerUserFromMessageDefines a min user that was seen in a certain message of a certain chat.
inputPeerChannelFromMessageDefines a min channel that was seen in a certain message of a certain chat.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputPeerNotifySettings.html b/data/corefork.telegram.org/type/InputPeerNotifySettings.html deleted file mode 100644 index d65f3df4e6..0000000000 --- a/data/corefork.telegram.org/type/InputPeerNotifySettings.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - InputPeerNotifySettings - - - - - - - - - - - - - -
- -
-
-
- -

InputPeerNotifySettings

- -

Notifications settings.

-

- -
-
inputPeerNotifySettings#9c3d198e flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = InputPeerNotifySettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inputPeerNotifySettingsNotification settings.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputPhoneCall.html b/data/corefork.telegram.org/type/InputPhoneCall.html deleted file mode 100644 index 9c1a4e3bad..0000000000 --- a/data/corefork.telegram.org/type/InputPhoneCall.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - InputPhoneCall - - - - - - - - - - - - - -
- -
-
-
- -

InputPhoneCall

- -

Phone call

-

- -
-
inputPhoneCall#1e36fded id:long access_hash:long = InputPhoneCall;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inputPhoneCallPhone call
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputPhoto.html b/data/corefork.telegram.org/type/InputPhoto.html deleted file mode 100644 index 4e1149ff17..0000000000 --- a/data/corefork.telegram.org/type/InputPhoto.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - InputPhoto - - - - - - - - - - - - - -
- -
-
-
- -

InputPhoto

- -

Defines a photo for further interaction.

-

- -
-
inputPhotoEmpty#1cd7bf0d = InputPhoto;
-inputPhoto#3bb3b94a id:long access_hash:long file_reference:bytes = InputPhoto;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
inputPhotoEmptyEmpty constructor.
inputPhotoDefines a photo for further interaction.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputPrivacyKey.html b/data/corefork.telegram.org/type/InputPrivacyKey.html deleted file mode 100644 index add8e6263f..0000000000 --- a/data/corefork.telegram.org/type/InputPrivacyKey.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - InputPrivacyKey - - - - - - - - - - - - - -
- -
-
-
- -

InputPrivacyKey

- -

Privacy key

-

- -
-
inputPrivacyKeyStatusTimestamp#4f96cb18 = InputPrivacyKey;
-inputPrivacyKeyChatInvite#bdfb0426 = InputPrivacyKey;
-inputPrivacyKeyPhoneCall#fabadc5f = InputPrivacyKey;
-inputPrivacyKeyPhoneP2P#db9e70d2 = InputPrivacyKey;
-inputPrivacyKeyForwards#a4dd4c08 = InputPrivacyKey;
-inputPrivacyKeyProfilePhoto#5719bacc = InputPrivacyKey;
-inputPrivacyKeyPhoneNumber#352dafa = InputPrivacyKey;
-inputPrivacyKeyAddedByPhone#d1219bdd = InputPrivacyKey;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputPrivacyKeyStatusTimestampWhether we can see the exact last online timestamp of the user
inputPrivacyKeyChatInviteWhether the user can be invited to chats
inputPrivacyKeyPhoneCallWhether the user will accept phone calls
inputPrivacyKeyPhoneP2PWhether the user allows P2P communication during VoIP calls
inputPrivacyKeyForwardsWhether messages forwarded from this user will be anonymous
inputPrivacyKeyProfilePhotoWhether people will be able to see the user's profile picture
inputPrivacyKeyPhoneNumberWhether people will be able to see the user's phone number
inputPrivacyKeyAddedByPhoneWhether people can add you to their contact list by your phone number
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputPrivacyRule.html b/data/corefork.telegram.org/type/InputPrivacyRule.html deleted file mode 100644 index 29a7468793..0000000000 --- a/data/corefork.telegram.org/type/InputPrivacyRule.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - InputPrivacyRule - - - - - - - - - - - - - -
- -
-
-
- -

InputPrivacyRule

- -

Privacy rule

-

- -
-
inputPrivacyValueAllowContacts#d09e07b = InputPrivacyRule;
-inputPrivacyValueAllowAll#184b35ce = InputPrivacyRule;
-inputPrivacyValueAllowUsers#131cc67f users:Vector<InputUser> = InputPrivacyRule;
-inputPrivacyValueDisallowContacts#ba52007 = InputPrivacyRule;
-inputPrivacyValueDisallowAll#d66b66c9 = InputPrivacyRule;
-inputPrivacyValueDisallowUsers#90110467 users:Vector<InputUser> = InputPrivacyRule;
-inputPrivacyValueAllowChatParticipants#840649cf chats:Vector<long> = InputPrivacyRule;
-inputPrivacyValueDisallowChatParticipants#e94f0f86 chats:Vector<long> = InputPrivacyRule;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputPrivacyValueAllowContactsAllow only contacts
inputPrivacyValueAllowAllAllow all users
inputPrivacyValueAllowUsersAllow only certain users
inputPrivacyValueDisallowContactsDisallow only contacts
inputPrivacyValueDisallowAllDisallow all
inputPrivacyValueDisallowUsersDisallow only certain users
inputPrivacyValueAllowChatParticipantsAllow only participants of certain chats
inputPrivacyValueDisallowChatParticipantsDisallow only participants of certain chats
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputSecureFile.html b/data/corefork.telegram.org/type/InputSecureFile.html deleted file mode 100644 index a1c55e96eb..0000000000 --- a/data/corefork.telegram.org/type/InputSecureFile.html +++ /dev/null @@ -1,151 +0,0 @@ - - - - - InputSecureFile - - - - - - - - - - - - - -
- -
-
-
- -

InputSecureFile

- -

Secure passport file, for more info see the passport docs »

-

- -
-
inputSecureFileUploaded#3334b0f0 id:long parts:int md5_checksum:string file_hash:bytes secret:bytes = InputSecureFile;
-inputSecureFile#5367e5be id:long access_hash:long = InputSecureFile;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
inputSecureFileUploadedUploaded secure file, for more info see the passport docs »
inputSecureFilePreuploaded passport file, for more info see the passport docs »
-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputSecureValue.html b/data/corefork.telegram.org/type/InputSecureValue.html deleted file mode 100644 index a49125d09b..0000000000 --- a/data/corefork.telegram.org/type/InputSecureValue.html +++ /dev/null @@ -1,145 +0,0 @@ - - - - - InputSecureValue - - - - - - - - - - - - - -
- -
-
-
- -

InputSecureValue

- -

Secure value, for more info see the passport docs »

-

- -
-
inputSecureValue#db21d0a7 flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?InputSecureFile reverse_side:flags.2?InputSecureFile selfie:flags.3?InputSecureFile translation:flags.6?Vector<InputSecureFile> files:flags.4?Vector<InputSecureFile> plain_data:flags.5?SecurePlainData = InputSecureValue;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inputSecureValueSecure value, for more info see the passport docs »
-

Related pages

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputSingleMedia.html b/data/corefork.telegram.org/type/InputSingleMedia.html deleted file mode 100644 index 53df231801..0000000000 --- a/data/corefork.telegram.org/type/InputSingleMedia.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - InputSingleMedia - - - - - - - - - - - - - -
- -
-
-
- -

InputSingleMedia

- -

A single media in an album or grouped media sent with messages.sendMultiMedia.

-

- -
-
inputSingleMedia#1cc6e91f flags:# media:InputMedia random_id:long message:string entities:flags.0?Vector<MessageEntity> = InputSingleMedia;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inputSingleMediaA single media in an album or grouped media sent with messages.sendMultiMedia.
-

Related pages

-

Uploading and Downloading Files

-

How to transfer large data batches correctly.

-

messages.sendMultiMedia

-

Send an album or grouped media

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputStickerSet.html b/data/corefork.telegram.org/type/InputStickerSet.html deleted file mode 100644 index 9128437107..0000000000 --- a/data/corefork.telegram.org/type/InputStickerSet.html +++ /dev/null @@ -1,168 +0,0 @@ - - - - - InputStickerSet - - - - - - - - - - - - - -
- -
-
-
- -

InputStickerSet

- -

Represents a stickerset

-

- -
-
inputStickerSetEmpty#ffb62b95 = InputStickerSet;
-inputStickerSetID#9de7a269 id:long access_hash:long = InputStickerSet;
-inputStickerSetShortName#861cc8a0 short_name:string = InputStickerSet;
-inputStickerSetAnimatedEmoji#28703c8 = InputStickerSet;
-inputStickerSetDice#e67f520e emoticon:string = InputStickerSet;
-inputStickerSetAnimatedEmojiAnimations#cde3739 = InputStickerSet;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputStickerSetEmptyEmpty constructor
inputStickerSetIDStickerset by ID
inputStickerSetShortNameStickerset by short name, from tg://addstickers?set=short_name
inputStickerSetAnimatedEmojiAnimated emojis stickerset
inputStickerSetDiceSend a dice
inputStickerSetAnimatedEmojiAnimationsAnimated emoji reaction stickerset (contains animations to play when a user clicks on a given animated emoji)
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputStickerSetItem.html b/data/corefork.telegram.org/type/InputStickerSetItem.html deleted file mode 100644 index def2440630..0000000000 --- a/data/corefork.telegram.org/type/InputStickerSetItem.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - InputStickerSetItem - - - - - - - - - - - - - -
- -
-
-
- -

InputStickerSetItem

- -

Sticker

-

- -
-
inputStickerSetItem#ffa0a496 flags:# document:InputDocument emoji:string mask_coords:flags.0?MaskCoords = InputStickerSetItem;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inputStickerSetItemSticker in a stickerset
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputStickeredMedia.html b/data/corefork.telegram.org/type/InputStickeredMedia.html deleted file mode 100644 index abef4d2a7c..0000000000 --- a/data/corefork.telegram.org/type/InputStickeredMedia.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - InputStickeredMedia - - - - - - - - - - - - - -
- -
-
-
- -

InputStickeredMedia

- -

Represents a media with attached stickers

-

- -
-
inputStickeredMediaPhoto#4a992157 id:InputPhoto = InputStickeredMedia;
-inputStickeredMediaDocument#438865b id:InputDocument = InputStickeredMedia;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
inputStickeredMediaPhotoA photo with stickers attached
inputStickeredMediaDocumentA document with stickers attached
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputTheme.html b/data/corefork.telegram.org/type/InputTheme.html deleted file mode 100644 index c0f1b6a12b..0000000000 --- a/data/corefork.telegram.org/type/InputTheme.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - InputTheme - - - - - - - - - - - - - -
- -
-
-
- -

InputTheme

- -

Cloud theme

-

- -
-
inputTheme#3c5693e9 id:long access_hash:long = InputTheme;
-inputThemeSlug#f5890df1 slug:string = InputTheme;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
inputThemeTheme
inputThemeSlugTheme by theme ID
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputThemeSettings.html b/data/corefork.telegram.org/type/InputThemeSettings.html deleted file mode 100644 index c5f500b61a..0000000000 --- a/data/corefork.telegram.org/type/InputThemeSettings.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - InputThemeSettings - - - - - - - - - - - - - -
- -
-
-
- -

InputThemeSettings

- -

Theme settings

-

- -
-
inputThemeSettings#8fde504f flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int outbox_accent_color:flags.3?int message_colors:flags.0?Vector<int> wallpaper:flags.1?InputWallPaper wallpaper_settings:flags.1?WallPaperSettings = InputThemeSettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inputThemeSettingsTheme settings
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputUser.html b/data/corefork.telegram.org/type/InputUser.html deleted file mode 100644 index 12e3526161..0000000000 --- a/data/corefork.telegram.org/type/InputUser.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - - InputUser - - - - - - - - - - - - - -
- -
-
-
- -

InputUser

- -

Defines a user for subsequent interaction.

-

- -
-
inputUserEmpty#b98886cf = InputUser;
-inputUserSelf#f7c1b13f = InputUser;
-inputUser#f21158c6 user_id:long access_hash:long = InputUser;
-inputUserFromMessage#1da448e2 peer:InputPeer msg_id:int user_id:long = InputUser;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputUserEmptyEmpty constructor, does not define a user.
inputUserSelfDefines the current user.
inputUserDefines a user for further interaction.
inputUserFromMessageDefines a min user that was seen in a certain message of a certain chat.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputWallPaper.html b/data/corefork.telegram.org/type/InputWallPaper.html deleted file mode 100644 index 1009bd0530..0000000000 --- a/data/corefork.telegram.org/type/InputWallPaper.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - InputWallPaper - - - - - - - - - - - - - -
- -
-
-
- -

InputWallPaper

- -

Wallpaper

-

- -
-
inputWallPaper#e630b979 id:long access_hash:long = InputWallPaper;
-inputWallPaperSlug#72091c80 slug:string = InputWallPaper;
-inputWallPaperNoFile#967a462e id:long = InputWallPaper;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputWallPaperWallpaper
inputWallPaperSlugWallpaper by slug (a unique ID)
inputWallPaperNoFileWallpaper with no file
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputWebDocument.html b/data/corefork.telegram.org/type/InputWebDocument.html deleted file mode 100644 index bb59fbe9bb..0000000000 --- a/data/corefork.telegram.org/type/InputWebDocument.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - InputWebDocument - - - - - - - - - - - - - -
- -
-
-
- -

InputWebDocument

- -

Specifies a document that will have to be downloaded from the URL by the telegram servers

-

- -
-
inputWebDocument#9bed434d url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = InputWebDocument;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
inputWebDocumentThe document
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/InputWebFileLocation.html b/data/corefork.telegram.org/type/InputWebFileLocation.html deleted file mode 100644 index 4e09dceb44..0000000000 --- a/data/corefork.telegram.org/type/InputWebFileLocation.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - InputWebFileLocation - - - - - - - - - - - - - -
- -
-
-
- -

InputWebFileLocation

- -

Location of remote file

-

- -
-
inputWebFileLocation#c239d686 url:string access_hash:long = InputWebFileLocation;
-inputWebFileGeoPointLocation#9f2221c9 geo_point:InputGeoPoint access_hash:long w:int h:int zoom:int scale:int = InputWebFileLocation;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
inputWebFileLocationLocation of a remote HTTP(s) file
inputWebFileGeoPointLocationGeolocation
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/Invoice.html b/data/corefork.telegram.org/type/Invoice.html deleted file mode 100644 index f491cd934e..0000000000 --- a/data/corefork.telegram.org/type/Invoice.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - Invoice - - - - - - - - - - - - - -
- -
-
-
- -

Invoice

- -

Invoice

-

- -
-
invoice#cd886e0 flags:# test:flags.0?true name_requested:flags.1?true phone_requested:flags.2?true email_requested:flags.3?true shipping_address_requested:flags.4?true flexible:flags.5?true phone_to_provider:flags.6?true email_to_provider:flags.7?true currency:string prices:Vector<LabeledPrice> max_tip_amount:flags.8?long suggested_tip_amounts:flags.8?Vector<long> = Invoice;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
invoiceInvoice
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/JSONObjectValue.html b/data/corefork.telegram.org/type/JSONObjectValue.html deleted file mode 100644 index 850d4f1ee8..0000000000 --- a/data/corefork.telegram.org/type/JSONObjectValue.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - JSONObjectValue - - - - - - - - - - - - - -
- -
-
-
- -

JSONObjectValue

- -

JSON key: value pair

-

- -
-
jsonObjectValue#c0de1bd9 key:string value:JSONValue = JSONObjectValue;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
jsonObjectValueJSON key: value pair
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/JSONValue.html b/data/corefork.telegram.org/type/JSONValue.html deleted file mode 100644 index 0d4aebe07f..0000000000 --- a/data/corefork.telegram.org/type/JSONValue.html +++ /dev/null @@ -1,187 +0,0 @@ - - - - - JSONValue - - - - - - - - - - - - - -
- -
-
-
- -

JSONValue

- -

JSON value

-

- -
-
jsonNull#3f6d7b68 = JSONValue;
-jsonBool#c7345e6a value:Bool = JSONValue;
-jsonNumber#2be0dfa4 value:double = JSONValue;
-jsonString#b71e767a value:string = JSONValue;
-jsonArray#f7444763 value:Vector<JSONValue> = JSONValue;
-jsonObject#99c1d49d value:Vector<JSONObjectValue> = JSONValue;
-
----functions---
-
-help.getAppConfig#98914110 = JSONValue;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
jsonNullnull JSON value
jsonBoolJSON boolean value
jsonNumberJSON numeric value
jsonStringJSON string
jsonArrayJSON array
jsonObjectJSON object value
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getAppConfigGet app-specific configuration
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/KeyboardButton.html b/data/corefork.telegram.org/type/KeyboardButton.html deleted file mode 100644 index f7de7eb7ed..0000000000 --- a/data/corefork.telegram.org/type/KeyboardButton.html +++ /dev/null @@ -1,193 +0,0 @@ - - - - - KeyboardButton - - - - - - - - - - - - - -
- -
-
-
- -

KeyboardButton

- -

Bot or inline keyboard buttons

-

- -
-
keyboardButton#a2fa4880 text:string = KeyboardButton;
-keyboardButtonUrl#258aff05 text:string url:string = KeyboardButton;
-keyboardButtonCallback#35bbdb6b flags:# requires_password:flags.0?true text:string data:bytes = KeyboardButton;
-keyboardButtonRequestPhone#b16a6c29 text:string = KeyboardButton;
-keyboardButtonRequestGeoLocation#fc796b3f text:string = KeyboardButton;
-keyboardButtonSwitchInline#568a748 flags:# same_peer:flags.0?true text:string query:string = KeyboardButton;
-keyboardButtonGame#50f41ccf text:string = KeyboardButton;
-keyboardButtonBuy#afd93fbb text:string = KeyboardButton;
-keyboardButtonUrlAuth#10b78d29 flags:# text:string fwd_text:flags.0?string url:string button_id:int = KeyboardButton;
-inputKeyboardButtonUrlAuth#d02e7fd4 flags:# request_write_access:flags.0?true text:string fwd_text:flags.1?string url:string bot:InputUser = KeyboardButton;
-keyboardButtonRequestPoll#bbc7515d flags:# quiz:flags.0?Bool text:string = KeyboardButton;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
keyboardButtonBot keyboard button
keyboardButtonUrlURL button
keyboardButtonCallbackCallback button
keyboardButtonRequestPhoneButton to request a user's phone number
keyboardButtonRequestGeoLocationButton to request a user's geolocation
keyboardButtonSwitchInlineButton to force a user to switch to inline mode Pressing the button will prompt the user to select one of their chats, open that chat and insert the bot‘s username and the specified inline query in the input field.
keyboardButtonGameButton to start a game
keyboardButtonBuyButton to buy a product
keyboardButtonUrlAuthButton to request a user to authorize via URL using Seamless Telegram Login. When the user clicks on such a button, messages.requestUrlAuth should be called, providing the button_id and the ID of the container message. The returned urlAuthResultRequest object will contain more details about the authorization request (request_write_access if the bot would like to send messages to the user along with the username of the bot which will be used for user authorization). Finally, the user can choose to call messages.acceptUrlAuth to get a urlAuthResultAccepted with the URL to open instead of the url of this constructor, or a urlAuthResultDefault, in which case the url of this constructor must be opened, instead. If the user refuses the authorization request but still wants to open the link, the url of this constructor must be used.
inputKeyboardButtonUrlAuthButton to request a user to authorize via URL using Seamless Telegram Login.
keyboardButtonRequestPollA button that allows the user to create and send a poll when pressed; available only in private
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/KeyboardButtonRow.html b/data/corefork.telegram.org/type/KeyboardButtonRow.html deleted file mode 100644 index cac9909cff..0000000000 --- a/data/corefork.telegram.org/type/KeyboardButtonRow.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - KeyboardButtonRow - - - - - - - - - - - - - -
- -
-
-
- -

KeyboardButtonRow

- -

Bot or inline keyboard rows

-

- -
-
keyboardButtonRow#77608b83 buttons:Vector<KeyboardButton> = KeyboardButtonRow;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
keyboardButtonRowInline keyboard row
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/LabeledPrice.html b/data/corefork.telegram.org/type/LabeledPrice.html deleted file mode 100644 index c15c07b9ba..0000000000 --- a/data/corefork.telegram.org/type/LabeledPrice.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - LabeledPrice - - - - - - - - - - - - - -
- -
-
-
- -

LabeledPrice

- -

Labeled pricetag

-

- -
-
labeledPrice#cb296bf8 label:string amount:long = LabeledPrice;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
labeledPriceThis object represents a portion of the price for goods or services.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/LangPackDifference.html b/data/corefork.telegram.org/type/LangPackDifference.html deleted file mode 100644 index 47fab2d914..0000000000 --- a/data/corefork.telegram.org/type/LangPackDifference.html +++ /dev/null @@ -1,167 +0,0 @@ - - - - - LangPackDifference - - - - - - - - - - - - - -
- -
-
-
- -

LangPackDifference

- -

Language pack changes

-

- -
-
langPackDifference#f385c1f6 lang_code:string from_version:int version:int strings:Vector<LangPackString> = LangPackDifference;
-
----functions---
-
-langpack.getLangPack#f2f2330a lang_pack:string lang_code:string = LangPackDifference;
-langpack.getDifference#cd984aa5 lang_pack:string lang_code:string from_version:int = LangPackDifference;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
langPackDifferenceChanges to the app's localization pack
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
langpack.getLangPackGet localization pack strings
langpack.getDifferenceGet new strings in languagepack
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/LangPackLanguage.html b/data/corefork.telegram.org/type/LangPackLanguage.html deleted file mode 100644 index feb09c962d..0000000000 --- a/data/corefork.telegram.org/type/LangPackLanguage.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - LangPackLanguage - - - - - - - - - - - - - -
- -
-
-
- -

LangPackLanguage

- -

Language pack language

-

- -
-
langPackLanguage#eeca5ce3 flags:# official:flags.0?true rtl:flags.2?true beta:flags.3?true name:string native_name:string lang_code:string base_lang_code:flags.1?string plural_code:string strings_count:int translated_count:int translations_url:string = LangPackLanguage;
-
----functions---
-
-langpack.getLanguage#6a596502 lang_pack:string lang_code:string = LangPackLanguage;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
langPackLanguageIdentifies a localization pack
-

Methods

- - - - - - - - - - - - - -
MethodDescription
langpack.getLanguageGet information about a language in a localization pack
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/LangPackString.html b/data/corefork.telegram.org/type/LangPackString.html deleted file mode 100644 index 215af5bb6b..0000000000 --- a/data/corefork.telegram.org/type/LangPackString.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - LangPackString - - - - - - - - - - - - - -
- -
-
-
- -

LangPackString

- -

Language pack string

-

- -
-
langPackString#cad181f6 key:string value:string = LangPackString;
-langPackStringPluralized#6c47ac9f flags:# key:string zero_value:flags.0?string one_value:flags.1?string two_value:flags.2?string few_value:flags.3?string many_value:flags.4?string other_value:string = LangPackString;
-langPackStringDeleted#2979eeb2 key:string = LangPackString;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
langPackStringTranslated localization string
langPackStringPluralizedA language pack string which has different forms based on the number of some object it mentions. See https://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html for more info
langPackStringDeletedDeleted localization string
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/MaskCoords.html b/data/corefork.telegram.org/type/MaskCoords.html deleted file mode 100644 index ad8a0859f7..0000000000 --- a/data/corefork.telegram.org/type/MaskCoords.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - MaskCoords - - - - - - - - - - - - - -
- -
-
-
- -

MaskCoords

- -

Mask coordinates (if this is a mask sticker, attached to a photo)

-

- -
-
maskCoords#aed6dbb2 n:int x:double y:double zoom:double = MaskCoords;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
maskCoordsPosition on a photo where a mask should be placed

The n position indicates where the mask should be placed:

- 0 => Relative to the forehead
- 1 => Relative to the eyes
- 2 => Relative to the mouth
- 3 => Relative to the chin
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/Message.html b/data/corefork.telegram.org/type/Message.html deleted file mode 100644 index 304a294082..0000000000 --- a/data/corefork.telegram.org/type/Message.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - Message - - - - - - - - - - - - - -
- -
-
-
- -

Message

- -

Object describing a message.

-

- -
-
messageEmpty#90a6ca84 flags:# id:int peer_id:flags.0?Peer = Message;
-message#85d6cbe2 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true from_scheduled:flags.18?true legacy:flags.19?true edit_hide:flags.21?true pinned:flags.24?true noforwards:flags.26?true id:int from_id:flags.8?Peer peer_id:Peer fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader date:int message:string media:flags.9?MessageMedia reply_markup:flags.6?ReplyMarkup entities:flags.7?Vector<MessageEntity> views:flags.10?int forwards:flags.10?int replies:flags.23?MessageReplies edit_date:flags.15?int post_author:flags.16?string grouped_id:flags.17?long restriction_reason:flags.22?Vector<RestrictionReason> ttl_period:flags.25?int = Message;
-messageService#2b085862 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true post:flags.14?true legacy:flags.19?true id:int from_id:flags.8?Peer peer_id:Peer reply_to:flags.3?MessageReplyHeader date:int action:MessageAction ttl_period:flags.25?int = Message;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
messageEmptyEmpty constructor, non-existent message.
messageA message
messageServiceIndicates a service message
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/MessageAction.html b/data/corefork.telegram.org/type/MessageAction.html deleted file mode 100644 index 8f8bc88e38..0000000000 --- a/data/corefork.telegram.org/type/MessageAction.html +++ /dev/null @@ -1,283 +0,0 @@ - - - - - MessageAction - - - - - - - - - - - - - -
- -
-
-
- -

MessageAction

- -

Object describing actions connected to a service message.

-

- -
-
messageActionEmpty#b6aef7b0 = MessageAction;
-messageActionChatCreate#bd47cbad title:string users:Vector<long> = MessageAction;
-messageActionChatEditTitle#b5a1ce5a title:string = MessageAction;
-messageActionChatEditPhoto#7fcb13a8 photo:Photo = MessageAction;
-messageActionChatDeletePhoto#95e3fbef = MessageAction;
-messageActionChatAddUser#15cefd00 users:Vector<long> = MessageAction;
-messageActionChatDeleteUser#a43f30cc user_id:long = MessageAction;
-messageActionChatJoinedByLink#31224c3 inviter_id:long = MessageAction;
-messageActionChannelCreate#95d2ac92 title:string = MessageAction;
-messageActionChatMigrateTo#e1037f92 channel_id:long = MessageAction;
-messageActionChannelMigrateFrom#ea3948e9 title:string chat_id:long = MessageAction;
-messageActionPinMessage#94bd38ed = MessageAction;
-messageActionHistoryClear#9fbab604 = MessageAction;
-messageActionGameScore#92a72876 game_id:long score:int = MessageAction;
-messageActionPaymentSentMe#8f31b327 flags:# currency:string total_amount:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string charge:PaymentCharge = MessageAction;
-messageActionPaymentSent#40699cd0 currency:string total_amount:long = MessageAction;
-messageActionPhoneCall#80e11a7f flags:# video:flags.2?true call_id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = MessageAction;
-messageActionScreenshotTaken#4792929b = MessageAction;
-messageActionCustomAction#fae69f56 message:string = MessageAction;
-messageActionBotAllowed#abe9affe domain:string = MessageAction;
-messageActionSecureValuesSentMe#1b287353 values:Vector<SecureValue> credentials:SecureCredentialsEncrypted = MessageAction;
-messageActionSecureValuesSent#d95c6154 types:Vector<SecureValueType> = MessageAction;
-messageActionContactSignUp#f3f25f76 = MessageAction;
-messageActionGeoProximityReached#98e0d697 from_id:Peer to_id:Peer distance:int = MessageAction;
-messageActionGroupCall#7a0d7f42 flags:# call:InputGroupCall duration:flags.0?int = MessageAction;
-messageActionInviteToGroupCall#502f92f7 call:InputGroupCall users:Vector<long> = MessageAction;
-messageActionSetMessagesTTL#aa1afbfd period:int = MessageAction;
-messageActionGroupCallScheduled#b3a07661 call:InputGroupCall schedule_date:int = MessageAction;
-messageActionSetChatTheme#aa786345 emoticon:string = MessageAction;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
messageActionEmptyEmpty constructor.
messageActionChatCreateGroup created
messageActionChatEditTitleGroup name changed.
messageActionChatEditPhotoGroup profile changed
messageActionChatDeletePhotoGroup profile photo removed.
messageActionChatAddUserNew member in the group
messageActionChatDeleteUserUser left the group.
messageActionChatJoinedByLinkA user joined the chat via an invite link
messageActionChannelCreateThe channel was created
messageActionChatMigrateToIndicates the chat was migrated to the specified supergroup
messageActionChannelMigrateFromIndicates the channel was migrated from the specified chat
messageActionPinMessageA message was pinned
messageActionHistoryClearChat history was cleared
messageActionGameScoreSomeone scored in a game
messageActionPaymentSentMeA user just sent a payment to me (a bot)
messageActionPaymentSentA payment was sent
messageActionPhoneCallA phone call
messageActionScreenshotTakenA screenshot of the chat was taken
messageActionCustomActionCustom action (most likely not supported by the current layer, an upgrade might be needed)
messageActionBotAllowedThe domain name of the website on which the user has logged in. More about Telegram Login »
messageActionSecureValuesSentMeSecure telegram passport values were received
messageActionSecureValuesSentRequest for secure telegram passport values was sent
messageActionContactSignUpA contact just signed up to telegram
messageActionGeoProximityReachedWe are now in proximity of this user (triggered by the other user, by sending a live geolocation with the proximity_notification_radius flag)
messageActionGroupCallThe group call has ended
messageActionInviteToGroupCallA set of users was invited to the group call
messageActionSetMessagesTTLYou changed the Time-To-Live of your messages in this chat.
messageActionGroupCallScheduledA group call was scheduled
messageActionSetChatThemeThe chat theme was changed
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/MessageEntity.html b/data/corefork.telegram.org/type/MessageEntity.html deleted file mode 100644 index 55b88eacac..0000000000 --- a/data/corefork.telegram.org/type/MessageEntity.html +++ /dev/null @@ -1,233 +0,0 @@ - - - - - MessageEntity - - - - - - - - - - - - - -
- -
-
-
- -

MessageEntity

- -

Message entities, representing styled text in a message

-

- -
-
messageEntityUnknown#bb92ba95 offset:int length:int = MessageEntity;
-messageEntityMention#fa04579d offset:int length:int = MessageEntity;
-messageEntityHashtag#6f635b0d offset:int length:int = MessageEntity;
-messageEntityBotCommand#6cef8ac7 offset:int length:int = MessageEntity;
-messageEntityUrl#6ed02538 offset:int length:int = MessageEntity;
-messageEntityEmail#64e475c2 offset:int length:int = MessageEntity;
-messageEntityBold#bd610bc9 offset:int length:int = MessageEntity;
-messageEntityItalic#826f8b60 offset:int length:int = MessageEntity;
-messageEntityCode#28a20571 offset:int length:int = MessageEntity;
-messageEntityPre#73924be0 offset:int length:int language:string = MessageEntity;
-messageEntityTextUrl#76a6d327 offset:int length:int url:string = MessageEntity;
-messageEntityMentionName#dc7b1140 offset:int length:int user_id:long = MessageEntity;
-inputMessageEntityMentionName#208e68c9 offset:int length:int user_id:InputUser = MessageEntity;
-messageEntityPhone#9b69e34b offset:int length:int = MessageEntity;
-messageEntityCashtag#4c4e743f offset:int length:int = MessageEntity;
-messageEntityUnderline#9c4e7e8b offset:int length:int = MessageEntity;
-messageEntityStrike#bf0693d4 offset:int length:int = MessageEntity;
-messageEntityBlockquote#20df5d0 offset:int length:int = MessageEntity;
-messageEntityBankCard#761e6af4 offset:int length:int = MessageEntity;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
messageEntityUnknownUnknown message entity
messageEntityMentionMessage entity mentioning the current user
messageEntityHashtag#hashtag message entity
messageEntityBotCommandMessage entity representing a bot /command
messageEntityUrlMessage entity representing an in-text url: https://google.com; for text urls, use messageEntityTextUrl.
messageEntityEmailMessage entity representing an email@example.com.
messageEntityBoldMessage entity representing bold text.
messageEntityItalicMessage entity representing italic text.
messageEntityCodeMessage entity representing a codeblock.
messageEntityPreMessage entity representing a preformatted codeblock, allowing the user to specify a programming language for the codeblock.
messageEntityTextUrlMessage entity representing a text url: for in-text urls like https://google.com use messageEntityUrl.
messageEntityMentionNameMessage entity representing a user mention: for creating a mention use inputMessageEntityMentionName.
inputMessageEntityMentionNameMessage entity that can be used to create a user user mention: received mentions use the messageEntityMentionName constructor, instead.
messageEntityPhoneMessage entity representing a phone number.
messageEntityCashtagMessage entity representing a $cashtag.
messageEntityUnderlineMessage entity representing underlined text.
messageEntityStrikeMessage entity representing strikethrough text.
messageEntityBlockquoteMessage entity representing a block quote.
messageEntityBankCardIndicates a credit card number
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/MessageFwdHeader.html b/data/corefork.telegram.org/type/MessageFwdHeader.html deleted file mode 100644 index 814c17e277..0000000000 --- a/data/corefork.telegram.org/type/MessageFwdHeader.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - MessageFwdHeader - - - - - - - - - - - - - -
- -
-
-
- -

MessageFwdHeader

- -

Info about a forwarded message

-

- -
-
messageFwdHeader#5f777dce flags:# imported:flags.7?true from_id:flags.0?Peer from_name:flags.5?string date:int channel_post:flags.2?int post_author:flags.3?string saved_from_peer:flags.4?Peer saved_from_msg_id:flags.4?int psa_type:flags.6?string = MessageFwdHeader;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messageFwdHeaderInfo about a forwarded message
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/MessageInteractionCounters.html b/data/corefork.telegram.org/type/MessageInteractionCounters.html deleted file mode 100644 index 49c7cc0aed..0000000000 --- a/data/corefork.telegram.org/type/MessageInteractionCounters.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - MessageInteractionCounters - - - - - - - - - - - - - -
- -
-
-
- -

MessageInteractionCounters

- -

Message interaction counters

-

- -
-
messageInteractionCounters#ad4fc9bd msg_id:int views:int forwards:int = MessageInteractionCounters;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messageInteractionCountersMessage interaction counters
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/MessageRange.html b/data/corefork.telegram.org/type/MessageRange.html deleted file mode 100644 index 7969e3e104..0000000000 --- a/data/corefork.telegram.org/type/MessageRange.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - MessageRange - - - - - - - - - - - - - -
- -
-
-
- -

MessageRange

- -

Indicates a range of chat messages

-

- -
-
messageRange#ae30253 min_id:int max_id:int = MessageRange;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messageRangeIndicates a range of chat messages
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/MessageReactionsList.html b/data/corefork.telegram.org/type/MessageReactionsList.html deleted file mode 100644 index f9e1e0c275..0000000000 --- a/data/corefork.telegram.org/type/MessageReactionsList.html +++ /dev/null @@ -1,128 +0,0 @@ - - - - - MessageReactionsList - - - - - - - - - - - - - -
- -
-
-
- -

MessageReactionsList

- -

List of message reactions

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/MessageReplies.html b/data/corefork.telegram.org/type/MessageReplies.html deleted file mode 100644 index 917aaad90b..0000000000 --- a/data/corefork.telegram.org/type/MessageReplies.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - MessageReplies - - - - - - - - - - - - - -
- -
-
-
- -

MessageReplies

- -

Info about post comments (for channels) or message replies (for groups)

-

- -
-
messageReplies#83d60fc2 flags:# comments:flags.0?true replies:int replies_pts:int recent_repliers:flags.1?Vector<Peer> channel_id:flags.0?long max_id:flags.2?int read_max_id:flags.3?int = MessageReplies;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messageRepliesInfo about the comment section of a channel post, or a simple message thread
-

Related pages

-

Threads

-

Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/MessageReplyHeader.html b/data/corefork.telegram.org/type/MessageReplyHeader.html deleted file mode 100644 index 92b307af78..0000000000 --- a/data/corefork.telegram.org/type/MessageReplyHeader.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - MessageReplyHeader - - - - - - - - - - - - - -
- -
-
-
- -

MessageReplyHeader

- -

Reply information

-

- -
-
messageReplyHeader#a6d57763 flags:# reply_to_msg_id:int reply_to_peer_id:flags.0?Peer reply_to_top_id:flags.1?int = MessageReplyHeader;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messageReplyHeaderMessage thread information
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/MessageUserVote.html b/data/corefork.telegram.org/type/MessageUserVote.html deleted file mode 100644 index 31861585fc..0000000000 --- a/data/corefork.telegram.org/type/MessageUserVote.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - MessageUserVote - - - - - - - - - - - - - -
- -
-
-
- -

MessageUserVote

- -

How a user voted in a poll

-

- -
-
messageUserVote#34d247b4 user_id:long option:bytes date:int = MessageUserVote;
-messageUserVoteInputOption#3ca5b0ec user_id:long date:int = MessageUserVote;
-messageUserVoteMultiple#8a65e557 user_id:long options:Vector<bytes> date:int = MessageUserVote;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
messageUserVoteUser ID
messageUserVoteInputOptionHow a user voted in a poll (reduced constructor, returned if an option was provided to messages.getPollVotes)
messageUserVoteMultipleHow a user voted in a multiple-choice poll
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/MessageViews.html b/data/corefork.telegram.org/type/MessageViews.html deleted file mode 100644 index 4fc0bb42ab..0000000000 --- a/data/corefork.telegram.org/type/MessageViews.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - MessageViews - - - - - - - - - - - - - -
- -
-
-
- -

MessageViews

- -

View, forward counter + info about replies of a specific message

-

- -
-
messageViews#455b853d flags:# views:flags.0?int forwards:flags.1?int replies:flags.2?MessageReplies = MessageViews;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messageViewsView, forward counter + info about replies of a specific message
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/MessagesFilter.html b/data/corefork.telegram.org/type/MessagesFilter.html deleted file mode 100644 index c47d1641e8..0000000000 --- a/data/corefork.telegram.org/type/MessagesFilter.html +++ /dev/null @@ -1,223 +0,0 @@ - - - - - MessagesFilter - - - - - - - - - - - - - -
- -
-
-
- -

MessagesFilter

- -

Object describes message filter.

-

- -
-
inputMessagesFilterEmpty#57e2f66c = MessagesFilter;
-inputMessagesFilterPhotos#9609a51c = MessagesFilter;
-inputMessagesFilterVideo#9fc00e65 = MessagesFilter;
-inputMessagesFilterPhotoVideo#56e9f0e4 = MessagesFilter;
-inputMessagesFilterDocument#9eddf188 = MessagesFilter;
-inputMessagesFilterUrl#7ef0dd87 = MessagesFilter;
-inputMessagesFilterGif#ffc86587 = MessagesFilter;
-inputMessagesFilterVoice#50f5c392 = MessagesFilter;
-inputMessagesFilterMusic#3751b49e = MessagesFilter;
-inputMessagesFilterChatPhotos#3a20ecb8 = MessagesFilter;
-inputMessagesFilterPhoneCalls#80c99768 flags:# missed:flags.0?true = MessagesFilter;
-inputMessagesFilterRoundVoice#7a7c17a4 = MessagesFilter;
-inputMessagesFilterRoundVideo#b549da53 = MessagesFilter;
-inputMessagesFilterMyMentions#c1f8e69a = MessagesFilter;
-inputMessagesFilterGeo#e7026d0d = MessagesFilter;
-inputMessagesFilterContacts#e062db83 = MessagesFilter;
-inputMessagesFilterPinned#1bb00451 = MessagesFilter;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputMessagesFilterEmptyFilter is absent.
inputMessagesFilterPhotosFilter for messages containing photos.
inputMessagesFilterVideoFilter for messages containing videos.
inputMessagesFilterPhotoVideoFilter for messages containing photos or videos.
inputMessagesFilterDocumentFilter for messages containing documents.
inputMessagesFilterUrlReturn only messages containing URLs
inputMessagesFilterGifReturn only messages containing gifs
inputMessagesFilterVoiceReturn only messages containing voice notes
inputMessagesFilterMusicReturn only messages containing audio files
inputMessagesFilterChatPhotosReturn only chat photo changes
inputMessagesFilterPhoneCallsReturn only phone calls
inputMessagesFilterRoundVoiceReturn only round videos and voice notes
inputMessagesFilterRoundVideoReturn only round videos
inputMessagesFilterMyMentionsReturn only messages where the current user was mentioned
inputMessagesFilterGeoReturn only messages containing geolocations
inputMessagesFilterContactsReturn only messages containing contacts
inputMessagesFilterPinnedFetch only pinned messages
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/NearestDc.html b/data/corefork.telegram.org/type/NearestDc.html deleted file mode 100644 index d190989b56..0000000000 --- a/data/corefork.telegram.org/type/NearestDc.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - NearestDc - - - - - - - - - - - - - -
- -
-
-
- -

NearestDc

- -

Object contains info on nearest data centre.

-

- -
-
nearestDc#8e1a1775 country:string this_dc:int nearest_dc:int = NearestDc;
-
----functions---
-
-help.getNearestDc#1fb33026 = NearestDc;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
nearestDcNearest data centre, according to geo-ip.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getNearestDcReturns info on data centre nearest to the user.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/NotifyPeer.html b/data/corefork.telegram.org/type/NotifyPeer.html deleted file mode 100644 index c357f7fa65..0000000000 --- a/data/corefork.telegram.org/type/NotifyPeer.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - - NotifyPeer - - - - - - - - - - - - - -
- -
-
-
- -

NotifyPeer

- -

Object defines the set of users and/or groups that generate notifications.

-

- -
-
notifyPeer#9fd40bd8 peer:Peer = NotifyPeer;
-notifyUsers#b4c83b4c = NotifyPeer;
-notifyChats#c007cec3 = NotifyPeer;
-notifyBroadcasts#d612e8ef = NotifyPeer;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
notifyPeerNotifications generated by a certain user or group.
notifyUsersNotifications generated by all users.
notifyChatsNotifications generated by all groups.
notifyBroadcastsChannel notification settings
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/Null.html b/data/corefork.telegram.org/type/Null.html deleted file mode 100644 index 35a8bc1d14..0000000000 --- a/data/corefork.telegram.org/type/Null.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - Null - - - - - - - - - - - - - -
- -
-
-
- -

Null

- -

Object corresponds to an arbitrary empty object.

-

- -
-
null#56730bcc = Null;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
nullCorresponds to an arbitrary empty object.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/Page.html b/data/corefork.telegram.org/type/Page.html deleted file mode 100644 index 62b0ebff9b..0000000000 --- a/data/corefork.telegram.org/type/Page.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - Page - - - - - - - - - - - - - -
- -
-
-
- -

Page

- -

Instant view page

-

- -
-
page#98657f0d flags:# part:flags.0?true rtl:flags.1?true v2:flags.2?true url:string blocks:Vector<PageBlock> photos:Vector<Photo> documents:Vector<Document> views:flags.3?int = Page;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
pageInstant view page
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PageBlock.html b/data/corefork.telegram.org/type/PageBlock.html deleted file mode 100644 index 367426db1d..0000000000 --- a/data/corefork.telegram.org/type/PageBlock.html +++ /dev/null @@ -1,283 +0,0 @@ - - - - - PageBlock - - - - - - - - - - - - - -
- -
-
-
- -

PageBlock

- -

Represents an instant view page element

-

- -
-
pageBlockUnsupported#13567e8a = PageBlock;
-pageBlockTitle#70abc3fd text:RichText = PageBlock;
-pageBlockSubtitle#8ffa9a1f text:RichText = PageBlock;
-pageBlockAuthorDate#baafe5e0 author:RichText published_date:int = PageBlock;
-pageBlockHeader#bfd064ec text:RichText = PageBlock;
-pageBlockSubheader#f12bb6e1 text:RichText = PageBlock;
-pageBlockParagraph#467a0766 text:RichText = PageBlock;
-pageBlockPreformatted#c070d93e text:RichText language:string = PageBlock;
-pageBlockFooter#48870999 text:RichText = PageBlock;
-pageBlockDivider#db20b188 = PageBlock;
-pageBlockAnchor#ce0d37b0 name:string = PageBlock;
-pageBlockList#e4e88011 items:Vector<PageListItem> = PageBlock;
-pageBlockBlockquote#263d7c26 text:RichText caption:RichText = PageBlock;
-pageBlockPullquote#4f4456d3 text:RichText caption:RichText = PageBlock;
-pageBlockPhoto#1759c560 flags:# photo_id:long caption:PageCaption url:flags.0?string webpage_id:flags.0?long = PageBlock;
-pageBlockVideo#7c8fe7b6 flags:# autoplay:flags.0?true loop:flags.1?true video_id:long caption:PageCaption = PageBlock;
-pageBlockCover#39f23300 cover:PageBlock = PageBlock;
-pageBlockEmbed#a8718dc5 flags:# full_width:flags.0?true allow_scrolling:flags.3?true url:flags.1?string html:flags.2?string poster_photo_id:flags.4?long w:flags.5?int h:flags.5?int caption:PageCaption = PageBlock;
-pageBlockEmbedPost#f259a80b url:string webpage_id:long author_photo_id:long author:string date:int blocks:Vector<PageBlock> caption:PageCaption = PageBlock;
-pageBlockCollage#65a0fa4d items:Vector<PageBlock> caption:PageCaption = PageBlock;
-pageBlockSlideshow#31f9590 items:Vector<PageBlock> caption:PageCaption = PageBlock;
-pageBlockChannel#ef1751b5 channel:Chat = PageBlock;
-pageBlockAudio#804361ea audio_id:long caption:PageCaption = PageBlock;
-pageBlockKicker#1e148390 text:RichText = PageBlock;
-pageBlockTable#bf4dea82 flags:# bordered:flags.0?true striped:flags.1?true title:RichText rows:Vector<PageTableRow> = PageBlock;
-pageBlockOrderedList#9a8ae1e1 items:Vector<PageListOrderedItem> = PageBlock;
-pageBlockDetails#76768bed flags:# open:flags.0?true blocks:Vector<PageBlock> title:RichText = PageBlock;
-pageBlockRelatedArticles#16115a96 title:RichText articles:Vector<PageRelatedArticle> = PageBlock;
-pageBlockMap#a44f3ef6 geo:GeoPoint zoom:int w:int h:int caption:PageCaption = PageBlock;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
pageBlockUnsupportedUnsupported IV element
pageBlockTitleTitle
pageBlockSubtitleSubtitle
pageBlockAuthorDateAuthor and date of creation of article
pageBlockHeaderPage header
pageBlockSubheaderSubheader
pageBlockParagraphA paragraph
pageBlockPreformattedPreformatted (<pre> text)
pageBlockFooterPage footer
pageBlockDividerAn empty block separating a page
pageBlockAnchorLink to section within the page itself (like <a href="#target">anchor</a>)
pageBlockListUnordered list of IV blocks
pageBlockBlockquoteQuote (equivalent to the HTML <blockquote>)
pageBlockPullquotePullquote
pageBlockPhotoA photo
pageBlockVideoVideo
pageBlockCoverA page cover
pageBlockEmbedAn embedded webpage
pageBlockEmbedPostAn embedded post
pageBlockCollageCollage of media
pageBlockSlideshowSlideshow
pageBlockChannelReference to a telegram channel
pageBlockAudioAudio
pageBlockKickerKicker
pageBlockTableTable
pageBlockOrderedListOrdered list of IV blocks
pageBlockDetailsA collapsible details block
pageBlockRelatedArticlesRelated articles
pageBlockMapA map
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PageCaption.html b/data/corefork.telegram.org/type/PageCaption.html deleted file mode 100644 index f402925c6a..0000000000 --- a/data/corefork.telegram.org/type/PageCaption.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PageCaption - - - - - - - - - - - - - -
- -
-
-
- -

PageCaption

- -

Page caption

-

- -
-
pageCaption#6f747657 text:RichText credit:RichText = PageCaption;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
pageCaptionPage caption
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PageListItem.html b/data/corefork.telegram.org/type/PageListItem.html deleted file mode 100644 index b006e41ab2..0000000000 --- a/data/corefork.telegram.org/type/PageListItem.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - PageListItem - - - - - - - - - - - - - -
- -
-
-
- -

PageListItem

- -

Item in block list

-

- -
-
pageListItemText#b92fb6cd text:RichText = PageListItem;
-pageListItemBlocks#25e073fc blocks:Vector<PageBlock> = PageListItem;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
pageListItemTextList item
pageListItemBlocksList item
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PageListOrderedItem.html b/data/corefork.telegram.org/type/PageListOrderedItem.html deleted file mode 100644 index 1d07e0bd56..0000000000 --- a/data/corefork.telegram.org/type/PageListOrderedItem.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - PageListOrderedItem - - - - - - - - - - - - - -
- -
-
-
- -

PageListOrderedItem

- -

Represents an instant view ordered list

-

- -
-
pageListOrderedItemText#5e068047 num:string text:RichText = PageListOrderedItem;
-pageListOrderedItemBlocks#98dd8936 num:string blocks:Vector<PageBlock> = PageListOrderedItem;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
pageListOrderedItemTextOrdered list of text items
pageListOrderedItemBlocksOrdered list of IV blocks
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PageRelatedArticle.html b/data/corefork.telegram.org/type/PageRelatedArticle.html deleted file mode 100644 index 9843fccfed..0000000000 --- a/data/corefork.telegram.org/type/PageRelatedArticle.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PageRelatedArticle - - - - - - - - - - - - - -
- -
-
-
- -

PageRelatedArticle

- -

Related articles

-

- -
-
pageRelatedArticle#b390dc08 flags:# url:string webpage_id:long title:flags.0?string description:flags.1?string photo_id:flags.2?long author:flags.3?string published_date:flags.4?int = PageRelatedArticle;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
pageRelatedArticleRelated article
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PageTableCell.html b/data/corefork.telegram.org/type/PageTableCell.html deleted file mode 100644 index b2b6d294e8..0000000000 --- a/data/corefork.telegram.org/type/PageTableCell.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PageTableCell - - - - - - - - - - - - - -
- -
-
-
- -

PageTableCell

- -

Represents a table in an instant view table

-

- -
-
pageTableCell#34566b6a flags:# header:flags.0?true align_center:flags.3?true align_right:flags.4?true valign_middle:flags.5?true valign_bottom:flags.6?true text:flags.7?RichText colspan:flags.1?int rowspan:flags.2?int = PageTableCell;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
pageTableCellTable cell
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PageTableRow.html b/data/corefork.telegram.org/type/PageTableRow.html deleted file mode 100644 index 95d0bb3df8..0000000000 --- a/data/corefork.telegram.org/type/PageTableRow.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PageTableRow - - - - - - - - - - - - - -
- -
-
-
- -

PageTableRow

- -

Table row

-

- -
-
pageTableRow#e0c0c5e5 cells:Vector<PageTableCell> = PageTableRow;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
pageTableRowTable row
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PasswordKdfAlgo.html b/data/corefork.telegram.org/type/PasswordKdfAlgo.html deleted file mode 100644 index ba64843cfc..0000000000 --- a/data/corefork.telegram.org/type/PasswordKdfAlgo.html +++ /dev/null @@ -1,151 +0,0 @@ - - - - - PasswordKdfAlgo - - - - - - - - - - - - - -
- -
-
-
- -

PasswordKdfAlgo

- -

Key derivation function to use when generating the password hash for SRP two-factor authorization

-

- -
-
passwordKdfAlgoUnknown#d45ab096 = PasswordKdfAlgo;
-passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPow#3a912d4a salt1:bytes salt2:bytes g:int p:bytes = PasswordKdfAlgo;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
passwordKdfAlgoUnknownUnknown KDF (most likely, the client is outdated and does not support the specified KDF algorithm)
passwordKdfAlgoSHA256SHA256PBKDF2HMACSHA512iter100000SHA256ModPowThis key derivation algorithm defines that SRP 2FA login must be used
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PaymentCharge.html b/data/corefork.telegram.org/type/PaymentCharge.html deleted file mode 100644 index 7e4881a471..0000000000 --- a/data/corefork.telegram.org/type/PaymentCharge.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PaymentCharge - - - - - - - - - - - - - -
- -
-
-
- -

PaymentCharge

- -

Charged payment

-

- -
-
paymentCharge#ea02c27e id:string provider_charge_id:string = PaymentCharge;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
paymentChargePayment identifier
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PaymentRequestedInfo.html b/data/corefork.telegram.org/type/PaymentRequestedInfo.html deleted file mode 100644 index 61789d9e88..0000000000 --- a/data/corefork.telegram.org/type/PaymentRequestedInfo.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PaymentRequestedInfo - - - - - - - - - - - - - -
- -
-
-
- -

PaymentRequestedInfo

- -

Requested payment info

-

- -
-
paymentRequestedInfo#909c3f94 flags:# name:flags.0?string phone:flags.1?string email:flags.2?string shipping_address:flags.3?PostAddress = PaymentRequestedInfo;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
paymentRequestedInfoOrder info provided by the user
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PaymentSavedCredentials.html b/data/corefork.telegram.org/type/PaymentSavedCredentials.html deleted file mode 100644 index 0e7bb22a23..0000000000 --- a/data/corefork.telegram.org/type/PaymentSavedCredentials.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PaymentSavedCredentials - - - - - - - - - - - - - -
- -
-
-
- -

PaymentSavedCredentials

- -

Saved payment credentials

-

- -
-
paymentSavedCredentialsCard#cdc27a1f id:string title:string = PaymentSavedCredentials;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
paymentSavedCredentialsCardSaved credit card
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/Peer.html b/data/corefork.telegram.org/type/Peer.html deleted file mode 100644 index 06198d93cb..0000000000 --- a/data/corefork.telegram.org/type/Peer.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - Peer - - - - - - - - - - - - - -
- -
-
-
- -

Peer

- -

Chat partner or group.

-

- -
-
peerUser#59511722 user_id:long = Peer;
-peerChat#36c6019a chat_id:long = Peer;
-peerChannel#a2a5371e channel_id:long = Peer;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
peerUserChat partner
peerChatGroup.
peerChannelChannel/supergroup
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PeerBlocked.html b/data/corefork.telegram.org/type/PeerBlocked.html deleted file mode 100644 index 7c86a744e6..0000000000 --- a/data/corefork.telegram.org/type/PeerBlocked.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PeerBlocked - - - - - - - - - - - - - -
- -
-
-
- -

PeerBlocked

- -

Info about a blocked user

-

- -
-
peerBlocked#e8fd8014 peer_id:Peer date:int = PeerBlocked;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
peerBlockedInformation about a blocked peer
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PeerLocated.html b/data/corefork.telegram.org/type/PeerLocated.html deleted file mode 100644 index 7076db3bc1..0000000000 --- a/data/corefork.telegram.org/type/PeerLocated.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - PeerLocated - - - - - - - - - - - - - -
- -
-
-
- -

PeerLocated

- -

Geolocated peer

-

- -
-
peerLocated#ca461b5d peer:Peer expires:int distance:int = PeerLocated;
-peerSelfLocated#f8ec284b expires:int = PeerLocated;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
peerLocatedPeer geolocated nearby
peerSelfLocatedCurrent peer
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PeerNotifySettings.html b/data/corefork.telegram.org/type/PeerNotifySettings.html deleted file mode 100644 index c9b7226eb3..0000000000 --- a/data/corefork.telegram.org/type/PeerNotifySettings.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - PeerNotifySettings - - - - - - - - - - - - - -
- -
-
-
- -

PeerNotifySettings

- -

Notification settings.

-

- -
-
peerNotifySettings#af509d20 flags:# show_previews:flags.0?Bool silent:flags.1?Bool mute_until:flags.2?int sound:flags.3?string = PeerNotifySettings;
-
----functions---
-
-account.getNotifySettings#12b3ad31 peer:InputNotifyPeer = PeerNotifySettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
peerNotifySettingsNotification settings.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getNotifySettingsGets current notification settings for a given user/group, from all users/all groups.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PeerSettings.html b/data/corefork.telegram.org/type/PeerSettings.html deleted file mode 100644 index 1d85db9751..0000000000 --- a/data/corefork.telegram.org/type/PeerSettings.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - PeerSettings - - - - - - - - - - - - - -
- -
-
-
- -

PeerSettings

- -

Peer settings

-

- -
-
peerSettings#733f2961 flags:# report_spam:flags.0?true add_contact:flags.1?true block_contact:flags.2?true share_contact:flags.3?true need_contacts_exception:flags.4?true report_geo:flags.5?true autoarchived:flags.7?true invite_members:flags.8?true geo_distance:flags.6?int = PeerSettings;
-
----functions---
-
-messages.getPeerSettings#3672e09c peer:InputPeer = PeerSettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
peerSettingsPeer settings
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getPeerSettingsGet peer settings
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PhoneCall.html b/data/corefork.telegram.org/type/PhoneCall.html deleted file mode 100644 index 9d483e50f2..0000000000 --- a/data/corefork.telegram.org/type/PhoneCall.html +++ /dev/null @@ -1,168 +0,0 @@ - - - - - PhoneCall - - - - - - - - - - - - - -
- -
-
-
- -

PhoneCall

- -

Phone call

-

- -
-
phoneCallEmpty#5366c915 id:long = PhoneCall;
-phoneCallWaiting#c5226f17 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long protocol:PhoneCallProtocol receive_date:flags.0?int = PhoneCall;
-phoneCallRequested#14b0ed0c flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_hash:bytes protocol:PhoneCallProtocol = PhoneCall;
-phoneCallAccepted#3660c311 flags:# video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_b:bytes protocol:PhoneCallProtocol = PhoneCall;
-phoneCall#967f7c67 flags:# p2p_allowed:flags.5?true video:flags.6?true id:long access_hash:long date:int admin_id:long participant_id:long g_a_or_b:bytes key_fingerprint:long protocol:PhoneCallProtocol connections:Vector<PhoneConnection> start_date:int = PhoneCall;
-phoneCallDiscarded#50ca4de1 flags:# need_rating:flags.2?true need_debug:flags.3?true video:flags.6?true id:long reason:flags.0?PhoneCallDiscardReason duration:flags.1?int = PhoneCall;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
phoneCallEmptyEmpty constructor
phoneCallWaitingIncoming phone call
phoneCallRequestedRequested phone call
phoneCallAcceptedAn accepted phone call
phoneCallPhone call
phoneCallDiscardedIndicates a discarded phone call
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PhoneCallDiscardReason.html b/data/corefork.telegram.org/type/PhoneCallDiscardReason.html deleted file mode 100644 index 034761b742..0000000000 --- a/data/corefork.telegram.org/type/PhoneCallDiscardReason.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - - PhoneCallDiscardReason - - - - - - - - - - - - - -
- -
-
-
- -

PhoneCallDiscardReason

- -

Why was the phone call discarded?

-

- -
-
phoneCallDiscardReasonMissed#85e42301 = PhoneCallDiscardReason;
-phoneCallDiscardReasonDisconnect#e095c1a0 = PhoneCallDiscardReason;
-phoneCallDiscardReasonHangup#57adc690 = PhoneCallDiscardReason;
-phoneCallDiscardReasonBusy#faf7e8c9 = PhoneCallDiscardReason;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
phoneCallDiscardReasonMissedThe phone call was missed
phoneCallDiscardReasonDisconnectThe phone call was disconnected
phoneCallDiscardReasonHangupThe phone call was ended normally
phoneCallDiscardReasonBusyThe phone call was discared because the user is busy in another call
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PhoneCallProtocol.html b/data/corefork.telegram.org/type/PhoneCallProtocol.html deleted file mode 100644 index 3d43b57e65..0000000000 --- a/data/corefork.telegram.org/type/PhoneCallProtocol.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PhoneCallProtocol - - - - - - - - - - - - - -
- -
-
-
- -

PhoneCallProtocol

- -

Phone call protocol

-

- -
-
phoneCallProtocol#fc878fc8 flags:# udp_p2p:flags.0?true udp_reflector:flags.1?true min_layer:int max_layer:int library_versions:Vector<string> = PhoneCallProtocol;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
phoneCallProtocolProtocol info for libtgvoip
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PhotoSize.html b/data/corefork.telegram.org/type/PhotoSize.html deleted file mode 100644 index 257bf004b5..0000000000 --- a/data/corefork.telegram.org/type/PhotoSize.html +++ /dev/null @@ -1,168 +0,0 @@ - - - - - PhotoSize - - - - - - - - - - - - - -
- -
-
-
- -

PhotoSize

- -

Location of a certain size of a picture

-

- -
-
photoSizeEmpty#e17e23c type:string = PhotoSize;
-photoSize#75c78e60 type:string w:int h:int size:int = PhotoSize;
-photoCachedSize#21e1ad6 type:string w:int h:int bytes:bytes = PhotoSize;
-photoStrippedSize#e0b0bc2e type:string bytes:bytes = PhotoSize;
-photoSizeProgressive#fa3efb95 type:string w:int h:int sizes:Vector<int> = PhotoSize;
-photoPathSize#d8214d41 type:string bytes:bytes = PhotoSize;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
photoSizeEmptyEmpty constructor. Image with this thumbnail is unavailable.
photoSizeImage description.
photoCachedSizeDescription of an image and its content.
photoStrippedSizeJust the image's content
photoSizeProgressiveProgressively encoded photosize
photoPathSizeMessages with animated stickers can have a compressed svg (< 300 bytes) to show the outline of the sticker before fetching the actual lottie animation.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/Poll.html b/data/corefork.telegram.org/type/Poll.html deleted file mode 100644 index 522a444abc..0000000000 --- a/data/corefork.telegram.org/type/Poll.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - Poll - - - - - - - - - - - - - -
- -
-
-
- -

Poll

- -

Indicates a poll message

-

- -
-
poll#86e18161 id:long flags:# closed:flags.0?true public_voters:flags.1?true multiple_choice:flags.2?true quiz:flags.3?true question:string answers:Vector<PollAnswer> close_period:flags.4?int close_date:flags.5?int = Poll;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
pollPoll
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PollAnswer.html b/data/corefork.telegram.org/type/PollAnswer.html deleted file mode 100644 index 74be44f614..0000000000 --- a/data/corefork.telegram.org/type/PollAnswer.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - PollAnswer - - - - - - - - - - - - - -
- -
-
-
- -

PollAnswer

- -

Indicates a possible answer to a poll.

-

- -
-
pollAnswer#6ca9c2e9 text:string option:bytes = PollAnswer;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
pollAnswerA possible answer of a poll
-

Related pages

-

Poll

-

Indicates a poll message

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PollAnswerVoters.html b/data/corefork.telegram.org/type/PollAnswerVoters.html deleted file mode 100644 index 0d7a391984..0000000000 --- a/data/corefork.telegram.org/type/PollAnswerVoters.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PollAnswerVoters - - - - - - - - - - - - - -
- -
-
-
- -

PollAnswerVoters

- -

How users voted on a certain poll answer

-

- -
-
pollAnswerVoters#3b6ddad2 flags:# chosen:flags.0?true correct:flags.1?true option:bytes voters:int = PollAnswerVoters;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
pollAnswerVotersA poll answer, and how users voted on it
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PollResults.html b/data/corefork.telegram.org/type/PollResults.html deleted file mode 100644 index e0b949cb69..0000000000 --- a/data/corefork.telegram.org/type/PollResults.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PollResults - - - - - - - - - - - - - -
- -
-
-
- -

PollResults

- -

Results of poll

-

- -
-
pollResults#dcb82ea3 flags:# min:flags.0?true results:flags.1?Vector<PollAnswerVoters> total_voters:flags.2?int recent_voters:flags.3?Vector<long> solution:flags.4?string solution_entities:flags.4?Vector<MessageEntity> = PollResults;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
pollResultsResults of poll
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PopularContact.html b/data/corefork.telegram.org/type/PopularContact.html deleted file mode 100644 index a9de19106b..0000000000 --- a/data/corefork.telegram.org/type/PopularContact.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PopularContact - - - - - - - - - - - - - -
- -
-
-
- -

PopularContact

- -

Popular contact

-

- -
-
popularContact#5ce14175 client_id:long importers:int = PopularContact;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
popularContactPopular contact
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PostAddress.html b/data/corefork.telegram.org/type/PostAddress.html deleted file mode 100644 index acf5d060ec..0000000000 --- a/data/corefork.telegram.org/type/PostAddress.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - PostAddress - - - - - - - - - - - - - -
- -
-
-
- -

PostAddress

- -

Shipping address

-

- -
-
postAddress#1e8caaeb street_line1:string street_line2:string city:string state:string country_iso2:string post_code:string = PostAddress;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
postAddressShipping address
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PrivacyKey.html b/data/corefork.telegram.org/type/PrivacyKey.html deleted file mode 100644 index 3018f23384..0000000000 --- a/data/corefork.telegram.org/type/PrivacyKey.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - PrivacyKey - - - - - - - - - - - - - -
- -
-
-
- -

PrivacyKey

- -

Privacy key

-

- -
-
privacyKeyStatusTimestamp#bc2eab30 = PrivacyKey;
-privacyKeyChatInvite#500e6dfa = PrivacyKey;
-privacyKeyPhoneCall#3d662b7b = PrivacyKey;
-privacyKeyPhoneP2P#39491cc8 = PrivacyKey;
-privacyKeyForwards#69ec56a3 = PrivacyKey;
-privacyKeyProfilePhoto#96151fed = PrivacyKey;
-privacyKeyPhoneNumber#d19ae46d = PrivacyKey;
-privacyKeyAddedByPhone#42ffd42b = PrivacyKey;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
privacyKeyStatusTimestampWhether we can see the last online timestamp
privacyKeyChatInviteWhether the user can be invited to chats
privacyKeyPhoneCallWhether the user accepts phone calls
privacyKeyPhoneP2PWhether P2P connections in phone calls are allowed
privacyKeyForwardsWhether messages forwarded from the user will be anonymously forwarded
privacyKeyProfilePhotoWhether the profile picture of the user is visible
privacyKeyPhoneNumberWhether the user allows us to see his phone number
privacyKeyAddedByPhoneWhether people can add you to their contact list by your phone number
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/PrivacyRule.html b/data/corefork.telegram.org/type/PrivacyRule.html deleted file mode 100644 index 6be41cf15e..0000000000 --- a/data/corefork.telegram.org/type/PrivacyRule.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - PrivacyRule - - - - - - - - - - - - - -
- -
-
-
- -

PrivacyRule

- -

Privacy rule

-

- -
-
privacyValueAllowContacts#fffe1bac = PrivacyRule;
-privacyValueAllowAll#65427b82 = PrivacyRule;
-privacyValueAllowUsers#b8905fb2 users:Vector<long> = PrivacyRule;
-privacyValueDisallowContacts#f888fa1a = PrivacyRule;
-privacyValueDisallowAll#8b73e763 = PrivacyRule;
-privacyValueDisallowUsers#e4621141 users:Vector<long> = PrivacyRule;
-privacyValueAllowChatParticipants#6b134e8e chats:Vector<long> = PrivacyRule;
-privacyValueDisallowChatParticipants#41c87565 chats:Vector<long> = PrivacyRule;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
privacyValueAllowContactsAllow all contacts
privacyValueAllowAllAllow all users
privacyValueAllowUsersAllow only certain users
privacyValueDisallowContactsDisallow only contacts
privacyValueDisallowAllDisallow all users
privacyValueDisallowUsersDisallow only certain users
privacyValueAllowChatParticipantsAllow all participants of certain chats
privacyValueDisallowChatParticipantsDisallow only participants of certain chats
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ReceivedNotifyMessage.html b/data/corefork.telegram.org/type/ReceivedNotifyMessage.html deleted file mode 100644 index 83eae56879..0000000000 --- a/data/corefork.telegram.org/type/ReceivedNotifyMessage.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - ReceivedNotifyMessage - - - - - - - - - - - - - -
- -
-
-
- -

ReceivedNotifyMessage

- -

Confirmation of message receipt

-

- -
-
receivedNotifyMessage#a384b779 id:int flags:int = ReceivedNotifyMessage;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
receivedNotifyMessageMessage ID, for which PUSH-notifications were cancelled.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/RecentMeUrl.html b/data/corefork.telegram.org/type/RecentMeUrl.html deleted file mode 100644 index d9bcb3d2a3..0000000000 --- a/data/corefork.telegram.org/type/RecentMeUrl.html +++ /dev/null @@ -1,163 +0,0 @@ - - - - - RecentMeUrl - - - - - - - - - - - - - -
- -
-
-
- -

RecentMeUrl

- -

Recent t.me urls

-

- -
-
recentMeUrlUnknown#46e1d13d url:string = RecentMeUrl;
-recentMeUrlUser#b92c09e2 url:string user_id:long = RecentMeUrl;
-recentMeUrlChat#b2da71d2 url:string chat_id:long = RecentMeUrl;
-recentMeUrlChatInvite#eb49081d url:string chat_invite:ChatInvite = RecentMeUrl;
-recentMeUrlStickerSet#bc0a57dc url:string set:StickerSetCovered = RecentMeUrl;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
recentMeUrlUnknownUnknown t.me url
recentMeUrlUserRecent t.me link to a user
recentMeUrlChatRecent t.me link to a chat
recentMeUrlChatInviteRecent t.me invite link to a chat
recentMeUrlStickerSetRecent t.me stickerset installation URL
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ReplyMarkup.html b/data/corefork.telegram.org/type/ReplyMarkup.html deleted file mode 100644 index 61427870e1..0000000000 --- a/data/corefork.telegram.org/type/ReplyMarkup.html +++ /dev/null @@ -1,158 +0,0 @@ - - - - - ReplyMarkup - - - - - - - - - - - - - -
- -
-
-
- -

ReplyMarkup

- -

Reply markup for bot and inline keyboards

-

- -
-
replyKeyboardHide#a03e5b85 flags:# selective:flags.2?true = ReplyMarkup;
-replyKeyboardForceReply#86b40b08 flags:# single_use:flags.1?true selective:flags.2?true placeholder:flags.3?string = ReplyMarkup;
-replyKeyboardMarkup#85dd99d1 flags:# resize:flags.0?true single_use:flags.1?true selective:flags.2?true rows:Vector<KeyboardButtonRow> placeholder:flags.3?string = ReplyMarkup;
-replyInlineMarkup#48a30254 rows:Vector<KeyboardButtonRow> = ReplyMarkup;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
replyKeyboardHideHide sent bot keyboard
replyKeyboardForceReplyForce the user to send a reply
replyKeyboardMarkupBot keyboard
replyInlineMarkupBot or inline keyboard
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ReportReason.html b/data/corefork.telegram.org/type/ReportReason.html deleted file mode 100644 index 4145658489..0000000000 --- a/data/corefork.telegram.org/type/ReportReason.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - ReportReason - - - - - - - - - - - - - -
- -
-
-
- -

ReportReason

- -

Report reason

-

- -
-
inputReportReasonSpam#58dbcab8 = ReportReason;
-inputReportReasonViolence#1e22c78d = ReportReason;
-inputReportReasonPornography#2e59d922 = ReportReason;
-inputReportReasonChildAbuse#adf44ee3 = ReportReason;
-inputReportReasonOther#c1e4a2b1 = ReportReason;
-inputReportReasonCopyright#9b89f93a = ReportReason;
-inputReportReasonGeoIrrelevant#dbd4feed = ReportReason;
-inputReportReasonFake#f5ddd6e7 = ReportReason;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
inputReportReasonSpamReport for spam
inputReportReasonViolenceReport for violence
inputReportReasonPornographyReport for pornography
inputReportReasonChildAbuseReport for child abuse
inputReportReasonOtherOther
inputReportReasonCopyrightReport for copyrighted content
inputReportReasonGeoIrrelevantReport an irrelevant geogroup
inputReportReasonFakeReport for impersonation
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/RestrictionReason.html b/data/corefork.telegram.org/type/RestrictionReason.html deleted file mode 100644 index 3ffe864b2b..0000000000 --- a/data/corefork.telegram.org/type/RestrictionReason.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - RestrictionReason - - - - - - - - - - - - - -
- -
-
-
- -

RestrictionReason

- -

Restriction reason

-

- -
-
restrictionReason#d072acb4 platform:string reason:string text:string = RestrictionReason;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
restrictionReasonRestriction reason
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/RichText.html b/data/corefork.telegram.org/type/RichText.html deleted file mode 100644 index 209db9a1da..0000000000 --- a/data/corefork.telegram.org/type/RichText.html +++ /dev/null @@ -1,218 +0,0 @@ - - - - - RichText - - - - - - - - - - - - - -
- -
-
-
- -

RichText

- -

Rich text

-

- -
-
textEmpty#dc3d824f = RichText;
-textPlain#744694e0 text:string = RichText;
-textBold#6724abc4 text:RichText = RichText;
-textItalic#d912a59c text:RichText = RichText;
-textUnderline#c12622c4 text:RichText = RichText;
-textStrike#9bf8bb95 text:RichText = RichText;
-textFixed#6c3f19b9 text:RichText = RichText;
-textUrl#3c2884c1 text:RichText url:string webpage_id:long = RichText;
-textEmail#de5a0dd6 text:RichText email:string = RichText;
-textConcat#7e6260d7 texts:Vector<RichText> = RichText;
-textSubscript#ed6a8504 text:RichText = RichText;
-textSuperscript#c7fb5e01 text:RichText = RichText;
-textMarked#34b8621 text:RichText = RichText;
-textPhone#1ccb966a text:RichText phone:string = RichText;
-textImage#81ccf4f document_id:long w:int h:int = RichText;
-textAnchor#35553762 text:RichText name:string = RichText;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
textEmptyEmpty rich text element
textPlainPlain text
textBoldBold text
textItalicItalic text
textUnderlineUnderlined text
textStrikeStrikethrough text
textFixedfixed-width rich text
textUrlLink
textEmailRich text email link
textConcatConcatenation of rich texts
textSubscriptSubscript text
textSuperscriptSuperscript text
textMarkedHighlighted text
textPhoneRich text linked to a phone number
textImageInline image
textAnchorText linking to another section of the page
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/SavedContact.html b/data/corefork.telegram.org/type/SavedContact.html deleted file mode 100644 index 9307197285..0000000000 --- a/data/corefork.telegram.org/type/SavedContact.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - SavedContact - - - - - - - - - - - - - -
- -
-
-
- -

SavedContact

- -

Saved contact

-

- -
-
savedPhoneContact#1142bd56 phone:string first_name:string last_name:string date:int = SavedContact;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
savedPhoneContactSaved contact
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/SecureCredentialsEncrypted.html b/data/corefork.telegram.org/type/SecureCredentialsEncrypted.html deleted file mode 100644 index b8a5c10950..0000000000 --- a/data/corefork.telegram.org/type/SecureCredentialsEncrypted.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - SecureCredentialsEncrypted - - - - - - - - - - - - - -
- -
-
-
- -

SecureCredentialsEncrypted

- -

Encrypted secure credentials

-

- -
-
secureCredentialsEncrypted#33f0ea47 data:bytes hash:bytes secret:bytes = SecureCredentialsEncrypted;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
secureCredentialsEncryptedEncrypted credentials required to decrypt telegram passport data.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/SecureData.html b/data/corefork.telegram.org/type/SecureData.html deleted file mode 100644 index 56f6cebe55..0000000000 --- a/data/corefork.telegram.org/type/SecureData.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - SecureData - - - - - - - - - - - - - -
- -
-
-
- -

SecureData

- -

Secure passport data, for more info see the passport docs »

-

- -
-
secureData#8aeabec3 data:bytes data_hash:bytes secret:bytes = SecureData;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
secureDataSecure data
-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/SecureFile.html b/data/corefork.telegram.org/type/SecureFile.html deleted file mode 100644 index c156384c43..0000000000 --- a/data/corefork.telegram.org/type/SecureFile.html +++ /dev/null @@ -1,151 +0,0 @@ - - - - - SecureFile - - - - - - - - - - - - - -
- -
-
-
- -

SecureFile

- -

Secure passport file, for more info see the passport docs »

-

- -
-
secureFileEmpty#64199744 = SecureFile;
-secureFile#e0277a62 id:long access_hash:long size:int dc_id:int date:int file_hash:bytes secret:bytes = SecureFile;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
secureFileEmptyEmpty constructor
secureFileSecure file
-

Related pages

-

Telegram Passport Manual

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/SecurePasswordKdfAlgo.html b/data/corefork.telegram.org/type/SecurePasswordKdfAlgo.html deleted file mode 100644 index a5317617b8..0000000000 --- a/data/corefork.telegram.org/type/SecurePasswordKdfAlgo.html +++ /dev/null @@ -1,155 +0,0 @@ - - - - - SecurePasswordKdfAlgo - - - - - - - - - - - - - -
- -
-
-
- -

SecurePasswordKdfAlgo

- -

KDF algorithm to use for computing telegram passport hash

-

- -
-
securePasswordKdfAlgoUnknown#4a8537 = SecurePasswordKdfAlgo;
-securePasswordKdfAlgoPBKDF2HMACSHA512iter100000#bbf2dda0 salt:bytes = SecurePasswordKdfAlgo;
-securePasswordKdfAlgoSHA512#86471d92 salt:bytes = SecurePasswordKdfAlgo;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
securePasswordKdfAlgoUnknownUnknown KDF algo (most likely the client has to be updated)
securePasswordKdfAlgoPBKDF2HMACSHA512iter100000PBKDF2 with SHA512 and 100000 iterations KDF algo
securePasswordKdfAlgoSHA512SHA512 KDF algo
-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/SecurePlainData.html b/data/corefork.telegram.org/type/SecurePlainData.html deleted file mode 100644 index f2b6b5295e..0000000000 --- a/data/corefork.telegram.org/type/SecurePlainData.html +++ /dev/null @@ -1,150 +0,0 @@ - - - - - SecurePlainData - - - - - - - - - - - - - -
- -
-
-
- -

SecurePlainData

- -

Plaintext verified passport data.

-

- -
-
securePlainPhone#7d6099dd phone:string = SecurePlainData;
-securePlainEmail#21ec5a5f email:string = SecurePlainData;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
securePlainPhonePhone number to use in telegram passport: it must be verified, first ».
securePlainEmailEmail address to use in telegram passport: it must be verified, first ».
-

Related pages

-

Telegram Passport Encryption Details

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/SecureRequiredType.html b/data/corefork.telegram.org/type/SecureRequiredType.html deleted file mode 100644 index af856c1f86..0000000000 --- a/data/corefork.telegram.org/type/SecureRequiredType.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - SecureRequiredType - - - - - - - - - - - - - -
- -
-
-
- -

SecureRequiredType

- -

Required secure file type

-

- -
-
secureRequiredType#829d99da flags:# native_names:flags.0?true selfie_required:flags.1?true translation_required:flags.2?true type:SecureValueType = SecureRequiredType;
-secureRequiredTypeOneOf#27477b4 types:Vector<SecureRequiredType> = SecureRequiredType;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
secureRequiredTypeRequired type
secureRequiredTypeOneOfOne of
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/SecureSecretSettings.html b/data/corefork.telegram.org/type/SecureSecretSettings.html deleted file mode 100644 index 4ddb813973..0000000000 --- a/data/corefork.telegram.org/type/SecureSecretSettings.html +++ /dev/null @@ -1,145 +0,0 @@ - - - - - SecureSecretSettings - - - - - - - - - - - - - -
- -
-
-
- -

SecureSecretSettings

- -

Telegram passport settings

-

- -
-
secureSecretSettings#1527bcac secure_algo:SecurePasswordKdfAlgo secure_secret:bytes secure_secret_id:long = SecureSecretSettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
secureSecretSettingsSecure settings
-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/SecureValue.html b/data/corefork.telegram.org/type/SecureValue.html deleted file mode 100644 index 7c97d8396c..0000000000 --- a/data/corefork.telegram.org/type/SecureValue.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - SecureValue - - - - - - - - - - - - - -
- -
-
-
- -

SecureValue

- -

Secure tgpassport value

-

- -
-
secureValue#187fa0ca flags:# type:SecureValueType data:flags.0?SecureData front_side:flags.1?SecureFile reverse_side:flags.2?SecureFile selfie:flags.3?SecureFile translation:flags.6?Vector<SecureFile> files:flags.4?Vector<SecureFile> plain_data:flags.5?SecurePlainData hash:bytes = SecureValue;
-
----functions---
-
-account.saveSecureValue#899fe31d value:InputSecureValue secure_secret_id:long = SecureValue;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
secureValueSecure value
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.saveSecureValueSave secure passport value
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/SecureValueError.html b/data/corefork.telegram.org/type/SecureValueError.html deleted file mode 100644 index 2086acf9e8..0000000000 --- a/data/corefork.telegram.org/type/SecureValueError.html +++ /dev/null @@ -1,183 +0,0 @@ - - - - - SecureValueError - - - - - - - - - - - - - -
- -
-
-
- -

SecureValueError

- -

Secure value error

-

- -
-
secureValueErrorData#e8a40bd9 type:SecureValueType data_hash:bytes field:string text:string = SecureValueError;
-secureValueErrorFrontSide#be3dfa type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorReverseSide#868a2aa5 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorSelfie#e537ced6 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorFile#7a700873 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorFiles#666220e9 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;
-secureValueError#869d758f type:SecureValueType hash:bytes text:string = SecureValueError;
-secureValueErrorTranslationFile#a1144770 type:SecureValueType file_hash:bytes text:string = SecureValueError;
-secureValueErrorTranslationFiles#34636dd8 type:SecureValueType file_hash:Vector<bytes> text:string = SecureValueError;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
secureValueErrorDataSecure value error
secureValueErrorFrontSideSecure value error front side
secureValueErrorReverseSideReverse side error
secureValueErrorSelfieSecure value error: invalid selfie
secureValueErrorFileSecure value error file
secureValueErrorFilesSecure value error files
secureValueErrorSecure value error
secureValueErrorTranslationFileTranslation missing
secureValueErrorTranslationFilesTranslation file error
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/SecureValueHash.html b/data/corefork.telegram.org/type/SecureValueHash.html deleted file mode 100644 index 2ded52d18e..0000000000 --- a/data/corefork.telegram.org/type/SecureValueHash.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - SecureValueHash - - - - - - - - - - - - - -
- -
-
-
- -

SecureValueHash

- -

Secure value hash

-

- -
-
secureValueHash#ed1ecdb0 type:SecureValueType hash:bytes = SecureValueHash;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
secureValueHashSecure value hash
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/SecureValueType.html b/data/corefork.telegram.org/type/SecureValueType.html deleted file mode 100644 index ffdd92d03c..0000000000 --- a/data/corefork.telegram.org/type/SecureValueType.html +++ /dev/null @@ -1,203 +0,0 @@ - - - - - SecureValueType - - - - - - - - - - - - - -
- -
-
-
- -

SecureValueType

- -

Secure value type

-

- -
-
secureValueTypePersonalDetails#9d2a81e3 = SecureValueType;
-secureValueTypePassport#3dac6a00 = SecureValueType;
-secureValueTypeDriverLicense#6e425c4 = SecureValueType;
-secureValueTypeIdentityCard#a0d0744b = SecureValueType;
-secureValueTypeInternalPassport#99a48f23 = SecureValueType;
-secureValueTypeAddress#cbe31e26 = SecureValueType;
-secureValueTypeUtilityBill#fc36954e = SecureValueType;
-secureValueTypeBankStatement#89137c0d = SecureValueType;
-secureValueTypeRentalAgreement#8b883488 = SecureValueType;
-secureValueTypePassportRegistration#99e3806a = SecureValueType;
-secureValueTypeTemporaryRegistration#ea02ec33 = SecureValueType;
-secureValueTypePhone#b320aadb = SecureValueType;
-secureValueTypeEmail#8e3ca7ee = SecureValueType;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
secureValueTypePersonalDetailsPersonal details
secureValueTypePassportPassport
secureValueTypeDriverLicenseDriver's license
secureValueTypeIdentityCardIdentity card
secureValueTypeInternalPassportInternal passport
secureValueTypeAddressAddress
secureValueTypeUtilityBillUtility bill
secureValueTypeBankStatementBank statement
secureValueTypeRentalAgreementRental agreement
secureValueTypePassportRegistrationInternal registration passport
secureValueTypeTemporaryRegistrationTemporary registration
secureValueTypePhonePhone
secureValueTypeEmailEmail
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/SendMessageAction.html b/data/corefork.telegram.org/type/SendMessageAction.html deleted file mode 100644 index 624193d47a..0000000000 --- a/data/corefork.telegram.org/type/SendMessageAction.html +++ /dev/null @@ -1,228 +0,0 @@ - - - - - SendMessageAction - - - - - - - - - - - - - -
- -
-
-
- -

SendMessageAction

- -

User actions. Use this to provide users with detailed info about their chat partners' actions: typing or sending attachments of all kinds.

-

- -
-
sendMessageTypingAction#16bf744e = SendMessageAction;
-sendMessageCancelAction#fd5ec8f5 = SendMessageAction;
-sendMessageRecordVideoAction#a187d66f = SendMessageAction;
-sendMessageUploadVideoAction#e9763aec progress:int = SendMessageAction;
-sendMessageRecordAudioAction#d52f73f7 = SendMessageAction;
-sendMessageUploadAudioAction#f351d7ab progress:int = SendMessageAction;
-sendMessageUploadPhotoAction#d1d34a26 progress:int = SendMessageAction;
-sendMessageUploadDocumentAction#aa0cd9e4 progress:int = SendMessageAction;
-sendMessageGeoLocationAction#176f8ba1 = SendMessageAction;
-sendMessageChooseContactAction#628cbc6f = SendMessageAction;
-sendMessageGamePlayAction#dd6a8f48 = SendMessageAction;
-sendMessageRecordRoundAction#88f27fbc = SendMessageAction;
-sendMessageUploadRoundAction#243e1c66 progress:int = SendMessageAction;
-speakingInGroupCallAction#d92c2285 = SendMessageAction;
-sendMessageHistoryImportAction#dbda9246 progress:int = SendMessageAction;
-sendMessageChooseStickerAction#b05ac6b1 = SendMessageAction;
-sendMessageEmojiInteraction#25972bcb emoticon:string msg_id:int interaction:DataJSON = SendMessageAction;
-sendMessageEmojiInteractionSeen#b665902e emoticon:string = SendMessageAction;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
sendMessageTypingActionUser is typing.
sendMessageCancelActionInvalidate all previous action updates. E.g. when user deletes entered text or aborts a video upload.
sendMessageRecordVideoActionUser is recording a video.
sendMessageUploadVideoActionUser is uploading a video.
sendMessageRecordAudioActionUser is recording a voice message.
sendMessageUploadAudioActionUser is uploading a voice message.
sendMessageUploadPhotoActionUser is uploading a photo.
sendMessageUploadDocumentActionUser is uploading a file.
sendMessageGeoLocationActionUser is selecting a location to share.
sendMessageChooseContactActionUser is selecting a contact to share.
sendMessageGamePlayActionUser is playing a game
sendMessageRecordRoundActionUser is recording a round video to share
sendMessageUploadRoundActionUser is uploading a round video
speakingInGroupCallActionUser is currently speaking in the group call
sendMessageHistoryImportActionChat history is being imported
sendMessageChooseStickerActionUser is choosing a sticker
sendMessageEmojiInteractionUser has clicked on an animated emoji, triggering a reaction
sendMessageEmojiInteractionSeenUser has seen the reaction generated by another user
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ShippingOption.html b/data/corefork.telegram.org/type/ShippingOption.html deleted file mode 100644 index d237631c82..0000000000 --- a/data/corefork.telegram.org/type/ShippingOption.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - ShippingOption - - - - - - - - - - - - - -
- -
-
-
- -

ShippingOption

- -

Shipping options

-

- -
-
shippingOption#b6213cdf id:string title:string prices:Vector<LabeledPrice> = ShippingOption;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
shippingOptionShipping option
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/SponsoredMessage.html b/data/corefork.telegram.org/type/SponsoredMessage.html deleted file mode 100644 index d6d77d117e..0000000000 --- a/data/corefork.telegram.org/type/SponsoredMessage.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - SponsoredMessage - - - - - - - - - - - - - -
- -
-
-
- -

SponsoredMessage

- -

A sponsored message

-

- -
-
sponsoredMessage#2a3c381f flags:# random_id:bytes from_id:Peer start_param:flags.0?string message:string entities:flags.1?Vector<MessageEntity> = SponsoredMessage;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
sponsoredMessageA sponsored message
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/StatsAbsValueAndPrev.html b/data/corefork.telegram.org/type/StatsAbsValueAndPrev.html deleted file mode 100644 index d4a22239c4..0000000000 --- a/data/corefork.telegram.org/type/StatsAbsValueAndPrev.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - StatsAbsValueAndPrev - - - - - - - - - - - - - -
- -
-
-
- -

StatsAbsValueAndPrev

- -

Channel statistics value pair

-

- -
-
statsAbsValueAndPrev#cb43acde current:double previous:double = StatsAbsValueAndPrev;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
statsAbsValueAndPrevStatistics value couple; initial and final value for period of time currently in consideration
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/StatsDateRangeDays.html b/data/corefork.telegram.org/type/StatsDateRangeDays.html deleted file mode 100644 index b669d1bc97..0000000000 --- a/data/corefork.telegram.org/type/StatsDateRangeDays.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - StatsDateRangeDays - - - - - - - - - - - - - -
- -
-
-
- -

StatsDateRangeDays

- -

Channel statistics date range

-

- -
-
statsDateRangeDays#b637edaf min_date:int max_date:int = StatsDateRangeDays;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
statsDateRangeDaysChannel statistics date range
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/StatsGroupTopAdmin.html b/data/corefork.telegram.org/type/StatsGroupTopAdmin.html deleted file mode 100644 index f2dd656ba9..0000000000 --- a/data/corefork.telegram.org/type/StatsGroupTopAdmin.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - StatsGroupTopAdmin - - - - - - - - - - - - - -
- -
-
-
- -

StatsGroupTopAdmin

- -

Most active admin in a supergroup

-

- -
-
statsGroupTopAdmin#d7584c87 user_id:long deleted:int kicked:int banned:int = StatsGroupTopAdmin;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
statsGroupTopAdminInformation about an active admin in a supergroup
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/StatsGroupTopInviter.html b/data/corefork.telegram.org/type/StatsGroupTopInviter.html deleted file mode 100644 index 3be9fadb31..0000000000 --- a/data/corefork.telegram.org/type/StatsGroupTopInviter.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - StatsGroupTopInviter - - - - - - - - - - - - - -
- -
-
-
- -

StatsGroupTopInviter

- -

Most active inviter in a supergroup

-

- -
-
statsGroupTopInviter#535f779d user_id:long invitations:int = StatsGroupTopInviter;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
statsGroupTopInviterInformation about an active supergroup inviter
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/StatsGroupTopPoster.html b/data/corefork.telegram.org/type/StatsGroupTopPoster.html deleted file mode 100644 index 1233fa77a8..0000000000 --- a/data/corefork.telegram.org/type/StatsGroupTopPoster.html +++ /dev/null @@ -1,146 +0,0 @@ - - - - - StatsGroupTopPoster - - - - - - - - - - - - - -
- -
-
-
- -

StatsGroupTopPoster

- -

Most active user in a supergroup

-

- -
-
statsGroupTopPoster#9d04af9b user_id:long messages:int avg_chars:int = StatsGroupTopPoster;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
statsGroupTopPosterInformation about an active user in a supergroup
-

Related pages

-

Channels

-

How to handle channels, supergroups, groups, and what's the difference between them.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/StatsPercentValue.html b/data/corefork.telegram.org/type/StatsPercentValue.html deleted file mode 100644 index 9b339aad8e..0000000000 --- a/data/corefork.telegram.org/type/StatsPercentValue.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - StatsPercentValue - - - - - - - - - - - - - -
- -
-
-
- -

StatsPercentValue

- -

Channel statistics percentage

-

- -
-
statsPercentValue#cbce2fe0 part:double total:double = StatsPercentValue;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
statsPercentValueChannel statistics percentage
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/StatsURL.html b/data/corefork.telegram.org/type/StatsURL.html deleted file mode 100644 index a0e0d571d0..0000000000 --- a/data/corefork.telegram.org/type/StatsURL.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - StatsURL - - - - - - - - - - - - - -
- -
-
-
- -

StatsURL

- -

URL with chat statistics

-

- -
-
statsURL#47a971e0 url:string = StatsURL;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
statsURLURL with chat statistics
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/StickerPack.html b/data/corefork.telegram.org/type/StickerPack.html deleted file mode 100644 index 3fa22e718b..0000000000 --- a/data/corefork.telegram.org/type/StickerPack.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - StickerPack - - - - - - - - - - - - - -
- -
-
-
- -

StickerPack

- -

Stickerpack

-

- -
-
stickerPack#12b299d4 emoticon:string documents:Vector<long> = StickerPack;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
stickerPackA stickerpack is a group of stickers associated to the same emoji.
It is not a sticker pack the way it is usually intended, you may be looking for a StickerSet.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/StickerSet.html b/data/corefork.telegram.org/type/StickerSet.html deleted file mode 100644 index 757d39728b..0000000000 --- a/data/corefork.telegram.org/type/StickerSet.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - StickerSet - - - - - - - - - - - - - -
- -
-
-
- -

StickerSet

- -

Represents a stickerset (stickerpack)

-

- -
-
stickerSet#d7df217a flags:# archived:flags.1?true official:flags.2?true masks:flags.3?true animated:flags.5?true videos:flags.6?true installed_date:flags.0?int id:long access_hash:long title:string short_name:string thumbs:flags.4?Vector<PhotoSize> thumb_dc_id:flags.4?int thumb_version:flags.4?int count:int hash:int = StickerSet;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
stickerSetRepresents a stickerset (stickerpack)
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/StickerSetCovered.html b/data/corefork.telegram.org/type/StickerSetCovered.html deleted file mode 100644 index 646498a3f5..0000000000 --- a/data/corefork.telegram.org/type/StickerSetCovered.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - StickerSetCovered - - - - - - - - - - - - - -
- -
-
-
- -

StickerSetCovered

- -

Stickerset, with a specific sticker as preview

-

- -
-
stickerSetCovered#6410a5d2 set:StickerSet cover:Document = StickerSetCovered;
-stickerSetMultiCovered#3407e51b set:StickerSet covers:Vector<Document> = StickerSetCovered;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
stickerSetCoveredStickerset, with a specific sticker as preview
stickerSetMultiCoveredStickerset, with a specific stickers as preview
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/Theme.html b/data/corefork.telegram.org/type/Theme.html deleted file mode 100644 index 7e6d543c7f..0000000000 --- a/data/corefork.telegram.org/type/Theme.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - Theme - - - - - - - - - - - - - -
- -
-
-
- -

Theme

- -

Cloud theme

-

- -
-
theme#e802b8dc flags:# creator:flags.0?true default:flags.1?true for_chat:flags.5?true id:long access_hash:long slug:string title:string document:flags.2?Document settings:flags.3?ThemeSettings installs_count:flags.4?int = Theme;
-
----functions---
-
-account.createTheme#8432c21f flags:# slug:string title:string document:flags.2?InputDocument settings:flags.3?InputThemeSettings = Theme;
-account.updateTheme#5cb367d5 flags:# format:string theme:InputTheme slug:flags.0?string title:flags.1?string document:flags.2?InputDocument settings:flags.3?InputThemeSettings = Theme;
-account.getTheme#8d9d742b format:string theme:InputTheme document_id:long = Theme;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
themeTheme
-

Methods

- - - - - - - - - - - - - - - - - - - - - -
MethodDescription
account.createThemeCreate a theme
account.updateThemeUpdate theme
account.getThemeGet theme information
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ThemeSettings.html b/data/corefork.telegram.org/type/ThemeSettings.html deleted file mode 100644 index 4eb8f529e2..0000000000 --- a/data/corefork.telegram.org/type/ThemeSettings.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - ThemeSettings - - - - - - - - - - - - - -
- -
-
-
- -

ThemeSettings

- -

Theme settings

-

- -
-
themeSettings#fa58b6d4 flags:# message_colors_animated:flags.2?true base_theme:BaseTheme accent_color:int outbox_accent_color:flags.3?int message_colors:flags.0?Vector<int> wallpaper:flags.1?WallPaper = ThemeSettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
themeSettingsTheme settings
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/TopPeer.html b/data/corefork.telegram.org/type/TopPeer.html deleted file mode 100644 index b6d7802c8f..0000000000 --- a/data/corefork.telegram.org/type/TopPeer.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - TopPeer - - - - - - - - - - - - - -
- -
-
-
- -

TopPeer

- -

Top peer

-

- -
-
topPeer#edcdc05b peer:Peer rating:double = TopPeer;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
topPeerTop peer
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/TopPeerCategory.html b/data/corefork.telegram.org/type/TopPeerCategory.html deleted file mode 100644 index f55654cd57..0000000000 --- a/data/corefork.telegram.org/type/TopPeerCategory.html +++ /dev/null @@ -1,178 +0,0 @@ - - - - - TopPeerCategory - - - - - - - - - - - - - -
- -
-
-
- -

TopPeerCategory

- -

Top peer category

-

- -
-
topPeerCategoryBotsPM#ab661b5b = TopPeerCategory;
-topPeerCategoryBotsInline#148677e2 = TopPeerCategory;
-topPeerCategoryCorrespondents#637b7ed = TopPeerCategory;
-topPeerCategoryGroups#bd17a14a = TopPeerCategory;
-topPeerCategoryChannels#161d9628 = TopPeerCategory;
-topPeerCategoryPhoneCalls#1e76a78c = TopPeerCategory;
-topPeerCategoryForwardUsers#a8406ca9 = TopPeerCategory;
-topPeerCategoryForwardChats#fbeec0f0 = TopPeerCategory;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
topPeerCategoryBotsPMMost used bots
topPeerCategoryBotsInlineMost used inline bots
topPeerCategoryCorrespondentsUsers we've chatted most frequently with
topPeerCategoryGroupsOften-opened groups and supergroups
topPeerCategoryChannelsMost frequently visited channels
topPeerCategoryPhoneCallsMost frequently called users
topPeerCategoryForwardUsersUsers to which the users often forwards messages to
topPeerCategoryForwardChatsChats to which the users often forwards messages to
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/TopPeerCategoryPeers.html b/data/corefork.telegram.org/type/TopPeerCategoryPeers.html deleted file mode 100644 index f343176b7b..0000000000 --- a/data/corefork.telegram.org/type/TopPeerCategoryPeers.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - TopPeerCategoryPeers - - - - - - - - - - - - - -
- -
-
-
- -

TopPeerCategoryPeers

- -

Top peers by top peer category

-

- -
-
topPeerCategoryPeers#fb834291 category:TopPeerCategory count:int peers:Vector<TopPeer> = TopPeerCategoryPeers;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
topPeerCategoryPeersTop peer category
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/True.html b/data/corefork.telegram.org/type/True.html deleted file mode 100644 index d67f5b3273..0000000000 --- a/data/corefork.telegram.org/type/True.html +++ /dev/null @@ -1,145 +0,0 @@ - - - - - True - - - - - - - - - - - - - -
- -
-
-
- -

True

- -

See predefined identifiers.

-

- -
-
true#3fedd339 = True;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
trueSee predefined identifiers.
-

Related pages

-

TL-formal

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/Update.html b/data/corefork.telegram.org/type/Update.html deleted file mode 100644 index 710cf89e79..0000000000 --- a/data/corefork.telegram.org/type/Update.html +++ /dev/null @@ -1,603 +0,0 @@ - - - - - Update - - - - - - - - - - - - - -
- -
-
-
- -

Update

- -

Object contains info on events occured.

-

- -
-
updateNewMessage#1f2b0afd message:Message pts:int pts_count:int = Update;
-updateMessageID#4e90bfd6 id:int random_id:long = Update;
-updateDeleteMessages#a20db0e5 messages:Vector<int> pts:int pts_count:int = Update;
-updateUserTyping#c01e857f user_id:long action:SendMessageAction = Update;
-updateChatUserTyping#83487af0 chat_id:long from_id:Peer action:SendMessageAction = Update;
-updateChatParticipants#7761198 participants:ChatParticipants = Update;
-updateUserStatus#e5bdf8de user_id:long status:UserStatus = Update;
-updateUserName#c3f202e0 user_id:long first_name:string last_name:string username:string = Update;
-updateUserPhoto#f227868c user_id:long date:int photo:UserProfilePhoto previous:Bool = Update;
-updateNewEncryptedMessage#12bcbd9a message:EncryptedMessage qts:int = Update;
-updateEncryptedChatTyping#1710f156 chat_id:int = Update;
-updateEncryption#b4a2e88d chat:EncryptedChat date:int = Update;
-updateEncryptedMessagesRead#38fe25b7 chat_id:int max_date:int date:int = Update;
-updateChatParticipantAdd#3dda5451 chat_id:long user_id:long inviter_id:long date:int version:int = Update;
-updateChatParticipantDelete#e32f3d77 chat_id:long user_id:long version:int = Update;
-updateDcOptions#8e5e9873 dc_options:Vector<DcOption> = Update;
-updateNotifySettings#bec268ef peer:NotifyPeer notify_settings:PeerNotifySettings = Update;
-updateServiceNotification#ebe46819 flags:# popup:flags.0?true inbox_date:flags.1?int type:string message:string media:MessageMedia entities:Vector<MessageEntity> = Update;
-updatePrivacy#ee3b272a key:PrivacyKey rules:Vector<PrivacyRule> = Update;
-updateUserPhone#5492a13 user_id:long phone:string = Update;
-updateReadHistoryInbox#9c974fdf flags:# folder_id:flags.0?int peer:Peer max_id:int still_unread_count:int pts:int pts_count:int = Update;
-updateReadHistoryOutbox#2f2f21bf peer:Peer max_id:int pts:int pts_count:int = Update;
-updateWebPage#7f891213 webpage:WebPage pts:int pts_count:int = Update;
-updateReadMessagesContents#68c13933 messages:Vector<int> pts:int pts_count:int = Update;
-updateChannelTooLong#108d941f flags:# channel_id:long pts:flags.0?int = Update;
-updateChannel#635b4c09 channel_id:long = Update;
-updateNewChannelMessage#62ba04d9 message:Message pts:int pts_count:int = Update;
-updateReadChannelInbox#922e6e10 flags:# folder_id:flags.0?int channel_id:long max_id:int still_unread_count:int pts:int = Update;
-updateDeleteChannelMessages#c32d5b12 channel_id:long messages:Vector<int> pts:int pts_count:int = Update;
-updateChannelMessageViews#f226ac08 channel_id:long id:int views:int = Update;
-updateChatParticipantAdmin#d7ca61a2 chat_id:long user_id:long is_admin:Bool version:int = Update;
-updateNewStickerSet#688a30aa stickerset:messages.StickerSet = Update;
-updateStickerSetsOrder#bb2d201 flags:# masks:flags.0?true order:Vector<long> = Update;
-updateStickerSets#43ae3dec = Update;
-updateSavedGifs#9375341e = Update;
-updateBotInlineQuery#496f379c flags:# query_id:long user_id:long query:string geo:flags.0?GeoPoint peer_type:flags.1?InlineQueryPeerType offset:string = Update;
-updateBotInlineSend#12f12a07 flags:# user_id:long query:string geo:flags.0?GeoPoint id:string msg_id:flags.1?InputBotInlineMessageID = Update;
-updateEditChannelMessage#1b3f4df7 message:Message pts:int pts_count:int = Update;
-updateBotCallbackQuery#b9cfc48d flags:# query_id:long user_id:long peer:Peer msg_id:int chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
-updateEditMessage#e40370a3 message:Message pts:int pts_count:int = Update;
-updateInlineBotCallbackQuery#691e9052 flags:# query_id:long user_id:long msg_id:InputBotInlineMessageID chat_instance:long data:flags.0?bytes game_short_name:flags.1?string = Update;
-updateReadChannelOutbox#b75f99a9 channel_id:long max_id:int = Update;
-updateDraftMessage#ee2bb969 peer:Peer draft:DraftMessage = Update;
-updateReadFeaturedStickers#571d2742 = Update;
-updateRecentStickers#9a422c20 = Update;
-updateConfig#a229dd06 = Update;
-updatePtsChanged#3354678f = Update;
-updateChannelWebPage#2f2ba99f channel_id:long webpage:WebPage pts:int pts_count:int = Update;
-updateDialogPinned#6e6fe51c flags:# pinned:flags.0?true folder_id:flags.1?int peer:DialogPeer = Update;
-updatePinnedDialogs#fa0f3ca2 flags:# folder_id:flags.1?int order:flags.0?Vector<DialogPeer> = Update;
-updateBotWebhookJSON#8317c0c3 data:DataJSON = Update;
-updateBotWebhookJSONQuery#9b9240a6 query_id:long data:DataJSON timeout:int = Update;
-updateBotShippingQuery#b5aefd7d query_id:long user_id:long payload:bytes shipping_address:PostAddress = Update;
-updateBotPrecheckoutQuery#8caa9a96 flags:# query_id:long user_id:long payload:bytes info:flags.0?PaymentRequestedInfo shipping_option_id:flags.1?string currency:string total_amount:long = Update;
-updatePhoneCall#ab0f6b1e phone_call:PhoneCall = Update;
-updateLangPackTooLong#46560264 lang_code:string = Update;
-updateLangPack#56022f4d difference:LangPackDifference = Update;
-updateFavedStickers#e511996d = Update;
-updateChannelReadMessagesContents#44bdd535 channel_id:long messages:Vector<int> = Update;
-updateContactsReset#7084a7be = Update;
-updateChannelAvailableMessages#b23fc698 channel_id:long available_min_id:int = Update;
-updateDialogUnreadMark#e16459c3 flags:# unread:flags.0?true peer:DialogPeer = Update;
-updateMessagePoll#aca1657b flags:# poll_id:long poll:flags.0?Poll results:PollResults = Update;
-updateChatDefaultBannedRights#54c01850 peer:Peer default_banned_rights:ChatBannedRights version:int = Update;
-updateFolderPeers#19360dc0 folder_peers:Vector<FolderPeer> pts:int pts_count:int = Update;
-updatePeerSettings#6a7e7366 peer:Peer settings:PeerSettings = Update;
-updatePeerLocated#b4afcfb0 peers:Vector<PeerLocated> = Update;
-updateNewScheduledMessage#39a51dfb message:Message = Update;
-updateDeleteScheduledMessages#90866cee peer:Peer messages:Vector<int> = Update;
-updateTheme#8216fba3 theme:Theme = Update;
-updateGeoLiveViewed#871fb939 peer:Peer msg_id:int = Update;
-updateLoginToken#564fe691 = Update;
-updateMessagePollVote#106395c9 poll_id:long user_id:long options:Vector<bytes> qts:int = Update;
-updateDialogFilter#26ffde7d flags:# id:int filter:flags.0?DialogFilter = Update;
-updateDialogFilterOrder#a5d72105 order:Vector<int> = Update;
-updateDialogFilters#3504914f = Update;
-updatePhoneCallSignalingData#2661bf09 phone_call_id:long data:bytes = Update;
-updateChannelMessageForwards#d29a27f4 channel_id:long id:int forwards:int = Update;
-updateReadChannelDiscussionInbox#d6b19546 flags:# channel_id:long top_msg_id:int read_max_id:int broadcast_id:flags.0?long broadcast_post:flags.0?int = Update;
-updateReadChannelDiscussionOutbox#695c9e7c channel_id:long top_msg_id:int read_max_id:int = Update;
-updatePeerBlocked#246a4b22 peer_id:Peer blocked:Bool = Update;
-updateChannelUserTyping#8c88c923 flags:# channel_id:long top_msg_id:flags.0?int from_id:Peer action:SendMessageAction = Update;
-updatePinnedMessages#ed85eab5 flags:# pinned:flags.0?true peer:Peer messages:Vector<int> pts:int pts_count:int = Update;
-updatePinnedChannelMessages#5bb98608 flags:# pinned:flags.0?true channel_id:long messages:Vector<int> pts:int pts_count:int = Update;
-updateChat#f89a6a4e chat_id:long = Update;
-updateGroupCallParticipants#f2ebdb4e call:InputGroupCall participants:Vector<GroupCallParticipant> version:int = Update;
-updateGroupCall#14b24500 chat_id:long call:GroupCall = Update;
-updatePeerHistoryTTL#bb9bb9a5 flags:# peer:Peer ttl_period:flags.0?int = Update;
-updateChatParticipant#d087663a flags:# chat_id:long date:int actor_id:long user_id:long prev_participant:flags.0?ChatParticipant new_participant:flags.1?ChatParticipant invite:flags.2?ExportedChatInvite qts:int = Update;
-updateChannelParticipant#985d3abb flags:# channel_id:long date:int actor_id:long user_id:long prev_participant:flags.0?ChannelParticipant new_participant:flags.1?ChannelParticipant invite:flags.2?ExportedChatInvite qts:int = Update;
-updateBotStopped#c4870a49 user_id:long date:int stopped:Bool qts:int = Update;
-updateGroupCallConnection#b783982 flags:# presentation:flags.0?true params:DataJSON = Update;
-updateBotCommands#4d712f2e peer:Peer bot_id:long commands:Vector<BotCommand> = Update;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
updateNewMessageNew message.
updateMessageIDSent message with random_id client identifier was assigned an identifier.
updateDeleteMessagesMessages were deleted.
updateUserTypingThe user is preparing a message; typing, recording, uploading, etc. This update is valid for 6 seconds. If no repeated update received after 6 seconds, it should be considered that the user stopped doing whatever he's been doing.
updateChatUserTypingThe user is preparing a message in a group; typing, recording, uploading, etc. This update is valid for 6 seconds. If no repeated update received after 6 seconds, it should be considered that the user stopped doing whatever he's been doing.
updateChatParticipantsComposition of chat participants changed.
updateUserStatusContact status update.
updateUserNameChanges the user's first name, last name and username.
updateUserPhotoChange of contact's profile photo.
updateNewEncryptedMessageNew encrypted message.
updateEncryptedChatTypingInterlocutor is typing a message in an encrypted chat. Update period is 6 second. If upon this time there is no repeated update, it shall be considered that the interlocutor stopped typing.
updateEncryptionChange of state in an encrypted chat.
updateEncryptedMessagesReadCommunication history in an encrypted chat was marked as read.
updateChatParticipantAddNew group member.
updateChatParticipantDeleteA member has left the group.
updateDcOptionsChanges in the data center configuration options.
updateNotifySettingsChanges in notification settings.
updateServiceNotificationA service message for the user.

The app must show the message to the user upon receiving this update. In case the popup parameter was passed, the text message must be displayed in a popup alert immediately upon receipt. It is recommended to handle the text as you would an ordinary message in terms of highlighting links, etc. The message must also be stored locally as part of the message history with the user id 777000 (Telegram Notifications).
updatePrivacyPrivacy rules were changed
updateUserPhoneA user's phone number was changed
updateReadHistoryInboxIncoming messages were read
updateReadHistoryOutboxOutgoing messages were read
updateWebPageAn (IV) webpage preview was generated
updateReadMessagesContentsContents of messages in the common message box were read
updateChannelTooLongThere are new updates in the specified channel, the client must fetch them, eventually starting the specified pts if the difference is too long or if the channel isn't currently in the states.
updateChannelA new channel is available
updateNewChannelMessageA new message was sent in a channel/supergroup
updateReadChannelInboxIncoming messages in a channel/supergroup were read
updateDeleteChannelMessagesSome messages in a supergroup/channel were deleted
updateChannelMessageViewsThe view counter of a message in a channel has changed
updateChatParticipantAdminAdmin permissions of a user in a legacy group were changed
updateNewStickerSetA new stickerset was installed
updateStickerSetsOrderThe order of stickersets was changed
updateStickerSetsInstalled stickersets have changed, the client should refetch them using messages.getAllStickers
updateSavedGifsThe saved gif list has changed, the client should refetch it using messages.getSavedGifs
updateBotInlineQueryAn incoming inline query
updateBotInlineSendThe result of an inline query that was chosen by a user and sent to their chat partner. Please see our documentation on the feedback collecting for details on how to enable these updates for your bot.
updateEditChannelMessageA message was edited in a channel/supergroup
updateBotCallbackQueryA callback button was pressed, and the button data was sent to the bot that created the button
updateEditMessageA message was edited
updateInlineBotCallbackQueryThis notification is received by bots when a button is pressed
updateReadChannelOutboxOutgoing messages in a channel/supergroup were read
updateDraftMessageNotifies a change of a message draft.
updateReadFeaturedStickersSome featured stickers were marked as read
updateRecentStickersThe recent sticker list was updated
updateConfigThe server-side configuration has changed; the client should re-fetch the config using help.getConfig
updatePtsChangedCommon message box sequence PTS has changed, state has to be refetched using updates.getState
updateChannelWebPageA webpage preview of a link in a channel/supergroup message was generated
updateDialogPinnedA dialog was pinned/unpinned
updatePinnedDialogsPinned dialogs were updated
updateBotWebhookJSONA new incoming event; for bots only
updateBotWebhookJSONQueryA new incoming query; for bots only
updateBotShippingQueryThis object contains information about an incoming shipping query.
updateBotPrecheckoutQueryThis object contains information about an incoming pre-checkout query.
updatePhoneCallAn incoming phone call
updateLangPackTooLongA language pack has changed, the client should manually fetch the changed strings using langpack.getDifference
updateLangPackLanguage pack updated
updateFavedStickersThe list of favorited stickers was changed, the client should call messages.getFavedStickers to refetch the new list
updateChannelReadMessagesContentsThe specified channel/supergroup messages were read
updateContactsResetAll contacts were deleted
updateChannelAvailableMessagesThe history of a channel/supergroup was hidden.
updateDialogUnreadMarkThe manual unread mark of a chat was changed
updateMessagePollThe results of a poll have changed
updateChatDefaultBannedRightsDefault banned rights in a normal chat were updated
updateFolderPeersThe dialog list of a folder was changed
updatePeerSettingsSettings of a certain peer have changed
updatePeerLocatedList of peers near you was updated
updateNewScheduledMessageNew incoming scheduled message
updateDeleteScheduledMessagesSome scheduled messages were deleted
updateThemeA new cloud theme was installed
updateGeoLiveViewedLive geoposition message was viewed
updateLoginTokenA login token (for login via QR code) was generated
updateMessagePollVoteA specific user has voted in a poll
updateDialogFilterA new folder was added
updateDialogFilterOrderNew chat folders order
updateDialogFiltersUpdate folder list
updatePhoneCallSignalingDataIncoming phone call signaling payload
updateChannelMessageForwardsThe forward counter of a message in a channel has changed
updateReadChannelDiscussionInboxIncoming messages were marked as read
updateReadChannelDiscussionOutboxOutgoing comments in a discussion thread were marked as read
updatePeerBlockedA peer was blocked
updateChannelUserTypinguser is typing in a supergroup, channel or message thread
updatePinnedMessagesSome messages were pinned in a chat
updatePinnedChannelMessagesMessages were pinned/unpinned in a channel/supergroup
updateChatA new chat is available
updateGroupCallParticipantsThe participant list of a certain group call has changed
updateGroupCallA new groupcall was started
updatePeerHistoryTTLThe Time-To-Live for messages sent by the current user in a specific chat has changed
updateChatParticipantA user has joined or left a specific chat
updateChannelParticipantA participant has left/joined a channel or supergroup.
updateBotStoppedA bot was stopped or re-started.
updateGroupCallConnectionNew WebRTC parameters
updateBotCommandsThe command set of a certain bot in a certain chat has changed.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/Updates.html b/data/corefork.telegram.org/type/Updates.html deleted file mode 100644 index b62f7f5edc..0000000000 --- a/data/corefork.telegram.org/type/Updates.html +++ /dev/null @@ -1,508 +0,0 @@ - - - - - Updates - - - - - - - - - - - - - -
- -
-
-
- -

Updates

- -

Object which is perceived by the client without a call on its part when an event occurs.

-

- -
-
updatesTooLong#e317af7e = Updates;
-updateShortMessage#313bc7f8 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int user_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShortChatMessage#4d6deea5 flags:# out:flags.1?true mentioned:flags.4?true media_unread:flags.5?true silent:flags.13?true id:int from_id:long chat_id:long message:string pts:int pts_count:int date:int fwd_from:flags.2?MessageFwdHeader via_bot_id:flags.11?long reply_to:flags.3?MessageReplyHeader entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-updateShort#78d4dec1 update:Update date:int = Updates;
-updatesCombined#725b04c3 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq_start:int seq:int = Updates;
-updates#74ae4240 updates:Vector<Update> users:Vector<User> chats:Vector<Chat> date:int seq:int = Updates;
-updateShortSentMessage#9015e101 flags:# out:flags.1?true id:int pts:int pts_count:int date:int media:flags.9?MessageMedia entities:flags.7?Vector<MessageEntity> ttl_period:flags.25?int = Updates;
-
----functions---
-
-contacts.deleteContacts#96a0e00 id:Vector<InputUser> = Updates;
-contacts.addContact#e8f463d0 flags:# add_phone_privacy_exception:flags.0?true id:InputUser first_name:string last_name:string phone:string = Updates;
-contacts.acceptContact#f831a20f id:InputUser = Updates;
-contacts.getLocated#d348bc44 flags:# background:flags.1?true geo_point:InputGeoPoint self_expires:flags.0?int = Updates;
-contacts.blockFromReplies#29a8962c flags:# delete_message:flags.0?true delete_history:flags.1?true report_spam:flags.2?true msg_id:int = Updates;
-
-messages.sendMessage#520c3870 flags:# no_webpage:flags.1?true silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-messages.sendMedia#3491eba9 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int media:InputMedia message:string random_id:long reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.10?int = Updates;
-messages.forwardMessages#d9fee60e flags:# silent:flags.5?true background:flags.6?true with_my_score:flags.8?true drop_author:flags.11?true drop_media_captions:flags.12?true from_peer:InputPeer id:Vector<int> random_id:Vector<long> to_peer:InputPeer schedule_date:flags.10?int = Updates;
-messages.editChatTitle#73783ffd chat_id:long title:string = Updates;
-messages.editChatPhoto#35ddd674 chat_id:long photo:InputChatPhoto = Updates;
-messages.addChatUser#f24753e3 chat_id:long user_id:InputUser fwd_limit:int = Updates;
-messages.deleteChatUser#a2185cab flags:# revoke_history:flags.0?true chat_id:long user_id:InputUser = Updates;
-messages.createChat#9cb126e users:Vector<InputUser> title:string = Updates;
-messages.importChatInvite#6c50051c hash:string = Updates;
-messages.startBot#e6df7378 bot:InputUser peer:InputPeer random_id:long start_param:string = Updates;
-messages.migrateChat#a2875319 chat_id:long = Updates;
-messages.sendInlineBotResult#220815b0 flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true hide_via:flags.11?true peer:InputPeer reply_to_msg_id:flags.0?int random_id:long query_id:long id:string schedule_date:flags.10?int = Updates;
-messages.editMessage#48f71778 flags:# no_webpage:flags.1?true peer:InputPeer id:int message:flags.11?string media:flags.14?InputMedia reply_markup:flags.2?ReplyMarkup entities:flags.3?Vector<MessageEntity> schedule_date:flags.15?int = Updates;
-messages.getAllDrafts#6a3f8d65 = Updates;
-messages.setGameScore#8ef8ecc0 flags:# edit_message:flags.0?true force:flags.1?true peer:InputPeer id:int user_id:InputUser score:int = Updates;
-messages.sendScreenshotNotification#c97df020 peer:InputPeer reply_to_msg_id:int random_id:long = Updates;
-messages.sendMultiMedia#cc0110cb flags:# silent:flags.5?true background:flags.6?true clear_draft:flags.7?true peer:InputPeer reply_to_msg_id:flags.0?int multi_media:Vector<InputSingleMedia> schedule_date:flags.10?int = Updates;
-messages.updatePinnedMessage#d2aaf7ec flags:# silent:flags.0?true unpin:flags.1?true pm_oneside:flags.2?true peer:InputPeer id:int = Updates;
-messages.sendVote#10ea6184 peer:InputPeer msg_id:int options:Vector<bytes> = Updates;
-messages.getPollResults#73bb643b peer:InputPeer msg_id:int = Updates;
-messages.editChatDefaultBannedRights#a5866b41 peer:InputPeer banned_rights:ChatBannedRights = Updates;
-messages.sendScheduledMessages#bd38850a peer:InputPeer id:Vector<int> = Updates;
-messages.deleteScheduledMessages#59ae2b16 peer:InputPeer id:Vector<int> = Updates;
-messages.setHistoryTTL#b80e5fe4 peer:InputPeer period:int = Updates;
-messages.setChatTheme#e63be13f peer:InputPeer emoticon:string = Updates;
-
-help.getAppChangelog#9010ef6f prev_app_version:string = Updates;
-
-channels.createChannel#3d5fb10f flags:# broadcast:flags.0?true megagroup:flags.1?true for_import:flags.3?true title:string about:string geo_point:flags.2?InputGeoPoint address:flags.2?string = Updates;
-channels.editAdmin#d33c8902 channel:InputChannel user_id:InputUser admin_rights:ChatAdminRights rank:string = Updates;
-channels.editTitle#566decd0 channel:InputChannel title:string = Updates;
-channels.editPhoto#f12e57c9 channel:InputChannel photo:InputChatPhoto = Updates;
-channels.joinChannel#24b524c5 channel:InputChannel = Updates;
-channels.leaveChannel#f836aa95 channel:InputChannel = Updates;
-channels.inviteToChannel#199f3a6c channel:InputChannel users:Vector<InputUser> = Updates;
-channels.deleteChannel#c0111fe3 channel:InputChannel = Updates;
-channels.toggleSignatures#1f69b606 channel:InputChannel enabled:Bool = Updates;
-channels.editBanned#96e6cd81 channel:InputChannel participant:InputPeer banned_rights:ChatBannedRights = Updates;
-channels.togglePreHistoryHidden#eabbb94c channel:InputChannel enabled:Bool = Updates;
-channels.editCreator#8f38cd1f channel:InputChannel user_id:InputUser password:InputCheckPasswordSRP = Updates;
-channels.toggleSlowMode#edd49ef0 channel:InputChannel seconds:int = Updates;
-channels.convertToGigagroup#b290c69 channel:InputChannel = Updates;
-
-phone.discardCall#b2cbc1c0 flags:# video:flags.0?true peer:InputPhoneCall duration:int reason:PhoneCallDiscardReason connection_id:long = Updates;
-phone.setCallRating#59ead627 flags:# user_initiative:flags.0?true peer:InputPhoneCall rating:int comment:string = Updates;
-phone.createGroupCall#48cdc6d8 flags:# peer:InputPeer random_id:int title:flags.0?string schedule_date:flags.1?int = Updates;
-phone.joinGroupCall#b132ff7b flags:# muted:flags.0?true video_stopped:flags.2?true call:InputGroupCall join_as:InputPeer invite_hash:flags.1?string params:DataJSON = Updates;
-phone.leaveGroupCall#500377f9 call:InputGroupCall source:int = Updates;
-phone.inviteToGroupCall#7b393160 call:InputGroupCall users:Vector<InputUser> = Updates;
-phone.discardGroupCall#7a777135 call:InputGroupCall = Updates;
-phone.toggleGroupCallSettings#74bbb43d flags:# reset_invite_hash:flags.1?true call:InputGroupCall join_muted:flags.0?Bool = Updates;
-phone.toggleGroupCallRecord#f128c708 flags:# start:flags.0?true video:flags.2?true call:InputGroupCall title:flags.1?string video_portrait:flags.2?Bool = Updates;
-phone.editGroupCallParticipant#a5273abf flags:# call:InputGroupCall participant:InputPeer muted:flags.0?Bool volume:flags.1?int raise_hand:flags.2?Bool video_stopped:flags.3?Bool video_paused:flags.4?Bool presentation_paused:flags.5?Bool = Updates;
-phone.editGroupCallTitle#1ca6ac0a call:InputGroupCall title:string = Updates;
-phone.toggleGroupCallStartSubscription#219c34e6 call:InputGroupCall subscribed:Bool = Updates;
-phone.startScheduledGroupCall#5680e342 call:InputGroupCall = Updates;
-phone.joinGroupCallPresentation#cbea6bc4 call:InputGroupCall params:DataJSON = Updates;
-phone.leaveGroupCallPresentation#1c50d144 call:InputGroupCall = Updates;
-
-account.getNotifyExceptions#53577479 flags:# compare_sound:flags.1?true peer:flags.0?InputNotifyPeer = Updates;
-
-folders.editPeerFolders#6847d0ab folder_peers:Vector<InputFolderPeer> = Updates;
-folders.deleteFolder#1c295881 folder_id:int = Updates;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
updatesTooLongToo many updates, it is necessary to execute updates.getDifference.
updateShortMessageInfo about a message sent to (received from) another user
updateShortChatMessageShortened constructor containing info on one new incoming text message from a chat
updateShortShortened constructor containing info on one update not requiring auxiliary data
updatesCombinedConstructor for a group of updates.
updatesFull constructor of updates
updateShortSentMessageShortened constructor containing info on one outgoing message to a contact (the destination chat has to be extracted from the method call that returned this object).
-

Methods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
MethodDescription
contacts.deleteContactsDeletes several contacts from the list.
messages.sendMessageSends a message to a chat
messages.sendMediaSend a media
messages.forwardMessagesForwards messages by their IDs.
messages.editChatTitleChanages chat name and sends a service message on it.
messages.editChatPhotoChanges chat photo and sends a service message on it
messages.addChatUserAdds a user to a chat and sends a service message on it.
messages.deleteChatUserDeletes a user from a chat and sends a service message on it.
messages.createChatCreates a new chat.
messages.importChatInviteImport a chat invite and join a private chat/supergroup/channel
messages.startBotStart a conversation with a bot using a deep linking parameter
help.getAppChangelogGet changelog of current app
channels.createChannelCreate a supergroup/channel.
channels.editAdminModify the admin rights of a user in a supergroup/channel.
channels.editTitleEdit the name of a channel/supergroup
channels.editPhotoChange the photo of a channel/supergroup
channels.joinChannelJoin a channel/supergroup
channels.leaveChannelLeave a channel/supergroup
channels.inviteToChannelInvite users to a channel/supergroup
channels.deleteChannelDelete a channel/supergroup
messages.migrateChatTurn a legacy group into a supergroup
messages.sendInlineBotResultSend a result obtained using messages.getInlineBotResults.
channels.toggleSignaturesEnable/disable message signatures in channels
messages.editMessageEdit message
messages.getAllDraftsSave get all message drafts.
messages.setGameScoreUse this method to set the score of the specified user in a game sent as a normal message (bots only).
phone.discardCallRefuse or end running call
phone.setCallRatingRate a call
channels.editBannedBan/unban/kick a user in a supergroup/channel.
messages.sendScreenshotNotificationNotify the other user in a private chat that a screenshot of the chat was taken
channels.togglePreHistoryHiddenHide/unhide message history for new channel/supergroup users
messages.sendMultiMediaSend an album of media
messages.updatePinnedMessagePin a message
account.getNotifyExceptionsReturns list of chats with non-default notification settings
messages.sendVoteVote in a poll
messages.getPollResultsGet poll results
messages.editChatDefaultBannedRightsEdit the default banned rights of a channel/supergroup/group.
folders.editPeerFoldersEdit peers in folder
folders.deleteFolderDelete a folder
contacts.addContactAdd an existing telegram user as contact
contacts.acceptContactIf the peer settings of a new user allow us to add him as contact, add that user as contact
channels.editCreatorTransfer channel ownership
contacts.getLocatedGet contacts near you
channels.toggleSlowModeToggle supergroup slow mode: if enabled, users will only be able to send one message every seconds seconds
messages.sendScheduledMessagesSend scheduled messages
messages.deleteScheduledMessagesDelete scheduled messages
contacts.blockFromRepliesStop getting notifications about thread replies of a certain user in @replies
phone.createGroupCallCreate a group call or livestream
phone.joinGroupCallJoin a group call
phone.leaveGroupCallLeave a group call
phone.inviteToGroupCallInvite a set of users to a group call.
phone.discardGroupCallTerminate a group call
phone.toggleGroupCallSettingsChange group call settings
messages.setHistoryTTLSet maximum Time-To-Live of all messages in the specified chat
channels.convertToGigagroupConvert a supergroup to a gigagroup
phone.toggleGroupCallRecordStart or stop recording a group call
phone.editGroupCallParticipantEdit information about a given group call participant
phone.editGroupCallTitleEdit the title of a group call or livestream
phone.toggleGroupCallStartSubscriptionSubscribe or unsubscribe to a scheduled group call
phone.startScheduledGroupCallStart a scheduled group call.
phone.joinGroupCallPresentationStart screen sharing in a call
phone.leaveGroupCallPresentationStop screen sharing in a group call
messages.setChatThemeChange the chat theme of a certain chat
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/UrlAuthResult.html b/data/corefork.telegram.org/type/UrlAuthResult.html deleted file mode 100644 index cac6564213..0000000000 --- a/data/corefork.telegram.org/type/UrlAuthResult.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - UrlAuthResult - - - - - - - - - - - - - -
- -
-
-
- -

UrlAuthResult

- -

URL authorization result

-

- -
-
urlAuthResultRequest#92d33a0e flags:# request_write_access:flags.0?true bot:User domain:string = UrlAuthResult;
-urlAuthResultAccepted#8f8c0e4e url:string = UrlAuthResult;
-urlAuthResultDefault#a9d6db1f = UrlAuthResult;
-
----functions---
-
-messages.requestUrlAuth#198fb446 flags:# peer:flags.1?InputPeer msg_id:flags.1?int button_id:flags.1?int url:flags.2?string = UrlAuthResult;
-messages.acceptUrlAuth#b12c7125 flags:# write_allowed:flags.0?true peer:flags.1?InputPeer msg_id:flags.1?int button_id:flags.1?int url:flags.2?string = UrlAuthResult;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
urlAuthResultRequestDetails about the authorization request, for more info click here »
urlAuthResultAcceptedDetails about an accepted authorization request, for more info click here »
urlAuthResultDefaultDetails about an accepted authorization request, for more info click here »
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
messages.requestUrlAuthGet more info about a Seamless Telegram Login authorization request, for more info click here »
messages.acceptUrlAuthUse this to accept a Seamless Telegram Login authorization request, for more info click here »
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/User.html b/data/corefork.telegram.org/type/User.html deleted file mode 100644 index 72027b32d8..0000000000 --- a/data/corefork.telegram.org/type/User.html +++ /dev/null @@ -1,177 +0,0 @@ - - - - - User - - - - - - - - - - - - - -
- -
-
-
- -

User

- -

Object defines a user.

-

- -
-
userEmpty#d3bc4b7a id:long = User;
-user#3ff6ecb0 flags:# self:flags.10?true contact:flags.11?true mutual_contact:flags.12?true deleted:flags.13?true bot:flags.14?true bot_chat_history:flags.15?true bot_nochats:flags.16?true verified:flags.17?true restricted:flags.18?true min:flags.20?true bot_inline_geo:flags.21?true support:flags.23?true scam:flags.24?true apply_min_photo:flags.25?true fake:flags.26?true id:long access_hash:flags.0?long first_name:flags.1?string last_name:flags.2?string username:flags.3?string phone:flags.4?string photo:flags.5?UserProfilePhoto status:flags.6?UserStatus bot_info_version:flags.14?int restriction_reason:flags.18?Vector<RestrictionReason> bot_inline_placeholder:flags.19?string lang_code:flags.22?string = User;
-
----functions---
-
-account.updateProfile#78515775 flags:# first_name:flags.0?string last_name:flags.1?string about:flags.2?string = User;
-account.updateUsername#3e0bdd7c username:string = User;
-account.changePhone#70c32edb phone_number:string phone_code_hash:string phone_code:string = User;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
userEmptyEmpty constructor, non-existent user.
userIndicates info about a certain user
-

Methods

- - - - - - - - - - - - - - - - - - - - - -
MethodDescription
account.updateProfileUpdates user profile.
account.updateUsernameChanges username for the current user.
account.changePhoneChange the phone number of the current account
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/UserFull.html b/data/corefork.telegram.org/type/UserFull.html deleted file mode 100644 index 9000fba448..0000000000 --- a/data/corefork.telegram.org/type/UserFull.html +++ /dev/null @@ -1,162 +0,0 @@ - - - - - UserFull - - - - - - - - - - - - - -
- -
-
-
- -

UserFull

- -

Object contains extended user info.

-

- -
-
userFull#d697ff05 flags:# blocked:flags.0?true phone_calls_available:flags.4?true phone_calls_private:flags.5?true can_pin_message:flags.7?true has_scheduled:flags.12?true video_calls_available:flags.13?true user:User about:flags.1?string settings:PeerSettings profile_photo:flags.2?Photo notify_settings:PeerNotifySettings bot_info:flags.3?BotInfo pinned_msg_id:flags.6?int common_chats_count:int folder_id:flags.11?int ttl_period:flags.14?int theme_emoticon:flags.15?string = UserFull;
-
----functions---
-
-users.getFullUser#ca30a5b1 id:InputUser = UserFull;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
userFullExtended user info
-

Methods

- - - - - - - - - - - - - -
MethodDescription
users.getFullUserReturns extended user info by ID.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/UserProfilePhoto.html b/data/corefork.telegram.org/type/UserProfilePhoto.html deleted file mode 100644 index 0f88af10b6..0000000000 --- a/data/corefork.telegram.org/type/UserProfilePhoto.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - UserProfilePhoto - - - - - - - - - - - - - -
- -
-
-
- -

UserProfilePhoto

- -

Object contains info on the user's profile photo.

-

- -
-
userProfilePhotoEmpty#4f11bae1 = UserProfilePhoto;
-userProfilePhoto#82d1f706 flags:# has_video:flags.0?true photo_id:long stripped_thumb:flags.1?bytes dc_id:int = UserProfilePhoto;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
userProfilePhotoEmptyProfile photo has not been set, or was hidden.
userProfilePhotoUser profile photo.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/UserStatus.html b/data/corefork.telegram.org/type/UserStatus.html deleted file mode 100644 index 3c1eef7ac6..0000000000 --- a/data/corefork.telegram.org/type/UserStatus.html +++ /dev/null @@ -1,168 +0,0 @@ - - - - - UserStatus - - - - - - - - - - - - - -
- -
-
-
- -

UserStatus

- -

User online status

-

- -
-
userStatusEmpty#9d05049 = UserStatus;
-userStatusOnline#edb93949 expires:int = UserStatus;
-userStatusOffline#8c703f was_online:int = UserStatus;
-userStatusRecently#e26f42f1 = UserStatus;
-userStatusLastWeek#7bf09fc = UserStatus;
-userStatusLastMonth#77ebc742 = UserStatus;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
userStatusEmptyUser status has not been set yet.
userStatusOnlineOnline status of the user.
userStatusOfflineThe user's offline status.
userStatusRecentlyOnline status: last seen recently
userStatusLastWeekOnline status: last seen last week
userStatusLastMonthOnline status: last seen last month
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/Vector t.html b/data/corefork.telegram.org/type/Vector t.html deleted file mode 100644 index 5a1965db3e..0000000000 --- a/data/corefork.telegram.org/type/Vector t.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - Vector t - - - - - - - - - - - - - -
- -
-
-
- -

Vector t

- -

Universal vector.

-

- -
-
vector#1cb5c415 {t:Type} # [ t ] = Vector t;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
vectorA universal vector constructor.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/Video.html b/data/corefork.telegram.org/type/Video.html deleted file mode 100644 index 94bdf516a9..0000000000 --- a/data/corefork.telegram.org/type/Video.html +++ /dev/null @@ -1,128 +0,0 @@ - - - - - Video - - - - - - - - - - - - - -
- -
-
-
- -

Video

- -

Video.

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/VideoSize.html b/data/corefork.telegram.org/type/VideoSize.html deleted file mode 100644 index 9d035614e7..0000000000 --- a/data/corefork.telegram.org/type/VideoSize.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - VideoSize - - - - - - - - - - - - - -
- -
-
-
- -

VideoSize

- -

Represents an animated video thumbnail

-

- -
-
videoSize#de33b094 flags:# type:string w:int h:int size:int video_start_ts:flags.0?double = VideoSize;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
videoSizeAnimated profile picture in MPEG4 format
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/WallPaper.html b/data/corefork.telegram.org/type/WallPaper.html deleted file mode 100644 index 3cec1b95e4..0000000000 --- a/data/corefork.telegram.org/type/WallPaper.html +++ /dev/null @@ -1,172 +0,0 @@ - - - - - WallPaper - - - - - - - - - - - - - -
- -
-
-
- -

WallPaper

- -

Object contains info on a wallpaper.

-

- -
-
wallPaper#a437c3ed id:long flags:# creator:flags.0?true default:flags.1?true pattern:flags.3?true dark:flags.4?true access_hash:long slug:string document:Document settings:flags.2?WallPaperSettings = WallPaper;
-wallPaperNoFile#e0804116 id:long flags:# default:flags.1?true dark:flags.4?true settings:flags.2?WallPaperSettings = WallPaper;
-
----functions---
-
-account.getWallPaper#fc8ddbea wallpaper:InputWallPaper = WallPaper;
-account.uploadWallPaper#dd853661 file:InputFile mime_type:string settings:WallPaperSettings = WallPaper;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
wallPaperWallpaper settings.
wallPaperNoFileNo file wallpaper
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
account.getWallPaperGet info about a certain wallpaper
account.uploadWallPaperCreate and upload a new wallpaper
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/WebAuthorization.html b/data/corefork.telegram.org/type/WebAuthorization.html deleted file mode 100644 index b17ead892f..0000000000 --- a/data/corefork.telegram.org/type/WebAuthorization.html +++ /dev/null @@ -1,143 +0,0 @@ - - - - - WebAuthorization - - - - - - - - - - - - - -
- -
-
-
- -

WebAuthorization

- -

Web authorization

-

- -
-
webAuthorization#a6f8f452 hash:long bot_id:long domain:string browser:string platform:string date_created:int date_active:int ip:string region:string = WebAuthorization;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
webAuthorizationRepresents a bot logged in using the Telegram login widget
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/WebDocument.html b/data/corefork.telegram.org/type/WebDocument.html deleted file mode 100644 index ba48b19b40..0000000000 --- a/data/corefork.telegram.org/type/WebDocument.html +++ /dev/null @@ -1,148 +0,0 @@ - - - - - WebDocument - - - - - - - - - - - - - -
- -
-
-
- -

WebDocument

- -

Remote document

-

- -
-
webDocument#1c570ed1 url:string access_hash:long size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;
-webDocumentNoProxy#f9c8bcc6 url:string size:int mime_type:string attributes:Vector<DocumentAttribute> = WebDocument;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
webDocumentRemote document
webDocumentNoProxyRemote document that can be downloaded without proxying through telegram
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/account.AuthorizationForm b/data/corefork.telegram.org/type/account.AuthorizationForm deleted file mode 100644 index f21679aa92..0000000000 --- a/data/corefork.telegram.org/type/account.AuthorizationForm +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Account.AuthorizationForm - - - - - - - - - - - - - -
- -
-
-
- -

Account.AuthorizationForm

- -

Authorization form

-

- -
-
account.authorizationForm#ad2e1cd8 flags:# required_types:Vector<SecureRequiredType> values:Vector<SecureValue> errors:Vector<SecureValueError> users:Vector<User> privacy_policy_url:flags.0?string = account.AuthorizationForm;
-
----functions---
-
-account.getAuthorizationForm#a929597a bot_id:long scope:string public_key:string = account.AuthorizationForm;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.authorizationFormAuthorization form
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getAuthorizationFormReturns a Telegram Passport authorization form for sharing data with a service
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/account.Authorizations b/data/corefork.telegram.org/type/account.Authorizations deleted file mode 100644 index ee22505e28..0000000000 --- a/data/corefork.telegram.org/type/account.Authorizations +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Account.Authorizations - - - - - - - - - - - - - -
- -
-
-
- -

Account.Authorizations

- -

Logged-in sessions

-

- -
-
account.authorizations#1250abde authorizations:Vector<Authorization> = account.Authorizations;
-
----functions---
-
-account.getAuthorizations#e320c158 = account.Authorizations;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.authorizationsLogged-in sessions
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getAuthorizationsGet logged-in sessions
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/account.AutoDownloadSettings b/data/corefork.telegram.org/type/account.AutoDownloadSettings deleted file mode 100644 index 168866f7d8..0000000000 --- a/data/corefork.telegram.org/type/account.AutoDownloadSettings +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Account.AutoDownloadSettings - - - - - - - - - - - - - -
- -
-
-
- -

Account.AutoDownloadSettings

- -

Media autodownload settings

-

- -
-
account.autoDownloadSettings#63cacf26 low:AutoDownloadSettings medium:AutoDownloadSettings high:AutoDownloadSettings = account.AutoDownloadSettings;
-
----functions---
-
-account.getAutoDownloadSettings#56da0b3f = account.AutoDownloadSettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.autoDownloadSettingsMedia autodownload settings
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getAutoDownloadSettingsGet media autodownload settings
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/account.ChatThemes b/data/corefork.telegram.org/type/account.ChatThemes deleted file mode 100644 index 941278a7d7..0000000000 --- a/data/corefork.telegram.org/type/account.ChatThemes +++ /dev/null @@ -1,167 +0,0 @@ - - - - - account.ChatThemes - - - - - - - - - - - - - -
- -
-
-
- -

account.ChatThemes

- -

Available chat themes

-

- -
-
account.chatThemesNotModified#e011e1c4 = account.ChatThemes;
-account.chatThemes#fe4cbebd hash:int themes:Vector<ChatTheme> = account.ChatThemes;
-
----functions---
-
-account.getChatThemes#d6d71d7b hash:int = account.ChatThemes;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
account.chatThemesNotModifiedThe available chat themes were not modified
account.chatThemesAvailable chat themes
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getChatThemesGet all available chat themes
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/account.ContentSettings b/data/corefork.telegram.org/type/account.ContentSettings deleted file mode 100644 index b773176c84..0000000000 --- a/data/corefork.telegram.org/type/account.ContentSettings +++ /dev/null @@ -1,162 +0,0 @@ - - - - - account.ContentSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.ContentSettings

- -

Sensitive content settings

-

- -
-
account.contentSettings#57e28221 flags:# sensitive_enabled:flags.0?true sensitive_can_change:flags.1?true = account.ContentSettings;
-
----functions---
-
-account.getContentSettings#8b9b4dae = account.ContentSettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.contentSettingsSensitive content settings
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getContentSettingsGet sensitive content settings
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/account.Password b/data/corefork.telegram.org/type/account.Password deleted file mode 100644 index ad0c8b274c..0000000000 --- a/data/corefork.telegram.org/type/account.Password +++ /dev/null @@ -1,162 +0,0 @@ - - - - - account.Password - - - - - - - - - - - - - -
- -
-
-
- -

account.Password

- -

Configuration for two-factor authorization

-

- -
-
account.password#185b184f flags:# has_recovery:flags.0?true has_secure_values:flags.1?true has_password:flags.2?true current_algo:flags.2?PasswordKdfAlgo srp_B:flags.2?bytes srp_id:flags.2?long hint:flags.3?string email_unconfirmed_pattern:flags.4?string new_algo:PasswordKdfAlgo new_secure_algo:SecurePasswordKdfAlgo secure_random:bytes pending_reset_date:flags.5?int = account.Password;
-
----functions---
-
-account.getPassword#548a30f5 = account.Password;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.passwordConfiguration for two-factor authorization
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getPasswordObtain configuration for two-factor authorization with password
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/account.PasswordInputSettings b/data/corefork.telegram.org/type/account.PasswordInputSettings deleted file mode 100644 index e3306aa0fe..0000000000 --- a/data/corefork.telegram.org/type/account.PasswordInputSettings +++ /dev/null @@ -1,146 +0,0 @@ - - - - - account.PasswordInputSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.PasswordInputSettings

- -

Constructor for setting up a new 2FA SRP password

-

- -
-
account.passwordInputSettings#c23727c9 flags:# new_algo:flags.0?PasswordKdfAlgo new_password_hash:flags.0?bytes hint:flags.0?string email:flags.1?string new_secure_settings:flags.2?SecureSecretSettings = account.PasswordInputSettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.passwordInputSettingsSettings for setting up a new password
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/account.PasswordSettings b/data/corefork.telegram.org/type/account.PasswordSettings deleted file mode 100644 index 16f470b4ab..0000000000 --- a/data/corefork.telegram.org/type/account.PasswordSettings +++ /dev/null @@ -1,164 +0,0 @@ - - - - - account.PasswordSettings - - - - - - - - - - - - - -
- -
-
-
- -

account.PasswordSettings

- -

Private info associated to the password info (recovery email, telegram passport info & so on)

-

- -
-
account.passwordSettings#9a5c33e5 flags:# email:flags.0?string secure_settings:flags.1?SecureSecretSettings = account.PasswordSettings;
-
----functions---
-
-account.getPasswordSettings#9cd4eaf9 password:InputCheckPasswordSRP = account.PasswordSettings;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.passwordSettingsPrivate info associated to the password info (recovery email, telegram passport info & so on)
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getPasswordSettingsGet private info associated to the password info (recovery email, telegram passport info & so on)
-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/account.PrivacyRules b/data/corefork.telegram.org/type/account.PrivacyRules deleted file mode 100644 index 6aab67c5bc..0000000000 --- a/data/corefork.telegram.org/type/account.PrivacyRules +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Account.PrivacyRules - - - - - - - - - - - - - -
- -
-
-
- -

Account.PrivacyRules

- -

Privacy rules

-

- -
-
account.privacyRules#50a04e45 rules:Vector<PrivacyRule> chats:Vector<Chat> users:Vector<User> = account.PrivacyRules;
-
----functions---
-
-account.getPrivacy#dadbc950 key:InputPrivacyKey = account.PrivacyRules;
-account.setPrivacy#c9f81ce8 key:InputPrivacyKey rules:Vector<InputPrivacyRule> = account.PrivacyRules;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.privacyRulesPrivacy rules
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
account.getPrivacyGet privacy settings of current account
account.setPrivacyChange privacy settings of current account
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/account.ResetPasswordResult b/data/corefork.telegram.org/type/account.ResetPasswordResult deleted file mode 100644 index a19e111e9d..0000000000 --- a/data/corefork.telegram.org/type/account.ResetPasswordResult +++ /dev/null @@ -1,175 +0,0 @@ - - - - - account.ResetPasswordResult - - - - - - - - - - - - - -
- -
-
-
- -

account.ResetPasswordResult

- -

Result of an account.resetPassword request.

-

- -
-
account.resetPasswordFailedWait#e3779861 retry_date:int = account.ResetPasswordResult;
-account.resetPasswordRequestedWait#e9effc7d until_date:int = account.ResetPasswordResult;
-account.resetPasswordOk#e926d63e = account.ResetPasswordResult;
-
----functions---
-
-account.resetPassword#9308ce1b = account.ResetPasswordResult;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
account.resetPasswordFailedWaitYou requested a password reset too many times, please wait until the specified date before retrying the reset.
account.resetPasswordRequestedWaitYou already requested a password reset, please wait until the specified date before retrying the reset.
account.resetPasswordOkThe 2FA password was reset successfully.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.resetPasswordInitiate a 2FA password reset
-

Related pages

-

account.resetPassword

-

Initiate a 2FA password reset: can only be used if the user is already logged-in, see here for more info »

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/account.SentChangePhoneCode b/data/corefork.telegram.org/type/account.SentChangePhoneCode deleted file mode 100644 index 46d3e709fe..0000000000 --- a/data/corefork.telegram.org/type/account.SentChangePhoneCode +++ /dev/null @@ -1,128 +0,0 @@ - - - - - Account.SentChangePhoneCode - - - - - - - - - - - - - -
- -
-
-
- -

Account.SentChangePhoneCode

- -

Sent phone code

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/account.SentEmailCode b/data/corefork.telegram.org/type/account.SentEmailCode deleted file mode 100644 index 4bb96eccb6..0000000000 --- a/data/corefork.telegram.org/type/account.SentEmailCode +++ /dev/null @@ -1,162 +0,0 @@ - - - - - account.SentEmailCode - - - - - - - - - - - - - -
- -
-
-
- -

account.SentEmailCode

- -

The email code that was sent

-

- -
-
account.sentEmailCode#811f854f email_pattern:string length:int = account.SentEmailCode;
-
----functions---
-
-account.sendVerifyEmailCode#7011509f email:string = account.SentEmailCode;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.sentEmailCodeThe sent email code
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.sendVerifyEmailCodeSend the verification email code for telegram passport.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/account.Takeout b/data/corefork.telegram.org/type/account.Takeout deleted file mode 100644 index b3fd425d7c..0000000000 --- a/data/corefork.telegram.org/type/account.Takeout +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Account.Takeout - - - - - - - - - - - - - -
- -
-
-
- -

Account.Takeout

- -

Takeout info

-

- -
-
account.takeout#4dba4501 id:long = account.Takeout;
-
----functions---
-
-account.initTakeoutSession#f05b4804 flags:# contacts:flags.0?true message_users:flags.1?true message_chats:flags.2?true message_megagroups:flags.3?true message_channels:flags.4?true files:flags.5?true file_max_size:flags.5?int = account.Takeout;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.takeoutTakout info
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.initTakeoutSessionInitialize account takeout session
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/account.Themes b/data/corefork.telegram.org/type/account.Themes deleted file mode 100644 index aa2e1f5ac7..0000000000 --- a/data/corefork.telegram.org/type/account.Themes +++ /dev/null @@ -1,167 +0,0 @@ - - - - - account.Themes - - - - - - - - - - - - - -
- -
-
-
- -

account.Themes

- -

Installed themes

-

- -
-
account.themesNotModified#f41eb622 = account.Themes;
-account.themes#9a3d8c6d hash:long themes:Vector<Theme> = account.Themes;
-
----functions---
-
-account.getThemes#7206e458 format:string hash:long = account.Themes;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
account.themesNotModifiedNo new themes were installed
account.themesInstalled themes
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getThemesGet installed themes
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/account.TmpPassword b/data/corefork.telegram.org/type/account.TmpPassword deleted file mode 100644 index 1e85896dac..0000000000 --- a/data/corefork.telegram.org/type/account.TmpPassword +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Account.TmpPassword - - - - - - - - - - - - - -
- -
-
-
- -

Account.TmpPassword

- -

Temporary password

-

- -
-
account.tmpPassword#db64fd34 tmp_password:bytes valid_until:int = account.TmpPassword;
-
----functions---
-
-account.getTmpPassword#449e0b51 password:InputCheckPasswordSRP period:int = account.TmpPassword;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.tmpPasswordTemporary payment password
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getTmpPasswordGet temporary payment password
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/account.WallPapers b/data/corefork.telegram.org/type/account.WallPapers deleted file mode 100644 index 7911ace3eb..0000000000 --- a/data/corefork.telegram.org/type/account.WallPapers +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Account.WallPapers - - - - - - - - - - - - - -
- -
-
-
- -

Account.WallPapers

- -

Wallpapers

-

- -
-
account.wallPapersNotModified#1c199183 = account.WallPapers;
-account.wallPapers#cdc3858c hash:long wallpapers:Vector<WallPaper> = account.WallPapers;
-
----functions---
-
-account.getWallPapers#7967d36 hash:long = account.WallPapers;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
account.wallPapersNotModifiedNo new wallpapers were found
account.wallPapersInstalled wallpapers
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getWallPapersReturns a list of available wallpapers.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/account.WebAuthorizations b/data/corefork.telegram.org/type/account.WebAuthorizations deleted file mode 100644 index f7d338ace9..0000000000 --- a/data/corefork.telegram.org/type/account.WebAuthorizations +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Account.WebAuthorizations - - - - - - - - - - - - - -
- -
-
-
- -

Account.WebAuthorizations

- -

Web authorizations

-

- -
-
account.webAuthorizations#ed56c9fc authorizations:Vector<WebAuthorization> users:Vector<User> = account.WebAuthorizations;
-
----functions---
-
-account.getWebAuthorizations#182e6d6f = account.WebAuthorizations;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
account.webAuthorizationsWeb authorizations
-

Methods

- - - - - - - - - - - - - -
MethodDescription
account.getWebAuthorizationsGet web login widget authorizations
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/auth.Authorization b/data/corefork.telegram.org/type/auth.Authorization deleted file mode 100644 index 1896747cfe..0000000000 --- a/data/corefork.telegram.org/type/auth.Authorization +++ /dev/null @@ -1,192 +0,0 @@ - - - - - auth.Authorization - - - - - - - - - - - - - -
- -
-
-
- -

auth.Authorization

- -

Oject contains info on user authorization.

-

- -
-
auth.authorization#cd050916 flags:# tmp_sessions:flags.0?int user:User = auth.Authorization;
-auth.authorizationSignUpRequired#44747e9a flags:# terms_of_service:flags.0?help.TermsOfService = auth.Authorization;
-
----functions---
-
-auth.signUp#80eee427 phone_number:string phone_code_hash:string first_name:string last_name:string = auth.Authorization;
-auth.signIn#bcd51581 phone_number:string phone_code_hash:string phone_code:string = auth.Authorization;
-auth.importAuthorization#a57a7dad id:long bytes:bytes = auth.Authorization;
-auth.importBotAuthorization#67a3ff2c flags:int api_id:int api_hash:string bot_auth_token:string = auth.Authorization;
-auth.checkPassword#d18b4d16 password:InputCheckPasswordSRP = auth.Authorization;
-auth.recoverPassword#37096c70 flags:# code:string new_settings:flags.0?account.PasswordInputSettings = auth.Authorization;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
auth.authorizationContains user authorization info.
auth.authorizationSignUpRequiredAn account with this phone number doesn't exist on telegram: the user has to enter basic information and sign up
-

Methods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
MethodDescription
auth.signUpRegisters a validated phone number in the system.
auth.signInSigns in a user with a validated phone number.
auth.importAuthorizationLogs in a user using a key transmitted from his native data-centre.
auth.importBotAuthorizationLogin as a bot
auth.checkPasswordTry logging to an account protected by a 2FA password.
auth.recoverPasswordReset the 2FA password using the recovery code sent using auth.requestPasswordRecovery.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/auth.CheckedPhone b/data/corefork.telegram.org/type/auth.CheckedPhone deleted file mode 100644 index d8e6f611cd..0000000000 --- a/data/corefork.telegram.org/type/auth.CheckedPhone +++ /dev/null @@ -1,128 +0,0 @@ - - - - - Auth.CheckedPhone - - - - - - - - - - - - - -
- -
-
-
- -

Auth.CheckedPhone

- -

Checked phone

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/auth.ExportedAuthorization b/data/corefork.telegram.org/type/auth.ExportedAuthorization deleted file mode 100644 index b4859767bd..0000000000 --- a/data/corefork.telegram.org/type/auth.ExportedAuthorization +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Auth.ExportedAuthorization - - - - - - - - - - - - - -
- -
-
-
- -

Auth.ExportedAuthorization

- -

Exported authorization

-

- -
-
auth.exportedAuthorization#b434e2b8 id:long bytes:bytes = auth.ExportedAuthorization;
-
----functions---
-
-auth.exportAuthorization#e5bfffcd dc_id:int = auth.ExportedAuthorization;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
auth.exportedAuthorizationData for copying of authorization between data centres.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
auth.exportAuthorizationReturns data for copying authorization to another data-centre.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/auth.LoginToken b/data/corefork.telegram.org/type/auth.LoginToken deleted file mode 100644 index ffedcd2bc4..0000000000 --- a/data/corefork.telegram.org/type/auth.LoginToken +++ /dev/null @@ -1,177 +0,0 @@ - - - - - auth.LoginToken - - - - - - - - - - - - - -
- -
-
-
- -

auth.LoginToken

- -

Login token (for QR code login)

-

- -
-
auth.loginToken#629f1980 expires:int token:bytes = auth.LoginToken;
-auth.loginTokenMigrateTo#68e9916 dc_id:int token:bytes = auth.LoginToken;
-auth.loginTokenSuccess#390d5c5e authorization:auth.Authorization = auth.LoginToken;
-
----functions---
-
-auth.exportLoginToken#b7e085fe api_id:int api_hash:string except_ids:Vector<long> = auth.LoginToken;
-auth.importLoginToken#95ac5ce4 token:bytes = auth.LoginToken;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
auth.loginTokenLogin token (for QR code login)
auth.loginTokenMigrateToRepeat the query to the specified DC
auth.loginTokenSuccessLogin via token (QR code) succeded!
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
auth.exportLoginTokenExport login token (for login via QR code)
auth.importLoginTokenLogin using a redirected login token, generated in case of DC mismatch during QR code login.

For more info, see login via QR code.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/auth.PasswordRecovery b/data/corefork.telegram.org/type/auth.PasswordRecovery deleted file mode 100644 index 1700050882..0000000000 --- a/data/corefork.telegram.org/type/auth.PasswordRecovery +++ /dev/null @@ -1,165 +0,0 @@ - - - - - auth.PasswordRecovery - - - - - - - - - - - - - -
- -
-
-
- -

auth.PasswordRecovery

- -

Recovery info of a 2FA password, only for accounts with a recovery email configured.

-

- -
-
auth.passwordRecovery#137948a5 email_pattern:string = auth.PasswordRecovery;
-
----functions---
-
-auth.requestPasswordRecovery#d897bc66 = auth.PasswordRecovery;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
auth.passwordRecoveryRecovery info of a 2FA password, only for accounts with a recovery email configured.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
auth.requestPasswordRecoveryRequest recovery code of a 2FA password, only for accounts with a recovery email configured.
-

Related pages

-

Two-factor authentication

-

How to login to a user's account if they have enabled 2FA, how to change password.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/auth.SentCode b/data/corefork.telegram.org/type/auth.SentCode deleted file mode 100644 index 8c4404559d..0000000000 --- a/data/corefork.telegram.org/type/auth.SentCode +++ /dev/null @@ -1,183 +0,0 @@ - - - - - auth.SentCode - - - - - - - - - - - - - -
- -
-
-
- -

auth.SentCode

- -

Contains info on a confirmation code message sent via SMS, phone call or Telegram.

-

- -
-
auth.sentCode#5e002502 flags:# type:auth.SentCodeType phone_code_hash:string next_type:flags.1?auth.CodeType timeout:flags.2?int = auth.SentCode;
-
----functions---
-
-auth.sendCode#a677244f phone_number:string api_id:int api_hash:string settings:CodeSettings = auth.SentCode;
-auth.resendCode#3ef1a9bf phone_number:string phone_code_hash:string = auth.SentCode;
-
-account.sendChangePhoneCode#82574ae5 phone_number:string settings:CodeSettings = auth.SentCode;
-account.sendConfirmPhoneCode#1b3faa88 hash:string settings:CodeSettings = auth.SentCode;
-account.sendVerifyPhoneCode#a5a356f9 phone_number:string settings:CodeSettings = auth.SentCode;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
auth.sentCodeContains info about a sent verification code.
-

Methods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
MethodDescription
auth.sendCodeSend the verification code for login
account.sendChangePhoneCodeVerify a new phone number to associate to the current account
auth.resendCodeResend the login code via another medium, the phone code type is determined by the return value of the previous auth.sendCode/auth.resendCode: see login for more info.
account.sendConfirmPhoneCodeSend confirmation code to cancel account deletion, for more info click here »
account.sendVerifyPhoneCodeSend the verification phone code for telegram passport.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/bytes.html b/data/corefork.telegram.org/type/bytes.html deleted file mode 100644 index ab59a32b8c..0000000000 --- a/data/corefork.telegram.org/type/bytes.html +++ /dev/null @@ -1,125 +0,0 @@ - - - - - bytes - - - - - - - - - - - - - -
- -
-
-
- -

bytes

- -

Basic bare type. It is an alias of the string type, with the difference that the value may contain arbitrary byte sequences, including invalid UTF-8 sequences.

-

When computing crc32 for a constructor or method it is necessary to replace all byte types with string types.

-

Related pages

-

string

-

A basic bare type. Values of type string look differently depending on the length L of the string being serialized:

-
    -
  • If L <= 253, the serialization contains one byte with the value of L, then L bytes of the string followed by 0 to 3 characters containing 0, such that the overall length of the value be divisible by 4, whereupon all of this is interpreted as a sequence of int(L/4)+1 32-bit little-endian integers.
  • -
  • If L >= 254, the serialization contains byte 254, followed by 3 bytes with the string length L in little-endian order, followed by L bytes of the string, further followed by 0 to 3 null padding bytes.
  • -
-

All strings passed to the API must be encoded in UTF-8. When arbitrary byte sequences have to be serialized, bytes alias is to be used.

-

Further details on basic types»

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/channels.AdminLogResults b/data/corefork.telegram.org/type/channels.AdminLogResults deleted file mode 100644 index d6d47e0a1b..0000000000 --- a/data/corefork.telegram.org/type/channels.AdminLogResults +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Channels.AdminLogResults - - - - - - - - - - - - - -
- -
-
-
- -

Channels.AdminLogResults

- -

Admin log events

-

- -
-
channels.adminLogResults#ed8af74d events:Vector<ChannelAdminLogEvent> chats:Vector<Chat> users:Vector<User> = channels.AdminLogResults;
-
----functions---
-
-channels.getAdminLog#33ddf480 flags:# channel:InputChannel q:string events_filter:flags.0?ChannelAdminLogEventsFilter admins:flags.1?Vector<InputUser> max_id:long min_id:long limit:int = channels.AdminLogResults;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
channels.adminLogResultsAdmin log events
-

Methods

- - - - - - - - - - - - - -
MethodDescription
channels.getAdminLogGet the admin log of a channel/supergroup
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/channels.ChannelParticipant b/data/corefork.telegram.org/type/channels.ChannelParticipant deleted file mode 100644 index a9f1078a28..0000000000 --- a/data/corefork.telegram.org/type/channels.ChannelParticipant +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Channels.ChannelParticipant - - - - - - - - - - - - - -
- -
-
-
- -

Channels.ChannelParticipant

- -

Channel participant

-

- -
-
channels.channelParticipant#dfb80317 participant:ChannelParticipant chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipant;
-
----functions---
-
-channels.getParticipant#a0ab6cc6 channel:InputChannel participant:InputPeer = channels.ChannelParticipant;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
channels.channelParticipantRepresents a channel participant
-

Methods

- - - - - - - - - - - - - -
MethodDescription
channels.getParticipantGet info about a channel/supergroup participant
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/channels.ChannelParticipants b/data/corefork.telegram.org/type/channels.ChannelParticipants deleted file mode 100644 index fd69f5cf9f..0000000000 --- a/data/corefork.telegram.org/type/channels.ChannelParticipants +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Channels.ChannelParticipants - - - - - - - - - - - - - -
- -
-
-
- -

Channels.ChannelParticipants

- -

Channel/supergroup participants

-

- -
-
channels.channelParticipants#9ab0feaf count:int participants:Vector<ChannelParticipant> chats:Vector<Chat> users:Vector<User> = channels.ChannelParticipants;
-channels.channelParticipantsNotModified#f0173fe9 = channels.ChannelParticipants;
-
----functions---
-
-channels.getParticipants#77ced9d0 channel:InputChannel filter:ChannelParticipantsFilter offset:int limit:int hash:long = channels.ChannelParticipants;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
channels.channelParticipantsRepresents multiple channel participants
channels.channelParticipantsNotModifiedNo new participant info could be found
-

Methods

- - - - - - - - - - - - - -
MethodDescription
channels.getParticipantsGet the participants of a channel
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/contacts.Blocked b/data/corefork.telegram.org/type/contacts.Blocked deleted file mode 100644 index adc23e3865..0000000000 --- a/data/corefork.telegram.org/type/contacts.Blocked +++ /dev/null @@ -1,167 +0,0 @@ - - - - - contacts.Blocked - - - - - - - - - - - - - -
- -
-
-
- -

contacts.Blocked

- -

Info on users from the current user's black list.

-

- -
-
contacts.blocked#ade1591 blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
-contacts.blockedSlice#e1664194 count:int blocked:Vector<PeerBlocked> chats:Vector<Chat> users:Vector<User> = contacts.Blocked;
-
----functions---
-
-contacts.getBlocked#f57c350f offset:int limit:int = contacts.Blocked;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
contacts.blockedFull list of blocked users.
contacts.blockedSliceIncomplete list of blocked users.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
contacts.getBlockedReturns the list of blocked users.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/contacts.Contacts b/data/corefork.telegram.org/type/contacts.Contacts deleted file mode 100644 index 972fc3ab8d..0000000000 --- a/data/corefork.telegram.org/type/contacts.Contacts +++ /dev/null @@ -1,167 +0,0 @@ - - - - - contacts.Contacts - - - - - - - - - - - - - -
- -
-
-
- -

contacts.Contacts

- -

Info on the current user's contact list.

-

- -
-
contacts.contactsNotModified#b74ba9d2 = contacts.Contacts;
-contacts.contacts#eae87e42 contacts:Vector<Contact> saved_count:int users:Vector<User> = contacts.Contacts;
-
----functions---
-
-contacts.getContacts#5dd69e12 hash:long = contacts.Contacts;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
contacts.contactsNotModifiedContact list on the server is the same as the list on the client.
contacts.contactsThe current user's contact list and info on users.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
contacts.getContactsReturns the current user's contact list.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/contacts.Found b/data/corefork.telegram.org/type/contacts.Found deleted file mode 100644 index 1983cc5ad1..0000000000 --- a/data/corefork.telegram.org/type/contacts.Found +++ /dev/null @@ -1,162 +0,0 @@ - - - - - contacts.Found - - - - - - - - - - - - - -
- -
-
-
- -

contacts.Found

- -

Object contains info on users found by name substring and auxiliary data.

-

- -
-
contacts.found#b3134d9d my_results:Vector<Peer> results:Vector<Peer> chats:Vector<Chat> users:Vector<User> = contacts.Found;
-
----functions---
-
-contacts.search#11f812d8 q:string limit:int = contacts.Found;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
contacts.foundUsers found by name substring and auxiliary data.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
contacts.searchReturns users found by username substring.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/contacts.ImportedContacts b/data/corefork.telegram.org/type/contacts.ImportedContacts deleted file mode 100644 index 0d86c881ab..0000000000 --- a/data/corefork.telegram.org/type/contacts.ImportedContacts +++ /dev/null @@ -1,162 +0,0 @@ - - - - - contacts.ImportedContacts - - - - - - - - - - - - - -
- -
-
-
- -

contacts.ImportedContacts

- -

Object contains info on succesfully imported contacts.

-

- -
-
contacts.importedContacts#77d01c3b imported:Vector<ImportedContact> popular_invites:Vector<PopularContact> retry_contacts:Vector<long> users:Vector<User> = contacts.ImportedContacts;
-
----functions---
-
-contacts.importContacts#2c800be5 contacts:Vector<InputContact> = contacts.ImportedContacts;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
contacts.importedContactsInfo on succesfully imported contacts.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
contacts.importContactsImports contacts: saves a full list on the server, adds already registered contacts to the contact list, returns added contacts and their info.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/contacts.Link b/data/corefork.telegram.org/type/contacts.Link deleted file mode 100644 index 0353c300cb..0000000000 --- a/data/corefork.telegram.org/type/contacts.Link +++ /dev/null @@ -1,128 +0,0 @@ - - - - - contacts.Link - - - - - - - - - - - - - -
- -
-
-
- -

contacts.Link

- -

Object describes the connection between a certain user and the current authorized user.

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/contacts.ResolvedPeer b/data/corefork.telegram.org/type/contacts.ResolvedPeer deleted file mode 100644 index fd5592237e..0000000000 --- a/data/corefork.telegram.org/type/contacts.ResolvedPeer +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Contacts.ResolvedPeer - - - - - - - - - - - - - -
- -
-
-
- -

Contacts.ResolvedPeer

- -

Peer returned after resolving a @username

-

- -
-
contacts.resolvedPeer#7f077ad9 peer:Peer chats:Vector<Chat> users:Vector<User> = contacts.ResolvedPeer;
-
----functions---
-
-contacts.resolveUsername#f93ccba3 username:string = contacts.ResolvedPeer;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
contacts.resolvedPeerResolved peer
-

Methods

- - - - - - - - - - - - - -
MethodDescription
contacts.resolveUsernameResolve a @username to get peer info
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/contacts.TopPeers b/data/corefork.telegram.org/type/contacts.TopPeers deleted file mode 100644 index 2c00e71687..0000000000 --- a/data/corefork.telegram.org/type/contacts.TopPeers +++ /dev/null @@ -1,172 +0,0 @@ - - - - - Contacts.TopPeers - - - - - - - - - - - - - -
- -
-
-
- -

Contacts.TopPeers

- -

Top peers

-

- -
-
contacts.topPeersNotModified#de266ef5 = contacts.TopPeers;
-contacts.topPeers#70b772a8 categories:Vector<TopPeerCategoryPeers> chats:Vector<Chat> users:Vector<User> = contacts.TopPeers;
-contacts.topPeersDisabled#b52c939d = contacts.TopPeers;
-
----functions---
-
-contacts.getTopPeers#973478b6 flags:# correspondents:flags.0?true bots_pm:flags.1?true bots_inline:flags.2?true phone_calls:flags.3?true forward_users:flags.4?true forward_chats:flags.5?true groups:flags.10?true channels:flags.15?true offset:int limit:int hash:long = contacts.TopPeers;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
contacts.topPeersNotModifiedTop peer info hasn't changed
contacts.topPeersTop peers
contacts.topPeersDisabledTop peers disabled
-

Methods

- - - - - - - - - - - - - -
MethodDescription
contacts.getTopPeersGet most used peers
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/double.html b/data/corefork.telegram.org/type/double.html deleted file mode 100644 index 08d7f11dc1..0000000000 --- a/data/corefork.telegram.org/type/double.html +++ /dev/null @@ -1,118 +0,0 @@ - - - - - double - - - - - - - - - - - - - -
- -
-
-
- -

double

- -

A basic bare type, values of which correspond two-element sequences containing 64-bit real numbers in a standard double format.

-

More on basic types»

-

Related pages

-

Binary Data Serialization

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/help.AppUpdate b/data/corefork.telegram.org/type/help.AppUpdate deleted file mode 100644 index 0a65ac7d90..0000000000 --- a/data/corefork.telegram.org/type/help.AppUpdate +++ /dev/null @@ -1,167 +0,0 @@ - - - - - help.AppUpdate - - - - - - - - - - - - - -
- -
-
-
- -

help.AppUpdate

- -

Contains info on app update availability.

-

- -
-
help.appUpdate#ccbbce30 flags:# can_not_skip:flags.0?true id:int version:string text:string entities:Vector<MessageEntity> document:flags.1?Document url:flags.2?string sticker:flags.3?Document = help.AppUpdate;
-help.noAppUpdate#c45a6536 = help.AppUpdate;
-
----functions---
-
-help.getAppUpdate#522d5a7d source:string = help.AppUpdate;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
help.appUpdateAn update is available for the application.
help.noAppUpdateNo updates are available for the application.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getAppUpdateReturns information on update availability for the current application.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/help.CountriesList b/data/corefork.telegram.org/type/help.CountriesList deleted file mode 100644 index 9ccbe3777e..0000000000 --- a/data/corefork.telegram.org/type/help.CountriesList +++ /dev/null @@ -1,167 +0,0 @@ - - - - - help.CountriesList - - - - - - - - - - - - - -
- -
-
-
- -

help.CountriesList

- -

Name, ISO code, localized name and phone codes/patterns of all available countries

-

- -
-
help.countriesListNotModified#93cc1f32 = help.CountriesList;
-help.countriesList#87d0759e countries:Vector<help.Country> hash:int = help.CountriesList;
-
----functions---
-
-help.getCountriesList#735787a8 lang_code:string hash:int = help.CountriesList;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
help.countriesListNotModifiedThe country list has not changed
help.countriesListName, ISO code, localized name and phone codes/patterns of all available countries
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getCountriesListGet name, ISO code, localized name and phone codes/patterns of all available countries
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/help.Country b/data/corefork.telegram.org/type/help.Country deleted file mode 100644 index 7bb25ce07d..0000000000 --- a/data/corefork.telegram.org/type/help.Country +++ /dev/null @@ -1,143 +0,0 @@ - - - - - help.Country - - - - - - - - - - - - - -
- -
-
-
- -

help.Country

- -

Name, ISO code, localized name and phone codes/patterns of a specific country

-

- -
-
help.country#c3878e23 flags:# hidden:flags.0?true iso2:string default_name:string name:flags.1?string country_codes:Vector<help.CountryCode> = help.Country;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
help.countryName, ISO code, localized name and phone codes/patterns of a specific country
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/help.CountryCode b/data/corefork.telegram.org/type/help.CountryCode deleted file mode 100644 index 25c7cd77b2..0000000000 --- a/data/corefork.telegram.org/type/help.CountryCode +++ /dev/null @@ -1,143 +0,0 @@ - - - - - help.CountryCode - - - - - - - - - - - - - -
- -
-
-
- -

help.CountryCode

- -

Country code and phone number pattern of a specific country

-

- -
-
help.countryCode#4203c5ef flags:# country_code:string prefixes:flags.0?Vector<string> patterns:flags.1?Vector<string> = help.CountryCode;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
help.countryCodeCountry code and phone number pattern of a specific country
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/help.DeepLinkInfo b/data/corefork.telegram.org/type/help.DeepLinkInfo deleted file mode 100644 index 2102d2bf51..0000000000 --- a/data/corefork.telegram.org/type/help.DeepLinkInfo +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Help.DeepLinkInfo - - - - - - - - - - - - - -
- -
-
-
- -

Help.DeepLinkInfo

- -

Contains information about a tg:// deep link

-

- -
-
help.deepLinkInfoEmpty#66afa166 = help.DeepLinkInfo;
-help.deepLinkInfo#6a4ee832 flags:# update_app:flags.0?true message:string entities:flags.1?Vector<MessageEntity> = help.DeepLinkInfo;
-
----functions---
-
-help.getDeepLinkInfo#3fedc75f path:string = help.DeepLinkInfo;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
help.deepLinkInfoEmptyDeep link info empty
help.deepLinkInfoDeep linking info
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getDeepLinkInfoGet info about a t.me link
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/help.InviteText b/data/corefork.telegram.org/type/help.InviteText deleted file mode 100644 index 8ad5222b4d..0000000000 --- a/data/corefork.telegram.org/type/help.InviteText +++ /dev/null @@ -1,162 +0,0 @@ - - - - - help.InviteText - - - - - - - - - - - - - -
- -
-
-
- -

help.InviteText

- -

Object contains info on the text of a message with an invitation.

-

- -
-
help.inviteText#18cb9f78 message:string = help.InviteText;
-
----functions---
-
-help.getInviteText#4d392343 = help.InviteText;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
help.inviteTextText of a text message with an invitation to install application.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getInviteTextReturns text of a text message with an invitation.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/help.PassportConfig b/data/corefork.telegram.org/type/help.PassportConfig deleted file mode 100644 index 262833152d..0000000000 --- a/data/corefork.telegram.org/type/help.PassportConfig +++ /dev/null @@ -1,169 +0,0 @@ - - - - - Help.PassportConfig - - - - - - - - - - - - - -
- -
-
-
- -

Help.PassportConfig

- -

Telegram passport configuration

-

- -
-
help.passportConfigNotModified#bfb9f457 = help.PassportConfig;
-help.passportConfig#a098d6af hash:int countries_langs:DataJSON = help.PassportConfig;
-
----functions---
-
-help.getPassportConfig#c661ad08 hash:int = help.PassportConfig;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
help.passportConfigNotModifiedPassword configuration not modified
help.passportConfigTelegram passport configuration
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getPassportConfigGet passport configuration
-

Related pages

-

Telegram Passport Manual

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/help.PromoData b/data/corefork.telegram.org/type/help.PromoData deleted file mode 100644 index 3257063f03..0000000000 --- a/data/corefork.telegram.org/type/help.PromoData +++ /dev/null @@ -1,167 +0,0 @@ - - - - - help.PromoData - - - - - - - - - - - - - -
- -
-
-
- -

help.PromoData

- -

Info about pinned MTProxy or Public Service Announcement peers.

-

- -
-
help.promoDataEmpty#98f6ac75 expires:int = help.PromoData;
-help.promoData#8c39793f flags:# proxy:flags.0?true expires:int peer:Peer chats:Vector<Chat> users:Vector<User> psa_type:flags.1?string psa_message:flags.2?string = help.PromoData;
-
----functions---
-
-help.getPromoData#c0977421 = help.PromoData;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
help.promoDataEmptyNo PSA/MTProxy info is available
help.promoDataMTProxy/Public Service Announcement information
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getPromoDataGet MTProxy/Public Service Announcement information
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/help.ProxyData b/data/corefork.telegram.org/type/help.ProxyData deleted file mode 100644 index 9a47fb9c7c..0000000000 --- a/data/corefork.telegram.org/type/help.ProxyData +++ /dev/null @@ -1,130 +0,0 @@ - - - - - Help.ProxyData - - - - - - - - - - - - - -
- -
-
-
- -

Help.ProxyData

- -

Info about an MTProxy

-

- -
-

-

Related pages

-

MTProto transports

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/help.RecentMeUrls b/data/corefork.telegram.org/type/help.RecentMeUrls deleted file mode 100644 index e9d0af3864..0000000000 --- a/data/corefork.telegram.org/type/help.RecentMeUrls +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Help.RecentMeUrls - - - - - - - - - - - - - -
- -
-
-
- -

Help.RecentMeUrls

- -

Recent t.me URLs

-

- -
-
help.recentMeUrls#e0310d7 urls:Vector<RecentMeUrl> chats:Vector<Chat> users:Vector<User> = help.RecentMeUrls;
-
----functions---
-
-help.getRecentMeUrls#3dc0f114 referer:string = help.RecentMeUrls;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
help.recentMeUrlsRecent t.me URLs
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getRecentMeUrlsGet recently used t.me links
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/help.Support b/data/corefork.telegram.org/type/help.Support deleted file mode 100644 index ad6b827857..0000000000 --- a/data/corefork.telegram.org/type/help.Support +++ /dev/null @@ -1,162 +0,0 @@ - - - - - help.Support - - - - - - - - - - - - - -
- -
-
-
- -

help.Support

- -

Info about the support user, relevant to the current user.

-

- -
-
help.support#17c6b5f6 phone_number:string user:User = help.Support;
-
----functions---
-
-help.getSupport#9cdf08cd = help.Support;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
help.supportInfo on support user.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getSupportReturns the support user for the 'ask a question' feature.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/help.SupportName b/data/corefork.telegram.org/type/help.SupportName deleted file mode 100644 index d460466170..0000000000 --- a/data/corefork.telegram.org/type/help.SupportName +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Help.SupportName - - - - - - - - - - - - - -
- -
-
-
- -

Help.SupportName

- -

Get localized name for support user

-

- -
-
help.supportName#8c05f1c9 name:string = help.SupportName;
-
----functions---
-
-help.getSupportName#d360e72c = help.SupportName;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
help.supportNameLocalized name for telegram support
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getSupportNameGet localized name of the telegram support user
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/help.TermsOfService b/data/corefork.telegram.org/type/help.TermsOfService deleted file mode 100644 index 36c97f6061..0000000000 --- a/data/corefork.telegram.org/type/help.TermsOfService +++ /dev/null @@ -1,143 +0,0 @@ - - - - - help.TermsOfService - - - - - - - - - - - - - -
- -
-
-
- -

help.TermsOfService

- -

Contains info about the latest telegram Terms Of Service.

-

- -
-
help.termsOfService#780a0310 flags:# popup:flags.0?true id:DataJSON text:string entities:Vector<MessageEntity> min_age_confirm:flags.1?int = help.TermsOfService;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
help.termsOfServiceInfo about the latest telegram Terms Of Service
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/help.TermsOfServiceUpdate b/data/corefork.telegram.org/type/help.TermsOfServiceUpdate deleted file mode 100644 index dbd87c5c5d..0000000000 --- a/data/corefork.telegram.org/type/help.TermsOfServiceUpdate +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Help.TermsOfServiceUpdate - - - - - - - - - - - - - -
- -
-
-
- -

Help.TermsOfServiceUpdate

- -

Update of Telegram's terms of service

-

- -
-
help.termsOfServiceUpdateEmpty#e3309f7f expires:int = help.TermsOfServiceUpdate;
-help.termsOfServiceUpdate#28ecf961 expires:int terms_of_service:help.TermsOfService = help.TermsOfServiceUpdate;
-
----functions---
-
-help.getTermsOfServiceUpdate#2ca51fd1 = help.TermsOfServiceUpdate;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
help.termsOfServiceUpdateEmptyNo changes were made to telegram's terms of service
help.termsOfServiceUpdateInfo about an update of telegram's terms of service. If the terms of service are declined, then the account.deleteAccount method should be called with the reason "Decline ToS update"
-

Methods

- - - - - - - - - - - - - -
MethodDescription
help.getTermsOfServiceUpdateLook for updates of telegram's terms of service
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/help.UserInfo b/data/corefork.telegram.org/type/help.UserInfo deleted file mode 100644 index 304f6dce1b..0000000000 --- a/data/corefork.telegram.org/type/help.UserInfo +++ /dev/null @@ -1,172 +0,0 @@ - - - - - Help.UserInfo - - - - - - - - - - - - - -
- -
-
-
- -

Help.UserInfo

- -

User info

-

- -
-
help.userInfoEmpty#f3ae2eed = help.UserInfo;
-help.userInfo#1eb3758 message:string entities:Vector<MessageEntity> author:string date:int = help.UserInfo;
-
----functions---
-
-help.getUserInfo#38a08d3 user_id:InputUser = help.UserInfo;
-help.editUserInfo#66b91b70 user_id:InputUser message:string entities:Vector<MessageEntity> = help.UserInfo;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
help.userInfoEmptyInternal use
help.userInfoInternal use
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
help.getUserInfoInternal use
help.editUserInfoInternal use
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/int.html b/data/corefork.telegram.org/type/int.html deleted file mode 100644 index 33e5c81299..0000000000 --- a/data/corefork.telegram.org/type/int.html +++ /dev/null @@ -1,118 +0,0 @@ - - - - - int - - - - - - - - - - - - - -
- -
-
-
- -

int

- -

A basic bare type, the values of which correspond to single-element sequences, i.e. numbers from -2^31 to 2^31-1 which in this case represent themselves.

-

More on basic types »

-

Related pages

-

Binary Data Serialization

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/long.html b/data/corefork.telegram.org/type/long.html deleted file mode 100644 index f36446d0dc..0000000000 --- a/data/corefork.telegram.org/type/long.html +++ /dev/null @@ -1,118 +0,0 @@ - - - - - long - - - - - - - - - - - - - -
- -
-
-
- -

long

- -

A basic bare type, elements of which correspond to two-element sequences, representing 64-bit signed numbers (little-endian).

-

More on basic types »

-

Related pages

-

Binary Data Serialization

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.AffectedFoundMessages b/data/corefork.telegram.org/type/messages.AffectedFoundMessages deleted file mode 100644 index 4f110b37f7..0000000000 --- a/data/corefork.telegram.org/type/messages.AffectedFoundMessages +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.AffectedFoundMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.AffectedFoundMessages

- -

Messages found and affected by changes

-

- -
-
messages.affectedFoundMessages#ef8d3e6c pts:int pts_count:int offset:int messages:Vector<int> = messages.AffectedFoundMessages;
-
----functions---
-
-messages.deletePhoneCallHistory#f9cbe409 flags:# revoke:flags.0?true = messages.AffectedFoundMessages;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.affectedFoundMessagesMessages found and affected by changes
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.deletePhoneCallHistoryDelete the phone call history with a user
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.AffectedHistory b/data/corefork.telegram.org/type/messages.AffectedHistory deleted file mode 100644 index ff2e529d91..0000000000 --- a/data/corefork.telegram.org/type/messages.AffectedHistory +++ /dev/null @@ -1,178 +0,0 @@ - - - - - messages.AffectedHistory - - - - - - - - - - - - - -
- -
-
-
- -

messages.AffectedHistory

- -

Object contains info on affected part of communication history with the user or in a chat.

-

- -
-
messages.affectedHistory#b45c69d1 pts:int pts_count:int offset:int = messages.AffectedHistory;
-
----functions---
-
-messages.deleteHistory#1c015b09 flags:# just_clear:flags.0?true revoke:flags.1?true peer:InputPeer max_id:int = messages.AffectedHistory;
-messages.readMentions#f0189d3 peer:InputPeer = messages.AffectedHistory;
-messages.unpinAllMessages#f025bc8b peer:InputPeer = messages.AffectedHistory;
-
-channels.deleteUserHistory#d10dd71b channel:InputChannel user_id:InputUser = messages.AffectedHistory;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.affectedHistoryAffected part of communication history with the user or in a chat.
-

Methods

- - - - - - - - - - - - - - - - - - - - - - - - - -
MethodDescription
messages.deleteHistoryDeletes communication history.
channels.deleteUserHistoryDelete all messages sent by a certain user in a supergroup
messages.readMentionsMark mentions as read
messages.unpinAllMessagesUnpin all pinned messages
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.AffectedMessages b/data/corefork.telegram.org/type/messages.AffectedMessages deleted file mode 100644 index d2ab4bc2d6..0000000000 --- a/data/corefork.telegram.org/type/messages.AffectedMessages +++ /dev/null @@ -1,178 +0,0 @@ - - - - - Messages.AffectedMessages - - - - - - - - - - - - - -
- -
-
-
- -

Messages.AffectedMessages

- -

Messages affected by changes

-

- -
-
messages.affectedMessages#84d19185 pts:int pts_count:int = messages.AffectedMessages;
-
----functions---
-
-messages.readHistory#e306d3a peer:InputPeer max_id:int = messages.AffectedMessages;
-messages.deleteMessages#e58e95d2 flags:# revoke:flags.0?true id:Vector<int> = messages.AffectedMessages;
-messages.readMessageContents#36a73f77 id:Vector<int> = messages.AffectedMessages;
-
-channels.deleteMessages#84c1fd4e channel:InputChannel id:Vector<int> = messages.AffectedMessages;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.affectedMessagesEvents affected by operation
-

Methods

- - - - - - - - - - - - - - - - - - - - - - - - - -
MethodDescription
messages.readHistoryMarks message history as read.
messages.deleteMessagesDeletes messages by their identifiers.
messages.readMessageContentsNotifies the sender about the recipient having listened a voice message or watched a video.
channels.deleteMessagesDelete messages in a channel/supergroup
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.AllStickers b/data/corefork.telegram.org/type/messages.AllStickers deleted file mode 100644 index 1472d82e95..0000000000 --- a/data/corefork.telegram.org/type/messages.AllStickers +++ /dev/null @@ -1,172 +0,0 @@ - - - - - Messages.AllStickers - - - - - - - - - - - - - -
- -
-
-
- -

Messages.AllStickers

- -

All stickers

-

- -
-
messages.allStickersNotModified#e86602c3 = messages.AllStickers;
-messages.allStickers#cdbbcebb hash:long sets:Vector<StickerSet> = messages.AllStickers;
-
----functions---
-
-messages.getAllStickers#b8a0a1a8 hash:long = messages.AllStickers;
-messages.getMaskStickers#640f82b8 hash:long = messages.AllStickers;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.allStickersNotModifiedInfo about all installed stickers hasn't changed
messages.allStickersInfo about all installed stickers
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
messages.getAllStickersGet all installed stickers
messages.getMaskStickersGet installed mask stickers
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.ArchivedStickers b/data/corefork.telegram.org/type/messages.ArchivedStickers deleted file mode 100644 index 6744c08eb6..0000000000 --- a/data/corefork.telegram.org/type/messages.ArchivedStickers +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Messages.ArchivedStickers - - - - - - - - - - - - - -
- -
-
-
- -

Messages.ArchivedStickers

- -

Archived stickers

-

- -
-
messages.archivedStickers#4fcba9c8 count:int sets:Vector<StickerSetCovered> = messages.ArchivedStickers;
-
----functions---
-
-messages.getArchivedStickers#57f17692 flags:# masks:flags.0?true offset_id:long limit:int = messages.ArchivedStickers;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.archivedStickersArchived stickersets
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getArchivedStickersGet all archived stickers
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.BotCallbackAnswer b/data/corefork.telegram.org/type/messages.BotCallbackAnswer deleted file mode 100644 index 89facc5d6d..0000000000 --- a/data/corefork.telegram.org/type/messages.BotCallbackAnswer +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Messages.BotCallbackAnswer - - - - - - - - - - - - - -
- -
-
-
- -

Messages.BotCallbackAnswer

- -

Callback answer of bot

-

- -
-
messages.botCallbackAnswer#36585ea4 flags:# alert:flags.1?true has_url:flags.3?true native_ui:flags.4?true message:flags.0?string url:flags.2?string cache_time:int = messages.BotCallbackAnswer;
-
----functions---
-
-messages.getBotCallbackAnswer#9342ca07 flags:# game:flags.1?true peer:InputPeer msg_id:int data:flags.0?bytes password:flags.2?InputCheckPasswordSRP = messages.BotCallbackAnswer;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.botCallbackAnswerCallback answer sent by the bot in response to a button press
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getBotCallbackAnswerPress an inline callback button and get a callback answer from the bot
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.BotResults b/data/corefork.telegram.org/type/messages.BotResults deleted file mode 100644 index c415fe94ee..0000000000 --- a/data/corefork.telegram.org/type/messages.BotResults +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.BotResults - - - - - - - - - - - - - -
- -
-
-
- -

messages.BotResults

- -

Result of a query to an inline bot

-

- -
-
messages.botResults#947ca848 flags:# gallery:flags.0?true query_id:long next_offset:flags.1?string switch_pm:flags.2?InlineBotSwitchPM results:Vector<BotInlineResult> cache_time:int users:Vector<User> = messages.BotResults;
-
----functions---
-
-messages.getInlineBotResults#514e999d flags:# bot:InputUser peer:InputPeer geo_point:flags.0?InputGeoPoint query:string offset:string = messages.BotResults;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.botResultsResult of a query to an inline bot
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getInlineBotResultsQuery an inline bot
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.ChatAdminsWithInvites b/data/corefork.telegram.org/type/messages.ChatAdminsWithInvites deleted file mode 100644 index 164342f3f0..0000000000 --- a/data/corefork.telegram.org/type/messages.ChatAdminsWithInvites +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.ChatAdminsWithInvites - - - - - - - - - - - - - -
- -
-
-
- -

messages.ChatAdminsWithInvites

- -

Info about chat invites generated by admins.

-

- -
-
messages.chatAdminsWithInvites#b69b72d7 admins:Vector<ChatAdminWithInvites> users:Vector<User> = messages.ChatAdminsWithInvites;
-
----functions---
-
-messages.getAdminsWithInvites#3920e6ef peer:InputPeer = messages.ChatAdminsWithInvites;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.chatAdminsWithInvitesInfo about chat invites generated by admins.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getAdminsWithInvitesGet info about chat invites generated by admins.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.ChatFull b/data/corefork.telegram.org/type/messages.ChatFull deleted file mode 100644 index 63ad4819c0..0000000000 --- a/data/corefork.telegram.org/type/messages.ChatFull +++ /dev/null @@ -1,168 +0,0 @@ - - - - - messages.ChatFull - - - - - - - - - - - - - -
- -
-
-
- -

messages.ChatFull

- -

Object contains extended info on chat with auxiliary data.

-

- -
-
messages.chatFull#e5d7d19c full_chat:ChatFull chats:Vector<Chat> users:Vector<User> = messages.ChatFull;
-
----functions---
-
-messages.getFullChat#aeb00b34 chat_id:long = messages.ChatFull;
-
-channels.getFullChannel#8736a09 channel:InputChannel = messages.ChatFull;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.chatFullExtended info on chat and auxiliary data.
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
messages.getFullChatReturns full chat info according to its ID.
channels.getFullChannelGet full info about a channel
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.ChatInviteImporters b/data/corefork.telegram.org/type/messages.ChatInviteImporters deleted file mode 100644 index d0962ed617..0000000000 --- a/data/corefork.telegram.org/type/messages.ChatInviteImporters +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.ChatInviteImporters - - - - - - - - - - - - - -
- -
-
-
- -

messages.ChatInviteImporters

- -

List of users that imported a chat invitation link.

-

- -
-
messages.chatInviteImporters#81b6b00a count:int importers:Vector<ChatInviteImporter> users:Vector<User> = messages.ChatInviteImporters;
-
----functions---
-
-messages.getChatInviteImporters#26fb7289 peer:InputPeer link:string offset_date:int offset_user:InputUser limit:int = messages.ChatInviteImporters;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.chatInviteImportersInfo about the users that joined the chat using a specific chat invite
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getChatInviteImportersGet info about the users that joined the chat using a specific chat invite
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.Chats b/data/corefork.telegram.org/type/messages.Chats deleted file mode 100644 index 906d8e7425..0000000000 --- a/data/corefork.telegram.org/type/messages.Chats +++ /dev/null @@ -1,198 +0,0 @@ - - - - - messages.Chats - - - - - - - - - - - - - -
- -
-
-
- -

messages.Chats

- -

Object contains list of chats with auxiliary data.

-

- -
-
messages.chats#64ff9fd5 chats:Vector<Chat> = messages.Chats;
-messages.chatsSlice#9cd81144 count:int chats:Vector<Chat> = messages.Chats;
-
----functions---
-
-messages.getChats#49e9528f id:Vector<long> = messages.Chats;
-messages.getCommonChats#e40ca104 user_id:InputUser max_id:long limit:int = messages.Chats;
-messages.getAllChats#875f74be except_ids:Vector<long> = messages.Chats;
-
-channels.getChannels#a7f6bbb id:Vector<InputChannel> = messages.Chats;
-channels.getAdminedPublicChannels#f8b036af flags:# by_location:flags.0?true check_limit:flags.1?true = messages.Chats;
-channels.getLeftChannels#8341ecc0 offset:int = messages.Chats;
-channels.getGroupsForDiscussion#f5dad378 = messages.Chats;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.chatsList of chats with auxiliary data.
messages.chatsSlicePartial list of chats, more would have to be fetched with pagination
-

Methods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
MethodDescription
messages.getChatsReturns chat basic info on their IDs.
channels.getChannelsGet info about channels/supergroups
channels.getAdminedPublicChannelsGet channels/supergroups/geogroups we're admin in. Usually called when the user exceeds the limit for owned public channels/supergroups/geogroups, and the user is given the choice to remove one of his channels/supergroups/geogroups.
messages.getCommonChatsGet chats in common with a user
messages.getAllChatsGet all chats, channels and supergroups
channels.getLeftChannelsGet a list of channels/supergroups we left
channels.getGroupsForDiscussionGet all groups that can be used as discussion groups
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.CheckedHistoryImportPeer b/data/corefork.telegram.org/type/messages.CheckedHistoryImportPeer deleted file mode 100644 index 84ce7b8c61..0000000000 --- a/data/corefork.telegram.org/type/messages.CheckedHistoryImportPeer +++ /dev/null @@ -1,165 +0,0 @@ - - - - - messages.CheckedHistoryImportPeer - - - - - - - - - - - - - -
- -
-
-
- -

messages.CheckedHistoryImportPeer

- -

Contains a confirmation text to be shown to the user, upon importing chat history, click here for more info ».

-

- -
-
messages.checkedHistoryImportPeer#a24de717 confirm_text:string = messages.CheckedHistoryImportPeer;
-
----functions---
-
-messages.checkHistoryImportPeer#5dc60f03 peer:InputPeer = messages.CheckedHistoryImportPeer;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.checkedHistoryImportPeerContains a confirmation text to be shown to the user, upon importing chat history.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.checkHistoryImportPeerCheck whether chat history exported from another chat app can be imported into a specific Telegram chat.

If the check succeeds, and no RPC errors are returned, a messages.CheckedHistoryImportPeer constructor will be returned, with a confirmation text to be shown to the user, before actually initializing the import.
-

Related pages

-

Imported messages

-

Telegram allows importing messages and media from foreign chat apps.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.DhConfig b/data/corefork.telegram.org/type/messages.DhConfig deleted file mode 100644 index 384999d67c..0000000000 --- a/data/corefork.telegram.org/type/messages.DhConfig +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Messages.DhConfig - - - - - - - - - - - - - -
- -
-
-
- -

Messages.DhConfig

- -

Contains info on cofiguring parameters for key generation by Diffie-Hellman protocol.

-

- -
-
messages.dhConfigNotModified#c0e24635 random:bytes = messages.DhConfig;
-messages.dhConfig#2c221edd g:int p:bytes version:int random:bytes = messages.DhConfig;
-
----functions---
-
-messages.getDhConfig#26cf8950 version:int random_length:int = messages.DhConfig;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.dhConfigNotModifiedConfiguring parameters did not change.
messages.dhConfigNew set of configuring parameters.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getDhConfigReturns configuration parameters for Diffie-Hellman key generation. Can also return a random sequence of bytes of required length.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.Dialogs b/data/corefork.telegram.org/type/messages.Dialogs deleted file mode 100644 index bdac069ab7..0000000000 --- a/data/corefork.telegram.org/type/messages.Dialogs +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.Dialogs - - - - - - - - - - - - - -
- -
-
-
- -

messages.Dialogs

- -

Object contains a list of chats with messages and auxiliary data.

-

- -
-
messages.dialogs#15ba6c40 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;
-messages.dialogsSlice#71e094f3 count:int dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Dialogs;
-messages.dialogsNotModified#f0e3e596 count:int = messages.Dialogs;
-
----functions---
-
-messages.getDialogs#a0f4cb4f flags:# exclude_pinned:flags.0?true folder_id:flags.1?int offset_date:int offset_id:int offset_peer:InputPeer limit:int hash:long = messages.Dialogs;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.dialogsFull list of chats with messages and auxiliary data.
messages.dialogsSliceIncomplete list of dialogs with messages and auxiliary data.
messages.dialogsNotModifiedDialogs haven't changed
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getDialogsReturns the current user dialog list.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.DiscussionMessage b/data/corefork.telegram.org/type/messages.DiscussionMessage deleted file mode 100644 index 1327fff791..0000000000 --- a/data/corefork.telegram.org/type/messages.DiscussionMessage +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.DiscussionMessage - - - - - - - - - - - - - -
- -
-
-
- -

messages.DiscussionMessage

- -

Info about a message thread

-

- -
-
messages.discussionMessage#a6341782 flags:# messages:Vector<Message> max_id:flags.0?int read_inbox_max_id:flags.1?int read_outbox_max_id:flags.2?int unread_count:int chats:Vector<Chat> users:Vector<User> = messages.DiscussionMessage;
-
----functions---
-
-messages.getDiscussionMessage#446972fd peer:InputPeer msg_id:int = messages.DiscussionMessage;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.discussionMessageInformation about a message thread
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getDiscussionMessageGet discussion message from the associated discussion group of a channel to show it on top of the comment section, without actually joining the group
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.ExportedChatInvite b/data/corefork.telegram.org/type/messages.ExportedChatInvite deleted file mode 100644 index 1d60af3e5a..0000000000 --- a/data/corefork.telegram.org/type/messages.ExportedChatInvite +++ /dev/null @@ -1,172 +0,0 @@ - - - - - messages.ExportedChatInvite - - - - - - - - - - - - - -
- -
-
-
- -

messages.ExportedChatInvite

- -

Contains info about a chat invite, and eventually a pointer to the newest chat invite.

-

- -
-
messages.exportedChatInvite#1871be50 invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
-messages.exportedChatInviteReplaced#222600ef invite:ExportedChatInvite new_invite:ExportedChatInvite users:Vector<User> = messages.ExportedChatInvite;
-
----functions---
-
-messages.getExportedChatInvite#73746f5c peer:InputPeer link:string = messages.ExportedChatInvite;
-messages.editExportedChatInvite#2e4ffbe flags:# revoked:flags.2?true peer:InputPeer link:string expire_date:flags.0?int usage_limit:flags.1?int = messages.ExportedChatInvite;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.exportedChatInviteInfo about a chat invite
messages.exportedChatInviteReplacedThe specified chat invite was replaced with another one
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
messages.getExportedChatInviteGet info about a chat invite
messages.editExportedChatInviteEdit an exported chat invite
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.ExportedChatInvites b/data/corefork.telegram.org/type/messages.ExportedChatInvites deleted file mode 100644 index cec73ddd15..0000000000 --- a/data/corefork.telegram.org/type/messages.ExportedChatInvites +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.ExportedChatInvites - - - - - - - - - - - - - -
- -
-
-
- -

messages.ExportedChatInvites

- -

Info about chat invites exported by a certain admin.

-

- -
-
messages.exportedChatInvites#bdc62dcc count:int invites:Vector<ExportedChatInvite> users:Vector<User> = messages.ExportedChatInvites;
-
----functions---
-
-messages.getExportedChatInvites#a2b5a3f6 flags:# revoked:flags.3?true peer:InputPeer admin_id:InputUser offset_date:flags.2?int offset_link:flags.2?string limit:int = messages.ExportedChatInvites;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.exportedChatInvitesInfo about chat invites exported by a certain admin.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getExportedChatInvitesGet info about the chat invites of a specific chat
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.FavedStickers b/data/corefork.telegram.org/type/messages.FavedStickers deleted file mode 100644 index fe5234fa16..0000000000 --- a/data/corefork.telegram.org/type/messages.FavedStickers +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Messages.FavedStickers - - - - - - - - - - - - - -
- -
-
-
- -

Messages.FavedStickers

- -

Favorited stickers

-

- -
-
messages.favedStickersNotModified#9e8fa6d3 = messages.FavedStickers;
-messages.favedStickers#2cb51097 hash:long packs:Vector<StickerPack> stickers:Vector<Document> = messages.FavedStickers;
-
----functions---
-
-messages.getFavedStickers#4f1aaa9 hash:long = messages.FavedStickers;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.favedStickersNotModifiedNo new favorited stickers were found
messages.favedStickersFavorited stickers
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getFavedStickersGet faved stickers
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.FeaturedStickers b/data/corefork.telegram.org/type/messages.FeaturedStickers deleted file mode 100644 index 760e7f6459..0000000000 --- a/data/corefork.telegram.org/type/messages.FeaturedStickers +++ /dev/null @@ -1,172 +0,0 @@ - - - - - Messages.FeaturedStickers - - - - - - - - - - - - - -
- -
-
-
- -

Messages.FeaturedStickers

- -

Featured stickers

-

- -
-
messages.featuredStickersNotModified#c6dc0c66 count:int = messages.FeaturedStickers;
-messages.featuredStickers#84c02310 hash:long count:int sets:Vector<StickerSetCovered> unread:Vector<long> = messages.FeaturedStickers;
-
----functions---
-
-messages.getFeaturedStickers#64780b14 hash:long = messages.FeaturedStickers;
-messages.getOldFeaturedStickers#7ed094a1 offset:int limit:int hash:long = messages.FeaturedStickers;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.featuredStickersNotModifiedFeatured stickers haven't changed
messages.featuredStickersFeatured stickersets
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
messages.getFeaturedStickersGet featured stickers
messages.getOldFeaturedStickersOld method for fetching featured sticker
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.FoundGifs b/data/corefork.telegram.org/type/messages.FoundGifs deleted file mode 100644 index 695812ca9c..0000000000 --- a/data/corefork.telegram.org/type/messages.FoundGifs +++ /dev/null @@ -1,128 +0,0 @@ - - - - - Messages.FoundGifs - - - - - - - - - - - - - -
- -
-
-
- -

Messages.FoundGifs

- -

Found GIFs

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.FoundStickerSets b/data/corefork.telegram.org/type/messages.FoundStickerSets deleted file mode 100644 index db41667d45..0000000000 --- a/data/corefork.telegram.org/type/messages.FoundStickerSets +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Messages.FoundStickerSets - - - - - - - - - - - - - -
- -
-
-
- -

Messages.FoundStickerSets

- -

Found stickersets

-

- -
-
messages.foundStickerSetsNotModified#d54b65d = messages.FoundStickerSets;
-messages.foundStickerSets#8af09dd2 hash:long sets:Vector<StickerSetCovered> = messages.FoundStickerSets;
-
----functions---
-
-messages.searchStickerSets#35705b8a flags:# exclude_featured:flags.0?true q:string hash:long = messages.FoundStickerSets;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.foundStickerSetsNotModifiedNo further results were found
messages.foundStickerSetsFound stickersets
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.searchStickerSetsSearch for stickersets
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.HighScores b/data/corefork.telegram.org/type/messages.HighScores deleted file mode 100644 index 09c9319a2f..0000000000 --- a/data/corefork.telegram.org/type/messages.HighScores +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Messages.HighScores - - - - - - - - - - - - - -
- -
-
-
- -

Messages.HighScores

- -

High scores (in games)

-

- -
-
messages.highScores#9a3bfd99 scores:Vector<HighScore> users:Vector<User> = messages.HighScores;
-
----functions---
-
-messages.getGameHighScores#e822649d peer:InputPeer id:int user_id:InputUser = messages.HighScores;
-messages.getInlineGameHighScores#f635e1b id:InputBotInlineMessageID user_id:InputUser = messages.HighScores;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.highScoresHighscores in a game
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
messages.getGameHighScoresGet highscores of a game
messages.getInlineGameHighScoresGet highscores of a game sent using an inline bot
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.HistoryImport b/data/corefork.telegram.org/type/messages.HistoryImport deleted file mode 100644 index 930fdcb56f..0000000000 --- a/data/corefork.telegram.org/type/messages.HistoryImport +++ /dev/null @@ -1,165 +0,0 @@ - - - - - messages.HistoryImport - - - - - - - - - - - - - -
- -
-
-
- -

messages.HistoryImport

- -

Identifier of a history import session, click here for more info ».

-

- -
-
messages.historyImport#1662af0b id:long = messages.HistoryImport;
-
----functions---
-
-messages.initHistoryImport#34090c3b peer:InputPeer file:InputFile media_count:int = messages.HistoryImport;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.historyImportID of a specific chat import session
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.initHistoryImportImport chat history from a foreign chat app into a specific Telegram chat.
Make sure to call messages.checkHistoryImportPeer, first, to make sure you have the rights to import history into this chat, and to show an additional confirmation prompt to the user with useful information returned by the RPC call.
Typically, history imports are allowed for private chats with a mutual contact or supergroups with change_info administrator rights ».

After initializing the history import process and uploading all media files associated with the chat using messages.uploadImportedMedia, call messages.startHistoryImport to complete the history import process, importing all messages into the chat.
-

Related pages

-

Imported messages

-

Telegram allows importing messages and media from foreign chat apps.

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.HistoryImportParsed b/data/corefork.telegram.org/type/messages.HistoryImportParsed deleted file mode 100644 index 7f318be8be..0000000000 --- a/data/corefork.telegram.org/type/messages.HistoryImportParsed +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.HistoryImportParsed - - - - - - - - - - - - - -
- -
-
-
- -

messages.HistoryImportParsed

- -

Contains information about a chat export file, generated by a foreign chat app.

-

- -
-
messages.historyImportParsed#5e0fb7b9 flags:# pm:flags.0?true group:flags.1?true title:flags.2?string = messages.HistoryImportParsed;
-
----functions---
-
-messages.checkHistoryImport#43fe19f3 import_head:string = messages.HistoryImportParsed;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.historyImportParsedContains information about a chat export file, generated by a foreign chat app. If neither the pm or group flags are set, the specified chat export was generated from a chat of unknown type.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.checkHistoryImportObtains information about a chat export file, generated by a foreign chat app.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.InactiveChats b/data/corefork.telegram.org/type/messages.InactiveChats deleted file mode 100644 index ae994a5af7..0000000000 --- a/data/corefork.telegram.org/type/messages.InactiveChats +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.InactiveChats - - - - - - - - - - - - - -
- -
-
-
- -

messages.InactiveChats

- -

Inactive chat list

-

- -
-
messages.inactiveChats#a927fec5 dates:Vector<int> chats:Vector<Chat> users:Vector<User> = messages.InactiveChats;
-
----functions---
-
-channels.getInactiveChannels#11e831ee = messages.InactiveChats;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.inactiveChatsInactive chat list
-

Methods

- - - - - - - - - - - - - -
MethodDescription
channels.getInactiveChannelsGet inactive channels and supergroups
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.MessageEditData b/data/corefork.telegram.org/type/messages.MessageEditData deleted file mode 100644 index 80118f8ba6..0000000000 --- a/data/corefork.telegram.org/type/messages.MessageEditData +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Messages.MessageEditData - - - - - - - - - - - - - -
- -
-
-
- -

Messages.MessageEditData

- -

Message edit data for media

-

- -
-
messages.messageEditData#26b5dde6 flags:# caption:flags.0?true = messages.MessageEditData;
-
----functions---
-
-messages.getMessageEditData#fda68d36 peer:InputPeer id:int = messages.MessageEditData;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.messageEditDataMessage edit data for media
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getMessageEditDataFind out if a media message's caption can be edited
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.MessageViews b/data/corefork.telegram.org/type/messages.MessageViews deleted file mode 100644 index b01091cca9..0000000000 --- a/data/corefork.telegram.org/type/messages.MessageViews +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.MessageViews - - - - - - - - - - - - - -
- -
-
-
- -

messages.MessageViews

- -

View, forward counter + info about replies

-

- -
-
messages.messageViews#b6c4f543 views:Vector<MessageViews> chats:Vector<Chat> users:Vector<User> = messages.MessageViews;
-
----functions---
-
-messages.getMessagesViews#5784d3e1 peer:InputPeer id:Vector<int> increment:Bool = messages.MessageViews;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.messageViewsView, forward counter + info about replies
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getMessagesViewsGet and increase the view counter of a message sent or forwarded from a channel
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.Messages b/data/corefork.telegram.org/type/messages.Messages deleted file mode 100644 index 10fcfcd5ca..0000000000 --- a/data/corefork.telegram.org/type/messages.Messages +++ /dev/null @@ -1,229 +0,0 @@ - - - - - messages.Messages - - - - - - - - - - - - - -
- -
-
-
- -

messages.Messages

- -

Object contains infor on list of messages with auxiliary data.

-

- -
-
messages.messages#8c718e87 messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesSlice#3a54685e flags:# inexact:flags.1?true count:int next_rate:flags.0?int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.channelMessages#64479808 flags:# inexact:flags.1?true pts:int count:int offset_id_offset:flags.2?int messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = messages.Messages;
-messages.messagesNotModified#74535f21 count:int = messages.Messages;
-
----functions---
-
-messages.getMessages#63c66506 id:Vector<InputMessage> = messages.Messages;
-messages.getHistory#4423e6c5 peer:InputPeer offset_id:int offset_date:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
-messages.search#a0fda762 flags:# peer:InputPeer q:string from_id:flags.0?InputPeer top_msg_id:flags.1?int filter:MessagesFilter min_date:int max_date:int offset_id:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
-messages.searchGlobal#4bc6589a flags:# folder_id:flags.0?int q:string filter:MessagesFilter min_date:int max_date:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;
-messages.getUnreadMentions#46578472 peer:InputPeer offset_id:int add_offset:int limit:int max_id:int min_id:int = messages.Messages;
-messages.getRecentLocations#702a40e0 peer:InputPeer limit:int hash:long = messages.Messages;
-messages.getScheduledHistory#f516760b peer:InputPeer hash:long = messages.Messages;
-messages.getScheduledMessages#bdbb0464 peer:InputPeer id:Vector<int> = messages.Messages;
-messages.getReplies#22ddd30c peer:InputPeer msg_id:int offset_id:int offset_date:int add_offset:int limit:int max_id:int min_id:int hash:long = messages.Messages;
-
-channels.getMessages#ad8c9a23 channel:InputChannel id:Vector<InputMessage> = messages.Messages;
-
-stats.getMessagePublicForwards#5630281b channel:InputChannel msg_id:int offset_rate:int offset_peer:InputPeer offset_id:int limit:int = messages.Messages;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.messagesFull list of messages with auxilary data.
messages.messagesSliceIncomplete list of messages and auxiliary data.
messages.channelMessagesChannel messages
messages.messagesNotModifiedNo new messages matching the query were found
-

Methods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
MethodDescription
messages.getMessagesReturns the list of messages by their IDs.
messages.getHistoryGets back the conversation history with one interlocutor / within a chat
messages.searchGets back found messages
channels.getMessagesGet channel/supergroup messages
messages.searchGlobalSearch for messages and peers globally
messages.getUnreadMentionsGet unread messages where we were mentioned
messages.getRecentLocationsGet live location history of a certain user
messages.getScheduledHistoryGet scheduled messages
messages.getScheduledMessagesGet scheduled messages
messages.getRepliesGet messages in a reply thread
stats.getMessagePublicForwardsObtains a list of messages, indicating to which other public channels was a channel message forwarded.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.PeerDialogs b/data/corefork.telegram.org/type/messages.PeerDialogs deleted file mode 100644 index a8e0b55a99..0000000000 --- a/data/corefork.telegram.org/type/messages.PeerDialogs +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Messages.PeerDialogs - - - - - - - - - - - - - -
- -
-
-
- -

Messages.PeerDialogs

- -

List of dialogs

-

- -
-
messages.peerDialogs#3371c354 dialogs:Vector<Dialog> messages:Vector<Message> chats:Vector<Chat> users:Vector<User> state:updates.State = messages.PeerDialogs;
-
----functions---
-
-messages.getPeerDialogs#e470bcfd peers:Vector<InputDialogPeer> = messages.PeerDialogs;
-messages.getPinnedDialogs#d6b94df2 folder_id:int = messages.PeerDialogs;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.peerDialogsDialog info of multiple peers
-

Methods

- - - - - - - - - - - - - - - - - -
MethodDescription
messages.getPeerDialogsGet dialog info of specified peers
messages.getPinnedDialogsGet pinned dialogs
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.RecentStickers b/data/corefork.telegram.org/type/messages.RecentStickers deleted file mode 100644 index 62e9050444..0000000000 --- a/data/corefork.telegram.org/type/messages.RecentStickers +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Messages.RecentStickers - - - - - - - - - - - - - -
- -
-
-
- -

Messages.RecentStickers

- -

Recent stickers

-

- -
-
messages.recentStickersNotModified#b17f890 = messages.RecentStickers;
-messages.recentStickers#88d37c56 hash:long packs:Vector<StickerPack> stickers:Vector<Document> dates:Vector<int> = messages.RecentStickers;
-
----functions---
-
-messages.getRecentStickers#9da9403b flags:# attached:flags.0?true hash:long = messages.RecentStickers;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.recentStickersNotModifiedNo new recent sticker was found
messages.recentStickersRecently used stickers
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getRecentStickersGet recent stickers
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.SavedGifs b/data/corefork.telegram.org/type/messages.SavedGifs deleted file mode 100644 index 36e2624d72..0000000000 --- a/data/corefork.telegram.org/type/messages.SavedGifs +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Messages.SavedGifs - - - - - - - - - - - - - -
- -
-
-
- -

Messages.SavedGifs

- -

Saved GIFs

-

- -
-
messages.savedGifsNotModified#e8025ca2 = messages.SavedGifs;
-messages.savedGifs#84a02a0d hash:long gifs:Vector<Document> = messages.SavedGifs;
-
----functions---
-
-messages.getSavedGifs#5cf09635 hash:long = messages.SavedGifs;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.savedGifsNotModifiedNo new saved gifs were found
messages.savedGifsSaved gifs
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getSavedGifsGet saved GIFs
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.SearchCounter b/data/corefork.telegram.org/type/messages.SearchCounter deleted file mode 100644 index c1196af0b3..0000000000 --- a/data/corefork.telegram.org/type/messages.SearchCounter +++ /dev/null @@ -1,143 +0,0 @@ - - - - - Messages.SearchCounter - - - - - - - - - - - - - -
- -
-
-
- -

Messages.SearchCounter

- -

Number of results that would be returned by a search

-

- -
-
messages.searchCounter#e844ebff flags:# inexact:flags.1?true filter:MessagesFilter count:int = messages.SearchCounter;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.searchCounterIndicates how many results would be found by a messages.search call with the same parameters
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.SentEncryptedMessage b/data/corefork.telegram.org/type/messages.SentEncryptedMessage deleted file mode 100644 index 99670c2fb0..0000000000 --- a/data/corefork.telegram.org/type/messages.SentEncryptedMessage +++ /dev/null @@ -1,177 +0,0 @@ - - - - - Messages.SentEncryptedMessage - - - - - - - - - - - - - -
- -
-
-
- -

Messages.SentEncryptedMessage

- -

Contains info on message sent to an encrypted chat.

-

- -
-
messages.sentEncryptedMessage#560f8935 date:int = messages.SentEncryptedMessage;
-messages.sentEncryptedFile#9493ff32 date:int file:EncryptedFile = messages.SentEncryptedMessage;
-
----functions---
-
-messages.sendEncrypted#44fa7a15 flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;
-messages.sendEncryptedFile#5559481d flags:# silent:flags.0?true peer:InputEncryptedChat random_id:long data:bytes file:InputEncryptedFile = messages.SentEncryptedMessage;
-messages.sendEncryptedService#32d439a4 peer:InputEncryptedChat random_id:long data:bytes = messages.SentEncryptedMessage;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.sentEncryptedMessageMessage without file attachemts sent to an encrypted file.
messages.sentEncryptedFileMessage with a file enclosure sent to a protected chat
-

Methods

- - - - - - - - - - - - - - - - - - - - - -
MethodDescription
messages.sendEncryptedSends a text message to a secret chat.
messages.sendEncryptedFileSends a message with a file attachment to a secret chat
messages.sendEncryptedServiceSends a service message to a secret chat.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.SentMessage b/data/corefork.telegram.org/type/messages.SentMessage deleted file mode 100644 index a49802247f..0000000000 --- a/data/corefork.telegram.org/type/messages.SentMessage +++ /dev/null @@ -1,128 +0,0 @@ - - - - - messages.SentMessage - - - - - - - - - - - - - -
- -
-
-
- -

messages.SentMessage

- -

Info on a successfully sent message.

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.SponsoredMessages b/data/corefork.telegram.org/type/messages.SponsoredMessages deleted file mode 100644 index c66c97c5b8..0000000000 --- a/data/corefork.telegram.org/type/messages.SponsoredMessages +++ /dev/null @@ -1,166 +0,0 @@ - - - - - messages.SponsoredMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.SponsoredMessages

- -

A set of sponsored messages associated with a channel

-

- -
-
messages.sponsoredMessages#65a4c7d5 messages:Vector<SponsoredMessage> chats:Vector<Chat> users:Vector<User> = messages.SponsoredMessages;
-
----functions---
-
-channels.getSponsoredMessages#ec210fbf channel:InputChannel = messages.SponsoredMessages;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.sponsoredMessagesA set of sponsored messages associated with a channel
-

Methods

- - - - - - - - - - - - - -
MethodDescription
channels.getSponsoredMessagesGet a list of sponsored messages
-

Related pages

-

Sponsored messages

-

How to implement sponsored messages

-
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.StatedMessage b/data/corefork.telegram.org/type/messages.StatedMessage deleted file mode 100644 index 14f8c98cb6..0000000000 --- a/data/corefork.telegram.org/type/messages.StatedMessage +++ /dev/null @@ -1,128 +0,0 @@ - - - - - messages.StatedMessage - - - - - - - - - - - - - -
- -
-
-
- -

messages.StatedMessage

- -

Object contains info on one message with auxiliary data and data on the current state of updates.

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.StatedMessages b/data/corefork.telegram.org/type/messages.StatedMessages deleted file mode 100644 index 9b3f0f2f93..0000000000 --- a/data/corefork.telegram.org/type/messages.StatedMessages +++ /dev/null @@ -1,128 +0,0 @@ - - - - - messages.StatedMessages - - - - - - - - - - - - - -
- -
-
-
- -

messages.StatedMessages

- -

Object contains info on the list of messages with auxiliary data and data on current state of updates.

-

- -
-

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.StickerSet b/data/corefork.telegram.org/type/messages.StickerSet deleted file mode 100644 index cf16a13b0e..0000000000 --- a/data/corefork.telegram.org/type/messages.StickerSet +++ /dev/null @@ -1,188 +0,0 @@ - - - - - Messages.StickerSet - - - - - - - - - - - - - -
- -
-
-
- -

Messages.StickerSet

- -

Stickerset

-

- -
-
messages.stickerSet#b60a24a6 set:StickerSet packs:Vector<StickerPack> documents:Vector<Document> = messages.StickerSet;
-
----functions---
-
-messages.getStickerSet#2619a90e stickerset:InputStickerSet = messages.StickerSet;
-
-stickers.createStickerSet#9021ab67 flags:# masks:flags.0?true animated:flags.1?true videos:flags.4?true user_id:InputUser title:string short_name:string thumb:flags.2?InputDocument stickers:Vector<InputStickerSetItem> software:flags.3?string = messages.StickerSet;
-stickers.removeStickerFromSet#f7760f51 sticker:InputDocument = messages.StickerSet;
-stickers.changeStickerPosition#ffb6d4ca sticker:InputDocument position:int = messages.StickerSet;
-stickers.addStickerToSet#8653febe stickerset:InputStickerSet sticker:InputStickerSetItem = messages.StickerSet;
-stickers.setStickerSetThumb#9a364e30 stickerset:InputStickerSet thumb:InputDocument = messages.StickerSet;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.stickerSetStickerset and stickers inside it
-

Methods

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
MethodDescription
messages.getStickerSetGet info about a stickerset
stickers.createStickerSetCreate a stickerset, bots only.
stickers.removeStickerFromSetRemove a sticker from the set where it belongs, bots only. The sticker set must have been created by the bot.
stickers.changeStickerPositionChanges the absolute position of a sticker in the set to which it belongs; for bots only. The sticker set must have been created by the bot
stickers.addStickerToSetAdd a sticker to a stickerset, bots only. The sticker set must have been created by the bot.
stickers.setStickerSetThumbSet stickerset thumbnail
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.StickerSetInstallResult b/data/corefork.telegram.org/type/messages.StickerSetInstallResult deleted file mode 100644 index d75a83ccaf..0000000000 --- a/data/corefork.telegram.org/type/messages.StickerSetInstallResult +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Messages.StickerSetInstallResult - - - - - - - - - - - - - -
- -
-
-
- -

Messages.StickerSetInstallResult

- -

Result of stickerset installation process

-

- -
-
messages.stickerSetInstallResultSuccess#38641628 = messages.StickerSetInstallResult;
-messages.stickerSetInstallResultArchive#35e410a8 sets:Vector<StickerSetCovered> = messages.StickerSetInstallResult;
-
----functions---
-
-messages.installStickerSet#c78fe460 stickerset:InputStickerSet archived:Bool = messages.StickerSetInstallResult;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.stickerSetInstallResultSuccessThe stickerset was installed successfully
messages.stickerSetInstallResultArchiveThe stickerset was installed, but since there are too many stickersets some were archived
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.installStickerSetInstall a stickerset
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.Stickers b/data/corefork.telegram.org/type/messages.Stickers deleted file mode 100644 index efe09eae3c..0000000000 --- a/data/corefork.telegram.org/type/messages.Stickers +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Messages.Stickers - - - - - - - - - - - - - -
- -
-
-
- -

Messages.Stickers

- -

Stickers

-

- -
-
messages.stickersNotModified#f1749a22 = messages.Stickers;
-messages.stickers#30a6ec7e hash:long stickers:Vector<Document> = messages.Stickers;
-
----functions---
-
-messages.getStickers#d5a5d3a1 emoticon:string hash:long = messages.Stickers;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
messages.stickersNotModifiedNo new stickers were found for the given query
messages.stickersFound stickers
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getStickersGet stickers by emoji
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/messages.VotesList b/data/corefork.telegram.org/type/messages.VotesList deleted file mode 100644 index 77e7adada6..0000000000 --- a/data/corefork.telegram.org/type/messages.VotesList +++ /dev/null @@ -1,162 +0,0 @@ - - - - - messages.VotesList - - - - - - - - - - - - - -
- -
-
-
- -

messages.VotesList

- -

How users voted in a poll

-

- -
-
messages.votesList#823f649 flags:# count:int votes:Vector<MessageUserVote> users:Vector<User> next_offset:flags.0?string = messages.VotesList;
-
----functions---
-
-messages.getPollVotes#b86e380e flags:# peer:InputPeer id:int option:flags.0?bytes offset:flags.1?string limit:int = messages.VotesList;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.votesListHow users voted in a poll
-

Methods

- - - - - - - - - - - - - -
MethodDescription
messages.getPollVotesGet poll results for non-anonymous polls
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/payments.PaymentForm b/data/corefork.telegram.org/type/payments.PaymentForm deleted file mode 100644 index e94b590f73..0000000000 --- a/data/corefork.telegram.org/type/payments.PaymentForm +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Payments.PaymentForm - - - - - - - - - - - - - -
- -
-
-
- -

Payments.PaymentForm

- -

Payment form

-

- -
-
payments.paymentForm#1694761b flags:# can_save_credentials:flags.2?true password_missing:flags.3?true form_id:long bot_id:long invoice:Invoice provider_id:long url:string native_provider:flags.4?string native_params:flags.4?DataJSON saved_info:flags.0?PaymentRequestedInfo saved_credentials:flags.1?PaymentSavedCredentials users:Vector<User> = payments.PaymentForm;
-
----functions---
-
-payments.getPaymentForm#8a333c8d flags:# peer:InputPeer msg_id:int theme_params:flags.0?DataJSON = payments.PaymentForm;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
payments.paymentFormPayment form
-

Methods

- - - - - - - - - - - - - -
MethodDescription
payments.getPaymentFormGet a payment form
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/payments.PaymentResult b/data/corefork.telegram.org/type/payments.PaymentResult deleted file mode 100644 index 43b5cec3b8..0000000000 --- a/data/corefork.telegram.org/type/payments.PaymentResult +++ /dev/null @@ -1,167 +0,0 @@ - - - - - Payments.PaymentResult - - - - - - - - - - - - - -
- -
-
-
- -

Payments.PaymentResult

- -

Payment result

-

- -
-
payments.paymentResult#4e5f810d updates:Updates = payments.PaymentResult;
-payments.paymentVerificationNeeded#d8411139 url:string = payments.PaymentResult;
-
----functions---
-
-payments.sendPaymentForm#30c3bc9d flags:# form_id:long peer:InputPeer msg_id:int requested_info_id:flags.0?string shipping_option_id:flags.1?string credentials:InputPaymentCredentials tip_amount:flags.2?long = payments.PaymentResult;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
payments.paymentResultPayment result
payments.paymentVerificationNeededPayment was not successful, additional verification is needed
-

Methods

- - - - - - - - - - - - - -
MethodDescription
payments.sendPaymentFormSend compiled payment form
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/payments.SavedInfo b/data/corefork.telegram.org/type/payments.SavedInfo deleted file mode 100644 index bc90f40ba1..0000000000 --- a/data/corefork.telegram.org/type/payments.SavedInfo +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Payments.SavedInfo - - - - - - - - - - - - - -
- -
-
-
- -

Payments.SavedInfo

- -

Saved payment info

-

- -
-
payments.savedInfo#fb8fe43c flags:# has_saved_credentials:flags.1?true saved_info:flags.0?PaymentRequestedInfo = payments.SavedInfo;
-
----functions---
-
-payments.getSavedInfo#227d824b = payments.SavedInfo;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
payments.savedInfoSaved server-side order information
-

Methods

- - - - - - - - - - - - - -
MethodDescription
payments.getSavedInfoGet saved payment information
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/payments.ValidatedRequestedInfo b/data/corefork.telegram.org/type/payments.ValidatedRequestedInfo deleted file mode 100644 index 7e3b536213..0000000000 --- a/data/corefork.telegram.org/type/payments.ValidatedRequestedInfo +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Payments.ValidatedRequestedInfo - - - - - - - - - - - - - -
- -
-
-
- -

Payments.ValidatedRequestedInfo

- -

Validated requested info

-

- -
-
payments.validatedRequestedInfo#d1451883 flags:# id:flags.0?string shipping_options:flags.1?Vector<ShippingOption> = payments.ValidatedRequestedInfo;
-
----functions---
-
-payments.validateRequestedInfo#db103170 flags:# save:flags.0?true peer:InputPeer msg_id:int info:PaymentRequestedInfo = payments.ValidatedRequestedInfo;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
payments.validatedRequestedInfoValidated user-provided info
-

Methods

- - - - - - - - - - - - - -
MethodDescription
payments.validateRequestedInfoSubmit requested order information for validation
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/phone.ExportedGroupCallInvite b/data/corefork.telegram.org/type/phone.ExportedGroupCallInvite deleted file mode 100644 index 4f237ba5be..0000000000 --- a/data/corefork.telegram.org/type/phone.ExportedGroupCallInvite +++ /dev/null @@ -1,162 +0,0 @@ - - - - - phone.ExportedGroupCallInvite - - - - - - - - - - - - - -
- -
-
-
- -

phone.ExportedGroupCallInvite

- -

An exported group call invitation.

-

- -
-
phone.exportedGroupCallInvite#204bd158 link:string = phone.ExportedGroupCallInvite;
-
----functions---
-
-phone.exportGroupCallInvite#e6aa647f flags:# can_self_unmute:flags.0?true call:InputGroupCall = phone.ExportedGroupCallInvite;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
phone.exportedGroupCallInviteAn invite to a group call or livestream
-

Methods

- - - - - - - - - - - - - -
MethodDescription
phone.exportGroupCallInviteGet an invite link for a group call or livestream
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/phone.GroupCall b/data/corefork.telegram.org/type/phone.GroupCall deleted file mode 100644 index 68ed37fc6b..0000000000 --- a/data/corefork.telegram.org/type/phone.GroupCall +++ /dev/null @@ -1,162 +0,0 @@ - - - - - phone.GroupCall - - - - - - - - - - - - - -
- -
-
-
- -

phone.GroupCall

- -

Contains info about a group call, and partial info about its participants.

-

- -
-
phone.groupCall#9e727aad call:GroupCall participants:Vector<GroupCallParticipant> participants_next_offset:string chats:Vector<Chat> users:Vector<User> = phone.GroupCall;
-
----functions---
-
-phone.getGroupCall#41845db call:InputGroupCall limit:int = phone.GroupCall;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
phone.groupCallContains info about a group call, and partial info about its participants.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
phone.getGroupCallGet info about a group call
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/phone.GroupParticipants b/data/corefork.telegram.org/type/phone.GroupParticipants deleted file mode 100644 index be36a12b14..0000000000 --- a/data/corefork.telegram.org/type/phone.GroupParticipants +++ /dev/null @@ -1,162 +0,0 @@ - - - - - phone.GroupParticipants - - - - - - - - - - - - - -
- -
-
-
- -

phone.GroupParticipants

- -

Info about the participants of a group call or livestream

-

- -
-
phone.groupParticipants#f47751b6 count:int participants:Vector<GroupCallParticipant> next_offset:string chats:Vector<Chat> users:Vector<User> version:int = phone.GroupParticipants;
-
----functions---
-
-phone.getGroupParticipants#c558d8ab call:InputGroupCall ids:Vector<InputPeer> sources:Vector<int> offset:string limit:int = phone.GroupParticipants;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
phone.groupParticipantsInfo about the participants of a group call or livestream
-

Methods

- - - - - - - - - - - - - -
MethodDescription
phone.getGroupParticipantsGet group call participants
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/phone.JoinAsPeers b/data/corefork.telegram.org/type/phone.JoinAsPeers deleted file mode 100644 index f3c42c5fb2..0000000000 --- a/data/corefork.telegram.org/type/phone.JoinAsPeers +++ /dev/null @@ -1,162 +0,0 @@ - - - - - phone.JoinAsPeers - - - - - - - - - - - - - -
- -
-
-
- -

phone.JoinAsPeers

- -

A list of peers that can be used to join a group call, presenting yourself as a specific user/channel.

-

- -
-
phone.joinAsPeers#afe5623f peers:Vector<Peer> chats:Vector<Chat> users:Vector<User> = phone.JoinAsPeers;
-
----functions---
-
-phone.getGroupCallJoinAs#ef7c213a peer:InputPeer = phone.JoinAsPeers;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
phone.joinAsPeersA list of peers that can be used to join a group call, presenting yourself as a specific user/channel.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
phone.getGroupCallJoinAsGet a list of peers that can be used to join a group call, presenting yourself as a specific user/channel.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/phone.PhoneCall b/data/corefork.telegram.org/type/phone.PhoneCall deleted file mode 100644 index b564346aad..0000000000 --- a/data/corefork.telegram.org/type/phone.PhoneCall +++ /dev/null @@ -1,172 +0,0 @@ - - - - - Phone.PhoneCall - - - - - - - - - - - - - -
- -
-
-
- -

Phone.PhoneCall

- -

Phone call

-

- -
-
phone.phoneCall#ec82e140 phone_call:PhoneCall users:Vector<User> = phone.PhoneCall;
-
----functions---
-
-phone.requestCall#42ff96ed flags:# video:flags.0?true user_id:InputUser random_id:int g_a_hash:bytes protocol:PhoneCallProtocol = phone.PhoneCall;
-phone.acceptCall#3bd2b4a0 peer:InputPhoneCall g_b:bytes protocol:PhoneCallProtocol = phone.PhoneCall;
-phone.confirmCall#2efe1722 peer:InputPhoneCall g_a:bytes key_fingerprint:long protocol:PhoneCallProtocol = phone.PhoneCall;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
phone.phoneCallA VoIP phone call
-

Methods

- - - - - - - - - - - - - - - - - - - - - -
MethodDescription
phone.requestCallStart a telegram phone call
phone.acceptCallAccept incoming call
phone.confirmCallComplete phone call E2E encryption key exchange »
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/photos.Photos b/data/corefork.telegram.org/type/photos.Photos deleted file mode 100644 index 45dfecf3cc..0000000000 --- a/data/corefork.telegram.org/type/photos.Photos +++ /dev/null @@ -1,167 +0,0 @@ - - - - - photos.Photos - - - - - - - - - - - - - -
- -
-
-
- -

photos.Photos

- -

Object contains list of photos with auxiliary data.

-

- -
-
photos.photos#8dca6aa5 photos:Vector<Photo> users:Vector<User> = photos.Photos;
-photos.photosSlice#15051f54 count:int photos:Vector<Photo> users:Vector<User> = photos.Photos;
-
----functions---
-
-photos.getUserPhotos#91cd32a8 user_id:InputUser offset:int max_id:long limit:int = photos.Photos;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
photos.photosFull list of photos with auxiliary data.
photos.photosSliceIncomplete list of photos with auxiliary data.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
photos.getUserPhotosReturns the list of user photos.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/stats.BroadcastStats b/data/corefork.telegram.org/type/stats.BroadcastStats deleted file mode 100644 index 64cd8292a1..0000000000 --- a/data/corefork.telegram.org/type/stats.BroadcastStats +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Stats.BroadcastStats - - - - - - - - - - - - - -
- -
-
-
- -

Stats.BroadcastStats

- -

Channel statistics

-

- -
-
stats.broadcastStats#bdf78394 period:StatsDateRangeDays followers:StatsAbsValueAndPrev views_per_post:StatsAbsValueAndPrev shares_per_post:StatsAbsValueAndPrev enabled_notifications:StatsPercentValue growth_graph:StatsGraph followers_graph:StatsGraph mute_graph:StatsGraph top_hours_graph:StatsGraph interactions_graph:StatsGraph iv_interactions_graph:StatsGraph views_by_source_graph:StatsGraph new_followers_by_source_graph:StatsGraph languages_graph:StatsGraph recent_message_interactions:Vector<MessageInteractionCounters> = stats.BroadcastStats;
-
----functions---
-
-stats.getBroadcastStats#ab42441a flags:# dark:flags.0?true channel:InputChannel = stats.BroadcastStats;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
stats.broadcastStatsChannel statistics
-

Methods

- - - - - - - - - - - - - -
MethodDescription
stats.getBroadcastStatsGet channel statistics
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/stats.MegagroupStats b/data/corefork.telegram.org/type/stats.MegagroupStats deleted file mode 100644 index 1cae3e16bf..0000000000 --- a/data/corefork.telegram.org/type/stats.MegagroupStats +++ /dev/null @@ -1,162 +0,0 @@ - - - - - stats.MegagroupStats - - - - - - - - - - - - - -
- -
-
-
- -

stats.MegagroupStats

- -

Supergroup statistics

-

- -
-
stats.megagroupStats#ef7ff916 period:StatsDateRangeDays members:StatsAbsValueAndPrev messages:StatsAbsValueAndPrev viewers:StatsAbsValueAndPrev posters:StatsAbsValueAndPrev growth_graph:StatsGraph members_graph:StatsGraph new_members_by_source_graph:StatsGraph languages_graph:StatsGraph messages_graph:StatsGraph actions_graph:StatsGraph top_hours_graph:StatsGraph weekdays_graph:StatsGraph top_posters:Vector<StatsGroupTopPoster> top_admins:Vector<StatsGroupTopAdmin> top_inviters:Vector<StatsGroupTopInviter> users:Vector<User> = stats.MegagroupStats;
-
----functions---
-
-stats.getMegagroupStats#dcdf8607 flags:# dark:flags.0?true channel:InputChannel = stats.MegagroupStats;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
stats.megagroupStatsSupergroup statistics
-

Methods

- - - - - - - - - - - - - -
MethodDescription
stats.getMegagroupStatsGet supergroup statistics
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/stats.MessageStats b/data/corefork.telegram.org/type/stats.MessageStats deleted file mode 100644 index 0eb39ee7e2..0000000000 --- a/data/corefork.telegram.org/type/stats.MessageStats +++ /dev/null @@ -1,162 +0,0 @@ - - - - - stats.MessageStats - - - - - - - - - - - - - -
- -
-
-
- -

stats.MessageStats

- -

Message statistics

-

- -
-
stats.messageStats#8999f295 views_graph:StatsGraph = stats.MessageStats;
-
----functions---
-
-stats.getMessageStats#b6e0a3f5 flags:# dark:flags.0?true channel:InputChannel msg_id:int = stats.MessageStats;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
stats.messageStatsMessage statistics
-

Methods

- - - - - - - - - - - - - -
MethodDescription
stats.getMessageStatsGet message statistics
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/stickers.SuggestedShortName b/data/corefork.telegram.org/type/stickers.SuggestedShortName deleted file mode 100644 index a5fe58ed4f..0000000000 --- a/data/corefork.telegram.org/type/stickers.SuggestedShortName +++ /dev/null @@ -1,162 +0,0 @@ - - - - - stickers.SuggestedShortName - - - - - - - - - - - - - -
- -
-
-
- -

stickers.SuggestedShortName

- -

A suggested short name for the specified stickerpack

-

- -
-
stickers.suggestedShortName#85fea03f short_name:string = stickers.SuggestedShortName;
-
----functions---
-
-stickers.suggestShortName#4dafc503 title:string = stickers.SuggestedShortName;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
stickers.suggestedShortNameA suggested short name for a stickerpack
-

Methods

- - - - - - - - - - - - - -
MethodDescription
stickers.suggestShortNameSuggests a short name for a given stickerpack name
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/storage.FileType b/data/corefork.telegram.org/type/storage.FileType deleted file mode 100644 index 4b3944f6ab..0000000000 --- a/data/corefork.telegram.org/type/storage.FileType +++ /dev/null @@ -1,188 +0,0 @@ - - - - - storage.FileType - - - - - - - - - - - - - -
- -
-
-
- -

storage.FileType

- -

Object describes the file type.

-

- -
-
storage.fileUnknown#aa963b05 = storage.FileType;
-storage.filePartial#40bc6f52 = storage.FileType;
-storage.fileJpeg#7efe0e = storage.FileType;
-storage.fileGif#cae1aadf = storage.FileType;
-storage.filePng#a4f63c0 = storage.FileType;
-storage.filePdf#ae1e508d = storage.FileType;
-storage.fileMp3#528a0677 = storage.FileType;
-storage.fileMov#4b09ebbc = storage.FileType;
-storage.fileMp4#b3cea0e4 = storage.FileType;
-storage.fileWebp#1081464c = storage.FileType;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
storage.fileUnknownUnknown type.
storage.filePartialPart of a bigger file.
storage.fileJpegJPEG image. MIME type: image/jpeg.
storage.fileGifGIF image. MIME type: image/gif.
storage.filePngPNG image. MIME type: image/png.
storage.filePdfPDF document image. MIME type: application/pdf.
storage.fileMp3Mp3 audio. MIME type: audio/mpeg.
storage.fileMovQuicktime video. MIME type: video/quicktime.
storage.fileMp4MPEG-4 video. MIME type: video/mp4.
storage.fileWebpWEBP image. MIME type: image/webp.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/string.html b/data/corefork.telegram.org/type/string.html deleted file mode 100644 index 4ea235596d..0000000000 --- a/data/corefork.telegram.org/type/string.html +++ /dev/null @@ -1,126 +0,0 @@ - - - - - string - - - - - - - - - - - - - -
- -
-
-
- -

string

- -

A basic bare type. Values of type string look differently depending on the length L of the string being serialized:

-
    -
  • If L <= 253, the serialization contains one byte with the value of L, then L bytes of the string followed by 0 to 3 characters containing 0, such that the overall length of the value be divisible by 4, whereupon all of this is interpreted as a sequence of int(L/4)+1 32-bit little-endian integers.
  • -
  • If L >= 254, the serialization contains byte 254, followed by 3 bytes with the string length L in little-endian order, followed by L bytes of the string, further followed by 0 to 3 null padding bytes.
  • -
-

All strings passed to the API must be encoded in UTF-8. When arbitrary byte sequences have to be serialized, bytes alias is to be used.

-

Further details on basic types»

-

Related pages

-

bytes

-

Basic bare type. It is an alias of the string type, with the difference that the value may contain arbitrary byte sequences, including invalid UTF-8 sequences.

-

When computing crc32 for a constructor or method it is necessary to replace all byte types with string types.

-

Binary Data Serialization

- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/updates.ChannelDifference b/data/corefork.telegram.org/type/updates.ChannelDifference deleted file mode 100644 index d01b971c3f..0000000000 --- a/data/corefork.telegram.org/type/updates.ChannelDifference +++ /dev/null @@ -1,172 +0,0 @@ - - - - - updates.ChannelDifference - - - - - - - - - - - - - -
- -
-
-
- -

updates.ChannelDifference

- -

Contains the difference (new messages) between our local channel state and the remote state

-

- -
-
updates.channelDifferenceEmpty#3e11affb flags:# final:flags.0?true pts:int timeout:flags.1?int = updates.ChannelDifference;
-updates.channelDifferenceTooLong#a4bcc6fe flags:# final:flags.0?true timeout:flags.1?int dialog:Dialog messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
-updates.channelDifference#2064674e flags:# final:flags.0?true pts:int timeout:flags.1?int new_messages:Vector<Message> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
-
----functions---
-
-updates.getChannelDifference#3173d78 flags:# force:flags.0?true channel:InputChannel filter:ChannelMessagesFilter pts:int limit:int = updates.ChannelDifference;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
updates.channelDifferenceEmptyThere are no new updates
updates.channelDifferenceTooLongThe provided pts + limit < remote pts. Simply, there are too many updates to be fetched (more than limit), the client has to resolve the update gap in one of the following ways:

1. Delete all known messages in the chat, begin from scratch by refetching all messages manually with getHistory. It is easy to implement, but suddenly disappearing messages looks awful for the user.
2. Save all messages loaded in the memory until application restart, but delete all messages from database. Messages left in the memory must be lazily updated using calls to getHistory. It looks much smoother for the user, they will need to redownload messages only after client restart. Unsynchronized messages left in the memory shouldn't be saved to database, results of getHistory and getMessages must be used to update state of deleted and edited messages left in the memory.
3. Save all messages loaded in the memory and stored in the database without saving that some messages form continuous ranges. Messages in the database will be excluded from results of getChatHistory and searchChatMessages after application restart and will be available only through getMessage. Every message should still be checked using getHistory. It has more disadvantages over 2) than advantages.
4. Save all messages with saving all data about continuous message ranges. Messages from the database may be used as results of getChatHistory and (if implemented continuous ranges support for searching shared media) searchChatMessages. The messages should still be lazily checked using getHistory, but they are still available offline. It is the best way for gaps support, but it is pretty hard to implement correctly. It should be also noted that some messages like live location messages shouldn't be deleted.
updates.channelDifferenceThe new updates
-

Methods

- - - - - - - - - - - - - -
MethodDescription
updates.getChannelDifferenceReturns the difference between the current state of updates of a certain channel and transmitted.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/updates.Difference b/data/corefork.telegram.org/type/updates.Difference deleted file mode 100644 index 24fc35c7c0..0000000000 --- a/data/corefork.telegram.org/type/updates.Difference +++ /dev/null @@ -1,177 +0,0 @@ - - - - - updates.Difference - - - - - - - - - - - - - -
- -
-
-
- -

updates.Difference

- -

Occurred changes.

-

- -
-
updates.differenceEmpty#5d75a138 date:int seq:int = updates.Difference;
-updates.difference#f49ca0 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> state:updates.State = updates.Difference;
-updates.differenceSlice#a8fb1981 new_messages:Vector<Message> new_encrypted_messages:Vector<EncryptedMessage> other_updates:Vector<Update> chats:Vector<Chat> users:Vector<User> intermediate_state:updates.State = updates.Difference;
-updates.differenceTooLong#4afe8f6d pts:int = updates.Difference;
-
----functions---
-
-updates.getDifference#25939651 flags:# pts:int pts_total_limit:flags.0?int date:int qts:int = updates.Difference;

-

Constructors

- - - - - - - - - - - - - - - - - - - - - - - - - -
ConstructorDescription
updates.differenceEmptyNo events.
updates.differenceFull list of occurred events.
updates.differenceSliceIncomplete list of occurred events.
updates.differenceTooLongThe difference is too long, and the specified state must be used to refetch updates.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
updates.getDifferenceGet new updates.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/updates.State b/data/corefork.telegram.org/type/updates.State deleted file mode 100644 index d2f0972a73..0000000000 --- a/data/corefork.telegram.org/type/updates.State +++ /dev/null @@ -1,162 +0,0 @@ - - - - - updates.State - - - - - - - - - - - - - -
- -
-
-
- -

updates.State

- -

Object contains info on state for further updates.

-

- -
-
updates.state#a56c2a3e pts:int qts:int date:int seq:int unread_count:int = updates.State;
-
----functions---
-
-updates.getState#edd4882a = updates.State;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
updates.stateUpdates state.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
updates.getStateReturns a current state of updates.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/upload.CdnFile b/data/corefork.telegram.org/type/upload.CdnFile deleted file mode 100644 index 4ea5f79b56..0000000000 --- a/data/corefork.telegram.org/type/upload.CdnFile +++ /dev/null @@ -1,167 +0,0 @@ - - - - - upload.CdnFile - - - - - - - - - - - - - -
- -
-
-
- -

upload.CdnFile

- -

Represents the download status of a CDN file

-

- -
-
upload.cdnFileReuploadNeeded#eea8e46e request_token:bytes = upload.CdnFile;
-upload.cdnFile#a99fca4f bytes:bytes = upload.CdnFile;
-
----functions---
-
-upload.getCdnFile#2000bcc3 file_token:bytes offset:int limit:int = upload.CdnFile;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
upload.cdnFileReuploadNeededThe file was cleared from the temporary RAM cache of the CDN and has to be reuploaded.
upload.cdnFileRepresent a chunk of a CDN file.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
upload.getCdnFileDownload a CDN file.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/upload.File b/data/corefork.telegram.org/type/upload.File deleted file mode 100644 index 0542d29041..0000000000 --- a/data/corefork.telegram.org/type/upload.File +++ /dev/null @@ -1,167 +0,0 @@ - - - - - upload.File - - - - - - - - - - - - - -
- -
-
-
- -

upload.File

- -

Contains info on file.

-

- -
-
upload.file#96a18d5 type:storage.FileType mtime:int bytes:bytes = upload.File;
-upload.fileCdnRedirect#f18cda44 dc_id:int file_token:bytes encryption_key:bytes encryption_iv:bytes file_hashes:Vector<FileHash> = upload.File;
-
----functions---
-
-upload.getFile#b15a9afc flags:# precise:flags.0?true cdn_supported:flags.1?true location:InputFileLocation offset:int limit:int = upload.File;

-

Constructors

- - - - - - - - - - - - - - - - - -
ConstructorDescription
upload.fileFile content.
upload.fileCdnRedirectThe file must be downloaded from a CDN DC.
-

Methods

- - - - - - - - - - - - - -
MethodDescription
upload.getFileReturns content of a whole file or its part.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/upload.WebFile b/data/corefork.telegram.org/type/upload.WebFile deleted file mode 100644 index bec0d30082..0000000000 --- a/data/corefork.telegram.org/type/upload.WebFile +++ /dev/null @@ -1,162 +0,0 @@ - - - - - Upload.WebFile - - - - - - - - - - - - - -
- -
-
-
- -

Upload.WebFile

- -

Remote file

-

- -
-
upload.webFile#21e753bc size:int mime_type:string file_type:storage.FileType mtime:int bytes:bytes = upload.WebFile;
-
----functions---
-
-upload.getWebFile#24e6818d location:InputWebFileLocation offset:int limit:int = upload.WebFile;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
upload.webFileRepresents a chunk of an HTTP webfile downloaded through telegram's secure MTProto servers
-

Methods

- - - - - - - - - - - - - -
MethodDescription
upload.getWebFileReturns content of an HTTP file or a part, by proxying the request through telegram.
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/widgets.html b/data/corefork.telegram.org/widgets.html deleted file mode 100644 index d39effe6f6..0000000000 --- a/data/corefork.telegram.org/widgets.html +++ /dev/null @@ -1,141 +0,0 @@ - - - - - Telegram Widgets - - - - - - - - - - - - - -
- -
-
-
-
-

Telegram Widgets

- -

Telegram widgets offer a quick way to add a sharing button to your pages, embed posts from public channels or groups. Widgets can also help your users log in with Telegram or view Telegram Discussions on your website.

-
-
-
- - -
-
- - -
-
- - -
-
- - -
-
-
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/widgets/discussion.html b/data/corefork.telegram.org/widgets/discussion.html deleted file mode 100644 index 4a057af876..0000000000 --- a/data/corefork.telegram.org/widgets/discussion.html +++ /dev/null @@ -1,226 +0,0 @@ - - - - - Discussion Widget - - - - - - - - - - - - - - - -
- -
-
-
- -

Discussion Widget

- -

You can embed discussions from any public channel on your website. You only need a link to a post with comments to embed it together with all discussion.

-

If you have a website with articles and a telegram channel where you post links to these articles, you can use this widget to show discussions from that channel on your website. In this case you only need a link to the channel. Discussions will be available on your website as soon as you post a link into the channel. For this to work, you should add the <link rel="canonical" href="%page_url%"> tag to the page header where %page_url% is the canonical URL of the current page.

-

Configure widget

-

You can choose options for your widget using the form below.

-

-
- -
-
- -
- -
-
-
- -
- -
-
- -
-
-
- -
-
- -
-
-
-
- -
- -
-
- - - - - - - -
- - -
-
- -
- -
- -
Make sure you have a <link rel="canonical" href="%page_url%"> tag in the page header with the canonical url of the current page.
-
-
- -
-
-
-
-
-

-

Basic comments

-

If you're looking to simply add Telegram comments to pages on your website, without linking them with a channel, you can use our basic comments solution.

-
- -
- -
-
- -
- - - - - - - - - - diff --git a/data/corefork.telegram.org/widgets/login.html b/data/corefork.telegram.org/widgets/login.html deleted file mode 100644 index d8c245ae6f..0000000000 --- a/data/corefork.telegram.org/widgets/login.html +++ /dev/null @@ -1,404 +0,0 @@ - - - - - Telegram Login Widget - - - - - - - - - - - - - - -
- -
-
-
- -

Telegram Login Widget

- -
-

The Telegram login widget is a simple way to authorize users on your website.
Check out this post for a general overview of the widget.

-
-

Setting up a bot

-

To use the login widget, you'll need a Telegram bot.

-

We strongly recommend that the profile picture of the bot you use for authorization corresponds with your website‘s logo, and that the bot’s name reflects that connection.

-

Users will see this message when they log into your website:

-
- -
- -

It is more likely that users will log in if your bot has a name and logo they expect to see.

-

Linking your domain to the bot

-

Once you have chosen a bot, send the /setdomain command to @Botfather to link your website's domain to the bot. Then configure your widget below and embed the code on your website.

-

Widget configuration

-

-
- -
-
-
- -
- -
- - -
- Log in below to load your bots with linked domains -
-
- -
- -
- - - -
-
- -
-
- -
- -
- - -
-
- -
- -
- - -
-
- -
- -
- -
-
- -
- -
- -
-
- -
-
-
-
-
-

-

Receiving authorization data

-

After a successful authorization, the widget can return data in two ways:

-
    -
  • by redirecting the user to the URL specified in the data-auth-url attribute with the following parameters: id, first_name, last_name, username, photo_url, auth_date and hash;
  • -
  • by calling the callback function data-onauth with the JSON-object containing id, first_name, last_name, username, photo_url, auth_date and hash fields.
  • -
-

Checking authorization

-

You can verify the authentication and the integrity of the data received by comparing the received hash parameter with the hexadecimal representation of the HMAC-SHA-256 signature of the data-check-string with the SHA256 hash of the bot's token used as a secret key.

-

Data-check-string is a concatenation of all received fields, sorted in alphabetical order, in the format key=<value> with a line feed character ('\n', 0x0A) used as separator – e.g., 'auth_date=<auth_date>\nfirst_name=<first_name>\nid=<id>\nusername=<username>'.

-

The full check might look like:

-
data_check_string = ...
-secret_key = SHA256(<bot_token>)
-if (hex(HMAC_SHA256(data_check_string, secret_key)) == hash) {
-  // data is from Telegram
-}
-

To prevent the use of outdated data, you can additionally check the auth_date field, which contains a Unix timestamp when the authentication was received.

-

Sample implementation

-

You can find sample PHP code for checking authorization and receiving data about a logged in user on this page.

-
- -
- -
-
- -
- - - - - - - - - diff --git a/data/corefork.telegram.org/widgets/post.html b/data/corefork.telegram.org/widgets/post.html deleted file mode 100644 index 383e14184f..0000000000 --- a/data/corefork.telegram.org/widgets/post.html +++ /dev/null @@ -1,240 +0,0 @@ - - - - - Post Widget - - - - - - - - - - - - - - - -
- -
-
-
- -

Post Widget

- -

You can embed messages from public groups and channels anywhere. Here’s what an embed of a Telegram message looks like when included on a web page:

-

- -

-
- -

To get the HTML-code for embedding a message, just open its t.me link (e.g., t.me/durov/43) in a web browser and click < > EMBED:

-
- -
- -

Configure widget

-

You can choose more options using the form below.

-

-
- -
-
- -
- -
-
-
- -
- -
-
- -
-
-
-
- -
- -
- - - -
-
- -
- -
-
- - - - - - - -
- - -
-
- -
- -
- -
-
- -
-
-
-
-
-

-
- -
- -
-
- -
- - - - - - - - - - diff --git a/data/corefork.telegram.org/widgets/share.html b/data/corefork.telegram.org/widgets/share.html deleted file mode 100644 index 18ec61fb75..0000000000 --- a/data/corefork.telegram.org/widgets/share.html +++ /dev/null @@ -1,250 +0,0 @@ - - - - - Sharing Button - - - - - - - - - - - - - - -
- -
-
-
- -

Sharing Button

- -

A Telegram Sharing Button is an easy way to let users forward content from your website or app to their friends, Channels or Saved Messages on Telegram.

-
- TITLE -
- -

When a user presses the button, Telegram asks them to choose a chat, group or channel where your link will be shared. You can also add some text that describes the link – the user will be able to edit it before sending the message.

-
- TITLE -
- -
-

Check out posts on the Telegram Blog for working examples of sharing buttons.

-
-

Adding Telegram sharing buttons to your website

-

Widget Constructor

-

Use this constructor to get embeddable code for your website.

-


- -

-
- -
-
- -
- -
-
-
- -
- -
-
- -
-
-
-
- -
- -
- - -
-
- -
- -
- - -
-
- -
- -
- -
-
- -
-
-
-
-
-

-

Custom buttons

-

Feel free to create your own custom UI for the button. The only thing you need to make it work is to point the user to this URL on click:

-
https://t.me/share/url?url={url}&text={text}
-

where {url} is the URL the user will be sharing and {text} is an optional description that will be included with the link. Both values should be URL-encoded.

-

Here is a sample code for PHP:

-
/**
- * @param string $url Absolute URL to share, e.g. "https://example.com/path/to/article?with=params"
- * @param string $text Optional comment to share URL with, e.g. "Check out this article!"
- * @return string Button HTML markup, feel free to modify to your taste
- */
-function telegramForwardButton($url, $text = '') {
-  $share_url = 'https://t.me/share/url?url='.rawurlencode($url).'&text='.rawurlencode($text);
-  return "<a href=\"{$share_url}\">Share</a>";
-}
-

You are welcome to use the Telegram Logos in your custom button design.

-

Integrations and libraries

- -

If you have a library, plugin or integration script for Telegram sharing buttons, please contact @BotSupport and we'll add you to this list.

-
- -
- -
-
- -
- - - - - - - - - diff --git a/data/telegram.org.html b/data/telegram.org.html deleted file mode 100644 index c8aca89b2d..0000000000 --- a/data/telegram.org.html +++ /dev/null @@ -1,283 +0,0 @@ - - - - - Telegram Messenger - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- - - - - - -
- -

Why Telegram?

- -
-
-
-
-

Simple

-
Telegram is so simple you already know how to use it.
-
-
- -
-
-
-

Private

-
Telegram messages are heavily encrypted and can self-destruct.
-
-
- -
-
-
-

Synced

-
Telegram lets you access your chats from multiple devices.
-
-
- -
-
-
-

Fast

-
Telegram delivers messages faster than any other application.
-
-
- -
-
-
-

Powerful

-
Telegram has no limits on the size of your media and chats.
-
-
- -
-
-
-

Open

-
Telegram has an open API and source code free for everyone.
-
-
- -
-
-
-

Secure

-
Telegram keeps your messages safe from hacker attacks.
-
-
- -
-
-
-

Social

-
Telegram groups can hold up to 200,000 members.
-
-
- -
-
-
-

Expressive

-
Telegram lets you completely customize your messenger.
-
-
-
-
- -
- -
-
-
- - - - - - - - diff --git a/data/telegram.org/android.html b/data/telegram.org/android.html deleted file mode 100644 index b3446fa6dc..0000000000 --- a/data/telegram.org/android.html +++ /dev/null @@ -1,79 +0,0 @@ - - - - - Telegram for Android - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
- - -

Telegram for Android

-
-
You can download Telegram for your Android device here. This version has fewer restrictions and receives automatic updates directly from telegram.org
- - - -
-

How to Install Telegram?

-
This video shows how to install Telegram on your Android device. See this page for detailed steps on various versions of Android.
-
- -
-
More comfortable with installing apps
from the Google Play Store?

Download Telegram from Google Play
-
-
- -
-
-
- - - - - - - diff --git a/data/telegram.org/blog.html b/data/telegram.org/blog.html deleted file mode 100644 index 84769c8768..0000000000 --- a/data/telegram.org/blog.html +++ /dev/null @@ -1,268 +0,0 @@ - - - - - Telegram Blog - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
-

Telegram News

-
-
- -
-

Video Stickers, Better Reactions and More

-
This update brings easy-to-make video stickers, better reactions with more compact animations and extra emoji, a button to review unseen…
-
-
Jan 31, 2022
-
- -
-

Reactions, Spoilers, Translation and QR Codes

-
Telegram's 12th update of the year introduces reactions, message translation, themed QR codes, hidden text (spoilers), and more.
-
-
Dec 30, 2021
-
- -
-

Protected Content, Delete by Date, Device Management and More

-
Today's update brings tools to prevent others from saving content from groups and channels, the ability to delete messages for specific…
-
-
Dec 7, 2021
-
- -
-

Hyper-Speed Scrolling and Calendar View for Shared Media, Join Requests, Global Chat Themes on iOS and More

-
Today's update brings new ways to find memories in shared media with accelerated scrolling…
-
-
Nov 3, 2021
-
- -
-

Chat Themes, Interactive Emoji, Read Receipts in Groups and Live Stream Recording

-
Today's update lets you set different themes for individual chats, share your feelings with…
-
-
Sep 19, 2021
-
- -
-

Live Streams, Flexible Forwarding, Jump to Next Channel, Trending Stickers and More

-
Telegram 8.0 brings live streams with unlimited viewers to groups and channels, options to…
-
-
Aug 31, 2021
-
- -
-

Video Calls with up to 1000 Viewers, Video Messages 2.0, Video Playback Speed and More

-
This update takes video to the next level. Group video calls now have up to 1000 viewers,…
-
-
Jul 30, 2021
-
- -
-

Group Video Calls

-
Today's update lets you turn on your camera or share your screen during Voice Chats in groups – on all devices, including tablets and desktops. This brings voice chats to a whole new…
-
-
Jun 25, 2021
-
- -
-

Animated Backgrounds

-
In addition to Group Video Calls, this update adds animated backgrounds and message sending animations, as well as a new menu button for bots, new ways to import stickers, reminders…
-
-
Jun 25, 2021
-
- -
-

Payments 2.0, Scheduled Voice Chats, New Web Versions

-
This update brings Payments 2.0 for all Telegram chats, Scheduling and Mini Profiles for Voice Chats, new versions of Telegram Web for…
-
-
Apr 26, 2021
-
- -
-

Voice Chats 2.0: Channels, Millions of Listeners, Recorded Chats, Admin Tools

-
Voice Chats first appeared in December, adding a new dimension of live talk to Telegram groups. Starting today, they become available in…
-
-
Mar 19, 2021
-
- -
-

Auto-Delete, Widgets and Expiring Invite Links

-
This update brings an auto-delete timer for messages in any chat, as well as new flexible invite links and faster access to your chats…
-
-
Feb 23, 2021
-
- -
-

Moving Chat History from Other Apps

-
Over 100 million new users joined Telegram this January, seeking more privacy and freedom. But what about the messages and memories that remain in older apps? Starting today, everyone…
-
-
Jan 28, 2021
-
- -
-

Voice Chats Done Right

-
Today, Telegram groups get an entire new dimension with Voice Chats – persistent conference calls that members can join and leave as they please. Our 12th update in 2020 brings them…
-
-
Dec 23, 2020
-
- -
-

Pinned Messages 2.0, Improved Live Locations, Playlists and More

-
Halloween is just around the corner and we've assembled choice tools to help organize your trick-or-treating. Practice your voodoo skills…
-
-
Oct 30, 2020
-
- -
-

Search Filters, Anonymous Admins, Channel Comments and More

-
Your personal Telegram Cloud is endless and full of spicy memes – to help you find your way around it, we're introducing Search Filters.…
-
-
Sep 30, 2020
-
- -
-

Video Calls and Seven Years of Telegram

-
Today marks seven years of Telegram. In 2013, we began as a small app focused on secure messaging and have since grown into a platform with over 400M users. Now this platform also…
-
-
Aug 14, 2020
-
- -
-

Profile Videos, 2 GB File Sharing, Group Stats, Improved People Nearby and More

-
Today's update brings Profile Videos along with improved People Nearby features, unlimited file sharing with up to 2 Gigabytes per file…
-
-
Jul 26, 2020
-
- -
-

Video Editor, Animated Photos, Better GIFs and More

-
In 2015, Telegram released the most powerful photo editor to be implemented in a messaging app, letting you enhance image quality and add…
-
-
Jun 4, 2020
-
- -
-

400 Million Users, 20,000 Stickers, Quizzes 2.0 and €400K for Creators of Educational Tests

-
Telegram has reached 400,000,000 monthly users, up from 300 million a year ago. Every day…
-
-
Apr 24, 2020
-
-
- -
- -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/400-million.html b/data/telegram.org/blog/400-million.html deleted file mode 100644 index 2cfa223db0..0000000000 --- a/data/telegram.org/blog/400-million.html +++ /dev/null @@ -1,272 +0,0 @@ - - - - - 400 Million Users, 20,000 Stickers, Quizzes 2.0 and €400K for Creators of Educational Tests - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

400 Million Users, 20,000 Stickers, Quizzes 2.0 and €400K for Creators of Educational Tests

- -
- -
- -
- 400 Million Users, 20,000 stickers, Quizzes 2.0 and €400K for Quiz Creators -
- -

Telegram has reached 400,000,000 monthly users, up from 300 million a year ago.

-

Every day at least 1.5 million new users sign up for Telegram. Features like folders, cloud storage and desktop support make Telegram ideal for remote work and study during the quarantine. It's no wonder Telegram is the #1 most downloaded social media application in over 20 countries – people all over the world are switching to Telegram at an accelerating pace.

-
- Telegram's growth over the last 7 years. -
- -

When we started Telegram 7 years ago, we assumed that people will always choose freedom and quality over restrictions and mediocrity. As the gap in popularity between Telegram and its older competitors narrows, we find more and more validity in that original assumption. Thank you for being smart and free!

-

What's next, you might ask? The current global lockdown highlighted the need for a trusted video communication tool. Video calls in 2020 are much like messaging in 2013. There are apps that are either secure or usable, but not both. We'd like to fix that, and we will focus on bringing you secure group video calls in 2020.

-

When will they be ready? You'll be the first to know when we're done, promise. So stop asking. 😈

-

Better Quizzes

-

We added Quiz Mode to Telegram Polls back in January, allowing users to flex their trivia muscles. In recent weeks, we witnessed a surge of more serious educational tests and quizzes created using @QuizBot. Today's update upgrades quizzes with educational features.

-

You can now add explanations that appear as users respond to quiz questions, helping them learn from their mistakes, or giving them more context. Explanations make Telegram quizzes suitable not only for testing knowledge — but also for spreading it.

-
- -
- -
-

For example, update the app and try this test on Telegram History and Features.

-
-

When you create a quiz via @QuizBot, you can set a timer for questions. Timers add to the competitive element of Telegram quizzes, which are often used for exam preparation in student group chats. With the new countdown animation, everyone can see how much time they have left.

-

€400K for Creators of Educational Tests

-

With 2 billion students currently away from schools, the world is in dire need of online educational tools. We’d like to contribute to solving this problem by creating a database of educational tests for all subjects and levels. To do that, today we’re announcing a crowd-sourcing initiative in which we will distribute EUR 400,000 among creators of educational tests.

-

To take part, use @QuizBot to create and publish an original educational test on any subject at any difficulty level, in any language. Feel free to choose anything from basic Medieval European History in English to Mikrobiologie für Experten auf Deutsch – and add any media you require to your questions, but make sure all intellectual property rights are respected.

-

We will publish the quizzes you submit in a searchable directory. Based on their quality and popularity we will then announce the winners in several stages. Submissions for the first stage end on May 15.

-
-

Subscribe to the @contest channel for updates on this and other competitions we run. Last year alone, we distributed 2 Million Euro among the winners of our contests. 💰

-
-

20,000 Stickers

-

While Telegram has been the go-to place for stickers since they first came out, until today there wasn’t an easy way to see all the best stickers all at once. Meet the new sticker directory, where you can browse and search the over 20,000 high-quality free Telegram stickers created in the last 5 years.

-
- -
- -

If you have a particular set in mind, you can find it via search, or if you feel like taking a trip through the Museum of Sticker History, you can scroll through the list and go all the way from today's trends to the first Sticker Sapiens that walked the earth.

-

New Attachment Menu on Android

-

On Android, all sections of the attachment menu are now accessible as expandable layers, making the menu sleek, chic, and easier to use. Also, don't miss the cute animated icons.

-
- -
- -

macOS Improvements

-

Users of Telegram for macOS can now access Shared Media straight from the redesigned profile pages. Those who have a lot of Folders may like the new folder sidebar with icons in the style of Telegram Desktop.

-

By the way, this screenshot was created using the updated in-app photo editor which now allows you to draw on pictures when sending or editing:

-
- New macOS features. -
- -

Bullseye

-

To accompany the animated 🎲 emoji from last update, you can now take a shot at throwing animated darts 🎯 in any chat to see who hits the bullseye first.

-
- -
- -

We hope you like this update – all 400,000,000 of you.

-

- -
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/admin-revolution.html b/data/telegram.org/blog/admin-revolution.html deleted file mode 100644 index cfb3035f2f..0000000000 --- a/data/telegram.org/blog/admin-revolution.html +++ /dev/null @@ -1,261 +0,0 @@ - - - - - Supergroups 10,000: Admin Tools & More - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Supergroups 10,000: Admin Tools & More

- -
- -
- -
- -
- -
-

This is an old blog post. In case you missed it, groups can already have up to 200,000 members each.

-
-

With Telegram 4.1, we're increasing the maximum size of supergroups to 10,000 members each. That’s a lot of people packed into one group, and now users and admins can use search to find specific users among them:

-
- -

Search for members

-
- -

Admins can also search for members in their channels.

-

With groups as big as 10,000 people – the size of a decent small town – you may be looking for some more powerful management tools. And that’s exactly what Telegram 4.1 gives you.

- - -

Admin Rights

-

You can now add admins with specific sets of privileges to help you run your community. Choose who among your trusted admins will be able to add new users, manage messages, block members, edit group info, or even add new admins.

-
- -

Admin rights

-
- -

Partial Bans

-

Admins who don’t want to completely ban members from their supergroups can now partially restrict their rights in order to stop behavior that's causing problems. You can put nasty users into read-only mode or maybe stop them from sending stickers or media for a certain period of time. Now you can do all of this with absolute precision:

-
- -

Partial bans

-
- -

Even robots can get in on the fun. With Bot API version 3.1, you can use admin bots to automatically impose temporary or permanent bans based on member actions. Check out the docs here to start building your robotic police force today.

-

Recent Admin Actions

-

When multiple admins are working with one group, it’s easy to get confused about which admin did what and when (or which admin bot has gone Skynet on your members). That’s why we've added a “Recent Actions” section to the admins page. This section stores a log of all service actions taken in the group in the last 48 hours and is visible to admins only.

-
-
- -

Recent admin actions

-
-
- -

Precise filters

-
- -

Recent actions in supergroups also show messages that were deleted in the last 48 hours and the original versions of edited messages for the same period, so nasty behavior like self-deleted spam will no longer help anyone escape the admins’ wrath.

-

Sharing and Android Pay

-

In other news, Telegram 4.1 for iOS brings you an improved sharing extension. When sharing stuff from other apps to Telegram you can add an optional comment and select multiple recipients easily. 3D Touch on the app icon to see some new actions, including taking a photo/video and sending it to multiple recipients.

-
- -

New sharing extension

-
- -

On Android, Telegram 4.1. gets you Android Pay support for Bot Payments and improved media selection – photos and videos are now shown together when sharing from the attachment menu or gallery.

-

Free speech

-

This update also features anti-censorship tools such as the ability to set up a Proxy server in the “Data and Storage” section of the Settings.

-

We believe in free and secure communication. It’s our responsibility to offer technology to defend our users’ right to privacy and freedom of speech around the world.

-

June 30, 2017
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/albums-saved-messages.html b/data/telegram.org/blog/albums-saved-messages.html deleted file mode 100644 index b61f9fc5fd..0000000000 --- a/data/telegram.org/blog/albums-saved-messages.html +++ /dev/null @@ -1,268 +0,0 @@ - - - - - Albums, Saved Messages and Better Search - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Albums, Saved Messages and Better Search

- -
- -
- -
- -
- -

Starting with Telegram 4.5, whenever you send multiple photos or videos they are grouped into albums. Each album can include up to 10 photos or videos, arranged in the chat as elegantly proportioned thumbnails. They will also result in one notification instead of ten on the recipient’s side.

-
-
- -
-
- -

Photo Order

-

From now on, you can control the order in which photos are sent. Each photo you choose for sharing will show its sequence number. This makes it easy to double check that your “before-and-after” pics will be sent in the correct order.

-

Multiple Profile Photos

-

When viewing a photo from an album, you’ll see other pictures from the same group as thumbnails in the lower part of the screen. Profile photos are now also displayed this way, which makes them much easier to navigate.

-
-
- -
-
- -

Saved Messages

-

You can now bookmark important messages by quickly forwarding them to Saved Messages – your personal cloud storage for any messages or media you may want to send or forward there. Each saved message has a “go to” button that takes you to the right place in the chat where it was originally posted.

-
- -

Saved Messages Chat

-
- -

The Saved Messages chat is always displayed at the top of the list in the sharing and forwarding menus. This makes it easy to save your favorites while keeping things as tidy as before.

-
- -

Number One in the Sharing Menu

-
- -

Saved Messages are easy to find: they are accessible both from the Chats list and from the side panel on Android / Settings on iOS.

-

Improved Search

-

Speaking of finding things, we’ve upgraded the global search algorithm used for finding public channels, groups and bots. Now you can search for public channels and bots by their titles, and most popular items will always be displayed first.

-

Pinned Messages in Channels

-

Channel admins can now pin messages to focus their subscribers’ attention on important announcements. This tool can also come in handy if you want to help new subscribers navigate your channel.

-
- -

Pinned Message

-
- - -

iOS: New Settings, iPhone X Support

-

Telegram 4.5 comes packed with goodies for iOS users. The Settings screen and the context menu in chats got a makeover. Version 4.5 also works great on iPhone X.

-
-
- -

Redesigned Settings

-
-
- -

Edit Settings

-
- -

And that’s it for today. We hope you enjoy these new features while we’re working on the next update!

-
-

-
- -

November 15, 2017
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/android-2-0.html b/data/telegram.org/blog/android-2-0.html deleted file mode 100644 index 80f5a9fe0c..0000000000 --- a/data/telegram.org/blog/android-2-0.html +++ /dev/null @@ -1,257 +0,0 @@ - - - - - Telegram 2.0 for Android: Material Design - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Telegram 2.0 for Android: Material Design

- -
- -
- -

Telegram for Android received a massive update today, featuring a full redesign along Android 5.0 material guidelines and adding long awaited features such as instant full-text cloud search, new flexible privacy settings for last-seen timestamps and account self-destruction.

-

Material Design

-

Every screen was updated to make Telegram consistent with Android 5.0 design standards and animations. We've also added support for the new standards on Android 4.x and even on older 2.x devices.

-
- - - - - -
-
- - -

Demo

-

Here‘s what Telegram’s new material design looks like in motion on a Google Nexus phone, just to give you a taste of the animations:

-
-
-
-
-
-
- -
-
- - -

Instant Full-Text Search

-

You can now find any message you sent or received in Telegram by using the universal search. Tapping a message in search results sends you to its place in your message history. This way you can find stuff even if you only vaguely remember the context.

-
- - -
-
- -

The search is much faster than what you have in GMail and other apps. Our technology guarantees that even if your inbox grows to several hundred thousands of messages, instant search will stay just as fast.

-

Hiding Last Seen Time

-

We take privacy very seriously, so we invested a lot of time and effort to make this feature right. As a result, the Who can see your Last Seen time control allows unprecedented precision and flexibility.

-
- - - -

-
- -

In fact, it's so good that we wrote a whole separate blog post about it. Read more here:
Privacy Revolution — Last Seen Done Right »

-

Account Self-Destruction

-

Big companies like to accumulate data about their users and keep it for an indefinite time. Telegram is not a commercial organization and we value our disk space greatly. Last year we introduced self-destructing messages, today we are adding self-destructing accounts.

-

From now on, if you stop using Telegram and do not login for at least 6 months, your account will be deleted along with all messages, media, contacts and every other piece of data you store in the Telegram cloud. You can change the exact period after which your inactive account will self-destruct – with options ranging from 1 month to 1 year.

-

..but I'm on iOS

-

Most of these new features are also avaible to iOS fans among Telegram users — except for material design of course. In order to maintain the balance, we're also adding a few nifty features to our iOS app today. Read all about them here:
The new Telegram for iOS — GIF search and more »

-

- -

The Telegram Team,
November 19, 2014

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/android-themes.html b/data/telegram.org/blog/android-themes.html deleted file mode 100644 index 0f0410c4ab..0000000000 --- a/data/telegram.org/blog/android-themes.html +++ /dev/null @@ -1,246 +0,0 @@ - - - - - Custom Themes - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Custom Themes

- -
- -
- -
- -
- -

We believe in freedom. This is why Telegram is a free and open platform – for stickers, for bots, and even for third-party client apps. We believe that if we give you freedom, you’ll know what to do with it.

-

Starting today, 85% of Telegram users can completely change what Telegram looks like for them. We are rolling out Custom Themes on Android, and will later support them on less popular platforms.

-

To switch to a different theme or create a new one, go to Settings > Theme. We‘ve included a Dark Theme in that menu for those of you who don’t want to use Telegram as a flashlight in dark places.

-
-
- -

The new dark theme

-
-
- -

Easy on the eyes

-
- -

Create Your Own

-

We've also added a Theme Editor to the app. You can now create new themes and easily share them with other users.

-
-
- -

Choose an element

-
-
- -

Pick a color

-
- -

Just like stickers and bots, Telegram themes are part of an open platform, so anybody can create a theme and dazzle the world with new colors and backgrounds. Here's another example of a theme created by our users:

-
-
- -

Theme preview: Chats list

-
-
- -

Chat screen

-
- -

Check out the @AndroidThemes and Desktop Themes channels for more new themes made by Telegram users.

-

If you're using our iOS app, hold on for a couple of weeks. You‘ll get themes eventually, but for now we’re building something different for you – and it’s truly epic.

-

- -

February 20, 2017
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/archive-and-new-design.html b/data/telegram.org/blog/archive-and-new-design.html deleted file mode 100644 index 9fa2fa687d..0000000000 --- a/data/telegram.org/blog/archive-and-new-design.html +++ /dev/null @@ -1,318 +0,0 @@ - - - - - Archived Chats, a New Design and More - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Archived Chats, a New Design and More

- -
- -
- -
- Introducing archived chats, a new design and more -
- -

Today's update gives you the tools to sort your messages with archived chats, a new design on Android and a handful of other nifty features to make the most of your messenger.

-

Everything in its place

-

Introducing archived chats, the new tool for spring cleaning in your chat list. Sort your active and inactive chats, separate personal stuff from work or banish annoying contacts to your archive for some spectacular revenge!

-
- -
- -

Swipe left on a chat to transfer it to your archived chats folder. When an archived chat gets a notification, it will pop out of the folder and back into your chat list. Muted chats will stay archived forever.

-

You can hide the archive by swiping left on it. See it again by dragging the screen down.

-
- -
- -

Pin an unlimited number of chats in your archive to keep your messages in the order you want. When chats pop out of your archive with a notification, you can archive them again to return them to their original place within the folder.

-
- Pinned chats in the archive -
- -

Bulk actions for a busy chat list

-

Time is money and money buys cat food, so don't waste time and make the most of the bulk actions in your chat list, now also available on Telegram for Android. Long tap on a chat to open the new menu where you can select multiple chats and then pin, mute, archive or delete them, all faster than ever before.

-
- -
- -

Android's new clothes

-

Telegram for Android got a lot slicker, starting with the app's new icon and down to every menu in the app sporting a new design.

-
- Telegram for Android's new icon -

New app icon

-
- -
- Redesigned menus -

Slick new menus

-
- - -

Selecting messages in chats is now not only more stylish but also more functional – note the new quick forwarding button which appears right under your thumb:

-
- -
- -

More info at a glance

-

With the expanded chat list, you can see more text from the messages in your list. Simply select Three lines in the Chat Settings menu to see up to three lines per chat instead of the usual two.

-
- Chat settings, choose between two or three lines per chat -

Chat list view settings

-
- -

Share and share a lot

-

Want to share a message far and wide? Pull up the new streamlined sharing menu to cover the entire screen and select your whole gang. And don‘t fret if you’re short on words, the comment field now supports emoji.

-
- The new sharing menu with online badges and emoji support -

New sharing menu

-
- -

The new design also makes it easier to share sticker packs.

-
- Sticker pack viewer with the new sharing buttons -

New sticker pack viewer

-
- -

You shall not pass

-

Meanwhile on iOS, passcode settings have been made more stylish and more robust to accommodate 6-digit codes, in addition to the previous 4-digit and custom alphanumeric options. Keep it secret, keep it safe 🔒.

-
- -
- - -

Another new feature on iOS allows clearing your recently used stickers so nobody can prove how much you love sending funny dog stickers.

-
- Clear recent stickers on iOS -

Clear recent stickers

-
- -

We also thought that large emoji feel more natural without chat bubbles and made them look like little stickers instead. Aren't they cute?

-
- Clear recent stickers on iOS -

New look for large emoji

-
- -

Easier forwarding, links to messages, online badges

-

Ever selected the wrong chat when forwarding a message? Tap the message snippet above the text box before sending to change where the message is forwarded to.

-
- Switch recipient when forwarding messages -

Switch recipient

-
- -

If you'd rather point to a particular spot in a conversation, you can now copy links to messages in private groups and channels – just like you could with public messages. Needless to say, links to private chats will only work for members of their respective communities.

-
- Copy links to individual messages in a private community -

Links to individual messages

-
- -

Last but not least, you can now instantly see who's online from the chat list and sharing menu to find out who else might be watching cat videos in the middle of the night.

-
- Online badges in chats -
- -

As always, stay tuned for more updates on all our platforms — we look forward to popping back out of your archive with the next version.

-

- -

May 9, 2019
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/autodelete-inv2.html b/data/telegram.org/blog/autodelete-inv2.html deleted file mode 100644 index bb7290b577..0000000000 --- a/data/telegram.org/blog/autodelete-inv2.html +++ /dev/null @@ -1,299 +0,0 @@ - - - - - Auto-Delete, Widgets and Expiring Invite Links - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Auto-Delete, Widgets and Expiring Invite Links

- -
-
-
- -
- Auto-Delete, Widgets and Expiring Invite Links -
- -

This update brings an auto-delete timer for messages in any chat, as well as new flexible invite links and faster access to your chats with home screen widgets. Also, groups can now have unlimited members.

-

Auto-Delete Messages

-

Some conversations aren't meant to last forever, which is why Telegram users can delete messages for all participants in a conversation at any time, without a trace. Since 2013, users can also set a self-destruct timer for messages in Secret Chats.

-

Starting today, you can enable an auto-delete timer in all Telegram chats, which will automatically erase messages for all participants either 24 hours or 7 days after sending.

-
- -
- -

Auto-delete only applies to messages sent after the timer is set, earlier messages will stay in the chat history. Unlike in Secret Chats, the countdown starts when messages are sent, not read.

-
-

To enable the timer on Android, tap ⋮ > Clear History then choose a duration.
On iOS, press and hold a message, tap Select > Clear Chat (top-left) > Enable Auto-Delete.

-
-

All messages show a countdown to their deletion time – simply tap on Android or press and hold on iOS to take a look. 🕵️

-
- Time before expiry -
- -

In groups and channels, only admins can enable or modify the timer.

-

Home Screen Widgets

-

For instant access to your most important chats, add a Telegram widget to your home screen. The Chat Widget shows a preview of recent messages, while the Shortcut Widget shows only names and profile pictures.

-
- -
- -

On Android, chats and messages in the widget will always be up to date, and you can further expand the widget to take up more of your screen. On iOS, widgets will only get fresh data occasionally and can't be expanded – this is due to system limitations.

-
-

To add a widget, press and hold on your home screen, then tap Widgets on Android or the (+) on iOS and search for Telegram.

-
-

Expiring Invite Links

-

Invite links are a quick and easy way to bring 1 or 1 million people to your groups and channels. Along with the main invite link, owners and admins can now create additional links with a limited duration, number of uses, or both.

-
- -
- -

Any invite link can be converted into a scannable QR Code to put on everything from brochures to billboards. You can also see which users joined using each invite link to find out where new members came from or which format has been most effective for growth. 🚀

-
- -
- -
-

To view and manage invite links, tap to open your Group or Channel's Profile > Edit > Invite Links. Tap (⋮) or (⋯) to convert a link to a QR Code.

-
-

Groups with Unlimited Members

-

Telegram groups allow up to 200,000 members to exchange messages, media and stickers. Groups that are close to the limit can now convert into Broadcast Groups that allow unlimited members.

-

Converting to a Broadcast Group makes it so that only admins can send messages, but members can still join voice chats.

-
- -
- -

Broadcast Groups are ideal for large communities, where people can follow along and catch exclusive interviews, news, or just casual talks.

-

Improved Chat Import

-

Our developers are continuing to refine and expand the chat import feature added to Telegram last month. With today’s update, imported messages will now appear sorted by their original date if added to a Telegram chat that is new or has fewer than 1000 messages.

-
- -
- -
-

Sorting by original date is currently available when importing to all one-on-one chats, all newly created groups, and smaller existing groups.

-
-

Improved Reporting System

-

Telegram processes millions of user reports each month to make sure the platform is not abused. To help make this more efficient, we will now always ask you to select specific messages when sending a report.

-

Additionally, all reporting options allow you to add a comment to give more context – like when reporting fake accounts.

-
- -
- -

And More Animated Emoji

-

A new update always means new animations, so test out the new characters below by sending a single emoji in any chat.

-
- -
- -

That's all for today's changes, this message will now delete in 3, 2, 1 … oh. Never mind, this is a blog post, they don't do that yet. 😅

-

- -

February 23, 2021
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - - diff --git a/data/telegram.org/blog/bots-2-0.html b/data/telegram.org/blog/bots-2-0.html deleted file mode 100644 index 8450c72736..0000000000 --- a/data/telegram.org/blog/bots-2-0.html +++ /dev/null @@ -1,260 +0,0 @@ - - - - - Bot Platform 2.0 - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Bot Platform 2.0

- -
- -
- -

At Telegram, we made it our mission to redefine the boundaries of what you can do with your messaging app. Last year we launched the Bot Platform that has unleashed the creativity of thousands of developers.

-

Today we are giving bot developers a whole new dimension with Bots 2.0: inline keyboards, callback and URL buttons, location permissions and on-the-fly message editing. The new bots can also generate any type of content for you to share with friends, including documents, MP3s, videos, stickers, animations and contacts.

-

To give you a taste of the new possibilities, we built some sample bots last weekend – @music, @youtube, @foursquare and @sticker (make sure your Telegram app was updated today before you try them).

-

New Keyboards, New Actions

-

Here's how @music works – it uses an inline keyboard that allows you to interact with it without sending any messages. And it updates its own messages on the fly as you flip through the pages of search results:

-
-
- -
-
- -

New Types of Content

-

The @music bot also works in inline mode, which means it can help you send MP3s to any of your chats, right from the input field:

-
-
- -
-
- -

Inline bots can now send all types of attachments that are available on Telegram. We suspect you're going to like the @sticker inline bot – it can find you relevant stickers based on emoji.

-

New Mechanics

-

Like the @music bot, @youtube also works in two modes. It uses the new clever chat switching mechanic to connect your Telegram account with YouTube:

-
-
- -
-
- -

Once a Youtube account is connected, you can access additional settings via the new menu option above the results.

-

New Permissions

-

Now, @foursquare is an inline bot that utilizes our new location features and helps you send addresses of places and venues nearby. Note how it asks for permission to use your location when you try to send something for the first time:

-
-
- -
-
- - -

New Horizons

-

These sample bots are but the beginning. Our Bot API 2.0 allows developers to create fluid and easy-to-use interfaces for powerful bots. And we will be seeing a lot of new ones in the coming months, after all, 2016 is the year of bots.

-

If you are a developer, take a look at our Introduction to Bots 2.0 and read the full changelog. Also, feel free to subscribe to our official @BotNews channel to stay up to date on platform news.

-

If you are a user, hang on – soon you will have plenty of cool bots to play with. Meanwhile, enjoy the sample bots!

-

- - -
-

Oh. And we almost forgot we've got more new stuff today!
Read on about Sharing and Previews »

-
-

- -

April 12, 2016
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/cache-and-stickers.html b/data/telegram.org/blog/cache-and-stickers.html deleted file mode 100644 index 2dfdf95a3c..0000000000 --- a/data/telegram.org/blog/cache-and-stickers.html +++ /dev/null @@ -1,231 +0,0 @@ - - - - - Clearing Cache and Reordering Stickers - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Clearing Cache and Reordering Stickers

- -
- -
- -

Unlike most messengers, Telegram can take up nearly zero space on your phone, even if you‘re using it heavily. When you remove Telegram data from your device’s local cache to free up space, we'll keep it in the cloud for as long as you need, with virtually no limitations.

-

Today we are introducing new cache management options that make it even easier to maintain Telegram’s slender footprint when space is short — without having to sacrifice useful data. The new Clear Cache option allows you to quickly delete cached media by type.

-
- - - -

-
- -

Using the Keep Media setting, you can control how long unused media stays on your device. If you haven't accessed a file for the specified time, it is automatically deleted from the cache. Naturally, your data will instantly re-download from the cloud the moment you access it again.

-

On iOS it is also possible to clear cached files on a chat-by-chat basis. On Android, this currently works with supergroups and channels (just tap and hold in the chats list, then ‘Delete from Cache’).

-
- -

-
- -

Available on iOS and Android (and coming to WindowsPhone soon), these simple settings help ensure that Telegram will only require the least amount of space on your devices.

-

Reorder Sticker Packs

-

We've also improved the ordering of sticker packs. You can now manually arrange your sticker packs in the order you prefer, and the order will be synced across your devices. Access sticker settings via the new button, right on the sticker panel.

-
- - -

-
- -

We're not done for 2015 yet, so watch out for more updates this year.

-

- - -

December 8, 2015
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/captions-places.html b/data/telegram.org/blog/captions-places.html deleted file mode 100644 index c843fb55c1..0000000000 --- a/data/telegram.org/blog/captions-places.html +++ /dev/null @@ -1,244 +0,0 @@ - - - - - Places, Captions and more - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Places, Captions and more

- -
- -
- -

Today we are adding several long-awaited features in one epic update to our Android and iOS apps.

-

Places

-

When sharing a location, you can now choose venues and landmarks. And when viewing a location, you can get directions. The section was also beautifully redesigned.

-
- - - -
-
- -

Photo Captions

-

Another thing Telegram was lacking – captions for photos. You can now add them to any picture you send, just tap the T in the photo editing panel.

-
- - - -
-
- -

New Voice Messages

-

You can now see whether the recipient has listened to your voice message — and keep track of which ones you've listened to yourself. Voice messages that have not been played yet are now marked with a small dot.

-
- -
-
- -

Smart Notifications

-

Tired of buzzing notifications from active group chats? Sick of multiple notifications every time somebody forwards you a dozen messages? Getting notifications on mobile while chatting with the same person from your desktop? Fixed! Starting today, you will be notified only when it is necessary.

-

Rich link previews

-

As promised, link previews now work for almost any news site — in addition to previews for the most popular services like YouTube and Twitter.

-

Android Goodies

-

Telegram for Android joins the iOS app in showing extended ‘typing’ statuses: you can now see when your chat partner is sending you a photo or recording a voice message. Scrolling and photo animations have become smoother than ever.

-

Last but not least, we've fully redesigned the emoji menu on Android so that it now features a dedicated stickers tab. This is the first drumbeat of the stickers revolution that is coming to Telegram soon.

-
- -
-
- -

Invite Links for Groups

-

OK, this feature is so awesome that it deserves a separate post.

-

- -

The Telegram Team,
April 30, 2015

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/channels-2-0.html b/data/telegram.org/blog/channels-2-0.html deleted file mode 100644 index d94037040c..0000000000 --- a/data/telegram.org/blog/channels-2-0.html +++ /dev/null @@ -1,246 +0,0 @@ - - - - - Channels 2.0 and More - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Channels 2.0 and More

- -
- -
- -

Telegram channels are becoming a worldwide trend. Each day they get more than 400,000,000 views. Today we are introducing several features that will make channels and bots even more powerful tools for connecting with your audience.

-

Links to Posts

-

The Quick Share menu now allows you to copy links to individual messages inside a channel. You can send these links to friends outside of Telegram or post them to other social networks. Following such links will open the channel and highlight the message.

-
- -

Copy Share Link

-
- -

Silent Messages

-

“Is it OK to post now?” “Is this urgent enough to notify everyone?” If you're a channel admin, you know these questions too well. Luckily, you can now send silent messages that will not notify your subscribers. This is very useful for late night or non-urgent updates. Tap on the bell icon to toggle silent messages on and off.

-
- -

Silent messages

-
- -

Admin Signatures

-

There are times when it‘s important to know who posted a certain message. Starting today, you can enable signatures in Channel Info. New messages will be signed with the posting admin’s chosen screen name but will not link to their profile.

-
-
- -

Channel Settings

-
-
- -

Signed Messages

-
- -

Edit Messages in Channels and Supergroups

-

Made a typo? Missed a word? Itching to add something? As of today, you can edit your messages after they were posted. Tap the message (double tap on iOS), then press ‘Edit’. This feature works with supergroups and channels because they both use the same underlying technology.

-

Quick Share Button for Bots

-

Many news organizations are building bots to provide tailored subscriptions. In this update we've made it easier to share the links, pictures and videos you get from bots. Check out the new official @forbesbot to see how this works.

-
- -

Quick Share button for bots

-
- -

Bonus: Sticker Previews

-

In other news, sticker previews now work everywhere including sticker suggestions when you type an emoji and the ‘Add stickers’ screen. Tap and hold on a sticker to see it in full size before sending. The devil's in the details, right?

-

Try it out with the Harry set: https://telegram.me/addstickers/harry

-

- -

And that‘s all we’ve got for you this month.
Stay tuned for more updates in March!

-

- -

February 24, 2016
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/channels.html b/data/telegram.org/blog/channels.html deleted file mode 100644 index 2d8ac564e9..0000000000 --- a/data/telegram.org/blog/channels.html +++ /dev/null @@ -1,224 +0,0 @@ - - - - - Channels: Broadcasting Done Right - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Channels: Broadcasting Done Right

- -
- -
- -
-

UPD: See Channels 2.0 for info on links to posts, silent messages and admin signatures.

-
-

Today we are introducing Channels, a new tool for broadcasting your messages to large audiences. Channels replace the old Broadcast lists and are better in every way. They can have an unlimited number of members, they can be public with a permanent URL and each post in a channel has its own view counter.

-
- -

-
- -

Views from forwarded copies of your messages will be included in the total count. Last but not least, new members can see the entire message history in a channel once they join — all the way to day one.

-

If you'd like an example, join our official Telegram channel to get notified about our updates, or try creating your own channels from the ‘New Message’ menu.

-

iOS 9 Notifications

-

In other good news, we‘ve added Quick Replies from notifications, which are now supported on iOS 9 devices. This means you can reply to messages in Telegram, directly from your iPhone’s lock screen. Split View and more iOS 9 features will become available in early October.

-

Unfortunately, due to a bug in iOS 9, it is currently not possible to display the input field for Quick Replies right away — you‘ll need to press the ’Reply' button in order for it to appear. Quick replies will work as expected when iOS 9.1 is released with the relevant bugfixes.

-

Photo Editor

-

The in-app Photo Editor for iOS was updated with tools to adjust an image's tint, fade, and curves. The existing shadows and highlights tools default to 50% and are now functional in both directions.

-
- - -

-
- -

September 22, 2015
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html b/data/telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html deleted file mode 100644 index 4a6b82ce4d..0000000000 --- a/data/telegram.org/blog/chat-themes-interactive-emoji-read-receipts.html +++ /dev/null @@ -1,297 +0,0 @@ - - - - - Chat Themes, Interactive Emoji, Read Receipts in Groups and Live Stream Recording - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Chat Themes, Interactive Emoji, Read Receipts in Groups and Live Stream Recording

- -
-
-
- - -
- Introducing Chat Themes, Interactive Emoji, Read Receipts in Groups and Live Stream Recording -
- -

Today's update lets you set different themes for individual chats, share your feelings with loved ones using interactive emoji with fullscreen effects, see detailed read receipts in groups and record video and audio from live broadcasts.

-

Chat Themes

-

Telegram has dozens of features to organize your chats and customize their appearance, from Chat Folders to Animated Backgrounds. In this update, coordination and decoration come together with new themes for individual chats.

-

Our designers created 8 new themes that you can apply to specific private chats. Each of the new themes features colorful gradient message bubbles, beautifully animated backgrounds and unique background patterns.

-
- -
- -

Both you and your chat partner can choose the theme for both sides and make any conversation easy to recognize, even when you can't find your glasses. This way you can set different themes for chats with co-workers and family members, so you won't accidentally send that video to your boss again.

-
-

To set a theme for your chat on Android, tap ⋮ > Change Colors. On iOS, tap the Chat Header > ⋯ > Change Colors. Your chat partner will see the theme if they are using the latest version of Telegram.

-
-

Each theme comes with a day and night version and will follow your app's night mode settings – whether you keep it dark all day, or have your chats follow the sun.

-

These first 8 themes are just the beginning – our designers are already working on adding more.

-

Interactive Emoji

-

We love animating emoji, but there are times when even a big red beating heart – that makes your phone vibrate with each beat! – is simply not enough to express your feelings.

-

With a little code, a little drawing and a lot of dark magic, we've created a new way of sharing emotion in real time. Send a single 🎆 🎉 🎈 👍 💩 or ❤️ to any private chat, then tap on the animated emoji to unleash a fullscreen effect.

-

If both you and your chat partner have the chat open, the animations and vibrations play simultaneously on your devices, so you feel close even when you're far apart.

-
- -
- -
-

Your chat partner will only see the effects if they are using the latest version of Telegram.

-
-

Our artists are already back in the dungeons, working on new fullscreen effects for more animated emoji.

-

Read Receipts in Small Groups

-

Both chat themes and interactive emoji currently only work in private chats. But this update also includes a big change for groups.

-

Group messages are marked as read (✓✓) as soon as one other member sees them. In small groups, you can now also select a message you sent to see which group members have read it.

-
- -
- -
-

To protect users' privacy, read receipts in groups are only stored for 7 days after the message was sent. It is not Telegram's business to keep a record of everything you've ever seen.

-
-

Record Live Streams and Video Chats

-

Telegram hosts millions of communities that can create live events for unlimited viewers. Whether it's a once-in-a-lifetime concert or an everyday algebra class, admins can now record Live Streams and Video Chats to publish them for those who missed the live version.

- - -
- -
- -

Admins can start a recording right from the Live Stream or Video Chat menu – with options to record Video and Audio or Only Audio. To record video, choose an orientation for the final video file, Portrait or Landscape. After you finish recording or end the broadcast, the file is instantly uploaded to your Saved Messages.

-
-

Tap ⋮ or ⋯ to open the broadcast menu and start recording. While recording, a red dot appears next to the title of the broadcast.

-
- - -

And that should give you enough things to do until we're back with the next update. As always, it shouldn't take us long.

-

- -

September 19, 2021
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - - diff --git a/data/telegram.org/blog/contacts-local-groups.html b/data/telegram.org/blog/contacts-local-groups.html deleted file mode 100644 index 1ab722b8ca..0000000000 --- a/data/telegram.org/blog/contacts-local-groups.html +++ /dev/null @@ -1,272 +0,0 @@ - - - - - Location-Based Chats, Adding Contacts Without Phone Numbers and More - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Location-Based Chats, Adding Contacts Without Phone Numbers and More

- -
- -
- -
- Telegram 5.8: Adding Contacts Without Phone Numbers, Location-Based Chats and More -
- -

In the previous update, we improved privacy settings and added a way for you to control who can see your phone number. Today we're making it easier to exchange contact info on Telegram.

-

All new chats now have an Add to Contacts button at the top. This allows you to quickly add anyone who messages you to your Telegram contacts, even if you don't know their phone number yet.

-
- Add/Block Buttons in a Chat -
- -

If you'd prefer they disappeared instead, the Block button is right next door.

-

Add People Nearby

-

Ever scrambled for business cards at a beach party? Or dropped somebody's phone into the pool in a “let me type in my number for you” moment? Worry no more.

-

Simply open Contacts > Add People Nearby to quickly exchange contact info with Telegram users who are standing next to you (and also have this section open).

-
- -
- -

This feature comes in especially handy when several people meet to perform the take-my-number dance. Now you can catch all your pokémon in just a few taps.

-

Location-Based Chats

-

Speaking of pokémon, the new People Nearby section also shows Groups Nearby – location-based group chats open for anyone around to join.

-
- -
- -

Tap Create a Local Group to unite your dormitory or apartment building, and maybe you can get Todd in 2C to finally turn his music down.

-
- Location-based group -
- -

This update opens up a new world of location-based group chats for anything from conferences, to festivals, to stadiums, to campuses, to chatting with people hanging out in the same cafe.

-

Transfer Group Chats

-

If you ever get tired of being the host of your group, you can pass the burden on to another administrator. Telegram apps now support transferring ownership rights from any groups and channels to other users.

-

Grant full admin rights to your Chosen One to see the Transfer Ownership button.

-
- Transfer group ownership -
- -

Whether your watch has ended, or you have some business to attend to in King's Landing, passing the torch is a simple, two-tap affair.

-

Enhanced Notification Exceptions

-

Notification Exceptions just got more powerful. You can now toggle message previews for specific chats. If you have many exceptions, use Search to find the right chat — or ‘Delete All’ to get back to square one instantly.

-
- Notification exceptions -
- -

Siri Shortcuts

-

Owners of iOS devices can now use Siri shortcuts to open chats with people. No hands just got no-handsomer.

-
- Siri -
- -

Theme Picker and Icon style

-

We've also revamped the Appearance settings on iOS so that it's easier to see what the different themes will look like even before you apply them.

-
- New theme picker on iOS -
- -

A while back, the Telegram X app for iOS was promoted, becoming the official Telegram, and its previous shell was removed from the store. If you are still using it for some reason, this is a good time to switch — ol' Telegram X is now three versions behind the main branch.

-

Some users told us they didn't want to switch because they liked the Telegram X icon better. So this update adds a way for your iOS app icon to get back in black:

-
- Pick your poison -
- -

By the way, Telegram X for Android is still there and is not going anywhere for now. If you're looking for an alternative interface, feel free to give it a try.

-

- -

June 23, 2019
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/coronavirus.html b/data/telegram.org/blog/coronavirus.html deleted file mode 100644 index 9ffb9f4b8f..0000000000 --- a/data/telegram.org/blog/coronavirus.html +++ /dev/null @@ -1,254 +0,0 @@ - - - - - Coronavirus News and Verified Channels - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Coronavirus News and Verified Channels

- -
- -
- -
- Verified Channels and Coronavirus Info -
- -

Telegram Channels are a powerful tool for broadcasting your messages to unlimited audiences. Since 2015, media organizations and public figures have been using them to reach readers, voters and fans – especially in countries where freedom of speech is limited.

-

Recently, we noticed a new type of channel gaining popularity: those created by Ministries of Health from around the world. India, Malaysia, Israel and many other countries now send news updates, warnings and tips via Telegram.

-
- -
- -
-

More about Channels and their features »

-
-

New Verification Tools

-

To help users distinguish trustworthy sources from fake news, we're launching a streamlined verification process today.

-

If you have verified accounts on other social media services, simply contact our new @VerifyBot to get a verification badge for your channel, group or bot.

-
-

More about Telegram Verification Guidelines »

-
-

Notifications for Users

-

Information is the most powerful weapon in the fight for global health – at least until we get a vaccine. To do our part, we've been sending notifications to all users in countries that have official channels with updates about the virus, offering them to join.

-

We invite all health officials to collaborate on keeping people informed. If you work for your country's Ministry of Health and would like to promote its channel, please verify it first using @VerifyBot, then contact us at corona@telegram.org.

-

Coronavirus Info

-

To make sure users find accurate and relevant information about the pandemic in their region, we've created a special channel which shows up as the top result for all coronavirus-related keywords in Search. It contains a list of official news sources by country:

-

- -

Beyond Channels: Groups and Bots

-

Telegram Channels are good for massive one-way broadcasts, but if you're looking for more interactive ways to inform people, try groups or bots.

-

Telegram Groups can have up to 200,000 members each and offer powerful tools for maintaining order. For example, doctors from the Indian state of Karnataka are using this public group to answer questions from users.

-
-

More about Telegram Groups »

-
-

Telegram Bots are third-party apps that you can interact with right from your chat list. You talk to them using buttons – and they reply with messages and media of all kinds. Bots are extremely flexible and can be used for anything from providing information to integrating with other web services.

-

For example, check out @QuizBot which can create and run quizzes like this one.

-
-

More about Telegram Bots »

-
-

And One More Thing

-

We couldn't do anything about the shortage of masks in the real world, but our artists found a way to squeeze an inexhaustible supply into your app.

-

You can apply masks from this set to any pictures you send using Telegram's Photo Editor. Whether to raise awareness, maintain digital hygiene, or simply to hide your nose is up to you.

-
- -
- -

Stay home. Wash your hands. Be safe. And stay tuned for our next updates!

-

- -

April 3, 2020,
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/cryptocontest.html b/data/telegram.org/blog/cryptocontest.html deleted file mode 100644 index 7ca25a4dad..0000000000 --- a/data/telegram.org/blog/cryptocontest.html +++ /dev/null @@ -1,224 +0,0 @@ - - - - - $300,000 for Cracking Telegram Encryption - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

$300,000 for Cracking Telegram Encryption

- -
- -
- -
-

This contest is over, but Telegram's bug bounty program is always open.

-

Security researchers are welcome to submit any issues they find in the Telegram apps or protocol to us at security@telegram.org. All submissions which result in a change of code or configuration are eligible for bounties, ranging from $500 to $100,000 or more, depending on the severity of the issue.

-
-

Earlier this year we had a contest to decipher intercepted Telegram messages, that did not produce a winner. Today we announce a new contest with an easier task and a larger prize — $300,000 for cracking Telegram's encryption, and this time contestants can not only monitor traffic, but also act as the Telegram server and use active attacks, which vastly increases their capabilities.

-

In this contest you assume the role of a malicious entity in full control of both the communication lines and the Telegram servers themselves.

-
-

UPD The current round of the contest is over. Go to results »

-
-

Your goal is to extract sensitive data (a secret email address) from a Secret Chat between two users — Nick and Paul. You control the entire process, from chat creation to the sending of each individual message and can perform various active attacks, including MITM, KPA, CPA, replay attacks, etc.

-

Contest Interface

-

In order to facilitate the task, we have created an interface, using which you can act as the server and determine which side gets what data. For more details, please check out the Cracking Contest Description.

-

Objectives

-

In order to confirm that Telegram crypto was indeed cracked and claim your $300,000, you‘ll need to send an email to the secret email address that you’ve extracted from one of the messages exchanged by Paul and Nick.

-

Your email must contain:
- The entire text of the message that contained the secret email.
- Session logs for the successful attempt with your user_id.
- A detailed explanation of the attack on the protocol.
- Your bank account details to receive the $300,000 prize.

-

There is also a bonus objective with an independent prize of $100,000.
See full description for details »

-

End Date

-

To prove that the competition was fair, we will add a command that returns the keys used for encryption as soon as a winner is announced. In case there is no winner by February 4, 2015, decryption commands will be added at that date.

-
-
-
- -

November 4, 2014
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/desktop-1-0.html b/data/telegram.org/blog/desktop-1-0.html deleted file mode 100644 index 9577f65739..0000000000 --- a/data/telegram.org/blog/desktop-1-0.html +++ /dev/null @@ -1,250 +0,0 @@ - - - - - Telegram Desktop reaches version 1.0 – and it's BEAUTIFUL - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Telegram Desktop reaches version 1.0 – and it's BEAUTIFUL

- -
- -
- -
- -
- -

Telegram was available for desktops and laptops since 2013. Today it finally graduates to version 1.0 with a fabulous new design.

-

Consistent material design, great animations, and support for custom themes make Telegram for Windows, Mac, and Linux the tool for messaging from your Mac or PC.

-

This is what Telegram Desktop 1.0 looks like:

-
-
- -

Login Screen

-
-
- -

Your Chats

-
-
- -

Smooth animations are now everywhere:

-
- -
- -

Custom Themes

-

If you're looking for an alternative design, Telegram Desktop also supports customized themes. Anyone can make a theme for Telegram Desktop. This theme, for example, changes green outgoing messages to blue:

-
- -

Blue theme

-
- -

And here’s a third-party night mode theme:

-
- -

Dark theme

-
- -

What Else Makes Telegram Desktop Cool?

-

The best thing about Telegram Desktop is that it automatically syncs messages from your phone with your computer using Telegram’s encrypted cloud. Just install it and log in to your account! All your messages, documents, photos and videos will be synced for you from the secure cloud.

-

Thanks to Cloud Drafts, you can even start typing on your phone, then continue on your desktop when you reach home or work.

-

Who needs email now? Telegram Desktop is many times faster and handles attachments like a pro. Just share your t.me/username with those who want to reach you.

-

- -

January 11, 2017
The Telegram Team

-

- -

P.S. For desktop experiences, we also have Telegram Web and Telegram Mac, but our founder insists that Telegram Desktop is the way to go on all platforms.

-

P.P.S. If you're looking for an easy way to get your emails right in Telegram, check out this Gmail bot. Helps one to stay in touch with those who insist on using antique methods of communication.

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/desktop-compact.html b/data/telegram.org/blog/desktop-compact.html deleted file mode 100644 index 9a9fe046b0..0000000000 --- a/data/telegram.org/blog/desktop-compact.html +++ /dev/null @@ -1,213 +0,0 @@ - - - - - Telegram Desktop Adds Compact Mode - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Telegram Desktop Adds Compact Mode

- -
- -
- -

The official Telegram app for Windows, OSX and Linux is now available in compact mode — you can resize the window so that only a single column remains. This makes it easier to use Telegram on smaller desktop or laptop screens.

-
- - - -
- -

You can download Telegram Desktop at desktop.telegram.org. As of last week, this app is also available in the Mac AppStore, alongside with our native OSX app.

-

To log in on your computer, simply enter your phone number and get a code delivered via Telegram to your phone. All your messages (except those from Secret Chats) are instantly synced between all your devices, so you can continue right where you left off.

-

- -

December, 22
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/discover-stickers-and-more.html b/data/telegram.org/blog/discover-stickers-and-more.html deleted file mode 100644 index 414cbe6cb5..0000000000 --- a/data/telegram.org/blog/discover-stickers-and-more.html +++ /dev/null @@ -1,246 +0,0 @@ - - - - - Sticker Search, Multiple Photos, and More - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Sticker Search, Multiple Photos, and More

- -
- -
- -
- -
- -
-

In other news: Telegram has now reached 200 million monthly active users.

-
-

Today we're launching Telegram 4.8 for iOS and Telegram 4.8.5 for Android which make it much easier to discover new stickers. From now on, when you type one emoji, you will see suggestions not just from the sticker sets you've added, but also from other popular sets.

-
- -

Suggested Stickers

-
- -

Sticker Search

-

We've added search for sticker sets. Scroll up in the sticker panel to find the new search field that will help you find something quickly – be it a set you've added, or a brand new pack of easter bears.

-
- -
- -

Multi-Shot Sending

-

Need a couple of extra selfies to maximize dramatic effect? Dog can't stop doing adorable tricks? Not a problem. Use the new + button when taking a photo to take and send multiple media one after another.

-
- -

Take & Send Multiple Photos

-
- -

Auto-Night Mode and Connected Websites

-

Telegram for iOS v.4.8 also includes some of the goodies which Android users have been enjoying since the previous release. With Auto-Night Mode settings you can automatically switch to the dark version of the interface after nightfall or in low-light conditions:

-
- -

Auto-Night Mode Settings on iOS

-
- -

As of v.4.8, the iOS app also supports text formatting in media captions, reporting individual messages in public entities, and has a section where you can manage connected websites.

-

Oh, and we've optimized battery usage so that you can enjoy all of the above even longer on a single charge.

-

- -

March 22, 2018,
The Telegram Team

-

- -
-

P.S. In case you missed this, Telegram has now reached 200 million active users.

-
-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/edit.html b/data/telegram.org/blog/edit.html deleted file mode 100644 index cb8c80e6f9..0000000000 --- a/data/telegram.org/blog/edit.html +++ /dev/null @@ -1,245 +0,0 @@ - - - - - Edit Messages, New Mentions and More - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Edit Messages, New Mentions and More

- -
- -
- -

Farewell to typos! Starting today, you can edit the text of your messages after sending them. This works across all Telegram chats, including groups and one-on-one conversations.

-
- -

Edit messages

-
- -

Simply tap and hold on a message, then press ‘Edit’. If you're on desktop, press the up arrow button to edit your last message. The messages will display a small ‘edited’ label so that it's easy to tell which were altered.

-

New Mentions

-

Mentioning other people in groups is handy since it sends them a notification about your message even if they muted the group. Starting today, you can mention any members in a group – even if they don't have a username. Just type the @ symbol and select whoever you would like to address. Easy!

-
- -

Mention group members

-
- -

People List

-

Speaking of addressing people, you can now get to your recent chats much faster using the new People list in Search.

-
- -

Recent chats

-
- - -

Bot Attachments

-

We've also made it easier for you to access your favorite inline bots. Simply scroll down the attachment menu – and there they are. The more you use them, the higher they will climb.

-
- -

Bots in attachment menu

-
- -

Naturally, you will only see inline bots in the attachment menu if you used them at least once. Try @youtube, @gif or @imdb if you don't know where to start. Check out this post for more info on how to use inline bots.

-

Interface Improvements

-

We‘ve added quick sharing buttons to forwarded messages from bots, channels, and public groups. Notifications about messages with stickers will now show the relevant emoji so that you’ll know the general idea at first glance.

-
- -

Scroll to bottom

-
- -

Last but not least, if you're on iOS, your app now remembers the scroll position in chats when switching to a different chat and back. And scrolling up in a chat summons a new button that will send you back to the bottom in one tap. This button also displays a handy unread message counter if new ones are waiting for you there.

-

- -

And that's it for today. Stay tuned for more updates coming soon!

-

- -

May 15, 2016
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/export-and-more.html b/data/telegram.org/blog/export-and-more.html deleted file mode 100644 index 8f62446caa..0000000000 --- a/data/telegram.org/blog/export-and-more.html +++ /dev/null @@ -1,238 +0,0 @@ - - - - - Chat Export Tool, Better Notifications and More - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Chat Export Tool, Better Notifications and More

- -
- -
- -
- -
- -

Today’s Telegram update brings you an easy way to save conversations on your disk. In just a few taps, you can export some (or all) of your chats, including photos and other media they contain. As a result you’ll get all your data accessible offline in JSON-format or in beautifully formatted HTML.

-
- -

Data Export Results

-
- -

To use this feature, make sure you have the latest version of Telegram Desktop installed on your computer, then click Settings > Export Telegram data. This tool will be particularly useful for users who have millions of messages and can’t easily access the oldest parts of their messaging history.

-
- -
- -

You can export individual chats by opening the menu in any chat and choosing Export chat history.

-

Exceptions in Notifications

-

Telegram was the first app to give its users notorious flexibility in fine-tuning how their message notifications work. Today we are taking this further by adding Exceptions to the notifications settings, where you can see which chats are excluded from the global settings you defined in Settings > Notifications.

-
- -

Notifications Exceptions

-
- -

Muting all chats but a few (or vice versa) has never been easier.

-

Improved Telegram Passport

-

We’ve been overwhelmed by the reception of Telegram Passport – the tool to log into third-party apps that require real-life identity. Just two weeks after its launch, Passport can be used to sign up for many services, from established sharing economy services to blockchain startups.

-
-To name just a few projects that integrated Telegram Passport: Sum & Substance (KYC & user verification), CEX.IO and Xena (cryptocurrency exchanges), CryptoPay (wallet), YouDrive (carsharing), Profi and Worki (job marketplaces), Minter Network and Minexcoin (blockchain startups), KICKICO, Cryptonomos and ICOadmin (ICO platforms).

- -

Building on this success, today we’re upgrading Passport to support names in original languages and additional types of documents. We’ve also strengthened the algorithms that encrypt Passport data to better protect your data against hacking attacks coming from Telegram (however unlikely those may seem). This way we further ensure that only you have access to your private data.

-

Source Code and APIs

-

As always, you do not have to take our word on how our encryption works. The updated source code of Telegram apps reflecting all of today’s changes is available on GitHub and open for everybody to review. If you are a developer of a service that requires identity verification, make sure you check out these docs explaining how Telegram Passport can be integrated into your app.

-

- -

August 27, 2018
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/filters-anonymous-admins-comments.html b/data/telegram.org/blog/filters-anonymous-admins-comments.html deleted file mode 100644 index 20e5bcd4dd..0000000000 --- a/data/telegram.org/blog/filters-anonymous-admins-comments.html +++ /dev/null @@ -1,261 +0,0 @@ - - - - - Search Filters, Anonymous Admins, Channel Comments and More - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Search Filters, Anonymous Admins, Channel Comments and More

- -
-
-
- -
- Introducing Search Filters, Anonymous Group Admins, Channel Comments and More -
- -

Your personal Telegram Cloud is endless and full of spicy memes. To help you find your way around it, we're introducing Search Filters. Today's update also features Anonymous Admins to make your battle for freedom safer and Channel Comments to make sure everyone's voice is heard.

-

Search Filters

-

From now on, you can filter search results by type using the new tabs: Media, Links, Files and others. To search a particular time period, just type “August 14” or “Yesterday”. Typing the name of any person, group, channel or bot will add a filter by source.

-
- -
- -

These search filters can be combined, which lets you look for something as specific as messages with a link, sent in March 2016, containing the word “boat”.

-

Anonymous Group Admins

-

Telegram is increasingly used to organize protests for democracy and freedom. Today we're introducing another tool for safer protests.

-

Toggle Remain Anonymous in Admin rights to enable Batman mode. The anonymized admin will be hidden in the list of group members, and their messages in the chat will be signed with the group name, similar to channel posts.

-
- Post from an anonymous admin in a group -
- -

Channel Comments

-

Speaking of Channels, we've added a comment button to posts on channels with discussion groups. Comments show up in a cozy little thread of their own, but will also land in the discussion group to keep everyone in the loop and make it easier for admins to keep the conversation civil.

-
- -
- -

If you are not a member of the channel's discussion group, you will be notified about replies to your comments via a new chat called Replies.

-
-

For a limited time only, you can test this feature in this channel.

-
-

If you'd like to enable discussions in your own channel, head to Channel Settings > Discussion.

-

Amazing Android Additions

-

Our Android wizards didn't forget to pack some new smooth animations. To get a taste, try expanding or hiding your keyboard – or switching between your day and night themes from the left menu. You will also see animated popups when deleting messages, changing notifications, saving media, etc.

-
- -
- -

In case you're more into practical things, press and hold on any profile picture in a group chat to take a closer look. And if you're using multiple accounts in one app, you can now preview the chat lists of your other accounts using the same gesture in the account switcher.

-

More Animated Emoji

-

We carry on with our quest to animate every emoji in existence. To get one of these 👇 in a chat, simply send a message with a single emoji.

-
- -
- - -

- -

And that's all for today, see you in the comments.

-

- -

September 30, 2020
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - - diff --git a/data/telegram.org/blog/group-video-calls.html b/data/telegram.org/blog/group-video-calls.html deleted file mode 100644 index a9b82fc3e0..0000000000 --- a/data/telegram.org/blog/group-video-calls.html +++ /dev/null @@ -1,264 +0,0 @@ - - - - - Group Video Calls - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Group Video Calls

- -
-
-
- -
- Introducing Group Video Calls -
- -

Today's update lets you turn on your camera or share your screen during Voice Chats in groups – on all devices, including tablets and desktops. This brings voice chats to a whole new level, ready for online classes, business meetings and family gatherings.

-

We're also introducing animated backgrounds, stylish message animations and more – enough to fill a second blog post.

-

Group video calls

-

Voice chats in any group can now seamlessly turn into group video calls – just tap the camera icon to switch your video on.

-
- -
- -

Tap on any video to make it fullscreen. If you pin a video, it will stay focused as new users join the call and turn on their cameras.

-
-

To start a voice chat, check the ⋮ menu in the profile of any group where you are an admin (on iOS, you will find a 'Voice Chat' button right in the group profile).

-
-

While audio-only participants are unlimited, video is currently available for the first 30 people who join the voice chat. This limit will increase soon as voice chats take on streaming games, live events and more.

-

Screen sharing

-

In addition to your camera feed, you can also share your screen – or both at the same time.

-
- -
- -
-

To share your screen, tap ⋮ or ⋯ in any app and select it from the menu.

-
-

Noise suppression options

-

We've improved noise suppression in voice chats to keep everyone's audio clear and crisp, even when you're eating something crispy. We've also added a toggle to turn noise suppression off in settings – for those times when munching has meaning.

-
- Noise suppression settings -
- - -

Tablet and desktop support

-

Tablets and computers have more screen space and offer more display options – tap to open the side panel and see a split-screen view of the video grid and list of participants, optimized for both portrait and landscape orientation.

-
- -
- -

Voice chats on desktop open in a separate window, so you can type and talk without minimizing anything. Desktop apps also have selective screensharing so you can broadcast an individual program instead of your whole screen.

-
- -
- -

When you're using a desktop app, anyone who starts sharing their screen will be pinned automatically. This is especially useful when small teams meet to coordinate their work.

-

And more?

-

That's it for today… No, wait. In fact, we're having two updates instead of one:

-
-

Read on to learn about Animated Backgrounds and more.

-
-

- -

June 25, 2021
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - - diff --git a/data/telegram.org/blog/inline-bots.html b/data/telegram.org/blog/inline-bots.html deleted file mode 100644 index d205fd3371..0000000000 --- a/data/telegram.org/blog/inline-bots.html +++ /dev/null @@ -1,234 +0,0 @@ - - - - - Introducing Inline Bots - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Introducing Inline Bots

- -
- -
- -

Bots became an integral part of Telegram for many users, but communication with them wasn't always easy. You had to send them messages in separate chats or add them to your groups. Today we are introducing a quicker way to contact bots.

-

With the new inline mode, bots become omnipresent and can be used as a tool in any of your chats, groups or channels – it doesn't matter, whether the bot is a member or not. Inline bots can help you with dozens of different tasks, like quickly sending relevant GIFs, pictures from the Web, YouTube videos, Wikipedia articles, etc.

-
-
- -
-
- -

How does it work?

-

We've created several sample bots for you to try out: @gif, @vid, @pic, @bing, @wiki, @imdb and @bold. To see them in action, simply type one of their @usernames in the message field in any chat, then type some keywords. The bot will offer you relevant content.

-
- - -
-
- - -

Tap on an item to instantly send it to the chat. This way you can share stuff from bots without any hassle. Inline bots don't see any messages in your chats – they only receive what you type after their username in the input field.

-
- - -
-
- -

Tap on ‘via @username’ to send a new request to the bot. Recently used inline bots will also show up in the suggestion box when you type @ in the input field in any chat.

-

A new dimension for bots

-

Like pretty much everything else at Telegram, inline bots are part of an open platform, available for free to every developer in the world starting today. Hundreds of new inline bots are sure to arrive once developers start supporting the new mode.

-

If you are a developer, take a look at our Introduction to Inline Bots. Also, feel free to subscribe to our official @BotNews channel to stay up to date on platform news.

-

- -

The Telegram Team,
January 4, 2016

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/instant-camera.html b/data/telegram.org/blog/instant-camera.html deleted file mode 100644 index eeab87a2c0..0000000000 --- a/data/telegram.org/blog/instant-camera.html +++ /dev/null @@ -1,229 +0,0 @@ - - - - - Instant Camera and More 3D Touch - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Instant Camera and More 3D Touch

- -
- -
- -

When taking pictures, even a split second can make the difference between capturing the perfect moment or missing it entirely. Starting today, our iOS users can snap a photo or take a video in no time. To access your camera quickly, simply tap and hold the attachment button, and you're ready to shoot:

-
-
- -
-
- -

This quick camera interface defaults to selfie mode with flash on, but you can change this and it will remember your choice.

-

With this update it also becomes easier to record videos using the standard camera interface. Press and hold the big button and the recording starts. By popular demand, videos you record in-app will now be saved to your device in Full HD quality.

-

More 3D Touch and More

-

Starting today you can use 3D Touch to preview photos and videos everywhere, including the attachment menus, message history, and the Shared Media section. The same goes for profile pictures: That's right, you no longer need to go to chat info to check them out in full size.

-
-
- -

We've also added Uber and Citymapper as options for opening a location:

-
-
- -

And, speaking of opening stuff, we've fixed the issue with files – you can now open any file you get in other apps again. This is extremely useful, given that you can share and store an unlimited number of documents and files of any type on Telegram.

-

- -

That's it for today, stay tuned for more updates coming soon! The cool features we are adding in the next release will be available for all platforms.

-

- - -

April 28, 2016
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/invite-links.html b/data/telegram.org/blog/invite-links.html deleted file mode 100644 index 3c98d9290e..0000000000 --- a/data/telegram.org/blog/invite-links.html +++ /dev/null @@ -1,217 +0,0 @@ - - - - - Migrating Existing Group Chats to Telegram - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Migrating Existing Group Chats to Telegram

- -
- -
- -

In addition to numerous great features in today's update, we’re happy to introduce a new way to move your existing group chats to Telegram — invite links for admins.

-

Each passing month brings more reasons to switch to Telegram from older services. Persistent history, instant full-text search, open platform, unlimited file sharing, rich link previews, native desktop apps, replies, mentions, hashtags and much more.

-

And yet, if you‘ve ever tried moving your existing group chats from other apps to Telegram, you know it was not easy. There was simply too much work to do and too much friction — you had to collect everyone’s usernames or phone numbers and add them to your group one by one. We're glad to announce that these days are over.

-

Invite Links

-

With invite links for groups, all you have to do is send a link to your existing group chat in any messaging service that your friends might still be using. As soon as they get Telegram, they can instantly join your Telegram group just by following that link.

-

Where do you get the link? Once you've created a group on Telegram, head to the "Add participant…” section and tap “Invite to Group via Link”. Easy!

-
- - - -
-
- -


- -

The Telegram Team,
April 30, 2015

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/live-streams-forwarding-next-channel.html b/data/telegram.org/blog/live-streams-forwarding-next-channel.html deleted file mode 100644 index d9f50e579b..0000000000 --- a/data/telegram.org/blog/live-streams-forwarding-next-channel.html +++ /dev/null @@ -1,285 +0,0 @@ - - - - - Live Streams, Flexible Forwarding, Jump to Next Channel, Trending Stickers and More - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Live Streams, Flexible Forwarding, Jump to Next Channel, Trending Stickers and More

- -
-
-
- -
- Live Streams, Flexible Forwarding, Jump to Next Channel, Trending Stickers and More -
- -

Telegram was launched just over 8 years ago and today we are continuing our tradition of monthly updates with version 8.0. This update brings live streams with unlimited viewers to groups and channels, options to remove captions from media and hide sender names when forwarding, an easy way to jump to the next unread channel without going back to your chat list, an improved sticker panel, new animated emoji and more.

-

Unlimited Live Streams

-

Our previous update made Group Video Calls a powerful tool for live broadcasts — and now their audience is unlimited (except by the popularity of your channel, or the population of Earth, whichever is more relevant in your case).

-

Start a Live Stream in a channel or a Video Chat in a group – both now support unlimited viewers. The power to run your own TV station is here, right in your pocket.

-
- -
- -
-

To begin, tap 'Video Chat' (in Groups) or 'Live Stream' (in Channels) on the profile page of a community where you are an admin.

-
-

The viewers of your Live Stream can also raise their hand and join your broadcast if you allow them to speak.

-

Flexible Forwarding

-

Forwarding has become a much more relaxing experience. Tap the 'Forward Message' label above the message bar to open a preview window, showing how the messages will look when they are sent – along with several customization options.

-
- -
- -

You can choose to hide the sender's name or hide captions on media messages. You can also deselect messages you don't want to send or change the recipient if you tapped the wrong chat.

-

Jump to Next Channel

-

There are millions of one-to-many channels on Telegram that users follow for news, events, and content.

-

To keep up with the news easily, you can now scroll through the channels you follow without going back to your chat list. When you reach the bottom of a channel, pull up to go to the next unread channel.

-
- -
- -

If you have organized your chat list with Folders or Archived Chats, the app will follow the structure you have set up: channels in the current folder, then within each folder, then those left in All Chats and the Archive. Simply open a channel from your Studies folder to read them all without getting distracted by Memes — and vice versa.

-

Trending Stickers

-

Thanks to an open platform and thousands of free, high-quality stickers in the sticker directory, there's a perfect sticker for every situation. This update makes it easier to find the one.

-

Trending Stickers are now shown above ‘Recently Used’ in your sticker panel. Tap 'Add' to save a pack for the future — the trending sticker section is one of the few things in this world that gets updated more often than the Telegram apps.

-

When you scroll through your packs at the top of the panel, the thumbnails expand and show the names of your sticker packs.

-
- -
- -

Telegram for Android also got larger previews for sticker suggestions. To get suggestions, enter one emoji in the input field. To see more suggested stickers, pull upward on the suggestions panel.

-
-

If you have a particular thing in mind and don't have it among your sets, type a word in the search field to find matches from the sticker directory. Try 'yellow', 'animal', 'dog', etc.

-
-

Choosing a Sticker

-

Similar to 'typing…' or 'recording a voice message', the apps now show a 'choosing a sticker' status at the top of the chat — so you know that your chat partner is still there, just looking for the perfect animated response.

-
- -
- -

Unread Comment Counters

-

Many channels have comments enabled for their posts so that subscribers can interact and share their thoughts. We've recently had a great chance to test this with thousands of birthday wishes — thank you all for your support.

-

Just like with chats, when you open a comment thread that has new messages, a counter will now appear showing the number of unread comments.

-
- Unread comments in a thread you just opened -
- -

New Animated Emoji

-

This month we asked ourselves: “Should we stop animating more and more emoji with each update?” After a heated discussion we arrived at this answer: “Probably not.” Send a message with a single emoji to get one of these new masterpieces in a chat:

-
- -
- -

That's it for today — and we already have some cool stuff in development for the next update. See you there!

-

- -

August 31, 2021
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - - diff --git a/data/telegram.org/blog/masks.html b/data/telegram.org/blog/masks.html deleted file mode 100644 index 1e5b415f63..0000000000 --- a/data/telegram.org/blog/masks.html +++ /dev/null @@ -1,248 +0,0 @@ - - - - - Photo Editor 2.0, Masks and Homemade GIFs - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Photo Editor 2.0, Masks and Homemade GIFs

- -
- -
- -

Last year we introduced the most powerful photo editing tool ever to be implemented in a messaging app. This allowed you to instantly improve photos before sending them on iOS and Android.

-

Today we’re pushing the photo editor to the next level with the fun stuff: you can now add drawings, masks, stickers and text right onto your pictures.

-
-
- -
-
- -

This is easy: just choose a mask, and it will be automatically positioned in the right place. Telegram identifies faces on photos and uses mask meta-data to find the perfect spot.

-

Our artists created hundreds of beautiful and fun masks as examples, but everything we do here in Telegram is an open platform. So as of today, anyone can use the /newmasks command for the @stickers bot to upload their own masks.

-
-
- -

Masks Button (top right)

-
-
- -

Adding Masks

-
- -

When opening a photo, you will see a list of mask sets that were used on it. This way popular custom masks will quickly become viral.

-

GIFs Democratized

-

Another thing that’s likely to spread virally now are your GIF-animations. Creating your own GIFs has never been easier: simply record a video in Telegram and tap the new “mute” button to share it as a looped autoplayed GIF.

-
-
- -
-
- -

The animation will be saved to your GIFs section so that you can quickly react to anything with a set of your own prerecorded GIF-emotions.

-

Trending stickers

-

The last addition to this entertainment-heavy update is the trending stickers tab. Whenever you’re feeling hungry for new stickers you can find the latest additions in the stickers panel in any of your chats.

-
- -

In-chat Trending Stickers

-
- -

- -

We're back from the summer break, so watch out for more updates coming your way soon.

-

- -

September 23, 2016
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/moar-stickers.html b/data/telegram.org/blog/moar-stickers.html deleted file mode 100644 index 30be8c9d12..0000000000 --- a/data/telegram.org/blog/moar-stickers.html +++ /dev/null @@ -1,343 +0,0 @@ - - - - - MOAR Stickers! - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

MOAR Stickers!

- -
- -
- -

Two months ago we launched a new kind of stickers, bringing popular memes, art and history together as an enhanced way of expressing emotions. Over the last few days we've added 15 new stickers to the original set.

-

Start a message with an emoji from this list to see emotionally corresponding stickers:

-
- - -
-
Napoléon Bonaparte:
"In France, only the impossible is admired" -
-
- -
-
- - -
-
Jimi Hendrix accepts the challenge -
-
- -
-
- - -
-
Dante's "What the HELL?!" -
-
- -
-
- - -
-
LOL Marley -
-
- - -
-
- - -
-
Screamin' Jay Hawkins:
"Don't put that spell on me!" - -
-
- -
-
- - -
-
Audrey is on the verge of tears -
-
- -
-
- - -
-
Malcolm X: "Mother of..." -
-
- -
-
- -
-
Virginia Woolf: "Go on..." -
-
- -
-
- - -
-
Poe is sceptical -
-
- -
-
- -
-
Coco Chanel is unmoved -
-
- -
-
- - -
-
Frederick Douglass is in a dark mood -
-
- -
-
- - -
-
Princess Diana blushing -
-
- - -
-
- - -
-
Julius Caesar approves -
-
- -
-
- - -
-
On second thought... No. -
-
- -
-
- - -
-
Kisses from Cleopatra -
-
- -
-

Remember that it's easy to send your own stickers in Telegram. Simply send a .webp image with a transparency layer as a file in your chat, and it will become a sticker.

-

- -

March 11, 2015
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/move-history.html b/data/telegram.org/blog/move-history.html deleted file mode 100644 index e389baa40c..0000000000 --- a/data/telegram.org/blog/move-history.html +++ /dev/null @@ -1,284 +0,0 @@ - - - - - Moving Chat History from Other Apps - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Moving Chat History from Other Apps

- -
-
-
- -
- Moving Chat History from Other Apps and More Privacy -
- -

Over 100 million new users joined Telegram this January, seeking more privacy and freedom. But what about the messages and memories that remain in older apps?

-

Starting today, everyone can bring their chat history – including videos and documents – to Telegram from apps like WhatsApp, Line and KakaoTalk. This works both for individual chats and groups:

-
- -
- -

To move a chat from WhatsApp on iOS, open the Contact Info or Group Info page in WhatsApp, tap Export Chat, then choose Telegram in the Share menu.

-

On Android, open a WhatsApp chat, tap ⋮ > More > Export Chat, then choose Telegram in the Share menu:

-
- -
- -
-

WhatsApp for iOS also lets you export chats directly from the chat list. Swipe left on a chat, then choose '…' > Export Chat.

-
-

Messages will be imported into the current day but will also include their original timestamps. All members of the chat on Telegram will see the messages.

-

Move Chats and Save Space

-

The best part is that the messages and media you move don’t need to occupy extra space. Older apps make you store all data on your device – but Telegram can take up virtually no space while letting you access all your messages, photos and videos anytime you need them.

-
-

You can free up space and control your cache size in Settings > Data and Storage > Storage Usage.

-
-

Control Your Digital Footprint

-

Your data is your business, which is why Telegram users can not only export their chats, but also delete messages they send and receive for both sides – without a trace.

-

With this update, you get even more control: secret chats, groups you created and call history can now also be deleted for all sides at any time.

-
- -
- -

Telegram servers don’t store information about deleted chats and call logs, so the data will disappear completely, forever.

-

Improved Voice Chats

-

You can now see which of your groups have active Voice Chats from the top of the Call History page.

-

While in a voice chat you can adjust the volume of individual participants to manage microphone levels. Adjustments made by group admins are applied for all listeners.

-
- -
- -

Improved Audio Player

-

When a track is playing, tap the author name in the player to see their tracks from all your chats. If you need to skip ahead or repeat something you missed, press and hold on the Next and Previous buttons to fast-forward and rewind.

-
- -
- -

We’ve also added a fade effect to please your ears when you pause and resume the music.

-

Greeting stickers

-

If you have contacts who joined Telegram recently, it may be a nice touch to welcome them using one of Telegram's unique features. A greeting sticker will be suggested in your new chats, ready to send in one tap.

-
- -
- -

New Android Animations

-

A new update means sleek new interface animations. See if you can catch them all when downloading files, playing music, or loading chats after logging in.

-
- -
- -

Reporting Fake Channels

-

All Telegram apps let you report spam and other types of illegal content, including calls to violence or child abuse. Now you can also report fake channels or groups that impersonate famous people or organizations. Open their profile page and tap '…' > Report > Fake Account to let our moderators know.

-

Improved Accessibility

-

Many accessibility improvements have been added for both TalkBack and VoiceOver users. As we continue to refine app interfaces for all users, we welcome additional feedback on our Suggestions Platform.

-

A warm welcome to everyone who joined us recently! The next update shouldn’t take long.

-

- -

January 28, 2021
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - - diff --git a/data/telegram.org/blog/new-profiles-people-nearby.html b/data/telegram.org/blog/new-profiles-people-nearby.html deleted file mode 100644 index d5c5d02873..0000000000 --- a/data/telegram.org/blog/new-profiles-people-nearby.html +++ /dev/null @@ -1,263 +0,0 @@ - - - - - New Profiles, Fast Media Viewer and People Nearby 2.0 - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

New Profiles, Fast Media Viewer and People Nearby 2.0

- -
- -
- -
- New Profiles, Fast Media Viewer and People Nearby 2.0 -
- -

Hundreds of millions rely on Telegram to share precious moments with their loved ones. Today we're making it easier to relive shared memories with redesigned profiles, instant access to shared media, and new ways to thumb through pictures and videos.

-

In case you're more of a digital extrovert, the updated People Nearby section offers fresh ways to forge new friendships.

-

Redesigned Profile Pages

-

This update transforms profiles into one of the most functional (and beautiful) sections of the app. It's simpler than ever to see the photos, videos and links you've shared with your friends – or browse their profile pictures.

-
- -
- -

Intuitive Media Browsing

-

You can now flip through media from chats and profiles with taps – no more smudges on your screen from repeatedly swiping. Simply hit the right or left side of an image to go forward and back.

-

In case you're wondering where to best try out these new features, look no further than the updated People Nearby section.

-

People Nearby 2.0

-

Last June, we added People Nearby for exchanging contact info face-to-face. With this update, People Nearby 2.0 can help you meet new friends, or arrange a last-minute date for Valentine's Day.

-

Head over to Contacts > People Nearby to see adventurous Telegram users in the area. Tap Make Myself Visible to join them and display your profile to others around you. They will be able to find you and send you messages – even if you navigate away from the page or close the app.

-
- -
- -

If you decide you're no longer in the mood for adventure, tap Stop Showing Me to re-engage your cloaking device.

-

New Animated Emoji

-

We couldn't pass up the chance to let you shower important people in your life with the newest animated emoji. 😘 😍 😻 🥰 💑 💋 💝 🧡 💛 💚 💙 💜 🖤 🤍 🤎 💔 – and of course 💌 – have just become a lot more moving.

-
- -
- -

If your emoji has a heart, we'll give it a beat. Stay tuned for the next update!

- - -

- -

February 13, 2020
XOXO
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/passport.html b/data/telegram.org/blog/passport.html deleted file mode 100644 index 8cca4e32d8..0000000000 --- a/data/telegram.org/blog/passport.html +++ /dev/null @@ -1,233 +0,0 @@ - - - - - Introducing Telegram Passport - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Introducing Telegram Passport

- -
- -
- -
- -
- -

Our digital lives are getting closer and closer to the real world, and the number of services that need to know your real-life ID increases accordingly. Before today, this meant you had to upload the same document scans over and over for each new app. No more!

-

Meet Telegram Passport – a unified authorization method for services that require personal identification. Upload your documents once, then instantly share your data with services that require real-world ID (finance, ICOs, etc.).

-
- -
- -

Protected by End-to-End Encryption

-

Your identity documents and personal data will be stored in the Telegram cloud using End-to-End Encryption. It is encrypted with a password that only you know, so Telegram has no access to the data you store in your Telegram passport. When you share data, it goes directly to the recipient.

-
- -

Sharing Data with an App

-
- -

In the future, all Telegram Passport data will move to a decentralized cloud.

-

Try It Now

-

If you'd like to see a real-life implementation of Telegram Passport, head over to ePayments.com – the first electronic payments system to support registration and verification with Telegram Passport.

-

You can also try out how Telegram Passport works using this page to request data.

-

Please note that you need the latest version of Telegram to access this feature. Once you've uploaded some documents, you will see your data in Settings > Privacy & Security > Telegram Passport (on iOS: Settings > Telegram Passport).

-

Connect Telegram Passport

-

All developers are welcome to integrate Telegram Passport into their apps and services free of charge. It takes minimum effort and can save many hours of coding.

-

If you are building a service that requires real-life ID, check out the API docs for SDKs and examples.

-

Stay Tuned

-

In the future, we will be adding third-party verification for Telegram Passports. This way, services won't even need to request the data itself, instead relying on the fact that the Telegram account was approved by a verification provider and the person is real.

-

- -

July 26, 2018
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/payments-2-0-scheduled-voice-chats.html b/data/telegram.org/blog/payments-2-0-scheduled-voice-chats.html deleted file mode 100644 index 6ecb091d68..0000000000 --- a/data/telegram.org/blog/payments-2-0-scheduled-voice-chats.html +++ /dev/null @@ -1,319 +0,0 @@ - - - - - Payments 2.0, Scheduled Voice Chats, New Web Versions - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Payments 2.0, Scheduled Voice Chats, New Web Versions

- -
-
-
- -
- Payments 2.0, Scheduled Voice Chats, New Web Versions and More -
- -

This update brings Payments 2.0 for all Telegram chats, Scheduling and Mini Profiles for Voice Chats, new Telegram apps for your browser, and more.

-

Payments 2.0

-

We first added support for payments in 2017. Payment bots allowed users to securely pay for goods and services without leaving the app – anything from ordering a pizza to hailing a taxi, to replacing winter tires when you're tired of winter.

-

Starting today, merchants can natively accept credit card payments in any chat, relying on 9 integrated third-party payment providers such as Stripe.

-

Buyers can add a tip whenever they make a purchase to show some extra love to their favorite artists, stores, or delivery drivers. Payments can now be made from any app – including desktop apps.

-
- -
- -

This is a free and privacy-conscious platform – Telegram takes no commission, and stores no payment information. Credit card information is sent directly to the payment provider and shipping information is shared with the merchant so they can send you your goods.

-
-

We've created a demo channel with the most exotic imaginary goods and services no money can buy, so you can test how this works without spending a penny.

-
-

Any merchant can start using the Payments API without getting additional approvals from Telegram. Developers interested in integrating payments can find all the details in the Payments Manual.

-

Scheduled Voice Chats

-

Voice Chats give users the option to catch up with a few friends or tune in to massive broadcasts with millions of listeners.

-

Admins of groups and channels can now schedule a Voice Chat for a particular date and time instead of creating one right away. This gives community members time to let their friends know and get the popcorn ready.

-
- -
- -

Users will see a colorful countdown at the top of the chat. Those too busy to watch the countdown can opt to receive a notification when the voice chat starts.

-
- -
- -
-

Admins can schedule a Voice Chat from their Group or Channel's profile page. On Android, tap ⋮ > Start Voice chat > Schedule Voice Chat. On iOS, tap the Voice Chat button and select Schedule Voice Chat.

-

Don't worry, the chat won't start automatically when the countdown reaches zero – only when an admin presses the Start Now button.

-
-

Mini Profiles for Voice Chats

-

You can now expand profile pictures and bios to get a better idea of who you're chatting with – without leaving the voice chat window.

-
- -
- -

You can also change your profile picture and edit your bio without leaving the chat – like changing from Shirley to Grognak the Barbarian as you meet for Dungeons and Dragons.

-

New Web Versions

-

Telegram's first Web Version was launched in 2014. Ever since, our pet demon of internal competition kept whispering: 'Why have one web version when you can have two?'

-

Today we're adding two new, fully-featured Telegram web apps – both supporting animated stickers, dark mode, chat folders and more.

-
- -
- -

With the new web versions you can get instant access to your chats on any device – desktop or mobile. These apps are incredibly efficient, requiring only a 400 KB download (that's like two photos of a medium-sized cat) and no installation.

-

Take them for a test drive, and see which one you like best:

- -

Like other Telegram apps, all our web versions are standalone: once you've logged in, you do not need to keep your phone nearby or connected to the internet.

-
-

If you find an issue with either of the new apps, let us know using our Suggestions Platform.

-
-

Direct Download for Android

-

In case you're more of an app person, you can now also download Telegram for Android directly from telegram.org. Apps installed from the website will automatically update to the latest version. You are likely to get new versions several days or weeks faster this way because you won't have to wait for updates to be reviewed by the store.

- - -
- -
- -
-

Telegram supports reproducible builds, so you can always be sure that the app you have on your device was built from the exact same open source code that is published on GitHub.

-
-

Pinch to zoom

-

Photos and videos can now be expanded directly from the chat – simply pinch to zoom in right away, without tapping to open the media viewer.

-
- -
- -

Improved Video Player

-

When watching a video from the media player on iOS, press and hold the + or - 15s buttons to fast-forward and rewind. On Android press and hold on the right or left side of the screen to do the same, and double-tap to jump 10 seconds in either direction.

-
- -
- -

Tips and New Android Animations

-

The Android app gets smoother and more dynamic with each update – check out the new animations when opening the side menu or swiping back to the chat list from a chat.

-
- -
- -
-

To learn more about what Telegram can do, tap Telegram Features from the side menu or visit the @TelegramTips channel.

-
-

Telegram Jobs

-

That's it for today. We are already working on the next update — and if you just thought 'Wow, that's the spirit!' rather than 'Poor people, have some rest', check out our list of open positions.

-

- -

April 26, 2021
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - - diff --git a/data/telegram.org/blog/payments.html b/data/telegram.org/blog/payments.html deleted file mode 100644 index 61d0a8a1b0..0000000000 --- a/data/telegram.org/blog/payments.html +++ /dev/null @@ -1,253 +0,0 @@ - - - - - Payments for Bots - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Payments for Bots

- -
- -
- -
-

UPD 2021: For up-to-date information about Payments on Telegram, see Payments 2.0 and the Payments Documentation.

-
-
- -
- -

Imagine a world where you can order pizza, pay for a pair of shoes, hire a cab, or refill your subway pass — all in a few button taps on Telegram.

-

To make this world possible, we are launching Bot Payments today. Bot developers can now accept payments from their users around the world, just like that:

-
-
- -
-
-
- -

If you have Telegram 4.0 (or newer) installed, you can order goods or services from bots that offer them. These bots may now add a Pay button to their messages. When you tap Pay, you'll be asked to fill in your credit card and shipping information and confirm the payment. Then you get what you paid for. Voila!

-

If your account is protected by 2-Step Verification, you can save your card for future purchases. If you do that, ordering stuff from bots will only take two taps. Bot Payments also support Apple Pay for a completely frictionless experience.

-

Check It Out Now

-

Try our demo @ShopBot to get a taste of what's coming. (Note: Our demo bot thinks it sells time machines, but they're not a part of what's coming. Sadly.) If you're looking to test a real payment with actual money, stop by our @TelegramDonate bot.

-

Telegram is an open platform, so bot developers can implement the necessary APIs and accept payments from users starting right now, without lengthy approval dramas. If you’re a bot developer, check out the docs immediately!

-

Behind the Scenes

-
- -
- -

At launch, most of the payments were handled by Stripe, but Telegram Bot Payments are a platform for payment providers all over the world. When accepting a payment from a user, the bot developer can choose between all available payment providers, selecting the one already used by the buyer or the one with the lowest commission.

-
-

UPD, 14.06.2017: Bot developers can now process payments from more than 200 countries via the global payment provider Paymentwall.

-

UPD, 02.06.2017: Yandex.Money and Payme are now also available as payment providers.

-

UPD, 01.09.2017: Rave by Flutterwave is now available, which is especially helpful for developers in Nigeria, Kenya, Ghana, South Africa, and Uganda.

-
-

This is just the beginning. In the next few days, payments will become available to developers in India via Razorpay, in Russia Qiwi will be joining the club a little later.

-

Follow our @BotNews channel to be the first to know about new providers joining.

-

If you’re a payment provider (especially in a developing country), click here to learn how to get on board.

-

Just Passing Through

-

Telegram acts as a messenger (pun intended) between the paying user, the bot developer, and their chosen payment system. The user sends their credit card details directly to the payment system. Then the payment system's response and the shipping details entered by the user are passed to the bot developer so that they can process the order.

-

Due to this structure, it is impossible for Telegram to handle complaints or cashbacks – any disputed payments are the responsibility of the bot developers, payment providers, and banks that participated in the exchange.

-

Since Telegram doesn't process the payments, we don't store and can't access any sensitive data. We also don't take any commission from payments and don't profit from these transactions.

-

Instead, we just do what every sheriff has to do with strangers passing through their turf: shoot the bad bots and award the good ones with a badge. We’re sure there’ll be plenty of good ones.

-

If You Are…

- -

And if you're none of the above for some weird reason, be a user, do the right thing. Happy shopping, everyone!

-

- -

May 18, 2017
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/photo-editor-and-passcodes.html b/data/telegram.org/blog/photo-editor-and-passcodes.html deleted file mode 100644 index bc8ca9a721..0000000000 --- a/data/telegram.org/blog/photo-editor-and-passcodes.html +++ /dev/null @@ -1,252 +0,0 @@ - - - - - Photo Editor and Passcode Lock - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Photo Editor and Passcode Lock

- -
- -
- -

Today’s update to our iOS and Android apps reflects the essence of Telegram — a combination of easy-to-use privacy tools and popular mass market features.

-

Photo Editor

-

Each day Telegram users share 35 million photos, and this number is growing by the hour. For comparison, Instagram users shared 70 million photos daily in December. Yet up until now, messaging app users couldn’t enjoy a photo editing experience on the level that is offered by photo-sharing apps. We’re changing this today.

-
-
- -
-
- - -

With the new photo editor, you can crop, rotate and auto-enhance photos before sending them. On top of that, you can use Photoshop-class granular controls for brightness, contrast, warmth, saturation, highlights, sharpening, blurring and more.

-

The auto-enhance tool is our favorite though — it can improve photos in an instant.

-
- - - - -
-
- -

Passcode Lock

-

Telegram is one of the few messaging apps that can be used on multiple devices at once. While this is definitely convenient, it also raises the bar when it comes to privacy. What if one of your Telegram devices, e.g. an iPad or another tablet, is sometimes used by your colleagues or family members?

-

In order to give you more control in such cases, we are introducing passcodes. Starting today, you can lock your iOS or Android device with a passcode – a simple 4-digit PIN or a longer password. The iOS app, and soon the Android app as well, can use passwords to encrypt the local database against such extreme cases as phone theft.

-
- - - - - - - - -

-
- -Without entering this passcode, no one will be able to access your Telegram messages. When Telegram is locked, notifications about new messages will not include texts or sender names, so private data stays hidden from prying eyes. - -
-

- -


-
- -

Since unlocking Telegram each time can get annoying, we implemented both manual and auto-lock. You can lock the app manually from the chats screen or enable auto-lock after a specified period of inactivity. iOS users can use Touch ID to unlock the app.

-

-
- -

February 25, 2015
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/polls-2-0-vmq.html b/data/telegram.org/blog/polls-2-0-vmq.html deleted file mode 100644 index b0e6a10f83..0000000000 --- a/data/telegram.org/blog/polls-2-0-vmq.html +++ /dev/null @@ -1,271 +0,0 @@ - - - - - Polls 2.0: Visible Votes, Multiple Answers, and Quiz Mode - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Polls 2.0: Visible Votes, Multiple Answers, and Quiz Mode

- -
- -
- -
- Introducing Polls 2.0: Visible Votes, Multiple Answers, and Quiz Mode -
- -

Since we first added polls for groups and channels, they've been used for everything from deciding where to have lunch to organizing leaderless protests. Today we're expanding the range of possibilities with three new kinds of Telegram polls.

-
- -
- -

Visible Votes

-

Previously, all polls on Telegram were anonymous. With this update, you can create polls that allow everyone in the group to see who voted for what. Now you will know exactly which friends you disagree with on the matter of pineapple and pizza.

-
- A poll that shows who voted for which option -
- -

Naturally, you can still create anonymous polls to make sure nobody finds out it was you who voted for broccoli instead of cookies.

-

Multiple Answers

-

One of the best ways to settle the score is with polls that allow people to select multiple answers. Scheduling events, or choosing a playlist of songs for a party – sometimes you need more than one choice.

-
- A poll that allows people to select multiple answers -
- -

Our aunt who has a knack for statistics and exploring bizarre correlations kept asking for this feature – and we just couldn't say no. (33% of developers who didn't refuse this request were also found to be addicted to cheese.)

-

Quiz Mode

-

For the game show guru and “Who Wants To Be A Millionaire” contestant in all of us, polls now have Quiz Mode. Such polls have one correct answer and can power anything from trivia games to public service exams.

-
- Quiz mode -
- -

As if guessing right wasn't sweet enough, correct answers will trigger a shower of confetti.

-

Creating Polls

-

Polls can be created in groups or channels (they feel lonely in one-on-one chats). Simply choose the “Poll” option in the attachment menu. Type in your question, add answer options, choose the settings that fit your purpose best – and you're ready to go:

-
- -
- -

Bot API and Quiz Bot

-

All the new poll types are supported in today's update to our Bot API, so bot developers can build on this new functionality.

-

As an example, we've created a Quiz Bot that lets you create multi-question quizzes and share them with others. It also lets you add text or media before questions to help create exam-style prompts with graphs and tables – or better yet, your own Know Your Meme tests.

-

Once your quiz is ready, you can share it to a group or channel – or invite users to answer questions privately, in a chat with the bot. To see how this works, try our demo quiz: Who is Who in the 'Great Minds' sticker pack.

-
- Demo Quiz -
- -

The bot will keep tabs on how many questions users got right and how much time it took them to complete the quiz. It also keeps a global leaderboard for each quiz you create.

-

Message Corners

-

In addition to the new polls, our apps just got a new visual setting. If you find your Telegram messages too hip to be square (or round, depending on your platform), you can tweak the appearance of message bubbles in Settings:

-
- -
- -

Download Progress Counters on Android

-

Just like on iOS, Android users can now see exact progress counters when downloading or uploading files – if they're in the mood to count bits and bytes.

-
- Download progress counters on Android -
- -

And that's it for today. Here's to a good new year full of updates. Stay tuned!

-

- -

January 23, 2020
The Telegram Team

-
- -
- -
- -
-
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/polls.html b/data/telegram.org/blog/polls.html deleted file mode 100644 index 1c007defe0..0000000000 --- a/data/telegram.org/blog/polls.html +++ /dev/null @@ -1,230 +0,0 @@ - - - - - Polls: Bringing Choice to Communities - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Polls: Bringing Choice to Communities

- -
- -
- -
- -
- -

Large communities on Telegram frequently use polls to coordinate their activities and stay in touch with their members. Today, we're rolling out a dedicated tool for polls in addition to existing bots like @vote. We hope the new built-in polls will be a welcome addition to groups with 100,000 members and channels with millions of subscribers.

-
- -
- -

Polls can be forwarded to increase reach and pinned for better visibility (and also to notify all members of the community).

-

At the moment, polls are anonymous, meaning that no one can see who voted for what. Going forward, we may introduce non-anonymous polls where the voters lists will be public, but such polls will be explicitly marked as non-anonymous.

-
-

Telegram has your back when it comes to privacy: we never disclose the private data you entrusted us with to third parties and never monetize it.

-
-
-

Image Search and Other Improvements on iOS

-

Back to more mundane matters, you can use Web Search again to find images when sending Photo & Video attachments or choosing profile pictures in our iOS app. Setting a Grinch avatar for Christmas has never been easier:

-
- -
- -

The Great iOS Bug Hunt goes on and the app received numerous fixes in version 5.1.1.

-

To name a few improvements: Clearing the cache in Settings > Data and Storage > Storage Usage now correctly reduces the space taken by the app. Files and media will keep downloading for a while after you close the app. You will see detailed progress when downloading and uploading files. We've also added online indicators for the ‘People’ section in search results.

-

Happy Winter Solstice!

-

- -

December 22, 2018
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/privacy-discussions-web-bots.html b/data/telegram.org/blog/privacy-discussions-web-bots.html deleted file mode 100644 index 16a6dc3480..0000000000 --- a/data/telegram.org/blog/privacy-discussions-web-bots.html +++ /dev/null @@ -1,284 +0,0 @@ - - - - - Focused Privacy, Discussion Groups, Seamless Web Bots and More - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Focused Privacy, Discussion Groups, Seamless Web Bots and More

- -
- -
- -
- -
- -

Telegram is about privacy. In 2014 we pioneered granular privacy settings in messaging. Today we are making them even more flexible with exceptions for group chats.

-

From now on, you can make something visible for all your classmates in one group chat and keep it private from, say, all your colleagues in another – with just two taps:

-
- -
- -

Settings will adjust automatically as people join and leave the groups. So when your half-brother unexpectedly gets a job as a data broker, you'll just need to kick him out of one group to update all your settings.

-

Who can see my phone number?

-

On Telegram, you can send messages in private chats and groups without making your phone number visible. But there may be cases when you want to make your number known (e.g. to all your coworkers), so we added a new dedicated privacy control – Who Can See My Number.

-
- A screenshot of the redesigned Privacy & Security settings screen -

Redesigned privacy settings on iOS

-
- - -

Meet Seamless Web Bots

-

We've made it easier to integrate bots with web services. Bots can now help you log in with your Telegram account on a website when you open a link. If you allow them to, you'll be logged in by the time the page loads in the browser:

-
- A confirmation dialog that offers to open a link and optionally authorize on the website -
- -

While this is purely optional, it opens the door for a vast variety of new bots. To try out this seamless authorization, press the ‘comments’ button under this post.

-

You can also make our sample @discussbot an admin in any of your broadcast channels to get a comments button under the posts you publish. The comments button opens a website where you are already logged in and ready to leave a comment. The bot will notify you if someone replies to what you wrote there.

-

Anyone can create similar bots to connect their existing services to Telegram on the fly. Integrating all kinds of social, gaming, productivity, dating or e-commerce services into your channels is now a breeze.

-

Broadcasts meet Group Chats

-

Telegram channels are a tool for broadcasting your thoughts to unlimited audiences. Telegram group chats offer a democratic way for communities of up to 200,000 members to discuss things.

-

Ever since we launched channels and groups, users have been asking us to add discussions to channels and announcements to groups. With this update, admins can add a group chat to their channel to serve as a discussion board:

-
- -
- -

Subscribers will see a ‘Discuss’ link on the bottom panel, and each new post from the channel will be automatically forwarded to and pinned in the discussion group.

-
- -
- -

View public channels

-

Speaking of channels, you can now view any public channel from the web – even if you aren‘t logged in to Telegram. The same also goes for those retro people who don’t have a Telegram account at all. Yet.

-
- A public channel, as seen from the web -
- -

Simply open the channel link in a browser and select “Preview channel” to see something like this: t.me/s/telegram

-

Scam Alerts

-

Telegram apps will now show a scam label for suspicious accounts.

-
- Chat with a scammer -
- -

iOS Goodies

-

In other news, Telegram 5.7 for iOS introduces thumbnails for PDF files. Keep in mind that Telegram lets you share files of any type, up to 1,5GB each in size (so you can telegram a PDF payload worthy of Elon's rockets).

-
- PDF file with a thumbnail -
- -

Telegram for iOS also catches up with the rest of our apps in terms of text links. You can now make any text a link to a website, keeping all the cords under the carpet.

-
- Creating a text link on iOS -
- -

Mind that people will get a warning about where exactly the link leads when they open it. (Hint: use URL shorteners if you want to rick-roll people).

-

Android Delights

-

As for Android, we've redesigned the majority of confirmation dialogs in the app, and improved the design for message search and adding people to groups. Additionally, the app got a new theme switcher in Chat Settings.

-
- -
- -

Have fun with all that and stay tuned for our next updates.

-

- -

May 31, 2019
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/privacy-revolution.html b/data/telegram.org/blog/privacy-revolution.html deleted file mode 100644 index f100e74092..0000000000 --- a/data/telegram.org/blog/privacy-revolution.html +++ /dev/null @@ -1,226 +0,0 @@ - - - - - Hiding Last Seen Time - Done Right - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Hiding Last Seen Time - Done Right

- -
- -
- -

Each day our volunteer-driven support team gets several thousand requests from our users to help them hide their Last Seen time. We knew it's important, and have been working hard to get this feature right. We wanted to make sure that Telegram users would have unprecedented precision and flexibility, without the usual tradeoffs.

-

Starting today, you can specify exactly who will see your Last Seen time in both our iOS and Android apps. You can choose between the three basic options (“Everybody”, “My Contacts” and “Nobody”) and add any number of exceptions into the “Always Share With…” and “Never Share With…” sections.

-
-

For example, this way you can make your Last Seen time available to everybody but your boss, or to nobody with the exception of your marriage partner (or vice versa, it's up to you). If you’d like to share your Last seen time only with your contacts plus the members of some work-related group you have, you can do it in just a few taps. This makes countless combinations possible.

-
-

Why Is This Important?

-

To make things fair, you won’t see Last Seen timestamps for people with whom you don‘t share your own. That’s why it‘s important to have granular controls — Telegram’s precision helps you avoid difficult choices. For example, you don't need to choose between hiding your Last Seen from your boss and being able to know when your best friend was online. You can have both.

-
- - -
-
- -

Last Seen Recently

-

Of course, the absence of a Last Seen timestamp makes it difficult to know whether the person you're about to contact is a regular user of Telegram and will be able to read your message. That is why even if the exact Last Seen time is hidden, you will still see an approximate value, like “last seen recently” (i.e. from one minute ago to about 3 days) or “last seen within a month”. This keeps stalkers away, but makes it possible to understand whether a person is reachable over Telegram.

-

Speaking of inactive users, we're not going to have too many of them soon. Starting today, Telegram accounts will self-destruct after 6 months of inactivity by default.

-

Self-Destructing Accounts

-

Big companies like to accumulate data about their users and keep it for an indefinite time. Telegram is not a commercial organization and we value our disk space greatly. Last year we introduced self-destructing messages, today we are adding self-destructing accounts.

-

From now on, if you stop using Telegram and do not login for at least 6 months, your account will be deleted along with all messages, media, contacts and every other piece of data you store in the Telegram cloud. You can change the exact period after which your inactive account will self-destruct – with options ranging from 1 month to 1 year.

-


- -

These new features are already available in our iOS and Android apps. Stay tuned for more privacy-related updates.

-
- -

The Telegram Team,
November 19, 2014

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/reactions-spoilers-translations.html b/data/telegram.org/blog/reactions-spoilers-translations.html deleted file mode 100644 index 7d17033f44..0000000000 --- a/data/telegram.org/blog/reactions-spoilers-translations.html +++ /dev/null @@ -1,300 +0,0 @@ - - - - - Reactions, Spoilers, Translation and QR Codes - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Reactions, Spoilers, Translation and QR Codes

- -
-
-
- -
- Reactions, Spoilers, Translation and QR Codes -
- - -

Telegram's 12th update of the year introduces reactions, message translation, themed QR codes, hidden text (spoilers), and more.

-

Reactions

-

Telegram was the first messaging app to add animated and interactive emoji, giving users unparalleled ways to express themselves in chats. Today some of these emoji become available as reactions to share feelings and feedback – without sending any messages.

-
- -
- -

Double tap a message to send a quick 👍 reaction. For more reactions like 😁 🎉 😱 🔥 👎, tap once on the message (or press and hold, if on iOS). Each reaction appears with its own unique animation.

-
-

You can change your default reaction to another emoji in Settings. Android: Chat Settings > Quick Reaction. iOS: Stickers and Emoji > Quick Reaction.

-
-

Reactions are always on in private chats. In groups and channels, the admins decide whether to turn on reactions and choose which reaction emoji are available in the chat. This enables many different ways to collect feedback – from simple likes ❤️ to upvote 👍 and downvote 👎 systems, and beyond.

- - -
-

Admins can control reactions via their group or channel's Info Page > Edit > Reactions. For more feedback options, try channel comments and our powerful polls.

-
-

Spoilers

-

To discuss the fates of Ciri or Peter Parker without spoiling the fun for others, select any part of your text when typing and choose the new 'Spoiler' formatting. This will hide the selected part of the message in the chat, as well as in the chat list and notifications.

-
- -
- -

When you're ready to see what's hidden, tap the spoiler to reveal its text.

-

Message Translation

-

Over half a billion people around the world use Telegram not only to stay in touch with friends, but also to chat in public groups and view content from channels – in every language imaginable. Now you can translate any message into another language, right in the app.

- - -
- -
- -

Enabling Translation in Settings > Language adds a dedicated Translate button to the context menu when selecting a message. You can also exclude any languages you speak fluently – which will hide the translate button for those messages.

-
-

Translation is available on all Android devices that support Telegram, but requires iOS 15+ on Apple devices. The list of available languages depends on your phone's operating system.

-
-

Themed QR Codes

-

You can generate QR codes for any users that have a public username. This also works for groups, channels and bots, making it easy to show someone your favorite blog or fan club.

-
- -
- -

Tap the new QR code icon next to the username of a person (or from a chat’s info page), choose the colors and pattern that fit best, then print, post or share your QR code to other apps.

-
-

A QR code for your own username can be obtained in Settings.

-
-

New Menus for macOS

-

We've redesigned all the context menus in Telegram for macOS – adding some new shortcut hints and introducing beautifully animated icons for every single menu item in the app.

-
- -
- -

More Interactive Emoji

-

Our animators also added new interactive versions of 🔥 😁 🤩 😢 😭 😱 ❄️. Send any of them in 1-on-1 chats, then tap to unleash a full-screen effect for you and your partner.

-
- -
- -

Thank you all for an incredible year. Here's to making 2022 even greater. 🎉

-

- -

December 30, 2021
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - - diff --git a/data/telegram.org/blog/replies-mentions-stickers.html b/data/telegram.org/blog/replies-mentions-stickers.html deleted file mode 100644 index af38987e40..0000000000 --- a/data/telegram.org/blog/replies-mentions-stickers.html +++ /dev/null @@ -1,257 +0,0 @@ - - - - - Better Replies, Stickers & Invitations - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Better Replies, Stickers & Invitations

- -
- -
- -
- -
- - -

Since 2015 when we first introduced replies, the maximum group size on Telegram has increased by 100 times – from 200 max members to 20,000. These days you can get new mentions or replies in group chats many times during a day – and it’s important not to miss those messages.

-

Starting with Telegram 4.3, whenever somebody replies to you or mentions you in a group, you’ll notice this straight away by the ‘@’ badge in the chats list:

-
-
- -
-
- - -

If you have new replies/mentions in a group, you can now instantly reach them by tapping the new ‘@’ button when inside the chat. This button will disappear once you’ve read all the relevant messages.

-

Favorite Stickers

-

Anyone can create and upload stickers on Telegram. As a result, thousands of new stickers are added to the platform each day, and some of us have dozens of sticker sets installed.

-

Starting today, anyone with five or more sticker sets installed can mark individual stickers as ‘favorites’, and have them always accessible at the top of the sticker panel in the ‘star’ section.

-
-
- -
-
- -

Stickers of the Group

-

Speaking of stickers, large groups with 100 members and more can now choose an official sticker set for all the members of the group to see and use while they're chatting in the group — without the need of adding it to their panels.

-
- -

Group Stickers

-
- -

Invite Friends

-

The ‘Invite Friends’ section (accessible from Contacts) has been completely redesigned. Your contacts that are not on Telegram yet but have many of their friends already using it are now listed at the top. If you invite any of them to join, they’ll be welcomed by tens of Telegram veterans among their contacts:

-
- -

Invite Friends to Telegram

-
- -

…And More

-

As always with new releases, we've included several small goodies you may also like:

-
    -
  • Twitch videos are now supported in the Telegram in-app player, so you can watch Twitch streams in Picture-in-Picture mode while chatting with your friends.
  • -
  • When on a Telegram voice call, you can now check the signal strength thanks to the new indicator.
  • -
  • On iOS, you can edit any photo you pasted directly to a chat from clipboard before sending.
  • -
  • On Android, when forwarding a message, you can long tap to select multiple recipients.
  • -
  • On Android, when viewing photos in Shared Media, you can go to the place in chat where the photo was posted.
  • -
  • On Android, if you have many new messages in many active chats, synchronization will happen much, much faster.
  • -
-

- -

Summer is over. Stay tuned, another update is already brewing in our dungeons!

-

September 3, 2017
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/scheduled-reminders-themes.html b/data/telegram.org/blog/scheduled-reminders-themes.html deleted file mode 100644 index 6d9f505a90..0000000000 --- a/data/telegram.org/blog/scheduled-reminders-themes.html +++ /dev/null @@ -1,264 +0,0 @@ - - - - - Scheduled Messages, Reminders, Custom Cloud Themes and More Privacy - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Scheduled Messages, Reminders, Custom Cloud Themes and More Privacy

- -
- -
- -
- Introducing Scheduled Messages, Reminders, Custom Cloud Themes and More Privacy -
- -

In our previous update, we added a handy menu when you hold the send button. Today we're populating this menu with a new option that helps you plan ahead.

-

Hold the ‘Send’ button in any chat and select ‘Schedule Message’ to automatically send things at a specified time in the future (DeLorean not included).

-
- -
- -

Scheduling also works in your ‘Saved Messages’ chat, turning your planned posts into reminders. Be your own time-travelling secretary – whether it's about a dentist appointment next week, or waking up in time for pizza delivery.

-
- -
- -

Whenever a scheduled message or reminder is sent, you get a special notification marked with a 📅, so you don't get caught off-guard by messages you planned in the past.

-

Custom Cloud Themes

-

You could first customize Telegram's appearance way back in 2017. Today's update makes this easier than ever across all platforms, including our native desktop apps.

-

Choose a pre-set accent color or pick something unique from the color wheel, and the app will adjust all elements accordingly. See how it looks in your favorite color, blue – no, yellow!

-
- -
- -

You can now easily create new themes based on your color and wallpaper choices, then fine-tune them manually or share right away. Each theme has a sharing link which allows anyone to switch to your theme and wallpaper in just two taps.

-
- Creating a new theme on iOS -
- -

When you change your theme, it gets updated for all its users. This way you can update your app's looks to evolve as Telegram updates – or to change with the seasons.

-

To try out cloud themes, take a look at Sky Blue or Desert. These will work for both iOS and Android, and we solemnly swear to update them to acid green on orange when you least expect it.

-

Redesigned Message Options

-

On iOS, we have condensed message options into a single menu for forwarding, replying and more. You can now also select any portion of the message to copy or share, instead of only the full text.

-
- -
- - -

New Privacy Settings

-

Telegram groups can be public and may hold up to 200,000 members each. When launching them, we were thinking of campuses, conventions and spaces where you could properly brag about your cats. However, Telegram communities are also increasingly used by people to organize themselves in the face of oppression.

-

We believe that all people have a right to express their opinions and communicate privately. To further protect these rights, we‘re expanding Telegram’s arsenal of Privacy Settings today.

-

If you set Who Can See My Phone Number to ‘Nobody’, a new option will appear below, allowing you to control your visibility for those who already have it. Setting Who Can Find Me By My Number to ‘My Contacts’ will ensure that random users who add your number as a contact are unable to match your profile to that number.

-

If, like the majority of our users, you rely on uploading phone contacts to identify friends and family members on the app, this setting won't get in your way.

-

More Animated Emoji

-

Regardless of whether you‘re fighting for freedom or queuing for coffee, you’ll likely find a use for the new additions to our animated emoji family.

-

As before, send a single 😁, 😧, 😡, 💩, 😢 or 😮 to unleash their spirit in motion.

-
- -
- -

And that's all, folks! While waiting for our next update, check out this brief history of Telegram. Or, if you're not into reading, run a bath and enjoy these animated rubber duck stickers.

-

- -

September 5, 2019
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/shared-links.html b/data/telegram.org/blog/shared-links.html deleted file mode 100644 index f7034c0274..0000000000 --- a/data/telegram.org/blog/shared-links.html +++ /dev/null @@ -1,221 +0,0 @@ - - - - - Shared Links and Recent Searches - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Shared Links and Recent Searches

- -
- -
- -

Have you ever tried to find a link somebody shared in a busy chat? It’s not always easy. Of course, you could use message search, but now it's even easier – simply go to the new Shared Links section in Shared Media. Voila!

-
- - -

-
- -

You will see the text of the message that accompanied the link, or the rich preview data in case the link was sent by itself. This feature is currently available for iOS and Android, but will make its way to our other apps soon.

-

Recent Search Results

-

By the way, as of the previous update on both iOS and Android, tapping the universal search field now gives you quick access to recent search results.

-
- - -

-
- -

We‘re ramping up for massive updates this Fall. Stay tuned!

-

- -

The Telegram Team,
August 20, 2015

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/silent-messages-slow-mode.html b/data/telegram.org/blog/silent-messages-slow-mode.html deleted file mode 100644 index 9c474f5cd9..0000000000 --- a/data/telegram.org/blog/silent-messages-slow-mode.html +++ /dev/null @@ -1,296 +0,0 @@ - - - - - Silent Messages, Slow Mode, Admin Titles and More - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Silent Messages, Slow Mode, Admin Titles and More

- -
- -
- -
- 5.10 update cover -
- -

The previous update brought more movement to Telegram – this one brings more peace of mind. You can now message friends freely when you know they are sleeping, studying or attending a meeting.

-

Simply hold the Send button to have any message or media delivered without sound.

-
- -
- -

Your recipient will get a notification as usual, but their phone won't make a sound – even if they forgot to enable the Do Not Disturb mode.

-
- Silent notification on the lock screen -
- -

This also works in groups, should you get an urgent idea at five in the morning – but not urgent enough to wake up everyone in your work chat.

-

Slow Mode

-

In case a group you manage is getting hard to follow, the Group Permissions section now features a Slow Mode switch.

-
- Slow Mode settings in the Group Permissions section -
- -

When an admin enables Slow Mode in a group, you will only be able to send one message per the interval they choose. A timer will show how long you have to wait before sending your next message.

-
- Slow Mode timer as seen in a user's input field -
- -

Slow Mode can make conversations in the group more orderly, while raising the value of each individual message. Keep it on permanently, or toggle as necessary to throttle rush hour traffic.

-

Admin Titles

-

If new time-lord powers aren't enough, group owners can now set custom titles for admins like ‘Meme Queen’, ‘Spam Hammer’ or ‘El Duderino’.

-
- Custom title section on the admin rights screen -
- -

As with the default admin labels, custom titles are shown with every message in the group so members know that they‘re talking to the designated ’Myth Buster'.

-
- A message from an admin with a custom title in a group -
- -

To add a custom title, edit the admin's rights in Group Settings.

-

Timestamps and Improved Scrubbing

-

Videos now display thumbnail previews as you scrub through, to help you find the moment you were looking for.

-

If you add a timestamp like 0:45 to a video caption, it will be automatically highlighted as a link. Tapping on a timestamp will play the video from the right spot. This also works if you mention a timestamp when replying to a video.

-
- -
- -

Timestamps are also supported for YouTube videos, in case you want to mark your favorite moments when sharing a Kurzgesagt episode.

-

Animated Emoji

-

When you have animated stickers, why not go one step further and get animated emoji? To check them out, send a single ❤️, 👍, 😒, 😳 or 🥳 to any chat.

-
- -
- -

If your life feels a little too animated recently, Sticker Settings now offer a toggle for looped playback. When disabled, animated stickers will play just once then stay still.

-

Android's New Attachment Menu

-

Android’s attachment menu got a makeover, giving media more real estate. Larger thumbnails make it easier to pick photos and videos at a glance, and swiping up will reveal your full Gallery for better browsing.

-
- -
- -

You can scroll left and right through the other attachment options like locations, polls and music. When selecting media, tap ‘…’ to send items as uncompressed documents.

-
- A screenshot of the options from the '...' menu -
- -

Accent Colors for Night Mode on iOS

-

iOS users can now choose accent colors for night themes. The night doesn't always have to be black and blue, after all.

-
- -
- -

Comments Widget

-

Comments.App, our tool for commenting on channel posts, now lets you add a comments widget to your website.

-

With the widget in place, Telegram users will be able to log in with just two taps and leave comments with text and photos, as well as like, dislike and reply to comments from others.

-

They can also subscribe to comments and get notifications from @DiscussBot.

-
- A screenshot of the Comments Widget featuring a photo sent as a reply to another comment -
- -

Open this page in your browser to try the new widget – it doesn't support Instant View pages… yet. 😈

-

That’s all for now, and don’t worry — the next Telegram update won’t be sent silently.

-

- -

August 9, 2019
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/stickers-meet-art-and-history.html b/data/telegram.org/blog/stickers-meet-art-and-history.html deleted file mode 100644 index bda6891a72..0000000000 --- a/data/telegram.org/blog/stickers-meet-art-and-history.html +++ /dev/null @@ -1,338 +0,0 @@ - - - - - When Stickers Meet Art And History - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

When Stickers Meet Art And History

- -
- -
- -

Today Telegram launched a new kind of stickers – a free emotion-based platform for artists. We mentioned several technological and architectural points that make Telegram stickers a completely new experience – open, free and limitless. But there’s another way in which they are unique, and it also has a lot to do with our values.

-

When designing our first set of stickers, we didn’t want to use just any cartoon characters to express emotions. Instead we decided to portray people we respect most. These are great artists, poets, actors, scientists and leaders.

-

We'd like to give them credit for their contributions to human civilization, and we hope that millions of Telegram users share our respect for these outstanding individuals.
Don't forget to check out Part 2: MOAR stickers!

-
-
- -
-
Abraham Lincoln approves
-
- -
-
- -
- - -
-
Salvador Dali unlocks achievement
-
- -
-
- -
- - -
-
Albert Einstein explains
-
- -
-
- -
- - -
-
Mahatma Gandhi likes where this is going
-
- -
-
- -
- - -
-
Charlie Chaplin had a bad day
-
- -
-
- -
- - -
-
Steve Jobs laughs out loud
-
- -
-
- -
- - -
-
Kafka is not happy. He never is...
-
- -
-
- -
- - -
-
John Lennon, but...
-
- -
-
- -
- - -
-
Richard Wagner's told you
-
- -
-
- -
- - -
-
Nikola Tesla is unimpressed
-
- -
-
- -
- - -
-
One doesn't simply send a Tolkien sticker
-
- -
-
- -
- - -
-
Mark Twain, huh?
-
- -
-
- -
- -
-
That Freudian scowl...
-
- -
-
- -
- - -
-
And the famous Monroe kiss
-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/stickers-revolution.html b/data/telegram.org/blog/stickers-revolution.html deleted file mode 100644 index e60ea9afc4..0000000000 --- a/data/telegram.org/blog/stickers-revolution.html +++ /dev/null @@ -1,231 +0,0 @@ - - - - - Custom Sticker Sets - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Custom Sticker Sets

- -
- -
- -
-

Check out Pavel's Channel for some cool sticker sets »

-
-

Starting today, artists can submit their custom sticker sets via the Telegram @stickers bot. Each sticker set gets a permanent link, so that users can easily add new stickers and share them with friends.

-

This enables artists of the world to unleash their creativity and help Telegram users customize their experience. Our in-house artist (responsible for the graphic art in this blog) created the Animals set as an example. If you have Telegram installed and updated, this link will open the set: https://telegram.me/addstickers/Animals.

-
- -

-
- -

Independent designers already began submitting their sticker sets, and we notice stickers like Flags of the World or Vicky uploaded to the @stickers bot.

-

Sharing Stickers

-

Sending a link isn‘t the only way to share a sticker set. When you receive a sticker from a set you do not currently have installed, simply tap on it and choose ’Add to Stickers‘ (’Info' on iOS) to preview and add the whole set.

-
- - -

-
- -

Once you've added a set, its stickers become available via emoji tooltips or the dedicated sticker panel. The iOS app now has one too — you can manually switch it on/off in Chat Settings — Stickers.

-

The new Stickers menu allows you to view, uninstall and share your sticker sets.

-
- -

-
- -

This update is available for Android and iOS and is coming to other apps soon. Sticker sets on Telegram are now fully equipped to spread virally and devour the world.

-

- -

The Telegram Team,
May 19, 2015

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/supergroups.html b/data/telegram.org/blog/supergroups.html deleted file mode 100644 index 97a041bc98..0000000000 --- a/data/telegram.org/blog/supergroups.html +++ /dev/null @@ -1,251 +0,0 @@ - - - - - Admins, Supergroups and More - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Admins, Supergroups and More

- -
- -
- -

Telegram groups are democratic by design. Everyone can invite new members and change the group‘s name and photo, which is ideal for small bands of friends or coworkers. But Telegram can also support much larger communities that need more administration. To make life easier in big groups, we’re introducing admins today.

-

From now on, you can choose how your groups will operate. By default, all members are still in control. But if you want more order, you can throw the switch and appoint additional administrators to your group.

-
- -

-
- -

If you enable the new restricted mode, only administrators will be able to add new people and change the name and photo of the group. Admins also have the power to remove other members from the group.

-

Supergroups

-
-

UPD: Check out Supergroups 2.0: Pinned posts, Public groups, new moderation tools!

-
-

Telegram groups have always been several steps ahead of the competition. You could have groups of up to 200 people communicating efficiently using replies, mentions and hashtags. Now it's time to go further.

-

Ever since our launch in 2013, our users have been telling us they would like to migrate even larger communities to Telegram. As of today, once your group is full, you can upgrade it to a supergroup that supports up to 5000 members.

-
- -

-
- -

Supergroups are optimized to host large online communities and will load quickly, even if you‘ve missed many messages while away. Here’s what you need to know about how they work:

-
    -
  • New members can see the entire message history when they join.
  • -
  • Deleted messages will disappear for all members.
  • -
  • Ordinary members can only delete their own messages.
  • -
  • Supergroups are muted by default and send fewer joined/left notifications.
  • -
-

All official Telegram clients are getting this update today.

-
-

Please note that you need the latest version of Telegram to access a supergroup. You may want to wait a little bit before upgrading your groups so that the update rolls out to all Telegram users, and they can see their groups.

-
-

iOS Bonus: Best In-App Notifications Ever

-

iOS users will enjoy our new in-app notifications. Pull down on a notification to expand it, view the full text of the message or preview attached media.

-
- -

-
- -

You can immediately send a quick reply or a sticker — all without leaving that particular spot in some other conversation.

-

Android Bonus: Quick Share for Channels

-

Meanwhile, Android users can enjoy the new quick sharing menu in channels. Just tap on the forwarding buttons right next to channel messages.

-
- -
-
- -
-

We have a few more surprises up our sleeve for this year. Stay tuned for more updates!

-

- -

The Telegram Team,
November 25, 2015

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/telegram-me-change-number-and-pfs.html b/data/telegram.org/blog/telegram-me-change-number-and-pfs.html deleted file mode 100644 index a1e2f9bdc0..0000000000 --- a/data/telegram.org/blog/telegram-me-change-number-and-pfs.html +++ /dev/null @@ -1,228 +0,0 @@ - - - - - Telegram.me, Changing Numbers and PFS - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Telegram.me, Changing Numbers and PFS

- -
- -
- -
-

Our iOS and Android apps got updated with three new features today.

-
-

Opening a telegram.me/YourUsernameHere link on your phone will now automatically fire up your Telegram app and open a chat with that user. You can share username links with friends, write them on business cards or put them up on your website.

-
- -
- -
Here's what people will see if they don't have Telegram yet
- -

Changing Your Phone Number

-

It is easy to switch to Telegram and retain your social graph, since it is based on phone numbers. But what if you need to change the phone number itself? As of today, you can change your number in Telegram — and keep everything, including all your contacts, messages and media from the Telegram cloud, as well as all your secret chats.

-
- - - -
-
- -

Your mutual contacts (people in your contacts, who also have your number) will get your new number added to your contact in their address book unless you have blocked them in Telegram. This makes changing numbers even easier.

-

Perfect Forward Secrecy

-

Last but not least, Telegram's Secret Chats now support Perfect Forward Secrecy. What this means is that your Secret Chats will now automatically change encryption keys after a period of time, in order to keep past communications safe. This way you no longer need to manually re-create Secret Chats to achieve this level of security.

-

- -

And that's it for today. Stay tuned for more updates coming your way on all platforms!

-
-

December 1, 2014
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/translations-iv2.html b/data/telegram.org/blog/translations-iv2.html deleted file mode 100644 index d61a63107a..0000000000 --- a/data/telegram.org/blog/translations-iv2.html +++ /dev/null @@ -1,276 +0,0 @@ - - - - - Custom Languages, Instant View 2.0 and More - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Custom Languages, Instant View 2.0 and More

- -
- -
- -
-Introducing custom languages, IV 2.0, a new design for Android and more -
- - - -

Telegram's Translations Platform allows you to suggest better wording for Telegram interfaces in any language. We've recently rolled out support for most mainstream languages, and translations are already underway.

-

Today's update brings equal treatment to the smaller linguistic communities around the world. Anyone can now use the translation platform to create their own custom language packs – and translate Telegram into any minority language or local dialect, be that Māori, Scottish Gaelic or Transliterated Klingon.

-

We've made it easy to spread your translations. To translate the interface of your app, simply follow the dedicated sharing link of the desired language. Sharing links can be obtained in the translation panel.

-
- Applying a custom language -
- -

Each language also gets its own public group for discussions. Here are the links for the Catalan language, for example:

- -

Once a user switches to your translation, all changes you apply in the interface will be applied immediately. The days of waiting for the apps to update or passing around localization files are over.

-

Instant View 2.0

-

Another unique feature of Telegram is the Instant View technology that allows Telegram users to view web pages in a consistent way, with zero loading time.

-

Today we're expanding the platform with support for right-to-left languages, blocks of related articles, image links, tables, nested lists, horizontal scrolling, collapsible text blocks and much more.

-

Now you can get beautiful instant view pages for even very complex articles. If you're reading this from one of our newly updated mobile apps, try this Wikipedia page for an example.

-
- -
- - - -

Soon we will announce a new crowdsourcing contest to make Instant View pages available for an even larger part of the internet.

-

The Great iOS Bug Hunt

-

We've made close to a thousand fixes and improvements to the iOS app since the major release of version 5.0. The new Telegram for iOS 5.1 features some 400 minor improvements.

-

New Design for Android

-

Telegram for Android has now reached version 5.0 and received a major overhaul in the design department. It is now much easier to access shared media from the profiles of users, groups and channels:

- - -
- -
- -

Shared media now offers high quality crisp previews, increased loading speed, more info in the links and files sections, and more efficient design.

-
- Shared Files -
- -

The Settings screens were redesigned for a more streamlined experience:

-
- -
- -

Following in the footsteps of the iOS app, Android users can take advantage of the new detailed settings for the badge counter in Settings > Notification and Sounds:

-
- Badge Counter Settings -
- -

We've upgraded the photo selector for profile pictures so that you can choose the correct head to be displayed on your profile:

-
- Choose an area to use for the photo -
- -

Last but not least, you can zoom videos during playback and browse full-resolution images sent as documents just like normal photos, by swiping left and right.

-

- -

December 10, 2018
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/video-1000.html b/data/telegram.org/blog/video-1000.html deleted file mode 100644 index 849a17bd81..0000000000 --- a/data/telegram.org/blog/video-1000.html +++ /dev/null @@ -1,354 +0,0 @@ - - - - - Video Calls with up to 1000 Viewers, Video Messages 2.0, Video Playback Speed and More - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Video Calls with up to 1000 Viewers, Video Messages 2.0, Video Playback Speed and More

- -
- -
-
- -
- Video Calls with up to 1000 Viewers, Video Messages 2.0, Video Playback Speed and More -
- -

This update takes video to the next level. Group video calls now have up to 1000 viewers, video messages record in higher quality and can be expanded, regular videos may be watched at 0.5 or 2x speed. We've also added screen sharing with sound to all video calls, including 1-on-1 calls — and much more.

-

Group Video Calls 2.0

-

Group video calls allow up to 30 users broadcast video from both their camera and screen – and now 1000 people can watch anything from online lectures to live rap battles.

-

We will keep increasing this limit until all humans on Earth can join one group call and watch us yodel in celebration (coming soon).

-
- -
- -
-

To start a Group Video Call, create a Voice Chat from the info page (in the ⋮ menu on Android) of any group where you are an admin – then turn your video on.

-
-

Video Messages 2.0

-

Video messages are a quick way to check in or share your surroundings without adding another video to your gallery. They now have higher resolution and you can tap on a video message to expand it and take in all those extra pixels.

-
- -
- -

Tapping on an expanded video message pauses it and gives you the opportunity to fast forward or rewind the message in case you missed a word.

-
-

To record a video message, tap the microphone icon in the message bar to switch from voice message recording to video. Press and hold to record, then tap the camera icon to switch back.

-
-

Audio from your device will keep playing as you record so you can now sing along to your favorite songs or reply without pausing your podcast. Additionally, recording with your rear camera lets you pinch to zoom in and capture things at a distance or add a dramatic effect (eerie music not included).

-

Video Playback Speed

-

To power through lecture videos and replay kung fu moves in slow motion, the media player now supports 0.5x, 1.5x and 2x playback speeds. Our Android developer is a fan of hummingbirds, so his app also supports 0.2x speed.

-
- -
- -
-

To change your video playback speed, tap ⋮ on Android or ⋯ on iOS when watching a video in fullscreen.

-
-

On Android, you can also press and hold the 2X button when playing voice or video messages to switch between 0.5x, 1x, 1.5x and 2x playback speed.

-

Timestamp Links

-

Since 2019, putting a timestamp like 0:30 in the captions or replies to videos and YouTube links lets users jump to that exact second – and you can now press and hold on a timestamp in a message to copy the link and share the moment in another chat.

-

Screen Sharing With Sound

-

Screen sharing has been added to 1-on-1 calls as well, and now includes the sound from your device when broadcasting in any video call. So make sure you quit Super Mario before its your turn to present — or don't, and use the game for sound effects.

-
- -
- -

When switching on video during any call, you can swipe to choose a camera or share your screen instead — and use the video preview to make sure that everything is perfect before going live.

- - -
-

To share your screen during a video call, tap the camera button and select your screen as the video source.

-
-

Auto-Delete After 1 Month

-

Messages in any chat can be set to erase themselves after 1 day or 1 week – and now 1 month, in case you need your chats to stick around for a full lunar cycle before disappearing.

-
- Auto-Delete After 1 Month -
- - - -
-

To enable the timer on Android, tap ⋮ > Clear History then choose a duration. On iOS, press and hold a message, tap Select > Clear Chat (top-left) > Enable Auto-Delete.

-
-

Precision Drawing

-

The media editor allows you to illustrate and decorate your photos and videos with drawings, text and stickers. To more easily add fine details (or that perfect mustache and pointy ears), the width of your brush now decreases as you zoom in – giving you the precision of a professional.

-
- -
- -
-

To change the width of your brush at any time, drag the dot up from the color selector.

-
-

The Telegram Desktop app now has its own photo editor to crop, rotate or flip images – and add drawings or stickers. Unique to desktop, your edited versions can be sent as uncompressed files by unchecking the Compress Images box.

-

Passcode Animations

-

New animations make the passcode lock interfaces even snappier than before. If you're using an animated background, it will also appear on the passcode lock screen. The disco never stops.

-
- -
- -

Password Recovery and Reminders

-

We've added a new prompt in Settings to help you practice entering your Two-Step Verification password.

-
- Practice Your 2-Step Verification Password -
- -

If you forgot your password, there is a new password reset option that works even if you don’t have a recovery email — as long as you're still logged into your account. The process will take 7 days and can be cancelled from any of your devices.

-

Message Sending Animations on Android

-

Like emoji and stickers, text messages have new lightweight animations – when you hit Send, your text smoothly transforms into the message bubble as it flies into the chat. iOS users received these energy-efficient animations in the previous update.

-
- -
- -

New In-App Camera on iOS

-

The in-app camera now utilizes all zoom levels on your device – including 0.5x and 2x if available. You can also press and hold to open a zoom wheel that lets you zoom in and out with granular control.

-
- -
- -
-

To use the in-app camera, tap the 📎 icon in the message bar and then tap the camera feed in the attachment menu.

-
-

More for iOS

-

Choose multiple recipients for forwarded messages by tapping 'Select' in the forwarding menu to share your best memes with all your best friends.

-
- Forwarding to multiple recipients -
- -

Scrolling with two fingers in the chat list quickly selects several chats for bulk actions like archive, delete or mark all as read.

- - - - -

Profile pictures now follow the messages as you scroll in group chats so you always know who sent each one, even in long chains of one. word. after. another.

-
- -
- -

New Animated Emoji

-

No Telegram update is complete without new animated emoji. As always, simply send a message with a single emoji to get one of these in a chat:

-
- -
- - -

And that's all for today's update – we're working on the next one at 2X speed.

-

- -

July 30, 2021
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - - diff --git a/data/telegram.org/blog/video-calls.html b/data/telegram.org/blog/video-calls.html deleted file mode 100644 index 95c93e6e3f..0000000000 --- a/data/telegram.org/blog/video-calls.html +++ /dev/null @@ -1,234 +0,0 @@ - - - - - Video Calls and Seven Years of Telegram - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Video Calls and Seven Years of Telegram

- -
-
-
- -
- Video Calls and Seven Years of Telegram -
- -

Today marks seven years of Telegram. In 2013, we began as a small app focused on secure messaging and have since grown into a platform with over 400M users. Telegram is now one of the top 10 most-downloaded apps and is used all over the world to stay in touch with family, collaborate with classmates and coordinate coworkers.

-

We did not reach this milestone on our own – Telegram has never advertised and every user has come to the app because of a recommendation from someone they trust. Strong principles and quality features speak for themselves, and millions of you listened. We've heard you as well, and will continue to develop features that make Telegram much more than just a messaging app. Today we're adding the one you've been asking for – fast and secure video calls.

-

Video Calls

-

2020 highlighted the need for face-to-face communication, and our alpha version of video calls is now available on both Android and iOS. You can start a video call from your contact's profile page, and switch video on or off at any time during voice calls. Like all other video content on Telegram, video calls support picture-in-picture mode, allowing you to scroll through chats and multitask while maintaining eye contact.

-
- -
- -

All video calls are protected with end-to-end encryption. To confirm your connection, compare the four emoji shown on-screen for you and your chat partner – if they match, your call is 100% secured by time-tested encryption also used in Telegram's Secret Chats and Voice Calls. You can find more details on this page.

-
-

Our apps for Android and iOS have reproducible builds, so anyone can verify encryption and confirm that their app uses the exact same open source code that we publish with each update.

-
-

Video calls will receive more features and improvements in future versions, as we work toward launching group video calls in the coming months. But for this midyear milestone, you can now enjoy a little one-on-one time with those closest to you, whether they're in the other room or on another continent.

-

More animated emoji

-

To help you celebrate, we've added another batch of new animated emoji. To get one of these 👇 in a chat, simply send a message with a single emoji.

-
- -
- -

Stay tuned for more updates!

-

- -

August 14, 2020,
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - - diff --git a/data/telegram.org/blog/video-editor-gifs.html b/data/telegram.org/blog/video-editor-gifs.html deleted file mode 100644 index 4b9f3ebdbb..0000000000 --- a/data/telegram.org/blog/video-editor-gifs.html +++ /dev/null @@ -1,252 +0,0 @@ - - - - - Video Editor, Animated Photos, Better GIFs and More - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Video Editor, Animated Photos, Better GIFs and More

- -
- -
- -
- Introducing an New Media Editor, Better GIFs, and More -
- -

In 2015, Telegram released the most powerful photo editor to be implemented in a messaging app, letting you enhance image quality and add drawings, stickers and text to pictures. Today we're upgrading the media editor with support for animated stickers and editing videos.

-
- -
- -

You can now enhance video quality automatically in two taps – or manually tweak a dozen parameters, like brightness or saturation, until your inner Kubrick is satisfied.

-

For perfect paintbrush precision, zoom in on photos or videos when drawing on them to get every line just right. Your made-up makeup – or your classmates' handlebar moustaches – will never look the same.

-

Animated Stickers on Media

-

Most importantly, you can now add animated stickers to any photo or video – just in case you were looking for ways to decorate your dinner table with twerking cherries. Putting an animated sticker on a photo turns it into a GIF:

-
- -
- - -

Speaking of GIFs

-

The GIF panel has been upgraded with a new Trending section and emoji-based tabs that cover the most popular emotions. You won't ever need to wrestle with words again when looking for Robert Downey Jr. 🙄

-
- -
- -

We've also improved loading times for GIFs in the panel, so you can find that perfect GIF faster. Hold on any GIF you haven't sent before to save it to your Recent tab for later use.

-

Flexible Folders

-

If you have many chats and use folders, hold on any chat in the list to add it to one of your folders. This also works for removing chats from folders. Last call for spring cleaning!

-
- Chat options menu with 'Add to Folder' highlighted. -
- -

Android Goodies

-

Android users get a few extra features to make their app slicker. Messages now get sent, edited and deleted with new smooth animations. We've also improved the video player to make sure that controls and long captions get out of your way quickly. Videos shorter than 30 seconds get looped automatically and voice messages play with even more wavy animations.

-
- -
- -

Cache management interfaces on Android got a facelift as well. Not only can you keep Telegram's storage footprint on your device incredibly small – you can do it in style. See Settings > Data and Storage > Storage Usage.

-

Last but not least, monkeys. You know that protecting your account with a Two-Step Verification password is a good idea, but we thought we'd sleep easier at night if we knew that a monkey was overseeing the process. No, this is totally not a coded message, go see for yourself.

-

And that's it for today. Enjoy making post-ironic memes with the new tools while we go back to the dungeons and continue working on you-know-what (and not only that).

-

- -

June 4, 2020
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/video-messages-and-telescope.html b/data/telegram.org/blog/video-messages-and-telescope.html deleted file mode 100644 index 075c2b6960..0000000000 --- a/data/telegram.org/blog/video-messages-and-telescope.html +++ /dev/null @@ -1,247 +0,0 @@ - - - - - Video Messages and Telescope - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Video Messages and Telescope

- -
- -
- -
- -
- -

We know you love the speed and simplicity of voice messages on Telegram. Starting today, you can also send video messages – just as swiftly:

-
-
- -
-
-
- -

To send a video message, go to any chat on Telegram and tap the mic icon to switch to camera mode. Now all you need to do is tap and hold the camera icon and record a video message. When you’re done, just release the recording button to dispatch your message — and it will arrive in the blink of an eye.

-

Video messages are so fast because Telegram compresses them and sends them even as you record them. By the way, if holding the button seems like too much work, you can lock the camera in recording mode by swiping up. This also works with voice messages now (here's one for you, cab drivers).

-

Video messages are automatically downloaded and autoplayed by default (you can change this in Settings if you’re on a data diet though) and generally feel and act like voice messages – on visual steroids.

-
- -

Picture in Picture

- -

While watching a video message, you can freely browse your other chats – the video will pop up in a corner and continue playing. You can move it around the screen and pause it from anywhere in Telegram. Cool, eh? Well, there's more:

-

Meet Telescope

-

Lots of popular folks address their fans via public channels on Telegram. Video messages will make their connection to fans more direct and intimate than ever. But we want to kick this up another notch.

-

Today we are launching Telescope, a dedicated video hosting platform for those who use videos to communicate with their audiences (here's one for you, blogger people!)

-

With Telescope, public video messages can go viral beyond the Telegram ecosystem. Telescope hosts autoplayed round videos of up to 1 minute in duration – the same format we use for Telegram video messages. And yes, you heard that right, you don't need a Telegram account to view them.

-

Every public channel on Telegram now has a telesco.pe URL, such as telesco.pe/channel_name, where all of its video messages are available to the world wide web and the wide, wide world.

-
- -

A Telescope Channel

- -

Whenever you post a video message to a public channel, it will also be uploaded to Telesco.pe and have a public URL there.

-
- -

Share Telescope Videos

- -

With Telescope, even those users who don’t have Telegram installed will be able to enjoy your public video messages and share them on Twitter or Facebook. As a result, this content will generate more views. And who would refuse more views these days, hmm?

-
-

This was just 1/3 of Telegram 4.0. Keep reading to learn more about Payments for Bots and the new Instant View Platform.

-
-

- -

May 18, 2017,
The Telegram Team

-

- -

P.S. Our founder has this weird urge to keep launching platforms that start with “Tele-”. Be sure to check out Telegraph, the publishing platform we launched last year.

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/video-stickers-better-reactions.html b/data/telegram.org/blog/video-stickers-better-reactions.html deleted file mode 100644 index fbcafb07e7..0000000000 --- a/data/telegram.org/blog/video-stickers-better-reactions.html +++ /dev/null @@ -1,273 +0,0 @@ - - - - - Video Stickers, Better Reactions and More - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Video Stickers, Better Reactions and More

- -
-
-
- -
- Video Stickers, Better Reactions and More -
- -

This update brings easy-to-make video stickers, better reactions with compact animations and extra emoji, a button to review unseen reactions, improved navigation between chats and more.

-

Video Stickers

-

Telegram's animated stickers have unmatched quality and efficiency – needing less than 30 KB of data per sticker. However, creating such stickers requires experience and specialized software such as Adobe Illustrator.

-

Today, we're adding support for stickers converted from regular videos, so that anyone can easily create detailed animated stickers using any video editing program.

-
- -
- -

Like always, you can publish your packs with the @Stickers bot – or add some of the new sets made by others. Whatever you do, never stare back at the tomato.

-
-

Check out the Video Sticker Manual for more details.

-

Developers can use the Sticker Import API to build powerful apps for creating and importing stickers to Telegram.

-
-

Better Reactions

-

Reactions now have more compact animations. To send a larger effect, press and hold on a reaction in the menu.

-

Like interactive emoji, reactions are now synchronized, so your recipients will see the animations in real time.

-
- -
- -

Reactions are used not only to express emotion, but also to answer questions and show approval – which is why they now have read status. Like for replies or @-mentions, a new ♡ button appears when your messages have unseen reactions.

-

New Reactions and Interactive Emoji

-

This update also adds 5 new reactions 🥰🤯🤔🤬👏 to help you discuss anything from Christopher Nolan's movies to global economic news.

-

These reactions can also be sent as interactive emoji. Send a single 🥰🤯🤔🤬 or 👏 to any private chat, then tap on the animated emoji to unleash a synchronized fullscreen effect.

-
- -
- -

Navigating Recent Chats

-

When jumping through unread channels or moving between chats, press and hold the 'Back' button to return to a specific chat. Opening chats from forwarded messages, links, usernames, profiles, etc. adds them to the list.

-
- -
- -

Bug Busting and More

-

Our developers spent two weeks in January focusing completely on fixing known issues in Telegram apps. Among other things, they improved call quality, added support for translation to Instant View pages (and bios on iOS), added the option to send silent messages from the sharing menu – and dozens of other improvements.

-

On iOS, you'll also notice new animations when tapping icons in the tab bar.

-
- -
- -

And that's it for today. Let's leave some features for February.

-

January 31, 2022
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - - diff --git a/data/telegram.org/blog/voice-chats-on-steroids.html b/data/telegram.org/blog/voice-chats-on-steroids.html deleted file mode 100644 index d2695f795c..0000000000 --- a/data/telegram.org/blog/voice-chats-on-steroids.html +++ /dev/null @@ -1,275 +0,0 @@ - - - - - Voice Chats 2.0: Channels, Millions of Listeners, Recorded Chats, Admin Tools - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Voice Chats 2.0: Channels, Millions of Listeners, Recorded Chats, Admin Tools

- -
-
-
- -
- Voice Chats 2.0: Channels, Millions of Listeners, Recorded Chats, Admin Tools -
- -

Voice Chats first appeared in December, adding a new dimension of live talk to Telegram groups. Starting today, they become available in channels too – and there are no more limits on the number of participants.

-

This update also brings recordable voice chats, rich lists of participants, raise hand mechanics, invite links for speakers and listeners, voice chat titles, and a way for public figures to join voice chats as their channels.

-

Limitless Voice Chats

-

Admins of channels and public groups can now host voice chats for millions of live listeners. No matter how popular your talk gets, new people will be able to tune in. It's like public radio reinvented for the 21st century.

-
- -
- -
-

To start a Voice Chat, open the profile of any group or channel where you're an admin, tap (⋮) or (⋯) and select Start Voice Chat.

-
-

Recorded Chats

-

While some conversations are meant to be temporary, others are worth preserving and passing on. Admins can now record audio from voice chats to save talks and publish them for followers who missed the live event.

-
- -
- -

Once you finish recording, the audio file becomes instantly available in your Saved Messages. To avoid surprises, chats that are being recorded are marked with a red light next to their title.

-

Raise Hand

-

In chats where participants are muted, listeners can tap to raise their hand and alert the admins that they want to speak. Just like calling in to a talk show – but with addictive animations.

-
- -
- -

Your bio text is now visible in the list of participants, which you can use to detail your expertise, interests, or just a little bit about yourself. This info might help admins find a good slot for your questions or comments.

-

Speaker and Listener Links

-

Admins of public groups and channels can now create invite links that open the voice chat right away. Separate links can be made for speakers and listeners. This way you won't need to unmute important guests when they join – and they can use a different link to promote the upcoming chat to their communities.

-
- -
- -

Voice chats also have optional titles which help users see the topic of conversation before they join.

-

Join As…

-

When entering a voice chat in a channel, users have the option to join with their personal account or appear as one of their channels. Celebrities and public figures can use this to avoid drawing too much attention to their personal accounts.

-
- Joining a voice chat as a channel -
- - -
-

For example, the Presidents of Brazil and Turkey could meet for a talk in Pavel Durov's Channel and answer questions from users without the risk of having their chat lists flooded with fan mail.

-
-

And More

-

If you choose the wrong chat by mistake when forwarding messages, press the X button before sending them – to either cancel forwarding or choose a different chat.

-
- Choose a different chat or cancel forwarding -
- -

You can also resume playback from where you left off when listening to long voice messages. This was previously available for long videos and long audio tracks, and we thought we'd covered everything – but then our grandma signed up.

-

Last but not least, Android users can choose which action is assigned to swiping left in the chat list: archiving chats, pinning, muting, deleting or marking them as read. (On iOS, all these swipe actions are always available, depending on which way you swipe.)

-
- -
- -

And that's it for today, stay tuned for the next update!

-

- -

March 18, 2021
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - - diff --git a/data/telegram.org/blog/voice-chats.html b/data/telegram.org/blog/voice-chats.html deleted file mode 100644 index a36d1a44d7..0000000000 --- a/data/telegram.org/blog/voice-chats.html +++ /dev/null @@ -1,311 +0,0 @@ - - - - - Voice Chats Done Right - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Voice Chats Done Right

- -
-
-
- -
- Voice Chats Done Right -
- -

Since 2013, we've been expanding the definition of Group Chats, adding features like replies, mentions, polls, admin tools, statistics – and allowing hundreds of thousands of members per group. Many of these features were later incorporated into other apps and redefined how people communicate.

-

Today, Telegram groups get an entire new dimension with Voice Chats – persistent conference calls that members can join and leave as they please. Our 12th update in 2020 brings them to you just in time for remote Christmas carols.

-
-

UPD March 2021: Don't miss Voice Chats 2.0: Channels, Millions of Listeners, Recorded Chats, Admin Tools

-
-

Voice Chats

-

Any Telegram group can now become a voice chat room that is always on. Voice Chats run in parallel to existing text and media-based communication, adding a live layer of ephemeral talk to the group. They can be used as virtual office spaces for teams or informal lounges for any community.

-

While Voice Chats are not group calls, they can achieve similar goals – at the same time offering flexibility instead of old school scheduling. In larger groups, they also provide serendipitous opportunities for talking to people.

-
- -
- -

Groups with active voice chats have a special bar at the top that shows who is talking at the moment (and even how loud they are). This can help you pick the right moment to join – like noticing your friends going over to the cooler.

-
- -
- -

After joining a voice chat, you are free to move around the app, browse conversations and send messages. You stay connected to the chat and the microphone controls remain on screen so that you can quickly mute and unmute yourself at any time.

-

If you're on Android, you can enjoy the full Voice Chat experience with a system-wide floating widget that shows your mic controls and who is currently talking, even when Telegram is in the background. Santa is on Android too – and he needs his sleigh navigator open at all times.

-
- -
- -

You can chat with whomever is online or invite more people via the handy menu. Voice Chats can accommodate a few thousand participants, which means they'll work for everything from consulting family members while out shopping to a massive live event.

-

Last but not least, Voice Chats show spectacular animations. To get these right, our designer had to sell his soul to the devil – and we think it was totally worth it.

-
-

To create a Voice Chat and find your own unique way of using them, open the profile of any group where you're an admin, tap (⋯) or (⋮) and select Start Voice Chat.

-
-

Like Telegram groups before them, we hope that Voice Chats will change the way people collaborate and keep in touch. In the coming weeks, we'll be refining them further, listening to your feedback, improving noise suppression, and adding more features like video and screen sharing.

-

Push-to-Talk Shortcuts

-

On Telegram Desktop and in the native macOS app, you can choose a push-to-talk key for Voice Chats, to control your mic even when Telegram is not focused. At long last, we've found a use for your Caps Lock key.

-
- -
- -

Sticker Outlines

-

Animated stickers on Telegram are optimized for efficiency and deliver smooth 180 frame animations with infinite resolution in less than 50 KB.

-

With today's update, stickers will load even faster than before – and show a shimmering outline of what you're about to see. Be careful not to blink though, or you'll miss it.

-
- -
- -

SD Card Storage on Android

-

Users on Android devices can now move their Telegram app data from internal storage to their SD card, allowing those with minimal storage to save more media and files and maximize their Telegram experience.

-
- Storage Usage settings -
- -
-

Remember that you can always keep Telegram's storage footprint on your device incredibly small. See Settings > Data and Storage > Storage Usage.

-
-

New Animations on Android

-

We've added slick new animations throughout the Android app – when tapping the New Message button, opening profiles, managing chat folders and anywhere you see message counters.

-
- -
- -

Announce Messages on iOS

-

If you're still on iOS, you can have Siri read incoming messages aloud in your headphones. Open iOS Settings > Notifications > Announce Messages and set Telegram to ON to stay up to date on your chats even while washing the dishes.

-

Editing Improvements

-

Android users can now quickly edit a photo which they've already sent to add effects, drawings or stickers with our powerful media editor. iOS users can tap the pen button to quickly edit and send back a photo they have received.

-

Each of these features was previously available only on one of the platforms, but now both iOS and Android offer equal opportunities for drawing moustaches on selfies.

-
- Editing Improvements on iOS and Android -
- -

When editing a message or caption, as you approach the maximum message length, a counter will appear showing how many remaining characters you have lef

-

More Animated Emoji

-

No update is complete without even more animated emoji. As usual, simply send a message with a single emoji to get one of these 👇 in a chat.

-
- -
- -

There's a story in there somewhere about a cyber cowboy solving a murder mystery.

-

Feature Suggestion Platform

-

Many Telegram features started out as user suggestions. To help identify potential new features and locate bugs within the app, we're launching a public Bug and Suggestion Platform.

- - -

We'll be rolling out the ability to suggest new features and report bugs gradually to make sure each submission gets the attention it deserves. All Telegram users are already welcome to view existing entries and vote on them.

-

And that's all for today, we'll see you in 2021 or once we're done building the next big thing – whichever comes first.

-

- -

December 23, 2020
The Telegram Team

-

- -
-

P.S. The end of the year is normally a time to look back at the past 12 months. Instead, our founder Pavel Durov has just announced his strategy for making Telegram sustainable, to continue providing you with great features for decades to come.

-
-
- -
- - -
- - -
-
-
- - - - - - - - diff --git a/data/telegram.org/blog/winter-contest-ends.html b/data/telegram.org/blog/winter-contest-ends.html deleted file mode 100644 index 1b651c3bac..0000000000 --- a/data/telegram.org/blog/winter-contest-ends.html +++ /dev/null @@ -1,224 +0,0 @@ - - - - - Winter Contest Ends - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Winter Contest Ends

- -
- -
- -

The contest to decrypt intercepted traffic of Telegram produced no winners as of March, 1. As promised, today we are publishing the encryption keys necessary to decrypt the traffic.

-
SECRET CHAT:
-2e 20 9f 9d 99 c9 fc 8a 3d dc d5 6d 21 26 46 c9 d8 1a 26 f8 ec f7 f2 7e c9 28 65 95 52 dc 1c 21 bb 95 60 b1 d8 5f 94 5f 43 8d 7e 8e 96 fa e6 89 91 a9 90 39 8b df ef 50 22 06 f8 52 80 e6 50 20 62 71 c4 b2 f5 f8 88 4d 83 ae 66 ec fe cd ec 92 26 69 72 5e 85 f9 ea 58 b0 d6 9f 5b 1e b7 68 15 76 5b 12 88 3d 17 f6 62 49 8b 1f 9d 7a 11 94 67 8d d1 ee d6 55 50 d4 51 c0 5e a5 9a 1a eb 8a 8c 7c 44 1b db 96 5a fd cd 85 47 5b f0 8a 1e b8 d6 74 a4 c7 e7 af 19 3f a6 0a ff e5 3b 9f c4 fc ea 59 af f6 72 60 16 6f 40 af 58 95 98 06 0c 22 00 d7 3d be 96 19 56 54 06 74 d2 6b 38 8d c2 a0 97 62 6d e4 10 99 b9 cf d5 0f 56 9d d3 bb 49 86 d5 15 23 86 03 c3 52 67 82 77 5e 53 e9 ba e8 63 58 ed 55 b0 ef ec 69 65 a0 e5 1d e4 b6 6e 5a 3d 5f 9b 9a 20 67 f5 d5 c4 d7 60 14 c6 56 2d 12 1b 0a
-
-DC 1:
-5e a6 0d a2 9c 90 8e f4 36 d5 48 fe 76 a3 11 f6 66 13 4e 94 bb 11 32 d6 cf fd b0 2f 7b 77 bb 01 d7 42 a4 22 d3 04 e7 d2 fc 5b 32 48 d6 71 eb 18 51 19 99 76 49 46 1a 43 d8 cf cd 8a e2 fe 42 2c 36 d7 05 8b 0c 5e 00 8a 5a bc 35 4f ec 75 b4 10 e1 84 bb cb af ec e3 d6 fd 59 fd 01 83 ef 8b dd 13 50 24 5b 80 09 75 7e c3 c3 08 ba 59 f4 ec c0 87 71 ba 9f 45 8c 15 df 2a cd a5 bc 81 a9 20 fe 42 e2 65 78 02 77 80 11 0e e4 67 f3 40 cf 72 be fc c2 8d 0b ad d9 9e 6e 1a c3 03 71 39 be b9 dd df 7c 63 a6 27 45 ee 8e 00 5e 12 51 51 6c 6a 10 a6 73 3a 10 5d d8 f3 b6 c5 70 fe 91 c2 64 4b d0 74 2d 47 e7 4e 00 cf d5 d3 65 15 2b 48 9c 75 eb a8 96 aa ce 09 49 9b 5e ea 76 06 19 f3 b3 e7 7b af df 5d 68 5e 80 10 48 ec 00 35 90 d3 e5 96 c6 59 a7 44 d8 20 a8 a2 b6 93 64 4f 98 44 23 8e fd
-
-DC 2:
-63 ab 0d b7 98 e1 78 ef 5f 05 9c e4 84 3b 53 b3 4f 6e d1 d3 8a 6d 59 19 32 26 73 60 c2 e2 fe ee d3 2d 74 35 18 08 ba 04 87 cf 7f d9 87 4b 64 d5 80 06 05 f5 01 56 6d c2 66 7e 2d ef f6 a3 82 3d 31 0e ed 6b 46 4c 11 d5 ec 0f 7b be 64 79 26 87 a9 d3 34 27 d8 8b aa b5 36 8b 95 2f a7 c7 2a a6 bf a9 44 51 c5 c8 06 04 78 d2 64 87 e8 13 f3 f0 9b c9 8c bc 29 01 55 a2 80 e1 e8 4e 74 53 7e 05 22 1b 51 3d 1a c5 61 b3 04 98 c2 2f 71 e3 76 2e 31 bd d8 55 15 4b 3e 34 ed 84 b2 56 d0 bd c6 9a 1a 2a 4b 2f fc 68 8e c4 e3 81 23 6f 07 3f 3a 6b 56 f6 ee 31 e6 aa 0d 49 36 6a 51 79 25 bf b6 40 64 8c e2 14 c8 70 37 cb 70 ad a1 83 ed 1f b9 78 b9 93 0c 7c 0c ed 6d c6 aa c2 d0 da 51 ce ae cf 99 8f 65 eb 5a 42 e6 ff 4a 51 a9 97 da 6e ac e5 63 c1 05 a9 fe d0 da da 43 e3 50 14 fc b1 46 ea
-
-DC 3:
-16 0c be 58 e1 74 74 f5 f9 8f f8 82 71 ed 57 84 20 49 bd da 17 0e 00 a8 a4 24 71 79 86 1f ef 3e 41 70 31 de c9 c2 19 23 37 fd ec 2f fa 9e 89 29 4f a2 af 69 cf 24 3a 6e 44 5d 89 d2 8b 50 45 26 3c ff e3 d4 4d 7d b4 88 54 8c 87 09 c5 ac 09 5c e6 62 43 73 b5 3e 96 ea f3 62 76 58 1b fd 8a 36 45 65 4a fc 7b ee 7b 13 06 e5 2f 9d 8f cb b9 a7 6f 76 00 f4 9a ab 50 fb 91 e0 2b ce 28 db 95 02 a0 62 33 bb e7 41 13 7b 2c 7e ba 7c d5 87 12 33 de 44 8d 4b 76 af 59 cc 80 42 02 69 56 90 8a 5d 95 0b 3e 8b ef 65 17 fc 79 62 b4 69 1b 21 aa 89 5b 22 f6 33 67 80 d0 22 f7 76 f2 6c 4b af 69 07 0f 2c 3a af 67 6b 74 c0 7f 8c 83 85 85 8e 47 b7 55 42 c1 3d 70 33 9d 87 60 7c f6 8b 99 96 1d af 82 b8 d2 37 c7 a3 fc ac 25 fe 77 f0 29 4d 82 a4 15 89 cb c2 27 ae 4f 16 d6 b8 4c cb de 2a 59 d7
-
-DC 4:
-b4 aa dc bc 8e e5 6a f4 9f 7b 65 de cd 1c 28 3d f1 58 f6 03 e1 34 9d 63 54 b0 15 a7 b8 a6 45 4e de dd cd e4 1a 54 d7 9b fe 46 05 c7 62 19 d9 7a c0 00 6b e6 72 83 3d 15 00 99 d9 9b 97 c0 4a a8 85 e7 85 3c 3f a4 2f 6a 57 0b 3c b0 2a 97 65 6f bf 4e 0d 93 f7 55 3b 3a 39 a1 1a 0f db 9d 7a df 5b c6 9b 45 9a ea e4 27 92 8c c3 d2 75 53 66 e4 1c 29 f1 14 fc fd e8 c0 c8 12 47 ee 5a 92 f1 bf 1f 6f 8e 95 a5 90 81 37 d6 5d bd 5c 4c 41 61 29 6e 4f 7e 83 e1 b9 ef 00 00 de 25 33 f4 df 1a 94 f0 e7 1c fd 35 c0 75 65 88 ef c5 aa b5 c9 7d 0e e4 6d b7 9f 10 ca 4b f0 c9 c7 2d 30 20 e9 e1 b8 03 de a2 60 4e 3f 59 dc 36 a2 50 f8 52 5e 32 c8 c1 84 87 84 d6 54 42 dd ab b4 1b d6 fe e4 29 d3 70 4e 3e 48 ba 86 80 39 b7 94 3c 31 18 f8 bd 7b d8 89 6b 32 77 5c 89 4a a1 ca 18 ba 1e 6a 87 6a
-
-DC 5:
-4c 76 1f 87 08 53 54 cb 12 fd 01 bd bd e6 42 d2 6b 47 4b d8 0b 6a eb 9f 24 8b ee 77 1f 8b a5 3f f5 f1 c7 80 05 80 2c 20 29 7c 3c 14 59 2b 5e 7f 69 58 3b 7e 07 37 25 67 3d 18 ac f2 28 43 63 8f a5 41 c1 ba 53 dd eb 3d 36 0d 7b d3 14 f7 f9 83 aa 0c 81 20 89 e0 c7 d7 e9 ef 11 aa 43 ca 54 2a 9f 69 0f 1d 99 ef f6 55 14 71 6d a3 1e c2 75 fb 1c 88 f7 c0 21 64 5d 34 db 3f a4 e7 a9 f0 af 9f 9d 14 a4 3a 49 7c 50 e6 45 24 3a cb a4 a6 2a 35 dd 6c 9c ce 87 24 d1 ff 13 19 15 43 89 a4 8c 39 66 a2 22 df 4e 94 76 e1 89 b5 03 7a 2b 34 e7 39 09 f9 22 5d cb 36 4e ce 37 e7 cf 7d ab b5 8b db 81 c6 c8 f4 c7 7c 3a 22 59 fc e6 32 19 aa 46 d2 95 96 61 61 e6 cc 57 f0 0e 87 5c 7d 5b 87 e7 64 28 c6 03 38 3c 0b a6 5e 4a 21 a3 67 af e5 b3 88 cc 9d 03 98 33 ac c6 87 b4 b6 82 42 c4 41 33 39
-


- -

We would like to use this opportunity to thank the users ABC, @DefuseSec, @hackappcom, @Morj and x7mz who helped us further improve security of the client apps and expand guidelines for third-party developers.

-

Since we have no winner in the current challenge, we are going to launch a new competition, with an easier task, but a larger prize. The new competition will allow participants not only to intercept traffic, but to manipulate it as well. We are now building the tools that will enable the contestants to perform all kinds of active attacks. Once the platform is ready later this month, we will announce the new contest on Twitter. Please follow us at @telegram!

-

March 2, 2014
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/faq_channels.html b/data/telegram.org/faq_channels.html deleted file mode 100644 index 9cd612a10c..0000000000 --- a/data/telegram.org/faq_channels.html +++ /dev/null @@ -1,165 +0,0 @@ - - - - - Channels FAQ - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
-
-

Channels FAQ

- -
-

This FAQ is about Telegram channels.
Back to the main FAQ »

-
-

-
-

Q: What's a channel?

-

Channels are a tool for broadcasting public messages to large audiences. In fact, channels can have an unlimited number of subscribers. When you post in a channel, the message is signed with the channel's name and not yours. You can appoint additional administrators to help you manage the channel. New subscribers can see the entire message history in a channel once they join.

-

If you'd like an example, join our official Telegram channel to get notified about our updates.

-

To create a channel:
iPhone: Start a new message (tap the icon in the top-right corner in Chats). Then ‘New Channel’.
Android: Tap the circular pencil icon in the chat list. Then ‘New Channel’.
Windows Phone: Tap the ‘+’ button on the bottom bar. Then ‘New Channel’.

-

Q: How are public and private channels different?

-

Public channels have a username. Anyone can find them in Telegram search and join. Private channels are closed societies – you need to be added by the owner or get an invite link to join.

-

Please note that private channels with publicly available invite links will be treated in the same way as public channels, should it come to content disputes.

-

Q: What can administrators do?

-

The owner of a channel can broadcast messages, delete any messages, add subscribers (the first 200 only), remove subscribers, change the channel's name, profile image and link, as well as delete the channel completely. The owner can also add and remove administators to help manage the channel.

-

You can set up administrator rights for each individual administrator when you appoint them.

-

Q: What happens if I delete a message?

-

If a message is deleted in a channel, it will disappear for all subscribers.

-

Q: How do I add people to my channel?

-

As the channel's owner, you may invite the first 200 subscribers to your channel. Once the subscriber count reaches 200, the channel is on its own. If it's a public channel, it will have a username and a telegram.me/ link (e.g. t.me/telegram) – you can post this link on social networks, advertise it in magazines, or tattoo it on your back. If you have a private channel, you can send an invite link to your friends.

-

Please do not send channel links (or other unsolicited messages) to strangers. If they report spam from your account, you may be banned from contacting other people, however good your intentions.

-

Q: What does the eye icon mean?

-

Each post in a channel has a view counter. Views from forwarded copies of your messages are also included in the total count. This way you can see how far it has spread.

-

Please note that these numbers are approximate — we don't want to keep a record for everything you've ever viewed. After a short while (around 4 days), Telegram will forget that you've seen a post and will count you again if you navigate to it. For this reason you may see several views for posts in a private channel where you are alone.

-

Q: How do I know who posted a message?

-

As the owner of the channel, you can enable admin signatures that users will see next to the view counters. These signature only mention the name of the administrator and no link to their profile.

-

If the signatures are disabled, there is no way for users to know whether a message was posted by the owner or one of the administrators.

-

Q: Are there any feedback options?

-

You can add a discussion group chat to the channel, and your subscribers will see a comment button for each post in the channel. Comments show up in a thread of their own and also land in the discussion group to keep everyone in the loop and make it easier for admins to keep the conversation civil.

-

You can also use bots (e.g. the @like bot) to add buttons to your posts.

-
- -
- -
-
-
- - - - - - - diff --git a/data/telegram.org/faq_spam.html b/data/telegram.org/faq_spam.html deleted file mode 100644 index a7ff571d34..0000000000 --- a/data/telegram.org/faq_spam.html +++ /dev/null @@ -1,163 +0,0 @@ - - - - - Spam FAQ - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
-
-

Spam FAQ

- -
-

This FAQ is for people whose accounts were limited after being reported for spam.
Back to the main FAQ »

-
-

-
-

Q: What happened to my account?

-

When users press the ‘Report spam’ button in a chat, they forward these messages to our team of moderators for review. If the moderators decide that the messages deserved this, the account becomes limited temporarily.

-

This means that if you have been sending unwanted messages to random strangers or posting spam in groups, you lose the ability to do so.

-

Q: So I can't send messages anymore?

-

No, it's not that bad. Limited accounts can send messages to people who have their number saved as a contact. You can also always reply to anyone who messages you first.

-

Q: Why was I reported?

-

Telegram‘s username search is not a tool for making new friends. People usually don’t like it when strangers contact them — so they will report you if they find your messages annoying. Please only contact people if you're sure that they are expecting messages from you. The same applies to adding people to unwanted groups and channels. In addition to this, group admins can also report users who post spam in their groups.

-

Naturally, all such reports are also checked by human moderators. If the messages contain spam, the account will be temporarily limited.

-

Q: What can people report me for?

-

For private messages, it really doesn‘t matter what you send, as long as the receivers find it unwelcome. It could have been a photo, an invite link or a simple ’hello‘. Please only send messages when you are sure people won’t mind getting them.

-

As a general rule, people do mind getting unsolicited advertisements, links, invite links to groups or channels, random photos and, above all, anything related to commerce or online popularity. If you send them something like this, you will be blocked — and everybody else will be happy.

-

Moderators are more lenient when it comes to messages in groups, but anyone who sends spam or unsolicited advertisments will be limited.

-

Q: What do I do now?

-

If this happened to you for the first time (and you are not an industrial scale spammer), most likely your account will be limited for a few days or so. Please wait and consider that people want a peaceful time using our messenger.

-

Repeated offences will result in longer periods of being blocked. If you keep writing unwanted messages to strangers, you may lose the ability to do so forever.

-

Q: I read all of the above, and I‘m certain that I didn’t break any rules!

-

If you are sure that the limit was wrongfully applied to your account, please contact our @SpamBot.

-

Please forgive us for the inconvenience — even the best systems, algorithms and well-trained people can make mistakes sometimes.

-

Q: I know I was wrong, please release me sooner!

-

We're sorry, but this is impossible. We value the inner peace of Telegram users too much.

-

Q: I‘ve just signed up and didn’t send any messages yet, but my account is limited.

-

Some numbers may trigger an overly harsh response from our system, either due to their previous owners‘ activities or due to them being certain virtual/VOIP numbers. We’re sorry if this resulted in your account being limited for no reason.

-

If you think this is your case, please contact @SpamBot and tell it your story.

-
- -
- -
-
-
- - - - - - - diff --git a/data/telegram.org/privacy.html b/data/telegram.org/privacy.html deleted file mode 100644 index 363908ba0d..0000000000 --- a/data/telegram.org/privacy.html +++ /dev/null @@ -1,299 +0,0 @@ - - - - - Telegram Privacy Policy - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
-
-

Telegram Privacy Policy

- -
- -

-

1. Introduction

-

This Privacy Policy sets out how we, Telegram Messenger Inc. (“Telegram”), use and protect your personal data that you provide to us, or that is otherwise obtained or generated by us, in connection with your use of our cloud-based messaging services (the “Services”). For the purposes of this Privacy Policy, ‘we’, ‘us’ and ‘our’ refers to Telegram, and ‘you’ refers to you, the user of the Services.

-

1.1 Privacy Principles

-

Telegram has two fundamental principles when it comes to collecting and processing private data:

-
    -
  • We don't use your data to show you ads.
  • -
  • We only store the data that Telegram needs to function as a secure and feature-rich messaging service.
  • -
-

1.2. Terms of Service

-

This Privacy Policy forms part of our Terms of Service, which describes the terms under which you use our Services and which are available at https://telegram.org/tos. This Privacy Policy should therefore be read in conjunction with those terms.

-

1.3. Table of Contents

-

This Privacy Policy explains the following:

- -

1.4. EEA Representative

-

If you live in a country in the European Economic Area (EEA), the Services are provided by Telegram, which for the purposes of applicable data protection legislation is the data controller responsible for your personal data when you use our Services. However, as Telegram is located outside the EEA, we have designated one of our EEA-based group companies, Telegram UK Holdings Ltd (71-75 Shelton Street, Covent Garden, London, England, WC2H 9JQ), as a representative to whom you may direct any issues you have relating to our processing of your personal data.

-

2. Legal Ground for Processing Your Personal Data

-

We process your personal data on the ground that such processing is necessary to further our legitimate interests (including: (1) providing effective and innovative Services to our users; and (2) to detect, prevent or otherwise address fraud or security issues in respect of our provision of Services), unless those interests are overridden by your interest or fundamental rights and freedoms that require protections of personal data.

-

3. What Personal Data We Use

-

3.1. Basic Account Data

-

Telegram is a communication service. You provide your mobile number and basic account data (which may include profile name, profile picture and about information) to create a Telegram account.

-

To make it easier for your contacts and other people to reach you and recognize who you are, the screen name you choose, your profile pictures, and your username (should you choose to set one) on Telegram are always public. We don't want to know your real name, gender, age or what you like.

-

We do not require your screen name to be your real name. Note that users who have you in their contacts will see you by the name they saved and not by your screen name. This way your mother can have the public name 'Johnny Depp' while appearing as 'Mom' to you and as 'Boss' to her underlings at work (or the other way around, depending on how these relationships are structured).

-

3.2. Your E-mail Address

-

When you enable 2-step-verification for your account or store documents using the Telegram Passport feature, you can opt to set up a password recovery email. This address will only be used to send you a password recovery code if you forget it. That's right: no marketing or “we miss you” bullshit.

-

3.3. Your Messages

-
3.3.1. Cloud Chats
-

Telegram is a cloud service. We store messages, photos, videos and documents from your cloud chats on our servers so that you can access your data from any of your devices anytime without having to rely on third-party backups. All data is stored heavily encrypted and the encryption keys in each case are stored in several other data centers in different jurisdictions. This way local engineers or physical intruders cannot get access to user data.

-
3.3.2. Secret Chats
-

Secret chats use end-to-end encryption. This means that all data is encrypted with a key that only you and the recipient know. There is no way for us or anybody else without direct access to your device to learn what content is being sent in those messages. We do not store your secret chats on our servers. We also do not keep any logs for messages in secret chats, so after a short period of time we no longer know who or when you messaged via secret chats. For the same reasons secret chats are not available in the cloud — you can only access those messages from the device they were sent to or from.

-
3.3.3. Media in Secret Chats
-

When you send photos, videos or files via secret chats, before being uploaded, each item is encrypted with a separate key, not known to the server. This key and the file’s location are then encrypted again, this time with the secret chat’s key — and sent to your recipient. They can then download and decipher the file. This means that the file is technically on one of Telegram’s servers, but it looks like a piece of random indecipherable garbage to everyone except for you and the recipient. We don’t know what this random data stands for and we have no idea which particular chat it belongs to. We periodically purge this random data from our servers to save disk space.

-
3.3.4. Public Chats
-

In addition to private messages, Telegram also supports public channels and public groups. All public chats are cloud chats (see section 3.3.1 above). Like everything on Telegram, the data you post in public communities is encrypted, both in storage and in transit — but everything you post in public will be accessible to everyone.

-
3.4. Phone Number and Contacts
-

Telegram uses phone numbers as unique identifiers so that it is easy for you to switch from SMS and other messaging apps and retain your social graph. We ask your permission before syncing your contacts.

-

We store your up-to-date contacts in order to notify you as soon as one of your contacts signs up for Telegram and to properly display names in notifications. We only need the number and name (first and last) for this to work and store no other data about your contacts.

-

Our automatic algorithms can also use anonymized sets of phone numbers to calculate the approximate number of potential contacts an unregistered phone number may have on Telegram. When you open the 'Invite friends' interface, we display the resulting statistics next to your contacts to give you an idea of who could benefit most from joining Telegram.

-

You can always stop syncing contacts or delete them from our servers in Settings > Privacy & Security > Data Settings.

-
-

If you are using Android, Telegram will ask you for permission to access your phone call logs (READ_CALL_LOG). If you grant this permission, Telegram will be able verify your account by transmitting a phone call instead of asking you to enter a code. Telegram uses this permission only to confirm receipt of the confirmation call by verifying the number in the call log.

-
-

3.5. Location Data

-

If you share a location in a chat, this location data is treated like other messages in cloud or secret chats respectively.

-

If you share your Live Location in any chat or turn on ’Make Myself Visible’ in People Nearby, Telegram will use your data to display your location to those users with whom you are sharing it, even when the app is closed – for as long as you keep these optional features activated.

-
3.6. Cookies
-

The only cookies we use are those to operate and provide our Services on the web. We do not use cookies for profiling or advertising. The cookies we use are small text files that allow us to provide and customize our Services, and in doing so provide you with an enhanced user experience. Your browser should allow you to control these cookies, including whether or not to accept them and how to remove them. You may choose to block cookies with your web browser, however, if you do disable these cookies you will not be able to log in to Telegram Web.

-

4. Keeping Your Personal Data Safe

-

4.1. Storing Data

-

If you signed up for Telegram from the UK or the EEA, your data is stored in data centers in the Netherlands. These are third-party provided data centers in which Telegram rents a designated space. However, the servers and networks that sit inside these data centers and on which your personal data is stored are owned by Telegram. As such, we do not share your personal data with such data centers. All data is stored heavily encrypted so that local Telegram engineers or physical intruders cannot get access.

-

4.2. End-to-End Encrypted Data

-

Your messages, media and files from secret chats (see section 3.3.2 above), as well as the contents of your calls and the data you store in your Telegram Passport are processed only on your device and on the device of your recipient. Before this data reaches our servers, it is encrypted with a key known only to you and the recipient. While Telegram servers will handle this end-to-end encrypted data to deliver it to the recipient – or store it in the case of Telegram Passport data, we have no ways of deciphering the actual information. In this case, we neither store nor process your personal data, rather we store and process random sequences of symbols that have no meaning without the keys which we don’t have.

-

4.3. Retention

-

Unless stated otherwise in this Privacy Policy, the personal data that you provide us will only be stored for as long as it is necessary for us to fulfill our obligations in respect of the provision of the Services.

-

5. Processing Your Personal Data

-

5.1. Our Services

-

Telegram is a cloud service. We will process your data to deliver your cloud chat history, including messages, media and files, to any devices of your choosing without a need for you to use third-party backups or cloud storage.

-

5.2. Safety and Security

-

Telegram supports massive communities which we have to police against abuse and Terms of Service violations. Telegram also has more than 400 million users which makes it a lucrative target for spammers. To improve the security of your account, as well as to prevent spam, abuse, and other violations of our Terms of Service, we may collect metadata such as your IP address, devices and Telegram apps you've used, history of username changes, etc. If collected, this metadata can be kept for 12 months maximum.

-

5.3. Spam and Abuse

-

To prevent phishing, spam and other kinds of abuse and violations of Telegram’s Terms of Service, our moderators may check messages that were reported to them by their recipients. If a spam report on a message you sent is confirmed by our moderators, your account may be limited from contacting strangers – temporarily or permanently. You can send an appeal using @Spambot. In case of more serious violations, your account may be banned. We may also use automated algorithms to analyze messages in cloud chats to stop spam and phishing.

-

5.4. Cross-Device Functionality

-

We may also store some aggregated metadata to create Telegram features (see section 5.5 below) that work across all your devices.

-

5.5. Advanced features

-

We may use some aggregated data about how you use Telegram to build useful features. For example, when you open the Search menu, Telegram displays the people you are more likely to message in a box at the top of the screen. To do this, we calculate a rating that shows which people you message frequently. A similar rating is calculated for inline bots so that the app can suggest the bots you are most likely to use in the attachment menu (or when you start a new message with “@”). To turn this feature off and delete the relevant data, go to Settings > Privacy & Security > Data Settings and disable “Suggest Frequent Contacts”.

-

5.6. No Ads Based on User Data

-

Unlike other services, we don't use your data for ad targeting or other commercial purposes. Telegram only stores the information it needs to function as a secure and feature-rich cloud service.

-

Telegram offers a tool for advertisers to promote their messages in public one-to-many channels, but these sponsored messages are based solely on the topic of the public channels in which they are shown. No user data is mined or analyzed to display ads or sponsored messages.

-

6. Bot Messages

-

6.1. Ecosystem

-

Telegram has an API that allows third-party developers to create bots. Bots are apps that look like special Telegram users: you can talk to them from your chat list, add them to groups or use a special “inline” interface to access their features. By performing any of these actions, you will be sending some of your data to the respective third-party bot developers.

-

6.2. How Bots Can Receive Data

-

You can send data to bot developers when you interact with their bots in one of these ways:

-
    -
  • By sending messages to a bot.
  • -
  • By using an inline bot.
  • -
  • By participating in a group with a bot.
  • -
  • By pressing buttons in messages sent by a bot.
  • -
  • By paying for goods and services via bots (see section 7 below).
  • -
-

6.3. What Data Bots Receive

-

In any of the above cases, the developers of an automated user (bot) can get your public account data (see section 3.1 above): your screen name, username and profile picture(s).

-

Bots can also receive the following data when you interact with them.

-
    -
  • Bots will obviously get your messages when you send them something.
  • -
  • If you click on links or buttons provided by the bot, the bot can potentially get your IP address (provided that it controls the website to which the link leads).
  • -
  • If the bot is a member of the same group with you, it may know you are a member.
  • -
  • When you start your message with the username of an inline bot (e.g. @gif) the interface transforms so that everything you type becomes a query to that bot. This query is sent to the bot so that it can provide its service. We will warn you about this the first time you use an inline bot.
  • -
  • Bots added to groups can operate in two modes: with access to messages in the group or without access. If the bot has access to messages, it can see everything that happens in the group. The interface clearly shows whether or not a bot has access to messages in groups.
  • -
-

6.4. Bots Are Not Maintained by Telegram

-

Other than our own bots, no other bots or third-party bot developers are affiliated with Telegram. They are completely independent from us. They should ask you for your permission before they access your data or you make it available to them.

- - -

7. Third Party Payment Services

-

7.1. Payment Information

-

The Payment Platform for Bots is available to users as of Telegram 4.0. Telegram does not process payments from users and instead relies on different payment providers around the world. It is the payment providers that handle and store your credit card details. Neither Telegram nor the merchants on the platform (bot developers) have access to this information. Although we work with payment providers they are completely independent from Telegram. Please study their relevant privacy policies before making your data available to them.

-

7.2. Credit Card Information

-

When making a purchase, you enter your credit card details into a form supplied by the payment provider that will be processing the payment, and this information goes directly to the payment provider's server. Your credit card information never reaches Telegram's servers. We do not access and do not store your credit card information. When you save your credit card info, it is saved on the respective payment provider's servers and the payment provider gives Telegram a token that you can reuse for future payments. It is not possible to reconstruct your credit card info from the token.

-

7.3 Shipping Information

-

When you enter shipping information in the process of placing an order, we send it directly to the merchant bot developer. We can store your shipping information for you if you choose to save it for future purchases. We will delete this information immediately if you ask us to.

-

7.4. Clearing Payment Information

-

You can clear all payment information associated with your account at any time by going to Telegram Settings > Privacy & Security > Data Settings and selecting ‘Clear Payment & Shipping Info’. If you choose to remove your payment information, we will delete your stored shipping info and payment tokens from all providers and ask the payment providers to remove your credit card information that they store.

-

7.5. Payment Disputes

-

Due to the fact that Telegram doesn't store any credit card details or transaction information, it is impossible for us to handle complaints or cashbacks – any disputed payments are the responsibility of the bot developers, payment providers, and banks that participated in the exchange.

-

8. Who Your Personal Data May Be Shared With

-

8.1. Other Telegram Users

-

Other users of our Services with whom you choose to communicate with and share certain information, who may be located outside the EEA. Note that by entering into the Terms of Service and choosing to communicate with such other users of Telegram, you are instructing us to transfer your personal data, on your behalf, to those users in accordance with this Privacy Policy. We employ all appropriate technical and organizational measures (including encryption of your personal data) to ensure a level of security for your personal data that is appropriate to the risk.

-

8.2. Telegram’s Group Companies

-

We may share your personal data with: (1) our parent company, Telegram Group Inc, located in the British Virgin Islands; and (2) Telegram FZ-LLC, a group member located in Dubai, to help provide, improve and support our Services. We will implement appropriate safeguards to protect the security and integrity of that personal data. This will take the form of standard contract clauses approved by the European Commission in an agreement between us and our relevant group companies. If you would like more information regarding these clauses, please contact us using the details in section 12 below.

-

8.3. Law Enforcement Authorities

-

If Telegram receives a court order that confirms you're a terror suspect, we may disclose your IP address and phone number to the relevant authorities. So far, this has never happened. When it does, we will include it in a semiannual transparency report published at: https://t.me/transparency.

-

9. Your Rights Regarding the Personal Data You Provide to Us

-

9.1. Your Rights

-

Under applicable data protection legislation, in certain circumstances, you have rights concerning your personal data. You have a right to: (1) request a copy of all your personal data that we store and to transmit that copy to another data controller; (2) delete (see section 10 below) or amend your personal data; (3) restrict, or object to, the processing of your personal data; (4) correct any inaccurate or incomplete personal data we hold on you; and (5) lodge a complaint with national data protection authorities regarding our processing of your personal data.

-

9.2. Exercising Your Rights

-

If you wish to exercise any of these rights, kindly contact us using the details in section 12 below.

-

9.3. Data Settings

-

You can control how your data is used (e.g., delete synced contacts) in Settings > Privacy & Security > Data Settings (using one of our mobile apps).

-

Sadly, if you're not OK with Telegram's modest minimum requirements, it won't be possible for us to provide you with our Services. You can delete your Telegram account by proceeding to the deactivation page.

-

10. Deleting data

-

10.1. Accounts

-

If you would like to delete your account, you can do this on the deactivation page. Deleting your account removes all messages, media, contacts and every other piece of data you store in the Telegram cloud. This action must be confirmed via your Telegram account and cannot be undone.

-

10.2. Messages

-
    -
  • In secret chats, deleting a message always instructs the app on the other end to delete it too.
  • -
  • In cloud chats, you can choose to delete a message for all participants within at least 48 hours after sending. Otherwise, deleting a message will delete it from your message history. This means that a copy will stay on the server as part of your partner's message history. As soon as your partner deletes it too, it's gone forever.
  • -
  • As of version 5.5, any party can choose to delete any messages in one-on-one chats, both sent and received, for both sides. There is no time limit. Any party can also opt to clear the entire chat history for both parties, in which case the apps will be instructed to remove all messages in that chat, however many of them are still retained by either of the participants.
  • -
  • In supergroups and channels, deleting a message removes it for all participants. Note that deleted messages and original versions of edited messages from supergroups are stored for 48 hours after deletion in order to be shown in the admins log.
  • -
-

10.3. Self-Destructing Messages

-

Messages in Secret Chats can be ordered to self-destruct. As soon as such a message is read (2 checks appear), the countdown starts. When the timer expires, both devices participating in a secret chat are instructed to delete the message (photo, video, etc.). Media with short timers (less than a minute) are shown with blurred previews. The timer is triggered when they are viewed.

-

10.4. Account Self-Destruction

-

By default, if you stop using Telegram and do not come online for at least 6 months, your account will be deleted along with all messages, media, contacts and every other piece of data you store in the Telegram cloud. You can go to Settings to change the exact period after which your inactive account will self-destruct.

-

11. Changes to this Privacy Policy

-

We will review and may update this Privacy Policy from time to time. Any changes to this Privacy Policy will become effective when we post the revised Privacy Policy on this page www.telegram.org/privacy. Please check our website frequently to see any updates or changes to our Privacy Policy, a summary of which we will set out below.

-

March 25, 2019

-
    -
  • Expanded [10.2. Deleting Messages] with data on the new features in version 5.5, which allow both participants to remove any messages from one-on-one chats for both sides without a time limit.
  • -
-

March 24, 2021

- -

October 26, 2021

- -

Important changes made to this Privacy Policy will be notified to you via Telegram.

-

12. Questions and concerns

-

If you have any questions about privacy and our data policies, please contact our @GDPRbot. Use the /access command to learn how to get a copy of your Telegram data and use the /contact command to leave a request, which we will answer at the earliest opportunity.

-

Telegram is an open source project. You can examine more information on our:

- -
-

This policy has been expanded on August 14, 2018 to add information required by the EU data protection law.

-
- -
- -
-
-
- - - - - - - - - diff --git a/data/telegram.org/support.html b/data/telegram.org/support.html deleted file mode 100644 index 6c587013fd..0000000000 --- a/data/telegram.org/support.html +++ /dev/null @@ -1,141 +0,0 @@ - - - - - Telegram support - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
-
-

Support

- -
-
- - -
-
- - -
-
- - -
-
- -
-
- -
-
-
-
- -
-
-
- - - - - - - diff --git a/data/telegram.org/teststore.html b/data/telegram.org/teststore.html deleted file mode 100644 index 710beff8d0..0000000000 --- a/data/telegram.org/teststore.html +++ /dev/null @@ -1,283 +0,0 @@ - - - - - Telegram Messenger - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- - - - - - -
- -

Why Telegram?

- -
-
-
-
-

Simple

-
Telegram is so simple you already know how to use it.
-
-
- -
-
-
-

Private

-
Telegram messages are heavily encrypted and can self-destruct.
-
-
- -
-
-
-

Synced

-
Telegram lets you access your chats from multiple devices.
-
-
- -
-
-
-

Fast

-
Telegram delivers messages faster than any other application.
-
-
- -
-
-
-

Powerful

-
Telegram has no limits on the size of your media and chats.
-
-
- -
-
-
-

Open

-
Telegram has an open API and source code free for everyone.
-
-
- -
-
-
-

Secure

-
Telegram keeps your messages safe from hacker attacks.
-
-
- -
-
-
-

Social

-
Telegram groups can hold up to 200,000 members.
-
-
- -
-
-
-

Expressive

-
Telegram lets you completely customize your messenger.
-
-
-
-
- -
- -
-
-
- - - - - - - - diff --git a/data/telegram.org/tour/channels.html b/data/telegram.org/tour/channels.html deleted file mode 100644 index a03cc25dcd..0000000000 --- a/data/telegram.org/tour/channels.html +++ /dev/null @@ -1,294 +0,0 @@ - - - - - Telegram Channels - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Telegram Channels

- -
- -
- -

Channels are a tool for broadcasting your public messages to large audiences. They offer a unique opportunity to reach people directly, sending a notification to their phones with each post.

-

Telegram Channels can have an unlimited amount of subscribers, and only admins have the right to post. Unlike Telegram Groups, channels show the name and photo of the channel next to messages – instead of the person who posted them.

-
- -
- -

Media organizations and public figures use channels to stay in touch with their readers, voters and fans. For some real-life examples, check out @Bloomberg, the Coronavirus Info channel, or join the official @Telegram channel covering our updates.

-

To create your own channel, open the “New Message” menu on Telegram and choose “New Channel”. Newly created channels start as private – but you can edit their profile to make them public.

-

The contents of public channels can be seen on the Web without a Telegram account and are indexed by search engines. For example, try t.me/s/FinancialTimes.

-

Autoplaying Videos and Rich Media

-

Channels aren't just for text messages and links – Telegram supports a wide range of content types, from autoplaying videos to animated stickers, polls and beyond.

-

Videos will start playing automatically with no sound. Pressing the volume buttons on the device unmutes the video, tapping on it launches the video from the beginning in full screen mode.

-
- TITLE -
- -

Several photos sent together will form an album with a beautiful layout – and only result in one notification to your subscribers for the whole batch.

-
- TITLE -
- -

You can send large files of any type and uncompressed images in full resolution – useful for content like infographics.

-
- TITLE -
- -

Podcasts also get special treatment. Telegram apps remember your last position when resuming playback of long audio files. Users who are in a hurry can listen to them at 2x speed:

-
- Screenshot showing the location of the 2x playback button for long audio files. -
- - -

Quick Sharing

-

Each post in a channel has a handy Share Button next to it, making it easy for your subscribers to forward things to others – or save them in their Saved Messages.

-
- TITLE -
- -

The Quick Share menu also shows a direct link to your post. Following such links inside Telegram opens the channel and highlights the message. If the user doesn't have Telegram, they will see a web page with an embedded post, like this: t.me/corona/16.

-

Powerful Polls

-

You can use polls to judge public opinion, make decisions and help your audience connect with you.

-
- A poll that shows who voted for which option -
- -

Quiz-Style Polls

-

To make things more fun – or add extra educational value to your posts 🧐 – use quiz-style polls that have one correct answer.

-
- TITLE -
- -

Discussion Groups

-

If you'd like to know what people think about the posts they view, you can set up a discussion group for your channel. New posts from the channel will be automatically forwarded to the group and pinned there.

-

Subscribers will see a comment button for each post in the channel. Comments show up in a thread of their own and also land in the discussion group to keep everyone in the loop and make it easier for admins to keep the conversation civil.

-
- -
- -

View Counters

-

Each post in a channel has a view counter. Views from forwarded copies of the messages are included in the total count.

-
- TITLE -
- -

Detailed Statistics

-

Advanced statistics are available for channels with more than 500 subscribers. You can view beautifully-detailed graphs about its growth and the performance of its posts.

-
- -
- -

You can track how many users join, leave and mute your channel, what languages they speak, how they interact with your posts, and how they found your channel – from Telegram search, by following a link, etc.

-

Scheduled and Silent Messages

-

You can plan your posts ahead and let them go live automatically at a specified time. For late night or non-urgent updates, you can send silent messages that will result in a notification with no sound for your subscribers.

-

Hold the “Send” button for extra sending options:

-
- TITLE -
- -

Pinned Messages

-

You can pin a message for extra visibility.

-
- TITLE -
- -

Hashtags

-

Telegram supports hashtags – tapping on a hashtag in a message will show a search interface with all other tagged posts in the channel. This is useful for adding a layer of navigation for your channel and improving visibility of your older posts.

-
- TITLE -
- -

Subscriber Privacy

-

The subscriber list is only visible to the channel owner and admins. Subscribers cannot see who else has signed up – nor can they see which accounts are managing the channel.

-

Extra Admins

-

You can appoint additional admins to help you manage the channel and define their role with granular precision. Choose who will be able to add new subscribers, manage messages, edit channel info, or even add new admins.

-

Admin Signatures

-

There are times when it's important to know who posted a certain message. For that, you can enable signatures in Channel Info. New messages will be signed with the posting admin's chosen screen name but will not link to their profile.

-
- TITLE -
- -

Embedded Messages

-

Messages from public channels can be easily embedded in any web page using Telegram Widgets.

-

- -

-
- - -

Editing Messages

-

Made a typo? Missed a word? Itching to add something? You can easily edit your messages in channels, regardless of how long ago they were posted. Tap the message (double tap or long tap on iOS), then press 'Edit'.

-

Deleting Messages

-

If you'd like to do a bit of timeline maintenance, you can delete any message at any time, for everyone. Deleted messages will vanish from the feed, for both new and old subscribers.

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/tour/groups.html b/data/telegram.org/tour/groups.html deleted file mode 100644 index 0146fa91b5..0000000000 --- a/data/telegram.org/tour/groups.html +++ /dev/null @@ -1,266 +0,0 @@ - - - - - Group Chats on Telegram - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Group Chats on Telegram

- -
-
- -
-

Telegram groups are a powerful tool for building communities and can support up to 200,000 members each.

-
-

Friends and families use groups to share photos and plans, teams and businesses to coordinate their work, massive ICOs to answer questions and keep in touch with their investors. Telegram has many features that make communication in groups easy no matter their size or purpose.

-

Replies

-

To reply to a specific message in a group chat, simply swipe left on it, type your text and hit ‘Send’. If you tap on the quote in a message that is a reply, the app scrolls up to the original message – and shows an arrow button to go back to the previous location. This makes navigating conversations in groups easy even if you've been away for a while.

-

The person you replied to will be notified about your message even if they muted the group chat — their notification settings for you personally apply in this case.

-

Mentions

-

If you want several people within a group chat to get instantly involved in the conversation, you may mention them in a message. They will be notified about your message, even if they muted the group chat — unless they've muted you personally, of course!

-

Reply/Mention alerts

-

In busy groups, you can get new mentions or replies many times during a day – and it’s important not to miss those messages. So whenever this happens, you’ll notice straight away by the ‘@’ badge in the chat list:

-
-
- -
-
- -

When you have new replies/mentions in a group, you can instantly reach them by tapping the new ‘@’ button when inside the chat. This button will disappear once you’ve read all the relevant messages (you can also use a long tap on the button to quickly mark them as read).

-

Supersize that

-

Groups are ideal for sharing stuff with friends and family or collaboration in small teams. But they can also host very large communities – in fact, up to to 200,000 members can join any group. We have plenty of admin tools to help admins keep the peace in these virtual cities.

-
-

Hint: If you're doing something massively popular, consider creating a channel. Channels are a tool for broadcasting public messages to large audiences, and can have an unlimited number of subscribers.

-
-

Pinned Messages

-

Group admins can inform all members about important news using pinned messages that are displayed at the top of the chat screen. All members will get a notification — even if they muted ordinary messages from the group.

-
- -

A pinned message

-
- -

Groups admins can always edit pinned messages. This means your pinned message can contain an up to date list of links to important messages or other channels and groups.

- - -

Invite Links

-

It's easy to move your existing group chats to Telegram without any hassle. Simply send your friends an invite link. As soon as they get Telegram, they can instantly join your Telegram group just by following that link.

-

To get the link, first create a group on Telegram, then head to the ‘Add participant…’ section and tap ‘Invite to Group via Link’.

-
- - - -
-
- -

Public groups

-

If you want a friendlier-looking link, groups can become public and get a short link, like t.me/publictestgroup. This way, anybody can view the group's entire chat history and join to post messages.

-
- -

A public group

-
- -

Message links

-

You can copy links to individual messages inside public groups. Anyone will be able to see them by opening their t.me link – no Telegram account required. Tweet with confidence!

-

Better With Bots

-

Bots further extend the potential power of groups, making anything possible – from automated moderation to games, payments and beyond.

-

Admin Tools

-

To help maintain order in your community, you can add admins with specific sets of privileges. Choose who among your trusted admins will be able to add new users, manage messages, block members, edit group info, or even add new admins.

-
- -

Admin rights

-
- -

Partial Bans

-

Admins who don’t want to completely ban members from their groups can partially restrict their rights in order to stop behavior that's causing problems. You can put nasty users into read-only mode or maybe stop them from sending stickers or media for a certain period of time. You can do all of this with absolute precision:

-
- -

Partial bans

-
- -

Even robots can get in on the fun. With Bot API version 3.1, you can use admin bots to automatically impose temporary or permanent bans based on member actions. Check out the docs here to start building your robotic police force today.

-

Recent Admin Actions

-

When multiple admins are working with one group, it’s easy to get confused about which admin did what and when (or which admin bot has gone Skynet on your members). That’s why we've added a “Recent Actions” section to the admins page. This section stores a log of all service actions taken in the group in the last 48 hours and is visible to admins only.

-
-
- -

Recent admin actions

-
-
- -

Precise filters

-
- -

Recent actions in groups also show messages that were deleted in the last 48 hours and the original versions of edited messages for the same period, so nasty behavior like self-deleted spam will no longer help anyone escape the admins’ wrath.

-

Stickers of the Group

-

Large groups with 100 members and more can choose an official sticker set for all the members of the group to see and use while they're chatting in the group — without the need of adding it to their panels.

-
- -

Group Stickers

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/tour/quizbot.html b/data/telegram.org/tour/quizbot.html deleted file mode 100644 index 6d20bac47b..0000000000 --- a/data/telegram.org/tour/quizbot.html +++ /dev/null @@ -1,215 +0,0 @@ - - - - - Quizzes - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Quizzes

- -
- -
- -
-

Visit Quiz Directory to try thousands of Quizzes created by participants of the 2020 Quiz Contest.

-
-

Telegram supports powerful polls for groups and channels which can be used for everything from deciding where to have lunch to organizing public service exams or leaderless protests.

-

Quiz-style polls are a special kind of poll that has one correct answer and an optional explanation which makes them ideal for educational purposes.

-
- -
- -

Quiz Bot

-

With the help of Quiz Bot you can create multi-question quizzes and share them with others. The bot lets you add text or media before questions to help create exam-style prompts with graphs and tables – or Know Your Meme tests.

-
- TITLE -
- -

You can set up a time limit for each question. The bot will keep tabs on how many questions users got right and how much time it took them to complete the quiz. It also keeps a global leaderboard for each quiz you create.

-

Creating a Quiz

-

Creating a quiz is very easy, just open @quizbot on Telegram, press 'START' and follow the prompts. If you're having any difficulty, please take a look at our Step-By-Step Instructions.

-

Sharing your Quiz

-

Once your quiz is ready, you can share it to a group or channel – or invite users to answer questions privately, in a chat with the bot. To see how this works, try our demo quiz: Who is Who in the 'Great Minds' sticker pack.

-
-

You can browse thousands of quizzes created during the 2020 Quiz Contest on quiz.directory.

-
-

Making your own Quiz Bot

-

If you are a developer, you are welcome to use the Telegram Bot API to create your own bot that supports polls and quizzes.

-
-

Creating a Quiz, Step-By-Step

-

Creating a quiz is very easy, just open @quizbot on Telegram, press 'START' and follow the prompts.

-

1. Name and description. First you will give your quiz a name and an optional description – for educational tests, it's best to use the subject matter, like Organic Chemistry I or British Royal History. The description could contain information or instructions like “you will need a graphing calculator for this test”.

-

2. Pre-question text or media. Now comes the time to create the quiz's questions. Tapping the 'Create a question' button opens the template to create your first question. However, if you would like text or media to appear before a question, send that first, before tapping 'Create a question'.

-

3. Questions. Once in the new-question interface, simply fill out the fields for what the question is asking, as well as its possible answers. Select the right answer by tapping on it, which will mark it with a green check.

-

4. Explanations. If you want to participate in our contest, you should add an explanation to each of your questions. Explanations will appear after users choose an answer. They can be used to give more information, clarify common errors, and support full text formatting, including hyperlinks. Once you are finished, tap 'Send' to add the question to your test. Repeat the question-making process until you've added all your quiz's questions, then send /done in the chat.

-

5. Timer. Next, the bot will ask you to choose how long users will have to answer each question. For questions that don't require any calculations, 10 or 15 seconds is usually enough. But for something like math, longer timers like 3 to 5 minutes are best. You can always change this setting later on, so don't worry.

-

6. Shuffle questions or answer options. The bot will then ask whether you'd like to shuffle question and answer options – meaning the questions will come up in a random order, and the answers for individual questions will be in a random order as well. It's normally a good idea to say 'Yes' here, so students can retake the quiz for practice without simply memorizing the order. However, if you have “all of the above” style answers, or questions that work best if presented in a specific order, select 'No'. Again, this setting can be changed in the future if needed.

-

7. Submitting your quiz to the contest. The bot will ask if you would like to submit your quiz to the contest. If you choose yes, it will ask a couple of additional questions to confirm your submission.

-

8. Testing or sharing your quiz. Your quiz is complete! From here, you'll see an overview of your new quiz, showing the number of questions and its settings. You can 'Start this quiz’, which will do so in a private chat with QuizBot, start it in a group, or forward the quiz to someone via 'Share quiz'. To copy the unique link to your quiz, press and hold 'Start quiz in a group'.

-

9. Editing your quizzes. Tapping 'Edit quiz' will allow you to alter any of the quiz's questions or settings, including its title and description. From 'Edit questions' you can add pre-question text or media, replace the question with improved answers, or even add additional questions. To select an individual question to edit, tap its /view link from the panel.

-

10. Quiz stats. Lastly, you can view Quiz Stats. This shows how many people have taken the quiz, along with who answered the questions most correctly and quickest. You are now the quiz master, ready to put your subjects to the test.

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/tour/screenshots.html b/data/telegram.org/tour/screenshots.html deleted file mode 100644 index 4029c0ce4f..0000000000 --- a/data/telegram.org/tour/screenshots.html +++ /dev/null @@ -1,217 +0,0 @@ - - - - - Telegram Logos and App Screenshots - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Telegram Logos and App Screenshots

- -
- -
- -

Logos

-

Please feel free to use these Telegram logos for article illustrations, graphs, “forward to Telegram” buttons, etc. Just make sure people understand you're not representing Telegram officially.

-
-

Download Telegram Logos

-
-

Screenshots

-

All Telegram screenshots on this page are dedicated to the public domain, see CC0 1.0 Universal. Click on images to download hi-res versions.

-
-
- List of chats, main screen of the Telegram app -

List of chats

-
-
- A group chat with 2,500 members and a poll -

Group chat with poll

-
- -
-
- A secret chat with disappearing media as viewed on a device with dark mode enabled -

Secret chat using a dark theme

-
-
- A private chat with a user, open sticker panel -

Private chat with stickers

-
- -
-
- Shared media section, accessible from a contact's profile page -

Shared media section from a chat

-
-
- Group chat, dowloading a large file in progress -

Group chat with a downloading file

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/verify.html b/data/telegram.org/verify.html deleted file mode 100644 index 02fc386f61..0000000000 --- a/data/telegram.org/verify.html +++ /dev/null @@ -1,151 +0,0 @@ - - - - - Page Verification Guidelines - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
-
-
-

Page Verification Guidelines

- -
- Verification -
- -

The Telegram team generally verifies active official channels, bots or public groups that have verified accounts on at least two of these services:

-
    -
  1. TikTok
  2. -
  3. Instagram
  4. -
  5. Facebook
  6. -
  7. YouTube
  8. -
  9. Twitter
  10. -
  11. VK
  12. -
  13. Snapchat
  14. -
-

Please add a link to your Telegram channel to your profiles on these services — so that we can confirm that they indeed belong to you. Once this is done, please contact our @VerifyBot for verification.

-

What if I don't have a verified account on two of these services?

-

If you have an undisputed page on Wikipedia, that satisfies Wikipedia's Notability Guidelines – and that page lists a link to your channel, bot or public group on Telegram – it can be counted as one of the missing verified accounts.

-

In the case of organizations, a link to the Telegram channel from the official website of the organization may also be taken into account. The bot will offer to submit additional data and comments after checking the social media links.

-
-

If you're using a Wikipedia or Official Website link instead of one of the social media accounts, please make sure that they include a link to the channel, group or bot you want to verify on Telegram.

-
-

Can my user account be verified?

-

Sorry, Telegram doesn’t verify user accounts at the moment. Verification is only available for big and active official channels, groups and bots.

-

Do I need verification?

-

Note that verification doesn't give any additional abilities in Telegram - it is simply one of the ways to demonstrate that your channel, group or bot is official. A link to Telegram on your official site or other official accounts elsewhere can achieve a similar result.

-

How do I change the name or short link after verification?

-

A verified channel, group or bot can't change its name or short link (t.me/…). If changes are necessary, you can remove verification status first. Contact @VerifyBot and send /unverify. You can then reobtain verification using the bot.

-
- -
-
- -
-
-
- - - - - - -