From 5c93284224568c0a6afbf6b0e5eb3c6b5a9f4f2b Mon Sep 17 00:00:00 2001 From: GitHub Action Date: Sun, 14 Nov 2021 11:05:52 +0000 Subject: [PATCH] Update content of files --- data/core.telegram.org/api/datacenter.html | 152 -- data/core.telegram.org/api/pattern.html | 122 -- data/core.telegram.org/bots/faq.html | 243 --- .../bots/samples/hellobot.html | 287 --- .../constructor/account.authorizations | 147 -- .../constructor/account.wallPapersNotModified | 132 -- .../constructor/account.webAuthorizations | 152 -- .../constructor/auth.codeTypeCall | 132 -- .../constructor/auth.exportedAuthorization | 152 -- .../constructor/auth.loginTokenMigrateTo | 152 -- .../constructor/botCommandScopeDefault.html | 132 -- .../constructor/botCommandScopePeer.html | 147 -- .../constructor/botInlineMessageMediaGeo.html | 175 -- .../constructor/botInlineMessageText.html | 170 -- .../constructor/cdnConfig.html | 149 -- .../constructor/cdnPublicKey.html | 154 -- ...nnelAdminLogEventActionChangeLocation.html | 152 -- ...elAdminLogEventActionParticipantLeave.html | 132 -- ...hannelAdminLogEventActionUpdatePinned.html | 147 -- .../constructor/channelMessagesFilter.html | 157 -- .../constructor/chatInvitePeek.html | 152 -- .../constructor/contacts.found | 162 -- .../constructor/contacts.resolvedPeer | 157 -- .../constructor/contacts.topPeers | 157 -- .../decryptedMessageMediaGeoPoint.html | 153 -- .../constructor/dialogFilterSuggested.html | 155 -- .../constructor/draftMessage.html | 177 -- .../constructor/draftMessageEmpty.html | 152 -- .../constructor/emojiKeywordsDifference.html | 162 -- .../constructor/emojiLanguage.html | 147 -- data/core.telegram.org/constructor/error.html | 152 -- .../constructor/fileHash.html | 171 -- .../core.telegram.org/constructor/folder.html | 177 -- .../constructor/geoPointEmpty.html | 132 -- .../constructor/help.deepLinkInfo | 165 -- .../constructor/help.deepLinkInfoEmpty | 132 -- .../constructor/help.passportConfig | 156 -- .../constructor/help.support | 152 -- .../constructor/highScore.html | 157 -- .../constructor/importedContact.html | 155 -- .../inputBotInlineMessageGame.html | 152 -- .../inputBotInlineMessageMediaAuto.html | 165 -- .../inputBotInlineMessageMediaContact.html | 172 -- .../inputBotInlineMessageMediaGeo.html | 175 -- .../inputBotInlineMessageMediaVenue.html | 182 -- .../inputBotInlineMessageText.html | 170 -- .../inputDocumentFileLocation.html | 167 -- .../inputEncryptedFileUploaded.html | 162 -- .../constructor/inputGameShortName.html | 152 -- .../constructor/inputGeoPoint.html | 162 -- .../constructor/inputGeoPointEmpty.html | 132 -- .../inputMediaDocumentExternal.html | 157 -- .../constructor/inputMediaUploadedPhoto.html | 165 -- .../inputMessagesFilterPhoneCalls.html | 152 -- .../inputMessagesFilterPhotos.html | 132 -- .../inputMessagesFilterPinned.html | 132 -- .../constructor/inputPeerEmpty.html | 132 -- .../constructor/inputPhoneContact.html | 166 -- .../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 -- .../constructor/inputStickerSetDice.html | 150 -- .../constructor/inputStickeredMediaPhoto.html | 147 -- .../constructor/inputThemeSlug.html | 147 -- .../constructor/inputUserFromMessage.html | 160 -- .../constructor/inputUserSelf.html | 132 -- .../constructor/inputWebDocument.html | 165 -- .../inputWebFileGeoPointLocation.html | 172 -- .../constructor/jsonBool.html | 147 -- .../constructor/keyboardButtonGame.html | 147 -- .../messageActionGeoProximityReached.html | 160 -- .../constructor/messageActionGroupCall.html | 157 -- .../messageActionSetMessagesTTL.html | 147 -- .../constructor/messageReplies.html | 189 -- .../constructor/messageViews.html | 165 -- .../constructor/messages.botCallbackAnswer | 177 -- .../constructor/messages.chatInviteImporters | 157 -- .../constructor/messages.dhConfigNotModified | 147 -- .../constructor/messages.dialogsSlice | 167 -- .../messages.exportedChatInviteReplaced | 157 -- .../constructor/messages.messagesNotModified | 147 -- .../constructor/messages.savedGifsNotModified | 132 -- .../constructor/messages.votesList | 170 -- .../constructor/nearestDc.html | 157 -- .../constructor/notifyPeer.html | 147 -- data/core.telegram.org/constructor/null.html | 132 -- .../constructor/pageBlockBlockquote.html | 152 -- .../constructor/pageBlockParagraph.html | 147 -- .../constructor/pageBlockUnsupported.html | 132 -- .../constructor/pageListOrderedItemText.html | 152 -- .../constructor/pageRelatedArticle.html | 182 -- .../constructor/pageTableRow.html | 147 -- .../constructor/passwordKdfAlgoUnknown.html | 132 -- .../constructor/paymentCharge.html | 152 -- .../constructor/paymentRequestedInfo.html | 167 -- .../constructor/phone.joinAsPeers | 157 -- .../phoneCallDiscardReasonMissed.html | 132 -- .../constructor/photoSizeEmpty.html | 150 -- .../constructor/photoSizeProgressive.html | 167 -- .../constructor/recentMeUrlUnknown.html | 147 -- .../constructor/replyKeyboardMarkup.html | 172 -- .../constructor/restrictionReason.html | 158 -- .../constructor/securePlainPhone.html | 150 -- .../secureValueErrorTranslationFile.html | 178 -- .../secureValueErrorTranslationFiles.html | 178 -- .../secureValueTypePassportRegistration.html | 134 -- .../secureValueTypePersonalDetails.html | 132 -- .../sendMessageUploadAudioAction.html | 147 -- .../sendMessageUploadPhotoAction.html | 147 -- .../constructor/statsGraph.html | 160 -- .../constructor/statsURL.html | 147 -- .../constructor/storage.fileGif | 132 -- .../constructor/storage.fileJpeg | 132 -- .../constructor/storage.fileMov | 132 -- .../constructor/storage.fileMp3 | 132 -- .../constructor/topPeer.html | 155 -- .../constructor/updateChannel.html | 147 -- .../updateChannelMessageViews.html | 157 -- .../constructor/updateChannelTooLong.html | 161 -- .../updateChatParticipantAdmin.html | 165 -- .../constructor/updateDialogUnreadMark.html | 157 -- .../constructor/updateDraftMessage.html | 155 -- .../constructor/updateEncryption.html | 152 -- .../constructor/updatePinnedMessages.html | 175 -- .../constructor/updateReadHistoryInbox.html | 182 -- .../constructor/updateRecentStickers.html | 132 -- .../constructor/updateStickerSetsOrder.html | 157 -- .../constructor/updateUserPhoto.html | 165 -- .../updates.channelDifferenceEmpty | 165 -- .../constructor/urlAuthResultRequest.html | 165 -- .../constructor/userStatusOnline.html | 147 -- .../method/account.getNotifySettings | 166 -- .../core.telegram.org/method/account.getTheme | 181 -- .../method/account.getWebAuthorizations | 136 -- .../method/account.saveTheme | 155 -- .../method/account.updatePasswordSettings | 207 -- .../method/account.updateProfile | 187 -- .../method/auth.exportAuthorization | 167 -- .../method/bots.answerWebhookJSONQuery | 178 -- .../method/channels.editLocation | 180 -- .../method/channels.editPhoto | 221 -- .../method/channels.getParticipant | 205 -- .../method/channels.toggleSignatures | 187 -- .../method/contacts.addContact | 217 -- .../method/contacts.blockFromReplies | 178 -- .../method/contacts.resolveUsername | 182 -- .../method/help.acceptTermsOfService | 150 -- .../method/help.dismissSuggestion | 160 -- .../method/help.getCdnConfig | 154 -- .../method/help.getDeepLinkInfo | 150 -- .../method/help.getNearestDc | 134 -- .../method/help.getProxyData | 132 -- .../method/help.hidePromoData | 150 -- .../method/invokeWithMessagesRange.html | 154 -- .../method/messages.acceptUrlAuth | 179 -- .../method/messages.getAllDrafts | 143 -- .../method/messages.getAllStickers | 153 -- .../method/messages.getEmojiKeywords | 149 -- .../method/messages.getMessages | 153 -- .../method/messages.readFeaturedStickers | 150 -- .../method/messages.readMessageContents | 149 -- .../method/messages.reportSpam | 180 -- .../method/messages.setBotCallbackAnswer | 203 -- .../method/messages.setHistoryTTL | 182 -- .../method/messages.unpinAllMessages | 153 -- .../method/payments.getBankCardData | 166 -- .../method/phone.editGroupCallParticipant | 225 --- .../method/phone.getGroupParticipants | 174 -- .../method/phone.inviteToGroupCall | 177 -- .../method/stats.getBroadcastStats | 194 -- .../method/stickers.createStickerSet | 282 --- .../core.telegram.org/method/updates.getState | 135 -- data/core.telegram.org/schema.html | 1800 ----------------- data/core.telegram.org/type/CdnConfig.html | 164 -- data/core.telegram.org/type/CdnPublicKey.html | 145 -- data/core.telegram.org/type/ChatTheme.html | 143 -- data/core.telegram.org/type/DraftMessage.html | 151 -- .../core.telegram.org/type/EmojiLanguage.html | 143 -- data/core.telegram.org/type/Error.html | 143 -- data/core.telegram.org/type/FileHash.html | 143 -- data/core.telegram.org/type/HighScore.html | 143 -- .../type/InputBotInlineMessage.html | 173 -- .../type/InputPrivacyKey.html | 178 -- .../type/InputThemeSettings.html | 143 -- .../type/InputWebDocument.html | 143 -- .../type/MessageReplies.html | 146 -- .../type/MessageUserVote.html | 153 -- data/core.telegram.org/type/NearestDc.html | 162 -- data/core.telegram.org/type/Null.html | 143 -- .../core.telegram.org/type/PaymentCharge.html | 143 -- .../type/PeerNotifySettings.html | 162 -- .../type/PollAnswerVoters.html | 143 -- .../type/RestrictionReason.html | 143 -- .../type/StatsPercentValue.html | 143 -- data/core.telegram.org/type/StatsURL.html | 143 -- .../type/account.AuthorizationForm | 162 -- .../type/account.WebAuthorizations | 162 -- .../type/auth.ExportedAuthorization | 162 -- .../type/contacts.ResolvedPeer | 162 -- data/core.telegram.org/type/help.DeepLinkInfo | 167 -- data/core.telegram.org/type/help.ProxyData | 130 -- data/core.telegram.org/type/long.html | 118 -- .../type/messages.ArchivedStickers | 162 -- data/core.telegram.org/type/messages.ChatFull | 168 -- .../type/messages.SponsoredMessages | 162 -- .../type/messages.StatedMessages | 128 -- .../core.telegram.org/widgets/discussion.html | 226 --- .../corefork.telegram.org/api/bots/games.html | 171 -- data/corefork.telegram.org/api/files.html | 568 ------ data/corefork.telegram.org/api/passport.html | 674 ------ data/corefork.telegram.org/api/payments.html | 366 ---- .../corefork.telegram.org/api/web-events.html | 177 -- data/corefork.telegram.org/bots/webhooks.html | 827 -------- .../constructor/account.authorizations | 147 -- .../constructor/account.passwordSettings | 161 -- .../constructor/account.privacyRules | 157 -- .../account.resetPasswordRequestedWait | 147 -- .../constructor/account.themes | 155 -- .../constructor/auth.exportedAuthorization | 152 -- .../constructor/auth.loginTokenMigrateTo | 152 -- .../constructor/auth.sentAppCode | 163 -- ...channelAdminLogEventActionChangeAbout.html | 152 -- ...nnelAdminLogEventActionChangeLocation.html | 152 -- ...minLogEventActionExportedInviteDelete.html | 147 -- ...lAdminLogEventActionParticipantVolume.html | 147 -- .../constructor/channelLocationEmpty.html | 132 -- .../channelMessagesFilterEmpty.html | 132 -- .../constructor/channelParticipant.html | 152 -- .../constructor/channelParticipantsBots.html | 132 -- .../constructor/chatInvite.html | 190 -- .../constructor/config.html | 420 ---- .../constructor/contacts.topPeersDisabled | 132 -- .../constructor/dialog.html | 214 -- .../constructor/dialogFilter.html | 220 -- .../constructor/emojiKeywordsDifference.html | 162 -- .../constructor/emojiLanguage.html | 147 -- .../constructor/game.html | 182 -- .../constructor/groupCallDiscarded.html | 157 -- .../constructor/groupCallParticipant.html | 247 --- .../constructor/help.promoDataEmpty | 147 -- .../constructor/help.userInfoEmpty | 132 -- .../constructor/inlineQueryPeerTypePM.html | 132 -- .../constructor/inputClientProxy.html | 154 -- .../constructor/inputDocumentEmpty.html | 132 -- .../constructor/inputMediaPhoto.html | 157 -- .../inputMessagesFilterDocument.html | 132 -- .../constructor/inputPaymentCredentials.html | 157 -- .../inputPaymentCredentialsSaved.html | 152 -- .../constructor/inputPhotoEmpty.html | 132 -- .../inputPhotoLegacyFileLocation.html | 172 -- .../inputReportReasonCopyright.html | 132 -- .../inputReportReasonViolence.html | 132 -- .../constructor/inputStickerSetDice.html | 150 -- .../constructor/inputThemeSlug.html | 147 -- .../constructor/inputUser.html | 155 -- .../constructor/inputWebDocument.html | 165 -- .../constructor/messageActionPinMessage.html | 132 -- .../messageActionSecureValuesSentMe.html | 154 -- .../constructor/messageFwdHeader.html | 195 -- .../constructor/messageService.html | 212 -- .../constructor/messages.allStickers | 155 -- .../constructor/messages.dialogs | 162 -- .../constructor/messages.foundStickerSets | 155 -- .../messages.recentStickersNotModified | 132 -- .../constructor/messages.sentMessageLink | 167 -- .../constructor/messages.sponsoredMessages | 157 -- .../constructor/null.html | 132 -- .../constructor/pageBlockAuthorDate.html | 152 -- .../pageListOrderedItemBlocks.html | 152 -- .../constructor/pageTableRow.html | 147 -- .../constructor/paymentCharge.html | 152 -- .../payments.ValidatedRequestedInfo | 145 -- .../constructor/payments.paymentResult | 147 -- .../payments.paymentVerificationNeeded | 147 -- .../constructor/peerBlocked.html | 152 -- .../constructor/pollAnswerVoters.html | 170 -- .../privacyValueAllowChatParticipants.html | 147 -- .../constructor/recentMeUrlStickerSet.html | 152 -- .../constructor/replyKeyboardForceReply.html | 162 -- .../constructor/secureData.html | 160 -- .../constructor/secureFileEmpty.html | 132 -- .../constructor/secureRequiredType.html | 167 -- .../constructor/secureRequiredTypeOneOf.html | 147 -- .../constructor/secureValueErrorData.html | 175 -- .../secureValueTypeTemporaryRegistration.html | 132 -- .../constructor/sendMessageCancelAction.html | 132 -- .../sendMessageUploadAudioAction.html | 147 -- .../sendMessageUploadPhotoAction.html | 147 -- .../constructor/statsGraphError.html | 150 -- .../constructor/storage.fileGif | 132 -- .../constructor/storage.filePng | 132 -- .../constructor/storage.fileWebp | 132 -- .../constructor/textItalic.html | 147 -- .../constructor/textMarked.html | 147 -- .../constructor/textSubscript.html | 147 -- .../constructor/themeSettings.html | 177 -- .../constructor/updateBotCallbackQuery.html | 182 -- .../constructor/updateBotInlineQuery.html | 177 -- .../updateEncryptedChatTyping.html | 147 -- .../constructor/updateLoginToken.html | 132 -- .../constructor/updateNewMessage.html | 157 -- .../updatePhoneCallSignalingData.html | 152 -- .../constructor/updateSavedGifs.html | 132 -- .../constructor/updateStickerSetsOrder.html | 157 -- .../constructor/urlAuthResultAccepted.html | 150 -- .../constructor/userProfilePhotoEmpty.html | 132 -- .../constructor/webPageEmpty.html | 147 -- .../method/account.confirmPasswordEmail | 175 -- .../method/account.getAccountTTL | 134 -- .../method/account.getAuthorizationForm | 176 -- .../account.getContactSignUpNotification | 135 -- .../method/account.getSecureValue | 151 -- .../method/account.installWallPaper | 172 -- .../account.setContactSignUpNotification | 150 -- .../method/auth.acceptLoginToken | 171 -- .../method/auth.bindTempAuthKey | 252 --- .../method/auth.checkPhone | 176 -- .../method/auth.sendInvites | 157 -- .../method/channels.editPhoto | 221 -- .../method/channels.getFullChannel | 187 -- .../method/channels.togglePreHistoryHidden | 202 -- .../method/help.getDeepLinkInfo | 150 -- .../method/help.getTermsOfServiceUpdate | 135 -- .../method/messages.acceptUrlAuth | 179 -- .../method/messages.deleteHistory | 206 -- .../method/messages.editChatAbout | 216 -- .../method/messages.getAttachedStickers | 148 -- .../method/messages.getChats | 173 -- .../method/messages.getExportedChatInvite | 155 -- .../method/messages.getGameHighScores | 187 -- .../method/messages.getHistory | 232 --- .../method/messages.getOnlines | 171 -- .../method/messages.getPinnedDialogs | 169 -- .../method/messages.getPollResults | 177 -- .../method/messages.getSavedGifs | 153 -- .../method/messages.initHistoryImport | 191 -- .../method/messages.readMessageContents | 149 -- .../method/messages.saveDraft | 202 -- .../method/messages.saveGif | 172 -- .../method/messages.search | 291 --- .../method/messages.searchGlobal | 226 --- .../method/messages.setInlineBotResults | 358 ---- .../method/messages.toggleStickerSets | 170 -- .../method/messages.uploadEncryptedFile | 155 -- .../method/payments.getBankCardData | 166 -- .../method/phone.joinGroupCall | 202 -- .../method/phone.saveCallDebug | 177 -- .../method/phone.sendSignalingData | 155 -- .../method/photos.updateProfilePhoto | 196 -- .../method/stats.getMessageStats | 189 -- .../method/stickers.removeStickerFromSet | 172 -- .../method/updates.getState | 135 -- .../method/upload.getCdnFile | 162 -- .../method/upload.getFileHashes | 171 -- .../mtproto/TL-combinators.html | 251 --- .../mtproto/description_v1.html | 205 -- .../type/BotCommand.html | 143 -- .../type/BotInlineResult.html | 148 -- .../type/ChannelAdminLogEventsFilter.html | 143 -- .../type/ChatParticipants.html | 148 -- .../corefork.telegram.org/type/ChatTheme.html | 143 -- .../type/GroupCallParticipant.html | 143 -- .../type/InputBotInlineResult.html | 158 -- .../type/InputDocument.html | 148 -- .../type/InputEncryptedFile.html | 158 -- .../type/InputNotifyPeer.html | 158 -- .../type/LangPackLanguage.html | 162 -- .../type/LangPackString.html | 153 -- .../type/MessageViews.html | 143 -- .../corefork.telegram.org/type/NearestDc.html | 162 -- .../corefork.telegram.org/type/PageBlock.html | 283 --- .../type/PeerSettings.html | 162 -- .../corefork.telegram.org/type/PhoneCall.html | 168 -- .../type/PollResults.html | 143 -- .../type/ReceivedNotifyMessage.html | 143 -- .../type/SecureSecretSettings.html | 145 -- .../type/SecureValue.html | 162 -- .../type/SecureValueError.html | 183 -- .../type/UrlAuthResult.html | 177 -- .../type/UserProfilePhoto.html | 148 -- data/corefork.telegram.org/type/WebPage.html | 177 -- .../type/account.ChatThemes | 167 -- .../type/auth.CheckedPhone | 128 -- .../type/auth.SentCodeType | 158 -- .../type/channels.ChannelParticipant | 162 -- .../type/help.PassportConfig | 169 -- .../corefork.telegram.org/type/help.PromoData | 167 -- .../corefork.telegram.org/type/help.ProxyData | 130 -- .../type/messages.AffectedFoundMessages | 162 -- .../type/messages.CheckedHistoryImportPeer | 165 -- .../type/messages.HighScores | 167 -- .../type/messages.SentMessage | 128 -- .../type/phone.GroupCall | 162 -- data/corefork.telegram.org/type/photos.Photo | 167 -- .../corefork.telegram.org/type/upload.CdnFile | 167 -- data/instantview.telegram.org/auth.html | 294 --- data/instantview.telegram.org/checklist.html | 624 ------ data/promote.telegram.org/basics.html | 204 -- data/telegram.org/api.html | 283 --- data/telegram.org/blog.html | 268 --- data/telegram.org/blog/400-million.html | 272 --- data/telegram.org/blog/6-years.html | 1355 ------------- .../blog/albums-saved-messages.html | 268 --- data/telegram.org/blog/bot-revolution.html | 279 --- data/telegram.org/blog/channels-2-0.html | 246 --- data/telegram.org/blog/desktop-1-0.html | 250 --- data/telegram.org/blog/edit.html | 245 --- data/telegram.org/blog/files-on-steroids.html | 240 --- data/telegram.org/blog/folders.html | 298 --- data/telegram.org/blog/group-video-calls.html | 264 --- data/telegram.org/blog/instant-view.html | 268 --- 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 ---- .../blog/new-profiles-people-nearby.html | 263 --- data/telegram.org/blog/now-you-see-me.html | 235 --- .../blog/permissions-groups-undo.html | 265 --- data/telegram.org/blog/polls.html | 230 --- .../blog/replies-mentions-stickers.html | 257 --- data/telegram.org/blog/search-and-media.html | 232 --- data/telegram.org/blog/share-preview.html | 269 --- data/telegram.org/blog/shared-links.html | 221 -- data/telegram.org/blog/supergroups5k.html | 232 --- data/telegram.org/blog/tdlib.html | 228 --- data/telegram.org/blog/telegraph.html | 238 --- data/telegram.org/blog/unsend-and-usage.html | 273 --- data/telegram.org/blog/video-calls.html | 234 --- data/telegram.org/blog/video-editor-gifs.html | 252 --- data/telegram.org/blog/voice-2-secret-3.html | 245 --- .../blog/voice-chats-on-steroids.html | 2 +- data/telegram.org/blog/voice-chats.html | 311 --- data/telegram.org/tos.html | 133 -- data/telegram.org/tour/screenshots.html | 217 -- 439 files changed, 1 insertion(+), 78823 deletions(-) delete mode 100644 data/core.telegram.org/api/datacenter.html delete mode 100644 data/core.telegram.org/api/pattern.html delete mode 100644 data/core.telegram.org/bots/faq.html delete mode 100644 data/core.telegram.org/bots/samples/hellobot.html delete mode 100644 data/core.telegram.org/constructor/account.authorizations 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/auth.codeTypeCall delete mode 100644 data/core.telegram.org/constructor/auth.exportedAuthorization delete mode 100644 data/core.telegram.org/constructor/auth.loginTokenMigrateTo 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/botInlineMessageMediaGeo.html delete mode 100644 data/core.telegram.org/constructor/botInlineMessageText.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/channelAdminLogEventActionChangeLocation.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionParticipantLeave.html delete mode 100644 data/core.telegram.org/constructor/channelAdminLogEventActionUpdatePinned.html delete mode 100644 data/core.telegram.org/constructor/channelMessagesFilter.html delete mode 100644 data/core.telegram.org/constructor/chatInvitePeek.html 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/decryptedMessageMediaGeoPoint.html delete mode 100644 data/core.telegram.org/constructor/dialogFilterSuggested.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/emojiKeywordsDifference.html delete mode 100644 data/core.telegram.org/constructor/emojiLanguage.html delete mode 100644 data/core.telegram.org/constructor/error.html delete mode 100644 data/core.telegram.org/constructor/fileHash.html delete mode 100644 data/core.telegram.org/constructor/folder.html delete mode 100644 data/core.telegram.org/constructor/geoPointEmpty.html 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.passportConfig delete mode 100644 data/core.telegram.org/constructor/help.support 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/inputBotInlineMessageGame.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/inputBotInlineMessageMediaVenue.html delete mode 100644 data/core.telegram.org/constructor/inputBotInlineMessageText.html delete mode 100644 data/core.telegram.org/constructor/inputDocumentFileLocation.html delete mode 100644 data/core.telegram.org/constructor/inputEncryptedFileUploaded.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/inputMediaDocumentExternal.html delete mode 100644 data/core.telegram.org/constructor/inputMediaUploadedPhoto.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterPhoneCalls.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterPhotos.html delete mode 100644 data/core.telegram.org/constructor/inputMessagesFilterPinned.html delete mode 100644 data/core.telegram.org/constructor/inputPeerEmpty.html delete mode 100644 data/core.telegram.org/constructor/inputPhoneContact.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/inputStickerSetDice.html delete mode 100644 data/core.telegram.org/constructor/inputStickeredMediaPhoto.html delete mode 100644 data/core.telegram.org/constructor/inputThemeSlug.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/inputWebDocument.html delete mode 100644 data/core.telegram.org/constructor/inputWebFileGeoPointLocation.html delete mode 100644 data/core.telegram.org/constructor/jsonBool.html delete mode 100644 data/core.telegram.org/constructor/keyboardButtonGame.html delete mode 100644 data/core.telegram.org/constructor/messageActionGeoProximityReached.html delete mode 100644 data/core.telegram.org/constructor/messageActionGroupCall.html delete mode 100644 data/core.telegram.org/constructor/messageActionSetMessagesTTL.html delete mode 100644 data/core.telegram.org/constructor/messageReplies.html delete mode 100644 data/core.telegram.org/constructor/messageViews.html delete mode 100644 data/core.telegram.org/constructor/messages.botCallbackAnswer delete mode 100644 data/core.telegram.org/constructor/messages.chatInviteImporters delete mode 100644 data/core.telegram.org/constructor/messages.dhConfigNotModified delete mode 100644 data/core.telegram.org/constructor/messages.dialogsSlice delete mode 100644 data/core.telegram.org/constructor/messages.exportedChatInviteReplaced delete mode 100644 data/core.telegram.org/constructor/messages.messagesNotModified delete mode 100644 data/core.telegram.org/constructor/messages.savedGifsNotModified 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/notifyPeer.html delete mode 100644 data/core.telegram.org/constructor/null.html delete mode 100644 data/core.telegram.org/constructor/pageBlockBlockquote.html delete mode 100644 data/core.telegram.org/constructor/pageBlockParagraph.html delete mode 100644 data/core.telegram.org/constructor/pageBlockUnsupported.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/pageTableRow.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/phone.joinAsPeers delete mode 100644 data/core.telegram.org/constructor/phoneCallDiscardReasonMissed.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/recentMeUrlUnknown.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/securePlainPhone.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/secureValueTypePassportRegistration.html delete mode 100644 data/core.telegram.org/constructor/secureValueTypePersonalDetails.html delete mode 100644 data/core.telegram.org/constructor/sendMessageUploadAudioAction.html delete mode 100644 data/core.telegram.org/constructor/sendMessageUploadPhotoAction.html delete mode 100644 data/core.telegram.org/constructor/statsGraph.html delete mode 100644 data/core.telegram.org/constructor/statsURL.html 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/topPeer.html delete mode 100644 data/core.telegram.org/constructor/updateChannel.html delete mode 100644 data/core.telegram.org/constructor/updateChannelMessageViews.html delete mode 100644 data/core.telegram.org/constructor/updateChannelTooLong.html delete mode 100644 data/core.telegram.org/constructor/updateChatParticipantAdmin.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/updateEncryption.html delete mode 100644 data/core.telegram.org/constructor/updatePinnedMessages.html delete mode 100644 data/core.telegram.org/constructor/updateReadHistoryInbox.html delete mode 100644 data/core.telegram.org/constructor/updateRecentStickers.html delete mode 100644 data/core.telegram.org/constructor/updateStickerSetsOrder.html delete mode 100644 data/core.telegram.org/constructor/updateUserPhoto.html delete mode 100644 data/core.telegram.org/constructor/updates.channelDifferenceEmpty delete mode 100644 data/core.telegram.org/constructor/urlAuthResultRequest.html delete mode 100644 data/core.telegram.org/constructor/userStatusOnline.html delete mode 100644 data/core.telegram.org/method/account.getNotifySettings delete mode 100644 data/core.telegram.org/method/account.getTheme delete mode 100644 data/core.telegram.org/method/account.getWebAuthorizations delete mode 100644 data/core.telegram.org/method/account.saveTheme 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/auth.exportAuthorization delete mode 100644 data/core.telegram.org/method/bots.answerWebhookJSONQuery 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.getParticipant delete mode 100644 data/core.telegram.org/method/channels.toggleSignatures delete mode 100644 data/core.telegram.org/method/contacts.addContact delete mode 100644 data/core.telegram.org/method/contacts.blockFromReplies delete mode 100644 data/core.telegram.org/method/contacts.resolveUsername 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.getCdnConfig delete mode 100644 data/core.telegram.org/method/help.getDeepLinkInfo delete mode 100644 data/core.telegram.org/method/help.getNearestDc delete mode 100644 data/core.telegram.org/method/help.getProxyData delete mode 100644 data/core.telegram.org/method/help.hidePromoData delete mode 100644 data/core.telegram.org/method/invokeWithMessagesRange.html delete mode 100644 data/core.telegram.org/method/messages.acceptUrlAuth 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.getEmojiKeywords delete mode 100644 data/core.telegram.org/method/messages.getMessages delete mode 100644 data/core.telegram.org/method/messages.readFeaturedStickers delete mode 100644 data/core.telegram.org/method/messages.readMessageContents delete mode 100644 data/core.telegram.org/method/messages.reportSpam delete mode 100644 data/core.telegram.org/method/messages.setBotCallbackAnswer delete mode 100644 data/core.telegram.org/method/messages.setHistoryTTL delete mode 100644 data/core.telegram.org/method/messages.unpinAllMessages delete mode 100644 data/core.telegram.org/method/payments.getBankCardData delete mode 100644 data/core.telegram.org/method/phone.editGroupCallParticipant 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/stats.getBroadcastStats delete mode 100644 data/core.telegram.org/method/stickers.createStickerSet delete mode 100644 data/core.telegram.org/method/updates.getState delete mode 100644 data/core.telegram.org/schema.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/ChatTheme.html delete mode 100644 data/core.telegram.org/type/DraftMessage.html delete mode 100644 data/core.telegram.org/type/EmojiLanguage.html delete mode 100644 data/core.telegram.org/type/Error.html delete mode 100644 data/core.telegram.org/type/FileHash.html delete mode 100644 data/core.telegram.org/type/HighScore.html delete mode 100644 data/core.telegram.org/type/InputBotInlineMessage.html delete mode 100644 data/core.telegram.org/type/InputPrivacyKey.html delete mode 100644 data/core.telegram.org/type/InputThemeSettings.html delete mode 100644 data/core.telegram.org/type/InputWebDocument.html delete mode 100644 data/core.telegram.org/type/MessageReplies.html delete mode 100644 data/core.telegram.org/type/MessageUserVote.html delete mode 100644 data/core.telegram.org/type/NearestDc.html delete mode 100644 data/core.telegram.org/type/Null.html delete mode 100644 data/core.telegram.org/type/PaymentCharge.html delete mode 100644 data/core.telegram.org/type/PeerNotifySettings.html delete mode 100644 data/core.telegram.org/type/PollAnswerVoters.html delete mode 100644 data/core.telegram.org/type/RestrictionReason.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/account.AuthorizationForm delete mode 100644 data/core.telegram.org/type/account.WebAuthorizations delete mode 100644 data/core.telegram.org/type/auth.ExportedAuthorization delete mode 100644 data/core.telegram.org/type/contacts.ResolvedPeer delete mode 100644 data/core.telegram.org/type/help.DeepLinkInfo delete mode 100644 data/core.telegram.org/type/help.ProxyData delete mode 100644 data/core.telegram.org/type/long.html delete mode 100644 data/core.telegram.org/type/messages.ArchivedStickers delete mode 100644 data/core.telegram.org/type/messages.ChatFull delete mode 100644 data/core.telegram.org/type/messages.SponsoredMessages delete mode 100644 data/core.telegram.org/type/messages.StatedMessages delete mode 100644 data/core.telegram.org/widgets/discussion.html delete mode 100644 data/corefork.telegram.org/api/bots/games.html delete mode 100644 data/corefork.telegram.org/api/files.html delete mode 100644 data/corefork.telegram.org/api/passport.html delete mode 100644 data/corefork.telegram.org/api/payments.html delete mode 100644 data/corefork.telegram.org/api/web-events.html delete mode 100644 data/corefork.telegram.org/bots/webhooks.html delete mode 100644 data/corefork.telegram.org/constructor/account.authorizations 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.themes delete mode 100644 data/corefork.telegram.org/constructor/auth.exportedAuthorization delete mode 100644 data/corefork.telegram.org/constructor/auth.loginTokenMigrateTo delete mode 100644 data/corefork.telegram.org/constructor/auth.sentAppCode delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeAbout.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteDelete.html delete mode 100644 data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantVolume.html delete mode 100644 data/corefork.telegram.org/constructor/channelLocationEmpty.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/channelParticipantsBots.html delete mode 100644 data/corefork.telegram.org/constructor/chatInvite.html delete mode 100644 data/corefork.telegram.org/constructor/config.html delete mode 100644 data/corefork.telegram.org/constructor/contacts.topPeersDisabled delete mode 100644 data/corefork.telegram.org/constructor/dialog.html delete mode 100644 data/corefork.telegram.org/constructor/dialogFilter.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/game.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/help.promoDataEmpty delete mode 100644 data/corefork.telegram.org/constructor/help.userInfoEmpty delete mode 100644 data/corefork.telegram.org/constructor/inlineQueryPeerTypePM.html delete mode 100644 data/corefork.telegram.org/constructor/inputClientProxy.html delete mode 100644 data/corefork.telegram.org/constructor/inputDocumentEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/inputMediaPhoto.html delete mode 100644 data/corefork.telegram.org/constructor/inputMessagesFilterDocument.html delete mode 100644 data/corefork.telegram.org/constructor/inputPaymentCredentials.html delete mode 100644 data/corefork.telegram.org/constructor/inputPaymentCredentialsSaved.html delete mode 100644 data/corefork.telegram.org/constructor/inputPhotoEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/inputPhotoLegacyFileLocation.html delete mode 100644 data/corefork.telegram.org/constructor/inputReportReasonCopyright.html delete mode 100644 data/corefork.telegram.org/constructor/inputReportReasonViolence.html delete mode 100644 data/corefork.telegram.org/constructor/inputStickerSetDice.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/inputWebDocument.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionPinMessage.html delete mode 100644 data/corefork.telegram.org/constructor/messageActionSecureValuesSentMe.html delete mode 100644 data/corefork.telegram.org/constructor/messageFwdHeader.html delete mode 100644 data/corefork.telegram.org/constructor/messageService.html delete mode 100644 data/corefork.telegram.org/constructor/messages.allStickers delete mode 100644 data/corefork.telegram.org/constructor/messages.dialogs delete mode 100644 data/corefork.telegram.org/constructor/messages.foundStickerSets delete mode 100644 data/corefork.telegram.org/constructor/messages.recentStickersNotModified 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/null.html delete mode 100644 data/corefork.telegram.org/constructor/pageBlockAuthorDate.html delete mode 100644 data/corefork.telegram.org/constructor/pageListOrderedItemBlocks.html delete mode 100644 data/corefork.telegram.org/constructor/pageTableRow.html delete mode 100644 data/corefork.telegram.org/constructor/paymentCharge.html delete mode 100644 data/corefork.telegram.org/constructor/payments.ValidatedRequestedInfo 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/peerBlocked.html delete mode 100644 data/corefork.telegram.org/constructor/pollAnswerVoters.html delete mode 100644 data/corefork.telegram.org/constructor/privacyValueAllowChatParticipants.html delete mode 100644 data/corefork.telegram.org/constructor/recentMeUrlStickerSet.html delete mode 100644 data/corefork.telegram.org/constructor/replyKeyboardForceReply.html delete mode 100644 data/corefork.telegram.org/constructor/secureData.html delete mode 100644 data/corefork.telegram.org/constructor/secureFileEmpty.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/secureValueErrorData.html delete mode 100644 data/corefork.telegram.org/constructor/secureValueTypeTemporaryRegistration.html delete mode 100644 data/corefork.telegram.org/constructor/sendMessageCancelAction.html delete mode 100644 data/corefork.telegram.org/constructor/sendMessageUploadAudioAction.html delete mode 100644 data/corefork.telegram.org/constructor/sendMessageUploadPhotoAction.html delete mode 100644 data/corefork.telegram.org/constructor/statsGraphError.html delete mode 100644 data/corefork.telegram.org/constructor/storage.fileGif delete mode 100644 data/corefork.telegram.org/constructor/storage.filePng delete mode 100644 data/corefork.telegram.org/constructor/storage.fileWebp 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/textSubscript.html delete mode 100644 data/corefork.telegram.org/constructor/themeSettings.html delete mode 100644 data/corefork.telegram.org/constructor/updateBotCallbackQuery.html delete mode 100644 data/corefork.telegram.org/constructor/updateBotInlineQuery.html delete mode 100644 data/corefork.telegram.org/constructor/updateEncryptedChatTyping.html delete mode 100644 data/corefork.telegram.org/constructor/updateLoginToken.html delete mode 100644 data/corefork.telegram.org/constructor/updateNewMessage.html delete mode 100644 data/corefork.telegram.org/constructor/updatePhoneCallSignalingData.html delete mode 100644 data/corefork.telegram.org/constructor/updateSavedGifs.html delete mode 100644 data/corefork.telegram.org/constructor/updateStickerSetsOrder.html delete mode 100644 data/corefork.telegram.org/constructor/urlAuthResultAccepted.html delete mode 100644 data/corefork.telegram.org/constructor/userProfilePhotoEmpty.html delete mode 100644 data/corefork.telegram.org/constructor/webPageEmpty.html delete mode 100644 data/corefork.telegram.org/method/account.confirmPasswordEmail delete mode 100644 data/corefork.telegram.org/method/account.getAccountTTL delete mode 100644 data/corefork.telegram.org/method/account.getAuthorizationForm delete mode 100644 data/corefork.telegram.org/method/account.getContactSignUpNotification delete mode 100644 data/corefork.telegram.org/method/account.getSecureValue delete mode 100644 data/corefork.telegram.org/method/account.installWallPaper delete mode 100644 data/corefork.telegram.org/method/account.setContactSignUpNotification 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.checkPhone delete mode 100644 data/corefork.telegram.org/method/auth.sendInvites delete mode 100644 data/corefork.telegram.org/method/channels.editPhoto delete mode 100644 data/corefork.telegram.org/method/channels.getFullChannel delete mode 100644 data/corefork.telegram.org/method/channels.togglePreHistoryHidden delete mode 100644 data/corefork.telegram.org/method/help.getDeepLinkInfo delete mode 100644 data/corefork.telegram.org/method/help.getTermsOfServiceUpdate delete mode 100644 data/corefork.telegram.org/method/messages.acceptUrlAuth delete mode 100644 data/corefork.telegram.org/method/messages.deleteHistory delete mode 100644 data/corefork.telegram.org/method/messages.editChatAbout delete mode 100644 data/corefork.telegram.org/method/messages.getAttachedStickers delete mode 100644 data/corefork.telegram.org/method/messages.getChats delete mode 100644 data/corefork.telegram.org/method/messages.getExportedChatInvite delete mode 100644 data/corefork.telegram.org/method/messages.getGameHighScores delete mode 100644 data/corefork.telegram.org/method/messages.getHistory delete mode 100644 data/corefork.telegram.org/method/messages.getOnlines 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.getSavedGifs delete mode 100644 data/corefork.telegram.org/method/messages.initHistoryImport delete mode 100644 data/corefork.telegram.org/method/messages.readMessageContents 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.search delete mode 100644 data/corefork.telegram.org/method/messages.searchGlobal delete mode 100644 data/corefork.telegram.org/method/messages.setInlineBotResults delete mode 100644 data/corefork.telegram.org/method/messages.toggleStickerSets delete mode 100644 data/corefork.telegram.org/method/messages.uploadEncryptedFile delete mode 100644 data/corefork.telegram.org/method/payments.getBankCardData delete mode 100644 data/corefork.telegram.org/method/phone.joinGroupCall 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/photos.updateProfilePhoto delete mode 100644 data/corefork.telegram.org/method/stats.getMessageStats delete mode 100644 data/corefork.telegram.org/method/stickers.removeStickerFromSet 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.getFileHashes delete mode 100644 data/corefork.telegram.org/mtproto/TL-combinators.html delete mode 100644 data/corefork.telegram.org/mtproto/description_v1.html delete mode 100644 data/corefork.telegram.org/type/BotCommand.html delete mode 100644 data/corefork.telegram.org/type/BotInlineResult.html delete mode 100644 data/corefork.telegram.org/type/ChannelAdminLogEventsFilter.html delete mode 100644 data/corefork.telegram.org/type/ChatParticipants.html delete mode 100644 data/corefork.telegram.org/type/ChatTheme.html delete mode 100644 data/corefork.telegram.org/type/GroupCallParticipant.html delete mode 100644 data/corefork.telegram.org/type/InputBotInlineResult.html delete mode 100644 data/corefork.telegram.org/type/InputDocument.html delete mode 100644 data/corefork.telegram.org/type/InputEncryptedFile.html delete mode 100644 data/corefork.telegram.org/type/InputNotifyPeer.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/MessageViews.html delete mode 100644 data/corefork.telegram.org/type/NearestDc.html delete mode 100644 data/corefork.telegram.org/type/PageBlock.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/PollResults.html delete mode 100644 data/corefork.telegram.org/type/ReceivedNotifyMessage.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/UrlAuthResult.html delete mode 100644 data/corefork.telegram.org/type/UserProfilePhoto.html delete mode 100644 data/corefork.telegram.org/type/WebPage.html delete mode 100644 data/corefork.telegram.org/type/account.ChatThemes delete mode 100644 data/corefork.telegram.org/type/auth.CheckedPhone delete mode 100644 data/corefork.telegram.org/type/auth.SentCodeType delete mode 100644 data/corefork.telegram.org/type/channels.ChannelParticipant 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/messages.AffectedFoundMessages delete mode 100644 data/corefork.telegram.org/type/messages.CheckedHistoryImportPeer delete mode 100644 data/corefork.telegram.org/type/messages.HighScores delete mode 100644 data/corefork.telegram.org/type/messages.SentMessage delete mode 100644 data/corefork.telegram.org/type/phone.GroupCall delete mode 100644 data/corefork.telegram.org/type/photos.Photo delete mode 100644 data/corefork.telegram.org/type/upload.CdnFile delete mode 100644 data/instantview.telegram.org/auth.html delete mode 100644 data/instantview.telegram.org/checklist.html delete mode 100644 data/promote.telegram.org/basics.html delete mode 100644 data/telegram.org/api.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/6-years.html delete mode 100644 data/telegram.org/blog/albums-saved-messages.html delete mode 100644 data/telegram.org/blog/bot-revolution.html delete mode 100644 data/telegram.org/blog/channels-2-0.html delete mode 100644 data/telegram.org/blog/desktop-1-0.html delete mode 100644 data/telegram.org/blog/edit.html delete mode 100644 data/telegram.org/blog/files-on-steroids.html delete mode 100644 data/telegram.org/blog/folders.html delete mode 100644 data/telegram.org/blog/group-video-calls.html delete mode 100644 data/telegram.org/blog/instant-view.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/new-profiles-people-nearby.html delete mode 100644 data/telegram.org/blog/now-you-see-me.html delete mode 100644 data/telegram.org/blog/permissions-groups-undo.html delete mode 100644 data/telegram.org/blog/polls.html delete mode 100644 data/telegram.org/blog/replies-mentions-stickers.html delete mode 100644 data/telegram.org/blog/search-and-media.html delete mode 100644 data/telegram.org/blog/share-preview.html delete mode 100644 data/telegram.org/blog/shared-links.html delete mode 100644 data/telegram.org/blog/supergroups5k.html delete mode 100644 data/telegram.org/blog/tdlib.html delete mode 100644 data/telegram.org/blog/telegraph.html delete mode 100644 data/telegram.org/blog/unsend-and-usage.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/voice-2-secret-3.html delete mode 100644 data/telegram.org/blog/voice-chats.html delete mode 100644 data/telegram.org/tos.html delete mode 100644 data/telegram.org/tour/screenshots.html diff --git a/data/core.telegram.org/api/datacenter.html b/data/core.telegram.org/api/datacenter.html deleted file mode 100644 index 4bb25565a7..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/pattern.html b/data/core.telegram.org/api/pattern.html deleted file mode 100644 index 12910e3514..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/bots/faq.html b/data/core.telegram.org/bots/faq.html deleted file mode 100644 index dc7493d2c5..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/samples/hellobot.html b/data/core.telegram.org/bots/samples/hellobot.html deleted file mode 100644 index f82db55dbc..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/constructor/account.authorizations b/data/core.telegram.org/constructor/account.authorizations deleted file mode 100644 index 13a00bdcfa..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.wallPapersNotModified b/data/core.telegram.org/constructor/account.wallPapersNotModified deleted file mode 100644 index 0b032e54e2..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 84ccd4540a..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/auth.codeTypeCall b/data/core.telegram.org/constructor/auth.codeTypeCall deleted file mode 100644 index 723ab4bd27..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.exportedAuthorization b/data/core.telegram.org/constructor/auth.exportedAuthorization deleted file mode 100644 index b41f1c3847..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.loginTokenMigrateTo b/data/core.telegram.org/constructor/auth.loginTokenMigrateTo deleted file mode 100644 index 9718b57c7b..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/botCommandScopeDefault.html b/data/core.telegram.org/constructor/botCommandScopeDefault.html deleted file mode 100644 index a80db6fba2..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 5ec72713c2..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/botInlineMessageMediaGeo.html b/data/core.telegram.org/constructor/botInlineMessageMediaGeo.html deleted file mode 100644 index c81c02208a..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/botInlineMessageText.html b/data/core.telegram.org/constructor/botInlineMessageText.html deleted file mode 100644 index 9ba66cfb11..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/cdnConfig.html b/data/core.telegram.org/constructor/cdnConfig.html deleted file mode 100644 index adb1885345..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 d2f65e88a6..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/channelAdminLogEventActionChangeLocation.html b/data/core.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html deleted file mode 100644 index f39eb93859..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/channelAdminLogEventActionParticipantLeave.html b/data/core.telegram.org/constructor/channelAdminLogEventActionParticipantLeave.html deleted file mode 100644 index 800728d20e..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/channelAdminLogEventActionUpdatePinned.html b/data/core.telegram.org/constructor/channelAdminLogEventActionUpdatePinned.html deleted file mode 100644 index 73d94b4e16..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/channelMessagesFilter.html b/data/core.telegram.org/constructor/channelMessagesFilter.html deleted file mode 100644 index 76a1151712..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/chatInvitePeek.html b/data/core.telegram.org/constructor/chatInvitePeek.html deleted file mode 100644 index 3b35695769..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/contacts.found b/data/core.telegram.org/constructor/contacts.found deleted file mode 100644 index d97e31e878..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 d6736bb850..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 c99a5e2831..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/decryptedMessageMediaGeoPoint.html b/data/core.telegram.org/constructor/decryptedMessageMediaGeoPoint.html deleted file mode 100644 index a8c3c072ef..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/dialogFilterSuggested.html b/data/core.telegram.org/constructor/dialogFilterSuggested.html deleted file mode 100644 index 48566a3e69..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/draftMessage.html b/data/core.telegram.org/constructor/draftMessage.html deleted file mode 100644 index 354e86e62e..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 6f927615e4..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/emojiKeywordsDifference.html b/data/core.telegram.org/constructor/emojiKeywordsDifference.html deleted file mode 100644 index b058b5afdb..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 3d7e037e99..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/error.html b/data/core.telegram.org/constructor/error.html deleted file mode 100644 index 69c78c8093..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/fileHash.html b/data/core.telegram.org/constructor/fileHash.html deleted file mode 100644 index 6bf498e851..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/folder.html b/data/core.telegram.org/constructor/folder.html deleted file mode 100644 index e21fbd12cd..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/geoPointEmpty.html b/data/core.telegram.org/constructor/geoPointEmpty.html deleted file mode 100644 index 16c50b12df..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/help.deepLinkInfo b/data/core.telegram.org/constructor/help.deepLinkInfo deleted file mode 100644 index c0f4020b1a..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 6d51e2386d..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.passportConfig b/data/core.telegram.org/constructor/help.passportConfig deleted file mode 100644 index 184605502e..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.support b/data/core.telegram.org/constructor/help.support deleted file mode 100644 index 30b15bd1a4..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/highScore.html b/data/core.telegram.org/constructor/highScore.html deleted file mode 100644 index 1c4f25bfd0..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 4909d2b11d..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/inputBotInlineMessageGame.html b/data/core.telegram.org/constructor/inputBotInlineMessageGame.html deleted file mode 100644 index cc5bb826c0..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/inputBotInlineMessageMediaAuto.html b/data/core.telegram.org/constructor/inputBotInlineMessageMediaAuto.html deleted file mode 100644 index 51944af606..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 75a8e8cf72..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 5df5225941..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/inputBotInlineMessageMediaVenue.html b/data/core.telegram.org/constructor/inputBotInlineMessageMediaVenue.html deleted file mode 100644 index e4856fad86..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 d2cdad5adb..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/inputDocumentFileLocation.html b/data/core.telegram.org/constructor/inputDocumentFileLocation.html deleted file mode 100644 index 2ca32801cd..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/inputEncryptedFileUploaded.html b/data/core.telegram.org/constructor/inputEncryptedFileUploaded.html deleted file mode 100644 index 1bcb5a0c76..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/inputGameShortName.html b/data/core.telegram.org/constructor/inputGameShortName.html deleted file mode 100644 index d3bec0c9d6..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 96673ffd97..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 76427519d0..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/inputMediaDocumentExternal.html b/data/core.telegram.org/constructor/inputMediaDocumentExternal.html deleted file mode 100644 index b5556b8b39..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/inputMediaUploadedPhoto.html b/data/core.telegram.org/constructor/inputMediaUploadedPhoto.html deleted file mode 100644 index 12d4512a6e..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/inputMessagesFilterPhoneCalls.html b/data/core.telegram.org/constructor/inputMessagesFilterPhoneCalls.html deleted file mode 100644 index b2a7cec4a0..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/inputMessagesFilterPhotos.html b/data/core.telegram.org/constructor/inputMessagesFilterPhotos.html deleted file mode 100644 index 6bdeeddeaa..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/inputMessagesFilterPinned.html b/data/core.telegram.org/constructor/inputMessagesFilterPinned.html deleted file mode 100644 index 0a2e96cc8f..0000000000 --- a/data/core.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/core.telegram.org/constructor/inputPeerEmpty.html b/data/core.telegram.org/constructor/inputPeerEmpty.html deleted file mode 100644 index a47a98d756..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/inputPhoneContact.html b/data/core.telegram.org/constructor/inputPhoneContact.html deleted file mode 100644 index 54354e0f11..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/inputPhotoLegacyFileLocation.html b/data/core.telegram.org/constructor/inputPhotoLegacyFileLocation.html deleted file mode 100644 index 26e02c32f9..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 889ac0d746..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 1cfd879520..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 4c66ab7dcd..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 2aae2a9991..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 fe0a0afd4a..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 aea52117fb..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 7a452878e0..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/inputStickerSetDice.html b/data/core.telegram.org/constructor/inputStickerSetDice.html deleted file mode 100644 index 2a9464cc9e..0000000000 --- a/data/core.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/core.telegram.org/constructor/inputStickeredMediaPhoto.html b/data/core.telegram.org/constructor/inputStickeredMediaPhoto.html deleted file mode 100644 index 284a7d8d3c..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/inputThemeSlug.html b/data/core.telegram.org/constructor/inputThemeSlug.html deleted file mode 100644 index 54c9f42d62..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/inputUserFromMessage.html b/data/core.telegram.org/constructor/inputUserFromMessage.html deleted file mode 100644 index a91a1312e5..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 703627b7e1..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/inputWebDocument.html b/data/core.telegram.org/constructor/inputWebDocument.html deleted file mode 100644 index 75bc73b7f0..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 47177b052c..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/jsonBool.html b/data/core.telegram.org/constructor/jsonBool.html deleted file mode 100644 index 75ec942d7e..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/keyboardButtonGame.html b/data/core.telegram.org/constructor/keyboardButtonGame.html deleted file mode 100644 index f7080a00d1..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/messageActionGeoProximityReached.html b/data/core.telegram.org/constructor/messageActionGeoProximityReached.html deleted file mode 100644 index 8c59a9d670..0000000000 --- a/data/core.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/core.telegram.org/constructor/messageActionGroupCall.html b/data/core.telegram.org/constructor/messageActionGroupCall.html deleted file mode 100644 index e08d58fc5b..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/messageActionSetMessagesTTL.html b/data/core.telegram.org/constructor/messageActionSetMessagesTTL.html deleted file mode 100644 index c3404e6bb5..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/messageReplies.html b/data/core.telegram.org/constructor/messageReplies.html deleted file mode 100644 index b1f01c979f..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/messageViews.html b/data/core.telegram.org/constructor/messageViews.html deleted file mode 100644 index c2eb4b4031..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.botCallbackAnswer b/data/core.telegram.org/constructor/messages.botCallbackAnswer deleted file mode 100644 index 161a94bb5d..0000000000 --- a/data/core.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/core.telegram.org/constructor/messages.chatInviteImporters b/data/core.telegram.org/constructor/messages.chatInviteImporters deleted file mode 100644 index 2904592530..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.dhConfigNotModified b/data/core.telegram.org/constructor/messages.dhConfigNotModified deleted file mode 100644 index 99f7e72779..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.dialogsSlice b/data/core.telegram.org/constructor/messages.dialogsSlice deleted file mode 100644 index 15a5aac89d..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.exportedChatInviteReplaced b/data/core.telegram.org/constructor/messages.exportedChatInviteReplaced deleted file mode 100644 index 26ac9653f5..0000000000 --- a/data/core.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/core.telegram.org/constructor/messages.messagesNotModified b/data/core.telegram.org/constructor/messages.messagesNotModified deleted file mode 100644 index 1b2c265080..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.savedGifsNotModified b/data/core.telegram.org/constructor/messages.savedGifsNotModified deleted file mode 100644 index 6d0935ee17..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.votesList b/data/core.telegram.org/constructor/messages.votesList deleted file mode 100644 index 3f72288753..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 3f44044b50..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/notifyPeer.html b/data/core.telegram.org/constructor/notifyPeer.html deleted file mode 100644 index 872f042f0e..0000000000 --- a/data/core.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/core.telegram.org/constructor/null.html b/data/core.telegram.org/constructor/null.html deleted file mode 100644 index c1d1c70ba5..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/pageBlockBlockquote.html b/data/core.telegram.org/constructor/pageBlockBlockquote.html deleted file mode 100644 index a595ffa7de..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/pageBlockParagraph.html b/data/core.telegram.org/constructor/pageBlockParagraph.html deleted file mode 100644 index 25cd64888b..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/pageBlockUnsupported.html b/data/core.telegram.org/constructor/pageBlockUnsupported.html deleted file mode 100644 index 69dd67836a..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/pageListOrderedItemText.html b/data/core.telegram.org/constructor/pageListOrderedItemText.html deleted file mode 100644 index c0fb27811a..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 37badf75a8..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/pageTableRow.html b/data/core.telegram.org/constructor/pageTableRow.html deleted file mode 100644 index 97027d6ab6..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/passwordKdfAlgoUnknown.html b/data/core.telegram.org/constructor/passwordKdfAlgoUnknown.html deleted file mode 100644 index e8f491a454..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 3f4efdaa92..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 f43cfd233b..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/phone.joinAsPeers b/data/core.telegram.org/constructor/phone.joinAsPeers deleted file mode 100644 index ee318f9a41..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/phoneCallDiscardReasonMissed.html b/data/core.telegram.org/constructor/phoneCallDiscardReasonMissed.html deleted file mode 100644 index 4f923bc708..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/photoSizeEmpty.html b/data/core.telegram.org/constructor/photoSizeEmpty.html deleted file mode 100644 index da244710d1..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 f9918ca914..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/recentMeUrlUnknown.html b/data/core.telegram.org/constructor/recentMeUrlUnknown.html deleted file mode 100644 index 62f4e58aa1..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/replyKeyboardMarkup.html b/data/core.telegram.org/constructor/replyKeyboardMarkup.html deleted file mode 100644 index b226332b18..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 82439f6626..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/securePlainPhone.html b/data/core.telegram.org/constructor/securePlainPhone.html deleted file mode 100644 index 1f4e593a15..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/secureValueErrorTranslationFile.html b/data/core.telegram.org/constructor/secureValueErrorTranslationFile.html deleted file mode 100644 index b459e8c816..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 cd92c66ae1..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/secureValueTypePassportRegistration.html b/data/core.telegram.org/constructor/secureValueTypePassportRegistration.html deleted file mode 100644 index 7d2073d325..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 5a7f2f8c2c..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/sendMessageUploadAudioAction.html b/data/core.telegram.org/constructor/sendMessageUploadAudioAction.html deleted file mode 100644 index cffbdb41f0..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/sendMessageUploadPhotoAction.html b/data/core.telegram.org/constructor/sendMessageUploadPhotoAction.html deleted file mode 100644 index 70cbce2cc9..0000000000 --- a/data/core.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/core.telegram.org/constructor/statsGraph.html b/data/core.telegram.org/constructor/statsGraph.html deleted file mode 100644 index 0c08a81967..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/statsURL.html b/data/core.telegram.org/constructor/statsURL.html deleted file mode 100644 index f99c2068db..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/storage.fileGif b/data/core.telegram.org/constructor/storage.fileGif deleted file mode 100644 index 276b7b6671..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 e1a859366b..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 20920854fb..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 453380df9b..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/topPeer.html b/data/core.telegram.org/constructor/topPeer.html deleted file mode 100644 index d12aee53e8..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/updateChannel.html b/data/core.telegram.org/constructor/updateChannel.html deleted file mode 100644 index 4371cbea0a..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/updateChannelMessageViews.html b/data/core.telegram.org/constructor/updateChannelMessageViews.html deleted file mode 100644 index e8796e3f64..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/updateChannelTooLong.html b/data/core.telegram.org/constructor/updateChannelTooLong.html deleted file mode 100644 index 210508b3ab..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/updateChatParticipantAdmin.html b/data/core.telegram.org/constructor/updateChatParticipantAdmin.html deleted file mode 100644 index b085f0390a..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/updateDialogUnreadMark.html b/data/core.telegram.org/constructor/updateDialogUnreadMark.html deleted file mode 100644 index 6cf5bc8a83..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 bbc43f6914..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/updateEncryption.html b/data/core.telegram.org/constructor/updateEncryption.html deleted file mode 100644 index 6e55abf7c9..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/updatePinnedMessages.html b/data/core.telegram.org/constructor/updatePinnedMessages.html deleted file mode 100644 index dc8360eb92..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/updateReadHistoryInbox.html b/data/core.telegram.org/constructor/updateReadHistoryInbox.html deleted file mode 100644 index 16bf175153..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/updateRecentStickers.html b/data/core.telegram.org/constructor/updateRecentStickers.html deleted file mode 100644 index 2959da4e55..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/updateStickerSetsOrder.html b/data/core.telegram.org/constructor/updateStickerSetsOrder.html deleted file mode 100644 index 0879d1674e..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/updateUserPhoto.html b/data/core.telegram.org/constructor/updateUserPhoto.html deleted file mode 100644 index 2a0e5260ee..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/updates.channelDifferenceEmpty b/data/core.telegram.org/constructor/updates.channelDifferenceEmpty deleted file mode 100644 index f7af6d05d9..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/urlAuthResultRequest.html b/data/core.telegram.org/constructor/urlAuthResultRequest.html deleted file mode 100644 index ae581a8d84..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/userStatusOnline.html b/data/core.telegram.org/constructor/userStatusOnline.html deleted file mode 100644 index 34ea5999ad..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/method/account.getNotifySettings b/data/core.telegram.org/method/account.getNotifySettings deleted file mode 100644 index c91cf63c67..0000000000 --- a/data/core.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/core.telegram.org/method/account.getTheme b/data/core.telegram.org/method/account.getTheme deleted file mode 100644 index 9727936799..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.getWebAuthorizations b/data/core.telegram.org/method/account.getWebAuthorizations deleted file mode 100644 index a6da5f4f05..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.saveTheme b/data/core.telegram.org/method/account.saveTheme deleted file mode 100644 index 29eac6e83c..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.updatePasswordSettings b/data/core.telegram.org/method/account.updatePasswordSettings deleted file mode 100644 index dbe97859a2..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 403d7c644d..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/auth.exportAuthorization b/data/core.telegram.org/method/auth.exportAuthorization deleted file mode 100644 index 43928dfaed..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/bots.answerWebhookJSONQuery b/data/core.telegram.org/method/bots.answerWebhookJSONQuery deleted file mode 100644 index 74fa1e2346..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/channels.editLocation b/data/core.telegram.org/method/channels.editLocation deleted file mode 100644 index 3b8076064a..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 372d0cde2c..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.getParticipant b/data/core.telegram.org/method/channels.getParticipant deleted file mode 100644 index e2f40efff8..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.toggleSignatures b/data/core.telegram.org/method/channels.toggleSignatures deleted file mode 100644 index d54f1d544c..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/contacts.addContact b/data/core.telegram.org/method/contacts.addContact deleted file mode 100644 index 5658f060d0..0000000000 --- a/data/core.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/core.telegram.org/method/contacts.blockFromReplies b/data/core.telegram.org/method/contacts.blockFromReplies deleted file mode 100644 index 95802fbd30..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.resolveUsername b/data/core.telegram.org/method/contacts.resolveUsername deleted file mode 100644 index b82f2f2a7d..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/help.acceptTermsOfService b/data/core.telegram.org/method/help.acceptTermsOfService deleted file mode 100644 index e08f6a6bdb..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 ca383d4e13..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.getCdnConfig b/data/core.telegram.org/method/help.getCdnConfig deleted file mode 100644 index 9f6870b38b..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.getDeepLinkInfo b/data/core.telegram.org/method/help.getDeepLinkInfo deleted file mode 100644 index 0236a8f808..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.getNearestDc b/data/core.telegram.org/method/help.getNearestDc deleted file mode 100644 index 8c8fe7dd28..0000000000 --- a/data/core.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/core.telegram.org/method/help.getProxyData b/data/core.telegram.org/method/help.getProxyData deleted file mode 100644 index 2e871d69bd..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.hidePromoData b/data/core.telegram.org/method/help.hidePromoData deleted file mode 100644 index fc394cfa58..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/invokeWithMessagesRange.html b/data/core.telegram.org/method/invokeWithMessagesRange.html deleted file mode 100644 index 3b72048749..0000000000 --- a/data/core.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/core.telegram.org/method/messages.acceptUrlAuth b/data/core.telegram.org/method/messages.acceptUrlAuth deleted file mode 100644 index 4f580998c6..0000000000 --- a/data/core.telegram.org/method/messages.acceptUrlAuth +++ /dev/null @@ -1,179 +0,0 @@ - - - - - messages.acceptUrlAuth - - - - - - - - - - - - - -
- -
-
-
- -

messages.acceptUrlAuth

- -

Use this to accept 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.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;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
write_allowedflags.0?trueSet this flag to allow the bot to send messages to you (if requested)
peerflags.1?InputPeerThe location of the message
msg_idflags.1?intMessage ID of the message with the login button
button_idflags.1?intID of the login button
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.getAllDrafts b/data/core.telegram.org/method/messages.getAllDrafts deleted file mode 100644 index 5f6d16c431..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 523abc85c0..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.getEmojiKeywords b/data/core.telegram.org/method/messages.getEmojiKeywords deleted file mode 100644 index e78341196e..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.getMessages b/data/core.telegram.org/method/messages.getMessages deleted file mode 100644 index 2ede6ccb94..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.readFeaturedStickers b/data/core.telegram.org/method/messages.readFeaturedStickers deleted file mode 100644 index bca88af772..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.readMessageContents b/data/core.telegram.org/method/messages.readMessageContents deleted file mode 100644 index 42c4511b2b..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.reportSpam b/data/core.telegram.org/method/messages.reportSpam deleted file mode 100644 index 7332f8f2e1..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.setBotCallbackAnswer b/data/core.telegram.org/method/messages.setBotCallbackAnswer deleted file mode 100644 index ec822abdec..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.setHistoryTTL b/data/core.telegram.org/method/messages.setHistoryTTL deleted file mode 100644 index 1f82c67f42..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.unpinAllMessages b/data/core.telegram.org/method/messages.unpinAllMessages deleted file mode 100644 index 2bb9f8d665..0000000000 --- a/data/core.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/core.telegram.org/method/payments.getBankCardData b/data/core.telegram.org/method/payments.getBankCardData deleted file mode 100644 index 49207436ae..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/phone.editGroupCallParticipant b/data/core.telegram.org/method/phone.editGroupCallParticipant deleted file mode 100644 index 73f64b5529..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.getGroupParticipants b/data/core.telegram.org/method/phone.getGroupParticipants deleted file mode 100644 index 1ae2ac8cd0..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 ac6e353747..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/stats.getBroadcastStats b/data/core.telegram.org/method/stats.getBroadcastStats deleted file mode 100644 index 9c7bbf93b2..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/stickers.createStickerSet b/data/core.telegram.org/method/stickers.createStickerSet deleted file mode 100644 index bea01fc38d..0000000000 --- a/data/core.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 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/core.telegram.org/method/updates.getState b/data/core.telegram.org/method/updates.getState deleted file mode 100644 index 10749bcb5e..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/schema.html b/data/core.telegram.org/schema.html deleted file mode 100644 index b88cc848fd..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 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 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 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 = 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 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/type/CdnConfig.html b/data/core.telegram.org/type/CdnConfig.html deleted file mode 100644 index ed6e13a282..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 bec1edbadb..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/ChatTheme.html b/data/core.telegram.org/type/ChatTheme.html deleted file mode 100644 index c3d2582390..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/DraftMessage.html b/data/core.telegram.org/type/DraftMessage.html deleted file mode 100644 index 41d05607a1..0000000000 --- a/data/core.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/core.telegram.org/type/EmojiLanguage.html b/data/core.telegram.org/type/EmojiLanguage.html deleted file mode 100644 index d02c7e6ec5..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/Error.html b/data/core.telegram.org/type/Error.html deleted file mode 100644 index af5e5e844e..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/FileHash.html b/data/core.telegram.org/type/FileHash.html deleted file mode 100644 index c7352dea59..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/HighScore.html b/data/core.telegram.org/type/HighScore.html deleted file mode 100644 index d07eaa273f..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/InputBotInlineMessage.html b/data/core.telegram.org/type/InputBotInlineMessage.html deleted file mode 100644 index 5bceedabb9..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/InputPrivacyKey.html b/data/core.telegram.org/type/InputPrivacyKey.html deleted file mode 100644 index 8a9ad11925..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/InputThemeSettings.html b/data/core.telegram.org/type/InputThemeSettings.html deleted file mode 100644 index c8f24b8834..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/InputWebDocument.html b/data/core.telegram.org/type/InputWebDocument.html deleted file mode 100644 index 42994c5f30..0000000000 --- a/data/core.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/core.telegram.org/type/MessageReplies.html b/data/core.telegram.org/type/MessageReplies.html deleted file mode 100644 index 4b61bd69b1..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/MessageUserVote.html b/data/core.telegram.org/type/MessageUserVote.html deleted file mode 100644 index 3b26b8ecc3..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/NearestDc.html b/data/core.telegram.org/type/NearestDc.html deleted file mode 100644 index 6d822787ff..0000000000 --- a/data/core.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/core.telegram.org/type/Null.html b/data/core.telegram.org/type/Null.html deleted file mode 100644 index 558bfa07de..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/PaymentCharge.html b/data/core.telegram.org/type/PaymentCharge.html deleted file mode 100644 index fd8811552c..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/PeerNotifySettings.html b/data/core.telegram.org/type/PeerNotifySettings.html deleted file mode 100644 index d248c2bbea..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/PollAnswerVoters.html b/data/core.telegram.org/type/PollAnswerVoters.html deleted file mode 100644 index a8a1629914..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/RestrictionReason.html b/data/core.telegram.org/type/RestrictionReason.html deleted file mode 100644 index f5b9120bc1..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/StatsPercentValue.html b/data/core.telegram.org/type/StatsPercentValue.html deleted file mode 100644 index 6cf487f2d5..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 c59405af32..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/account.AuthorizationForm b/data/core.telegram.org/type/account.AuthorizationForm deleted file mode 100644 index d8dec512c0..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.WebAuthorizations b/data/core.telegram.org/type/account.WebAuthorizations deleted file mode 100644 index 53f74d54a6..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.ExportedAuthorization b/data/core.telegram.org/type/auth.ExportedAuthorization deleted file mode 100644 index ea829518b0..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/contacts.ResolvedPeer b/data/core.telegram.org/type/contacts.ResolvedPeer deleted file mode 100644 index 8afbe9611d..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/help.DeepLinkInfo b/data/core.telegram.org/type/help.DeepLinkInfo deleted file mode 100644 index c3c6163867..0000000000 --- a/data/core.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/core.telegram.org/type/help.ProxyData b/data/core.telegram.org/type/help.ProxyData deleted file mode 100644 index 9e2f5e37f0..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/long.html b/data/core.telegram.org/type/long.html deleted file mode 100644 index 9d3468077a..0000000000 --- a/data/core.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/core.telegram.org/type/messages.ArchivedStickers b/data/core.telegram.org/type/messages.ArchivedStickers deleted file mode 100644 index 098cc90145..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.ChatFull b/data/core.telegram.org/type/messages.ChatFull deleted file mode 100644 index 4fef014943..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.SponsoredMessages b/data/core.telegram.org/type/messages.SponsoredMessages deleted file mode 100644 index b717e32e6e..0000000000 --- a/data/core.telegram.org/type/messages.SponsoredMessages +++ /dev/null @@ -1,162 +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;
-
----functions---
-
-channels.getSponsoredMessages#ec210fbf channel:InputChannel = messages.SponsoredMessages;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
messages.sponsoredMessagesA set of sponsored messages associated to a channel
-

Methods

- - - - - - - - - - - - - -
MethodDescription
channels.getSponsoredMessagesGet a list of sponsored messages
- -
- -
-
- -
- - - - - - diff --git a/data/core.telegram.org/type/messages.StatedMessages b/data/core.telegram.org/type/messages.StatedMessages deleted file mode 100644 index 6279c351cf..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/widgets/discussion.html b/data/core.telegram.org/widgets/discussion.html deleted file mode 100644 index 83b48d88d5..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/corefork.telegram.org/api/bots/games.html b/data/corefork.telegram.org/api/bots/games.html deleted file mode 100644 index 600eab5db5..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/files.html b/data/corefork.telegram.org/api/files.html deleted file mode 100644 index 5727e3a817..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/passport.html b/data/corefork.telegram.org/api/passport.html deleted file mode 100644 index a64f87068e..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/payments.html b/data/corefork.telegram.org/api/payments.html deleted file mode 100644 index 862d059a39..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/web-events.html b/data/corefork.telegram.org/api/web-events.html deleted file mode 100644 index d153d315e6..0000000000 --- a/data/corefork.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/corefork.telegram.org/bots/webhooks.html b/data/corefork.telegram.org/bots/webhooks.html deleted file mode 100644 index a88393aa0d..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, non-wildcard, 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/constructor/account.authorizations b/data/corefork.telegram.org/constructor/account.authorizations deleted file mode 100644 index 15b5f7695a..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.passwordSettings b/data/corefork.telegram.org/constructor/account.passwordSettings deleted file mode 100644 index 0791940a6e..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 405a1c9135..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 f4f6951303..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.themes b/data/corefork.telegram.org/constructor/account.themes deleted file mode 100644 index dc103de79e..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/auth.exportedAuthorization b/data/corefork.telegram.org/constructor/auth.exportedAuthorization deleted file mode 100644 index 959c17861f..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.loginTokenMigrateTo b/data/corefork.telegram.org/constructor/auth.loginTokenMigrateTo deleted file mode 100644 index 62c23ba21f..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.sentAppCode b/data/corefork.telegram.org/constructor/auth.sentAppCode deleted file mode 100644 index ad47b0bc56..0000000000 --- a/data/corefork.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/corefork.telegram.org/constructor/channelAdminLogEventActionChangeAbout.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeAbout.html deleted file mode 100644 index fc15842447..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/channelAdminLogEventActionChangeLocation.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionChangeLocation.html deleted file mode 100644 index 43fbf2f068..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/channelAdminLogEventActionExportedInviteDelete.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionExportedInviteDelete.html deleted file mode 100644 index 5a4f118e70..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/channelAdminLogEventActionParticipantVolume.html b/data/corefork.telegram.org/constructor/channelAdminLogEventActionParticipantVolume.html deleted file mode 100644 index 40656d3a78..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/channelLocationEmpty.html b/data/corefork.telegram.org/constructor/channelLocationEmpty.html deleted file mode 100644 index e2db0e0e47..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/channelMessagesFilterEmpty.html b/data/corefork.telegram.org/constructor/channelMessagesFilterEmpty.html deleted file mode 100644 index 59237bc256..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 a170cc28f5..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/channelParticipantsBots.html b/data/corefork.telegram.org/constructor/channelParticipantsBots.html deleted file mode 100644 index c3290e4356..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/chatInvite.html b/data/corefork.telegram.org/constructor/chatInvite.html deleted file mode 100644 index 4651d0ab93..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/config.html b/data/corefork.telegram.org/constructor/config.html deleted file mode 100644 index a677804169..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/contacts.topPeersDisabled b/data/corefork.telegram.org/constructor/contacts.topPeersDisabled deleted file mode 100644 index d0238aafc8..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/dialog.html b/data/corefork.telegram.org/constructor/dialog.html deleted file mode 100644 index b401d2d0a3..0000000000 --- a/data/corefork.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/corefork.telegram.org/constructor/dialogFilter.html b/data/corefork.telegram.org/constructor/dialogFilter.html deleted file mode 100644 index 124b88ffac..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/emojiKeywordsDifference.html b/data/corefork.telegram.org/constructor/emojiKeywordsDifference.html deleted file mode 100644 index a5a8db5386..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 3130bf9def..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/game.html b/data/corefork.telegram.org/constructor/game.html deleted file mode 100644 index e4e9e2549f..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/groupCallDiscarded.html b/data/corefork.telegram.org/constructor/groupCallDiscarded.html deleted file mode 100644 index 0e9cc3daa9..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 aa14570e63..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/help.promoDataEmpty b/data/corefork.telegram.org/constructor/help.promoDataEmpty deleted file mode 100644 index e48037781f..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.userInfoEmpty b/data/corefork.telegram.org/constructor/help.userInfoEmpty deleted file mode 100644 index 5e6490f1e9..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/inlineQueryPeerTypePM.html b/data/corefork.telegram.org/constructor/inlineQueryPeerTypePM.html deleted file mode 100644 index 5f8c3310d8..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/inputClientProxy.html b/data/corefork.telegram.org/constructor/inputClientProxy.html deleted file mode 100644 index 2deb367906..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/inputDocumentEmpty.html b/data/corefork.telegram.org/constructor/inputDocumentEmpty.html deleted file mode 100644 index 18596c82da..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/inputMediaPhoto.html b/data/corefork.telegram.org/constructor/inputMediaPhoto.html deleted file mode 100644 index 7b45c1ee8b..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/inputMessagesFilterDocument.html b/data/corefork.telegram.org/constructor/inputMessagesFilterDocument.html deleted file mode 100644 index 14a5184a93..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/inputPaymentCredentials.html b/data/corefork.telegram.org/constructor/inputPaymentCredentials.html deleted file mode 100644 index 59990e92db..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/inputPaymentCredentialsSaved.html b/data/corefork.telegram.org/constructor/inputPaymentCredentialsSaved.html deleted file mode 100644 index 98528fda0b..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/inputPhotoEmpty.html b/data/corefork.telegram.org/constructor/inputPhotoEmpty.html deleted file mode 100644 index d9480b30ce..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/inputPhotoLegacyFileLocation.html b/data/corefork.telegram.org/constructor/inputPhotoLegacyFileLocation.html deleted file mode 100644 index 6e37f67c26..0000000000 --- a/data/corefork.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/corefork.telegram.org/constructor/inputReportReasonCopyright.html b/data/corefork.telegram.org/constructor/inputReportReasonCopyright.html deleted file mode 100644 index f21ef4ac9e..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/inputReportReasonViolence.html b/data/corefork.telegram.org/constructor/inputReportReasonViolence.html deleted file mode 100644 index 58217929fb..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/inputStickerSetDice.html b/data/corefork.telegram.org/constructor/inputStickerSetDice.html deleted file mode 100644 index c2ef2b3ceb..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/inputThemeSlug.html b/data/corefork.telegram.org/constructor/inputThemeSlug.html deleted file mode 100644 index 18576fcb69..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 15cf791d0f..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/inputWebDocument.html b/data/corefork.telegram.org/constructor/inputWebDocument.html deleted file mode 100644 index 642b4f9354..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/messageActionPinMessage.html b/data/corefork.telegram.org/constructor/messageActionPinMessage.html deleted file mode 100644 index e9e7873a65..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/messageActionSecureValuesSentMe.html b/data/corefork.telegram.org/constructor/messageActionSecureValuesSentMe.html deleted file mode 100644 index 17ad93d9ba..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/messageFwdHeader.html b/data/corefork.telegram.org/constructor/messageFwdHeader.html deleted file mode 100644 index c1570fc86e..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/messageService.html b/data/corefork.telegram.org/constructor/messageService.html deleted file mode 100644 index 5b451f0bee..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/messages.allStickers b/data/corefork.telegram.org/constructor/messages.allStickers deleted file mode 100644 index 2a4c2aa8b4..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.dialogs b/data/corefork.telegram.org/constructor/messages.dialogs deleted file mode 100644 index 2cc12c88b7..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.foundStickerSets b/data/corefork.telegram.org/constructor/messages.foundStickerSets deleted file mode 100644 index e35fa11430..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.recentStickersNotModified b/data/corefork.telegram.org/constructor/messages.recentStickersNotModified deleted file mode 100644 index 9d232b7f3c..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.sentMessageLink b/data/corefork.telegram.org/constructor/messages.sentMessageLink deleted file mode 100644 index 530a1f7680..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 2cf4c057e2..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/null.html b/data/corefork.telegram.org/constructor/null.html deleted file mode 100644 index 021a6e7b4c..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/pageBlockAuthorDate.html b/data/corefork.telegram.org/constructor/pageBlockAuthorDate.html deleted file mode 100644 index bc5fb4b65b..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/pageListOrderedItemBlocks.html b/data/corefork.telegram.org/constructor/pageListOrderedItemBlocks.html deleted file mode 100644 index 80276efcc8..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/pageTableRow.html b/data/corefork.telegram.org/constructor/pageTableRow.html deleted file mode 100644 index 5f27c8a9f9..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/paymentCharge.html b/data/corefork.telegram.org/constructor/paymentCharge.html deleted file mode 100644 index 04c218e5fb..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/payments.ValidatedRequestedInfo b/data/corefork.telegram.org/constructor/payments.ValidatedRequestedInfo deleted file mode 100644 index eb379d0b6a..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.paymentResult b/data/corefork.telegram.org/constructor/payments.paymentResult deleted file mode 100644 index f0ee4e69aa..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 e3a023dc2c..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/peerBlocked.html b/data/corefork.telegram.org/constructor/peerBlocked.html deleted file mode 100644 index 8f26e02bde..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/pollAnswerVoters.html b/data/corefork.telegram.org/constructor/pollAnswerVoters.html deleted file mode 100644 index 25d6d9786b..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/privacyValueAllowChatParticipants.html b/data/corefork.telegram.org/constructor/privacyValueAllowChatParticipants.html deleted file mode 100644 index 07276d0633..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/recentMeUrlStickerSet.html b/data/corefork.telegram.org/constructor/recentMeUrlStickerSet.html deleted file mode 100644 index 4e603397e7..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/replyKeyboardForceReply.html b/data/corefork.telegram.org/constructor/replyKeyboardForceReply.html deleted file mode 100644 index 244c1f270e..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/secureData.html b/data/corefork.telegram.org/constructor/secureData.html deleted file mode 100644 index 6603c1fddf..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/secureFileEmpty.html b/data/corefork.telegram.org/constructor/secureFileEmpty.html deleted file mode 100644 index 5534b1ccf8..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/secureRequiredType.html b/data/corefork.telegram.org/constructor/secureRequiredType.html deleted file mode 100644 index 6fc7976454..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 00f34e5eae..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/secureValueErrorData.html b/data/corefork.telegram.org/constructor/secureValueErrorData.html deleted file mode 100644 index a0cb4382b3..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/secureValueTypeTemporaryRegistration.html b/data/corefork.telegram.org/constructor/secureValueTypeTemporaryRegistration.html deleted file mode 100644 index f57e3d82f7..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/sendMessageCancelAction.html b/data/corefork.telegram.org/constructor/sendMessageCancelAction.html deleted file mode 100644 index a862619dff..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/sendMessageUploadAudioAction.html b/data/corefork.telegram.org/constructor/sendMessageUploadAudioAction.html deleted file mode 100644 index 14ab2bce9c..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/sendMessageUploadPhotoAction.html b/data/corefork.telegram.org/constructor/sendMessageUploadPhotoAction.html deleted file mode 100644 index 17b3a00ba4..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/statsGraphError.html b/data/corefork.telegram.org/constructor/statsGraphError.html deleted file mode 100644 index ed9dd6f86a..0000000000 --- a/data/corefork.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/corefork.telegram.org/constructor/storage.fileGif b/data/corefork.telegram.org/constructor/storage.fileGif deleted file mode 100644 index 4042ac4eb8..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.filePng b/data/corefork.telegram.org/constructor/storage.filePng deleted file mode 100644 index 3b45602354..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.fileWebp b/data/corefork.telegram.org/constructor/storage.fileWebp deleted file mode 100644 index f8d8f1c259..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/textItalic.html b/data/corefork.telegram.org/constructor/textItalic.html deleted file mode 100644 index 6a1f0bb5ab..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 b8a6e3672d..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/textSubscript.html b/data/corefork.telegram.org/constructor/textSubscript.html deleted file mode 100644 index 34de5d2eb3..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/themeSettings.html b/data/corefork.telegram.org/constructor/themeSettings.html deleted file mode 100644 index cf08c71c4a..0000000000 --- a/data/corefork.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/corefork.telegram.org/constructor/updateBotCallbackQuery.html b/data/corefork.telegram.org/constructor/updateBotCallbackQuery.html deleted file mode 100644 index ee8b4d59cb..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/updateBotInlineQuery.html b/data/corefork.telegram.org/constructor/updateBotInlineQuery.html deleted file mode 100644 index 5b6d51ad54..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/updateEncryptedChatTyping.html b/data/corefork.telegram.org/constructor/updateEncryptedChatTyping.html deleted file mode 100644 index 2d9f4955c7..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/updateLoginToken.html b/data/corefork.telegram.org/constructor/updateLoginToken.html deleted file mode 100644 index 530e13e291..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/updateNewMessage.html b/data/corefork.telegram.org/constructor/updateNewMessage.html deleted file mode 100644 index 6f83cd9b99..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/updatePhoneCallSignalingData.html b/data/corefork.telegram.org/constructor/updatePhoneCallSignalingData.html deleted file mode 100644 index 4d9002f9dc..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/updateSavedGifs.html b/data/corefork.telegram.org/constructor/updateSavedGifs.html deleted file mode 100644 index cbe60dbf28..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/updateStickerSetsOrder.html b/data/corefork.telegram.org/constructor/updateStickerSetsOrder.html deleted file mode 100644 index 923edc5436..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/urlAuthResultAccepted.html b/data/corefork.telegram.org/constructor/urlAuthResultAccepted.html deleted file mode 100644 index 0f20c853a5..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/userProfilePhotoEmpty.html b/data/corefork.telegram.org/constructor/userProfilePhotoEmpty.html deleted file mode 100644 index 1f407cb2c4..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/webPageEmpty.html b/data/corefork.telegram.org/constructor/webPageEmpty.html deleted file mode 100644 index 8d73288694..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/method/account.confirmPasswordEmail b/data/corefork.telegram.org/method/account.confirmPasswordEmail deleted file mode 100644 index 6896f20d87..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.getAccountTTL b/data/corefork.telegram.org/method/account.getAccountTTL deleted file mode 100644 index 24af9a816b..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.getAuthorizationForm b/data/corefork.telegram.org/method/account.getAuthorizationForm deleted file mode 100644 index bfdbf6f63b..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.getContactSignUpNotification b/data/corefork.telegram.org/method/account.getContactSignUpNotification deleted file mode 100644 index b6e8ddf4db..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.getSecureValue b/data/corefork.telegram.org/method/account.getSecureValue deleted file mode 100644 index 0f4aead633..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.installWallPaper b/data/corefork.telegram.org/method/account.installWallPaper deleted file mode 100644 index f0b7e35f33..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.setContactSignUpNotification b/data/corefork.telegram.org/method/account.setContactSignUpNotification deleted file mode 100644 index e5d0ee194c..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/auth.acceptLoginToken b/data/corefork.telegram.org/method/auth.acceptLoginToken deleted file mode 100644 index 82a208aa0b..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 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 c9d98c06de..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.checkPhone b/data/corefork.telegram.org/method/auth.checkPhone deleted file mode 100644 index 1fedb983d3..0000000000 --- a/data/corefork.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/corefork.telegram.org/method/auth.sendInvites b/data/corefork.telegram.org/method/auth.sendInvites deleted file mode 100644 index e46a084050..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/channels.editPhoto b/data/corefork.telegram.org/method/channels.editPhoto deleted file mode 100644 index 37d148c7ee..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.getFullChannel b/data/corefork.telegram.org/method/channels.getFullChannel deleted file mode 100644 index 614fdbd2d7..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.togglePreHistoryHidden b/data/corefork.telegram.org/method/channels.togglePreHistoryHidden deleted file mode 100644 index c582f714bf..0000000000 --- a/data/corefork.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/corefork.telegram.org/method/help.getDeepLinkInfo b/data/corefork.telegram.org/method/help.getDeepLinkInfo deleted file mode 100644 index 3f249d3e85..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.getTermsOfServiceUpdate b/data/corefork.telegram.org/method/help.getTermsOfServiceUpdate deleted file mode 100644 index 03c8a7bbcf..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/messages.acceptUrlAuth b/data/corefork.telegram.org/method/messages.acceptUrlAuth deleted file mode 100644 index 0a32cd586b..0000000000 --- a/data/corefork.telegram.org/method/messages.acceptUrlAuth +++ /dev/null @@ -1,179 +0,0 @@ - - - - - messages.acceptUrlAuth - - - - - - - - - - - - - -
- -
-
-
- -

messages.acceptUrlAuth

- -

Use this to accept 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.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;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
flags#Flags, see TL conditional fields
write_allowedflags.0?trueSet this flag to allow the bot to send messages to you (if requested)
peerflags.1?InputPeerThe location of the message
msg_idflags.1?intMessage ID of the message with the login button
button_idflags.1?intID of the login button
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.deleteHistory b/data/corefork.telegram.org/method/messages.deleteHistory deleted file mode 100644 index 6909114f0d..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.editChatAbout b/data/corefork.telegram.org/method/messages.editChatAbout deleted file mode 100644 index 83de438e1f..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.getAttachedStickers b/data/corefork.telegram.org/method/messages.getAttachedStickers deleted file mode 100644 index bd35d0a4c9..0000000000 --- a/data/corefork.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/corefork.telegram.org/method/messages.getChats b/data/corefork.telegram.org/method/messages.getChats deleted file mode 100644 index 57872af905..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.getExportedChatInvite b/data/corefork.telegram.org/method/messages.getExportedChatInvite deleted file mode 100644 index 1fbf7afe2e..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.getGameHighScores b/data/corefork.telegram.org/method/messages.getGameHighScores deleted file mode 100644 index 9f75c72da1..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.getHistory b/data/corefork.telegram.org/method/messages.getHistory deleted file mode 100644 index 8b4b18978e..0000000000 --- a/data/corefork.telegram.org/method/messages.getHistory +++ /dev/null @@ -1,232 +0,0 @@ - - - - - messages.getHistory - - - - - - - - - - - - - -
- -
-
-
- -

messages.getHistory

- -

Gets back the conversation history with one interlocutor / within a chat

-

- -
-
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.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;

-

Parameters

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NameTypeDescription
peerInputPeerTarget peer
offset_idintOnly return messages starting from the specified message ID
offset_dateintOnly return messages sent before the specified date
add_offsetintNumber of list elements to be skipped, negative values are also accepted.
limitintNumber of results to return
max_idintIf a positive value was transferred, the method will return only messages with IDs less than max_id
min_idintIf a positive value was transferred, the method will return only messages with IDs more than min_id
hashlongResult hash
-

Result

-

messages.Messages

-

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.
400CHAT_ID_INVALIDThe provided chat id is invalid.
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.getOnlines b/data/corefork.telegram.org/method/messages.getOnlines deleted file mode 100644 index cf94ef0f16..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.getPinnedDialogs b/data/corefork.telegram.org/method/messages.getPinnedDialogs deleted file mode 100644 index 259ceab9dc..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 1cecfdea6a..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.getSavedGifs b/data/corefork.telegram.org/method/messages.getSavedGifs deleted file mode 100644 index cb09d6eeb5..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.initHistoryImport b/data/corefork.telegram.org/method/messages.initHistoryImport deleted file mode 100644 index 1986edcf57..0000000000 --- a/data/corefork.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/corefork.telegram.org/method/messages.readMessageContents b/data/corefork.telegram.org/method/messages.readMessageContents deleted file mode 100644 index 5b694146d9..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.saveDraft b/data/corefork.telegram.org/method/messages.saveDraft deleted file mode 100644 index 21785cd4ef..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 e156b3ae5c..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.search b/data/corefork.telegram.org/method/messages.search deleted file mode 100644 index 516f3d3bd2..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.searchGlobal b/data/corefork.telegram.org/method/messages.searchGlobal deleted file mode 100644 index 38715911ff..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.setInlineBotResults b/data/corefork.telegram.org/method/messages.setInlineBotResults deleted file mode 100644 index 52cee5df8f..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.toggleStickerSets b/data/corefork.telegram.org/method/messages.toggleStickerSets deleted file mode 100644 index 097b2300fd..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.uploadEncryptedFile b/data/corefork.telegram.org/method/messages.uploadEncryptedFile deleted file mode 100644 index e678a19676..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/payments.getBankCardData b/data/corefork.telegram.org/method/payments.getBankCardData deleted file mode 100644 index ce3a5a2844..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/phone.joinGroupCall b/data/corefork.telegram.org/method/phone.joinGroupCall deleted file mode 100644 index 3ff97aba75..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.saveCallDebug b/data/corefork.telegram.org/method/phone.saveCallDebug deleted file mode 100644 index 2276a8b601..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 2fc02df1ee..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/photos.updateProfilePhoto b/data/corefork.telegram.org/method/photos.updateProfilePhoto deleted file mode 100644 index 5d57909379..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.getMessageStats b/data/corefork.telegram.org/method/stats.getMessageStats deleted file mode 100644 index 2c71f704f7..0000000000 --- a/data/corefork.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/corefork.telegram.org/method/stickers.removeStickerFromSet b/data/corefork.telegram.org/method/stickers.removeStickerFromSet deleted file mode 100644 index 5693156c0d..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/updates.getState b/data/corefork.telegram.org/method/updates.getState deleted file mode 100644 index f94a6ba551..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 dc748058ff..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.getFileHashes b/data/corefork.telegram.org/method/upload.getFileHashes deleted file mode 100644 index 93b025188c..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/mtproto/TL-combinators.html b/data/corefork.telegram.org/mtproto/TL-combinators.html deleted file mode 100644 index 256ddc34a3..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/description_v1.html b/data/corefork.telegram.org/mtproto/description_v1.html deleted file mode 100644 index ca2ed0b856..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/type/BotCommand.html b/data/corefork.telegram.org/type/BotCommand.html deleted file mode 100644 index 18e6d48e04..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/BotInlineResult.html b/data/corefork.telegram.org/type/BotInlineResult.html deleted file mode 100644 index 0892b32709..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/ChannelAdminLogEventsFilter.html b/data/corefork.telegram.org/type/ChannelAdminLogEventsFilter.html deleted file mode 100644 index 66ad938aec..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 = ChannelAdminLogEventsFilter;

-

Constructors

- - - - - - - - - - - - - -
ConstructorDescription
channelAdminLogEventsFilterFilter only certain admin log events
- -
- -
-
- -
- - - - - - diff --git a/data/corefork.telegram.org/type/ChatParticipants.html b/data/corefork.telegram.org/type/ChatParticipants.html deleted file mode 100644 index bf0deff84d..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/ChatTheme.html b/data/corefork.telegram.org/type/ChatTheme.html deleted file mode 100644 index 3ee4671ca4..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/GroupCallParticipant.html b/data/corefork.telegram.org/type/GroupCallParticipant.html deleted file mode 100644 index 582f83cc98..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/InputBotInlineResult.html b/data/corefork.telegram.org/type/InputBotInlineResult.html deleted file mode 100644 index 6efeebab00..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/InputDocument.html b/data/corefork.telegram.org/type/InputDocument.html deleted file mode 100644 index e961301cb9..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/InputEncryptedFile.html b/data/corefork.telegram.org/type/InputEncryptedFile.html deleted file mode 100644 index 334c1abdbf..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/InputNotifyPeer.html b/data/corefork.telegram.org/type/InputNotifyPeer.html deleted file mode 100644 index fefda65d04..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/LangPackLanguage.html b/data/corefork.telegram.org/type/LangPackLanguage.html deleted file mode 100644 index 558054ce25..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 662b745c74..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/MessageViews.html b/data/corefork.telegram.org/type/MessageViews.html deleted file mode 100644 index cd36282935..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/NearestDc.html b/data/corefork.telegram.org/type/NearestDc.html deleted file mode 100644 index 529f8c427d..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/PageBlock.html b/data/corefork.telegram.org/type/PageBlock.html deleted file mode 100644 index c16efd3651..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/PeerSettings.html b/data/corefork.telegram.org/type/PeerSettings.html deleted file mode 100644 index 4892b15b70..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 43d2c20614..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/PollResults.html b/data/corefork.telegram.org/type/PollResults.html deleted file mode 100644 index 794459cf1e..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/ReceivedNotifyMessage.html b/data/corefork.telegram.org/type/ReceivedNotifyMessage.html deleted file mode 100644 index 5a599bf6d1..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/SecureSecretSettings.html b/data/corefork.telegram.org/type/SecureSecretSettings.html deleted file mode 100644 index cb44152b9d..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 7334cf5abe..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 2c4fdda992..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/UrlAuthResult.html b/data/corefork.telegram.org/type/UrlAuthResult.html deleted file mode 100644 index 629c51d00b..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/UserProfilePhoto.html b/data/corefork.telegram.org/type/UserProfilePhoto.html deleted file mode 100644 index 070b8f0aef..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/WebPage.html b/data/corefork.telegram.org/type/WebPage.html deleted file mode 100644 index c52df3d3ad..0000000000 --- a/data/corefork.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/corefork.telegram.org/type/account.ChatThemes b/data/corefork.telegram.org/type/account.ChatThemes deleted file mode 100644 index 1a0fb03f57..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/auth.CheckedPhone b/data/corefork.telegram.org/type/auth.CheckedPhone deleted file mode 100644 index c19a5f1c05..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.SentCodeType b/data/corefork.telegram.org/type/auth.SentCodeType deleted file mode 100644 index 5b90cfea6d..0000000000 --- a/data/corefork.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/corefork.telegram.org/type/channels.ChannelParticipant b/data/corefork.telegram.org/type/channels.ChannelParticipant deleted file mode 100644 index 04d69b365e..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/help.PassportConfig b/data/corefork.telegram.org/type/help.PassportConfig deleted file mode 100644 index d14e291354..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 7f38a15d87..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 b323dbc528..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/messages.AffectedFoundMessages b/data/corefork.telegram.org/type/messages.AffectedFoundMessages deleted file mode 100644 index 2e1318b3d7..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.CheckedHistoryImportPeer b/data/corefork.telegram.org/type/messages.CheckedHistoryImportPeer deleted file mode 100644 index f4ad9390e7..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.HighScores b/data/corefork.telegram.org/type/messages.HighScores deleted file mode 100644 index 3805249fd2..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.SentMessage b/data/corefork.telegram.org/type/messages.SentMessage deleted file mode 100644 index 28e8dc7706..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/phone.GroupCall b/data/corefork.telegram.org/type/phone.GroupCall deleted file mode 100644 index d97d3db25f..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/photos.Photo b/data/corefork.telegram.org/type/photos.Photo deleted file mode 100644 index 00b7adbd86..0000000000 --- a/data/corefork.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/corefork.telegram.org/type/upload.CdnFile b/data/corefork.telegram.org/type/upload.CdnFile deleted file mode 100644 index f3fd928d29..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/instantview.telegram.org/auth.html b/data/instantview.telegram.org/auth.html deleted file mode 100644 index d8257d08eb..0000000000 --- a/data/instantview.telegram.org/auth.html +++ /dev/null @@ -1,294 +0,0 @@ - - - - - Instant View - - - - - - - - - - - -
- -
-
-
-
-
- -
-
-
-
-
-
-
-
- -
-
-
-
-

Instant Views Explained

- -
- -
- -
- -

Instant View allows Telegram users to view articles from around the Web in a consistent way, with zero loading time. When you get a link to an article via Telegram, simply tap the Instant View button, and the page will open instantly.

-

With Instant View, Telegram users can enjoy articles from any mass media or blogs in a uniform and easily readable way. Instant View pages support text and media of any type and work great even if the original website was not optimized for mobile devices.

-

On top of this, Instant View pages are extremely lightweight and are cached on the Telegram servers, so they load instantly on pretty much any connection — hence the name. No more waiting for clunky websites to load, now you can get the good stuff right away!

-

And the best part is that webmasters don't need to change anything on their websites for Instant Views to work.

-
-
- -

Instant View Button

-
-
- -

Instant View Page

-
- -

How does this work?

-

When you share a link via Telegram and a link preview is generated, our Instant View bot also checks if it has an Instant View Template for that website. Templates are sets of instructions we call rules that teach the IV bot to build instant view pages for particular domains or URLs.

-

If a template exists for the link, the bot uses it to find the relevant content on the page (headings, text, media, embedded elements), remove clutter, and create a slim and beautiful Instant View page.

-

Anyone can use our Instant View Editor to create templates. Once a template for a URL is approved by our team, all Telegram users will get the option to view the page in the Instant View format whenever they see a link to it on Telegram.

-

If you publish your content on Telegram yourself, you don‘t even need to wait for us to approve your template. You can just send specially formatted links to your subscribers, and they’ll get Instant View pages built using your template right away.

-

Read More About Publishing Templates »

-

Join buttons

-

Another added bonus if you have a channel is that you can direct users to join your channel from the Instant View pages built from your articles.

-
- -

Join Button

- -

For this to work, the template must contain a channel property that holds a link to your channel. More in the docs »

-

Instant View Editor

-

Telegram's Instant View Editor allows you to create and test templates for any domain. To begin, just go to My Templates, type a target URL for your Instant View template into the box, and hit ‘enter’. This will open the editor. The source page will be displayed on the left.

-
-

Tip: Use the Developer Tools in your browser (e.g. Inspect mode in Chrome) to study the HTML markup of the page.

-
-
-
-
- -

The middle section of the page is where you create your template for the chosen domain name or URL. Templates consist of simple instructions to our IV bot we call rules. You can later study the syntax in detail here. Once you've saved your rules for the page (cmd + S or ctrl + S in the Rules window), the window on the right will display the Instant View page that the IV bot would create based on the current instructions.

-
-

Note the status line at the bottom of the page — it displays the result of the last operation. This is also where you'll find the output of the @debug function:

-
-
- -
- -

Sample templates

-

If you'd like an example, you can check out the exact same templates that we're currently using to generate Instant View pages for posts on Medium, Telegra.ph, and the Telegram Blog. We've added many comments to these templates, so they literally speak for themselves.

-

Feel free to experiment with them and see what changes. Don‘t worry, your changes won’t be applied to the actual Instant View pages that regular Telegram users can see.

-

Templates tutorial

-

When creating an Instant View template, you have four main objectives:

-
    -
  • Instant View pages must only be generated for pages that need them.
  • -
  • All essential content from the source page must be represented.
  • -
  • All unnecessary elements must be eliminated from the Instant View page.
  • -
  • Your template must work well with any of the pages it covers.
  • -
-

Accordingly, one of the ways to create a template is to follow these steps:

-

Step 1. Aim your template

-

Instant View pages work best with relatively static articles. On the other hand, the main page of a news site that contains ever-changing lists of links to new articles would hardly benefit from the IV treatment.

-

For the first step, you will likely use conditions to clearly define which parts of the target website will and will not be covered by your template.

-

Step 2. Grab the essentials

-

Now it's time to do some real business. An Instant View page requires at least two properties to be created: a title and a body. Take a close look at the target article and make sure that all important elements are carried over to the IV page in a format supported by the Telegram apps.

-

At this stage, you may need to use functions to transform some elements before they are transferred. By the time you're done, your IV page should show the entire text of the article, along with all the headings and subheadings, quotes, cover and other photos, videos, and other kinds of embedded content from the source page.

-

Step 3. Remove the rest

-

Salvage the remaining useful bits, then use the @remove function to drop the rest. By now you should have a clean and slim IV page that displays the pure content and none of the fluff.

-

Step 4. Refine your template

-

At this stage, we advise you to leave the familiar confines of the page you were using for testing and check out different pages from your target website. See if any pages that don't deserve IVs are getting them — and whether IV pages are missing for any that do deserve them.

-

Also, check whether pages with irregular elements are processed correctly. Pay special attention to ensure that various types of media, embedded content, quotes, and separators are all displayed nicely. Check 5-10 different links and make the relevant adjustments.

-
-

See also: Our Perfect Template Checklist »

-
-

Naturally, this is just a brief outline of what you could do — Instant View pages offer limitless possibilities.

-

Tracking changes

-

Once you're satisfied with your template's generated IV pages, press the Track Changes button. If modified template rules are subsequently applied, they can now be checked across all applicable IV pages within the system.

-
- -

Track Changes

-
- -

After Track Changes is enabled, editing your template will not immediately check for changes across all pages. Instead, when you're happy with the currently generated IV page, and no warnings are shown, click Mark as Checked to see if your changes broke anything on the other IV pages impacted by your template.

-
- -

Pages Modified

- -

If any changes are detected, the status line will display the difference and the result:

-
- -

Changes Detected

- - -
-

Take care that your changes don‘t break pages that already had good IV pages. There’s a handy indicator at the top of the page that shows the status of the pages relevant for your template. As long as it's green, everything's fine.

-
-

Publishing templates

-

If the Instant View page has been processed successfully, you'll see a View in Telegram button in the top right corner – you can use it to view the resulting page in-app.

-

For your own audience

-

Note that if you send the resulting t.me/iv?url=...&rhash=... link to other Telegram users, they will see an Instant View page built using your template (the rhash parameter in the link determines which template is used to create the page). This means that, as a website owner, you can create a template for your page and publish t.me/iv?url=... links with the corresponding rhash to your Telegram channel — and your subscribers will be able to view your articles in the Instant View format right away.

-

For all Telegram users

-

If you'd like your template to become truly public and seen by all users, regardless of the link they get, the template will need to be approved by the Telegram team.

-
-
-

And that‘s it, you’re now ready to move on to the full instant view documentation.
Don't forget that you can also check out our annotated sample templates.

-
-
- -
-
-
-
-
- - - - - - - - - - - - - - diff --git a/data/instantview.telegram.org/checklist.html b/data/instantview.telegram.org/checklist.html deleted file mode 100644 index 384015f0df..0000000000 --- a/data/instantview.telegram.org/checklist.html +++ /dev/null @@ -1,624 +0,0 @@ - - - - - Checklist – Instant View - - - - - - - - - - - - - - -
- -
-
-
-
-
-
- -
-
-
-
-
-
-
-
-
- -
-
-
-
-

A Guide to Good Templates

- -
- -
- -
- -

This page lists general rules and detailed clarifications for creating good Instant View templates for news articles.

-

For more info on templates, see our Introduction and Sample Templates.

-

General Rules

-

Instant View templates must meet these five basic requirements:

-

1. IVs must only be generated for pages that need them

-

Instant View pages work best with relatively static articles. Dynamic pages (such as the main page of a news site) that are constantly refreshed with new links and media don't need IV.

-

Templates should only generate IV pages for articles and should not affect service areas of websites, as well as any other sections unsuitable for IV. IV pages should not be generated for articles that have content which is not supported in IV since this would result in unacceptable loss of information (e.g., IV pages don't support dynamic maps — if you generate an IV page for a wiki article with a dynamic map, the IV version will be missing a key element).

-

2. All essential content must be preserved

-

IV pages should show the entire text of the article, along with all its formatting, media, and embedded content. This includes headings, subheadings, quotes, captions, photos, videos, links, etc.

-

3. Unnecessary elements must be removed

-

IV pages should display only the source’s content – removing all interface elements, advertisments and irrelevant embedded material.

-

4. Template must process all the pages it covers

-

Pages with irregular elements should be processed correctly. All media, embeds, quotes and separators should be properly displayed.

-

5. No extraneous info may be added

-

Any attempt to add content that is not present on the original page will cause your template to be rejected.

-

You may include the username of websites’ official channels in Instant View templates. The username is assigned to the channel property, and to be considered official, the channel must be labeled as such by the company or person who published it (on its website or social media).

-
-

More detailed criteria and clarifications are available below.

-
-
-

Submitting Templates

-

You can submit your template for review as soon as it covers a sufficient number of articles. Make sure you've enabled Track Changes for at least 10-15 different pages on the target website and that all IV pages are generated correctly.

-

When ready, simply tap Submit Template next to a template in the My Templates section:

-
- -

Submitting a template from My Templates

- -

Finding Issues

-

Anyone can check how well Instant View templates process articles on their respective websites, and may submit feedback using the Report Issue button.

-

Click to select and highlight incorrectly parsed blocks in the source page or in the Instant View result and provide a detailed explanation of what is wrong (check the criteria below for ideas). The author of the template will be able to see all issues, fix and resubmit their work.

-
-

Perfect Templates

-

To make it easier to report issues in Instant View templates, we’ve compiled this list of characteristics that make a perfect template. Please use the list below as a reference when looking for issues in templates.

-

1. IV Targets: Must Generate

-

Templates must generate Instant View pages for all relevant pages on the target website.

-

1.1. Pages with static article-like content

-
    -
  • News articles
  • -
  • Blog posts
  • -
  • Guides
  • -
  • Wiki entries
  • -
  • Documentation
  • -
  • Etc.
  • -
-
-

Tip: It may be a good idea to identify a common feature of all the IV-positive pages and add rules so that the template only applies to them. Note that these pages only need IV pages if their essential content is supported in the IV format — otherwise, see 2.3.

-
-

2. IV Targets: Must NOT Generate

-

Templates must not generate Instant View content for pages of the following types:

-

2.1. Pages with dynamic content

-
    -
  • Dynamically updated lists of articles
  • -
  • Catalogs
  • -
  • Forum threads
  • -
  • Search pages and search results
  • -
  • Etc.
  • -
-
-

Tip: IV pages are cached. As articles get older, their cached IV pages update less frequently. Any pages that update content in real time would subsequently display outdated IV pages to users — which is unacceptable.

-
-

2.2. Pages that require significant interaction

-
    -
  • Service areas of websites, such as Contact pages with forms
  • -
  • Store areas of websites, such as pages where users can buy products
  • -
  • Etc.
  • -
-
-

Tip: While it's possible to modify interactive components of a page into simple links, the IV format was primarily designed to allow Telegram users to enjoy web content in a quick and uniform way. Interacting with websites, buying things, writing reviews, etc. are outside of the current scope for IVs.

-
-

2.3. Pages featuring content not supported by the IV format

-
    -
  • Pages with unsupported embedded content that can't be displayed
  • -
  • Any other unsupported content
  • -
-
-

Tip: The rule is simple. If an essential part of an article is not available in the Instant View format, an IV page must not be generated. In most cases, this will happen automatically but template creators can further protect their templates from data loss by marking any unsupported essential content using the @unsupported function. See this section for advice on handling unsupported videos.

-
-

2.4. Inaccessible pages

-
    -
  • Pages that are fully or partially behind a paywall.
  • -
  • Pages that are only accessible after logging in, etc.
  • -
-

3. Essential Content

-

All essential content must be presented on the Instant View page.

-

3.1. General properties

-
    -
  • The title must be shown on the IV page (may need to include the kicker).
  • -
  • The subtitle must be shown on the IV page if a subtitle exists in the source.
  • -
  • The date of publication must be shown on the IV page if the date of publication is mentioned anywhere in the source (including meta tags).
  • -
-

These properties are also essential, but not always present or supported in IV:

-
    -
  • Author name can be shown on the IV page if an author is specified in the source.
  • -
  • Author name on the IV page can link to the author URL if an author URL is specified in the source.
  • -
  • The main image can be shown as a cover on the IV page if a suitable image exists in the source.
  • -
  • NEW Right-To-Left pages (Arabic, Persian, Hebrew, etc.) must have the dir="rtl" attribute set.
  • -
-
-

Important: See our Clarifications below for tips on how to best process cover images, date and time, author names and URLs, and other tricky elements.

-
-

3.2. Link preview

-
    -
  • The link preview must include a photo if a suitable image or document exist in the source.
  • -
  • If the page has a cover but the metadata contains no image or contains the generic site logo, you must use the cover as the photo.
  • -
  • The link preview requires a description.
  • -
  • If a short description exists in the source, it must be used for the link preview (OpenGraph descriptions, lead sections, etc.).
  • -
  • If the description in the metadata (routinely) doesn’t describe the contents of the article, your template must create a description using the subtitle or lead section, first paragraph, etc.
  • -
  • The site_name property must include the name that users see on the main page of the website (examples here).
  • -
  • It is advisable to generate proper link previews even for pages that do not generate an IV.
  • -
-
-

Note: Telegram apps will show site_name in the header of the IV. It must match the name that users see on the main page of the website (see examples) and it must not contain any additional data. For this reason metadata should not be used blindly. If the main page doesn’t display a site name, use the name they use on social networks (Telegram channels have priority).

-
-

3.3. Supported elements

-
    -
  • All important media (images, videos, slideshows, and other content that is relevant to the article) that exists in the source must be formatted accordingly.
  • -
  • Media captions must be included with the corresponding media, provided they exist in the source and can be reliably identified.
  • -
  • Credits in quotes and media captions must be formatted correctly.
  • -
  • Dividers must be converted to simplified dividers on the IV page if dividers exist in the source.
  • -
  • Anchor links must work properly on IV page if anchor links exist in the source.
  • -
-
-

Tip: Check that pages featuring unsupported content do not generate IV pages. In most cases, this will happen automatically, but it is a good idea to confirm this before submitting your template. Mark any unsupported essential content using the @unsupported function. See this section for advice on handling unsupported videos.

-
-

4. Content to be Removed

-

Anything that is not essential to the article in question should be removed from the Instant View page, including:

-
    -
  • Main navigation bars and menus (essential navigation may be adjusted to simple links)
  • -
  • Top bars
  • -
  • Side bars (can potentially be adjusted and appended to bottom of IV page)
  • -
  • Footers
  • -
  • Unsupported widgets (check supported embeds)
  • -
  • Advertisements
  • -
  • Banners
  • -
  • Social media links and buttons, including “Share” and “Like”
  • -
  • Other buttons (if it is essential, it must be simplified into a link)
  • -
  • Etc.
  • -
-

5. Extraneous Content

-

The resulting IV page may not contain any content not present in the original.

-
    -
  • No signatures or information about the template's author
  • -
  • No extra links or ads of any kind
  • -
  • Etc.
  • -
-
-

Tip: You may display the official Telegram channel of the website that published the article at the top of the IV page (by using the channel property). To be considered official, the channel must be labelled as such somewhere on the source website (doesn't have to be on the same page as the original article).

-
-

6. Clarifications

-
-

Below are some clarifications for the trickier aspects of creating perfect Instant View templates.

-
-

GENERAL PROPERTIES

-

6.1.1 Author name

-

Author name is required only if it is presented in the source article in a consistent, clear and identifiable way (in an html block with particular properties), especially if there's a name of an actual person.

-

In less obvious cases, what the user sees when viewing the original article in a browser has priority over invisible meta-information. Names of actual people are always preferable over entity names like 'team' or the name of the website.

-

You may omit the author in cases where no name can be seen by a regular user opening the original article in the browser. You may omit the name when there's no identifiable person, only the website's 'team', 'editors', 'website name' etc.

-

Absent author names for articles in which no author can be easily identified by a regular viewing user are not considered an issue.

-

6.1.2 Date and time

-

The date of publication is obligatory for news publications. It must be obtained by any means possible, including meta tags, etc. If the date is specified correctly, time is optional.

-

If conflicting dates are stored in multiple places on the source page, preference should be given to the time that is visible to an ordinary user who views the page in a browser.

-

The IV editor's 'Preview' section will always show the date/time in UTC format, while the 'Original' section may use a different time zone. It is possible for a perfect template to display a date/time that looks different than the original.

-

Support for time zones is optional, unless the time zone is reliably identifiable from the source, in which case it’s obligatory.

-
-

Tip: If given 'date published' and 'date last edited', use 'date published' for articles. For wiki-like entries 'date last edited' must be used.

-
-

6.1.3 Subtitle

-

A subtitle is a subordinate title of a published work or article giving additional information about its content. If this is present in the original article, a subtitle is required. Here's an example of a subtitle:

-
- -

A Subtitle

-
- -

Few publications actually use subtitles. More commonly, short summary sentences are shown below the title (and are called standfirst in the UK). These summary sentences are usually short and are not part of the article's text. It is advisable but not required to represent them as subtitle elements. Here's an example:

-
- -

A Summary

- -

6.1.4 Lead paragraph

-

Many publications use a slightly different style for their lead paragraphs. Unlike subtitles and summaries, the lead paragraph is part of the article's text. Even if the lead uses a different style from the rest of the text, it is less desirable to present it as a subtitle — but this is not a critical issue.

-

If the lead paragraph uses a different style, it is recommended to use bold or italic text.

-
- -

A summary, then lead in bold

- -

In the example above, the lead paragraph is highlighted in bold: “TAXI giant Uber has reportedly fired over 20 workers following an internal investigation into sexual harassment allegations.”

-

The article then continues: “The company told staff of the layoffs on Tuesday and related claims by law firm Perkins Coie, a person close with the case told Bloomberg.” It would be acceptable to present the “TAXI giant Uber…” paragraph as bold, or italic, or plain text.

-
-

Tip: Generally, it is advisable to avoid setting too much text as the subtitle. If the website publishes summaries that take an entire paragraph or even multiple paragraphs, it's better to use italic/bold text instead of the subtitle element to represent this content in IV.

-
-

6.1.5 Kicker

-

Kickers are separately formatted parts of the title supported in IV 2.0 with the kicker property. The kicker property must be set if a kicker is present and its text is actually a part of the title/story (see 'UBER SEX CLAIMS' on the screenshot above).

-

If the kicker represents a regular section or category into which the article falls, (e.g. 'CRIME: Seventy suitcases stolen from Heathrow airport'), it should be omitted. Missing section/category kickers are not considered an issue.

-

IMAGES AND MEDIA

-

6.2.1 Image quality

-

When several image resolutions are available and can be extracted reliably, the IV page should use better quality images (within reason). The optimal resolution range is 1280px-2560px, using larger images is pointless. Note that images that are too large (>5 MB) will fail to load. We recommend updating your template to IV 2.1 to automatically extract optimal images from the srcset attribute.

-

If for some reason it is only technically possible to obtain low-resolution versions of images (lower than 320px) for a page, but its original web version has high-resolution images, the page should not generate an IV.

-
-

Note: For the Icon type, we highly recommend setting the correct size using the width/height attributes so that they appear the same way in IV as they do in the text. Otherwise, you risk grabbing the 3x version of an emoji and displaying it as a full-blown image.

-
-

See also: Infographics

-

6.2.2 Cover images

-

It is obligatory to use a cover image:

-
    -
  • If the image is present on the page and described in the source as “featured-img”, “cover”, “lead_img”, “main_image”, etc.
  • -
  • When the article has a cover on the source website (above the title or subtitle).
  • -
-

In other cases, cover images are optional:

-
    -
  • We recommend setting a cover If there's a suitable image directly below the title/subtitle.
  • -
  • While it is possible to use GIFs and videos as cover, in most cases, it's better to leave these elements in the body of the article.
  • -
-

Sometimes, a cover is less desirable:

-
    -
  • In single-image, single-video, or single-GIF articles with no significant text.
  • -
  • When text on the cover image repeats the title.
  • -
  • Images from meta-tags are not recommended: they might be suitable, but are usually designed with sharing widgets in mind and don’t work well in the IV environment.
  • -
-

A cover must not be set if:

-
    -
  • The chosen image is clearly inappropriate for the cover.
  • -
  • The chosen image appears several paragraphs into the article and it is possible to reliably identify this.
  • -
  • The cover image is duplicated in the article.
  • -
  • Several images appear in the article one after another. In this case, the template should not break the sequence by extracting one of them as a cover (example).
  • -
-
-

Tip: Cover images can also have captions in IV, don't lose them.

-
-

6.2.3 Galleries and slideshows

-

Slideshows are required only if the source article shows several photos or other media as a slideshow or gallery. If this is the case, do the following:
- Present all images in the IV as a gallery, if possible.
- If that's not possible, keep a link to the full gallery.
- If none of the above are possible, generate no IV for the page.

-

If the source has several ordinary images/videos/GIFs following each other in the source, you may also convert them into a slideshow, but this is purely optional. This makes more sense in cases when images serve as additional content (e.g., a long text about a new car which is followed by ten images of the car).

-

We will not accept issue reports based on presence or absence of slideshows for ordinary images following each other in the source article.

-

EXCEPTION! Slideshows must not be used when:

-
    -
  • The slideshow fetches unrelated images (e.g. an illustration and a disclaimer).
  • -
  • The article consists entirely of a slideshow (and its caption/description) and there's no other content.
  • -
  • The article uses images/videos/GIFs with captions as the main medium (e.g.: travel blogs that show many photos with captions, step-by-step crafting guides, cooking recipes, etc.).
  • -
-

In the cases above, use images with captions (or even plain paragraph text) following one another.

-
-

Tip: Remember that captions should be preserved for all images in the source. If you lose captions for images you've put into a slideshow, it's a valid issue. IV Slideshows support both a caption for the entire slideshows and different captions for each individual element.

-
-

6.2.4 Captions

-

Any captions present in the source article must be preserved. This includes captions for the cover image and captions for all individual elements of slideshows.

-
- -

All Captions Preserved

-
- -

If the image has no caption, but has meaningful text in the alt attribute, you may use that text as the caption. This is optional, we will not accept issue reports about alt-text missing from captions.

-
-

Tip: Please don't include meaningless alt-text as captions (e.g., the PlayStation blog always puts the name of the corresponding game in the alt attribute of all screenshots – there's no need to reproduce that on the IV page.)

-
-

6.2.5 Media credits

-

IV 2.0 supports a dedicated <cite> tag for credits in media captions. Credits in captions must be preserved and placed inside the appropriate tag, provided it is possible to reliably identify them.

-

6.2.6 Infographics

-

Tall infographic images are currently unreadable in Telegram apps. If there’s a reliable way to identify them (e.g., consistently used attributes or a specific section on the website that only contains infographics) the IV must add an image link to the full version of the image. If there is no reliable way to identify such images and they are not consistently featured on the website, it is acceptable to leave infographics as ordinary photos.

-

LINKS

-

6.3.1 Image links

-

In IV 2.0, <img> tags support the attribute href to make the image clickable. It must be used to preserve the link behind the image if it leads to some different page or content.

-

Image links are required only if they are meaningful. If the link opens the same image in a higher resolution, it must be removed. Exception: Infographics.

-

6.3.2 Related Articles and other “More” links

-

IV 2.0 supports a dedicated type for RelatedArticles. Related articles are relatively static individual links or blocks of articles which are thematically related to the current one. They don't have to be located on the same domain.

-

It is obligatory to format “Related articles” links using the new <related> tag and/or remove other “More” links, provided all these links can be extracted from the article without endangering essential information.

-

We designed the RelatedArticles block to deliver a better IV-reading experience to users. The IV engine automatically checks whether articles in the <related> block have an IV, you don't need to worry about this.

-
-

If pages have no IV, they will not be displayed. If this results in an empty block, it will not be displayed.

-
-

There are cases when you must not use RelatedArticles:

-

1. Keep but don’t format as Related

-
    -
  • Links that can’t be safely and reliably extracted from the article text.
  • -
  • Links that are part of essential content for the article (without which the article makes no sense).
  • -
  • Navigational links to the other parts of multipart articles.
  • -
-
-

Never put essential links into <related>, they will be lost if the page they are leading to doesn’t have an IV.

-
-

2. Remove

-
    -
  • “More” blocks that show different links each time the page is reloaded.
  • -
  • (Consistently) random unrelated articles.
  • -
  • Dynamic lists of "Latest articles from this category”, “More articles by this author”, “Featured articles”, etc.
  • -
  • Lists of categories (links to dynamic lists).
  • -
  • External links leading to “Partner sites” (e.g., You won't believe what this game does to people!).
  • -
-

6.3.2.1. Formatting Related Articles

-

It is sufficient to put links into <related>. You only need the <a> – the IV engine will handle the rest (title, description, etc.). Your IV may only have one block of related articles at the end of the page. If the source has several blocks, merge them together or choose which one to keep.

-

Headers
Only one header may be present for the block of related articles at the end of the page. We will not accept reports about missing headers on Related blocks (unless the header contains critical information).

-

Note that if a header for a related article is not reliably extractable from the body, you must not use <related> for that link. (Otherwise, if the link gets no IV, the text will have a hanging header).

-

“Inline” blocks
You may leave “inline” related links in the middle the article. If you do, these <related> blocks must not have headers (unless the header contains critical information).

-

6.3.3 Channel links

-

You may display the official channel of the website that published the article on the IV page by using the channel property:

-
- -

Official Channel Link

-
- -

This channel link is optional. We will not accept issue reports based on the absence or presence of a channel link, with one exception:

-

If the channel property is set, the channel it is pointing to must be the official channel. To be considered official, the channel must be labelled as such somewhere on the source website (doesn't have to be on the same page as the original article).

-

6.3.4 Source links

-

Some articles include a link to their source. This link could be inserted at the end of the article in the format via <a href="https://example.org">Website Name</a>. A word with a similar meaning could be used instead of 'via' for websites in other languages.

-

6.3.5 Author links

-

Author links are optional. If there's a clearly identifiable author and they have a page on the target website, use that one. In more ambiguous cases, use what the regular viewing user can see in the original article or omit the link altogether.

-
-

Tip: IV only supports one author URL per article. If there are several in the article, it's permissible to choose one or omit them altogether.

-
-

6.3.6 Social media links

-

Sharing buttons and other interface-based links must be removed as per Rule 4.

-

Many articles include something like “check out our Facebook page” at the end of the text. Such links must be removed if they are placed in a reliably identifiable container.

-

6.3.7 Multi-page articles

-

To parse several pages into one IV, update your template to IV 2.1 (which skips canonical redirects by default) and use the inline function. Make sure to check in-app to see if your solution is working. The IV should open correctly when users share a link to any part of the article.

-

If pages can’t be safely assembled into one IV, navigation must be preserved. Please confirm that navigation is working and all further pages open correctly. If navigation can’t be preserved, the article must not generate an IV.

-

Never format links to the other parts of an article as related. This may break navigation if one part of the article fails to generate IV (since related articles without IVs are omitted in the block).

-

UNSUPPORTED CONTENT

-

Pages that display unsupported content (e.g. an interactive map widget) must not generate IVs.

-

Important: We will accept issue reports requesting to generate IVs for pages with content previously deemed unsupported if you include a link to a template that fully supports the content in question. This does not apply to supporting content from popular widgets that are likely to get official support in the future, see the list below.

-

6.4.1 Complex tables

-

IV 2.0 includes support for Tables. IVs can now be generated for articles with simple tables. However, complex tables may not render through existing means, and must be tagged as @unsupported.

-

Important: We will accept issue reports requesting to generate IVs for pages with content previously deemed unsupported if you include a link to a template that fully supports the content in question.

-

6.4.2 Video/Audio from unsupported players

-
    -
  • If the unsupported widget has an iFrame version, make it into an <iframe>. If you do that, the IV page will not be generated due to unsupported content, but things will work out of the box if and when we support that widget.
  • -
  • If it is not possible to represent the widget as an iFrame, but it is possible to get a direct link to the video/audio, use that link to generate a <video> or <audio> with the correct src attribute.
  • -
  • Otherwise, mark the object with the @unsupported function.
  • -
-
-

If an article that is otherwise supported includes a video or an audio track that would cause it to become unsupported, it is acceptable to include a link to the video instead of unsupporting the article. If there’s no other content on the page, it must not generate an IV.

-
-

6.4.3 Auxiliary widgets

-

Some pages include unsupported widgets that are not essential for the understanding of the article. A local news site may show a weather forecast widget on their pages. A business newspaper may show a stock price ticker for the companies covered in the article. Some websites include “And what would you do?” polls at the end of some of their articles to increase user engagement.

-

Such non-essential widgets may be omitted in IV. Warning: Make sure that this dynamic auxiliary data doesn't get added to the static IV page.

-

6.4.4 Popular Widgets

-

Telegram is likely to support the following popular widgets in the future:

-
    -
  • Reddit
  • -
  • Spotify
  • -
  • Getty images
  • -
  • Imgur
  • -
  • Coub
  • -
  • Soundbank
  • -
  • JW Player
  • -
  • Twitter Timeline
  • -
  • Infogram
  • -
  • VK Post
  • -
  • WordPress Embed Post
  • -
  • Yandex.music
  • -
-

Supporting content from these widgets is optional since it will eventually become available through official means.

-

OTHER

-

6.5.1 Subdomains

-

Subdomains that present content in a similar way to the higher-level domain must be supported.

-

If a subdomain looks like a separate website, supporting it is optional. We will accept issue reports if a template generates broken IV pages for any subdomain.

-
-

Note: We will add the necessary redirects so that Telegram apps will show IVs for articles on the main domain when users share links to the mobile version. It is not necessary to support pages from the mobile version.

-
-

6.5.2 Service areas

-

Non-article pages are strictly optional, unless there’s interactive content – in which case they must not generate IVs. This includes Terms of Service, Privacy Policies, About sections, Contacts sections and special “Print” versions of articles.

-

6.5.3 Single-media pages

-

Support for pages that only contain a single media item (photo, GIF, video, etc.) is required if:

-
    -
  • The pages are routinely accessible to users through the main navigation of the website and include other data like title, date, etc.
  • -
  • Such pages are the main medium for the domain in question (e.g. Pikabu.ru)
  • -
-

If the single-media page contains unsupported media, it must not generate an IV. See 6.4.2 Unsupported Video and Audio content.

-

In all other cases, supporting single-media pages is optional.

-

6.5.4 Ancient lore

-

Support for news articles from 2015 and earlier is optional. We won’t accept issue reports on news articles posted before 2016 if the template correctly handles articles published recently.

-

6.5.5 Quotes

-

Quotes must be formatted to match their appearance in the source article, provided it is possible to identify them (and their type) in a reliable way. Line breaks in quotes must be preserved.

-

Quotes support <cite> tags. If a quote includes an author, it must be formatted accordingly (provided the author can be reliably identified in the source).

-
-

7. Checklist Changelog

-

We will be updating this document with further clarifications as new issues arise.

-

Mar 20 2019

-
-

Don’t miss the IV 2.1 update.

-
-

Checklist 2.2:

-

Expanded clarifications

-
    -
  • 3.2, Link Preview: site_name must include the name that users see on the main page of the website; cover photo must be used in preview if metadata is empty or contains site logo; template must generate proper description if metadata is unsuitable
  • -
  • 3.3, Supported Elements: Credits must be supported in media captions and quotes
  • -
  • 6.1.2, Date and Time: Time is optional if the date is set correctly; time zones are optional, unless reliably identifiable in the source
  • -
  • 6.2.1, Image Quality: for issues to be accepted, the difference in image quality must be significant; higher resolution images must be reliably extractable; note
  • -
  • 6.3.1, Image links: Must be preserved if they are meaningful
  • -
  • 6.3.2, Related articles: Details on when RelatedArticles must not be used; Formatting guidelines
  • -
  • 6.4, Unsupported content: Optional to extract content from popular widgets which are scheduled for official Telegram support, even if another template does this
  • -
  • 6.4.2, Unsupported Video/Audio: Possible to include a link to an audio/video instead of unsupporting an otherwise fine article
  • -
  • 6.5.1, Subdomains: Added a note on mobile versions
  • -
-

Added NEW clarifications

- -
-

Feb 6 2019

-

Checklist 2.1

-
    -
  • Related Articles (6.3.2). Considerably expanded guidelines. Now obligatory to put related links into the new “Related articles” block, provided they are reliably identifiable in the source. Other links should be removed, see full details.
  • -
  • Cover Images (6.2.2). Added conditions when covers are obligatory.
  • -
  • Galleries and Slideshows (6.2.3). Added detailed explanations on gallery usage.
  • -
-
-

Feb 2 2019

-

Checklist 2.0: Changes for the Second Instant View Contest

-

The Clarifications section has been rewritten to better organize the lore we've accumulated during and after the previous contest. These clarifications have been updated:

-
    -
  • Tables are supported (if they are not too complex).
  • -
  • Nested lists (and lists inside tables) are supported.
  • -
  • RTL-support has been introduced and is obligatory for RTL pages.
  • -
  • Related Articles got a dedicated element (UPDATED 6.02, see guidelines!).
  • -
  • Image links are supported.
  • -
  • Added guidelines on image quality.
  • -
  • Updated guidelines for cover images
  • -
  • The new Icon type requires careful handling.
  • -
  • Media credits can be formatted properly (if separable from caption).
  • -
  • Kickers in titles got a dedicated element for certain cases.
  • -
  • Added guidelines for supporting subdomains.
  • -
  • Updated guidelines for social media links
  • -
  • Updated the guidelines for site_name in link previews.
  • -
-

Don't forget to check out what's new in IV 2.0 to know what your templates are now able to support.

-
- -
-
-
-
-
- - - - - - - - - - - - - - diff --git a/data/promote.telegram.org/basics.html b/data/promote.telegram.org/basics.html deleted file mode 100644 index c2247a9bbf..0000000000 --- a/data/promote.telegram.org/basics.html +++ /dev/null @@ -1,204 +0,0 @@ - - - - - Telegram Ads - - - - - - - - - - - - - - - - - - - - - - - -
- -
-
-
- -
-
-

Telegram Ad Platform

- -

Telegram provides a free and secure messaging service for more than 500 million monthly active users around the world. In addition to sending private messages and chatting in private groups, Telegram users can subscribe to public one-to-many channels.

-

Every month, Telegram users generate over 500 billion views in one-to-many channels.

-
- -
- -

-

Advertising on Telegram

-

Sponsored messages on Telegram are displayed in large public one-to-many channels with 1000+ subscribers and are limited to 160 characters. Sponsored Messages are based solely on the topic of the public channels in which they are shown.

-

This means that no user data is mined or analyzed to display ads, and every user viewing a particular channel on Telegram sees the same sponsored messages.

-
- -
- -

Context-based advertising

-

Advertisers can choose the language and approximate topics of channels where their ads will be displayed. It is also possible to choose specific channels where a certain ad will be shown – or add specific channels where it will not be displayed.

-

This allows advertisers to serve precise and efficient ads while preserving user privacy.

-

Privacy-conscious ads

-

Unlike other apps, Telegram doesn't track whether users tap on a sponsored message and doesn't profile them based on their activity. We also prevent external links in sponsored messages to ensure that third parties can’t spy on our users. We believe that everyone has the right to privacy, and technological platforms should respect that.

-

Revenue sharing with channel owners

-

Sponsored Messages are currently in test mode. Once they are fully launched and allow Telegram to cover its basic costs, we will start sharing ad revenue with the owners of public channels in which sponsored messages are displayed.

-

Getting started

-

Telegram welcomes all responsible advertisers. Anyone can study Telegram's Ad Policies and Guidelines, create an account on the Ad Platform and try out the interface. For a detailed overview of the platform, see this guide.

-

-
- -
-
- -
-
-
-
- - - - - - - - - - - - - - - - diff --git a/data/telegram.org/api.html b/data/telegram.org/api.html deleted file mode 100644 index 5b31e53dd8..0000000000 --- a/data/telegram.org/api.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/blog.html b/data/telegram.org/blog.html deleted file mode 100644 index be6d9f1229..0000000000 --- a/data/telegram.org/blog.html +++ /dev/null @@ -1,268 +0,0 @@ - - - - - Telegram Blog - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
-

Telegram News

-
-
- -
-

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
-
- -
-

Coronavirus News and Verified 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…
-
-
Apr 3, 2020
-
- -
-

Chat Folders, Archive, Channel Stats and More

-
Many of our users rely on Telegram for their work and studies, even more so in the last weeks. To make sure everyone's chat lists can handle…
-
-
Mar 30, 2020
-
- -
-

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…
-
-
Feb 13, 2020
-
-
- -
- -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/400-million.html b/data/telegram.org/blog/400-million.html deleted file mode 100644 index 7edcd1286a..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/6-years.html b/data/telegram.org/blog/6-years.html deleted file mode 100644 index f25f33c876..0000000000 --- a/data/telegram.org/blog/6-years.html +++ /dev/null @@ -1,1355 +0,0 @@ - - - - - Celebrating 6 Years of Telegram - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Celebrating 6 Years of Telegram

- -
- -
- -

We launched Telegram 6 years ago, on August 14, 2013 – and immediately set to work on the next update. That‘s how it’s been ever since.

-

After a little while we noticed that our work not only brings progress to Telegram – but also results in the evolution of messaging as a whole. It is heartwarming to see our solutions and design decisions adopted as de facto standards across the board.

-

To keep you entertained while we‘re working on this month’s second update, we've compiled a brief history of Telegram. It ended up rather on the ‘humongous’ side of ‘brief’ – but it's not like the next update is tomorrow either. So read on.

-

Oh, and if you want to give us a gift, bring two of your best friends to Telegram today.

-
-
- A poster celebrating 6 years of Telegram -
- -

A (Not So) Brief History of Telegram

-

For some reason, we started writing this backwards – from the latest update to the primordial summer of 2013. And then it was too late to change the order because the guy who compiled the post said he would go on a hunger strike if we tried.

-

So if you're a fan of chronology, please jump to the end and scroll up from there. (By the way, we decided we're going to keep this post up to date as new updates arrive.)

-

September 2019

-

Scheduled Messages, Reminders, Custom Cloud Themes and More Privacy

-

The end of summer brought scheduled messages and reminders to better keep track of important tasks and appointments. On the visual side, shareable Custom Cloud Themes came to all platforms, along with more animated emoji.

-

An important privacy option was added for those who need it most – Who Can Find Me By My Phone Number. This new setting can prevent random users (or government organizations) from being able to match a number from their device's contacts to your Telegram account.

-

On Telegram since September 2019:

- -

August 2019

-

Silent Messages, Slow Mode, Admin Titles and More

-

The August update brought a way to send silent messages – which result in a notification without sound. We also added custom titles and a slow mode for group admins. But you probably remember this, it's only been a week.

-

Following the success of animated stickers, this update also introduced animated emoji for ❤️, 👍, 😒, 😳 and 🥳. More followed.

-
- TITLE -
- -

On Telegram since August 2019:

- -

July 2019

-

Animated Stickers Done Right

-

The July update introduced animated stickers. We managed to achieve a smooth 60 FPS at just 20-30 KB per sticker. Animated stickers consume less bandwith than static ones and less battery than GIFs, while commanding more attention than the two combined.

-

Here are some sample animated sets in case you missed them: Hot Cherry, Tidy Tie Tom, Resistance Dog, Fred the Pug, Melie the Cavy, Earl the Wolf, Egg Yolk

-

These stickers are powered with uranium and dreams and are guaranteed to keep going forever.

-
- TITLE -
- -

On Telegram since July 2019:

- -
-

June 2019

-

Location-Based Chats, Adding Contacts Without Phone Numbers and More

-

The June update focused on making it easier to add people to contacts. A universal Add button was introduced to all new chats, making it possible to add users to contacts even if you don't know their number yet.

-

A new Add People Nearby section was created to quickly exchange numbers with people close to you. The new section also allows creating location-based public chats.

-
- TITLE -
- -

On Telegram since June 2019:

- -
-

May 2019, Second Update

-

Focused Privacy, Discussion Groups, Seamless Web Bots and More

-

The second May update made Telegram Privacy Settings even more flexible. You can add whole groups to ‘Never Share’ or ‘Always Share’ exceptions. Settings will adjust automatically as people join and leave the groups.

-

On Telegram, your phone number was never visible to random people in groups, the default being ‘My Contacts’. This update offered even more control via Settings > Privacy & Security > Phone Number.

-

The update also introduced an easier way to integrate web services with Telegram, adding one-tap authorization via bots. Last but not least, it offered two new ways of adding comments to channels – via Comments.app and connected discussion groups. (We didn't start the flame war.)

-
- TITLE -
- -

On Telegram since May 31, 2019:

- -
-

May 2019, First Update

-

Archived Chats, a New Design on Android and More

-

The first May update introduced Archived Chats. Unmuted chats pop out of the archive with the next incoming message – but muted chats stay archived forever (or until they generate a notification via a mention or reply). An unlimited number of chats can be pinned in the archive.

-

Android design got a major overhaul. Aside from the visual improvements, this update added a three-lines-per-chat view option for the Android chat list (similar to the iOS default), as well as bulk actions in the chats list to easily delete, archive or mute multiple chats at once.

-
- TITLE -
- -

On Telegram since May 9, 2019:

- -

March 2019

-

Taking Back Our Right to Privacy

-

Before the March update, you could delete your messages within 48 hours of sending them. As of this update, you can delete any message you've ever sent or received in any private chat, there's no time limit. This also applies to clearing entire chats. The deleted messages don't leave a mark in the chat.

-

This update also introduced a setting for Anonymous Forwards, allowing you to control when messages forwarded from your account link back to it. This way people you chat with have no verifiable proof you ever sent them anything.

-
- TITLE -
- -

On Telegram since March 2019:

- -

February 2019

-

Autoplaying Videos, Automatic Downloads and Multiple Accounts

-

Following the February update, smaller videos start playing without sound when they reach your screen. Pressing the volume buttons on your device unmutes them.

-

This update also introduced presets for autodownload settings to switch between Low, Medium, High and Custom data consumption in a few taps. Default settings for data usage have become more generous but depend on the affordability of mobile data in each particular country.

-

As of this update, iOS users can also log in to Telegram with multiple accounts from one app, easily switch between them and get notifications. Support for multiple accounts was added to Android in December 2017.

-
- TITLE -
- -

On Telegram since February 2019

- -

January 2019, Second Update

-

Chat Backgrounds 2.0: Make Your Own

-

The second update in January brought chat wallpapers to version 2.0, adding support for motion and blur effects, plain color backgrounds and patterns, as well as an option to share backgrounds via links and find new ones in search.

-

For those who appreciate art history, the classical Telegram backgrounds which were used at launch can be found here.

-
- TITLE -
- -

On Telegram since January 31, 2019

- -

January 2019, First Update

-

Group Permissions, Undo Delete and More

-

The first January update brought group permissions, allowing admins to restrict all members from posting specific kinds of content or even from messaging altogether. The maximum size for groups was doubled to 200,000 members.

-

The update also added an ‘Undo’ option after deleting chats or clearing history. It's like a time machine, but with fewer paradoxes.

-
- TITLE -
- -

On Telegram since January 21, 2019

- -
-

2018

-
-

December 2018, Second Update

-

Polls: Bringing Choice to Communities

-

As of the second update from December '18, Telegram users can create polls in groups and channels, letting group members vote anonymously.

-

Poll bots have been available since the dawn of the Bot Platform.

-
- TITLE -
- -

On Telegram since December 22, 2018

- -

December 2018, First Update

-

Custom Languages, Instant View 2.0 and More

-

This first December update in 2018 revolutionized app interfaces, adding custom languages – whether that's Māori, Scottish Gaelic or Transliterated Klingon. Qapla'. Users can share translated language packs with dedicated sharing links.

-

Everyday be talk like a pirate day if ye've downloaded the pirate speak chest. Babel fish now optional.

-
- TITLE -
- -

On Telegram since December 10, 2018

- -

October 2018

-

Introducing Telegram 5.0 for iOS

-

Telegram for iOS was rebuilt from scratch for this update – using the Swift programming language. The new client is slicker, faster and more battery-friendly. If the old Telegram was a race car, this one is a race car with jet engines and a well-caffeinated driver.

-

New badge counter settings were added on iOS, allowing users to exclude messages from muted chats or count unread chats instead of messages.

-

The native macOS client added swipe gestures to navigate interfaces. MacBook Pro owners got touch bar support.

-
- TITLE -
- -

On Telegram since October 2018

- -

August 2018

-

Chat Export Tool, Better Notifications and More

-

This update brought an easy way to download copies of your chats, including photos and other media using Telegram Desktop. August '18 also saw the birth of Notification Exceptions – a way to customize notification settings for particular users.

-
- TITLE -
- -

On Telegram since August 2018

- -

July 2018

-

Introducing Telegram Passport

-

Telegram Passport was launched as a unified authorization service for ICOs, financial services and other platforms based on real-life ID. You no longer have to upload scans of your ID each time a different service requires it.

-
- TITLE -
- -

On Telegram since July 2018

- -

June 2018

-

Replace Media, Share vCards, Mark as Unread, 2X Voice Messages, and More

-

The June '18 update brought the ability to replace photos and videos when editing messages – in case you accidentally sent a picture of your lunch instead of the company's new logo.

-

As of this update, voice and video messages can be played at 2x speed and users can mark chats as read or unread.

-
- TITLE -
- -

On Telegram since June 2018:

- -

March 2018

-

Sticker Search, Multiple Photos and More

-

Since they were introduced, stickers have become a key method of communication for many Telegram users. As of this update, users can search for new sticker packs.

-

I'm not addicted to sending stickers. I can stop any time.

-
- TITLE -
- -

200,000,000 Monthly Active Users

-

Telegram has never been promoted with ads, so every user joined because they were invited by others. Telegram is more than a messaging app, it's the idea that everyone on the planet has a right to be free.

-
- TITLE -
- -

On Telegram since March 2018:

- -

February 2018

-

Two updates were launched on February 6, 2018.

-

Streaming and Auto-Night Mode on Android

-

This was when the apps got streaming support, allowing you to view videos without waiting for them to fully download. This update also introduced auto-night mode for Android users, shielding weary eyes from bright light when browsing memes in bed.

-
- TITLE -
- -

Telegram Login for Websites

-

Another update introduced the Telegram Login Widget for external websites, empowering businesses to use Telegram bots to automate anything from customer support to accepting payments or tracking shipments.

-
- TITLE -
- -

On Telegram since February 2018

- -

January 2018

-

Two updates were launched on January 31, 2018.

-

Telegram X: Progress through Competition

-

Two Telegram X clients were unveiled as alternatives to the main iOS and Android apps – built from the ground up to be faster and easier to use, while featuring smooth animations and a sleek design. Telegram X for iOS has since become the native client on iPhones around the world.

-
- TITLE -
- -

TDLib - Build Your Own Telegram

-

The Telegram Database Library helps developers make their own versions of Telegram – and was used to create Telegram X for Android. TDLib handles network implementation, encryption, and local storage, giving third-party developers more time to focus on the fun parts of app design. All the API methods are fully documented and the code is available on GitHub.

-

Both Telegram X and the Telegram Bot API are an example of what can be done with this library.

-
- TITLE -
- -

On Telegram since January 2018

- -
-

2017

-
-

December 2017

-

Themes, Multiple Accounts and More

-

Themes came to iOS, with simple ‘Day’ and ‘Night’ options. We considered adding a ‘Twilight’ option but it got sabotaged by lovesick vampires and werewolves.

-

Android added support for multiple accounts, to quickly switch between up to three profiles (or personalities) without logging out.

-
- TITLE -
- - -

On Telegram since December 2017

- -

November 2017

-

Albums, Saved Messages and Better Search

-

Albums and Saved Messages came to Telegram in November as a way to cut down on clutter and keep things organized. Multiple media items could be sent as one message, neatly arranged instead of filling up the chat with individual messages and multiple notifications.

-

Saved Messages brought bookmarks and personal storage, giving users the ability to forward messages there for later reference.

-
- TITLE -
- - -

On Telegram since November 2017

- -

October 2017

-

Live Locations, Media Player and Languages

-

October '17 expanded location sharing to include a live feed, useful for finding your friends or seeing how far they are from a destination. The interactive maps support multiple users, so your entire group can share their locations and see each other in one place.

-

Telegram also expanded its localization, launching the Translations Platform for users to refine the currently-available translations.

-
- TITLE -
- - -

On Telegram since October 2017

- -
-

August 2017

-

Better Replies, Stickers & Invitations

-

Keeping track of replies and mentions was streamlined in August’s update, adding the new ‘@’ badge to the chat list, and ‘@’ button inside chats to jump from mention to mention.

-

The option to set favorite stickers was added, while groups got the ability to choose official sticker sets.

-
- TITLE -
- -

On Telegram since August 2017

- -
-

July 2017

-

Disappearing Media, Your Bio & More Speed

-

July’s update added a self-destruct timer for photos and videos to give users the option to send disappearing media in Private Chats.

-

To help say a little more about themselves, user profiles were given a bio section.

-
- TITLE -
- - -

On Telegram since July 2017

- -
-

June 2017

-

Supergroups 10,000: Admin Tools & More

-

Groups leveled up in June '17, increasing the maximum members to 10,000 and introducing a suite of new tools to manage the masses.

-

Admin permissions became individual, allowing for specific privileges. So did members’, meaning people could be put under custom restrictions for acting up.

-

The Recent Actions page was added for admins, showing a summary of all notable group activity within the past 48 hours.

-
- TITLE -
- - -

On Telegram since June 2017

- -
-

May 2017

-

Three updates were released on May 18, 2017.

-

Video Messages and Telescope
Just in time for Summer, video messages were introduced to add another dimension to chats and channels.

-
- TITLE -
- -

Instant Views for Everyone & a $200K Contest

-

Instant View grew into a platform for reformatting articles from the Web into lightweight, uniform pages which instantly open in Telegram, rather than a browser. A contest to create new templates was launched.

-
- TITLE -
- -

Payments for Bots
Bot payments joined the pool party as well, so users could pay for goods and services right in the app.

-
- TITLE -
- - -

On Telegram since May 2017

- -
-

March 2017

-

Voice Calls: Secure, Crystal-Clear, AI-Powered

-

March '17 brought voice calls to Telegram, featuring end-to-end encryption, crisp sound and incredible speed.

-

The video editor received a compression slider to change the quality at which a video is sent.

-
- TITLE -
- -

On Telegram since March 2017

- -
-

February 2017

-

Custom Themes

-

Custom themes first came to the Android phone app, along with a theme editor, giving users the ability to recolor individual elements and share their creations with others.

-
- TITLE -
- -

Telegram Desktop reaches version 1.0 – and it's BEAUTIFUL

-

Telegram Desktop, first launched in January '14, reached version 1.0, with a new design, refined animations and custom theme support, in addition to all its earlier features.

-

The GMail bot made its debut as well, allowing users to condense all their communications into one platform.

-
- TITLE -
- -

Telegram for Android Wear 2.0

-

Telegram came to wrists with its Android Wear 2.0 version, featuring fully-functional messaging capability, plus added themes to keep things chic.

-
- TITLE -
- - -

On Telegram since February 2017

- -
-

January 2017

-

Unsend Messages, Network Usage, and More

-

Telegram rang in the New Year with a completely new feature - the ability to unsend messages sent within the past 48 hours.

-

To keep track of users' data consumption, Network Usage was added to Settings.

-
- TITLE -
- -

On Telegram since January 2017

- -
-

2016

-
-

December 2016, Second Update

-

Meet the Telegraph API for Logins and Stats

-

The Telegraph API opened to the public in the final update of 2016. Publishing and organizing articles gained automated support with the new @Telegraph bot.

-
- TITLE -
- -

On Telegram since December 20, 2016

- -
-

December 2016, First Update

-

Pinned Chats and IFTTT Integrations

-

Conversation management became easier with the option to pin chats to the top of the chat list.

-

IFTTT integration was introduced to help link Telegram to over 360 services at launch. This gives users control over their accounts on other services straight from the Telegram app – including social media, mail clients and even things like smart appliances or other devices.

-
- TITLE -
- -

On Telegram since December 7, 2016

- -
-

November 2016

-

Instant View, Telegraph, and Other Goodies

-
- TITLE -
- -

Instant View came in November 2016, instantly loading articles and web pages all inside the Telegram app. Added in the same update, the Telegraph platform is a minimalist word processor compatible with Instant View, designed for quickly publishing documents and articles.

-

On Telegram since November 2016

- -
-

This is where wide full-color illustrations for our blog posts end – or begin, depending on which direction you just came from.

-
-
-

October 2016

-

Gaming Platform 1.0

-

With winter not far off, Telegram introduced a Games platform that allows users to play games through bots. Players get the chance to challenge friends, while creators have an easy and accessible way to bring their game ideas to life.

-
- -
- -

On Telegram since October 2016

- -
-

September 2016

-

Photo Editor 2.0, Masks and Homemade GIFs

-

In September ‘16, the time came to improve Telegram’s Photo Editor with fun new decorations like masks, text, stickers and drawings. Additionally, the video editor added the ability to make GIFs out of videos by tapping its new ‘Mute’ button.

-
- -
- -

On Telegram since September 2016

- -
-

August 2016

-

Trending Stickers, Storage and More

-

A Trending Stickers option was added so popular sticker packs can be easily found and added to one's collection. Groups received previews so prospective members can see what they‘re about and who’s in them before joining the party.

-
- -
- -

On Telegram since August 2016

- -
-

June 2016

-

Drafts, Picture-in-Picture, and More

-

June '16 brought cross-platform cloud drafts, syncing your unfinished messages across devices. Since then, users have been able to start typing on one device and finish on another. For more multitasking, Picture-in-Picture support was added to let users work and watch simultaneously.

-
- -
- -

On Telegram since June 2016

- -
-

May 2016

-

Edit Messages, New Mentions and More

-

Fast typers rejoiced as the ability to edit sent messages was introduced in all chats. Mentions were expanded to include users without usernames, and Bots were given their own space in the attachment menu for easy access.

-
- -
- -

On Telegram since May 2016

- -
-

April 2016, Second Update

-

Instant Camera and More 3D Touch

-

Instant camera was added so users could snap and send photos faster, saving the extra thumb-work to make sure the moment is captured.

-
- -
- -

On Telegram since April 28, 2016

- -
-

April 2016, First Update

-

Bot Platform 2.0

-

Starting in April 2016, inline bots no longer require you to use a keyboard. These software-controlled friends now immediately present clickable options to get results with no typing required. They were also integrated with services like YouTube and Foursquare for easy video and location sharing.

-
- -
- -

Sharing and Previews

-

This update gave users a new way of sharing media between chats, introducing GIF and sticker previews to make the selection process more straightforward.

-
- -
- -

On Telegram since April 12, 2016

- -
-

March 2016

-

Supergroups 5000: Public Groups, Pinned Posts

-

To keep order as supergroups grew from 1,000 members to 5,000, important announcements could be placed at the top of the screen as pinned messages. Additional moderation tools were introduced that helped prevent spam in public supergroups. This included the ability to report spam, ban a user outright, or simply erase all of their posts from the group.

-
- -
- -

On Telegram since March 2016

- -
-

February 2016, Second Update

-

Channels 2.0 and More

-

Channels got plenty of new features including admin signatures and silent broadcasts. It became possible to edit your messages in channels and supergroups.

-
- -
- -

On Telegram since February 24, 2016

- -

February 2016, First Update

-

Voice Messages 2.0, Secret Chats 3.0 and…

-

Chatting got easier with raise-to-speak and raise-to-listen functionality, streamlining voice messages by giving a no-tap way to play and record. On the privacy end, users got the ability to restrict who can invite them to groups and channels.

-
- -
- -

On Telegram since February 12, 2016

- -
-

January 2016

-

Introducing Inline Bots

-

Inline bots make it possible to use bot services in any chat without adding those bots as members – you just start any message with their username and everything that comes after becomes a query for the bot. These utilities can link Wikipedia articles, post YouTube videos or search for GIFs to entertain friends. Unfortunately, while being very good at fetch, they still can't pull a sled – even after all these years.

-
- -
- -

GIF Revolution

-

GIF file size was reduced by 95%, making them load 20x faster. Autoplay for all GIFs was enabled to show off their new-found speed.

-
- -
- -

On Telegram since January 2016

- -
-

2015

-
-

December 2015

-

Clearing Cache and Reordering Stickers

-

The space-saving option of clearing cache was introduced, including chat-by-chat specificity. This was coupled with a setting to choose how long to keep media before it gets deleted from the cache (to be re-downloaded from the cloud should you need it again).

-
- -
- -

On Telegram since December 2015

- -
-

November 2015

-

Admins, Supergroups and More

-

This update added the admin role. Admins have the power to manage group chats and enforce rules. Just in time, as the maximum number of users for group chats grew to 1,000 people with the addition of supergroups.

-
- -
- -

On Telegram since November 2015

- -
-

September 2015

-

Channels: Broadcasting Done Right

-

September '15 brought channels, the perfect tool for broadcasting messages to the masses. Channels can have unlimited followers, offer view counters for each post and only let the admins post. These one-way chats give updates the spotlight by moving the discussion elsewhere. Channels were quickly adopted in regions where freedom of speech falls short.

-
- -
- -

On Telegram since September 2015

- -
-

August 2015

-

Shared Links and Recent Searches

-

Telegram delivered quality of life updates in August '15, showing shared links on chat info pages as well as a list of recent searches when beginning a new one.

-
- -
- -

On Telegram since August 2015

- -
-

July 2015

-

In-App Media Playback and Search in Chats

-

This update added the ability to view media, enjoy music and watch videos from external sources directly in the app. Chat-specific search was implemented as well, making it easier to find messages from a particular conversation.

-
- -
- -

On Telegram since July 2015

- -
-

June 2015

-

Telegram Bot Platform

-

In June of 2015, Telegram released the Bot API and created a platform for users to create and publish their own bots. Bots exist to add features to Telegram and make user's lives easier - bots can handle payments, moderate groups, fetch emails and much more.

-
- -
- -

Telegram on Apple Watch

-

Telegram also received Apple Watch support. With a flick of the wrist, users can view recent chats, reply with stickers, dictate messages and more. Anything that can't fit on the watch display gets a shortcut to open on your phone instead.

-
- -
- -

On Telegram since June 2015

- -
-

May 2015

-

Custom Sticker Sets

-

Since May '15, stickers can be uploaded and shared as sticker sets. All apps got a dedicated sticker panel. Tapping on any sticker shows its set and lets you add the lot.

-
- -
- -

On Telegram since May 2015

- -
-

April 2015

-

Migrating Existing Group Chats to Telegram

-

Invite links were added so users can easily bring their friends to group chats, even when those friends are lost in another messenger.

-
- -
- -

Places, Captions and more

-

Users gained the ability to caption photos, so the context and content can be sent as one message.

-
- -
- -

Active Sessions and Two-Step Verification

-

Telegram rolled out an essential privacy feature in April 2015 - Two-step Verification – adding an extra layer of protection by requiring a password when logging into a new device.

-
- -
- -

Link Previews

-

Link previews were introduced to help users see where a link leads without having to click on it and find out for themselves.

-
- -
- -

On Telegram since April 2015

- -
-

March 2015, Second Update

-

Sending Files On Steroids — And More

-

This update brought the ability to send multiple files at once and trim videos before sending them.

-
- -
- -

On Telegram since March 25, 2015

- -
-

March 2015, First Update

-

Reinventing Group Chats: Replies, Mentions, Hashtags and More

-

March '15 made messaging more convenient – Telegram added replies, mentions and hashtags. Replies make it easier to keep continuity in group chats, while mentions help get someone's attention and hashtags allow users to label messages for future use.

-
- -
- -

On Telegram since March 19, 2015

- -
-

February 2015, Second Update

-

Photo Editor and Passcode Lock

-

February '15 delivered the most powerful photo editor among messaging apps – featuring auto-enhance, crop and rotate functions in its initial version. To keep those photos and chats secure, users were given the option to lock their app with a passcode.

-
- -
- -

On Telegram since February 25, 2015

- -
-

February 2015, First Update

-

Shared Files and Fast Mute

-

This update introduced the Files tab to better view all documents shared in a particular chat (some media outlets mistakenly thought this was when we introduced sending files). Additionally, the update brought in Mute shortcuts, helping users disable notifications more quickly.

-
- -
- -

On Telegram since February 1, 2015

- -
-

January 2015

-

Stickers Done Right

-

January '15 saw the first sticker on Telegram. Since then, starting a message with a single emoji brings up a list of emotionally corresponding sticker suggestions.

-

The first official stickers from Telegram formed the classic Great Minds set. Artists were invited to publish their work on the free and open platform.

-
- -
- -

On Telegram since January 2015

- -
-

2014

-
-

December 2014

-

Telegram.me, Changing Numbers, PFS and more

-

Users with usernames were offered Telegram.me/username links, which open their profile page in Telegram. This update also enabled changing the phone number of a Telegram account. Single-column mode was added for Telegram Desktop, making multitasking easier on smaller screens.

-
- -
- -
-

Fun fact: In 2016, Instagram will restrict users from adding Telegram.me (and Snapchat) links to their bios.

-
-

On Telegram since December 2014

- -
-

November 2014

-

There were two Telegram updates on November 19, 2014.

-

Hiding Last Seen Time - Done Right

-

This update expanded Privacy Settings to cover Last Seen status, allowing unprecedented flexibility with ‘Always Share With’ and ‘Never Share With’ exceptions for individual users.

-

This was also when account self-destruction was introduced. Telegram doesn‘t aim to accumulate and store your data when you don’t need it anymore. So if you throw away your SIM card and it gets a new owner in 6 months, they won't access your chats.

-
- -
- -

Material Design on Android, Instant Search for Messages and more

-

November '14 also delivered Instant Full-Text Search to iOS and Android. Since then you can quickly find any message you ever sent or received on Telegram.

-

GIF search was first supported on iOS. The Android app got a massive redesign, consistent with material guidelines.

-
- -
- -

On Telegram since November 2014

- -
-

October 2014

-

Public usernames, smaller timers for Secret Chats, and more

-

October '14 marks the beginning of properly recorded history on Telegram. The first update ever to be described in a blog post brought public usernames, adding the ability to share your Telegram contact without disclosing your phone number.

-

Secret Chats got a major upgrade, with self-destructing media showing blurred thumbnails and starting the countdown only after they are first opened. This prevented them from disappearing before actually being viewed. This was also when screenshot notifications were first introduced.

-

Telegram for Android received several updates, adding support for Android Wear and tablets, as well as video compression.

-
- -
- -

On Telegram since October 2014

- -
-
- -
- -

September 2014

-

GIFs, iPad support and broadcast lists on iOS

-

Telegram has supported iPads since September '14. In this update, the iOS app learned to play GIF animations and added cloud search for messages, as well as adding search by file name to the Shared Documents section. iOS also caught up with Android, adding support for broadcast lists.

-
- -
- -

On Telegram since September 2014

- -
-

August 2014

-

Broadcast lists were first introduced to Android in August '14, only to be replaced with channels a little over a year later.

-
- -
- -

On Telegram since August 2014

- -
-

June 2014

-

Multiple photo upload and more

-

Telegram for Android caught up with iOS, allowing users to preview photos before sending — as well as select and send many photos at once. Notifications were improved to be more reliable.

-
- -
- -

On Telegram since June 2014

- -
-

March 2014

-

Voice Messages, Delete Messages for both sides in Secret Chats, Language Settings on Android

-

The March '14 update introduced voice messages to Telegram. Messages deleted in Secret Chats began disappearing for both sides.

-

Telegram for Android added the option to change the app language in Settings. The first languages to be added were German and Italian.

-
- -
- -

On Telegram since March 2014

- -
-

February 2014

-

New apps, autodownload settings and contact management tools for Android

-

More Telegram apps entered the fray. An unofficial Telegram app for Web was introduced and later moved to web.telegram.org to become the official web version. Telegram for Windows Phone was created in a contest for app developers.

-

Meanwhile, an update introduced autodownload settings and new tools to manage contacts on Android.

-
- -
- -

On Telegram since February 2014

- -
-

January 2014

-

Send documents and files

-

First thing in 2014, Telegram allowed documents of any type to be sent, including .pdf, .doc, .png, .mp3, etc. The size limit is 1,5 GB per file.

-

An unofficial Telegram app for PC was announced, which would later become the official Telegram Desktop.

-
- -
- -

On Telegram since January 2014

- -
-

2013

-
-

December 2013

-

Crowdsourcing a more secure future

-

The only significant vulnerability to ever be discovered in the MTProto protocol was fixed during the First Telegram Crypto Contest. The researcher who discovered it was awarded a bounty of $100,000.

-
- -
- -

On Telegram since December 2013

- -
-

October 2013

-

After a contest for Android developers, the alpha version of Telegram for Android was officially launched. Telegram apps got Secret Chats with self-destruct timers.

-

The MTProto Protocol specification and Telegram API were fully documented and the code of the apps became open source.

-
- -
- -

On Telegram since October 2013

- -
-

August 14, 2013

-

Telegram for iOS was launched.

-
-

Congratulations on completing this (not very) brief course on the history of Telegram. You just got an honorary PhD in Instant Messaging – unless you simply jumped down here, in which case you still have a long way 👆to go to get back to the top.

-

Armed with this much knowledge, you should probably join our Volunteer Support Force. And if that‘s not your cup of tea – just tell us in the comments which feature you didn’t know existed.

-

- -

August 15, 2019
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 283374f3f2..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/bot-revolution.html b/data/telegram.org/blog/bot-revolution.html deleted file mode 100644 index 3010914f59..0000000000 --- a/data/telegram.org/blog/bot-revolution.html +++ /dev/null @@ -1,279 +0,0 @@ - - - - - Telegram Bot Platform - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Telegram Bot Platform

- -
- -
- -
-

UPD: Check out the new Inline bots as well!

-
-

Telegram is about freedom and openness – our code is open for everyone, as is our API. Today we’re making another step towards openness by launching a Bot API and platform for third-party developers to create bots.

-

Bots are simply Telegram accounts operated by software – not people – and they'll often have AI features. They can do anything – teach, play, search, broadcast, remind, connect, integrate with other services, or even pass commands to the Internet of Things.

-
- - - -

- -
- - -

Today’s 3.0 update to the Telegram apps makes interacting with bots super-easy. In most cases you won’t even have to type anything, because bots will provide you with a set of custom buttons.

-
-

"Every application needs a slightly optimized set of buttons, just for it.
Steve Jobs, 2007 iPhone launch

-
-

Bots can now provide you with custom keyboards for specialized tasks that could look like this for example:

-
- - - -
- -

- -

Here are some sample bots that were built by the platform's beta testers this past weekend:

-
    -
  • @ImageBot – send this bot a keyword and it’ll provide you with a relevant picture.
  • -
  • @TriviaBot – test your trivia knowledge or add to groups to compete with friends.
  • -
  • @PollBot – add this one to group chats to create polls.
  • -
  • @RateStickerBot – discover and rate new stickers.
  • -
  • @AlertBot – set a time and this bot will send you a reminder for anything you like.
  • -
  • @HotOrBot – find friends with this Tinder-like dating bot.
  • -
  • @GithubBot – track GitHub updates.
  • -
  • @StoreBot – find new bots and rate them.
  • -
-
- -
- -

Our beta testers needed only a few hours to build these bots – setting up a new bot is a breeze. Just generate a key with @BotFather and use a simple https API to control your bot. If you’re an engineer, check out our Introduction to bots for details.

-

Bots in Telegram will look different from human users: their chat and profile screens have a slightly different UI and they don't have access to all messages by default when added to groups.

-

Taking over the world

-

Once you've launched your bot, watch it spread. In Telegram, any forwarded message contains a link to its original sender. This means any message from your bot forwarded to a person or group is a messaging equivalent of a retweet – bots are viral.

-

Additionally, all bots have an Add To Group and a Share button in their profile. You can set up a description and link that will be used when people share your bot on Telegram or other platforms.

-
- - - - - - -
- -

- -

A typical link to a bot looks like this:

-
-

https://telegram.me/your_bot

-
-

Opening such a link starts a chat with that bot if you have Telegram installed. These links are easy to identify because all bot usernames must end in bot.

-

If the bot developer wants to pass their bot some additional info (like an auth key for example, see deep linking), the link might also look like this:

-
-

https://telegram.me/your_bot?start=value

-
-

The bots are coming

-

Starting today, you'll see links like this in Telegram and elsewhere. Embrace them, they are bots! They will provide the services you asked us for – polls, news, games, integrations, e-butlers or cat images. Any dream can come true with bots.

-

- -

The Telegram Team,
June 24, 2015

-

- -

P.S. All bot developers are welcome to share ideas for our Bot API on @BotSupport.

-
-

You can read more about the our bot platform in the Introduction to Bots and in the Bot API Manual.

-
-
- -
- - -
- - -
-
-
- - - - - - - 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 3b74bf057e..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/desktop-1-0.html b/data/telegram.org/blog/desktop-1-0.html deleted file mode 100644 index d3f6455da9..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/edit.html b/data/telegram.org/blog/edit.html deleted file mode 100644 index f521b32d49..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/files-on-steroids.html b/data/telegram.org/blog/files-on-steroids.html deleted file mode 100644 index b70124b283..0000000000 --- a/data/telegram.org/blog/files-on-steroids.html +++ /dev/null @@ -1,240 +0,0 @@ - - - - - Sending Files On Steroids — And More - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Sending Files On Steroids — And More

- -
- -
- -

Many of you love Telegram for the ability to send huge files up to 1.5 Gb.

-

Today’s iOS update brings you a radically improved Send File menu. We have integrated cloud services like iCloud, DropBox, Google Drive and others, so you can now easily share your existing documents directly from the Send File menu.

-
- - - - - - - -
- -

Share multiple files and trim videos

-

Starting today, you can also share multiple media files at once and see their size and resolution before sending them. As for sharing videos, we added the long-awaited preview and trim functionality to the iOS app.

-

Another improvement that is specific to iOS for now is the ability to open locations in Google Maps and other non-default map applications, as well as get driving directions.

-
- - - - -
- -

Hashtags and Android features

-

Hashtags now support non-latin characters on both mobile platforms, and what is more important, recently used hashtags will be instantly suggested when you type the # symbol. This makes them much more usable.

-

As for improvements to the Android app, this update includes the ability to erase search history for Web images, GIFs and hashtags (simply tap and hold on recent items in search), sounds for incoming and outgoing messages in the currently opened chat and a multitude of design and UI improvements.

-

In fact, we were lucky to get feedback from the Google design team that provided ideas on how to improve the UI of our Android app. This release has some of these ideas implemented – for example, if you set a custom background for your Telegram chats, it will also be used in the Menu Drawer.

-
- - - - - -
- -

Stay tuned – we are shipping another great update next week.

-

-
- -

March 25, 2015
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/folders.html b/data/telegram.org/blog/folders.html deleted file mode 100644 index 71673fc44c..0000000000 --- a/data/telegram.org/blog/folders.html +++ /dev/null @@ -1,298 +0,0 @@ - - - - - Chat Folders, Archive, Channel Stats and More - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Chat Folders, Archive, Channel Stats and More

- -
- -
- -
- Introducing Chat Folders -
- -

Many of our users rely on Telegram for their work and studies, even more so in the last weeks. To make sure everyone's chat lists can handle the increased load and you don't miss important messages, we're introducing Chat Folders today.

-

If you have too many chats, you can now separate fun from work, or family stuff from school stuff – then swipe between the tabs to quickly access any of your chats.

-
- -
- -

You can include or exclude all chats of a particular type, like Channels, or Unread – or one by one.

-

Folders become available in the interface when your chat list is long enough to start getting cluttered. Alternatively, you may use this link in your app to enable Chat Folders.

-

Unlimited Pins

-

Each of your folders can have as many pinned chats as you like.

-
- Pinned chats in folders -
- -

Archived Chats

-

Chat Folders work best to make some of your chats more visible. If you're looking to hide some of your chats from view, try archiving them instead.

-

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.

-

On Android, if you are already using Folders, swiping will not work for archiving. Instead, you can long press on a chat to open the bulk actions menu where you can select multiple chats and then pin, mute, archive or delete them all at once.

-
- Archive button in the bulk actions menu -
- - -

Desktop Sync

-

Like everything on Telegram (except for Secret Chats), your Chat Folders will seamlessly sync to all your other connected apps, including our Desktop Apps.

-

Thanks to the extra space available on your computer screen, we've added a folder sidebar – as well as some icons to make your folders more recognizable:

-
- -
- -
-

Get the multiplatform Telegram Desktop or our dedicated macOS app. If you're not using those, you're only enjoying half of Telegram.

-
-

Channel Stats

-
-If you have a channel with more than 1000 50 subscribers, you can now view detailed statistics about its growth and the performance of its posts. -
- -
- -
- -

With this information, you can find out what's working and what's working really well. Hint: Cat Pictures.

-

Voice Recording Animations on Android

-

Our designers added some fancy wavy animations below your finger when you're recording a voice or video message.

-
- -
- -

Tip of the day: Did you know you can slide your finger up to lock recording and keep talking without holding the button?

-

New Animated Emoji

-

The latest additions to our army of animated emoji can help you be brave and urge your friends to stay safe and healthy. Send 🦠, 🤒, 😷, 🤕, 🤧, 🤢, 🤮, 🧼, 💉, 💊 or 🚑 to any chat to check them out.

-
- -
- -

Most of our sticker packs now also have something to say about the situation. Type 🦠 in any chat and wait to see the suggestions:

-
- -
- -

And One More Thing

-

Missing your Catan or D&D partners while the world is on lockdown? Send 🎲 to any chat to get a certified random number from the animated dice.

-

Besides trying to test your luck, you can also use it as a tiebreaker if a group poll or friendly debate ends in a split decision. Pick a number – the closest one wins!

-
- -
- -

Stay home, stay safe and stay tuned for our next updates!

-

- -

March 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 81c436b6d7..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/instant-view.html b/data/telegram.org/blog/instant-view.html deleted file mode 100644 index 6633932adc..0000000000 --- a/data/telegram.org/blog/instant-view.html +++ /dev/null @@ -1,268 +0,0 @@ - - - - - Instant View, Telegraph, and Other Goodies - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Instant View, Telegraph, and Other Goodies

- -
- -
- - -
- -
- -
Meet Instant View, an elegant way to view your dog articles with zero pageload time. To try it out, use Telegram version 3.14 to share a link to a Medium post or a TechCrunch article. This will get you an Instant View button that immediately shows a native page, saving you time and data.
- -
-
- -

Instant View button

-
-
- -

Saves time and data

-
- -

If you have feedback about the way an Instant View page was generated, ping our @previews bot. Only a handful of websites are supported at the moment, but we'll be adding more as we go. Eventually we want to provide Instant View pages for every story on the Web and thus devour the entire Internet (*evil laugh*).

-

Telegraph

-

Today we are launching Telegraph – a publishing tool that lets you create richly formatted posts with photos and all sorts of embedded stuff. Telegraph posts get beautiful Instant View pages on Telegram.

-

To try it, go to telegra.ph, publish a story, and share it on Telegram. With Telegraph, your Telegram channel can run stories just like the mainstream media (although you may find it tricky to become as biased).

-

Jump to Date

-

You can now travel in time to any moment in the past. Just tap Search inside a chat and choose a day using the Calendar tool.

-
-
- -

Calendar button

-
-
- -

Pick a day

-
- -

Unfortunately, this doesn't work with dates from the future. Sorry, no flying cars and hoverboards for you today.

-

View Pack for Recent Stickers

-

Remember all those times when you had a sad Pepe among your recently sent stickers? If you‘re like us, your natural desire would’ve been to reunite the sad Pepe with the rest of his family by scrolling to the Pepe pack in your sticker panel.

-

You can now do that in an instant: try a long tap (or 3D-touch on iOS) on a recent sticker, then choose ‘View Pack’. Hey presto! For some mysterious reason, this also works with non-Pepe stickers.

-
-
- -
-
- - - -

Groups in Common

-

Sometimes you want to find a group in your chats, but can‘t recall the title. Here’s a life-hack for you: think about a contact of yours that was also a member in that group. This association technique may help you bring back the title too. If it doesn‘t, open that contact’s profile and tap Groups in Common.

-

Android Strikes Back

-

Some of you Android users told us we loved iPhones more than Androids. That almost made us cry (remember the sad Pepe in our recent stickers?). To make things right with you, we fired our iOS dev, who was too good.

-

Well, not really. We simply locked ourselves in the coding basement for several weeks to bring you this:

-
    -
  • A slick new interface for creating groups and selecting users in privacy settings (shiny animations included).
  • -
  • A new beautiful interface for notification settings.
  • -
  • Improved security for passcode locks (your chats won't be seen in the task switcher now). This one also works on iOS.
  • -
  • Improved camera speed when taking photos and videos.
  • -
  • Better video compression.
  • -
  • An improved and less obstructive photo viewer.
  • -
  • Easier editing of messages and adding captions to photos.
  • -
-

And that's just getting us warmed up. Make Android Great Again!

-

Also

-

Something big is brewing in our secret dungeons. Stay tuned.

-

- -

November 22, 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 8d096a6ec0..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 4f03e0b672..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 14bb07de53..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 729f6691d2..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/new-profiles-people-nearby.html b/data/telegram.org/blog/new-profiles-people-nearby.html deleted file mode 100644 index face9f1969..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/now-you-see-me.html b/data/telegram.org/blog/now-you-see-me.html deleted file mode 100644 index fdef14c31f..0000000000 --- a/data/telegram.org/blog/now-you-see-me.html +++ /dev/null @@ -1,235 +0,0 @@ - - - - - Disappearing Media, Your Bio & More Speed - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Disappearing Media, Your Bio & More Speed

- -
- -
- -
- -
- -

Telegram 4.2 is here! We have completely redesigned our photo editing tools, and it takes you even fewer taps to make your photos look amazing. In addition, you can now set a self-destruct timer for any photos and videos you share in private chats.

-
- -
- -

If you set a timer, the countdown starts the moment your recipient opens the photo or video you sent. After the time runs out, the photo/video will disappear forever, just like in Secret Chats.

-

If the recipient tries to make a screenshot of your disappearing media, you’ll get a notification immediately.

-

Who are you again?

-

Starting today, you can add a bio to your profile by typing a few words about yourself in Settings. Every time you stumble upon new users in large groups you might want to learn more about them. That's where bios can help.

-
- -

Bio in your profile

-
- -

More Speed and Security

-

On top of this, as of 4.2, Telegram apps will rely on a CDN (distributed network) to cache publicly available photos and videos posted in massive channels (100,000+ members). This will result in significantly higher download speeds for tens of millions of Telegram users around the world. Check out this post to learn more about how we managed to do it in a slick and secure way.

-

One More Thing

-

Stickers are now easier to use as you can enlarge the scrolling area. More legroom for your emotions!

-
-
- -
-

-
- -

July 23, 2017
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/permissions-groups-undo.html b/data/telegram.org/blog/permissions-groups-undo.html deleted file mode 100644 index 5908d05a02..0000000000 --- a/data/telegram.org/blog/permissions-groups-undo.html +++ /dev/null @@ -1,265 +0,0 @@ - - - - - Group Permissions, Undo Delete and More - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Group Permissions, Undo Delete and More

- -
- -
- -
- Introducing Telegram 5.2: New permissions for groups, unified group settings, undo deleting chats and more -
- -

Ever wanted to run a sticker-free or GIF-free community? With group permissions, admins can now restrict all members from posting specific kinds of content. Or even restrict members from sending messages altogether – let the admins chat amongst themselves while everybody else witnesses their wisdom in silent awe.

-
- -
- -

In case you ever felt lonely in a group with 100,000 members, Telegram groups now support up to 200,000 members – so now you can feel twice as lonely 🙃. To make managing groups more enjoyable, we've streamlined all group interfaces, including the Settings screens, Admin panels and Member lists.

-
- New group, redesigned empty screen -

A newly created group

-
- -

As of today, supergroups and basic groups are simply groups. It now takes just a few taps to make any group public, add admins with granular privileges or toggle persistent history.

-

Have fun bossing around groups the size of the city of Kassel!

-

Undo clearing history and deleting chats

-

Deleting the wrong chat is rarely fun – but now you'll have a chance to reconsider.

-

When you delete a chat or clear chat history, you'll get a detailed confirmation dialog and an option to restore the chat within the next 5 seconds. Once the time is up, the chat is irretrievably lost in the jaws of Telegram’s underground data shredders.

-
- -
- -

If you relied on “I accidentally deleted the chat with my homework” in your studies, please accept our apologies. From now on, you'll have to blame your digital dog.

-

Sort your contacts

-

Back to the topic of bossing people around, you can now sort your contacts by name and by last seen time on both iOS and Android.

-
-
- Sorting contacts on iOS -

iOS

-
-
- Sorting contacts on Android -

Android

-
- -

Thumbnails and download animations

-

Waiting for large media downloads to finish ranks very low on the list of “The Most Exciting Things to Do Online”. We decided to spice this process up a bit by improving our animation algorithms and adding an ultra-light thumbnail to each photo and video:

-
- -
- -

From now on, every photo you receive will start its life as an obscure blur instead of an empty square. Isn’t this just beautiful?

-

Search bars, dark mode and moar profile pics

-

Search bars on Telegram for iOS and the default dark mode theme on Android got some face-lifting. The Android app also allows you to set up a profile picture when you create an account, so expect to see more friends with faces from now on.

-

Meanwhile on Desktop…

-

The new group permissions also work in Telegram Desktop. Additionally, version 1.5.8 introduces support for automatically downloading files and music and choosing input and output devices for Telegram Calls.

-

Last but not least, you can now change your visuals before heading into an emoji fight:

-
- Choose your emoji on Telegram Desktop -

Choose how you see emoji on Telegram Desktop

-
- -

Another glorious Telegram update is coming in a week or two, so STAY TUNED!

-

- -

January 21, 2019,
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/polls.html b/data/telegram.org/blog/polls.html deleted file mode 100644 index 51d16c1eaf..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/replies-mentions-stickers.html b/data/telegram.org/blog/replies-mentions-stickers.html deleted file mode 100644 index 162fde7fc6..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/search-and-media.html b/data/telegram.org/blog/search-and-media.html deleted file mode 100644 index 888b415f15..0000000000 --- a/data/telegram.org/blog/search-and-media.html +++ /dev/null @@ -1,232 +0,0 @@ - - - - - In-App Media Playback and Search in Chats - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

In-App Media Playback and Search in Chats

- -
- -
- -

The new version of Telegram allows you to play media from services like YouTube, Vimeo or SoundCloud directly from Telegram – without having to leave the app. Just tap on the preview of a link to an external media to view the video or listen to the audio file (speaking of audio files, they are now beautifully rendered and played in chats).

-
- - - - - -

- -
- -

The new attachment menu in Android is not only gorgeous and beautifully animated; it also allows you to share contacts, audios and recent photos way easier:

-
- -
-
- -

All of your communications in Telegram are already instantly searchable with the multi-purpose search field, but now you can also search for messages in specific chats. Just tap on the name of the chat in iOS or toggle the Actions menu in Android:

-
- - - - - -

-
- -

You will see the number of occurrences of the keyword in the chat and will be able to navigate through them with the up/down arrows. Enjoy!

-

- -

The Telegram Team,
July 17, 2015

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/share-preview.html b/data/telegram.org/blog/share-preview.html deleted file mode 100644 index 1e6e103839..0000000000 --- a/data/telegram.org/blog/share-preview.html +++ /dev/null @@ -1,269 +0,0 @@ - - - - - Sharing and Previews - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Sharing and Previews

- -
- -
- -

In addition to a major update to our Bot Platform, we're making several design and interface improvements to our apps today. This post mostly shows iOS screenshots, but be sure to check out the massive Android redesign we did in this version.

-

A fresh new look at sharing

-

Starting today, our iOS users can easily share photos and videos to other Telegram chats with a comment, or send them to other apps.

-
-
- -

New sharing menu

-
-
- -

Open in other apps

-
- -

New video player

-

We've also added a new slick in-app media player so that you can watch videos from YouTube and other services in style. It will also take you fewer taps to start watching.

-
- -

New in-app video player

-
- -

Preview sticker packs and stickers

-

Adding new sticker packs has become easier. Tapping on any sticker in a chat will now instantly open the relevant sticker pack. You can preview and send stickers right from this menu. Now you won't have to teach your grandparents how to add stickers.

-
-
- -

View sticker pack

-
-
- -

Preview sticker

-
- - -

Preview GIFs and bot content

-

On iOS, ‘Tap and hold to preview’ also works with GIFs in the GIF panel. Pull up for additional actions.

-
-
- -
-
- -

The same is true for content from inline bots. Tap and hold to preview results suggested by inline bots before sending. Try it now with @gif, @sticker or @coub.

-

Don't worry, this is coming soon to Android too! Speaking of which…

-

New design

-

The Android app received a major tuneup in the design department. We've redesigned the chat screen, optimized the colors, reimagined buttons and message bubbles, created beautiful progress bars, fully revamped documents and other attachments.

-
-
- -
-
- -
-
- -
-
- -

We've also improved the design of our iOS app, adding juicy progress bars and a new look for documents. Telegram Desktop has also received multiple design improvements and now fully supports the new bots.

-

- -
-

Yes, don‘t forget that in addition to the above we’re introducing the biggest update to our bot platform since June 2015 today. Read more about Bots 2.0 »

-
-

- -

April 12, 2016
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 d0f430ef45..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/supergroups5k.html b/data/telegram.org/blog/supergroups5k.html deleted file mode 100644 index c990a9d124..0000000000 --- a/data/telegram.org/blog/supergroups5k.html +++ /dev/null @@ -1,232 +0,0 @@ - - - - - Supergroups 5000: Public Groups, Pinned Posts - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Supergroups 5000: Public Groups, Pinned Posts

- -
- -
- -

Telegram is famous for its awesome group chats. Today’s update makes them even more awesome. To begin with, we’re increasing the number of people who can join a supergroup from 1000 to 5000 members. That's 5 times as good.

-

Supergroup admins can now inform all members about important news using pinned messages. Pinned messages 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

-
- -

Starting today, supergroups can become public and get a short link, like telegram.me/publictestgroup. This way, anybody can view the group's entire chat history and join to post messages.

-
- -

A public group

-
- -

We know what you’re thinking. What about spammers? To prevent potential spam issues, we're introducing powerful moderation tools for group admins. From now on, they can quickly delete all messages from a specific member, block and report them.

-
- -

New tools for admins

-
- -

These features work only in supergroups, but starting today, any group can be converted to a supergroup by its creator. Group admins are now shown in group members’ lists, so ping your group admin if you think this would be cool.

-
-

Good old groups still work great for smaller communities, so there's no need to convert your group right away.

-
-

And that's it for today, watch out for more updates coming soon!

-

- -

March 13, 2016
The Telegram Team

-

- -

P.S. Please note that we’ll be rolling out public groups gradually. They’re already live in Europe and America, but are currently not available in several countries in Asia, from which we detected significant spam activity in the past.

-

We’ll be making the feature available in more countries as we improve our anti-spam algorithms and scale our abuse team.

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/tdlib.html b/data/telegram.org/blog/tdlib.html deleted file mode 100644 index 261885a3f9..0000000000 --- a/data/telegram.org/blog/tdlib.html +++ /dev/null @@ -1,228 +0,0 @@ - - - - - TDLib – Build Your Own Telegram - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

TDLib – Build Your Own Telegram

- -
- -
- -
- -
- -

Telegram offers developers more than just the Bot API. Since day one, we've also had a free and open Telegram API that allows anyone to create their own messaging apps operating in the Telegram cloud. These apps openly compete with the official ones and some of them have now reached more than 10 million downloads on Google Play.

-

Users of these alternative clients can communicate with anyone on Telegram, but the apps often offer experimental, highly specialized or locally flavored features. Today we are introducing a new tool for third-party developers that will make it even easier to build fast, secure and feature-rich Telegram apps on our platform.

-

Introducing TDLib

-

Meet TDLib – the Telegram Database Library. TDLib takes care of all network implementation details, encryption and local data storage, so that developers can dedicate more time to design, responsive interfaces and beautiful animations.

-
Universally useful
-

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 compatible with any programming language that can execute C functions; it also has native bindings to Java and C#.

-
Open and well-documented
-

All TDLib API methods and public interfaces are fully documented. The code is, of course, completely open and available on GitHub.

-
Secure and reliable
-

TDLib will remain stable on slow and unreliable Internet connections and guarantees that all updates will be delivered in the correct order. All local data is encrypted using a user-provided encryption key.

-
Optimized for performance
-

The library is fully asynchronous and optimized for high performance. We use TDLib in the Telegram Bot API, where each TDLib instance handles more than 18,000 active bots simultaneously.

-
Battle-tested
-

Our new Android X client is an example of what can be done with TDLib. Using TDLib, it took the developer of the app approximately one year to reproduce all the major features of Telegram for Android – and add plenty of his own.

-

- -

Let's see what else TDLib will help bring to the Telegram ecosystem this year.

-

January 31, 2018,
The Telegram Team

-

- -
-

P.S. Today, we're also introducing Telegram X for Android, a new official app.
Check out the announcement here »

-
-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/telegraph.html b/data/telegram.org/blog/telegraph.html deleted file mode 100644 index 575f2f3ce4..0000000000 --- a/data/telegram.org/blog/telegraph.html +++ /dev/null @@ -1,238 +0,0 @@ - - - - - Meet the Telegraph API for Logins and Stats - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Meet the Telegraph API for Logins and Stats

- -
- -
- -
- -
- -

Last month, we launched Telegra.ph, a minimalist publishing tool that allows you to create richly formatted posts and push them to the Web in just a click.

-

We tried to keep Telegraph‘s interface as simple as possible: there’s no need to log in or navigate menus. You just open telegra.ph, write your post, hit publish, and it's live.

-
- -

Yes, it's that simple

-
- -

Better with Bots

-

This simplicity has its price of course. Sometimes you want to edit your articles on several devices or stay logged in to avoid having to write your name and profile link under each new title. If any of this sounds familiar, meet our new @Telegraph bot.

-

This simple bot will help you log in and manage your Telegraph posts across any number of devices. In addition, it can give you page view statistics for any post on Telegraph. Just send it a link and watch the numbers roll in.

-

A Time to Gather Stones

-

If you have created some Telegraph posts in the past using browsers on your different devices, the @Telegraph bot helps unite them all under your rule.

-
-
- -

A time to log in

-
-
- -

And a time to gather posts

-
- -

Simply press the Log in on this device button, and all posts you‘ve previously written in that device’s browser will be added to your Telegraph account.

-

Telegraph API

-

Mind you, Telegraph is not intended just for Telegram users. Anyone can use this dead-simple publishing tool. For those who are suffering the constraints of other messengers and can't enjoy the comfort offered by the @Telegraph bot, we have created an open Telegraph API.

-

Using the Telegraph API, any developer can create bots like @Telegraph for any other platform, or even standalone interfaces.

-
-

Here's the full documentation, in case you're interested.

-
-

Meanwhile, allow us to return to our coding dungeons where we're brewing another update to our apps for you this year.

-

- -

December 20, 2016
The Telegram Team

-
- -
- - -
- - -
-
-
- - - - - - - diff --git a/data/telegram.org/blog/unsend-and-usage.html b/data/telegram.org/blog/unsend-and-usage.html deleted file mode 100644 index 4b1cd5a0fe..0000000000 --- a/data/telegram.org/blog/unsend-and-usage.html +++ /dev/null @@ -1,273 +0,0 @@ - - - - - Unsend Messages, Network Usage, and More - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Unsend Messages, Network Usage, and More

- -
- -
- -
- -
- - -

Happy new 2017! We hope everybody had a great celebration. We at Telegram certainly did. One of our engineers got so excited about the new year that he mistakenly shared these stickers with his Mom:

-
- -

Ooops!

-
- -

To fix this, he quickly added a way to unsend recently sent messages. This smart move saved his morning, and it can still save yours! If you use Telegram v.3.16, you can now unsend any weird messages you shared within the last 48 hours.

-
- -

Works in groups and PM

-
- -

Naturally, this isn‘t a one-time feature. After this update, you’ll be able to retract any messages within 48 hours of sending them. Take that, Friday nights!

-

Network usage

-

The holiday season is in high swing in many parts of the world, so we figured some of you folks are busy traveling. If that's the case, you may want to check out the new Network Usage section that shows exactly how much data you consumed while in roaming or wi-fi or whatever.

-
-
- -

Data and Storage

-
-
- -

Network Usage

-
- -

Don't forget to hop on the hotel wifi before any serious Telegramming in foreign lands. And remember that you can toggle automatic media download in Telegram Settings.

-

T.me Links

-

This is the perfect season to meet new people. Want to give them some contact information, but a phone number seems like too much? That's exactly the reason we added usernames and Telegram.me links waaay back in 2014.

-

Starting today, you can use t.me instead of telegram.me. Take a napkin, write t.me/username in no time, and give it to someone before they can get away!

-

This also works with channels:
t.me/telegram
Public groups:
t.me/snowballfight
And stickers:
t.me/addstickers/NickSantini

-

Android Developers Never Sleep

-

85% of Telegram users are on Android. Our CEO is worried that, if ignored, this Android population can start a rebellion and dethrone him. To please the mob, he made us introduce the following features to the Android app:

-
    -
  • Messages from one sender are now neatly grouped together, and scrolling up shows the date right away, making the chats easier to navigate.
  • -
  • The app now restores your previous scroll position when you switch back to a chat. Very useful when somebody sends you a saga in 1,000 messages, and you want to patiently read them in the right order.
  • -
-
- -

That's the date up there

-
- -
    -
  • Sharing files (a feature we had since forever) has become easier because you see a list of recently downloaded files right on the sharing screen.
  • -
-
- -

Recently downloaded files

-
- -
    -
  • We now support GBoard, the Google keyboard that can apparently send cat GIFs.
  • -
  • And for those 2 users that already have Android 7.1 installed, we are happy to announce that we've added a fast action menu with frequent chats to your home screen. All hail the early adopters!
  • -
  • Back to the important stuff: the cowboy, the clown, and the sick face emoji (also known as the ‘exfoliating green tea mask face’ emoji) have found their way to Android. We support all of them now.
  • -
-
- -

New emoji

-
- -

What do these emoji mean? When are you supposed to use them? Is the singular form of ‘emoji’ in fact ‘emojus’? To answer all these questions with utmost accuracy, we've also added support for this one:

-
- -
- -

- -

January 3, 2017
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 77c2d5ee47..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 e8860007be..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/voice-2-secret-3.html b/data/telegram.org/blog/voice-2-secret-3.html deleted file mode 100644 index b2ac76b048..0000000000 --- a/data/telegram.org/blog/voice-2-secret-3.html +++ /dev/null @@ -1,245 +0,0 @@ - - - - - Voice Messages 2.0, Secret Chats 3.0 and... - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
- -
-
-

Voice Messages 2.0, Secret Chats 3.0 and...

- -
- -
- -

Voice messages on Telegram just got a completely new interface with waveform visualizations, a brand new player and raise-to-speak functionality.

-

You can now start listening to a long voice message and switch to other media or chats. The message will continue playing in the background. For who are we to defy the god of multi-tasking?

-
- -

New looks for voice messages

-
- -

Recording and listening to voice messages got easier with raise-to-speak and raise-to-listen. When a chat is open, bring your phone to your ear (as if taking a phone call) to listen to new voice messages or record a new one after the signal.

-
- -

Raise to Speak: Preview before sending

-
- -

This feature involves plenty of behind-the-scene magic with proximity sensors, gyroscopes and accelerometers. It works well with most modern devices, but is still experimental. Some phones may require arcane intervention from our devs.

-

Secret Chats 3.0

-

With their self-destruct timers and end-to-end encryption, secret chats are a great way to pass sensitive information. Today we’re bringing the best features from cloud chats over to secret chats: detailed link previews, replies, photo and video captions, sticker sharing, inline bots and GIFs. We’ve also improved key visualizations to make secret chats immune to potential alien invasions.

-
- -

A Secret Chat full of new goodies

-
- -

…and…

-

Privacy. When overly active friends start adding you to random groups or channels, it gets overwhelming quickly. Now you can decide who may add you to groups and channels with granular precision. E.g. “All my contacts. Except those two.”

-

Supergroups. Supergroup creators also get more control. They can now change who may add new members to their group: all existing members or only selected admins. Supergroups can have up to 1000 members, and finding a balance between order and chaos is important if you want them to grow.

-

Sharing extension. Sharing on iOS devices has become way smoother. You can now share any photo, video, audio, document or location to any Telegram chat or channel straight from default iOS apps like Contacts, Maps, Voice Memos and Photos. It is also possible to share stuff to several chats or channels at once.

-

Attachment Menu. Media files will zoom beautifully when you select them in the attachment menu. Note that we’ve moved ‘Image Search’ to the ’Photo or Video’ section (tap the magnifying glass icon in the top right corner).

-

Hotkeys. iPad users with external keyboards get hotkey support. Now you can navigate chats and send messages without ever touching your iPad’s screen. Saves a lot of time.

-

Photo Editor. In the Android corner, we’re introducing additional photo-editing tools – rotate, fade, tint and curves.

-
-
- -

Photo editor

-
-
- -

Curves tool

-
-
- -

We’re not done with updates this month – more features and good news are coming very soon to a Telegram Messenger near you.

-

- - -

February 12, 2016
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 index a374deaf50..70a7a17c18 100644 --- a/data/telegram.org/blog/voice-chats-on-steroids.html +++ b/data/telegram.org/blog/voice-chats-on-steroids.html @@ -13,7 +13,7 @@ - + diff --git a/data/telegram.org/blog/voice-chats.html b/data/telegram.org/blog/voice-chats.html deleted file mode 100644 index 5d9884d39a..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/tos.html b/data/telegram.org/tos.html deleted file mode 100644 index 35122515f3..0000000000 --- a/data/telegram.org/tos.html +++ /dev/null @@ -1,133 +0,0 @@ - - - - - Terms of Service - - - - - - - - - - - - - - - - - - - -
-
- -
-
-
-
-

Terms of Service

- -

By signing up for Telegram, you accept our Privacy Policy and agree not to:

-
    -
  • Use our service to send spam or scam users.
  • -
  • Promote violence on publicly viewable Telegram channels, bots, etc.
  • -
  • Post illegal pornographic content on publicly viewable Telegram channels, bots, etc.
  • -
-

We reserve the right to update these Terms of Service later.

-
-

Citizens of EU countries and the United Kingdom must be at least 16 years old to sign up.

-
-
- -
- -
-
-
- - - - - - - diff --git a/data/telegram.org/tour/screenshots.html b/data/telegram.org/tour/screenshots.html deleted file mode 100644 index 31b6bd3f55..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

-
- -
- - -
- - -
-
-
- - - - - - -